7.5.3 Base configuration common to all examples
This section lists some established configuration options that are common to all of the examples. These are only for demonstration purposes in the examples and might or might not be duplicated in your particular environment.
Management Module settings for Nortel GbESMs
Each Nortel GbESM is configured with an IP address for the MGT1 ports (see Figure
GbESM_1 is configured with 9.42.171.243 and mask 255.255.255.0
GbESM _2 is configured with 9.42.171.244 and mask 255.255.255.0
The default gateway is set to the internal interface of the Management Module 9.42.171.242
Both GbESMs have Fast POST enabled
Both GbESMs have External Ports enabled
Both GbESMs have External Management over all Ports enabled
Both GbESMs have Preserve new IP configuration on all resets enabled
We do not discuss the Management Module configuration from this point forward. There are no changes to the settings listed above.
IP address and VLAN scheme
The IP address for all lab examples is written as 10.x.0.y. The x identifies the VLAN while the y identifies the switch. An example of this would be 10.99.0.245. The 99 identifies VLAN 99 which is a management VLAN created for the examples. The last octet being 245 distinguishes the IP address as one belonging to Core1. Core1 will always have the last octet of 245. The last octet for Core2 is 246, GbESM_1 is 243, and GbESM_2 is 244. Each blade will have the slot number for the last octet (example: slot 1 would be 1). The net mask is 255.255.255.0 throughout these examples. Also of note, GbESM_1 is the switch module in slot 1 of the BladeCenter chassis.
All example configurations have some combination of the following VLANs configured: VLAN 1, 5, 10, 20, 35, 36, 45, 46, or 99.
Note: The VLANs chosen here are only for the purposes of demonstration and might or might not be a part of your particular network.
All configurations assume that VLANs carried on 802.1Q trunks are limited to only those that are necessary (this is good security practice). Additionally, VLAN 5 is created for use as the untagged or native VLAN on 802.1Q links.
Blade server configuration with BASP
A team of both blade Ethernet interfaces is made by launching the BASP Advanced Control Suite software. Smart Load Balance and Failover is the teaming feature used in this document. The following VLANs are placed on the blade servers (exact number and placement depends on trunking and teaming for the given example):
Blade Server 1: VLAN 20
Blade Server 2: VLAN 10, 20
Blade Server 3: VLAN 10, 20
Blade Server 4: VLAN 99
68Nortel Networks L2/3 Ethernet Switch Module for IBM Eserver BladeCenter
