presentacion intro nexus 7000

© 2008 Cisco Systems, Inc. All rights reserved. Cisco ConfidentialCisco Expo 2008 1

Cisco Next Generation Data Center:Nexus 7000 Introduction

Marian Klas, CCIE #[email protected]

© 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 2Cisco Expo 2008

Agenda

Introduction

Nexus 7000 Chassis

Nexus 7000 Modules

Nexus 7000 Fabric & Bandwidth

NX-OS Overview

Data Center Network Manager

Data Center Network Design Evolution

Q & A


OperationalLimitations

Data Centers Are Under Increasing Pressure

New BusinessPressures

Collaboration SLA MetricsEmpowered User Global Availability Reg. Compliance

Power & Cooling ProvisioningAsset Utilization Security Threats Bus. Continuance


Scale of Current Problems Demands a New Approach

Infrastructure ScalabilityInfrastructure ScalabilityBy 2009, 50% of large businesses will spend more on power By 2009, 50% of large businesses will spend more on power and cooling then on new servers and cooling then on new servers (Gartner, 2006)(Gartner, 2006)

QuadQuad--cores and octalcores and octal--cores will drive significantly more trafficcores will drive significantly more trafficStorage is expected to continue to grow at a 40Storage is expected to continue to grow at a 40--70% CAGR 70% CAGR (Gartner, 2006)(Gartner, 2006)

Operational Continuity

Expectation of 24x7 application availability

54% of network downtime is caused by human error (Uptime Institute, 2007)

Operational ContinuityOperational Continuity

Expectation of 24x7 application availabilityExpectation of 24x7 application availability

54% of network downtime is caused by human error 54% of network downtime is caused by human error (Uptime Institute, 2007)(Uptime Institute, 2007)

Transport Flexibility

Continued deconstruction of the server increases demands on the network

Market transitions between transport technologies and application architectures

Transport FlexibilityTransport Flexibility

Continued deconstruction of the server increases demands on Continued deconstruction of the server increases demands on the networkthe network

Market transitions between transport technologies and Market transitions between transport technologies and application architecturesapplication architectures


Critical Infrastructure for Data Center 3.0Unified Fabric and I/O Interfaces

Cisco® Nexus Switching Platforms

NX-OS Operating System


Simply infrastructure (reduce capex) and operational complexity (lower opex)Lowers overall data center power draw

Forward Investment Protection

Engineered the most stringent availability requirements

Designed with features that improve operational continuity

Delivers virtualized network services

Provides holistic view of the network to simplify management and facilitate troubleshooting


Agenda

Introduction

Nexus 7000 Chassis

Nexus 7000 Modules


NX-OS Overview



Q & A


Nexus 7000: First In Class

Data CenterClass Platform

Data CenterClass Operating

System


(DCNM)

Multi-Terabit system

550Gb/slot capable

Optimized for 10 / 40 / 100 Gbps interfaces

Extreme availability

Multi-protocol (Ethernet, Storage and Unified I/O)

Self Healing Operating system

Graceful system operation

Virtualized Control Plane and Data Plane

Fully Modular

Security

Unified Data Center Manager

Configuration / Provisioning / Service Enablement / Network Ops / Status / Statistics / Event Management

Powerful feature rich web services API (XML)


Nexus 7010 10-Slot ChassisFirst chassis in Nexus 7000 product familyOptimized for data center environmentsHigh density

256 10G interfaces per system

High performance1.2Tbps system bandwidth at initial release80Gbps per slot60Mpps per slot

Future proofInitial fabric provides up to 4.1TbpsProduct family scaleable to 15+Tbps40/100G and Unified Fabric ready

33.1-38”(84-96.5cm)

17.3” (43.9cm)

21 RU36.5”

(92.7cm)


Nexus 7010 Chassis Front

Lockable front doors (removable)

System status LEDs

Integrated cable management with door

Air intake with optional filter

8 payload slots (1-4, 7-10)

2 supervisor slots (5-6)


Nexus 7010 Chassis Back

Air exhaust

5 crossbar fabric modules

2 fabric fan trays

2 system fan trays

3 power supplies


System Power

6000W AC power supply for Nexus 7000 series chassis

Dual inputs at 220/240V or 110/120V

Proportional load-sharing among supplies

Hot swappable

Blue beacon LED for easy identification


Cable Management

