Cisco DCNM Virtual Device Context Configuration Guide, Release 4.x
Managing VDCs
Downloads: This chapterpdf (PDF - 571.0KB) The complete bookPDF (PDF - 2.16MB) | Feedback

Managing VDCs

Table Of Contents

Managing VDCs

Information About Managing VDCs

Interface Allocation

VDC Resource Limits

HA Policies

Licensing Requirements for Managing VDCs

Prerequisites for Managing VDCs

Guidelines and Limitations for Managing VDCs

Managing VDCs

Allocating Interfaces to a VDC

Changing VDC Resource Limits

Changing the HA Policies

Discovering VDCs

Deleting a VDC

Field Descriptions for VDC Management

Field Description: Virtual Devices: Summary Pane

Field Description: Virtual Devices: virtual device: Details Tab: General Section

Field Description: Virtual Devices: virtual device: Details Tab: Interfaces Section

Field Description: Virtual Devices: virtual device: Details Tab: Resources Section

Additional References for Managing VDCs

Related Documents for Managing VDCs

Feature History for Managing VDCs


Managing VDCs


This chapter describes how to manage virtual device contexts (VDCs) on Cisco Data Center Network Manager (DCNM).

This chapter includes the following sections:

Information About Managing VDCs

Licensing Requirements for Managing VDCs

Prerequisites for Managing VDCs

Guidelines and Limitations for Managing VDCs

Managing VDCs

Field Descriptions for VDC Management

Additional References for Managing VDCs

Feature History for Managing VDCs

Information About Managing VDCs

After you create a VDC, you can change the interface allocation, VDC resource limits, and the single-supervisor and dual-supervisor high availability (HA) policies. You can also save the running configuration of all VDCs on the physical device to the startup configuration.

This section includes the following topics:

Interface Allocation

VDC Resource Limits

HA Policies

Interface Allocation

When you create a VDC, you can allocate I/O interfaces to the VDC. Later, the deployment of your physical device might change and you can reallocate the interfaces as necessary.

The following Cisco Nexus 7000 Series Ethernet modules have four port groups that consist of two, four, eight, or twelve interfaces each, depending on the module:

N7K-M148GS-11L, N7K-M148GT-11, and N7K-M148GS-11—There are no restrictions on the interface allocation between VDCs, but Cisco recommends that interfaces belonging to the same port group be in a single VDC.

N7K-M132XP-12—Interfaces belonging to the same port group must belong to the same VDC. See the example for this module in Figure 4-1.

N7K-M108X2-12L—There are no restrictions on the interface allocation between VDCs.

Figure 4-1 Example Interface Allocation for Port Groups on a Cisco Nexus 7000 Series 10-Gbps Ethernet Module (N7K-M132XP-12)

Table 4-1 shows the port numbering for the port groups.

Table 4-1 Port Numbers for Port Groups on the Cisco Nexus 7000 Series 32-port 10-Gbps Ethernet Module N7K-M132XP-12

Port Group
Port Numbers

Group 1

1, 3, 5, 7

Group 2

2, 4, 6, 8

Group 3

9, 11, 13, 15

Group 4

10, 12, 14, 16

Group 5

17, 19, 21, 23

Group 6

18, 20, 22, 24

Group 7

25, 27, 29, 31

Group 8

26, 28, 30, 32


For more information on port groups on the Cisco Nexus 7000 Series 10-Gbps Ethernet modules, see the Cisco Nexus 7000 Series Hardware Installation and Reference Guide.


Note When you add or delete interfaces, the Cisco NX-OS software removes the configuration and disables the interfaces.


VDC Resource Limits

You can change the resource limits for your VDC individually as your needs change. You can change the following limits for the following resources:

IPv4 multicast route memory

IPv6 multicast route memory

IPv4 unicast route memory

IPv6 unicast route memory

Port channels

Switched Port Analyzer (SPAN) monitor sessions

VLANs

Virtual routing and forwarding instances (VRFs)

HA Policies

The HA policy determines the action that the physical device takes when the VDC encounters an unrecoverable field. You can change the HA policy for the VDC that was specified when you created the VDC.


Note You cannot change the HA policies for the default VDC.


Licensing Requirements for Managing VDCs

The following table shows the licensing requirements for this feature:

Product
License Requirement

Cisco DCNM

Managing nondefault VDCs requires an Advanced Services license. Managing the default VDC requires no license. For a complete explanation of the Cisco DCNM licensing scheme, see the Cisco DCNM Fundamentals Configuration Guide, Release 4.x.

Cisco NX-OS

Managing nondefault VDCs requires an Advanced Services license. Managing the default VDC requires no license. For a complete explanation of the Cisco NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide.

Note The DCNM and NX-OS software allow a grace period of 120 days to use VDCs without an Advanced Services license. If the grace period expires before you obtain a license, all nondefault VDC configuration is removed from the physical device.


Prerequisites for Managing VDCs

