B9 BSS O&M Routing Configurations Ed06 PDF

Alcatel BSS
B9 BSS O&M Routing

Configurations
BSS Document
Engineering Document
Release B9
3BK 17422 5002 PGZZA Ed.06
BLANK PAGE BREAK
Status
RELEASED
Short title
Engineering Rules
All rights reserved. Passing on and copying of this document, use
and communication of its contents not permitted without written
authorization from Alcatel/Evolium.
2 / 94
3BK 17422 5002 PGZZA Ed.06
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.1
Rules in PCL Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.2
Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1.3
Hardware Coverage Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
CISCO Routers and Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.1
CISCO 2811 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.2
CISCO 3725 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3
CISCO Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.1
WAN Interface Card - 2 Ports Smart Serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.2
WAN Interface Card - 4 Ports EtherSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.3.3
Network Module - 1 Port Channelized E1/T1 ISDN PRI Balanced . . . . . . . . . . .
2.3.4
Network Module - 2 Ports Channelized E1/T1 ISDN PRI Balanced . . . . . . . . . .
2.4
CISCO Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.1
Cisco Type 1 - Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.2
Cisco Type 2 - Compression Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.3
Cisco Type 3 - Extended Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
2.4.4
Cisco Templates Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R / BSC G2 Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.1
General Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.2
Explanations for OMC-R and BSC G2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3
BSC G2 Collocated via X.25 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.1
OMC-R X.25 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.3.2
Connection to BSC G2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4
BSC G2 Remote via PSDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.1
PSDN Subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.4.2
Remote BSC G2 via PSDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5
BSC G2 Connection via Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.1
X.25 Extraction on G2 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.5.2
X.25 Extraction on G2.5 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6
BSC G2 Connection via MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.2
OMC-R Configurations and Needed CISCO Routers . . . . . . . . . . . . . . . . . . . . . . .
3.6.3
Small Number of BSC G2 at MSC Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.4
Large Number of BSC G2 at MSC Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.6.5
Mixed Local and Remote MSC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.7
BSC G2 and A9130 BSC Evolution Comparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R / A9130 BSC Evolution Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.1
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2
Direct IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.1
Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.2.2
Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3
Over Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
4.3.1
4.3.2
4.4
A9130 BSC Evolution IP Address Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
OMC-R / CBC Server Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.1
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2
Adding the CBC Server to the Cisco Router (Type 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.1
Case 1: One Free WIC Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
5.2.2
Case 2: New Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3BK 17422 5002 PGZZA Ed.06
7
11
12
12
12
13
14
15
17
17
17
18
18
19
19
19
19
19
21
22
22
23
23
23
24
24
24
25
25
25
26
26
26
27
29
32
34
35
36
36
36
36
37
37
38
38
39
40
41
41
41
3 / 94
Contents
A9130 BSC Evolution / CBC Server Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

6.1
Direct IP Link Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.1.1
6.1.2
6.2
Ater Interface Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
6.2.1
6.2.2
7
OMC-R / MFS Legacy Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.1
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.2
MFS Legacy and OMC-R in LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
7.3
MFS Legacy and OMC-R in WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8
OMC-R / MFS Evolution Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
8.1.1
8.1.2
8.2
MFS Evolution IP Address Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9
MFS / A-GPS Server Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.1
MFS and A-GPS Server Not Collocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.2
MFS and A-GPS Server Collocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3
Co-localized MFS / BSC Evolution and A-GPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
9.3.1
9.3.2
10 OMC-R / HMI Server and NMC Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.1.1
10.1.2
10.2
PSDN Subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
10.3
X.25 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11 OMC-R / NPA Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.1
Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.2
Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
11.3
Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12 X.25 Default Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.1
BSC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2
OMC-R Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.1
X.25 Configuration Dependant Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.2
X.25 Configuration Default Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.2.3
OSI Configuration Dependant Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3
CISCO Routers Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.1
X.25 and LAPB Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
12.3.2
Line Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix A : CISCO 3640A Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.1
CISCO 3640A - Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.2
CISCO 3640A in BSS O&M Routing Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
A.3
CISCO 3640A - E1 Network Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Appendix B : CISCO 2621XM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
43
44
44
44
45
45
45
47
48
48
48
49
50
50
51
51
53
54
55
56
56
56
57
58
58
58
59
59
61
62
62
62
63
64
67
67
73
79
81
81
83
85
85
86
86
87
Appendix C : Alcatel 36110 Mainstreet X.25 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

C.1
Rack Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.2
Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.2.1
Control Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.2.2
Interface boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
C.3
X.25 Switch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
89
89
89
89
89
90
4 / 94
3BK 17422 5002 PGZZA Ed.06
Contents
Appendix D : Glossary and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
3BK 17422 5002 PGZZA Ed.06
5 / 94
Contents
6 / 94
3BK 17422 5002 PGZZA Ed.06
Preface
Preface
Purpose
It can be found in the "B9 SED Documentation Plan", in "Engineering Rules".

This document describes the generic BSS O&M routing configurations
applicable for all hardware in release B9 of the BSS.
Specifically, it describes the following OEM device interconnections:
OMC-R / BSC
OMC-R / BSC Evolution
OMC-R / MFS
OMC-R / MFS Evolution
OMC-R / CBC Server
OMC-R / HMI Server
OMC-R / NMC
OMC-R / NPA
MFS / A-GPS Server
BSC Evolution / CBC Server.
This document describes the configuration rules applicable to these
configurations, the engineering rules for PCLs, and the generic parameters
required to configure the interfaces.
Note:
3BK 17422 5002 PGZZA Ed.06
Tools such as the RNO and RNP are beyond the scope of this document, as
they are not part of the BSS O&M routing configurations.
7 / 94
Preface
Whats New
In Edition 06
Move the Cisco 2621XM in Appendix: CISCO 2621XM Router (Section B).
Update with right numbering of CISCO interfaces and cables in OMC-R /
BSC G2 Interconnection (Section 3).
Removal of the old NM-4T serial interface from CISCO Interface Modules
(Section 2.3).
Update with OMC-R Configurations and Needed CISCO Routers (Section
3.6.2).
In Edition 05
Introduction of the CISCO 2811 Router (Section 2.1) and WAN Interface Card 4 Ports EtherSwitch (Section 2.3.2).
Simplify the OMC-R / MFS Legacy Interconnection (Section 7).
Update the MFS Evolution IP Address Restrictions (Section 8.2).
Update the A9130 BSC Evolution IP Address Restrictions (Section 4.4).
Reorganise the CISCO Routers and Modules (Section 2) and BSC G2
Connection via MSC (Section 3.6).
Removal of Cisco 4700 and Cisco 2501 routers from this document (too old).
In Edition 04
Define the minimum requirements for each interconnection case.
Update with OMC-R / MFS Evolution Interconnection (Section 8).
Update with Mx-BSC and OMC-R interconnection with Cisco ML-PPP
configuration in Over Ater Interface (Section 4.3).
In Edition 03
The minimum bandwidth for XLARGE is defined as 512 Kbps in X.25
Recommendations (Section 10.3).
In Edition 02
The editorial review performed inside this document.
In Edition 01
The creation of the B9 document.
Audience
This document is intended for:

Marketing Product and Support personnel
Development Center personnel
Technical Assistance Center personnel
Customer Services personnel
Validation and System Specifications personnel.
8 / 94
3BK 17422 5002 PGZZA Ed.06
Preface
Assumed Knowledge
Internal Referenced
Documents
Referenced Documents
Related Documents
3BK 17422 5002 PGZZA Ed.06
None.
[1]
X.25 default parameters

3BK 17025 0102 PGZZA
[2]
X.25 Implementation over Ater

3BK 17004 0003 DSZZA
[ 3]
G2 BSC Engineering Rules

3BK 15006 AAAA PWZZA
[ 4]
Product Configuration Level G2 Transcoder

3BK 15011 AAAA ALZZA
[5]
Product Configuration Level BSC G2

[6]
Product Configuration Level LMT/O&M

[7]
Product Configuration Level PCL A935 MFS

[8]
Product Configuration Level A1353-RA

[9]
GPRS: OMC/MFS security aspects

3BKA20CBR066918
[ 10 ]
G2 TC Engineering rules
3BK 17025 0125 PGZZA
[ 11 ]
B9 BSS Configuration Rules

3BK 17422 5000 PGZZA
[ 12 ]
SFD - Location Services (LCS)

3BK 10204 0540 DTZZA
[ 13 ]
B9 SED Documentation Plan

3BK 10242 0014 DCZZA
[ 14 ]
B8 BSS O&M Routing Configurations

3BK 17421 5002 PGZZA
9 / 94
Preface
10 / 94
3BK 17422 5002 PGZZA Ed.06
1 Introduction
1 Introduction
It describes the Alcatel coding for all the products implies in the O&M BSS
network.
3BK 17422 5002 PGZZA Ed.06
11 / 94
1 Introduction
1.1 Rules in PCL Documents

The PCL documents provide the technical information required to configure the
different items. Each item, or set of items, is designated by an official Technical
Data Sheet (TDS) reference, which is composed of twelve characters:
7 of which indicate the name of the TDS
2 of which indicate the configuration
1 of which indicates the reference
2 of which indicate the edition of the TDS.
The following table lists the TDS names and corresponding PCLs. Note that in
this document, only the TDS references are used.
PCL Document
TDS Name
TDS Description
A1353-RA (see [ 9 ])
LAN****
TDS option
BSC G2 (see [ 6 ])
BSCG2CA
BSC G2 Cables
BSC G2 (see [ 6 ])
ROUTER****
CISCO configurations
G2 Transcoder (see [ 5 ])
G2TCM0
Transcoder HW packages
A9135 MFS (see [ 8 ])
MFSINST
MFS installation parts
LMT/O&M (see [ 7 ])
BSCLINK
Connection to BSC
1.2 Naming Convention

A1353-RA is the commercial name of the G3 OMC-R. In this document, only
the term OMC-R is used.
A9135-MFS is the commercial name of the Multi-BSS Fast Server (MFS). In
this document, the term MFS is used.
A9130 MFS Evolution is the commercial name of the MFS for MX platform.
1.3 Hardware Coverage Restrictions

For more details, refer to [ 12 ].
12 / 94
3BK 17422 5002 PGZZA Ed.06
2 CISCO Routers and Modules

The CISCO routers are defined as the right external equipments for BSS
interconnections in LAN and WAN conenctions.
3BK 17422 5002 PGZZA Ed.06
13 / 94
2.1 CISCO 2811 Router

CISCO 2811 router provides all the Alcatel needed features to replace the
Cisco 3725 router or Cisco 2621XM router.
This router has the following interfaces:
4 high-speed WAN Interfaces Card (HWIC) slots
1 Network Module Enhanced (NME) slot
2 Fast Ethernet 10/100 BaseT ports (RJ-45 connector)
2 USB 1.1 ports
1 console port (RJ-45 connector)
1 auxiliary port (up to 115.2 Kbps)
1 AIM (Advanced Integration Module) slot
For generic Alcatel use, the following modules are selected for this router:
12 port E1/T1 ISDN PRI network module (NM-xCE1/T1-PRI, x=12)
12 ports Smart Serial for WAN interface card (WIC-2T) or
HWIC-4ESW module.
CISCO 2811 characteristics are listed in the following table:
Compact Flash memory
64 MB (upgradable to 256 MB)
DRAM memory
256 MB (upgradable to 768 MB)
Processor type
350 MHz (RISC)
CISCO IOS
Release 12.3(8)T4
Figure 1: CISCO 2811 Router Rear View

Where:
14 / 94
1 Ground connector
4-7 HWIC slots
2-3 FastEthernet ports
8 - ENM slot
3BK 17422 5002 PGZZA Ed.06
2.2 CISCO 3725 Router

Note:
This router has its End-Of-Sale on Mar, 2007.

The CISCO 3725 router has a fixed configuration with the following interfaces:
2 slots for Network Modules
3 slots for WAN interface cards
2 built-in FastEthernet LAN interfaces (RJ-45 connector)
1 single-width slot to install one Network Module
1 double-width slot to install one single-width or double-width Network
Module
1 auxiliary port (RJ-45 connector)
For generic Alcatel use , the following modules are selected for this router:
12 port E1/T1 ISDN PRI network module (NM-xCE1/T1-PRI, x=12)
2 ports Smart Serial for WAN interface card (WIC-2T) or
4 ports Serial network module (NM-4T)
Notices:
All the network modules indicated above are single-width slots.
Two WIC-2T modules perform the same function as one NM-4T module.
The following table lists the characteristics of the CISCO 3725 router.
Processor type
240 MHz IDT R7000 RISC
Flash memory
8 MB, expandable to 32 MB
PCMCIA Flash memory cards are supported
3BK 17422 5002 PGZZA Ed.06
DRAM or SDRAM (1)
32 MB, expandable to 128
NVRAM memory (2)
128 KB
CISCO IOS
Release 12.2(8r) or later
(1)
: It serves two functions: it stores the running configuration and routing tables; and
is also used for packet buffering by the routers network interface.
(2)
: Non-volatile random access memory (NVRAM) stores the system configuration

file and the virtual configuration register.
15 / 94
Figure 2: CISCO 3725 Router Rear View

Where:
1 - Double-width network module slot
6 - Compact Flash slot
2 - Interface card slots
7 - Fast Ethernet 0/0
3 - Power supply
8 - Fast Ethernet 0/1
4 - Auxiliary port
9 - Single-width network module slot
5 - Console port
Unit numbering:
The CISCO 3725 router has unit numbers that identify the interfaces on the
modules and WAN interface cards installed in the router. Unit numbers begin at
0 for each interface type, from right to the left. Modules and WAN interface
cards are identified by interface type, slot number, followed by a forward slash
(/), and then the unit number (for example, FastEthernet 0/0).
16 / 94
3BK 17422 5002 PGZZA Ed.06
2.3 CISCO Interface Modules

These network modules are additional cards for the previously CISCO routers
mentioned, that will be inserted in the empty slots.
2.3.1 WAN Interface Card - 2 Ports Smart Serial

SERIAL1
SERIAL0
SERIAL0
CONN
WIC
2T
CONN
1. The dual-serial port WAN interface cards (WIC-2T) have two serial ports
with asynchronous support of a maximum speed of 115.2 Kbps/port and
minimum speed of 600 bps/port.
2. Two cables are required to support the two ports on the WIC. Each port of a
WIC requires a CAB-SS-X21FC cable.
3. This module is supported on the Cisco 2811 and Cisco 3725 / 2621
routers.
2.3.2 WAN Interface Card - 4 Ports EtherSwitch
Figure 3: Network Module with 4 Ports Cisco EtherSwitch

1. This HWIC-4ESW module is a high-speed WIC card with 4-ports of Cisco
EtherSwitch 10BASE-T/100BASE-TX, supported on the Cisco 2811 router.
2. Each port is a 10/100 switched Ethernet port with RJ-45 connector.
3. Features such as port autosensing, quality of service (QoS), VLAN support
from 802.1x (where x=P, Q, D) standards on the Cisco EtherSwitch HWIC.
4. This module is supported only on the Cisco 2811 router.
3BK 17422 5002 PGZZA Ed.06
17 / 94
2.3.3 Network Module - 1 Port Channelized E1/T1 ISDN PRI Balanced
Figure 4: Network Module with 1 port Channelized E1/T1 ISDN PRI Balanced
1. This module (NM-1CE1/T1-PRI) receives and transmits data bidirectionally
at the E1/T1 rate.
2. The Alcatel recommended usage is the E1 rate of 2.048 Mbps that provides
up to 30 virtual channels.
3. This module requires a cable with RJ-48C male connector.
4. This module is supported on the Cisco 2811 and Cisco 3725 routers.
2.3.4 Network Module - 2 Ports Channelized E1/T1 ISDN PRI Balanced
Figure 5: Network Module with 2 ports Channelized E1/T1 ISDN PRI Balanced
1. This module (NM-2CE1T1-PRI) receives and transmits data bidirectionally at
the E1/T1 rate. It requires a RJ-48C male connector.
2. The Alcatel recommended usage is the E1 rate of 2.048 Mbps that provides
up to 30 virtual channels.
3. This module requires a cable with RJ-48C male connector.
4. This module is supported on the Cisco 2811 and Cisco 3725 routers.
18 / 94
3BK 17422 5002 PGZZA Ed.06
2.4 CISCO Configurations

These Cisco routers differ according to the role they play and thus the type of
modules they include:
2.4.1 Cisco Type 1 - Basic Configuration

It is always co-located at the OMC-R site.
One such router is included in any network configuration and allows the
operator to build a network involving 1 MSC, a maximum of 2 OMC-Rs,
and 30 BSCs (with redundant X.25 connections)
Applicable on Cisco 2811 (or Cisco 3725) router.
2.4.2 Cisco Type 2 - Compression Configuration

It is always co-located at MSC site.
It is defined to increase the number of BSCs G2 supervised by OMC-R,
through the X.25 timeslosts compression.
It used in networks involving 1 MSC or more, a maximum of 2 OMC-R, and
more than 30 BSC G2 (case of redundant X.25 connections)
Applicable on Cisco 2811 (or Cisco 3725) router.
2.4.3 Cisco Type 3 - Extended Configuration

It is always co-located at BSC / MFS Evolution site.
It is defined to route the RIP V2 O&M traffic to standard Ethernet network of
OMC-R.
Applicable on Cisco 2811 (or Cisco 2621XM) router.
2.4.4 Cisco Templates Location

All the Cisco templates files can be retrieved from the Alcatel TD internal
web page:
http://aww.mrc.alcatel.ro/Sec/cisco/cisco.html
3BK 17422 5002 PGZZA Ed.06
19 / 94
20 / 94
3BK 17422 5002 PGZZA Ed.06
3 OMC-R / BSC G2 Interconnection

This chapter describes the OMC-R and all BSC G2 interconnections.
3BK 17422 5002 PGZZA Ed.06
21 / 94
3.1 General Topology

A general topology including BSS network (G2 BSCs) and OMC-R is given
below:
BSC G2
BSC G2
BSC G2
MSC
PSDN
X.25
switch
PCM
X.25
CISCO
Router
X.25
X.25
HSI ports
OMCR
ETH ports
IP
IP
LAN
BSC
Evolution
PCM
TC
MSC
BSC
Evolution
IP
CISCO
Router
Figure 6: OMC-R / BSS Network Interfaces
3.2 Explanations for OMC-R and BSC G2

1. Each BSC G2 communicates with an OMC-R through OSI-CPR boards
(one active, and one in standby, at a time) and always dynamically balanced
the O&M load amongst its available X.25 links.
2. The communication between OMC-R and BSCs G2 is done via the CMIP
and FTAM protocols.
3. The entire remote BSS network site is routed to the local OMC-R site
through the X.25 routing equipment: an X.25 switch or a multiprotocol
router (X.25 + IP).
4. At OMC-R, the X.25 primary link comes always on HSI-0 port and the X.25
redundancy link comes on HSI-1 port.
5. The X.25 redundancy link is mandatory for both BSC G2 and OMC-R. This
link is used for the secured X.25 feature.
In the case of no redundancy, the BSC configuration will be in
degraded mode, in which no service quality is ensured.
6. If there is no X.25 routing equipment, for example, if the BSC is directly
connected to the OMC-R, the X.25 parameters are the same.
However, if there is at least one X.25 equipment between the BSC and OMC-R
(e.g. router, switch+router), some parameters must be different because of the
requirements for a slower interface towards the BSC and a faster interface
towards the OMC-R are required for traffic concentration .
22 / 94
3BK 17422 5002 PGZZA Ed.06
3.3 BSC G2 Collocated via X.25 Switch

This way of connecting BSC G2 to OMC-R via X.25 switch is kept for history.
If is requested by a given customer, the customer will have to find by itself
an X25 switch.
3.3.1 OMC-R X.25 Interface

On each OMC-R configuration, only one HSI board is used for connections with
the BSS. This X.25 interface board HSI has four RS-449 ports. There is only
one communication speed rate of 64 Kbps at the OMC-R level.
On this HSI board:
Two first connectors (0 and 1) are dedicated to only one BSC G2
connection, and are mandatory for redundancy.
The two other connectors (2 and 3) are not used.
The OMC-R link output port of the G2 BSC is located on the CPR board:
Functional:
Bit rates up to 64 kbps using X.21 circuits
Electrical:
CCITT V.11 Standard
3.3.2 Connection to BSC G2

BSC G2
db25
2 x 3BK 07784 JA
V11
X25 SWITCH
V11
3BK 07641 GA
RS449
OMCR HSI Board
Figure 7: OMC-R and BSC G2 via X.25 Switch

The reference for BSC G2 cable is BSCG2CAOAD.
3BK 17422 5002 PGZZA Ed.06
23 / 94
3.4 BSC G2 Remote via PSDN

3.4.1 PSDN Subscription
3 OSI associations are possible in parallel:
1 outgoing CMISE
1 incoming CMISE
1 incoming FTAM
All parallel requests on CMISE level are mapped on the two CMISE
associations. Each association requires one logical channel. Thus, to be
more secured, 4 switched virtual circuits SVC (logical channels) per BSC
link are mandatory.
The rule used to establish the number of logical channels is:
"The number of logical channels is 4 per BSC G2 "
This number is calculated for O&M operations, but must be higher if additional
services are in use (e.g. SMS-CB requires one additional logical channel).
3.4.2 Remote BSC G2 via PSDN

The PSDN provider installs the modem. There is no codification for this item.
G2 BSC are connected to the WAN using a V.11 Modem.
3BK 07641 GA
BSC G2
V11 modem
3BK 07641 GA
RS449
2 x 3BK 07784 JA
PSDN
db32m
V11 modem
V11 modem
Agent Host HSI Board
Figure 8: OMC-R-BSC G2 via PSDN

Description
Quantity
TDS Reference
V11 modem (given by PSDN access

provider)
cable BSC G2 / modem
BSCG2CAOAD
cable modem / OMC-R
HOST400OAG
Table 1: Items for OMC-R-BSC G2 via PSDN
24 / 94
3BK 17422 5002 PGZZA Ed.06
3.5 BSC G2 Connection via Transcoder

3.5.1 X.25 Extraction on G2 TC
The TRCU site and the OMC-R can be directly connected via the V11 interface.
However, if more than a single BSS is to be served by the OMC-R, an X.25
switch is necessary. The maximum number of BSS, which can be connected
via A-ter, is linked to the capacity of this X.25 switch.
The G2 TC output follows the X.25 protocol.
3BK 07744 JA
TRCU
TC G2
25 m
X25 SWITCH
V11
V11
V11
3BK 07641 GA
RS449
OMCR HSI Board

Figure 9: OMC-R-BSC via G2 TC
The following items must be provided for connection via X.25 concentration unit
with TRCUs with G2 TC.
Note:
X.25 Redundancy on the OMC-R and TC sides is mandatory.

Description
Quantity
TDS Reference
Cable G2 TC / X.25 switch
G2TCM0OOF
Cable X.25 switch / OMC-R
HOST400OAG (1)
X.25 SWITCH (2)
(1)
: 2 cable sets and 2 V11 ports are required in the case of X.25 redundancy.
(2)
: 2x 1 board V11/V11 per default. This switch is obsolete and cannot be ordered.
Table 2: Items for OMC-R-BSC Connection via A-ter with G2 TC
3.5.2 X.25 Extraction on G2.5 TC

This is a very seldom case present on the field and going to disappear, kept
for history reasons.
The X.25 extraction strategy on A9125 TC is identical to the strategy used for
G2 TC. Physical interfaces at G2.5 TC follow the X.21 standard.
The A9125 TC can be shared between several BSC G2 using the X.25 switch.
3BK 17422 5002 PGZZA Ed.06
25 / 94
3.6 BSC G2 Connection via MSC

This solution is preferred by Alcatel because of the decreased cost of OMC-R /
BSC G2 connections, in comparison with the connection via PSDN.
3.6.1 Introduction
The A interface between the BSCs G2 and MSC carries the X.25 data
traffic supervision (CMISE and FTAM) over channelized G.703 by using
dedicated time slots.
The extraction of X.25 data from PCM links is done at the MSC site by a
router using its E1 and Serial boards.
The OMC-R is connected to the router via an Ethernet interface for
configuration and maintenance of the router.
The OMC-R is connected to the router via 2 serial ports for X.25 traffic
supervision coming from the BSCs.
An IP backbone can be set between the both MSCs in order to carry the IP
packets from remote HMI server(s) to the OMC-R.
3.6.2 OMC-R Configurations and Needed CISCO Routers

Note:
All the CISCO routers are configured as CISCO Type 1 for the maximum
connection of BSC G2 with redundancy links.
OMC-R Configuration
Router Qty
CISCO Router (defined as CISCO Type 1)
Small
Model 2811 (or 3725) with 1 x E1 port
Standard
Model 2811 (or 3725) with 1 x E1 port
Large 12
Model 2811 with 2 x E1 ports
Large 12
Model 3725 with 3 x E1 ports (*)
X-Large Master
Model 2811 (or 3725) with 2 x E1 ports
X-Large Agent
Model 2811 with 2 x E1 ports
X-Large Agent
Model 3725 with 3 x E1 ports (*).
(*) 3 x E1 ports are composed from one E1 board with 2 ports (NM-2CE1T1-PRI
module) and another one E1 board with 1 port (NM-1CE1T1-PRI module).
26 / 94
3BK 17422 5002 PGZZA Ed.06
3.6.3 Small Number of BSC G2 at MSC Site

This configuration allows max. 1 OMC-R interconnected with max. 15 BSCs
G2 with redundancy at BSC site and without compression on E1 link.
Each OMC-R in small configuration requires one PCM link from MSC to
manage all its BSCs G2.
BSCs
DDF
TCs
DDF
MSC
PCM
CISCO
router
E1 board
FE0
FE1
S0 S1
OMCR
LAN
Figure 10: BSCs G2 / OMC-R via MSC - Small configuration

Maximum distance between the router-OMC-R is 15m.
Maximum distance between the MSC-router is only delimited by PCM
characteristic.
Links between the LAN and OMC-R are supplied with OMC-Rs.
The FE-0 and FE-1 are shown as the Fast Ethernet interfaces.
3.6.3.1 Router Minimum Requirements

1-Port for FastEthernet interface.
2-Ports for Serial WAN Interface Cards.
1-Ports for E1 ISDN PRI module.
The router must supports: X.25, IP, Channelized E1 ISDN PRI Balanced
(G.703).
3BK 17422 5002 PGZZA Ed.06
27 / 94
3.6.3.2 Implementation Tools

Description
Quantity
CISCO ROUTER 2811
TDS reference
ROUTER1OOA01
- Rack
- WIC-2T module
- X.21 Smart Serial cables
- NM-1CE1T1-PRI module
- E1 ISDN PRI cable (RJ-48C)
RS449 X.21 DTE cable (for HSI ports)
3BK 08417 AAAA
PCM cables for BSCs
BSCG2CA[OA,OB][1,2,3,4,5,6,7,8]
PCM cables for TCs
G2TCSM0OO[R,S,5,6,T,U,G,H]
External PCM cable MSC / CISCO
Customer dependent
Ethernet cables (RJ-45)
BSCLINKOOV16
28 / 94
3BK 17422 5002 PGZZA Ed.06
3.6.4 Large Number of BSC G2 at MSC Site

There are 2 generic configurations to be described with the number of BSCs
between 15 and 31 handled by MSC (with redundancy set at MSC site) and
without compression on E1 link.
3.6.4.1 Solution 1 (one router used)

A new E1 board with two E1 ports replaces the existing E1 board. If an empty
E1 network module is available on the router, insert the new board into this
network module.
BSCs
DDF
TCs
DDF
MSC
PCM
CISCO
router
E1
FE0
FE1
S0 S1
OMCR1
LAN
Figure 11: Large number of BSCs at MSC site - Solution 1

The new module is referenced by Cisco as NM-2CE1T1-PRI for Cisco
2811 (or Cisco 3725).
The number of BSC G2 connected is limited to 31 BSCs with redundancy
and without compression on E1 link.
One additional PCM link is needed between the MSC and CISCO router to
carry another max. 15 BSCs with redundancy at BSC site.
3BK 17422 5002 PGZZA Ed.06
29 / 94
3.6.4.2 Solution 1 Router Minimum Requirements

2-Ports for Serial WAN Interface Card.
2-Ports for Channelized E1 ISDN PRI module.
The router must supports: X.25, IP, Channelized E1 ISDN PRI Balanced
(G.703).
3.6.4.3 Solution 1 Implementation Tools

Description
Quantity
CISCO ROUTER 2811 (*):
TDS reference
ROUTER1OOB01
- Rack
- WIC-2T module
3BK 08417 AAAA
PCM cables for BSCs
X (**)
BSCG2CA[OA,OB][1,2,3,4,5,6,7,8]
PCM cables for TCs
X (**)
External PCM cable MSC / CISCO
Customer dependent
Standard Ethernet cables (RJ-45)
3BK 07588 AA
(*) The Cisco 3725 router can be used as well.

(**) Depending of the number of BSCs supervised that consume the maximum
capacity of E1 link.
30 / 94
3BK 17422 5002 PGZZA Ed.06
3.6.4.4 Solution 2 (two routers used for redundancy)

Second router to manage all the X.25 redundancy links; in that case, the first
router will manage only the X.25 primary links.
MSC
PCM
PCM
CISCO
Router
CISCO
Router
X.25
Primary
Links
S0
S1
HSI0
HSI1
X.25
Redundancy
Links
OMCR
Figure 12: Large number of BSCs at MSC site - Solution 2

ALL the BSCs must have the X.25 extraction point at MSC.
ALL the X.25 primary links to be carried through HSI-0 port of the OMC-R.
ALL the X.25 secondary links to be carried through HSI-1 port of the OMC-R.
The both CISCO routers are configured as Cisco type 1.
This solution does not use the X.25 timeslots compression.
3.6.4.5 Solution 2 Router Minimum Requirements

The minimum requirements are the same as defined in Solution 1 Router
Minimum Requirements (Section 3.6.4.2).
3.6.4.6 Solution 2 Implementation Tools

Description
Quantity
CISCO ROUTER 2811 (*)
TDS reference
ROUTER1OOA01
- Rack
- WIC-2T module
- NM-1CE1B-PRI module
RS449 X.21 DTE cable (for HSI

ports)
3BK 08417 AAAA
External PCM cables MSC / CISCOs
Customer dependent
(*) The Cisco 3725 router can be used as well.
3BK 17422 5002 PGZZA Ed.06
31 / 94
3.6.5 Mixed Local and Remote MSC Configuration

The PCM link between the local MSC1 and the remote MSC2 is used for X.25
data transmission. A second CISCO router is used at remote MSC site to
compress the X.25 data and to send over the PCM link between MSCs. One
time slot is sufficient to carry X.25 data for 5-6 BSCs G2.
BSCs
BSCs
DDF
DDF
TCs
TCs
DDF
DDF
PCM
MSC 1
PCM
CISCO1
MSC 2
PCM
PCM
E1 E1
FE0
S0 S1
PCM
OMCR1
PCM
CISCO2
E1 E1
Empty slot
FE1
FE0
S2 S3
FE1
PCM
HMI
OMCR1
LAN 2
LAN 1
Figure 13: BSC G2/OMC-R via MSC - Mixed local and remote MSCs
Explanations :
The CISCO2 router compresses the X.25 time slots, coming from the
BSCs G2 through the remote MSC2.
Afterwards, the compressed X.25 time slots are re-routed over the PCM
link between the MSCs.
The CISCO1 router decompresses the X.25 time slots from the second
router in order to collect the X.25 data of the remote BSCs.
In parallel, CISCO1s role is to connect the BSCs G2 coming through the
local MSC1.
4 TS are dedicated on PCM link between MSC1 and MSC2 for the HMI
user sessions.
3.6.5.1 Router Minimum Requirements

4-Ports for Serial WAN Interface Cards.
2-Ports for E1 ISDN PRI module.
The router must supports: X.25, IP, IP compressed, Channelized E1 ISDN
PRI Balanced (G.703).
32 / 94
3BK 17422 5002 PGZZA Ed.06
3.6.5.2 Recommendations
If the operator cannot provide time slots on its PCM network, then use:
TCP/IP backbone between MSCs if MSCs are at the same location or
Serial ports by adding a serial WAN board in the empty slot of the remote
MSCs.
3.6.5.3 Implementation Tools

Description
Quantity
CISCO ROUTER 2811 (CISCO 1):
TDS reference
ROUTER1OOB01
- Rack
- WIC-2T module
CISCO ROUTER 2811 (CISCO 2):
ROUTER1OOC01
- Rack
3BK 08417 AAAA
PCM cables for BSCs
x (*)
BSCG2CA[OA,OB][1,2,3,4,5,6,7,8]
PCM cables for TCs
x (*)
External PCM cable MSC1 / MSC2
Customer dependent
External PCM cable MSC1 ( DDF) /

CISCO1
Customer dependent
External PCM cable MSC2 ( DDF ) /

CISCO2
Customer dependent
Ethernet cables (RJ-45 connectors)
BSCLINKOOV16
(*) Depending of the number of BSCs supervised that consume the maximum
capacity of E1 link.
3BK 17422 5002 PGZZA Ed.06
33 / 94
3.7 BSC G2 and A9130 BSC Evolution Comparations

For X.25 links (BSC G2)
For ML-PPP links (BSC Evolution)
Only 2 supervision links.
4 16 supervision links.
1 link down => critical alarm raised.
1-2 link(s) down => minor alarm raised.
Difficult to debug and to configure.
Easy to debug and to configure.
Cisco Serial modules and cables (quite

expensive).
IP cables (very cheap).
FTAM over X.25 lower throughput rate.
FTP over ML-PPP higher throughput rate.
Active / Standby links.
Load Sharing Management links.
34 / 94
3BK 17422 5002 PGZZA Ed.06
4 OMC-R / A9130 BSC Evolution Interconnection

It describes the IP direct and Ater connections between the OMC-R and
A9130 BSC Evolution.
3BK 17422 5002 PGZZA Ed.06
35 / 94
4.1 Introduction
The O&M supervision traffic has changed the routing protocol from X.25
(BSC G2) into IP (BSC Evolution) to increase the file transfer rate, for
easier implementation and also for low cost. The FTP over TCP/IP network
infrastructure is used for the file transfer between A9130 BSC Evolution and
OMC-R.
In A9130 BSC Evolution, the two OMCP boards are responsible for supervision
part of the BSS and it provides the logical interface to OMC-R.
These OMCP boards works in active / standby mode.
The A9130 BSC Evolution supports the following two routes to connect
to OMC-R:
Direct IP network via Cisco router configured as RIP V2.
Over Ater Interface via Cisco router configured as ML-PPP.
4.2 Direct IP Network

BSC Evolution uses the external IP address to connect with OMC-R. The O&M
traffic for BSC Evolution is done via its Ethernet port (ETH-3) of the BSC
Evolution and going to OMC-R through a router knowing the RIP V2 protocol.
For BSC Evolution connection, the HSI ports of OMC-R are no more used.
Figure 14: OMC-R and BSC Evolution - Direct Extraction at BSC
4.2.1 Router Minimum Requirements

3-Ports for FastEthernet interface.
The router must supports: IP, RIP V2.
4.2.2 Implementation Tools

Description
Quantity
TDS reference
BSCLINKOOV16
Cisco 2811 router:
ROUTER1OOD01
- rack
- HWIC-4ESW module
36 / 94
3BK 17422 5002 PGZZA Ed.06
4.3 Over Ater Interface

The O&M traffic coming from A9130 BSC Evolution has at least 2 Atermux
links. Recommended links is min. 4.
The last timeslots from Ater are routed by MSC on the PCM link(s) between
the MSC and Cisco router.
Also each timeslot from PCM link(s) are defined as virtual serial interface in
the Cisco router by its E1 controller.
All these virtual serial interfaces are integrated, by the Cisco router, in the
MultiLink PPP interface bundle.
The number of the virtual serial interfaces included in the ML-PPP bundle is
in the range of 4-16 lines.
Note:
The supervision is not lost, if you have only 1 Atermux link available, due to
the load sharing management of ML-PPP links .
Figure 15: OMC-R and BSC Evolution - Extraction at MSC

The OMC-R can supervised max. 7 BSC Evolution on a PCM link due to its
recommended O&M bandwidth of 256 Kbps.

1-Port for E1 ISDN PRI module per each 7 BSC Evolution interconnected.
The router must supports: IP, ML-PPP, Channelized E1 ISDN PRI Balanced
(G.703).
Note:
3BK 17422 5002 PGZZA Ed.06
If the customer follows these minimum requirements then he doesnt need

to use the Alcatel solution, because the supplying and configuration of the
router(s) is under its own responsibility.
37 / 94

Description
Quantity
CISCO ROUTER 2811:
TDS reference
ROUTER1OOC01
- Rack
PCM cable MSC / CISCO
Customer dependent
Standard Ethernet cable
BSCLINKOOV16
4.4 A9130 BSC Evolution IP Address Restrictions

The IP address assigment for A9130 BSC Evolution has the following
restrictions:
In the case of an O&M link on ML-PPP (O&M link over Ater), A9130 BSC
Evolution external addresses must not belong to the network: 1.1.1.0/29.
OMC-Rs or other machines/equipments, with which the A9130 BSC
Evolution interacts, must not belong to the following networks: 172.n.0.0,
where n=16,17,18.
Figure 16: A9130 BSC Evolution IP Address Restrictions

The router is present mandatory in two different (sub)-networks else it
generates immediately an IP address conflict.
Knowing that 172.n.0.0, where n=16,17,18 are internal subnetworks for the
A9130 BSC Evolution, externally to this equipment, these sub-networks
must not be present on the other part of the router.
38 / 94
3BK 17422 5002 PGZZA Ed.06
5 OMC-R / CBC Server Interconnection

It describes the X.25 connection between the OMC-R and CBC Server.
3BK 17422 5002 PGZZA Ed.06
39 / 94
5.1 Presentation
The following figure describes the OMC-R and Celltick CBC Server
interconnection.
BSC 1
BSC 2
BSC 15
MSC
E1 link
(X25 over Ater)
E1 board
CISCO 2811
type 1
3 serial WAN ports

(for X25 links)
HSI
Redundance
X25 links
OMCR
HSI
Single
X25 link
CBS server
(Celltick)
LAN (10/100 Mb/s)
Figure 17: OMC-R and CBC Server Interconnection

The Celltick CBC Server is a Celltick solution to implement the SMS-CBC
function in the GSM network architecture. The Celltick CBC Server is a
SUN Server machine running the Celltick software on the Solaris operating
system. The Celltick is fully responsible with installation and X.25 configuration
for this CBC Server.
The SMS-CBC is a service that can be activated on a given BSC G2 from
OMC-R. The activation of this service checks the X25 routing between CBC
Server and BSC G2. If it is Ok, then this service will be activated on BSC G2.
The CBC Server and BSC G2 connection are using the same X.25 links from
OSI-CPR boards like the ones for O&M purposes.
The X25 serial interface (link) between CBC Server and BSC G2 is configured
in the same way as the X25 serial interface between OMC-R and BSC G2.
40 / 94
3BK 17422 5002 PGZZA Ed.06
5.2 Adding the CBC Server to the Cisco Router (Type 1)

5.2.1 Case 1: One Free WIC Slot
If the customer has no free serial port, but at least one WIC slot is free on
existing Cisco router then another one WIC module and one X.21 smart serial
cable (CAB-SS-X21FC) are needed as indicated in the table below.
Description
Quantity
TDS reference
WIC-2T module
BSCLINKOOJ16
X.21 Smart Serial cable

(CAB-SS-X21FC)
BSCLINKOOJ16
5.2.2 Case 2: New Router

If the customer has no free serial port and no free WIC slot on existing Cisco
router then another full Cisco router 2811 (type 1) has to be ordered with
WIC-2T boards and associated cables as indicated in the table below.
Description
Quantity
TDS reference
CISCO ROUTER 2811:
3BK 17422 5002 PGZZA Ed.06
- Rack
- WIC-2T module
- X.21 Smart Serial cable
41 / 94
42 / 94
3BK 17422 5002 PGZZA Ed.06
6 A9130 BSC Evolution / CBC Server Interconnection

It describes the IP connection between the A9130 BSC Evolution and CBC.
3BK 17422 5002 PGZZA Ed.06
43 / 94
6.1 Direct IP Link Connection

The connectivity between the A9130 BSC Evolution and CBC is realized using
a Cisco router, which it is capable to use IP and X.25 protocols. The A9130
BSC Evolution uses the IP link until reaches the router.
The CBC is still on X.25 at the link with the serial interface of the router. The
Cisco router is responsible to encapsulate the data from IP packets into the
X.25 packets towards CBC.
For the direct IP link connection, X.25 packets from CBC Server are sent over
IP network to the BSC Evolution via the Ethernet ports of SSW RTM board.
BSC
Evolution
IP
IP
IP
Network
CISCO
router
X.25
CBC
Figure 18: BSC Evolution and CBC Server with Direct IP Connection

1-Port for Serial WAN Interface Cards.
The router must supports: X.25, IP, X.25 over IP.

Description
Quantity
CISCO 2811 Router
44 / 94
TDS reference
ROUTER1OOE01
- Rack
- WIC-2T module
- X.21 Smart Serial cable
BSCLINKOOV16
3BK 17422 5002 PGZZA Ed.06
6.2 Ater Interface Connection

For the route over Ater interface, Ater can be extracted only from TP board
inside the BSC Evolution.
The X.25 packets must be first transferred from OMCP board to TP through its
internal IP network, and then ML-PPP interface from router maps X.25 packets
on one or more time slots of Ater interface using E1 link.
External routers are responsible for converting ML-PPP to LAPB, then
transferring to CBC server.
BSC
Evolution
Ater
TC
MSC
PCM
CISCO
router
X.25
CBC
Figure 19: BSC Evolution and CBC over Ater interface

1-Port for Serial WAN Interface card.
1-Port for E1 ISDN PRI module.
The router must supports: X.25, Channelized E1 ISDN PRI Balanced
(G.703).

Description
Quantity
CISCO ROUTER 2811:
ROUTER1OOA01
- Rack
- WIC-2T module
- X.21 Smart Serial cable (CAB-SS-X21FC)
- E1 ISDN PRI cable
3BK 17422 5002 PGZZA Ed.06
TDS reference
45 / 94
46 / 94
3BK 17422 5002 PGZZA Ed.06
7 OMC-R / MFS Legacy Interconnection

It describes the Legacy MFS local and remote connection with OMC-R.
3BK 17422 5002 PGZZA Ed.06
47 / 94
7.1 Presentation
There are two cases to interconnect the OMC-R and MFS Legacy:
Case 1 (LAN): Collocated and in the same subnetwork using an IP switch.
Case 2 (WAN): Not Collocated and in a different subnetwork via a PSDN
network, dedicated leased lines or through a remote MSC.
7.2 MFS Legacy and OMC-R in LAN

The IP switch can emulate the local LAN. This solution is proposed as the
easiest Ethernet infrastructure.
MFS
OMCR
IP
Switch
Figure 20: Legacy MFS and OMC-R in LAN

There is no restriction about the IP addressing for MFS Legacy and OMC-R.
Description
Quantity
TDS Reference
IP Switch external
Customer dependant
Standard Ethernet cables
BSCLINKOOV16
7.3 MFS Legacy and OMC-R in WAN

The remote MFS Legacy and OMC-R in the WAN network is defined using an
intermediate PSDN network.
MFS
HMI
OMCR
IP
Switch
CISCO
IP router
PSDN
CISCO
IP router
Figure 21: Legacy MFS and OMC-R in WAN with PSDN

This interconnection can re-use the present OMC-BSC network.
Router Minimum Requirements:
The router must supports: IP.
48 / 94
3BK 17422 5002 PGZZA Ed.06
8 OMC-R / MFS Evolution Interconnection

It describes the interconnection between OMC-R and MFS Evolution.
3BK 17422 5002 PGZZA Ed.06
49 / 94
8.1 Presentation
The content of this interconnection is still under study !
The OMC-R and A9130 MFS Evolution interconnection requires a router
knowing the RIP V2 protocol with at least 3 Ethernet ports available and its
specific settings for this implementation.
This RIP V2 router must be collocated with the A9130 MFS Evolution.
The A.x is the single floating IP address of the MFS Evolution that is known
by the OMC-R.
The 2 networks (B and C) are internally to the MFS Evolution, not known by
the OMC-R.
The O.w is the default gateway of the OMC-R to be connected to A9130
MFS Evolution.
The O subnetwork is mandatory to be different than A subnetwork.

The router must supports: IP, RIP V2 (its timers changeable), NAT.
Note:
50 / 94
If the customer follows these minimum requirements then he doesnt need

to use the Alcatel solution, because the supplying and configuration of the
router(s) is under its own responsibility.
3BK 17422 5002 PGZZA Ed.06

Description
Quantity
TDS Reference
CISCO 2811 Router:
ROUTER1OOD01
Rack
HWIC-4ESW Module
BSCLINKOOV16
8.2 MFS Evolution IP Address Restrictions

The IP address assigment for MFS Evolution has the following restrictions:
MFS Evolution external addresses must not belong to the following
networks: 172.n.0.0, where n=16,17,18, 19 and 32.
OMC-Rs or other machines/equipments, with which the MX-MFS interacts,
must not belong to the following networks: 172.n.0.0, where n=16,17,18, 19
and 32.
Figure 22: MFS Evolution IP Address Restrictions

These 172.n.0.0 (where n=16,17,18, 19 and 32) subnetworks are allowed
for MFS Legacy, but not for MFS Evolution.
3BK 17422 5002 PGZZA Ed.06
51 / 94
52 / 94
3BK 17422 5002 PGZZA Ed.06
9 MFS / A-GPS Server Interconnection

It describes the MFS and A-GPS Server connection using the TCP/IP over
Ethernet solution.
3BK 17422 5002 PGZZA Ed.06
53 / 94
9.1 MFS and A-GPS Server Not Collocated

Regardless of whether the MFS and A-GPS Server are collocated or not, a
router will be used to interconnect them. The router is external to the MFS,
which implies that it is not supervised by the MFS, so that there is no need to
model it. The MFS with the router in front of it presents only one IP address
to the A-GPS server. Reciprocally, the A-GPS server presents only one IP
address to the router in front of the MFS.
This router must be NAT capable to allow the MFS to present only one IP
address to the A-GPS Server.
The router must be configured in such a way as to support dynamic N to 1
source NAT. A firewall is also recommended to isolate the MFS as much as
possible from the external network.
When the router is configured in dynamic N to 1 source NAT, it behaves as
follows:
When a GPU sends a request to the A-GPS server, regardless of the GPU,
the router replaces (in the output IP header) the internal IP address of this
GPU (for example 1.1.1.53) with the external address
The A-GPS server sends the response to the request to this external
address and the router performs the reverse operation (replacing the
destination IP address by 1.1.1.53, for example).
The 1.1.1.x and 2.2.2.x are the default gateway IP addresses . These values
are coded in the MFS and can be changed using BUL files.
LAN 1
AGPS
Server
MFS
IP
Router
OMCR
LAN 2
Figure 23: MFS and external A-GPS Server - Not Collocated

Its source address, its destination address and the application port identify the
request from the GPU sent to the external A-GPS Server. This information
is kept in memory of the router and it is able to make the match between the
source GPU address and the external address, using the application port.
Router Minimum Requirements:
The router must supports: IP, NAT dynamic.
54 / 94
3BK 17422 5002 PGZZA Ed.06
The IP router is in charge of the LCS related traffic and is not supervised
by MFS. It is recommended not to use this router also for O&M traffic (on
OMC-R/MFS interface).
The router can be configured on-line, i.e. without any reset. Therefore, if the
external router for the communication with OMC-R is re-used to support
communication with A-GPS server(s), the router can be reconfigured
without any O&M outage .
9.2 MFS and A-GPS Server Collocated

Normally these machines are on different sub-networks, and therefore a router
has to be used. The two Ethernet interfaces of the router towards MFS must be
configured with the following default gateway IP addresses: 1.1.1.10 and
respectively 2.2.2.10. These values are coded in MFS and can be changed
using BUL files. In the figure below, the two switches are considered to be
internal part of MFS block.
LAN 1
AGPS
Server
MFS
OMCR
Router
LAN 2
Figure 24: MFS and A-GPS Server collocated

Optionally, this figure also shows the possibility of having an OMC-R collocated
with the MFS. In this case, the split is done for LCS related traffic and O&M
traffic.
Description
Quantity
TDS Reference
MFS
Customer dependant
A-GPS Server
Customer dependant
Cisco 2811 Router:
ROUTER1OOD01
BSCLINKOOV16
- Rack
- HWIC-4ESW Module
(RJ-45)
3BK 17422 5002 PGZZA Ed.06
55 / 94
9.3 Co-localized MFS / BSC Evolution and A-GPS Server

The IP access between A-GPS server and co-localized MFS / BSC Evolution
is ensured through ML-PPP links over A-ter provided between the TP board
and the MSC, up to the IP router of the customer.
There is no IP access on the BSC Evolution site. The following figure shows
this configuration.
MFS/BSC
Switch 1
TP board
Switch 2
IP routing
MSC
GP
Board
IP NAT
Router
IP
Network
AGPS
Server
Figure 25: A-GPS Server with co-localized with MFS

1-Port for E1 ISDN PRI module.
The router must supports: IP, NAT

Description
Quantity
TDS Reference
MFS/BSC + OCM cables
Customer dependant
A-GPS Server
Customer dependant
Cisco 2811 router:
ROUTER1OOD01
- Rack
- HWIC-4ESW Module
Ethernet cables with RJ-45 connectors
56 / 94
BSCLINKOOV16
3BK 17422 5002 PGZZA Ed.06
10 OMC-R / HMI Server and NMC Interconnection

It describes the OMCR and HMI / NMC connection via PSDN.
3BK 17422 5002 PGZZA Ed.06
57 / 94
10.1 Presentation
The following figure shows an example for an OMC-R having a remote HMI
server and NMC through WAN network (PSDN).
HMI 1
LAN
CISCO
2621
Master
PSDN
NMC
CISCO
2621
Agent
HMI2
CISCO
2811
Figure 26: OMC-R and Remote HMI / NMC

The OMC-R and NMC can be collocated or not, however in both cases seen is
the Ethernet interface.

The router must supports: X.25, IP, IP over X.25.

Description
Quantity
CISCO 2811 Router
ROUTER1OOE01
- Rack
- WIC-2T module

(CAB-SS-X21FC)
58 / 94
TDS Reference
BSCLINKOOV16
3BK 17422 5002 PGZZA Ed.06
10.2 PSDN Subscription

One PSDN connection is used for the remote HMI server. The subscription
needed depends on the number of remote user sessions.
The following table gives the baud rate and the number of Switched Virtual
Circuits SVC (two ways logical channels) according to number of sessions:
SUBSCRIPTION Remote HMI Server => OMC-R
Number of remote sessions
Baud rate speed
Number of Logical Channels

SVC
from 1 to 5
256 Kbps (1)
Table 3: PSDN Subscription: Baud rate and SVC for remote HMI
Note 1): 64 Kbps in case of compression with CISCO router.
Notice: This table is available at the Host site and the remote HMI site. For
more details, see [ 12 ].
10.3 X.25 Recommendations