Integrated cable management tray with strapsNo interference with servicing of common equipmentCable grooming to right, left, or splitCan route up to 384 Cat6A cables to one side of chassis –worst-case scenarioCable tray cover and lockable front doors prevent accidental interference


Agenda

Introduction

Nexus 7000 Chassis

Nexus 7000 Modules


NX-OS Overview



Q & A


Compact Flash cover

Supervisor EngineDual-core 1.66GHz Intel Xeon processor with 4GB DRAMConnectivity Management Processor (CMP) for lights-out management 2MB NVRAM, 2GB internal bootdisk, 2 external compact flash slots10/100/1000 management port with 802.1AE LinkSecConsole & Auxiliary serial portsUSB ports for file transferBlue beacon LED for easy identification

BeaconLED

Console Port

AUX PortManagementEthernet

USB Ports CMP Ethernet

Reset ButtonStatusLEDs

Compact FlashSlots


Management Ethernet Interface

10/100/1000 interface used exclusively for system managementBelongs to dedicated “management” VRF

Prevents data plane traffic from entering/exiting from mgmt0 interfaceCannot move mgmt0 interface to another VRFCannot assign other system ports to management VRF

Capable of IEEE 802.3ae LinkSec encryption (not enabled in 4.0 release)


Out-of-bandmanagementnetwork

CMPCMP

CMPCMP

DataNetwork

CMPCMP

CMPCMP

Connectivity Management Processor (CMP)Standalone, always-on microprocessor on supervisor engine

Provides ‘lights out’ remote management and disaster recovery via 10/100/1000 interface

Removes need for terminal servers

Monitor supervisor and modules, access log files, power cycle supervisor, etc.

Runs lightweight Linux kernel and network stack

Completely independent of NX-OS on main CPU

DataNetwork

console cables

Terminal Servers(out-of-bandconsole connectivity)

Out-of-bandmanagementnetwork


32-Port 10GE I/O Module32 10GE ports with SFP+ transceivers80G full duplex fabric connectivityIntegrated 60Mpps forwarding engine for fully distributed forwarding4:1 oversubscription at front panel

Virtual output queueing (VOQ) ensuring fair access to fabric bandwidth802.1AE LinkSec on every portBuffering:

Dedicated mode: 100MB ingress, 80MB egressShared mode: 1MB/port +100 MB ingress, 80MB egress per 4 ports

Queues: 8q2t ingress, 1p7q4t egressBlue beacon LED for easy identification

SFP+

SR at initial release – 300m over MMFLR post-release – 10km over SMF


Shared versus Dedicated Mode

9 11 13 15

9 11 13 15

Dedicated modeOne interface gets 10G bandwidth

Three interfaces disabled

Shared modeFour interfaces share 10G bandwidth

10G

To fabric

10G

To fabric


48-Port 1GE I/O Module48 1GE 10/100/1000 RJ-45 ports

40G full duplex fabric connectivity

Integrated 60Mpps forwarding engine for fully distributed forwarding

Virtual output queueing (VOQ) ensuring fair access to fabric bandwidth

802.1AE LinkSec on every portBuffer: 7.5MB ingress, 6.2MB egressQueues: 2q4t ingress, 1p3q4t egressBlue beacon LED for easy identification


Agenda

Introduction

Nexus 7000 Chassis

Nexus 7000 Modules


NX-OS Overview



Q & A


I/O Module Bandwidth Capacity

Initially shipping I/O module bandwidth: 80Gbps per slotAssumes 8 * 10G ports in dedicated mode per module

In Nexus 7000 10-slot chassis:(80Gbps/slot) * (8 payload slots) = 640Gbps

(640Gbps) * (2 for full duplex operation) = 1280Gbps = 1.2Tbps system bandwidth

1.2 Terabits per second initial system bandwidth


Fabric Bandwidth Capacity

Initially shipping fabric bandwidth: 230Gbps per payload slot, 115Gbps per supervisor slot

Initially shipping modules cannot fully leverage fabric bandwidthAssumes future modules that can leverage full bandwidth

In Nexus 7000 10-slot chassis:(230Gbps/slot) * (8 payload slots) = 1840Gbps(115Gbps/slot) * (2 supervisor slots) = 230Gbps(1840 + 230 = 2070Gbps) * (2 for full duplex operation) = 4140Gbps = 4.1Tbps system bandwidth

