11-22-2013 10:06 AM - edited 08-29-2017 04:03 AM
Vinayak Sudame is a technical lead with the Data Center Switching Support Team in 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 Cisco Nexus 5000, Cisco Nexus 2000, and FCoE. Vinayak is also involved in developing internal and external technical Cisco content: for example, the Cisco Nexus 5000 troubleshooting guide (cisco.com), Cisco Nexus 5000 portal (partners), and so on. This involves cross-team collaboration and working with multiple different teams within Cisco. Vinayak has also contributed to training account teams and partners in customer assurance engineering (CAE) bootcamp dealing with Cisco Nexus 5000 technologies. In the past, Vinayak's responsibilities included supporting the MDS platform (Fibre Channel technologies) and work with EMC support on escalated MDS cases. He was the subject matter expert for Santap Technologies before moving to Cisco Nexus 5000 support. Vinayak holds a master's degree in electrical engineering with specialization in networking from Wichita State University, Kansas. He also holds Cisco certification CCIE (no. 20672) in routing and switching.
The following experts were helping Vinayak to answer few of the questions asked during the session: Carlos Lopez and Carlo Schmidt. Carlos and Carlo are Data Center experts and have vast knowledge in this topics..
You can download the slides of the presentation in PDF format here. The related Ask The Expert sessions is available here. The Complete Recording of this live Webcast can be accessed here.
A: Yes, if the small form-factor pluggable (SFP) validation fails, the port is down. This typically happens when you use a 1G SFP on a port that is configured for 10G. "sfp invalid" is the scenario where the port is down.
A: A FEX can only be used on a port that is configured for "switchport mode fex." A FEX transceiver is used for the connection between N5Ks and Nexus 2000 Series switches (N2Ks). So if you use these, only use them in order to connect to your FEX. Some vendor SFPs can create issues if they are not from Cisco.
A: You might also see an "err-disabled" status. There are not many statuses. Sometimes, if an interface goes down because of congestion, older switches throw Packet Over SONET (POS) errors. There are error detection methods now for link recovery. Most of the time, it ends up with an end device issue.
A: This depends on the configuration on the 6500. Auto Negotiation (AN) should not complete when a 1G SFP is inserted into a port configured for 10G.
A: Yes. It is recommended that you run the VLAN only between the two N5Ks. It should be a separate VLAN, and the VLAN should be carried over a separate link. It could be through a management port or a physical 1G or 10G port.
A: The peer link can be used in order to carry this traffic, and there is no need for a separate link unless you peer routing protocols. It is encouraged to trunk all VLANs over the peer link if you have routed VLANs.
A: You can use a vPC VLAN. In most configurations, the Layer 3 (L3) gateway is connected via a vPC. Due to this, it is required that you use a vPC VLAN.
A: Besides the Bug Search Tool, you can use the notification tool, http://www.cisco.com/cisco/support/notifications.html.The notification tool might be able to help you.
A: The release notes and the configuration guide are the best places to start. If a particular issue appears frequently, Cisco often releases "Quick Configuration guides" for these specific problems. This is not done for everything, though. N6K and N2K do not have M2 or F2 cards.
A: The Configuration Limits for the Cisco Nexus Operating System (NX-OS) has the limitations. The Release Notes have caveats.
A: Cisco bug ID CSCui74708 Nexus 6000: Loses Static route in hardware after reload. This issue is fixed in Version 6.0(2)N2(2) and later.
A: Cisco bug ID CSCuc84658 – Nexus 5000: Incorrect Adjacency for Next Hop. This was fixed in Version 6.0(2)N1(1), Version 5.2(1)N1(3), and later versions.
A: Cisco bug ID CSCta97375 GLDN:SABRE:Sabre oui is not recognized as cisco oui 547FEE. Cisco bug ID CSCtr01652 Add New OUIs to liboui's list of recognized Cisco OUIs. Cisco bug ID CSCty04686 Add MAC OUI "002a6a", "8c604f", "00defb" for 5k/UCS-FI.
A: You can download the software from the Cisco.com download software page. The DCNM download is under Cisco.com in the support section.
A: No, the Nexus 3000 Series switches (N3Ks) and N5Ks must be manually configured for 1G if a 1G SFP is used. T ports (copper) are autosensing. The 10G speed is autosensing, but the 1G speed must be manually configured.
A: This issue should not be limited to dual-homed FEXs, because it occurs on single-homed FEXs as well. The issue is possible with single-homed or dual-homed.
A: It is not yet possible.
A: Yes, you can.
A: Cisco supports a 10G environment, so you should be able to go anywhere close to the line rate. During vMotion, it could boil down to how many simultaneous vMotions can be done. It is basically limited as per the resources on hosts and not from the network perspective.
A: It is 0x8906.
A: The ethertype is 0x8914.
A: 1G is the required speed.
A: The NPIV feature is nondisruptive, but the Node Port Virtualization (NPV) feature is disruptive.
A: Yes, it does require an NPIV core switch.
A: No, switching is primarily done on the upstream NPIV switch. There is no local switching.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: