Table Of Contents

Troubleshooting VDCs

Information About Troubleshooting VDCs

Initial Troubleshooting Checklist

VDC Issues

You Cannot Create a VDC

You Cannot Log into a Device

You Cannot Switch to a VDC

You Cannot Delete a VDC

You Cannot Allocate an Interface to a VDC

The VDC Does Not Reflect a Resource Template Change

The VDC Remains in a Failed State

You Cannot Copy the Running-Config to the Startup-Config in a VDC

Troubleshooting VDCs

---

This chapter describes how to troubleshoot virtual device contexts (VDCs).

This chapter includes the following sections:

•Information About Troubleshooting VDCs

•Initial Troubleshooting Checklist

•VDC Issues

Information About Troubleshooting VDCs

Cisco NX-OS supports VDCs, which you can use to divide the physical NX-OS device into separate virtual devices. Each VDC appears as a unique device to the connected users. A VDC runs as a separate logical entity within the physical NX-OS device, maintains its own unique set of running software processes, has its own configuration, and can be managed by a separate administrator.

VDC issues may not be directly related to VDC management. See the troubleshooting chapter that reflects your symptoms to find other issues related to VDCs. For instance, if you configure a VDC template that limits the number of port channels in that VDC, you may experience problems if you try to create more port channels than the VDC template allows.

VDC templates set limits on the following features:

•Port channels

•SPAN sessions

•IPv4 route map memory

•VLANs

•Virtual routing and forwarding instances (VRFs)

The minimum resource value configures the guaranteed limit for that feature. The maximum resource value represents oversubscription for the feature and is available on a first-come-first-serve basis.

---

Note When you allocate an interface to a VDC, Cisco NX-OS removes all configuration for that interface.

---

See the Cisco NX-OS Virtual Device Context Configuration Guide, Release 4.0 for more information on VDCs or for details on any VDC configuration changes recommended in this chapter.

Initial Troubleshooting Checklist

Begin troubleshooting VDC issues by checking the following issues first:

Checklist	Checkoff
Verify that you are in logged into the device as network admin if you are creating or modifying VDCs.
Verify that you are in the correct VDC. You must be in the default VDC to configure VDCs.
Verify that you have installed the Advanced Services license to configure VDCs.
Verify that you are not attempting to create more than three VDCs.

Use the following commands to display VDC information:

•show vdc membership

•show vdc resource

VDC Issues

Problems with VDCs usually occur from logging into the incorrect VDC or misallocating resources for a VDC.

This section includes the following topics:

•You Cannot Create a VDC

•You Cannot Log into a Device

•You Cannot Switch to a VDC

•You Cannot Delete a VDC

•You Cannot Allocate an Interface to a VDC

•Table 4-6 shows the port allocation requirements for the Cisco Nexus 7000 Series 32-port 10-Gbps Ethernet module (N7K-M132XP-12).

•The VDC Remains in a Failed State

•You Cannot Copy the Running-Config to the Startup-Config in a VDC

You Cannot Create a VDC

When you experience problems with creating a VDC, you may see one of the following system messages:

Error Message    VDC_MGR-2-VDC_BAD: vdc_mgr: There has been a failure at res_mgr 

Explanation    Not sufficient resources available based on template configuration. If no template is used a default template is applied.

Recommended Action    Verify that you have sufficient resources available to create this VDC by using the show vdc resources [detail] or show vdc resource template CLI commands. Modify the template you are using to create the VDC or create a new template with resource limits that are currently available.

Error Message    VDC_MGR-2-VDC_BAD: vdc_mgr: : There has been a failure at sys_mgr 

Explanation    Services crashed or failed to come up because of insufficient system resources other than what can be reserved using resource templates. These are dynamic resources based on system utilization and may not be available to support a new VDC.

Recommended Action    Use the show system internal sysmgr service running CLI command to determine what caused the failure.

See Table 4-1 for possible causes and solutions.

Symptom    You cannot create a VDC.

Table 4-1 You Cannot Create a VDC

Symptom	Possible Cause	Solution
You cannot create a VDC.	You are not logged in as network-admin.	Log into the device with an account that has network-admin privileges.
	You are not logged into the default VDC.	Use the switchto CLI command to switch to the default VDC to allocate resources.
	There are not enough resources.	Use the show vdc resources [detail] or show vdc resource template CLI commands to determine your available resources. Modify your template or create a VDC with fewer resources by using the limit-resource CLI command in VDC configuration mode.

You Cannot Log into a Device

You may experience issues when logging into a device. See Table 4-2 for possible causes and solutions.

Symptom    You cannot log into a device.

Table 4-2 You Cannot Log Into a Device

Symptom	Possible Cause	Solution
You cannot log into a device.	There is no account information for the VDC.	Log into the device as network-admin and use the switchto CLI command to switch to the VDC and configure the password and network connectivity for this VDC.
	You are using an incorrect VDC username.	Log into the device with the account created for that VDC.

You Cannot Switch to a VDC

You may experience issues when you switch to another VDC. See Table 4-3 for possible causes and solutions.

Symptom    You cannot switch to a VDC.

Table 4-3 You Cannot Switch to a VDC