4.1 Terabits per second fabric bandwidth capacity


Future Vision for Platform Series

Future goal to double fabric bandwidth500+Gbps bandwidth per slot

Requires future fabric module

10 slot chassis will scale to 9+Tbps system bandwidth

18 slot chassis will scale to 15+Tbps system bandwidth

15+ Terabits per second platform bandwidth capacity


Fabric Module

Provides 46Gbps per I/O module slot

Also provides 23G per supervisor slot

Up to 230Gbps per slot with 5 fabric modules

Initially shipping I/O modules do not leverage full fabric bandwidth

Load-sharing across all fabric modules in chassis

Multilevel redundancy with graceful performance degradation

Non-disruptive OIR

Blue beacon LED for easy identification


46Gbps92Gbps138Gbps184Gbps230Gbps

Fabric Capacity and RedundancyPer-slot bandwidth capacity increases with each fabric module

1G module requires 2 fabrics for N+1 redundancy

10G module requires 3 fabrics for N+1 redundancy

4th and 5th fabric modules provide additional level of redundancy

Future modules will leverage additional fabric bandwidth

Fabric failure results in reduction of overall system bandwidth

Fabrics

ModuleSlots

40G

1G Module

80G

10G Module


Access to Fabric Bandwidth

Supervisor engine controls access to fabric bandwidth using central arbitration

Fabric bandwidth represented by Virtual Output Queues (VOQs)


What Is VOQ?Ingress module

Module 1 Module 2(1G module)

Module 3(10G module)

Module 4(10G module)

VOQs forModule 2

0 1 2 30 1 2 30 1 2 30 1 2 3

VOQs forModule 3

0 1 2 30 1 2 30 1 2 30 1 2 3

0 1 2 30 1 2 3

0 1 2 30 1 2 3

VOQs forModule 4

0 1 2 30 1 2 3

0 1 2 30 1 2 3

0 1 2 30 1 2 3

0 1 2 30 1 2 3

Egress modules

Fabricmodule

0 1 2 30 1 2 3

0 1 2 30 1 2 3

0 1 2 30 1 2 3

0 1 2 30 1 2 3

Destination 1

Destination 2

Destination 3

Destination 4

Destination 5

Destination 6

Destination 7

Destination 8

Destination 1

Destination 2

Destination 3

Destination 4

Destination 5

Destination 6

Destination 7

Destination 8

0 1 2 30 1 2 30 1 2 30 1 2 3

0 1 2 30 1 2 3

0 1 2 30 1 2 3

Destination 1

Destination 2

Destination 3

Destination 4 0 1 2 30 1 2 30 1 2 30 1 2 3

EgressCapacity

(ability to receive traffic from fabric)

VOQ Buffers correspond to Egress Capacity

(send traffic into fabric based on destination)


Centralized Fabric Arbitration

Access to fabric bandwidth on ingress module controlled by central arbiter on supervisor

In other words, access to the VOQ for the destination across the fabric

Arbitration works on credit request/grant basisModules communicate egress fabric buffer availability to central arbiterModules request credits from supervisor to place packets in VOQ for transmission to destination over fabricSupervisor grants credits based on egress fabric buffer availability for that destination

Arbiter discriminates among four classes of servicePriority traffic takes precedence over best-effort traffic across fabric


CentralArbiter

Module 2

Fabrics

VOQ Operation

Supervisor

BufferCredits

VOQ fore2/1,3,5,7

VOQ fore1/1,3,5,7

0 1 2 3VOQ for

e3/1,3,5,7

0 1 2 3 0 1 2 3

Capacity available!

Capacity available! Capacity

available!

Module 1 Module 3

0 1 2 3Egress

DestinationCapacity

EgressDestination

Capacity

0 1 2 3Egress

DestinationCapacity

0 1 2 3

Egress modules have capacity to receive traffic

from fabric


Fabrics

VOQ Operation

Supervisor

Module 1 Module 2 Module 3

0 1 2 3VOQ for

e3/10 1 2 3

EgressDestination

Capacity

0 1 2 3Egress

DestinationCapacity

0 1 2 3VOQ for

e2/1

INGRESS MODULE EGRESS MODULES

VOQs on ingress module correspond to capacity

on egress modules

CentralArbiter

BufferCredits

VOQ fore2/1,3,5,7

