Contenues dans
Trouver plus de documentation
Ressources d'assistance comprises
| Télécharger cet ouvrage au format PDF
- CHAPTER 3
Subcommands for the Sun Enterprise Network Array
Hotplugging
- This section describes two of the luxadm subcommands that are used in hotplugging devices in a Sun Enterprise Network Array. See Chapter 5, "Hotplugging in the Sun Enterprise Network Array" for more information.
Removing Devices
- Use the remove_device subcommand to hot remove a device or a chain of devices.
- The remove_device subcommand interactively guides you through the hot removal of one or more devices. The remove_device subcommand:
-
- Offlines the device (this fails if the disk is open).
- Informs you when device(s) can be safely removed.
- Informs you which device to remove by blinking the activity LED on the enclosure.
- Requests confirmation that the list(s) is/are as expected.
- Removes the logical device(s) names for the device that was removed.
-
luxadm [ -v ] remove_device { enclosure,dev... | pathname... }
|
-
TABLE 3-1 remove_device
| Option/Argument | Description |
| enclosure | 1 is the enclosure name of a Sun Enterprise Network Array . |
| dev | 1 is the name of a specific disk in an enclosure . |
| pathname | is the physical or logical path name of a Sun Enterprise Network Array or a specific disk in an array1. |
| 1 See "Addressing a Sun Enterprise Network Array" on page 2". |
- Example:
-
# luxadm remove_device macs3,r1
WARNING!!! Please ensure that no filesystems are mounted on these
device(s).
All data on these devices should have been backed up.
The list of devices which will be removed is:
1: Box Name "macs3" rear slot 1
Please enter 'q' to Quit OR <Return> to Continue:
offlining: Drive in "macs3" rear slot 1
Hit any key after inserting/removing drives:
|
- You must physically remove the disk drive at this point.
-
Drive in Box Name "macs3" rear slot 1
Removing Logical Nodes:
Removing /dev/dsk/c1t81d0s0
Removing /dev/rdsk/c1t81d0s0
Removing /dev/dsk/c1t81d0s1
Removing /dev/rdsk/c1t81d0s1
Removing /dev/dsk/c1t81d0s2
Removing /dev/rdsk/c1t81d0s2
Removing /dev/dsk/c1t81d0s3
Removing /dev/rdsk/c1t81d0s3
Removing /dev/dsk/c1t81d0s4
Removing /dev/rdsk/c1t81d0s4
Removing /dev/dsk/c1t81d0s5
Removing /dev/rdsk/c1t81d0s5
Removing /dev/dsk/c1t81d0s6
Removing /dev/rdsk/c1t81d0s6
Removing /dev/dsk/c1t81d0s7
Removing /dev/rdsk/c1t81d0s7
#
|
Inserting Devices
- Use the insert_device subcommand for hot insertion of a new device or a chain of new devices. If you specify more than one enclosure, you can perform concurrent hot insertions on multiple busses.
- The insert_device subcommand interactively guides you through the hot insertion of one or more devices. The insert_device subcommand:
-
- Informs you when the device(s) can be safely inserted.
- Requests confirmation that the list(s) is/are as expected.
- Creates the logical device names for the new devices.
- Displays the logical path name for the devices.
-
luxadm [ -v ] insert_device enclosure,dev...
|
-
- Example:
-
# luxadm insert_device
Please hit <enter> when you have finished adding device(s):
|
- You must physically install the disk drive at this point.
-
Waiting for Loop Initialization to complete...
New Logical Nodes under /dev/es:
New Logical Nodes under /dev/dsk and /dev/rdsk :
c1t81d0s0
c1t81d0s1
c1t81d0s2
c1t81d0s3
c1t81d0s4
c1t81d0s5
c1t81d0s6
c1t81d0s7
#
|
Downloading Code
Downloading fcode
- Use the fcal_s_download subcommand to download new fcode into ALL the FC100/S Sbus Cards or to display the current version of the fcode in each FC100/S Sbus card
- When downloading new fcode, the fcal_s_download subcommand is interactive and expects user confirmation before downloading the fcode
-
Caution - Ensure that you download the correct file: usr/lib/firmware/fc_s/ fcal_s_fcode..
-
luxadm [ -v ] fcal_s_download [ -f fcode-file]
|
-
TABLE 3-3 fcal_s_download
| Option | Description |
| -f fcode-file | fcode-file is the name of the file that has the new fcode. If you invoke the fcal_s_download subcommand without the [ -f fcode-file ] option, the current version of the fcode in each FC100/S Sbus card is displayed. The version of the FC100/S Sbus Cards fcode released with this operating system is kept in the directory usr/lib/firmware/fc_s and is named fcal_s_fcode. |
Other Operations
Powering On Enclosures or Disk Drives
- Use the power_on subcommand to set a drive to its normal power on state. If you specify a Sun Enterprise Network Array disk drive, the power_on subcommand sets the specified disks to the normal start-up state.
-
luxadm [ -v ] power_on { enclosure[,dev]... | pathname...}
|
-
TABLE 3-4 power_on
| Option/Argument | Description |
| enclosure | 1 is the enclosure name of a Sun Enterprise Network Array . |
| dev | 1 is the name of a specific disk in an enclosure . |
| pathname | is the physical or logical path name of a Sun Enterprise Network Array or a specific disk in an array1. |
| 1 See "Addressing a Sun Enterprise Network Array" on page 2". |
Probing for Sun Enterprise Network Arrays
- Use the probe subcommand to display information about all attached Sun Enterprise Network Array. Information displayed includes the logical pathnames, the WWNs, and the enclosure names.:
-
-
TABLE 3-5 probe
| Option | Description |
| -p | also displays the physical pathname. |
- Example:
-
# luxadm probe
Found
SENA Name:dogbert Node WWN:1234123412341234
Logical Path:/dev/es/ses0
Logical Path:/dev/es/ses1
#
|
- Example:
-
# luxadm probe -p
Found
SENA Name:dogbert Node WWN:1234123412341234
Logical Path:/dev/es/ses0
Physical Path:/devices/sbus@3,0/SUNW,socal@0,0/sf@0,0/
ses@w1234123412341235,0:0
Logical Path:/dev/es/ses1
Physical Path:/devices/sbus@3,0/SUNW,socal@0,0/sf@0,0/
ses@w1234123412341236,0:0
#
|
Renaming a Sun Enterprise Network Array
- Use the enclosure_name new_name subcommand to change the enclosure name of one or more Sun Enterprise Network Arrays. The new name must be 16 or less characters. The only allowed characters are alphabetic or numeric digits.
-
luxadm [ -v ] enclosure_name #### enclosure... | pathname...
|
-
TABLE 3-6 enclosure_name
| Option/Argument | Description |
| #### | is the new enclosure name. |
| enclosure | 1 is the enclosure name of a Sun Enterprise Network Array . |
| pathname | is the physical or logical path name of a Sun Enterprise Network Array1. |
| 1 See "Addressing a Sun Enterprise Network Array" on page 2". |
Setting a Disk LED to the Blink Mode
- Use the led_blink subcommand to start blinking (flashing) the yellow LED associated with a specific disk. The led_blink subcommand only applies to subsystems that support this functionality.
-
luxadm [ -v ] led_blink { enclosure,dev... | pathname...}
|
-
TABLE 3-7 led_blink
| Option/Argument | Description |
| enclosure | 1 is the enclosure name of a Sun Enterprise Network Array . |
| dev | 1 is the name of a specific disk in an enclosure . |
| pathname | 1 is the physical or logical path name of a specific disk in an array . |
| 1 See "Addressing a Sun Enterprise Network Array" on page 2". |
- Example:
-
# luxadm led_blink /devices/sbus@3,0/SUNW,socal@0,0/sf@0,0/
ssd@w21000020370412ec,0:c,raw
LED state is BLINKING for device in location: front,slot 0
#
|
Expert Mode Subcommands
Reading Link Error Status Blocks
-
Caution - The rdls subcommand is for expert use only. It should only be used by users who are knowledgable about the Sun Enterprise Network Array subsystem and Fiber Channel Loops
- Use the rdls subcommand to read the link error status block from a specified device. The rdls subcommand also displays the link error status information for the Host Adapter associated with the specified device, if available.
-
luxadm -e [ -v ] rdls { enclosure[,dev]... | pathname...}
|
-
TABLE 3-8 rdls
| Option/Argument | Description |
| -e | The -e option (expert mode) is required for this subcommand. |
| enclosure | 1 is the enclosure name of a Sun Enterprise Network Array . |
| dev | 1 is the name of a specific disk in an enclosure . |
| pathname | is the physical or logical path name of a Sun Enterprise Network Array or a specific disk in an array1. |
| 1 See "Addressing a Sun Enterprise Network Array" on page 2". |
- Example
-
# luxadm -e rdls BOX
Link Error Status information for Device:
BOX
(AL_PA=0x9e)
Link Failures0
Loss of sync.-1159869698
Link Error Status information for the Host Adapter:
(AL_PA=0xef)
Link Failures123456
Loss of sync.7866121
Loss of signal.7867562
Primitive sequence protocol errors:4750704
Invalid transmission words8675309
CRC errors:123456
NOTE: These LESB counts are not cleared by a reset, only power
cycles.
These counts must be compared to previously read counts.
#
|
Reinitializing a Link
-
Caution - The forcelip subcommand is for expert use only and should be used with CAUTION. It will reset all ports on the loop and may cause the device addresses to change.
- Use the forcelip subcommand to force the link to reinitialize using the Loop Initialize Primitive (LIP) sequence. You can specify any device on the loop.
-
luxadm -e [ -v ] forcelip { enclosure[,dev]... | pathname...}
|
-
TABLE 3-9 forcelip
| Option/Argument | Description |
| -e | The -e option (expert mode) is required for this subcommand. |
| enclosure | 1 is the enclosure name of a Sun Enterprise Network Array . |
| dev | 1 is the name of a specific disk in an enclosure . |
| pathname | is the physical or logical path name of a Sun Enterprise Network Array or a specific disk in an array1. |
| 1 See "Addressing a Sun Enterprise Network Array" on page 2". |
|
|