Cisco Ethernet switch Operations Instructions download pdf (Page 138)

124 Cisco Systems Intelligent Gigabit Ethernet Switch Module

7.5 Example topologies and their configuration

This section provides several topologies and offers reasons for their selection, as well as

step-by-step configuration options.

7.5.1 Topology 1: Dual IGESMs, four-port aggregation to two 6500s

This example (in Figure 7-3) offers the maximum performance available from the BladeCenter

when using two Cisco Systems IGESMs, as well as redundancy, depending on the

configuration of the operating systems and features running on the blade servers and the

IGESMs within the BladeCenter. It makes use of two Cisco Systems IGESMs, each with all

four ports LACP aggregated into a single link, and each going to a separate Cisco switch. No

ports will be in a Spanning Tree blocking state with this configuration because each Cisco

Systems IGESM only has a single (albeit aggregated) connection into the layer 2 network.

Configurations presented for blade server attachment to this topology

The following list describes the blade server configuration (see Figure 7-3) for this example:

򐂰 BladeServer1: 802.1Q trunk links carrying multiple VLANs to a NIC.

This configuration is provided to show how to permit multiple VLANs to access each

individual NIC in the blade server. It demonstrates one way to isolate traffic types from

each other through several VLANs per NIC.

Broadcom teaming software is required, but no redundancy is used.

򐂰 BladeServer2: Access ports to NICs through individual connections.

This configuration is provided to show how to use each NIC as a standard access link. (No

VLANs, trunking, or redundancy is used from the blade server’s perspective.) This is the

traditional way most servers were attached in the past, and it is simple and effective, but

not very flexible.

This configuration is performed using the stock network configuration tools available in

Windows 2000. No teaming software is used.

We do not show NIC teaming examples suitable for Trunk Failover, which require the same

VLANs be carried to both NICs on the blade servers. For examples suitable for use with Trunk

Failover, see blade server configs for servers 3 and 4 in the Topology 2 example.

Important: This topology is not recommended in environments where high availability to

the blade server NICs is required, based on the possibility of loss of connectivity during an

all-uplink or aggregation switch failure and the inability of the blade server NICs to sense

this upstream failure through the Cisco Systems IGESM (without NIC Teaming or Trunk

Failover). To utilize this design for high availability, use NIC Teaming on the servers

(available with the BASP software) and Trunk Failover on the IGESMs (available with

12.1(14)AY4 and above). This section shows various forms of NIC Teaming but not Trunk

Failover. For an explanation on Trunk Failover and how to implement it, see 7.7, “Trunk

Failover feature description and configuration” on page 193.

Important: The blade server configurations in this chapter are not part of the topology

discussion; their configurations are provided to help explain some of the possibilities for

attaching the servers to this topology. The examples should

not be construed as the way a

blade server must be configured. If your only goal is to understand a given server

attachment example, review that specific example and its associated upstream connection

on the Cisco Systems IGESMs and ignore the extra blade server configurations.

1 ... 137 138 139 ... 266

Comments to this Manuals

No comments

Cisco Ethernet switch Operations Instructions Page 138

Comments to this Manuals

Related products and manuals for Networking Cisco Ethernet switch

Relacionado con productos y manuales para Auriculares inalámbricos Nokia HS 36W