b9 bss o&m routing configurations ed06.pdf
TRANSCRIPT
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
1/94
Alcatel BSS
B9 BSS O&M RoutingConfigurations
BSS Document
Engineering Document
Release B9
3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
2/94
Status RELEASED
Short title Engineering Rules
All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel/Evolium.
BLANK PAGE BREAK
2 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
3/94
Contents
Contents
Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 Rules in PCL Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2 Naming Convention . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.3 Hardware Coverage Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2 CISCO Routers and Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 CISCO 2811 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.2 CISCO 3725 Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152.3 CISCO Interface Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.3.1 WAN Interface Card - 2 Ports Smart Serial . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3.2 WAN Interface Card - 4 Ports EtherSwitch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172.3.3 Network Module - 1 Port Channelized E1/T1 ISDN PRI Balanced . . . . . . . . . . . 182.3.4 Network Module - 2 Ports Channelized E1/T1 ISDN PRI Balanced . . . . . . . . . . 18
2.4 CISCO Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.4.1 Cisco Type 1 - Basic Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.4.2 Cisco Type 2 - Compression Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.4.3 Cisco Type 3 - Extended Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192.4.4 Cisco Templates Location . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
3 OMC-R / BSC G2 Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.1 General Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.2 Explanations for OMC-R and BSC G2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223.3 BSC G2 Collocated via X.25 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.3.1 OMC-R X.25 Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.3.2 Connection to BSC G2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.4 BSC G2 Remote via PSDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.4.1 PSDN Subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
3.4.2 Remote BSC G2 via PSDN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 243.5 BSC G2 Connection via Transcoder . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.5.1 X.25 Extraction on G2 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.5.2 X.25 Extraction on G2.5 TC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
3.6 BSC G2 Connection via MSC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.6.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 263.6.2 OMC-R Configurations and Needed CISCO Routers . . . . . . . . . . . . . . . . . . . . . . . 263.6.3 Small Number of BSC G2 at MSC Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.6.4 Large Number of BSC G2 at MSC Site . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.6.5 Mixed Local and Remote MSC Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.7 BSC G2 and A9130 BSC Evolution Comparations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344 OMC-R / A9130 BSC Evolution Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
4.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2 Direct IP Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2.1 Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.2.2 Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
4.3 Over Ater Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.3.1 Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.3.2 Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
4.4 A9130 BSC Evolution IP Address Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 385 OMC-R / CBC Server Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
5.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 405.2 Adding the CBC Server to the Cisco Router (Type 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.2.1 Case 1: One Free WIC Slot . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
5.2.2 Case 2: New Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
3BK 17422 5002 PGZZA Ed.06 3 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
4/94
Contents
6 A9130 BSC Evolution / CBC Server Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 436.1 Direct IP Link Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.1.1 Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 446.1.2 Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
6.2 Ater Interface Connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.2.1 Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 456.2.2 Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
7 OMC-R / MFS Legacy Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 477.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.2 MFS Legacy and OMC-R in LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 487.3 MFS Legacy and OMC-R in WAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
8 OMC-R / MFS Evolution Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 498.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
8.1.1 Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 508.1.2 Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
8.2 MFS Evolution IP Address Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 519 MFS / A-GPS Server Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
9.1 MFS and A-GPS Server Not Collocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 549.2 MFS and A-GPS Server Collocated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 559.3 Co-localized MFS / BSC Evolution and A-GPS Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
9.3.1 Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 569.3.2 Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
10 OMC-R / HMI Server and NMC Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5710.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10.1.1 Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5810.1.2 Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
10.2 PSDN Subscription . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5910.3 X.25 Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
11 OMC-R / NPA Interconnection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6111.1 Presentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6211.2 Router Minimum Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6211.3 Implementation Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
12 X.25 Default Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6312.1 BSC configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6412.2 OMC-R Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
12.2.1 X.25 Configuration Dependant Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6712.2.2 X.25 Configuration Default Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7312.2.3 OSI Configuration Dependant Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
12.3 CISCO Routers Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8112.3.1 X.25 and LAPB Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
12.3.2 Line Parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Appendix A : CISCO 3640A Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
A.1 CISCO 3640A - Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85A.2 CISCO 3640A in BSS O&M Routing Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86A.3 CISCO 3640A - E1 Network Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
Appendix B : CISCO 2621XM Router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
Appendix C : Alcatel 36110 Mainstreet X.25 Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89C.1 Rack Layout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89C.2 Hardware Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
C.2.1 Control Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89C.2.2 Interface boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
C.3 X.25 Switch Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
4 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
5/94
Contents
Appendix D : Glossary and Abbreviations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
3BK 17422 5002 PGZZA Ed.06 5 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
6/94
Contents
6 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
7/94
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 configurationsapplicable 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 parametersrequired to configure the interfaces.
Note: Tools such as the RNO and RNP are beyond the scope of this document, asthey are not part of the BSS O&M routing configurations.
3BK 17422 5002 PGZZA Ed.06 7 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
8/94
Preface
Whats New In Edition 06Move 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 05Introduction of the CISCO 2811 Router (Section 2.1) and WAN Interface C ard - 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-PPPconfiguration in Over Ater Interface (Section 4.3) .
In Edition 03The minimum bandwidth for XLARGE is defined as 512 Kbps in X.25 Recommendations (Section 10.3) .
In Edition 02The editorial review performed inside this document.
In Edition 01The 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
9/94
Preface
Assumed Knowledge
Internal ReferencedDocuments
None.
Referenced Documents [ 1 ] X.25 default parameters3BK 17025 0102 PGZZA
[ 2 ] X.25 Implementation over Ater3BK 17004 0003 DSZZA
[ 3] G2 BSC Engineering Rules3BK 15006 AAAA PWZZA
[ 4] Product Configuration Level G2 Transcoder3BK 15011 AAAA ALZZA
[ 5 ] Product Configuration Level BSC G23BK 15006 AAAA ALZZA
[ 6 ] Product Configuration Level LMT/O&M
3BK 15014 AAAA ALZZA[ 7 ] Product Configuration Level PCL A935 MFS
3BK 15030 AAAA ALZZA
[ 8 ] Product Configuration Level A1353-RA3BK 15031 AAAA ALZZA
[ 9 ] GPRS: OMC/MFS security aspects3BKA20CBR066918
[ 10 ] G2 TC Engineering rules3BK 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 Plan3BK 10242 0014 DCZZA
Related Documents [ 14 ] B8 BSS O&M Routing Configurations3BK 17421 5002 PGZZA
3BK 17422 5002 PGZZA Ed.06 9 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
10/94
Preface
10 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
11/94
1 Introduction
1 Introduction
It describes the Alcatel coding for all the products implies in the O&M BSSnetwork.
3BK 17422 5002 PGZZA Ed.06 11 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
12/94
1 Introduction
1.1 Rules in PCL DocumentsThe PCL documents provide the technical information required to configure thedifferent items. Each item, or set of items, is designated by an official TechnicalData Sheet (TDS) reference, which is composed of twelve characters:
7 of which indicate the name of the TDS2 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 inthis document, only the TDS references are used.
PCL Document TDS Name TDS Description
A1353-RA (see [ 9 ]) LAN**** TDS optionBSC 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 ConventionA1353-RA is the commercial name of the G3 OMC-R. In this document, onlythe term OMC-R is used.
A9135-MFS is the commercial name of the Multi-BSS Fast Server (MFS). Inthis document, the term MFS is used.
A9130 MFS Evolution is the commercial name of the MFS for MX platform.
1.3 Hardware Coverage RestrictionsFor more details, refer to [ 12 ].
12 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
13/94
2 CISCO Routers and Modules
2 CISCO Routers and Modules
The CISCO routers are defined as the right external equipments for BSSinterconnections in LAN and WAN conenctions.
3BK 17422 5002 PGZZA Ed.06 13 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
14/94
2 CISCO Routers and Modules
2.1 CISCO 2811 RouterCISCO 2811 router provides all the Alcatel needed features to replace theCisco 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:
1 Ground connector 4-7 HWIC slots
2-3 FastEthernet ports 8 - ENM slot
14 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
15/94
2 CISCO Routers and Modules
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 NetworkModule
1 auxiliary port (RJ-45 connector)
1 console 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
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; andis also used for packet buffering by the routers network interface.
(2) : Non-volatile random access memory (NVRAM) stores the system configurationfile and the virtual configuration register.
3BK 17422 5002 PGZZA Ed.06 15 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
16/94
2 CISCO Routers and Modules
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 themodules and WAN interface cards installed in the router. Unit numbers begin at0 for each interface type, from right to the left. Modules and WAN interfacecards 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
17/94
2 CISCO Routers and Modules
2.3 CISCO Interface ModulesThese network modules are additional cards for the previously CISCO routersmentioned, that will be inserted in the empty slots.
2.3.1 WAN Interface Card - 2 Ports Smart Serial
CONN
WIC2T
SERIAL0
SERIAL0
SERIAL1
CONN
1. The dual-serial port WAN interface cards (WIC-2T) have two serial portswith asynchronous support of a maximum speed of 115.2 Kbps/port andminimum speed of 600 bps/port.
2. Two cables are required to support the two ports on the WIC. Each port of aWIC requires a CAB-SS-X21FC cable .
3. This module is supported on the Cisco 2811 and Cisco 3725 / 2621routers .
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 CiscoEtherSwitch 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 supportfrom 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
18/94
2 CISCO Routers and Modules
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 bidirectionallyat the E1/T1 rate.
2. The Alcatel recommended usage is the E1 rate of 2.048 Mbps that providesup 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 atthe E1/T1 rate. It requires a RJ-48C male connector .
2. The Alcatel recommended usage is the E1 rate of 2.048 Mbps that providesup 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
19/94
2 CISCO Routers and Modules
2.4 CISCO ConfigurationsThese Cisco routers differ according to the role they play and thus the type ofmodules 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 theoperator 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, andmore 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 ofOMC-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 internalweb page:
http://aww.mrc.alcatel.ro/Sec/cisco/cisco.html
3BK 17422 5002 PGZZA Ed.06 19 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
20/94
2 CISCO Routers and Modules
20 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
21/94
3 OMC-R / BSC G2 Interconnection
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
22/94
3 OMC-R / BSC G2 Interconnection
3.1 General TopologyA general topology including BSS network (G2 BSCs) and OMC-R is givenbelow:
PCM
MSC
BSC G2 BSC G2
PSDN
CISCORouter
X.25switch
BSC G2
HSI ports
OMCRIP
LANBSC
Evolution
BSCEvolution
TCMSC
ETH ports
CISCORouter
X.25
X.25
IP
PCM
IP
X.25
Figure 6: OMC-R / BSS Network Interfaces
3.2 Explanations for OMC-R and BSC G21. Each BSC G2 communicates with an OMC-R through OSI-CPR boards
(one active, and one in standby, at a time) and always dynamically balancedthe O&M load amongst its available X.25 links.
2. The communication between OMC-R and BSCs G2 is done via the CMIPand FTAM protocols.
3. The entire remote BSS network site is routed to the local OMC-R sitethrough the X.25 routing equipment: an X.25 switch or a multiprotocolrouter (X.25 + IP).
4. At OMC-R, the X.25 primary link comes always on HSI-0 port and the X.25redundancy link comes on HSI-1 port.
5. The X.25 redundancy link is mandatory for both BSC G2 and OMC-R. Thislink is used for the secured X.25 feature.
In the case of no redundancy, the BSC configuration will be indegraded 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
23/94
3 OMC-R / BSC G2 Interconnection
3.3 BSC G2 Collocated via X.25 SwitchThis 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 itselfan X25 switch.
3.3.1 OMC-R X.25 Interface
On each OMC-R configuration, only one HSI board is used for connections withthe BSS. This X.25 interface board HSI has four RS-449 ports. There is onlyone 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 G2connection , 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
RS449
OMCR HSI Board
V113BK 07641 GA
2 x 3BK 07784 JA
BSC G2
db25
V11X25 SWITCH
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
24/94
3 OMC-R / BSC G2 Interconnection
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 CMISEassociations. Each association requires one logical channel. Thus, to bemore secured, 4 switched virtual circuits SVC (logical channels) per BSClink 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 additionalservices 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.
RS449
Agent Host HSI Board
BSC G2
PSDN
V11 modem
V11 modem
V11 modem
2 x 3BK 07784 JA
4
3BK 07641 GA
db32m
Figure 8: OMC-R-BSC G2 via PSDN
Description Quantity TDS Reference
V11 modem (given by PSDN accessprovider)
3 -
cable BSC G2 / modem 1 BSCG2CAOAD
cable modem / OMC-R 1 HOST400OAG
Table 1: Items for OMC-R-BSC G2 via PSDN
24 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
25/94
3 OMC-R / BSC G2 Interconnection
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.25switch is necessary. The maximum number of BSS, which can be connectedvia A-ter, is linked to the capacity of this X.25 switch.
The G2 TC output follows the X.25 protocol.
RS449
OMCR HSI Board
3BK 07744 JA
25 m
3BK 07641 GA
TRCUTC G2 X25 SWITCHV11
V11V11
Figure 9: OMC-R-BSC via G2 TC
The following items must be provided for connection via X.25 concentration unitwith 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 1 G2TCM0OOF
Cable X.25 switch / OMC-R 1 HOST400OAG (1)
X.25 SWITCH (2) 1
(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, keptfor history reasons.
The X.25 extraction strategy on A9125 TC is identical to the strategy used forG2 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
26/94
3 OMC-R / BSC G2 Interconnection
3.6 BSC G2 Connection via MSCThis 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 datatraffic supervision (CMISE and FTAM) over channelized G.703 by usingdedicated time slots.
The extraction of X.25 data from PCM links is done at the MSC site by arouter using its E1 and Serial boards.
The OMC-R is connected to the router via an Ethernet interface forconfiguration 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 IPpackets 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 maximumconnection of BSC G2 with redundancy links.
OMC-R Configuration Router Qty CISCO Router (defined as CISCO Type 1)
Small 1 Model 2811 (or 3725) with 1 x E1 port
Standard 1 Model 2811 (or 3725) with 1 x E1 port
Large 12 2 Model 2811 with 2 x E1 ports
Large 12 1 Model 3725 with 3 x E1 ports (*)
X-Large Master 1 Model 2811 (or 3725) with 2 x E1 ports
X-Large Agent 2 Model 2811 with 2 x E1 ports
X-Large Agent 1 Model 3725 with 3 x E1 ports (*).
(*) 3 x E1 ports are composed from one E1 board with 2 ports (NM-2CE1T1-PRImodule) and another one E1 board with 1 port (NM-1CE1T1-PRI module).
26 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
27/94
3 OMC-R / BSC G2 Interconnection
3.6.3 Small Number of BSC G2 at MSC Site
This configuration allows max. 1 OMC-R interconnected with max. 15 BSCsG2 with redundancy at BSC site and without compression on E1 link .
Each OMC-R in small configuration requires one PCM link from MSC tomanage all its BSCs G2.
BSCs
MSC
TCs
E1 board
S0 S1
DDF
DDF
LAN
CISCOrouter
PCM
FE0 FE1
OMCR
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 PCMcharacteristic.
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
28/94
3 OMC-R / BSC G2 Interconnection
3.6.3.2 Implementation Tools
Description Quantity TDS reference
CISCO ROUTER 2811 ROUTER1OOA01
- Rack 1
- WIC-2T module 1
- X.21 Smart Serial cables 2
- NM-1CE1T1-PRI module 1
- E1 ISDN PRI cable (RJ-48C) 1
RS449 X.21 DTE cable (for HSI ports) 2 3BK 08417 AAAA
PCM cables for BSCs 1
BSCG2CA[OA,OB][1,2,3,4,5,6,7,8]PCM cables for TCs 1 G2TCSM0OO[R,S,5,6,T,U,G,H]
External PCM cable MSC / CISCO 1 Customer dependent
Ethernet cables (RJ-45) 2 BSCLINKOOV16
28 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
29/94
3 OMC-R / BSC G2 Interconnection
3.6.4 Large Number of BSC G2 at MSC Site
There are 2 generic configurations to be described with t he number of BSCsbetween 15 and 31 handled by MSC (with redundancy set at MSC site) andwithout 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 emptyE1 network module is available on the router, insert the new board into thisnetwork module.
BSCs
MSC
TCs
E1
FE0 FE1
S0
DDF
DDF
LAN
CISCO router
PCM
OMCR1
S1
Figure 11: Large number of BSCs at MSC site - Solution 1
The new module is referenced by Cisco as NM-2CE1T1-PRI for Cisco2811 (or Cisco 3725).
The number of BSC G2 connected is limited to 31 BSCs with redundancyand without compression on E1 link .
One additional PCM link is needed between the MSC and CISCO router tocarry another max. 15 BSCs with redundancy at BSC site.
3BK 17422 5002 PGZZA Ed.06 29 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
30/94
3 OMC-R / BSC G2 Interconnection
3.6.4.2 Solution 1 Router Minimum Requirements
1-Port for FastEthernet interface.
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 TDS reference
CISCO ROUTER 2811 (*): ROUTER1OOB01
- Rack 1
- WIC-2T module 1
- X.21 Smart Serial cables 2
- NM-2CE1T1-PRI module 1
- E1 ISDN PRI cable (RJ-48C) 2
RS449 X.21 DTE cable (for HSI ports) 2 3BK 08417 AAAA
PCM cables for BSCs X (**) BSCG2CA[OA,OB][1,2,3,4,5,6,7,8]
PCM cables for TCs X (**) G2TCSM0OO[R,S,5,6,T,U,G,H]
External PCM cable MSC / CISCO 1 Customer dependent
Standard Ethernet cables (RJ-45) 2 3BK 07588 AA
(*) The Cisco 3725 router can be used as well.
(**) Depending of the number of BSCs supervised that consume the maximumcapacity of E1 link.
30 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
31/94
3 OMC-R / BSC G2 Interconnection
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 firstrouter will manage only the X.25 primary links.
PCM
X.25
PrimaryLinks
CISCORouter
CISCORouter
OMCR
HSI0 HSI1
S0 S1
X.25
RedundancyLinks
PCM
MSC
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 RequirementsThe 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 TDS reference
CISCO ROUTER 2811 (*) ROUTER1OOA01
- Rack 2
- WIC-2T module 2
- X.21 Smart Serial cables 2
- NM-1CE1B-PRI module 2
- E1 ISDN PRI cable (RJ-48C) 2
RS449 X.21 DTE cable (for HSIports)
2 3BK 08417 AAAA
External PCM cables MSC / CISCOs 2 Customer dependent
(*) The Cisco 3725 router can be used as well.
3BK 17422 5002 PGZZA Ed.06 31 / 94
http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?-http://-/?- -
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
32/94
3 OMC-R / BSC G2 Interconnection
3.6.5 Mixed Local and Remote MSC Configuration
The PCM link between the local MSC1 and the remote MSC2 is used for X.25data transmission. A second CISCO router is used at remote MSC site tocompress the X.25 data and to send over the PCM link between MSCs. Onetime slot is sufficient to carry X.25 data for 5-6 BSCs G2.
BSCs
MSC 1
TCs
E1 E1
FE0 FE1
S0 S1 S2 S3
DDF
DDF
PCM PCM
LAN 1
BSCs
MSC 2
TCs
E1 E1
Empty slot
FE0 FE1
DDF
DDF
LAN 2
PCM
HMI
ISCO1 CISCO2
PCM PCM PCMPCM
OMCR1 OMCR1
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 theBSCs G2 through the remote MSC2.
Afterwards, the compressed X.25 time slots are re-routed over the PCMlink between the MSCs.
The CISCO1 router decompresses the X.25 time slots from the secondrouter in order to collect the X.25 data of the remote BSCs.
In parallel, CISCO1s role is to connect the BSCs G2 coming through thelocal MSC1.
4 TS are dedicated on PCM link between MSC1 and MSC2 for the HMIuser sessions.
3.6.5.1 Router Minimum Requirements
1-Port for FastEthernet interface.
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
33/94
3 OMC-R / BSC G2 Interconnection
3.6.5.2 RecommendationsIf 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 TDS reference
CISCO ROUTER 2811 (CISCO 1): ROUTER1OOB01
- Rack 1
- WIC-2T module 2
- X.21 Smart Serial cables 4
- NM-2CE1T1-PRI module 1
- E1 ISDN PRI cable (RJ-48C) 2
CISCO ROUTER 2811 (CISCO 2): ROUTER1OOC01
- Rack 1
- NM-1CE1T1-PRI module 1
- E1 ISDN PRI cable (RJ-48C) 1
RS449 X.21 DTE cable (for HSI ports) 4 3BK 08417 AAAA
PCM cables for BSCs x (*) BSCG2CA[OA,OB][1,2,3,4,5,6,7,8]
PCM cables for TCs x (*) G2TCSM0OO[R,S,5,6,T,U,G,H]
External PCM cable MSC1 / MSC2 1 Customer dependent
External PCM cable MSC1 ( DDF) / CISCO1
2 Customer dependent
External PCM cable MSC2 ( DDF ) / CISCO22
Customer dependent
Ethernet cables (RJ-45 connectors) 5 BSCLINKOOV16
(*) Depending of the number of BSCs supervised that consume the maximumcapacity of E1 link.
3BK 17422 5002 PGZZA Ed.06 33 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
34/94
3 OMC-R / BSC G2 Interconnection
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 ( quiteexpensive ).
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
35/94
4 OMC-R / A9130 BSC Evolution Interconnection
4 OMC-R / A9130 BSC Evolution Interconnection
It describes the IP direct and Ater connections between the OMC-R andA9130 BSC Evolution.
3BK 17422 5002 PGZZA Ed.06 35 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
36/94
4 OMC-R / A9130 BSC Evolution Interconnection
4.1 IntroductionThe O&M supervision traffic has changed the routing protocol from X.25(BSC G2) into IP (BSC Evolution) to increase the file transfer rate, foreasier implementation and also for low cost. The FTP over TCP/IP networkinfrastructure is used for the file transfer between A9130 BSC Evolution andOMC-R.In A9130 BSC Evolution, the two OMCP boards are responsible for supervisionpart 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 connectto 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 NetworkBSC Evolution uses the external IP address to connect with OMC-R. The O&Mtraffic for BSC Evolution is done via its Ethernet port (ETH-3) of the BSCEvolution 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
Standard Ethernet cables (RJ-45) 2 BSCLINKOOV16
Cisco 2811 router:
- rack
- HWIC-4ESW module
1
1
ROUTER1OOD01
36 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
37/94
4 OMC-R / A9130 BSC Evolution Interconnection
4.3 Over Ater InterfaceThe O&M traffic coming from A9130 BSC Evolution has at least 2 Atermuxlinks. 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 inthe Cisco router by its E1 controller.
All these virtual serial interfaces are integrated, by the Cisco router, in theMultiLink PPP interface bundle.
The number of the virtual serial interfaces included in the ML-PPP bundle isin the range of 4-16 lines.
Note: The supervision is not lost, if you have only 1 Atermux link available, due tothe 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 itsrecommended O&M bandwidth of 256 Kbps.
4.3.1 Router Minimum Requirements
1-Port for FastEthernet interface.
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: If the customer follows these minimum requirements then he doesnt needto use the Alcatel solution, because the supplying and configuration of therouter(s) is under its own responsibility.
3BK 17422 5002 PGZZA Ed.06 37 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
38/94
4 OMC-R / A9130 BSC Evolution Interconnection
4.3.2 Implementation Tools
Description Quantity TDS reference
CISCO ROUTER 2811: ROUTER1OOC01
- Rack 1
- NM-2CE1T1-PRI module 1
- E1 ISDN PRI cable (RJ-48C) 2
PCM cable MSC / CISCO 2 Customer dependent
Standard Ethernet cable 1 BSCLINKOOV16
4.4 A9130 BSC Evolution IP Address RestrictionsThe IP address assigment for A9130 BSC Evolution has the followingrestrictions:
In the case of an O&M link on ML-PPP (O&M link over Ater), A9130 BSCEvolution external addresses must not belong to the network: 1.1.1.0/29 .
OMC-Rs or other machines/equipments, with which the A9130 BSCEvolution 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 itgenerates immediately an IP address conflict.
Knowing that 172.n.0.0 , where n=16,17,18 are internal subnetworks for theA9130 BSC Evolution, externally to this equipment, these sub-networksmust not be present on the other part of the router.
38 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
39/94
5 OMC-R / CBC Server Interconnection
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
40/94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
41/94
5 OMC-R / CBC Server Interconnection
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 serialcable (CAB-SS-X21FC) are needed as indicated in the table below.
Description Quantity TDS reference
WIC-2T module 1 BSCLINKOOJ16
X.21 Smart Serial cable(CAB-SS-X21FC)
1 BSCLINKOOJ16
5.2.2 Case 2: New Router
If the customer has no free serial port and no free WIC slot on existing Ciscorouter then another full Cisco router 2811 (type 1) has to be ordered withWIC-2T boards and associated cables as indicated in the table below.
Description Quantity TDS reference
CISCO ROUTER 2811:
- Rack 1
- WIC-2T module 1
- X.21 Smart Serial cable 1
3BK 17422 5002 PGZZA Ed.06 41 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
42/94
5 OMC-R / CBC Server Interconnection
42 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
43/94
6 A9130 BSC Evolution / CBC Server Interconnection
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
44/94
6 A9130 BSC Evolution / CBC Server Interconnection
6.1 Direct IP Link ConnectionThe connectivity between the A9130 BSC Evolution and CBC is realized usinga Cisco router, which it is capable to use IP and X.25 protocols. The A9130BSC 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. TheCisco router is responsible to encapsulate the data from IP packets into theX.25 packets towards CBC.
For the direct IP link connection, X.25 packets from CBC Server are sent overIP network to the BSC Evolution via the Ethernet ports of SSW RTM board.
IPNetwork
IP IP CISCOrouter CBC
BSCEvolution
X.25
Figure 18: BSC Evolution and CBC Server with Direct IP Connection
6.1.1 Router Minimum Requirements1-Port for FastEthernet interface.
1-Port for Serial WAN Interface Cards.
The router must supports: X.25, IP, X.25 over IP.
6.1.2 Implementation Tools
Description Quantity TDS reference
CISCO 2811 Router ROUTER1OOE01
- Rack 1
- WIC-2T module 1
- X.21 Smart Serial cable 1
Standard Ethernet cables (RJ-45) 2 BSCLINKOOV16
44 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
45/94
6 A9130 BSC Evolution / CBC Server Interconnection
6.2 Ater Interface ConnectionFor the route over Ater interface, Ater can be extracted only from TP boardinside 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 packetson one or more time slots of Ater interface using E1 link.
External routers are responsible for converting ML-PPP to LAPB, thentransferring to CBC server.
Ater PCM CISCOrouter CBC
BSCEvolution
X.25TCMSC
Figure 19: BSC Evolution and CBC over Ater interface
6.2.1 Router Minimum Requirements
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).
6.2.2 Implementation Tools
Description Quantity TDS reference
CISCO ROUTER 2811: ROUTER1OOA01
- Rack 1
- WIC-2T module 1
- X.21 Smart Serial cable (CAB-SS-X21FC) 1
- NM-1CE1T1-PRI module 1
- E1 ISDN PRI cable 1
3BK 17422 5002 PGZZA Ed.06 45 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
46/94
6 A9130 BSC Evolution / CBC Server Interconnection
46 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
47/94
7 OMC-R / MFS Legacy Interconnection
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
48/94
7 OMC-R / MFS Legacy Interconnection
7.1 PresentationThere 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 PSDNnetwork, dedicated leased lines or through a remote MSC.
7.2 MFS Legacy and OMC-R in LANThe IP switch can emulate the local LAN. This solution is proposed as theeasiest Ethernet infrastructure.
MFS OMCR
IPSwitch
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 1 Customer dependant
Standard Ethernet cables 3 BSCLINKOOV16
7.3 MFS Legacy and OMC-R in WANThe remote MFS Legacy and OMC-R in the WAN network is defined using anintermediate PSDN network.
IPSwitch
PSDNCISCOIP router
MFS HMI
OMCR
CISCOIP 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:
2-Port for FastEthernet interface.
The router must supports: IP.
48 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
49/94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
50/94
8 OMC-R / MFS Evolution Interconnection
8.1 Presentation
The content of this interconnection is still under study !
The OMC-R and A9130 MFS Evolution interconnection requires a routerknowing the RIP V2 protocol with at least 3 Ethernet ports available and itsspecific 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 knownby the OMC-R.
The 2 networks (B and C) are internally to the MFS Evolution, not known bythe OMC-R.
The O.w is the default gateway of the OMC-R to be connected to A9130MFS Evolution.
The O subnetwork is mandatory to be different than A subnetwork.
8.1.1 Router Minimum Requirements
3-Ports for FastEthernet interface.
The router must supports: IP, RIP V2 (its timers changeable), NAT.
Note: If the customer follows these minimum requirements then he doesnt needto use the Alcatel solution, because the supplying and configuration of therouter(s) is under its own responsibility.
50 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
51/94
8 OMC-R / MFS Evolution Interconnection
8.1.2 Implementation Tools
Description Quantity TDS Reference
CISCO 2811 Router:
Rack
HWIC-4ESW Module
1
1
ROUTER1OOD01
Standard Ethernet cables 3 BSCLINKOOV16
8.2 MFS Evolution IP Address RestrictionsThe IP address assigment for MFS Evolution has the following restrictions:
MFS Evolution external addresses must not belong to the followingnetworks: 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, 19and 32 .
Figure 22: MFS Evolution IP Address Restrictions
These 172.n.0.0 (where n=16,17,18, 19 and 32) subnetworks are allowedfor MFS Legacy, but not for MFS Evolution.
3BK 17422 5002 PGZZA Ed.06 51 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
52/94
8 OMC-R / MFS Evolution Interconnection
52 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
53/94
9 MFS / A-GPS Server Interconnection
9 MFS / A-GPS Server Interconnection
It describes the MFS and A-GPS Server connection using the TCP/IP overEthernet solution.
3BK 17422 5002 PGZZA Ed.06 53 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
54/94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
55/94
9 MFS / A-GPS Server Interconnection
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 theexternal router for the communication with OMC-R is re-used to supportcommunication with A-GPS server(s), the router can be reconfiguredwithout any O&M outage .
9.2 MFS and A-GPS Server CollocatedNormally these machines are on different sub-networks, and therefore a routerhas to be used. The two Ethernet interfaces of the router towards MFS must beconfigured with the following default gateway IP addresses : 1.1.1.10 andrespectively 2.2.2.10. These values are coded in MFS and can be changedusing BUL files. In the figure below, the two switches are considered to beinternal part of MFS block.
LAN 1AGPS
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 collocatedwith the MFS. In this case, the split is done for LCS related traffic and O&Mtraffic.
Description Quantity TDS Reference
MFS 1 Customer dependant
A-GPS Server 1 Customer dependant
Cisco 2811 Router:- Rack
- HWIC-4ESW Module
1 ROUTER1OOD01
Standard Ethernet cables(RJ-45)
3 BSCLINKOOV16
3BK 17422 5002 PGZZA Ed.06 55 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
56/94
9 MFS / A-GPS Server Interconnection
9.3 Co-localized MFS / BSC Evolution and A-GPS ServerThe IP access between A-GPS server and co-localized MFS / BSC Evolutionis ensured through ML-PPP links over A-ter provided between the TP boardand the MSC, up to the IP router of the customer.
There is no IP access on the BSC Evolution site. The following figure showsthis configuration.
GPBoard
Switch 1
Switch 2
IPNetwork
MFS/BSC
MSCTP board
IP routing
IP NATRouter
AGPS
Server
Figure 25: A-GPS Server with co-localized with MFS
9.3.1 Router Minimum Requirements
1-Port for FastEthernet interface.
1-Port for E1 ISDN PRI module.
The router must supports: IP, NAT
9.3.2 Implementation Tools
Description Quantity TDS Reference
MFS/BSC + OCM cables 1 Customer dependant
A-GPS Server 1 Customer dependant
Cisco 2811 router:
- Rack
- HWIC-4ESW Module
1
1
ROUTER1OOD01
Ethernet cables with RJ-45 connectors 2 BSCLINKOOV16
56 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
57/94
10 OMC-R / HMI Server and NMC Interconnection
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
58/94
10 OMC-R / HMI Server and NMC Interconnection
10.1 PresentationThe following figure shows an example for an OMC-R having a remote HMIserver and NMC through WAN network (PSDN).
PSDN
Master
Agent
HMI2
CISCO
2621
CISCO
2811NMC
CISCO
2621HMI 1
Figure 26: OMC-R and Remote HMI / NMC
The OMC-R and NMC can be collocated or not, however in both cases seen isthe Ethernet interface.
10.1.1 Router Minimum Requirements
1-Port for FastEthernet interface.
1-Port for Serial WAN Interface Cards.
The router must supports: X.25, IP, IP over X.25.
10.1.2 Implementation Tools
Description Quantity TDS ReferenceCISCO 2811 Router ROUTER1OOE01
- Rack 2
- WIC-2T module 2
- X.21 Smart Serial cables(CAB-SS-X21FC)
2
Standard Ethernet cables (RJ-45) 2 BSCLINKOOV16
58 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
59/94
10 OMC-R / HMI Server and NMC Interconnection
10.2 PSDN SubscriptionOne PSDN connection is used for the remote HMI server. The subscriptionneeded 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) 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. Formore details, see [ 12 ].
10.3 X.25 RecommendationsThe following bandwidths for X.25 links are recommended in the case ofdifferent OMC-R configurations:
OMC-R Configurations Maximum Real G2 BSC Recommended X.25 Bandwidth per Link
SMALL 10 64 Kbit/sSTANDARD 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
60/94
10 OMC-R / HMI Server and NMC Interconnection
60 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
61/94
11 OMC-R / NPA Interconnection
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
62/94
11 OMC-R / NPA Interconnection
11.1 PresentationUsually the OMC-R and NPA are collocated in the same LAN. The remote NPAClient(s) can be connected to NPA Server through a WAN network (PSDN) aswell as the local NPA Client(s) in LAN.
The following figure shows the interconnection between the OMC-R / NPAServer with local and remote NPA Client(s). The possible HMI on the remoteside (LAN2) is optional.
OMCR
NPAserver
NPAclient
PSDN CISCO
2621/ 2811
CISCO
2621/ 2811
HMI
NPAclient
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
1-Port for FastEthernet interface.
1-Port for Serial WAN Interface Cards.
The router must supports: X.25, IP, IP over X.25.
11.3 Implementation Tools
Description Quantity TDS Reference
CISCO 2811 Router ROUTER1OOB01
- Rack 2
- WIC-2T module 2
- X.21 Smart Serial cables(CAB-SS-X21FC)
2
62 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
63/94
12 X.25 Default Parameters
12 X.25 Default Parameters
This section describes the default X.25 parameters used to configure differentlinks.
To discourage any patching of DLS relations, no description of the DLS willbe given in this document.
3BK 17422 5002 PGZZA Ed.06 63 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
64/94
12 X.25 Default Parameters
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 5 5
Frame timer T1 (x100 ms) 2 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
65/94
12 X.25 Default Parameters
X.25 connection via Ater interface (BSC G2)
Extraction at TC siteExtractionat MSC site
Extraction viaCISCO
BSS - OMC primaryX.25 address mandatory mandatory mandatory
BSS - OMC secondaryX.25 address
mandatory (1) mandatory(1)
mandatory (1)
OMC primary X.25address
mandatory mandatory mandatory
OMC secondary X.25address
optional ( 2 ) optional ( 2 ) optional ( 2 )
BSS - CBC primaryX.25 address
(4) (4) (4)
BSS - CBC secondaryX.25 address
(4) (4) (4)
X.25 extraction TRCU MSC MSC
Maximum number ofretransmission
5 5 5
Frame timer (timer T1)(100 ms)
3 3 3
Frame window size 07 07 07
Number of virtualcircuits
04 (5),(10) 04 (5),(10) 08 (5)
Max. SimultaneousVirtual Circuits
04 (5) 04 (5) 08 (5)
Throughput class fortransmission (bps)
48000 48000 64000
Throughput class for
reception (bps)
48000 48000 64000
Throughput classnegotiation
No No No
Packet size fortransmission (bytes)
256 (6),(14) 256 (6),(14) 256 (6),(14)
Packet size forreception (bytes)
256 (6),(14) 256 (6),(14) 256 (6),(14)
Window size fortransmission
03 03 2
3BK 17422 5002 PGZZA Ed.06 65 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
66/94
12 X.25 Default Parameters
X.25 connection via Ater interface (BSC G2)
Extraction at TC siteExtractionat MSC site
Extraction viaCISCO
Window size forreception 03 03 2
Max number of bytesin the I-frame
259 (7),(14) 259 (7),(14) 259 (7),(14)
Local window betweenRFH 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 redundancyat the BSC side.
2. X.25 address of the 2nd link connected to the OMC-R in the case ofredundancy or load sharing.
3. Not relevant, a CBC cannot be connected directly to the BSC (no collocatedBSC/CBC).
4. Mandatory only if a CBC is connected to the BSC.
5. Number of virtual circuits must be equal to maximum simultaneous virtualcircuits.
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.25address is declared at the X.25 switch port.
9. This field is optional (X.25 address of the 2nd link connected to the BSC inthe case of redundancy at BSC side) but must be left empty in the casewhere 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 connectingvia Transpac. Transpac itself will add the caller address (BSC address) inthe 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
67/94
12 X.25 Default Parameters
12.2 OMC-R ConfigurationAll required modifications must be done on the OMC-R using the X.25 tool withroot permission, on different switches or routers when they are used.
12.2.1 X.25 Configuration Dependant Parameters
X.25 Connection via a Switch Connection through PSDN
BSC G2 BSC G2
Link Editor Window
Link number 0 or 1 (1) 0 or 1 (1)
Link Description What ever you like (2) 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 7 7
Interface DTE (3) DTE (3)
Lap Mode LAPB (3) LAPB (3)
Local X121 Address (5) (11)
Version 1984 (3) 1984 (3)
Link Editor / Packet size (bytes)
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) 4 4
Table 5: X.25 parameters via Switch/PSDN for OMC-R
3BK 17422 5002 PGZZA Ed.06 67 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
68/94
12 X.25 Default Parameters
X.25 Connection via a SwitchBSC G2
Connection through PSDNBSC G2
Link Editor / Logical Channel range
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)
Advance Configuration / Link modes
Source Address Control (7) Force use of local address (12) Omit source address (12)
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 8 (3) 8 (3)
68 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
69/94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
70/94
12 X.25 Default Parameters
X.25 Connection via Ater Interface (BSC G2)
Extraction at TC siteExtraction at MSCsite Extraction via CISCO
Link Editor WindowLink number 0 or 1 (1) 0 or 1 (1) 0 or 1 (1)
Link Description What ever you like (2) What ever you like (2) What ever you like (2)
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 7 7 7
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 / 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
71/94
12 X.25 Default Parameters
X.25 connection via Ater interface (BSC G2)
Extraction at TC siteExtraction at MSCsite Extraction via CISCO
Link Editor / Logical Channel RangePVC Minimum 0 (6) 0 (6) 0 (6)
PVC Maximum 0 (6) 0 (6) 0 (6)
SVC incomingMinimum
0 (6) 0 (6) 0 (6)
SVC IncomingMaximum
0 (6) 0 (6) 0 (6)
SVC Two wayMinimum
1 (3) 1 (3) 1 (3)
SVC Two WayMaximum
Varying (8) Varying (8) 1024 (must the same in router)
SVC OutgoingMinimum
0 (6) 0 (6) 0 (6)
SVC OutgoingMaximum
0 (6) 0 (6) 0 (6)
Advance Configuration / Link Modes
Source AddressControl
Force use of localaddress (12)
Force use of localaddress (12)
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 towardsDefaults
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
72/94
12 X.25 Default Parameters
X.25 connection via Ater interface (BSC G2)
Extraction at TC siteExtraction at MSCsite Extraction via CISCO
Modulo 8 (3) 8 (3) 8 (3)Advance Configuration / Throughput Window / Window Sizes ( packets)
Local Default 2 2 7
Local Maximum 2 2 7
Remote Default 2 2 7
Remote Maximum 2 2 7
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 theclock received from the OMC-R.
5. The X.25 local address supplied by the X.25 supplier must be the OMCprimary 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 (3virtual circuits per BSC).
9. The link clock is provided to the OMC-R externally by the X.25 switch. TheX.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 responsibilityof 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 theOMC-R address in the X.25 packets. If so, use the option Omit sourceaddress 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 ofthe intermediate network or switch used between the MSC and the OMC-R.
72 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
73/94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
74/94
12 X.25 Default Parameters
12.2.2.1 Advanced Configuration / LAPB, WANLAPB Parameters
Ack Timer [T1] 20
P-bit Timer 8
Reject Timer 24
Busy-state Timer 100
Link Idle Timer 250
Max. RR delay 4
Max. Tries [N2] 10
Max. UnACKed IPDUs 7
Transmit Probe 0
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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
75/94
12 X.25 Default Parameters
12.2.2.2 Advanced Configuration / Addressing
Extended Address None
12.2.2.3 Advanced Configuration / CUG and FacilitiesClosed 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
76/94
12 X.25 Default Parameters
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 ClassSee section related to the type of link because these parameters are closelylinked to the link type (either 9.6 kbps or 64 Kbps) or link configuration.
76 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
77/94
12 X.25 Default Parameters
12.2.2.6 Advanced Configuration / Timers and CountersX.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 5
DTE / DCE Resolution 2000
Idle Disconnect (LAN or Dialup) 0
X.25 Retransmission Counters
DTE Restart Request [R20] 6
DTE Clear Request [R23] 6
DTE Reset Request [R22] 6
DTE Registration Request [R28] 1
X.25 Transmit Delays
Internal Delay 5
Line Delay 5
3BK 17422 5002 PGZZA Ed.06 77 / 94
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
78/94
12 X.25 Default Parameters
12.2.2.7 Advanced Configuration / SpecialD-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 No
78 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
79/94
12 X.25 Default Parameters
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 ConfigurationThis value specifies the maximum simultaneous inbound or outboundconnections.
Stack Manager/Devices/X.25 device
Connection pool 200
12.2.3.2 Resource ConfigurationThese values are used to adjust the internal resource of the stack with thecontext 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
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
80/94
12 X.25 Default Parameters
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 1
QOS threshold / mpx 8
Max size / nofc 100
12.2.3.4 CONS
Stack Manager / Resources / CONS
Connection Timer (*10s) 17
12.2.3.5 Route ManagerThe "Prefix Route" values adjusts the NSAP prefix by adding or deletinginformation. The X.25 menu sets the type of X.25 service required for theCONS configuration.
Route Manager / Category / Prefix Route / X.25 Service
Link Type 1980
Addressing CONS-80
80 / 94 3BK 17422 5002 PGZZA Ed.06
-
8/9/2019 B9 BSS O&M Routing Configurations ed06.pdf
81/94
12 X.25 Default Parameters
12.3 CISCO Routers ConfigurationThe router configuration is done by typing in command mode line either locallyfrom the console (VT terminal) or remotely via a telnet session. Alternatively,the commands can be prepared in a text file and then transferred to therouter via FTP.
12.3.1 X.25 and LAPB Parameters
The following values are default values except when shown in bold.
ParameterSerial Board for OMC (Value toOMC)
E1 Board for BSC via MSC(Value to BSC)
Encapsulation lapb no No
Encapsulation X.25 dce dce
Lapb interf ace-outage (ms) 0 0
Lapb k (frames) 7 7
Lapb modulo 8 8
Lapb n1 (bit) 12056 12056