Symptom	Possible Cause	Solution
You cannot switch to a VDC.	You are not logged in as network-admin or network-operator.	Log into the device with an account that has the correct privileges.

You Cannot Delete a VDC

When you experience problems deleting a VDC, you may see one of the following system messages:

Error Message    VDC_MGR-2-VDC_UNGRACEFUL: vdc_mgr: Ungraceful cleanup request received 
for vdc [dec], restart count for this vdc is [dec] 

Explanation    Vdc_mgr has begun an ungraceful cleanup for a VDC.

Recommended Action    No action is required.

Error Message    VDC_MGR-2-VDC_OFFLINE: vdc [dec] is now offline  

Explanation    Vdc_mgr has finished deleting a VDC.

Recommended Action    No action is required.

See Table 4-4 for possible causes and solutions.

Symptom    You cannot delete a VDC.

Table 4-4 You Cannot Delete a VDC

Symptom	Possible Cause	Solution
You cannot delete a VDC.	You attempted to delete the default VDC.	You cannot delete the default VDC.
	Unknown errors occurred when deleting a VDC.	Use the show tech-support VDC CLI command to gather more information.

You Cannot Allocate an Interface to a VDC

When you experience problems with creating a VDC, you may see the following system message:

Error Message    VDC_MGR-2-VDC_BAD: vdc_mgr: There has been a failure at gim 
(port_affected_list). 

Explanation    Interface allocation failed.

Recommended Action    Use show vdc membership status or show interface brief CLI commands to gather more information.

See Table 4-5 for possible causes and solutions.

Symptom    You cannot allocate an interface to a VDC.

Table 4-5 You Cannot Allocate an Interface to a VDC

Symptom	Possible Cause	Solution
You cannot allocate an interface to a VDC.	You are not logged in as network-admin.	Log into the device with an account that has the correct privileges.
	You are not logged into the correct VDC.	Use the switchto CLI command to switch to the default VDC to allocate resources.
	The interface is part of a dedicated port group.	Use the show interface capabilities CLI commands to determine if the port is dedicated. All ports in a dedicated port group must be in the same VDC.
	The interface is on the Cisco Nexus 7000 Series 32-port 10-Gbps Ethernet module (N7K-M132XP-12).	You must allocate all ports in a port group to the same VDC for this module. See Table 4-6 for port number to port group mapping.
	The VDC allocation failed.	Use the show vdc membership [status] or show interface brief CLI commands to gather more information.

Table 4-6 shows the port allocation requirements for the Cisco Nexus 7000 Series 32-port 10-Gbps Ethernet module (N7K-M132XP-12).

Table 4-6 Port Numbers for Cisco Nexus 7000 Series 32-port 10-Gbps Ethernet module.

Port Group	Port Numbers
1	1, 3, 5, 7
2	2, 4, 6, 8
3	9, 11, 13, 15
4	10, 12, 14, 16
5	17, 19, 21, 23
6	18, 20, 22, 24
7	25, 27, 29, 31
8	26, 28, 30, 32

The VDC Does Not Reflect a Resource Template Change

You may experience issues when updating a resource template. See Table 4-7 for possible causes and solutions.

Symptom    The VDC does not reflect a resource template change.

Table 4-7 The VDC Does Not a Reflect Resource Template Change

Symptom	Possible Cause	Solution
The VDC does not reflect a resource template change.	The template has not been reapplied to VDC after a template change.	Use the show vdc resource template CLI command to verify the template. Use the template CLI command in VDC configuration mode to reapply the template to the VDC. You may have to use the reload CLI command to reboot the device or force a stateful switchover to get the new resource limits.

The VDC Remains in a Failed State

You may experience issues when a VDC fails. You configure switchover and high availability (HA) polices for a VDC when you create the VDC. These policies determine what happens when the VDC fails or when a stateful switchover occurs to the standby supervisor.

See Table 4-8 for possible causes and solutions.

Symptom    VDC remains in failed state.

Table 4-8 Symptom: VDC Remains in Failed State

Symptom	Possible Cause	Solution
The VDC remains in failed state.	The VDC failed and the HA policy was set to bring down for VDCs.	Use the show vdc detail CLI command to verify the HA policy for this VDC. Use the ha-policy CLI command in VDC configuration mode to change the HA policy.
	A supervisor switchover has occurred and the switchover policy was set to bring down for VDCs.	Use the no vdc command to delete the failed VDC. Recreate the VDC with a different switchover policy using the sw-policy keyword.

You Cannot Copy the Running-Config to the Startup-Config in a VDC

You may experience issues trying to save the configuration in a VDC. See Table 4-9 for possible causes and solutions.

Symptom    You cannot copy the running-config file to the startup-config file in a VDC.

Table 4-9 You Cannot copy the Running-Config to the Startup-Config in a VDC

Symptom	Possible Cause	Solution
You cannot copy the running-config file to the startup-config file in a VDC.	The resource allocation was not saved in the default VDC.	You must save the resource allocation from the default VDC before you can save the configuration in a nondefault VDC. Log into the default VDC and use the copy running-config startup-config CLI command to save the resource allocation. Log into the nondefault VDC and save the configuration or use the copy running-config startup-config vdc-all CLI command in the default VDC to save the configuration in all VDCs.