- Introduction
- Getting Started with Cisco Virtual Topology System
- Managing Local Users and Groups
- Managing Inventory
- Managing Resources
- Creating and Managing Admin Domains
- Managing Templates
- Managing Tenants
- Provisioning Overlay Networks
- Viewing Overlay Details
- Administering Cisco VTS
- Service Extension Templates-Supported Configuration
- Supported Underlay Configuration
- OpenStack Configuration for SR-IOV Support
Managing
Resources
Cisco VTS enables you to define global and device local resource pools so that the resources can be allocated when VMs or tenants are added.
You can define the multicast addresses that can be allocated sequentially for VXLAN tunnel creation so that you do not have to manage them separately. VNI and multicast pools are global.
You can define the multicast addresses as global resource pool. These multicast addresses will be allocated sequentially when new VXLAN tunnels are created. Network administrator can define multiple multicast address ranges.
VLAN range can be assigned or each device. You can also group devices and assign VLAN range to the device group.
Additionally, for Nexus 7000 devices, you can assign VLAN resources at physical or FEX interface level. You can also group the interfaces from different devices and assign VLAN ranges to the interface group.
![]() Note | Default resource pools are device-specific VLAN pools that are also created automatically when leafs are added to the inventory. The default VLAN range is from 1001 to 2000. You can modify the range as per your requirement. |
You can edit the range and also delete any unused ranges.
This chapter has the following sections:
- Specifying Global VNI Range
- Specifying VLAN Range
- Specifying Multicast IP Pool
- Specifying Interface VLAN Range
- Creating Interface Groups
Specifying Global VNI Range
You can specify the global VNI range. To do this:
Specifying VLAN Range
VLAN ranges needs to be created for all the leafs and DCIs. You can create device specific VLAN range. You can also group devices together, and create a VLAN range for the group.
For Cisco Nexus 7000 devices, you can specify VLAN range per interface. You can also group interfaces together and specify ranges.
When you add Nexus 7000 devices to inventory, Cisco VTS checks whether these devices are in vPC and the compute links attached to these vPC devices are dual homed. If the devices are in vPC, VTC automatically creates a device group containing these two devices. This device group would have BD range associated with it, which VTS uses to provision overly networks. The default BD range is 1000 to 2000. you can configure this value.
-
For computes attached to Cisco Nexus 7000 switch as single homed, Cisco VTS automatically creates a default device interface pool per interface attached to the compute. This default interface pool is of name vts-Device-InterfaceName with a default VLAN range of 2-4094.
-
If a compute attached to the Cisco Nexus 7000 is dual homed, Cisco VTS automatically creates a default device interface group pool containing the dual homed interfaces of two switches. This default interface group pool is of name vts-group-<number> with a default VLAN range of 0-4096.
-
For single homed and non vPC interfaces, Cisco VTS creates a default per interface level VLAN range of 0-4096.
-
If computes are attached to FEX, the interface pool with default range is created for the FEX device. This FEX VLAN pool is of name vts-device-<fexId> with default range of 0-4096.
-
For computes attached in vPC to two different FEX, Cisco VTS automatically creates a group for the two interfaces going to two different FEXs. Overlay network provisioning on this vPC compute uses a common VLAN from the two FEXs ranges.
Cisco VTS only allows grouping of two FEXs to form a logical group. It does not allow a FEX from one logical group to form a grouping with a FEX from a different logical group. For example, if a host compute1 is connected in vPC to two FEXs 101 and 102, these two FEXs will form a logical group. Cisco VTS does not allow having a host compute2 connected in vPC to FEX 102 and FEX 103. This is because the same VLAN across multiple FEXs for a given network would be difficult to maintain.
- The default VLAN pool of a device gets deleted when the device is added to a Device Group. This is because it will be using the default VLAN pool of the Device Group once it is part of the group. However, when the device is removed from the Device Group, Cisco VTS does not add back the original VLAN pool to it. The Cisco VTS admin has to add the VLAN pool back to the device, manually.
![]() Note | We recommend that you check the supported VLAN range for the device that is created automatically, and also take a note of the reserved VLAN range. Every device has its own limitation. You need to ensure that you are not using a reserved VLAN range for your particular device. |
See the following sections for details:
Specifying Device VLAN Range
To specify device VLAN pool:
Specifying Group VLAN Range
You can group devices and assign VLAN range for the device group. To specify VLAN range for a device group:
Specifying Multicast IP Pool
You can specify the number of overlay networks that can be mapped to a single multicast address. Choose Enter VNI(NetworkCount) from the drop down, and enter the number of networks you want to map to a single multicast address. You can also opt to have all networks to map to a single multicast IP. To do this choose All Network from the drop down.
You can specify the IP range. The range must be within the multicast IP address range configured on leaf devices via day zero configuration file. The valid range is from 239.0.0.0 to 239.255.255.255.
Specifying Interface VLAN Range
To specify VLAN range for an interface:
Creating Interface Groups
You can group interfaces and assign VLAN ranges for the group. You can create groups for physical interfaces or FEX interfaces and assign ranges.
![]() Note | You cannot group physical and FEX interfaces together. |
Important Note
For versions earlier than 2.3.1, Cisco VTS restricted the use of static allocation to within a range, for all resources, and all attempts to allocate outside the range returned an exception. Currently, by default, ranges are not required for static allocation. A static allocation may be done both inside a range and outside it.
If you wish to enable the restriction, this can be done using REST API. See the Cisco VTS 2.5 Developer Guide for details

Feedback