Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Weird teaming/port bonding question

Hi.I have a weird question regarding teaming.

One of my Windows administrators has asked me to configure the switch a new server will connect to for teaming(2 NIC ports on the server should work together).

The problem is when I studied the existing configuration for an existing server that is working in teaming with his NICs I found that 2 ports on a switch the server is connected to aren't in Etherchannel as I have read it must be done for teaming to work.

In fact one NIC is connected to a 1 Gigabit port and the other to a 100 Mbit port and both ports are in the same VLAN(VLAN all our servers are in).

Is it possible that on the server side NICs are working in a team but on the switch side they are just in the same VLAN?

By the way switch is Cisco Catalyst 6500.

3 ACCEPTED SOLUTIONS

Accepted Solutions
New Member

Re: Weird teaming/port bonding question

NIC Teaming implementations vary, but in my experience, NIC teaming only requires the NICs to be on the same VLAN, as heartbeats need to be sent between the NICs.

hth,

Ross

Hall of Fame Super Blue

Re: Weird teaming/port bonding question

Hi

As mentioned by previous poster there are different ways to run NIC teaming. We run in fault tolerant mode within our company.

The server NIC's are definitely not setup as etherchannel connections. Maybe that is necessary for some configurations altho i haven't come across them. You just connect your two NIC's into the switches and as said before make sure they are on the same vlan.

Obviously if you are teaming for fault tolerance you generally connect the two server NICs to two separate switches.

HTH

Jon

New Member

Re: Weird teaming/port bonding question

nothing specific to teaming is required - you will need to make sure that no access-lists are in the way, that Windows firewall on the server allows pings, etc.

regards,

Ross

6 REPLIES
New Member

Re: Weird teaming/port bonding question

NIC Teaming implementations vary, but in my experience, NIC teaming only requires the NICs to be on the same VLAN, as heartbeats need to be sent between the NICs.

hth,

Ross

New Member

Re: Weird teaming/port bonding question

Thanks.I'll place both server NICs in the same VLAN(one NIC on Gigabit port and the other on a 100 Mbit port) and see if it will work.

Hall of Fame Super Blue

Re: Weird teaming/port bonding question

Hi

As mentioned by previous poster there are different ways to run NIC teaming. We run in fault tolerant mode within our company.

The server NIC's are definitely not setup as etherchannel connections. Maybe that is necessary for some configurations altho i haven't come across them. You just connect your two NIC's into the switches and as said before make sure they are on the same vlan.

Obviously if you are teaming for fault tolerance you generally connect the two server NICs to two separate switches.

HTH

Jon

New Member

Re: Weird teaming/port bonding question

Put the 2 NICs on server on the switch in today both on different modules of Catalyst 6500(same VLAN) and on Gigabit ports and it seems to be working OK from the server side(server connected to the domain all right).

But just one question:do I have to configure something on the switch to be able to ping the server as I can't do that at the moment?

New Member

Re: Weird teaming/port bonding question

nothing specific to teaming is required - you will need to make sure that no access-lists are in the way, that Windows firewall on the server allows pings, etc.

regards,

Ross

New Member

Re: Weird teaming/port bonding question

Everything works fine now.Server firewall was the problem so when the Windows administrator took care of it pings went through with no problem.

Thanks for all your help guys.

287
Views
0
Helpful
6
Replies