IBM totalstorage 326, Справочник пользователя

Страница: 174 / 240

When activated, only ports with a GBIC or imbedded optics present
are included in the crossPortTest list of ports to test. For example, if
GBIC mode is activated:
v
Ports 0 - 6 (which have imbedded optics) are always included in
the testing.
v
Port 7 is only included if a GBIC is plugged into Port 7.
The state of the GBIC mode is saved in flash. It stays activated
(even after restarts or power on and off cycles) until it is disabled as
follows:
sw:admin> setGbicMode 0
An example mode of operation would be to disable the hub, set the
GBIC mode to 1, and execute the crossPortTest command with
singlePortAlso activated. The crossPortTest would then limit testing
to:
v
All ports with GBIC and embedded optics present
v
All ports with GBIC and embedded optics present and properly
cable loopbacked
v
Allow ports to be connected to itself (single port connections)
Note: If a GBIC is failing severely, such that the crossPortTest
cannot determine if a GBIC is even installed, that port is not
tested, and is not reported as failing. Therefore, it is
important to make sure that testing occurs on all the ports
that are intended. This can be done by observing the screen
messages from the crossPortTest.
diagClearError
Clears diagnostic errors detected on a specified port. If you do not
include the
port # parameter, all errors are cleared.
diagDisablePost
Disables POST processing. The start-up time without POST
processing is approximately 50-55 seconds for warm or cold starts.
A hub restarted without POST generates the DIAG-
POST_SKIPPED error.
Note: IBM recommends that POST processing always be executed
to ensure the operational status of the hub during the start
up stage.
diagEnablePost
Enables POST processing. The choice remains in effect across
power on and off cycles until toggled by the user. The start up time
with POST processing is approximately 110-120 seconds for a
warm POST and 165:175 seconds for a cold POST. The factory
default enables POST processing.
diagShow Summarizes the diagnostic results since the hub was last started
up, including POST results.
The diagShow command also allows you to loop on the command.
For example,
diagShow 4
162
Model 326 User’s Reference