Setting a fabric name, Setting the switch priority – H3C Technologies H3C S5830V2 Series Switches User Manual
Page 55
44
principal switch and cannot obtain domain IDs dynamically. You must configure a unique domain ID for
each switch.
•
To dynamically build a fabric, you must enable the fabric configuration function on switches.
•
To statically set up a fabric, you must disable the fabric configuration function on switches and
manually configure domain IDs for the switches.
To enable or disable the fabric configuration function:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter VSAN view.
vsan vsan-id
N/A
3.
Enable or disable the
fabric configuration
function for the
VSAN.
•
Enable the fabric configuration
function:
domain configure enable
•
Disable the fabric
configuration function:
undo domain configure
enable
Enable or disable the function for all
switches in the VSAN as required.
By default, the fabric configuration function
is enabled.
Setting a fabric name
The fabric name configured takes effect only on a statically-built fabric. You must configure the same
fabric name for all switches in a VSAN.
To set a fabric name:
Step Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter VSAN view.
vsan vsan-id
N/A
3.
Configure a fabric
name.
fabric-name name
By default, the fabric name is null.
If the user does not configure a fabric name, the
switch WWN is used as the fabric name.
Setting the switch priority
The priority value for FC switches is in the range of 1 to 254. The smaller the value, the higher the priority.
The FC switch with the highest priority will be elected as the principal switch.
The priority is configured on a per-VSAN basis, and one FC switch can have different priorities in
different VSANs.
In a stable fabric, the configured priority does not take effect immediately. Therefore, the running priority
of a switch might be different from the configured priority. To validate the configured priority, use the
domain restart disruptive command to perform a disruptive reconfiguration. After a disruptive
reconfiguration, the running priority still might be different from the configured priority, depending on the
configured priority value, as shown in
.