The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
This chapter describes how to configure an admin virtual device context (VDC) on Cisco NX-OS devices.
Your software release might not support all the features documented in this module. For the latest caveats and feature information, see the Bug Search Tool at https://tools.cisco.com/bugsearch/ and the release notes for your software release. To find information about the features documented in this module, and to see a list of the releases in which each feature is supported, see the "New and Changed Information"chapter or the Feature History table in this chapter.
Beginning with Cisco NX-OS Release 6.1 you can enable an admin VDC at the initial system bootup through a setup script. It is an optional step and the creation of an admin VDC is not required. An admin VDC is used for administrative functions only.
Beginning with Cisco NX-OS Release 6.2(2), the Supervisor 1 module supports an admin VDC with the same functionalities as Supervisor 2/2e modules. You can enable a default VDC or an admin VDC on the Supervisor 1 module. For the supported number of VDCs on Supervisor 1 and 2/2e modules, see the Cisco Nexus 7000 Verified Scalability Guide.
Beginning with Cisco NX-OS Release 6.2(2), all functionalities regarding the Supervisor 2e module on the Cisco Nexus 7000 Series switch is applicable to the Supervisor 2e module on the Cisco Nexus 7700 switch.
For more information on Supervisor modules and the Cisco Nexus 7700 switches, see the Cisco Nexus 7000 Series Hardware Installation and Reference Guide.
Admin VDCs are supported on Supervisor 1 and Supervisor 2/2e modules. When an admin VDC is enabled, only the mgmt0 port is allocated to the admin VDC.
Note | The Advanced Services Package License and/or the VDC License are not required to enable the admin VDC. |
You can create an admin VDC in one of the following ways:
After a fresh switch bootup, a prompt is displayed to select the admin VDC. Choose Yes at the prompt to create an admin VDC. This option is recommended for brand new deployments. It is not recommended to use this option when migrating from Supervisor 1 to Supervisor 2/2e. For more information on the Supervisor 1 to Supervisor 2/2e migration procedure, see the following document: http://www.cisco.com/en/US/docs/switches/datacenter/hw/nexus7000/installation/guide/n7k_replacing.html#wp1051017
Enter the system admin-vdc command after bootup. The default VDC becomes the admin VDC. All the nonglobal configuration in the default VDC is lost after you enter this command. This option is recommended for existing deployments where the default VDC is used only for administration and does not pass any traffic.
You can change the default VDC to the admin VDC with the system admin-vdc migrate new vdc name command. After entering this command, the nonglobal configuration on a default VDC is migrated to the new migrated VDC. This option is recommended for existing deployments where the default VDC is used for production traffic whose downtime must be minimized.
Note | If the default VDC has Fabric Extenders that are enabled and configured, the migration of the default VDC configuration can take several minutes. |
Admin VDCs have the following configuration guidelines and limitations:
No features or feature sets can be enabled in an admin VDC.
No interfaces from any line card module can be allocated to an admin VDC. Only mgmt0 can be allocated to an admin VDC which means that for an admin VDC, only out-of-band management is possible through the mgmt0 interface and console port.
When an admin VDC is enabled at bootup, it replaces the default VDC.
Once an admin VDC is created, it cannot be deleted and it cannot be changed back to the default VDC. To change it back to the default VDC, erase the configuration and perform a fresh bootup.
For the supported number of VDCs on Supervisor 1 and Supervisor 2/2e modules, see the Cisco Nexus 7000 Verified Scalability Guide.
The guidelines and limitations for migrating to an admin VDC with system admin-vdc and system admin-VDC migrate commands are as follows:
During the admin VDC migration, some feature configurations, such as access control lists (ACLs), are copied into the new VDC but they are not removed from the admin VDC. You have to explicitly remove any unwanted configurations in the admin VDC. While it is recommended to remove this configuration, keeping it does not cause any side effect.
The guidelines and limitations for migrating to an admin VDC with the system admin-vdc migrate command only are as follows:
If you enable the VTP in the default VDC when you enter the system admin-vdc migrate command, the VTP configuration is not automatically migrated. After the migration is complete, you must reconfigure the VTP feature in the new VDC.
If the time zone is configured in the default VDC when you enter the system admin-vdc migrate command, the time zone configuration is not automatically migrated. After the migration is complete, you must reconfigure the timezone in the new VDC.
As the management IP address in the default VDC is not migrated to the new VDC, some existing sessions are not automatically up in the new VDC. You have to configure a new IP address for the management interface in the VDC. Also, any external devices, for example, VPC keepalives over the management interface on the VPC peer or SNMP management stations should be reconfigured.
During the migration, if the Cisco Nexus 7000 Series switches have enough system resources to spare, the resource limits of the default VDC are copied into the migrated VDC or the migration fails with an error message.
If the default VDC has Fabric Extenders that are enabled and configured, the migration of the default VDC configuration can take several minutes.
Enter the password for "admin": Confirm the password for "admin": Do you want to enable admin vdc (yes/no) [n]:yesThis example shows the show vdc output before the admin VDC is created:
switch(config)# sh vdc vdc_id vdc_name state mac type lc ------ -------- ----- ---------- --------- ------ 1 switch active 00:26:98:0d:01:41 Ethernet m1 f1 m1xl m2xl 2 vdc2 active 00:26:98:0d:01:42 Ethernet m1 f1 m1xl m2xl 3 vdc3 active 00:26:98:0d:01:43 Ethernet f2This example shows the output of the system admin-vdc command after a bootup:
switch(config)# system admin-vdc All non-global configuration from the default vdc will be removed, Are you sure you want to continue? (yes/no) [no] yesThis example shows the show vdc output after executing the system admin-vdc command:
switch(config)# show vdc vdc_idvdc_name state mac type lc ------ -------- ----- ---------- --------- ------ 1 switch active 00:26:98:0d:01:41 AdminNone 2 vdc2 active00:26:98:0d:01:42 Ethernet m1 f1 m1xl m2xl 3 vdc3 active 00:26:98:0d:01:43 Ethernetf2This example shows the output of the system admin-vdc migrate new vdc name command to migrate the default VDC to the admin VDC:
switch(config)# system admin-vdc migrate new-vdc All non-global configuration from the default vdc will be removed, Are you sure you want to continue? (yes/no) [no] yes Note: Interface mgmt0 will not have its ip address migrated to the new vdc Note: During migration some configuration may not be migrated. Example: VTP will need to be reconfigured in the new vdc if it was enabled. Please refer to configuration guide for details. Please wait, this may take a while Note: Ctrl-C has been temporarily disabled for the duration of this command 2012 Jul 5 22:20:58 switch %$ VDC-1 %$ %VDC_MGR-2-VDC_ONLINE: vdc 4 has come online switch(config)#This example shows the show vdc output after the admin VDC is created:
switch(config)# show vdc vdc_idvdc_name state mac type lc ------ -------- ----- ---------- --------- ------ 1 switch active 00:26:98:0d:01:41 AdminNone 2 vdc2 active 00:26:98:0d:01:42 Ethernet m1 f1 m1xl m2xl 3 vdc3 active 00:26:98:0d:01:43 Ethernet f2 4 new-vdc active 00:26:98:0d:01:44 Ethernet m1 f1 m1xl m2xl switch(config)#
Related Topic |
Document Title |
---|---|
Cisco NX-OS licensing |
Cisco Nexus 7000 Series NX-OS Unicast Routing Command Reference |
Supported number of VDCs |
Cisco Nexus 7000 Verified Scalability Guide |
VDC commands |
Cisco Nexus 7000 Series NX-OS Virtual Device Context Command Reference |
This table includes only the updates for those releases that have resulted in additions or changes to the feature.
Feature Name | Release | Feature Information |
---|---|---|
Supervisor 1 module |
6.2(2) |
Added support for admin VDCs on the Supervisor 1 module. |
Admin VDC |
6.1(1) |
This feature was introduced on Supervisor 2 and Supervisor 2e modules. |