
Fabric OS 5.3.0 administrator guide 215
This procedure restores most configuration parameters to factory defaults. After performing this procedure,
you must check the new configuration and reconfigure those parameters that you customized in the old
configuration.
To convert a SAN Director 2/128 to support two domains:
1.
Connect to the switch and log in as admin.
2.
If the Director is already in a fabric, minimize disruption by removing the Director from the fabric using
one of the following methods:
• Physically disconnect the Director.
• Use the
portCfgPersistentDisable
command on all connected remote switches to
persistently disable their ports that are connected to the Director, or remove ISLs that connect the
SAN Director 2/128 to the current fabric.
3.
Enter the
chassisConfig
command to change the configuration from the default (one domain) to
two domains. This command reboots the system.
During the conversion, you are prompted to save the configuration of sw0. Follow the prompts to save
the configuration file.
4.
Enter the
ipAddrSet
command to set and confirm the IP address of sw1 (sw1 takes on a default that
must be corrected). The IP address of sw0 will already be set.
5.
After the system reboots, log in again as admin to each logical switch and enter the
switchName
command to assign a name to the new switch.
6.
Using the configuration file saved in
step 3
as a guide, manually reconfigure sw0 and sw1.
Do not configure zoning parameters; these are propagated automatically when you merge the Director
into the fabric.
7.
If the fabric is in secure mode, perform the following steps; otherwise, proceed to
step 8
.
a.
Optionally, to configure sw0 and sw1 in one operation, connect them with an ISL link to form a
temporary fabric.
b.
If you want sw0 and sw1 to be fabric configuration servers, update the overall fabric’s FCS policy to
include them. If not, skip this step.
c.
On sw0, enable security mode and use the
secModeEnable
command to create an FCS list that
matches your overall fabric’s FCS policy.
d.
Reset the version stamp on sw0.
e.
If you connected sw0 and sw1 in
step a
and you do not want them connected, disconnect the ISL
link between them. If you did not connect them, repeat
step 7b
through
step 7d
on sw1.
8.
If you physically disconnected the switch in
step 2
, reconnect it to the fabric.
9.
If you used the
portCfgPersistentDisable
command in
step 2
, use the
portCfgPersistentEnable
command to persistently enable all ports that connect the switch to
other switches in the fabric.
10.
Enter the
fabricShow
command to verify that sw0 and sw1 have been merged with the fabric.
11.
Enter the
configShow
command to verify that zoning parameters were propagated.
NOTE:
This procedure restores most configuration parameters to factory defaults. After
performing this procedure, you must check the new configuration and reconfigure those
parameters that you customized in the old configuration.
During this procedure, power is reset and the CP blades are rebooted, so traffic on the fabric is
disrupted. If the fabric is in secure mode, enabling security on the new domains is a complicated
task. You should avoid converting existing SAN Director 2/128 models that are acting as the core
in a core-edge network.
switch:admin>
chassisconfig 2
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 ...