![background image](http://html1.mh-extra.com/html/ibm/nortel-networks-l2-3/nortel-networks-l2-3_manual_3481374131.webp)
Chapter 7. Nortel Networks L2/3 GbESM configuration and network integration
117
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 re-enable them using the
following commands. If they were merely unplugged, they can simply be plugged back in.
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 Po1-2
no shut
int range g0/1-2, g0/11-12
no shut
Verifying operation of the configuration
You should use the commands in Example 7-25 on page 118 and Example 7-26 on page 119
to verify that the configuration is functioning as intended.
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.
Summary of Contents for Nortel Networks L2/3
Page 2: ......
Page 8: ...vi Nortel Networks L2 3 Ethernet Switch Module for IBM Eserver BladeCenter...
Page 14: ...xii Nortel Networks L2 3 Ethernet Switch Module for IBM Eserver BladeCenter...
Page 28: ...14 Nortel Networks L2 3 Ethernet Switch Module for IBM Eserver BladeCenter...
Page 34: ...20 Nortel Networks L2 3 Ethernet Switch Module for IBM Eserver BladeCenter...
Page 70: ...56 Nortel Networks L2 3 Ethernet Switch Module for IBM Eserver BladeCenter...
Page 164: ...150 Nortel Networks L2 3 Ethernet Switch Module for IBM Eserver BladeCenter...
Page 182: ...168 Nortel Networks L2 3 Ethernet Switch Module for IBM Eserver BladeCenter...
Page 188: ...174 Nortel Networks L2 3 Ethernet Switch Module for IBM Eserver BladeCenter...
Page 189: ......