VOQ fore1/1,3,5,7

0 1 2 3VOQ for

e3/1,3,5,7

0 1 2 3 0 1 2 3


Fabrics

VOQ Operation

Supervisor

Module 1 Module 2 Module 3

0 1 2 3VOQ for

e3/1 Destined to e3/1, priority

level 1

Request to transmit to

e3/1, priority 1!

Request granted!

0 1 2 3Egress

DestinationCapacity

Buffer for VOQ priority 1 now

available!

0 1 2 3Egress

DestinationCapacity

0 1 2 3VOQ for

e2/1

INGRESS MODULE EGRESS MODULES

CentralArbiter

BufferCredits

VOQ fore2/1,3,5,7

VOQ fore1/1,3,5,7

0 1 2 3VOQ for

e3/1,3,5,7

0 1 2 3 0 1 2 3

Deduct credit from VOQ priority 1


Benefits of Central Arbitration and VOQ

Ensures fair access to bandwidth for multiple ingress ports transmitting to one egress portPrevents congested egress ports from blocking ingress traffic destined to other portsPriority traffic takes precedence over best-effort traffic across fabricEngineered to support Unified I/O

Can provide no-drop service across fabric for future FCoE interfaces


Agenda

Introduction

Nexus 7000 Chassis

Nexus 7000 Modules


NX-OS Overview



Q & A


NX-OSSAN-OS

IOS

NX-OS: Purpose Built for the Data Center

CiscoNexus

OperationalContinuity

InfrastructureScalability

TransportFlexibility


NX-OSSoftwareArchitecture

‘Next-generation’ operating system that brings 3 fundamental technologies into a single platform:– Layer-2 classical (now) and unified I/O switching (future)– Layer-3 multi-protocol routing (now)– Storage protocols and SAN switching (future)

“100% features for 80% of the customers”– NX-OS is not all things to all people– But is state of the art for targeted environments

Design Philosophy– Invest in sophisticated software infrastructure so that multiple features can leverage it– Dealing with software complexity that is growing all the time– Focus on Serviceability– Provide comprehensive management that extends well beyond CLI using a Wizard-based GUI– Modularity is paramount

Layer-2 Protocols Storage ProtocolsLayer-3 Protocols

Interface Management

Chassis Management

Kernel

Sysm

gr, P

SS &

MTS

SNM

P, X

ML,

CLI

Man

agem

ent

Chip/Driver Infrastructure

VLAN mgr

STP

OSPF

BGP

EIGRP

GLBP

HSRP

VRRP

VSANsZoningFCIPFSPFIVR

UDLD

CDP

802.1XIGMP snp

LACP PIMCTS SNMP

Other Services

Future ServicesPossibilities

……

Protocol Stack (IPv4 / IPv6 / L2)


New NX-OS Feature Navigator

http://www.cisco.com/cdc_content_elements/flash/dataCenter/ciscofeaturenavigator/index.html

Available NOW


NX-OS LicensingSimple, Flexible Licensing Model

There are three levels of enforced licensing: Base, Enterprise Services, and Advanced Services

Grace periods facilitate feature testing and trials without buying a license (for example, 120 days), with some restrictions. The Cisco Trusted Security does not have a grace period because of export restrictions on strong cryptography

Advanced Services

Enterprise Services

Base

GREPBRMSDP

ACLsTACACS+NACCall Home

Cisco GOLDEEMStorm

controlUDLDJumbo Frames

802.1xIPSGDAIDHCP snoopingCoPPVRF liteVRRPGLBPHSRP

Cisco Trusted Security

VDCs

IGMPPIM-SSMBidirectional PIMPIM-SMGraceful

RestartBGPIS-ISEIGRPOSPF

RADIUSSNMPRBACSSHv2Port Security

uRPF check

DHCP helper

IGMP snoopingRIP/RIPng

QoSSPANNetFlowPVLANsLACP802.1QMSTP+PVRST+ISSU

Note: Enterprise Services is NOT included with Advanced Services license


Stateful Fault Recovery

Linux Kernel

BG

P

OSP

F

PIM

TCP/

UD

P

IPv6

STP

HSR

P

LAC

P

etc

HA Manager

Restart process!

If a fault occurs in a process…HA manager determines best recovery action (restart process, switchover to redundant supervisor)Process restarts with no impact on data plane

