© 2004 emc corporation. all rights reserved. 111 networker management console: device configuration...

© 2004 EMC Corporation. All rights reserved. 111

NetWorker Management Console:Device Configuration

Product OverviewAugust 2005


Device Configuration Development Team

Email alias: devgui

Keith LoPresto

Lai Fong Ho

Minh Chau

Mu Chai

Pallapotu Ramesh


Agenda Overview and Benefits

Limitations

Installation Requirements

Web Browser Requirements

Architecture – Process Interaction

Device Configuration GUI

– Launch Device Configuration GUI

– Add Storage Node

– Auto Configure SCSI/NDMP Libraries

– Monitor Status

– Auto Configure Silo Libraries

– Re-configure a Library: Add & Remove Devices

– Scan for Devices

– Custom Configure a Library

– Configure Stand-alone Tape Drive

– Add Stand-alone Device (File, ADV_File and Tape)

– Delete Stand-alone Device

Auto Configuration Failure and Common Causes

Troubleshooting

Preview: Post Keystone Beta Devices GUI


Overview and Benefits

Problem– No Graphical User Interface (GUI) for configuring and re-configuring

devices to NetWorker

This feature solves the problem by:– Providing a GUI for auto configuring libraries within NetWorker– Providing a GUI for re-configuring NetWorker libraries


Limitations

Only support auto configuring SCSI, NDMP and STL Silo library types

Does not support auto configuring RSM and AlphaStor library types

- use jbconfig CLI to configure RSM and AlphaStor libraries

Does not support auto configuring library which does not return its devices’ serial number

- use “sn –a b.t.l” CLI to verify that the library does not return its

devices’ serial number

- use jbconfig CLI to configure libraries which do not return

serial numbers

Does not support auto configuring NDMP library on NDMP Tape Server running at NDMP Protocol version 2.

- use jbconfig CLI to configure NDMP libraries on NDMP Tape Server

running at NDMP Protocol version 2.


Installation Requirements

NetWorker 7.3 Management Console Server

NetWorker 7.3 Server

NetWorker 7.3 Storage Node


Web Browser Requirements

– AIX• Mozilla 1.8• Netscape 4.7.2

– HP/UX• Mozilla 1.6

– Linux• Mozilla 1.4

– Solaris 8 & 9• Netscape 6.2.3

– Solaris 10• Mozilla 1.7

– Windows2003 Enterprise or Datacenter Edition• IE 6.x

– Windows XP, 2000, or 2003 (32-bit)• IE 5.5 or 6.x• Netscape 4.7.6 or 7.x



gstdhttp1loads

2

Web start

3

Console ClientConsole Server

splash.html

Welcome …

NW server

nsrd

nsrmmdbd

nsrexecd

browser

RPC

4app

nsrjobsdRPC



gstd

Console Client Console Server NW Server

nsrd

ddmgr

NW StorageNode

dvdetect

NW StorageNode

dvdetect

…

RPC

DeviceConfig

GUI

RPC

RAP DB

Communication between processes

Spawn process

Communication

App

Device Detection process

Device Detection Managerddmgr

dvdetect


Launch Device Configuration GUI Link to your NMC server

Click to Login


Launch Device Configuration GUI



Launch db5’s NetWorker Administrator


Launch Device Configuration GUI Click on the “Devices” icon



Pull down the list and select “Device Configuration”


Device Configuration GUINW server Storage nodes folder

Storage nodes


Device Configuration GUI

Libraries folder Stand-alone Devices folder


Add Storage Node• Auto configuration performs on storage nodes• Add storage node as needed


Add Storage Node Enter storage node name


Add Storage Node server defaultmaximal sharingno sharing

Device SCSI addresses that will be excluded from the scan and auto configuration


Add Storage Node

Will be used by scan and auto configuring NDMP libraries


Add Storage Node

Click to create storage node


Add Storage Node


Auto Configure SCSI/NDMP Libraries