The following bandwidths for X.25 links are recommended in the case of
different OMC-R configurations:
OMC-R Configurations
Maximum Real G2 BSC
Recommended X.25 Bandwidth per Link
SMALL
10
64 Kbit/s
STANDARD
20
128 Kbit/s
LARGE1
35
256 Kbit/s
LARGE2
45
256 Kbit/s
X-LARGE AGENT
40
512 Kbit/s
X-LARGE MASTER
35
512 Kbit/s
3BK 17422 5002 PGZZA Ed.06
59 / 94
60 / 94
3BK 17422 5002 PGZZA Ed.06
11 OMC-R / NPA Interconnection

It describes the OMCR and NPA connection with local or remote NPA clients.
3BK 17422 5002 PGZZA Ed.06
61 / 94
11.1 Presentation
Usually the OMC-R and NPA are collocated in the same LAN. The remote NPA
Client(s) can be connected to NPA Server through a WAN network (PSDN) as
well as the local NPA Client(s) in LAN.
The following figure shows the interconnection between the OMC-R / NPA
Server with local and remote NPA Client(s). The possible HMI on the remote
side (LAN2) is optional.
LAN 1
LAN 2
OMCR
NPA
server
HMI
CISCO
2621/
2811
CISCO
2621/
2811
PSDN
NPA
client
NPA
client
Figure 27: OMC-R / NPA Server with Mixed NPA Client(s)

