• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 12591
  • Last Modified:

Nic Teaming - Cisco Port config help on switch

Ok I want to setup Nic Teaming on a Server and I need to know what the commands are for the port configuration on a Cisco Switch (2950 or 2960).

This could be a team setup for Intel or Broadcom  Nics.  I'm not completely familiar with the different types of teams and which is better looking for recommendations.  I believe what I wish to use though is the standard LACP IEEE 802.3ad link aggregation team.  If for some reason you would recommend against this type of team please explain why.  If there is a better method I would like to know what it is and how to set it up.

Again I'm trying to create a Team that basically takes the multi nics to increase bandwidth to the server while only using one IP.  It is also my understanding that if one of the nic connections goes down it will continue to function on the other Nic or Nics in the team.
0
lawson2305
Asked:
lawson2305
  • 7
  • 4
  • 2
  • +2
3 Solutions
 
lawson2305Author Commented:
Ok first document gives information on doing this between two switches.  I would like to have detailed commands laid out for doing doing this.  Say FastEthernet Ports 0/2,0/3,0/4 on a Cisco 2960 switch.

Second document is for Etherchannel setup which would be if I was setting up any teaming method but LACP IEEE 802.3ad.  Correct?

Third is just more of the same on link two.

Please be more specific.
0
Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

 
CaoilteCommented:
for 802.3ad you want to set up a port-channel

in config more issue int port-channel XXX ( where XXX is the next number or 1 if it's the first )

configure up the PO as if it was a normal interface "switchport mode trunk " etc.

on the ports to be a member of the channel issue "channel-group XXX" ( do a ? in the ports to be sure on the format of this one as it can be a little different on some switches )
0
 
Aaron StreetInfrastructure ManagerCommented:
802.3ad is what you want. (all ports have to be in the same switch/stack of cisco switchs)

you can either use

#int g3/0/1 (example of a port there ;) )
#channel-group 1 mode desirable

(this will join an etherchannel/ aggration if the device pluged in to the port is able to auto configure. (ie you have enababled it on the server Nics to be auto as well)

or

#channel-group 1 mode on (this will create an ether channel)

and like caloilte says. once you have the port channel you can configre it as you would a normal interface on a switch, by issing a simple command of

#int port-channel 1
like you would issue a # int g3/0/1

But if both your switch and your server support 802.3ad then this is the simplest way to go. simple make sure they are both set to auto/desirable. and as you attact the cables it will take care of the aggration iits self..
0
 
Aaron StreetInfrastructure ManagerCommented:
oh check what protical your NIc's support LACP or PAgP. the command is slightly different for each. many servers are LACP. So check your NIC's drivers fo what they say. and set the switch up using the command below

switch(config-if)#channel-group 1 mode ?
 
active     Enable LACP unconditionally
  auto       Enable PAgP only if a PAgP device is detected
  desirable  Enable PAgP unconditionally
  on         Enable Etherchannel only
  passive    Enable LACP only if a LACP device is detected
0
 
lawson2305Author Commented:
Ok this was my main question was how to enable LACP and I thought it was with Active but that just didn't seem complete.

Say this is the second Port Channel.

So basically to make sure I understand this correctly I would do this for a LACP connection with my example:

2960 switch:
switch: enable
switch#: config t
switch(config)#: int port-channel 2
switch(config-if)#: switchport mode trunk
switch(config-if)#: exit
switch(config)#: int fastethernet 0/2
switch(config-if)#: channel-group 2 mode active
switch(config-if)#: exit
switch(config)#: int fastethernet 0/3
switch(config-if)#: channel-group 2 mode active
switch(config-if)#: exit
switch(config)#: int fastethernet 0/4
switch(config-if)#: channel-group 2 mode active
switch(config-if)#: ctrl-z
switch#: wr

What about???? -
switch(config)#: int fastethernet 0/2
switch(config-if)#: channel-protocol lacp

Does this also need to be done on every FE interface?

Also with LACP do you recommend that I remove Auto negotiate?

Last Question:
2950 I could not get ACTIVE:
switch(config)#: int fastethernet 0/2
switch(config-if)#: channel-group 2 mode ?
  auto       Enable PAgP only if a PAgP device is detected
  desirable  Enable PAgP unconditionally
  on         Enable Etherchannel only

Is this the OS version or 2950 period? or does it require some other config on a 2950.
0
 
CaoilteCommented:
For my 802.3ad I did not need to set lacp at all... the config was more like...
switch: enable
switch#: config t
switch(config)#: int port-channel 2
switch(config-if)#: switchport trunk encapsulation dot1q
switch(config-if)#: switchport mode trunk
switch(config-if)#: exit
switch(config)#: int fastethernet 0/2
switch(config-if)#: channel-group 2 mode auto
switch(config-if)#: exit
switch(config)#: int fastethernet 0/3
switch(config-if)#: channel-group 2 mode auto
switch(config-if)#: exit
switch(config)#: int fastethernet 0/4
switch(config-if)#: channel-group 2 mode auto
switch(config-if)#: ctrl-z
switch#: wr


Any particular reason you want to set LACP specifically on ?
0
 
lawson2305Author Commented:
Because I want to use LACP.  If you notice you are not using LACP you are using Cisco proprietary PAgP.

One thing I have gathered is that it looks like I need to set either the Switch or Server Active and the other passive to avoid possible loops.

So if I use my above example then I would be setting the ports active at the switch and would want to set the ports passive at the server.  Is it recommended in anyway to configure the server Nics as active instead of the switch or does it not matter?
0
 
lawson2305Author Commented:
switch(config)#: int fastethernet 0/2
switch(config-if)#: channel-protocol lacp

I think this would only be used if you are connecting like say two cisco devices using lacp.  You would define the above on one of the switches but in my example this is being defined on the server so I don't think this is needed on the switch.
0
 
lawson2305Author Commented:
So am I incorrect in the idea that I want to use LACP and that I should set this not to Active or Passive but to Auto?

Please I would like to close this question and get this finished.
0
 
Aaron StreetInfrastructure ManagerCommented:
You need to check what the server NIC and the Switch can support.

with out knowing this it is impossible to answer the question .

There is not much difference between LACP and PAgP.

Personlay I would set the Server to be the active party,and the the switch PAssive.

This way you can set all ports on a switch to passive. then you dont have to worry where you plug in the server, and the switch will take care of the links
0
 
lawson2305Author Commented:
DevilWAH thank you for this additional information after I posted my last link I did start to think it would probably be best to set the switch Passive.  Not sure if I can control at server if it is active or passive but I know I can on the Switch.
0
 
Aaron StreetInfrastructure ManagerCommented:
on the server is basical turn the nic teamin on or off. more than set it to passive or active.
0
 
lawson2305Author Commented:
Question,
Should you disable
 spanning-tree portfast trunk
At the interface that you put the switchport on or no?
0
 
65tdCommented:
Of the documents I have reviewed, disable spanning-tree portfast trunk.
See the FAQ's second Q for more information.
http://www.vmware.com/pdf/esx3_vlan_wp.pdf
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.

Join & Write a Comment

Featured Post

Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

  • 7
  • 4
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now