LUXADM(1M) | Maintenance Commands | LUXADM(1M) |
luxadm [options]... subcommand [options]... enclosure [,dev] | pathname...
The command line must contain a subcommand. The command line may also contain options, usually at least one enclosure name or pathname, and other parameters depending on the subcommand. You need specify only as many characters as are required to uniquely identify a subcommand.
Specify the device that a subcommand interacts with by entering a pathname. For the SENA subsystem, a disk device or enclosure services controller may instead be specified by entering the World Wide Name (WWN) for the device or a port to the device. The device may also be specified by entering the name of the SENA enclosure, and an optional identifier for the particular device in the enclosure. The individual FC_AL devices may be specified by entering the WWN for the device or a port to the device.
For SENA, a typical physical pathname for a device is:
/devices/sbus@1f,0/SUNW,socal@1,0/sf@0,0/ssd@w2200002037000f96, 0:a,raw
For all SENA IBs (Interface Boards) and Sun Fire 880 SES device controllers on the system, a logical link to the physical paths is kept in the directory /dev/es. An example of a logical link is /dev/es/ses0.
The WWN may be used in place of the pathname to select an FC_AL device, SENA subsystem IB, or Sun Fire 880 internal storage subsystem. The WWN is a unique 16 hexadecimal digit value that specifies either the port used to access the device or the device itself. A typical WWN value is:
2200002037000f96
See NOTES for more information on the WWN formats.
For a disk in a Sun Fire 880 internal storage subsystem, a typical physical pathname is:
/devices/pci@8,600000/SUNW,qlc@2/fp@0,0/ssd@w2100002037a6303c,0:a
and a typical logical pathname is:
/dev/rdsk/c2t8d0s2
For individual FC_AL devices, a typical physical pathname is:
/devices/sbus@3.0/SUNW,socal@d,10000/sf@0,0/ssd@w2200002037049fc3,0:a,raw
and a typical logical pathname is:
/dev/rdsk/c1t0d0s2
box_name is the name of the SENA enclosure, as specified by the enclosure_name subcommand. When used without the optional slot_number parameter, the box_name identifies the SENA subsystem IB.
f or r specifies the front or rear slots in the SENA enclosure.
slot_number specifies the slot number of the device in the SENA enclosure, 0-6 or 0-10.
For a Sun Fire 880 internal storage subsystem, a device may also be identified by its enclosure name and slot name. However, there is only one set of disks:
box_name[,sslot_number]
box_name is the name of the Sun Fire 880 enclosure, as specified by the enclosure_name subcommand. When used without the optional slot_number parameter, box_name identifies the Sun Fire 880 internal storage subsystem enclosure services device. Use s to specify the disk slot number in the Sun Fire 880 internal storage subsystem, 0 - 11.
See disks(1M) and devlinks(1M) for additional information on logical names for disks and subsystems.
-e
-v
Options that are specific to particular subcommands are described with the subcommand in the USAGE section.
enclosure
fibre_channel_HBA_port
/devices/pci@8,600000/pci@1/SUNW,qlc@4/fp@0,0:devctl
pathname
Subsystem data consists of enclosure environmental sense information and status for all subsystem devices, including disks.
Disk data consists of inquiry, capacity, and configuration information.
-p
-r
-v
download [ -s ] [ -f filename_path ] enclosure...
When the SENA's download is complete, the SENA will be reset and the downloaded code executed. If no filename is specified, the default prom image will be used. The default prom image for the SENA is in the directory /usr/lib/locale/C/LC_MESSAGES and is named ibfirmware
When the Sun Fire 880 internal storage subsystem's download is complete, the subsystem resets and the downloaded code begins execution. The default firmware image for the Sun Fire 880 internal storage subsystem is in: /usr/platform/SUNW,Sun-Fire-880/lib/images/int_fcbpl_fw.
-s
The -s option does not apply to the Sun Fire 880 internal storage subsystem as it always stores downloaded firmware in the flash memory.
When using the -s option, the download subcommand modifies the FEPROM on the subsystem and should be used with caution.
enclosure_name new_name enclosure | pathname
failover primary | secondary pathname
fcal_s_download [ -f fcode-file ]
Use fcal_s_download only in single-user mode. Using fcal_s_download to update a host adapter while there is I/O activity through that adapter will cause the adapter to reset. Newly updated FCode will not be executed or visible until a system reboot.
-f fcode-file
fcode_download -p
fcode_download -d dir-name
Use fcode_download to load FCode only in single-user mode. Using fcode_download to update a host adapter while there is I/O activity through that adapter causes the adapter to reset. Newly updated FCode will not be executed or visible until a system reboot.
-d dir-name
-p
inquiry enclosure[,dev ]... | pathname...
insert_device [ enclosure,dev... ]
led enclosure,dev...| pathname...
led_blink enclosure,dev...| pathname...
led_off enclosure,dev...| pathname...
led_on pathname...
power_off [ -F ] enclosure[,dev]... | pathname ...
-F
Warning: Powering off a device which has data that is currently being used will cause unpredictable results. Users should attempt to power off the device normally (without -F) first, only resorting to this option when sure of the consequences of overriding normal checks.
power_on enclosure[,dev]..
probe [ -p ]
-p
qlgc_s_download [ -f fcode-file ]
-f fcode-file
release pathname
This subcommand is included for historical and diagnostic purposes only.
remove_device [ -F ] enclosure[,dev]...| pathname...
For Multi-Hosted disk, the steps taken are:
-F
Warning: Removal of a device which has data that is currently being used will cause unpredictable results. Users should attempt to hotplug normally (without -F) first, only resorting to this option when sure of the consequences of overriding normal hotplugging checks.
reserve pathname
This subcommand is included for historical and diagnostic purposes only.
set_boot_dev [ -y ] pathname
start pathname
stop pathname...
If you specify a disk to an expert subcommand that operates on a bus, the subcommand operates on the bus to which the specified disk is attached.
-e bypass [-ab]
enclosure,dev
-e bypass -f enclosure
This subcommand supports the following options:
-a
-b
-e dump_map fibre_channel_HBA_port
-e enable [-ab]
enclosure,dev
-e enable -f enclosure
This subcommand supports the following options:
-a
-b
-e forcelip enclosure[,dev] ... | pathname...
This is an expert only command and should be used with caution. It will reset all ports on the loop.
-e rdls enclosure[,dev] ... | pathname...
These commands do not apply to the Sun Fire 880 internal storage subsystem.
-e bus_getstate pathname
-e bus_quiesce pathname
-e bus_reset pathname
-e bus_resetall pathname
-e bus_unquiesce pathname
-e dev_getstate pathname
-e dev_reset pathname
-e offline pathname
-e online pathname
The following example finds and displays all of the SENAs and individual FC_AL devices on a system:
example% luxadm probe
Example 2 Displaying a SENA or Sun Fire 880 Internal Storage Subsystem
The following example displays a SENA or Sun Fire 880 internal storage subsystem:
example% luxadm display /dev/es/ses0
Example 3 Displaying Two Subsystems
The following example displays two subsystems using the enclosure names:
example% luxadm display BOB system1
Example 4 Displaying Information about the First Disk
The following example displays information about the first disk in the front of the enclosure named BOB. Use f to specify the front disks. Use r to specify the rear disks.
example% luxadm display BOB,f0
Example 5 Displaying Information on a Sun Fire 880 Internal Storage Subsystem
The Sun Fire 880 internal storage subsystem has only one set of disks. In this case, use s to specify the slot:
example% luxadm display BOB,s0
Example 6 Displaying Information about a SENA disk, an Enclosure, or an Individual FC_AL Drive
The following example displays information about a SENA disk, an enclosure, or an individual FC_AL drive with the port WWN of 2200002037001246:
example% luxadm display 2200002037001246
Example 7 Using Unique Characters to Issue a Subcommand
The following example uses only as many characters as are required to uniquely identify a subcommand:
example% luxadm disp BOB
Example 8 Displaying Error Information
The following example displays error information about the loop that the enclosure BOB is on:
example% luxadm display -r BOB
Example 9 Downloading New Firmware into the Interface Board
The following example downloads new firmware into the Interface Board in the enclosure named BOB (using the default path for the file to download):
example% luxadm download -s BOB
Example 10 Displaying Information from the SCSI Inquiry Command
The following example displays information from the SCSI inquiry command from all individual disks on the system, using only as many characters as necessary to uniquely identify the inquiry subcommand:
example% luxadm inq /dev/rdsk/c?t?d?s2
Example 11 Hotplugging
The following example hotplugs a new drive into the first slot in the front of the enclosure named BOB:
example% luxadm insert_device BOB,f0
The following example hotplugs a new drive into the first slot in the Sun Fire 880 internal storage subsystem named SF880-1:
example% luxadm insert_device SF880-1,s0
Example 12 Running an Expert Subcommand
The following example runs an expert subcommand. The subcommand forces a loop initialization on the loop that the enclosure BOB is on:
example% luxadm -e forcelip BOB
Example 13 Using the Expert Mode Hot Plugging Subcommands
An example of using the expert mode hot plugging subcommands to hot remove a disk follows. See NOTES for hot plugging limitations.
The first step reserves the SCSI device so that it can't be accessed by way of its second SCSI bus:
example# luxadm reserve /dev/rdsk/c1t8d0s2
Example 14 Taking the Disk to be Removed Offline
The next two steps take the disk to be removed offline then quiesce the bus:
example# luxadm -e offline /dev/rdsk/c1t8d0s2 example# luxadm -e bus_quiesce /dev/rdsk/c1t8d0s2
Example 15 Unquiescing the Bus
The user then removes the disk and continues by unquiescing the bus, putting the disk back online, then unreserving it:
example# luxadm -e bus_unquiesce /dev/rdsk/c1t8d0s2 example# luxadm -e online /dev/rdsk/c1t8d0s2 example# luxadm release /dev/rdsk/c1t8d0s2
0
−1
/usr/lib/locale/C/LC_MESSAGES/ibfirmware
luxadm: can't acquire "PATHNAME": No such file or directory
will be displayed.
You must be careful not to quiesce a bus that contains the root or the /usr filesystems or any swap data. If you do quiesce such a bus a deadlock can result, requiring a system reboot.
May 17, 2020 |