Cisco Systems BPX 8600 Series Switch User Manual


 
22-15
Cisco BPX 8600 Series Installation and Configuration
Release 9.3.10, Part Number 78-11603-01 Rev. D0, July 2001
Chapter 22 Configuring Frame Relay to ATM Network and Service Interworking
Connection Management
Full VPI/VCI addressing range
The entire range of VPI and VCI on both UNI and NNI interfaces is supported. For ATM-UNI,
8 bits of VPI and 16 bits of VCI are supported. For ATM-NNI, 12 bits of VPI and 16 bits of VCI
are supported. In either case, VPC connections only pass through the lower 12 bits of the VCI field.
Connection Classes
ATM and interworking connection classes are defined with appropriate bandwidth parameter
defaults. These classes only apply at addcon time. They are templates to ease the task of
configuring the large number of bandwidth parameters that exist per connection.
Commands
These commands are associated with virtual circuit feature changes:
addcon
addcongrp
cnfcon
cnfatmcls
delcon
delcongrp
dspatmcls
dspcongrps
grpcon
Connection Management
Interworking connections may be added from either the BPX switch, the IGX switch, the MGX 8800,
or the MGX 8220. Intra- and inter-domain interworking connections are supported.
Connection configuration parameters are endpoint-specific. Thus, the ATM-only parameters are only
configurable on the BPX switch end. The IGX switch does not know about these parameters, so they
cannot be configured or displayed at the IGX switch end. Parameter units are endpoint-specific also.
Units on the BPX switch are cells per second, units on the IGX switch are bits per second.
Bundled interworking connections are not supported.
Virtual path interworking connections are not supported.
Because the NNI cell format has 12 bits for the VPI, the command addcon allows specification of VPI
04095 on NNI ports.
Routing
Interworking connections use the complex gateway feature of the AIT trunk card to repackage data from
frames to ATM cells, and vice-versa. All BPX switch-IGX switch hops these connections route over
must provide the complex gateway function.
IGX-to-IGX hops (Frame Relay connections) can be any trunk card type. This requirement simplifies
the routing mechanism when dealing with structured networks, because software does not know the
type of trunks in remote domains.