Feature |
Product |
Release introduced |
---|---|---|
run spbm installation script |
5320 Series |
Fabric Engine 8.6 |
5420 Series |
VOSS 8.4 |
|
5520 Series |
VOSS 8.2.5 |
|
5720 Series |
Fabric Engine 8.7 |
|
7520 Series |
Fabric Engine 8.10 |
|
7720 Series |
Fabric Engine 8.10 |
|
VSP 4450 Series |
VOSS 4.1 |
|
VSP 4900 Series |
VOSS 8.1 |
|
VSP 7200 Series |
VOSS 4.2.1 |
|
VSP 7400 Series |
VOSS 8.0 |
|
VSP 8200 Series |
VOSS 4.1 |
|
VSP 8400 Series |
VOSS 4.2 |
|
VSP 8600 Series |
VSP 8600 8.0 |
|
XA1400 Series |
Not Supported |
You can use a CLI script to quickly configure the SPB and IS-IS infrastructure to enable Fabric Connect on a switch. You can use the SPB script, rather than manually configure the minimum SPBM and IS-IS parameters.
Configure the SPB Ethertype.
Create an SPB instance.
Create an SPBM backbone VLAN and associate it to the SPB instance.
Create an SPBM secondary backbone VLAN and associate it to the SPB instance.
Add an SPB nickname.
Create a manual area.
Enable IS-IS on one of the switch interfaces.
Enable IS-IS globally.
Configure the IS-IS system name.
Configure the IS-IS system ID.
Configure SPBM port and MLT interfaces.
Clean up any SPBM configuration.
The following table displays the default values applied if you use the run spbm command. The SPB script creates some of the default values based on the MAC address of the switch, including the nickname and System ID value.
Parameter |
Default values |
---|---|
Ethertype |
0x8100 |
Primary B-VLAN |
4051 |
Secondary B-VLAN |
4052 |
Manual area |
49.0000 |
Nickname |
Derived from the chassis MAC |
System name |
IS-IS system name. By default, the system uses the global system name as the IS-IS system name, until you manually configure it. Also, the system does not save the global system name in the running configuration on the switch. |
System ID value |
Derived from the chassis MAC, using a different algorithm from that for the Nickname |
Note
The SPB script only creates the SPBM instance, VLAN, and other parameters if they do not exist. For example, if the SPBM instance and VLAN already exist, the SPB script does not create them. If the SPB script is unable to create a parameter because it already exists, then the script stops and the system displays an error message.