shared virtual address to the GbESMs. This virtual address is configured as the GbESM’s default gateway.
The necessary static routes for the Core switch 1 are:
ip route 10.10.0.0 255.255.255.0 10.35.0.100 ip route 10.20.0.0 255.255.255.0 10.35.0.100
Because Core switch 2 uses VLAN 46 rather than 35 to send traffic to the GbESMs, its static routes are different as shown below:
ip route 10.10.0.0 255.255.255.0 10.46.0.100 ip route 10.20.0.0 255.255.255.0 10.46.0.100
Configuration on server blades to work with VRRP
The server blades default gateway must be set to work with the shared VRRP addresses configured on the GbESMs. This is done using by opening the properties dialog of the network object in Windows and then the properties dialog of the TCP/IP protocol:
Blade server 1 is only on VLAN 20 and will have a default gateway of 10.20.0.100.
Blade server 2 is on VLANs 10 and 20 using NIC teaming and tagging; each of the VLAN network objects will have its own default gateway. VLAN 10 will use 10.10.0.100; VLAN 20 will use 10.20.0.100.
Blade server 3 has the NIC attached to GbESM 1 on VLAN 10 and the NIC attached to GbESM 2 on VLAN 20 and will use the same addresses as blade server 2.
Reconnect procedure when configuration is ready
If the ports were disabled using the commands shown above, then
Enable the ports on GbESM1 and GbESM2
/oper/port EXT1/ena /oper/port EXT2/ena /oper/port EXT3/ena /oper/port EXT5/ena /oper/port EXT6/ena
Enable the ports on Core1 and Core2
conf t
int range
int range
Verifying operation of the configuration
You should use the commands in Example
To verify that ports are successfully connected to the other device and are in the prover VLAN, use the /i/port, /i/l2/trunk, and /i/link commands. The ports should be shown as being up. The trunks should be forwarding, and VLAN membership should be as shown in the configuration with tagging off.
Chapter 7. Nortel Networks L2/3 GbESM configuration and network integration 117