1 / 0

Nexus 2000 Connectivity - Supported Topologies

1K. Cisco Nexus. x86. Nexus 2000 Connectivity - Supported Topologies. Nexus 5500 Platform 2 nd -Generation Nexus 5000 with L3 support. Flexible port configurations Unified Port Concept: 1G / 10G / FCoE / DCB , 1/2/4/8 G FC, 1GE Fix port not support FC, Module 16x Unified Ports SFP +

naif
Télécharger la présentation

Nexus 2000 Connectivity - Supported Topologies

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. 1K Cisco Nexus x86 Nexus 2000 Connectivity - Supported Topologies
  2. Nexus 5500 Platform2nd-Generation Nexus 5000 with L3 support Flexible port configurations Unified Port Concept: 1G/10G/FCoE/DCB, 1/2/4/8 G FC, 1GE Fix port not support FC, Module 16x Unified Ports SFP+ Layer 2 / Layer 3 support Front-to-back and back-to-front airflow Support for increased number of FEX per N5500 4KVLANs 40G Uplinks (future) Latency: ~2 usec Cisco Fabric Path Support IETF TRILL & Cisco L2MP Standards-based T11 FCoE Hardware support for IEEE 1588 (Precision Time Protocol – µs accuracy & timestamp) 32K MAC Table Entries Enhanced feature SPAN, multicast
  3. Nexus 5548 Rear Panel 32 x Fixed ports 1/10 GE Expansion Module
  4. Layer 3 on Nexus 5548P N55-D160L3 field replaceable daughter card Upgradeable in-rack No un-mounting required No reduction of front panel ports. 160Gbps L3 bandwidth AvailableQ1CY11 Layer 3 Daughter card Front of the Switch Choice Future Proofing Flexibility
  5. Install L3 daughter card on Nexus 5548 AvailableQ1CY11 2 Unscrew the IO Module Pull the IO Module out Front of the Switch Plug and Screw the L3 IO Module Plug and Screw the Fan Modules 3 Unscrew the Fan Modules Pull the Fan Modules out 1
  6. Nexus 5596 2nd Generation Nexus 5000 with L3 support N559696xSFP+ (w/3x Module) in 2RU N5196P: 96x SFP+ (w/ 3x Modules) in 2RU 96 Fixed Ports capable of 10GE/1GE/FCoE/FC (Unified Port) Three Expansion Module Slots Modules Supports on Nexus 5500 Platform features AND unified ports on all ports 16x 10G/FCoE/DCB SFP+ 8x 10G/FCoE, 8x 1/2/4/8G FC 16x Unified Ports SFP+
  7. L3 Support on Nexus 5596 N5596P: 96x SFP+ (w/ 3x Modules) in 2RU Module Module Module 48x Unified Ports SFP+ Each L3 module provides 160GbpsL3 forwarding bandwidth L3 module can only be used for Nexus 5596 No front panel ports on L3 module At FCS nexus 5596 supports one L3 module. Subsequent release will support three L3 module with aggregation 480GbpsL3 throughput
  8. L3 Bandwidth and Packet Flow AvailableCY11 N5548P Intelligent Layer 3 Highlights UPC: 8-port lookup/port ASIC X-Bar Fabric: 100x100 crossbar fabric ASIC X-Bar Fabric can scale up to 12 x UPC L3 Capability (field upgradeable): 5548: 1x daughter-card slot 5596: Up to 3x GEM module Each daughter-card or GEM supports 160Gbps of bidirectional bandwidth Modules: 16x 10G SFP+ 8x 10G, 8x 1/2/4/8G FC L3 Module – 160G (no front-panel ports) Layer 3 Daughter Card UPC UPC 8 8 X-Bar Fabric 8 8 8 8 8 8 UPC UPC UPC UPC UPC UPC Module Slot 32 Fixed Ports N5596P Layer 3 Module Layer 3 Module Module Slot UPC UPC UPC UPC UPC UPC 8 8 8 8 8 8 X-Bar Fabric 8 8 8 8 8 8 UPC UPC UPC UPC UPC UPC 48 Fixed Ports
  9. L3 Features NX-OS Support Single Unified Layer 2/Layer 3 Management In Service Software Upgrade (ISSU) for Layer 3* MIBs and DCNM (Datacenter Network Manager) * Post FCS Support
  10. N5548/N2K Bundles Transition Summary Provide an easy transition from N5010/FEX and N5020/FEX to Oxygen/FEX Transition N5010P/4FEX business to N5548P/4FEX, Transition N5020P/6FEX business to N5548P/6FEX/GEM, transition N5020P/4FEX-10G to N5548P/4FEX-10G
  11. Cisco FEXlink: Virtualized Access SwitchChanging the device paradigm De-Coupling of the Layer 1 and Layer 2 Topologies Simplified Management Model, plug and play provisioning, centralized configuration Line Card Portability (N2K supported with Multiple Parent Switches – N5K, 6100, N7K) Unified access for any server (100M1GE10GE FCoE): Scalable Ethernet, HPC, unified fabric or virtualization deployment . . . Virtualized Switch
  12. Cisco FEXlink: Virtualized Access SwitchUpgrade Flexibility Nexus parent switch provides the forwarding functionality for the Virtualized Access Switch Upgrading the parent switch upgrades the capabilities of the entire virtualized Access switch Nexus 7000 Parent Switch M1 Line Card - 32 FEX, Layer 2 & 3 Ethernet Nexus 7000 Parent Switch F2 Line Card - DCB, Ethernet, FC, FCoE, NIV, Layer 2 & Layer 3, FabricPath (2HCY11) Migrating Parent Switches Nexus 5000 Parent Switch 12 FEX, DCB, Layer 2 Ethernet, FCoE, FC Nexus 5500 Parent Switch 16 FEX, DCB, Ethernet, FC, FCoE, NIV, Layer 2 & Layer 3 (1HCY11), FabricPath (2HCY11) Future Evolution of Parent Switches
  13. Nexus 5000 Parent SwitchAll Nexus 5000 are VNTag Capable Q1CY2011 * Potential to increase supported FEX to Nexus 5500 fabric link distances with 2248/2232 and Future FEX
  14. Nexus 7000 Parent SwitchFEX enabled line cards – VNTag Capable F2 2HCY2011
  15. Nexus 5000 and Nexus 7000 Parent SwitchFEX Support
  16. Nexus 2148T, 2248TP, 2232PPCapabilities
  17. Nexus 5000 and Nexus 7000 Parent SwitchFEX Capabilities * Scalability for Number of Routes, PACL/VACL/RACL for Nexus 7000 is based on M1 line card, N7K-M132XP-12 or N7K-M132XP-12XL ** Scalability for Number of Routes, PACL/VACL/RACL for Nexus 5000 is dependent on selection of parent switch, Nexus 5000 or Nexus 5500
  18. Cabling Plant Main Distribution Area – analogous to MDF MDA Location of Core equipment and main cross-connect panels Horizontal Distribution Area HDA HDA Location of the aggregation equipment and end of row cross-connect panel HDA HDA EDA EDA HDA Equipment Distribution Area Compute racks/cabinets and top of rack cross-connect panel HDA HDA BACKBONE CABLING HDA HORIZONTAL CABLING HDA HDA EDA EDA Vertical Cabling: Patch cable to compute equipment Horizontal Cabling: from rack/cabinet to end of row cross-connect Backbone Cabling: from end of row cross-connect to main cross-connect Recommendations Use fiber as horizontal cabling to ease the transition from GE to 10GE Vertical Cabling is just a patch cable top match access IO: GE, 10GE, FC, FCoE, copper, fiber, etc
  19. 2HCY11 Q1CY11 Q3CY10 1H CY2010 Fabric Extender Roadmap Internal Cisco Only Combined Platform Roadmap Nexus 2232TP 1/10GT FEX Stretch goal: Power Supply & FAN for back-to-front airflow Stretch goal: 400W DC Power Supply Nexus 2224TP 100Mbps/1000Base-T FEX Stretch Goal: NEBS on N2248TP, N2232PP Fabric Extender Transceiver Nexus 2232PP 1/10GE FEX Nexus 2248TP GE/FE FEX Hardware Nexus 5000 DEE WHY (Shipping) FET Nexus 2232PP Nexus 2248TP FEX ISSU Local FEX Port Channels (N22xx only) FCoE & DCB on N2232 FEX DEE WHY + (Shipping) 1G on Nexus 2232 Nexus 2224TP EAGLEHAWK vPC sync (configuration sync) FEX pre-provisioning 16 FEX per N5548P E-ROCKS (ECed) SVI Routing (N5500 platform) Stretch goal: Nexus 2232TP Stretch goal: 20 FEX/N5500 Stretch goal: Power Supply & FAN for back-to-front airflow Stretch goal: 400W DC Power Supply FAIRHAVEN (Planning) FabricPath Dual Layer vPC CAIRO (5.1) N2248T-1G support N2K Support on M132XP and M132XP-XL 32 FEX per N7K FET Support SVI Routing HA: FEX ISSU, port-channel N2K-to-N7K, NIC teaming VDC per FEX Nexus 7000 DELHI (5.2 - ECed) N2232PP-10G 1/10GE FEX (no FCoE on M1 card) Stretch goal: Local FEX Port Channels, vPC host-to-FEX, L3 routed interfaces on FEX, PVLAN, SPAN source, NetFlow, Nexus 2224TP FREETOWN (6.0 - CCed) FEX support on F2 Module (48p 10G, wirerate, FCoE, FabricPath) FCoE on N2232PP vPC from FEX-to-N7K FEX pre-provisioning
  20. Continuous Innovations to Simplify Configuration and Management Config Sync Config Sync enables changes on one switch to automatically synchronize to its peer switches Config Sync works in conjunction with vPC FEX Pre-Provisioning Admins will have the flexibility to pre-provision FEX host ports prior to the FEX physically present in the network. Port Profiles Port-Profile feature consists of a configuration template which can be applied to an interface or a range of interfaces Eliminates repetitive interface configurations HIF Simplified FEX configuration Ease of management for large number of interfaces Flexible rollout to support heterogenous environment Reduced operational costs BusinessValue
  21. Virtualized SwitchDevice Level Redundancy Switch level High Availability needs to consider Control Plane Supervisor Redundancy Data Plane Forwarding ASIC Redundancy Fabric ASIC Redundancy Fabric Isolated/Redundant Paths System Mechanical Redundancy Power Supply Fan Redundant Supervisor – Nexus 5000/5500 running in vPC mode or Nexus 7000 with dual supervisor 10 – 80 Gbps via 1 – 8 redundant fabric links per line card (N2K) 1 – 32 Line Cards per virtual switch
  22. Nexus 2000 Fabric ExtenderFabric Redundancy Models Fabric Extender associates (pins) a server side (1GE) port with a fabric uplink Server ports are either individually pinned to specific uplinks (static pinning) or all interfaces pinned to a single logical port channel Behavior on FEX uplink failure depends on the configuration Static Pinning – Server ports pinned to the specific uplink are brought down with the failure of the pinned uplink Port Channel – Server traffic is shifted to remaining uplinks based on port channel hash Server Interface goes down Static Pinning Server Interface stays active Port Channel
  23. Virtualized Access SwitchSupervisor Redundancy—vPC Single Supervisor Based Virtual Switch Dual Supervisor Based Virtual Switch – 4.1(3)N1 Single Supervisor – 1 x N5K Dual Supervisor – 2 x N5K 10 – 40 Gbps Fabric allocated per line card (N2K) 20 – 40 Gbps Fabric allocated per line card (N2K) 1 – 12 Line Cards per virtual switch 1 – 12 Line Cards per virtual switch
  24. Virtualized Access SwitchvPC Redundancy Models—Dual Chassis vPC provides two redundancy designs for the virtualized access switch Option 1—MCEC connectivity from the server Two virtualized access switches bundled into a vPC pair Full redundancy for supervisor, line card, cable or NIC failure Logically a similar HA model to that currently provided by VSS 802.3ad Link Aggregation Control Protocol (LACP) Two Virtualized access switches Each with a Single Supervisor vPC peers MCEC from server to the access switch MultichassisEtherChannel (MCEC) LACP
  25. Virtualized Access SwitchvPC Redundancy Models—Dual Supervisor vPC Option 2—Fabric Extender connected to two Nexus 5000 From the server perspective a single access switch with each line card supported by redundant supervisors Full redundancy for supervisor, fabric via vPC and cable or NIC failure via active/standby NIC redundancy Logically a similar HA model to that currently provided by dual supervisor based modular switch Fabric Extender N2Kdual homed to redundant Nexus 5000
  26. Nexus 7000 Parent SwitchSystem High Availability Nexus 7000 provides chassis based high availability All physical components physically redundant NX-OS high availability Fabric Port channel between a Nexus 2248 to a single Nexus 7000 The port channel can span several I/O Modules for redundancy Component level redundancy is similar to dual homed Nexus 5000/5500 with dual homing to 2 x Nexus 7000 Dual Sup and Chassis HA Fabric Port Channel Spans line cards
  27. Nexus 5000 Parent SwitchVirtualized Access Switch High Availability Models Switch Fabric + Network level and Server level HA Switch Fabric + Control Plane + Network level and Server level HA vPC Peer Link vPC Peer Links N2K MCEC Host MCEC MCEC – Running between Single Supervisor Based Virtual Switches Dual Supervisor Based Virtual Switches
  28. Nexus 7000 Parent SwitchVirtualized Access Switch High Availability Models Switch Fabric + Control Plane + Network level and Server level HA
  29. NIC Teaming OptionsServer Team view of HA 6 Options
  30. Automatic: This option figures out what is connected upstream and automatically configures the best teaming option 802.3ad dynamic: This option requires LACP support and in this configuration vPC since the NICs are split across FEXes Switch Assisted Load Balancing: Translation = static port-channeling Transmit Load Balancing: 1 Port RX all ports in the team TX Network Fault Tolerance: Translation: Active/Standby 802.3ad requires vPC and LACP Switch Assisted Load Balancing requires vPC only TLB works ALWAYS and provides increased bandwidth in the TX direction NFT works always and provides not bandwidth benefits to the server NIC Teaming OptionsServer Team view of HA
  31. TLB Option
  32. TLBAll Links TX and One Link RX (and TX) 5k01 5k02 Peer-link primary secondary “fabric links” vPC 1 vPC 2 FEX100 FEX120 HIF HIF
  33. For Your Reference Data Center Access ArchitectureNexus 5000 and 2148T Deployment Options Not Supported With vPC Without vPC 2HCY11(55xx Only)
  34. For Your Reference Data Center Access ArchitectureNexus 5000 & 2248T Deployment Options Not Supported With vPC Without vPC 2HCY11(55xx Only)
  35. For Your Reference Data Center Access ArchitectureNexus 5000 & 2232 Deployment Options Not Supported With vPC Without vPC 2HCY11(55xx Only)
  36. Data Center Access ArchitectureNexus 7000 & 2248/2232 Deployment Options For Your Reference N7K Cairo NX-OS – Q4CY10 N7K Delhi NX-OS - Q1CY11 N7K - 2HCY2011 (pre CC) Y Y Y active active active active active active stretch N Y active active active active active active N N radar
  37. 1K Cisco Nexus x86 Nexus 2000 DesignAgenda FEXLink and the Virtualized Switch – This material is covered on Day 1 (review as required) Nexus 2000 Feature Support High Availability and Switch Configurations Server Redundancy Spanning Tree and FEX Support for enhanced edge capabilities (L3, FCoE, FabricPath) Impact on Network Topology
  38. Nexus Virtualized Access Switch Nexus STP Design Considerations Access design needs to take into account topology and hardware capabilities of the current generation FEX Currently all Fabric Extender server ports are hard coded as STP edge ports BPDU Guard is enabled and can not be disabled Global BPDU Filtering is enabled on the Nexus 2000 HIF ports by default Interface level BPDU Filtering can be configured Edge ports DO count against the STP logical port count Fabric Extender ports are STP edge ports, BPDU Guard is enabled, downstream devices can not generate BPDU’s. Flexlink or BPDU Filtering VM VMK SC
  39. Nexus Virtualized Access Switch Nexus 2000 Design Considerations N2K HIF ports have BPDU Guard enabled by default (it is not possible to disable currently) If a BPDU is received port will transition to err-disable state Global BPDU Filter compliments BPDU Guard On link up port will send 10-12 BPDUs and then stop (in order to reduce CPU load) If BPDU is received the port will err-disable This is NOT interface level BPDU Filtering E E E 1. X-Connected patch cable 2. BPDU Sent on Link-Up 3. BPDU Guard err-disables edge port and prevents loop dc11-5020-3# show spanning-tree int eth 155/1/25 detail Port 1945 (Ethernet155/1/25, vPC) of MST0000 is designated forwarding Port path cost 200, Port priority 128, Port Identifier 128.1945 <snip> The port type is edge Link type is point-to-point by default, Internal Bpdu guard is enabled Bpdu filter is enabled by default PVST Simulation is enabled by default BPDU: sent 11, received 0 4. BPDU are not sent once link is up and active
  40. Nexus Virtualized Access Switch Nexus 2000 Design Considerations Key Point: Ensure you count EDGE & EDGE TRUNK ports too STP Logical Ports Logical Ports = (# Trunks) x (# VLANs per trunk) Nexus 7000 STP logical port scaling: Rapid-PVST+ limit = 16,000* MST limit = 75,000* Nexus 5000 STP logical port scaling: Rapid-PVST+ limit = 12,000* MST limit = 12,000* * Not a HW (Line Card, ASIC) limitation, SW improvements will increase this number, CPU upgrades will also increase scalability
  41. Nexus Virtualized Access Switch Stub Layer 2 Devices When connecting any device to Nexus 2000 HIF ports ensure that the ‘stub’ switch is not running STP on the uplinks Single homed with BPDU filtering enabled on the uplink Dual homed with vPC and BPDU filtering enabled on the port channel Dual homed with Flexlink These are supported designs vPC + BPDU Filtering BPDU Filtering Flexlink THESE ARE NOT RECOMMENED DESIGNS
  42. Nexus Virtualized Access Switch Stub Layer 2 Devices BPDU filtering on the uplinks of ‘stub’ switches switches enables connectivity to Nexus HIF ports It is recommended that you do not disable STP on the ‘stub’ switches Leverage port security, storm control, BPDU Guard and where appropriate 802.1x on ‘stub’ switch access ports Dual homed vPC direct to N5K vPC + BPDU Filtering BPDU Filtering Flexlink interface GigabitEthernet0/1 switchport trunk native vlan 100 switchport trunk allowed vlan 100,200 switchport mode trunk spanning-tree bpdufilter enable interface Port-channel1 switchport trunk native vlan 100 switchport trunk allowed vlan 100,200 switchport mode trunk spanning-tree bpdufilter enable
  43. Nexus Virtualized Access Switch Stub Layer 2 Devices Design Topologies that do not require STP for downstream link recovery can be configured Flexlink is one option for connecting a downstream switch that is STP independent Flexlinkdisables Spanning Tree on the active and backup interfaces BPDUs are dropped in HW on ingress and not transmitted upstream on the ‘flexlink’ ports vPC + BPDU Filtering BPDU Filtering Flexlink interface GigabitEthernet0/1 switchport trunk native vlan 100 switchport trunk allowed vlan 100,200 switchport mode trunk switchport backup interface Gi0/2 switchport backup interface Gi0/2 multicast fast-convergence switchport backup interface Gi0/2 prefer vlan 200
  44. Nexus Virtualized Access Switch Stub Layer 2 Devices Spanning Tree should ‘not’ be disabled on either the Nexus 5000 nor the downstream switches (e.g. Cisco 2960) DO NOT extend the downstream device topology (External devices can still create loops in the topology) Harden the ‘stub’ switch access ports This design suitable onlyfor highly controlled environments 1GE Blade Switches interface FastEthernet0/24 switchport access vlan 200 switchport mode access switchport port-security violation protect storm-control broadcast level pps 1k storm-control multicast level pps 1k spanning-tree bpduguard enable
  45. 1K Cisco Nexus x86 Nexus 2000 DesignAgenda FEXLink and the Virtualized Switch – This material is covered on Day 1 (review as required) Nexus 2000 Feature Support High Availability and Switch Configurations Server Redundancy Spanning Tree and FEX Support for enhanced edge capabilities (L3, FCoE, FabricPath) Impact on Network Topology
  46. Virtualized Access Switch - FCoEExtending FCoE – Nexus 2232 SAN A SAN B FEX-2232 extends the reach of 10Gig Ethernet/FCoE to distributed line card (ToR) Support for up to 384 10Gig/FCoE attached hosts managed by a single Nexus 5000 Nexus 5000 is the FCF or can be in FIP Snooping + mode (when supported) Currently Nexus 2232 needs to be single homed to upstream Nexus 5000 (straight through N2K) to ensure SAN ‘A’ and SAN ‘B’ isolation Server Ethernet driver connected to the FEX in NIC Teaming (AFT, TLB) or with vPC (802.3ad) Nexus 5000 as FCF or as E-NPV device Nexus 5000 Nexus 5000 Fabric Links Option 1: Single Homed Port Channel Fabric Links Option 2: Static Pinned Nexus 2232 10GE FEX Nexus 2232 10GE FEX Server Option 1: FCoE on individual links. Ethernet traffic is Active/Standby Server Option 2: FCoE on a vPC member PC with a single link Requires FIP enabled CNAs
  47. Virtualized Access Switch - FCoEExtending FCoE – Nexus 2232 SAN A SAN B It is possible to attach DCB capable blade switches to 10G FEX ports (2232) Same high availability design rules must be followed Native Ethernet links from Nexus 4000 to FEX can be individual links or port-channeled FCoE links from Nexus 4000 to FEX can be single links or a single port-channel FEX must be single homed to upstream Nexus 5000 Not a recommended design due to difficulties in planning for over-subscription of LAN and SAN (including FLOGI scalability) Not Currently Recommended BPDU Guard on N2K server ports is currently hard coded Nexus 5000 as FCF or as E-NPV device Nexus 5000 Nexus 5000 Need BPDU Filter on IP N4k uplinks Nexus 2232 10GE FEX STP Edge Ports Single Homed Unified Wire Need BPDU Filter on N4k uplinks Dedicated FCoE links - STP not running on FCoE VLAN FIP Snooping Nexus 4000 DCB Blade Switch
  48. Virtualized Access Switch Nexus 7000 & Nexus 2232 Nexus 7000 + Nexus 2232 provides 10G classical Ethernet connectivity Leverage existing SAN infrastructure FCoE is planned to be supported with the use of F2 series line cards (2HCY11) SAN A SAN B Nexus 7000 Nexus 2232 10GE FEX
  49. Virtualized Access Switch Nexus 7000 FabricPath (Q4CY10) FabricPath – Migration to a ‘Routed’ Layer 2 Data Center Fabric FabricPath is a ‘Routed’ layer 2 topology Flexibility of layer 2 to support compute workload migration and applications requirement Scalability of routed fabric Availability of a routed fabric Nexus 7000 parent switch with F1 and M1 line cards will ‘not’ allow the use of FabricPath with attached FEX Support for FabricPath with N2K is planned for F2 (2HCY11) ‘Ships in the Night’ support for FCoE (Q1CY11) Servers Servers
  50. Virtualized Access Switch Nexus 5500 & Nexus 2000 FabricPath – Migration to a ‘Routed’ Layer 2 Data Center Fabric FabricPath is a ‘Routed’ layer 2 topology Flexibility of layer 2 to support compute workload migration and applications requirement Scalability of routed fabric Availability of a routed fabric Nexus 5500 parent switch will allow the use of FabricPath with attached FEX – 2HCY11 Supported with all Nexus 2000 No support planned for Nexus 5000 (5010/5020) ‘Ships in the Night’ support for FCoE FC Attached Storage Servers, FCoE attached Storage Servers
  51. Virtualized Access Switch Nexus 7000 & Nexus 2000 – Routed Access (Q4CY10) Routed Access support with Nexus 7000 and FEX (Q4CY10) Leverage existing SAN infrastructure FCoE is planned to be supported with the use of F2 series line cards (2HCY11) Layer 3 uplinks SAN A SAN B L3 L2
  52. Virtualized Access Switch Nexus 5500 & Nexus 2000 – Routed Access (Q1CY11) Support for Routed Access Topologies with Nexus 5500 & Nexus 2000 (Q1CY11) Supported with all Nexus 2000 No support planned for Nexus 5000 ‘Ships in the Night’ support for FCoE L3 L2 FC Attached Storage Servers, FCoE attached Storage Servers
  53. For More Information SAVBU N5k/N2k webpage http://savbu.cisco.com/index.php/nexus-5k-homepage-side Nexus bootcamp training slide and VOD http://savbu.cisco.com/index.php/boot-camps/1167-savbu-tmepm-led-bootcamps QA alias ask-nexus5000-tme@cisco.com ask-nexus5000-pm@cisco.com
More Related