Operating instructions
160 Cisco Systems Intelligent Gigabit Ethernet Switch Module
Verifying correct operation on the external switches (6500-1 and 6500-3)
This section includes some commands you can use to verify the desired configuration and
operation of the 6500s.
Basically, you can run the same set of commands as previously shown for the Cisco Systems
IGESMs. Naturally, there will be some differences in the output, but you want to make sure
that the proper ports are channeled and trunked and carrying the correct VLANs. Also watch
out for any admin down ports.
You should also be able to ping the following addresses:
Ping to BladeServer1 at 10.1.10.1
Ping to BladeServer1 at 10.1.15.1
Ping to BladeServer1 at 10.1.20.1
Ping to BladeServer1 at 10.1.25.1
Ping to BladeServer2 at 10.1.10.2
Ping to BladeServer2 at 10.1.20.2
Ping to BladeServer3 at 10.1.30.3
Ping to BladeServer4 at 10.1.35.4
Ping to BladeServer4 at 10.1.40.4
Ping to BladeServer4 at 10.1.45.4
Ping to BladeServer4 at 10.1.50.4
At this time, it is also possible to verify redundancy. This can be done by taking various
elements of the network down (links or devices, or both) to make sure that the network
operates as desired.
7.5.3 Topology 3a: Dual Cisco Systems IGESMs, two-port aggregation with
RSPAN
This topology (Figure 7-18) is similar to topology 2, but offers the option of a dedicated
RSPAN port on each of the Cisco Systems IGESMs. The disadvantage to this design is that,
assuming Spanning Tree costs places the two EtherChannel uplinks into forwarding, upon
failure of one of the EtherChannel uplinks, a higher than normal oversubscription will come
into play, which might impact performance.
As with topology 2, there is one case where high availability might still be an issue, and that is
if all uplinks from a single Cisco Systems IGESM were to go down, but the Cisco Systems
IGESM itself did not go down. In that case, the blade server NICs would be unable to detect
the upstream failure and issues would arise. Utilizing properly configured NIC Teaming and
Trunk Failover would resolve this issue.
Brief discussion about RSPAN for this topology example
Important: There are very specific rules for using RSPAN. Failure to comply with these
rules can result in unexpected and undesired results. Guidelines and use of RSPAN can be
reviewed at the following locations:
http://www.cisco.com/en/US/products/hw/switches/ps708/products_configuration_guide_chapt
er09186a008007f323.html
http://www.cisco.com/en/US/products/hw/switches/ps628/products_configuration_guide_chapt
er09186a00801a6ba9.html