© Copyright IBM Corp. 2004, 2005. All rights reserved. 227
Appendix A. Hints and tips
In this section, we provide hints and tips that may prove useful during the setup, configuration,
and operation of your Cisco Systems Intelligent Gigabit Ethernet Switch Module for the
IBM Eserver BladeCenter.
As noted elsewhere in this document, the information herein applies to the 4-port
copper-based IGESM running a 12.1(14) version of IOS. If working with the 4-port SFP-based
IGESM or a 4-port copper-based IGESM running 12.1(22) and above code, see the
appropriate document for those solutions.
Blade server NIC numbering
The topic of which connection on a given blade server goes to which Cisco Systems IGESM
in the BladeCenter is the subject of some discussion.
The fact is that the physical first NIC on an HS20/JS20 blade server will always go to the
IGESM in bay 1 (top bay) and the second physical NIC on an HS20/JS20 blade server will
always go to the IGESM in bay 2 (bottom bay). This is hardwired in the BladeCenter and can
not be changed.
With that said, the operating system running on the blade server usually attempts to apply
logical names to these physical NICs, and they may be backward from what is expected. We
now discuss how this can come about and how to tell which logical connection goes to which
physical NIC.
In
most cases, for Windows 2000, the connection named Local Area Connection goes to the
Cisco Systems IGESM in switch bay 1 (referred to as CIGESM1 in Chapter 7, “Cisco Systems
IGESM configuration and network integration” on page 99), and the connection named Local
Area Connection 2
goes to the Cisco Systems IGESM in switch bay 2 (referred to as
CIGESM2 in Chapter 7).
We use the phrase
most cases, because as already noted, this is not always the case.
For Windows 2000, the order of the Local Area Connection logical
names assigned to
physical NICs is based on the
order in which the drivers for each NIC are installed. The
A
Comments to this Manuals