Cisco 3825 - Manual (Page 97)

4-39
Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide
OL-15667-03
Chapter 4 Configuring the Cisco 3825 Mobile Wireless Edge Router in a RAN-O Solution with the Command-Line
Configuration Sequence
Step 7 Specify the slot location and port of IMA interface group.
Router(config-if)# interface ATM slot/IMA<group-number>
Where:
• slot—Specifies the slot location of the ATM IMA port adapter.
• group-number—Specifies the group number of the IMA group.
For example, the following command specifies the slot number as 0 and the group number as 0:
Router(config-if)# interface ATM0/IMA0
Note Should you desire, the optional ima group-id command can be used to explicitly configure the IMA
Group ID for the IMA interface. You cannot configure the same IMA Group ID on two different IMA
interfaces; therefore, if you configure an IMA Group ID with the system-selected default ID already
configured on an IMA interface, the system toggles the IMA interface to make the user-configured IMA
Group ID the effective IMA Group ID. At the same, the system toggles the original IMA interface to
select a different IMA Group ID.
Step 8 Disable the IP address configuration for the physical layer interface.
Router(config-if)# no ip address
Step 9 Specify the ATM bandwith as dynamic.
Router(config-if)# atm bandwith dynamic
Step 10 Create an ATM path on the UMTS Iub interface, enter the following command:
Router(config-if)# atm umts-iub
Step 11 Disable the Interim Local Management Interface (ILMI) keepalive parameters.
Router(config-if)# no atm ilmi-keepalive
Step 12 Create an ATM PVC:
Router(config-if)# pvc [ name] vpi/vci [qsaal]
Where:
• name—(Optional) specifies the name of the ATM PVC interface you create.
• vpi—Specifies the ATM network virtual path identifier (VPI) of this PVC.
• vci—Specifies the ATM network virtual channel identifier (VCI) of this PVC.
• qsaal—(Optional) specifies theQ.2931 signaling ATM adaptation layer (QSAAL) encapsulation
type.
Note Typically AAL5 PVCs are defined using qsaal encapsulation. However, if the traffic profile is
such that the AAL5 packets exceed normal signaling (272 bytes) payload size, it is
recommended that the PVC be defined using AAL0.
This is commonly true for OAM PVCs and synchronization PVCs. NodeB Application Part
(NBAP) and Access Link Control Application Part (ALCAP) PVCs can be defined using qsaal
encapsulation.