CiscoDay DataCenter3 0 Nexus UCS (Part1) 08092011

Cisco Nexus 5000 and 2000 Update
Presentation_ID © 2008 Cisco Systems, Inc. All rights reserved. Cisco Confidential 1
Agenda
 Nexus 5500
Nexus 5000 & 5500 Hardware
Architecture
Layer 3
 Nexus 2000 (N2K)
Virtualized Switch
 Nexus Fabric
FCoE
NIV
Nexus 5000 and 2000
Virtualized Data Center Access
Nexus 2000
Fabric Extender
Nexus 5010 48 Fixed Ports 100M/1G Ethernet (1000 BASE-T)
20 Fixed Ports 10G/FCoE/IEEE DCB 32 Fixed ports 1G/10G/FCoE/IEEE DCB Nexus 5020
Line-rate, Non-blocking 10G 4-8 Fixed Port 10G Uplink 40 Fixed Ports 10G/FCoE/IEEE DCB
1 Expansion Module Slot Distributed Virtual Line Card Line-rate, Non-blocking 10G
Redundant Fans & Power Supplies 2 Expansion Module Slots
Redundant Fans & Power Supplies
Ethernet Ethernet + Fibre Channel Fibre Channel 8G Fibre Channel

6 Ports 10G/FCoE/IEEE DCB 4 Ports 10G/FCoE/IEEE DCB 8 Ports 1/2/4G Fibre Channel 6 Ports 2/4/8G Fibre Channel
4 Ports 1/2/4G Fibre Channel
Nexus 5000 and 2000 Architecture
Nexus 5020
Nexus 5010
Expansion Modules
 Nexus 5000 utilizes expansion slots to provide flexibility of
interface types
Additional 10GE DCB/FCoE compliant ports
1/2/4/8G Fibre Channel ports
 Nexus 5020 has two expansion module slots
 Nexus 5010 has one expansion module slot
 Expansion Modules are hot swappable
 Contain no forwarding logic
Expansion
Modules Slots
Nexus 5000 Hardware Overview
Data and Control Plane Elements
SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP SFP Expansion
Module
CPU
Intel LV Xeon
1.66 GHz
Unified Port Unified Port Unified Port

Controller Controller Controller South
Bridge
DRAM
NVRAM
Unified Crossbar ç
PCIe
Flash
Bus
Fabric
Serial
SERDES
Console
Unified Port
Controller
... Unified Port
Controller
NIC NIC
XAUI
Mgmt 0
SFP SFP SFP SFP SFP SFP
Inband Data Path to CPU
Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 7
Nexus 5548P
Nexus 5548
32 Fixed Ports
1 Expansion Module
Expansion Module
Expansion Module Expansion Module
8 Port FC 1/2/4/8 Gig
Unified Ports 16 Ports 1/10 GE
Presentation_ID + 8 Ports 1/10 GE
© 2010 Cisco and/or its affiliates. All rights reserved. Cisco Public 8
Nexus 5548P Rear Panel
32 x Fixed ports 1/10 GE Expansion Module
Nexus 5548UP Rear Panel
32 x Fixed ports 1/10 GE or 1/2/4/8 FC Expansion Module
Nexus 5548P/UP Front Panel
Fabric Out of Band Mgmt
Interconnect 10/100/1000 USB Flash
Console Fan Module Fan Module Power Entry Power Entry
N + N Redundant FANs N + N Power Supplies
Nexus 5548P Expansion Modules
16 ports
1/10 GE
8 ports
1/10 GE
+
8 ports
1/2/4/8 G FC
16 ports
Unified
1/10 GE or 1/2/4/8 G
FC
Nexus 5596UP
Nexus 5596
48 Fixed Ports
3 Expansion Modules
Nexus 5596UP Rear Panel
Expansion Module Expansion Module Expansion Module
48 x Fixed ports 1/10 GE or 1/2/4/8 FC
Nexus 5596UP Front Panel
Fabric Out of Band Mgmt
Interconnect 10/100/1000 Console USB Flash
Power Entry Power Entry Fan Module Fan Module Fan Module Fan Module
N + N Power Supplies N + 1 Redundant FANs

