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 virtual device context (VDC) resource templates on Cisco NX-OS devices.
VDC resource templates set the minimum and maximum limits for device resources that the Cisco NX-OS software assigns to a VDC when you create the VDC. You can explicitly specify a VDC resource template, or you can use the default VDC template provided by the Cisco NX-OS software.
This chapter includes the following sections:
VDC resource templates set the minimum and maximum limits for shared physical device resources when you create the VDC. The Cisco NX-OS software reserves the minimum limit for the resource to the VDC. Any resources allocated to the VDC beyond the minimum are based on the maximum limit and availability on the device.
You can explicitly specify a VDC resource template or you can use the default VDC template provided by the Cisco NX-OS software. VDC templates set limits on the following resources:
Note The default IPv4 and IPv6 route memory available for all VDCs on the supervisor is 250 MB. Beginning with Cisco NX-OS Release 5.2(1), the default memory is 300 MB. This amount remains the same with both the 4-GB and the 8-GB supervisor (see Adding Memory to a Cisco Nexus 7000 Series Supervisor for information on 8-GB supervisor modules). You can have approximately 11,000 routes, each with 16 next hops, in 16 MB of route memory. The show routing memory estimate routes number-of-routes next-hops number-of-next-hops command shows the amount of unicast RIB (IPv4 RIB and IPv6 RIB) shared memory needed to support the specified number of routes and next hops.
If you do not set a limit for a resource in a VDC resource template, the default limits for that resource are the same as those in the default VDC resource template. Table 4-1 lists the default VDC resource template limits.
|
|
|
---|---|---|
IPv4 multicast route memory1 |
||
|
Note You cannot change the limits in the default VDC resource template.
Any changes that you make to a VDC resource template do not affect any VDCs you created using that VDC resource template. To update a VDC with the new limits in the VDC resource, you must explicitly reapply the template to the VDC (see Chapter 3, “Managing VDCs”).
Note Only the network administrator can change a VDC template in the default VDC.
The following table shows the licensing requirements for this feature:
The following platform supports this feature. For platform-specific information, including guidelines and limitations, system defaults, and configuration limits, see the corresponding documentation.
|
|
---|---|
The maximum amount of system resources assigned to a VDC is limited by the VDC resource template used when the VDC is created. You can create VDC resource templates to use when creating VDCs to use resource limits other than those provided in the default VDC resource template.
Note If you do not set limits for a resource in a VDC resource template, the default limits are the limits for that resource in the default VDC resource template (see Table 4-1).
Ensure that you have discovered the physical device using a username that has the network-admin role.
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 default VDC with the icon.
Step 4 From the Details pane, click the Resource Templates tab.
Step 5 Right-click in the Details pane and choose Add Template from the drop-down list.
Step 6 At the cursor, enter the new VDC resource template name and press the Enter key.
Step 7 From the menu bar, choose File > Deploy to apply your changes to the device.
You can add a resource limit to a VDC resource template.
Note You cannot change the configuration of the default templates.
Ensure that you have discovered the physical device using a username that has the network-admin role.
Create a VDC resource template (see the “Adding a VDC Resource Template” section).
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 default VDC with the icon.
Step 4 From the Details pane, click the Resource Templates tab.
Step 5 Double-click the VDC resource template.
Step 6 Right-click on the VDC resource template and choose Add Resource Limit from the drop-down list.
Step 7 Choose a VDC resource from the drop-down menu.
Step 8 In the limit cell under Minimum, enter the minimum limit.
Step 9 In the limit cell under Maximum, enter the maximum limit.
Step 10 From the menu bar, choose File > Deploy to apply your changes to the device.
Adding a VDC Resource Template
You can change the values of a resource limit in a VDC resource template.
Note You can have a maximum of two SPAN monitoring sessions on your physical device.
Note You cannot change the configuration of the default resource templates.
Ensure that you have discovered the physical device using a username that has the network-admin role.
Ensure that a VDC resource template has been created in the default VDC (see the “Adding a VDC Resource Template” section).
Ensure that resource limits have been added to the VDC resource template (see the “Adding a Resource Limit to a VDC Resource Template” section).
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 default VDC with the icon.
Step 4 From the Details pane, click the Resource Templates tab.
Step 5 Double-click the VDC resource template.
Step 6 Click the limits to change and enter the new values.
Step 7 From the menu bar, choose File > Deploy to apply your changes to the device.
You can delete a resource limit from a VDC resource template.
Note You cannot change the configuration of the default resource templates.
Ensure that you have discovered the physical device using a username that has the network-admin role.
Ensure that a VDC resource template has been created in the default VDC (see the “Adding a VDC Resource Template” section).
Ensure that resource limits have been added to the VDC resource template (see the “Adding a Resource Limit to a VDC Resource Template” section).
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 default VDC with the icon.
Step 4 From the Details pane, click the Resource Templates tab.
Step 5 Double-click the VDC resource template to display the resource limits.
Step 6 Click the resource limit to delete.
Step 7 In the Details pane, right-click and choose Delete Resource Limit from the drop-down list.
Step 8 From the menu bar, choose File > Deploy to apply your changes to the device.
You can delete a VDC resource template.
Note You cannot delete the default resource templates.
Ensure that you have discovered the physical device using a username that has the network-admin role.
Ensure that a VDC resource template has been created in the default VDC (see the “Adding a VDC Resource Template” section).
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 default VDC with the icon.
Step 4 From the Details pane, click the Resource Templates tab.
Step 5 Click the VDC resource template.
Step 6 In the Details Pane, right-click and choose Delete Template from the drop-down list.
Step 7 From the menu bar, choose File > Deploy to apply your changes to the device.
The maximum amount of system resources assigned to a VDC is limited by the VDC resource template used when the VDC is created. You can create VDC resource templates to use when creating VDCs to use resource limits other than those provided in the default VDC resource template. You can create a maximum of 64 VDC resource templates.
Note If you do not set limits for a resource in a VDC resource template, the default limits are the limits for that resource in the default VDC resource template (see Table 4-1).
Note You can have a maximum of two SPAN monitoring sessions on your physical device.
Note You cannot change the configuration of the default resource templates.
2. vdc resource template vdc-template-name
3. limit-resource m4route-mem [ minimum min-value ] maximum max-value
limit-resource m6route-mem [ minimum min-value ] maximum max-value
limit-resource monitor-session minimum min-value maximum { max-value | equal-to-min }
limit-resource port-channel minimum min-value maximum { max-value | equal-to-min }
limit-resource u4route-mem [ minimum min-value ] maximum max-value
limit-resource u6route-mem [ minimum min-value ] maximum max-value
limit-resource vlan minimum min-value maximum { max-value | equal-to-min }
limit-resource vrf minimum min-value maximum { max-value | equal-to-min }
To display VDC resource template configuration information, perform one of the following tasks:
|
|
---|---|
For detailed information about the fields in the output from this command, see the Cisco Nexus 7000 Series NX-OS Virtual Device Context Command Reference .
The following example shows how to configure a VDC resource template:
This section includes the following topic:
This tab allows you to configure VDC resource templates for the physical device.
|
|
---|---|
Maximum limit. The maximum limit is allocated on a first-come, first-serve basis. |
Table 4-3 lists the default settings for VDC resource template parameters.
|
|
|
---|---|---|
IPv4 route memory resource limit2 |
||
|
For additional information related to implementing VDCs, see the following sections:
|
|
---|---|
Cisco Nexus 7000 Series NX-OS Virtual Device Context Command Reference |
Table 4-4 lists the release history for this feature.
|
|
|
---|---|---|