User guide

2–FastFabric TUI Menu
Fast Fabric IB Chassis Setup/Admin Menu
2-12 IB0054607-01 A
(All): The answer to Would you like to perform fabric link speed
error analysis
indicates whether iba_report -o slowlinks should be
run. If the user answers
y to this question, the Check for links
configured to run slower than supported
question is asked. If the
user answers
y, the -o misconfiglinks option will also be used for
iba_report. Additionally, if the user answers y to the Would you like to
perform fabric link speed error analysis
question, the Check for
links connected with mismatched speed potential
question will also
be asked. If the user answers
y, the -o misconnlinks option is also be
used for
iba_report.
Answering
y to all but the last 2 questions is recommended (these are the
defaults for each prompt). This checks all the ports in the fabric for any links
that have high error rates or are running at a lower speed than expected.
Any identified links should be diagnosed and corrected.
(Switch): If the user responds
n to all of the prompts, the showallports -C
command is run to allow the state and symbol error counts of all chassis ports to
be manually reviewed.
Control Chassis Fabric Manager
(Switch) The Configure Chassis Fabric Manager selection will assist in
controlling the Fabric Manager for any QLogic 12000 chassis with appropriate
license keys. This operation will be skipped for other chassis models.
Prompts will guide the user through selecting the control options:

restart - Unconditionally restart the Fabric Manager on master Management
Modules (MM), it will make sure it is not running on slave MMs.

restartall - Unconditionally restart the FM on master and slave MMs

run - make sure FM is running on master Management Modules (MM), it will
make sure it is not running on slave MMs.

runall - make sure FM is running on master and slave MMs

stop - Stop FM on master and slave MMs.
Prompts will also guide the user through selecting the Fabric Manager autostart
options:

enable - Enables Fabric Manager start on master MM upon chassis
boot/reboot, disabled Fabric Manager autostart on any slave MMs in
selected chassis.
NOTE:
If the fabric is homogeneous and all links are expected to be running at
full speed, answer
y to the last two questions as well.