Operating instructions

Chapter 7. Cisco Systems IGESM configuration and network integration 163
configuration. From the Cisco Systems IGESM’s perspective, both connections are
configured as simple access ports with a static VLAN assigned.
– This configuration uses of the Broadcom teaming software to bind and balance the
links together. The Cisco Systems IGESMs will establish what VLAN the teamed ports
will be placed into (it will need to be the same for both Cisco Systems IGESM ports that
go to this server).
– The example for BladeServer3 provided in this chapter uses what is known as
Active/Active, or Server Load Balancing, such that both interfaces can be carrying
traffic at the same time. This is opposed to Active/Standby (not shown here), also
known as Hot Standby, where only one of the links is up at a time.
򐂰 BladeServer4: 802.1Q trunk links carrying multiple VLANs on a teamed/SLB connection to
the server.
This configuration is provided to show how to use multiple NICs to look like a single NIC,
but still make use of multiple VLANs on this single logical NIC. It makes use of the teaming
drivers to tie the NICs together and create the desired VLANs. From the Cisco Systems
IGESMs perspective, both connections are configured as trunk ports, carrying a common
set of VLANs (you need to configure the same VLANs on both of the Cisco Systems
IGESM ports going to this server’s four logical NICs).
– This example uses the Broadcom teaming software to bind and balance the links
together and create the logical interfaces that will represent the various VLANs
demonstrated in this document.
– The example for BladeServer4 provided in this chapter uses what is known as
Active/Active, or Server Load Balancing, such that both interfaces can be carrying
traffic at the same time. This is opposed to Active/Standby (not shown here), also
known as Hot Standby, where only one of the links is up at a time.
Important: To ensure blade servers 3 and 4 achieve the highest availability, Trunk Failover
should also be configured (not shown in this example). For details and requirements on
configuring the Trunk Failover feature, see 7.7, “Trunk Failover feature description and
configuration” on page 193.