Nexus 5596UP Expansion Modules
16 ports
1/10 GE
8 ports
1/10 GE
+
8 ports
1/2/4/8 G FC
Nexus 5596UP Expansion Modules
16 ports
Unified
1/10 GE or 1/2/4/8 G
FC
L3 module
Nexus 5596 Hardware Diagram
Carmel 1
DDR3 x2
Carmel 2
South Intel
Carmel 6
Carmel cpu Bridge Jasper Forest
10 Gig Sunnyvale
NVRAM Memory
PCIe x8
UPC UPC UPC UPC UPC UPC
Serial Flash
12 Gig
12 Gig
PEX 8525
4 port PCIE
Switch
PCIe x4 PCIe x4 PCIe x4
UPC
Unified Crossbar Fabric
CPU
PCIE PCIE PCIE
Dual Gig Dual Gig Dual Gig
0 1 0 1
1 N/C
12 Gig 12 Gig
Xcon1 Mgmt
UPC UPC UPC UPC UPC UPC
10 Gig Xcon2 Console
Nexus 5500 Series
Universal Port – Flexibility and Reuse
 Unified Port supports multiple
transceiver types
 1G Ethernet Copper/Fibre
 10G Ethernet Copper/Fibre
 10G DCB/FCoE Copper/Fibre
 1/2/4/8G Fibre Channel
 Change the transceiver and
connect evolving end devices,
 Server 1G to 10G NIC migration
 FC to FCoE migration
 FC to NAS migration
 Unified Port supports a Unified
Servers, FCoE FC Attached
Access Layer across the entire attached Storage
Servers
Storage
Fabric
 Flexibility to evolve system end Unified Port – ‘Any’ device in any rack connected to the
points same edge infrastructure
Agenda
 Nexus 5500
Architecture
Layer 3
 Nexus 2000 (N2K)
Virtualized Switch
 Nexus Fabric
FCoE
NIV
Nexus 5500 Series
2nd Generation Nexus 5000 with Layer 3 support
Layer 3 Feature Support (Q1CY11)

Interfaces: Routed, SVI, port-channel Up to 16K IPv4 /32 Host Routing Table
16-way L3 ECMP 8K IPv4 LPM Routing Table
IPv4 Routing: Static, RIPv2, OSPFv2, IPv6 Routing: OSPFv3, RIP-NG, EIGRP*
EIGRP, BGP
Policy-based Routing (PBR)* IGMP v1, v2, v3; PIM
HSRP, VRRP, GLBP* 4K L3 IP Multicast groups
RACL VRF-Lite (IP VPNs)
Unicast RPF (uRPF) Bcast/Mcast suppression
BiDirectional Forward Detection (BFD)* QoS marking, scheduling and policing
* Post FCS(MQC)
Support
Nexus 5500 Series
Nexus 5500 Layer 3 Daughter Card
N5548P Layer 3 Intelligent Layer 3 Highlights

Daughter Card
Carmel Carmel
 UPC: 8-port lookup/port ASIC
8 8
 X-Bar Fabric: 100x100 crossbar fabric ASIC
X-Bar Fabric
8 8
 X-Bar Fabric can scale up to 12 x UPC
8 8 8 8
Carmel Carmel Carmel Carmel Carmel Carmel  L3 Capability (field upgradeable):
Module Slot  5548: 1x daughter-card slot
32 Fixed Ports
 5596: Up to 3x GEM module
 Each daughter-card or GEM supports
N5596P 160Gbps of bidirectional bandwidth
Layer 3 Layer 3
Module Slot  Modules:
Daughter Card Daughter Card
 16x 10G SFP+
