This document contains the slides for the live webcast.
As part of the foundation for Cisco Unified Fabric, the Cisco Nexus 5000 and 6000 Series Switches help address business, application, and operational requirements of evolving data centers. They provide infrastructure simplicity to decrease the total cost of ownership. During the live webcast, Cisco expert Vinayak Sudame covered important caveats and best practices for the Cisco Nexus series switches, including configuring and troubleshooting Cisco Nexus 5000 and 6000 Series Switches as well as Fibre Channel over Ethernet (FCoE). In addition, Vinayak also provided best practices for working with the Technical Assistance Center (TAC).
Cisco Nexus 5000, 6000 and FCoE Important Caveats
Cisco Nexus 5000, 6000 and FCoE Best Practices
TAC Best Practices
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 has a Masters in Electrical Engineering with Specialization in Networking from Wichita State University, Kansas and is a CCIE # 20672 in Routing and Switching.
Hi all,We recently migrate our core network from plain old Catalyst and Nexus switches to ACI, and stumbled upon one case.An IBM integrated system (PureApp) was connected to the network via 2 port-channel (non-vPC) stemming from its ToR switches. As we mi...
My network topology is simple to understand.ACI network configured as L2 OUT. Mapping of VLAN to BD is BD=EPG=VLAN.Gateways of all the vlans are on firewall.Servers are connected to cisco 3560 switches and switches connected to LEAF switches. I...
EPG1 -- BD1 -- VRF1 -- Tenant1EPG2 -- BD2 -- VRF1 -- Tenant1A) from the routing perspective is the above scenario same as having EPG1 and EPG2 in the same BD? that is do we need to do any extra config other than the creating epg's and having contracts?b) ...
Posting to see if anyone else has encountered this same issue, when polling the nexus 3064 for transceiver information, every once in a while certain ports will return value of 0 for things like temperature, voltage, dbm, etc. and sometimes they wil...
Hi Team, We are using Nexus5548UP where ports 1-19 are ethernet and ports 20-32 are for FC now I want to use 2 additional ports for FC now my question is, can I use ports 14-15 for FC or is it a rule that the FC ports have to be contiguous as such I ...