Professional Documents
Culture Documents
IP Backhaul
IP Backhaul
Release 26.0
401-710-090
Issue 3
March 2006
This material is protected by the copyright and trade secret laws of the United States and other countries. It may not be reproduced,
distributed, or altered in any fashion by any entity (either internal or external to Lucent Technologies), except in accordance with applicable
agreements, contracts or licensing, without the express written consent of Lucent Technologies and the business management owner of the
material.
Trademarks
All trademarks and service marks specified herein are owned by their respective companies.
Contents
.......................................................................................................................................................................................
xv
Safety information
.....................................................................................................................................................................................
xvi
...........................................................................................................................................................
xvi
.............................................................................................................................................
xvii
....................................................................................................................................................................................
xv
...............................................................................................................................................................................................................
xviii
.............................................................................................................................................
..........................................................................................................................................................................................
xix
xx
Introduction to IP Backhaul
IP Backhaul
Overview
.........................................................................................................................................................................................................
.................................................................................................................................................................................
1-2
.....................................................................................................................................................................................................
1-4
IP Backhaul features
Availability
Prerequisites
...................................................................................................................................................................................................
...........................................................................................................................................................
......................................................................................................................................................................
1-5
1-9
1-13
................................................................................................................................................................
1-19
...............................................................................................................................................................................................
1-25
1-1
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
iii
Issue 3, March 2006
See notice on first page
Contents
.........................................................................................................................................................................................................
Reference Diagram
....................................................................................................................................................................................
..........................................................................................................................................................................
2-4
2-6
2-10
....................................................................................................................................................................................................
2-12
...........................................................................................................................................
2-15
............................................................................................................................................................................
2-20
..................................................................................................................................................................
2-22
............................................................................................................................................................................................
2-24
..................................................................................
2-25
.............................................................................................................................................................................................
2-27
2-2
...............................................................................................................................................................................
...........................................................................................................................................................
2-1
IP Backhaul implementation
Overview
.........................................................................................................................................................................................................
3-1
......................................................................................................................................................................
3-3
..................................................................................................................................................
3-6
....................................................................................................................................................
3-9
.......................................................................................................................................................................................................
...............................................................................................................................................
3-13
3-14
.......................................................................................................................................................................................................
..............................................................................................................................................
3-18
........................................................................................................................................................................
3-20
3-17
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
iv
Contents
.......................................................................................................................................................................................................
...............................................................................................................................................................
3-33
..............................................................................................................................................................................
3-34
FMM-RCS implementation
Provision ecp form
.........................................................................................................................
3-37
..........................................................................................................................................................................
3-38
3-32
...........................................................................................................................
3-41
..............................................................................................................................................................................
3-44
......................................................................................................................................................................
3-49
........................................................................................................................................................................
3-50
Post deployment
Post deployment activities
.................................................................................................................................................................
............................................................................................................
3-51
3-52
.........................................................................................................................................................................................................
4-1
4-2
...........................................................................................................................................................................
4-3
FMM-AP OA&M
.......................................................................................................................................................................................
4-5
1X RNC OA&M
........................................................................................................................................................................................
4-6
Router/switch OA&M
BTS OA&M
BTS OA&M for IPBH
MSC
.................................................................................................................................................................................
4-11
............................................................................................................................................................................................
4-21
....................................................................................................................................
4-29
...............................................................................................................................................................................
4-38
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
v
Issue 3, March 2006
See notice on first page
Contents
OMC-RAN
Monitor IPBH from the OMC-RAN
5
.........................................................................................................................................
4-48
Fault management
Overview
.........................................................................................................................................................................................................
5-1
Network monitoring
Fault management
......................................................................................................................................................................................
........................................................................................................................................................
......................................................................................................................................
5-3
5-5
5-7
......................................................................................................................................................
5-10
.........................................................................................................................................................................
5-14
.........................................................................................................................................................................
5-17
.........................................................................................................................................................................
5-20
..........................................................................................................................................................................................
5-24
.....................................................................................................................
...................................................
5-30
.....................................................................................................
5-34
5-27
..........................................
5-37
...............................................................................................................
5-41
IPGW0 is unreachable
..........................................................................................................................................................................
5-45
IPGW1 is unreachable
..........................................................................................................................................................................
5-48
..........................................................................................................................................................
..............................................................................................................................................
5-55
......................................................................................................................................................
5-59
....................................................................................................................................................................
5-63
5-51
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
vi
Contents
......................................................................................................................................................
5-66
....................................................................................................................................................................
5-70
.............................................................................
5-73
..........................................................................................................................................................
5-76
...................................................................................................
............................
5-83
.............................................................................
5-86
One DS1 in MLG is not configured in ER, or wrong DS1 is assigned to MLG in ER
Edge router card failure affecting all associated DS1 interfaces
6
5-79
.........................................................................................................................................................................................................
SM for IPBH
................................................................................................................................................................................................
...................................................................................................................................................................
...............................................................................................................................................................
6-1
6-2
6-6
6-9
.........................................................................................................................................................................................................
7-1
Hazard statements
Overview
.........................................................................................................................................................................................................
...........................................................................................................................................................
7-3
....................................................................................................................................................................
7-5
7-2
Glossary
Index
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
vii
Issue 3, March 2006
See notice on first page
List of tables
Introduction to IP Backhaul
1-1
1-2
1-3
1-4
.....................................................................................................................................................
1-3
....................................................................
1-6
..............................................................................................................................
1-9
............................................................................................................................
1-14
2-2
2-3
2-4
...........................................................................................................
............................................................................................................
2-6
2-20
.....................................................................................................
2-22
....................................................................................................................................
2-27
IP Backhaul implementation
3-1
3-2
3-3
3-4
3-5
3-6
3-7
AP VLAN checklist
3-8
3-9
.....................................................................................................................................
.......................................................................................................................
.....................................................
........................................................................................................................
3-3
3-4
3-9
3-10
.....................................................................................................................
3-10
....................................................................................................................................
3-11
.............................................................................................................................................................
3-11
...................................................................................................................................................
3-12
.........................................................................................................................................................
3-34
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
ix
Issue 3, March 2006
See notice on first page
List of tables
3-10
...................................................................................................................................................
3-38
3-11
......................................................................................................................................................
3-44
3-12
3-13
..............................................................................................................................................
3-49
.................................................................................................................................................
3-50
4-2
4-3
4-4
Modified inputs
4-5
New outputs
4-6
Modified outputs
4-7
4-8
................................................................................................................................
4-9
.............................................................................
4-12
....................................................................................................................................................
4-30
.....................................................................................................................................................................
4-31
..............................................................................................................................................................................
4-33
..................................................................................................................................................................
......................................................................................................................................
................................................................................................................
4-34
4-36
4-38
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
List of figures
Introduction to IP Backhaul
1-1
1-2
1-3
1-4
IPBHNetwork
1-5
IPBH architecture
................................................................................................................................................
..................................................................................
1-16
1-17
..................................................
1-18
..........................................................................................................................................................................
1-19
..................................................................................................................................................................
1-21
2-2
.......................................................................................................................................................
2-7
2-1
2-2
2-3
2-4
2-5
IPBTS GW Sparing
2-6
2-7
2-8
2-9
..........................................................................................................
2-11
.................................................................................................................
2-12
.............................................................................................................................................................
2-16
.....................................................................................................
2-18
...................................................................................................................................................
2-19
.........................................................................................................................................
.................................................................................................................................
2-20
2-22
IP Backhaul implementation
3-1
3-2
3-3
.......................................................................................................................................................
3-6
.............................................................................................................................
3-15
..................................................................................................................................
3-18
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
xi
Issue 3, March 2006
See notice on first page
List of figures
4-1
4-2
4-3
4-4
.....................................................
4-13
4-5
.....................................................
4-13
4-6
.....................................................
4-14
4-7
.....................................................
4-14
4-8
..............................................................................
4-15
4-9
..............................................................................
4-15
4-10
4-11
4-12
4-13
4-14
.......................................................
4-18
4-15
.......................................................
4-18
4-16
.............................................................................
4-19
4-17
.............................................................................
4-19
4-18
4-19
4-20
4-21
.............................................................................................................................................................
4-23
4-22
.............................................................................................................................................................
4-24
4-23
...................................................................................................................................................................
4-25
4-24
...................................................................................................................................................................
4-26
4-25
4-26
...................................................................................................................................................
.........................................................................................................................................
...........................................................................................................................
4-8
4-9
...................................
4-16
...........................................................................
4-16
................................................................................
4-16
............................................................
4-17
..........................................................................
4-20
.............................................................................................
4-20
......................................................................................................................................................................
4-22
..........................................................................................................................................................
4-27
................................................................................................................................................................
4-28
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
xii
List of figures
4-27
SDP 2101
....................................................................................................................................................................................
4-40
4-28
SDP 2131
....................................................................................................................................................................................
4-41
4-29
SDP 2138
....................................................................................................................................................................................
4-42
4-30
.................................................................................................................................................
4-43
4-31
.................................................................................................................................................
4-44
4-32
SDP 2260
....................................................................................................................................................................................
4-45
4-33
SDP 2265
....................................................................................................................................................................................
4-46
4-34
.......................................................................................................
4-47
4-35
......................................................................................................
4-49
4-36
4-37
4-38
4-39
4-50
.................................................................................................
4-51
....................................................................................................
4-52
....................................................................................................
4-53
Fault management
5-1
....................................................................
Network monitoring
...............................................................................................................................................................
5-7
6-2
......................................................................................................
........................................................................................................................................
6-9
6-10
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
xiii
Issue 3, March 2006
See notice on first page
Purpose
This document describes the IP Backhaul for CDMA Voice and Packet Data (IP
Backhaul) optional feature for 3G1X CDMA in Lucent Technologies
Flexent /AUTOPLEX wireless networks.
Reason for reissue
This issue of this document (Issue 3, March 2006), supersedes Issue 1 (December
2005). Issue 2 was an Lucent Technologies internally available document in support of
Release 25.01 (January 2006).
This issue provides the following new and changed information:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
xv
Issue 3, March 2006
See notice on first page
,
Safety information
This information product contains hazard statements for your safety. Hazard statements
are given at points where safety consequences to personnel, equipment, and operation
may exist. Failure to follow these statements may result in serious consequences.
How to use this information product
The following table briefly describes each chapter and its contents:
Chapter
Description
Glossary
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
,
xvi
Conventions used
Literal user input: Keystrokes that are entered character by character exactly as
shown in the text appear in monospace type.
For example:
Enter the following command:
apappconfig
Variable user input: Input values that vary from one execution or instance to
another appear in monospace italic type.
For example:
cd directory
Variable system output: Values that vary from one instance to another in system
output appear in monospace type.
For example:
RST SPA=SPA_NAME REQUEST COMPLETED
where SPA_NAME = the name of the Service
successfully restored.
Key names: The names of keys on a terminal keyboard are indicated by bold
letters.
For example:
Press the F4 (Enter Query) function key.
Key symbols: The Crtl (Control) key is signified by the caret ( ^ ) symbol. When
the ^ symbol precedes the name of another key (as in ^e), press the Crtl key and
the other key simultaneously.
Variable information: Variable data to be entered is identified in monospace type.
For example:
URCm where m represents a different type of universal radio control cell.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
xvii
Issue 3, March 2006
See notice on first page
,
In this information product, the following words specify what action you should
perform to input data or execute commands:
The word enter means to key in the specified keystrokes (such as a command) and
then press the Enter or Return key.
For example:
Enter the following command:
apappconfig
The word press means to push down the specified key or keys on the keyboard.
For example:
Press the F4 (Enter Query) function key.
The word type means to key in the specified keystrokes (such as a value in the
field of a form) without pressing the Enter or Return key.
For example:
In the IP address field, type the IP address of the host server.
The following documents are either referenced in this document or contain information
that is related to topics that are covered in this document:
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
,
xviii
Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance Control
Procedures, 401-610-160.
Flexent /Autoplex Wireless Networks BTS conversion from LAPD to IPBH,
401-612-841.
Flexent /Autoplex Wireless Networks Operations and Maintenance Center Radio
Access Network (OMC-RAN) Operations, Administration, and Maintenance
(OA&M), 401-662-105.
Flexent Wireless Networks Radio Cluster Server (RCS) FMM-RCS OA&M,
401-710-102.
Flexent Wireless Networks CDMA 1X Radio Network Controller (RNC)
Operations, Administration, & Maintenance, 401-710-082.
Flexent CDMAModular Cell 4.0 and Compact Modular Cell 4.0 Operations,
Administration and Maintenance, 401-703-407
Flexent CDMAModular Cell 1.0, 2.0, 3.0 and Compact Modular Cell 3.0
Operations, Administration and Maintenance, 401-710-122
For technical support, contact your local customer support team. You can reach them
via the web at https://support.lucent.com or the telephone number listed under the
Technical Assistance Center menu at http://www.lucent.com/contact/.
For technical support, call the following numbers:
Please be prepared to describe the specific problem in your network. An operator will
either transfer your call directly to a customer technical support representative or
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
xix
Issue 3, March 2006
See notice on first page
,
forward your request to a representative, who will return your call as soon as possible.
Service-affecting situations are always handled immediately.
How to comment
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
,
xx
I ntroduction to IP Backhaul
1
IP Backhaul
Overview
.................................................................................................................................................................................................................................
Purpose
This document describes the CDMA technology IP Backhaul offer that is available
from Lucent Technologies. It provides an overview of IP Backhaul and the IP Backhaul
network, provides implementation requirements and describes the implementation steps
that are needed. In addition OA&M functions and processes needed for IPBH are
described and performance information about a Lucent Technologies IP Backhaul
network are provided.
Internet Protocol (IP) is the standard protocol that forms the basis of the Internet as
defined by the Internet Engineering Task Force (IETF). IP works in networks with
numerous and varied types of hardware and software, and it allows full peer-to-peer
communications between any nodes in the network. Backhaul is the means by which
the base transceiver stations (BTSs) connect to the mobile switching center (MSC).
Contents
IP Backhaul features
1-2
Availability
1-4
Prerequisites
1-5
1-9
Benefits of IP Backhaul
1-13
1-19
IPBH traffic
1-25
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-1
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
IP
Backhaul features
.................................................................................................................................................................................................................................
IP Backhaul FIDs
IP Backhaul was introduced initially in ECP Release 25.0. The individual feature
identifiers (FIDs) that comprise the IP Backhaul offer are listed by release.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-2
Introduction to IP Backhaul
IP Backhaul features
The following table identifies how specific network features work with IPBH.
Table 1-1
Feature
Comment
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-3
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Availability
.................................................................................................................................................................................................................................
Release availability
The IP Backhaul feature was available in CDMA starting with Release 25.0.
Market availability
The IP Backhaul feature is available in the North American region (NAR) and for
International markets.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-4
Introduction to IP Backhaul
Prerequisites
.................................................................................................................................................................................................................................
Supported technologies
CDMA cellular
CDMA Personnel Communication System (PCS)
The following table identifies how specific network features work with IPBH.
Feature
Comment
HLR
OMC-RAN
Hardware requirements
Table 1-2, Network elements in an IPBH network and required changes (p. 1-6)
displays all of the hardware required for IPBH and identifies required hardware
changes for IPBH.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-5
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Prerequisites
Network
Element
Function
FMM-AP
Holds RCS-APs
(BTS controllers
in the ECPC)
Only RCSs on
FMM-AP are
supported
1XRNC
(optional)
Holds IP
backhaul servers
(BHS).
Requires GICC
1.1 cards (2) for
Ethernet
connection.
5ESS
DCS/PSU2e
Holds IP
backhaul servers
(BHS).
BTS / Modular
cell / Modular
cell 4.0 with
URC or URC-II
Standard cell
hardware based
on your system.
BTS / Modular
cell / HD 4.0
with URC or
URC-II
Standard cell
hardware based
on your system.
BTS / Modular
cell / Modular
cell 4.0 Compact
with URC or
URC-II
Standard cell
hardware based
on your system
BTS / Modular
cell / Modular
cell 1/2/3 with
URCm card
Standard cell
hardware based
on your system
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-6
Introduction to IP Backhaul
Table 1-2
Prerequisites
Network
Element
Function
Backhaul
transport: Edge
routers (ER)
Support DS1
transport.
Backhaul
transport:
Layer2/layer 3
switches
Provide IP
network
interconnections
between IPBH
network elements
Software requirements
Executive cellular processor (ECP) Release 25.0 and higher that contains all
FMM-AP, RCS-AP and 1XRNC software.
5ESS DCS: 5e19.1 (generic) release for R25.0 NAR
5ESS DCS 5ee16.l (generic) release for R26.0 International
BTS release 25.0 and higher
Modular cell 4.0, HD 4.0 and Compact 4.0
Modular cells 1, 2, and 3
Remote maintenance terminal (RMT) software using either the
Maintenance version that allows all capabilities of the RMT except setting
facilities backplane memory parameters.
Self-install version that allows all capabilities of RMT including facilities
backplane memory parameters.
C E L L 152 - IP Backhaul Support for Right to Use xxx, where the value xxx is the
number of IPBH carriers configured This value varies by customer and can be any
number from 0 to 10,800, or greater, depending on the user. See your Lucent
Technologies representative for details.
You will need to know the number of carriers for your configuration prior to
implementing IPBH. This value is the purchased number of IPBH carriers that can be
configured in an office. During configuration, warnings are built in to notify when
carrier capacity has reached 75% and 90% of capacity. If 100% capacity is reached no
additional configurations can occur. For planning purposes, be sure you know the
number of carriers you have purchased.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-7
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Prerequisites
When the IP Backhaul Enabled field is set for a BTS via the cell2 form, a Backhaul
Server (BHS) has to be assigned in the cell2 form for each carrier assigned to a radio
via the cdmeqp/btseqp form for the cell. Each carrier that is assigned to a BHS on
the cell2 form is counted as a configured IPBH carrier. The number of currently
configured IPBH carriers for the office is displayed on the ECP form. The number of
currently configured IPBH carriers is not allowed to exceed the number of purchased
IPBH carriers designated in the RTU QFAF. When an attempt is made to configure
more IPBH carriers than the RTU QFAF allows, the cell2 form update is denied
Technical industry standards
The Point-To-Point Protocol (PPP), STD 51, IETF RFC 1661, July 1994
The PPP Multilink Protocol (MP), IETF RFC 1990
User Datagram Protocol, IETF RFC 768, August 1980
Internet Protocol version 4, IETF RFC 791, September 1981
IEEE 802.1D/Q Mac Bridges and Virtual LAN
Differentiated Service, IETF RFC 3317Differentiated Services Quality of Service
Policy Information Base
The PPP Internet Protocol Control Protocol, IETF RFC1332 & 1877 (Extension for
DNS)
The Multi-Class Extension to Multi-Link PPP, IETF RFC 2686
PPP Challenge Handshake Authentication Protocol (CHAP) IETF RFC 1994
HDLC Like Framing for PPP, IETF RFC 1662
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-8
Introduction to IP Backhaul
IPBH
documentation roadmap
.................................................................................................................................................................................................................................
Related documentation
The following graphic identifies the Lucent Technologies customer documentation that
is available for the network elements that comprise the IPBH network. Note that
non-Lucent hardware documentation is available through your vendor.
Table 1-3
Task
Description
Document name
Implement IPBH
network
IPBH overview
IPBH planning
IPBH
implementation
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-9
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Table 1-3
(continued)
Task
Description
Document name
Convert existing
LAPD network
from frame Relay
to IPBH
Step-by-step
procedure for cell
conversion.
Install packet
handlers for IPBH
OA&M documents
for the 5ESS
Switch.
RC Views
For International
documents, see
listing at end of
this table.
Install packet
handlers for IPBH
Network planning
and engineering
guidelines
System planning
Cell OA&M
RC/V description
for screens, forms
and field
parameters
Database update
Syntax and
description of
network
commands
Alarms and
messages
Look up alarm
message and
determine status
and purpose of
alarm.
Alarms and
messages
Troubleshoot an
alarm message
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-10
Introduction to IP Backhaul
Table 1-3
(continued)
Task
Description
Document name
System
performance and
service
measurement data
All Service
Measurements for
the network are
identified and
detailed.
Monitor the
network from the
ECP complex
Monitor the
network from the
OMC-RAN
Description of
OMC-RAN
OA&M for
monitoring a
network.
Maintain and
provision the
RCS-APs
FMM-RCS
OA&M
Install/update
GICC card for
IPBH
1X RNC OA&M
FMM-TI reference
for TICLI
commands
Establish IPBH
parameters for
data offload to the
RNC
Reference TICLI
commands
Additional 5ESS
DCS documents
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-11
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
The course CL5591: IP Backhaul for CDMA Voice and Packet Data is available
starting with Release 25.0. This course describes IP Backhaul and provides a detailed
overview of the implementation necessary to successfully convert BTSs from LAPD to
IPBH.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-12
Introduction to IP Backhaul
Benefits
of IP Backhaul
.................................................................................................................................................................................................................................
IPBH definition
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-13
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Benefits of IP Backhaul
With IPBH, both signaling and user traffic are multiplexed over IP over unchannelized
DS1s.
Current Lucent Technologies backhaul networks utilize frame relay packet pipes. Table
1-4, Differences between FR and IPBH (p. 1-14) lists the major differences between
frame relay (FR) and IP Backhaul.
Table 1-4
IP Backhaul
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-14
Introduction to IP Backhaul
Benefits of IP Backhaul
Advantages of IPBH
IPBH provides the following advantages versus frame relay (FR) backhaul:
Signaling links delivered to the ECPC directly from the DACS or via a 5ESS DCS
nailup.
Signaling links delivered to the ECPC via nailup connection to the DS1s
5ESS DCS interfaces carry packet pipes (PPs) only or PPs with signaling links
(optional)
PPs are delivered to the frame relay packet handler (FRPH) via TSI and DF2
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-15
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Benefits of IP Backhaul
For Code Division Multiple Access (CDMA) systems, the BTS backhaul network
currently consists of DS1 facilities connecting each BTS to a DS1 transport network
that terminates in the MSC either on a Digital Access and Cross-connect System
(DACS), or directly on the Wireless 5ESS Digital Cellular Switch (5ESS DCS).
User traffic is carried on dedicated multi-DS0 packet pipes (PP) that terminate on
FRPHs. Control traffic is carried on dedicated DS0s that terminate on BTS controllers
(RCS-APs in the ECPC) over DS1 interfaces.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-16
Introduction to IP Backhaul
Benefits of IP Backhaul
Figure 1-2, Typical IP Backhaul network with 5ESS DCS/PSU2e (p. 1-17) shows a
typical configuration for a IP Backhaul network:
Figure 1-2 Typical IP Backhaul network with 5ESS DCS/PSU2e
The typical IP backhaul network with a 5ESS DCS provides the following:
Control signaling delivered to the Flexent Mobility Manager (FMM) local area
network (LAN) directly from the backhaul router, (No DS0 grooming is required.)
Traffic is delivered directly to the backhaul server (BHS) freeing up resources
previously used for FR overhead.
The Digital Network Units-SONET (DNU/Ss) and Digital Line Trunk Units
(DLTUs) are retired from backhaul usage.
The recovered Time Slot Interchange (TSI) capacity can be used for trunk growth.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-17
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Benefits of IP Backhaul
Figure 1-3, Typical IP Backhaul network with 5ESS DCS/PSU2e and 1X RNC
(p. 1-18) shows a typical configuration for a IP Backhaul network:
Figure 1-3 Typical IP Backhaul network with 5ESS DCS/PSU2e and 1X RNC
The typical IP backhaul network with the 5ESS DCS PSU2e and RNC provides the
following:
Control signaling delivered to the Flexent Mobility Manager (FMM) local area
network (LAN) directly from the backhaul router. (No DS0 grooming is required.)
Traffic is delivered directly to the backhaul server (BHS) on the 5ESS without
using resources previously used for FR overhead.
The Digital Network Units-SONET (DNU/Ss) and Digital Line Trunk Units
(DLTUs) are retired from backhaul usage.
Data offload traffic is delivered to the BHS on the RNC.
The recovered Time Slot Interchange (TSI) capacity can be used for trunk growth.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-18
Introduction to IP Backhaul
IPBH
network architecture
.................................................................................................................................................................................................................................
Attributes
Figure 1-4 IPBHNetwork
All traffic and signaling between Base Transceiver Stations (BTS) and the Mobile
Switching Center (MSC) is carried over the IP network layer (IP Version 4 only).
The network interfaces at the BTSs are un-channelized DS1s.
At the BTS, traffic on any carrier can be switched to/from any DS1 so DS1s can
be optimally utilized. Bandwidth is added to a BTS in DS1 increments as needed to
support capacity growth regardless of carrier configuration and carrier load. DS1
capacity using the UDPMux protocol is approximately 145 3G1X voice call legs
per DS1.
Traffic and signaling are mixed over the DS1s and separated at the IP switching
layer.
On the network side, the DS1s terminate on commercial IP edge routers.
Connections to elements at the MSC are all IP over Ethernet, rather than fractional
DS1 time division multiplex (TDM) channels.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-19
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Provisioned data determines which packet switching unit (PSU) will serve the
traffic from a given BTS. Carrier geographic clustering is supported for voice or
combined voice and data traffic carried by the 5ESS DCS.
BTSs can be provisioned such that voice is served on a PSU (or PSUs) while
packet data is served on an RNC (or RNCs). This enables packet data to be truly
off-loaded from PSUs and the inter-PSU soft handoff network. Carrier geographic
clustering is not supported for data offload traffic on the RNC.
IP backhaul is supported on all Modular cell types with Universal Radio
Controllers (URCm, URC and URC-II). It is not supported on Modular cells with
Circuit Radio Controllers (CRC).
IP backhaul is supported on Radio Cluster Servers (RCS-AP) hosted on FMM-APs
and supports a mix of IP and FR BTSs on one RCS-AP.
IP backhaul cell is either all IP or all frame relay (FR) and cannot be mixed on the
same cell.
Soft handoff universe can support a mix of IP and FR BTSs. IPBH has no affect on
ATM SHO network (intra- or inter-MSC).
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-20
Introduction to IP Backhaul
Figure 1-5, IPBH architecture (p. 1-21) identifies all of the elements in the IPBH
network architecture.
Figure 1-5 IPBH architecture
Legend:
Abbr.
Meaning
BTS 1
BTS n
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-21
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Abbr.
Meaning
MLG
Multi-link Group
An aggregated grouping of multiple DS1s for transmission
between two points.
URC #
UDP
UPDmux
ML-PPP
NxDS1
TCP IP
ER-#
Edge Router - #
are cross-connected to a pair of Multi-layer switches (MLS)
over Ethernet
MLS-#
Multi-layer Switch #
MSC adjacent switches connect to FMM-APs, PSUs and
RNCs on flexible L2 transmission lines
L2-A/L2-B
FMM-APs
TR1/2
PSUs
BHS
Backhaul Server
1X RNCs
The physical layer at the BTS continues to be DS1. All user traffic and signaling are
multiplexed onto common DS1s and the IP layer is used to route packets to and from
the desired MSC destinations.
The DS1s are terminated at the BTS on a universal radio controller (URC) board. All
the URCs within a BTS are interconnected to enable traffic on any carrier to be
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-22
Introduction to IP Backhaul
transported over any DS1. This enables optimal DS1 utilization. No IP router is
required at the BTS site.
On the network side, the DS1s terminate on a standard IP edge router. IP edge routers
support DS1 over a variety of physical interfaces including: T1/E1, T3/E3/STS-1,
OC-3/STM-1 and OC-12/STM-4.
Multi-link groups
Multiple DS1s between a URC and an edge router are grouped together into a
multi-link group (MLG). The layer 2 protocol between the BTS and the edge router is
PPP [1] over DS1 or Multi-Link PPP [2] over NxDS1. ML-PPP enables multiple DS1s
on the same URC (that terminate on the same router) to be grouped together into a
Multi-Link Group (MLG). Each PPP/DS1 link or ML- PPP/NxDS1 link requires a
unique IP address. Using MLGs (rather than individual DS1s) minimizes the number of
separate interfaces that have to be managed by the application, and minimizes the
number of IP addresses that a BTS requires. MLGs also aggregate bandwidth which
increases aggregate DS1 efficiency.
Throughout this document, the term MLG is used to refer to a PPP or ML-PPP link
between a BTS and an edge router regardless of the number of DS1s in the MLG.
Each URC has only one MLG. The BTS with multiple MLGs can have each MLG on
a different ER.
Backhaul routers
The edge routers perform IP routing (layer 3); the L2 switches perform Ethernet
switching (layer 2).
Edge routers
The edge routers provide the OC3 terminations toward the BTSs and wide-band
uplinks toward the MSC.
Multi-layer switches
The MLSs are optimized to provide economical Ethernet connections to the individual
control and traffic servers at the MSC. The MLSs perform both IP routing (layer 3)
and Ethernet switching (layer 2).
Router configuration
The expected initial configuration has all the routers at the MSC site. However, it is
also possible to remote edge routers in cases where there is an economic advantage to
terminate the DS1s closer to some group of BTSs and carry their aggregated traffic to
the MSC over some type of wide-band facilities. These wide-band facilities are
expected to be either unswitched (layer 2 pipes) or tunneled (layer 2 or 3) with
guaranteed bandwidth. In any case their bandwidth must be engineered to meet the
very strict delay and jitter requirements of CDMA backhaul.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-23
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
Packets between IP BTSs and RCS-APs are carried over Ethernet links between the
MLSs and the FMM-AP Ethernet LAN. There are links between the MLs and each
growth frame with RCS-APs. RCS-APs communicate with BTSs over the same two
Ethernet interfaces that they use for internal AP-to-AP communications.
DCS/PSU network interface
User traffic is carried over direct 100 Mbps Ethernet links between the MLSs and PSU
Protocol Handler boards that are known as Backhaul PHs, or BPHs. Each BPH has 1
Ethernet link.
BPHs are deployed in serving or non-serving (active/standby) pairs (1+1) for improved
reliability. A serving (active) BPH can take over from the non-serving (standby) BPH
without loss of stable calls. When a non-serving BPH takes over, it assumes the IP
address of the serving BPH so this switchover is transparent to the other network
elements (ECPC and BTSs).
A fault tolerant configuration has the serving and non-serving BPHs of a pair
connected to different MLSs. This implies that the traffic subnets span MLSs (that is,
theMLs are connected at Layer 2 for the traffic subnets). A serving and non-serving
pair of BPHs is known to other network elements as a single logical entity called a
Backhaul Server or BHS. The details of BPH sparing are not visible to other network
elements since the switchover between BPHs in a pair is transparent. A PSU that
terminates IP backhaul traffic is expected to require no more than 3 to 4 BHSs. Each
BHS in a PSU can serve approximately 2000 call legs. IP backhaul is supported only
on PSU2e (PF3, CF3), which requires the Core700 SMP in the host SM.
1X RNC Network Interface
User traffic is carried over Gigabit Ethernet links between the MSC switches and RNC
Gateway Intelligent Carrier Cards (GICCs). Each GICC that supports IP backhaul has
1 Gigabit Ethernet link to an MSC switch.
GICCs that support backhaul are deployed in serving and non-serving (active/standby)
pairs (1+1) for improved reliability. A non-serving GICC takes over from the serving
GICC without loss of stable calls. When a non-serving GICC takes over, it assumes the
IP address of the serving GICC so the L2 switch over is transparent to the other
network elements (ECPC and BTSs). See System Capacity Monitoring and Engineering
Guidelines, 401-610-009 for current capacity information for the RNC.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-24
Introduction to IP Backhaul
IPBH
traffic
.................................................................................................................................................................................................................................
Purpose
The flow of data through the IP Backhaul network depends on the configuration of the
network. This section introduces the traffic protocol layers and describes the flow of
traffic in the IPBH network.
User traffic protocol
User traffic is carried on application layer connections over IP between URCs and
BHSs (in PSUs and RNCs).
There are several important considerations in the selection of the user traffic protocol
layers:
Intra- or inter-MSC
BTSs with IP backhaul can co-exist in the same MSC and in the same Inter-MSC
soft-handoff network as BTSs with FR backhaul. That is, all frame selectors (FSs)
must support simultaneous call legs from any combination of FR backhaul and IP
backhaul BTSs. FR backhaul uses the frame relay DLCI to route traffic frames from
the frame relay PH (FRPH) that terminates the packet pipe to any FS4 in the
soft-handoff network.
Compatibility with FR backhaul cells
Efficient use of DS1s dictates bundling of small traffic frames into larger IP packets.
This spreads the UDP/IP header over many traffic frames. The chosen protocol is
called UDPMux because of the bundling (also called multiplexing) of traffic frames
into UDP datagrams. UDPMux is a proprietary application layer that is transported
over standard UDP/IP. As mentioned above, to preserve compatibility with TDM
backhaul, each traffic frame continues to be routed within the soft-handoff network
based on DLCI.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
1-25
Issue 3, March 2006
See notice on first page
Introduction to IP Backhaul
IPBH traffic
For IP backhaul, as a further DS1 efficiency improvement, the DLCI of each traffic
frame is replaced over the backhaul with a 1 byte value called a CID (Call ID). The
CID is allocated during call leg setup. The BHS performs the mapping between the 1
byte CID used between the BHS and BTS and the DLCI used between the BHS and
FS (within the soft-handoff network). So a UDPMux bundle is a standard UDP/IP
datagram with a small UDPMux header (application layer) and a sequence of traffic
frames each of which includes a CID and length field. For uplink traffic the BTS
creates UDPMux bundles from nearly simultaneous traffic frames that are to be sent
over a particular MLG to a particular BHS. The receiving BHS parses out the
individual traffic frames, restores the full DLCI for each frame (based on the CID) and
routes each frame to the destination FS based on the DLCI (just like an FRPH). For
downlink traffic a BHS creates UDPMux bundles from nearly simultaneous traffic
frames destined to the same BTS and MLG. For each traffic frame it inserts the CID
based on address information from the FS. The receiving BTS parses out the individual
traffic frames and routes each frame to the destination channel element based on the
CID. The expected DS1 capacity using the UDPMux protocol is 145 3G1X voice call
legs per T1.
In a network, latency, a synonym for delay, is an expression of how much time it takes
for a packet of data to get from one designated point to another. In some instances
latency is measured by sending a packet that is returned to the sender and the
round-trip time is considered the latency. Simulations indicate that around 320 bytes
per UDPMux data gram (around 15 traffic frames on average) is ideal for optimizing
DS1 efficiency while minimizing latency (delay) and jitter.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
1-26
Overview
.................................................................................................................................................................................................................................
Purpose
This chapter describes the interfaces and interactions within the IP Backhaul network.
Contents
Reference Diagram
2-2
2-4
2-6
2-10
5ESS DCS
2-12
2-15
2-20
2-22
DS1s in IPBH
2-24
2-25
IP Addressing
2-27
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-1
Issue 3, March 2006
See notice on first page
Reference
Diagram
.................................................................................................................................................................................................................................
Network architecture
Figure 2-1, IP Backhaul network reference diagram (p. 2-2) is referenced throughout
this chapter.
Figure 2-1 IP Backhaul network reference diagram
Legend:
Abbr.
Meaning
BTS 1
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-2
Reference Diagram
Abbr.
Meaning
BTS n
MLG
Multi-link Group
An aggregated grouping of multiple DS1s for transmission
between two points.
URC #
UDP
UPDmux
ML-PPP
NxDS1
TCP IP
ER-#
Edge Router - #
are cross-connected to a pair of Multi-layer switches (MLS)
over Ethernet
MLS-#
Multi-layer Switch #
MSC adjacent switches connect to FMM-APs, PSUs and
RNCs on flexible L2 transmission lines
L2-A/L2-B
FMM-APs
TR1/2
PSUs
BHS
Backhaul Server
1X RNCs
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-3
Issue 3, March 2006
See notice on first page
Base
transceiver station
.................................................................................................................................................................................................................................
Purpose
The BTS manages signals to and from users and call control manager functions in the
MSC.
HW/SW requirements
A cell cannot have a mix of FR and IPBH facilities in service. All Universal Radio
Controllers (URCs) within communication facilities in a cell must be configured for
either FR or IPBH.
Modular cell 1.0-3.0 supports the configuration of 1 URCm with no T1/E1
facilities. For URCms with no facilities, all signaling and traffic are routed through
facilities on another URCm. CRCs are not supported for IPBH.
For Modular cell 4.0, each URC or URC-II must be connected to at least one edge
router.
DS1s
DS1 continues to be the physical layer at the BTS, using full, unchannelized DS1s.
The creation of any sub-DS1 rate channels is not required. Instead all user traffic and
signaling are multiplexed onto common DS1s and the IP layer is used to route packets
to and from the desired MSC destinations.
Modular cells
The DS1s are terminated at the BTS on a URC board. IP Backhaul is supported on all
Modular cells equipped with URCs. Each CRC in a Modular cell 1/2/3 must be
upgraded to a URCm prior to conversion of the BTS to IP Backhaul. All the URCs
within a BTS frame are interconnected to enable traffic on any carrier to be transported
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-4
over any DS1. This enables optimal DS1 utilization. This is an integrated IP solution at
the BTS. There is no IP router required at the BTS site.
Refer to Flexent CDMA Modular Cell 4.0 and Compact Modular Cell 4.0 Operations,
Administration and Maintenance, 401-703-407 and Flexent / CDMA Modular Cell
1.0, 2.0, 3.0 and Compact Modular Cell 3.0 Operations, Administration and
Maintenance, 401-710-122 for cell OA&M information.
All IP
The 3G1X carriers and URCs in a BTS are either all IP or all frame relay. A cell
cannot have a mix of FR and IPBH facilities in service, except as a transient condition
during conversion of a cell.
Important! Note that this statement excludes EVDO. A BTS can be configured to
simultaneously support EVDO and 3G1X. A configuration for the EVDO URC can
be IP, while all the 3G1X URCs are frame relay.
BTS to router interfaces
On the network side, the DS1s are terminated on a standard IP edge router. The design
of the physical transport of the DS1s is a service provider option. IP edge routers
support DS1 over a variety of physical interfaces.
Multi-link group (MLG)
Characteristics of MLGs:
The layer 2 protocol between the BTS and the edge router is PPP over DS1 or
ML-PPP over NxDS1. ML-PPP enables multiple DS1s on the same URC (that
terminate on the same router) to be grouped together into a multi-link group (MLG).
Each PPP/DS1 link or MLPPP/ NxDS1 link requires a unique IP address. Using MLGs
(rather than individual DS1s) minimizes the number of separate interfaces that have to
be managed by the application. MLGs also aggregate bandwidth which increases
aggregate DS1 efficiency.
For greater path diversity, a BTSs MLGs may be spread across a pair of edge routers
as shown in Reference Diagram (p. 2-2). Each MLG may have one or several DS1s
(within the URC capacity limit).
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-5
Issue 3, March 2006
See notice on first page
Backhaul
routers and switches
.................................................................................................................................................................................................................................
Purpose
Document
Description
VRAD-5576
See your Lucent Technologies account representative for access to these documents.
Transport network configuration
The network transport portion of the IPBH architecture resides between the cell sites
and the Mobile Switching Center (MSC). Its purpose is to transport traffic between the
cells and the MSC components. Figure 2-2, IPBH network topology (p. 2-7)
illustrates the general network topology in a duplex configuration. The Automatic
Protection Switching (APS) mechanism of Synchronous Optical Network (SONET) is
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-6
used to provide redundancy for router failure and OC3 link failure (Active OC3 and
Protect OC3).
Figure 2-2 IPBH network topology
Edge routers
T1/E1
T3/E3
OC-3/STM-1
OC-12/STM-4
The expected initial configuration has all the routers at the MSC site. However, it is
also possible to have remote edge routers.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-7
Issue 3, March 2006
See notice on first page
Remote routers are used in cases where there is an economic advantage to terminate
the DS1s closer to some group of BTSs and carry their aggregated traffic to the MSC
over some type of wideband facilities. These wideband facilities are expected to be
either unswitched (layer 2 pipes) or tunneled (Layer 2 or Layer 3) with guaranteed
bandwidth. In any case their bandwidth must be engineered to meet the very strict
delay and jitter requirements of CDMA backhaul.
Adjacent switches
Regarding routers and switches, the backhaul network architecture is vendor neutral.
For the most part only commonly available interfaces and features are required.
However, there are some quality of service (QoS) capabilities that are required to
achieve high quality voice over DS1, that are standardized but are not widely
supported on edge routers.
IP router requirements
The IP router must support the following standard protocols to be compatible with
Lucent Technologies IP Backhaul:
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-8
The Ethernet switch should support the IEEE 802.1D/Q function to be compatible
with Lucent IP Backhaul
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-9
Issue 3, March 2006
See notice on first page
Radio
cluster server
.................................................................................................................................................................................................................................
Purpose
The radio cluster server (RCS) is an application on an RCS-AP that performs the call
processing and OA&M functions for the cells.
HW/SW requirements
An RCS-AP can simultaneously support IP and frame relay BTSs. That is, an RCS-AP
can run a mix of RCS-Link Access Protocol on the D channel (LAPD) instances (to
support BTSs in FR mode) and RCS-IP instances (to support BTSs in IP mode).
An RCS-AP that supports only IP BTS does not require DS1 links or a DS1 I/O card.
RCS connectivity to the backhaul network
Each MSC adjacent switch has one 100 Mbps Ethernet link to one of the switches in
each FMM growth frame with RCS-APs. Based on RCS-AP capacity, a frame that is
fully equipped with RCS-APs does not require more than one 100 Mbps Ethernet link
to each adjacent switch. The two links to a given FMM frame are redundant, that is,
each link can support the full backhaul message load for that frame. RCS-APs
communicate with BTSs over the same two Ethernet interfaces that they use for
internal AP-to-AP communications.
FMM-AP
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-10
Figure 2-3, RCS signaling conversion: simplified view (p. 2-11) shows a simplified
view of the RCS signaling conversion in the IPBH network.
Figure 2-3 RCS signaling conversion: simplified view
Note that once the MSC is completely IP, the DACS will no longer be needed.
When all IPBH BTS and network preparations are completed for an IPBH network, the
following types of activities can occur for the RCS:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-11
Issue 3, March 2006
See notice on first page
5ESS
DCS
.................................................................................................................................................................................................................................
Purpose
The 5ESS DCS hosts the backhaul server (BHS) on the packet switching unit (PSU2e)
for user traffic.
HW/SW requirements
Legend:
2-12
5ESS DCS
PSU2e characteristics:
BHAs
The backhaul server association (BHA) is a UDPMux session between a BTS and a
BPH. This association is identified by the BTS IP address, the BHS IP address, and the
UDP ports. See 5ESS DCS OA&M (p. 4-11) information about commands to view
all BHA information.
Backhaul protocol handlers (BPH)
User traffic is carried over direct 100 Mbps Ethernet links between the MSC adjacent
switches and PSU2e Protocol Handler (PH) boards that are known as Backhaul PHs, or
BPHs. Each BPH has one Ethernet link.
Fault tolerance
BPHs are deployed in serving and non-serving pairs (1+1) for improved reliability.
A non-serving BPH can take over from the serving BPH without loss of stable
calls.
BPH failover occurs due to Ethernet failure, loss of connectivity to 1st hop router
or unrecoverable hardware or software faults.
When a non-serving BPH takes over, it assumes the IP address of the serving BPH
so this switchover is transparent to the other network elements, the Executive
Cellular Processor Cluster (ECPC) and BTSs.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-13
Issue 3, March 2006
See notice on first page
5ESS DCS
A fault tolerant configuration has the serving and non-serving BPHs of a pair
connected to different adjacent switches as shown in Figure 2-4, 5ESS Switch packet
handlers in PSU2e (p. 2-12). This implies that the traffic subnets span the adjacent
switches (that is, the adjacent switches are connected at Layer 2 for the traffic subnets).
BHS
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-14
Radio
network controller (1X RNC)
.................................................................................................................................................................................................................................
Purpose
The 1X radio network controller ( 1X RNC also referred to as RNC) hosts a backhaul
server (BHS) for data offload of user traffic in an IPBH network.
New terms for IPBH in the RNC:
Internet Protocol base transceiver station gateway (IPBTS GW) The hardware
and software functionality in the RNC that provides the IPBH gateway to the BTS.
A BTS GW is IP based and interfaces through a GICC external GigE port.
Backhaul server (BHS) The logical representation of the upper and lower IPBTS
GW in a pair of GICCs in the RNC.
There is one IPBTS GW service per GICC pair (not allowed on SC-GICC).
HW/SW requirements
IPBTS GW characteristics:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-15
Issue 3, March 2006
See notice on first page
Both IPBTS GWs send periodic address resolution protocol (ARP) requests to the
first hop router to verify connectivity to the router
The call leg dynamic data is synchronized between the GICCs to facilitate
switchover and failover without losing stable call legs.
Legend:
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-16
Figure 2-6, 1X RNC shelf configuration for IP Backhaul (p. 2-18) shows the
configuration of the TPU shelf in the IP Backhaul RNC. The GICCs in slot 19 in the
upper and lower shelves provide backhaul server (BHS) functions:
The TPU shelf can have a mix of GICC 1.0s and GICC 1.1s
The SC-GICC (slot 3) always supports the A8/A9 and A10/A11 gateways and can
be equipped with ATM 5ESS DCS gateways
Slots 4, 19 and 20 can be equipped either as 5ESS DCS GWs or IPBTS GWs:
GICCs in these slots can support either ATM 5ESS DCS GW or IPBTS GW
only -- they cannot support both simultaneously
GICCs are equipped in pairs, both GWs in a pair can only support one gateway
type
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-17
Issue 3, March 2006
See notice on first page
IPBTS GWs are supported only on GICC 1.1 with a limit of one IPBTS GW
per GICC
ATM 5ESS DCS GWs are supported on GICC 1.0 and GICC 1.1 with a limit
of two 5ESS DCS GWs per GICC
GICC
User traffic is carried over Gigabit Ethernet links between the MSC adjacent switches
and RNC gateway intelligent carrier cards (GICCs). Each GICC that supports backhaul
has a single Gigabit Ethernet (GigE) link to an MSC adjacent switch.
BHS
As for BPHs, an active/standby pair of GICCs is also known to other network elements
as a single logical BHS.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-18
Figure 2-7, 1X RNC BHS processes (p. 2-19) shows the BHS server functionality
within the 1X RNC.
Figure 2-7 1X RNC BHS processes
The BHS represents a pair of IPBTS GWs and hides the internal 1X RNC IP Backhaul
architecture from the BTS and ECPC. The BTS and ECPC communicate only with the
BHS, and are not affected by switching between the IPBTS GWs. The RNC forwards
BHS status to the ECPC. This status reflects the status of the active IPBTS GW only.
If an IPBTS GW switchover occurs, the RNC BHS status simply represents the status
of the newly active IPBTS GW. The active IPBTS GW uses the BHS service IP
address to communicate and exchange bearer traffic with the BTSs.
Fault tolerance
GICCs that support backhaul are deployed in serving and non-serving pairs (1+1) for
improved reliability. A non-serving GICC can take over from the serving GICC without
loss of stable calls. When a non-serving GICC takes over, it assumes the IP address of
the serving GICC so this switchover is transparent to the other network elements
(ECPC and BTSs). A fault tolerant configuration has the serving and non-serving
GICCs of a pair connected to different adjacent switches as shown in Figure 2-1, IP
Backhaul network reference diagram (p. 2-2).
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-19
Issue 3, March 2006
See notice on first page
User
traffic protocols
.................................................................................................................................................................................................................................
Purpose
Figure 2-8, Bearer traffic protocol stacks (p. 2-20) shows the protocol scheme used
for bearer traffic in IPBH.
Figure 2-8 Bearer traffic protocol stacks
Name
Function
UDP
User traffic
Application layer protocol
LAPD
User traffic
Application layer protocol
Negotiates the setup of a particular voice channel
UDPMux
Allows several UDP packets to be bundled and sent together and later
de-multiplexed
Transport layer protocol
Lucent proprietary
CEFS L3 (Layer 3)
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-20
Table 2-2
Name
Function
T1/E1
UDP
IP
ML-PPP
(continued)
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-21
Issue 3, March 2006
See notice on first page
Signaling
traffic protocols
.................................................................................................................................................................................................................................
Purpose
Signaling traffic is carried on application layer connections over IP between URCs and
RCS-APs.
Protocol stacks
Figure 2-9, Signaling traffic protocol stacks (p. 2-22) shows the protocol scheme
used for control traffic in IPBH.
Figure 2-9 Signaling traffic protocol stacks
Name
Function
CCMS
Signaling Traffic
Cell Communication Manager
Application layer protocol
Runs from RCS-AP to URC
Protocols for message headers, message bodies, and extended message
headers
Lucent proprietary
TCP
IP
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-22
Table 2-3
Name
Function
ML-PPP
T1/E1
(continued)
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-23
Issue 3, March 2006
See notice on first page
DS1s
in IPBH
.................................................................................................................................................................................................................................
Efficient use of DS1s
Efficient use of DS1s dictates bundling of small traffic frames into larger IP packets.
Bundling spreads the User Datagram Protocol (UDP)/IP header overhead over many
frames. Of course, only traffic frames that are nearly simultaneous can be bundled
together.
The chosen protocol is called UDPMux because of the bundling (also called
multiplexing) of traffic frames into UDP datagrams. UDPMux is a proprietary
application layer that is transported over standard UDP/IP.
To preserve compatibility with FR backhaul, each traffic frame continues to be routed
within the soft-handoff network based on DLCI. For IP Backhaul, as a further DS1
efficiency improvement, the DLCI of each traffic frame is replaced over the backhaul
with a one byte value called a call identifier (CID). The CID is allocated during call
leg setup. The BHS performs the mapping between the one byte CID, which is used
between the BHS and BTS, and the data link connection identifier (DLCI), which is
used between the BHS and frame selector (FS), within the soft handoff network.
A UDPMux bundle is a standard UDP/IP datagram with a small UDPMux header
(application layer) and a sequence of traffic frames, each of which includes a CID and
length field:
For uplink traffic, the BTS creates UDPMux bundles from nearly simultaneous
traffic frames that are sent over a particular MLG to a particular BHS. The
receiving BHS parses out the individual traffic frames, restores the full DLCI for
each frame (based on the CID) and routes each frame to the destination FS based
on the DLCI (just like an FRPH).
For downlink traffic a BHS creates UDPMux bundles from nearly simultaneous
traffic frames destined to the same BTS and MLG. For each traffic frame, the BHS
inserts the CID based on address information from the frame selector. The
receiving BTS parses out the individual traffic frames and routes each frame to the
destination channel element based on the CID.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-24
Backhaul
server assignment and PSU2e/1X RNC engineering
.................................................................................................................................................................................................................................
Purpose
This section describes how the user traffic of a BTS is assigned to particular PSUs and
1X RNCs. To simplify switch engineering and thus minimize the amount of
provisioning required, data is provisioned at the MSC for each BTS that determines the
PSU2e(s) and/or RNC(s) to serve the user traffic of that BTS.
Carrier geographic clustering
For each BTS carrier, a PSU2e BHS is specified to serve the voice and data traffic
of that carrier:
The PSU2e is identified by its SM number (1-192) and PSU2e number (0 or 1).
The BHS is identified by its logical number within the PSU2e (1-10).
For each BTS, a primary and alternate DCS BHS may be specified to serve the
packet data traffic of the BTS for all carriers.
For each BTS, a primary and alternate RNC BHS may be specified to serve the
packet data traffic of the BTS for all carriers:
An RNC is identified by a logical number within the MSC (1- 15).
A BHS is identified by logical number within an RNC (1-3).
The alternate RNC BHS may be a different BHS on the same RNC as the primary, or
it may be a BHS on a different RNC than the primary.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-25
Issue 3, March 2006
See notice on first page
If no RNC or DCS BHS is specified for the data traffic, then the data traffic defaults
to the same PSU BHSs that are specified for the voice traffic. The alternate DCS or
RNC BHS is used for data traffic when the primary BHS is marked unavailable. The
alternate BHS is not used to relieve overload conditions on the primary BHS.
Important! Data off-load to the optional 1X RNC is not available in international
markets, however data can be off-loaded to a specific Backhaul Server (BHS).
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-26
IP
Addressing
.................................................................................................................................................................................................................................
Purpose
An Internet Protocol (IP) v4 address (IPBH uses the IPv4 address) is a 32-bit binary
number usually displayed as four octets in decimal, separated by periods.
The Internet is a collection of networks whose users communicate with each other via
addressing called the IP address (Internet Protocol address).
The IP address has two parts:
IP address requirements
The addresses used for IPBH are private IP addresses and will be used only between
the BTS and router, and the router and MSC. Therefore, the address ranges can be
duplicated on different MSCs in an IPBH network. Reserving a large chunk of
addresses will not affect an existing network if there are not conflicts within the
reserved addresses.
Private IP addresses used include:
Table 2-4
Network element
Max. # elements
Total size
BTS
600 BTSs
Static : 2 IP
addresses per MLG
RCS-AP
22 RCS-APs per
frame
2 IP addresses per
AP
28 Frames
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-27
Issue 3, March 2006
See notice on first page
Table 2-4
IP Addressing
(continued)
Network element
Max. # elements
Total size
5ESS DCS
10 BHS/PSU
2 + 1 VIP per
GICC pair
Two IP addresses are used per MLG, with 1 MLG per URC:
Each MLG requires a unique IP address. The router assigns this address
automatically during the network protocol negotiation phase of PPP link
initialization. The PPP Network Control Protocol (NCP) that enables dynamic
IP address assignment to a PPP endpoint is the IP Control Protocol (IPCP).
The router assigns IP addresses to MLGs from an address pool that is provisioned
at the router for all the MLGs that the router terminates.
BHS IP addresses are manually provisioned through the 5ESS DCS and 1X RNC
OA&M.
One IP subnet is used for all RCS-APs (control subnet) where:
Only the network ID of a control subnet is provisioned (no provisioning per
AP).
Only RCS-APs are addressable from the backhaul network.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-28
IP Addressing
During URC initialization, the URC queries the backhaul connection server
(BHCS) to discover the RCS-AP addresses:
IP addresses are manually provisioned through the 5ESS DCS and RNC.
There are 3 IP addresses per BHS: 1 service address seen by the ECPC and BTSs,
and one physical IP address per BPH/GICC.
1+1 pair of BHSs may be connected to separate adjacent switches for fault
tolerance.
RCS-AP IP addresses
The backhaul IP address of an RCS-AP interface is static and supports fault tolerant
networking.
No direct provisioning is done for the RCS-AP:
Each RCS-AP requires two IP addresses for backhaul, one for each of its Ethernet
interfaces:
One network prefix per MSC is provisioned for the control subnets: 2 control
subnets, 2 adjacent blocks with 1024 host IDs each.
The provisioned network ID and the APs logical number determine the two
addresses used by an RCS-AP.
The MSC requires 2 contiguous subnets with a total size of 2,048 host IDs.
Each control subnet corresponds to each half of the FMM-AP LAN.
Each RCS-AP takes two host IDs based on AP location (frame and slot):
Control subnets are further divided into per-frame subnets.
Frame subnet offset is determined by frame number.
Subnets per frame are required to route directly over the links to/from each
frame.
Only RCS-APs have addresses on the IPBH network.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
2-29
Issue 3, March 2006
See notice on first page
IP Addressing
The BPHs are paired in a 1+1 sparing arrangement for fault tolerance.
Three IP addresses are provisioned:
Two IP addresses are assigned for the BPHs. Each BPH in a backhaul server
(BHS) pair has an IP address. The BPHs in a BHS pair connect to different
MSC adjacent switches for fault tolerance.
A service address (virtual address) is also provisioned. The service address is
owned by the active BPH that is seen by both the ECPC and the BTS.
1X RNC IP address
1 service address (virtual address) is seen by the ECP, BTSs. The BHS address
seen by the ECP/BTSs floats between the GICCs; it is automatically assigned to
the serving GICC.
Each GICC in the pair is assigned one external physical IP address used for
monitoring the Ethernet link.
Internal addresses:
Note that the BHS service address and the GICC external physical IP addresses
must not overlap with the RNC internal address space:
The internal IP pool starting address and internal IP subnet mask can be viewed
on the TPU-GUI.
The defaults for the RNC internal addresses are:
IP pool start: 172.16.128.112
Shelf InternalIPSubnetMask: 255.255.192.0
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
2-30
I P Backhaul implementation
3
Overview
.................................................................................................................................................................................................................................
Purpose
3-3
Implementation of IPBH
3-3
3-6
3-9
3-13
3-14
3-17
3-18
3-20
3-32
FMM-RCS implementation
3-33
3-34
3-37
3-38
3-41
3-44
3-49
3-50
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-1
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Overview
Post deployment
3-51
3-51
3-52
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-2
IP Backhaul implementation
All IPBH implementation is done in phases from the MSC when the RMT capability at
the MSC feature is enabled:
Table 3-1
Phase
Activity
Pre-conversion
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-3
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Table 3-1
Implementation of IPBH
(continued)
Phase
Activity
Conversion
Post deployment
Converting a frame relay (FR) packet pipe backhaul to IP Backhaul requires changes to
both the MSC (ECPC, 5ESS DCS and RNC) and the BTS. Most changes to the IP
network, MSC and BTS can be executed before the final cutover, minimizing service
outage time.
Important! During conversion a URC will go out of service (OOS) for a time as
the RCS is restored.
During implementation, the following network elements are grown in, modified or
reconfigured:
Table 3-2
Network Element
Activity
Purpose
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-4
IP Backhaul implementation
Table 3-2
IP network
ECPC
Implementation of IPBH
(continued)
Update parameters.
5ESS DCS
BTS
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-5
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Pre-conversion:
Install IP network
.................................................................................................................................................................................................................................
Purpose
The network transport portion of the IPBH architecture resides between the cell sites
and the Mobile Switching Center (MSC). Its purpose is to transport traffic between the
cells and the MSC components. illustrates the general network topology in a duplex
configuration. The Automatic Protection Switching (APS) mechanism of Synchronous
Optical Network (SONET) is used to provide redundancy for router failure and OC3
link failure (Active OC3 and Protect OC3).
Figure 3-1 IPBH network topology
Configure routers and switches, then verify connectivity for the following interfaces:
between
between
between
between
between
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-6
IP Backhaul implementation
The following processes are done at the IP routers and switches for installation and
configuration:
1. Cell IP addressingdone locally on the edge router or on an external address
server (for example, DHCP)
2. Provision BHS connection IP address information
3. ML-PPP on the DS1 (T1/E1) interfaces
4. Traffic IP gateways (adjacent switches)
5. Control IP gateways (adjacent switches)
6. Interconnectivity between edge routers and adjacent switches.
7. Provision Diffserv properties (Diffserv codepoints and queuing properties)
8. Interface to router management system
9. Set IPBH enabled to y on the cell2 form.
History logging
The MLPPP consists of individual DS1s from the URCs aggregated into a Multi-link
Group (MLG). The MLG allows IP packets to traverse from the URC to the router.
The MLGs are concentrated into OC3s, and forwarded to the routers. There are
multiple OC3s that are linked to the routers. MLG size for the URC I varies from 1 to
4, for a URC II, the size varies from 1 to 8. Specific MLG size is determined by the
user.
At the DS1 concentrator, the MLGs from the URC are concentrated onto channelized
OC3 interfaces and mapped into a single OC3. The DS1 s that make up an MLG need
to be carried on the same OC3. The DS1 concentrator forwards the MLGs to the
routers.
The router is provisioned for the size of the MLG. Initial configuration occurs for the
MLG, then for the DS1 s.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-7
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Description
Value
Encapsulation
Multilink PPP
On
PFC, ACFC
Packet Header
compression
On
Minimum Links
IP Source address
Based on IP addressing
scheme
IP Destination add
Based on IP addressing
scheme
Non revertive
1+1
STS
Bidirectional APS
Reference
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-8
IP Backhaul implementation
IPBH
network elements checklist
.................................................................................................................................................................................................................................
Overview
Hardware requirements
Cabling requirements
Software requirements
Subnetwork and IP addressing requirements
The following table lists the new hardware required for IPBH when it is added to an
existing network.
Table 3-3
Network
element
New hardware
BTS
5ESS DCS
PSU2e, PHE3
FMM-RCS
AP
NA
1X-RNC
Two new
routers
Two
Switches
2 new AP PICs
Check
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-9
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
The following table lists the cables required for physically connecting IPBH network
elements.
Table 3-4
Connection
Cable type
T1
AP frame to L2 switch
Cat5
PHE-3 to L2 switch
Cat5e
1X RNC to L2 switch
MM fiber
Router to L2 switch
MM fiber
Router to PSAX
MM fiber
Check
The following lists the software that must be installed on each of the IPBH network
elements.
Table 3-5
Network element
Software
ECP
5ESS DCS
Check
RCS-AP (FMM-AP)
BTS
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-10
IP Backhaul implementation
Network element
Max. # elements
Total size
RCS-AP
3 AP*8 drawers
2 IP addresses per
AP
10 BHS/PSU
26 subnet addresses
per service module
(SM), each SM uses
one VLAN
15 RNCs
2 + 1 VIP per
GICC pair
BTS
12 UrcS/ BTS
600 BTSs
Static: 2 IP
addresses per MLG
Pair of subnet
addresses per URC,
30 subnet addresses
for static ML-PPP
address
28 Frames
5ESS DCS
64 SMs per DCS
(up to 192)
1X RNC
Dynamic: pool or
IP addresses per
MLG
21 subnet addresses,
two VLANS per APF
The AP control VLAN supports the signaling traffic between the backhaul cells and the
ECP. The following table lists the number of IP subnets needed for this VLAN. The
AP control VLAN requires three subnets, with a total of fourteen IP addresses.
Table 3-7
AP VLAN checklist
Subnetwork
Host
IP address
xxx.xxx.xx.a
BHCS
xxx.xxx.xx.a1
Router interface 1
xxx.xxx.xx.a2
Router interface 2
xxx.xxx.xx.a3
Default Gateway
xxx.xxx.xx.a4
FMM-RCS AP 1
xxx.xxx.xx.b5
FMM-RCS AP 2
xxx.xxx.xx.b6
Router interface 1
xxx.xxx.xx.b7
Router interface 2
xxx.xxx.xx.b8
Default Gateway
xxx.xxx.xx.b9
xxx.xxx.xx.b
Check
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-11
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Table 3-7
AP VLAN checklist
(continued)
Subnetwork
Host
IP address
xxx.xxx.xx.c
FMM-RCS AP 1
xxx.xxx.xx.c10
FMM-RCS AP 2
xxx.xxx.xx.c11
Router interface 1
xxx.xxx.xx.c12
Router interface 2
xxx.xxx.xx.c13
Default Gateway
xxx.xxx.xx.c14
Check
BHS VLAN
The BHS VLAN supports the BHSs on both the 5ESS DCS and the 1X-RNC. The
BHS VLAN carries the traffic packets as they are sent to the BHSs from the backhaul
cells and to backhaul cells from the BHSs. The BHS VLAN requires one subnet, with
a total of nine IP addresses.
The following table lists the IP subnets needed for this VLAN.
Table 3-8
Subnetwork
Host
IP address
xxx.xxx.xx.d
xxx.xxx.xx.d15
xxx.xxx.xx.e
xxx.xxx.xx.e16
xxx.xxx.xx.f
xxx.xxx.xx.f17
xxx.xxx.xx.g
xxx.xxx.xx.g18
xxx.xxx.xx.h
1X-RNC/TPU 1 to L2 switch
1
xxx.xxx.xx.h19
xxx.xxx.xx.i
1X-RNC/TPU 2 to L2 switch
2
xxx.xxx.xx.i20
xxx.xxx.xx.j
Router interface 1 to L2
switch 1
xxx.xxx.xx.j21
xxx.xxx.xx.k
Router interface 2 to L2
switch 2
xxx.xxx.xx.k22
xxx.xxx.xx.l
L2 switch 1 to L2 switch 2
xxx.xxx.xx.l23
Check
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-12
IP Backhaul implementation
This section describes the activities required for preparing the 5ESS DCS for IPBH
network.
Contents
Prepare 5ESS DCS for conversion
3-14
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-13
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Prepare
5ESS DCS for conversion
.................................................................................................................................................................................................................................
Install and configure new hardware and software
Installation and configuration on the 5ESS-DCS establishes the backhaul server (BHS)
for the IPBH network. Hardware and software installation are described in detail in the
5ESS-DCS documentation including the necessary requirements for connectivity
between the BHS at the 5ESS DCS and the IP Backhaul network.
All PHVs must be on ECP Release 24.0.
The following activities prepare the 5ESS DCS for IPBH configuration:
Reference
See the following sections in the 5ESS Switch Applications Manual, 235-200-100
(NAR) or :5ESS Switch Applications OA&M Manual, 5AP:
IPBH (PHE3) Provisioning,
IPBH (PHE3) Deprovisioning
PH Growth
PH Degrowth
See the following sections in the 5ESS Switch Flexent/ AUTOPLEX Wireless
Networks Applications OA&M Manual (5AP) International:
PHE3 Provisioning, PHE3 Deprovisioning
Deprovisioning Channel Groups
PHE3 Growth
PHE3 Degrowth
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-14
IP Backhaul implementation
Figure 3-2, 5ESS DCS provisioning for IPBH (p. 3-15) identifies the RC View
screens and activities in provisioning the 5ESS DCS.
Figure 3-2 5ESS DCS provisioning for IPBH
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-15
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
4. RC View 33.3 (90.6 INTL)BPH router attributes: For each BPH of the PH
group, define the router IP address.
5. RC View 22.32 (9.37 INTL)Assign BPHs to a PH group: Complete the PH
group definition by populating the BPH position of the 2 BPHs.
PSU growth
Note that the PSU unit must be grown before the protocol handlers.
See PSU Growth in 5ESS Switch Flexent /Autoplex Wireless Networks Applications
Manual, 235-105-231.
PHE3 growth
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-16
IP Backhaul implementation
This section describes the activities required for preparing the RNC as part of an IPBH
network.OMC-RAN user interface (p. 4-49)
Contents
1X RNC implementation overview
3-18
3-20
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-17
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
1X
RNC implementation overview
.................................................................................................................................................................................................................................
Requirements for setup
All PHVs and RNCs supporting cells in the soft handoff universe must be upgraded to
Release 25 or later.
When the optional RNC is used, the following activities must be completed prior to
starting any conversion activities:
1. If doing data offload, install RNC with R25 or later software.
2. Install and configure primary BHS (GICC pair) and optional secondary BHS on
RNC at the TPU-GUI. See Install and configure IPBTS GW hardware and
software (p. 3-18).
Install and configure IPBTS GW hardware and software
The RNCn installation and configuraiton for IPBH is done at the the 1X RNC, as
illustrated in Figure 3-3, 1X RNC provisioning for IPBH (p. 3-18). This includes
Installation and configuraiton of the the BHS on the IPBTS GW in the RNC to set up
the connectivity between the BHS (on the BHS GICDC) and the IP Backhaul network.
Figure 3-3 1X RNC provisioning for IPBH
GICC (upper)
Install IPBTS GW
GICC
Assign IPBTS GW
GICC
TPU-GUI
IPBTS GWUpper
Provision BHS IP
attributes
TPU-GUI
Provision GICC
IP attributes
TPU-GUI
BHS
IPBTS GW
Lower
GICC (lower)
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-18
IP Backhaul implementation
Installationinstall and cable the IPBTS GW GICC pair. See Physical GICC card
installation (p. 3-21).
Identify the IPBTS GW GICC at the TPU-GUIassign the GICC pair that will
provide the IPBTS GW function. See Add and configure GICC pair on TPU-GUI
(p. 3-22).
Provision GICC IP attributes at the TPU-GUIfor each LAN port, define its fixed
address for ARPs with the first hop router and IP address of the first hop router on
the BHS Level IPBH Parameters page.
Provision BHS IP attributesassign the BHS IP address and establish BHS loading
threshold parameters.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-19
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Install
IPBTS Gateway
.................................................................................................................................................................................................................................
When to use
Use this procedure to install the GICC for an IPBTS GW in an existing 1X RNC
network.
The following separate procedures are included:
1. Physical GICC card installation (p. 3-21)
2. Physically connect the cable (p. 3-22)
3. Add and configure GICC pair on TPU-GUI (p. 3-22)
GICC card redundancy
The GICC cards are grown in pairs starting with slot 20, then slot 4, and finally slot
19.
Required materials
GICC card(s)
Optical (OC3) fiber cables: OC3 may be Single-Mode Fiber (SMF) or Multi-Mode
Fiber (MMF), duplex or simplex, and crimp (ST) or push-pull coupling (SC).
Required interface
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-20
IP Backhaul implementation
Ask your network administrator for the values for the RNC Level IPBH
parameters, if necessary.
When replacing a GICC, always verify that the mate GICC to which you intend to
switch is not alarmed.
CAUTION
ESD hazard
To prevent damage to the integrated circuits on the cards, Electrostatic Discharge
Protection (EDP) must always be used.
Electrostatic Discharge (ESD) protective straps, shoes or mats must be used when
working with these cards.
To physically install a GICC card and connect the cables:
.................................................................................................................................................................................................
Run GigE cables from the 1X RNC cabinet to the L2 switch for each GICC in the
upper and lower shelf. The cable should be routed through the Frame Interface Panel
(FIP).
.................................................................................................................................................................................................
Begin installation of the GICCs in the upper shelf after confirming the installation slot
locations in the upper and lower shelves.
.................................................................................................................................................................................................
Hold the GICC replacement card vertical, and slide it firmly into the slot between the
two guides, then lock the upper and lower levers.
Result: The Power/Fault LED light turns green.
.................................................................................................................................................................................................
Connect the GICC connector cables. Change the heartbeat target IP address for the one
or two equipped GigE ports on the GICC to the routers IP address, and submit the
changes.
.................................................................................................................................................................................................
Tighten the card retention screw to anchor the card in the chassis.
.................................................................................................................................................................................................
Connect the GigE cable for PSU Gateway service. See Physically connect the cable
(p. 3-22) for instructions.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-21
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
.................................................................................................................................................................................................
Perform Step 4 through Step 6 for the GICC in the lower shelf.
E.................................................................................................................................................................................................
ND OF STEPS
Use this procedure to install GigE cable(s) prior to performing provisioning and
configuration procedures.
To install a GigE cable, do the following:
.................................................................................................................................................................................................
Run the GigE cable from the 1X RNC cabinet to the L2 switch. (The cable should be
routed through the Frame Interface Panel (FIP).
.................................................................................................................................................................................................
This procedure adds and configures the GICC card pairs through the TPU-GUI
Configuration Wizard.
To add and configure GICC cards:
.................................................................................................................................................................................................
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-22
IP Backhaul implementation
.................................................................................................................................................................................................
On the OMP Web tool bar on the left side of the page, use the drop-down list in
the upper left corner of the page to select the RNC to be configured.
On the 1X RNC TPU Web page, select Configuration Data.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-23
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
.................................................................................................................................................................................................
On the RNC Configuration Data page under Wizards, select GICC Growth.
Result: The Grow GICC - Warning Message page displays the following message:
GICCS should be grown in pairs.
Ensure that the GICCs are placed in the respective slots before proceeding.
Note that if the prerequisites have not been met and you continue to configure the
GICCs, alarms will be generated.
.................................................................................................................................................................................................
Select Next.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-24
IP Backhaul implementation
.................................................................................................................................................................................................
Find GICC # area on Shelf 1: Working GICCS for the slot being grown in.
By GICC Type, use the drop-down list and select IPBTS.
Find GICC # area on Shelf 2: Protection GICCS for the slot being grown in.
By GICC Type, use the drop-down list and select IPBTS.
Choose Next to continue.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-25
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
.................................................................................................................................................................................................
Choose Add, then enter the BHS IP address, subnet mask and UDP port.
.................................................................................................................................................................................................
Select Next.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-26
IP Backhaul implementation
.................................................................................................................................................................................................
Enter new critical threshold values for the displayed parameters if desired. If there is
no change, proceed to Step 9.
.................................................................................................................................................................................................
Select Next.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-27
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
The External IP packet Data Network page displays for you to review the GICC
information.
.................................................................................................................................................................................................
10
Select Next.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-28
IP Backhaul implementation
The Summary Page displays all the set up information ready for submission.
.................................................................................................................................................................................................
11
Select Submit.
Result The Confirm box displays the question: Are you sure you want to Grow
selected GICCs?
.................................................................................................................................................................................................
12
Select Yes.
Result The Message box displays: Request to grow GICC(s) processed
successfully!
.................................................................................................................................................................................................
13
Select OK.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-29
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
14
15
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-30
IP Backhaul implementation
.................................................................................................................................................................................................
16
Determine the state of the new GICC by reviewing the Admin State, Oper State and
Usage State.
Result The new GICC could be in any of the following states. The states vary
Oper State
Usage State
Unlocked
Enabled
Idle or Active
Locked
Enabled
Idle or Active
Unlocked
Disabled
Idle or Active
Locked
Disabled
Idle or Active
17
Admin StateLocked
Oper StateDisabled
Usage StateIdle
.................................................................................................................................................................................................
18
Perform an unlock of the GICC via the Commandscolumn of the TPU Network
Elements page
Result The GICC card is now in service.
END OF STEPS
........................................................................................................................................................................................................................
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-31
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
This section describes the activities required for preparing the FMM-AP and its
associated processors as part of an IPBH network.
Contents
FMM-RCS implementation
3-33
3-34
3-37
3-38
3-41
3-44
3-49
3-50
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-32
IP Backhaul implementation
FMM-RCS
implementation
.................................................................................................................................................................................................................................
Provision FMM-RCS for IPBH
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-33
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Provision
ecp form
.................................................................................................................................................................................................................................
Purpose
Use this procedure to provision fields on the ecp form that are associated with
converting the FMM-RCS (AP-RCS) to support IPBH.
ecp form-IPBH fields
Table 3-9, ecp form-IPBH fields (p. 3-34) lists all of the IPBH field, describes their
purpose and lists valid values for that field.
Table 3-9
Field name
Description
Valid
values
Restriction
IP Backhaul
Control
Network ID
0-255
IP Address part 1
IP Address part 2
IP Address part 3
IP Address part 4
BHCS
Failure
Reporting
Interval
0-60
minutes;
Default
Traffic
Diffserv
Codepoint
User Class
Traffic
Diffserv
Codepoint
0-63
Signaling
Class Traffic
Diffserv
Codepoint
0-63
Default=15
minutes
Default=0
Default=46
Default=10
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-34
IP Backhaul implementation
Table 3-9
(continued)
Field name
Description
Valid
values
Restriction
Backhaul
Connection
Server Lan0
IP address
0-255
Backhaul
Connection
Server Lan1
IP address
Lan0
Backhaul
Connection
Server
Gateway IP
Address
Lan1
Backhaul
Connection
Server
Gateway IP
Address
0-255
0-255
0-255
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-35
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
You must know the fields and valid values needed for converting the AP-RCS to
support IPBH.
Refer to the frequency and impacts of performing this procedure
Frequency
Lucent Technologies does not recommend changing the IP Backhaul Control Network
ID field except during a scheduled retrofit.
Impacts
Changing the IP Backhaul Control Network ID field while the system is running may
cause the IP addressing for the APs, BHCS, and ECP to become out of sync. To
correct this problem, a system restart is needed. Lucent Technologies recommends
changing this field only during a scheduled retrofit as a system restart is already
planned.
Procedure
.................................................................................................................................................................................................
Populate the IPBH fields as given in Table 3-9, ecp form-IPBH fields (p. 3-34).
E.................................................................................................................................................................................................
ND OF STEPS
Result
The first step of provisioning the FMM-RCS (AP-RCS) for IPBH is complete. Go to
Configure FMM-RCS IP Integrity Manager (p. 3-37) for the next procedure.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-36
IP Backhaul implementation
Configure
FMM-RCS IP Integrity Manager
.................................................................................................................................................................................................................................
Purpose
Use this procedure to configure the RCS-IP integrity manager (IM). This procedure
must be done before provisioning the apeqp form.
The RCS-IM
The IP Backhaul Control Network ID field must be provisioned on the ecp form. See
Provision ecp form (p. 3-34).
Procedure
.................................................................................................................................................................................................
Result
The RCS-IM has been configured. Continue with Provision apeqp form (p. 3-38).
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-37
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Provision
apeqp form
.................................................................................................................................................................................................................................
Purpose
Use this procedure to provision the IPBH related fields on the apeqp form.
apeqp form-IPBH fields
Table 3-10, apeqp form-IPBH fields (p. 3-38) lists all of the IPBH fields used on the
form, describes their purpos,e and lists valid values for that field.
Table 3-10
Field
Description
Valid values
RCS IP Services
Enabled
Y or N
RCS-IM Exists
Y or N
0-255
Interface 0
Backhaul IP
Address
Interface 1
Backhaul IP
Address
IP Address part 1
IP Address part 2
IP Address part 3
IP Address part 4
Default = n
Default = n
Default = 0
0-255
IP Address part 1
IP Address part 2
IP Address part 3
IP Address part 4
Default = 0
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-38
IP Backhaul implementation
Table 3-10
(continued)
Field
Description
Valid values
Lan0 Default
Gateway IP
Address
0-255
Lan1 Default
Gateway IP
Address
IP Address part 1
IP Address part 2
IP Address part 3
IP Address part 4
Default = 0
0-255
IP Address part 1
IP Address part 2
IP Address part 3
IP Address part 4
Default = 0
You know the fields and valid values needed for converting the FMM-RCS to
support IPBH.
The IP Backhaul Control Network ID field has been provisioned on the ecp form
The RCS IM has been configured.
Procedure
.................................................................................................................................................................................................
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-39
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
All other fields on the apeqp form are based on data entered on the ecp form. See
Provision ecp form (p. 3-34) for entry of ecp information for IPBH.
.................................................................................................................................................................................................
Save and exit the form. For complete information on all fields on this screen, see Table
3-10, apeqp form-IPBH fields (p. 3-38).
E.................................................................................................................................................................................................
ND OF STEPS
Result
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-40
IP Backhaul implementation
Retrieve
Backplane Serial Number (BPSN)
.................................................................................................................................................................................................................................
Purpose
Use this procedure to run the command to retrieve the backplane serial numbers
(BPSN) and place it in the cdmeqp database.
The BPSN is on the BTS at the cellsite, and is unique per assemblage. During cell
initialization, an IP-based cell passes this number to the MSC, where the MSC
compares it to the BPSN stored at the MSC.
Before you begin
This procedures requires an active signalling link to cells that are on Release 25 or
later.
User interface
This procedure requires execution of TICLI commands from either the TICLI or the
OMC-RAN TICLI.
Procedure
.................................................................................................................................................................................................
then enter
where
UPDATE:CELL x, BPSN
where x=cell
number.
UPDATE:AP y, BPSN
where y=AP
number.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-41
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Result: The valid BPSN of the cell is inserted into the cdmeqpdb file and the
a failure was
reported
displays only the BPSN information from the database for the
cell.
Successful
The following output example is from the UPDATE: AP command. Each character in
an invalid BPSN is represented by two hex digits.
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
UPDATE:AP 31,BPSN! IN PROGRESS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
CELL ASMB BPSN
ACTION PERFORMED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
144 1
0x0b07090c0b0b0b0b0b0b0b41
RECD INVALID
1234567890123456789012345678901212345678901234567890123456789
BPSN
FROM
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
CELL, DB NOT UPDATED
1234567890123456789012345678901212345678901234567890123456789
150 1
sprcs0000150
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
151 1
sprcs0000151
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
152
1
sprcs0000152
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
153 1
sprcs0000153
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
154
1
sprcs0000154
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
155 1
sprcs0000155
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
156 1
sprcs0000156
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
157 1
0x0b07090c0b0b0b0b0b0b0b41
RECD INVALID BPSN FROM
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
CELL,
DB
NOT
UPDATED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
158 1
sprcs00158a1
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
158 2
sprcs00158a2
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
159
1
sprcs00159a1
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
159
2
sprcs00159a2
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
160 1
sprcs00160a1
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
160 2
sprcs00160a2
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
161
1
sprcs00161a1
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ORIGINATING COMMAND #329979115.3
1234567890123456789012345678901212345678901234567890123456789
2005-04-13 09:56:52 REPORT #000001
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
EXECUTED ON PROCESSOR: AP 35
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The following are some of the BPSN update error messages:
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-42
IP Backhaul implementation
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
BPSN READ FROM DB, CELL DID NOT RESPOND
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
BPSN BLANK IN DB, CELL DID NOT RESPOND
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
BPSN UPDATED IN DB
1234567890123456789012345678901212345678901234567890123456789
BPSN BLANK IN DB, CELL RELEASE IPBH INCOMPAT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
BPSN BLANK IN DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
BPSN READ FROM DB, CELL NOT ACTIVE
1234567890123456789012345678901212345678901234567890123456789
BPSN BLANK IN DB, CELL FAILED TO GET BPSN
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
BPSN READ FROM DB, CELL FAILED TO GET BPSN
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RECD DUP OF BPSN FOR CELL:130, ASM:1, DB NOT UPDATED
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
The first part of converting the FMM-RCS is now complete. Continue
configuration with Provision cell2 form (p. 3-44).
END OF STEPS
........................................................................................................................................................................................................................
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-43
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Provision
cell2 form
.................................................................................................................................................................................................................................
Purpose
Use this procedure to provision fields associated with converting the FMM-RCS to
support IPBH on the cell2 form.
Related information
The user entering information on the cell2 form should be aware of the fields and valid
values needed for converting the FMM-RCS to support IPBH.
To use an RNC: Data offload must be on and a data offload RNC defined. The
backhaul offload BHS is separate from the BHS defined on the SOC table. The
backhaul offload BHSs can be provisioned on either RNCs or 5ESS DCSs, but not
both simultaneously.
Important! Data off-load to the optional 1X RNC is not available in international
markets, however data can be off-loaded to a specific Backhaul Server (BHS).
cell2 form-IPBH fields
Table 3-11, cell2 form-IPBH fields (p. 3-44) lists all of the IPBH field, describes
their purpose and lists valid values for that field.
Table 3-11
Field
Description
Valid values
Restrictions
IP Backhaul Enabled
Y or N
Backhaul Offload
Y or N
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-44
IP Backhaul implementation
Table 3-11
(continued)
Field
Description
Valid values
Restrictions
Blank, 1-15,
step by 1
Blank, 1-3
Blank, 1-192
Blank, 0 or 1
Blank, 1 to 10
Blank, 1 to 15
Blank, 1-3
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-45
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Table 3-11
(continued)
Field
Description
Valid values
Restrictions
Alternate Switching
Module Number (SM)
Blank, 1 to 192
Blank, 0 or 1
Blank, 1-10
0 to 100% in
increments of
10
Blank, Voice,
Both
(View-only)
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-46
IP Backhaul implementation
Table 3-11
(continued)
Field
Description
Valid values
Restrictions
Blank, 1 to 192
Blank, 0 or 1
Blank, 1 to 10
The ecp form has been provisioned with the IP Backhaul Control Network ID
field. See Provision ecp form (p. 3-34).
The IPBH RTU feature qualifier value must be large enough to add the additional
carriers equipped for the cell.
The RCS-IP IM has been configured. See Configure FMM-RCS IP Integrity
Manager (p. 3-37).
The btseqp/cdmeqp form must be set for Backhaul mode. See Provision btseqp
form (p. 3-50) and Provision cdmeqp form (p. 3-49).
The apeqp form has been provisioned with the RCS-IP Services Enabled and
RCS-IM Exists fields. See Provision apeqp form (p. 3-38).
The BPSNs have been retrieved from the cells and the btseqp/cmdeqp database
has been updated. See Retrieve Backplane Serial Number (BPSN) (p. 3-41) and
Provision cdmeqp form (p. 3-49).
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-47
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Procedure
.................................................................................................................................................................................................
Advance to the CDMA Cell Site for IP Backhaul Information Only screens.
.................................................................................................................................................................................................
Populate the IPBH fields as described in Table 3-11, cell2 form-IPBH fields
(p. 3-44).
END OF STEPS
........................................................................................................................................................................................................................
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-48
IP Backhaul implementation
Provision
cdmeqp form
.................................................................................................................................................................................................................................
Purpose
Use this procedure to provision fields associated with converting the RCS to support
IPBH on the cdmeqp form. This form is used for Modular cells 1, 2, and 3.
Related information
The user entering information on the cdmeqp form should be aware of the fields and
valid values needed for converting the RCS to support IPBH.
cdmeqp form-IPBH fields
Table 3-12, cdmeqp form-IPBH fields (p. 3-49) lists all of the IPBH fields, describes
their purpose and lists valid values for each field.
Table 3-12
Field
Description
Valid values
Backhaul Mode
Procedure
.................................................................................................................................................................................................
Populate the Backplane Serial Number if it was not previously populated using the
UPDATE:CELL x, BPSN TICLI command.
.................................................................................................................................................................................................
Enter the value IP in the Backhaul mode field. See Table 3-12, cdmeqp form-IPBH
fields (p. 3-49) for a list of valid values for IPBH fields.
END OF STEPS
........................................................................................................................................................................................................................
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-49
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Provision
btseqp form
.................................................................................................................................................................................................................................
Purpose
Use this procedure to provision fields associated with converting the FMM-RCS to
support IPBH on the btseqp form. This form is used for One-BTS cells.
Related information
The user entering information on the btseqp form should be aware of the fields and
valid values needed for converting the FMM-RCS to support IPBH.
btseqp form-IPBH fields
Table 3-13, btseqp form-IPBH fields (p. 3-50) lists all of the IPBH fieldS, describes
their purpose and lists valid values for each field.
Table 3-13
Field
Description
Valid values
Backplane Serial
Number
Backhaul Mode
Procedure
.................................................................................................................................................................................................
Enter the value IP in the Backhaul mode field for each CMD/CRC. See Table 3-13,
btseqp form-IPBH fields (p. 3-50) for a list of valid values for IPBH fields.
.................................................................................................................................................................................................
........................................................................................................................................................................................................................
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-50
IP Backhaul implementation
Post deployment
Post
deployment activities
.................................................................................................................................................................................................................................
Reclaiming FR resources
Delete all the packet pipe trunk group member records for the cells packet pipe
trunk group in the cmodpptm form.
Delete the related record in pptg form.
Update the record for the cell in cdmeqp/btseqp form:
The fields in cdmeqp are: AP Signaling Link Information for Connections at
the AP, Digital Module Link Information for Connections at the CDM, CDM
Digital Module DS1 Information (Signaling Type and Signaling/PP Data Rate),
and Signaling Link Width.
The fields in btseqp are: Digital Module Signaling Link Information for
Connections at the CDM, AP Signaling Link Information for Connections at
the AP, CDM Digital Module DS1 Info (Type and Data Rate), and Signaling
Link Width.
Update the cell2 form to blank the CDMA Packet Pipe Trunk Group field.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
3-51
Issue 3, March 2006
See notice on first page
IP Backhaul implementation
Delete
DS1/DS0s used with FR-based FMM-RCS
.................................................................................................................................................................................................................................
Purpose
Use this procedure to delete DS1/DS0s that were associated with a LAPD/FR-based
RCS that has been converted to IPBH. These deleted DS1/DS0s can then be used for
other purposes.
Required activities
The apeqp form must be cleaned up manually once all the LAPD-based cells using
DS1s supported by a particular AP have been converted to IP and committed. The
commit does not do this step.
Before you begin
Save and exit the form. For complete information on all fields on this screen, see Table
3-10, apeqp form-IPBH fields (p. 3-38).
END OF STEPS
........................................................................................................................................................................................................................
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
3-52
Overview
.................................................................................................................................................................................................................................
Purpose
4-2
Router/switch OA&M
4-2
BTS OA&M
4-3
4-3
MSC
4-5
FMM-AP OA&M
4-5
1X RNC OA&M
4-6
4-11
ECPC OA&M
4-21
4-29
4-38
OMC-RAN
4-48
4-48
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-1
Issue 3, March 2006
See notice on first page
This section describes OA&M activities for routers and mobile switching center (MSC)
adjacent switches.
OA&M activities
See your vendor documentation for details on OA&M activities for your selected
routers and switches. Ask your Lucent representative about VRAD-5576 for specific
requirements for routers and switches.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-2
BTS OA&M
BTS
OA&M for IPBH
.................................................................................................................................................................................................................................
Purpose
This section describes OA&M activities for the base transceiver station (BTS).
IPBH within the BTS
Some BTS data for IP mode can be entered while the BTS is live on frame relay
(FR).
Each BTS is assigned a primary and alternate radio cluster server application
processor (RCS-AP).
Each BTS is configured to use the desired set of backhaul servers (BHS).
BHS IP addresses are provisioned only at the 5ESS DCS and 1X RNC.
The ECPC selects the BHS that interfaces with a cell.
BHS re-assignments can be done while a BTS is live.
RCS-AP and BHS assignments and re-assignments do not require re-configuration
of transport facilities.
The following OA&M additions and modifications have been made for IPBH:
IP mode data added to existing RC/V forms: See ECPC OA&M (p. 4-21).
Modified Technician Interface Commands: See Input/Output commands and
messages (p. 4-29).
New and Modified Status Display Pages: See Status display pages (p. 4-38).
BTS IPBH Service Measurements: See Chapter 6, IPBH performance measures.
DS1 Monitoring and recovery.
The remote maintenance terminal (RMT) is software that runs on a personal computer
that can then communicate to the BTS. The RMT software communicates with
software running on the cell, and provides the ability to perform various diagnostic
functions. This communication occurs through an Ethernet connection. The full
installation RMT software version is required to reconfigure a BTS from FR to IPBH
remotely. This document assumes that the user is familiar with the use of the RMT for
BTS maintenance activities.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-3
Issue 3, March 2006
See notice on first page
Remote access allows the RMT to communicate with a URC in a cell through the
LAN connection of any FMM-AP on the same LAN as the AP managing the cell
without having to make a cell site visit. To communicate remotely via RMT, the user
connects the PC or laptop computer with the RMT software to the LAN of an AP that
serves a particular BTS. When communication is established, RMT commands can be
executed.
The connection status is logged using existing logging mechanisms. RMT can be
connected to any FMM-AP frame that is configured as an RCS-AP.
DS1 monitoring and recovery
BER Major Alarm Indicates that BER exceeds the major threshold
(default=5x10^-5)
BER Minor Alarm References the major BER alarm threshold for threshold level
for minor alarm threshold (default threshold equals ten times less than major alarm
threshold)
Important! This threshold is tunable by Lucent Technologies. Contact your account
representative for assistance.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-4
MSC
FMM-AP
OA&M
.................................................................................................................................................................................................................................
Purpose
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-5
Issue 3, March 2006
See notice on first page
1X
RNC OA&M
.................................................................................................................................................................................................................................
Purpose
This section discusses IPBH changes to OA&M for the 1X Radio Network Controller
(RNC).
IPBTS GW on the 1X RNC
The IP Backhaul BTS gateway (IPBTS GW) is hosted on a GICC pair in the RNC.
Each GICC pair hosts the active and standby backhaul servers (BHSs) that provide
data offload capability.
The following additions and modifications have been made for IPBH:
IP mode data is added to existing RC/V forms for RNC provisioningSee RC/V
forms updated for IP Backhaul (p. 4-21).
Modified Technician Interface CommandsSee Input/Output commands and
messages (p. 4-29) for information on new 1X RNC output messages that report
BHS traffic overload, BHS port usage limit, and BHS dropped packet threshold
crossings.
New and modified traffic processing unit-graphical user interface (TPU-GUI)
screensSee IPBH provisioning at the RNC (p. 4-6).
IPBH Service MeasurementsSee Service measurements (p. 6-1).
The 1X RNC is provisioned initially using the TPU-GUI First Time Wizard that
takes the user step-by-step through RNC provisioning.
New TPU-GUI pages:
The IPBTS is the selected GICC configuration type on the RNC Configuration
Data Screen.
BHS Level IPBH Parameters.
RNC Level IPBH Parameters.
Provisioning order
1X RNC provisioning for IPBH occurs for the IPBTS GW GICC pair:
1. Installationinstall and cable the IPBTS GW GICC pair.
2. Identify IPBTS GW GICC at the TPU-GUIassign the GICC pair that will provide
the IPBTS GW function.
3. Provision GICC IP attributes at the TPU-GUIfor each LAN port, define its fixed
address for ARPs with the first hop router and IP address of the first hop router.
4. Provision BHS IP attributesassign BHS IP addresses and establish BHS loading
threshold parameters.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-6
1X RNC OA&M
TPU-GUI screens
IPBH affects only a small number of TPU-GUI screens. For all other TPU-GUI
screens, refer to the Flexent Wireless Networks 1X RNC OA&M Manual
(401-710-082).
1X RNC configuration data
The RNC Configuration Data Screen provides two new links for BHS Level IPBH
Parameters and RNC Level IPBH Parameters.
Figure 4-1 RNC Configuration Data
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-7
Issue 3, March 2006
See notice on first page
1X RNC OA&M
BHS Level IPBH Parameters allow the user to change the BHS Service IP Address,
BHS Service Subnet Mask and BHS Service UDP Port for a configured IPBTS GICC
Pair.
Figure 4-2 BHS Level IPBH Parameters
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-8
1X RNC OA&M
RNC Level IPBH Parameters allow the user to enter and modify:
Input/Output commands
Commands that are specific to the 1X RNC/TPU can be initiated either from the
TPU-GUI or TPU-CLI.
Table 4-1
Command
Description
GET:RNC-TPU-STATE
SHUTDOWN:RNC-TPU
GET:RNC-BHS-INFO
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-9
Issue 3, March 2006
See notice on first page
Table 4-1
1X RNC OA&M
(continued)
Command
Description
LOCK-RNC-TPU
See Input/Output commands and messages (p. 4-29) for additional information about
these inputs and outputs.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-10
5ESS
DCS OA&M
.................................................................................................................................................................................................................................
Purpose
IP Backhaul is supported on BHSs hosted on the 5ESS DCS. This section describes
OA&M functions for both NAR and INTL markets.
5ESS DCS changes for IPBH
The following additions and modifications have been made for IPBH:
New and modified 5ESS DCS status display pageSee Status display pages
(p. 4-38).
New 5ESS-DCS traffic measurementsSee Service measurements (p. 6-1).
Note that the 1X RNC refers to the IPBTS gateway that connects the BTS to the
backhaul server (BHS) in the RNC. The gateway from the the 5ESS to the BTS is
simply referred to as the BHS gateway.
BHS GW characteristics:
Failover
Ethernet failure
Loss of connectivity to 1st hop router
Unrecoverable HW and SW faults
The non-serving BPH, once it becomes the serving BPH, will send a gratuitous ARP
for the serving IP address and start processing the traffic. All the stable call legs are
preserved over the failover.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-11
Issue 3, March 2006
See notice on first page
The BPH maintenance states are reported on MCC 1188 and MCC 118 [0-4].
See Status display pages (p. 4-38) to view samples of these pages.
Traffic Measurements
See Chapter 6, IPBH performance measures for details on these modified reports.
5ESS DCS RC Views for IPBH provisioning
The following RC Views are used to provision IP backhaul in the 5ESS DCS:
Table 4-2
NAR
INTL
Description
22.32
9.37
PHGRP
33.1
90.5
BPH IP attributes
IPPRC
33.3
90.6
IPRTE
RC View 33.4
90.7
IPETH
The following RC Views are used to provision IP backhaul in the 5ESS DCS.
RC View 22.32
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-12
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN
1
OF
4
RECENT
CHANGE 22.32
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(5892)
PROTOCOL HANDLER GROUP DEFINITION
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*1. SM
___
GENERAL PARAMETERS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*2.
PSU
_
SECONDARY
ADDR
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*3. PH GROUP __
12. PKT BUS INTRVL
____
1234567890123456789012345678901212345678901234567890123456789
4. APP TYPE ________
13. L1 OVRLD THRESHOLD __
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
14. L2 OVRLD THRESHOLD __
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5. PROTOCOL HANDLERS (PHLIST)
15. CONN CHK ENABLED
_
1234567890123456789012345678901212345678901234567890123456789
CHL
PH
16.
CON
CHK
HIGH
INT
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ROW PH SHELF GRP POSITION TYPE
17. CON CHK LOW INT
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1
0
_
__
__
____
18. CONN CHK MAX FAIL __
1234567890123456789012345678901212345678901234567890123456789
2
1
_
__
__
____
19. SW OVR TIMER
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Figure 4-5 RC View 22.32 (NAR): Protocol Handler Group Definition 2 of 4
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN 2 OF 4
RECENT CHANGE 22.32
1234567890123456789012345678901212345678901234567890123456789
(5892)
PROTOCOL HANDLER GROUP DEFINITION
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
GENERAL PARAMETERS cont.
IP BACKHAUL PARAMETERS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
20. DIFF SRV CODE POINT __
25. BHA BASE UDP PORT _____
1234567890123456789012345678901212345678901234567890123456789
21. RCV ICMP THRSH
___
26. BHA PRE PORT
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
22. AVG DELAY THRESHOLD ______
27. BHA QUALITY
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
23. PCT DELAY THRESHOLD ______
28. BHA INACT TIMER
__
1234567890123456789012345678901212345678901234567890123456789
24. DELAY PERCENTAGE
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-13
Issue 3, March 2006
See notice on first page
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
SCREEN
3
OF
4
RECENT
CHANGE 22.32
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(5892)
PROTOCOL
HANDLER
GROUP DEFINITION
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IPSHO PARAMETERS
40. IP TRAFFIC STATE _
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
29.
EXT
L1
OVRLD
THRESHOLD
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
30. EXT L2 OVRLD THRESHOLD __
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
31. HIGH DSCP
__
1234567890123456789012345678901212345678901234567890123456789
32. LOW DSCP
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
33.
OAM
DSCP
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
HIGH UDP
_____
1234567890123456789012345678901212345678901234567890123456789
LOW UDP
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
OAM
UDP
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
NETWORK TEST UDP
_____
1234567890123456789012345678901212345678901234567890123456789
38. HEART BEAT FREQ
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
39. HEART BEAT LDI
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Figure 4-7 RC View 22.32 (NAR): Protocol Handler Group Definition 4 of 4
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
SCREEN 4 OF 4
RECENT CHANGE 22.32
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(5892)
PROTOCOL HANDLER GROUP DEFINITION
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
NPH PARAMETERS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
41. UDP START PORT _____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
42. UDP BLOCK SIZE ____
1234567890123456789012345678901212345678901234567890123456789
43. NPH QUALITY
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
44.
BNID
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-14
RC View 33.1
Figure 4-8 RC View 33.1 (NAR): IP Processor Assignment 1 of 3
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN
1
OF
3
RECENT
CHANGE 33.1
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(5987)
INTERNET PROTOCOL (IP) PROCESSOR ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*1. PROCESSOR ID
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*2. PROCESSOR TYPE ___
1234567890123456789012345678901212345678901234567890123456789
(*)3. QUALIFIER 2
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(*)4.
QUALIFIER
3
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5. IP ADDRESS
1234567890123456789012345678901212345678901234567890123456789
ROW
LOCAL
IP
ADDR
IP SUBNET MASK
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1
___.___.___.___
___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
2 ___.___.___.___ ___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
3 ___.___.___.___ ___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
4 ___.___.___.___ ___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5 ___.___.___.___ ___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Figure 4-9 RC View 33.1 (NAR): IP Processor Assignment 2 of 3
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
SCREEN
2
OF
3
RECENT
CHANGE 33.1
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(5987)
INTERNET PROTOCOL (IP) PROCESSOR ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP PARAMETER ASSIGNMENT
UDP PARAMETER ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
16.
REASSEM
TIMER
___
24. UDP CHKSUM EN _
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
17. ICMP ERR CNT ___
25. UDP START PORT _____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
18. MTU ENABLE
_
26. UDP DEF TTL
___
1234567890123456789012345678901212345678901234567890123456789
19. MTU DISC
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
20. OVLD TRIG
__
ARP PARAMETER ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
27. REFRESH INTRVL ___
1234567890123456789012345678901212345678901234567890123456789
TCP PARAMETER ASSIGNMENT
28. CLEANUP INTRVL ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
21. TCP MSS
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
22.
TCP
START
PORT
_____
29. PM GROUP ________
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
23. TCP DEF TTL
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-15
Issue 3, March 2006
See notice on first page
Figure 4-10 RC View 33.1 (NAR): Internet Protocol (IP) Processor Assignment 3
of 3
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
SCREEN
3
OF
3
RECENT
CHANGE 33.1
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(5987)
INTERNET PROTOCOL (IP) PROCESSOR ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#32. ICMP ERR GEN
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#33.
IP
FRAGMENT
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#34. MTU INTVL AFT FAIL ____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RC View 33.3
Figure 4-11 RC View 33.3 (NAR): IP Processor Routing to Interface
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RECENT CHANGE 33.3
1234567890123456789012345678901212345678901234567890123456789
(5989)
INTERNET PROTOCOL (IP) ROUTING TO INTERFACE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*1. DEST IP ADDR
___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
*6. INTERFACE NAME ___________________
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
7. NET OR HOST
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
8. IP SUBNET MASK ___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
#13. GATEWAY IP ADDR ___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
18. ROUTE METRIC
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RC View 33.4
Figure 4-12 RC View 33.4 (NAR): IP Interface Assignment 1 of 2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN
1
OF
2
RECENT
CHANGE 33.4
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(5995)
ETHERNET INTERNET PROTOCOL (IP) INTERFACE
1234567890123456789012345678901212345678901234567890123456789
ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*1. SM
___
1234567890123456789012345678901212345678901234567890123456789
*2. PSU
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*3.
SHELF
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*4. CHANNEL GROUP __
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#5. INTERFACE NAME ___________________
1234567890123456789012345678901212345678901234567890123456789
6. PHE LINK
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-16
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS SWITCH
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN
2
OF
2
RECENT
CHANGE 33.4
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
(5995)
ETHERNET INTERNET PROTOCOL (IP) INTERFACE
1234567890123456789012345678901212345678901234567890123456789
ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#7. GATEWAY IP ADDRESS 1 ___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
#12. IP SUBNET MASK 1
___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
17.
GATEWAY
IP
ADDRESS
2
___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
22. IP SUBNET MASK 2
___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
27. MCAST ADDR ___.___.___.___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
32. MTU SIZE
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
33. RATE
____
1234567890123456789012345678901212345678901234567890123456789
34. MODE
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5ESS DCS RC Views for IPBH provisioning (INTL)
The following RC Views are used to provision IP backhaul in the 5ESS DCS.
RC View 9.37
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-17
Issue 3, March 2006
See notice on first page
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN 1 OF 2
RECENT CHANGE - 9.37 PHGRP
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
PROTOCOL
HANDLER
GROUP DEFINITION
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*1. SM
___
#13. L1 OVRLD
1234567890123456789012345678901212345678901234567890123456789
THRESHOLD
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*2.
PSU
_
#14. L2 OVRLD
1234567890123456789012345678901212345678901234567890123456789
THRESHOLD
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*3. PH GROUP
__
#15. CONN CHK
1234567890123456789012345678901212345678901234567890123456789
ENABLED
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#4. APP TYPE
________
#16. CONN CHK
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
INTRVL
__
1234567890123456789012345678901212345678901234567890123456789
#17. CONN CHK INTRVL
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
LOW
___
1234567890123456789012345678901212345678901234567890123456789
5. PROTOCOL HANDLERS
#18. CONN CHK MAX
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
FAIL
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SHELF CHL GRP POSITION PH TYPE
#19. SW OVR
1234567890123456789012345678901212345678901234567890123456789
TIMER
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1)
_
__
__
____
#20. DIFF SVR CODE
1234567890123456789012345678901212345678901234567890123456789
POINT
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
2)
_
__
__
____
#21. RCV ICMP MSG
1234567890123456789012345678901212345678901234567890123456789
THRHLD
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#22. INHIBIT CALL
1234567890123456789012345678901212345678901234567890123456789
PROC
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
&11. SECONDARY ADDR
___
23. DEBUG
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
FLAGS
________
1234567890123456789012345678901212345678901234567890123456789
#12. PKT BUS INTRVL
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Figure 4-15 RC View 9.37 (INTL): Protocol Handler Group Definition 2 of 2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN 2 OF 2
RECENT CHANGE - 9.37 PHGRP
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
PROTOCOL HANDLER GROUP DEFINITION
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP BACKHAUL PARAMETERS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
24. BHA BASE UDP PORT
_____
1234567890123456789012345678901212345678901234567890123456789
25. BHA PRE UDP PORT
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
26.
BHA
QUALITY
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
27. BHA INACT TIMER
__
1234567890123456789012345678901212345678901234567890123456789
28. UDPMUX BUNDLE SZ
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
29. UDPMUX BUNDLE TMR 1
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
30. UDPMUX BUNDLE TMR 2
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-18
RC View 90.5
Figure 4-16 RC View 90.5 (INTL): IP Processor Assignment 1 of 2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN 1 OF 2
RECENT CHANGE - 90.5 IPPRC
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP PROCESSOR ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*1. PROCESSOR ID
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*2. PROCESSOR TYPE
__
1234567890123456789012345678901212345678901234567890123456789
+3. QUALIFIER 2
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
+4.
QUALIFIER
3
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5. IP ADDRESS
1234567890123456789012345678901212345678901234567890123456789
LOCAL IP ADDR
IP SUBNET MASK
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1)
___
___
___
___
___
___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
2) ___ ___ ___ ___ ___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
3) ___ ___ ___ ___ ___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
4) ___ ___ ___ ___ ___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
5) ___ ___ ___ ___ ___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Figure 4-17 RC View 90.5 (INTL): IP Processor Assignment 2 of 2
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN 2 OF 2
RECENT CHANGE - 90.5 IPPRC
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP PROCESSOR ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP PARAMETER ASSIGNMENT
UDP PARAMETER ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
16.
REASSEM
TIMER
___
23.
UDP CHKSUM EN
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
17. ICMP ERR CNT
___
24. UDP START PORT
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
18. MTU ENABLE
_
25. UDP DEF TTL
___
1234567890123456789012345678901212345678901234567890123456789
19. MTU DISC
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ARP PARAMETER ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
TCP PARAMETER ASSIGNMENT
26. REFRESH INTRVL
__
1234567890123456789012345678901212345678901234567890123456789
20. TCP MSS
____
27. CLEANUP INTRVL
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
21.
TCP
START
PORT
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
22. TCP DEF TTL
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-19
Issue 3, March 2006
See notice on first page
RC View 90.6
Figure 4-18 RC View 90.6 (INTL): IP Processor Routing to Interface
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN 1 OF 1
RECENT CHANGE - 90.6 IPRTE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP ROUTING TO INTERFACE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*1. DEST IP ADDR
___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*6.
INTERFACE
NAME
___________________
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
7.
NET
OR
HOST
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
8. IP SUBNET MASK
___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
#13. GATEWAY IP ADDR
___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
18.
ROUTE
METRIC
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
RC View 90.7
Figure 4-19 RC View 90.7 (INTL): IP Interface Assignment
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SCREEN 1 OF 1
RECENT CHANGE - 90.7 IPETH
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ETHERNET INTERNET PROTOCOL (IP) INTERFACE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
ASSIGNMENT
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*1. SM
___
33. RATE
___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*2. PSU
_
34. MODE
_
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*3. SHELF
_
#35. APP
1234567890123456789012345678901212345678901234567890123456789
TYPE
_____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
*4. CHANNEL GROUP
__
1234567890123456789012345678901212345678901234567890123456789
#5. INTERFACE NAME
___________________
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#6.
PHE
LINK
__
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
#7. GATEWAY IP ADDR 1
___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
#12. IP SUBNET MASK 1
___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
17.
GATEWAY
IP
ADDR
2
___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
22.
IP
SUBNET
MASK
2
___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
27. MCAST ADDR
___ ___ ___ ___
1234567890123456789012345678901212345678901234567890123456789
32. MTU SIZE
____
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
Backhaul server associations
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-20
ECPC
OA&M
.................................................................................................................................................................................................................................
Purpose
This section describes Recent Change and Verify forms that are new or have been
modified for IPBH on the ECP.
RC/V forms updated for IP Backhaul
The following forms are updated for IP Backhaul: ecp, apeqp, btseqp, cell2, and
cdmeqp. Views of each form and IPBH screen are shown on subsequent pages.
The following fields are populated for IPBH:
Form
ecp
btseqp
Backhaul Mode
Backplane Serial Number
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-21
Issue 3, March 2006
See notice on first page
ECPC OA&M
Form
cell2
IP Backhaul Enabled
Backhaul Offload
Primary RNC Number
Primary RNC Backhaul Server Number
Primary Switching Module Number (SM)
Primary Packet Switching Unit Number (PSU)
Primary DCS Backhaul Server Number
Alternate RNC Number
Alternate RNC Backhaul Server Number
Alternate Switching Module Number (SM)
Alternate Packet Switching Unit Number (PSU)
Alternate DCS Backhaul Server Number
MLG Loading Bias Translation (BIASMLG)
CDMA Carrier Service Option Class
CDMA Carrier Switching Module
CDMA Carrier Packet Switching Unit
CDMA Carrier Backhaul Server
cdmeqp
apeqp
See Text Recent Change and Verify Manual (Text RC/V), 401-610-038, and Database
Update, 401-610-036, for complete details about these forms, including population
rules.
ecp form
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-22
ECPC OA&M
btseqp form
The following fields are used for IPBH: Backhaul Mode per URC and Backplane
Serial Number (BPSN) per frame.
Figure 4-21 RC/V form: btseqp
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-23
Issue 3, March 2006
See notice on first page
ECPC OA&M
cell2 form
The cell2 form activates the IPBH feature, identifies the service option class (SOC),
associates the cells carriers to the SM/PSU/BHS, specifies data offload and provides
the DCS/BHS or 1X RNC/BHS used for data offload. The service option class (SOC)
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-24
ECPC OA&M
is display only. It is set to BOTH when data offload is n. It is set to VOICE when
data offload is y, since the carriers listed will only handle the voice traffic.
Figure 4-23 RC/V form: cell2
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-25
Issue 3, March 2006
See notice on first page
ECPC OA&M
This screen for CDMA Cell Site IP Backhaul Information identifies IPBH parameters
per cell site.
Figure 4-24 RC/V form: cell2
This form identifies when the IPBH feature is enabled for the cell and when data
traffic is off-loaded to a specific BHS on the DCS or RNC.
cdmeqp form
The Backhaul Mode field identifies the backhaul mode of ATM Protocol, Frame Relay,
SH or IP per frame. The Back Plane Serial Number (BPSN) is also populated on this
form.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-26
ECPC OA&M
This form identifies the CRCs for the Mod 1,2,3 cells:
Figure 4-25 RC/V form: cdmeqp
See Text Recent Change and Verify Manual (Text RC/V), 401-610-038, and Database
Update, 401-610-036, for complete details about these forms, including population
rules.
apeqp form
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-27
Issue 3, March 2006
See notice on first page
RCI-IM Exists
ECPC OA&M
is set on a single AP pair with the command script during install using
apappconfig.
The apeqp form is also used to enable RCS Flexible Sparing. See Flexent Wireless
Networks Cell Reliability and Engineering Improvements for IPBH RCS APs - Delivery
of Flexible Sparing Phase 1,, 401-612-830. for details on that feature.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-28
Input/Output
commands and messages
.................................................................................................................................................................................................................................
Purpose
This section describes the new and modified input and output commands for IPBH.
Because of the volume of messages that report on IPBH, this section provides a
high-level overview of commands that support IPBH and does not cover all IPBH
commands and resulting output. Itemizing all new commands is beyond the scope of
this document. It is intended to help you identify critical commands to use in managing
your iPBH network. It is assumed that the user is familiar with the purpose of
commands used in a Lucent Technologies network.
Overview
IPBH input and output messages can be viewed through user interfaces and ROP
printouts.
See the following documents for detailed information on these new and modified I/O
messages for IPBH:
Input commands
IPBH input messages are described in detail in the Input Messages Manual
(401-610-055). This section describes the new messages and provides some of the use
of variables for the command message.
Important! All LOCK, UNLOCK, SHUTDOWN, and GET commands in are only available
via TPUCLI from the AP supporting the 1X RNC.
New inputs
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-29
Issue 3, March 2006
See notice on first page
Table 4-3
Command
Syntax
TICLI
TI
ALW:CELL-MLG
Requests the status of the Backhaul Servers (BHSs) associated with the
requested cell. The report includes status and location information for
all BHSs provisioned on the cell2 RC/V form for both voice and data
traffic.
OP:CELL-CSB
OP:CELL a, CSB
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-30
Table 4-3
(continued)
Command
Syntax
TICLI
TI
OP:DCS-BHSSTAT
Requests the RNC BHS status from the ecp to be output to the ROP.
Status includes maintenance state, overload state, blocking state, etc.
UPDATE:AP-BPSN
UPDATE:AP y,BPSN
Request to update the Back Plane Serial Numbers (BPSNs) for each
cell configured on the specified Application Processor (AP), to be
updated in the database prior to converting to Internet Protocol (IP)
Backhaul. If possible, the BPSNs are retrieved from each cell for all
the assemblages in the cell. If the BPSNs cannot be retrieved for a cell,
the value from the database will be retrieved. The output will list the
BPSNs and the source of the BPSN data (cell or database).
UPDATE:CELL-BPSN
UPDATE:CELL x,BPSN
See Flexent /Autoplex Wireless Networks Input Messages Manual, 401-610-055 for
complete details.
Modified inputs
Table 4-4
Modified inputs
Command
Syntax
TICLI
TI
ABT:VCA-AUD
ABT:VCA, AUD a
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-31
Issue 3, March 2006
See notice on first page
Table 4-4
Modified inputs
(continued)
Command
Syntax
TICLI
TI
ALW:VCA-AUD
See Flexent /Autoplex Wireless Networks Input Messages Manual, 401-610-055 for
complete details.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-32
Output messages
IPBH output messages are described in detail in the Output Messages Manual
(401-610-057). This section describes the new and modified output messages.
See Flexent /Autoplex Wireless Networks Output Messages Manual, 401-610-057 for
complete details on these messages.
New outputs
Table 4-5
New outputs
New output
Purpose
ALW-CELL-MLG
DUMP-CELL-AUTH-FAIL
INH-CELL-MLG
OP-AP-IPBHINFO
OP-BHS-CELL
OP-CELL-CSB
OP-DCS-BHSSTAT
OP-RNC-BHSSTAT
REPT-BHS-IPERR
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-33
Issue 3, March 2006
See notice on first page
Table 4-5
New outputs
(continued)
New output
Purpose
REPT-BHS-STATUS
REPT-CELL-AUTH-FAIL
UPDATE-AP-BPSN
UPDATE-CELL-BPSN
See Flexent /Autoplex Wireless Networks Output Messages Manual, 401-610-057 for
complete details on these messages.
Modified outputs
Table 4-6
Modified outputs
Command Name
AUD-VCA-NAME-E-C
AUD-VCA-NAME-E-N
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-34
Table 4-6
Modified outputs
(continued)
Command Name
GET-RNC-TPU-STATE
INH-CELL-IN-PROG
LOCK-RNC-TPU
OP-ALARM
OP-AP-ALARM
OP-AP-INFO
OP-CELL
REPT-AP-ALLLAN
REPT-AP-LANFAIL
REPT-CELL-CP-FAIL
REPT-CELL-HEH-2
REPT-DCF-RECOVERY
REPT-DCF-SUMMARY
REPT-VCA-INIT
RESTART-RCS
RMV-AP
RMV-RCS
RST-RCS
SHUTDOWN-RNC-TPU
SWITCHOVER-RCS
UNLOCK-RNC-TPU
See Flexent /Autoplex Wireless Networks Output Messages Manual, 401-610-057 for
complete details on these messages.
5ESS DCS I/O commands for IPBH
This section provides a high-level overview of commands that support IPBH. Itemizing
all new commands is beyond the scope of this document. Please refer 5ESS Switch
Flexent /Autoplex Wireless Networks Applications Input/Output Messages,
235-600-700/750 for complete details on these messages.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-35
Issue 3, March 2006
See notice on first page
Table 4-7
Input
Output
ALW:HDW
None.
INH:HDWCHK
PH IMAGE TYPE
SOURCE IP
DESTINATION IP
BYTES SENT
HOPS
TIMEOUT DURATION
TRACE TIMEOUTS
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-36
Table 4-7
(continued)
Input
Output
OP:TCPIP:ARPDMP,CHNG=a-b-c-d;
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-37
Issue 3, March 2006
See notice on first page
Status
display pages
.................................................................................................................................................................................................................................
ECPC status display pages
This section describes the new and changed status page. It is assumed that you are
familiar with the use of the SDP pages and the color coding for status: Available =
green, Unavailable = red, Degraded = yellow, and Indeterminate = white.
See Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance
Control Procedures, 401-610-160 for detailed information.
Table 4-8
SDP Page
New or
Modified
Description
SDP 2101
New
APX Index Page II- New index page added for BHS
status pages.
SDP 2131
Modified
SDP 2138
Modified
SDP 2236
New
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-38
Table 4-8
(continued)
SDP Page
New or
Modified
Description
SDP 2237
New
SDP 2260
New
SL on each CRC/MLG.
Note, for Modular cell 1,2 or 3, if the CRC does
not have an equipped DS1, it uses the parent
MLG.
SDP 2265
New
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-39
Issue 3, March 2006
See notice on first page
See Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance
Control Procedures, 401-610-160 for detailed information.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-40
This page has been modified to indicate whether or not IP Backhaul is enabled for the
cell and MLG sharing (indicated by SH when on).
Figure 4-28 SDP 2131
See Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance
Control Procedures, 401-610-160 for detailed information.
SDP 2138- Cell CDM Status Page
The SDP 2138 page shows status for IP BHAs which use MLGs that are physically
located on the URC.
When IPBH is enabled on the cell2 form, the following information is provided on
SDP 2138:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-41
Issue 3, March 2006
See notice on first page
The status:
See Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance
Control Procedures, 401-610-160 for detailed information.
SDP 2236 - Cell Carrier SOC BHS status
Carrier ID (1 - 18)
Channel number (1 - 2047)
BHS assigned to each Service Option Class type per carrier: Voice or Data
BHS_ID (PSU) include DCS# (1-16), SM# (1-192), PSU# (0-1), BHS# (1-10)
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-42
The status of Carrier-SOC-BHS (available - green, unavailable - red, degraded yellow, indeterminate - black)
See Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance
Control Procedures, 401-610-160 for detailed information.
SDP 2237 - Cell MLG Status
CRC ID (1 - 16)
The status of CRC (ACTIVE - green, OOS - red)
MLG ID (1 - 2)
The status of MLG (active - green, oos - red, inh - white)
DS1 associated with each MLG
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-43
Issue 3, March 2006
See notice on first page
See Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance
Control Procedures, 401-610-160 for detailed information.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-44
This page displays BHS status for both voice and data for DCS BHSs consisting of
one screen per switching module (SM) for the DCS (1-16).
Figure 4-32 SDP 2260
See Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance
Control Procedures, 401-610-160 for detailed information.
SDP 2265 - BHS Status
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-45
Issue 3, March 2006
See notice on first page
with red background). If not, the RNC number will be marked as NORMAL (White
text with black background).
Figure 4-33 SDP 2265
See Flexent /Autoplex Wireless Networks ECP OA&M and SDP Maintenance
Control Procedures, 401-610-160 for detailed information.
5ESS DCS status pages
The PH group number on the 1188 is the same as the BHS number on the ECP
SDP 2260 and 2236 and the cell2 form.
Each PH group consists of 2 PHs listed by shelf and slot number, horizontally
across the same row as the PH group number.
If either PH in the row is listed as having *M (major) or *C (critical) overload,
then the entire PH group (BHS) is reported in overload on the ECP 2260 page and
BHSSTAT output messages.
If at least 1 PH in the row is ACT/SERV, then the BHS is reported available in the
ECP 2260 and BHSSTAT output messages.
If both PHs in a row are OOS, then the ECP reports the BHS as unavailable.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-46
If a BHS used for data offload is unavailable and there is an alternate BHS
provisioned on the cell2 form for a cell, the alternate BHS will be used for future
data calls using that cell.
If a BHS used for data offload is available, but in overload, the primary BHS
provisioned on the cell2 form for a cell will continue to be used for future data
calls.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-47
Issue 3, March 2006
See notice on first page
OMC-RAN
Monitor
IPBH from the OMC-RAN
.................................................................................................................................................................................................................................
OMC-RAN for IPBH
See Flexent Wireless Networks Operations and Maintenance Center Radio Access
Network (OMC-RAN) Operations, Administration & Maintenance, 401-662-105 for
information on planning for OMC-RAN.
The OMC-RAN can be installed in your network either prior to or following the
installation of an IPBH network.
When the IPBH network is configured, the IPBH screens and configuration information
appears on the existing screens of the OMC-RAN.
Monitoring IPBH information on the OMC-RAN
The primary purpose of the OMC-RAN is for alarm monitoring and fault clearance.
The types of information that is available on the Status Display Page also appears on
the OMC-RAN screens. However, you can also do configuration from the OMC-RAN.
See Flexent Wireless Networks Operations and Maintenance Center Radio Access
Network (OMC-RAN)Planning Operations, Administration & Maintenance,
401-662-105 for complete information about OMC-RAN.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-48
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-49
Issue 3, March 2006
See notice on first page
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-50
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-51
Issue 3, March 2006
See notice on first page
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
4-52
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
4-53
Issue 3, March 2006
See notice on first page
F ault management
5
Overview
.................................................................................................................................................................................................................................
Purpose
5-3
Fault management
5-3
5-5
5-7
5-10
Cable faults
5-14
5-14
5-17
5-20
5-24
5-27
5-30
5-34
5-37
5-41
Communication faults
5-45
IPGW0 is unreachable
5-45
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-1
Issue 3, March 2006
See notice on first page
Fault management
Overview
IPGW1 is unreachable
5-48
5-51
5-55
5-59
No Ethernet connectivity
5-63
5-66
No Ethernet connectivity
5-70
5-73
5-76
5-76
5-79
5-83
5-86
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-2
Fault management
Network monitoring
Fault
management
.................................................................................................................................................................................................................................
Definition
Fault management (FM) is a set of functions that enables the detection, isolation and
correction of abnormal operation of the telecommunication network and its
environment.
FM functions
Alarm surveillance
Fault localization
Fault correction
Testing
Alarm surveillance
Description
Hardware faults
Software faults
Functional faults
Overload conditions
Communication failures
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-3
Issue 3, March 2006
See notice on first page
Fault management
Fault management
Fault localization
Fault correction takes the appropriate action to correct a fault once the root cause has
been identified.
It transfers data concerning the repair of a fault and for the control of procedures that
use redundant resources to replace equipment or facilities that have failed.
Testing
Testing conduct tests to determine the root cause of a fault. Testing can be carried out
by directly accessing the relevant functionality of the NE using the LMT to help you
analyze the problem.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-4
Fault management
General
problem solving model
.................................................................................................................................................................................................................................
Description
The general problem solving model represents a model that can be used as a general
approach for each troubleshooting situation.
Process
The stages for the general problem solving model process are:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-5
Issue 3, March 2006
See notice on first page
Fault management
.................................................................................................................................................................................................
To properly analyze the problem, identify the general symptoms and then ascertain
what kinds of problems (causes) could result in these symptoms.
.................................................................................................................................................................................................
.................................................................................................................................................................................................
Eliminating causes.
Narrowing the number of potential causes.
.................................................................................................................................................................................................
If...
then...
return to Step 2.
Result
Process complete.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-6
Fault management
Network
monitoring and fault detection
.................................................................................................................................................................................................................................
Reference diagram
Figure 5-1, Network monitoring (p. 5-7) diagram is referenced throughout this
chapter.
Figure 5-1 Network monitoring
Host interfaces
All hosts on the IP backhaul network (URCs, BHSs, and RCS-APs) continuously
monitor and report the health of all their interfaces through MSC operation,
administration and maintenance (OA&M) systems. This information is displayed on
SDP pages, NE GUI pages and as output to the ROP. When the OMC-RAN is part of
the IPBH network, some health events are also reported to the OMC-GUI.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-7
Issue 3, March 2006
See notice on first page
Fault management
URC interfaces
Each URC continuously updates its RCS with the status of all its DS1s. RCS requires
real-time knowledge of DS1 status in order to perform its call leg admission control
function and DS1 alarms and technician output reports.
In addition to admission control, RCS makes the DS1 status information available
through status display pages for the following:
URC n
BTS n
Link status via URC
RCS and BHS status via MSC OA&M
BHS interfaces
Each Backhaul Server (BHS) continuously monitors the health of its Ethernet links and
its ability to communicate with its gateway router. The status of each BHS interface is
reported and alarmed through 5ESS DCS and 1X RNC OA&M. The ECPC sees only
the status of a BHS. The ECPC also reports its view of BHS status through alarms,
status display and technician output reports.
RCS-AP and FMM LAN interfaces
The status of all Ethernet links within the FMM-AP LAN, and between the FMM LAN
and the MSC adjacent switches, are continuously monitored and reported through
ECPC OA&M. All link faults are alarmed. In addition, each RCS-AP continuously
monitors its ability to communicate with both gateway routers configured for the
control network. Loss of AP connectivity to a gateway router is alarmed.
End-to-end connectivity
URC-RCS connectivity
The end-to-end connectivity between each URC and its primary and alternate RCS-APs
continues to be reported on status display page 2131 (SDP 2131) and associated output
reports. There are multiple physical paths between a URC and an RCS-AP. As long as
there is a healthy connection over any one of the physical paths then the status of the
end-to-end connection is green. URC-RCS connectivity is independent of RCS
maintenance state.
URC-BHS connectivity
Each URC monitors end-to-end connectivity to all the BHSs that are assigned to serve
call legs on that URC. This URC-BHS connectivity status is available on SDP 2236
and associated technician output report.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-8
Fault management
Router status
The status of the backhaul routers, all inter-router links and all host interfaces (from
the point of view of the routers) is available through the router network management
system (RNMS) as indicated in Figure 5-1, Network monitoring (p. 5-7).
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-9
Issue 3, March 2006
See notice on first page
Fault management
Sample
section: Identified fault
.................................................................................................................................................................................................................................
Format of sample
The following sample sections identify the layout of the troubleshooting pages and
describe the contents of each section.
Each fault is described for an environment that assumes the system is in stable and
operational condition and is up and running with no alarms present.
Fault ID: IPBH-FM-NE-#
Service impact
This block will identify any service impacts to the network that can occur with the
fault.
The following types of service impacts can occur and will be identified when present:
Resolution
Text in this block will identify the steps or activities needed to resolve the fault.
Severity
Critical
Major
Minor
Fault identification
This is a high-level view of actions needed to resolve the fault and/or an indicator that
no manual intervention is required to resolve the fault.
Other indications
Information in this block lists possible other indicators that may accompany the fault.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-10
Fault management
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
BTS
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
Router
Management:
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
Edge Router
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
MLS
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
Transport Network
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
RCS
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
RCS
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
SDP ####:
ROP:
5ESS DCS
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
1188 MCC:
118 [0-4]:
ROP:
1X RNC
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
TPU-GUI:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-11
Issue 3, March 2006
See notice on first page
Fault management
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
OMP-FX
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
EMS:
OMC-RAN
Alarm or notification
on NE interface.
Automatic recovery
action on NE.
OMC-GUI:
Other Indications
Message or report
through another
medium than user
interface, such as
technician interface
(TI).
Message or report
through another
medium than user
interface, such as
technician interface
(TI).
Fault resolution
Recommended actions to resolve fault. This may include a single action , a series of
actions or an indicator that no manual intervention is required to resolve the fault.
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
Transport Network
Router Management
Edge Router
MLS
RCS
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-12
Fault management
Network Element
ECP
SDP ####:
ROP:
1188 MCC:
118 [0-4]:
ROP:
TPU-GUI:
EMS:
OMC-GUI:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-13
Issue 3, March 2006
See notice on first page
Fault management
Cable faults
DS1
(T1/E1) cable cut
.................................................................................................................................................................................................................................
Fault Description
Incoming DS1 failure to the BTS. Multi-T1 MLG (Partial MLG Failure)
Fault ID: IPBH-FM-BTS-1
Severity
Critical.
Service impact
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network element
Fault detection
Automatic
recovery
BTS
No impact.
Removes DS1
from MLG.
Transport Network
Reflects DS1
interface/sub-interface
OperStatus down.
Router
Management
Edge Router
Removes DS1
from MLG.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-14
Fault management
Network element
Fault detection
Automatic
recovery
MLS
No impact.
No impact.
No impact.
No impact.
No impact.
No impact.
RCS
No impact.
No impact.
RCS
Alarm.
SDP 2237: Shows that this
No impact.
No impact.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
No impact.
No impact.
Other Indications
OP:CELL
Fault resolution
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-15
Issue 3, March 2006
See notice on first page
Fault management
Network Element
BTS
Transport Network
Router Management
Edge Router
MLS
No impact.
No impact.
RCS
ECP
5ESS DCS
No impact.
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
Other Indications
None.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-16
Fault management
DS1
(T1/E1) cable cut
.................................................................................................................................................................................................................................
Fault identification
Critical.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
BTS
No impact.
Transport Network
Reflects DS1
interface/sub-interface
OperStatus down.
Router
Management
Edge Router
MLS
No impact.
No impact.
Fault management
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
FMM-APs
No impact.
No impact.
No impact.
RCS
No impact.
Alarm or notification on
NE interface.
ECP
No impact.
No impact.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
OMC-GUI: Shows
No impact.
Critical Alarm on AP
Detailed view.
OP:ALARM
Other
Indications
OP:CELL
Fault resolution
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-18
Fault management
Network Element
BTS
Transport Network
Router Management
OperStatus up.
Edge Router
Detects that signal is good, and adds the DS1 back into the
MLG.
MLS
No impact.
No impact.
RCS
ECP
5ESS DCS
No impact.
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
Other Indications
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-19
Issue 3, March 2006
See notice on first page
Fault management
DS1
(T1/E1) cable cut
.................................................................................................................................................................................................................................
Fault identification
Major.
Service impact
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Automatic recovery
BTS
Transport Network
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-20
Fault management
Network
element
Fault detection
Automatic recovery
Reflects DS1
interface/sub-interface
OperStatus down. Line
status reflects loss of signal.
Router
Management
Edge Router
MLS
No impact.
No impact.
No impact.
No impact.
No impact.
No impact.
RCS
Detects Loss of
Heartbeat after 24
seconds and put the
URC out of service.
Signaling Link will be
re-established. Original
MLG association will
change to use another
URCs MLG.
No impact.
Signaling is
re-established. Original
MLG association will
change to use another
URCs MLG. After the
signaling link is
established again to the
shared MLG, the
information will be sent
to the RCS. Receive SL
bandwidth change from
BTS.
ECP
URC
No impact.
No impact.
No impact.
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-21
Issue 3, March 2006
See notice on first page
Fault management
Network
element
Fault detection
Automatic recovery
OMC-RAN
No impact.
OP:ALARM
OP:ALARM
OP:CELL
OP:CELL
Fault resolution
BTS
When MLG comes back it will be used for bearer traffic only.
To use the original MLG for signaling traffic, the URC will
not be rebooted.
Transport Network
Router Management
Edge Router
MLS
No impact.
No impact.
RCS
BTS notifies RCS that URC is available for bearer traffic and
the MLG Association has changed.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-22
Fault management
Network Element
ECP
No impact.
RNC
No impact.
OMP-FX
No impact.
OMC-RAN
Other Indications
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-23
Issue 3, March 2006
See notice on first page
Fault management
Bad
DS1 cable
.................................................................................................................................................................................................................................
Fault identification
High BER (>5*10-5) on outgoing DS1 failure to Edge Router (ER). Multi-T1 MLG .
This is the BER towards the router. Current router software versions do not detect
BER.
Fault ID: IPBH-FM-ER-1
Severity
Major.
Service impact
Technician corrects DS1 (T1/E1) problem by installing a new DS1 (T1/E1) between
the BTS and the ER..
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
BTS
No detection.
No impact.
No impact.
Transport Network
May display
intermittent failures.
Router
Management
Edge Router
No detection.
No impact.
No impact.
MLS
No impact.
No impact.
No impact.
No impact.
No impact.
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-24
Fault management
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
RCS
No impact.
May display
intermittent signaling
link failures.
No impact.
ECP
No impact.
major alarm.
SDP 2237: Shows
No impact.
No impact.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
See OMC-GUI:
OMC-GUI: may
No impact.
display an
intermittent major
alarm on the AP
Detailed View.
Other Indications
NE impacts: None.
Subsequent alarms: None.
Subsequent other indications: None.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-25
Issue 3, March 2006
See notice on first page
Fault management
Fault resolution
Technician corrects DS1 (T1/E1) problem by installing a new DS1 between the BTS
and the ER..
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
No impact.
Transport Network
Router Management
No impact.
Intermittent problems are gone
MLS
No impact.
No impact.
RCS
ECP
be displayed.
SDP 2237: Alarm clears. No intermittent minor alarms should
be displayed.
ROP: After problem is resolved, no additional reports on this
problem should be received.
5ESS DCS
No impact.
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
Other Indications
Service impact
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-26
Fault management
Cable
cut/disconnected between ER and MLS
.................................................................................................................................................................................................................................
Fault identification
None.
Service impact
None.
Resolution
Install a new T1 cable between the edge router and the MLS.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
BTS
No impact.
No impact.
No impact.
Transport Network
No impact.
Router
Management
Edge Router
MLS
Shows ER and
MLS Ethernet
interfaces
OperStatus
down.
See Router
Management.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-27
Issue 3, March 2006
See notice on first page
Fault management
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
No impact.
No impact.
No impact.
RCS
No impact.
No impact.
No impact.
ECP
No impact.
No impact.
No impact.
5ESS DCS
No impact.
No impact.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
No impact.
No impact.
No impact.
Other
Indications
NE Impacts: None.
Subsequent alarms: None.
Subsequent other indications: None
Subsequent service impact: Change in delay characteristics.
Subsequent states: None.
Fault resolution
BTS
No impact.
Transport Network
Router Management
Edge Router
MLS
No impact.
RCS
No impact.
ECP
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-28
Fault management
Network Element
5ESS DCS
No impact.
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
Other Indications
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-29
Issue 3, March 2006
See notice on first page
Fault management
Stable calls should remain active, however there may be some loss of data. Also, some
new call setups or reactivations on the affected BTSs may fail before the RNC
recovers.
Severity
Major.
Other indications
There may be some REPT-CPFAIL reports for new call setups on the ROP.
States
RNC Serving IPBTS GW state changes to disabled/idle. This can be viewed on the
TPU-GUI. State change reports appear on the ROP.
Resolution
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Automatic
recovery
BTS
No impact.
No impact.
Transport Network
Router
Management
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-30
Fault management
Network
element
Fault detection
Automatic
recovery
Edge Router
No impact.
No impact.
No impact.
MLS
No impact.
Receives a
gratuitous ARP
from the newly
active GW and
starts sending
packets to it
No impact.
No impact.
No impact.
RCS
No impact.
No impact.
No impact.
ECP
SDP 2236:May
show an
intermittent
change in the
Carrier-SOC-BHS
status.
No impact.
No impact.
No impact.
1X 1X RNC
TPU-GUI:
Performs
automatic failover
to standby IPBTS
GW.
OMP-FX
No impact.
No impact.
OMC-RAN
No impact.
No impact.
Other Indications
None.
None.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-31
Issue 3, March 2006
See notice on first page
Fault management
Network
element
Fault detection
States
Automatic
recovery
Fault resolution
BTS
No impact.
Transport Network
Router management
Edge Router
No impact.
MLS
No impact.
RCS
No impact.
ECP
5ESS DCS
No impact.
1X RNC
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-32
Fault management
Network Element
OMP-FX
OMC-RAN
None.
States
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-33
Issue 3, March 2006
See notice on first page
Fault management
Cable
cut on non-serving IPBTS GW GigE interface
.................................................................................................................................................................................................................................
Fault identification
None.
Resolution
Major.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
BTS
No impact.
No impact.
No impact.
Transport Network
Reflects
MLSEthernet
interface OperStatus
down.
Router
Management
Edge Router
No impact.
No impact.
No impact.
MLS
Detects loss of
direct connectivity
to GICC.
No impact.
No impact.
No impact.
No impact.
No impact.
RCS
No impact.
No impact.
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-34
Fault management
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
ECP
See impacts to
SDP, OMC-RAN,
EMS and ECP
ROP.
No impact.
indication on RNC
summary indicator.
ROP: Receives RNC
report on major
alarm against GigE.
5ESS DCS
No impact.
No impact.
No impact.
1X RNC
Detects loss of
ARP beating.
None.
OMP-FX
No impact.
OMC-RAN
See OMC-GUI
==>
OMC-GUI: Shows
No impact.
TRBL indication
on RNC Summary
page. Reports major
alarms against the
TPU and the GICC.
Other
Indications
States
RNC Non-serving
IPBTS GW state
changes to
disabled/idle.
None.
NE impacts: None.
Subsequent alarms: None.
Subsequent other indications: None.
Subsequent device impact: None.
Subsequent states: None.
Fault resolution
Fault management
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
No impact.
Transport Network
Router Management
Edge Router
No impact.
MLS
No impact.
RCS
No impact.
ECP
5ESS DCS
No impact.
1X RNC
OMC-RAN
None.
States
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-36
Fault management
Loss of Layer 2 detected by the serving IPBTS GICC. Non-serving IPBTS GICC is
out-of-service. Alternate BHS has been assigned and is In-Service. (NAR only).
Fault ID: IPBH-FM-RNC-3
Severity
Critical.
Service impact
Calls will drop. New data call setups or reactivations on the affected BTSs may fail
before the BTSs establish connections with the alternate BHSs.
Resolution
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
this fault event, the order of recovery is identified.
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
BTS
No impact.
3. Establish new
BHAs with
alternate BHSs.
Transport Network
Router
Management:
Edge Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
Fault management
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
FMM-APs
No impact.
No impact.
None.
RCS
No impact.
No impact.
2. Forward
information from
the ECP to the BTS
ECP
1. Assigns alternate
BHSs to the
affected RCSs.
No impact.
No impact.
No impact.
1X RNC
TPU-GUI: Reports
major GigE port
alarm, critical TPU
alarm and critical BHS
alarm.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-GUI: TRBL
indication on RNC
Summary page.
Critical alarms against
the BHS and TPUs are
displayed. Major
alarms against the
affected GICCS are
displayed.
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-38
Fault management
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
TI: OP:ALARM
Other Indications
States
Fault resolution
Technician repairs the cable. Network elements respond to fault resolution in the order
identified.
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
Transport Network
Router Management
Edge Router
No impact.
MLS
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-39
Issue 3, March 2006
See notice on first page
Fault management
Network Element
RCS
ECP
No impact.
1X RNC
OMP-FX
OMC-GUI: Show that the GigE port alarm has been cleared.
Other indications
Service impact
None.
States
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-40
Fault management
Cable
cut on serving IPBTS GW GigE interface
.................................................................................................................................................................................................................................
Fault identification
Service impact
Critical.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
BTS
Alarms and
notifications
Automatic recovery
No impact.
Transport Network
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-41
Issue 3, March 2006
See notice on first page
Fault management
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
Reflects interface
OperStatus
down. Layer 2
will report the
failure.
Router
Management
Edge Router
No impact..
MLS
No impact.
No impact.
No impact.
No impact.
No impact.
No impact..
RCS
ECP
No impact.
indicator shows
BHS is
Unavailable.
ROP:RNC reports
Major alarm
against GigE port
and critical alarm
against BHS
service. The BTS
may report loss
of heartbeat
events, depending
on how quickly
the RNC detects
the failure.
5ESS DCS
No impact.
No impact.
No impact..
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-42
Fault management
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
1X RNC
TPU-GUI:GigE
No impact.
No impact.
OMP-FX
OMC-RAN
None.
OMC-GUI:
No impact.
TRBL
indication on
RNC Summary
page. Reports
TPU critical
alarm.
States
RNC IPBTS GW
and BHS states
change to
disabled/idle.
Other
Indications
There may be
some
REPT-CPFAIL
reports for new
call setups from
the affected
BTSs.
Automatic Recovery Actions
NE impacts: None
Subsequent alarms: None
Subsequent other indications: None
Subsequent service impact:No new data calls can be established on the impacted
BTSs.
Subsequent states: None.
Fault resolution
Fault management
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
Transport Network
Router Management
Edge Router
No impact.
MLS
No impact.
RCS
3. Establishes associations with Primary BHS. Establishes all new data calls on
these associations.
ECP
5ESS DCS
No impact.
1X RNC
EMS: TPU alarm indicator may return to Normal. (or at least down to Major
dependent on other alarm conditions existing)
OMC-RAN
OMC-GUI:Displays show that the GigE port alarm has been cleared. TPU alarm
indicator may return to Normal. (or at least down to Major dependent on other
alarm conditions existing)
Other Indications
No impact.
Service impact:
States
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-44
Fault management
Communication faults
IPGW0
is unreachable
.................................................................................................................................................................................................................................
Fault identification
None
Resolution
Repair MLS-1.
Severity
Major.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
BTS
No impact.
No impact.
Edge Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
Assumes MLS-1
and MLS-2,
connections will be
routed to MLS-2
instead of going to
MLS-1 until the
problem is
resolved.
Transport Network
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-45
Issue 3, March 2006
See notice on first page
Fault management
IPGW0 is unreachable
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
RCS
Receive Notification of
MLS Failure.
No impact.
ECP
Major Alarm.
major alarm is
cleared.
Alarm.
5ESS DCS
No impact.
No impact.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
OMC-GUI: Major
alarm is cleared on
the AP Detailed
View.
Other Indications
None.
None.
None.
NE impacts: None.
Subsequent alarms: None.
Subsequent other indications: None
Subsequent service impact: None.
Subsequent states: None.
Fault resolution
Repair MLS-1.
The following results occur on the network elements when a fault is corrected:
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-46
Fault management
IPGW0 is unreachable
Network Element
BTS
Transport Network
Edge Router
No impact.
Router Management
No impact.
MLS
ECP
5ESS DCS
No impact.
1X RNC
No impact.
OMP-FX
OMC-RAN
Other Indications
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-47
Issue 3, March 2006
See notice on first page
Fault management
IPGW1
is unreachable
.................................................................................................................................................................................................................................
Fault identification
Major.
Service impact
None.
Resolution
Repair MLS-2.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
BTS
No impact.
No impact.
Edge Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
Assuming MLS-1
and MLS-2,
connections will be
routed to MLS-1
instead of going to
MLS-2 until the
problem is
resolved.
Transport Network
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-48
Fault management
IPGW1 is unreachable
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
FMM-APs
RCS
No impact.
No impact.
ECP
Major Alarm.
Alarm is cleared.
Alarm.
cleared message is
received.
5ESS DCS
Alarm or notification
on NE interface.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
OMC-GUI: Major
alarm is cleared on
the AP Detailed
View.
Other Indications
None.
None.
None.
NE impacts: None.
Subsequent alarms: None.
Subsequent other indications: None
Subsequent service impact: None.
Subsequent states: None.
Fault resolution
Repair MLS-2.
The following results occur on the network elements when a fault is corrected:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-49
Issue 3, March 2006
See notice on first page
Fault management
IPGW1 is unreachable
Network Element
BTS
Transport Network
Edge Router
No impact.
Router Management
No. impact.
MLS
RCS
No impact.
ECP
5ESS DCS
No impact.
1X RNC
No impact.
OMP-FX
OMC-RAN
Other Indications
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-50
Fault management
Duplex
IPGW access failures
.................................................................................................................................................................................................................................
Fault identification
None.
Resolution
Repair one or both IPGWs. If the problem is a cable that is bad or was inadvertently
disconnected, the technician should either connect a new cable or re-connect the
existing cables. In the worst case, cables between the FMM-AP frame and the IP
Gateways would need to be replaced with new cables.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Automatic
recovery
BTS
No impact.
No impact.
Router
Management
No impact.
No impact.
Edge
Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
No impact.
Transport Network
Fault management
Network
element
Fault detection
Automatic
recovery
FMM-APs
No impact.
No impact.
No impact.
No impact.
ECP
No impact.
No impact.
No impact.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
None.
None.
None.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-52
Fault management
NE impacts: None.
Subsequent alarms: No impact.
Subsequent other indications: None
Subsequent service impact: No impact.
Subsequent states: None.
Fault resolution
The technician should either connect a new cable or re-connect the existing cables.
The cables between the FMM-AP frame and the IP Gateways may need to be
replaced with new cables.
If the problem is resolved by connecting these new cables or re-connecting the cables,
the system software will automatically recover the links. See the fault correction results
below.
If the problem is not in the cabling, the contact Lucent Wireless Services (LWS) for
further diagnosis.
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
Transport Network
Router Management
No impact.
Edge Router
No impact.
MLS
No impact.
Verify that the critical alarm is cleared and verify that the
RCS-AP is in an active state.
RCs
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-53
Issue 3, March 2006
See notice on first page
Fault management
Network Element
ECP
No impact.
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-54
Fault management
Only
remaining 5E GW goes OOS
.................................................................................................................................................................................................................................
Fault identification
The 1X RNC is not available and causes the BHS to be disabled. (NAR only.)
An alternate BHS has been configured.
Fault ID: IPBH-FM-RNC-6
Severity
Critical.
Service impact
When the PSUGW is OOS, all data handoffs being served by BTSs that do not have
their BHS on the current RNC will fail. This scenario assumes an alternate BHS is
available. If an alternate BHS is not available, new data calls and reactivations on the
BTSs that are served by this BHS will fail until the problem is resolved since the BHS
is declared disabled when the PSUGW is OOS.
Resolution
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network element
Fault detection
Alarms and
notifications
Automatic recovery
BTS
No impact.
No impact.
Recovery occurs in
the order shown:
4. Notified by RCS
to initiate new
associations with the
alternate BHS.
Transport Network
Router
Management
No impact.
No impact.
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-55
Issue 3, March 2006
See notice on first page
Fault management
Network element
Fault detection
Alarms and
notifications
Automatic recovery
Edge Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
No impact.
No impact.
No impact.
No impact.
RCS
No impact.
No impact.
3. Establish new
BHAs with new
BHS.
ECP
2. Assigns alternate
BHSs to the affected
RCSs.
summary indication =
TRBL.
SDP 2265: BHS indicator
shows BHS is
unavailable.
ROP: RNC reports
No impact.
No impact.
No impact.
1X RNC
OMP-FX
EMS ==>
No impact.
OMC-RAN
OMC-GUI ==>
OMC-GUI: TRBL
indication on RNC
Summary page. TPU
alarm indicator shows
critical alarm.
No impact.
Other Indications
States
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-56
Fault management
Fault resolution
BTS
Transport Network
Router Management
No Impact
Edge Router
No Impact
MLS
No Impact
None
RCS
ECP
5ESS DCS
No impact
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-57
Issue 3, March 2006
See notice on first page
Fault management
Network Element
1X RNC
OMP-FX
Other Indications
None.
State change
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-58
Fault management
No
1st Hop router connectivity
.................................................................................................................................................................................................................................
Fault identification
.
Loss of Layer 3 detected on Serving BPH 0 (If duplex router configuration, then both
fail).
Fault ID: IPBH-FM-DCS-1
Severity
Loss of Layer 3.
Resolution
The fault is caused by incorrect provisioning of the IP address for the 1st Hop
Router(s). To resolve the problem, provision the correct IP address.
See IPBH Provisioning section, in 5ESS Switch Flexent /Autoplex Wireless
Networks Applications OA&M Manual, 235-200-100 or OA&M Manual, 5AP
International.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Automatic
recovery
BTS
No impact.
No impact.
No impact.
No impact.
Router
Management
No impact.
No impact.
Edge
Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
No impact.
Transport Network
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-59
Issue 3, March 2006
See notice on first page
Fault management
Network
element
Fault detection
Automatic
recovery
No impact.
No impact.
No impact.
RCS
No impact.
No impact.
No impact.
ECP
No impact.
5ESS DCS
received.
1188 MCC: The affected BPH Link Status
is OOS-GW and the Service Status is
UNAV; PH Group becomes
BPHGRPOFN
118[0-4]MCC: The PH Status of the
affected BPH is ACT-DGR - active,
degraded.
Fail-over - the
Non-Serving
BPH1 becomes
Serving and
BPH 0
becomes
UNAV.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
No impact.
No impact.
No impact.
Other
Indications
None.
None.
None.
NE impacts: None.
Subsequent alarms: None
Subsequent other indications: None
Subsequent service impact: No service impact since switched to the other BPH. No
dropped calls.
Subsequent states: None.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-60
Fault management
Fault resolution
The fault is caused by incorrect provisioning of the IP address for the 1st Hop
Router(s). To resolve the problem, provision the correct IP address.
See IPBH Provisioning section, 6.11.7 in 5ESS Switch Flexent/ AUTOPLEX
Wireless Networks Applications OA&M Manual (NAR 235-200-100) NAR or 5ESS
Switch Flexent/ AUTOPLEX Wireless Networks Applications OA&M Manual
(5AP) International.
Do the following to correct the fault:
1. Provision the correct IP address for the 1st hop router(s) on the 5ESS DCS Recent
Views form 22.32 (NAR) or 9.37 (INTL).
2. Verify connectivity from the BPH to the 1st hop router, enter the command EXC:
PING (NAR) or , EXC-PING(INTL)
3. Verify connectivity from the BPH to the 1st hop router, enter the command EXC:
TRACERT,CHNG=cg# (NAR) or EXC-TRACERT:UNIT=a-b-c-d (INTL)
4. Check physical connection to the router (between L2 switch and router).
5. If router specific debugging tools are available, verify that router ARP policing is
not dropping ARPs received by the router.
6. If in a duplex L2 switch configuration, verify that the interswitch trunk is
physically connected and operational.
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
No impact.
Transport Network
Router Management
No impact.
Edge Router
No impact.
MLS
No impact.
No impact.
RCS
No impact.
ECP
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-61
Issue 3, March 2006
See notice on first page
Fault management
Network Element
5ESS DCS
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
Other Indications
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-62
Fault management
No
Ethernet connectivity
.................................................................................................................................................................................................................................
Fault identification
None.
Resolution
None.
Fault detection automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Automatic
recovery
BTS
No impact.
No impact.
No impact.
Transport Network
Router
Management
No impact.
No impact.
No impact.
Edge Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
No impact.
No impact.
RCS
No impact.
No impact.
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-63
Issue 3, March 2006
See notice on first page
Fault management
No Ethernet connectivity
Network
element
Fault detection
Automatic
recovery
ECP
No impact.
No impact.
No impact.
5ESS DCS
Loss of Ethernet
connectivity
between the BPH
and the directly
connected L2
switch/MLS
Fail-over - the
Non-Serving BPH1
becomes Serving
and BPH 0 becomes
UNAV.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
No impact.
No impact.
No impact.
Other
Indications
None.
None.
None.
NE impacts: None.
Subsequent alarms: None.
Subsequent other indications: None.
Subsequent service impact: No service impact since switched to the other BPH. No
dropped calls.
Subsequent states: None.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-64
Fault management
No Ethernet connectivity
Fault resolution
BTS
No impact.
Transport Network
Router Management
Edge Router
No impact.
MLS
No impact.
RCS
No impact.
ECP
No impact.
5ESS DCS
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
Other Indications
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-65
Issue 3, March 2006
See notice on first page
Fault management
No
1st Hop router connectivity
.................................................................................................................................................................................................................................
Fault identification
Loss of Layer 3.
Resolution
The fault is caused by incorrect provisioning of the IP address for the 1st Hop
Router(s). To resolve the problem, provision the correct IP address.
See IPBH Provisioning section, in 5ESS Switch Flexent /Autoplex Wireless
Networks Applications OA&M Manual, 235-200-100 or OA&M Manual, 5AP
International.
Other indications
None.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Automatic recovery
BTs
No impact.
No impact.
No impact.
Router
Management
No impact.
No impact.
No impact.
Edge Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
No impact.
Transport Network
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-66
Fault management
Network
element
Fault detection
Automatic recovery
No impact.
No impact.
No impact.
R CS
No impact.
No impact.
No impact.
ECP
No impact.
No impact.
No impact.
5ESS DCS
REPT SM=sm
PSELINK=sm-psu-link
OLD_STAT=ACT
NEW_STAT=OOS-GW
RATE=NOT APPLICABLE
REPT SM=sm
PHGRP=sm-psu=phgrp
OFFNORM NEW STAT
POS 1=UNAV POS
0=SERVING
OVERLOAD
SUMMARY=NORMAL
OLD STAT POS
1=NONSERV
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
No impact.
No impact.
No impact.
Other
Indications
None.
None.
None.
NE impacts: None.
Subsequent alarms: None.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-67
Issue 3, March 2006
See notice on first page
Fault management
Fault resolution
The fault is caused by provisioning the incorrect IP address for the 1st Hop Router(s).
To resolve the problem, provision the correct IP address.
The fault is caused by incorrect provisioning of the IP address for the 1st Hop
Router(s). To resolve the problem, provision the correct IP address.
See IPBH Provisioning section, in 5ESS Switch Flexent /Autoplex Wireless
Networks Applications OA&M Manual, 235-200-100 or OA&M Manual, 5AP
International.
Use EXC: PING (NAR), EXC-PING (INTL) command to verify connectivity from this
BPH to the 1st hop router. Or use the IP network command EXC:TRCRT,CHNG=cg#
(NAR), EXC-TRCRT:UNIT=a-b-c-d (INTL); Check physical connection to the router
(between L2 switch and router). If this document should mention router specific
debugging tools then -i.e. verify that router ARP policing is not dropping ARPs
received by the router. If in a duplex L2 switch configuration, then verify that the
interswitch trunk is physically connected and operational.
Do the following to correct the fault:
1. Provision the correct IP address for the 1st hop router(s) on the 5ESS DCS Recent
Views form 22.32 (NAR) or 9.37 (INTL).
2. Verify connectivity from the BPH to the 1st hop router, enter the command EXC:
PING (NAR) or , EXC-PING(INTL)
3. Verify connectivity from the BPH to the 1st hop router, enter the command EXC:
TRACERT,CHNG=cg# (NAR) or EXC-TRACERT:UNIT=a-b-c-d (INTL)
4. Check physical connection to the router (between L2 switch/MLS and the router).
5. If this document should mention router specific debugging tools then -i.e. verify
that router ARP policing is not dropping ARPs received by the router.
6. If in a duplex L2 switch configuration, then verify that the interswitch trunk is
physically connected and operational.
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
No impact.
Transport Network
Router Management
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-68
Fault management
Network Element
Edge Router
No impact.
MLS
No impact.
No impact.
RCS
No impact.
ECP
No impact.
5ESS DCS
No impact.
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
Other Indications
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-69
Issue 3, March 2006
See notice on first page
Fault management
No
Ethernet connectivity
.................................................................................................................................................................................................................................
Fault identification
Loss of Layer 2.
Resolution
None.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault
detection
Automatic recovery
BTs
No impact.
No impact.
No impact.
Transport Network
Router
Management
No impact.
No impact.
Edge Router
No impact.
No impact.
No impact.
MLS
Detects loss of
layer 2.
No impact.
No impact.
No impact.
No impact.
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-70
Fault management
No Ethernet connectivity
Network
element
Fault
detection
Automatic recovery
RCS
No impact.
No impact.
No impact.
ECP
No impact.
No impact.
No impact.
5ESS DCS
Low Priority
ARP-beat fails
and no traffic
reception
REPT SM=sm
PSELINK=sm-psu-link
OLD_STAT=ACT
NEW_STAT=OOS-LK
RATE=NOT APPLICABLE
REPT SM=sm
PHGRP=sm-psu-phgrp
OFFNORM NEW STAT POS
1=UNAV POS 0=SERVING
OVERLOAD
SUMMARY=NORMAL
OLD STAT POS 1=NONSERV
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
No impact.
No impact.
No impact.
Other
Indications
None.
None.
None.
NE impacts: None.
Subsequent alarms: None.
Subsequent other indications: None.
Subsequent service impact: None.
Subsequent states: None.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-71
Issue 3, March 2006
See notice on first page
Fault management
No Ethernet connectivity
Fault resolution
BTS
No impact.
Transport Network
Router Management
Edge Router
No impact.
MLS
No impact.
No impact.
RCS
No impact.
ECP
No impact.
5ESS DCS
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
Other Indications
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-72
Fault management
Edge
router card failure affecting all associated DS1 interfaces
.................................................................................................................................................................................................................................
Fault identification
Major.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
BTS
Alarms and
notifications
Automatic recovery
URC reboot. If there is another
active CDMA 1X-URC within
the same cabinet, then automatic
recovery will occur with MLG
sharing. If this URC is the parent
for a DO-URC, then the
DO-URC will be OOS.
Transport Network
Shows
vendor-specific
hardware fault for
the card that
failed.
Router
Management
Edge Router
MLS
No impact.
No recovery.
No impact.
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-73
Issue 3, March 2006
See notice on first page
Fault management
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
No impact.
No impact.
No impact.
RCS
ECP
Updates to SDP,
OMC-RAN and TI.
No impact.
URC ACT
SDP 2237:Shows
MLG OOS
ROP: Receives
5E MCC:No
No impact.
impact.
ROP: If the debug
TPU-GUI:No
impact.
No impact.
EMS:No impact.
None.
OMC-GUI:
OMC-RAN will
display a major
alarm on the AP
Detailed View.
AP Detailed View.
States
None
Other
Indications
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-74
Fault management
NE impacts: None
Subsequent alarms: None
Subsequent other indications: None
Subsequent service impact: Loss of capacity .
Subsequent states: None.
Fault resolution
BTS
If MLG sharing, restore the links to the MLG. If no MLG sharing, the
URC will resume using the local MLG when it finds that it has been
replaced while going through reboot.
Transport Network
Edge Router
Clears the vendor-specific hardware alarms and restores the links to the
MLG.
Router Management
MLS
No impact.
FMM-APs
No impact.
RCS
BTS will notify RCS that the link is back in service. If the RCS had
reported the URC OOS, it is now in service.
ECP
5ESS DCS
No impact.
RNC
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
Other Indications
No impact.
Service impact:
Capacity is restored.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-75
Issue 3, March 2006
See notice on first page
Fault management
Major.
Service impact
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault
detection
Automatic recovery
BTS
Detects BER in
excess of major
alarm
threshold.
No impact.
Transport Network
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-76
Fault management
Network
element
Fault
detection
Router
Management
Automatic recovery
No impact.
No impact.
Edge
Router
Detects loss of
DS1 following
BTS removal.
No impact.
MLS
No impact.
No impact.
No impact.
No impact.
No impact.
No impact.
RCS
No impact.
No impact.
ECP
in any MLG.
ROP: receives Major Alarm.
No impact.
No impact.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
See OMC-GUI
==>
No impact.
on AP Detailed view.
OP:ALARM
OP:ALARM
Other
Indications
OP:CELL
Fault resolution
Fault management
Network element
BTS
Transport Network
Router Management
No impact.
Edge Router
MLS
No impact.
No impact.
RCS
ECP
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
Other Indications
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-78
Fault management
Active
RCS IP goes OOS-F while mate AP is OOS-F
.................................................................................................................................................................................................................................
Fault identification
The active RCS IP goes Out of Service - Fault (OOS-F) while the mate AP is OOS-F.
RCS IP Services Failure: resources on the AP are not available - CCMip failure,
BHGmon alarm no path to backhaul network or Ethernet Interface node (EIN)
failure.
Fault ID: IPBH-FM-FMMAP-1
Service impact
None.
Severity
Critical.
Resolution
None.
Fault detection and automatic recovery
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
BTS
No impact.
No impact.
Transport Network
No impact.
Router
Management
Edge Router
No impact.
No impact.
No impact.
MLS
No impact.
No impact.
No impact.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-79
Issue 3, March 2006
See notice on first page
Fault management
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
No impact.
RCS IP processes
will attempt to
restart.
FMM-APs
If RCS-IM process
is still running, the
RCS IP services
will restart.
If RCS-IM process
are not running, the
RCS IP services
will not restart.
RCS
No impact.
No impact.
ECP
When automatic
recovery is
successful and RCS
IP services come
back, the critical
alarm is cleared.
When automatic
recovery is not
successful, the
critical alarm
remains.
No impact.
5ESS DCS
No impact.
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
OMC-GUI: A critical
alarm displays on AP
Detailed View.
No impact.
Other Indications
Automatic Recovery Actions
NE impacts: None.
Subsequent alarms: None.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-80
Fault management
Fault resolution
BTS
Transport Network
Router Management
No impact.
Edge Router
No impact.
MLS
No impact.
RCS
No impact.
ECP
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-81
Issue 3, March 2006
See notice on first page
Fault management
Network Element
1X RNC
No impact.
OMP-FX
OMC-RAN
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-82
Fault management
One DS1 (T1/E1) in MLG is not configured in edge router (ER), or wrong DS1 is
assigned to MLG in ER, this DS1 will not be in the MLG. Remove it from MLG is
not needed.
No PPP Connection on one DS1 in an MLG (other DS1s have PPP connections).
Fault ID: IPBH-FM-ER-3
Severity
Minor.
Service impact
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
BTS
No impact.
Transport Network
Reflects DS1
interface/sub-interface
OperStatus down.
Router
Management
Edge Router
No impact.
If wrong DS1 is
configured, it is
removed from the
MLG.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-83
Issue 3, March 2006
See notice on first page
Fault management
Network element
Fault detection
Alarms and
notifications
Automatic
recovery
MLS
No impact.
No impact.
No impact.
No impact.
Alarm or notification
on NE interface.
No impact.
RCS
No impact.
No impact.
ECP
No impact.
No impact.
No impact.
No impact.
1X RNC
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
No impact.
alarm on AP Detailed
View.
Other Indications
Router sends
linkDown trap if
enabled.
TI: OP:ALARM
NE impact.s: None.
Subsequent alarms: None..
Subsequent other indications: None
Subsequent service impact: None.
Subsequent states: None.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-84
Fault management
Fault resolution
BTS
Transport Network
Router Management
Edge Router
MLS
No impact.
No impact.
RCS
No impact.
ECP
5ESS DCS
No impact.
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
Other Indications
Service impact
Capacity is restored.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-85
Issue 3, March 2006
See notice on first page
Fault management
Edge
router card failure affecting all associated DS1 interfaces
.................................................................................................................................................................................................................................
Fault identification
Major.
Service impact
The alarms, notifications and automatic recovery actions are identified by network
element (NE):
Fault detection: The location where the fault is detected in the network.
Alarms and notifications: The alarms and outputs that display on the user interface
for the NE.
Automatic recovery actions: Automatic actions that are initiated when the fault is
detected.
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
BTS
AIS alarm.
No impact if APS
switchover is
completed before the
end of 5 seconds.
Transport Network
Shows vendor-specific
hardware fault.
Router
Management
Edge Router
MLS
No impact.
Performs switchover
to the standby router.
No impact.
No impact.
No impact.
No impact.
No impact.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-86
Fault management
Network
element
Fault detection
Alarms and
notifications
Automatic recovery
RCS
No impact.
No impact.
ECP
SDP: No impact.
No impact.
loss messages.
No impact.
5ESS DCS
5E MCC No impact.
No impact.
No impact.
No impact.
OMP-FX
No impact.
No impact.
No impact.
OMC-RAN
No impact.
No impact.
Other
Indications
None.
NE impacts : None.
Subsequent alarms: None.
Subsequent other indications: None
Subsequent service impact: None.
Subsequent states: None.
Fault resolution
The technician replaces the faulty edge router component and then forces a switchback.
The following results occur on the network elements when a fault is corrected:
Network Element
BTS
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
5-87
Issue 3, March 2006
See notice on first page
Fault management
Network Element
Transport Network
Router Management
Edge Router
MLS
No impact.
No impact.
RCS
ECP
SDP: No impact.
ROP: ROP may receive BHA loss messages.
5ESS DCS
ROP: When the debug flag is turned on, ROP reports loss of
BHA if APS switchover cant completed after 5 seconds.
1X RNC
No impact.
OMP-FX
No impact.
OMC-RAN
No impact.
Other Indications
Service impact
None.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
5-88
Service measurements
Overview
.................................................................................................................................................................................................................................
Purpose
This section describes the tools and information that are available for evaluating and
improving performance in an IP backhaul network using Service Measurements (SM).
Contents
SM for IPBH
6-2
6-6
6-9
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
6-1
Issue 3, March 2006
See notice on first page
SM
for IPBH
.................................................................................................................................................................................................................................
New counts
New counts have been added to ECP-SM in support of the RCS/SM to report new cell
counts.
Cell Backhaul (MLG) related counts
Important! Please note that PP blocking in the IP backhaul world implies that
none of the MLGs (including shared MLGs, if any) are available.
These counts may be used for engineering backhaul facilities at the cell.
Call blocking due to MLG capacity limits
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
6-2
SM for IPBH
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
6-3
Issue 3, March 2006
See notice on first page
SM for IPBH
AP-related counts
Total RCS Messages Transmitted from the AP per URCThis count reports the
total number of RCS messages per URC transmitted from an AP to the BTS on the
signaling links. The counts may be used as a critical trigger for AP engineering.
The counts are based on the number of messages from/to the base station that are
directly correlated with AP capacity (processor occupancy) and used for
engineering of RCS instances per AP.
Total RCS Messages Received from the BTS Per URCThis count reports the
total number of RCS messages per URC received from the BTS on the signaling
links. The counts may be used as a critical trigger for AP engineering. The counts
are based on the number of messages from/to the base station that are directly
correlated with AP capacity (processor occupancy) and used for engineering of
RCS instances per AP.
Peak Signaling Traffic Load (downlink) per APThis count provides a measure of
the peak signaling traffic load (in the downlink) per AP, which is the sum total of
loading offered (total bytes transmitted over an individual LAN) at a given AP over
the Ethernet link. The loading is obtained by calculating the volume of Ethernet
traffic transmitted per second. For a given AP, for every 10 seconds, the traffic
loading is compared with the previous maximum number. If the new maximum (or
peak) has been reached, the new value is saved.
Average Signaling Traffic Load (downlink) per APThis count provides a measure
of the average signaling traffic load (in the downlink) per AP, which is the sum
total of loading offered (total bytes transmitted over an individual LAN) at a given
AP over the Ethernet link. The loading is obtained by calculating the volume of
Ethernet traffic transmitted per second sampled over every 10 seconds.
BHS-related counts
The following are new counts to assist in BHS (at either a PSU or a 1X RNC)
engineering:
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
6-4
SM for IPBH
These counts are based on unavailability of packet pipe resources whether it is frame
relay packet pipe (FR) or ATM packet pipe or IP (MLG).
The following existing SM parameters can be referenced when evaluating performance
for IP backhaul:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
6-5
Issue 3, March 2006
See notice on first page
5ESS
measurement reports
.................................................................................................................................................................................................................................
IPBH Backhaul Measurement Report
This report is generated using the OP-TFPHG command for real-time reports or the
OP-TRPHG command to retrieve stored reports.
The counts reported include:
The following counts are reported separately for each BPH associated with the PH
Group. The BPH isidentified by SM-PSU-SHELF-PH:
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
6-6
This report is generated using the OP-TFPHG command for real-time reports or the
OP-TRPHG command to retrieve stored reports. This report provides IP BACKHAUL
PH supplemental measurements. The measurements on this report enhance and provide
greater detail beyond what is available on the IPBH report.
The counts reported include:
The following counts shall be reported separately for each BPH associated with the PH
Group. The BPH shall be identified by SM-PSU-SHELF-PH:
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
6-7
Issue 3, March 2006
See notice on first page
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
6-8
5ESS
DCS TRFM for IPBH
.................................................................................................................................................................................................................................
Purpose
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
OP TRFC30 IPBH
TIME 05:59:30
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SECTION 154: IP BACKHAUL MEASUREMENTS (IPBH)
1234567890123456789012345678901212345678901234567890123456789
IP BACKHAUL PH GROUP SUMMARY REPORT:
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SM PSU PHGRP RXUDPMDG TXUDPMDG RXUDPMSEG TXUDPMSEG RXUDPMBYTE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
1
3530
3530
3530
3530
203
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SM PSU PHGRP TXUDPMBYTE TXUDPMBF TXUDPMPT
TXUDPMLT BPHPBOCC
1234567890123456789012345678901212345678901234567890123456789
3
0
1
203
0
0
3530
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SM
PSU
PHGRP
MAXPBBYTE
MAXBPHOCC
MAJOVLD
CRITOVLD
RXERREFRM
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
1
1364
4
0
0
14828
1234567890123456789012345678901212345678901234567890123456789
SM
PSU
PHGRP
RXERRIPDG
RXERRIPBH
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
1
0
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP BACKHAUL PH GROUP REPORT:
1234567890123456789012345678901212345678901234567890123456789
SM PSU SHLF PH RXEFRM
TXEFRM
RXBYTE
TXBYTE
RXEPAUSE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
0
6 8025
60
524
3
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
1
1 11555
3590
789
269
0
1234567890123456789012345678901212345678901234567890123456789
SM
PSU
SHLF
PH
TXEPAUSE
ENETLOSS
ROUTERFC
TOTPBPKTS
TOTPBBYTE
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
0
6
0
0
0
98534
8279
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
1
1 0
0
0
98529
8279
1234567890123456789012345678901212345678901234567890123456789
SM PSU SHLF PH RXAPMSG TXAPMSG
RXICMP
TXICMP
BPHSERV
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
0
6 611
60
0
0
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
1
1 4141
60
0
0
1800
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
6-9
Issue 3, March 2006
See notice on first page
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
OP TRFC30 IPBHSUP
TIME 06:29:30
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SECTION 153: IP BACKHAUL SUPPLEMENTAL MEASUREMENTS (IPBHSUP)
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP BACKHAUL PH GROUP SUMMARY REPORT:
1234567890123456789012345678901212345678901234567890123456789
SM PSU PHGRP BHACON
BHAHBTO
MAXBHA
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
10
0
0
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
IP BACKHAUL PH GROUP REPORT:
1234567890123456789012345678901212345678901234567890123456789
SM PSU SHLF PH ENET2SHRT ENET2LONG ENETCRC ENETMISA
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
NSENETTYPE
1234567890123456789012345678901212345678901234567890123456789
3
0
0
3 0
0
0
0
150
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
1
10 0
0
0
0
150
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SM
PSU
SHLF
PH
INVIPMAC
IPTOOSHRT
IPCHKSUM
BADIPLEN
IPHDRLEN
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
0
3 7265
0
0
0
0
1234567890123456789012345678901212345678901234567890123456789
3
0
0
3
7265
0
0
0
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
0
3 0
0
0
0
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
1
10 0
0
0
0
0
1234567890123456789012345678901212345678901234567890123456789
SM PSU SHLF PH UDPCHKSUM BADUDPLEN OORUDPPORT UNASSBHA
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SRCIPMIS
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
0
3 0
0
0
0
0
1234567890123456789012345678901212345678901234567890123456789
3
0
1
10
0
0
0
0
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
SM PSU SHLF PH SRCUDPMIS UDPMXSHRT UDPMUXLEN UDPMUXMSEQ
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
3
0
0
3 0
0
0
0
1234567890123456789012345678901212345678901234567890123456789
3
0
1
10 0
0
0
0
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
1234567890123456789012345678901212345678901234567890123456789
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
6-10
Overview
.................................................................................................................................................................................................................................
Purpose
This chapter provides information on hazards, which may arise in the course of your
work.
Contents
Hazard statements
7-2
7-3
7-5
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
7-1
Issue 3, March 2006
See notice on first page
Hazard statements
Overview
.................................................................................................................................................................................................................................
Purpose
7-3
7-5
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
7-2
Structure
of hazard statements
.................................................................................................................................................................................................................................
Overview
Hazard statements describe the safety risks relevant while performing tasks on Lucent
Technologies products during deployment and/or use. Failure to avoid the hazards may
have serious consequences.
General structure
Item
Structure element
Purpose
Signal word
Hazard type
Damage statement
Avoidance message
Identifier
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
7-3
Issue 3, March 2006
See notice on first page
Signal words
Meaning
DANGER
WARNING
CAUTION
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
7-4
General
hazard statements
.................................................................................................................................................................................................................................
Purpose
Provides information on general hazard statements that may arise in the course of your
work, but are not necessarily related to a specific procedure.
DANGER
Electric shock hazard
This equipment generates high leakage current. This can lead to high voltages with
respect to ground for accessible parts of the installation. Contact with these parts can
cause serious health effects, possibly including death, even hours after the event.
This equipment is only suited for permanent connection. Before connecting the power
supply, establish a grounding connection.
WARNING
Electric shock hazard
Contact with energized parts can cause serious injury.
At least one other trained person must be in attendance, who can immediately and
safely disconnect the system if necessary.
This second person must be trained in first aid for emergency purposes.
WARNING
Electric shock hazard
There is a danger of electric shock if the grounding system is inadequate.
You must comply with the grounding requirements for the grounding system.
WARNING
Electric shock hazard
Contact with energized parts can cause serious injury.
Work on energized equipment is only permitted if you are using insulated connection
terminals, are adequately trained and follow safe work practices.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
7-5
Issue 3, March 2006
See notice on first page
WARNING
Electric shock hazard
Contact with energized parts can cause serious personal injury.
Seal off the installation area (warning tape, signs) to prevent untrained or
unauthorized persons from entering.
Follow safe work practices and lockout/tagout procedures.
WARNING
Electric shock hazard
Some parts of all electrical installations are energized. Failure to follow safe work
practices and the safety warnings may lead to bodily injury and property damage.
For this reason, only trained and qualified personnel (electrical workers as defined in
IEC 60215 or EN 60215 + A1 or in the National Electrical Code or in ANSI/NFPA
No. 10) may install or service the installation.
WARNING
Laser hazard
The light from laser and high-radiance LEDs may cause eye damage if absorbed by
the retina.
In the US consult ANSI Z136.2, in Europe consult IEC-60825 Safety of laser products,
for guidance on the safe use of optical fiber communication systems in the workplace.
WARNING
Falling object hazard
Cabinet may tip when it is moved if an obstacle or a downward step is encountered.
Do not use dolly wheels if the installation location has an uneven surface, steps etc.
WARNING
Overhead load hazard
Cabinet eyebolts can break, severely damaging the cabinet, if a crane is used to lift the
cabinet into an upright position.
Ensure that the cabinet is in an upright position before transportation by crane.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
7-6
WARNING
Inhalation hazard
Inhalation of asbestos fibers can result in serious illness or death.
Buildings constructed before 1980 MAY contain asbestos. Buildings constructed before
1970 OFTEN contain asbestos. Potential exposure could occur during routing of cable
or wires, removing cables, removing transite or asbestos cement boards, drilling
wallboard, transite panels, or floor tiles, removing sprayed on fireproofing, moving or
removing ceiling tiles, installing cable hangers.
Do not disturb asbestos. When asbestos is present ensure potential expose is controlled
by adhering to local asbestos management regulations and follow safe work practices.
CAUTION
Service disruption hazard
Condensation can occur in the network element during transport, especially on moving
from outside to closed rooms. Condensation can cause malfunctioning of the circuit
packs.
Ensure that circuit packs and shelves have reached room temperature and are dry
before taking them into operation.
CAUTION
Service disruption hazard
Tools left in the work area can cause short circuits during operation which can lead to
the destruction of units.
Make sure after finishing your work that no tools, testing equipment, flashlights, etc.,
have been left in or on the equipment.
CAUTION
Lifting hazard
Lifting this equipment by yourself can result in injury due to the size and weight of the
equipment.
Always use three people or a lifting device to transport and position this equipment.
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
7-7
Issue 3, March 2006
See notice on first page
CAUTION
Flammable material hazard
The heat vent (grill) at the top of the cabinet can become obstructed, preventing
ventilation of the cabinet.
Make sure that the airvent is not obstructed and remains clear at all times.
CAUTION
ESD hazard
Semiconductor components can be damaged by static discharges.
The following rules must be followed when handling any module containing
semiconductor components:
Wear conductive or antistatic working clothes (for example, a coat made of 100%
cotton).
Wear the grounded wrist strap.
Wear shoes with conductive soles on a conductive floor surface or conductive work
mat.
Leave the modules in their original packaging until ready for use.
Make sure there is no difference in potential between yourself, the workplace, and
the packaging before removing, unpacking, or packing a module.
Hold the module only by the grip without touching the connection pins, tracks, or
components.
Place modules removed from the equipment on a conductive surface.
Test or handle the module only with grounded tools on grounded equipment.
Handle defective modules exactly like new ones to avoid causing further damage.
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
7-8
Glossary
.................................................................................................................................................................................................................................
Numerics
1X RNC
An Ethernet/IP Switch
AP
Application Processor
APS
Adaptive Service
ATM
BER
Backhaul
BHA
Backhaul Association
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
GL-1
Issue 3, March 2006
See notice on first page
Glossary
BHCA
Backhaul Server
A server which bridges bearer path traffic from the IP messages from the BTS onto the
internal busses and protocols of the PSU or RNC for delivery to cards providing frame
selection service.
BHSPH
CCM
Control Fanout
CICC
Call Identifier
CRC
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
GL-2
Glossary
.................................................................................................................................................................................................................................
DACS
E1
European Digital signal level 1 transmission rate 2.048 Mbps. Each E1 frame has 32
time slots
ECP
Edge Router
A network element that terminates the PPP and ML-PPP protocol stacks from the URC
and interchanges packets with IP/Ethernet.
ESD
Electrostatic discharge
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
GL-3
Issue 3, March 2006
See notice on first page
Glossary
EVDO
FAF
Frame Gateway
FID
Feature Identifier
FMM
Frame Relay
FRPH
Frame Selector
.................................................................................................................................................................................................................................
GE
Gigabit Ethernet
GICC
Gateway
.................................................................................................................................................................................................................................
HD
High Density
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
GL-4
Glossary
HSRP
ICMP
Internet Protocol
IPBH
IP Backhaul
IPBTS
LAG
Mbps
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
GL-5
Issue 3, March 2006
See notice on first page
Glossary
MLG
Multi-Layer Switch
MSC
NAR
Nonvolatile Memory
.................................................................................................................................................................................................................................
OMC
Out of service
OSN
PCF
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
GL-6
Glossary
PF3
Packet Fanout
PH
Packet Handler
PHE
Point-to-point
PPP
Point-to-Point Protocol
PS
Packet Switch
PSU
QoS
Quality of Service
.................................................................................................................................................................................................................................
RAN
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
GL-7
Issue 3, March 2006
See notice on first page
Glossary
RNC
SDP
Soft Handoff
SL
Signaling Link
SM
Service Measurements
5ESS Switch Module
SMP
Software Update
SW
Switch
.................................................................................................................................................................................................................................
T1
Traffic Gateway
.................................................................................................................................................................................................................................
Lucent Technologies - Proprietary
401-710-090
See notice on first page
Issue 3, March 2006
GL-8
Glossary
TI
Technician Interface
TPU
UDP
VRRP
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
GL-9
Issue 3, March 2006
See notice on first page
Index
Numerics
1X RNC, 2-15
1XRNC, 4-6
Also see: RNC
1X RNC
TPU GUI, 4-7
1X RNCs
hardware requirements, 1-5
1X RNC
network interface, 1-24
1X1X RNC
network interface, 1-24
.............................................................
.............................................................
B Backhaul network
current, 1-15
IP Backhaul, 1-16
Backhaul protocol handler, 2-13
Backhaul routers
network interface, 1-23
Backhaul server, 2-14, 2-18
Backhaul server association,
2-13
OA&M, 4-3
btseqp
provision, 3-50, 3-50
Build IPBH network, 3-3
.............................................................
C Cable
Fault, 5-30
Cable cut, 5-27
fault, 5-17
cdmeqp
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
IN-1
Issue 3, March 2006
See notice on first page
Index
cell2
provision, 3-44, 3-48
Commands
I/O, 4-29
Configuration
.............................................................
cdme1p, 3-49
E ECP
cdmeqp, 3-49
RC/V, 4-21
Configure
ecp, 3-34
ECPC
RNC, 2-16
provision, 3-34
Edge router
IPBTS, 2-15
Fault, 5-24
remote, 2-7
RCS-AP, 3-37
RCS-IM, 3-37
Convert
GICC, 2-18
to IPBH, 3-3
.............................................................
.............................................................
F Fault, 5-30
D Data packets
lost, 5-24
Delete
DS1/DS0, 3-52
T1, 5-24
monitoring, 4-4
FIDs, 1-2
FMM-AP, 2-10
hardware requirements, 1-5
DS1/DS0
OA&M, 4-5
DS1s, 2-4
install, 3-22
Cable, 5-24
GigE cable
cable, 5-14
FMM-RCS, 3-33
Forms
apeqp, 3-38
PSU, 3-16
.............................................................
H Hardware requirements, 1-5
I/O, 4-29
I/O commands
RNC, 4-9
IN-2
Index
Implementatin
RNC, 3-18
Implementation, 3-1
5ESS DCS, 3-14
IPBH network, 3-3
phases, 3-3
Inputs, 4-29, 4-29
Install
5ESS DCS, 3-14
GICC, 3-18, 3-20, 3-21
IPBTS gateway, 3-20
IPBTS GW, 3-18
Integrity Manager, 3-37
IP addressing, 3-9
O OA&M
RCS-AP, 2-29
requirements, 2-27
RNC, 2-30
IP Backhaul architecture, 2-2
IP Backhaul network, 1-16, 2-1
I/O, 4-29
IPBH network
N Network architecture, 1-19, 2-2
build, 3-3
Network fault management
implementation, 3-3
IPBH network architecture,
1-19
PH provisioning, 3-16
M Messages
IP network
P Performance, 6-1
MLG, 2-5
IPBH
RNC, 4-6
.............................................................
IP conversion, 3-3
install, 3-6
L Layer 3, 5-59
URC, 5-83
BTS, 2-28
.............................................................
IP address, 2-27
BHS, 2-29
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
IN-3
Issue 3, March 2006
See notice on first page
Index
RCS, 2-10
network interface, 1-23
RCS-AP, 2-10, 3-33
configure, 3-37
IP address, 2-29
RCS-IM
configure, 3-37
ECPC, 6-2
RCS-AP, 3-33
RNC, 4-6
Requirements, 1-5
Provisioning
PH, 3-16
hardware, 1-5
IP address, 2-27
PSU2e, 2-12
router, 2-8
software, 1-7
.............................................................
R Radio cluster server, 2-10
Retrieve
BPSN, 3-41, 3-41
fault, 5-14
Fault, 5-24
IP address, 2-30
Technologies, 1-5
OA&M, 4-6
Router requirements, 2-8
Terminology, 1-13
Also see: Glossary
TPU GUI
33.3, 4-12
90.6, 4-17
configuration, 2-16
RC View 9.37 (INTL), 4-17
90.5, 4-17
9.37, 4-17
RMT, 4-3
7-3, 7-5
screens, 4-7
Traffic
signaling, 2-22
user, 2-25
Traffic flow, 1-25
SDP, 4-38
.............................................................
IN-4
Index
.............................................................
V Voice quality problems, 5-24
.................................................................................................................................................................................................................................
401-710-090
Lucent Technologies - Proprietary
IN-5
Issue 3, March 2006
See notice on first page