Cisco 3550 Switches and NIC Teaming on Servers

Tonight our server guys are installing a 4 port NIC card into one of their servers for NIC Teaming.  This network consists of three Cisco 3550-48 switches.  All three switches are all in the same VLAN.  Are there any special configurations needed on the switches that I would need to make to ensure their NIC teaming project is a success tonight?  I was reading alot of articles and they all said something different.  One article said their was a special configuration, the next article said as long as all the switches are in the same VLAN it will work fine.  Any assistance wouild be greatly appreciated.  Thanks.
LVL 4
denver218Asked:
Who is Participating?
 
evan_weinerCommented:
It'll be something similar to this...

interface Port-channel1
 description bundle
 switchport access vlan 20
 switchport mode access
 speed 1000
 duplex full
 spanning-tree portfast
!
...
!
interface GigabitEthernet1/0/1
 description NIC1
 switchport access vlan 20
 switchport mode access
 speed 1000
 duplex full
 channel-group 1 mode passive
!
interface GigabitEthernet2/0/1
 description NIC2
 switchport access vlan 20
 switchport mode access
 speed 1000
 duplex full
 channel-group 1 mode passive
!

Depending on the requirements of the NIC, you may need to play with the channel-group mode under the physical interface.  Just do channel-group # mode ? to see the options although I think the Broadcom's will do LACP (the server connected to this example is a Broadcom).

You can also check the status -

VA-SPTC-Core-C3750#sh etherchanne
                Channel-group listing:
                ----------------------

Group: 1
----------
Group state = L2
Ports: 2   Maxports = 16
Port-channels: 1 Max Port-channels = 16
Protocol:   LACP
Minimum Links: 0

-Evan
0
 
evan_weinerCommented:
Depending on the NIC, you will most likely need to configure a port channel on the 3550 (type would definitely depend on what NIC) and the NC should have software with it for the teaming part.  This article should help you get going but you'll need to tweak it a bit depending on the NIC.

http://www.cisco.com/en/US/tech/tk389/tk213/technologies_configuration_example09186a0080094647.shtml
0
 
denver218Author Commented:
The type of NIC is an Intel, and they do have software to configure it.  I will take a look at the link.  Thanks.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

 
denver218Author Commented:
Let's say I'm going to use ports fa0/1 - 4 on my cisco switch.  Can you show me an example of how these ports need to be configured.  Thanks.
0
 
evan_weinerCommented:
etherchannel or LACP?
0
 
denver218Author Commented:
I'm not sure.  Does this depend on the NIC card that they using?
0
 
evan_weinerCommented:
Yes.  Do you have the model of the NIC?
0
 
denver218Author Commented:
The NIC they now decided to use is a 4 port Broadcom BCM5709C NetXtreme II GigE.  Thanks.
0
 
evan_weinerCommented:
If it's all in VLAN1, you can omit the "switchport access vlan 20" part as the interfaces will default to VLAN1 or put in the appropriate VLAN number.
0
 
denver218Author Commented:
Okay, let me give it a try and see what happens.  My speed will be 100 not 1000 though cause this isn't a gigabit switch.  Thanks.  I'll let you know the outcome.
0
 
denver218Author Commented:
Things still are not working right.  I have 2 servers each has a 4 port NIC.  I configured the switch as above, but if I transfer a file between the two servers is only going at 10Mb.  I'm not sure what I'm doing wrong.  Any ideas?
0
 
evan_weinerCommented:
Can you post your switch config and screenshots from BACS?
0
 
denver218Author Commented:
Below are my switch configurations:  Thanks.

version 12.1
no service pad
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname LAN_SW1
!
!
ip subnet-zero
ip routing
!
!
spanning-tree mode pvst
spanning-tree extend system-id
!
!
!
!
interface Port-channel1
 switchport mode access
 speed 100
 duplex full
 spanning-tree portfast
!
interface Port-channel2
 switchport mode access
 speed 100
 duplex full
 spanning-tree portfast
!
interface FastEthernet0/1
 switchport mode access
 speed 100
 duplex full
 channel-group 1 mode passive
!
interface FastEthernet0/2
 switchport mode access
 speed 100
 duplex full
 channel-group 1 mode passive
!
interface FastEthernet0/3
 switchport mode access
 speed 100
 duplex full
 channel-group 1 mode passive
!
interface FastEthernet0/4
 switchport mode access
 speed 100
 duplex full
 channel-group 1 mode passive
!
interface FastEthernet0/5
 switchport mode access
 speed 100
 duplex full
 channel-group 2 mode passive
!
interface FastEthernet0/6
 switchport mode access
 speed 100
 duplex full
 channel-group 2 mode passive
!
interface FastEthernet0/7
 switchport mode access
 speed 100
 duplex full
 channel-group 2 mode passive