VDC management has the following prerequisites:

Ensure that you have discovered the physical device using a username that has the network-admin role.

Guidelines and Limitations for Managing VDCs

VDC management has the following guidelines and limitations:

Only users with the network-admin user role can manage VDCs.

You can only change VDCs from the default VDC.

Managing VDCs

This section includes the following topics:

Allocating Interfaces to a VDC

Changing VDC Resource Limits

Changing the HA Policies

Discovering VDCs

Deleting a VDC

Figure 4-2 shows the Virtual Devices pane.

Figure 4-2 Virtual Devices Pane

Allocating Interfaces to a VDC

You can allocate one or more interfaces to a VDC. When you allocate an interface, you move it from one VDC to another VDC. The interfaces are in the down state after you move them.


Note When you allocate an interface, all configuration on the interface is lost.


BEFORE YOU BEGIN

Ensure that you have discovered the physical device using a username that has the network-admin role.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Virtual Devices.

Step 2 From the Summary pane, double-click the device to display the list of VDCs.

Step 3 Click the VDC to change.

The Details tab appears in the Details pane.

Step 4 From the Details pane, click Interfaces.

Step 5 Right-click in the Interfaces area and choose Add Interface from the pop-up menu.

A new row appears.

Step 6 From the cell under Interface Name in the new row, click the down arrow to display the interfaces dialog box (see Figure 4-3).

Figure 4-3 Interfaces Dialog Box

Step 7 From the dialog box, you can enter the range of interfaces or select specific interfaces to allocate.

Step 8 Click OK.

Step 9 From the menu bar, choose File > Deploy to apply your changes to the device.

Step 10 (Optional) To change the configuration of an interface in the VDC, click the interface, then right-click, and choose Manage in the pop-up menu.


Changing VDC Resource Limits

You can change the limits on the VDC resources. Changes to the limits take effect immediately except for the IPv4 and IPv6 routing table memory limits, which take effect after the next VDC reset, physical device reload, or physical device stateful switchover.


Note You can have a maximum of two SPAN monitoring session on your physical device.


BEFORE YOU BEGIN

Ensure that you have discovered the physical device using a username that has the network-admin role.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Virtual Devices.

Step 2 From the Summary pane, double-click the device to display the list of VDCs.

Step 3 Click the VDC to change.

The Details tab appears in the Details pane.

Step 4 From the Details pane, click Resources.

Step 5 Double-click the limit to change and enter the new value.

Step 6 From the menu bar, choose File > Deploy to apply your changes to the device.


Changing the HA Policies

You can change the HA policies for a VDC. The VDC HA policies are as follows:

Dual supervisor modules:

Bringdown—Puts the VDC in the failed state. To recover from the failed state, you must reload the physical device.

Restart—Restarts the VDC. This process includes shutting down all the interfaces within that VDC and stopping all the virtualized services processes. The Cisco NX-OS software restarts all the virtualized services saved in the startup configuration and brings the interfaces back up with the configuration saved in the startup configuration. Any configuration that you did not save in the startup configuration prior to the restart is lost.

Switchover—Initiates a supervisor module switchover.

Single supervisor modules:

Bringdown—Puts the VDC in the failed state. To recover from the failed state, you must reload the physical device.

Reload—Reloads the supervisor module.


Caution With the reload action, any configuration that you did not save in the startup configuration prior to the reload is lost.

Note The reload action affects all interfaces and all VDCs on the physical device.


Restart—Restarts the VDC. This process includes shutting down all the interfaces within that VDC and stopping all the virtualized services processes. The Cisco NX-OS software restarts all the virtualized services saved in the startup configuration and brings the interfaces back up with the configuration saved in the startup configuration. Any configuration that you did not save in the startup configuration prior to the restart is lost.


Caution With the reload action, any configuration that you did not save in the startup configuration prior to the reload is lost.

Note You cannot change the HA policies for the default VDC.


BEFORE YOU BEGIN

Ensure that you have discovered the physical device using a username that has the network-admin role.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Virtual Devices.

Step 2 From the Summary pane, double-click the device to display the list of VDCs.

Step 3 Click the VDC to change.

The Details tab appears in the Details pane.

Step 4 From the Single Supervisor HA-Policy field, click the down arrow and choose an HA policy from the drop-down list.

Step 5 From the Dual Supervisor HA-Policy field, click the down arrow and choose an HA policy from the drop-down list.

Step 6 From the menu bar, choose File > Deploy to apply your changes to the device.


Discovering VDCs

You can discover a nondefault VDC with user credentials that are different from the default VDC.

BEFORE YOU BEGIN

Ensure that you have set the correct logging severity levels in the VDC using the Cisco NX-OS device command-line interface (CLI) (see the Cisco DCNM Fundamentals Configuration Guide, Release 4.x).

DETAILED STEPS


Step 1 From the Feature Selector pane, choose DCNM Server Administration > Devices and Credentials.

