Cisco 3825 Software Configuration Manual page 102
Mobile wireless edge router
Hide thumbs
Also See for 3825:
- Non proprietary security policy (30 pages) ,
- Installation and upgrades (20 pages) ,
- Quick start manual (138 pages)
Table of Contents
Advertisement
Configuration Sequence
To configure the remote parameters required to establish an IP/UDP backhaul connection, enter the
Step 17
following command including the IP address and port you want to establish the IP/UDP backhaul
connection from.
Router(config-if)# umts-iub remote ip-address port
For example, the following command configures the umts-iub remote interface with an IP address and
port of 20.20.20.20 6666:
Router(config-if)# umts-iub local 20.20.20.20 6666
Exit the interface configuration mode.
Step 18
Router(config-if)# exit
Router(config)#
Step 19
Specify the ATM/IMA interface that the PVCs will be assigned to and enter the sub-interface mode.
Router(config)# interface ATM slot /IMA <group-number>[.<subinterface-number> { multipoint
point-to-point}]
Where:
slot—Specifies the slot location of the ATM IMA port adapter.
•
group-number—Specifies the group number of the IMA group.
•
subinterface-number—Specifies the sub-interface number.
•
For example, the following command specifies the slot number as 0 and the group number as 0.1 for
multipoint:
Router(config)# interface ATM0/IMA0.1 multipoint
Create an ATM path on the UMTS Iub interface, enter the following command:
Step 20
Router(config-subif)# atm umts-iub
Create an ATM PVC:
Step 21
Router(config-subif)# 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
Cisco 3825 Mobile Wireless Edge Router Software Configuration Guide
4-44
Chapter 4
Configuring the Cisco 3825 Mobile Wireless Edge Router in a RAN-O Solution with the Command-Line
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.
OL-15667-03
Hide quick links:
Advertisement
Table of Contents