!
interface FastEthernet0/8
 switchport mode access
 speed 100
 duplex full
 channel-group 2 mode passive
!
interface FastEthernet0/9
 switchport mode dynamic desirable
!
interface FastEthernet0/10
 switchport mode dynamic desirable
!
interface FastEthernet0/11
 switchport mode dynamic desirable
!
interface FastEthernet0/12
 switchport mode dynamic desirable
!
interface FastEthernet0/13
 switchport mode dynamic desirable
!
interface FastEthernet0/14
 switchport mode dynamic desirable
!
interface FastEthernet0/15
 switchport mode dynamic desirable
!
interface FastEthernet0/16
 switchport mode dynamic desirable
!
interface FastEthernet0/17
 switchport mode dynamic desirable
!
interface FastEthernet0/18
 switchport mode dynamic desirable
!
interface FastEthernet0/19
 switchport mode dynamic desirable
!
interface FastEthernet0/20
 switchport mode dynamic desirable
!
interface FastEthernet0/21
 switchport mode dynamic desirable
!
interface FastEthernet0/22
 switchport mode dynamic desirable
!
interface FastEthernet0/23
 switchport mode dynamic desirable
!
interface FastEthernet0/24
 switchport mode dynamic desirable
!
interface GigabitEthernet0/1
 switchport mode dynamic desirable
!
interface GigabitEthernet0/2
 switchport mode dynamic desirable
!
interface Vlan1
 ip address 172.19.4.1 255.255.255.0
!
ip classless
ip http server
!
!
line con 0
line vty 0 4
 login
line vty 5 15
 login
!
!
end
0
 
evan_weinerCommented:
How about a sh log, sh etherchannel sum, and screenshot from the Broadcom config suite?  Did you configure the team in there?
0
 
denver218Author Commented:
Ok, below is the requested information.  Port channel 2 is the one that I currently have configured.  It consists of ports fa0/5 thru fa0/8.  Port Channel 1 is currently not being used at the moment because the server it down for maintenance.

Switch#show etherchannel
                Channel-group listing:
                ----------------------

Group: 1
----------
Group state = L2
Ports: 4   Maxports = 16
Port-channels: 1 Max Port-channels = 16
Protocol:   LACP

Group: 2
----------
Group state = L2
Ports: 4   Maxports = 16
Port-channels: 1 Max Port-channels = 16
Protocol:   LACP


Switch#show log
Syslog logging: enabled (0 messages dropped, 0 messages rate-limited, 0 flushes,
 0 overruns)
    Console logging: level debugging, 168 messages logged
    Monitor logging: level debugging, 0 messages logged
    Buffer logging: level debugging, 168 messages logged
    Exception Logging: size (4096 bytes)
    File logging: disabled
    Trap logging: level informational, 172 message lines logged

Log Buffer (4096 bytes):
5:29:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, change
d state to up
05:29:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, chang
ed state to up
05:29:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, chang
ed state to up
05:29:39: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, chang
ed state to up
05:32:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, chang
ed state to down
05:32:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, chang
ed state to down
05:32:50: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, chang
ed state to down
05:32:51: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, chang
ed state to down
05:32:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, chang
ed state to up
05:32:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, chang
ed state to up
05:32:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, chang
ed state to up
05:32:58: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, chang
ed state to up
05:32:59: %LINK-3-UPDOWN: Interface Port-channel2, changed state to up
05:33:00: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel2, changed
 state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed
state to down
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed
state to down
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed
state to down
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed
state to down
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface Port-channel2, changed st
ate to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/6, changed state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/7, changed state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/8, changed state to down
2d20h: %LINK-3-UPDOWN: Interface Port-channel2, changed state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/5, changed state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/5, changed state to up
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/6, changed state to up
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/7, changed state to up
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/8, changed state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed
state to down
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed
state to down
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed
state to down
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed
state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/5, changed state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/6, changed state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/7, changed state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/8, changed state to down
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/5, changed state to up
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/6, changed state to up
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/7, changed state to up
2d20h: %LINK-3-UPDOWN: Interface FastEthernet0/8, changed state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/6, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed
state to up
Switch#2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed
state to up
Switch#2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/5, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/8, changed
state to up
2d20h: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0/7, changed
state to up
Switch#

Attached are the Screen Shots.  As you can see if I go to the properties of the NIC Team it shows a speed of 400 Mbps so it looks like its working.
 screen-shots.docx
0
 
evan_weinerCommented:
So let's back up a bit.  If you do a sh ether sum, does it list it as up? (something like SU after the interface name)?  Where are you trying to transfer files to - is it on the same switch, router between, etc?  Could there be some other factors limiting performance?  Is the other client attached to wireless?
0
 
denver218Author Commented:
Thanks
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.