
Fabric OS 5.3.0 administrator guide 209
Disabling and enabling port blades
Port blades are enabled by default. In some cases, you will need to disable a port blade to perform
diagnostics. When diagnostics are executed manually (from the Fabric OS command line), many
commands require the port blade to be disabled. This ensures that diagnostic activity does not interfere
with normal fabric traffic.
To disable a port blade:
1.
Connect to the switch and log in as admin.
2.
Enter the
bladeDisable
command with the slot number of the port blade you want to disable:
To enable a port blade:
1.
Connect to the switch and log in as admin.
2.
Enter the
bladeEnable
command with the slot number of the port blade you want to enable:
B-Series MP Router blade (FR4-18i) exceptions
You may wish to persistently disable B-Series MP Router blade ports that are not configured so they cannot
join the fabric when the following scenarios apply:
•
You have inserted the blade into a slot that was previously empty or contained an FC4-48, FC4-32,
FC4-16, or FC4-16IP.
•
You have turned on the power of the chassis and the B-Series MP Router blade in that slot was not
active prior to the power-on.
If the B-Series MP Router blade is operational and the switch is rebooted, then after the successful boot up
of the system the blade will continue operations using the previous configurations.
If a previously configured B-Series MP Router blade is removed and another or the same B-Series MP Router
blade is inserted into the same slot, then the ports will use the previous configuration and come up
enabled.
If a previously-configured B-Series MP Router blade is removed and an FC4-48, FC4-32, or FC4-16 blade
is plugged in, then–other than the port’s EX_Port configuration–all the remaining port configurations
previously applied to the B-Series MP Router FC_Ports can be used. So the EX_Port configuration on those
ports will be disabled before the FC4-48, FC4-32, or FC4-16 blade becomes operational. When a blade
is present in the slot, then any requested port configuration is validated against the blade’s capabilities
before accepting the request.
To summarize:
•
When an FC4-16 or FC4-32 blade is replaced by an B-Series MP Router blade, the FC configuration of
the previously configured FC_Ports will continue to be used, and all FC_Ports on the B-Series MP Router
blade will be persistently disabled.
•
When an B-Series MP Router blade is replaced by an FC4-16 or FC4-32 blade, then the EX_Port
configuration will be removed from any ports that were configured as EX_Ports (equivalent to disabling
the EX_Port configuration using the
portCfgEXPort
command). All remaining port configurations will
be retained.
FC4-48 blade exceptions
The FC4-48 blade is compatible only with the FC4 control processor blade, FC4-16/32 port blade,
B-Series MP Router, and FC4-16IP iSCSI blade.
Because the area IDs are shared with different port IDs, the FC4-48 blade only supports F, G and E_Ports.
Port swapping on an FC4-48 is supported only on ports 0–15. For the FC4-32 blade port swapping is
supported on all 32 ports. This means that if you replace an FC4-32 where a port has been swapped on
switch:admin>
bladedisable 3
Slot 3 is being disabled
switch:admin>
bladeenable 3
Slot 3 is being enabled
Summary of Contents for AA979A - StorageWorks SAN Switch 2/8V
Page 1: ...HP StorageWorks Fabric OS 5 3 x administrator guide Part number 5697 0244 November 2009 ...
Page 16: ...16 ...
Page 20: ...18 ...
Page 24: ...24 Introducing Fabric OS CLI procedures ...
Page 116: ...118 Maintaining configurations ...
Page 170: ...172 Managing administrative domains ...
Page 200: ...202 Installing and maintaining firmware ...
Page 222: ...224 Routing traffic ...
Page 274: ...286 Administering FICON fabrics ...
Page 294: ...306 Working with diagnostic features ...
Page 350: ...362 Administering Extended Fabrics ...
Page 438: ...440 Configuring the PID format ...
Page 444: ...446 Configuring McData Open Fabric mode ...
Page 450: ...452 Understanding legacy password behaviour ...