[ Contents
] [ Index ]
Monitoring JBODs
Enabling JBOD Support
To monitor peripheral device condition and events of a JBOD, you first need to enable JBOD support.
- Select View > Agent Options Management. The Agent Options
Management window is displayed.
- Select the Enable JBOD Support check box.
- To immediately display the JBOD in the main window, you need to probe
for new inventory. Select View > View Server, and click Probe.
- Click OK. The JBOD is displayed in the main window.
In a single-bus configuration, both ports of the JBOD are connected
to one HBA on the server.
You can configure a split-bus, split-server configuration. In the split-server
configuration, a SAF-TE limitation prevents the main window from showing
the drives connected to Port A and Port B. The program can only monitor
the JBOD from the server connected to Port B.
Or, you can configure a split-bus, single-server configuration that uses two HBAs on
a single server. In the single-server configuration, SANscape compensates for the SAF-TE
limitation and displays all the drives connected to Port A and Port B.
Displaying Component and Alarm Characteristics
The View Enclosure window displays the component and alarm characteristics of a JBOD.
- Select the EMU
icon.
- Select View > View Enclosure.
To display FRU ID information, click View FRU.
Downloading Firmware for Devices
This option enables you to upgrade the firmware on hard drives and SAF-TE devices on the JBOD.
Upgrading Firmware on Hard Drives
- Select any JBOD component.
- Select Array Administration > Download FW for Devices.
- Click the Download FW for Disks tab.
- Select the drives that you want to download the new firmware to from Available Disks and click Add.
If there are logical drives that you want to remove, select them from Selected Disks and click Remove.
- Click Browse and locate the download firmware file. Select it, click Open, and click OK. The firmware starts to download.
- When the progress reaches 100%, click OK.
- To update SANscape, select View > View Server.
- Click Probe and click OK.
- To verify that the firmware has downloaded successfully, select View > View Physical Drive, and make sure the firmware version has changed in the Product Revision field.
Upgrading Firmware on SAF-TE Devices
- Select any JBOD component.
- Select Array Administration > Download FW for Devices.
- Click the Download FW for SAFTE Devices tab.
- To add a device, select it from Available SAF-TE Devices and click Add.
To remove a device, select it from Selected SAF-TE Devices and click Remove.
- Click Browse and locate the download firmware file. Select it and click Open.
- Click OK.
The firmware starts to download. The array starts beeping and the LEDs
start blinking at around 70%.
- When the progress reaches 100%, click OK.
- To update SANscape, select View > View Server, and click Probe.
- Click OK.
- To verify that the firmware has downloaded successfully, select View > View Enclosure, and make sure the firmware version has changed in the Firmware Rev field.
Replacing a Failed Drive
Drive failure places the JBOD in a critical state. A red device status symbol is displayed on the
JBOD device in the main window. After replacing a failed drive, perform the
following steps to discover the drive.
Solaris
- If the drive comes back online automatically (that is, the red device status symbol is dismissed), run the command:
devfsadmin
- Run the command:
format
- If the device does not come back online (that is, the red device status symbol is not dismissed), perform a reconfiguration reboot by running the command:
reboot -- -r
Microsoft Windows
- Install the new drive according to the instructions included in the
SANnet II Installation, Operation, and Service Manual for your
array.
- Select View > View Server, and click Rescan.
- To verify that SANscape recognizes the new drive, select it on the main window.
- Select View > View Physical Drive, and verify the information.
HP-UX
- Run the command:
# ioscan -fnC disk
- Select View > View Server, and click Rescan.
- To verify that the program recognizes the new drive, select it on the main window.
- Select View > View Physical Drive, and verify the information.
If the drive is still not seen, the host might need to be rebooted. Run the commands:
# sync;sync;sync
# reboot
IBM AIX
NOTE: You must have superuser privileges to run the commands necessary to replace a failed drive.
- Create the logical drive and map its LUN to the correct host channel.
- Run the command:
# cfgmgr
- Run the command:
# lspv
Output similar to the following is displayed:
hdisk0 000df50dd520b2e rootvg
hdisk1 000df50d928c3c98 None
hdisk1 000df50d928c3c98 None
- If any of the drives show "none," you need to assign a Physical Volume IDENTIFIER.
- Run the command:
# smitty
- Select Drives.
- Select Fixed Disk.
- Select Change/Show Characteristics of a Disk.
- Select the disk without a PVID.
- Select ASSIGN physical volume identifier, press Tab once to display Yes for the value, and
press Return.
- Press Return again to confirm and repeat steps a-e as necessary.
- From the smitty main menu, select System Storage Management (Physical & Logical Storage) > Logical Volume
Manager > Volume Groups > Add a Volume Group.
- Specify a name for the volume group, make sure the partitions for the journaled file system are large enough, and
select the Physical Volume Name(s).
- From the smitty main menu, select System Storage Management (Physical & Logical Storage) > File Systems >
Add / Change/ Show / Delete File Systems > (Enhanced) Journaled File System.
- Select the volume group and set the field.
Run the command:
# umount mount point
[ Contents ] [ Index
]
|