The remote NPA Client is connected to the NPA Server through WAN network
(PSDN).
11.2 Router Minimum Requirements

The router must supports: X.25, IP, IP over X.25.
11.3 Implementation Tools

Description
Quantity
CISCO 2811 Router
62 / 94
TDS Reference
ROUTER1OOB01
- Rack
- WIC-2T module

(CAB-SS-X21FC)
3BK 17422 5002 PGZZA Ed.06
12 X.25 Default Parameters

This section describes the default X.25 parameters used to configure different
links.
To discourage any patching of DLS relations, no description of the DLS will
be given in this document.
3BK 17422 5002 PGZZA Ed.06
63 / 94
12.1 BSC configuration

X.25 Connection via a Switch
Connection through PSDN
BSC G2
BSC G2
BSS - OMC primary X.25 address
(8)
(11)
BSS - OMC secondary X.25 address
(9)
(12)
OMC primary X.25 address
Mandatory
mandatory
OMC secondary X.25 address
optional ( 2 )
optional ( 2 )
BSS - CBC primary X.25 address
(4)
(4)
BSS - CBC secondary X.25 address
(4)
(4)
X.25 extraction
BSC
BSC
Maximum number of retransmission
Frame timer T1 (x100 ms)
2 (13)
Frame window size
07
07
Number of virtual circuits
04 (5),(10)
04 (5),(10)
Max. simultaneous virtual circuits
04 (5),(10)
04 (5)
Throughput class for transmission

