2. Nexus is a modular network switch
introduced on January 28, 2008
Designed for the data center (optimized for
high-density 10 Gigabit Ethernet.)
Its throughput is beyond 15 Tbps.
It has a modular NX-OS firmware/operating
system
3. The Nexus switches family range:
- Nexus 1000v virtual switch
- Nexus 2000 fabric extender
- Nexus 3000 series
- Nexus 4000 IBM Blade Center switch
- Nexus 5000 series
- Nexus 7000 series modular datacenter switches
4. Usability focused for demanding
operational environments
Delivers a unified fabric and I/O
15+ Tb/s scalable switching capacity
5. The Cisco Nexus 7000 Series was designed
around three principles:
1- Infrastructure scalability:
Virtualization, efficient power and cooling, high
density, and performance all support efficient
data center infrastructure growth.
2-Operational continuity: The Cisco Nexus
design integrates hardware, NX-OS software
features, and management to support zero-
downtime environments.
6. 3-Transport flexibility: You can incrementally
and cost-effectively adopt new networking
innovations and technologies, such as:
Cisco Overlay Transport Virtualization (OTV)
Cisco FabricPath
Fibrer Channel over Ethernet (FCoE)
Cisco IOS Multiprotocol Label Switching
(MPLS)
7. Nexus VS 65XX :
- Virtual port channel (VPC) : VPC is similar
to VSS of the 65K's.
- Virtual device context (VDC) :
With VDC you virtually divide your switch
up to 4 different virtual switches and
allocate hardware resources to them
- 65K's can perform all the functions... Nexus
still doesn't support service modules like
FWSM, load balancers etc...
8. Cisco Overlay Transport Virtualization (OTV):
- It makes multiple DC as one Dc.
- The NX7k switch has MAC add table for each NX7k
switch
- The MAC add tables are automatically shared
- It stops spanning tree protocol
- In multicast : Just one copy sent to the core
Cisco FabricPath :
- Combines the simplicity of L2 domain with
scalability of L3 domain , Creates (L2 routing tables)
- No blocking , send through all links, down link will
be excluded.
- Shortest path will be used
- Add fabricpath Switch destination header
- Add server any where in the dc
9. Fiber Channel over Ethernet (FCoE) :
- Allow the server to connect to the San and
the LAN through one link
Hitless software upgrade by :
- In Service Software Upgrade (ISSU)
Cisco Data Center Network Manager:
- Management tool
10. Nexus 7000 Hw specifications :
- Delivers high-density 10, 40, and 100 Gigabit
Ethernet
- provide parallel fabric channels to each I/O and
supervisor module slot
- Up to five simultaneously active fabric modules
work together delivering up to 230 Gbps per slot
46 Gbps per slot per fabric ( 46*5 fabric = 230 Gbps per
slot )
- 46 is for fabric 1 , in fabric 2 its 110 per slot
- With 550G per slot, scales to more than 17 Tbps
switching capacity
11. New Nexus 7000 Supervisor Engines :
- Cisco Nexus 7000 Series Supervisor 2 and 2E
Modules deliver increased control plane
performance and system scalability
- Cisco Nexus 7000 Series Supervisor 2 has
twice the CPU performance of the Supervisor
1 Module
- Cisco Nexus 7000 Series Supervisor 2E
performance is Four times the CPU
performance of the Supervisor 1 Module
12. Simpler More Stable Layer 2 Network
Highly Available Platform
Preserves operational best practices
FCoE based Unified Fabric
Virtualization Optimized Networking
Support for GE, FCoE, DCE, and FC
Reduces power, cooling, cabling
Up to 52 non-blocking 10GbE
Up to 1.2 Tbps capacity
Infrastructure
Scalability
Transport
Flexibility
Operational
Continuity
15. - NX-OS two images kickstart image and system
image.
- Not all the features are enabled by default... for
example if you want to use OSPF... you firstly
have to enable the feature. ... (feature ospf)
- All the features are licensed... This is not very
bad... considering that an enterprise licenses gets
almost all of your features running.
16. You don't have to prefix "do" in front of your
"privilege level show commands" if you are in
configuration mode
The routing protocol configuration is more on
the interface level like in IPV6... ipv6 enable
NX-OS CANNOT NAT"; no NAT command on
NX-OS... unusual as it is one of the common L3
feature on any cisco device.
No F and GE in the commands … all are
Ethernet
There aren't any speed designations in the
interface name.
17. no "write" command you have to use the big old
"copy run start“
The " sh tech-support" gives you never ending
data... its HUGE MB's of data
Supports VTP only in transparent mode
- Doesn't support PAGP supports only LACP
- It doesn't support EIGRP unicast
neighborship...
The "sh run" has a lot of minor components
which makes it easier to look at the
configuration... like "sh run rpm"(route
processor module) : gives you all the route policy
config like route-maps and prefix lists