Carmel Carmel Carmel Carmel Carmel Carmel
 8x 10G, 8x 1/2/4/8G FC
8 8 8 8 8 8
 L3 Module – 160G (no front-panel ports)
X-Bar Fabric
8 8 8 8 8 8
 16x 10G 10G-BaseT (future)
Carmel Carmel Carmel Carmel Carmel Carmel  4x 40G QSFP (future)
48 Fixed Ports
Nexus 5548 Layer 3 Daughter Card installation
2 Unscrew the IO Module

Pull the IO Module out
Plug and Screw the L3 IO Module

3 Plug and Screw the Fan Modules 1 Unscrew the Fan Modules
Pull the Fan Modules out
IO Module without L3 daughter card
Top view
IO module with integrated L3 daughter card
Top view
L3 expansion module for Nexus 5596
Nexus 5596UP with L3 Module
Expansion Module Expansion Module L3 Module
32 x Fixed ports 1/10 GE or 1/2/4/8 FC
Nexus 5500 Series
Layer 3 – Routed Access
 In most Data Center architectures
the use of Layer 3 in the access
layer is not compatible with
virtualized workloads
 In some environments the scaling
of workloads can allow migration of
the Layer 3 boundary to the access
 Nexus 5500 supports the ability to
extend layer 3 routing to the access
 In smaller environments can be
leveraged to provide routed
services for small Data Center sites
 Fully compatible with Nexus 2000
Virtualized Switch architecture
Servers, FCoE FC Attached
 Co-existence with the evolution of attached Storage Storage
Unified I/O and FCoE
Servers
Scaling the Virtualized Architecture
Scaling the Data Center Fabric
 Scaling of both VM and non VM
based workloads is driving
increased density of compute and
growth of layer 2 fabrics
 Nexus designs currently leveraging vPC
Scaling for up
vPC to increase capacity and to 32 x 10G
increase scale of layer 2 fabrics links = 320
Gbps
 Nexus 5000/5500 when combined
with F1 line cards on Nexus 7000
can support port channels of up to vPC
32 x 10G interfaces = 320 Gbps
between access and aggregation
 Nexus 5500/2000 virtualized access Scaling for up
switch can support MCEC based to 16 x 10G
links
port channels of up to 16 x 10G
links between server and virtualized VM VM VM
access switch #2 #3 #4
Agenda
 Nexus 5500
Architecture
Layer 3
 Nexus 2000 (N2K)
Virtualized Switch
 Nexus Fabric
FCoE
NIV
Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 30
Cisco FEXlink: Virtualized Access Switch
Nexus 2000 Fabric Extender
Nexus 5000
 Nexus 5000/2000 Virtualized Access Parent Switch
Switch provides a number of design
options to address evolving Data Centre
requirements
 Nexus 2000 Fabric Extender operates as
a remote line card in the Virtualized
switch
 Nexus 2000 server ports are ports on the
Nexus 5000
 Centralized management and
configuration of all ports on the Nexus
5000
 Fabric Extender provides for flexibility in
the design of the physical topologies 10GE Fabric Links
Nexus 2000 Fabric
Extender
What is FEX
 The Cisco Nexus 2000 Series

Fabric Extenders behave as
remote I/O modules for a parent
Cisco Nexus 5000 Series Switch.
The Fabric Extender is
essentially an extension of the
parent Cisco Nexus switch fabric,
with the Fabric Extender and the
parent Cisco Nexus switch
together forming a virtual
modular system
Presentation_ID © 2010 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 32
Parent Switch provides the forwarding functionality
 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
Migrating “Supervisor”
Parent Switches Upgrade
Nexus 5500 Parent Switch

Nexus 7000 Parent Switch Nexus 5000 Parent Switch
16 FEX, DCB, Ethernet, FC,
32 FEX, Layer 2 & 3 12 FEX, DCB, Layer 2
FCoE, Layer 2 & Layer 3,
Ethernet Ethernet, FCoE, FC
FabricPath
Upgrade Flexibility
 Virtualized Access Switch provides for additional flexibility for end station
