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.
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. 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 1-1 lists the default template resource limits of the nondefault VDC.
Note You cannot change the limits in the default VDC resource template.
|
|
|
---|---|---|
IPv4 multicast route memory1 |
||
|
Any changes that you make to a VDC resource template do not affect any VDCs that 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 1, “Managing VDCs”).
Table 1-2 lists the default template resource limits of the global default VDC.
|
|
|
---|---|---|
IPv4 multicast route memory2 |
||
|
Note Only the network administrator can change a VDC template in the default VDC.
Table 1-3 lists the licensing requirements for this feature:
Table 1-3 Licensing Requirements for VDC Templates
VDC templates have the following configuration guidelines and limitations:
VDC resource templates describe the minimum and maximum resources that the VDC can use. If you do not specify a VDC resource template when you create a VDC, the Cisco NX-OS software uses the default template, vdc-default.
Note As an alternative to using VDC resource templates, you can change the individual resource limits after you create the VDC by changing an individual resource limit for a single VDC or by changing the resource limits in a nondefault VDC resource template and applying the template to the VDC. For information about managing VDC resource limits after you create a VDC, see Chapter1, “Managing VDCs”
Note You can have a maximum of two SPAN monitoring sessions on your physical device.
You can change the individual resource limits after you create the VDC as follows:
For information about managing VDC resource limits after you create a VDC, see Chapter1, “Managing VDCs”
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 that you can use when creating VDCs that have resource limits other than those provided in the default VDC resource template. For information about the maximum number of VDC resource templates that you can create, see Appendix 1, “VDC Configuration Limits.”
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 1-1).
Note You can set only one value for the multicast and unicast route memory resources maximum and minimum limits. If you specify a minimum limit, that is the value for both the minimum and maximum limits and the maximum limit is ignored. If you specify only a maximum limit, that is the value for both the minimum and maximum limits.
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 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 .
This example shows how to configure a VDC resource template:
For additional information related to implementing VDCs, see the following section:
|
|
---|---|
Cisco Nexus 7000 Series NX-OS Virtual Device Context Command Reference |
Table 1-4 lists the release history for this feature.
|
|
|
---|---|---|