
________________________________________________________________________________________________
____________________________________________________________________________________________
Page 11
4.1.3 Identify a Not Connected Device
There are a couple of methods to identify a not connected device:
1. The console error message displayed at boot time. (as previously shown).
2. This console error message displayed when a console disk exerciser attempts to exercise a not connected
device.
3. Using the WWIDMGR command, the console can also display the status of fibre channel devices controlled
by an HSG8x.
P00>>>wwidmgr -show wwid -udid 40 –full
[0] UDID:40 WWID:01000010:6000-1fe1-0000-04a0-ffff-fffe-0005-0000 (ev:wwid0)
- current_unit:40 current_col: 1 default_unit: 5901
via adapter via fc_nport Con DID Lun
- pga0.0.0.6.0 5000-1fe1-0000-04a2 Yes 210313 40
- pga0.0.0.6.0 5000-1fe1-0000-04a1 Yes 210513 40
- pga0.0.0.6.0 5000-1fe1-0000-04a4 No 210713 40
4.2 How to Use a Not Connected Device
4.2.1 Using FFAUTO to Autoboot Not Connected Devices
FFAUTO determines console behavior when the system is trying to autoboot. An autoboot is any boot other than a
manual >>> boot command. FFAUTO can be set to ON or OFF. The default state is OFF where console behavior
is not affected. FFAUTO is stored in non-volatile memory therefore its state persists across system resets and
power cycles.
>>> set FFAUTO ON
In the ON state, console behavior is affected during an autoboot. When the console is trying to autoboot, the
console attempts to boot from each “connected” device listed in the bootdef_dev environment variable (>>> show
botdef_dev). If the console reaches the end of the bootdef_dev list without successfully booting, the console goes
to the beginning of the bootdef_dev list and attempts booting again. Disks that are found in the not connected state
are changed to the connected state, thereby enabling the console to access that device.
Kommentare zu diesen Handbüchern