migration
 Addition or replacement of Nexus 2000 upgrades the ‗line cards‘ for the
virtualized switch
“Line Card”
Upgrade
Nexus 5000 Parent Switch Nexus 5500 Parent Switch

DCB, Ethernet, FCoE, FC DCB, Ethernet, FC, FCoE,
Layer 3, FabricPath
Changing 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
Packet Forwarding Overview
Nexus 2000 Nexus 5000 Nexus 2000
1 Ingress Unified Egress

UPC Crossbar UPC
Nexus 2000
NIV ASIC
Fabric Nexus 2000
NIV ASIC
6
2 3 4 5
3. Nexus 5000 UPC 4. If required
performs ingress egress queuing 6. VNTag stripped
1. Frame received on forwarding and and flow control and frame
N2K HIF port queuing
forwarded out on
N2K HIF port
2. Nexus 2000
appends VNTag and 5. Nexus 5000 UPC
forwards frame to appends destination
fabric uplink VNTag and forwards
frame on fabric link
36
Switching Morphology—Is this Really Different?
Ingress Unified Egress

UPC Crossbar UPC
Nexus 2000 Nexus 2000
Fabric
NIV ASIC NIV ASIC
Line Card Internal Packet Header

Ports, Buffers, Distributed X-Bar used across the Fabric
Egress Forwarding Fabric (Constellation Header –
MCAST ASIC
VNTag)
replication
Fabric ASIC
Port ASIC Port ASIC
& DFC &
Buffers Buffers
PFC
67xx - DFC Sup720 67xx - CFC
37
Packet Forwarding Latency
1G Store &
Ingress Unified Egress
Forward
UPC Crossbar UPC
Nexus 2000 Nexus 2000
VNTag ASIC
Cut Through Switching
Fabric in all subsequent stages
VNTag ASIC
10G Cut-Thru
 Nexus 2000 also supports Nexus 5000/2232 Port to Port Latency*

5
Cut -Through switching
Port to Port Latency (usec)

4
 1GE to 10GE on first N2K ingress is
store and forward 3
 All other stages are Cut Through

2
(10GE N2K port operates in end to
end cut through) 1
 Port to Port latency is dependent on a

0
single store and forward operation at most 64 128 256 512 1024 1280 1518 9216
Packet Size (Bytes)
38
Changing the device paradigm
 Virtualized Access Switch changes the Unified
Port
Controll
Unified
Port
Controll
Unified
Port
Controll
er er er
device paradigm
Unified Crossbar
 Distributed forwarding ASIC‘s all located Fabric
on the central parent switch (Nexus Unified

SERD
ES
.. Unified
5000/5500) Port
Controll
er .
Port
Controll
er
1.92 Tbps of forwarding capacity

Over 1 Bpps of forwarding capacity
 Nexus 2000 provides Line Card Diversity
and flexibility
100M/1G Copper
1/10G SFP+
Future support for 10GBaseT
 Increases the architectural flexibility by
providing a more flexible coupling of
components
 Improves TCO for the life of the
Virtualized Access Switch ‗system‘
39
Unified Server Access Architecture
• Nexus 2000 architecture additions in 2HCY10:
• Nexus 2K to Nexus 5548P, N2K to Nexus 7K, Nexus 2K to UCS 6100
for control plane only
• N2K inherits the features from parent switch
Nexus 7000
Nexus 5000 UCS 6100
Unified
Access
Layer
Direct Attach
10GE Nexus
4000 Cisco
Nexus Nexus Nexus
2000 2000 2000 UCS
1 & 10GE 10GE Rack 10GE Blade

