HP Servers NIC Teaming with Cisco Nexus 2000/5000

I have number of HP switches that will be connected to Cisco Nexus 2000/5000 switches.
In HP Servers, there are multiple options for NIC teaming. I like to connect each port in a NIC card to two different Nexus 2000 switches extension to Nexus 5000 switches. Nexus 5000 switches will be configured as VPC for clustering.
Wanted to know what whould be the best NIC teaming option from the followng HP Server's NIC Teaming options:
Automatic
802.3ad Dynamic with Fault Tolerence
Switch-assisted load balancing with Fault Tolerance (SLB)
Transmit load balancing with Fault Tolerance (TLB)
Transmit Load Balancing with Fault tolerance and preference order
Network Fault Tolerance Only (NFT)
Network Fault Tolerance with Preference Order

Nexus switches only support LACP (802.3ad) or ON mode. So, to match your server config with your switch, the first option is the best one to use. I think, SLB is a Microsoft propriety protocol.
HTH

Similar Messages

Ask the Expert: Cisco Nexus 2000, 5000, and 6000 Series Switches

with Cisco Expert Vinayak Sudame
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions how to configure and troubleshoot the Cisco Nexus 2000, 5000 and 6000 Series Switches with Cisco subject matter expert Vinayak Sudame. You can ask any question on configuration, troubleshooting, features, design and Fiber Channel over Ethernet (FCoE).
Vinayak Sudame is a Technical Lead in Data Center Switching Support Team within Cisco's Technical Services in RTP, North Carolina. His current responsibilities include but are not limited to Troubleshooting Technical support problems and Escalations in the areas of Nexus 5000, Nexus 2000, FCoE. Vinayak is also involved in developing technical content for Cisco Internal as well as external. eg, Nexus 5000 Troubleshooting Guide (CCO), Nexus 5000 portal (partners), etc. This involves cross team collaboration and working with multiple different teams within Cisco. Vinayak has also contributed to training account teams and partners in CAE (Customer Assurance Engineering) bootcamp dealing with Nexus 5000 technologies. In the past, Vinayak's responsibilities included supporting MDS platform (Fiber Channel Technologies) and work with EMC support on Escalated MDS cases. Vinayak was the Subject Matter Expert for Santap Technologies before moving to Nexus 5000 support. Vinayak holds a Masters in Electrical Engineering with Specialization in Networking from Wichita State University, Kansas. He also holds Cisco Certification CCIE (#20672) in Routing and Switching.
Remember to use the rating system to let Vinayak know if you have received an adequate response.
Vinayak might not be able to answer each question due to the volume expected during this event. Remember that you can continue the conversation on the Data Center sub-community, Other Data Center Topics discussion forum shortly after the event.
This event last through Friday July 12, 2013. Visit the community often to view responses to youe questions of other community members.

Hi Vinayak,
Output of "show cfs internal ethernet-peer database"
Switch 1
ETH Fabric
Switch WWN logical-if_index
20:00:54:7f:ee:b7:c2:80 [Local]
20:00:54:7f:ee:b6:3f:80 16000005
Total number of entries = 2
Switch 2
ETH Fabric
Switch WWN logical-if_index
20:00:54:7f:ee:b6:3f:80 [Local]
20:00:54:7f:ee:b7:c2:80 16000005
Total number of entries = 2
Output of "show system internal csm info trace"
Switch 1 in which "show cfs peers" show proper output
Mon Jul 1 05:46:19.145339 (CSM_T) csm_sp_buf_cmd_tbl_expand_range(8604): No range command in buf_cmd_tbl.
Mon Jul 1 05:46:19.145280 (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
Mon Jul 1 05:46:19.145188 (CSM_T) csm_sp_handle_local_verify_commit(4291):
Mon Jul 1 05:46:19.145131 csm_continue_verify_ac[597]: peer is not reachable over CFS so continuing with local verify/commit
Mon Jul 1 05:46:19.145071 csm_tl_lock(766): Peer information not found for IP address: '172.16.1.54'
Mon Jul 1 05:46:19.145011 csm_tl_lock(737):
Mon Jul 1 05:46:19.144955 (CSM_EV) csm_sp_build_tl_lock_req_n_send(941): sending lock-request for CONF_SYNC_TL_SESSION_TYPE_VERIFY subtype 0 to Peer ip = (172.16.1.54)
Mon Jul 1 05:46:19.143819 (CSM_T) csm_copy_image_and_internal_versions(788): sw_img_ver: 5.2(1)N1(2a), int_rev: 1
Mon Jul 1 05:46:19.143761 (CSM_T) csm_sp_get_peer_sync_rev(329): found the peer with address=172.16.1.54 and sync_rev=78
Mon Jul 1 05:46:19.143699 (CSM_T) csm_sp_get_peer_sync_rev(315):
Mon Jul 1 05:46:19.143641 (CSM_EV) csm_sp_build_tl_lock_req_n_send(838): Entered fn
Mon Jul 1 05:46:19.143582 (CSM_T) csm_set_sync_status(6257): Peer RT status PSSed
Switch 2 in which "show cfs peers" does not show proper output
Mon Jul 1 06:13:11.885354 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 77 seq 482
Mon Jul 1 06:13:11.884992 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 357 seq 369
Mon Jul 1 06:13:11.884932 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 357 seq 368
Mon Jul 1 06:13:11.884872 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 357 seq 367
Mon Jul 1 06:13:11.884811 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 357 seq 366
Mon Jul 1 06:13:11.884750 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd channel-group 51 mode active, cmd pseq 352 seq 365
Mon Jul 1 06:13:11.884690 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport trunk allowed vlan 2, 11, cmd pseq 352 seq 364
Mon Jul 1 06:13:11.884630 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd switchport mode trunk, cmd pseq 352 seq 363
Mon Jul 1 06:13:11.884568 (CSM_ERR) csm_pss_cmd_tree_walk_cb(2057): Parent command not found for cmd description process_vpc, cmd pseq 352 seq 362
Mon Jul 1 06:13:11.884207 (CSM_EV) csm_sp_acfg_gen_handler(3011): Preparing config into /tmp/csm_sp_acfg_1733916569.txt
Mon Jul 1 06:13:11.878695 csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
Mon Jul 1 06:13:11.878638 (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
Mon Jul 1 06:12:29.527840 (CSM_T) csm_pss_del_seq_tbl(1989): Freeing seq tbl data
Mon Jul 1 06:12:29.513255 (CSM_T) csm_sp_acfg_gen_handler(3106): Done acfg file write
Mon Jul 1 06:12:29.513179 (CSM_EV) csm_sp_acfg_gen_handler(3011): Preparing config into /tmp/csm_sp_acfg_1733911262.txt
Mon Jul 1 06:12:29.508859 csm_get_locked_ssn_ctxt[539]: Lock not yet taken.
Mon Jul 1 06:12:29.508803 (CSM_EV) csm_sp_acfg_gen_handler(2937): Recieved sp acfg merge request for type: running cfg
Mon Jul 1 05:53:17.651236 Collecting peer info
Mon Jul 1 05:53:17.651181 Failed to get the argumentvalue for 'ip-address'
Mon Jul 1 05:40:59.262736 DB Unlocked Successfully
Mon Jul 1 05:40:59.262654 Unlocking DB, Lock Owner Details:Client:1 ID:1
Mon Jul 1 05:40:59.262570 (CSM_T) csm_sp_del_buf_cmd(1713): Deleting comand with Id = 1
Mon Jul 1 05:40:59.262513 DB Lock Successful by Client:1 ID:1
Mon Jul 1 05:40:59.262435 Recieved lock request by Client:1 ID:1
Mon Jul 1 05:40:41.741224 ssnmgr_ssn_handle_create_get: Session FSM already present, ID:1
Mon Jul 1 05:40:41.741167 ssnmgr_handle_mgmt_request: Create/Get request received for session[process_n5kprof]
show cfs lock gives no output.
Just to further clarify, we have 4 5548UP switches in the same management vlan. 2 switches are in one location lets say location A and they are CFS peers and are working fine.
These two switches which are having problem are in location B. All the switches are in the same vlan. Essentially the all CFS multicast messages will be seen by all 5548 switches as they are in the same vlan. I am assuming that this might not create any problems as we specify the peers in the respective configurations. Or do we have to change the CFSoIPv4 multicast addresses in location B or may be configure a different region.
Regards.

Cisco Nexus 2000

My question may seem silly, but I have gotten conflicting responses thus far.
My question is, can a Nexus 2000 series switch be implemented by itself, or does it have to have a "parent" 5000 or 7000 series?

The Nexus 2000 is not a switch.
It's a fabric extender, you can visualize it as a NIC card extension from your servers to the switch, ie: Nexus 5000 or Nexus 7000 are needed for the 2000 to function. Nexus 7000 will work with specific line card and only the 2200, whereas the Nexus 5000 will work with any Nexus 2000 series (2148,2232,2248).
Docs:
www.cisco.com/go/nexus2000
http://www.cisco.com/en/US/products/ps10110/prod_literature.html

FCoE with Cisco Nexus 5548 switches and VMware ESXi 4.1

Can someone share with me what needs to be setup on the Cisco Nexus side to work with VMware in the following scenario?
Two servers with two cards dual port FCoE cards with two ports connected to two Nexus 5548 switches that are clusterd together. We want to team the ports together on the VMware side using IP Hash so what should be done on the cisco side for this to work?
Thanks...

Andres,
The Cisco Road Map for the 5010 and 5020 doesn't include extending the current total (12) FEX capabities. The 5548 and 5596 will support more (16) per 55xxk, and with the 7K will support upto 32 FEX's.
Documentation has been spotty on this subject, because the term 5k indicates that all 5000 series switches will support extended FEX's which is not the case only the 55xx will support more than 12 FEX. Maybe in the future the terminology for the 5k series should be term 5000 series and 5500 series Nexus, there are several differences and advancements between the two series.

Broadcom LiveLink : Receiving MAC flaps with Cisco Nexus 7000

We are migrating from using two Nortel 8600's running VRRP at the distribution to Cisco Nexus 7K's using HSRP. So we have a server connected to two 3750G switches which then connect to the Nexi (previously the 8600's). As soon as we connected the 3750's to the Nexus and moved the gateway to Nexus, LiveLink forces all the servers to alternate traffic between NIC1 and NIC2.
Since LiveLink is a teaming application, it uses virtual mac for nic1 and nic2, but the virtual mac associated with the IP address moves to the active link.
LiveLink is used to check the availability of the gateway by polling the gateway out of each interface using an ARP request.
The problem does not exhibit itself in our Cisco VSS environment, and with Nortel's VRRP. I tried running VRRP on the Nexus but no joy.
Anyone know of a bug that could cause this issue?

Unfortunately we have LiveLink enabled on most of our Windows servers in our data centers. One of my colleagues sent me this bug issue. I'm not sure if this is the cause, but it's worth trying. We will update the NxOs (currently on 5.1.1) next week and see if that fixes the problem.
•CSCtl85080
Symptom: Incomplete Address Resolution Protocol (ARP) entries are observed on a Cisco Nexus 7000 Series switch, along with partial packet loss and a memory leak.
Conditions: This symptom might be seen when ARP packets have a nonstandard size (that is, greater than 64 bytes).
Workaround: This issue is resolved in 5.1.3.

NIC Teaming with CSS

Hi Gilles,
Is NIC teaming supported with CSS? How can I load balance two servers with each server having two NIC and using NIC teaming.
Thanks
Sushil

As far as I know there is no LAG on the css. I think the best solution is to use a switch in between the servers and the css.

HP NIC Team with MDT

I am trying to deploy servers with MDT and as a requirement would need to team NIC, We use HP servers and they provide a utility
CQNICCMD to get that done.
Have referred the below link for the command/switches.
http://h20564.www2.hp.com/hpsc/doc/public/display?docId=c04024934
I am not sure where in the task sequence should I get the NIC team done cause they keep failing where every I put it.Any documentation on how to get this done will be of great help.

I would place the command during the State Restore phase, somewhere during custom steps. Assuming that the Teaming can be done in the regular OS.
The question is: What are the failures?
Please note that if you are configuring the only NIC's on the machine *AND* running the scripts from *over* the network, your script could suddenly find it self running without access to it's own source. I would devise a method to copy the scripts/install
program/drivers locally, kick off the script locally, and then wait for the network to be available.
Keith Garner - Principal Consultant [owner] -
http://DeploymentLive.com

Highest supported Brocade DCX firmware version to be interoperable with Cisco Nexus 5020

A Cisco Nexus 5020 (FCoE) switch is connected to Brocade DCX-B switch.
5020 is at latest firmware level of 5.0.2.N2.1
Brocade is at firmware level of 6.2.1b
If we need to upgrade brocade firmware, what is the maximum revision we can go to? Is there some documentation available for interoperability between the code levels of the two hardwares?

Hi Anwarul,
Please refer to "Table 7-10 Nexus InterOp Matrix" near the end of this link:
http://www.cisco.com/en/US/docs/switches/datacenter/mds9000/interoperability/matrix/Matrix7.html
Regards,
Ken

Teaming with Cisco 3120x

Hi there,
I hope somebody can help us. We recently bought some HP c7000 Blade Enclosures with 2 Cisco 3120x switches inside. On the blades we run Windows Server 2003 and 2008 and use teaming.
When a switch needs to be replaced after an hardware failure the new switch will be unconfigured placed back into the c7000 enclosure. The ports of the 3120x are not shut so the Windows servers will start transmit traffic through that ports. The problem is that the switches are not yet properly configured.
How can we solve this problem? Or do we need a test enclosure where we can shut the ports before putting back in the porduction enclosure?
How do you handle hardware failure's?
Thanks for the help!

Hi,
I've a doubt and a suggestion, but I'm not an expert in DC, so bear with me.
First, teaming and etherchannel are different names for the same, ethernet inverse multiplexing,
standardized in 802.3ad (LACP)
What I see as a problem with defining it in only one side is that your MACs will be moving
from one switch to the other, but nothing serious. You will not have link balancing or HA controlled from the switch side,
but as a response to whatever the host sends. So what is the problem with your design that prevents stacking and
multi chassis ethernet bonding is something I'd like to know.
Now, with your reinsertion trouble, I guess admin down all the ports on the host side before reinsertion
is one option.
As a more risky option, you can actually insert the switch and prevent it from booting by breaking into rommon.
The switch supports xmodem, so you can upload the configuration while the switch is non functional.
Good luck.

SR-IOV Uplink Port with NIC Teaming

Hello,
I'm trying to setup my uplink port profile and logical switch with NIC Teaming and SR-IOV support. In Hyper-V this was easy, just had to create the NIC Team (which I configured as Dynamic & LACP) then check the box on the virtual switch.
I'm VMM it does not seem to like to enable NIC Teams with SR-IOV:
Can anyone advise? I'm not using any virtual ports. I just want all my VMs to connect to the physical switch though the LACP NIC Team, something which I thought would be simple.
I have a plan B - don't use Microsoft's NIC Teaming and instead use the Intel technology to present all the adapters as one to the host. I'd rather no do this.
Thanks
MrGoodBytes

Hi Sir,
"SR-IOV does have certain limitations. If you configure port access control lists (ACLs), extensions or policies in the virtual switch, SR-IOV is disabled because its traffic totally bypasses the switch.
You can’t team two SR-IOV network cards in the host. You can, however, take two physical SR-IOV NICs in the host, create separate virtual switches and team two virtual network cards within a VM. "
There is really a limitation when using NIC teaming :
http://technet.microsoft.com/en-us/magazine/dn235778.aspx
Best Regards,
Elton Ji
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected] .

DCNM compatibilty with nexus 2000 and 5000 series

Hi,
I would to know if the DNCM can manage a Data Center composed with Nexus 2000 & 5000 series only!
Kind regards

Hi reswaran,
The features are:
- Automatic network discovering and real- time topology.
- Network anomaliy detection (threshold, alarms, errors, ...)
- Use email or aletrs to notify notify operations staff of critical outages thant may be service-imapcting
- Centralized administration interface, with acces via web
- Securised acces and rights managment
- Stock of data in an exportable database
- Quick, simple qnd transparent deployment
- Monitoring WAN bandwith usage
- Configurable report generation
- Generation of the performance reports
- Provide network map
- Support several network unit
- Intergrated Syslog server
- Polling andt monitoring SNMP trap alarms
- Secure config distribution
- Support 200 devices
What kind of NMS can you recommend?
thanks a lot

Macvtap over Cisco Nexus ...

Hi everybody!
First all my apologizes for my english language!
I have a standard server running linux (centos 6.5) with kvm to install and configure virtual machines. I tried to use macvtap driver to setup the virutal network interfaces. I not use ucs Cisco servers or Nexus 1000v switches!
The physical ethernet is connected to Cisco Nexus 2000 (with a Cisco Nexus 5548up). To default a standard switch not working with the macvtap configuration because the swith to be support "reflective relay" or "hair pinning" propierties for to this works.
Is possible configure the Cisco Nexus 5548up/2000 to this works? Capabilities how to Adapter-FEX, veheternet, VM-FEX o similars can help me?
Know you some docs over this?
Thank you all.

Hi Tony,
You do not have to worry about PFC. Priority-Flow-Control is something which is related to FCOE or DCBX protocol. With iSCSI as this is a TCP traffic, you have to make sure that you have a proper QOS for the IP Subnet or VLAN that has your iSCSI hosts transmitting the data. As iSCSI rides over TCP this is the major issue that I have seen related to the valid QOS config for the traffic. There is not best practice for it but you have make sure that you added it to a class other than BE or Scavanger class.
Hope this helps.
Cheers,
-amit singh

Ask the Expert: Configuration, Design, and Troubleshooting of Cisco Nexus 1000

With Louis Watta
Welcome to the Cisco Support Community Ask the Expert conversation. This is an opportunity to learn and ask questions about design, configuration, and troubleshooting of Cisco Nexus 1000V Series Switches operating inside VMware ESXi and Hyper-V with Cisco expert Louis Watta. Cisco Nexus 1000V Series Switches deliver highly secure, multitenant services by adding virtualization intelligence to the data center network. With Cisco Nexus 1000V Series Switches, you can have a consistent networking feature set and provisioning process all the way from the virtual machine access layer to the core of the data center network infrastructure.
This is a continuation of the live Webcast.
Louis Watta is a technical leader in the services organization for Cisco. Watta's primary background is in data center technologies: servers (UNIX, Windows, Linux), switches (MDS, Brocade), storage arrays (EMC, NetApp, HP), network switches (Cisco Catalyst and Cisco Nexus), and enterprise service hypervisors (VMware ESX, Hyper-V, KVM, XEN). As a Technical Leader in Technical Services, Louis currently supports beta and early field trials (EFTs) on new Cisco software and hardware. He has more than 15 years of experience in a wide variety of data center applications and is interested in data center technologies oriented toward data center virtualization and orchestration. Prior to Cisco, Louis was a system administrator for GTE Government Systems. He has a bachelor of science degree in computer science from North Carolina State University. .
Remember to use the rating system to let Louis know if you have received an adequate response.
Louis might not be able to answer each question because of the volume expected during this event. Remember that you can continue the conversation on the Data Center community Unified Computing shortly after the event.
This event lasts through Friday, JUne 14, 2013. Visit this forum often to view responses to your questions and the questions of other Cisco Support Community members.
Webcast related links:
Slides
FAQ
Webcast Video Recording

Right now there is only a few features that are not supported on N1Kv on Hyper-V
They are VXLAN and QOS Fair Weighted Queuing. We are currently demoing VXLAN functionality at Microsoft TechEd Conference this week in New Orleans. So VXLAN support should be coming soon. I can't give you a specific timeline.
For Fair Weighted Queuing I'm not sure. In the VMware world we take advantage of NETIOC infrastructure. In the MS world they do not have a NETIOC infrastructure that we can use to create a similar feature.
Code base parity (as in VMware and Hyper-V VSMs running NXOS 5.x) will happen with the next major N1KV release for ESX.
Let me know if that doesn't answer your question.
thanks
louis

Relationship between coherence and NIC teaming

Hi,
We are using Tangosol coherence for clustering purpose in our product Webmethods Integration server.
When our server starts up it tries to jojn tne cluster.
Our scenario is this :-
We have 2 servers running on 2 separate boxes A&B.
They are on same network segment.
Multicast test is working properly .
The issue is only one of the nodes(which is started first) in becoming the part of the cluster and other one remain disabled.
We found out that the NIC teaming was disabled in the boxes.
When we enabled NIC teaming with smart load balancing then both the nodes are able to join the cluster.
My specific question is,
Is there any relationship between Tangosol coherence and NIC teaming? If yes, what's the relationship.
Regards,
Ritwik Bhattacharyya

I did some tinkering a while back trying to get 4Gb/s bonded etherchannels going on linux boxes but I had issues with out of order and missing packets:
4Gb/s bonded ethernet test results - finally...
But to answer your question there is no reason that you would need NIC teaming on in order to make Coherence work. It sounds like something is not configured correctly with your NIC or switch. Maybe try connecting the machines with a crossover cable instead of a switch just to eliminate the switch as a possible problem. It sounds like maybe you're just using the wrong ethernet port on a server or something.
-Andrew

NIC teaming creates packet loss (Windows 2008 R2)?

I'm experiencing some packet loss to all of our VMs that we didn't have before we made some changes to our Hyper-V implementation (Windows 2008 R2). Most of the VMs also run 2008 R2 - with 3 that run Server 2003.
The host server is a Dell R610 with three 4 port NICS - two Intel quad port gigabit and a quad port Broadcom.
We us the individual ports of the Broadcom for host management and live migration - no problems here. We use the Intel cards for both iSCSI and VM networks. Calling the two intel cards “A” and “B”, and the ports P1-4 we've used AP1, AP2, BP1, BP2 (ports
1 & 2 of both Intel NICs) for iSCSI connections, and we've created a NIC Team with AP3, AP4, BP3, and BP4 (ports 3 and 4 of both Intel NICs). The team type is "Virtual Machine Load Balancing". We then created a Hyper-V switch based on this team
for use with all of the VMs created on the host. (as a side note: prior to implementing the NIC team, we just had 4 Hyper-V switches, one associated with each of these 4 ports.)
The 4 ports of the NIC team are connected to two different Cisco SG200 switches - AP3 and BP3 are connected to switch1, and AP4 and BP4 are connected to switch2 (in an attempt to maximize redundancy). The two Cisco SG200s are simply connected to the rest
of our network - each to a different switch within the subnet. There is minimal configuration done to the SG200s (for example NO
link aggregation); spanning tree is enable however.
My question is: can the network cables be connected to different switches (as they currently are) and if so is there some configuration piece (either on the switch or within Windows) that I'm missing?
What are the options here if this configuration is incorrect? The packet loss is in the range of 0.1%, but we've had odd spikes where a VM was essentially unavailable for a brief period (a few minutes) then returned to "normal" (0,1% loss).
Pinging a device (like the SG200 itself) or another physical server (for example our domain controller or the hyper-v host itself) results in essentially 0 loss; maybe one or two packets during the course of a 12 hour ping (this was the “normal” ping
response to VMs before we created the NIC team, so I’m quite sure this has something to do with it).
Thanks in advance!

I believe when utilizing the Virtual Machine Load Balancing the ports must be connected to the same switch, stack, or chassis as the arp for the MAC could move. I believe, although I could be wrong, that the outages you see is when the machine "moves"
between ports and the arp being updated between the two switches.
I believe you are looking for switch fault tolerance teaming which will allow for the failure of adapter, cabling, or switch which will achieve your goal of maximum redundancy. This is achieved via spanning tree on the switches, which you indicated
is already configured.

HP Servers NIC Teaming with Cisco Nexus 2000/5000

Similar Messages

Maybe you are looking for