Step 2 From the menu bar, choose Devices and Credentials > New Device.

A new line appears in the Devices list.

Step 3 Click the cell under IP Address in the new line and enter the IP address of the VDC to discover.

Step 4 Double click the cell under User Credentials in the new line and click the down arrow to display the user credentials dialog. Enter the user credentials information and click OK.

Step 5 From the menu bar, choose Devices and Credentials > Discover.


Deleting a VDC

When you delete a VDC, the Cisco NX-OS software removes the configuration for all interfaces allocated to the VDC and returns the interfaces to the default VDC. Deleting a VDC stops all virtualized services and removes any configuration within that VDC.


Note You cannot delete the default VDC (VDC 1).



Caution Deleting a VDC disrupts all traffic on the VDC.

BEFORE YOU BEGIN

Ensure that you have discovered the physical device using a username that has the network-admin role.

DETAILED STEPS


Step 1 From the Feature Selector pane, choose Virtual Devices.

Step 2 From the Summary pane, double-click the device to display the list of VDCs.

Step 3 Click the VDC to delete.

Step 4 From the menu bar, choose Virtual Devices > Delete VDC.

The VDC disappears from the list in the Summary pane.

Step 5 From the menu bar, choose File > Deploy to apply your changes to the device.


Field Descriptions for VDC Management

This section includes the following topics:

Field Description: Virtual Devices: Summary Pane

Field Description: Virtual Devices: virtual device: Details Tab: General Section

Field Description: Virtual Devices: virtual device: Details Tab: Interfaces Section

Field Description: Virtual Devices: virtual device: Details Tab: Resources Section

Field Description: Virtual Devices: Summary Pane

Table 4-2 Field Description: Virtual Devices: Summary Pane

Element
Description

Name

Name of the physical or VDC device.

Status

Status of the VDC.

Single Supervisor HA Policy

Single supervisor HA policy for the virtual device.

MAC Address

MAC address for the virtual device.

Management Interface IP Address Prefix

IP address and prefix for the VDC management interface.

Management Interface Status

Status of the VDC management interface.

SSH

SSH status.


Field Description: Virtual Devices: virtual device: Details Tab: General Section

Table 4-3 Field Description: Virtual Devices: virtual device: Details Tab: General Section 

Element
Description

Switch Name

Name of the physical device.

VDC Name

Name of the virtual device.

Single Supervisor HA Policy

Single supervisor HA policy for the virtual device.

Dual Supervisor HA Policy

Dual supervisor HA policy for the virtual device.

Status

Status of the virtual device.

MAC Address

MAC address for the virtual device.


Field Description: Virtual Devices: virtual device: Details Tab: Interfaces Section

Table 4-4 Field Description: Virtual Devices: virtual device: Details Tab: Interfaces Section 

Element
Description

Interface Name

Name of the Ethernet interfaces allocated to the virtual device.

Mode

Mode for the interface.

Admin Status

Administrative status for the interface.

Operational Status

Operational status for the interface.

Description

Description for the interface.


Field Description: Virtual Devices: virtual device: Details Tab: Resources Section

Table 4-5 Field Description: Virtual Devices: virtual device: Details Tab: Resource Section 

Element
Description

Name

Name of the resource.

Allocation

Minimum

Minimum guarantee limit for a resource.

Maximum

Maximum limit for a resource on an as-available basis.

Current Usage

Used

Amount of a resource currently in use.

Free

Amount of the resource currently not used.

Used Percent

Percent of the total resource for the virtual device.


Additional References for Managing VDCs

For additional information related to managing VDCs, see the following sections:

Related Documents for Managing VDCs

Related Documents for Managing VDCs

Related Topic
Document Title

Cisco DCNM Licensing

Cisco NX-OS Licensing Guide

Cisco NX-OS Licensing

Cisco DCNM Fundamentals Configuration Guide, Release 4.x

Cisco Nexus 7000 Series 32-port 10-Gbps Ethernet module

Cisco Nexus 7000 Series Hardware Installation and Reference Guide

Command reference

Cisco Nexus 7000 Series NX-OS Virtual Device Context Command Reference


Feature History for Managing VDCs

Table 4-6 lists the release history for this feature.

Table 4-6 Feature History for Managing VDC 

Feature Name
Releases
Feature Information

Managing VDCs

4.2(1)

No change from Release 4.1(2).

IPv4 unicast route memory resource

4.1(2)

Changed the default maximum value from 256 to 8.

IPv6 unicast route memory resource

4.1(2)

Changed the default maximum value from 256 to 4.

Multicast route memory resources

4.1(2)

Added IPv4 and IPv6 multicast route memory resources.

Port channel resources

4.1(2)

Changed the default maximum value from 256 to 768.

IPv4 unicast route memory resource

4.0(2)

Changed the default maximum value from 256 to 320.

IPv6 unicast route memory resource

4.0(2)

Changed the default maximum value from 256 to 192.