1GE Rack 10GE Rack Switch w/ FCoE UCS Compute
Blade Servers Mount Servers
Mount Servers Mount Servers (IBM/Dell) Blade & Rack
w/ Pass-Thru
Nexus 5000 and Nexus 7000 Parent Switch
FEX Capabilities
Nexus 7000* Nexus 5000**
# of 1G Ports 32 x 2248 = 1536 (Q4CY10) 12 x N2K = 576, 16 x N2K = 786 (Q4CY10)

# of 10G Ports 32 x 2232 = 1024 (1HCY11) 12 x N2K = 384, 16 x N2K = 512 (Q4CY10)
Port Speed 100M/1G (10G Q1CY11) 100M/1G/10G
FabricPath Requires F2 (2HCY11) Requires 5500 (1HCY11)
L3 Support SVI (Q4CY10), Routed Ports (CY11) SVI (Q1CY11), Routed Ports (CY11)
NIV Support Future 1HCY11
Unified I/O capable Requires F2 (2HCY11) Yes
Total SPAN sessions 2 Tx/Rx + 14 Tx only 2Tx/Rx, 4 Tx/Rx in Q4CY10 (Nexus 5500)
vPC Support 1HCY11 Yes
Host Port Channels 1HCY11 Yes (2248/2232)
MAC address table 128K 14K (Nexus 5000), 32K (Nexus 5500)
Netflow Yes (1HCY11) No
VDC Yes (All ports in a FEX are in the same VDC) No
PVLAN No Isolated and Community
* 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
Presentation_ID © 2009 Cisco Systems, Inc. All rights reserved. Cisco Confidential
Agenda
 Nexus 5500
Architecture
Layer 3
 Nexus 2000 (N2K)
Virtualized Switch
 Nexus Fabric
FCoE
NIV
Unified Fabric
Fibre Channel over Ethernet (FCoE)
FCoE Benefits
 Mapping of FC Frames over  Fewer Cables
Ethernet Both block I/O & Ethernet
traffic co-exist on same cable
 Enables FC to Run
on a Lossless  Fewer adapters needed
Ethernet Network
 Overall less power
Ethernet  Interoperates with existing
SAN‘s
Fibre Management of SAN‘s
Channel remains constant
Traffic
 No Gateway
Unified Fabric and FCoE FC
 The first phase of the Unified Fabric Fabric A Fabric B

evolution design focused on the fabric
edge
 Unified the LAN Access and the SAN
FCoE
Edge by using FCoE FC
Nexus
 Consolidated Adapters, Cabling and 5000/5500
Switching at the first hop in the fabrics
Nexus 5000 as
FCF or as NPV
 The Unified Edge supports multiple device
LAN and SAN topology options
 Virtualized Data Center LAN designs
 Fibre Channel edge with direct
Nexus 2232
attached initiators and targets 10GE FEX
 Fibre Channel edge-core and edge-

core-edge designs
 Fibre Channel NPV edge designs
Generation 2 CNAs
44
FCoE Multi-Tier Fabric Design
Extending FCoE past the Unified Edge
 Extending FCoE Fibre Channel fabrics LAN Fabric
Fabric A Fabric B
beyond direct attach initiators can be
achieved in two basic ways
FCF
 Extend the Unified Edge
VE
 Add DCB enabled Ethernet switches
Using FCoE
between the VN and VF ports (stretch for ISL
the ‗link‘ between the VN_Port and the between FC
VE
VF_Port) Switches
FCF
 Extend Unified Fabric capabilities into the Switch Mode
SAN Core VF
Extending
FCoE into a
 Leverage FCoE wires between Fibre multi-hop
Channel switches (VE_Ports) Ethernet
‘Access’ Fabric
 What design considerations do we have
when extending FCoE beyond the edge?
VN DCB + FIP
 High Availability Snooping
Bridge
 Oversubscription for SAN and LAN
 Ethernet layer 2 and STP design
45
Enhanced IEEE DCB Service Lanes
 Tuning of the DCB Service Lanes to