State checkpointing (PSS) allows instant, stateful process recoverySoftware utilizes Graceful Restart where appropriate

Nexus Data Plane

PSS

NX-OS services checkpoint their runtime state to the PSS for recovery in the event of a failure


Hardware FIB

Software RIB

Stateless Fault Recovery

Linux Kernel

BG

P

OSP

F

PIM

TCP/

UD

P

IPv6

STP

HSR

P

LAC

P

etc

HA Manager

Restart process!

Graceful restartGraceful restart

Routing updatesRouting updates

If a fault occurs in a non checkpointing process (L3 routing):Process restarts with no impact on data plane

– Software utilizes Graceful Restart where appropriate (OSPF, EIGRP, IS-IS, BGP)– Otherwise periodic updates (RIPv2, PIM, IGMP, MSDP, MLD)

Table Update

Nexus Data Plane


Release 4.0

Release4.1

In-Service Software Upgrade

Linux Kernel

OSP

F

BG

P

PIM

etc.

HA Manager

Nexus Data Plane

Linux Kernel

HA Manager

Active

I/O Module Images

Upgrade and reboot

Release 4.0

Release4.1

OSP

F

BG

P

PIM

etc.

Standby

Initiate stateful failoverUpgrade and rebootUpgrade and reboot I/O modules

Nexus7k# install all kickstart bootdisk:4.1-kickstart system bootdisk:4.1-systemNexus7k#

Release 4.0

Release4.1


Virtual Device Contexts (VDCs)

VDC – Virtual Device ContextFlexible separation/distribution of Software Components

Flexible separation/distribution of Hardware Resources

Securely delineatedAdministrative Contexts

Infrastructure

Layer-2 Protocols Layer-3 Protocols

VLAN mgr

STP

OSPF

BGP

EIGRP

GLBP

HSRP

VRRP

UDLD

CDP

802.1XIGMP sn.

LACP PIMCTS SNMP

RIBRIB


Layer-2 Protocols Layer-3 Protocols

VLAN mgr

STP

OSPF

BGP

EIGRP

GLBP

HSRP

VRRP

UDLD

CDP

802.1XIGMP sn.

LACP PIMCTS SNMP

RIBRIB


Kernel

VDC A

VDC B

VDC AVDC A VDC BVDC B

VDC n

VDCs are not…The ability to run different OS levels on the same box at the same time

based on a hypervisor model; there is a single ‘infrastructure’ layer that handles h/w programming…


Virtual Device Contexts (VDCs)

Network Consolidation:Multiple logical nets/single physical net

Maintain clear delineation between nets

Independent Topologies

Clear Management Boundaries

Fault Containment

Service Velocity:In-line tests

Rapid deployment and rollback

e.g. Enable Utility Computing

Device Consolidation:Logical Appliances

Multi-switch emulation

Pwr, Cooling & Real-Estate efficiencies

Physical network islands are virtualized

onto common datacenter networking

infrastructure

VDCExtranet

VDCProd

VDCDMZ


Agenda

Introduction

Nexus 7000 Chassis

Nexus 7000 Modules


NX-OS Overview



Q & A


DCNM Solution Components

DCNM is a Client Server Solution

DCNM Server communicates with the NX-OS devices

DCNM Client communicates with the DCNM Server

NX-OS Device(s)

DCNM Server

DCNM Client


DCNM DiscoveryDiscovers NX-OS and Cisco IOS devicesDiscovers adjacent devices if CDP enabledServer collects extensive switch inventory and configuration details. Based on the collected information, DCNM Server builds a virtual network model.As part of discovery process, DCNM establishes an SSH session with each NX-OS device managed by DCNM and each Cisco IOS device discoveredSSH session is left in place after discovery. DCNM relies on the SSH session to gather information at regular intervals.


DCNM Server Network Model

DCNM Server builds an intelligent Network data model that enables the server to intelligently serve user requests.

NX-OS Devices Network

DCNM Server

DCNM Server Network Data

Model


Communications

DCNM Server connects to the NX-OS devices over SSH.

DCNM Client communicates to the DCNM server over Java RMI. No direct communication between DCNM Client and the Nexus devices.

DCNM Server notifies DCNM Client of asynchronous events as JMS messages.

NexusDCNM Server

DCNM Client

SSH

Java RMI

JMS


