[ Contents ] [ Index
]
Monitoring JBODs
Enabling JBOD Support
To monitor peripheral device condition and
events of a JBOD, you first need to enable JBOD support.
- Choose View > Agent Options Management.
If you are not already logged in as ssconfig
or ssadmin, a password prompt is displayed; type the password.
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.
In a split-bus configuration, each port
is connected to its own HBA. 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.
NOTE: In a split-bus configuration,
if each port is connected to different servers, the program can only
monitor the JBOD from the server connected to port B.
Displaying Component and Alarm Characteristics
The View Enclosure window displays
the component and alarm characteristics of a JBOD.
When a JBOD is in a state that requires attention,
a device status state symbol is displayed on the JBOD device in the main
window. See Main
SANscape Window for a description of the symbols.
- Select the enclosure
icon.
- Choose View > View Enclosure.
To display FRU ID information,
click View FRU.
Environmental State
The Environmental State section of
the View Enclosure window reports the status of power supplies,
fans, and temperature. It provides an overall environmental status of
the array as well as the status of the individual components. For a description
of the Component/Status list, see View
Enclosure - Environmental State.
To determine power supply and fan locations,
refer to the SANscape User's Guide.
SAF-TE Temperature Sensor Locations
Monitoring temperature at different points
within the array is one of the most important SAF-TE functions. High temperatures
can cause significant damage if they go unnoticed. There are a number
of different sensors at key points in the enclosure. The following table
shows the location of each of those sensors, which corresponds to the
Temperature # displayed in the View Enclosure Component/Status
list.
SANnet II 100 SCSI Array SAF-TE Temperature
Locations
Temperature ID |
Location |
0, 1, 5 |
Temperature sensor on chassis |
2 |
Temperature sensor on power supply #0 |
3 |
Temperature sensor on left side EMU
module |
4 |
Temperature sensor on right side EMU
module |
6 |
Temperature sensor on power supply #1 |
Downloading Firmware for Devices
For instructions on how to download firmware
to disk drives on a Solaris host, refer to the README file in the patch
that contains the firmware. For patch information, refer to the release
notes for your array.
Discovering a 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.
Solaris OS
- 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
Linux OS
- Reboot the system.
- Run the command:
# dmesg
- In the dmesg output, look for a
line similar to:
Detected scsi disk sdX at scsi, id, lun
where X is the disk number.
- To create the device entries in /dev,
run the command
# cd /dev; ./MAKEDEV sdX
where X is the disk number.
- Proceed to fdisk, format, and create
a filesystem.
Microsoft Windows OS
- Install the new drive according to the
instructions included in the SANnet II Family 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 from the main window.
- Select View > View Physical Drive,
and verify the information.
HP-UX OS
- Run the command
# ioscan -fnC disk
- Select View > View Server, and
click Rescan.
- To verify that SANscape recognizes the
new drive, select it from 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 OS
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 Devices.
- 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 Step a-Step f 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
]
|