(bps)
64000
64000
Throughput class for reception (bps)
64000
64000
Throughput class negotiation
No
No
Packet size for transmission (bytes)
256 (6)
256 (6)
Packet size for reception (bytes)
256 (6)
256 (6)
Window size for transmission
04
03
Window size for reception
04
03
Max number of bytes in the I-frame
259 (7)
259 (7)
Local window between RFH and FTAM
03
03
64 / 94
3BK 17422 5002 PGZZA Ed.06
X.25 connection via Ater interface (BSC G2)
Extraction at TC site
Extraction
at MSC site
Extraction via
CISCO
BSS - OMC primary

X.25 address
mandatory
mandatory
mandatory
BSS - OMC secondary

X.25 address
mandatory (1)
mandatory
(1)
mandatory (1)
OMC primary X.25

address
mandatory
mandatory
mandatory
OMC secondary X.25

address
optional ( 2 )
optional ( 2 )
optional ( 2 )
BSS - CBC primary

X.25 address
(4)
(4)
(4)
BSS - CBC secondary

X.25 address
(4)
(4)
(4)
X.25 extraction
TRCU
MSC
MSC
Maximum number of
retransmission
Frame timer (timer T1)

(100 ms)
Frame window size
07
07
07
Number of virtual
circuits
04 (5),(10)
04 (5),(10)
08 (5)
Max. Simultaneous
Virtual Circuits
04 (5)
04 (5)
08 (5)
Throughput class for

