Specifications

10-36
Cisco IGX 8400 Series Provisioning Guide, Release 9.3.3 and Later Releases
OL-1166-04
Chapter 10 Cisco IGX 8400 Series IP Service
IP Service Provisioning
Logical Switch Partitioning and Allocation of Resources
A logical switch is configured by enabling and allocating resources to the partition. This must be done
for each partition in the interface. The same procedure must be followed to define each logical switch.
The following resources are partitioned among the different logical switches:
• LCNs
• Bandwidth
• VPI range
Resources are configured and allocated per interface, but the pool of resources may be managed at a
different level. The bandwidth is limited by the interface rate, which places the limitation at the interface
level. Similarly, the range of VPI is also defined at the interface level.
Configure these parameters on a VSI partition on an interface:
• min lcn: Guaranteed LCNs for the partition on the interface
• max lcn: Total number of LCNs the partition is allowed for setting up connections on the interface
• min bw: Guaranteed bandwidth for the partition on the interface
• max bw: Maximum bandwidth for this partition on the interface
• start vpi: Lower bound of the VPI range reserved for this partition on the interface
• end vpi: Upper bound of the VPI range reserved for this partition on the interface
Configure partitions by using the cnfrsrc command.
Note Switch Software Release 9.3 or later supports up to three partitions.
Table 10-11 shows the three resources that must be configured for a partition designated ifc1
(interface controller 1).
The controller is supplied with a range of LCNs, VPIs, and bandwidth. Examples of available VPI values
for a VPI partition are listed in Table 10-12.
Table 10-11 ifc1 Parameters (Virtual Switch Interface)
ifc1 Parameters Minimum Maximum
lcns min_lcn max_lcn
bw min_bw max_bw
vpi min_vpi max_vpi
Table 10-12 VPI Range for Partitioning
UXM Range
Trunks 1-4095 VPI range (UNI/NNI).
Ports UNI: 1 - 255/NNI: 1 - 4095.
Virtual trunk Only one VPI available per virtual trunk because a virtual trunk is currently
delineated by a specific VPI.