Cisco BPX 8650, Installation And Configuration Manual

Page: 443 / 606

24-17
Cisco BPX 8600 Series Installation and Configuration
Release 9.3.30, Part Number 78-12907-01 Rev. E0, May 2005
Chapter 24 Configuring BXM Virtual Trunks
Command Overview
APS Redundancy
Virtual trunks support APS redundancy on BXM OC-3 and OC-12 ports. For more information, see
Chapter 25, “Configuring SONET Automatic Protection System.” To configure APS redundancy, use the
following commands:
• addapsln
•
delapsln
• switchapsln
•
cnfapsln
The prior Y-redundancy is not supported by virtual trunks.
Virtual Trunk Commands
Because a virtual trunk is defined within a trunk physical interface, the physical characteristics are
derived form the interface. All the virtual trunks within a port have the same attributes.
If a physical trunk is specified on a physical port that supports multiple virtual trunks, the command is
applied to all virtual trunks on the physical port.
If a virtual trunk is specified for a command that configures information related to the physical port, the
physical port information is configured for all virtual trunks.
cnfrsrc Configures the conids, for example, LCN, and the bandwidth. The conid capacity indicates the
number of connection channels on the trunk port, which are used by the virtual trunk.
The number of connection channels on the trunk port cannot be greater than the total number of
connection channels on the card. The maximum number of channels is additionally limited by the
number of VCI bits in the UNI cell header.
For a virtual trunk, the number is divided by the maximum number of virtual trunks on the port
to determine the default. You configure this value by using the
cnfsrc command on the BPX.
The following are the number of connection IDs that are used for virtual trunks on various cards:
Port Type Maximum Conids Default Value
BXM/UXM 1 to number of channels on the card 256
BNI T3/E3 1 to 1771 256
BNI OC-3 1 to 15867 (3837 max/vtrk) 256
cnftrkparm Configures the trunk parameters. Both BXM and UXM virtual trunks have all the configuration
parameters for queues as physical trunks.
The integrated alarm thresholds for major alarms and the gateway efficiency factor is the same
for all virtual trunks on the port.
Note
BNI virtual trunks are supported by a single queue and do not support configuration of all
the OptiClass queues on a single virtual trunk.
When a physical port attribute change is made, you are notified that all trunks on the port are
affected.
Table 24-4 Commands Used for Primary Configuration (continued)
Name Description