To allocate physical interfaces to VDC from the config terminal mode type the VDC name and then allocate the physical interfaces as shown below by using the command “allocate interface”

N7000-ITKE01#configure t

N7000-ITKE01 (config)#vdc VDC-CORE1

N7000-ITKE01-DC-CORE1 (config-vdc)#allocate interface  Ethernet1/1

N7000-ITKE01-DC-CORE1 (config-vdc)#allocate interface  Ethernet1/2

N7000-ITKE01 -DC-CORE1 (config-vdc)#allocate interface  Ethernet1/3

Now let’s verify the Interface allocation to the VDC by using following command ” show vdc membership”

N7000-ITKE01-DC-CORE1# show vdc membership

vdc_id:2 vdc_name: DC-CORE1 interfaces:
        Ethernet1/1           Ethernet1/2           Ethernet1/3          
        Ethernet1/4           Ethernet1/5           Ethernet1/6          
        Ethernet1/7           Ethernet1/8           Ethernet1/9          
        Ethernet1/10          Ethernet1/11          Ethernet1/12         
        Ethernet1/13          Ethernet1/14          Ethernet1/15         
        Ethernet1/16          Ethernet1/17          Ethernet1/18         
        Ethernet1/19          Ethernet1/20          Ethernet1/21         
        Ethernet1/22          Ethernet1/23          Ethernet1/24         
        Ethernet1/25          Ethernet1/27          Ethernet1/29         
        Ethernet1/31         

N7000-ITKE01-DC-CORE1#

In addition to interfaces other physical resources such as IPv4 router memory, IPv6 router memory, port-channels, SPAN sessions can be allocated to individual VDC.

Configuring Virtual Device Contexts (VDC)   Cisco Nexus 7000 Series switch is as simple as just entering the VDC name, by following below mentioned steps we can create VDC named VDC-Admin

Step 1

Connect to Cisco Nexus 7000 Series switch using a console port.

Step 2

Create a VDC named DC-CORE1

N7000-ITKE01#configure t

N7000-ITKE01 (config)#vdc  DC-CORE1

Step 3

Verify the created VDC by using following commands “Show vdc” and “show vdc VDC-CORE1 detail” as demonstrated below.

N7000-ITKE01# sho vdc

vdc_id  vdc_name                          state               mac            
——  ——–                          —–               ———-     
1       VDC-Admin                         active              00:26:98:07:1c:c1
2       DC-CORE1                          active              00:26:98:07:1c:c2
3       DC-AGG1                           active              00:26:98:07:1c:c3

The show VDC command shows VDC id based on which VDC created first.BY default VDC id is assigned to the default VDC. In this case it is VDC-Admin.

VDC-Admin# sho vdc DC-CORE1 ?
  <CR>       
  >           Redirect it to a file
  >>          Redirect it to a file in append mode
  detail      Show detailed vdc information
  membership  Show vdc interface membership information
  resource    Show resource configuration for VDC
  |           Pipe command output to filter

In upcoming post I will show how to allocate physical interfaces to the newly created VDC.

The Virtual Device Contexts (VDC) is a new feature introduced in Cisco Nexus 7000 NX-OS, so does it happens to be the first Data Center Switch to provide Virtual Device Contexts (VDC) capabilities. The Virtual Device Contexts (VDC) allows a Cisco Nexus 7000 Series switch to be logically segmented into four different virtual switches (device contexts). The logical separation of single Nexus 7000 into multiple logical devices provides the following benefits:

• Administration and management separation
• Change and failure domain isolation from other VDSs
• Address, VLAN, VRP and vPC isolation.

When the Cisco Nexus 7000 Series switch is first booted, all interfaces of all line cards in the modular switch platform are placed in the default VDC (VDC 1).  Up to four VDCs can be created including the default VDC, but an interface can only belong to one VDC.  Interfaces from different line cards can be placed in different VDCs.  Once an interface is placed into a VDC, the interface can no longer be managed in the default VDC context.

The Cisco Nexus 7000 Series switch shares some components between VDC(s), which include the following:

• A single instance of the kernel which support all of the processes and VDCs.
• Supervisor Modules
• Fabric Modules
• Power Supplies
• Fan trays
• System fan trays
• CMP
• CoPP
• Hardware SPAN resources.

When we started planning for this project lot of solutions were presented, starting from Nortel, Juniper and Cisco. We opted for the Cisco recommended solution. In the new solution we are having Cisco Nexus 7010 as our Core Switches.

Since still we are staging our Cisco Nexus 7010 switches, while doing so I figure out there are no more Giga Ethernet or Ten Giga Ethernet interfaces in the Cisco Nexus 7010 Series Switch. All interfaces are known as Ethernet ports.

VDC-Admin-DC-ITKE1(config)# interface ?

  ethernet      Ethernet IEEE 802.3z

  loopback      Loopback interface

  mgmt          Management interface

  port-channel  Port Channel interface

  vlan          Vlan interface

VDC-Admin-DC-ITKE1 (config)# interface ethernet 1/26

VDC-Admin-DC-ITKE1 (config-if)# speed ?

  10     10Mb/s

  100    100Mb/s

  1000   1Gb/s

  10000  10Gb/s

  auto   Auto negotiate speed

VDC-Admin-DC-ITKE1 (config-if)#

 But nothing to worry they will not just support 10Mb/s but even they can support 10 GB/s. This is one of key difference I found between Cisco Catalyst 6500 Series and Nexus 7000 Series Switches. As we proceed further I let you all know the major differences between Cisco Catalyst 6500 Series and Nexus 7000 Series Switches. One fact to known about Nexus 7000 Series Switches run by Cisco NX-OS software. It was specifically designed for the most mission-critical place in the network, the data center.