transmission (bps)
48000
48000
64000
Throughput class for

reception (bps)
48000
48000
64000
Throughput class
negotiation
No
No
No
Packet size for

transmission (bytes)
256 (6),(14)
256 (6),(14)
256 (6),(14)
Packet size for

reception (bytes)
256 (6),(14)
256 (6),(14)
256 (6),(14)
Window size for

transmission
03
03
3BK 17422 5002 PGZZA Ed.06
65 / 94
Extraction
at MSC site
Extraction via
CISCO
Window size for

reception
03
03
Max number of bytes

in the I-frame
259 (7),(14)
259 (7),(14)
259 (7),(14)
Local window between

RFH and FTAM
03
03
03
Table 4: X.25 Parameters for the BSC

Notes:
1. X.25 address of the 2nd link connected to the BSC in the case of redundancy
at the BSC side.
2. X.25 address of the 2nd link connected to the OMC-R in the case of
redundancy or load sharing.
3. Not relevant, a CBC cannot be connected directly to the BSC (no collocated
BSC/CBC).
4. Mandatory only if a CBC is connected to the BSC.
5. Number of virtual circuits must be equal to maximum simultaneous virtual
circuits.
6. Packet sizes for transmission and reception must have the same values,
see note 7.
7. This value must be greater than the maximum packet size on the network.
8. This field is mandatory but must be left empty in the case where the X.25
address is declared at the X.25 switch port.
9. This field is optional (X.25 address of the 2nd link connected to the BSC in
the case of redundancy at BSC side) but must be left empty in the case
where the X.25 address is declared at the X.25 switch port.
10. Add 2 virtual circuits if the BSC is, or will be, connected to an external CBC.
11. This field is mandatory but must be left empty if connecting via Transpac.
Transpac itself will add the caller address (BSC address) in the X.25 packets.
12. This field is optional (X.25 address of the 2nd link connected to the BSC in
the case of redundancy at BSC side) but must be left empty if connecting
via Transpac. Transpac itself will add the caller address (BSC address) in
the X.25 packets.
13. Timers for Transpac network are respectively 400ms and 100ms i.e.
parameter values 4 and 1.
14. Mandatory value, do not change.
66 / 94
3BK 17422 5002 PGZZA Ed.06
12.2 OMC-R Configuration

