Virtual Device ContextsVDCs used to virtualize physical hardware of Nexus 7000(As

SDRs in IOS XR or Contexts in ASA)

VDCs also virtualize control plane protocols of Nexus 7000

Separate control plane per VDC

OSPF 1 in VDC 1 is not OSPF 1 in VDC 2

Multiple logical roles per physical chassis

E.g. Core, Aggregation/Distribution & access on same box

Multi-Tenancy

Some features can’t co-exist in same VDC

OTV and VLAN interfaces (SVIs)

F2 cards and M1/F1

No Of VDCs 4 VDCs per chassis with SUP 1

4+1 VDCs per chassis with SUP 2

8+1 VDCs per chassis with SUP 2E*

No internal cross VDC communication

Physical cable can be used to connect VDCs

Default VDCDefault VDC “1” always exists and cannot be removed

& used to create and manage other VDCs

Controls VDC port allocations & VDC resource allocations

Number of VLANs, VRFs, Routing table memory

All ports allocated to default VDC at initialization

The VDCs that are used by the Cisco Nexus 7000 Series switches separate data plane, control plane, and management plane functions.

Default VDC tasksSome tasks can only be performed in the default VDC

• VDC creation/deletion/suspend

• Resource allocation – interfaces, memory

• NX-OS Upgrade across all VDCs

• ISSU Upgrade

• Feature-set installation for Nexus 2000

• Fabric Path and FCoE

• Port Channel load balancing

• ACL Capture feature enable

• System-Wide QoS

Admin VDC Supported on supervisor module Sup2/2E and the new

Cisco NX-OS version 6.1

Licenses are installed and activated in the Admin VDC

Creation and deleting of VDC is done in Admin VDC

Cannot perform any traffic forwarding

Layer 2 and Layer 3 functionality is disabled

Interface Group

Resource Limit

Template

Question ???