nk them out and put them in another VDC. This is the equivalent of pulling half of the blade out of the virtual device NX-7K-2 and putting it into the virtual device Annie. It won't harm the switch, but anything connected to those ports will go offline. Chapter 18: Cisco Nexus Next, I'll allocate all 32 ports of the 10 GB blade: NX-7K-2(config-vdc)# allocate interface Ethernet8/1-32 Moving ports will cause all config associated to them in source vdc to be removed. Are you sure you want to move the ports (y/n)? [yes] y A quick sanity check shows that we have two VDCs now-the original system context and Annie. We can show the VDCs configured with the show vdc command: NX-7K-2 (config-vdc)# sho vdc vdc id vdc name state NX-7K-2 active 00:26:98:1b:fo:41 Annie active 00:26:98:1b:fo:42 Now let's create the Guinness VDC, this time with an ID of 3: NX-7K-2 (config-vdc)# vdc Guinness id 3 Note: Creating VDC, one moment please 2010 May 27 00:08:41 NX-7K-2 %$ VDC-1 %$ %VDC MGR-2-VDC_ONLINE vdc 3 has come online Now I'll allocate interfaces. This VDC only gets the other half of the 48-port blade. There are no 10 Gbps ports in this VDC: NX-7K-2(config-vdc)# allocate interface Ethernet3/25-48 Moving ports will cause all config associated to them in source vdc to be removed. Are you sure you want to move the ports (y/n)? [yes] And the preliminary configuration of our VDCs is done. Show VDC gives us a list of what's configured: NX-7K-2 (config-vdc)# sho vdc vdc id vdc_name state NX-7K-2 active 00:26:98:1b:f0:41 Annie active 00:26:98:1b:f0:42 Guinness active 00:26:98:1b:f0:43 To see a detailed report of which ports have been allocated to which VDCs, I can use the show vdc membership command. Really, though, I like to just do a show run vdc and see the commands applied to the VDCs. All of the limit-resource commands shown are defaults; their use is outside the scope of this already large book: NX-7K-2 (config)# sho run vdc !Command: show running-config vdc !Time: Thu May 27 00:54:11 2010 version 4.2(4) vdc NX-7K-2 id 1 limit-resou