All required modifications must be done on the OMC-R using the X.25 tool with
root permission, on different switches or routers when they are used.
12.2.1 X.25 Configuration Dependant Parameters

BSC G2
BSC G2
Link number
0 or 1 (1)
0 or 1 (1)
Link Description
What ever you like (2)
Link type
WAN (3)
WAN (3)
Device
(18)
(18)
Port number
0 or 1 (1)
0 or 1 (1)
TxClock
External (3), (9)
External (3), (9)
Frame window size
Interface
DTE (3)
DTE (3)
Lap Mode
LAPB (3)
LAPB (3)
Local X121 Address
(5)
(11)
Version
1984 (3)
1984 (3)
Local default
256 (3)
256 (3)
Local maximum
256 (3)
256 (3)
Remote Default
256 (3)
256 (3)
Remote Maximum
256 (3)
256 (3)
Frame Timer T1 (100 ms)
Link Editor Window
Link Editor / Packet size (bytes)
Table 5: X.25 parameters via Switch/PSDN for OMC-R
3BK 17422 5002 PGZZA Ed.06
67 / 94

BSC G2

BSC G2
PVC Minimum
0 (6)
0 (6)
PVC Maximum
0 (6)
0 (6)
SVC incoming Minimum
0 (6)
0 (6)
SVC incoming Maximum
0 (6)
0 (6)
SVC Two way Minimum
1 (3)
1 (3)
SVC Two Way Maximum
(19)
(19)
SVC Outgoing Minimum
0 (6)
0 (6)
SVC Outgoing Maximum
0 (6)
0 (6)
Force use of local address (12)
Omit source address (12)
Link Editor / Logical Channel range
Advance Configuration / Link modes

Source Address Control (7)
Advance Configuration / Throughput Window / Throughput class

Local Minimum
3 (6)
3 (6)
Local Default
12 (3)
12 (3)
Local Maximum
13 (6)
13 (6)
Remote Minimum
3 (6)
3 (6)
Remote Default
12 (3)
12 (3)
Remote Maximum
13 (6)
13 (6)
Negotiate towards Defaults
No (3)
No (3)
Advance Configuration / Throughput Window / Packet size ( bytes )

Max NSDU length
256 (3)
256 (3)
Advance Configuration / Throughput Window / Network profile

Modulo
68 / 94
8 (3)
8 (3)
3BK 17422 5002 PGZZA Ed.06

BSC G2

BSC G2
Advance Configuration / Throughput Window / Window Sizes (packets)

Local Default
Local Maximum
Remote Default
Remote Maximum
Number of bytes in I-frame
261
261
Advance Configuration / LAPB Parameters

Ack Timer [T1]
(3), (17)
2 (16)
Max. RR delay
(3), (17)
1 (16)
Table 6: X.25 LAPB Parameters via Switch/PSDN for OMC-R
3BK 17422 5002 PGZZA Ed.06
69 / 94
X.25 Connection via Ater Interface (BSC G2)
Extraction at MSC
site
Extraction via CISCO
Link number
0 or 1 (1)
0 or 1 (1)
0 or 1 (1)
Link Description
Link type
WAN (3)
WAN (3)
WAN (3)
Device
(18)
(18)
(18)
Port number
0 or 1 (1)
0 or 1 (1)
0 or 1 (1)
TxClock
External (3), (15)
External (14)
External (14)
Frame window size
Interface
DTE (3)
DTE (3)
DTE (3)
Lap Mode
LAPB (3)
LAPB (3)
LAPB (3)
Local X121 Address
(5)
(5)
(5)
Version
1984 (3)
1984 (3)
1984 (3)
Link Editor Window
Link Editor / Packet size (bytes)

Local default
256 (3)
256 (3)
256 (3)
Local maximum
256 (3)
256 (3)
256 (3)
Remote Default
256 (3)
256 (3)
256 (3)
Remote Maximum
256 (3)
256 (3)
256 (3)
Table 7: X.25 parameters via Ater for OMC-R
70 / 94
3BK 17422 5002 PGZZA Ed.06
Extraction at MSC
site
Link Editor / Logical Channel Range

PVC Minimum
0 (6)
0 (6)
0 (6)
PVC Maximum
0 (6)
0 (6)
0 (6)
SVC incoming
Minimum
0 (6)
0 (6)
0 (6)
SVC Incoming
Maximum
0 (6)
0 (6)
0 (6)
SVC Two way

Minimum
1 (3)
1 (3)
1 (3)
SVC Two Way

Maximum
Varying (8)
Varying (8)
1024 (must the same in router)
SVC Outgoing
Minimum
0 (6)
0 (6)
0 (6)
SVC Outgoing
Maximum
0 (6)
0 (6)
0 (6)
Force use of local

address (12)
Force use of local address (12)
Advance Configuration / Link Modes

Source Address
Control
Force use of local

address (12)
Advance Configuration / Throughput Window / Throughput Class

Local Minimum
3 (6)
3 (6)
3 (6)
Local Default
12 (3)
12 (3)
15 (3)
Local Maximum
13 (6)
13 (6)
15 (3)
Remote Minimum
3 (6)
3 (6)
3 (6)
Remote Default
12 (3)
12 (3)
15 (3)
Remote Maximum
13 (6)
13 (6)
15 (3)
Negotiate towards
Defaults
No (3)
No (3)
No (3)
Advance Configuration / Throughput Window / Packet Size (bytes)

Max NSDU length
256 (3)
256 (3)
576 (3)
Advance Configuration / Throughput Window / Network Profile
3BK 17422 5002 PGZZA Ed.06
71 / 94
Modulo
Extraction at MSC
site
8 (3)
8 (3)
8 (3)
Advance Configuration / Throughput Window / Window Sizes ( packets)

Local Default
Local Maximum
Remote Default
Remote Maximum
Table 8: X.25 LAPB Parameters via Ater for OMC-R

Notes:
1. Values must be identical:
0: primary link,
1: secondary link if present.
2. This is the name of the link.
3. Mandatory value, do not change.
4. The link clock is internally generated by the OMC-R. The BSC uses the
clock received from the OMC-R.
5. The X.25 local address supplied by the X.25 supplier must be the OMC
primary X.25 address ( link number 0) or OMC secondary X.25 address
(link number 1).
6. Not used, do not change the values.
7. To force the OMC-R to insert its own address in the X.25 packet.
8. Value is equal to 3 times the maximum number of BSS to be connected (3
virtual circuits per BSC).
9. The link clock is provided to the OMC-R externally by the X.25 switch. The
X.25 switch is also in charge of providing the clock link towards the BSC.
10. The link clock is externally provided to the OMC-R. It is the responsibility
of the PSDN network to provide the link clock.
11. This field is mandatory but must be left empty if connecting via Transpac.
12. Depends on whether the switch or the router is configured to insert the
OMC-R address in the X.25 packets. If so, use the option Omit source
address otherwise use Force use of local address. It is network dependent.
13. Transpac itself will add the caller address ( BSC address) in the X.25 packet.
14. The link clock is externally provided to the OMC-R. It is the responsibility of
the intermediate network or switch used between the MSC and the OMC-R.
72 / 94
3BK 17422 5002 PGZZA Ed.06
15. In case of a direct connection, the link clock is internally generated by

the OMC-R, or else the link clock is externally provided to the OMC-R. It
is the responsibility of the intermediate network or switch used between
the TC and the OMC-R.
16. Specific to connection via Transpac.
17. Default values.
18. HSI if an E4500 is used, HSIP in case of an E450 (and all machines with
PCI bus).
19. Without use of the CBC, the required value is equal to 3 times the maximum
number of BSS to be connected ( 3 virtual circuits per BSC) else the
value is 4.
12.2.2 X.25 Configuration Default Parameters

