I was really impressed as I started my first SPB configuration on an Avaya switch, I had a 200 lines MPLS like configuration in mind and was surprised that you do not need a lot of commands to setup SPB. I walk you through the basic steps that you need for SPB. Here in this post I will only cover the basic setup.
First you need to enable SPB globally to get started, this requieres a reboot on the VSP7k and the ERS4k. At the ERS8k you need a premier license to get started.
After that command the device will reboot and come up partially defaulted, so that will be the first step to enable SPB. For the VSP7k to enable SPB on the rear-ports it also requieres a reboot, it can be applied with that command:
rear-port mode spbm
In the next step we have to create 2 SPB backbone VLANs. You can choose any VLAN ID you like. It is recommanded by Avaya to use 4051 and 4052.
vlan create 4051 name SPBM-1 type spbm-bvlan vlan create 4052 name SPBM-2 type spbm-bvlan
Than give your device a name. The sys name that you see on the CLI prompt is also used in SPB for L2 pings and trace routes. Here you should use something that is human readable.
snmp-server name VSP7k_10
Now we go to the router ISIS configuration and configure the area. BTW the 49 has nothing to do with country dial up code for Germany. It is the default area that we are using here. The system-id and nick-name have to be unique in your network. You can choose what ever you want, but make a good documentation of what you have done to prevent that never 2 devices uses the same ID. I usually borrow the numbers from the device IP adress for example the switch management IP would be 10.10.10.10 than I translate these digits into the nick-name and system-id.
router isis manual-area 49.0001 system-id 0010.0010.0010 spbm 1 spbm 1 nick-name 10.10.10
Now we have to enable isis:
router isis enable
The last step would be to enable SPB on the interfaces that you would like to use. It can run on a single interface or MLT. You only need dot1q encapsulation or tag all in Avaya terminilogy enabled on the particular ports or trunks.
interface Ethernet 1/1 isis isis spbm 1 isis enable
Note on the VSP7k it is only interface “ethernet” this can be diffrent like e.g. interface gigabitEthernet on the VSP4k depending on the device type and software.
Thats the complete basic configuration, your device is ready now to connect to anonther switch with an SPB configuration on port 1/1.
When you connect two switches with an SPB enabled interface with each other they will form up an adjacency
show isis adjacencies ================================================================================ ISIS Adjacencies ================================================================================ INTERFACE L STATE UPTIME PRI HOLDTIME SYSID HOST-NAME -------------------------------------------------------------------------------- Mlt1 1 UP 22:20:11 127 21 0010.0010.0012 ERS-12 Port1/1 1 UP 10:12:45 127 22 0010.0010.0010 VSP7k-10 Port1/2 1 UP 10:12:45 127 22 0010.0010.0011 VSP7k-11
Now you can create services that run over the SPB fabric like e.g. VLAN 2000 will mapped into I-SID 20002000 as a L2VSN service.
vlan create 2000 type port 1 vlan i-sid 2000 20002000
You can move an access port into VLAN 2000 that will be transported over the I-SID 20002000. On Any other SPB enabled switch in your network you would only type the two commands above and also add an acces port to VLAN 2000 that would provide L2 connection between these two acces ports. It is possible to use different VLANs on different switches, as long as the I-SID ID is the same you will have a connection. There are no configurations needed on any uplink ports no matter if the switches are directly connected or any number of switches are between them in the nwtwork path. In the moment you create the I-SID SPB will provide the shortest path across the network.