support a variety of use cases
 Extended switch to switch no drop
traffic lanes Support for 3 km
no drop switch to
 Support for 3km with Nexus 5000 switch links
Inter Building DCB
and 5500 Service Lanes
 Future SW changes will be able

to support > 3km on Nexus 5500
Support for up to
 Increased number of no drop services 4 No Drop DCB
Service Lanes
lanes (4) for RDMA and other multi- RDMA + FCOE
queue HPC and compute applications
Configs for
Pause Threshold Resume
3000m no-drop Buffer size
(XOFF) Threshold (XON)
class
N5020 143680 bytes 58860 bytes 38400 bytes
N5548 152000 bytes 103360 bytes 83520 bytes
Cisco Confidential - Internal Only 46

FCoE Multi-Tier Fabric Design
Larger Fabric Multi-Hop Topologies
N7K or MDS FCoE
enabled Fabric
 Multi-hop edge/core/edge topology Switches
 Supported by Nexus 5000 &

5500 in Q4CY10
 Core SAN switches supporting VE
VF
VE
FCoE
 N7K with F1 line cards Edge FCF VE
VE
Switch VNP
 MDS with FCoE line cards Mode
 Edge FC switches supporting either

 N5K - FCoE-NPV with FCoE
uplinks to the FCoE enabled
core (VNP to VF)
 N5K or N7K - FC Switch with FC Attached
FCoE ISL uplinks (VE to VE) Storage
 Fully compatible with virtualized Servers, NAS, FC, Servers, NAS, FC,
access switch and will Co-exist with FCoE attached FCoE attached
Storage Storage
FabricPath and/or Layer 3 designs
47
Agenda
 Nexus 5500
Architecture
Layer 3
 Nexus 2000 (N2K)
Virtualized Switch
 Nexus Fabric
FCoE
NIV
48
Network Interface Virtualization
 NIV allows a single physical PCIe
device to be virtualized into
multiple different PCIe devices
 Provides true traffic segregation in
hardware without need for VLANs
or QinQ tags
 Virtual Interfaces can be Ethernet
NICs or Fibre Channel HBAs and
presented as individual PCIe
devices at the host level
VN-Tag  Enforces the value proposition of
& VIC FCoE, but can support iSCSI and
vNIC vNIC vNIC
Protocol NFS services
 Driven to standards through IEEE
802.1Qbh working group
vHBA vHBA
Cisco Confidential - Internal Only 49

Network Interface Virtualization Architecture (NIV)
 The Network Interface
Bridges that support
Virtualization (NIV) Architecture Interface Virtualization (IV)
provides the ability to extend the ports must support VNTag
bridge (switch) interface to LIF LIF and the VIC protocol
downstream devices
NIV uplink ports must
 NIV associates the Logical connect to an NIV
Interface (LIF) to a Virtual capable bridge or an
Interface (VIF) NIV Downlink
NIV downlink ports
may be connected to VIF NIV may be cascaded
an NIV uplink port, extending the port
bridge or NIC extension one
NIV downlink ports are additional level
assigned a virtual identifier
(VIF) that corresponds to a
virtual interface on the
bridge and is used to Hypervisor
forward frames through VIF
NIV’s NIV capable adapters
may extending the
port extension
Note: Not All Designs Supported in the NIV Architecture Are Currently Implemented
50
Nexus 5500 Virtualized Access Switch
Why virtualized adapters?
Nexus 5000
 Any network interface can be virtualized
1 2 3 4 5 6 7 8
(FEX, adapter)
 Enables external switch to forward frames
that ―belong‖ to the same physical port by
1 2 3 4 5
using VNTag
 Under standardization - 802.1Qbh
1
 Why virtualized adapters?

1 2 3
FEX Functionally consolidated I/O