Get RequestsGet requests are served by DCNM Server without having to retrieve

the information from the device(s).

NX-OS Device(s) Network

DCNM Server

Client

DCNM Server Network Data

Model


Set RequestsSet requests make changes to the device configuration. Request is first applied to

the DCNM Server network model to validate request. Validation rules applied are the same as what NX-OS does to validate CLI commands.Request forwarded to device(s) only if validation is successful.

+ Change Request =

Yes

No

Client

DCNM Server

NX-OS Device(s) Network


Feature Selector

FeatureFilter Selection Details

AssociatedFeatures

Selection


Agenda

Introduction

Nexus 7000 Chassis

Nexus 7000 Modules


NX-OS Overview



Q & A


DC CoreUnified Fabric Evolution (2007)

CBS 3100 Blade

Catalyst 49xxRack

Catalyst 6500End-of-Row

Catalyst 49xxRack

CBS 3100MDS 9124eBlade

1GbE Server Access 1GbE and 4Gb FC Server Access

DC Access

Catalyst 650010GbE Core

Catalyst 650010GbE VSS AggDC Services


MDS 9500Storage

SAN A/BDC Aggregation


Storage

IP+MPLS WAN Agg Router

WAN

MDS 9500Storage Core

Gigabit Ethernet

10 Gigabit Ethernet

10 Gigabit DCE

4Gb Fibre Channel


DC CoreUnified Fabric Evolution (H1 2008)

CBS 3100 Blade

Catalyst 49xxRack


Catalyst 49xxRack


10GbE and 4Gb FC Server Access

DC Access

Catalyst 650010GbE Core



MDS 9500Storage

SAN A/BDC Aggregation


Storage1GbE Server Access


WAN


Nexus 700010GbE Core

Nexus 700010GbE AggCatalyst 6500DC Services

Nexus 7000End-of-Row

Gigabit Ethernet

10 Gigabit Ethernet

10 Gigabit DCE

4Gb Fibre ChannelIntroduce Nexus 7000 In the Core

Introduce Nexus 7000 For 10GbE Server Access

Introduce Nexus 7000 in the Aggregation Layerwith Catalyst 6500 for DC Services


DC Core

CBS 3100 Blade

Catalyst 49xxRack


Gigabit Ethernet

10 Gigabit Ethernet

10 Gigabit DCE

4Gb Fibre Channel

Nexus 5000Rack

DC Access


MDS 9500Storage


Storage


WAN

10GbE and 4Gb FC Server Access


Catalyst 49xxRack

10GbE and 4Gb FC Server Access10Gb FCoE Server Access

10 Gigabit FCoE/DCE

SAN A/BMDS 9500Storage Core

1GbE Server Access


Unified Fabric Evolution (H2 2008)


DC Aggregation

Introduce Nexus 5000 For Rack Server Accessand Server I/O Consolidation with FCoE


DC Core

CBS 3100 Blade

Catalyst 49xxRack


Nexus 5000Rack

10Gb DCE Server Access

DC Access

MDS 9500Storage


Storage


WAN


Gigabit Ethernet

10 Gigabit Ethernet

10 Gigabit DCE

4Gb Fibre Channel

Nexus 3000BladeCBS 3100MDS 9124eBlade

10 Gigabit FCoE/DCE



Unified Fabric Evolution (Summer 2009)


DC AggregationSAN A/B

1GbE Server Access

Introduce Nexus 3000 and Nexus 7000 DCE I/O Moduleand Interconnect Access Layers to MDS with FCoE



DC CoreUnified Fabric Evolution (2H 2009)

CBS 3100 Blade

Catalyst 49xxRack

Nexus 5000Rack

Nexus 3000Blade

10Gb DCE Server Access

DC Access

MDS 9500Storage


Storage


WANGigabit Ethernet

10 Gigabit Ethernet

10 Gigabit DCE

4Gb Fibre Channel

10 Gigabit FCoE/DCE


SAN A/B




1GbE Server Access

DC Aggregation

Introduce Nexus 7000 DCE I/O Modules in Aggregation Layerfor Network-Wide Unified Fabric


Q and A


Please, complete the evaluation form for this session.

Thank You !!!

presentacion intro nexus 7000

Documents

cisco systems

cisco confidentialcisco

network downtime

generation data center

modules nexus

chassis nexus

agenda introduction

transport technologies