Auto Configure SCSI/NDMP Libraries maximal sharingno sharing

Check SCSI/NDMP Library type


Auto Configure SCSI/NDMP Libraries

server defaultmaximal sharingno sharing

Select the library type to be configured

Click to Start auto configuration


Configure all Libraries Wizard

Click to exit wizard


Monitor Status

Click to switch to “Monitoring” pane


Monitor Status Click to switch to Device Configuration pane


Device Configuration GUI Auto configured library


Auto Configure Silo Library



Click to test the Silo controller connectivity

Note: “DAS Client Name” is required only for the “DAS Silo” type Controller

ACSLS Silo (Storage Tek)DAS Silo(ADIC/EMASS/Grau)3494 Silo (IBM)



Click to start configuration



Click to exit wizard


Re-configure a Library: Remove Devices



Uncheck to remove device

Click to start the Configuration



dlt7000(4) is removed from the library


Scan for Devices• Run “Scan for Devices” to discover removed devices


Scan for Devices

Click to start Scan

Select Device type to be scanned


Scan for DevicesUn-configured device is found in the library


Re-configure a Library: Add Devices



Check to add to library

Click to start the Configuration



dlt7000(4) is added to the library


Custom Configure a Library

• Run “Scan for Devices” to discover new devices


Custom Configure a Library


Custom Configure a Library Configure to the library

Not configure to the library

Click to start configuration


Custom Configure a LibraryCustom configured library


Configure Stand-alone Tape Drive

• Configure an unconfigured stand-alone tape drive automatically



Stand-alone Tape drive is configured


Add Stand-alone Device (File, ADV_File and Tape)

• Add/Create a new stand-alone device by hand


Add Stand-alone Device

Click to create device

Note: If the device is configured on a remote storage node, the “Name” should have the “rd=<hostname>:” prefix. For example: rd=pa1lho:e:\tmp\test


Add File Type Device

Stand-alone ADV_file is added


Delete Stand-alone Device


Auto Configuration Failure and Common Causes

Auto Configuration Failure

After auto configuration is finished:

- No library is auto configured

- Library is shown as unconfigured library

Common Causes

- Device driver is not installed properly

- Auto detection fails to match up detected library and its devices:

- Old device firmware

- Library does not return its devices’ serial numbers

- Auto detection is failed to start on storage nodes


Troubleshooting

Check the Monitoring -> Log

Run the “sn –a b.t.l” CLI to verify that the library returns its devices’ serial number

If b.t.l of a library is not known, run the inquire CLI first

BusbTargettLUNl


Troubleshooting – Auto Configuration Failure

Device Driver is not installed properly



• Device Paths are missing. Most likely the device driver is not installed properly

Expected:Tape, \\.\Tape0Tape, \\.\Tape1



• Library does not return its devices’ serial numbers. Check if the firmware is up-to-dated, or if the library is not able to return its devices’ serial numbers.

G:\>sn -a 2.0.0<Medium Changer Device ATL P1000 6220051 2.23 at [email protected]> <Medium Changer S/N> 915AA11531 <Medium Changer SCSI-3 Device Identifiers> ATNN=ATL Products P3000 IENN=2222222222222222<Data Transfer Element 128> <Serial Number> CX910S5252<Data Transfer Element 129> <Serial Number> CX910S6334

Example 1:

Example 2:



Failed to start auto detection on the NDMP server


Preview: Post Keystone Beta Devices GUI• Consolidate “Device Configuration” and “Device Operations”• “Configure all Libraries” and “Scan for Devices” will be accessible throughout the entire Devices GUI

Device Operations

Device Configuration



• Libraries folder contains all libraries on NW server



• Devices folder contains all devices on NW server



• Storage Nodes folder contains all storage nodes on NW server

© 2004 emc corporation. all rights reserved. 111 networker management console: device configuration...

Documents

emc corporation

device configuration

auto configuration slide

storage node slide

x slide

needed slide

login slide

devices folder slide