devices (Eth/FC)
Port 0 Port 1 Multiple interfaces for single OS
NIV Capable Adapter server
Interfaces to virtualized servers
vNIC vNIC vNIC vNIC vNIC
1 2 3 4 5
51
Nexus 5500 Virtualized Access Switch
Technologies related to VN-Link
VN-Link ≠ VN-Tag ≠ NIV

Complete virtual Allows external switch Adapter virtualization
machine awareness to identify a remote (creates multiple
& integration with interface logical NICs)
hypervisor
•NIV can be leveraged

•Nexus 1000V
outside of the scope of
VN-Link (SW) •VN-Tag is leveraged for
VN-Link
No use of VN-Tag multiple use cases
•Fixed vEth (competitive
Standard (802.1Q) (802.1Qbh pre-standard)
value against HP Flex
•Cisco VIC + UCS 6100 VN-Link (HW)
NICs + NICs
VN-Link (HW) FEX-Link
consolidation & dynamic
Uses VN-Tag Network Interface
provisioning)
Pre-standard Virtualization
•Dynamic vETH = VN-Link
(802.1Qbh)
in HW
52
Agenda
 Nexus 5500
Architecture
Layer 3
 Nexus 2000 (N2K)
Virtualized Switch
 Nexus Fabric
FCoE
NIV
53
54

CiscoDay DataCenter3 0 Nexus UCS (Part1) 08092011

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

CiscoDay DataCenter3 0 Nexus UCS (Part1) 08092011

Hochgeladen von

Copyright:

Verfügbare Formate

Cisco Nexus 5000 and 2000 Update

Ethernet Ethernet + Fibre Channel Fibre Channel 8G Fibre Channel

Unified Port Unified Port Unified Port

32 x Fixed ports 1/10 GE Expansion Module

32 x Fixed ports 1/10 GE or 1/2/4/8 FC Expansion Module

Console Fan Module Fan Module Power Entry Power Entry

N + N Redundant FANs N + N Power Supplies

Expansion Module Expansion Module Expansion Module

48 x Fixed ports 1/10 GE or 1/2/4/8 FC

N + N Power Supplies N + 1 Redundant FANs

10 Gig Xcon2 Console

Layer 3 Feature Support (Q1CY11)

N5548P Layer 3 Intelligent Layer 3 Highlights

2 Unscrew the IO Module

Plug and Screw the L3 IO Module

Expansion Module Expansion Module L3 Module

32 x Fixed ports 1/10 GE or 1/2/4/8 FC

 The Cisco Nexus 2000 Series

Nexus 5500 Parent Switch

Nexus 5000 Parent Switch Nexus 5500 Parent Switch

Nexus 2000 Nexus 5000 Nexus 2000

1 Ingress Unified Egress

Ingress Unified Egress

Line Card Internal Packet Header

67xx - DFC Sup720 67xx - CFC

 Nexus 2000 also supports Nexus 5000/2232 Port to Port Latency*

Port to Port Latency (usec)

 All other stages are Cut Through

 Port to Port latency is dependent on a

on the central parent switch (Nexus Unified

1.92 Tbps of forwarding capacity

1 & 10GE 10GE Rack 10GE Blade

# of 1G Ports 32 x 2248 = 1536 (Q4CY10) 12 x N2K = 576, 16 x N2K = 786 (Q4CY10)

 The first phase of the Unified Fabric Fabric A Fabric B

 Fibre Channel edge-core and edge-

 Tuning of the DCB Service Lanes to

 Future SW changes will be able

N5020 143680 bytes 58860 bytes 38400 bytes

N5548 152000 bytes 103360 bytes 83520 bytes

Cisco Confidential - Internal Only 46

 Supported by Nexus 5000 &

 Edge FC switches supporting either

Cisco Confidential - Internal Only 49

 Why virtualized adapters?

FEX Functionally consolidated I/O

VN-Link ≠ VN-Tag ≠ NIV

•NIV can be leveraged

Das könnte Ihnen auch gefallen