This section gives the default values for the advanced configuration parameters
related to an X.25 link on the Sun side. Default parameters are given as a
reference to check the link configuration.
All parameters are related to the SUN Solstice 9.2 X.25 tool utility.
If no specific value is given in the link configuration section, use the default
value as stated in the following tables.
Values off or on used in the tables specify the button related to the
option in the X.25 tool utility interface.
3BK 17422 5002 PGZZA Ed.06
73 / 94
12.2.2.1 Advanced Configuration / LAPB, WAN

LAPB Parameters
Ack Timer [T1]
20
P-bit Timer
Reject Timer
24
Busy-state Timer
100
Link Idle Timer
250
Max. RR delay
Max. Tries [N2]
10
Max. UnACKed IPDUs
Transmit Probe
Enable X.32 Authentication
No
WAN Parameters
Calling Procedure
None
Link Conformance
Ignore UA if on ERROR state
off
FR receipt of FR if in ERROR
off
FR on Inv. Resp.if in ERROR
off
Send FR if S_Frame & no P-bit
off
No DM on entry to ADM state
off
Abandon X.32 registration on SAB
off
ISO 8882 conformance
off
Initial state of link is Off
off
74 / 94
3BK 17422 5002 PGZZA Ed.06
12.2.2.2 Advanced Configuration / Addressing

Extended Address
None
12.2.2.3 Advanced Configuration / CUG and Facilities

Closed User Group
CUG, no other access
off
Preferential CUG
off
CUG, with outgoing access
off
CUG, with incoming access
off
Reject incoming CUG calls
off
CUG Format
BASIC
Facilities
Incoming reverse charging
off
Local charging prevention
off
Bar incoming calls
off
Bar outgoing calls
off
Allow TOI/NPI addressing
off
Bar TOI/NPI addressing
off
Allow NUI override
off
Bar outgoing during X.32 registration
off
Size Negotiation
Request size negotiation
off
Disallow size negotiation
off
Fast select
With no restriction on response
off
With restriction on response
off
3BK 17422 5002 PGZZA Ed.06
75 / 94
12.2.2.4 Advanced Configuration / Link Modes

Allow omission of diagnostic packets
off
Use diagnostic packets
off
Restrict clear lengths
off
Disallow diagnostic packets
off
Discard diagnostics on non-zero LCN
off
Allow hex digits in DTE addresses
off
Bar non-privileged listeners
off
Strict ISO 8882 conformance
off
Keep X.121 address in Call Request to LAN
off
Insert X.121 address in Call Indication from LAN
off
Process priority according to DATAPAC (1976) rules
off
Prioritize international calls
off
Priority encoding
No special action
Outgoing International Calls
Not distinguished
National DNIC
0000
Forced Packet size
Default
Source Address Control
No special action
12.2.2.5 Advanced Configuration / Throughput Class

See section related to the type of link because these parameters are closely
linked to the link type (either 9.6 kbps or 64 Kbps) or link configuration.
76 / 94
3BK 17422 5002 PGZZA Ed.06
12.2.2.6 Advanced Configuration / Timers and Counters

X.25 timers
Restart Response [T20]
1800
Call Req. Response [T21]
2000
Reset Response [T22]
1800
Clear Req. Response [T23]
1800
DTE window status [T24]
750
Window rotation [T25]
1500
Interrupt Response [T26]
1800
Registration Request [T28]
10
Pending Ack Delay
DTE / DCE Resolution
2000
Idle Disconnect (LAN or Dialup)
X.25 Retransmission Counters

DTE Restart Request [R20]
DTE Clear Request [R23]
DTE Reset Request [R22]
DTE Registration Request [R28]
X.25 Transmit Delays

Internal Delay
Line Delay
3BK 17422 5002 PGZZA Ed.06
77 / 94
12.2.2.7 Advanced Configuration / Special

D-bit Control
Call Accept In
Clear call
Call Accept Out
Clear call
Data In
Reset call
Data Out
Reset call
Throughput Class Packet / Window Mapping

Throughput Class Type
Normal Negotiation
12.2.2.8 Advanced Configuration / X.32 Authentication

Enable X.32 Authentication
78 / 94
No
3BK 17422 5002 PGZZA Ed.06
12.2.3 OSI Configuration Dependant Parameters

This section gives the default values required to configure stack components,
network layers addresses and static routing at Sun side.
All parameters are related to the SUN Solstice 9.2 ositool utility.
12.2.3.1 Device Configuration

This value specifies the maximum simultaneous inbound or outbound
connections.
Stack Manager/Devices/X.25 device
200
Connection pool
12.2.3.2 Resource Configuration

These values are used to adjust the internal resource of the stack with the
context and channel parameters.
Stack Manager/Resources
transport over CONS
Contexts
1024
Channels
1024
CONS
Contexts
1024
Channels
1024
Stack Manager/Resources
low interface
Contexts
1024
Channels
1024
3BK 17422 5002 PGZZA Ed.06
79 / 94
12.2.3.3 Transport over CONS

Stack Manager/Resources/Transport over CONS/Additional Option
Max Multiplexing (initiator)
18
Max Multiplexing (acceptor)
18
QOS threshold / nfc
QOS threshold / mpx
Max size / nofc
100
12.2.3.4 CONS
Stack Manager / Resources / CONS
17
Connection Timer (*10s)
12.2.3.5 Route Manager

The "Prefix Route" values adjusts the NSAP prefix by adding or deleting
information. The X.25 menu sets the type of X.25 service required for the
CONS configuration.
Route Manager / Category / Prefix Route / X.25 Service
Link Type
1980
Addressing
CONS-80
80 / 94
3BK 17422 5002 PGZZA Ed.06
12.3 CISCO Routers Configuration

The router configuration is done by typing in command mode line either locally
from the console (VT terminal) or remotely via a telnet session. Alternatively,
the commands can be prepared in a text file and then transferred to the
router via FTP.
12.3.1 X.25 and LAPB Parameters

The following values are default values except when shown in bold.
Parameter
Serial Board for OMC (Value to

OMC)
E1 Board for BSC via MSC

(Value to BSC)
Encapsulation lapb
no
No
Encapsulation X.25
dce
dce
Lapb interface-outage (ms)
Lapb k (frames)
Lapb modulo
Lapb n1 (bit)
12056
12056
Lapb counter n2
20
10
Lapb protocol
none
None
Lapb t1 (ms)
3000
5000
Lapb t4 (s)
15
X.25 accept-reverse
disabled
Disabled
X.25 address
X.25 bfe-decision
no
No
X.25 bfe-emergency
never
Never
X.25 default
no
No
X.25 facility
none
None
X.25 hic
X.25 hoc
X.25 hold-queue (frames)
30
30
X.25 hold-vc-timer (minutes)
X.25 htc
1024
3BK 17422 5002 PGZZA Ed.06
81 / 94
Parameter

OMC)

(Value to BSC)
X.25 idle
X.25 ip-precedence
disabled
Disabled
X.25 ips (input packet size) (bytes)
256
256
X.25 lic
X.25 linkrestart
enabled
Enabled
X.25 loc
X.25 ltc
X.25 map
not used
not used
X.25 map bridge
not used
not used
X.25 map cmns
not used
not used
X.25 map compressedtcp
not used
not used
X.25 map pad
not used
not used
X.25 modulo
X.25 nvc
X.25 ops (output packet size)

(bytes)
256
256
X.25 pad-access
accept all
accept all
X.25 pvc (encapsulation)
not used
not used
X.25 pvc (switched)
not used
not used
X.25 pvc (tunnel)
not used
not used
X.25 remote red
not used
not used
X.25 routing
enabled
Enabled
X.25 rpoa
none
None
X.25 suppress-called-address
off
Off
X.25 suppressed-cabling-address
off
Off
X.25 t10 (sec.)
60
60
X.25 t11 (sec.)
180
180
X.25 t12 (sec.)
60
60
82 / 94
3BK 17422 5002 PGZZA Ed.06
Parameter

OMC)

(Value to BSC)
X.25 t13 (sec.)
60
60
X.25 t20 (sec.)
not used
not used
X.25 t21 (sec.)
not used
not used
X.25 t22 (sec.)
not used
not used
X.25 t23 (sec.)
not used
not used
X.25 th (packet)
X.25 use-source-address
disabled
Disabled
X.25 incoming window size
X.25 outgoing window size
12.3.2 Line Parameter

Parameter
Type
OMC
BSC
Clock rate
bps
250000
BSC transmitter delay

(G2 BSC)
flags
100
3BK 17422 5002 PGZZA Ed.06
83 / 94
84 / 94
3BK 17422 5002 PGZZA Ed.06
Appendix A : CISCO 3640A Router
Appendix A: CISCO 3640A Router

A.1 CISCO 3640A - Product Description
The CISCO 3640 has slots that accept a variety of network module interface
cards, including LAN and WAN mixed media cards supported Ethernet, Fast
Ethernet, Token Ring and a variety of WAN technologies. These cards provide
the foundation of LAN and WAN connectivity on a single, modular, network
module. Additional applications are supported with a series of network module
cards offering digital modems, asynchronous and synchronous Serial, ISDN
PRI and ISDN BRI interfaces.
For generic Alcatel use, only the following modules are chosen:
4 port Ethernet network modules
4 port serial network modules
E1 ISDN PRI network modules
1 Fast Ethernet port
CISCO 3640A routers have the following characteristics:
Slots available for modules
Processor type
100 Mhz IDT R4700 RISC
Flash memory
8 MB, expandable to 32 MB
PCMCIA Flash memory cards are supported,
available in 4 to 16 MB
Main memory
32 MB standard, expendable to 64 MB
DRAM or SDRAM memory (1)
32 MB, expandable to 128
NVRAM memory (2)
128 KB
Standard components
2 PCMCIA slots
CISCO IOS
Release 12.0(4), 12.1(8) or later.
Table 9: Characteristics of CISCO 3640A Router

(1) serves two functions: it stores the running configuration and routing tables
and is used for packet buffering by the routers network interface
(2) Non Volatile Random Access Memory (NVRAM) stores the system
configuration file and the virtual configuration register.
3BK 17422 5002 PGZZA Ed.06
85 / 94
Appendix A : CISCO 3640A Router
SLOT 3
SLOT 2
SLOT 1
SLOT 0
power
supply
ON/OFF
Switch
Figure 28: CISCO 3640A Rear View

Unit numbering:
The CISCO 3600 series routers have unit numbers that identify the interfaces
on the modules and WAN interface cards installed in the router. Unit numbers
begin at 0 for each interface type, and continue from right to left, and (if
necessary) from bottom to top. Modules and WAN interface cards identify the
interface type, slot number, followed by a forward slash (/), and then the unit
number (for example, Ethernet 0/0).
A.2 CISCO 3640A in BSS O&M Routing Configurations

The CISCO 3640A was used especially in the following configurations:
BSC connection to OMC-R via MSC,
Connection of MFS to a distant OMC-R through a G.703 leased line,
Connection of Remote MFS to OMC-R via MSC.
A.3 CISCO 3640A - E1 Network Module

E1
PRI
CT1/PRI
Leds
DB15
Enable Led
Figure 29: Network Module - 1 port Channelized E1/ISDN PRI Balanced

This obsolete module is referred to as 1 Port Channelized E1/ISDN PRI
Balanced (NM-1CE1B).
It receives and transmits data bidirectionally at the E1 rate of 2.048 Mbps, and
provides up to 30 virtual channels.
86 / 94
3BK 17422 5002 PGZZA Ed.06
Appendix B : CISCO 2621XM Router
Appendix B: CISCO 2621XM Router

CISCO 2621XM router provides the versatility needed to adapt to the evolutions
in network technology.
This router has a fixed configuration with the following interfaces:
1 Network module slot
2 WAN Interfaces Card (WIC) slots
2 Fast Ethernet 10/100 BaseT ports (RJ-45 connector)
1 auxiliary asynchronous port (RJ-45 connector) to connect modems,
passive terminals...
1 AIM (Advanced Integration Module) slot
CISCO 2621XM characteristics are listed in the following table:
Flash memory
8 MB
DRAM memory
40 MB (with upgrade DRAM 32 to 40 MB)
Processor type
50 MHz (RISC)
CISCO IOS
Release 12.2
ON/OFF
Switch
Wan Interface Card slots
(WIC)
I
O
SLOT 0
Network module Slot
power
supply
Ethernet ports
(RJ45)
Auxiliary port
(RJ45)
Console port
(RJ45)
Figure 30: CISCO 2621XM Router Rear View
3BK 17422 5002 PGZZA Ed.06
87 / 94
Appendix B : CISCO 2621XM Router
88 / 94
3BK 17422 5002 PGZZA Ed.06
Appendix C : Alcatel 36110 Mainstreet X.25 Switch
Appendix C: Alcatel 36110 Mainstreet X.25 Switch

This multiprotocol concentrator belongs to the MainStreet family and has a
modular architecture. It is delivered with the V.11 interface board. Cascading of
Alcatel 36110 MainStreet Multiprotocol Concentrators is possible in order to
support the full range of BSC served by one OMC-R.
Note:
The terms switch or concentrator will be used equally.
C.1 Rack Layout

X25
X25
X25
X25
X25
X25
X25
X25
PAD
PAD
Power
X25
X25
X25
X25
X25
X25
X25
X25
PAD
PAD
Slot number
Slots 1 to 7
V.35 and V.11boards
Slots 1 to 9
V.28 boards
Figure 31: Alcatel 36110 MainStreet Multiprotocol Concentrator - Rack Layout

Slot 0: reserved to control board.
Slots 8 and 9: reserved to PAD lines or local network boards.
C.2 Hardware Description

C.2.1 Control Board
The control board assumes switching functions, routing and operation on
the network.
The board is on slot 0.
It has one X.21 interface (DB-15 female connector).
C.2.2 Interface boards

One type is used for the connections with BSC:
V11
Is used only for connections with BSC 64 kbits/s
Is used for connections with OMC-R (2 links if redundancy else 1 link)
It has two DB-15 female connectors per board (one per BSC or OMC-R).
Locations are available on slots 1 to 7 but due to the maximum capacity of
the concentrator (512 Kbits/s) only 8 BSC 64 kbits/s will be connected which
means a maximum of 4 boards. A maximum of 5 boards can be used on the
whole as one board must be used for OMC-R connection.
3BK 17422 5002 PGZZA Ed.06
89 / 94
C.3 X.25 Switch Configuration

NE Port 1 )
OMC Port 2 )
MNEmonic
what ever you like (5)
what ever you like (5)
ConFIdentiality
Line ADDress
(8)
(9)
PVCs number
000
000
USe of v.c. 0
WaRnings Validation
Data Compression Sub
Fac. Rever. charg
Fac.fAst Select
Fac. Through. class
Fac. Outgoing access
Rec. pack. Wind. Size
02
02
Rec. Packet Length
08
08
Rec. THroughput class
12
12
Rec. Max. Thr. class
13
13
ACCes : connection type
LEA
LEA
Counter N2
05
10
TiMer t2
0003
0003
POLling level 2
V25BiS
00
00
MoDulo level 3 (MD3)
CoeF min of Quality
20
20
Transfer MODe
DCE
DCE
Line routing TYPe
SU
SU
NETwork mode
NUI to send
InS. Address
90 / 94
3BK 17422 5002 PGZZA Ed.06
NE Port 1 )
OMC Port 2 )
SVCs number
03 (3)
varying (3)
STat. Validation
Standby INdication
NETwork profile
PR0
PR0
Reser. Prior. Calls
000
000
Fac. flow Control
Fac. Incom. access
Fac. Prev. Charging
Trans. Pack. Wind. Size
02
02
Trans. Packet Length
08
08
Trans. THrough. class
12
12
Trans. Max. Thr. class
13
13
ACCes : network
LEA
LEA
FRame window size (K)
07
07
TiMer t1
0020
0020
CLocK speed
08 (6) or 00 (7)
08 (6)
Timer Carrier Lost 109
0100
0100
MoDuLo level 2
Back-up LeaSed line
NUI facility treatment
Table 10: X.25 Switch Parameters

Notes:
1. NE port configuration can be linked with either a G2 BSC or a G2 TC .
2. Use always this configuration for the OMC port, regardless of the type of
BSC configuration.
3. Add 2 virtual circuits if the BSC is, or will be, connected to an external CBC.
4. The value is equal to 3 times the number of BSC to be connected (3 virtual
circuits per BSC) to that OMC through that X.25 switch.
5. To make configuration layout more readable.
3BK 17422 5002 PGZZA Ed.06
91 / 94
6. The X.25 switch provides the clock for both BSC and OMC ports, that is,
both ports are configured as DCE from a clock generation point of view.
7. Straps on X.25 switch boards may have to be configured. (Refer to the
related Installation Manual)
8. In the case of extraction at the TC site, clock is provided by the TC to the
X.25 switch, and X.25 port has to be configured as DTE from a clock
generation point of view.
9. The clock speed parameter is set to 00 because the clock is external.
10. The parameter is left void if the BSC X.25 address has been explicitly
defined in the DLS.
11. Otherwise this field must be defined with the BSC X.25 address.
12. Parameter is left void if the OMC-R does send its X.25 address explicitly.
13. Otherwise this field must be defined with the OMC X.25 address.
92 / 94
3BK 17422 5002 PGZZA Ed.06
Appendix D : Glossary and Abbreviations
Appendix D: Glossary and Abbreviations
3BK 17422 5002 PGZZA Ed.06
A-ter
Interface between MSC and BSC
AUI
Attachment Unit Interface
BNC
Type of coaxial connector used for LAN Ethernet 10-base2 (thin)
BSC
Base Station Controller
BSS
Base Station System
BTS
Base Transceiver Station
CBC
Cell Broadcast Center
CMIP
Common Management Information Protocol
CMISE
Common Management Information Service Element
CS
Control Station
DCN
Data Communication Network
DDF
Digital Distribution Frame
FTAM
File Transfer Access Management
GPRS
General Packet Radio service
GSL
GPRS Signaling Link
GSM
Global System for Mobile communication
HSI
High-speed Serial Interface
I-MFS
Internet Multi Functions Server
IOS
Internet Operating System
IP
Internet Protocol
ISDN
Integrated Digital Service Network
ISL
Internal Serial Link
LAN
Local Area Network
MB
Megabyte
MFS
Multi-bss Fast packet Server
MII
Milan
ML-PPP
MultiLink Point-to-Point Protocol
MSC
Mobile services Switching Center
NE
Network Element
NMC
Network Management Center
NPA
Network Performance Analyzer tool
OEM
Original Equipment Manufacturer
O&M
Operation and Maintenance
OMC-R
Operation and Maintenance Center-Radio
PAD
Packet Assembler Disassembler
PCI
Peripheral Component Interconnect
PCL
Product Configuration Level
93 / 94
Appendix D : Glossary and Abbreviations
94 / 94
PCM
Pulse code Modulation
PLMN
Public Land Mobile Network
PSDN
Packet Switch Data Network
PM
Performance Management
Q3
Q protocol N 3
RNO
Radio Network Optimization tool
RNP
Radio Network Planning tool
TC
TransCoder
TCH
Traffic Channel
TCP
Transmission Control Protocol
TDS
Technical Data Sheet
TRCU
Transcoder Rate adaptation Control Unit
X.25
X.25 link.
WAN
Wide Area Network
3BK 17422 5002 PGZZA Ed.06

B9 BSS O&M Routing Configurations Ed06 PDF

Загружено:

Сведения о документе

Исходное описание:

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

B9 BSS O&M Routing Configurations Ed06 PDF

Загружено:

Авторское право:

Доступные форматы

Alcatel BSS

B9 BSS O&M Routing

3BK 17422 5002 PGZZA Ed.06

BLANK PAGE BREAK

3BK 17422 5002 PGZZA Ed.06

3BK 17422 5002 PGZZA Ed.06

A9130 BSC Evolution / CBC Server Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Appendix C : Alcatel 36110 Mainstreet X.25 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3BK 17422 5002 PGZZA Ed.06

Appendix D : Glossary and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

3BK 17422 5002 PGZZA Ed.06

3BK 17422 5002 PGZZA Ed.06

It can be found in the "B9 SED Documentation Plan", in "Engineering Rules".

3BK 17422 5002 PGZZA Ed.06

This document is intended for:

3BK 17422 5002 PGZZA Ed.06

3BK 17422 5002 PGZZA Ed.06

X.25 default parameters

X.25 Implementation over Ater

G2 BSC Engineering Rules

Product Configuration Level G2 Transcoder

Product Configuration Level BSC G2

Product Configuration Level LMT/O&M

Product Configuration Level PCL A935 MFS

Product Configuration Level A1353-RA

GPRS: OMC/MFS security aspects

B9 BSS Configuration Rules

SFD - Location Services (LCS)

B9 SED Documentation Plan

B8 BSS O&M Routing Configurations

3BK 17422 5002 PGZZA Ed.06

3BK 17422 5002 PGZZA Ed.06

1.1 Rules in PCL Documents

A9135 MFS (see [ 8 ])

MFS installation parts

1.2 Naming Convention

1.3 Hardware Coverage Restrictions

3BK 17422 5002 PGZZA Ed.06

2 CISCO Routers and Modules

2 CISCO Routers and Modules

3BK 17422 5002 PGZZA Ed.06

2 CISCO Routers and Modules

2.1 CISCO 2811 Router

64 MB (upgradable to 256 MB)

256 MB (upgradable to 768 MB)

350 MHz (RISC)

Figure 1: CISCO 2811 Router Rear View

4-7 HWIC slots

2-3 FastEthernet ports

3BK 17422 5002 PGZZA Ed.06

2 CISCO Routers and Modules

2.2 CISCO 3725 Router

This router has its End-Of-Sale on Mar, 2007.

240 MHz IDT R7000 RISC

3BK 17422 5002 PGZZA Ed.06

DRAM or SDRAM (1)

32 MB, expandable to 128

NVRAM memory (2)

Release 12.2(8r) or later

: Non-volatile random access memory (NVRAM) stores the system configuration

2 CISCO Routers and Modules

Figure 2: CISCO 3725 Router Rear View