Low Level Design For IP Backhaul 0205-Final

Low Level Design for IP Backhaul
HUAWEI TECHNOLOGIES CO., LTD.
ethio telecom TEP Confidential [键入文字]

Contents
Contents .................................................................................................................................... 1
Figures ...................................................................................................................................... 9
Tables........................................................................................................................................ 1
1 Project Overview.................................................................................................................... 3
2 Network Requirement ............................................................................................................ 5
2.1 Performance Requirement .................................................................................................... 5
2.2 QoS Requirement ................................................................................................................. 6
2.3 High Availability Requirement .............................................................................................. 8
2.4 Scalability Requirement ........................................................................................................ 9
2.5 Security Requirement ........................................................................................................... 9
3 Solution Overview ................................................................................................................ 10
3.1 Solution Overview .............................................................................................................. 10
3.1.1 Wireless Service Solution Overview ............................................................................... 10
3.1.2 Core Network Solution Overview ................................................................................... 12
3.2 Addressing the Requirement ............................................................................................... 13
3.2.1 Private Network IP Requirment ..................................................................................... 13
4 Network Architecture Design ............................................................................................... 15
4.1 Network Architecture Overview ......................................................................................... 15
4.2 Physical Topology Overview ............................................................................................... 16
4.3 IPRAN Network Design ....................................................................................................... 16
4.4 Interconnection design ....................................................................................................... 21
4.4.1 Core Site Topology.......................................................................................................... 22
5 Product and Naming ............................................................................................................ 25
5.1 Product Detail(Hardware) ................................................................................................... 25
5.1.1 CX600 Product ............................................................................................................... 25
5.1.2 NE40E Product .............................................................................................................. 26
5.1.3 ATN950B Product .......................................................................................................... 27
5.1.4 S9300 Product ................................................................................................................ 27
5.1.5 Summary Hardware description for products ................................................................... 28
5.2 Product Detail(Software) .................................................................................................... 29
5.3 Product Hardware Configuration ........................................................................................ 30
5.3.1 CX600 Product ............................................................................................................... 30
ethio telecom TEP Confidential

5.3.2 NE40E Product .............................................................................................................. 31

5.3.3 ATN950B Product .......................................................................................................... 32
5.3.4 S9300 Product ................................................................................................................ 32
5.4 Equipment Naming ............................................................................................................. 33
5.4.1 Equipment Naming Conventions .................................................................................... 33
5.5 Interface Description .......................................................................................................... 41
5.5.1 Interface Naming Conventions ....................................................................................... 41
5.5.2 Interface Description Conventions ................................................................................. 42
5.6 Equipment Port Connection List .......................................................................................... 66
5.7 Cable label naming ............................................................................................................. 72
6 Logical Planning and Design .............................................................................................. 106
6.1 IP Address Planning .......................................................................................................... 106
6.1.1 Designing Loopback Interface Addresses ..................................................................... 106
6.1.2 Designing Interconnected interfaces ............................................................................. 110
6.2 VLAN Planning .................................................................................................................. 122
6.2.1 Design Guidelines ......................................................................................................... 122
7 Routing protocol Design ..................................................................................................... 124
7.1 IS-IS Design ....................................................................................................................... 124
7.1.1 Overview ...................................................................................................................... 124
7.1.2 Designing Basic Functions ............................................................................................ 125
7.1.3 Designing IS-IS Cost..................................................................................................... 127
7.1.4 Configure Example for ISIS ......................................................................................... 128
7.2 BGP Design ....................................................................................................................... 138
7.2.1 Overview ...................................................................................................................... 138
7.2.3 Designing Routing Priorities ........................................................................................ 139
7.2.4 Designing Route Advertisement ................................................................................... 140
7.2.5 Designing Route Reflectors........................................................................................... 141
7.2.6 Detail Parameter Designs ............................................................................................. 143
7.2.7 Configure Example for BGP ........................................................................................ 146
8 MPLS Protocol design ........................................................................................................ 158
8.1 MPLS LDP design .............................................................................................................. 158
8.1.1 Overview ...................................................................................................................... 158
8.1.3 Designing Paths ............................................................................................................ 158
8.1.5 Configure Example for MPLS LDP ............................................................................. 159
8.2 MPLS TE design ................................................................................................................. 168

8.2.1 Overview ...................................................................................................................... 169

8.2.3 Designing Paths ............................................................................................................ 172
8.2.4 Designing BFD for TE-LSP/TE-Tunnel ....................................................................... 175
8.2.6 Configure Example for MPLS TE ................................................................................ 177
9 Mobile Services Implement ................................................................................................ 184
9.1 2G/3G/LTE S1 Mobile Service............................................................................................ 184
9.1.1 Overview ...................................................................................................................... 184
9.1.2 Basic Design ................................................................................................................. 185
9.1.3 Reliability Design ......................................................................................................... 190
9.1.4 Scalability Design ......................................................................................................... 195
9.1.5 QoS Design ................................................................................................................... 200
9.1.6 Configure Example for 2G/3G/LTE S1 Service ............................................................ 201
9.2 LTE X2 Mobile Service ....................................................................................................... 210
9.2.1 Overview ...................................................................................................................... 210
9.2.2 Basic Design ................................................................................................................. 211
9.2.4 QoS Design ................................................................................................................... 214
9.2.5 Configure Example for LTE X2 Service ....................................................................... 214
9.3 2G TDM Service Design ..................................................................................................... 216
9.3.1 Overview ...................................................................................................................... 216
9.3.2 Basic Design ................................................................................................................. 216
9.3.4 QoS Design ................................................................................................................... 220
9.3.5 Configure Example for 2G TDM Service ..................................................................... 221
9.4 CS Service Design .............................................................................................................. 225
9.4.1 CS Service Scenario overview ...................................................................................... 225
9.4.2 Physical Connection ..................................................................................................... 225
9.4.3 CS IP Address Planning ............................................................................................... 243
9.4.4 CS Vlan Planning ......................................................................................................... 244
9.4.5 Configure Example for CS service ............................................................................. 252
9.5 PS Service Design .............................................................................................................. 255
9.5.1 PS Service Scenario ...................................................................................................... 255
9.5.2 Physical Connection ..................................................................................................... 256
9.5.3 PS IP Address Planning................................................................................................ 265
9.5.4 PS Vlan Planning.......................................................................................................... 266
9.5.5 Configure Example for PS service ............................................................................ 269

10 Fixed-Line Services Implement ........................................................................................ 273

10.1 HSI Services Design ....................................................................................................... 273
10.1.1 HSI Services Overview ............................................................................................... 273
10.1.2 Bearer Requirements.................................................................................................. 274
10.1.3 Service Deploy ............................................................................................................ 275
10.1.4 HA .............................................................................................................................. 278
10.2 VOIP Services Design .................................................................................................... 279
10.2.1 VOIP Services Overview............................................................................................. 279
10.2.2 Bearer Requirements .................................................................................................. 281
10.2.3 Service Deploy ............................................................................................................ 281
10.2.4 HA .............................................................................................................................. 283
11 Interconnection Implement .............................................................................................. 284
11.1 Overview ........................................................................................................................ 284
11.2 Interconnection Topology Design .................................................................................... 286
11.2.1 Overview .................................................................................................................... 286
11.2.2 Physical Network Scope.............................................................................................. 286
11.2.3 Logical Network Scope ............................................................................................... 287
11.3 Naming & Addressing ..................................................................................................... 287
11.3.1 Network Device Naming ............................................................................................. 287
11.3.2 IP Address Planning for Interconnection ................................................................... 289
11.4 Site Network Design ....................................................................................................... 291
11.4.1 Overview .................................................................................................................... 291
11.4.2 Nifas Silk Site ............................................................................................................. 291
11.4.3 Kirkos Site .................................................................................................................. 293
11.4.4 Bole Site ...................................................................................................................... 295
11.4.5 Microwave Site ........................................................................................................... 296
11.4.6 Arada Site................................................................................................................... 299
11.4.7 Configuration Template for Eth-Trunk ..................................................................... 300
11.5 IGP Design ...................................................................................................................... 300
11.5.1 Overview .................................................................................................................... 300
11.5.2 IGP Deployment Scope ............................................................................................... 301
11.5.3 ISIS Design Rule......................................................................................................... 301
11.5.4 ISIS Metric Planning .................................................................................................. 302
11.5.5 LDP-IGP Synchronization.......................................................................................... 303
11.5.6 ISIS Authentication and Silent Interface .................................................................... 303
11.5.7 Configuration Template for ISIS ................................................................................ 304
11.6 BGP Design ..................................................................................................................... 304
11.6.1 Overview .................................................................................................................... 304

11.6.2 BGP Deployment Scope .............................................................................................. 304

11.6.3 BGP Design Rule ........................................................................................................ 305
11.6.4 BGP Route Advertisement & Control Design............................................................. 306
11.6.5 Configure Example for BGP ...................................................................................... 310
11.7 MPLS Design ................................................................................................................... 311
11.7.1 Overview .................................................................................................................... 311
11.7.2 MPLS and MPLS VPN Design Rule ........................................................................... 312
11.7.3 MPLS LSR ID ............................................................................................................ 312
11.7.4 MPLS LSP Trigger / Label allocation ........................................................................ 313
11.7.5 MPLS LDP GR........................................................................................................... 313
11.8 Service Bearer and VRF Design ........................................................................................ 314
11.8.1 Overview .................................................................................................................... 314
11.8.2 CS Service Bearer ....................................................................................................... 314
11.8.3 PS Service Bearer ....................................................................................................... 315
11.8.1 Service VPN Design .................................................................................................... 316
12 Synchronization Design .................................................................................................... 319
12.1 IP Clock Solution and Capacity ........................................................................................ 319
12.2 Synchronous Ethernet Clock............................................................................................ 321
12.2.1 Design Guidelines ....................................................................................................... 321
12.2.2 Design Result .............................................................................................................. 323
12.2.3 Configure Example for Synchronous Ethernet clock ................................................... 323
13 QoS Design ....................................................................................................................... 326
13.1 Traffic Classification and Marking ................................................................................... 326
13.2 Congestion Management and Avoidance ........................................................................ 328
13.2.1 Congestion Management ............................................................................................ 328
13.2.2 Congestion Avoidance ................................................................................................ 329
13.3 Configure Example for Qos deployment .......................................................................... 331
14 Network Mangement System ........................................................................................... 334
14.1 End to End NMS Design ................................................................................................... 334
14.1.1 ATN&CX &NE40E&93Switch................................................................................... 334
14.1.2 RTN ............................................................................................................................ 338
14.1.3 BASE STATION OAM .............................................................................................. 339
14.2 U2000 Planning .............................................................................................................. 342
14.3 U2000 NBI Overview ....................................................................................................... 345
15 Security Design................................................................................................................. 347
15.1 Security Overview........................................................................................................... 347
15.2 Security in Equipment ..................................................................................................... 347
15.2.1 SSH: STELNET and SFTP ........................................................................................ 347

15.2.2 Local User List ........................................................................................................... 348

15.2.3 ACL for Remote Access .............................................................................................. 349
15.3 Security in Network ........................................................................................................ 349
15.3.1 ISIS MD5 Authentication ........................................................................................... 349
15.3.2 BGP MD5 Authentication .......................................................................................... 350
15.3.3 MPLS LDP MD5 ........................................................................................................ 350
16 Future IPV6 ..................................................................................................................... 351
16.1 IPV6 Overview ................................................................................................................ 351
16.1.1 Definition .................................................................................................................... 351
16.1.2 Purpose ....................................................................................................................... 351
16.2 Supported IPv6 related RFCs and usage in each proposed device ..................................... 352
16.3 IPV6 Evolution ................................................................................................................ 354
16.4 Supported Migration techniques ..................................................................................... 354
16.4.1 ISIS for IPv6............................................................................................................... 354
16.4.2 BGP for IPv6 .............................................................................................................. 354
16.4.3 IPv6 over IPv4 ............................................................................................................ 355
16.4.4 IPv4 over IPv6 ............................................................................................................ 356
16.4.5 DS-Lite ....................................................................................................................... 356
16.5 IPv6 Deployment Strategy .............................................................................................. 357
16.5.1 ISIS for IPv6 ............................................................................................................... 357
16.5.2 BGP for IPv6 .............................................................................................................. 359
16.5.3 IPv6 over IPv4 ............................................................................................................ 362
16.5.4 IPv4 over IPv6 ............................................................................................................ 364
16.5.5 DS-Lite ....................................................................................................................... 369
16.6 Upcoming IPv6 related features and how to update each proposed devices .................... 374
16.6.1 NE40E/CX600 ............................................................................................................ 374
16.6.2 ATN ............................................................................................................................ 374
17 Future Multicast............................................................................................................... 375
17.1 Multicast Service Overview ............................................................................................. 375
17.2 Supported Multicast related RFCs and usage in each proposed device ............................. 375
17.3 Multicast Routing Protocols ............................................................................................ 375
17.4 Multicast Deployment .................................................................................................... 377
17.5 Multicast Deployment Example ...................................................................................... 383
17.5.1 Deployment Topology ................................................................................................. 383
17.5.2 IP Plan for Multicast Deployment Example ............................................................... 383
17.5.3 Configuration Template for Multicast ........................................................................ 383
18 Physical Layout ................................................................................................................ 390
18.1 Core Site NE40E Layout ................................................................................................... 390

18.1.1 NE40E-X8 in Arada.................................................................................................... 390

18.1.2 NE40E-X8 in Bole ....................................................................................................... 390
18.1.3 NE40E-X8 in Kirkos ................................................................................................... 390
18.1.4 NE40E-X8 in Microwave ............................................................................................ 391
18.1.5 NE40E-X8 in NifasSilk ............................................................................................... 391
18.2 RSG Site CX600 Layout .................................................................................................... 392
18.2.1 CX600-X16 in Arada .................................................................................................. 392
18.2.2 CX600-X16 in Bole ..................................................................................................... 393
18.2.3 CX600-X16 in Kirkos ................................................................................................. 396
18.2.4 CX600-X16 in Microwave .......................................................................................... 398
18.2.5 CX600-X16in NifasSilk ............................................................................................... 401
18.3 ASG Site CX600 Layout .................................................................................................... 403
18.3.1 CX600-X8 in Addis Ketema ....................................................................................... 403
18.3.2 CX600-X8 in Addis SidisKilo ..................................................................................... 404
18.3.3 CX600-X8 in Yeka ...................................................................................................... 405
18.3.4 CX600-X8 in Filowaha ............................................................................................... 406
18.3.5 CX600-X8 in OldAirport ............................................................................................ 407
18.3.6 CX600-X8 in Karanyo ................................................................................................ 407
18.3.7 CX600-X8 in Mekanisa............................................................................................... 408
18.3.8 CX600-X8 in Bole Micheal ......................................................................................... 409
18.3.9 CX600-X8 in Akaki .................................................................................................... 410
18.3.10 CX600-X8 in Kality .................................................................................................. 411
18.3.11 CX600-X8 in Lebu .................................................................................................... 412
18.3.12 CX600-X8 in HannaMariam .................................................................................... 413
18.3.13 CX600-X8 in Kolfe.................................................................................................... 413
18.3.14 CX600-X8 in Burau .................................................................................................. 414
18.3.15 CX600-X8 in Asko .................................................................................................... 415
18.3.16 CX600-X8 in Shegole ................................................................................................ 416
18.3.17 CX600-X8 in Gebeya ................................................................................................ 417
18.3.18 CX600-X8 in Ferensail.............................................................................................. 418
18.3.19 CX600-X8 in Kotebe ................................................................................................. 419
18.3.20 CX600-X8 in Ayat..................................................................................................... 420
18.3.21 CX600-X8 in Gerji .................................................................................................... 421
18.4 CSG Site ATN Layout ....................................................................................................... 422
18.4.1 Scenarios1: ATN 1x10GE without E1......................................................................... 422
18.4.2 Scenarios2: ATN 1x10GE with E1 .............................................................................. 423
18.4.4 Scenarios4: ATN 2x10GE with E1 .............................................................................. 424


Appendix............................................................................................................................... 427

Figures
Figure 2- 1 Services Interruption time Requirement ........................................................................................................................8

Figure 3- 1 Wireless Service Solution ...........................................................................................................................................10
Figure 3- 2 IP CORE Optimization and Legacy CS/PS Service Migration ...................................................................................11
Figure 3- 3 Solution from BSC/RNC to CS/PS Network ..............................................................................................................12
Figure 3- 4 Solution from Huawei CS to Current CS ....................................................................................................................13
Figure 4- 1 Network Architecture ..................................................................................................................................................15
Figure 4- 2 Physical Topology.......................................................................................................................................................16
Figure 4- 3 IPRAN Network Design .............................................................................................................................................17
Figure 4- 4 Arada Site ...................................................................................................................................................................22
Figure 4- 5 Microwave Site ...........................................................................................................................................................23
Figure 4- 6 Bole Site......................................................................................................................................................................23
Figure 4- 7 Kirkos Site ..................................................................................................................................................................24
Figure 4- 8 Nifas Silk Site .............................................................................................................................................................24
Figure 5- 1 CX600 Series Family ..................................................................................................................................................26
Figure 5- 2 NE40E Series Family ..................................................................................................................................................27
Figure 5- 3 ATN Frame .................................................................................................................................................................27
Figure 7- 1 ISIS design overview ................................................................................................................................................124
Figure 7- 2 ISIS process design ...................................................................................................................................................125
Figure 7- 3 ISIS cost design.........................................................................................................................................................127
Figure 7- 4 Configure example topology .....................................................................................................................................128
Figure 7- 5 Bgp design overview .................................................................................................................................................138
Figure 7- 6 Routing policy design for access side .......................................................................................................................139
Figure 7- 7 Routing Policy Design ..............................................................................................................................................140
Figure 7- 8 Route advertisement design (LTE X2) ......................................................................................................................140
Figure 7- 9 Route advertisement design (2G/3G/LTE S1) ...........................................................................................................141
Figure 7- 10 Route Reflectors design ..........................................................................................................................................142
Figure 7- 11 BGP neighbor requirement between RSGs (scenarios 1) ........................................................................................142
Figure 7- 12 BGP neighbor requirement between RSGs (scenarios 2) ........................................................................................143
Figure 7- 13 Configure example topology ...................................................................................................................................146
Figure 8- 1 Configure example topology .....................................................................................................................................159
Figure 8- 2 MPLS TE design overview .......................................................................................................................................169
Figure 8- 3 MPLS TE Path design ...............................................................................................................................................173
Figure 8- 4 MPLS TE Path design result .....................................................................................................................................174
Figure 8- 5 MPLS TE design result .............................................................................................................................................175
Figure 8- 6 configure example topology ......................................................................................................................................177
Figure 9- 1 Mobile services design overview ..............................................................................................................................184
Figure 9- 2 The two scenarios at the Service access side .............................................................................................................186

Figure 9- 3 VRF RT Design ........................................................................................................................................................189

Figure 9- 4 VRRP Design ............................................................................................................................................................191
Figure 9- 5 Reliability Design result in Access ring ....................................................................................................................194
Figure 9- 6 Reliability Design result on ASG node .....................................................................................................................194
Figure 9- 7 Reliability Design result in Aggregation ring............................................................................................................195
Figure 9- 8 Reliability Design result on RSG node .....................................................................................................................195
Figure 9- 9 Reliability Design result in base station controller side ............................................................................................195
Figure 9- 10 adding a node to the access ring ..............................................................................................................................196
Figure 9- 11 adding a node between two CSGs on the access ring ..............................................................................................197
Figure 9- 12 adding a node between the source ASG and sink CSG on the access ring ..............................................................197
Figure 9- 13 adding a node between two ASGs on the aggregation ring .....................................................................................198
Figure 9- 14 adding a node between the source RSG and sink ASG on the aggregation ring .....................................................199
Figure 9- 15 adding a node to a link ............................................................................................................................................199
Figure 9- 16 adding a node between two CSGs ...........................................................................................................................200
Figure 9- 17 configure example topology ....................................................................................................................................201
Figure 9- 18 LTE X2 service overview .......................................................................................................................................211
Figure 9- 19 LTE X2 service basic designs in BGP relationship .................................................................................................211
Figure 9- 20 VRF RT design .......................................................................................................................................................212
Figure 9- 22 2G TDM service design overview...........................................................................................................................216
Figure 9- 23 2G TDM service reliability design ..........................................................................................................................218
Figure 9- 24 2G TDM service reliability result in access ring .....................................................................................................219
Figure 9- 25 2G TDM service reliability result on ASG node .....................................................................................................220
Figure 9- 26 2G TDM service reliability result in aggregation ring ............................................................................................220
Figure 9- 28 CS Active and Standby Interface Scenario...........................................................................................................225
Figure 9- 29 CS Dual Active Interface Scenario .........................................................................................................................225
Figure 9- 30 PS Active and Standby Interface Scenario ..............................................................................................................255
Figure 9- 31 PS Dual Active Interface Scenario ..........................................................................................................................256
Figure 9- 32 PS Gi Interface Scenario .........................................................................................................................................256
Figure 10- 1 Residential HSI service transmission process .........................................................................................................273
Figure 10- 2 residential HSI service bearer mode ........................................................................................................................274
Figure 10- 3 HSI service deploy ..................................................................................................................................................275
Figure 10- 4 HSI service typical topology ...................................................................................................................................276
Figure 10- 5 HIS service overview ..............................................................................................................................................276
Figure 10- 6 HSI service VLAN design.......................................................................................................................................277
Figure 10- 7 HSI packet forwarding overview ............................................................................................................................277
Figure 10- 8 HSI reliability design ..............................................................................................................................................278
Figure 10- 9 VoIP service procedure ...........................................................................................................................................280
Figure 10- 10 VoIP service bearer mode .....................................................................................................................................281
Figure 11- 1 physical Network design in core site .......................................................................................................................286
Figure 11- 2 logical network design ............................................................................................................................................287
Figure 11- 3 physical connection design in Nifas Silk.................................................................................................................291
Figure 11- 4 NE40E layout in Nifas Silk site ..............................................................................................................................292

Figure 11- 5 physical connection design in Kirkos ......................................................................................................................293

Figure 11- 6 NE40E layout in Kirkos site....................................................................................................................................295
Figure 11- 7 physical connection design in Bole .........................................................................................................................295
Figure 11- 8 NE40E layout in Bole site .......................................................................................................................................296
Figure 11- 9 physical connection design in Microwave...............................................................................................................297
Figure 11- 10 NE40E layout in Microwave site ..........................................................................................................................298
Figure 11- 11 physical connection design in Arada .....................................................................................................................299
Figure 11- 12 NE40E layout in Arada site ...................................................................................................................................299
Figure 11- 12 NE40E layout in Arada site ...................................................................................................................................300
Figure 11- 13 ISIS deployment design ........................................................................................................................................301
Figure 11- 14 BGP deployment design ........................................................................................................................................305
Figure 11- 15 BGP Route Control for Redundant PEs ................................................................................................................307
Figure 11- 17 BGP/MPLS L3vpn Option A Solution ..................................................................................................................307
Figure 11- 18 Inter-ASBGP/MPLS L3vpn Option C Solution ....................................................................................................308
Figure 11- 18 MPLS design overview .........................................................................................................................................312
Figure 11- 19 CS service bearer overview ...................................................................................................................................314
Figure 11- 20 PS service bearer ...................................................................................................................................................315
Figure 12- 1 The traffic module of the IP CLK Solution .............................................................................................................319
Figure 12- 2 The connection between the BITS and RSGs .........................................................................................................322
Figure 12- 3 The external clock interface of the RSGs ................................................................................................................322
Figure 12- 4 Clock priority planning on ET IP RAN network .....................................................................................................323
Figure 13-1 IP & MPLS Forward Traffic Classification .............................................................................................................326
Figure 13-2 Scenerio one: RNC/BSC and CS/PS domain in the same site ..................................................................................327
Figure 13-3 Scenerio two: RNC/BSC and CS/PS domain in the diffrent site ..............................................................................327
Figure 13-4 The qos marking behavior from base station to base station controller ....................................................................328
Figure 13-5 The qos marking behavior from base station Controller to CS/PS domain. .............................................................328
Figure 13- 6 The congestion management and avoidance from basestation to basestation controller .........................................330
Figure 13- 7 The congestion management and avoidance from BSC/RNC to CS/PS domain .....................................................330
Figure 14- 1 Design for end to end NMS.....................................................................................................................................334
Figure 14- 2 Design for Mangement Route .................................................................................................................................335
Figure 14- 3 Design for RTN .......................................................................................................................................................338
Figure 14- 4 Traffic module of the Base Station OAM ...............................................................................................................339
Figure 14- 5 The IP design for the heartbeat communication ......................................................................................................343
Figure 14- 6 The IP design for the NE Management ...................................................................................................................343
Figure 14- 7 The IP design for the Server & Disk array Management ........................................................................................344
Figure 17- 1 IPTV MVPN deployment .......................................................................................................................................379
Figure 17- 2 IPTV multicast service ............................................................................................................................................380
Figure 17- 3 The process of an STB's access to the broadband network .....................................................................................382
Figure 17- 4 Multicast deployment topology ...............................................................................................................................383

Tables
Table 2- 1 Data traffic please check following table .......................................................................................................................5

Table 2- 2 Voice traffic please check following table .....................................................................................................................6
Table 2- 3 Service Bandwidth .........................................................................................................................................................6
Table 2- 4 Service KPI Requirements .............................................................................................................................................7
Table 3- 1 The Private Network IP Requirement table ..................................................................................................................13
Table 5- 1 CX600 Board Type ......................................................................................................................................................30
Table 5- 2 NE40E Board Type ......................................................................................................................................................31
Table 5- 3 ATN950B Board Type .................................................................................................................................................32
Table 5- 4 S9303 Board Type ........................................................................................................................................................32
Table 5- 5 S9306 Board Type ........................................................................................................................................................32
Table 6- 1 VLAN Planning..........................................................................................................................................................122
Table 7- 1 Basic Functions design ...............................................................................................................................................125
Table 7- 2 Basic functions design ................................................................................................................................................138
Table 7- 3 Forcing an ASG to Select Base Station Routes Advertised by CSGs Preferentially ..................................................144
Table 7- 4 Forcing an ASG to Select Local Routes Preferably ....................................................................................................144
Table 8- 1 Basic Functions design ...............................................................................................................................................158
Table 8- 2 MPLS parameters .......................................................................................................................................................169
Table 8- 3 MPLS TE tunnel parameters ......................................................................................................................................170
Table 8- 4 Constrained interfaces of TE tunnels .......................................................................................................................173
Table 9- 1 the IP and VLAN design at the Access side ...............................................................................................................185
Table 9- 2 Service Bearer design .................................................................................................................................................187
Table 9- 3 BGP VPNv4 route design ........................................................................................................................................188
Table 9- 4 RD and RT design table .............................................................................................................................................189
Table 9- 5 Reliability Design .......................................................................................................................................................190
Table 9- 6 QoS Mapping .............................................................................................................................................................200
Table 9- 7 VRF RT design example ............................................................................................................................................212
Table 9- 8 VRF RT design result .................................................................................................................................................213
Table 9- 9 Qos design ..................................................................................................................................................................214
Table 9- 10 2G TDM service basic design ...............................................................................................................................217
Table 9- 11 2G TDM service reliability design ...........................................................................................................................218
Table 9- 12 Qos design ................................................................................................................................................................220
Table 10- 1 major functions of devices on the residential HSI service bearer network ...............................................................273
Table 10- 2 Service protects information .....................................................................................................................................278
Table 10- 3 Main functions of devices deployed at different network layers ..............................................................................280
Table 11- 1 core site list...............................................................................................................................................................287
-1-
Table 11- 2 core site equipment list .............................................................................................................................................287

Table 11- 3 Loopback assignment design ....................................................................................................................................289
Table 11- 4 Interconnection IP assignment design ......................................................................................................................290
Table 11- 5 Port Connections in Nifas Silk Site .......................................................................................................................291
Table 11- 6 Port Connections in Kirkos Site ............................................................................................................................293
Table 11- 6 Port Connections in Bole Site ................................................................................................................................295
Table 11- 5 Port Connections in Microwave Site .....................................................................................................................297
Table 11- 5 ISIS design result......................................................................................................................................................301
Table 11- 6 ISIS metric planning in Microwave ..........................................................................................................................302
Table 11- 7 ISIS metric planning in Kirkos .................................................................................................................................302
Table 11- 8 ISIS metric planning in Bole ....................................................................................................................................302
Table 11- 9 ISIS metric planning in Arada ..................................................................................................................................302
Table 11- 10 ISIS metric planning in Nifas Silk ..........................................................................................................................302
Table 11- 8 CS device interface and target VRF .........................................................................................................................314
Table 11- 9 PS device interface and target VRF ..........................................................................................................................315
Table 11- 10 VPN Naming, RD and RT design...........................................................................................................................317
Table 13-1 PQ+WFQ Design ......................................................................................................................................................329
Table 13-2 WRED Drop Threshold for Different Packet Color ..................................................................................................330
Table 14- 1 VRF design of base station OAM .............................................................................................................................339
Table 14- 2 The IP design result for U2000 .................................................................................................................................344
Table 14- 3 Supported NBI functions by U2000 .........................................................................................................................345
Table 15- 1 Local User List .........................................................................................................................................................348
-2-
1 Project Overview
Ethiopia is political center of Africa, holding huge population and quick economic development. There
are strong telecom requirements in Ethiopia, including voice, data and broadband etc.
Being the only telecom operator in Ethiopia, Ethio Telecom is committed to be a world class telecom
operator for the country and serve the Ethiopian citizens with universal telecom service and national
broadband.
According to the Ethiopian government’s Growth and Transformation Plan and Ethio Telecom’ goal,
Ethiopia Telecom will modernize the whole nationwide networks with state-of-art technologies and
advanced telecom services in recent 2 years.
Currently, poor network quality already seriously affect Ethio Telecom’s brand and Ethiopia politics and
economics position, improving the network quality is becoming the most urgent work for Ethio Telecom
currently.
Based on understanding of ET’s requirement and Huawei’s worldwide experience, we will propose the
integrated solution for network modernization; finally we will provide high quality and best experience
voice and data services.
The ET IPRAN archtectrue is show below:
CR/ER CR/ER CR/ER CR/ER
IPCORE
GGSN SGSN GGSN SGSN
NE40E-X8 NE40E-X8 NE40E-X8 NE40E-X8
MSOFT3000 UMG8900 MSOFT3000 UMG8900

Core Network Core Network
CX600-X16 CX600-X16 CX600-X16 CX600-X16
BSC RNC BSC RNC
Agg Layer
IPRAN
CX600 CX600 CX600 CX600
CX600 CX600
MSAG ATN RTN MSAG ATN ATN

ATN ATN ATN ATN RTN MSAG RTN
MSAG MSAG MSAG
Access Layer MSAG ATN RTN ATN RTN
MSAG RTN
MSAG MSAG
-3-
Five NE40E-x8 pairs will be installed in the IP Core network to connect Huawei CS/PS device and
existing IPCore CR/ER. Five CX600-X16 pairs will be installed in the IP RAN network as RSG to
connect Huawei RNC/BSC device and Huawei NE40E. 21 CX600-X8 pairs will be installed in the IP
RAN network as ASG to aggregate the traffic from CSG to RSG. 129 ATN950Bs will be installed in the
IPRAN network as CSG to connect the Base Station
This document will give the detailed introduction about Huawei’s solution and low level design (LLD)
for IP Transmission network modernization, including network equipment, IP protocol design, clock sync,
NMS, etc; It includes:
 Chapter 1:Project Overview
 Chapter 2:Network Requirement
 Chapter 3: Solution Overview
 Chapter 4: Network Architecture Design
 Chapter 5: Product and Naming
 Chapter 6: Logical Planning and Design
 Chapter 7: Routing protocol Design
 Chapter 8: MPLS Protocol design
 Chapter 9: Mobile Services Implement
 Chapter 10: Fixed-Line Services Implement
 Chapter 11: Interconnection Implement
 Chapter 12: Synchronization Design
 Chapter 13: QoS Design
 Chapter 14: Network Management System
 Chapter 15: Security Design
 Chapter 16: Future IPV6 Evolution
 Chapter 17: Future Multicast
 Appendix
-4-
2 Network Requirement
2.1 Performance Requirement

As per mobile subscriber development plan, swapping and new mobile base station will be deployed in
Addis Ababa. Base on planning, 722 physical sites will be deployed in Addis Ababa, include 614 BTSs,
722 NodesB and 329 eNodeBs. Also, 5 BSC and 5 RNC will be corresponding set up. There are 5 CS
sites, 4 PS sites, Arada site PS for regions which is not belong to this project. The mobile service traffic
forecast is given by mobile planning team as follow:
PS data traffic:
 Gb(2G)=0.8K*920000=736M
 Iu_PS(3G)=23K*1500000=34500M
 S1_U(LTE)=100k*400000=40000M
Table 2- 1 Data traffic please check following table
PS Interface Single Subscriber Rate Total Subscribers Total Bandwidth

Gb 0.8K 920,000 736M
Iu_PS 23K 1,500,000 34,500M
S1_U 100K 400,000 40,000M
Total 75,236M
CS voice traffic:
PerUser@BusyHour Rate=Erl@BH*ActivityFactor*Ri
AMR12.2, Activity Factor: 0.67
Ri: Bearer or Services bit rate, for example: AMR12.2 is 12.2kbps, in IP layer is 30kbps
PerUser@BusyHour Rate=Erl@BH*ActivityFactor*Ri =0.025*0.67*30K=0.503Kbps
 A(Voice)=0.503K*4656767=2342353K
 Iu_CS(Voice)=0.503K*1521408=765268K
-5-
Table 2- 2 Voice traffic please check following table
CS Interface Erl Codec Total Subscriber Total Bandwidth

A 0.025 AMR12.2 4656767 2342M
Iu_CS 0.025 AMR12.2 1521408 765M
Total 3103M
RF new plan 722 swapping/new BTS/NodeB/e-NodeB
 GSM(per node)=3078M/614=5M
 UMTS(per node)=35265/722=49.3M
 LTE(per node)=40000/329=121.6M
Table 2- 3 Service Bandwidth
System Total Bandwidth Count Bandwidth Requirement

GSM 3078M 614 5M
UMTS 35265M 722 49.3M
LTE 40000M 329 121.6M
Total 78343M
Huawei plan and design 80GE bandwidth for Centre aggregation ring in this phase, reserve enough
slots for fixed-line service and future extension.
2.2 QoS Requirement

There are four elements for measuring QoS and SLA: Availability, Latency, Jitter and Packet loss.
Availability: refers to the percentage of the time when the service is available to users against the total
service rental time.
Latency: refers to the time between a packet being sent and being received from basestation to the
controller.
Jitter: refers to the difference between delays of each packet.
Packet loss: refers to the percentage of the packets lost against the total packets transmitted between two
the basestation and the controller. Packet loss is caused mainly by congestion.
Backhaul must meet the bellowing requirement. Recommanded Qos will be provide in ET IPRan:
Type Latency Jitter PLR

Best 10ms 2ms 0.0001%
2G/3G/LTE-S1 Recommended 20ms 4ms 0.001%
Tolerable 40ms 8ms 0.5%
-6-
Best 20ms 4ms 0.0001%

LTE-X2 Recommended 40ms 7ms 0.001%
Tolerable 80ms 10ms 0.5%
All the data in the table is base on the worst case. Worst case main the base station connected to CSG, and
the CSG connect to the ASG, and ASG connect to the RSG, and RSG connect to the controller.the hop on
the path is the most.
The target IP Backhaul network is a FMC based network, carries multiple services, each with its own
unique set of requirements. For Mobile service, low latency, jitter and packet loss are the key factors for
high quality service. So Mobile service requires the Backhaul network to provide efficient tunnel
transport and provide various reliability technologies to ensure minimal delay and fast recover when
failure happened.
For HSI, the key requirements are high acceptable bandwidth, minimal delay and jitter. HSI requires the
Backhaul network to provide unlimited bandwidth support and flat network architecture such as BRAS to
edge.
Corporate VPN services require always-on bandwidth and minimal delay and jitter. As such, the
requirement on the network is guaranteed Hard QoS for each and every corporate VPN customer.
Therefore, various cutting-edge technologies, such as MPLS Hierarchical QoS [MPLS H-QoS] need to
be deployed on the Ethio Telecom Backhaul network.
Real-time Application services such as VoIP and IPTV are very sensitive to network delay, jitter and
packet loss. VoIP is the most sensitive to delay and thus requires the Backhaul network to support various
cutting-edge technologies to ensure end-to-end lower delay. IPTV is most sensitive to packet loss, if the
lost frame is an i-frame, which contains the most detailed information, it could lead to very noticeable
reduction in IPTV quality. Hence, the network should contain appropriate technologies to allow constant
monitoring of real-time applications, and retransmit lost packets in case of packet loss.
The following figure shows the KPI requirements for different service.
Table 2- 4 Service KPI Requirements
Service Service KPI Requirements Main point of
Name Bandwidth Delay Jitter Packet Loss Scalability
Residen Typical
HSI Low Low High MAC table
tial 512Kbps
Triple-p Bandwidth,D
BTV 2Mbps Mid Mid High
lay uplicate
-7-
services Point
VoD 2Mbps Mid Mid High Bandwidth
Network
VoIP 120Kbps High High Low
QoS
Enterpri L2VPN MAC
se VPN By SLA Mid Mid High table,VC ID

L3VPN
services number
Mobile Mobile
Network
backhau By Service High High High
Backhaul QoS
l
2.3 High Availability Requirement

The Availability for the Network
The availability of the IP Backhaul network has direct impact on the customers’ satisfaction of the
services and the profit of the telecom operators. For each major services carried, the availability
requirements are as follows.
Figure 2- 1 Services Interruption time Requirement
In brief, the IP/MPLS network must make sure the 200ms convergence time if some links or nodes
failure.
The Availability for the equipment
The Avalibility for Huawei device is list below:
NE40E-X8 CX600-X8 CX600-X16 ATN950B S9300

MTBF(year) 36.23 36.38 36.23 22.83 24.1
MTTR(hour) 0.5 0.5 0.5 2 0.5
Reliability 0.999998424 0.999998431 0.999998424 0.99999 0.999996
-8-
2.4 Scalability Requirement

As services develop, the IPRAN capacity must be expanded. Available capacity expansion methods
include adding nodes to the access ring, aggregation ring and links. Below Scenario need be mention in
this document
 Adding a node between two CSGs on the access ring.
 Adding a node between the source ASG and sink CSG on the access ring.
 Adding a node between two ASGs on the aggregation ring.
 Adding a node between the source RSG and sink ASG on the aggregation ring.
 Adding a node to a link.
 Removing a node from the access ring, aggregation ring, and links.
2.5 Security Requirement

For network security issues, ET need Huawei provide series of solution to import the IPRAN network
Security and prevent network invasion, disoperation, etc. The solution includes M2000 Security, NE
Security, Network Security, NMS Server Security, Database Security, and Log Management etc.
All the devices in network won’t directly expose to external potential attacker, and almost services of ET
Network are transported through MPLS that provides better security than IP transportation. To summary
up, ET IP RAN Network faces relatively low security threats. We propose to deploy the following
security measures in the Network. All the routers and switches enable Control Plane Protection function
to protect CPU from attacking. (Enable by default)
ISIS, LDP and BGP runs in ET network enable MD5 neighbor authentication to prevent DOS attacking.
Regarding the detailed information, please refer to the chapter 15 sercurity sections.
Secure operation and management measures like SSH, AAA,. Regarding the detailed information, please
refer to the chapter 15 sercurity sections.
Application-layer service association function will create the security policy dynamically.
Disable all the unnecessary services such as ftp, telnet etc.
-9-
3 Solution Overview
3.1 Solution Overview

3.1.1 Wireless Service Solution Overview
Totally five core site in Addis Ababa. Only NifasSilk connect to the ZTE ER router which in existing network. And Bole,
Microwave, Kirkos and Arada will connect to the ZTE CR router which in existing network.
Figure 3- 1 Wireless Service Solution
2G/3G/LTE CX600-X8 Master IPCLK
BSC/RNC MGW
2G/3G/LTE ATN950B MSC
2G/3G/LTE
CX600-X8 2G/3G/LTE CR/ER
NE40E-X8
ATN950B EPC
2G/3G/LTE S9303
ATN Network CX Network CX600-X16 IP Core
2G/3G/LTE SGSN
CR/ER
ATN950B E8000E
GGSN
CX600-X8 Slave IPCLK
2G/3G/LTE 2G/3G/LTE
U2000 Server Core Site
MW
Hierarchy
Native ETH L3VPN
L3VPN L3VPN IP/MPLS VPN
2G ETH
3G ETH
Access Tunnel Aggregate Tunnel IP Core Tunnel
LTE S1
LTE X2
X2
L3VPN L3VPN IP/MPLS VPN
Hierarchy L3VPN
-10-
Figure 3- 2 IP CORE Optimization and Legacy CS/PS Service Migration
In first 6 months, NE40E integrate Huawei CS/PS service, interconnect IP CORE network by ER/CR
routers (NifasSilk connect to ER), considering bandwidth growth, capacity evolution, L2 switch stability
and reasonable network architecture. It is necessary to optimize IP CORE architecture. Voice ER will be
offline, NE40E uplinks directly connect to CR, legacy CS/PS service switch (T64G) will be migrated into
NE40E, then migrate CS/PS service connect from Old T64G to new S9300 switch step by step
CS/PS service migration is complicated and high-rish operation, professional service should be put into
PB.
The Ethiopia IP RAN part comprises huge quantity of routers. Those routers vary in forwarding/routing
capacity/function and link bandwidth. Besides, the connectivity between ATN sites are not fixed.
Depending on wireless expansion requirements, adding sites or physical connection changes happen
frequently. In other words, scalability, resiliency, and topology adaptability are the considerations for IP
RAN design.
To reach these design goals, the Hierarchical VPN (HVPN) solution is adopted for Ethiopia IP RAN
project. HVPN is simple in theory, but easy to configure. The configuration of a hierarchy VPN is similar
to that of an end-to-end (E2E) VPN, requiring less maintenance skills.
On a hierarchy VPN, IGP routes are completely isolated by processes or areas on the access ring and
aggregation ring. Devices on a ring are unaware of link break or node faults on another ring. This
improves the network robustness. When base stations need to connect to a different BSC/RNC or when
-11-
devices need to be added on a ring, only configurations of devices on an access ring need to be adjusted.
Devices on an aggregation ring require no configuration modification.
The link state databases (LSDBs) of devices on the same ring are synchronized, and there are not many
Layer 3 protocol entries in each LSDB. Theoretically, a hierarchy VPN is applicable to a network where
10000 ATN+CX devices are connected in the network if bandwidth is sufficient. (HVPN can support 50
pairs ASG at most, and support 200 ATN for each ASG pair )
2/3G and LTE services will be carried in IPRAN network. All services are end-to-end services.
Hierarchical L3VPN will be deployed for the three services. RSGs and ASGs will function as RRs.
Reflect the private network route from CSG to RSG. And also reflect the private network route from RSG
to CSG.
3.1.2 Core Network Solution Overview

Figure 3- 3 Solution from BSC/RNC to CS/PS Network
Controller IPRAN IPCORE CS/PS Domain

BSC CX600 NE40E
GGSN SGSN
CX600
Option A
RNC NE40E
MSOFT3000 UMG8900
Option A-L3VPN
Gb Vrf Gb Vrf
Sig Vrf Sig Vrf
Media Vrf Media Vrf
Iur Vrf Iur Vrf
Iuu Vrf Iuu Vrf
CoreNetwork Service
The stream from BSC/RNC to core network passby IPRAN and IPCORE. Native IP is deployed between
the backbone network and the backhaul network. Between CX600 and NE40E, each VPN needs an
independent sub-interface. However, due to restrictions to the number of VLANs and subinterfaces, the
number of inter-AS/domain VPNs supported by Option A is limited. Services will be sensed by
inter-AS/domain nodes.
-12-
Figure 3- 4 Solution from Huawei CS to Current CS
IP Core Other
NE40E-1 Cloud Site
MSOFT3000 UMG8900 MSOFT3000 UMG8900
NE40E-2
Billing Vrf Billing Vrf
Sig Vrf LDP LSP Sig Vrf
Media Vrf Media Vrf
Li-CS Vrf Li-CS Vrf
Huawei Core network will be put in IP CORE. Between HW NE40E and CR Router, MPLS LDP is
deployed to carry L3VPN service.
3.2 Addressing the Requirement

3.2.1 Private Network IP Requirment
Table 3- 1 The Private Network IP Requirement table
Service Mode Count Requirment Summary IP Block Reserved

per site
1 Loopback for 191 1 2C 10.0.5.0/24 10.0.5.53-60
ATN&CX&NE40E 10.0.5.190-230
10.0.5.241-255
2 Interconnection 181 8 6C 10.1.(23 - 28).0/24 10.1.28.0/24
bewtween ATN&CX
3 Interconnection 10 0.5C 5C 10.1.(29 - 33).0/24 finish
bewtween CX&NE40E
4 IP for MW OAM 144 4 4C 10.204.(206-209).0/24 10.204.(210-213).0/24
5 IP for 2G base station 614 8 13C 10.204.(0-19).0/24 10.204.(20-26).0/24
6 IP for 3G base station 722 8 15C 10.204.(27-49).0/24 10.204.(50-57).0/24
7 IP for 4G base station 329 12 15C 10.204.(58- 75).0/24 10.204.(76-81).0/24
8 IP for base station OAM 722 8 15C 10.204.(82-105).0/24 10.204.(106-113).0/24
9 IP for BSC 5 1C 5C 10.204.(114-118).0/24 10.204.(119-120).0/24
10 IP for RNC 5 1C 5C 10.204.(121-125).0/24 10.204.(126-127).0/24
11 IP for bole CS 1 1C 1C 10.184.128.0/24 finish
IP for Arada CS 1 1C 1C 10.185.128.0/24 finish
IP for microwave PS 1 2C 2C 10.186.96-97.0/24 finish
IP for microwave CS 1 1C 1C 10.186.128.0/24 finish
IP for kirkos PS 1 2C 2C 10.202.0-1.0/24 finish
-13-
IP for kirkos CS 1 1C 1C 10.202.32.0/24 finish

IP for nifassilk PS 1 2C 2C 10.203.0-1.0/24 finish
IP for nifassilk CS 1 1C 1C 10.203.32.0/24 finish
12 IP for E&I Core Station 20 10 2C 10.204.(128~129).0/24 10.204.(155~159).0/24
13 IP for E&I CX Station 4 16 1C 10.204.130.0/24
14 IP for E&I Common 765 8 24C 10.204.(131-154).0/24
Station
15 IP for A&S 3 12C/10C/10C 32C 10.204.(160-191).0/24 10.204.(192~199).0/24
16 IPCORE Integration 5 1C 5C 10.1.(34 - 38).0/24 finish
17 PS private cell-phone 3 4B 12B 10.40-51.0/16 finish
pool
18 IP for CS M2000 1 1C 1C 10.204.200.0/24 10.204.201.0/24
19 IP for Wireless M2000 1 1C 1C 10.204.202.0/24 10.204.203.0/24
20 IP for IP&RTN U2000 2 0.5C 1C 10.204.204.0/24 10.204.205.0/24
Summary 13B 10.204.(214~255).0/24
-14-
4 Network Architecture Design
4.1 Network Architecture Overview

Figure 4- 1 Network Architecture
The ET IPRAN network is composed of ATN950B, CX600 and NE40E equipments. Among them,
ATN950B devices are used as CSGs on the base station side, CX devices (including CX600-X8/X16) are
used as ASGs on the aggregation side and the RSG on the base station controller site. NE40E place at the
same site with CS/PS play as the same role as ZTE Voice ER, And Interconnect to the ER device which
is existed in ZTE IP Core network, NE40E also will connect to the PS/CS device.
At access side, Radio BTS/NodeB/eNodeB without optical resource will connect to Microwave first, and
Radio BTS/NodeB /eNodeB with optical resource will connect to ATN950B directly as well.
-15-
CX600-X16 will work as RSG device at Core node, and RNC/BSC will connect to the CX600-X16, In
Addis Ababa, there are 5 set RNC/BSC, which will be placed in 5 sites (Microwave, Kirkos and Nifas
Silk, Bole,Arada)
4.2 Physical Topology Overview

In order to utilize the existing fiber resource in Addis Ababa the entire network topology is designed as
below:
Figure 4- 2 Physical Topology
4.3 IPRAN Network Design

As shown in figure below, the ET IPRAN network is designed to carry the 2G/3G/LTE (Long Term
Evolution) mobile services:
-16-
Figure 4- 3 IPRAN Network Design
RSG (Radio Service Gateway) pairs are deployed for connecting base station controllers (BSCs) and
radio network controllers (RNCs) directly, while mobility management entities (MMEs) connected to
RSG through the NE40E.
Huawei deploy 5 core sites in Addis Ababa.
Region Site ID Site Name Latitude Longitute Device Type Device amount
CAAZ 111051 Microwave 9.018475 38.747067 CX600-X16+NE40E-X8 2+2
EAAZ 111136 Bole 8.999854 38.784662 CX600-X16+NE40E-X8 2+2
NAAZ 111055 Arada 9.03325 38.75031 CX600-X16+NE40E-X8 2+2
SAAZ 111007 NifasSilk 8.963958 38.762735 CX600-X16+NE40E-X8 2+2
SAAZ 111168 Kirkos 8.994036 38.753809 CX600-X16+NE40E-X8 2+2
The aggregation layer consists of ASGs (Aggregation Site Gateway) aggregating traffic from the access
layer. To improve the reliability of aggregation nodes, deploy an ASG pair for each access area.
Huawei deploy 21 Agg sites in Addis Ababa. ASG use CX600-X8 routers
Device
Region Site ID Site Name Latitude Longitute Device Type amount
CAAZ 111058 Filowaha 9.013441 38.753355 CX600-X8 2
EAAZ 111010 BoleMchael 8.98065 38.77559 CX600-X8 2
EAAZ 111082 Yeka 9.01979 38.81979 CX600-X8 2
EAAZ 111086 Kotebe 9.02262 38.85366 CX600-X8 2
EAAZ 111089 Gerji 8.99399 38.81289 CX600-X8 2
EAAZ 111165 AyatMeronia 9.02197 38.87414 CX600-X8 2
NAAZ 111038 AddisuGebeya 9.058421 38.734723 CX600-X8 2
NAAZ 111148 SidistKilo 9.04202 38.76663 CX600-X8 2
-17-
NAAZ 111161 Ferensailegasion 9.054265 38.778317 CX600-X8 2

SAAZ 111120 HannaMariam 8.945814 38.747414 CX600-X8 2
SAAZ 111228 Lebu 8.94401 38.73421 CX600-X8 2
SAAZ 111408 Akaki 8.867261 38.789313 CX600-X8 2
SAAZ 111767 Kality 8.932093 38.762553 CX600-X8 2
SWAAZ 111128 OldAirport 8.99781 38.7314 CX600-X8 2
SWAAZ 111176 Karanyo 9.007087 38.702855 CX600-X8 2
SWAAZ 111205 Mekanisa 8.969952 38.731072 CX600-X8 2
WAAZ 111030 Kolfe 9.04001 38.71341 CX600-X8 2
WAAZ 111057 AddisKetema 9.034465 38.732936 CX600-X8 2
WAAZ 111124 Shegole 9.06277 38.71949 CX600-X8 2
WAAZ 111163 284E(Asko) 9.06435 38.69815 CX600-X8 2
WAAZ 117001 Burau 9.07737 38.67181 CX600-X8 2
The access layer consists of CSGs (Cell Site Gateway). The network topology can be a ring or chain
depending on fiber connections between sites. Ring topology topology is recommended. Avoid planning
rings tangent at an ASG or a CSG, ring-with-ring, or rings across an aggregation node. Otherwise, tunnel
planning will be complex.
In some scenarios, CSGs will be directly connected to RSGs which we abbreviated it to D-CSG (directly
connected CSG). In this condition an E2E L3VPN will be deployed on them to carry the mobile service.
Huawei deploy 129 Access sites in Addis Ababa. CSG uses ATN950B routers.
Region CSG Aggregation Site ID Site Name Latitude Longitute Device Type Device
Site Name amount
SAAZ Akaki 111034 122_D 8.88319 38.78292 ATN950B 1
NAAZ Arada 111004 10 9.04442 38.74143 ATN950B 1
NAAZ 111068 34N 9.05525 38.73888 ATN950B 1
NAAZ 111069 36N 9.05642 38.74976 ATN950B 1
NAAZ 111075 52N 9.04344 38.75084 ATN950B 1
NAAZ 111118 134 9.0576 38.74372 ATN950B 1
NAAZ 111274 70 9.04842 38.7519 ATN950B 1
NAAZ 111420 74 9.02935 38.7527 ATN950B 1
WAAZ Asko 111067 25N 9.06836 38.68433 ATN950B 1
WAAZ 111048 286E 9.06514 38.70377 ATN950B 1
WAAZ 111062 08N 9.05676 38.69577 ATN950B 1
WAAZ 111063 10N 9.05218 38.6998 ATN950B 1
EAAZ Ayat 111407 75N 9.01707 38.89541 ATN950B 1
EAAZ Bole 111192 041D 9.00234 38.77863 ATN950B 1
EAAZ 111064 15N 9.00809 38.78028 ATN950B 1
EAAZ 111065 16N 9.02063 38.789 ATN950B 1
-18-
EAAZ 111074 51N 9.00824 38.79333 ATN950B 1

EAAZ 111105 14N 8.99243 38.78871 ATN950B 1
EAAZ 111277 180D 9.01524 38.78365 ATN950B 1
EAAZ 111397 70N 9.003622 38.783765 ATN950B 1
EAAZ 111406 50N 8.98726 38.78153 ATN950B 1
EAAZ 111421 130D 9.00484 38.78996 ATN950B 1
EAAZ 111006 18D 9.027333 38.784033 ATN950B 1
EAAZ Bole Michael 111399 82N 8.97698 38.77558 ATN950B 1
NAAZ Ferinas 111300 23N 9.06329 38.77715 ATN950B 1
CAAZ Filowoha 111040 185D 9.01935 38.73993 ATN950B 1
CAAZ 111042 192D 9.01207 38.77185 ATN950B 1
CAAZ 111043 194D 9.00735 38.76662 ATN950B 1
CAAZ 111109 81N 9.01349 38.74423 ATN950B 1
CAAZ 111202 022D 9.02257 38.76011 ATN950B 1
CAAZ 111273 045D 8.99298 38.77773 ATN950B 1
CAAZ 111393 035D 9.01277 38.74868 ATN950B 1
CAAZ 111396 NationalH 9.01289 38.76247 ATN950B 1
otel
CAAZ 111401 TesfayeM 9.01888 38.76802 ATN950B 1
ulatRealSt
ate
CAAZ 111405 09N 9.00867 38.77312 ATN950B 1
CAAZ 111418 84N 9.006 38.74029 ATN950B 1
NAAZ Gebeya 111079 60N 9.07112 38.73748 ATN950B 1
NAAZ 111060 05N 9.06596 38.74393 ATN950B 1
EAAZ Gerji 111095 307N 8.99775 38.80545 ATN950B 1
EAAZ 111125 290E 8.98901 38.81587 ATN950B 1
EAAZ 111164 BoleCom 8.98858 38.79953 ATN950B 1
munitySch
ool
SAAZ HannaMariam 111156 30N 8.9558 38.74204 ATN950B 1
SAAZ 111173 85N 8.94883 38.75321 ATN950B 1
SAAZ Kality 111157 33N 8.93128 38.75404 ATN950B 1
SAAZ 111072 47N 8.94096 38.77478 ATN950B 1
SAAZ 111073 48N 8.91533 38.76825 ATN950B 1
SAAZ 111196 125_D 8.92635 38.76317 ATN950B 1
SWAAZ Keranio 111302 76N 8.92111 38.66197 ATN950B 1
SWAAZ 111169 43N 9.00096 38.68864 ATN950B 1
SWAAZ 111171 55N 8.99251 38.70058 ATN950B 1
SWAAZ 111189 64N 9.00074 38.70063 ATN950B 1
SWAAZ 111214 59N 9.00583 38.71144 ATN950B 1
SWAAZ 111223 141D 8.99894 38.69567 ATN950B 1
-19-
SWAAZ 111427 79N 9.01115 38.70338 ATN950B 1

WAAZ Ketema 111001 004_D 9.03244 38.72548 ATN950B 1
WAAZ 111041 188_D 9.02262 38.72986 ATN950B 1
WAAZ 111080 67N 9.04564 38.73601 ATN950B 1
WAAZ 111081 69N 9.02112 38.73524 ATN950B 1
WAAZ 111131 002_D 9.03796 38.73558 ATN950B 1
WAAZ 111159 72N 9.02636 38.72731 ATN950B 1
WAAZ 111391 Medenabu 9.03309 38.74178 ATN950B 1
ilding
WAAZ 111404 03N 9.03361 38.72769 ATN950B 1
SAAZ Kirkos 111077 56N 8.9966 38.76015 ATN950B 1
SAAZ 111417 49N 8.98879 38.75315 ATN950B 1
WAAZ Kolfe 111182 175 9.02786 38.714 ATN950B 1
WAAZ 111153 137_D 9.04536 38.71181 ATN950B 1
WAAZ 111158 42N 9.05232 38.71242 ATN950B 1
WAAZ 111160 74N 9.04653 38.70449 ATN950B 1
WAAZ 111231 78N 9.02614 38.70876 ATN950B 1
WAAZ 111394 04N 9.04137 38.71027 ATN950B 1
EAAZ Kotebe 111398 73N 9.03859 38.83623 ATN950B 1
EAAZ 111400 297E 8.99663 38.84747 ATN950B 1
EAAZ 111093 300E 9.04072 38.84429 ATN950B 1
EAAZ 111096 308N 9.03181 38.8424 ATN950B 1
EAAZ 111097 309N 9.02969 38.8545 ATN950B 1
EAAZ 111101 314N 9.0068 38.84324 ATN950B 1
EAAZ 111102 315N 9.01517 38.85635 ATN950B 1
EAAZ 111103 316N 9.02228 38.86428 ATN950B 1
EAAZ 111119 301E 9.04153 38.86109 ATN950B 1
EAAZ 111162 283E 9.00879 38.85179 ATN950B 1
EAAZ 111166 313N 8.99954 38.83575 ATN950B 1
EAAZ 111230 296E 9.01808 38.84426 ATN950B 1
EAAZ 111409 298E 9.01228 38.864111 ATN950B 1
SAAZ Lebu 111211 317N 8.9582 38.70715 ATN950B 1
SAAZ 111212 71N 8.95217 38.72237 ATN950B 1
SWAAZ Mekanism 111184 80N 8.98945 38.68573 ATN950B 1
SWAAZ 111186 22N 8.9753 38.68612 ATN950B 1
SWAAZ 111227 54N 8.982897 38.692077 ATN950B 1
SWAAZ 111430 145D 8.98076 38.69439 ATN950B 1
SWAAZ 111433 28N 8.98682 38.67519 ATN950B 1
SWAAZ 111122 29N 8.97187 38.71365 ATN950B 1
SWAAZ 111183 65N 8.97426 38.72478 ATN950B 1
SWAAZ 111215 77N 8.98522 38.70844 ATN950B 1
SAAZ NifasSilk 111070 37N 8.9483 38.76512 ATN950B 1
-20-
SAAZ 111071 45N 8.97027 38.76644 ATN950B 1

SAAZ 111115 126_D 8.95654 38.76846 ATN950B 1
SAAZ 111123 46N 8.96305 38.7571 ATN950B 1
SWAAZ OldAirport 111121 53D 8.98901 38.73303 ATN950B 1
SWAAZ 111172 44N 8.97684 38.73177 ATN950B 1
SWAAZ 111190 62N 8.98835 38.7184 ATN950B 1
SWAAZ 111213 38N 9.01434 38.71217 ATN950B 1
SWAAZ 111216 61N 8.98371 38.73813 ATN950B 1
SWAAZ 111419 63N 9.0162 38.72175 ATN950B 1
WAAZ Shegole 111078 57N 9.06097 38.72649 ATN950B 1
WAAZ 111276 136 9.05372 38.72007 ATN950B 1
NAAZ SidisKilo 111278 12 9.04382 38.75874 ATN950B 1
NAAZ 111204 24N 9.0496 38.76464 ATN950B 1
NAAZ 111066 17N 9.03577 38.77979 ATN950B 1
NAAZ 111046 201 9.03695 38.76602 ATN950B 1
NAAZ 111061 06N 9.06955 38.75912 ATN950B 1
NAAZ 111076 53N 9.04225 38.77457 ATN950B 1
NAAZ 111108 01N 9.05631 38.763 ATN950B 1
NAAZ 111207 83N 9.05887 38.77005 ATN950B 1
NAAZ 111402 39N 9.04086 38.76113 ATN950B 1
EAAZ Yeka 111083 279E 9.02281 38.80266 ATN950B 1
EAAZ 111084 280E 9.03879 38.83116 ATN950B 1
EAAZ 111085 281E 9.01702 38.80674 ATN950B 1
EAAZ 111087 287E 9.02354 38.81197 ATN950B 1
EAAZ 111088 288E 9.00901 38.80637 ATN950B 1
EAAZ 111090 291E 8.99518 38.82653 ATN950B 1
EAAZ 111091 293E 9.02781 38.8324 ATN950B 1
EAAZ 111092 294E 9.01433 38.83578 ATN950B 1
EAAZ 111094 306N 9.0318 38.82083 ATN950B 1
EAAZ 111098 310N 9.02093 38.83018 ATN950B 1
EAAZ 111099 311N 9.01364 38.81229 ATN950B 1
EAAZ 111100 312N 9.00323 38.82949 ATN950B 1
EAAZ 111106 285E 9.00394 38.81958 ATN950B 1
EAAZ 111107 292E 9.01303 38.82072 ATN950B 1
EAAZ 111279 295E 9.00731 38.83545 ATN950B 1
4.4 Interconnection design

Principle for designing:
An entire ring is recommended for high reliability, especially with larger number of members.
-21-
We should design the logical topology strictly based on the physical environment, especially for saving
the optical fiber resource.
The interconnected interfaces at the aggregation and core layers should reside on different boards for
protection, and the service interfaces and master/slave interfaces at the core layer should reside on
different boards or devices.
The access layer can uses 10GE links for service access, but at the aggregation 2*10GE/1*40GE/2*40GE.
Multiple physical interfaces will be bundled into an Eth-Trunk using the link aggregation technique just
like smart group. The Eth-Trunk interface is a logical interface, having all functions of an Ethernet
interface and is more reliable.
 The bandwidth of ring Microwave-Filowoha-Bole-NifasSilk-Kirkos-OldAirport is 2*40GE
 The bandwidth of ring Microwave –Ketema-Arada-SidisKilo-Yeka-Bole-Filowoha is 1*40GE
 The rest of the CX ring is 2*10GE
 The ATN ring is 1*10GE
4.4.1 Core Site Topology

Figure 4- 4 Arada Site
Arada_CR_A Arada_CR_B
Arada_SW_CS_A Arada_SW_CS_B M6000
NE40E-X8
Arada_ER_HW_A Arada_ER_HW_B
CX600-X16
S9300
To To E8000E
Ferensail_ASG_B Addisu Gebeya_ASG_A
BSC
Arada_RSG_A Arada_RSG_B RNC
GE
10GE
40GE
To To
Sidis Kilo_ASG_B Addis Ketema_ASG_A
BSC RNC
-22-
Figure 4- 5 Microwave Site
Microwave_CR_A Microwave_CR_B
Microwave_FW_PS_A Microwave_FW_PS_B Microwave_SW_CS_A Microwave_SW_CS_B
M6000
Microwave_ER_HW_A Microwave_ER_HW_B NE40E-X8
CX600-X16
S9300
To E8000E
Addis Ketema_ASG_B
BSC
Microwave_SW_PS_A Microwave_SW_PS_B
RNC
Microwave_RSG_A Microwave_RSG_B
GE
10GE
To To 40GE
Filowoha_ASG_B Old Airport_ASG_A
BSC RNC
Figure 4- 6 Bole Site
Bole_CR_A Bole_CR_B
M6000
NE40E-X8
CX600-X16
Bole_ER_HW_A Bole_ER_HW_B S9300
E8000E
To
Yeka_ASG_A BSC
RNC
Bole_SW_CS_A Bole_SW_CS_B
Bole_RSG_A Bole_RSG_B GE
10GE
To To 40GE
Nifas Silk_RSG_B Filowoha_ASG_A
BSC RNC
-23-
Figure 4- 7 Kirkos Site
Arada_CR_A Arada_CR_B
Kirkos_FW_PS_A Kirkos_FW_PS_B
M6000
NE40E-X8
CX600-X16
S9300
E8000E
Kirkos_ER_HW_A Kirkos_ER_HW_B
BSC
RNC
Kirkos_SW_PS_A Kirkos_SW_PS_B Kirkos_SW_CS_A Kirkos_SW_CS_B
Kirkos_RSG_A Kirkos_RSG_B GE
10GE
To To 40GE
Old Airport_ASG_B Nifas Silk_RSG_A
BSC RNC
Figure 4- 8 Nifas Silk Site
Nifas Silk_ER_Data_A Nifas Silk_ER_Data_B

Nifas Silk_FW_PS_A Nifas Silk_FW_PS_B Nifas Silk_SW_CS_A Nifas Silk_SW_CS_B
M6000
NE40E-X8
Nifas Silk_ER_HW_A Nifas Silk_ER_HW_B
CX600-X16
S9300
E8000E
BSC
Nifas Silk_SW_PS_A Nifas Silk_SW_PS_B RNC
GE
Nifas Silk_RSG_A Nifas Silk_RSG_B 10GE
To 40GE
Bole Micheal_ASG_A
To To To
Hanna Mariam_ASG_B Kirkos_RSG_B Bole_RSG_A
BSC RNC
-24-
5 Product and Naming
5.1 Product Detail(Hardware)

5.1.1 CX600 Product
The CX600 Multi Services Platform (CX600) is designed with the routing platform to provide solutions
for the carrier-class Fixed-Mobile Convergence (FMC) network. The solutions provided by the CX600
cover the areas of access, convergence and transmission. CX600s, in general, are deployed at the
convergence and core layers of the carrier-class network.
Based on distributed hardware forwarding and non-blocking switching technologies, the CX600 features
carrier-class reliability, line speed forwarding capability, a well-designed Quality of Service (QoS)
mechanism, strong service-processing capability, and excellent expansibility. In addition to providing
competitive Layer 2 services, including Ethernet access and convergence, Ethernet switching, and
transmission of Ethernet over Multi-Protocol Label Switching (EoMPLS) services, the CX600 provides
diverse Layer 3 (IP) services, such as Internet broadband services, triple play (video, voice, and data)
services for individual users as well as IP leased line and IP Virtual Private Network (VPN) services for
enterprise users. Based on enhanced video features including fast channel change (FCC), retransmission
request (RET) and inline Real-time Stream Monitoring the CX600 can improve user experience in the
IPTV service.
The CX600 boasts a complete platform series, from the mini CX600-X1/X2 to the CX600-X8/X16
platform. The entire CX600 family series is shown below:
CX600 Series Family
-25-
Figure 5- 1 CX600 Series Family
5.1.2 NE40E Product

The NetEngine40E series universal service router (NE40E) is a high-end network product provided by
Huawei Technologies Co., Ltd. NE40Es are usually deployed at the edges of Internet Protocol (IP)
backbone networks, IP Metropolitan Area Networks (MANs), and other large-scale IP networks. The
NE40E and NE5000E together provide a complete, layered IP network solution.
The NE40E can be flexibly deployed at the edge or core of IP or MPLS networks, simplifying network
structure. With its ability to provide an extensive range of services and reliable service quality, the NE40E
is driving IP and MPLS bearer networks to develop greater broadband capacity and to become more
secure, more intelligent, and more service-oriented. Based on distributed hardware forwarding and
non-blocking switching technologies, the NE40E features line-rate forwarding capability, a well designed
Quality of Service (QoS) mechanism, strong service-processing capability, and excellent expansibility.
The NE40E is based on a 400G platform and provides 100G line cards to satisfy the increased demand
for bandwidth. Compatible with all line cards currently in use, the NE40E minimizes investment needs.
-26-
Figure 5- 2 NE40E Series Family
High GE/10GE
density 32U
Abundant legacy
interface
Powerful L2&L3 14U
function
LTE Ready 5U
First 300mm Depth
UPE Router
4U
3U
FMC Service
NE40E-X16 NE40E-X8 NE40E-X3 NE40E-X2/X1
Backplane 30T 15T 1.35T 450G/285G
Switching Capacity 12.58T 7.08T 1.08T 40G/20G
Throughput 3200Mpps 1600Mpps 300Mpps 60Mpps/30Mpps
5.1.3 ATN950B Product

The ATN series are case-shaped products used for multi-service access on the edge. The ATN series
together with the CX600 series can be used to build route-based network that support end-to-end FMC
bearing. Taking the challenges faced by carriers with respect to resources, cost, and services at the access
layer during the evolvement of mobile networks, the ATN series, which adhere to Huawei's "Any Media"
conception, provide sustainable IP RAN solutions to 2G, 3G, and Long Term Evolution (LTE)
applications.
ATN 950B is the Industry‘s first 2U high 10GE LTE CSR. ATN 950B series features in multi-service
transport, high-precision clock synchronization, and multi-media access though copper, fiber, ET. The
product series is only 300mm deep, 2U high design, supporting Co-Cabinet with the BTS/eNBs and
saving valuable site resources.
Figure 5- 3 ATN Frame
5.1.4 S9300 Product

The S9300&S9300E are mainly used to access, aggregate, and transmit services across a MAN. As an
access and aggregation switch, the S9300&S9300E provide line-speed Fast Ethernet (FE), Gigabit
-27-
Ethernet (GE), 10GE, and 40GE interfaces. The S9300&S9300E can be deployed in enterprise networks
and data centers, providing high-density interfaces and rich value-added service (VAS) capabilities.
The S9300&S9300E come in three different models: S9303, S9306, S9312 and S9303E, S9306E, and
S9312E. The S9303 or S9303E supports a maximum of three line processing units (LPUs); the S9306 or
S9306E supports a maximum of six LPUs; the S9312 or S9312E supports a maximum of 12 LPUs.
The S9300&S9300E use Huawei's Versatile Routing Platform (VRP) operating system and
hardware-based forwarding and non-blocking data switching technology. The S9300&S9300E feature
carrier-class reliability, line-speed forwarding capability, Quality of Service (QoS), service processing
capabilities, and scalability. The S9300 provides rich value-added service features, including firewall,
Network Address Translation (NAT), network traffic analysis, IPSec VPN, load balancing, and WLAN
AC.
Figure 5- 4 S9300 Frame
5.1.5 Summary Hardware description for products

Item CX600-X16 CX600-X8/NE40E-X8 ATN950B S9306 S9303
CPU 1.5 GHz 1.5 GHz CXP 700MHz 500MHz
SDRAM 2 GB 2 GB 1 GB 1GB 512 MB
NVRAM 4 MB 4 MB - 512 KB 512 KB
Flash 32 MB 32 MB 128 MB 64MB 64 MB
CF card 4 GB 4 GB 512 GB 512 GB 512 GB
Forwarding rate 7.68T 3.84 T 56Gbit/s 6T 3T
Power module -48V DC -48V DC -48V DC -48V/-60V DC -48V/-60V DC
90V/275V AC 90V/275V AC 90V/275V AC 110V/220V AC 110V/220V AC
-28-
LPU slots 16 8 6 6 3
MPU slots 2 2 2 2 2
SFU slots 4 1 - - -
Interface Type 100/1000Base-X-SFP 100/1000Base-RJ45 10/100BASE-T RJ45
10/100/1000Base-RJ45 100/1000Base-X-SFP 100/1000BASE-X SFP
10GBase LAN/WAN-SFP+ 10GBase 10/100/1000BASE-T RJ45
10GBase LAN/WAN-XFP LAN/WAN-XFP 10GBASE-X SFP+
10GBase LAN-SFP+ STM-1 10GBASE-X XFP
40GBase LAN-CFP E1 100BASE-FX SFP
100GBase CFP
5.2 Product Detail(Software)

Product Name Product Version Feature List
ATN 950B ATN950B IP Multicast:PIM/IGMP/Layer 2 Multicast/MSDP/MLD
V200R002C00 IP Services:IP Addressing/DNS/ACL/IPv4/IPv6/Load Balancing
IP Routing:Static Routes/RIP/RIPng/IS-IS/OSPF/OSPFv3/BGP
MPLS:MPLS/MPLS LDP/MPLS TE
VPN:BGPMPLSIPVPN/GRE/VLL/PWE3/VPLS/CES/ATMIWF/
LAN Access and MAN Access:Ethernet/VLAN/Trunk/STP RSTP
MSTP/QinQ/RRPP
System Management:DCN/Information Center/SNMP/RMON and
RMON2/NTP
CX CX600 IP Multicast:PIM/IGMP/Layer 2 Multicast/MSDP/MLD
600-X8/X16 V600R006C00 IP Services:IP Addressing/DNS/ACL/IPv4/IPv6/Load Balancing
MSTP/QinQ/RRPP
RMON2/NTP
WAN Access:ATM IMA/Frame Relay/HDLC and IP-Trunk/PPP and
MP/1483B/E1 BER Measurement/ATM
-29-
NE40E-X8 NE40E&80E IP Multicast:PIM/IGMP/Layer 2 Multicast/MSDP/MLD

V600R006C00 IP Services:IP Addressing/DNS/ACL/IPv4/IPv6/Load Balancing
MSTP/QinQ/RRPP
RMON2/NTP
WAN Access:ATM IMA/Frame Relay/HDLC and IP-Trunk/PPP and
MP/1483B/E1 BER Measurement/ATM
S9303/S9306 S9300 Ethernet:Ethernet/VLAN/MAC/ARP/Smart Link/DLDP/LLDP/Virtual cable
V200R001 test
Protection against Ethernet loops:MSTP/RRPP/Loop detection
IP routing:IPv4 unicast/IPv6 unicast
Multicast:IGMP, MLD, MSDP, PIM-DM, PIMSM,and PIM-SSM.
MPLS:Basic MPLS functions/MPLS OAM/MPLS-TE/VLL/HVPLS
OAM:Ethernet OAM,BFD
QoS:Traffic classification/Traffic behavior/Queue scheduling/Congestion
avoidance/Traffic shaping/Traffic policing
Enterprise network:NAC,Firewall,NAT,Load balancing,IPSec VPN,WLAN AC
5.3 Product Hardware Configuration

5.3.1 CX600 Product
Table 5- 1 CX600 Board Type
Equipment Flexible Board Card Type Interface Interface Type

LPUF-51 CR5D0EFGFA70 24*GE SFP
LPUI-101 CR5D0LAXFA71 10*10GE SFP
CX600-X16
LPUI-101 CR5D00E2MC70 2*40GE CFP
LPUF-50 CR52-P21-40x100/1000Base-X-SFP 24*E1 DB100
LPUI-51 CR5D0L5XFA71 5*10GE SFP
LPUI-51 CR5DL2XEFG7B 2*10GE+24*GE SFP
CX600-X8 LPUI-101 CR5D0LAXFA71 10*10GE SFP
LPUI-101 CR5D00E2MC70 2*40GE CFP
LPUF-50 CR52-P21-40x100/1000Base-X-SFP 24*E1 DB100
Typical layout for CX600-X8 and CX600-X16 is show in below figure
-30-
Upper air intake vent
GE 40GE 10GE 40GE

2
0 0 1 0
C
R
5
D
0
C C 2 3
- E X X
F 4
GC
FR
6 6
A5
7
D D
0D
L
0 0
0
2-0 M M
P
1 22 U
F
40GE3 P
17 P
18 4 5 10GE6 40GE7
5 0
U U 0 1 0
1
7
B B
0 C
4 4 2 3 C C
-
R
5
1 1 R
5
R
5
D
0
0 0 4
D
0
D
0
0 L 0
E A E
2 X 2
M F M
C A C
1 7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough

C 19 CX6DSFUI401B
19
R
5
3 Air intake vent CX6DSFUI401B
P
- 20 20
1
0
-
E1 2
14 1 GE
2 40GE 40GE 40GE 10GE 21 CX6DSFUI401B
21
x
c 0 0 0 0 1
E
1
C
R 22 CX6DSFUI401B
22
/ 5
c D C C C 2 3
- T1 - - E0 X X X Lower cable trough

- F
D
B
C
R
GC
FR
6 6 6 4
10GE 10GE
1
0
5 A5
7
D D D
0 D
L
0D
L
0 S 0 0 1 0 1
2 0 P
1-2 0 P
2-0 S F S
U
1 11 F 22 UF 40GE3 40GE4 R
9 U
11 R
10 5 6 40GE7 10GE 8 2 3 2 3
5 5 0 0
U I U 0 0 1
0
7
1
7
A 4 A 4 4
0 0 C
R
C
R
4 0 4 C
R
2 3 C
R
- - - 5
D
5
D
1 1 1 5
D
5
D
0
0
0
0
0 C 0 0
0
4 0
L
E E E A
2
M
2
M
2
M
X
F
10GE8 9 10 11 12 13 10GE14 15 16
C C C A 0 1 0 1
3 1 1 7 7 7 7
0 0 0 1
1 2 3 4 9 11 10 7 8 2 3 C 2 3 C
R R
5 5
D D
4 0 4 0
Cable trough L
A
X
L
A
X
F F
A A
7 7
1 1
8 14
Lower air intake vent
5.3.2 NE40E Product

Table 5- 2 NE40E Board Type
Equipment Board Card Type Interface Interface Type
LPUI-101 CR5D0LAXFA71 10*10GE SFP

NE40E-X8
LPUF-21 CR52-P21-40x100/1000Base-X-SFP 40*GE SFP
Typical layout for NE40E is show in below figure
NE40E-X8
1 2 3 4 9 11 10 5 6 7 8
0 1
2 3 0 0 0
4 5
1 1 1
6 7
8 9 2 2 2
10 11
12 13
3 3 3
14 15
16 17
4 4 4
18 19
20 21 SRU SFU SRU
22 23 0 0 0
24 25
26 27 1 1 1
28 29
30 31 2 2 2
32 33
34 35 3 3 3
36 37
4 4 4
38 39
c
-31-
5.3.3 ATN950B Product

Table 5- 3 ATN950B Board Type
Equipment Card Type Interface Interface Type
ANDD000EX100 10GE XFP
ATN950B ANDD00EM8F00 8*GE SFP/RJ45
ANDD16E17502 16*E1 DB100
Typical layout for ATN950B is show in below figure
ATN950B
ANDD00CXPB01 ANDD00CXPB01
ATN950B | 290E
7 7 8 8
P
I ANDD000EX100 ANDD000EX100
U 5 5 6 6
10GE
10GE
F 0 0
A
N 3 4
P
I ANDD00EM8F00 ANDD16E17502
U 1 0 2 1 4 6 2 0 2 4 2 6 8 10 12 14
GE
E1
1 3 5 7 1 3 5 7 9 11 13 15
5.3.4 S9300 Product

Table 5- 4 S9303 Board Type
LE0DG48TFA00 48*GE RJ45
S9303 LE0DG48SFA00 48*GE SFP
LE0DX16SFC00 16*10G SFP+
Table 5- 5 S9306 Board Type
LE0MG48SC 48*GE SFP

S9306
LE0DX16SFC00 16*10GE SFP
Typical layout for S9303 and S9306 are show in below figure
-32-
S9303
46 44 42 40 38 36 34 32 30 28 26 24 22 20 18 16 14 12 10 8 6 4 2 0
3 47 45 43 41 39 37 35 33 31 29 27 25 23 21 19 17 15 13 11 9 7 5 3 1
46 44 42 40 38 36 34 32 30 28 26 24 22 20 18 16 14 12 10 8 6 4 2 0
2 47 45 43 41 39 37 35 33 31 29 27 25 23 21 19 17 15 13 11 9 7 5 3 1
14 12 10 8 6 4 2 0
1 15 13 11 9 16x10Ge 7 5 3 1
MCU MCU
POWER MODULE POWER MODULE POE
S9306
46 44 42 40 38 36 34 32 30 28 26 24 22 20 18 16 14 12 10 8 6 4 2 0
6 47 45 43 41 39 37 35 33 31 29 27 25 23 21 19 17 15 13 11 9 7 5 3 1
14 12 10 8 6 4 2 0
4 15 13 11 9 16x10Ge 7 5 3 1
8 SRU
7 SRU
14 12 10 8 6 4 2 0
3 15 13 11 9 16x10Ge 7 5 3 1
46 44 42 40 38 36 34 32 30 28 26 24 22 20 18 16 14 12 10 8 6 4 2 0
1 47 45 43 41 39 37 35 33 31 29 27 25 23 21 19 17 15 13 11 9 7 5 3 1
5.4 Equipment Naming

5.4.1 Equipment Naming Conventions
Equipment Name adopts the convention as follow.
General Naming formulation is as following: for all NE naming only different on part “NEName”, other
part must be the same as “.Vendor.Village.City.Region”
“NE Name “for IP Equipment site:
 NE Name: Site ID_X_Y_R_P
 “X” is to identify the product type in one site Location ,example: CX,AT,NE,LW,W
-33-
 “Y” is to identify the number if there are more than one equipment
 “R” indicate role of this NE, for example: CSG,ASG,RSG
 “P” indicate NE plane, A plane olr B plane
 Example: 111006_CX_01_RSG_A.HW.BOLE.CAA.AA
Site
SiteName Latitude Longitute DeviceName
ID
111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA
11105 111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA
Microwave 9.018475 38.747067
1 111051_NE_01_RSG_A.HW.Microwave.CAAZ.AA
111051_NE_02_RSG_B.HW.Microwave.CAAZ.AA
111136_CX_01_RSG_A.HW.Bole.EAAZ.AA
11113 111136_CX_02_RSG_B.HW.Bole.EAAZ.AA
Bole 8.999854 38.784662
6 111136_NE_01_RSG_A.HW.Bole.EAAZ.AA
111136_NE_02_RSG_B.HW.Bole.EAAZ.AA
111055_CX_01_RSG_A.HW.Arada.NAAZ.AA
11105 111055_CX_02_RSG_B.HW.Arada.NAAZ.AA
Arada 9.03325 38.75031
5 111055_NE_01_RSG_A.HW.Arada.NAAZ.AA
111055_NE_02_RSG_B.HW.Arada.NAAZ.AA
111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA
11100 111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA
NifasSilk 8.963958 38.762735
7 111007_NE_01_RSG_A.HW.NifasSilk.SAAZ.AA
111007_NE_02_RSG_B.HW.NifasSilk.SAAZ.AA
111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA
11116 111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA
Kirkos 8.994036 38.753809
8 111168_NE_01_RSG_A.HW.Kirkos.SAAZ.AA
111168_NE_02_RSG_B.HW.Kirkos.SAAZ.AA
11105 111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA
Filowaha 9.013441 38.753355
8 111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA
11101 111010_CX_01_ASG_A.HW.BoleMchael.EAAZ.AA
BoleMchael 8.98065 38.77559
0 111010_CX_02_ASG_B.HW.BoleMchael.EAAZ.AA
11108 111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA
Yeka 9.01979 38.81979
2 111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA
11108 111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA
Kotebe 9.02262 38.85366
6 111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA
11108 111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA
Gerji 8.99399 38.81289
9 111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA
11116 111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA
AyatMeronia 9.02197 38.87414
5 111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA
11103 AddisuGebeya 9.058421 38.734723 111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA
-34-
8 111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA
11114 111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA
SidistKilo 9.04202 38.76663
8 111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA
111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.
11116 AA
Ferensailegasion 9.054265 38.778317
1 111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.
AA
111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.A
11112
HannaMariam 8.945814 38.747414 A
0
111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA
11122 111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA
Lebu 8.94401 38.73421
8 111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA
11140 111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA
Akaki 8.867261 38.789313
8 111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA
11176 111767_CX_01_ASG_A.HW.Kality.SAAZ.AA
Kality 8.932093 38.762553
7 111767_CX_02_ASG_B.HW.Kality.SAAZ.AA
11112 111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA
OldAirport 8.99781 38.7314
8 111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA
11117 111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA
Karanyo 9.007087 38.702855
6 111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA
11120 111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA
Mekanisa 8.969952 38.731072
5 111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA
11103 111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA
Kolfe 9.04001 38.71341
0 111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA
11105 111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA
AddisKetema 9.034465 38.732936
7 111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA
11112 111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA
Shegole 9.06277 38.71949
4 111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA
11116 111163_CX_01_ASG_A.HW.Asko.WAAZ.AA
284E(Asko) 9.06435 38.69815
3 111163_CX_02_ASG_B.HW.Asko.WAAZ.AA
11700 117001_CX_01_ASG_A.HW.Burau.WAAZ.AA
Burau 9.07737 38.67181
1 117001_CX_02_ASG_B.HW.Burau.WAAZ.AA
11104
185D 9.01935 38.73993 111040_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA
0
11104
2
11104
3
11110
81N 9.01349 38.74423 111109_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA
9
11120
2
-35-
11127
3
11139
3
11139
NationalHotel 9.01289 38.76247 111396_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA
6
11140 TesfayeMulatRealSta
9.01888 38.76802 111401_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA
1 te
11140
5
11141
8
11140
75N 9.01707 38.89541 111407_ATN_01_CSG_A.HW.Ayat.EAAZ.AA
7
11119
041D 9.00234 38.77863 111192_ATN_01_CSG_A.HW.Bole.EAAZ.AA
2
11106
15N 9.00809 38.78028 111064_ATN_01_CSG_A.HW.Bole.EAAZ.AA
4
11106
5
11107
4
11110
5
11127
7
11139
7
11140
6
11142
1
11100
6
11139 111399_ATN_01_CSG_A.HW.Bole
82N 8.97698 38.77558
9 Michael.EAAZ.AA
11109
307N 8.99775 38.80545 111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA
5
11112
290E 8.98901 38.81587 111125_ATN_01_CSG_A.HW.Gerji.EAAZ.AA
5
11116 BoleCommunityScho
8.98858 38.79953 111164_ATN_01_CSG_A.HW.Gerji.EAAZ.AA
4 ol
11139 73N 9.03859 38.83623 111398_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA
-36-
8
11140
297E 8.99663 38.84747 111400_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA
0
11109
3
11109
308N 9.03181 38.8424 111096_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA
6
11109
7
11110
1
11110
2
11110
3
11111
9
11116
2
11116
6
11123
0
11140 38.8641111
298E 9.01228 111409_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA
9 1
11108
279E 9.02281 38.80266 111083_ATN_01_CSG_A.HW.Yeka.EAAZ.AA
3
11108
4
11108
5
11108
7
11108
8
11109
0
11109
1
11109
2
11109
306N 9.0318 38.82083 111094_ATN_01_CSG_A.HW.Yeka.EAAZ.AA
4
-37-
11109
8
11109
9
11110
0
11110
6
11110
7
11127
9
11100
10 9.04442 38.74143 111004_ATN_01_CSG_A.HW.Arada.NAAZ.AA
4
11106
34N 9.05525 38.73888 111068_ATN_01_CSG_A.HW.Arada.NAAZ.AA
8
11106
9
11107
5
11111
8
11127
4
11142
0
11130
23N 9.06329 38.77715 111300_ATN_01_CSG_A.HW.Ferinas.NAAZ.AA
0
11107
60N 9.07112 38.73748 111079_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA
9
11106
05N 9.06596 38.74393 111060_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA
0
11127
12 9.04382 38.75874 111278_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA
8
11120
24N 9.0496 38.76464 111204_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA
4
11106
6
11104
201 9.03695 38.76602 111046_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA
6
11106
1
11107 53N 9.04225 38.77457 111076_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA
-38-
6
11110
8
11120
7
11140
2
11103
122_D 8.88319 38.78292 111034_ATN_01_CSG_A.HW.Akaki.SAAZ.AA
4
11121
317N 8.9582 38.70715 111211_ATN_01_CSG_A.HW.Lebu.SAAZ.AA
1
11121
71N 8.95217 38.72237 111212_ATN_01_CSG_A.HW.Lebu.SAAZ.AA
2
11115 111156_ATN_01_CSG_A.HW.HannaMariam.SAAZ.A
30N 8.9558 38.74204
6 A
11117 111173_ATN_01_CSG_A.HW.HannaMariam.SAAZ.A
85N 8.94883 38.75321
3 A
11115
33N 8.93128 38.75404 111157_ATN_01_CSG_A.HW.Kality.SAAZ.AA
7
11107
2
11107
3
11119
125_D 8.92635 38.76317 111196_ATN_01_CSG_A.HW.Kality.SAAZ.AA
6
11107
56N 8.9966 38.76015 111077_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA
7
11141
49N 8.98879 38.75315 111417_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA
7
11107
37N 8.9483 38.76512 111070_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA
0
11107
1
11111
126_D 8.95654 38.76846 111115_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA
5
11112
3
11118
80N 8.98945 38.68573 111184_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA
4
11118
6
11122
7
-39-
11130
2
11143
145D 8.98076 38.69439 111430_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA
0
11143
3
11116
43N 9.00096 38.68864 111169_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA
9
11117
1
11118
9
11121
4
11122
141D 8.99894 38.69567 111223_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA
3
11142
7
11112 111122_ATN_01_CSG_A.HW.Mekanism.SWAAZ.A
29N 8.97187 38.71365
2 A
65N 8.97426 38.72478
3 A
77N 8.98522 38.70844
5 A
11112 111121_ATN_01_CSG_A.HW.OldAirport.SWAAZ.A
53D 8.98901 38.73303
1 A
44N 8.97684 38.73177
2 A
62N 8.98835 38.7184
0 A
38N 9.01434 38.71217
3 A
61N 8.98371 38.73813
6 A
63N 9.0162 38.72175
9 A
11106
25N 9.06836 38.68433 111067_ATN_01_CSG_A.HW.Asko.WAAZ.AA
7
11104
286E 9.06514 38.70377 111048_ATN_01_CSG_A.HW.Asko.WAAZ.AA
8
11106
08N 9.05676 38.69577 111062_ATN_01_CSG_A.HW.Asko.WAAZ.AA
2
11106 10N 9.05218 38.6998 111063_ATN_01_CSG_A.HW.Asko.WAAZ.AA
-40-
3
11100
004_D 9.03244 38.72548 111001_ATN_01_CSG_A.HW.Ketema.WAAZ.AA
1
11104
1
11108
67N 9.04564 38.73601 111080_ATN_01_CSG_A.HW.Ketema.WAAZ.AA
0
11108
1
11113
1
11115
9
11139
Medenabuilding 9.03309 38.74178 111391_ATN_01_CSG_A.HW.Ketema.WAAZ.AA
1
11140
4
11118
175 9.02786 38.714 111182_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA
2
11115
137_D 9.04536 38.71181 111153_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA
3
11115
42N 9.05232 38.71242 111158_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA
8
11116
0
11123
1
11139
4
11107
57N 9.06097 38.72649 111078_ATN_01_CSG_A.HW.Shegole.WAAZ.AA
8
11127
136 9.05372 38.72007 111276_ATN_01_CSG_A.HW.Shegole.WAAZ.AA
6
5.5 Interface Description

5.5.1 Interface Naming Conventions
Interface Name adopts the convention as follow.
[NE Name].[Vendor].[Village].[City].[Region]-[Interface Type][Slot No.]/[Card No.]/ [Port No.]
-41-
For example:
111006_CX_01_RSG_A.HW.BOLE.CAA.AA-40GE10/2/0
5.5.2 Interface Description Conventions

Interface description adopts the convention as follow.
To [NE Name].[Vendor].[Village].[City].[Region]-[Interface Type][Slot No.]/[Card No.]/ [Port No.]
For example:
To 111006_CX_01_RSG_A.HW.BOLE.CAA.AA-40GE10/2/0
Equipment Port Description

111007_CX_01_RSG_A.HW.NifasSilk. To_111071_ATN_01_CSG_A.HW.NifasSilk.SAA
XGE8/0/2
SAAZ.AA Z.AA_XGE0/5/0
111007_CX_01_RSG_A.HW.NifasSilk. To_111120_CX_02_ASG_B.HW.HannaMariam.S
XGE8/0/0
SAAZ.AA AAZ.AA_XGE8/0/0
111007_CX_01_RSG_A.HW.NifasSilk. To_111120_CX_02_ASG_B.HW.HannaMariam.S
XGE8/0/1
SAAZ.AA AAZ.AA_XGE8/0/1
111007_CX_02_RSG_B.HW.NifasSilk.S To_111010_CX_01_ASG_A.HW.BoleMichael.EA
XGE8/0/1
AAZ.AA AZ.AA_XGE8/0/0
111007_CX_02_RSG_B.HW.NifasSilk.S To_111010_CX_01_ASG_A.HW.BoleMichael.EA
XGE8/0/0
AAZ.AA AZ.AA_XGE8/0/1
111010_CX_01_ASG_A.HW.BoleMicha To_111399_ATN_01_CSG_A.HW.BoleMichael.E
XGE8/0/2
el.EAAZ.AA AAZ.AA_XGE0/5/0
111010_CX_02_ASG_B.HW.BoleMicha To_111010_CX_01_ASG_A.HW.BoleMichael.EA
XGE2/0/0
el.EAAZ.AA AZ.AA_XGE2/0/0
111010_CX_02_ASG_B.HW.BoleMicha To_111010_CX_01_ASG_A.HW.BoleMichael.EA
XGE2/0/1
111030_CX_01_ASG_A.HW.Kolfe.WA To_111158_ATN_01_CSG_A.HW.Kolfe.WAAZ.
XGE8/0/2
AZ.AA AA_XGE0/5/0
111030_CX_01_ASG_A.HW.Kolfe.WA To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.
XGE8/0/0
AZ.AA AA_XGE8/0/0
111030_CX_01_ASG_A.HW.Kolfe.WA To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.
XGE8/0/1
AZ.AA AA_XGE8/0/1
111030_CX_02_ASG_B.HW.Kolfe.WA To_111231_ATN_01_CSG_A.HW.Kolfe.WAAZ.
XGE8/0/3
AZ.AA AA_XGE0/5/0
111030_CX_02_ASG_B.HW.Kolfe.WA To_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111030_CX_02_ASG_B.HW.Kolfe.WA To_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
111038_CX_01_ASG_A.HW.Gebeya.N XGE8/0/2 To_111060_ATN_01_CSG_A.HW.Gebeya.NAAZ
-42-
AAZ.AA .AA_XGE0/5/0
111038_CX_01_ASG_A.HW.Gebeya.N To_111079_ATN_01_CSG_A.HW.Gebeya.NAAZ
XGE8/0/3
AAZ.AA .AA_XGE0/5/0
111038_CX_01_ASG_A.HW.Gebeya.N To_111055_CX_02_RSG_B.HW.Arada.NAAZ.A
XGE8/0/0
AAZ.AA A_XGE8/0/0
111038_CX_01_ASG_A.HW.Gebeya.N To_111055_CX_02_RSG_B.HW.Arada.NAAZ.A
XGE8/0/1
AAZ.AA A_XGE8/0/1
111038_CX_02_ASG_B.HW.Gebeya.N To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.
XGE2/0/0
AAZ.AA AA_XGE2/0/0
111038_CX_02_ASG_B.HW.Gebeya.N To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.
XGE2/0/1
AAZ.AA AA_XGE2/0/1
111040_ATN_01_CSG_A.HW.Filowoha To_111418_ATN_01_CSG_A.HW.Filowoha.CAA
XGE0/6/0
.CAAZ.AA Z.AA_XGE0/5/0
XGE0/6/0
111043_ATN_01_CSG_A.HW.Filowoha To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.
XGE0/6/0
.CAAZ.AA AA_XGE8/0/2
111046_ATN_01_CSG_A.HW.SidisKilo To_111066_ATN_01_CSG_A.HW.SidisKilo.NAA
XGE0/6/0
.NAAZ.AA Z.AA_XGE0/5/0
111048_ATN_01_CSG_A.HW.Asko.W To_111063_ATN_01_CSG_A.HW.Asko.WAAZ.
XGE0/6/0
AAZ.AA AA_XGE0/5/0
111055_CX_01_RSG_A.HW.Arada.NA To_111274_ATN_01_CSG_A.HW.Arada.NAAZ.
XGE8/0/2
AZ.AA AA_XGE0/5/0
111055_CX_01_RSG_A.HW.Arada.NA To_111161_CX_02_ASG_B.HW.Ferensailegasion.
XGE8/0/0
AZ.AA NAAZ.AA_XGE8/0/0
111055_CX_01_RSG_A.HW.Arada.NA To_111161_CX_02_ASG_B.HW.Ferensailegasion.
XGE8/0/1
AZ.AA NAAZ.AA_XGE8/0/1
111055_CX_02_RSG_B.HW.Arada.NA To_111004_ATN_01_CSG_A.HW.Arada.NAAZ.
XGE8/0/4
AZ.AA AA_XGE0/5/0
XGE8/0/3
AZ.AA AA_XGE0/5/0
111057_CX_01_ASG_A.HW.Ketema.W To_111041_ATN_01_CSG_A.HW.Ketema.WAA
XGE8/0/4
AAZ.AA Z.AA_XGE0/5/0
XGE8/0/3
XGE8/0/2
111057_CX_01_ASG_A.HW.Ketema.W To_111124_CX_02_ASG_B.HW.Shegole.WAAZ.
XGE8/0/0
AAZ.AA AA_XGE8/0/0
111057_CX_01_ASG_A.HW.Ketema.W To_111124_CX_02_ASG_B.HW.Shegole.WAAZ.
XGE8/0/1
AAZ.AA AA_XGE8/0/1
111057_CX_02_ASG_B.HW.Ketema.W To_111001_ATN_01_CSG_A.HW.Ketema.WAA
XGE8/0/4
-43-
XGE8/0/2
XGE8/0/3
111058_CX_01_ASG_A.HW.Filowaha. To_111273_ATN_01_CSG_A.HW.Filowoha.CAA
XGE8/0/2
CAAZ.AA Z.AA_XGE0/5/0
XGE8/0/1
XGE8/0/0
XGE0/6/0
111064_ATN_01_CSG_A.HW.Bole.EA To_111397_ATN_01_CSG_A.HW.Bole.EAAZ.A
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
111068_ATN_01_CSG_A.HW.Arada.N To_111075_ATN_01_CSG_A.HW.Arada.NAAZ.
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
111070_ATN_01_CSG_A.HW.NifasSilk To_111123_ATN_01_CSG_A.HW.NifasSilk.SAA
XGE0/6/0
.SAAZ.AA Z.AA_XGE0/5/0
XGE0/6/0
111072_ATN_01_CSG_A.HW.Kality.S To_111157_ATN_01_CSG_A.HW.Kality.SAAZ.
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
111075_ATN_01_CSG_A.HW.Arada.N To_111055_CX_02_RSG_B.HW.Arada.NAAZ.A
XGE0/6/0
AAZ.AA A_XGE8/0/2
111076_ATN_01_CSG_A.HW.SidisKilo To_111148_CX_02_ASG_B.HW.SidistKilo.NAA
XGE0/6/0
111082_CX_01_ASG_A.HW.Yeka.EAA To_111087_ATN_01_CSG_A.HW.Yeka.EAAZ.A
XGE8/0/2
Z.AA A_XGE0/5/0
XGE8/0/3
Z.AA A_XGE0/5/0
XGE8/0/4
Z.AA A_XGE0/5/0
111082_CX_01_ASG_A.HW.Yeka.EAA XGE8/0/0 To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA
-44-
Z.AA _XGE8/0/0
111082_CX_01_ASG_A.HW.Yeka.EAA To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA
XGE8/0/1
Z.AA _XGE8/0/1
111083_ATN_01_CSG_A.HW.Yeka.EA To_111085_ATN_01_CSG_A.HW.Yeka.EAAZ.A
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
111086_CX_01_ASG_A.HW.Kotebe.EA To_111103_ATN_01_CSG_A.HW.Kotebe.EAAZ.
XGE8/0/2
AZ.AA AA_XGE0/5/0
111086_CX_01_ASG_A.HW.Kotebe.EA To_111398_ATN_01_CSG_A.HW.Kotebe.EAAZ.
XGE8/0/3
AZ.AA AA_XGE0/5/0
111086_CX_01_ASG_A.HW.Kotebe.EA To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA
XGE8/0/0
AZ.AA _XGE8/0/0
111086_CX_01_ASG_A.HW.Kotebe.EA To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA
XGE8/0/1
AZ.AA _XGE8/0/1
111086_CX_02_ASG_B.HW.Kotebe.EA To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111086_CX_02_ASG_B.HW.Kotebe.EA To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
111089_CX_01_ASG_A.HW.Gerji.EAA To_111125_ATN_01_CSG_A.HW.Gerji.EAAZ.A
XGE8/0/2
Z.AA A_XGE0/5/0
111089_CX_01_ASG_A.HW.Gerji.EAA To_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA
XGE8/0/0
Z.AA _XGE8/0/0
111089_CX_01_ASG_A.HW.Gerji.EAA To_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA
XGE8/0/1
Z.AA _XGE8/0/1
111089_CX_02_ASG_B.HW.Gerji.EAA To_111095_ATN_01_CSG_A.HW.Gerji.EAAZ.A
XGE8/0/3
Z.AA A_XGE0/5/0
111089_CX_02_ASG_B.HW.Gerji.EAA To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA
XGE2/0/0
Z.AA _XGE2/0/0
111089_CX_02_ASG_B.HW.Gerji.EAA To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA
XGE2/0/1
Z.AA _XGE2/0/1
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
111093_ATN_01_CSG_A.HW.Kotebe.E To_111119_ATN_01_CSG_A.HW.Kotebe.EAAZ.
XGE0/6/0
AAZ.AA AA_XGE0/5/0
-45-
111094_ATN_01_CSG_A.HW.Yeka.EA To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA
XGE0/6/0
AZ.AA _XGE8/0/3
XGE0/6/0
AAZ.AA AA_XGE0/5/0
111097_ATN_01_CSG_A.HW.Kotebe.E To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.A
XGE0/6/0
AAZ.AA A_XGE8/0/3
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AZ.AA A_XGE0/5/0
111107_ATN_01_CSG_A.HW.Yeka.EA To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA
XGE0/6/0
AZ.AA _XGE8/0/2
XGE0/6/0
XGE0/6/0
XGE0/6/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
111120_CX_01_ASG_A.HW.HannaMar To_111173_ATN_01_CSG_A.HW.HannaMariam.
XGE8/0/2
iam.SAAZ.AA SAAZ.AA_XGE0/5/0
111120_CX_01_ASG_A.HW.HannaMar To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA
XGE8/0/0
iam.SAAZ.AA _XGE8/0/0
111120_CX_01_ASG_A.HW.HannaMar To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA
XGE8/0/1
iam.SAAZ.AA _XGE8/0/1
111120_CX_02_ASG_B.HW.HannaMari To_111156_ATN_01_CSG_A.HW.HannaMariam.
XGE8/0/2
am.SAAZ.AA SAAZ.AA_XGE0/5/0
111120_CX_02_ASG_B.HW.HannaMari XGE2/0/0 To_111120_CX_01_ASG_A.HW.HannaMariam.S
-46-
am.SAAZ.AA AAZ.AA_XGE2/0/0
111120_CX_02_ASG_B.HW.HannaMari To_111120_CX_01_ASG_A.HW.HannaMariam.S
XGE2/0/1
am.SAAZ.AA AAZ.AA_XGE2/0/1
111121_ATN_01_CSG_A.HW.OldAirpo To_111172_ATN_01_CSG_A.HW.OldAirport.SW
XGE0/6/0
rt.SWAAZ.AA AAZ.AA_XGE0/5/0
111122_ATN_01_CSG_A.HW.Mekanis To_111215_ATN_01_CSG_A.HW.Mekanism.SW
XGE0/6/0
m.SWAAZ.AA AAZ.AA_XGE0/5/0
111123_ATN_01_CSG_A.HW.NifasSilk To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.
XGE0/6/0
.SAAZ.AA AA_XGE8/0/2
111124_CX_01_ASG_A.HW.Shegole.W To_111276_ATN_01_CSG_A.HW.Shegole.WAA
XGE8/0/2
111124_CX_01_ASG_A.HW.Shegole.W To_111163_CX_02_ASG_B.HW.Asko.WAAZ.A
XGE8/0/0
AAZ.AA A_XGE8/0/0
111124_CX_01_ASG_A.HW.Shegole.W To_111163_CX_02_ASG_B.HW.Asko.WAAZ.A
XGE8/0/1
AAZ.AA A_XGE8/0/1
111124_CX_02_ASG_B.HW.Shegole.W To_111078_ATN_01_CSG_A.HW.Shegole.WAA
XGE8/0/2
111124_CX_02_ASG_B.HW.Shegole.W To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.
XGE2/0/0
AAZ.AA AA_XGE2/0/0
111124_CX_02_ASG_B.HW.Shegole.W To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.
XGE2/0/1
AAZ.AA AA_XGE2/0/1
111125_ATN_01_CSG_A.HW.Gerji.EA To_111164_ATN_01_CSG_A.HW.Gerji.EAAZ.A
XGE0/6/0
AZ.AA A_XGE0/5/0
111128_CX_01_ASG_A.HW.OldAirport To_111213_ATN_01_CSG_A.HW.OldAirport.SW
XGE8/0/3
.SWAAZ.AA AAZ.AA_XGE0/5/0
111128_CX_01_ASG_A.HW.OldAirport To_111216_ATN_01_CSG_A.HW.OldAirport.SW
XGE8/0/2
111128_CX_01_ASG_A.HW.OldAirport To_111176_CX_02_ASG_B.HW.Karanyo.SWAA
XGE8/0/0
.SWAAZ.AA Z.AA_XGE8/0/0
111128_CX_01_ASG_A.HW.OldAirport To_111176_CX_02_ASG_B.HW.Karanyo.SWAA
XGE8/0/1
.SWAAZ.AA Z.AA_XGE8/0/1
111131_ATN_01_CSG_A.HW.Ketema. To_111080_ATN_01_CSG_A.HW.Ketema.WAA
XGE0/6/0
WAAZ.AA Z.AA_XGE0/5/0
111136_CX_01_RSG_A.HW.Bole.EAA To_111065_ATN_01_CSG_A.HW.Bole.EAAZ.A
XGE8/0/1
Z.AA A_XGE0/5/0
111136_CX_01_RSG_A.HW.Bole.EAA To_111421_ATN_01_CSG_A.HW.Bole.EAAZ.A
XGE8/0/0
Z.AA A_XGE0/5/0
111136_CX_02_RSG_B.HW.Bole.EAA To_111277_ATN_01_CSG_A.HW.Bole.EAAZ.A
XGE8/0/1
Z.AA A_XGE0/5/0
111148_CX_01_ASG_A.HW.SidistKilo. To_111046_ATN_01_CSG_A.HW.SidisKilo.NAA
XGE8/0/1
NAAZ.AA Z.AA_XGE0/5/0
111148_CX_01_ASG_A.HW.SidistKilo. To_111204_ATN_01_CSG_A.HW.SidisKilo.NAA
XGE8/0/0
-47-
111148_CX_02_ASG_B.HW.SidistKilo. To_111207_ATN_01_CSG_A.HW.SidisKilo.NAA
XGE8/0/2
XGE8/0/3
111153_ATN_01_CSG_A.HW.Kolfe.W To_111394_ATN_01_CSG_A.HW.Kolfe.WAAZ.
XGE0/6/0
AAZ.AA AA_XGE0/5/0
111157_ATN_01_CSG_A.HW.Kality.S To_111767_CX_02_ASG_B.HW.Kality.SAAZ.A
XGE0/6/0
AAZ.AA A_XGE8/0/2
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
111161_CX_01_ASG_A.HW.Ferensaile To_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.
XGE8/0/0
gasion.NAAZ.AA AA_XGE8/0/0
111161_CX_01_ASG_A.HW.Ferensaile To_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.
XGE8/0/1
111161_CX_02_ASG_B.HW.Ferensaile To_111300_ATN_01_CSG_A.HW.Ferinas.NAAZ.
XGE8/0/2
111161_CX_02_ASG_B.HW.Ferensaile To_111161_CX_01_ASG_A.HW.Ferensailegasion
XGE2/0/0
gasion.NAAZ.AA .NAAZ.AA_XGE2/0/0
111161_CX_02_ASG_B.HW.Ferensaile To_111161_CX_01_ASG_A.HW.Ferensailegasion
XGE2/0/1
gasion.NAAZ.AA .NAAZ.AA_XGE2/0/1
XGE0/6/0
AAZ.AA AA_XGE0/5/0
111163_CX_01_ASG_A.HW.Asko.WA To_111048_ATN_01_CSG_A.HW.Asko.WAAZ.
XGE8/0/2
AZ.AA AA_XGE0/5/0
111163_CX_01_ASG_A.HW.Asko.WA To_117001_CX_02_ASG_B.HW.Burau.WAAZ.A
XGE8/0/0
AZ.AA A_XGE8/0/0
111163_CX_01_ASG_A.HW.Asko.WA To_117001_CX_02_ASG_B.HW.Burau.WAAZ.A
XGE8/0/1
AZ.AA A_XGE8/0/1
111163_CX_02_ASG_B.HW.Asko.WA To_111062_ATN_01_CSG_A.HW.Asko.WAAZ.
XGE8/0/3
AZ.AA AA_XGE0/5/0
111163_CX_02_ASG_B.HW.Asko.WA To_111062_ATN_01_CSG_A.HW.Asko.WAAZ.
XGE8/0/2
AZ.AA AA_XGE0/5/0
111163_CX_02_ASG_B.HW.Asko.WA To_111163_CX_01_ASG_A.HW.Asko.WAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111163_CX_02_ASG_B.HW.Asko.WA To_111163_CX_01_ASG_A.HW.Asko.WAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
111164_ATN_01_CSG_A.HW.Gerji.EAAZ. To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA
XGE0/6/0
AA _XGE8/0/2
111165_CX_01_ASG_A.HW.Ayat.EAA XGE8/0/2 To_111407_ATN_01_CSG_A.HW.Ayat.EAAZ.A
-48-
Z.AA A_XGE0/5/0
111165_CX_01_ASG_A.HW.Ayat.EAA To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.A
XGE8/0/0
Z.AA A_XGE8/0/0
111165_CX_01_ASG_A.HW.Ayat.EAA To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.A
XGE8/0/1
Z.AA A_XGE8/0/1
111165_CX_02_ASG_B.HW.Ayat.EAA To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA
XGE2/0/0
Z.AA _XGE2/0/0
111165_CX_02_ASG_B.HW.Ayat.EAA To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA
XGE2/0/1
Z.AA _XGE2/0/1
XGE0/6/0
AAZ.AA AA_XGE0/5/0
111168_CX_01_RSG_A.HW.Kirkos.SA To_111077_ATN_01_CSG_A.HW.Kirkos.SAAZ.
XGE8/0/0
AZ.AA AA_XGE0/5/0
111168_CX_02_RSG_B.HW.Kirkos.SA To_111417_ATN_01_CSG_A.HW.Kirkos.SAAZ.
XGE8/0/0
AZ.AA AA_XGE0/5/0
111171_ATN_01_CSG_A.HW.Keranio. To_111189_ATN_01_CSG_A.HW.Keranio.SWA
XGE0/6/0
SWAAZ.AA AZ.AA_XGE0/5/0
XGE0/6/0
111176_CX_01_ASG_A.HW.Karanyo.S To_111169_ATN_01_CSG_A.HW.Keranio.SWA
XGE8/0/3
WAAZ.AA AZ.AA_XGE0/5/0
111176_CX_01_ASG_A.HW.Karanyo.S To_111214_ATN_01_CSG_A.HW.Keranio.SWA
XGE8/0/2
111176_CX_01_ASG_A.HW.Karanyo.S To_111302_ATN_01_CSG_A.HW.AyerTena.SW
XGE8/0/4
WAAZ.AA AAZ.AA_XGE0/5/0
111176_CX_01_ASG_A.HW.Karanyo.S To_111205_CX_02_ASG_B.HW.Mekanisa.SWA
XGE8/0/0
111176_CX_01_ASG_A.HW.Karanyo.S To_111205_CX_02_ASG_B.HW.Mekanisa.SWA
XGE8/0/1
111176_CX_02_ASG_B.HW.Karanyo.S To_111176_CX_01_ASG_A.HW.Karanyo.SWAA
XGE2/0/0
111176_CX_02_ASG_B.HW.Karanyo.S To_111176_CX_01_ASG_A.HW.Karanyo.SWAA
XGE2/0/1
111183_ATN_01_CSG_A.HW.Mekanis To_111205_CX_02_ASG_B.HW.Mekanisa.SWA
XGE0/6/0
m.SWAAZ.AA AZ.AA_XGE8/0/2
111184_ATN_01_CSG_A.HW.AyerTen To_111205_CX_02_ASG_B.HW.Mekanisa.SWA
XGE0/6/0
a.SWAAZ.AA AZ.AA_XGE8/0/3
111186_ATN_01_CSG_A.HW.AyerTen To_111433_ATN_01_CSG_A.HW.AyerTena.SW
XGE0/6/0
a.SWAAZ.AA AAZ.AA_XGE0/5/0
XGE0/3/0
XGE0/6/0
-49-
111190_ATN_01_CSG_A.HW.OldAirpo To_111128_CX_02_ASG_B.HW.OldAirport.SWA
XGE0/6/0
rt.SWAAZ.AA AZ.AA_XGE8/0/2
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
XGE0/6/0
111205_CX_01_ASG_A.HW.Mekanisa. To_111122_ATN_01_CSG_A.HW.Mekanism.SW
XGE8/0/2
SWAAZ.AA AAZ.AA_XGE0/5/0
111205_CX_01_ASG_A.HW.Mekanisa. To_111430_ATN_01_CSG_A.HW.AyerTena.SW
XGE8/0/3
111205_CX_01_ASG_A.HW.Mekanisa. To_111128_CX_02_ASG_B.HW.OldAirport.SWA
XGE8/0/0
111205_CX_01_ASG_A.HW.Mekanisa. To_111128_CX_02_ASG_B.HW.OldAirport.SWA
XGE8/0/1
111205_CX_02_ASG_B.HW.Mekanisa. To_111205_CX_01_ASG_A.HW.Mekanisa.SWA
XGE2/0/0
111205_CX_02_ASG_B.HW.Mekanisa. To_111205_CX_01_ASG_A.HW.Mekanisa.SWA
XGE2/0/1
111211_ATN_01_CSG_A.HW.Lebu.SA To_111212_ATN_01_CSG_A.HW.Lebu.SAAZ.A
XGE0/6/0
AZ.AA A_XGE0/5/0
111212_ATN_01_CSG_A.HW.Lebu.SA To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA
XGE0/6/0
AZ.AA _XGE8/0/2
XGE0/6/0
XGE0/6/0
XGE0/6/0
XGE0/6/0
XGE0/6/0
111228_CX_01_ASG_A.HW.Lebu.SAA To_111211_ATN_01_CSG_A.HW.Lebu.SAAZ.A
XGE8/0/2
Z.AA A_XGE0/5/0
111228_CX_01_ASG_A.HW.Lebu.SAA To_111767_CX_02_ASG_B.HW.Kality.SAAZ.A
XGE8/0/0
Z.AA A_XGE8/0/0
111228_CX_01_ASG_A.HW.Lebu.SAA To_111767_CX_02_ASG_B.HW.Kality.SAAZ.A
XGE8/0/1
Z.AA A_XGE8/0/1
111228_CX_02_ASG_B.HW.Lebu.SAA XGE2/0/0 To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA
-50-
Z.AA _XGE2/0/0
111228_CX_02_ASG_B.HW.Lebu.SAA To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA
XGE2/0/1
Z.AA _XGE2/0/1
111230_ATN_01_CSG_A.HW.Kotebe.E To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.A
XGE0/6/0
AAZ.AA A_XGE8/0/2
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
XGE0/6/0
AZ.AA A_XGE0/5/0
XGE0/6/0
111394_ATN_01_CSG_A.HW.Kolfe.W To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.A
XGE0/6/0
AAZ.AA A_XGE8/0/2
111396_ATN_01_CSG_A.HW.Filowoha.CA To_111405_ATN_01_CSG_A.HW.Filowoha.CAA
XGE0/6/0
AZ.AA Z.AA_XGE0/5/0
111397_ATN_01_CSG_A.HW.Bole.EA To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_
XGE0/6/0
AZ.AA XGE8/0/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
XGE0/6/0
XGE0/6/0
AZ.AA A_XGE0/5/0
111408_CX_01_ASG_A.HW.Akaki.SA To_111010_CX_02_ASG_B.HW.BoleMichael.EA
XGE8/0/0
AZ.AA AZ.AA_XGE8/0/0
111408_CX_01_ASG_A.HW.Akaki.SA To_111010_CX_02_ASG_B.HW.BoleMichael.EA
XGE8/0/1
AZ.AA AZ.AA_XGE8/0/1
111408_CX_02_ASG_B.HW.Akaki.SA To_111034_ATN_01_CSG_A.HW.Akaki.SAAZ.A
XGE8/0/2
AZ.AA A_XGE0/5/0
111408_CX_02_ASG_B.HW.Akaki.SA To_111408_CX_01_ASG_A.HW.Akaki.SAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111408_CX_02_ASG_B.HW.Akaki.SA To_111408_CX_01_ASG_A.HW.Akaki.SAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
-51-
XGE0/6/0
AAZ.AA AA_XGE0/5/0
XGE0/6/0
111419_ATN_01_CSG_A.HW.OldAirpo To_111128_CX_02_ASG_B.HW.OldAirport.SWA
XGE0/6/0
XGE0/6/0
AZ.AA A_XGE0/5/0
111427_ATN_01_CSG_A.HW.Keranio. To_111176_CX_02_ASG_B.HW.Karanyo.SWAA
XGE0/6/0
SWAAZ.AA Z.AA_XGE8/0/2
XGE0/6/0
XGE0/6/0
111767_CX_01_ASG_A.HW.Kality.SA To_111196_ATN_01_CSG_A.HW.Kality.SAAZ.
XGE8/0/2
AZ.AA AA_XGE0/5/0
111767_CX_01_ASG_A.HW.Kality.SA To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.A
XGE8/0/0
AZ.AA A_XGE8/0/0
111767_CX_01_ASG_A.HW.Kality.SA To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.A
XGE8/0/1
AZ.AA A_XGE8/0/1
111767_CX_02_ASG_B.HW.Kality.SA To_111767_CX_01_ASG_A.HW.Kality.SAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111767_CX_02_ASG_B.HW.Kality.SA To_111767_CX_01_ASG_A.HW.Kality.SAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
117001_CX_01_ASG_A.HW.Burau.WA To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.A
XGE8/0/0
AZ.AA A_XGE8/0/0
117001_CX_01_ASG_A.HW.Burau.WA To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.A
XGE8/0/1
AZ.AA A_XGE8/0/1
117001_CX_02_ASG_B.HW.Burau.WA To_117001_CX_01_ASG_A.HW.Burau.WAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
117001_CX_02_ASG_B.HW.Burau.WA To_117001_CX_01_ASG_A.HW.Burau.WAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
111007_CX_01_RSG_A.HW.NifasSilk. 40GE3/0/ To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.
SAAZ.AA 0 AA_40GE3/0/0
111007_CX_01_RSG_A.HW.NifasSilk. 40GE3/2/ To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.
SAAZ.AA 0 AA_40GE3/2/0
111007_CX_02_RSG_B.HW.NifasSilk.S 40GE7/0/ To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA
AAZ.AA 0 _40GE7/0/0
111007_CX_02_RSG_B.HW.NifasSilk.S 40GE7/2/ To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA
AAZ.AA 0 _40GE7/2/0
111051_CX_01_RSG_A.HW.Microwave 40GE3/0/ To_111051_CX_02_RSG_B.HW.Microwave.CAA
.CAAZ.AA 0 Z.AA_40GE3/0/0
111051_CX_01_RSG_A.HW.Microwave 40GE3/2/ To_111051_CX_02_RSG_B.HW.Microwave.CAA
-52-
111051_CX_02_RSG_B.HW.Microwave 40GE7/2/ To_111128_CX_01_ASG_A.HW.OldAirport.SWA
.CAAZ.AA 0 AZ.AA_40GE7/2/0
111051_CX_02_RSG_B.HW.Microwave 40GE7/0/ To_111128_CX_01_ASG_A.HW.OldAirport.SWA
.CAAZ.AA 0 AZ.AA_40GE7/0/0
111055_CX_01_RSG_A.HW.Arada.NA 40GE7/0/ To_111055_CX_02_RSG_B.HW.Arada.NAAZ.A
AZ.AA 0 A_40GE7/0/0
111055_CX_02_RSG_B.HW.Arada.NA 40GE7/2/ To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.
AZ.AA 0 AA_40GE7/2/0
111057_CX_01_ASG_A.HW.Ketema.W 40GE7/0/ To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.
AAZ.AA 0 AA_40GE7/0/0
111057_CX_02_ASG_B.HW.Ketema.W 40GE7/2/ To_111051_CX_02_RSG_B.HW.Microwave.CAA
AAZ.AA 0 Z.AA_40GE10/2/0
111058_CX_01_ASG_A.HW.Filowaha. 40GE3/0/ To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.
CAAZ.AA 0 AA_40GE3/0/0
111058_CX_01_ASG_A.HW.Filowaha. 40GE3/2/ To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.
CAAZ.AA 0 AA_40GE3/2/0
111058_CX_02_ASG_B.HW.Filowaha. 40GE7/0/ To_111051_CX_01_RSG_A.HW.Microwave.CAA
CAAZ.AA 0 Z.AA_40GE7/0/0
111058_CX_02_ASG_B.HW.Filowaha. 40GE7/2/ To_111051_CX_01_RSG_A.HW.Microwave.CAA
CAAZ.AA 0 Z.AA_40GE7/2/0
111082_CX_01_ASG_A.HW.Yeka.EAA 40GE7/0/ To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA
Z.AA 0 _40GE7/0/0
111082_CX_02_ASG_B.HW.Yeka.EAA 40GE7/2/ To_111148_CX_01_ASG_A.HW.SidistKilo.NAA
Z.AA 0 Z.AA_40GE7/2/0
111128_CX_01_ASG_A.HW.OldAirport 40GE3/0/ To_111128_CX_02_ASG_B.HW.OldAirport.SWA
.SWAAZ.AA 0 AZ.AA_40GE3/0/0
111128_CX_01_ASG_A.HW.OldAirport 40GE3/2/ To_111128_CX_02_ASG_B.HW.OldAirport.SWA
111128_CX_02_ASG_B.HW.OldAirport 40GE7/0/ To_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.A
.SWAAZ.AA 0 A_40GE7/0/0
111128_CX_02_ASG_B.HW.OldAirport 40GE7/2/ To_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.A
.SWAAZ.AA 0 A_40GE7/2/0
111136_CX_01_RSG_A.HW.Bole.EAA 40GE3/0/ To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_
Z.AA 0 40GE3/0/0
111136_CX_01_RSG_A.HW.Bole.EAA 40GE3/2/ To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_
Z.AA 0 40GE3/2/0
111136_CX_01_RSG_A.HW.Bole.EAA 40GE10/2 To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA
Z.AA /0 _40GE7/2/0
111136_CX_02_RSG_B.HW.Bole.EAA 40GE7/0/ To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ
Z.AA 0 .AA_40GE7/0/0
111136_CX_02_RSG_B.HW.Bole.EAA 40GE7/2/ To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ
Z.AA 0 .AA_40GE7/2/0
-53-
111148_CX_01_ASG_A.HW.SidistKilo. 40GE7/0/ To_111148_CX_02_ASG_B.HW.SidistKilo.NAA

NAAZ.AA 0 Z.AA_40GE7/0/0
111148_CX_02_ASG_B.HW.SidistKilo. 40GE7/2/ To_111055_CX_01_RSG_A.HW.Arada.NAAZ.A
NAAZ.AA 0 A_40GE7/2/0
111168_CX_01_RSG_A.HW.Kirkos.SA 40GE3/0/ To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.A
AZ.AA 0 A_40GE3/0/0
111168_CX_01_RSG_A.HW.Kirkos.SA 40GE3/2/ To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.A
AZ.AA 0 A_40GE3/2/0
111168_CX_02_RSG_B.HW.Kirkos.SA 40GE7/0/ To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.
111168_CX_02_RSG_B.HW.Kirkos.SA 40GE7/2/ To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.
111071_ATN_01_CSG_A.HW.NifasSilk To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.
XGE0/5/0
.SAAZ.AA AA_XGE8/0/2
111120_CX_02_ASG_B.HW.HannaMari To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.
XGE8/0/0
am.SAAZ.AA AA_XGE8/0/0
111120_CX_02_ASG_B.HW.HannaMari To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.
XGE8/0/1
am.SAAZ.AA AA_XGE8/0/1
111010_CX_01_ASG_A.HW.BoleMicha To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.
XGE8/0/0
el.EAAZ.AA AA_XGE8/0/1
111010_CX_01_ASG_A.HW.BoleMicha To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.
XGE8/0/1
el.EAAZ.AA AA_XGE8/0/0
111399_ATN_01_CSG_A.HW.BoleMic To_111010_CX_01_ASG_A.HW.BoleMichael.EA
XGE0/5/0
hael.EAAZ.AA AZ.AA_XGE8/0/2
111010_CX_01_ASG_A.HW.BoleMicha To_111010_CX_02_ASG_B.HW.BoleMichael.EA
XGE2/0/0
111010_CX_01_ASG_A.HW.BoleMicha To_111010_CX_02_ASG_B.HW.BoleMichael.EA
XGE2/0/1
111158_ATN_01_CSG_A.HW.Kolfe.W To_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/2
111057_CX_02_ASG_B.HW.Ketema.W To_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.A
XGE8/0/0
AAZ.AA A_XGE8/0/0
111057_CX_02_ASG_B.HW.Ketema.W To_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.A
XGE8/0/1
AAZ.AA A_XGE8/0/1
111231_ATN_01_CSG_A.HW.Kolfe.W To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/3
111030_CX_01_ASG_A.HW.Kolfe.WA To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111030_CX_01_ASG_A.HW.Kolfe.WA To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
111060_ATN_01_CSG_A.HW.Gebeya. To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.
XGE0/5/0
NAAZ.AA AA_XGE8/0/2
111079_ATN_01_CSG_A.HW.Gebeya. XGE0/5/0 To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.
-54-
NAAZ.AA AA_XGE8/0/3
111055_CX_02_RSG_B.HW.Arada.NA To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.
XGE8/0/0
AZ.AA AA_XGE8/0/0
111055_CX_02_RSG_B.HW.Arada.NA To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.
XGE8/0/1
AZ.AA AA_XGE8/0/1
111038_CX_01_ASG_A.HW.Gebeya.N To_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.
XGE2/0/0
AAZ.AA AA_XGE2/0/0
111038_CX_01_ASG_A.HW.Gebeya.N To_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.
XGE2/0/1
AAZ.AA AA_XGE2/0/1
XGE0/5/0
XGE0/5/0
111058_CX_02_ASG_B.HW.Filowaha. To_111043_ATN_01_CSG_A.HW.Filowoha.CAA
XGE8/0/2
XGE0/5/0
111063_ATN_01_CSG_A.HW.Asko.W To_111048_ATN_01_CSG_A.HW.Asko.WAAZ.
XGE0/5/0
AAZ.AA AA_XGE0/6/0
111274_ATN_01_CSG_A.HW.Arada.N To_111055_CX_01_RSG_A.HW.Arada.NAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/2
111161_CX_02_ASG_B.HW.Ferensaile To_111055_CX_01_RSG_A.HW.Arada.NAAZ.A
XGE8/0/0
gasion.NAAZ.AA A_XGE8/0/0
111161_CX_02_ASG_B.HW.Ferensaile To_111055_CX_01_RSG_A.HW.Arada.NAAZ.A
XGE8/0/1
gasion.NAAZ.AA A_XGE8/0/1
XGE0/5/0
AAZ.AA A_XGE8/0/4
XGE0/5/0
AAZ.AA A_XGE8/0/3
111041_ATN_01_CSG_A.HW.Ketema. To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.
XGE0/5/0
WAAZ.AA AA_XGE8/0/4
XGE0/5/0
WAAZ.AA AA_XGE8/0/3
XGE0/5/0
WAAZ.AA AA_XGE8/0/2
111124_CX_02_ASG_B.HW.Shegole.W To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.
XGE8/0/0
AAZ.AA AA_XGE8/0/0
111124_CX_02_ASG_B.HW.Shegole.W To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.
XGE8/0/1
AAZ.AA AA_XGE8/0/1
111001_ATN_01_CSG_A.HW.Ketema. To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.
XGE0/5/0
WAAZ.AA AA_XGE8/0/4
XGE0/5/0
WAAZ.AA AA_XGE8/0/2
-55-
XGE0/5/0
WAAZ.AA AA_XGE8/0/3
111273_ATN_01_CSG_A.HW.Filowoha To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ
XGE0/5/0
.CAAZ.AA .AA_XGE8/0/2
XGE0/5/0
XGE0/5/0
XGE0/5/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
XGE0/5/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE8/0/2
AZ.AA AA_XGE0/6/0
XGE8/0/1
111087_ATN_01_CSG_A.HW.Yeka.EA To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA
XGE0/5/0
AZ.AA _XGE8/0/2
XGE0/5/0
AZ.AA _XGE8/0/3
XGE0/5/0
AZ.AA _XGE8/0/4
111089_CX_02_ASG_B.HW.Gerji.EAA To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA
XGE8/0/0
Z.AA _XGE8/0/0
111089_CX_02_ASG_B.HW.Gerji.EAA XGE8/0/1 To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA
-56-
Z.AA _XGE8/0/1
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
111103_ATN_01_CSG_A.HW.Kotebe.E To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/2
111398_ATN_01_CSG_A.HW.Kotebe.E To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/3
111082_CX_02_ASG_B.HW.Yeka.EAA To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.A
XGE8/0/0
Z.AA A_XGE8/0/0
111082_CX_02_ASG_B.HW.Yeka.EAA To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.A
XGE8/0/1
Z.AA A_XGE8/0/1
111086_CX_01_ASG_A.HW.Kotebe.EA To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111086_CX_01_ASG_A.HW.Kotebe.EA To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
111125_ATN_01_CSG_A.HW.Gerji.EA To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA
XGE0/5/0
AZ.AA _XGE8/0/2
111165_CX_02_ASG_B.HW.Ayat.EAA To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA
XGE8/0/0
Z.AA _XGE8/0/0
111165_CX_02_ASG_B.HW.Ayat.EAA To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA
XGE8/0/1
Z.AA _XGE8/0/1
111095_ATN_01_CSG_A.HW.Gerji.EA To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA
XGE0/5/0
AZ.AA _XGE8/0/3
111089_CX_01_ASG_A.HW.Gerji.EAA To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA
XGE2/0/0
Z.AA _XGE2/0/0
111089_CX_01_ASG_A.HW.Gerji.EAA To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA
XGE2/0/1
Z.AA _XGE2/0/1
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
111082_CX_02_ASG_B.HW.Yeka.EAA To_111094_ATN_01_CSG_A.HW.Yeka.EAAZ.A
XGE8/0/3
Z.AA A_XGE0/6/0
-57-
XGE0/5/0
AAZ.AA AA_XGE0/6/0
111086_CX_02_ASG_B.HW.Kotebe.EA To_111097_ATN_01_CSG_A.HW.Kotebe.EAAZ.
XGE8/0/3
AZ.AA AA_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AZ.AA A_XGE0/6/0
111082_CX_02_ASG_B.HW.Yeka.EAA To_111107_ATN_01_CSG_A.HW.Yeka.EAAZ.A
XGE8/0/2
Z.AA A_XGE0/6/0
XGE0/5/0
XGE0/5/0
XGE0/5/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
111173_ATN_01_CSG_A.HW.HannaM To_111120_CX_01_ASG_A.HW.HannaMariam.S
XGE0/5/0
ariam.SAAZ.AA AAZ.AA_XGE8/0/2
111228_CX_02_ASG_B.HW.Lebu.SAA To_111120_CX_01_ASG_A.HW.HannaMariam.S
XGE8/0/0
Z.AA AAZ.AA_XGE8/0/0
111228_CX_02_ASG_B.HW.Lebu.SAA To_111120_CX_01_ASG_A.HW.HannaMariam.S
XGE8/0/1
Z.AA AAZ.AA_XGE8/0/1
111156_ATN_01_CSG_A.HW.HannaM To_111120_CX_02_ASG_B.HW.HannaMariam.S
XGE0/5/0
ariam.SAAZ.AA AAZ.AA_XGE8/0/2
111120_CX_01_ASG_A.HW.HannaMar To_111120_CX_02_ASG_B.HW.HannaMariam.S
XGE2/0/0
iam.SAAZ.AA AAZ.AA_XGE2/0/0
111120_CX_01_ASG_A.HW.HannaMar XGE2/0/1 To_111120_CX_02_ASG_B.HW.HannaMariam.S
-58-
iam.SAAZ.AA AAZ.AA_XGE2/0/1
XGE0/5/0
XGE0/5/0
111007_CX_02_RSG_B.HW.NifasSilk.S To_111123_ATN_01_CSG_A.HW.NifasSilk.SAA
XGE8/0/2
111276_ATN_01_CSG_A.HW.Shegole. To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.
XGE0/5/0
WAAZ.AA AA_XGE8/0/2
111163_CX_02_ASG_B.HW.Asko.WA To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.
XGE8/0/0
AZ.AA AA_XGE8/0/0
111163_CX_02_ASG_B.HW.Asko.WA To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.
XGE8/0/1
AZ.AA AA_XGE8/0/1
111078_ATN_01_CSG_A.HW.Shegole. To_111124_CX_02_ASG_B.HW.Shegole.WAAZ.
XGE0/5/0
WAAZ.AA AA_XGE8/0/2
111124_CX_01_ASG_A.HW.Shegole.W To_111124_CX_02_ASG_B.HW.Shegole.WAAZ.
XGE2/0/0
AAZ.AA AA_XGE2/0/0
111124_CX_01_ASG_A.HW.Shegole.W To_111124_CX_02_ASG_B.HW.Shegole.WAAZ.
XGE2/0/1
AAZ.AA AA_XGE2/0/1
111164_ATN_01_CSG_A.HW.Gerji.EA To_111125_ATN_01_CSG_A.HW.Gerji.EAAZ.A
XGE0/5/0
AZ.AA A_XGE0/6/0
111213_ATN_01_CSG_A.HW.OldAirpo To_111128_CX_01_ASG_A.HW.OldAirport.SWA
XGE0/5/0
111216_ATN_01_CSG_A.HW.OldAirpo To_111128_CX_01_ASG_A.HW.OldAirport.SWA
XGE0/5/0
111176_CX_02_ASG_B.HW.Karanyo.S To_111128_CX_01_ASG_A.HW.OldAirport.SWA
XGE8/0/0
111176_CX_02_ASG_B.HW.Karanyo.S To_111128_CX_01_ASG_A.HW.OldAirport.SWA
XGE8/0/1
XGE0/5/0
111065_ATN_01_CSG_A.HW.Bole.EA To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA
XGE0/5/0
AZ.AA _XGE8/0/1
111421_ATN_01_CSG_A.HW.Bole.EA To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA
XGE0/5/0
AZ.AA _XGE8/0/0
111277_ATN_01_CSG_A.HW.Bole.EA To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_
XGE0/5/0
AZ.AA XGE8/0/1
111046_ATN_01_CSG_A.HW.SidisKilo To_111148_CX_01_ASG_A.HW.SidistKilo.NAA
XGE0/5/0
111204_ATN_01_CSG_A.HW.SidisKilo To_111148_CX_01_ASG_A.HW.SidistKilo.NAA
XGE0/5/0
XGE0/5/0
-59-
XGE0/5/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
111767_CX_02_ASG_B.HW.Kality.SA To_111157_ATN_01_CSG_A.HW.Kality.SAAZ.
XGE8/0/2
AZ.AA AA_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
111038_CX_02_ASG_B.HW.Gebeya.N To_111161_CX_01_ASG_A.HW.Ferensailegasion
XGE8/0/0
AAZ.AA .NAAZ.AA_XGE8/0/0
111038_CX_02_ASG_B.HW.Gebeya.N To_111161_CX_01_ASG_A.HW.Ferensailegasion
XGE8/0/1
AAZ.AA .NAAZ.AA_XGE8/0/1
111300_ATN_01_CSG_A.HW.Ferinas. To_111161_CX_02_ASG_B.HW.Ferensailegasion.
XGE0/5/0
NAAZ.AA NAAZ.AA_XGE8/0/2
111161_CX_01_ASG_A.HW.Ferensaile To_111161_CX_02_ASG_B.HW.Ferensailegasion.
XGE2/0/0
gasion.NAAZ.AA NAAZ.AA_XGE2/0/0
111161_CX_01_ASG_A.HW.Ferensaile To_111161_CX_02_ASG_B.HW.Ferensailegasion.
XGE2/0/1
gasion.NAAZ.AA NAAZ.AA_XGE2/0/1
XGE0/5/0
AAZ.AA AA_XGE0/6/0
111048_ATN_01_CSG_A.HW.Asko.W To_111163_CX_01_ASG_A.HW.Asko.WAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/2
117001_CX_02_ASG_B.HW.Burau.WA To_111163_CX_01_ASG_A.HW.Asko.WAAZ.A
XGE8/0/0
AZ.AA A_XGE8/0/0
117001_CX_02_ASG_B.HW.Burau.WA To_111163_CX_01_ASG_A.HW.Asko.WAAZ.A
XGE8/0/1
AZ.AA A_XGE8/0/1
111062_ATN_01_CSG_A.HW.Asko.W To_111163_CX_02_ASG_B.HW.Asko.WAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/3
111062_ATN_01_CSG_A.HW.Asko.W To_111163_CX_02_ASG_B.HW.Asko.WAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/2
111163_CX_01_ASG_A.HW.Asko.WA To_111163_CX_02_ASG_B.HW.Asko.WAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111163_CX_01_ASG_A.HW.Asko.WA To_111163_CX_02_ASG_B.HW.Asko.WAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
111089_CX_02_ASG_B.HW.Gerji.EAA To_111164_ATN_01_CSG_A.HW.Gerji.EAAZ.A
XGE8/0/2
Z.AA A_XGE0/6/0
111407_ATN_01_CSG_A.HW.Ayat.EA To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA
XGE0/5/0
AZ.AA _XGE8/0/2
111086_CX_02_ASG_B.HW.Kotebe.EA XGE8/0/0 To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA
-60-
AZ.AA _XGE8/0/0
111086_CX_02_ASG_B.HW.Kotebe.EA To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA
XGE8/0/1
AZ.AA _XGE8/0/1
111165_CX_01_ASG_A.HW.Ayat.EAA To_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA
XGE2/0/0
Z.AA _XGE2/0/0
111165_CX_01_ASG_A.HW.Ayat.EAA To_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA
XGE2/0/1
Z.AA _XGE2/0/1
XGE0/5/0
AAZ.AA AA_XGE0/6/0
111077_ATN_01_CSG_A.HW.Kirkos.S To_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/0
111417_ATN_01_CSG_A.HW.Kirkos.S To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/0
XGE0/5/0
XGE0/5/0
111169_ATN_01_CSG_A.HW.Keranio. To_111176_CX_01_ASG_A.HW.Karanyo.SWAA
XGE0/5/0
111214_ATN_01_CSG_A.HW.Keranio. To_111176_CX_01_ASG_A.HW.Karanyo.SWAA
XGE0/5/0
111302_ATN_01_CSG_A.HW.AyerTen To_111176_CX_01_ASG_A.HW.Karanyo.SWAA
XGE0/5/0
a.SWAAZ.AA Z.AA_XGE8/0/4
111205_CX_02_ASG_B.HW.Mekanisa. To_111176_CX_01_ASG_A.HW.Karanyo.SWAA
XGE8/0/0
111205_CX_02_ASG_B.HW.Mekanisa. To_111176_CX_01_ASG_A.HW.Karanyo.SWAA
XGE8/0/1
111176_CX_01_ASG_A.HW.Karanyo.S To_111176_CX_02_ASG_B.HW.Karanyo.SWAA
XGE2/0/0
111176_CX_01_ASG_A.HW.Karanyo.S To_111176_CX_02_ASG_B.HW.Karanyo.SWAA
XGE2/0/1
111205_CX_02_ASG_B.HW.Mekanisa. To_111183_ATN_01_CSG_A.HW.Mekanism.SW
XGE8/0/2
111205_CX_02_ASG_B.HW.Mekanisa. To_111184_ATN_01_CSG_A.HW.AyerTena.SW
XGE8/0/3
XGE0/5/0
XGE0/5/0
XGE0/5/0
111128_CX_02_ASG_B.HW.OldAirport To_111190_ATN_01_CSG_A.HW.OldAirport.SW
XGE8/0/2
-61-
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE8/0/0
XGE0/5/0
111122_ATN_01_CSG_A.HW.Mekanis To_111205_CX_01_ASG_A.HW.Mekanisa.SWA
XGE0/5/0
m.SWAAZ.AA AZ.AA_XGE8/0/2
111430_ATN_01_CSG_A.HW.AyerTen To_111205_CX_01_ASG_A.HW.Mekanisa.SWA
XGE0/5/0
a.SWAAZ.AA AZ.AA_XGE8/0/3
111128_CX_02_ASG_B.HW.OldAirport To_111205_CX_01_ASG_A.HW.Mekanisa.SWA
XGE8/0/0
.SWAAZ.AA AZ.AA_XGE8/0/0
111128_CX_02_ASG_B.HW.OldAirport To_111205_CX_01_ASG_A.HW.Mekanisa.SWA
XGE8/0/1
.SWAAZ.AA AZ.AA_XGE8/0/1
111205_CX_01_ASG_A.HW.Mekanisa. To_111205_CX_02_ASG_B.HW.Mekanisa.SWA
XGE2/0/0
111205_CX_01_ASG_A.HW.Mekanisa. To_111205_CX_02_ASG_B.HW.Mekanisa.SWA
XGE2/0/1
111212_ATN_01_CSG_A.HW.Lebu.SA To_111211_ATN_01_CSG_A.HW.Lebu.SAAZ.A
XGE0/5/0
AZ.AA A_XGE0/6/0
111228_CX_02_ASG_B.HW.Lebu.SAA To_111212_ATN_01_CSG_A.HW.Lebu.SAAZ.A
XGE8/0/2
Z.AA A_XGE0/6/0
XGE0/5/0
XGE0/5/0
XGE0/5/0
XGE0/5/0
XGE0/5/0
111211_ATN_01_CSG_A.HW.Lebu.SA To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA
XGE0/5/0
AZ.AA _XGE8/0/2
111767_CX_02_ASG_B.HW.Kality.SA To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA
XGE8/0/0
AZ.AA _XGE8/0/0
111767_CX_02_ASG_B.HW.Kality.SA To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA
XGE8/0/1
AZ.AA _XGE8/0/1
111228_CX_01_ASG_A.HW.Lebu.SAA To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA
XGE2/0/0
Z.AA _XGE2/0/0
111228_CX_01_ASG_A.HW.Lebu.SAA XGE2/0/1 To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA
-62-
Z.AA _XGE2/0/1
111086_CX_02_ASG_B.HW.Kotebe.EA To_111230_ATN_01_CSG_A.HW.Kotebe.EAAZ.
XGE8/0/2
AZ.AA AA_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE8/0/0
XGE0/5/0
AZ.AA A_XGE0/6/0
XGE0/5/0
111030_CX_02_ASG_B.HW.Kolfe.WA To_111394_ATN_01_CSG_A.HW.Kolfe.WAAZ.
XGE8/0/2
AZ.AA AA_XGE0/6/0
XGE0/5/0
111136_CX_02_RSG_B.HW.Bole.EAA To_111397_ATN_01_CSG_A.HW.Bole.EAAZ.A
XGE8/0/0
Z.AA A_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
AAZ.AA AA_XGE0/6/0
XGE0/5/0
XGE0/5/0
XGE0/5/0
AZ.AA A_XGE0/6/0
111010_CX_02_ASG_B.HW.BoleMicha To_111408_CX_01_ASG_A.HW.Akaki.SAAZ.A
XGE8/0/0
el.EAAZ.AA A_XGE8/0/0
111010_CX_02_ASG_B.HW.BoleMicha To_111408_CX_01_ASG_A.HW.Akaki.SAAZ.A
XGE8/0/1
el.EAAZ.AA A_XGE8/0/1
111034_ATN_01_CSG_A.HW.Akaki.S To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/2
111408_CX_01_ASG_A.HW.Akaki.SA To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111408_CX_01_ASG_A.HW.Akaki.SA To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
XGE0/5/0
AAZ.AA AA_XGE0/6/0
-63-
XGE8/0/1
111128_CX_02_ASG_B.HW.OldAirport To_111419_ATN_01_CSG_A.HW.OldAirport.SW
XGE8/0/3
XGE0/5/0
AZ.AA A_XGE0/6/0
111176_CX_02_ASG_B.HW.Karanyo.S To_111427_ATN_01_CSG_A.HW.Keranio.SWA
XGE8/0/2
XGE0/5/0
XGE0/5/0
111196_ATN_01_CSG_A.HW.Kality.S To_111767_CX_01_ASG_A.HW.Kality.SAAZ.A
XGE0/5/0
AAZ.AA A_XGE8/0/2
111408_CX_02_ASG_B.HW.Akaki.SA To_111767_CX_01_ASG_A.HW.Kality.SAAZ.A
XGE8/0/0
AZ.AA A_XGE8/0/0
111408_CX_02_ASG_B.HW.Akaki.SA To_111767_CX_01_ASG_A.HW.Kality.SAAZ.A
XGE8/0/1
AZ.AA A_XGE8/0/1
111767_CX_01_ASG_A.HW.Kality.SA To_111767_CX_02_ASG_B.HW.Kality.SAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
111767_CX_01_ASG_A.HW.Kality.SA To_111767_CX_02_ASG_B.HW.Kality.SAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
111030_CX_02_ASG_B.HW.Kolfe.WA To_117001_CX_01_ASG_A.HW.Burau.WAAZ.A
XGE8/0/0
AZ.AA A_XGE8/0/0
111030_CX_02_ASG_B.HW.Kolfe.WA To_117001_CX_01_ASG_A.HW.Burau.WAAZ.A
XGE8/0/1
AZ.AA A_XGE8/0/1
117001_CX_01_ASG_A.HW.Burau.WA To_117001_CX_02_ASG_B.HW.Burau.WAAZ.A
XGE2/0/0
AZ.AA A_XGE2/0/0
117001_CX_01_ASG_A.HW.Burau.WA To_117001_CX_02_ASG_B.HW.Burau.WAAZ.A
XGE2/0/1
AZ.AA A_XGE2/0/1
111007_CX_02_RSG_B.HW.NifasSilk.S 40GE3/0/ To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.
111007_CX_02_RSG_B.HW.NifasSilk.S 40GE3/2/ To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.
111136_CX_01_RSG_A.HW.Bole.EAA 40GE7/0/ To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.
Z.AA 0 AA_40GE7/0/0
111136_CX_01_RSG_A.HW.Bole.EAA 40GE7/2/ To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.
Z.AA 0 AA_40GE7/2/0
111051_CX_02_RSG_B.HW.Microwave 40GE3/0/ To_111051_CX_01_RSG_A.HW.Microwave.CAA
111051_CX_02_RSG_B.HW.Microwave 40GE3/2/ To_111051_CX_01_RSG_A.HW.Microwave.CAA
111128_CX_01_ASG_A.HW.OldAirport 40GE7/2/ To_111051_CX_02_RSG_B.HW.Microwave.CAA
-64-
.SWAAZ.AA 0 Z.AA_40GE7/2/0
111128_CX_01_ASG_A.HW.OldAirport 40GE7/0/ To_111051_CX_02_RSG_B.HW.Microwave.CAA
.SWAAZ.AA 0 Z.AA_40GE7/0/0
111055_CX_02_RSG_B.HW.Arada.NA 40GE7/0/ To_111055_CX_01_RSG_A.HW.Arada.NAAZ.A
AZ.AA 0 A_40GE7/0/0
111057_CX_01_ASG_A.HW.Ketema.W 40GE7/2/ To_111055_CX_02_RSG_B.HW.Arada.NAAZ.A
AAZ.AA 0 A_40GE7/2/0
111057_CX_02_ASG_B.HW.Ketema.W 40GE7/0/ To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.
111051_CX_02_RSG_B.HW.Microwave 40GE10/2 To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.
.CAAZ.AA /0 AA_40GE7/2/0
111058_CX_02_ASG_B.HW.Filowaha. 40GE3/0/ To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ
CAAZ.AA 0 .AA_40GE3/0/0
111058_CX_02_ASG_B.HW.Filowaha. 40GE3/2/ To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ
CAAZ.AA 0 .AA_40GE3/2/0
111051_CX_01_RSG_A.HW.Microwave 40GE7/0/ To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.
.CAAZ.AA 0 AA_40GE7/0/0
111051_CX_01_RSG_A.HW.Microwave 40GE7/2/ To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.
.CAAZ.AA 0 AA_40GE7/2/0
111082_CX_02_ASG_B.HW.Yeka.EAA 40GE7/0/ To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA
Z.AA 0 _40GE7/0/0
111148_CX_01_ASG_A.HW.SidistKilo. 40GE7/2/ To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA
NAAZ.AA 0 _40GE7/2/0
111128_CX_02_ASG_B.HW.OldAirport 40GE3/0/ To_111128_CX_01_ASG_A.HW.OldAirport.SWA
111128_CX_02_ASG_B.HW.OldAirport 40GE3/2/ To_111128_CX_01_ASG_A.HW.OldAirport.SWA
111168_CX_01_RSG_A.HW.Kirkos.SA 40GE7/0/ To_111128_CX_02_ASG_B.HW.OldAirport.SWA
AZ.AA 0 AZ.AA_40GE7/0/0
111168_CX_01_RSG_A.HW.Kirkos.SA 40GE7/2/ To_111128_CX_02_ASG_B.HW.OldAirport.SWA
AZ.AA 0 AZ.AA_40GE7/2/0
111136_CX_02_RSG_B.HW.Bole.EAA 40GE3/0/ To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA
Z.AA 0 _40GE3/0/0
111136_CX_02_RSG_B.HW.Bole.EAA 40GE3/2/ To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA
Z.AA 0 _40GE3/2/0
111082_CX_01_ASG_A.HW.Yeka.EAA 40GE7/2/ To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA
Z.AA 0 _40GE10/2/0
111058_CX_01_ASG_A.HW.Filowaha. 40GE7/0/ To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_
CAAZ.AA 0 40GE7/0/0
111058_CX_01_ASG_A.HW.Filowaha. 40GE7/2/ To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_
CAAZ.AA 0 40GE7/2/0
111148_CX_02_ASG_B.HW.SidistKilo. 40GE7/0/ To_111148_CX_01_ASG_A.HW.SidistKilo.NAA
NAAZ.AA 0 Z.AA_40GE7/0/0
-65-
111055_CX_01_RSG_A.HW.Arada.NA 40GE7/2/ To_111148_CX_02_ASG_B.HW.SidistKilo.NAA

AZ.AA 0 Z.AA_40GE7/2/0
111168_CX_02_RSG_B.HW.Kirkos.SA 40GE3/0/ To_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.A
AZ.AA 0 A_40GE3/0/0
111168_CX_02_RSG_B.HW.Kirkos.SA 40GE3/2/ To_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.A
AZ.AA 0 A_40GE3/2/0
111007_CX_01_RSG_A.HW.NifasSilk. 40GE7/0/ To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.A
SAAZ.AA 0 A_40GE7/0/0
111007_CX_01_RSG_A.HW.NifasSilk. 40GE7/2/ To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.A
SAAZ.AA 0 A_40GE7/2/0
5.6 Equipment Port Connection List

Equipment Port Connection is list below:
SourceNE Port Name Destination NE Port Name

111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA XGE8/0/2 111071_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA XGE0/5/0
111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA XGE8/0/0 111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA XGE8/0/0
111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA XGE8/0/1 111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA XGE8/0/1
111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA XGE8/0/1 111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA XGE8/0/0
111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA XGE8/0/0 111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA XGE8/0/1
111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA XGE8/0/2 111399_ATN_01_CSG_A.HW.BoleMichael.EAAZ.AA XGE0/5/0
111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.AA XGE2/0/0 111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA XGE2/0/0
111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.AA XGE2/0/1 111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA XGE2/0/1
111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA XGE8/0/2 111158_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA XGE0/5/0
111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA XGE8/0/0 111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA XGE8/0/0
111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA XGE8/0/1 111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA XGE8/0/1
111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA XGE8/0/3 111231_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA XGE0/5/0
111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA XGE2/0/0 111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA XGE2/0/0
111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA XGE2/0/1 111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA XGE2/0/1
111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA XGE8/0/2 111060_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA XGE0/5/0
111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA XGE8/0/3 111079_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA XGE0/5/0
111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA XGE8/0/0 111055_CX_02_RSG_B.HW.Arada.NAAZ.AA XGE8/0/0
111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA XGE8/0/1 111055_CX_02_RSG_B.HW.Arada.NAAZ.AA XGE8/0/1
111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA XGE2/0/0 111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA XGE2/0/0
111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA XGE2/0/1 111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA XGE2/0/1
111040_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA XGE0/6/0 111418_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA XGE0/5/0
111043_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA XGE0/6/0 111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA XGE8/0/2
111046_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA XGE0/6/0 111066_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA XGE0/5/0
111048_ATN_01_CSG_A.HW.Asko.WAAZ.AA XGE0/6/0 111063_ATN_01_CSG_A.HW.Asko.WAAZ.AA XGE0/5/0
111055_CX_01_RSG_A.HW.Arada.NAAZ.AA XGE8/0/2 111274_ATN_01_CSG_A.HW.Arada.NAAZ.AA XGE0/5/0
-66-
111055_CX_01_RSG_A.HW.Arada.NAAZ.AA XGE8/0/0 111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA XGE8/0/0

111055_CX_01_RSG_A.HW.Arada.NAAZ.AA XGE8/0/1 111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA XGE8/0/1
111055_CX_02_RSG_B.HW.Arada.NAAZ.AA XGE8/0/4 111004_ATN_01_CSG_A.HW.Arada.NAAZ.AA XGE0/5/0
111055_CX_02_RSG_B.HW.Arada.NAAZ.AA XGE8/0/3 111420_ATN_01_CSG_A.HW.Arada.NAAZ.AA XGE0/5/0
111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA XGE8/0/4 111041_ATN_01_CSG_A.HW.Ketema.WAAZ.AA XGE0/5/0
111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA XGE8/0/0 111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA XGE8/0/0
111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA XGE8/0/1 111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA XGE8/0/1
111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA XGE8/0/4 111001_ATN_01_CSG_A.HW.Ketema.WAAZ.AA XGE0/5/0
111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA XGE8/0/2 111273_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA XGE0/5/0
111064_ATN_01_CSG_A.HW.Bole.EAAZ.AA XGE0/6/0 111397_ATN_01_CSG_A.HW.Bole.EAAZ.AA XGE0/5/0
111068_ATN_01_CSG_A.HW.Arada.NAAZ.AA XGE0/6/0 111075_ATN_01_CSG_A.HW.Arada.NAAZ.AA XGE0/5/0
111070_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA XGE0/6/0 111123_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA XGE0/5/0
111072_ATN_01_CSG_A.HW.Kality.SAAZ.AA XGE0/6/0 111157_ATN_01_CSG_A.HW.Kality.SAAZ.AA XGE0/5/0
111075_ATN_01_CSG_A.HW.Arada.NAAZ.AA XGE0/6/0 111055_CX_02_RSG_B.HW.Arada.NAAZ.AA XGE8/0/2
111076_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA XGE0/6/0 111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA XGE8/0/1
111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA XGE8/0/2 111087_ATN_01_CSG_A.HW.Yeka.EAAZ.AA XGE0/5/0
111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA XGE8/0/0 111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA XGE8/0/0
111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA XGE8/0/1 111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA XGE8/0/1
111083_ATN_01_CSG_A.HW.Yeka.EAAZ.AA XGE0/6/0 111085_ATN_01_CSG_A.HW.Yeka.EAAZ.AA XGE0/5/0
111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA XGE8/0/2 111103_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA XGE0/5/0
111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA XGE8/0/3 111398_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA XGE0/5/0
111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA XGE8/0/0 111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA XGE8/0/0
111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA XGE8/0/1 111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA XGE8/0/1
111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA XGE2/0/0 111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA XGE2/0/0
-67-
111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA XGE2/0/1 111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA XGE2/0/1

111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA XGE8/0/2 111125_ATN_01_CSG_A.HW.Gerji.EAAZ.AA XGE0/5/0
111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA XGE8/0/0 111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA XGE8/0/0
111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA XGE8/0/1 111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA XGE8/0/1
111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA XGE8/0/3 111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA XGE0/5/0
111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA XGE2/0/0 111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA XGE2/0/0
111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA XGE2/0/1 111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA XGE2/0/1
111093_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA XGE0/6/0 111119_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA XGE0/5/0
111094_ATN_01_CSG_A.HW.Yeka.EAAZ.AA XGE0/6/0 111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA XGE8/0/3
111097_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA XGE0/6/0 111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA XGE8/0/3
111107_ATN_01_CSG_A.HW.Yeka.EAAZ.AA XGE0/6/0 111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA XGE8/0/2
111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA XGE8/0/2 111173_ATN_01_CSG_A.HW.HannaMariam.SAAZ.AA XGE0/5/0
111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA XGE8/0/0 111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA XGE8/0/0
111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA XGE8/0/1 111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA XGE8/0/1
111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA XGE8/0/2 111156_ATN_01_CSG_A.HW.HannaMariam.SAAZ.AA XGE0/5/0
111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA XGE2/0/0 111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA XGE2/0/0
111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA XGE2/0/1 111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA XGE2/0/1
111121_ATN_01_CSG_A.HW.OldAirport.SWAAZ.AA XGE0/6/0 111172_ATN_01_CSG_A.HW.OldAirport.SWAAZ.AA XGE0/5/0
111122_ATN_01_CSG_A.HW.Mekanism.SWAAZ.AA XGE0/6/0 111215_ATN_01_CSG_A.HW.Mekanism.SWAAZ.AA XGE0/5/0
111123_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA XGE0/6/0 111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA XGE8/0/2
111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA XGE8/0/2 111276_ATN_01_CSG_A.HW.Shegole.WAAZ.AA XGE0/5/0
111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA XGE8/0/0 111163_CX_02_ASG_B.HW.Asko.WAAZ.AA XGE8/0/0
111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA XGE8/0/1 111163_CX_02_ASG_B.HW.Asko.WAAZ.AA XGE8/0/1
-68-
111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA XGE8/0/2 111078_ATN_01_CSG_A.HW.Shegole.WAAZ.AA XGE0/5/0

111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA XGE2/0/0 111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA XGE2/0/0
111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA XGE2/0/1 111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA XGE2/0/1
111125_ATN_01_CSG_A.HW.Gerji.EAAZ.AA XGE0/6/0 111164_ATN_01_CSG_A.HW.Gerji.EAAZ.AA XGE0/5/0
111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA XGE8/0/3 111213_ATN_01_CSG_A.HW.OldAirport.SWAAZ.AA XGE0/5/0
111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA XGE8/0/2 111216_ATN_01_CSG_A.HW.OldAirport.SWAAZ.AA XGE0/5/0
111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA XGE8/0/0 111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA XGE8/0/0
111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA XGE8/0/1 111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA XGE8/0/1
111131_ATN_01_CSG_A.HW.Ketema.WAAZ.AA XGE0/6/0 111080_ATN_01_CSG_A.HW.Ketema.WAAZ.AA XGE0/5/0
111136_CX_01_RSG_A.HW.Bole.EAAZ.AA XGE8/0/1 111065_ATN_01_CSG_A.HW.Bole.EAAZ.AA XGE0/5/0
111136_CX_01_RSG_A.HW.Bole.EAAZ.AA XGE8/0/0 111421_ATN_01_CSG_A.HW.Bole.EAAZ.AA XGE0/5/0
111136_CX_02_RSG_B.HW.Bole.EAAZ.AA XGE8/0/1 111277_ATN_01_CSG_A.HW.Bole.EAAZ.AA XGE0/5/0
111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA XGE8/0/1 111046_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA XGE0/5/0
111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA XGE8/0/0 111204_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA XGE0/5/0
111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA XGE8/0/2 111207_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA XGE0/5/0
111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA XGE8/0/3 111402_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA XGE0/5/0
111153_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA XGE0/6/0 111394_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA XGE0/5/0
111157_ATN_01_CSG_A.HW.Kality.SAAZ.AA XGE0/6/0 111767_CX_02_ASG_B.HW.Kality.SAAZ.AA XGE8/0/2
111159_ATN_01_CSG_A.HW.Ketema.WAAZ.AA XGE0/6/0 111081_ATN_01_CSG_A.HW.Ketema.WAAZ.AA XGE0/5/0
111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.AA XGE8/0/0 111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA XGE8/0/0
111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.AA XGE8/0/1 111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA XGE8/0/1
111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA XGE8/0/2 111300_ATN_01_CSG_A.HW.Ferinas.NAAZ.AA XGE0/5/0
111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA XGE2/0/0 111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.AA XGE2/0/0
111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA XGE2/0/1 111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.AA XGE2/0/1
111163_CX_01_ASG_A.HW.Asko.WAAZ.AA XGE8/0/2 111048_ATN_01_CSG_A.HW.Asko.WAAZ.AA XGE0/5/0
111163_CX_01_ASG_A.HW.Asko.WAAZ.AA XGE8/0/0 117001_CX_02_ASG_B.HW.Burau.WAAZ.AA XGE8/0/0
111163_CX_01_ASG_A.HW.Asko.WAAZ.AA XGE8/0/1 117001_CX_02_ASG_B.HW.Burau.WAAZ.AA XGE8/0/1
111163_CX_02_ASG_B.HW.Asko.WAAZ.AA XGE8/0/3 111062_ATN_01_CSG_A.HW.Asko.WAAZ.AA XGE0/5/0
111163_CX_02_ASG_B.HW.Asko.WAAZ.AA XGE8/0/2 111062_ATN_01_CSG_A.HW.Asko.WAAZ.AA XGE0/5/0
111163_CX_02_ASG_B.HW.Asko.WAAZ.AA XGE2/0/0 111163_CX_01_ASG_A.HW.Asko.WAAZ.AA XGE2/0/0
111163_CX_02_ASG_B.HW.Asko.WAAZ.AA XGE2/0/1 111163_CX_01_ASG_A.HW.Asko.WAAZ.AA XGE2/0/1
111164_ATN_01_CSG_A.HW.Gerji.EAAZ.AA XGE0/6/0 111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA XGE8/0/2
111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA XGE8/0/2 111407_ATN_01_CSG_A.HW.Ayat.EAAZ.AA XGE0/5/0
111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA XGE8/0/0 111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA XGE8/0/0
111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA XGE8/0/1 111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA XGE8/0/1
111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA XGE2/0/0 111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA XGE2/0/0
111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA XGE2/0/1 111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA XGE2/0/1
-69-
111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA XGE8/0/0 111077_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA XGE0/5/0

111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA XGE8/0/0 111417_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA XGE0/5/0
111171_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA XGE0/6/0 111189_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA XGE0/5/0
111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA XGE8/0/3 111169_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA XGE0/5/0
111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA XGE8/0/2 111214_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA XGE0/5/0
111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA XGE8/0/4 111302_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA XGE0/5/0
111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA XGE8/0/0 111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA XGE8/0/0
111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA XGE8/0/1 111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA XGE8/0/1
111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA XGE2/0/0 111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA XGE2/0/0
111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA XGE2/0/1 111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA XGE2/0/1
111183_ATN_01_CSG_A.HW.Mekanism.SWAAZ.AA XGE0/6/0 111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA XGE8/0/2
111184_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA XGE0/6/0 111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA XGE8/0/3
111186_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA XGE0/6/0 111433_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA XGE0/5/0
111190_ATN_01_CSG_A.HW.OldAirport.SWAAZ.AA XGE0/6/0 111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA XGE8/0/2
111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA XGE8/0/2 111122_ATN_01_CSG_A.HW.Mekanism.SWAAZ.AA XGE0/5/0
111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA XGE8/0/3 111430_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA XGE0/5/0
111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA XGE8/0/0 111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA XGE8/0/0
111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA XGE8/0/1 111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA XGE8/0/1
111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA XGE2/0/0 111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA XGE2/0/0
111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA XGE2/0/1 111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA XGE2/0/1
111211_ATN_01_CSG_A.HW.Lebu.SAAZ.AA XGE0/6/0 111212_ATN_01_CSG_A.HW.Lebu.SAAZ.AA XGE0/5/0
111212_ATN_01_CSG_A.HW.Lebu.SAAZ.AA XGE0/6/0 111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA XGE8/0/2
111215_ATN_01_CSG_A.HW.Mekanism.SWAAZ.AA XGE0/6/0 111183_ATN_01_CSG_A.HW.Mekanism.SWAAZ.AA XGE0/5/0
111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA XGE8/0/2 111211_ATN_01_CSG_A.HW.Lebu.SAAZ.AA XGE0/5/0
111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA XGE8/0/0 111767_CX_02_ASG_B.HW.Kality.SAAZ.AA XGE8/0/0
111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA XGE8/0/1 111767_CX_02_ASG_B.HW.Kality.SAAZ.AA XGE8/0/1
111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA XGE2/0/0 111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA XGE2/0/0
111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA XGE2/0/1 111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA XGE2/0/1
111230_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA XGE0/6/0 111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA XGE8/0/2
-70-

111278_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA XGE0/6/0 111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA XGE8/0/0
111394_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA XGE0/6/0 111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA XGE8/0/2
111397_ATN_01_CSG_A.HW.Bole.EAAZ.AA XGE0/6/0 111136_CX_02_RSG_B.HW.Bole.EAAZ.AA XGE8/0/0
111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA XGE8/0/0 111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.AA XGE8/0/0
111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA XGE8/0/1 111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.AA XGE8/0/1
111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA XGE8/0/2 111034_ATN_01_CSG_A.HW.Akaki.SAAZ.AA XGE0/5/0
111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA XGE2/0/0 111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA XGE2/0/0
111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA XGE2/0/1 111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA XGE2/0/1
111419_ATN_01_CSG_A.HW.OldAirport.SWAAZ.AA XGE0/6/0 111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA XGE8/0/3
111427_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA XGE0/6/0 111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA XGE8/0/2
111767_CX_01_ASG_A.HW.Kality.SAAZ.AA XGE8/0/2 111196_ATN_01_CSG_A.HW.Kality.SAAZ.AA XGE0/5/0
111767_CX_01_ASG_A.HW.Kality.SAAZ.AA XGE8/0/0 111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA XGE8/0/0
111767_CX_01_ASG_A.HW.Kality.SAAZ.AA XGE8/0/1 111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA XGE8/0/1
111767_CX_02_ASG_B.HW.Kality.SAAZ.AA XGE2/0/0 111767_CX_01_ASG_A.HW.Kality.SAAZ.AA XGE2/0/0
111767_CX_02_ASG_B.HW.Kality.SAAZ.AA XGE2/0/1 111767_CX_01_ASG_A.HW.Kality.SAAZ.AA XGE2/0/1
117001_CX_01_ASG_A.HW.Burau.WAAZ.AA XGE8/0/0 111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA XGE8/0/0
117001_CX_01_ASG_A.HW.Burau.WAAZ.AA XGE8/0/1 111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA XGE8/0/1
117001_CX_02_ASG_B.HW.Burau.WAAZ.AA XGE2/0/0 117001_CX_01_ASG_A.HW.Burau.WAAZ.AA XGE2/0/0
117001_CX_02_ASG_B.HW.Burau.WAAZ.AA XGE2/0/1 117001_CX_01_ASG_A.HW.Burau.WAAZ.AA XGE2/0/1
111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA 40GE3/0/0 111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA 40GE3/0/0
111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA 40GE3/2/0 111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA 40GE3/2/0
111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA 40GE7/0/0 111136_CX_01_RSG_A.HW.Bole.EAAZ.AA 40GE7/0/0
111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA 40GE7/2/0 111136_CX_01_RSG_A.HW.Bole.EAAZ.AA 40GE7/2/0
111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA 40GE3/0/0 111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA 40GE3/0/0
111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA 40GE3/2/0 111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA 40GE3/2/0
111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA 40GE7/2/0 111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA 40GE7/2/0
-71-
111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA 40GE7/0/0 111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA 40GE7/0/0

111055_CX_01_RSG_A.HW.Arada.NAAZ.AA 40GE7/0/0 111055_CX_02_RSG_B.HW.Arada.NAAZ.AA 40GE7/0/0
111055_CX_02_RSG_B.HW.Arada.NAAZ.AA 40GE7/2/0 111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA 40GE7/2/0
111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA 40GE7/0/0 111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA 40GE7/0/0
111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA 40GE7/2/0 111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA 40GE10/2/0
111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA 40GE3/0/0 111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA 40GE3/0/0
111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA 40GE3/2/0 111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA 40GE3/2/0
111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA 40GE7/0/0 111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA 40GE7/0/0
111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA 40GE7/2/0 111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA 40GE7/2/0
111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA 40GE7/0/0 111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA 40GE7/0/0
111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA 40GE7/2/0 111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA 40GE7/2/0
111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA 40GE3/0/0 111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA 40GE3/0/0
111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA 40GE3/2/0 111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA 40GE3/2/0
111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA 40GE7/0/0 111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA 40GE7/0/0
111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA 40GE7/2/0 111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA 40GE7/2/0
111136_CX_01_RSG_A.HW.Bole.EAAZ.AA 40GE3/0/0 111136_CX_02_RSG_B.HW.Bole.EAAZ.AA 40GE3/0/0
111136_CX_01_RSG_A.HW.Bole.EAAZ.AA 40GE3/2/0 111136_CX_02_RSG_B.HW.Bole.EAAZ.AA 40GE3/2/0
111136_CX_01_RSG_A.HW.Bole.EAAZ.AA 40GE10/2/0 111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA 40GE7/2/0
111136_CX_02_RSG_B.HW.Bole.EAAZ.AA 40GE7/0/0 111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA 40GE7/0/0
111136_CX_02_RSG_B.HW.Bole.EAAZ.AA 40GE7/2/0 111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA 40GE7/2/0
111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA 40GE7/0/0 111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA 40GE7/0/0
111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA 40GE7/2/0 111055_CX_01_RSG_A.HW.Arada.NAAZ.AA 40GE7/2/0
111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA 40GE3/0/0 111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA 40GE3/0/0
111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA 40GE3/2/0 111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA 40GE3/2/0
111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA 40GE7/0/0 111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA 40GE7/0/0
111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA 40GE7/2/0 111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA 40GE7/2/0
5.7 Cable label naming

Cable Label Naming is list below
Equipment Port Label

From_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_XGE8/0/2==
111007_CX_01_RSG_A. XGE8/0/
========To_111071_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA_XG
HW.NifasSilk.SAAZ.AA 2
E0/5/0
111007_CX_01_RSG_A. XGE8/0/
========To_111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA_
XGE8/0/0
111007_CX_01_RSG_A. XGE8/0/
========To_111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA_
XGE8/0/1
111007_CX_02_RSG_B. XGE8/0/ From_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_XGE8/0/1==
-72-
HW.NifasSilk.SAAZ.AA 1 ========To_111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA_
XGE8/0/0
From_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_XGE8/0/0==
111007_CX_02_RSG_B. XGE8/0/
========To_111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA_
XGE8/0/1
111010_CX_01_ASG_A. From_111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA_XGE8/0/
XGE8/0/
HW.BoleMichael.EAAZ. 2==========To_111399_ATN_01_CSG_A.HW.BoleMichael.EAAZ.
2
AA AA_XGE0/5/0
111010_CX_02_ASG_B. From_111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.AA_XGE2/0/0
XGE2/0/
HW.BoleMichael.EAAZ. ==========To_111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.A
0
AA A_XGE2/0/0
XGE2/0/
HW.BoleMichael.EAAZ. ==========To_111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.A
1
AA A_XGE2/0/1
From_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA_XGE8/0/2====
111030_CX_01_ASG_A. XGE8/0/
======To_111158_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA_XGE0/5/
HW.Kolfe.WAAZ.AA 2
0
111030_CX_01_ASG_A. XGE8/0/
======To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA_XGE8/0
HW.Kolfe.WAAZ.AA 0
/0
111030_CX_01_ASG_A. XGE8/0/
======To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA_XGE8/0
HW.Kolfe.WAAZ.AA 1
/1
From_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE8/0/3====
111030_CX_02_ASG_B. XGE8/0/
HW.Kolfe.WAAZ.AA 3
0
111030_CX_02_ASG_B. XGE2/0/ From_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE2/0/0====
HW.Kolfe.WAAZ.AA 0 ======To_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA_XGE2/0/0
HW.Kolfe.WAAZ.AA 1 ======To_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA_XGE2/0/1
From_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA_XGE8/0/2===
111038_CX_01_ASG_A. XGE8/0/
=======To_111060_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA_XGE0
HW.Gebeya.NAAZ.AA 2
/5/0
111038_CX_01_ASG_A. XGE8/0/
=======To_111079_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA_XGE0
HW.Gebeya.NAAZ.AA 3
/5/0
111038_CX_01_ASG_A. XGE8/0/
=======To_111055_CX_02_RSG_B.HW.Arada.NAAZ.AA_XGE8/0/
HW.Gebeya.NAAZ.AA 0
0
111038_CX_01_ASG_A. XGE8/0/
HW.Gebeya.NAAZ.AA 1
1
111038_CX_02_ASG_B. XGE2/0/ From_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA_XGE2/0/0===
-73-
HW.Gebeya.NAAZ.AA 0 =======To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA_XGE2/
0/0
From_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA_XGE2/0/1===
111038_CX_02_ASG_B. XGE2/0/
=======To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA_XGE2/
HW.Gebeya.NAAZ.AA 1
0/1
111040_ATN_01_CSG_ From_111040_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA_XGE0/6/0=
XGE0/6/
A.HW.Filowoha.CAAZ. =========To_111418_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA_X
0
AA GE0/5/0
XGE0/6/
0
AA GE0/5/0
XGE0/6/
A.HW.Filowoha.CAAZ. =========To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_XG
0
AA E8/0/2
111046_ATN_01_CSG_ From_111046_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA_XGE0/6/0=
XGE0/6/
A.HW.SidisKilo.NAAZ. =========To_111066_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA_
0
AA XGE0/5/0
From_111048_ATN_01_CSG_A.HW.Asko.WAAZ.AA_XGE0/6/0===
111048_ATN_01_CSG_ XGE0/6/
=======To_111063_ATN_01_CSG_A.HW.Asko.WAAZ.AA_XGE0/
A.HW.Asko.WAAZ.AA 0
5/0
From_111055_CX_01_RSG_A.HW.Arada.NAAZ.AA_XGE8/0/2====
111055_CX_01_RSG_A. XGE8/0/
======To_111274_ATN_01_CSG_A.HW.Arada.NAAZ.AA_XGE0/5/
HW.Arada.NAAZ.AA 2
0
111055_CX_01_RSG_A. XGE8/0/
======To_111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA_
HW.Arada.NAAZ.AA 0
XGE8/0/0
111055_CX_01_RSG_A. XGE8/0/
======To_111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA_
HW.Arada.NAAZ.AA 1
XGE8/0/1
From_111055_CX_02_RSG_B.HW.Arada.NAAZ.AA_XGE8/0/4====
111055_CX_02_RSG_B. XGE8/0/
HW.Arada.NAAZ.AA 4
0
111055_CX_02_RSG_B. XGE8/0/
HW.Arada.NAAZ.AA 3
0
From_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_XGE8/0/4==
111057_CX_01_ASG_A. XGE8/0/
========To_111041_ATN_01_CSG_A.HW.Ketema.WAAZ.AA_XG
HW.Ketema.WAAZ.AA 4
E0/5/0
111057_CX_01_ASG_A. XGE8/0/
========To_111391_ATN_01_CSG_A.HW.Ketema.WAAZ.AA_XG
HW.Ketema.WAAZ.AA 3
E0/5/0
111057_CX_01_ASG_A. XGE8/0/ From_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_XGE8/0/2==
HW.Ketema.WAAZ.AA 2 ========To_111404_ATN_01_CSG_A.HW.Ketema.WAAZ.AA_XG
-74-
E0/5/0
111057_CX_01_ASG_A. XGE8/0/
========To_111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA_XGE
HW.Ketema.WAAZ.AA 0
8/0/0
111057_CX_01_ASG_A. XGE8/0/
HW.Ketema.WAAZ.AA 1
8/0/1
From_111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA_XGE8/0/4===
111057_CX_02_ASG_B. XGE8/0/
=======To_111001_ATN_01_CSG_A.HW.Ketema.WAAZ.AA_XGE
HW.Ketema.WAAZ.AA 4
0/5/0
111057_CX_02_ASG_B. XGE8/0/
HW.Ketema.WAAZ.AA 2
0/5/0
111057_CX_02_ASG_B. XGE8/0/
HW.Ketema.WAAZ.AA 3
0/5/0
From_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_XGE8/0/2==
111058_CX_01_ASG_A. XGE8/0/
========To_111273_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA_X
HW.Filowaha.CAAZ.AA 2
GE0/5/0
111058_CX_01_ASG_A. XGE8/0/
GE0/5/0
111058_CX_01_ASG_A. XGE8/0/
GE0/5/0
XGE0/6/
0
AA XGE0/5/0
111064_ATN_01_CSG_ XGE0/6/ From_111064_ATN_01_CSG_A.HW.Bole.EAAZ.AA_XGE0/6/0====
A.HW.Bole.EAAZ.AA 0 ======To_111397_ATN_01_CSG_A.HW.Bole.EAAZ.AA_XGE0/5/0
XGE0/6/
0
AA XGE0/5/0
From_111068_ATN_01_CSG_A.HW.Arada.NAAZ.AA_XGE0/6/0===
111068_ATN_01_CSG_ XGE0/6/
=======To_111075_ATN_01_CSG_A.HW.Arada.NAAZ.AA_XGE0/
A.HW.Arada.NAAZ.AA 0
5/0
111069_ATN_01_CSG_ XGE0/6/
5/0
111070_ATN_01_CSG_ XGE0/6/ From_111070_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA_XGE0/6/0=
A.HW.NifasSilk.SAAZ. 0 =========To_111123_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA_X
-75-
AA GE0/5/0
111071_ATN_01_CSG_ From_111071_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA_XGE0/6/0=
XGE0/6/
A.HW.NifasSilk.SAAZ. =========To_111115_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA_X
0
AA GE0/5/0
From_111072_ATN_01_CSG_A.HW.Kality.SAAZ.AA_XGE0/6/0===
111072_ATN_01_CSG_ XGE0/6/
=======To_111157_ATN_01_CSG_A.HW.Kality.SAAZ.AA_XGE0/
A.HW.Kality.SAAZ.AA 0
5/0
111073_ATN_01_CSG_ XGE0/6/
5/0
111075_ATN_01_CSG_ XGE0/6/
2
XGE0/6/
A.HW.SidisKilo.NAAZ. =========To_111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA_X
0
AA GE8/0/1
111082_CX_01_ASG_A. XGE8/0/ From_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA_XGE8/0/2=====
HW.Yeka.EAAZ.AA 2 =====To_111087_ATN_01_CSG_A.HW.Yeka.EAAZ.AA_XGE0/5/0
HW.Yeka.EAAZ.AA 0 =====To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA_XGE8/0/0
HW.Yeka.EAAZ.AA 1 =====To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA_XGE8/0/1
111083_ATN_01_CSG_ XGE0/6/ From_111083_ATN_01_CSG_A.HW.Yeka.EAAZ.AA_XGE0/6/0====
A.HW.Yeka.EAAZ.AA 0 ======To_111085_ATN_01_CSG_A.HW.Yeka.EAAZ.AA_XGE0/5/0
From_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE8/0/2===
111086_CX_01_ASG_A. XGE8/0/
=======To_111103_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA_XGE0/
HW.Kotebe.EAAZ.AA 2
5/0
111086_CX_01_ASG_A. XGE8/0/
=======To_111398_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA_XGE0/
HW.Kotebe.EAAZ.AA 3
5/0
111086_CX_01_ASG_A. XGE8/0/ From_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE8/0/0===
HW.Kotebe.EAAZ.AA 0 =======To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_XGE8/0/0
111086_CX_01_ASG_A. XGE8/0/ From_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE8/0/1===
-76-
HW.Kotebe.EAAZ.AA 1 =======To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_XGE8/0/1
From_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE2/0/0====
111086_CX_02_ASG_B. XGE2/0/
======To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE2/0/
HW.Kotebe.EAAZ.AA 0
0
111086_CX_02_ASG_B. XGE2/0/
======To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE2/0/
HW.Kotebe.EAAZ.AA 1
1
111089_CX_01_ASG_A. XGE8/0/ From_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA_XGE8/0/2=====
HW.Gerji.EAAZ.AA 2 =====To_111125_ATN_01_CSG_A.HW.Gerji.EAAZ.AA_XGE0/5/0
HW.Gerji.EAAZ.AA 0 =====To_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA_XGE8/0/0
HW.Gerji.EAAZ.AA 1 =====To_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA_XGE8/0/1
111089_CX_02_ASG_B. XGE8/0/ From_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA_XGE8/0/3=====
HW.Gerji.EAAZ.AA 0 =====To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA_XGE2/0/0
HW.Gerji.EAAZ.AA 1 =====To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA_XGE2/0/1
111093_ATN_01_CSG_ From_111093_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA_XGE0/6/0==
XGE0/6/
A.HW.Kotebe.EAAZ.A ========To_111119_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA_XGE
0
A 0/5/0
A.HW.Yeka.EAAZ.AA 0 ======To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_XGE8/0/3
XGE0/6/
0
A 0/5/0
XGE0/6/
A.HW.Kotebe.EAAZ.A ========To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE8/
0
A 0/3
-77-
XGE0/6/
0
A 0/5/0
XGE0/6/
0
A 0/5/0
XGE0/6/
0
A 0/5/0
A.HW.Yeka.EAAZ.AA 0 ======To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_XGE8/0/2
XGE0/6/
0
AA XGE0/5/0
XGE0/6/
0
AA GE0/5/0
XGE0/6/
0
AA GE0/5/0
111118_ATN_01_CSG_ XGE0/6/
5/0
XGE0/6/
0
A 0/5/0
111120_CX_01_ASG_A. From_111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA_XGE8/0
XGE8/0/
HW.HannaMariam.SAA /2==========To_111173_ATN_01_CSG_A.HW.HannaMariam.SAA
2
Z.AA Z.AA_XGE0/5/0
XGE8/0/
HW.HannaMariam.SAA /0==========To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA_XG
0
Z.AA E8/0/0
XGE8/0/
HW.HannaMariam.SAA /1==========To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA_XG
1
Z.AA E8/0/1
111120_CX_02_ASG_B. From_111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA_XGE8/0
XGE8/0/
HW.HannaMariam.SAA /2==========To_111156_ATN_01_CSG_A.HW.HannaMariam.SAA
2
Z.AA Z.AA_XGE0/5/0
-78-
XGE2/0/
HW.HannaMariam.SAA /0==========To_111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.
0
Z.AA AA_XGE2/0/0
XGE2/0/
HW.HannaMariam.SAA /1==========To_111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.
1
Z.AA AA_XGE2/0/1
111121_ATN_01_CSG_ From_111121_ATN_01_CSG_A.HW.OldAirport.SWAAZ.AA_XGE0/
XGE0/6/
A.HW.OldAirport.SWA 6/0==========To_111172_ATN_01_CSG_A.HW.OldAirport.SWAA
0
AZ.AA Z.AA_XGE0/5/0
111122_ATN_01_CSG_ From_111122_ATN_01_CSG_A.HW.Mekanism.SWAAZ.AA_XGE0/6
XGE0/6/
A.HW.Mekanism.SWAA /0==========To_111215_ATN_01_CSG_A.HW.Mekanism.SWAAZ.
0
Z.AA AA_XGE0/5/0
XGE0/6/
A.HW.NifasSilk.SAAZ. =========To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_XG
0
AA E8/0/2
From_111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA_XGE8/0/2==
111124_CX_01_ASG_A. XGE8/0/
========To_111276_ATN_01_CSG_A.HW.Shegole.WAAZ.AA_XG
HW.Shegole.WAAZ.AA 2
E0/5/0
111124_CX_01_ASG_A. XGE8/0/
========To_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE8/0
/0
111124_CX_01_ASG_A. XGE8/0/
========To_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE8/0
/1
From_111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA_XGE8/0/2==
111124_CX_02_ASG_B. XGE8/0/
========To_111078_ATN_01_CSG_A.HW.Shegole.WAAZ.AA_XG
E0/5/0
111124_CX_02_ASG_B. XGE2/0/
========To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA_XGE
2/0/0
111124_CX_02_ASG_B. XGE2/0/
========To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA_XGE
2/0/1
111125_ATN_01_CSG_ XGE0/6/ From_111125_ATN_01_CSG_A.HW.Gerji.EAAZ.AA_XGE0/6/0====
A.HW.Gerji.EAAZ.AA 0 ======To_111164_ATN_01_CSG_A.HW.Gerji.EAAZ.AA_XGE0/5/0
111128_CX_01_ASG_A. From_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA_XGE8/0/
XGE8/0/
HW.OldAirport.SWAAZ 3==========To_111213_ATN_01_CSG_A.HW.OldAirport.SWAAZ.
3
.AA AA_XGE0/5/0
XGE8/0/
2
.AA AA_XGE0/5/0
111128_CX_01_ASG_A. XGE8/0/ From_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA_XGE8/0/
HW.OldAirport.SWAAZ 0 0==========To_111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA
-79-
.AA _XGE8/0/0
XGE8/0/
HW.OldAirport.SWAAZ 1==========To_111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA
1
.AA _XGE8/0/1
111131_ATN_01_CSG_ From_111131_ATN_01_CSG_A.HW.Ketema.WAAZ.AA_XGE0/6/0=
XGE0/6/
A.HW.Ketema.WAAZ.A =========To_111080_ATN_01_CSG_A.HW.Ketema.WAAZ.AA_X
0
A GE0/5/0
111136_CX_01_RSG_A. XGE8/0/ From_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_XGE8/0/1=====
HW.Bole.EAAZ.AA 1 =====To_111065_ATN_01_CSG_A.HW.Bole.EAAZ.AA_XGE0/5/0
111136_CX_01_RSG_A. XGE8/0/ From_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_XGE8/0/0=====
111136_CX_02_RSG_B. XGE8/0/ From_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_XGE8/0/1=====
111148_CX_01_ASG_A. From_111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA_XGE8/0/1=
XGE8/0/
HW.SidistKilo.NAAZ.A =========To_111046_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA_
1
A XGE0/5/0
111148_CX_01_ASG_A. From_111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA_XGE8/0/0=
XGE8/0/
0
A XGE0/5/0
111148_CX_02_ASG_B. From_111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA_XGE8/0/2=
XGE8/0/
2
A XGE0/5/0
XGE8/0/
3
A XGE0/5/0
From_111153_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA_XGE0/6/0===
111153_ATN_01_CSG_ XGE0/6/
=======To_111394_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA_XGE0/
A.HW.Kolfe.WAAZ.AA 0
5/0
111157_ATN_01_CSG_ XGE0/6/
=======To_111767_CX_02_ASG_B.HW.Kality.SAAZ.AA_XGE8/0/
2
111158_ATN_01_CSG_ XGE0/6/
5/0
XGE0/6/
0
A GE0/5/0
111160_ATN_01_CSG_ XGE0/6/
5/0
111161_CX_01_ASG_A. From_111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.AA_XGE
XGE8/0/
HW.Ferensailegasion.NA 8/0/0==========To_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.A
0
AZ.AA A_XGE8/0/0
-80-
XGE8/0/
HW.Ferensailegasion.NA 8/0/1==========To_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.A
1
AZ.AA A_XGE8/0/1
111161_CX_02_ASG_B. From_111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA_XGE
XGE8/0/
HW.Ferensailegasion.NA 8/0/2==========To_111300_ATN_01_CSG_A.HW.Ferinas.NAAZ.A
2
AZ.AA A_XGE0/5/0
XGE2/0/
HW.Ferensailegasion.NA 2/0/0==========To_111161_CX_01_ASG_A.HW.Ferensailegasion.N
0
AZ.AA AAZ.AA_XGE2/0/0
XGE2/0/
HW.Ferensailegasion.NA 2/0/1==========To_111161_CX_01_ASG_A.HW.Ferensailegasion.N
1
XGE0/6/
0
A 0/5/0
From_111163_CX_01_ASG_A.HW.Asko.WAAZ.AA_XGE8/0/2====
111163_CX_01_ASG_A. XGE8/0/
======To_111048_ATN_01_CSG_A.HW.Asko.WAAZ.AA_XGE0/5/
HW.Asko.WAAZ.AA 2
0
111163_CX_01_ASG_A. XGE8/0/ From_111163_CX_01_ASG_A.HW.Asko.WAAZ.AA_XGE8/0/0====
HW.Asko.WAAZ.AA 0 ======To_117001_CX_02_ASG_B.HW.Burau.WAAZ.AA_XGE8/0/0
HW.Asko.WAAZ.AA 1 ======To_117001_CX_02_ASG_B.HW.Burau.WAAZ.AA_XGE8/0/1
From_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE8/0/3====
111163_CX_02_ASG_B. XGE8/0/
HW.Asko.WAAZ.AA 3
0
111163_CX_02_ASG_B. XGE8/0/
HW.Asko.WAAZ.AA 2
0
111163_CX_02_ASG_B. XGE2/0/ From_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE2/0/0====
HW.Asko.WAAZ.AA 0 ======To_111163_CX_01_ASG_A.HW.Asko.WAAZ.AA_XGE2/0/0
111163_CX_02_ASG_B. XGE2/0/ From_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE2/0/1====
HW.Asko.WAAZ.AA 1 ======To_111163_CX_01_ASG_A.HW.Asko.WAAZ.AA_XGE2/0/1
111164_ATN_01_CSG_A. XGE0/6/ From_111164_ATN_01_CSG_A.HW.Gerji.EAAZ.AA_XGE0/6/0====
HW.Gerji.EAAZ.AA 0 ======To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA_XGE8/0/2
111165_CX_01_ASG_A. XGE8/0/ From_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA_XGE8/0/2=====
HW.Ayat.EAAZ.AA 2 =====To_111407_ATN_01_CSG_A.HW.Ayat.EAAZ.AA_XGE0/5/0
HW.Ayat.EAAZ.AA 0 =====To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE8/0/0
HW.Ayat.EAAZ.AA 1 =====To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE8/0/1
111165_CX_02_ASG_B. XGE2/0/ From_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA_XGE2/0/0=====
HW.Ayat.EAAZ.AA 0 =====To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA_XGE2/0/0
-81-
HW.Ayat.EAAZ.AA 1 =====To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA_XGE2/0/1
XGE0/6/
0
A 0/5/0
From_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_XGE8/0/0====
111168_CX_01_RSG_A. XGE8/0/
======To_111077_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA_XGE0/5/
HW.Kirkos.SAAZ.AA 0
0
From_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_XGE8/0/0====
111168_CX_02_RSG_B. XGE8/0/
======To_111417_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA_XGE0/5/
HW.Kirkos.SAAZ.AA 0
0
111171_ATN_01_CSG_ From_111171_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA_XGE0/6/0
XGE0/6/
A.HW.Keranio.SWAAZ. ==========To_111189_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA
0
AA _XGE0/5/0
XGE0/6/
0
AZ.AA Z.AA_XGE0/5/0
111176_CX_01_ASG_A. From_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA_XGE8/0/3=
XGE8/0/
HW.Karanyo.SWAAZ.A =========To_111169_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA_
3
A XGE0/5/0
XGE8/0/
2
A XGE0/5/0
XGE8/0/
HW.Karanyo.SWAAZ.A =========To_111302_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA
4
A _XGE0/5/0
XGE8/0/
HW.Karanyo.SWAAZ.A =========To_111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA_
0
A XGE8/0/0
XGE8/0/
HW.Karanyo.SWAAZ.A =========To_111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA_
1
A XGE8/0/1
111176_CX_02_ASG_B. From_111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA_XGE2/0/0=
XGE2/0/
HW.Karanyo.SWAAZ.A =========To_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA_X
0
A GE2/0/0
XGE2/0/
HW.Karanyo.SWAAZ.A =========To_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA_X
1
A GE2/0/1
XGE0/6/
A.HW.Mekanism.SWAA /0==========To_111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.A
0
Z.AA A_XGE8/0/2
111184_ATN_01_CSG_ From_111184_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA_XGE0/6/
XGE0/6/
A.HW.AyerTena.SWAA 0==========To_111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.A
0
Z.AA A_XGE8/0/3
-82-
XGE0/6/
A.HW.AyerTena.SWAA 0==========To_111433_ATN_01_CSG_A.HW.AyerTena.SWAAZ.
0
Z.AA AA_XGE0/5/0
XGE0/3/
0
AA _XGE0/5/0
XGE0/6/
0
AA _XGE0/5/0
XGE0/6/
A.HW.OldAirport.SWA 6/0==========To_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.
0
AZ.AA AA_XGE8/0/2
111196_ATN_01_CSG_ XGE0/6/
5/0
XGE0/6/
A.HW.Filowoha.CAAZ. =========To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_XG
0
AA E8/0/0
XGE0/6/
0
AA XGE0/5/0
111205_CX_01_ASG_A. From_111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA_XGE8/0/2
XGE8/0/
HW.Mekanisa.SWAAZ. ==========To_111122_ATN_01_CSG_A.HW.Mekanism.SWAAZ.A
2
AA A_XGE0/5/0
XGE8/0/
HW.Mekanisa.SWAAZ. ==========To_111430_ATN_01_CSG_A.HW.AyerTena.SWAAZ.A
3
AA A_XGE0/5/0
XGE8/0/
HW.Mekanisa.SWAAZ. ==========To_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.A
0
AA A_XGE8/0/0
XGE8/0/
HW.Mekanisa.SWAAZ. ==========To_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.A
1
AA A_XGE8/0/1
111205_CX_02_ASG_B. From_111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA_XGE2/0/0
XGE2/0/
HW.Mekanisa.SWAAZ. ==========To_111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA
0
AA _XGE2/0/0
XGE2/0/
HW.Mekanisa.SWAAZ. ==========To_111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA
1
AA _XGE2/0/1
111211_ATN_01_CSG_ XGE0/6/ From_111211_ATN_01_CSG_A.HW.Lebu.SAAZ.AA_XGE0/6/0====
A.HW.Lebu.SAAZ.AA 0 ======To_111212_ATN_01_CSG_A.HW.Lebu.SAAZ.AA_XGE0/5/0
-83-

A.HW.Lebu.SAAZ.AA 0 ======To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA_XGE8/0/2
XGE0/6/
0
AZ.AA Z.AA_XGE0/5/0
XGE0/6/
0
AA _XGE0/5/0
XGE0/6/
0
Z.AA AA_XGE0/5/0
XGE0/6/
0
AZ.AA Z.AA_XGE0/5/0
XGE0/6/
0
Z.AA AA_XGE0/5/0
111228_CX_01_ASG_A. XGE8/0/ From_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA_XGE8/0/2=====
HW.Lebu.SAAZ.AA 2 =====To_111211_ATN_01_CSG_A.HW.Lebu.SAAZ.AA_XGE0/5/0
HW.Lebu.SAAZ.AA 0 =====To_111767_CX_02_ASG_B.HW.Kality.SAAZ.AA_XGE8/0/0
HW.Lebu.SAAZ.AA 1 =====To_111767_CX_02_ASG_B.HW.Kality.SAAZ.AA_XGE8/0/1
111228_CX_02_ASG_B. XGE2/0/ From_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA_XGE2/0/0=====
HW.Lebu.SAAZ.AA 0 =====To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA_XGE2/0/0
HW.Lebu.SAAZ.AA 1 =====To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA_XGE2/0/1
XGE0/6/
A.HW.Kotebe.EAAZ.A ========To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE8/
0
A 0/2
111231_ATN_01_CSG_ XGE0/6/
5/0
XGE0/6/
0
AA GE0/5/0
111274_ATN_01_CSG_ XGE0/6/
5/0
XGE0/6/
0
AA GE8/0/0
-84-
XGE0/6/
0
AA GE0/5/0
111394_ATN_01_CSG_ XGE0/6/
=======To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE8/0/
2
From_111396_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA_XGE0/6/0=
111396_ATN_01_CSG_A. XGE0/6/
=========To_111405_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA_X
HW.Filowoha.CAAZ.AA 0
GE0/5/0
A.HW.Bole.EAAZ.AA 0 ======To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_XGE8/0/0
XGE0/6/
0
A 0/5/0
XGE0/6/
0
A 0/5/0
XGE0/6/
0
AA GE0/5/0
XGE0/6/
0
AA GE0/5/0
From_111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA_XGE8/0/0====
111408_CX_01_ASG_A. XGE8/0/
======To_111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.AA_XG
HW.Akaki.SAAZ.AA 0
E8/0/0
From_111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA_XGE8/0/1====
111408_CX_01_ASG_A. XGE8/0/
======To_111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.AA_XG
HW.Akaki.SAAZ.AA 1
E8/0/1
From_111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA_XGE8/0/2====
111408_CX_02_ASG_B. XGE8/0/
======To_111034_ATN_01_CSG_A.HW.Akaki.SAAZ.AA_XGE0/5/
HW.Akaki.SAAZ.AA 2
0
111408_CX_02_ASG_B. XGE2/0/ From_111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA_XGE2/0/0====
HW.Akaki.SAAZ.AA 0 ======To_111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA_XGE2/0/0
HW.Akaki.SAAZ.AA 1 ======To_111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA_XGE2/0/1
XGE0/6/
0
A 0/5/0
111418_ATN_01_CSG_ XGE0/6/ From_111418_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA_XGE0/6/0=
-85-
A.HW.Filowoha.CAAZ. 0 =========To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_XG
AA E8/0/1
XGE0/6/
A.HW.OldAirport.SWA 6/0==========To_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.
0
AZ.AA AA_XGE8/0/3
XGE0/6/
A.HW.Keranio.SWAAZ. ==========To_111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA_
0
AA XGE8/0/2
XGE0/6/
0
Z.AA AA_XGE0/5/0
XGE0/6/
0
Z.AA AA_XGE0/5/0
From_111767_CX_01_ASG_A.HW.Kality.SAAZ.AA_XGE8/0/2====
111767_CX_01_ASG_A. XGE8/0/
======To_111196_ATN_01_CSG_A.HW.Kality.SAAZ.AA_XGE0/5/
HW.Kality.SAAZ.AA 2
0
111767_CX_01_ASG_A. XGE8/0/ From_111767_CX_01_ASG_A.HW.Kality.SAAZ.AA_XGE8/0/0====
HW.Kality.SAAZ.AA 0 ======To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA_XGE8/0/0
HW.Kality.SAAZ.AA 1 ======To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA_XGE8/0/1
111767_CX_02_ASG_B. XGE2/0/ From_111767_CX_02_ASG_B.HW.Kality.SAAZ.AA_XGE2/0/0====
HW.Kality.SAAZ.AA 0 ======To_111767_CX_01_ASG_A.HW.Kality.SAAZ.AA_XGE2/0/0
HW.Kality.SAAZ.AA 1 ======To_111767_CX_01_ASG_A.HW.Kality.SAAZ.AA_XGE2/0/1
117001_CX_01_ASG_A. XGE8/0/ From_117001_CX_01_ASG_A.HW.Burau.WAAZ.AA_XGE8/0/0====
HW.Burau.WAAZ.AA 0 ======To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE8/0/0
HW.Burau.WAAZ.AA 1 ======To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE8/0/1
117001_CX_02_ASG_B. XGE2/0/ From_117001_CX_02_ASG_B.HW.Burau.WAAZ.AA_XGE2/0/0====
HW.Burau.WAAZ.AA 0 ======To_117001_CX_01_ASG_A.HW.Burau.WAAZ.AA_XGE2/0/0
HW.Burau.WAAZ.AA 1 ======To_117001_CX_01_ASG_A.HW.Burau.WAAZ.AA_XGE2/0/1
From_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_40GE3/0/0==
111007_CX_01_RSG_A. 40GE3/0/
========To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_40G
E3/0/0
From_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_40GE3/2/0==
111007_CX_01_RSG_A. 40GE3/2/
========To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_40G
E3/2/0
111007_CX_02_RSG_B. 40GE7/0/ From_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_40GE7/0/0==
HW.NifasSilk.SAAZ.AA 0 ========To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE7/0/
-86-
0
From_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_40GE7/2/0==
111007_CX_02_RSG_B. 40GE7/2/
========To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE7/2/
0
111051_CX_01_RSG_A. From_111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA_40GE3/0/0
40GE3/0/
HW.Microwave.CAAZ. ==========To_111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA_
0
AA 40GE3/0/0
111051_CX_01_RSG_A. From_111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA_40GE3/2/0
40GE3/2/
HW.Microwave.CAAZ. ==========To_111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA_
0
AA 40GE3/2/0
111051_CX_02_RSG_B. From_111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA_40GE7/2/0
40GE7/2/
HW.Microwave.CAAZ. ==========To_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.A
0
AA A_40GE7/2/0
40GE7/0/
HW.Microwave.CAAZ. ==========To_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.A
0
AA A_40GE7/0/0
111055_CX_01_RSG_A. 40GE7/0/ From_111055_CX_01_RSG_A.HW.Arada.NAAZ.AA_40GE7/0/0====
HW.Arada.NAAZ.AA 0 ======To_111055_CX_02_RSG_B.HW.Arada.NAAZ.AA_40GE7/0/0
From_111055_CX_02_RSG_B.HW.Arada.NAAZ.AA_40GE7/2/0====
111055_CX_02_RSG_B. 40GE7/2/
======To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_40GE7/
HW.Arada.NAAZ.AA 0
2/0
From_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_40GE7/0/0==
111057_CX_01_ASG_A. 40GE7/0/
========To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA_40GE
HW.Ketema.WAAZ.AA 0
7/0/0
From_111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA_40GE7/2/0==
111057_CX_02_ASG_B. 40GE7/2/
========To_111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA_40
HW.Ketema.WAAZ.AA 0
GE10/2/0
From_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_40GE3/0/0=
111058_CX_01_ASG_A. 40GE3/0/
=========To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_40
GE3/0/0
From_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_40GE3/2/0=
111058_CX_01_ASG_A. 40GE3/2/
=========To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_40
GE3/2/0
From_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_40GE7/0/0=
111058_CX_02_ASG_B. 40GE7/0/
=========To_111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA_4
0GE7/0/0
111058_CX_02_ASG_B. 40GE7/2/
=========To_111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA_4
0GE7/2/0
111082_CX_01_ASG_A. 40GE7/0/ From_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA_40GE7/0/0====
HW.Yeka.EAAZ.AA 0 ======To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_40GE7/0/0
111082_CX_02_ASG_B. 40GE7/2/ From_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_40GE7/2/0====
HW.Yeka.EAAZ.AA 0 ======To_111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA_40GE
-87-
7/2/0
111128_CX_01_ASG_A. From_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA_40GE3/0/
40GE3/0/
HW.OldAirport.SWAAZ 0==========To_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.A
0
.AA A_40GE3/0/0
40GE3/2/
HW.OldAirport.SWAAZ 0==========To_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.A
0
.AA A_40GE3/2/0
111128_CX_02_ASG_B. From_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA_40GE7/0/
40GE7/0/
HW.OldAirport.SWAAZ 0==========To_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_40
0
.AA GE7/0/0
40GE7/2/
HW.OldAirport.SWAAZ 0==========To_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_40
0
.AA GE7/2/0
111136_CX_01_RSG_A. 40GE3/0/ From_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE3/0/0=====
HW.Bole.EAAZ.AA 0 =====To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_40GE3/0/0
111136_CX_01_RSG_A. 40GE3/2/ From_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE3/2/0=====
HW.Bole.EAAZ.AA 0 =====To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_40GE3/2/0
111136_CX_01_RSG_A. 40GE10/ From_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE10/2/0====
HW.Bole.EAAZ.AA 2/0 ======To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA_40GE7/2/0
From_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_40GE7/0/0=====
111136_CX_02_RSG_B. 40GE7/0/
=====To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_40GE7/0
HW.Bole.EAAZ.AA 0
/0
From_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_40GE7/2/0=====
111136_CX_02_RSG_B. 40GE7/2/
=====To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_40GE7/2
HW.Bole.EAAZ.AA 0
/0
111148_CX_01_ASG_A. From_111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA_40GE7/0/0=
40GE7/0/
HW.SidistKilo.NAAZ.A =========To_111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA_40
0
A GE7/0/0
111148_CX_02_ASG_B. From_111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA_40GE7/2/0=
40GE7/2/
HW.SidistKilo.NAAZ.A =========To_111055_CX_01_RSG_A.HW.Arada.NAAZ.AA_40GE
0
A 7/2/0
From_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_40GE3/0/0===
111168_CX_01_RSG_A. 40GE3/0/
=======To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_40GE3/0
HW.Kirkos.SAAZ.AA 0
/0
From_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_40GE3/2/0===
111168_CX_01_RSG_A. 40GE3/2/
=======To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_40GE3/2
HW.Kirkos.SAAZ.AA 0
/0
From_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_40GE7/0/0====
111168_CX_02_RSG_B. 40GE7/0/
======To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_40GE7/
HW.Kirkos.SAAZ.AA 0
0/0
From_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_40GE7/2/0====
111168_CX_02_RSG_B. 40GE7/2/
======To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_40GE7/
HW.Kirkos.SAAZ.AA 0
2/0
-88-
XGE0/5/
A.HW.NifasSilk.SAAZ. =========To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_XG
0
AA E8/0/2
XGE8/0/
HW.HannaMariam.SAA /0==========To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_
0
Z.AA XGE8/0/0
XGE8/0/
HW.HannaMariam.SAA /1==========To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_
1
Z.AA XGE8/0/1
XGE8/0/
HW.BoleMichael.EAAZ. 0==========To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_
0
AA XGE8/0/1
XGE8/0/
HW.BoleMichael.EAAZ. 1==========To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_
1
AA XGE8/0/0
111399_ATN_01_CSG_ From_111399_ATN_01_CSG_A.HW.BoleMichael.EAAZ.AA_XGE0/5
XGE0/5/
A.HW.BoleMichael.EAA /0==========To_111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.
0
Z.AA AA_XGE8/0/2
XGE2/0/
HW.BoleMichael.EAAZ. 0==========To_111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.A
0
AA A_XGE2/0/0
XGE2/0/
HW.BoleMichael.EAAZ. 1==========To_111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.A
1
AA A_XGE2/0/1
111158_ATN_01_CSG_ XGE0/5/
=======To_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA_XGE8/0/
2
111057_CX_02_ASG_B. XGE8/0/
HW.Ketema.WAAZ.AA 0
0
111057_CX_02_ASG_B. XGE8/0/
HW.Ketema.WAAZ.AA 1
1
111231_ATN_01_CSG_ XGE0/5/
=======To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE8/0/
3
111030_CX_01_ASG_A. XGE2/0/ From_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA_XGE2/0/0====
HW.Kolfe.WAAZ.AA 0 ======To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE2/0/0
111030_CX_01_ASG_A. XGE2/0/ From_111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA_XGE2/0/1====
HW.Kolfe.WAAZ.AA 1 ======To_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE2/0/1
111060_ATN_01_CSG_ From_111060_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA_XGE0/5/0==
XGE0/5/
A.HW.Gebeya.NAAZ.A ========To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA_XGE8
0
A /0/2
-89-
111079_ATN_01_CSG_ From_111079_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA_XGE0/5/0==
XGE0/5/
A.HW.Gebeya.NAAZ.A ========To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA_XGE8
0
A /0/3
111055_CX_02_RSG_B. XGE8/0/
======To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA_XGE8/0/
HW.Arada.NAAZ.AA 0
0
111055_CX_02_RSG_B. XGE8/0/
======To_111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA_XGE8/0/
HW.Arada.NAAZ.AA 1
1
111038_CX_01_ASG_A. XGE2/0/
=======To_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA_XGE2/
HW.Gebeya.NAAZ.AA 0
0/0
111038_CX_01_ASG_A. XGE2/0/
=======To_111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA_XGE2/
HW.Gebeya.NAAZ.AA 1
0/1
XGE0/5/
0
AA GE0/6/0
XGE0/5/
0
AA GE0/6/0
From_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_XGE8/0/2==
111058_CX_02_ASG_B. XGE8/0/
GE0/6/0
XGE0/5/
0
AA XGE0/6/0
111063_ATN_01_CSG_ XGE0/5/
=======To_111048_ATN_01_CSG_A.HW.Asko.WAAZ.AA_XGE0/
A.HW.Asko.WAAZ.AA 0
6/0
111274_ATN_01_CSG_ XGE0/5/
=======To_111055_CX_01_RSG_A.HW.Arada.NAAZ.AA_XGE8/0/
2
XGE8/0/
HW.Ferensailegasion.NA 8/0/0==========To_111055_CX_01_RSG_A.HW.Arada.NAAZ.AA_
0
AZ.AA XGE8/0/0
XGE8/0/
HW.Ferensailegasion.NA 8/0/1==========To_111055_CX_01_RSG_A.HW.Arada.NAAZ.AA_
1
AZ.AA XGE8/0/1
111004_ATN_01_CSG_ XGE0/5/
4
111420_ATN_01_CSG_ XGE0/5/ From_111420_ATN_01_CSG_A.HW.Arada.NAAZ.AA_XGE0/5/0===
-90-
A.HW.Arada.NAAZ.AA 0 =======To_111055_CX_02_RSG_B.HW.Arada.NAAZ.AA_XGE8/0/
3
XGE0/5/
A.HW.Ketema.WAAZ.A =========To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_XG
0
A E8/0/4
XGE0/5/
0
A E8/0/3
XGE0/5/
0
A E8/0/2
111124_CX_02_ASG_B. XGE8/0/
========To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_XGE
8/0/0
111124_CX_02_ASG_B. XGE8/0/
========To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_XGE
8/0/1
XGE0/5/
A.HW.Ketema.WAAZ.A =========To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA_XG
0
A E8/0/4
XGE0/5/
0
A E8/0/2
XGE0/5/
0
A E8/0/3
XGE0/5/
A.HW.Filowoha.CAAZ. =========To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_X
0
AA GE8/0/2
XGE0/5/
0
AA GE8/0/1
XGE0/5/
0
AA GE8/0/0
XGE0/5/
0
AA XGE0/6/0
111076_ATN_01_CSG_ XGE0/5/ From_111076_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA_XGE0/5/0=
-91-
A.HW.SidisKilo.NAAZ. 0 =========To_111066_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA_
AA XGE0/6/0
111075_ATN_01_CSG_ XGE0/5/
6/0
111118_ATN_01_CSG_ XGE0/5/
6/0
XGE0/5/
0
AA GE0/6/0
XGE0/5/
0
AA GE0/6/0
111157_ATN_01_CSG_ XGE0/5/
6/0
111072_ATN_01_CSG_ XGE0/5/
6/0
111055_CX_02_RSG_B. XGE8/0/
HW.Arada.NAAZ.AA 2
0
XGE8/0/
1
A XGE0/6/0
A.HW.Yeka.EAAZ.AA 0 ======To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA_XGE8/0/2
HW.Gerji.EAAZ.AA 0 =====To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA_XGE8/0/0
HW.Gerji.EAAZ.AA 1 =====To_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA_XGE8/0/1
-92-
XGE0/5/
A.HW.Kotebe.EAAZ.A ========To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE8/
0
A 0/2
XGE0/5/
A.HW.Kotebe.EAAZ.A ========To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE8/
0
A 0/3
111082_CX_02_ASG_B. XGE8/0/ From_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_XGE8/0/0=====
HW.Yeka.EAAZ.AA 0 =====To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE8/0/0
HW.Yeka.EAAZ.AA 1 =====To_111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA_XGE8/0/1
111086_CX_01_ASG_A. XGE2/0/
=======To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE2/0
HW.Kotebe.EAAZ.AA 0
/0
111086_CX_01_ASG_A. XGE2/0/
=======To_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE2/0
HW.Kotebe.EAAZ.AA 1
/1
A.HW.Gerji.EAAZ.AA 0 ======To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA_XGE8/0/2
HW.Ayat.EAAZ.AA 0 =====To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA_XGE8/0/0
HW.Ayat.EAAZ.AA 1 =====To_111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA_XGE8/0/1
A.HW.Gerji.EAAZ.AA 0 ======To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA_XGE8/0/3
HW.Gerji.EAAZ.AA 0 =====To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA_XGE2/0/0
HW.Gerji.EAAZ.AA 1 =====To_111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA_XGE2/0/1
XGE0/5/
0
A 0/6/0
111093_ATN_01_CSG_ XGE0/5/ From_111093_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA_XGE0/5/0==
-93-
A.HW.Kotebe.EAAZ.A 0 ========To_111096_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA_XGE
A 0/6/0
111086_CX_02_ASG_B. XGE8/0/
======To_111097_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA_XGE0/6
HW.Kotebe.EAAZ.AA 3
/0
XGE0/5/
0
A 0/6/0
XGE0/5/
0
A 0/6/0
XGE0/5/
0
A 0/6/0
XGE0/5/
0
AA XGE0/6/0
XGE0/5/
0
AA GE0/6/0
XGE0/5/
0
AA GE0/6/0
111068_ATN_01_CSG_ XGE0/5/
6/0
XGE0/5/
0
A 0/6/0
111173_ATN_01_CSG_ XGE0/5/ From_111173_ATN_01_CSG_A.HW.HannaMariam.SAAZ.AA_XGE0/
A.HW.HannaMariam.SA 0 5/0==========To_111120_CX_01_ASG_A.HW.HannaMariam.SAA
-94-
AZ.AA Z.AA_XGE8/0/2
From_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA_XGE8/0/0=====
111228_CX_02_ASG_B. XGE8/0/
=====To_111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA_XG
HW.Lebu.SAAZ.AA 0
E8/0/0
From_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA_XGE8/0/1=====
111228_CX_02_ASG_B. XGE8/0/
=====To_111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA_XG
HW.Lebu.SAAZ.AA 1
E8/0/1
111156_ATN_01_CSG_ From_111156_ATN_01_CSG_A.HW.HannaMariam.SAAZ.AA_XGE0/
XGE0/5/
A.HW.HannaMariam.SA 5/0==========To_111120_CX_02_ASG_B.HW.HannaMariam.SAA
0
AZ.AA Z.AA_XGE8/0/2
XGE2/0/
HW.HannaMariam.SAA /0==========To_111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.
0
Z.AA AA_XGE2/0/0
XGE2/0/
HW.HannaMariam.SAA /1==========To_111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.
1
Z.AA AA_XGE2/0/1
XGE0/5/
0
AZ.AA Z.AA_XGE0/6/0
XGE0/5/
0
Z.AA AA_XGE0/6/0
From_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_XGE8/0/2==
111007_CX_02_RSG_B. XGE8/0/
========To_111123_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA_XG
E0/6/0
111276_ATN_01_CSG_ From_111276_ATN_01_CSG_A.HW.Shegole.WAAZ.AA_XGE0/5/0=
XGE0/5/
A.HW.Shegole.WAAZ.A =========To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA_XG
0
A E8/0/2
111163_CX_02_ASG_B. XGE8/0/
======To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA_XGE8/0
HW.Asko.WAAZ.AA 0
/0
111163_CX_02_ASG_B. XGE8/0/
======To_111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA_XGE8/0
HW.Asko.WAAZ.AA 1
/1
111078_ATN_01_CSG_ From_111078_ATN_01_CSG_A.HW.Shegole.WAAZ.AA_XGE0/5/0=
XGE0/5/
A.HW.Shegole.WAAZ.A =========To_111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA_XG
0
A E8/0/2
111124_CX_01_ASG_A. XGE2/0/
2/0/0
111124_CX_01_ASG_A. XGE2/0/
2/0/1
-95-

A.HW.Gerji.EAAZ.AA 0 ======To_111125_ATN_01_CSG_A.HW.Gerji.EAAZ.AA_XGE0/6/0
XGE0/5/
A.HW.OldAirport.SWA 5/0==========To_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ
0
AZ.AA .AA_XGE8/0/3
XGE0/5/
A.HW.OldAirport.SWA 5/0==========To_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ
0
AZ.AA .AA_XGE8/0/2
XGE8/0/
HW.Karanyo.SWAAZ.A =========To_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA
0
A _XGE8/0/0
XGE8/0/
HW.Karanyo.SWAAZ.A =========To_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA
1
A _XGE8/0/1
XGE0/5/
0
A GE0/6/0
A.HW.Bole.EAAZ.AA 0 ======To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_XGE8/0/1
A.HW.Bole.EAAZ.AA 0 ======To_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_XGE8/0/0
A.HW.Bole.EAAZ.AA 0 ======To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_XGE8/0/1
XGE0/5/
A.HW.SidisKilo.NAAZ. =========To_111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA_X
0
AA GE8/0/1
XGE0/5/
A.HW.SidisKilo.NAAZ. =========To_111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA_X
0
AA GE8/0/0
XGE0/5/
0
AA GE8/0/2
XGE0/5/
0
AA GE8/0/3
111394_ATN_01_CSG_ XGE0/5/
6/0
From_111767_CX_02_ASG_B.HW.Kality.SAAZ.AA_XGE8/0/2====
111767_CX_02_ASG_B. XGE8/0/
======To_111157_ATN_01_CSG_A.HW.Kality.SAAZ.AA_XGE0/6/
HW.Kality.SAAZ.AA 2
0
111160_ATN_01_CSG_ XGE0/5/ From_111160_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA_XGE0/5/0===
A.HW.Kolfe.WAAZ.AA 0 =======To_111158_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA_XGE0/
-96-
6/0
XGE0/5/
0
A GE0/6/0
111153_ATN_01_CSG_ XGE0/5/
6/0
111038_CX_02_ASG_B. XGE8/0/
=======To_111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.AA
HW.Gebeya.NAAZ.AA 0
_XGE8/0/0
111038_CX_02_ASG_B. XGE8/0/
=======To_111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.AA
HW.Gebeya.NAAZ.AA 1
_XGE8/0/1
111300_ATN_01_CSG_ From_111300_ATN_01_CSG_A.HW.Ferinas.NAAZ.AA_XGE0/5/0==
XGE0/5/
A.HW.Ferinas.NAAZ.A ========To_111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.A
0
A A_XGE8/0/2
XGE2/0/
HW.Ferensailegasion.NA 2/0/0==========To_111161_CX_02_ASG_B.HW.Ferensailegasion.N
0
XGE2/0/
HW.Ferensailegasion.NA 2/0/1==========To_111161_CX_02_ASG_B.HW.Ferensailegasion.N
1
XGE0/5/
0
A 0/6/0
111048_ATN_01_CSG_ XGE0/5/
=======To_111163_CX_01_ASG_A.HW.Asko.WAAZ.AA_XGE8/0/
A.HW.Asko.WAAZ.AA 0
2
HW.Burau.WAAZ.AA 0 ======To_111163_CX_01_ASG_A.HW.Asko.WAAZ.AA_XGE8/0/0
HW.Burau.WAAZ.AA 1 ======To_111163_CX_01_ASG_A.HW.Asko.WAAZ.AA_XGE8/0/1
111062_ATN_01_CSG_ XGE0/5/
=======To_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE8/0/
A.HW.Asko.WAAZ.AA 0
3
111062_ATN_01_CSG_ XGE0/5/
=======To_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE8/0/
A.HW.Asko.WAAZ.AA 0
2
HW.Asko.WAAZ.AA 0 ======To_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE2/0/0
HW.Asko.WAAZ.AA 1 ======To_111163_CX_02_ASG_B.HW.Asko.WAAZ.AA_XGE2/0/1
-97-
111407_ATN_01_CSG_ XGE0/5/ From_111407_ATN_01_CSG_A.HW.Ayat.EAAZ.AA_XGE0/5/0====
A.HW.Ayat.EAAZ.AA 0 ======To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA_XGE8/0/2
111086_CX_02_ASG_B. XGE8/0/ From_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE8/0/0====
HW.Kotebe.EAAZ.AA 0 ======To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA_XGE8/0/0
111086_CX_02_ASG_B. XGE8/0/ From_111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA_XGE8/0/1====
HW.Kotebe.EAAZ.AA 1 ======To_111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA_XGE8/0/1
HW.Ayat.EAAZ.AA 0 =====To_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA_XGE2/0/0
HW.Ayat.EAAZ.AA 1 =====To_111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA_XGE2/0/1
XGE0/5/
0
A 0/6/0
From_111077_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA_XGE0/5/0===
111077_ATN_01_CSG_ XGE0/5/
=======To_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_XGE8/0/
A.HW.Kirkos.SAAZ.AA 0
0
From_111417_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA_XGE0/5/0===
111417_ATN_01_CSG_ XGE0/5/
=======To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_XGE8/0/
A.HW.Kirkos.SAAZ.AA 0
0
XGE0/5/
0
AA _XGE0/6/0
XGE0/5/
0
AZ.AA Z.AA_XGE0/6/0
XGE0/5/
A.HW.Keranio.SWAAZ. ==========To_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA_
0
AA XGE8/0/3
XGE0/5/
A.HW.Keranio.SWAAZ. ==========To_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA_
0
AA XGE8/0/2
XGE0/5/
A.HW.AyerTena.SWAA 0==========To_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA
0
Z.AA _XGE8/0/4
XGE8/0/
HW.Mekanisa.SWAAZ. ==========To_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA_
0
AA XGE8/0/0
XGE8/0/
HW.Mekanisa.SWAAZ. ==========To_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA_
1
AA XGE8/0/1
111176_CX_01_ASG_A. XGE2/0/ From_111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA_XGE2/0/0=
HW.Karanyo.SWAAZ.A 0 =========To_111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA_X
-98-
A GE2/0/0
XGE2/0/
HW.Karanyo.SWAAZ.A =========To_111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA_X
1
A GE2/0/1
XGE8/0/
HW.Mekanisa.SWAAZ. ==========To_111183_ATN_01_CSG_A.HW.Mekanism.SWAAZ.A
2
AA A_XGE0/6/0
XGE8/0/
HW.Mekanisa.SWAAZ. ==========To_111184_ATN_01_CSG_A.HW.AyerTena.SWAAZ.A
3
AA A_XGE0/6/0
XGE0/5/
0
Z.AA AA_XGE0/6/0
XGE0/5/
0
AA _XGE0/3/0
XGE0/5/
0
AA _XGE0/6/0
111128_CX_02_ASG_B. From_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA_XGE8/0/
XGE8/0/
2
.AA AA_XGE0/6/0
111073_ATN_01_CSG_ XGE0/5/
6/0
111058_CX_02_ASG_B. XGE8/0/
GE0/6/0
XGE0/5/
0
AA XGE0/6/0
XGE0/5/
A.HW.Mekanism.SWAA /0==========To_111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.A
0
Z.AA A_XGE8/0/2
XGE0/5/
A.HW.AyerTena.SWAA 0==========To_111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.A
0
Z.AA A_XGE8/0/3
XGE8/0/
HW.OldAirport.SWAAZ 0==========To_111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.A
0
.AA A_XGE8/0/0
111128_CX_02_ASG_B. XGE8/0/ From_111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA_XGE8/0/
-99-
HW.OldAirport.SWAAZ 1 1==========To_111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.A
.AA A_XGE8/0/1
XGE2/0/
HW.Mekanisa.SWAAZ. ==========To_111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA
0
AA _XGE2/0/0
XGE2/0/
HW.Mekanisa.SWAAZ. ==========To_111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA
1
AA _XGE2/0/1
A.HW.Lebu.SAAZ.AA 0 ======To_111211_ATN_01_CSG_A.HW.Lebu.SAAZ.AA_XGE0/6/0
HW.Lebu.SAAZ.AA 2 =====To_111212_ATN_01_CSG_A.HW.Lebu.SAAZ.AA_XGE0/6/0
XGE0/5/
0
AZ.AA Z.AA_XGE0/6/0
XGE0/5/
0
AA _XGE0/6/0
XGE0/5/
0
Z.AA AA_XGE0/6/0
XGE0/5/
0
AZ.AA Z.AA_XGE0/6/0
XGE0/5/
0
Z.AA AA_XGE0/6/0
A.HW.Lebu.SAAZ.AA 0 ======To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA_XGE8/0/2
HW.Kality.SAAZ.AA 0 ======To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA_XGE8/0/0
HW.Kality.SAAZ.AA 1 ======To_111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA_XGE8/0/1
HW.Lebu.SAAZ.AA 0 =====To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA_XGE2/0/0
HW.Lebu.SAAZ.AA 1 =====To_111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA_XGE2/0/1
111086_CX_02_ASG_B. XGE8/0/
======To_111230_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA_XGE0/6
HW.Kotebe.EAAZ.AA 2
/0
111182_ATN_01_CSG_ XGE0/5/
6/0
-100-
XGE0/5/
0
AA GE0/6/0
111069_ATN_01_CSG_ XGE0/5/
6/0
XGE8/0/
0
A XGE0/6/0
XGE0/5/
0
AA GE0/6/0
From_111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA_XGE8/0/2====
111030_CX_02_ASG_B. XGE8/0/
HW.Kolfe.WAAZ.AA 2
0
XGE0/5/
0
AA GE0/6/0
111136_CX_02_RSG_B. XGE8/0/ From_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_XGE8/0/0=====
XGE0/5/
0
A 0/6/0
XGE0/5/
0
A 0/6/0
XGE0/5/
0
AA GE0/6/0
XGE0/5/
0
AA GE0/6/0
XGE8/0/
HW.BoleMichael.EAAZ. ==========To_111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA_XGE
0
AA 8/0/0
XGE8/0/
HW.BoleMichael.EAAZ. ==========To_111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA_XGE
1
AA 8/0/1
111034_ATN_01_CSG_ XGE0/5/ From_111034_ATN_01_CSG_A.HW.Akaki.SAAZ.AA_XGE0/5/0===
-101-
A.HW.Akaki.SAAZ.AA 0 =======To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA_XGE8/0/
2
111408_CX_01_ASG_A. XGE2/0/ From_111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA_XGE2/0/0====
HW.Akaki.SAAZ.AA 0 ======To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA_XGE2/0/0
111408_CX_01_ASG_A. XGE2/0/ From_111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA_XGE2/0/1====
HW.Akaki.SAAZ.AA 1 ======To_111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA_XGE2/0/1
XGE0/5/
0
A 0/6/0
111058_CX_02_ASG_B. XGE8/0/
GE0/6/0
XGE8/0/
3
.AA AA_XGE0/6/0
XGE8/0/
2
A XGE0/6/0
XGE0/5/
0
Z.AA AA_XGE0/6/0
XGE0/5/
0
Z.AA AA_XGE0/6/0
111196_ATN_01_CSG_ XGE0/5/
=======To_111767_CX_01_ASG_A.HW.Kality.SAAZ.AA_XGE8/0/
2
HW.Akaki.SAAZ.AA 0 ======To_111767_CX_01_ASG_A.HW.Kality.SAAZ.AA_XGE8/0/0
HW.Akaki.SAAZ.AA 1 ======To_111767_CX_01_ASG_A.HW.Kality.SAAZ.AA_XGE8/0/1
HW.Kality.SAAZ.AA 0 ======To_111767_CX_02_ASG_B.HW.Kality.SAAZ.AA_XGE2/0/0
HW.Kality.SAAZ.AA 1 ======To_111767_CX_02_ASG_B.HW.Kality.SAAZ.AA_XGE2/0/1
HW.Kolfe.WAAZ.AA 0 ======To_117001_CX_01_ASG_A.HW.Burau.WAAZ.AA_XGE8/0/0
HW.Kolfe.WAAZ.AA 1 ======To_117001_CX_01_ASG_A.HW.Burau.WAAZ.AA_XGE8/0/1
HW.Burau.WAAZ.AA 0 ======To_117001_CX_02_ASG_B.HW.Burau.WAAZ.AA_XGE2/0/0
-102-

HW.Burau.WAAZ.AA 1 ======To_117001_CX_02_ASG_B.HW.Burau.WAAZ.AA_XGE2/0/1
111007_CX_02_RSG_B. 40GE3/0/
========To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_40G
E3/0/0
111007_CX_02_RSG_B. 40GE3/2/
========To_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_40G
E3/2/0
From_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE7/0/0=====
111136_CX_01_RSG_A. 40GE7/0/
=====To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_40GE7/0
HW.Bole.EAAZ.AA 0
/0
From_111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE7/2/0=====
111136_CX_01_RSG_A. 40GE7/2/
=====To_111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA_40GE7/2
HW.Bole.EAAZ.AA 0
/0
40GE3/0/
HW.Microwave.CAAZ. ==========To_111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA_
0
AA 40GE3/0/0
40GE3/2/
HW.Microwave.CAAZ. ==========To_111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA_
0
AA 40GE3/2/0
40GE7/2/
HW.OldAirport.SWAAZ 0==========To_111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA
0
.AA _40GE7/2/0
40GE7/0/
HW.OldAirport.SWAAZ 0==========To_111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA
0
.AA _40GE7/0/0
111055_CX_02_RSG_B. 40GE7/0/ From_111055_CX_02_RSG_B.HW.Arada.NAAZ.AA_40GE7/0/0====
HW.Arada.NAAZ.AA 0 ======To_111055_CX_01_RSG_A.HW.Arada.NAAZ.AA_40GE7/0/0
From_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_40GE7/2/0==
111057_CX_01_ASG_A. 40GE7/2/
========To_111055_CX_02_RSG_B.HW.Arada.NAAZ.AA_40GE7/
HW.Ketema.WAAZ.AA 0
2/0
From_111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA_40GE7/0/0==
111057_CX_02_ASG_B. 40GE7/0/
========To_111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA_40GE
HW.Ketema.WAAZ.AA 0
7/0/0
111051_CX_02_RSG_B. From_111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA_40GE10/2/
40GE10/
HW.Microwave.CAAZ. 0==========To_111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA_4
2/0
AA 0GE7/2/0
111058_CX_02_ASG_B. 40GE3/0/
=========To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_40
GE3/0/0
111058_CX_02_ASG_B. 40GE3/2/
=========To_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_40
GE3/2/0
-103-
111051_CX_01_RSG_A.
40GE7/0/ From_111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA_40GE7/0/0
HW.Microwave.CAAZ.
0 --To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_40GE7/0/0
AA
111051_CX_01_RSG_A.
40GE7/2/ From_111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA_40GE7/2/0
HW.Microwave.CAAZ.
0 --To_111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA_40GE7/2/0
AA
111082_CX_02_ASG_B. 40GE7/0/ From_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_40GE7/0/0--To_1
HW.Yeka.EAAZ.AA 0 11082_CX_01_ASG_A.HW.Yeka.EAAZ.AA_40GE7/0/0
111148_CX_01_ASG_A.
40GE7/2/ From_111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA_40GE7/2/0--
HW.SidistKilo.NAAZ.A
0 To_111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA_40GE7/2/0
A
40GE3/0/
HW.OldAirport.SWAAZ 0--To_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA_40GE3/0
0
.AA /0
40GE3/2/
HW.OldAirport.SWAAZ 0--To_111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA_40GE3/2
0
.AA /0
111168_CX_01_RSG_A. 40GE7/0/ From_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_40GE7/0/0--To
HW.Kirkos.SAAZ.AA 0 _111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA_40GE7/0/0
111168_CX_01_RSG_A. 40GE7/2/ From_111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_40GE7/2/0--To
HW.Kirkos.SAAZ.AA 0 _111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA_40GE7/2/0
111136_CX_02_RSG_B. 40GE3/0/ From_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_40GE3/0/0--To_1
HW.Bole.EAAZ.AA 0 11136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE3/0/0
111136_CX_02_RSG_B. 40GE3/2/ From_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_40GE3/2/0--To_1
HW.Bole.EAAZ.AA 0 11136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE3/2/0
111082_CX_01_ASG_A. 40GE7/2/ From_111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA_40GE7/2/0--To_
HW.Yeka.EAAZ.AA 0 111136_CX_01_RSG_A.HW.Bole.EAAZ.AA_40GE10/2/0
111058_CX_01_ASG_A. 40GE7/0/ From_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_40GE7/0/0--
HW.Filowaha.CAAZ.AA 0 To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_40GE7/0/0
111058_CX_01_ASG_A. 40GE7/2/ From_111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA_40GE7/2/0--
HW.Filowaha.CAAZ.AA 0 To_111136_CX_02_RSG_B.HW.Bole.EAAZ.AA_40GE7/2/0
111148_CX_02_ASG_B.
40GE7/0/ From_111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA_40GE7/0/0--
HW.SidistKilo.NAAZ.A
0 To_111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA_40GE7/0/0
A
111055_CX_01_RSG_A. 40GE7/2/ From_111055_CX_01_RSG_A.HW.Arada.NAAZ.AA_40GE7/2/0--To_
HW.Arada.NAAZ.AA 0 111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA_40GE7/2/0
111168_CX_02_RSG_B. 40GE3/0/ From_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_40GE3/0/0--To_
HW.Kirkos.SAAZ.AA 0 111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_40GE3/0/0
111168_CX_02_RSG_B. 40GE3/2/ From_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_40GE3/2/0--To_
HW.Kirkos.SAAZ.AA 0 111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA_40GE3/2/0
111007_CX_01_RSG_A. 40GE7/0/ From_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_40GE7/0/0--
HW.NifasSilk.SAAZ.AA 0 To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_40GE7/0/0
111007_CX_01_RSG_A. 40GE7/2/ From_111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA_40GE7/2/0--
-104-
HW.NifasSilk.SAAZ.AA 0 To_111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA_40GE7/2/0
-105-
6 Logical Planning and Design
6.1 IP Address Planning

6.1.1 Designing Loopback Interface Addresses
Design Guidelines
 The IP address of a loopback interface uses a 32-bit mask.
 The addresses of loopback interfaces are allocated from the aggregation layer, and then the
access layer. The values are in ascending order.
111051_CX_01_RSG_A.HW.Microwave.CAAZ.AA 10.0.5.1
111051_CX_02_RSG_B.HW.Microwave.CAAZ.AA 10.0.5.2
111136_CX_01_RSG_A.HW.Bole.EAAZ.AA 10.0.5.3
111136_CX_02_RSG_B.HW.Bole.EAAZ.AA 10.0.5.4
111055_CX_01_RSG_A.HW.Arada.NAAZ.AA 10.0.5.5
111055_CX_02_RSG_B.HW.Arada.NAAZ.AA 10.0.5.6
111168_CX_01_RSG_A.HW.Kirkos.SAAZ.AA 10.0.5.7
111168_CX_02_RSG_B.HW.Kirkos.SAAZ.AA 10.0.5.8
111007_CX_01_RSG_A.HW.NifasSilk.SAAZ.AA 10.0.5.9
111007_CX_02_RSG_B.HW.NifasSilk.SAAZ.AA 10.0.5.10
111058_CX_01_ASG_A.HW.Filowaha.CAAZ.AA 10.0.5.11
111058_CX_02_ASG_B.HW.Filowaha.CAAZ.AA 10.0.5.12
111165_CX_01_ASG_A.HW.Ayat.EAAZ.AA 10.0.5.13
111165_CX_02_ASG_B.HW.Ayat.EAAZ.AA 10.0.5.14
111010_CX_01_ASG_A.HW.BoleMichael.EAAZ.AA 10.0.5.15
111010_CX_02_ASG_B.HW.BoleMichael.EAAZ.AA 10.0.5.16
111089_CX_01_ASG_A.HW.Gerji.EAAZ.AA 10.0.5.17
111089_CX_02_ASG_B.HW.Gerji.EAAZ.AA 10.0.5.18
111086_CX_01_ASG_A.HW.Kotebe.EAAZ.AA 10.0.5.19
111086_CX_02_ASG_B.HW.Kotebe.EAAZ.AA 10.0.5.20
111082_CX_01_ASG_A.HW.Yeka.EAAZ.AA 10.0.5.21
111082_CX_02_ASG_B.HW.Yeka.EAAZ.AA 10.0.5.22
-106-
111038_CX_01_ASG_A.HW.Gebeya.NAAZ.AA 10.0.5.23
111038_CX_02_ASG_B.HW.Gebeya.NAAZ.AA 10.0.5.24
111161_CX_01_ASG_A.HW.Ferensailegasion.NAAZ.AA 10.0.5.25
111161_CX_02_ASG_B.HW.Ferensailegasion.NAAZ.AA 10.0.5.26
111148_CX_01_ASG_A.HW.SidistKilo.NAAZ.AA 10.0.5.27
111148_CX_02_ASG_B.HW.SidistKilo.NAAZ.AA 10.0.5.28
111408_CX_01_ASG_A.HW.Akaki.SAAZ.AA 10.0.5.29
111408_CX_02_ASG_B.HW.Akaki.SAAZ.AA 10.0.5.30
111120_CX_01_ASG_A.HW.HannaMariam.SAAZ.AA 10.0.5.31
111120_CX_02_ASG_B.HW.HannaMariam.SAAZ.AA 10.0.5.32
111767_CX_01_ASG_A.HW.Kality.SAAZ.AA 10.0.5.33
111767_CX_02_ASG_B.HW.Kality.SAAZ.AA 10.0.5.34
111228_CX_01_ASG_A.HW.Lebu.SAAZ.AA 10.0.5.35
111228_CX_02_ASG_B.HW.Lebu.SAAZ.AA 10.0.5.36
111176_CX_01_ASG_A.HW.Karanyo.SWAAZ.AA 10.0.5.37
111176_CX_02_ASG_B.HW.Karanyo.SWAAZ.AA 10.0.5.38
111205_CX_01_ASG_A.HW.Mekanisa.SWAAZ.AA 10.0.5.39
111205_CX_02_ASG_B.HW.Mekanisa.SWAAZ.AA 10.0.5.40
111128_CX_01_ASG_A.HW.OldAirport.SWAAZ.AA 10.0.5.41
111128_CX_02_ASG_B.HW.OldAirport.SWAAZ.AA 10.0.5.42
111057_CX_01_ASG_A.HW.Ketema.WAAZ.AA 10.0.5.43
111057_CX_02_ASG_B.HW.Ketema.WAAZ.AA 10.0.5.44
111163_CX_01_ASG_A.HW.Asko.WAAZ.AA 10.0.5.45
111163_CX_02_ASG_B.HW.Asko.WAAZ.AA 10.0.5.46
117001_CX_01_ASG_A.HW.Burau.WAAZ.AA 10.0.5.47
117001_CX_02_ASG_B.HW.Burau.WAAZ.AA 10.0.5.48
111030_CX_01_ASG_A.HW.Kolfe.WAAZ.AA 10.0.5.49
111030_CX_02_ASG_B.HW.Kolfe.WAAZ.AA 10.0.5.50
111124_CX_01_ASG_A.HW.Shegole.WAAZ.AA 10.0.5.51
111124_CX_02_ASG_B.HW.Shegole.WAAZ.AA 10.0.5.52
Reserved for New CX(RSG&ASG) router which is installed
in the future 10.0.5.53-60
111040_ATN_01_CSG_A.HW.Filowoha.CAAZ.AA 10.0.5.61
-107-
111407_ATN_01_CSG_A.HW.Ayat.EAAZ.AA 10.0.5.72
111192_ATN_01_CSG_A.HW.Bole.EAAZ.AA 10.0.5.73
111399_ATN_01_CSG_A.HW.Bole Michael.EAAZ.AA 10.0.5.83
111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA 10.0.5.84
111409_ATN_01_CSG_A.HW.Kotebe.EAAZ.AA 10.0.5.87
111083_ATN_01_CSG_A.HW.Yeka.EAAZ.AA 10.0.5.100
-108-
111079_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA 10.0.5.115
111060_ATN_01_CSG_A.HW.Gebeya.NAAZ.AA 10.0.5.116
111068_ATN_01_CSG_A.HW.Arada.NAAZ.AA 10.0.5.117
111300_ATN_01_CSG_A.HW.Ferinas.NAAZ.AA 10.0.5.124
111278_ATN_01_CSG_A.HW.SidisKilo.NAAZ.AA 10.0.5.125
111034_ATN_01_CSG_A.HW.Akaki.SAAZ.AA 10.0.5.134
111156_ATN_01_CSG_A.HW.HannaMariam.SAAZ.AA 10.0.5.135
111173_ATN_01_CSG_A.HW.HannaMariam.SAAZ.AA 10.0.5.136
111157_ATN_01_CSG_A.HW.Kality.SAAZ.AA 10.0.5.137
111077_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA 10.0.5.141
111417_ATN_01_CSG_A.HW.Kirkos.SAAZ.AA 10.0.5.142
111211_ATN_01_CSG_A.HW.Lebu.SAAZ.AA 10.0.5.143
111212_ATN_01_CSG_A.HW.Lebu.SAAZ.AA 10.0.5.144
111070_ATN_01_CSG_A.HW.NifasSilk.SAAZ.AA 10.0.5.145
111302_ATN_01_CSG_A.HW.AyerTena.SWAAZ.AA 10.0.5.149
111169_ATN_01_CSG_A.HW.Keranio.SWAAZ.AA 10.0.5.150
-109-
111122_ATN_01_CSG_A.HW.Mekanism.SWAAZ.AA 10.0.5.161
111121_ATN_01_CSG_A.HW.OldAirport.SWAAZ.AA 10.0.5.164
111001_ATN_01_CSG_A.HW.Ketema.WAAZ.AA 10.0.5.170
111067_ATN_01_CSG_A.HW.Asko.WAAZ.AA 10.0.5.178
111182_ATN_01_CSG_A.HW.Kolfe.WAAZ.AA 10.0.5.182
111078_ATN_01_CSG_A.HW.Shegole.WAAZ.AA 10.0.5.188
111276_ATN_01_CSG_A.HW.Shegole.WAAZ.AA 10.0.5.189
6.1.2 Designing Interconnected interfaces
Design Guidelines
 The address of an interconnected interface uses a 30-bit mask.
 The addresses of interconnected interfaces are allocated from the aggregation layer, then the
-110-
access layer. The values are in ascending order.
 Main interfaces are used as the interconnected interfaces between ASG pairs for
aggregation-layer ISIS processes. Sub-interfaces are enabled for all access-layer ISIS processes.
Each sub-interface joins the corresponding process to ensure that each area is a closed loop.
 RSGs are interconnected with RNCs through VLANIF interfaces. Issue the port-switch command
to the main interfaces and then configure sub-interfaces between RSGs for IGP establishment. Then,
configure IP connections on the aggregation ring.
Source NE Port Name Source IP Destination NE Port Name Destination IP

111128_CX_01_ASG_A.HW.OldA 111176_CX_02_ASG_B.H
irport.SWAAZ.AA Eth-Trunk4 10.1.23.1 W.Karanyo.SWAAZ.AA Eth-Trunk4 10.1.23.2
111176_CX_02_ASG_B.HW.Kara 111176_CX_01_ASG_A.H
nyo.SWAAZ.AA Eth-Trunk1 10.1.23.5 W.Karanyo.SWAAZ.AA Eth-Trunk1 10.1.23.6
111176_CX_01_ASG_A.HW.Kara 111205_CX_02_ASG_B.H
nyo.SWAAZ.AA Eth-Trunk2 10.1.23.9 W.Mekanisa.SWAAZ.AA Eth-Trunk2 10.1.23.10
111205_CX_02_ASG_B.HW.Meka 111205_CX_01_ASG_A.H
nisa.SWAAZ.AA Eth-Trunk1 10.1.23.13 W.Mekanisa.SWAAZ.AA Eth-Trunk1 10.1.23.14
111205_CX_01_ASG_A.HW.Meka 111128_CX_02_ASG_B.H
nisa.SWAAZ.AA Eth-Trunk4 10.1.23.17 W.OldAirport.SWAAZ.AA Eth-Trunk4 10.1.23.18
111168_CX_01_RSG_A.HW.Kirk Eth-Trunk1. 111168_CX_02_RSG_B.H Eth-Trunk1.
os.SAAZ.AA 100 10.1.23.21 W.Kirkos.SAAZ.AA 100 10.1.23.22
111168_CX_02_RSG_B.HW.Kirko 111007_CX_01_RSG_A.H
s.SAAZ.AA Eth-Trunk2 10.1.23.25 W.NifasSilk.SAAZ.AA Eth-Trunk2 10.1.23.26
111007_CX_01_RSG_A.HW.Nifas Eth-Trunk1. 111007_CX_02_RSG_B.H Eth-Trunk1.
Silk.SAAZ.AA 100 10.1.23.29 W.NifasSilk.SAAZ.AA 100 10.1.23.30
111007_CX_02_RSG_B.HW.Nifas 111136_CX_01_RSG_A.H
Silk.SAAZ.AA Eth-Trunk2 10.1.23.33 W.Bole.EAAZ.AA Eth-Trunk2 10.1.23.34
111136_CX_01_RSG_A.HW.Bole. Eth-Trunk1. 111136_CX_02_RSG_B.H Eth-Trunk1.
EAAZ.AA 100 10.1.23.37 W.Bole.EAAZ.AA 100 10.1.23.38
111136_CX_02_RSG_B.HW.Bole. 111058_CX_01_ASG_A.H
EAAZ.AA Eth-Trunk2 10.1.23.41 W.Filowaha.CAAZ.AA Eth-Trunk2 10.1.23.42
111058_CX_01_ASG_A.HW.Filo 111058_CX_02_ASG_B.H
waha.CAAZ.AA Eth-Trunk1 10.1.23.45 W.Filowaha.CAAZ.AA Eth-Trunk1 10.1.23.46
111058_CX_02_ASG_B.HW.Filo 111051_CX_01_RSG_A.H
waha.CAAZ.AA Eth-Trunk2 10.1.23.49 W.Microwave.CAAZ.AA Eth-Trunk2 10.1.23.50
111051_CX_01_RSG_A.HW.Micr Eth-Trunk1. 111051_CX_02_RSG_B.H Eth-Trunk1.
owave.CAAZ.AA 100 10.1.23.53 W.Microwave.CAAZ.AA 100 10.1.23.54
111051_CX_02_RSG_B.HW.Micr 111128_CX_01_ASG_A.H
owave.CAAZ.AA Eth-Trunk2 10.1.23.57 W.OldAirport.SWAAZ.AA Eth-Trunk2 10.1.23.58
111128_CX_01_ASG_A.HW.OldA Eth-Trunk1 10.1.23.61 111128_CX_02_ASG_B.H Eth-Trunk1 10.1.23.62
-111-
irport.SWAAZ.AA W.OldAirport.SWAAZ.AA
111128_CX_02_ASG_B.HW.OldA 111168_CX_01_RSG_A.H
irport.SWAAZ.AA Eth-Trunk2 10.1.23.65 W.Kirkos.SAAZ.AA Eth-Trunk2 10.1.23.66
111007_CX_01_RSG_A.HW.Nifas 111120_CX_02_ASG_B.H
Silk.SAAZ.AA Eth-Trunk4 10.1.23.69 W.HannaMariam.SAAZ.AA Eth-Trunk4 10.1.23.70
111120_CX_02_ASG_B.HW.Hann 111120_CX_01_ASG_A.H
aMariam.SAAZ.AA Eth-Trunk1 10.1.23.73 W.HannaMariam.SAAZ.AA Eth-Trunk1 10.1.23.74
111120_CX_01_ASG_A.HW.Hann 111228_CX_02_ASG_B.H
aMariam.SAAZ.AA Eth-Trunk2 10.1.23.77 W.Lebu.SAAZ.AA Eth-Trunk2 10.1.23.78
111228_CX_02_ASG_B.HW.Lebu. 111228_CX_01_ASG_A.H
SAAZ.AA Eth-Trunk1 10.1.23.81 W.Lebu.SAAZ.AA Eth-Trunk1 10.1.23.82
111228_CX_01_ASG_A.HW.Lebu 111767_CX_02_ASG_B.H
.SAAZ.AA Eth-Trunk2 10.1.23.85 W.Kality.SAAZ.AA Eth-Trunk2 10.1.23.86
111767_CX_02_ASG_B.HW.Kalit 111767_CX_01_ASG_A.H
y.SAAZ.AA Eth-Trunk1 10.1.23.89 W.Kality.SAAZ.AA Eth-Trunk1 10.1.23.90
111767_CX_01_ASG_A.HW.Kalit 111408_CX_02_ASG_B.H
y.SAAZ.AA Eth-Trunk2 10.1.23.93 W.Akaki.SAAZ.AA Eth-Trunk2 10.1.23.94
111408_CX_02_ASG_B.HW.Akak 111408_CX_01_ASG_A.H
i.SAAZ.AA Eth-Trunk1 10.1.23.97 W.Akaki.SAAZ.AA Eth-Trunk1 10.1.23.98
111408_CX_01_ASG_A.HW.Akak 111010_CX_02_ASG_B.H
i.SAAZ.AA Eth-Trunk4 10.1.23.101 W.BoleMichael.EAAZ.AA Eth-Trunk4 10.1.23.102
111010_CX_02_ASG_B.HW.Bole 111010_CX_01_ASG_A.H
Michael.EAAZ.AA Eth-Trunk1 10.1.23.105 W.BoleMichael.EAAZ.AA Eth-Trunk1 10.1.23.106
111010_CX_01_ASG_A.HW.Bole 111007_CX_02_RSG_B.H
Michael.EAAZ.AA Eth-Trunk4 10.1.23.109 W.NifasSilk.SAAZ.AA Eth-Trunk4 10.1.23.110
111057_CX_01_ASG_A.HW.Kete 111124_CX_02_ASG_B.H
ma.WAAZ.AA Eth-Trunk4 10.1.23.113 W.Shegole.WAAZ.AA Eth-Trunk4 10.1.23.114
111124_CX_02_ASG_B.HW.Sheg 111124_CX_01_ASG_A.H
ole.WAAZ.AA Eth-Trunk1 10.1.23.117 W.Shegole.WAAZ.AA Eth-Trunk1 10.1.23.118
111124_CX_01_ASG_A.HW.Sheg 111163_CX_02_ASG_B.H
ole.WAAZ.AA Eth-Trunk2 10.1.23.121 W.Asko.WAAZ.AA Eth-Trunk2 10.1.23.122
111163_CX_02_ASG_B.HW.Asko 111163_CX_01_ASG_A.H
.WAAZ.AA Eth-Trunk1 10.1.23.125 W.Asko.WAAZ.AA Eth-Trunk1 10.1.23.126
111163_CX_01_ASG_A.HW.Asko 117001_CX_02_ASG_B.H
.WAAZ.AA Eth-Trunk2 10.1.23.129 W.Burau.WAAZ.AA Eth-Trunk2 10.1.23.130
117001_CX_02_ASG_B.HW.Bura 117001_CX_01_ASG_A.H
u.WAAZ.AA Eth-Trunk1 10.1.23.133 W.Burau.WAAZ.AA Eth-Trunk1 10.1.23.134
117001_CX_01_ASG_A.HW.Bura 111030_CX_02_ASG_B.H
u.WAAZ.AA Eth-Trunk2 10.1.23.137 W.Kolfe.WAAZ.AA Eth-Trunk2 10.1.23.138
111030_CX_02_ASG_B.HW.Kolfe 111030_CX_01_ASG_A.H
.WAAZ.AA Eth-Trunk1 10.1.23.141 W.Kolfe.WAAZ.AA Eth-Trunk1 10.1.23.142
111030_CX_01_ASG_A.HW.Kolfe 111057_CX_02_ASG_B.H
.WAAZ.AA Eth-Trunk4 10.1.23.145 W.Ketema.WAAZ.AA Eth-Trunk4 10.1.23.146
-112-
111136_CX_01_RSG_A.HW.Bole. 111082_CX_01_ASG_A.H
EAAZ.AA Eth-Trunk6 10.1.23.149 W.Yeka.EAAZ.AA Eth-Trunk6 10.1.23.150
111082_CX_01_ASG_A.HW.Yeka 111082_CX_02_ASG_B.H
.EAAZ.AA Eth-Trunk1 10.1.23.153 W.Yeka.EAAZ.AA Eth-Trunk1 10.1.23.154
111082_CX_02_ASG_B.HW.Yeka 111148_CX_01_ASG_A.H
.EAAZ.AA Eth-Trunk2 10.1.23.157 W.SidistKilo.NAAZ.AA Eth-Trunk2 10.1.23.158
111148_CX_01_ASG_A.HW.Sidis 111148_CX_02_ASG_B.H
tKilo.NAAZ.AA Eth-Trunk1 10.1.23.161 W.SidistKilo.NAAZ.AA Eth-Trunk1 10.1.23.162
111148_CX_02_ASG_B.HW.Sidist 111055_CX_01_RSG_A.H
Kilo.NAAZ.AA Eth-Trunk2 10.1.23.165 W.Arada.NAAZ.AA Eth-Trunk2 10.1.23.166
111055_CX_01_RSG_A.HW.Arad Eth-Trunk1. 111055_CX_02_RSG_B.H Eth-Trunk1.
a.NAAZ.AA 100 10.1.23.169 W.Arada.NAAZ.AA 100 10.1.23.170
111055_CX_02_RSG_B.HW.Arad 111057_CX_01_ASG_A.H
a.NAAZ.AA Eth-Trunk2 10.1.23.173 W.Ketema.WAAZ.AA Eth-Trunk2 10.1.23.174
111057_CX_01_ASG_A.HW.Kete 111057_CX_02_ASG_B.H
ma.WAAZ.AA Eth-Trunk1 10.1.23.177 W.Ketema.WAAZ.AA Eth-Trunk1 10.1.23.178
111057_CX_02_ASG_B.HW.Kete 111051_CX_02_RSG_B.H
ma.WAAZ.AA Eth-Trunk6 10.1.23.181 W.Microwave.CAAZ.AA Eth-Trunk6 10.1.23.182
111161_CX_02_ASG_B.H
111055_CX_01_RSG_A.HW.Arad W.Ferensailegasion.NAAZ.
a.NAAZ.AA Eth-Trunk4 10.1.23.185 AA Eth-Trunk4 10.1.23.186
111161_CX_01_ASG_A.H
111161_CX_02_ASG_B.HW.Feren W.Ferensailegasion.NAAZ.
sailegasion.NAAZ.AA Eth-Trunk1 10.1.23.189 AA Eth-Trunk1 10.1.23.190
111161_CX_01_ASG_A.HW.Feren 111038_CX_02_ASG_B.H
sailegasion.NAAZ.AA Eth-Trunk2 10.1.23.193 W.Gebeya.NAAZ.AA Eth-Trunk2 10.1.23.194
111038_CX_02_ASG_B.HW.Gebe 111038_CX_01_ASG_A.H
ya.NAAZ.AA Eth-Trunk1 10.1.23.197 W.Gebeya.NAAZ.AA Eth-Trunk1 10.1.23.198
111038_CX_01_ASG_A.HW.Gebe 111055_CX_02_RSG_B.H
ya.NAAZ.AA Eth-Trunk4 10.1.23.201 W.Arada.NAAZ.AA Eth-Trunk4 10.1.23.202
111082_CX_01_ASG_A.HW.Yeka 111089_CX_02_ASG_B.H
.EAAZ.AA Eth-Trunk4 10.1.23.205 W.Gerji.EAAZ.AA Eth-Trunk4 10.1.23.206
111089_CX_02_ASG_B.HW.Gerji. 111089_CX_01_ASG_A.H
EAAZ.AA Eth-Trunk1 10.1.23.209 W.Gerji.EAAZ.AA Eth-Trunk1 10.1.23.210
111089_CX_01_ASG_A.HW.Gerji 111165_CX_02_ASG_B.H
.EAAZ.AA Eth-Trunk2 10.1.23.213 W.Ayat.EAAZ.AA Eth-Trunk2 10.1.23.214
111165_CX_02_ASG_B.HW.Ayat. 111165_CX_01_ASG_A.H
EAAZ.AA Eth-Trunk1 10.1.23.217 W.Ayat.EAAZ.AA Eth-Trunk1 10.1.23.218
111165_CX_01_ASG_A.HW.Ayat. 111086_CX_02_ASG_B.H
EAAZ.AA Eth-Trunk2 10.1.23.221 W.Kotebe.EAAZ.AA Eth-Trunk2 10.1.23.222
111086_CX_02_ASG_B.HW.Kote 111086_CX_01_ASG_A.H
be.EAAZ.AA Eth-Trunk1 10.1.23.225 W.Kotebe.EAAZ.AA Eth-Trunk1 10.1.23.226
111086_CX_01_ASG_A.HW.Kote Eth-Trunk4 10.1.23.229 111082_CX_02_ASG_B.H Eth-Trunk4 10.1.23.230
-113-
be.EAAZ.AA W.Yeka.EAAZ.AA
111057_CX_01_ASG_A.HW.Kete 111404_ATN_01_CSG_A.
ma.WAAZ.AA XGE8/0/2 10.1.24.1 HW.Ketema.WAAZ.AA XGE0/5/0 10.1.24.2
111057_CX_02_ASG_B.HW.Kete 111131_ATN_01_CSG_A.
111131_ATN_01_CSG_A.HW.Ket 111080_ATN_01_CSG_A.
ema.WAAZ.AA XGE0/6/0 10.1.24.21 HW.Ketema.WAAZ.AA XGE0/5/0 10.1.24.22
111159_ATN_01_CSG_A.HW.Ket 111081_ATN_01_CSG_A.
ema.WAAZ.AA XGE0/6/0 10.1.24.29 HW.Ketema.WAAZ.AA XGE0/5/0 10.1.24.30
111408_CX_02_ASG_B.HW.Akak 111034_ATN_01_CSG_A.
i.SAAZ.AA XGE8/0/2 10.1.24.37 HW.Akaki.SAAZ.AA XGE0/5/0 10.1.24.38
111055_CX_01_RSG_A.HW.Arad 111274_ATN_01_CSG_A.
a.NAAZ.AA XGE8/0/2 10.1.24.41 HW.Arada.NAAZ.AA XGE0/5/0 10.1.24.42
111274_ATN_01_CSG_A.HW.Ara 111069_ATN_01_CSG_A.
da.NAAZ.AA XGE0/6/0 10.1.24.45 HW.Arada.NAAZ.AA XGE0/5/0 10.1.24.46
111075_ATN_01_CSG_A.HW.Ara 111055_CX_02_RSG_B.H
da.NAAZ.AA XGE0/6/0 10.1.24.61 W.Arada.NAAZ.AA XGE8/0/2 10.1.24.62
111055_CX_02_RSG_B.HW.Arad 111420_ATN_01_CSG_A.
111055_CX_02_RSG_B.HW.Arad 111004_ATN_01_CSG_A.
111055_CX_01_RSG_A.HW.Arad Eth-Trunk1. 111055_CX_02_RSG_B.H Eth-Trunk1.
a.NAAZ.AA 1 10.1.24.77 W.Arada.NAAZ.AA 1 10.1.24.78
111163_CX_01_ASG_A.HW.Asko 111048_ATN_01_CSG_A.
.WAAZ.AA XGE8/0/2 10.1.24.81 HW.Asko.WAAZ.AA XGE0/5/0 10.1.24.82
111048_ATN_01_CSG_A.HW.Ask 111063_ATN_01_CSG_A.
o.WAAZ.AA XGE0/6/0 10.1.24.85 HW.Asko.WAAZ.AA XGE0/5/0 10.1.24.86
111163_CX_02_ASG_B.HW.Asko 111067_ATN_01_CSG_A.
-114-
111163_CX_02_ASG_B.HW.Asko 111062_ATN_01_CSG_A.
111165_CX_01_ASG_A.HW.Ayat. 111407_ATN_01_CSG_A.
EAAZ.AA XGE8/0/2 10.1.24.97 HW.Ayat.EAAZ.AA XGE0/5/0 10.1.24.98
111399_ATN_01_CSG_A.
111010_CX_01_ASG_A.HW.Bole HW.Bole
Michael.EAAZ.AA XGE8/0/2 10.1.24.101 Michael.EAAZ.AA XGE0/5/0 10.1.24.102
111136_CX_01_RSG_A.HW.Bole. 111421_ATN_01_CSG_A.
EAAZ.AA XGE8/0/0 10.1.24.105 HW.Bole.EAAZ.AA XGE0/5/0 10.1.24.106
111421_ATN_01_CSG_A.HW.Bol 111074_ATN_01_CSG_A.
e.EAAZ.AA XGE0/6/0 10.1.24.109 HW.Bole.EAAZ.AA XGE0/5/0 10.1.24.110
111397_ATN_01_CSG_A.HW.Bol 111136_CX_02_RSG_B.H
e.EAAZ.AA XGE0/6/0 10.1.24.133 W.Bole.EAAZ.AA XGE8/0/0 10.1.24.134
111136_CX_01_RSG_A.HW.Bole. 111065_ATN_01_CSG_A.
111136_CX_02_RSG_B.HW.Bole. 111277_ATN_01_CSG_A.
111136_CX_01_RSG_A.HW.Bole. Eth-Trunk1. 111136_CX_02_RSG_B.H Eth-Trunk1.
EAAZ.AA 1 10.1.24.149 W.Bole.EAAZ.AA 1 10.1.24.150
111058_CX_01_ASG_A.HW.Filo 111396_ATN_01_CSG_A.
waha.CAAZ.AA XGE8/0/0 10.1.24.157 HW.Filowoha.CAAZ.AA XGE0/5/0 10.1.24.158
111396_ATN_01_CSG_A.HW.Filo 111405_ATN_01_CSG_A.
woha.CAAZ.AA XGE0/6/0 10.1.24.161 HW.Filowoha.CAAZ.AA XGE0/5/0 10.1.24.162
111202_ATN_01_CSG_A.HW.Filo 111058_CX_02_ASG_B.H
woha.CAAZ.AA XGE0/6/0 10.1.24.177 W.Filowaha.CAAZ.AA XGE8/0/0 10.1.24.178
-115-
111058_CX_01_ASG_A.HW.Filo Eth-Trunk1. 111058_CX_02_ASG_B.H Eth-Trunk1.

waha.CAAZ.AA 1 10.1.24.181 W.Filowaha.CAAZ.AA 1 10.1.24.182
111089_CX_01_ASG_A.HW.Gerji 111125_ATN_01_CSG_A.
.EAAZ.AA XGE8/0/2 10.1.25.1 HW.Gerji.EAAZ.AA XGE0/5/0 10.1.25.2
111125_ATN_01_CSG_A.HW.Ger 111164_ATN_01_CSG_A.
ji.EAAZ.AA XGE0/6/0 10.1.25.5 HW.Gerji.EAAZ.AA XGE0/5/0 10.1.25.6
111164_ATN_01_CSG_A.HW.Ger 111089_CX_02_ASG_B.H
ji.EAAZ.AA XGE0/6/0 10.1.25.9 W.Gerji.EAAZ.AA XGE8/0/2 10.1.25.10
111089_CX_02_ASG_B.HW.Gerji. Eth-Trunk1. 111089_CX_01_ASG_A.H Eth-Trunk1.
EAAZ.AA 1 10.1.25.13 W.Gerji.EAAZ.AA 1 10.1.25.14
111089_CX_02_ASG_B.HW.Gerji. 111095_ATN_01_CSG_A.
EAAZ.AA XGE8/0/3 10.1.25.17 HW.Gerji.EAAZ.AA XGE0/5/0 10.1.25.18
111173_ATN_01_CSG_A.
111120_CX_01_ASG_A.HW.Hann HW.HannaMariam.SAAZ.A
aMariam.SAAZ.AA XGE8/0/2 10.1.25.21 A XGE0/5/0 10.1.25.22
111156_ATN_01_CSG_A.
111120_CX_02_ASG_B.HW.Hann HW.HannaMariam.SAAZ.A
aMariam.SAAZ.AA XGE8/0/2 10.1.25.25 A XGE0/5/0 10.1.25.26
111767_CX_01_ASG_A.HW.Kalit 111196_ATN_01_CSG_A.
y.SAAZ.AA XGE8/0/2 10.1.25.29 HW.Kality.SAAZ.AA XGE0/5/0 10.1.25.30
111196_ATN_01_CSG_A.HW.Kal 111073_ATN_01_CSG_A.
ity.SAAZ.AA XGE0/6/0 10.1.25.33 HW.Kality.SAAZ.AA XGE0/5/0 10.1.25.34
111073_ATN_01_CSG_A.HW.Kal XGE0/6/0 10.1.25.37 111072_ATN_01_CSG_A. XGE0/5/0 10.1.25.38
-116-
ity.SAAZ.AA HW.Kality.SAAZ.AA
111072_ATN_01_CSG_A.HW.Kal 111157_ATN_01_CSG_A.
ity.SAAZ.AA XGE0/6/0 10.1.25.41 HW.Kality.SAAZ.AA XGE0/5/0 10.1.25.42
111157_ATN_01_CSG_A.HW.Kal 111767_CX_02_ASG_B.H
ity.SAAZ.AA XGE0/6/0 10.1.25.45 W.Kality.SAAZ.AA XGE8/0/2 10.1.25.46
111767_CX_02_ASG_B.HW.Kalit Eth-Trunk1. 111767_CX_01_ASG_A.H Eth-Trunk1.
y.SAAZ.AA 1 10.1.25.49 W.Kality.SAAZ.AA 1 10.1.25.50
111176_CX_01_ASG_A.HW.Kara 111214_ATN_01_CSG_A.
nyo.SWAAZ.AA XGE8/0/2 10.1.25.53 HW.Keranio.SWAAZ.AA XGE0/5/0 10.1.25.54
111214_ATN_01_CSG_A.HW.Ker 111171_ATN_01_CSG_A.
anio.SWAAZ.AA XGE0/6/0 10.1.25.57 HW.Keranio.SWAAZ.AA XGE0/5/0 10.1.25.58
111427_ATN_01_CSG_A.HW.Ker 111176_CX_02_ASG_B.H
anio.SWAAZ.AA XGE0/6/0 10.1.25.69 W.Karanyo.SWAAZ.AA XGE8/0/2 10.1.25.70
111176_CX_02_ASG_B.HW.Kara Eth-Trunk1. 111176_CX_01_ASG_A.H Eth-Trunk1.
nyo.SWAAZ.AA 1 10.1.25.77 W.Karanyo.SWAAZ.AA 1 10.1.25.78
nyo.SWAAZ.AA XGE8/0/3 10.1.25.81 HW.Keranio.SWAAZ.AA XGE0/5/0 10.1.25.82
nyo.SWAAZ.AA XGE8/0/4 10.1.25.85 HW.AyerTena.SWAAZ.AA XGE0/5/0 10.1.25.86
111168_CX_01_RSG_A.HW.Kirk 111077_ATN_01_CSG_A.
os.SAAZ.AA XGE8/0/0 10.1.25.89 HW.Kirkos.SAAZ.AA XGE0/5/0 10.1.25.90
111168_CX_02_RSG_B.HW.Kirko 111417_ATN_01_CSG_A.
s.SAAZ.AA XGE8/0/0 10.1.25.93 HW.Kirkos.SAAZ.AA XGE0/5/0 10.1.25.94
111168_CX_01_RSG_A.HW.Kirk Eth-Trunk1. 111168_CX_02_RSG_B.H Eth-Trunk1.
os.SAAZ.AA 1 10.1.25.97 W.Kirkos.SAAZ.AA 1 10.1.25.98
111030_CX_01_ASG_A.HW.Kolfe 111158_ATN_01_CSG_A.
.WAAZ.AA XGE8/0/2 10.1.25.101 HW.Kolfe.WAAZ.AA XGE0/5/0 10.1.25.102
111158_ATN_01_CSG_A.HW.Kol 111160_ATN_01_CSG_A.
fe.WAAZ.AA XGE0/6/0 10.1.25.105 HW.Kolfe.WAAZ.AA XGE0/5/0 10.1.25.106
111394_ATN_01_CSG_A.HW.Kol 111030_CX_02_ASG_B.H
fe.WAAZ.AA XGE0/6/0 10.1.25.117 W.Kolfe.WAAZ.AA XGE8/0/2 10.1.25.118
111030_CX_02_ASG_B.HW.Kolfe Eth-Trunk1. 111030_CX_01_ASG_A.H Eth-Trunk1.
.WAAZ.AA 1 10.1.25.121 W.Kolfe.WAAZ.AA 1 10.1.25.122
-117-
111030_CX_02_ASG_B.HW.Kolfe 111231_ATN_01_CSG_A.
.WAAZ.AA XGE8/0/3 10.1.25.125 HW.Kolfe.WAAZ.AA XGE0/5/0 10.1.25.126
111086_CX_01_ASG_A.HW.Kote 111103_ATN_01_CSG_A.
be.EAAZ.AA XGE8/0/2 10.1.25.133 HW.Kotebe.EAAZ.AA XGE0/5/0 10.1.25.134
111103_ATN_01_CSG_A.HW.Kot 111409_ATN_01_CSG_A.
ebe.EAAZ.AA XGE0/6/0 10.1.25.137 HW.Kotebe.EAAZ.AA XGE0/5/0 10.1.25.138
111230_ATN_01_CSG_A.HW.Kot 111086_CX_02_ASG_B.H
ebe.EAAZ.AA XGE0/6/0 10.1.25.165 W.Kotebe.EAAZ.AA XGE8/0/2 10.1.25.166
111086_CX_02_ASG_B.HW.Kote Eth-Trunk1. 111086_CX_01_ASG_A.H Eth-Trunk1.
be.EAAZ.AA 1 10.1.25.169 W.Kotebe.EAAZ.AA 1 10.1.25.170
111086_CX_01_ASG_A.HW.Kote 111398_ATN_01_CSG_A.
be.EAAZ.AA XGE8/0/3 10.1.25.173 HW.Kotebe.EAAZ.AA XGE0/5/0 10.1.25.174
111097_ATN_01_CSG_A.HW.Kot 111086_CX_02_ASG_B.H
ebe.EAAZ.AA XGE0/6/0 10.1.25.193 W.Kotebe.EAAZ.AA XGE8/0/3 10.1.25.194
111086_CX_02_ASG_B.HW.Kote Eth-Trunk1. 111086_CX_01_ASG_A.H Eth-Trunk1.
be.EAAZ.AA 2 10.1.25.197 W.Kotebe.EAAZ.AA 2 10.1.25.198
111228_CX_01_ASG_A.HW.Lebu 111211_ATN_01_CSG_A.
.SAAZ.AA XGE8/0/2 10.1.25.201 HW.Lebu.SAAZ.AA XGE0/5/0 10.1.25.202
111211_ATN_01_CSG_A.HW.Leb 111212_ATN_01_CSG_A.
u.SAAZ.AA XGE0/6/0 10.1.25.205 HW.Lebu.SAAZ.AA XGE0/5/0 10.1.25.206
111212_ATN_01_CSG_A.HW.Leb XGE0/6/0 10.1.25.209 111228_CX_02_ASG_B.H XGE8/0/2 10.1.25.210
-118-
u.SAAZ.AA W.Lebu.SAAZ.AA
111228_CX_02_ASG_B.HW.Lebu. Eth-Trunk1. 111228_CX_01_ASG_A.H Eth-Trunk1.
SAAZ.AA 1 10.1.25.213 W.Lebu.SAAZ.AA 1 10.1.25.214
111205_CX_01_ASG_A.HW.Meka 111430_ATN_01_CSG_A.
nisa.SWAAZ.AA XGE8/0/3 10.1.26.1 HW.AyerTena.SWAAZ.AA XGE0/5/0 10.1.26.2
111430_ATN_01_CSG_A.HW.Aye 111186_ATN_01_CSG_A.
rTena.SWAAZ.AA XGE0/6/0 10.1.26.5 HW.AyerTena.SWAAZ.AA XGE0/5/0 10.1.26.6
111184_ATN_01_CSG_A.HW.Aye 111205_CX_02_ASG_B.H
rTena.SWAAZ.AA XGE0/6/0 10.1.26.21 W.Mekanisa.SWAAZ.AA XGE8/0/3 10.1.26.22
111205_CX_02_ASG_B.HW.Meka Eth-Trunk1. 111205_CX_01_ASG_A.H Eth-Trunk1.
nisa.SWAAZ.AA 1 10.1.26.25 W.Mekanisa.SWAAZ.AA 1 10.1.26.26
111205_CX_01_ASG_A.HW.Meka 111122_ATN_01_CSG_A.
nisa.SWAAZ.AA XGE8/0/2 10.1.26.29 HW.Mekanism.SWAAZ.AA XGE0/5/0 10.1.26.30
111122_ATN_01_CSG_A.HW.Me 111215_ATN_01_CSG_A.
kanism.SWAAZ.AA XGE0/6/0 10.1.26.33 HW.Mekanism.SWAAZ.AA XGE0/5/0 10.1.26.34
111215_ATN_01_CSG_A.HW.Me 111183_ATN_01_CSG_A.
kanism.SWAAZ.AA XGE0/6/0 10.1.26.37 HW.Mekanism.SWAAZ.AA XGE0/5/0 10.1.26.38
111183_ATN_01_CSG_A.HW.Me 111205_CX_02_ASG_B.H
kanism.SWAAZ.AA XGE0/6/0 10.1.26.41 W.Mekanisa.SWAAZ.AA XGE8/0/2 10.1.26.42
111205_CX_02_ASG_B.HW.Meka Eth-Trunk1. 111205_CX_01_ASG_A.H Eth-Trunk1.
nisa.SWAAZ.AA 2 10.1.26.45 W.Mekanisa.SWAAZ.AA 2 10.1.26.46
111007_CX_01_RSG_A.HW.Nifas 111071_ATN_01_CSG_A.
Silk.SAAZ.AA XGE8/0/2 10.1.26.49 HW.NifasSilk.SAAZ.AA XGE0/5/0 10.1.26.50
111071_ATN_01_CSG_A.HW.Nif 111115_ATN_01_CSG_A.
asSilk.SAAZ.AA XGE0/6/0 10.1.26.53 HW.NifasSilk.SAAZ.AA XGE0/5/0 10.1.26.54
111123_ATN_01_CSG_A.HW.Nif 111007_CX_02_RSG_B.H
asSilk.SAAZ.AA XGE0/6/0 10.1.26.65 W.NifasSilk.SAAZ.AA XGE8/0/2 10.1.26.66
111007_CX_01_RSG_A.HW.Nifas Eth-Trunk1. 111007_CX_02_RSG_B.H Eth-Trunk1.
Silk.SAAZ.AA 1 10.1.26.69 W.NifasSilk.SAAZ.AA 1 10.1.26.70
111216_ATN_01_CSG_A.
111128_CX_01_ASG_A.HW.OldA HW.OldAirport.SWAAZ.A
irport.SWAAZ.AA XGE8/0/2 10.1.26.73 A XGE0/5/0 10.1.26.74
111216_ATN_01_CSG_A.HW.Old XGE0/6/0 10.1.26.77 111121_ATN_01_CSG_A. XGE0/5/0 10.1.26.78
-119-
Airport.SWAAZ.AA HW.OldAirport.SWAAZ.A
A
111172_ATN_01_CSG_A.
111121_ATN_01_CSG_A.HW.Old HW.OldAirport.SWAAZ.A
Airport.SWAAZ.AA XGE0/6/0 10.1.26.81 A XGE0/5/0 10.1.26.82
111190_ATN_01_CSG_A.
111190_ATN_01_CSG_A.HW.Old 111128_CX_02_ASG_B.H
Airport.SWAAZ.AA XGE0/6/0 10.1.26.89 W.OldAirport.SWAAZ.AA XGE8/0/2 10.1.26.90
111128_CX_01_ASG_A.HW.OldA Eth-Trunk1. 111128_CX_02_ASG_B.H Eth-Trunk1.
irport.SWAAZ.AA 1 10.1.26.93 W.OldAirport.SWAAZ.AA 1 10.1.26.94
111213_ATN_01_CSG_A.
111128_CX_01_ASG_A.HW.OldA HW.OldAirport.SWAAZ.A
irport.SWAAZ.AA XGE8/0/3 10.1.26.97 A XGE0/5/0 10.1.26.98
111419_ATN_01_CSG_A.
111419_ATN_01_CSG_A.HW.Old 111128_CX_02_ASG_B.H
Airport.SWAAZ.AA XGE0/6/0 10.1.26.105 W.OldAirport.SWAAZ.AA XGE8/0/3 10.1.26.106
111128_CX_01_ASG_A.HW.OldA Eth-Trunk1. 111128_CX_02_ASG_B.H Eth-Trunk1.
irport.SWAAZ.AA 2 10.1.26.109 W.OldAirport.SWAAZ.AA 2 10.1.26.110
111124_CX_01_ASG_A.HW.Sheg 111276_ATN_01_CSG_A.
ole.WAAZ.AA XGE8/0/2 10.1.26.113 HW.Shegole.WAAZ.AA XGE0/5/0 10.1.26.114
111124_CX_02_ASG_B.HW.Sheg 111078_ATN_01_CSG_A.
ole.WAAZ.AA XGE8/0/2 10.1.26.117 HW.Shegole.WAAZ.AA XGE0/5/0 10.1.26.118
111148_CX_01_ASG_A.HW.Sidis 111204_ATN_01_CSG_A.
tKilo.NAAZ.AA XGE8/0/0 10.1.26.121 HW.SidisKilo.NAAZ.AA XGE0/5/0 10.1.26.122
111204_ATN_01_CSG_A.HW.Sidi 111108_ATN_01_CSG_A.
sKilo.NAAZ.AA XGE0/6/0 10.1.26.125 HW.SidisKilo.NAAZ.AA XGE0/5/0 10.1.26.126
111278_ATN_01_CSG_A.HW.Sidi 111148_CX_02_ASG_B.H
sKilo.NAAZ.AA XGE0/6/0 10.1.26.137 W.SidistKilo.NAAZ.AA XGE8/0/0 10.1.26.138
111148_CX_01_ASG_A.HW.Sidis Eth-Trunk1. 111148_CX_02_ASG_B.H Eth-Trunk1.
tKilo.NAAZ.AA 1 10.1.26.141 W.SidistKilo.NAAZ.AA 1 10.1.26.142
111148_CX_01_ASG_A.HW.Sidis 111046_ATN_01_CSG_A.
tKilo.NAAZ.AA XGE8/0/1 10.1.26.145 HW.SidisKilo.NAAZ.AA XGE0/5/0 10.1.26.146
111066_ATN_01_CSG_A.HW.Sidi XGE0/6/0 10.1.26.153 111076_ATN_01_CSG_A. XGE0/5/0 10.1.26.154
-120-
sKilo.NAAZ.AA HW.SidisKilo.NAAZ.AA
111076_ATN_01_CSG_A.HW.Sidi 111148_CX_02_ASG_B.H
sKilo.NAAZ.AA XGE0/6/0 10.1.26.157 W.SidistKilo.NAAZ.AA XGE8/0/1 10.1.26.158
111148_CX_01_ASG_A.HW.Sidis Eth-Trunk1. 111148_CX_02_ASG_B.H Eth-Trunk1.
tKilo.NAAZ.AA 2 10.1.26.161 W.SidistKilo.NAAZ.AA 2 10.1.26.162
111148_CX_02_ASG_B.HW.Sidist 111207_ATN_01_CSG_A.
Kilo.NAAZ.AA XGE8/0/2 10.1.26.165 HW.SidisKilo.NAAZ.AA XGE0/5/0 10.1.26.166
111148_CX_02_ASG_B.HW.Sidist 111402_ATN_01_CSG_A.
Kilo.NAAZ.AA XGE8/0/3 10.1.26.169 HW.SidisKilo.NAAZ.AA XGE0/5/0 10.1.26.170
111082_CX_01_ASG_A.HW.Yeka 111087_ATN_01_CSG_A.
.EAAZ.AA XGE8/0/2 10.1.26.173 HW.Yeka.EAAZ.AA XGE0/5/0 10.1.26.174
111087_ATN_01_CSG_A.HW.Yek 111083_ATN_01_CSG_A.
a.EAAZ.AA XGE0/6/0 10.1.26.177 HW.Yeka.EAAZ.AA XGE0/5/0 10.1.26.178
111107_ATN_01_CSG_A.HW.Yek 111082_CX_02_ASG_B.H
a.EAAZ.AA XGE0/6/0 10.1.26.197 W.Yeka.EAAZ.AA XGE8/0/2 10.1.26.198
111082_CX_01_ASG_A.HW.Yeka Eth-Trunk1. 111082_CX_02_ASG_B.H Eth-Trunk1.
.EAAZ.AA 1 10.1.26.201 W.Yeka.EAAZ.AA 1 10.1.26.202
111094_ATN_01_CSG_A.HW.Yek 111082_CX_02_ASG_B.H
a.EAAZ.AA XGE0/6/0 10.1.26.233 W.Yeka.EAAZ.AA XGE8/0/3 10.1.26.234
111082_CX_01_ASG_A.HW.Yeka Eth-Trunk1. 111082_CX_02_ASG_B.H Eth-Trunk1.
.EAAZ.AA 2 10.1.26.237 W.Yeka.EAAZ.AA 2 10.1.26.238
-121-
111038_CX_01_ASG_A.HW.Gebe 111060_ATN_01_CSG_A.
ya.NAAZ.AA XGE8/0/2 10.1.27.5 HW.Gebeya.NAAZ.AA XGE0/5/0 10.1.27.6
111038_CX_01_ASG_A.HW.Gebe 111079_ATN_01_CSG_A.
ya.NAAZ.AA XGE8/0/3 10.1.27.9 HW.Gebeya.NAAZ.AA XGE0/5/0 10.1.27.10
111161_CX_02_ASG_B.HW.Feren 111300_ATN_01_CSG_A.
sailegasion.NAAZ.AA XGE8/0/2 10.1.27.13 HW.Ferinas.NAAZ.AA XGE0/5/0 10.1.27.14
6.2 VLAN Planning

6.2.1 Design Guidelines
 Access-layer VLANs indicate service types. To facilitate daily maintenance, the services of the same
type from different base stations are configured with the same VLAN ID. That is, each service
carries a unique VLAN Planning
Table 6- 1 VLAN Planning
Service Type VLAN Range Remark

Abis 100~199 2G Voice ,Media
Iub 200~299 3G Voice ,Media
S1_C 300~399 LTE control plane
S1_U 400~499 LTE data plane
2G/3G/LTE WOAM 500~599 OAM
E&I OAM 600~699 OAM
CS service 700~899 CS
PS service 900~1299 PS
BSC/RNC 1300~1499 Radio
RTN OAM 4000~4094 OAM
Reserved for other service 1500~4000 Reserved
 VLANs between RSGs and RNCs/BSCs do not indicate service types but are configured with
VLANIF interfaces. Keep the VLAN IDs consistent with those of the RNC service gateway.
 The interconnected interfaces between network devices are generally main interfaces and therefore
-122-
do not require VLAN configuration. When sub interfaces need to be differentiated in the IGP
multi-area and multi-process or on a mixture of layers 2 and 3, allocate sub interface IDs in order.
-123-
7 Routing protocol Design
7.1 IS-IS Design

In the hierarchy VPN solutions, IGP can be designed as the IS-IS multi-process or the open shortest
path first (OSPF) single-process and multi-area. This project use the IS-IS multi-process solution for
it’s easy to deployed and convenient for maintenance.
7.1.1 Overview
Figure 7- 1 ISIS design overview
The aggregation and access layers both adopt the IS-IS protocol. The CSGs on an access ring are
configured with an IGP single-process, the ASGs on an aggregation ring are configured with the IGP
processes of all mounted access rings and the aggregation-layer IGP process, and the RSGs are
configured with an aggregation-layer IGP single-process.
 An interface joins the corresponding IS-IS process based on the area where its link belongs.
 Main interfaces are used as the interconnected interfaces between ASG pairs for
aggregation-layer processes. Sub interfaces are enabled for all access-layer processes. Each sub
-124-
interface joins the corresponding process to ensure that each area is a closed loop.
 The loopback addresses of the ASGs are used as LSR IDs and join the aggregation-layer IGP
process. The interconnected interfaces between ASGs are configured with sub interfaces. Each sub
interface joins the corresponding IGP process deployed on the ASGs in order to enjoy a service
forwarding priority.
 Routes are separated by different processes at the access and aggregation layers. If route
information needs to be exchanged as in the public network DCN solution, use the routing policy
deployed on the ASGs to control the aggregation-layer routes learnt by access rings so that the
access rings only learn the routes required by the aggregation-layer area, for example, the U2000
routes.
Figure 7- 2 ISIS process design
 CSG chains will be directly connected to RSG in the Kirkos/Bole/Arada, and In order to establish
the IBGP PEER and LSP with the primary and secondary RSGs, the sub interface between RSG
pairs which is recommend to be built and all the direct-connected CSGs need to be deployed in same
IGP process as the figure above shows. We suggest to build a new fiber from D-CSG to RSG site as
a ring topology to provide high reliability.
7.1.2 Designing Basic Functions

Table 7- 1 Basic Functions design
Parameter Design Guidelines
-125-
IS-IS process ID This parameter starts with 1 at the access layer, and 100 at the
aggregation layer.
Router ID This parameter takes the address of Loopback0.
Network entity name This parameter is in the format of Area address.System ID.SEL. The
area address is 1 to 13 bytes long, the system ID is 6 byes long, and
SEL(SEL:The role of an SEL is similar to that of the "protocol
identifier" of IP. A transport protocol matches an SEL. The SEL is
always "00" in IP.) is 00.
1. The area ID is designed as 25.(1 + ProcessID).just like
25.1001 which isis process id is 1.
2. The system ID must be unique on the entire network. Obtain
the system ID using the IP address of the loopback0 interface. Take
the IP address 10.11.101.1 for example. Extend each decimal digit
of the IP address to three bits by adding 0s. Then, the IP address
becomes 010.011.101.001. Finally, divide the IP address into three
parts to get the system ID, that is, 0100.1110.1001.
3. If multiple access rings are connected to an ASG pair, deploy
multiple IS-IS processes. It is recommended that the system ID be
unique for each process. You can use the process ID and loopback
IP address for planning the Network entity name, with the process
ID being high-order bits and the loopback IP address being
low-order bits. Currently, For example. There are 2 access ring
connet to ASG pair, the isis processid for the first access ring is 1,
and the high-order bit of the Network entity name will be 1.
Route grade Level-2
is-name Sysname recommended or user-defined
Cost type Wide (compatible with TE deployment, recommended)
Fast Convergence (FC)
Label switched path Enable the level-2 LSP fast flooding function.
(LSP) fast flooding
LSP generation The maximum delay is 1s and the initial delay is 50 ms. The delay
intelligent timer increases by 50 ms each time.
-126-
SPF intelligent timer The maximum delay is 1s and the initial delay is 50 ms. The delay
increases by 50 ms each time.
Bidirectional forwarding It is recommended to enable the function.
detection (BFD) Principle for setting the detection period:
TE: 100 ms x 3 for access/aggregation sides
LDP: 30 ms x 3 for the access side, and 100 msx3 for the
aggregation side
Stability
Overload flag bit This parameter takes the value on-startup to ensure IGP
convergence synchronization when different devices are restarted
synchronously. Routes advertised by a device are not preferred
within the specified timeout duration (600s by default) after the
device is restarted.
Graceful restart (GR) Disabled. Use the non-stop routing (NSR) function, instead.
7.1.3 Designing IS-IS Cost

IGP is configured to ensure that IP protocol signaling routes are preferentially forwarded in a local
access ring or aggregation ring, instead of traversing between ASGs or RSGs. The following Figure
shows the IGP design guidelines for access and aggregation rings.
Figure 7- 3 ISIS cost design
 The default cost of an access-layer link is 100.
-127-
 The cost of the sub interface between an ASG pair is larger than the metric of the entire access
ring. Assume that one access ring covers no more than 20 nodes, the cost of the link between the
ASG pair should be larger than 2000.
 The default cost of an aggregation-layer link (including links between ASG/RSG and P devices)
using IS-IS is 10. So in the aggregation ring the LDP LSP depend on the number of the hops
between Routers effectively. The MPLS TE will be deployed in this network to carry on the mobile
service. Explicit path will be used for the aggregation ring.
7.1.4 Configure Example for ISIS

Figure 7- 4 Configure example topology
Note: In this document, we define P node as one or more routers in the IP RAN network that
interface with ASG, CSG and RSG
The configuration principle is as follows:
 In the access area, enable IS-IS on routers, with IS-IS process 1 used and Level 2 routes
advertised.
 In the aggregation area, enable IS-IS on routers, with IS-IS process 100 used and Level 2 routes
advertised.
 When the loopback0 address is used as the LSR ID, advertise the LSR IDs of ASGs to the IS-IS
process of the aggregation area. The access ring also uses the LSR IDs of ASGs. Configure direct
route import on the master and slave ASGs, and configure a routing policy to import routes of the
-128-
local loopback0 interface to IS-IS process 1 of the access area. In this example, the cost value of
imported routes is 10000.
 Deploy BFD for ISIS on the access ring and aggregation ring. Set the BFD detection period as
100 ms.
 The cost values of the interface links in the access area use 100 and in the aggregation area use
the value 10.
 The access link between the master and slave ASGs must have a larger cost value than the
maximum metric value for the access ring. The cost value can be set to 2000 if there are no more
than 20 nodes on the access ring.
CSG(125D-CSG)：
#
isis 1
is-level level-2 //Configure the device as a Level-2 router.
cost-style wide
timer lsp-generation 1 50 50 level-2 //Set the delay in generating LSPs.
flash-flood level-2 //Enable LSP fast flooding to speed up IS-IS network convergence.
bfd all-interfaces enables //Configure BFD for IS-IS. The detection period is 10 ms.
bfd all-interfaces min-tx-interval 100 min-rx-interval 100
network-entity 25.1001.0100.0000.5140.00 //Configure NET.
is-name CSG-33N //Configure a dynamic host name for IS-IS processes.
timer spf 1 50 50 //Configure the delay in route computation using SPF.
traffic-eng level-2
log-peer-change //Turn on the IS-IS peer state change output switch
set-overload on-startup
//Set IS-IS processes to be in the overload state when IS-IS processes start up
#
interface GigabitEthernet0/5/0
ip address 10.1.25.30 255.255.255.252
isis enable 1 //Enable IS-IS on the interface.
isis cost 100 //Set the cost value of the interface.
#
-129-
ip address 10.1.25.33 255.255.255.252

isis enable 1
#
interface LoopBack0
ip address 10.0.5.140 255.255.255.255
isis enable 1
#
ASG(Kality-ASG-A):
#
switchover mode nonstop-routing //Enable the CX device to support NSR. ATN devices
enable NSR by default.
#
ip ip-prefix LoopBack0 index 10 permit 10.0.5.33 32
#
//Configure a routing policy that matches ip ip-prefix LoopBack0 to permit the route of
loopback0 to pass.
route-policy LoopBack0 permit node 10
if-match ip-prefix LoopBack0
#
isis 100
is-level level-2
cost-style wide
timer lsp-generation 1 50 50 level-2
flash-flood level-2
bfd all-interfaces enable
network-entity 25.1100.0100.0000.5033.00
is-name Kaility-ASG-A
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
interface Eth-trunk 1
-130-
ip address 10.1.23.90 255.255.255.252

isis enable 100
isis cost 10
#
iinterface GigabitEthernet2/0/0
eth-trunk 1
#
eth-trunk 1
#
ip address 10.1.23.93 255.255.255.252
isis enable 100
isis cost 10
#
eth-trunk 2
#
eth-trunk 2
#
interface LoopBack0
ip address 10.0.5.33 255.255.255.255
isis enable 100
#
isis 1 //Configure an IS-IS process on the access ring.
is-level level-2
cost-style wide
flash-flood level-2
network-entity 25.1001.0100.0000.5033.00
import-route direct cost 10000 route-policy LoopBack0
-131-
//Import the loopback0 routes to IS-IS 1.

is-name Kaility-ASG-A
timer spf 1 50 50
traffic-eng level-2
log-peer-change
set-overload on-startup allow external
#
interface Eth-trunk 1.1
ip address 10.1.25.50 255.255.255.252
isis enable 1
isis cost 2000
#
interface GigabitEthernet 8/0/2
ip address 10.1.25.29 255.255.255.252
isis enable 1
isis cost 100
#
ASG(Kality-ASG-B):
#
switchover mode nonstop-routing
//Enable the CX device to support NSR. ATN devices enable NSR by default.
#
ip ip-prefix LoopBack0 index 10 permit 10.0.5.34 32
#
route-policy LoopBack0 permit node 10
if-match ip-prefix LoopBack0
#
isis 100
is-level level-2
cost-style wide
flash-flood level-2
-132-
network-entity 25.1100.0100.0000.5034.00
is-name Kaility-ASG-B
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
ip address 10.1.23.89 255.255.255.252
isis enable 100
isis cost 10
#
iinterface GigabitEthernet2/0/0
eth-trunk 1
#
eth-trunk 1
#
ip address 10.1.23.86 255.255.255.252
isis enable 100
isis cost 10
#
eth-trunk 2
#
eth-trunk 2
#
interface LoopBack0
ip address 10.0.5.34 255.255.255.255
isis enable 100
#
isis 1 //Configure an IS-IS process on the access ring.
-133-
is-level level-2
cost-style wide
flash-flood level-2
network-entity 25.1001.0100.0000.5034.00
import-route direct cost 10000 route-policy LoopBack0
//Import the loopback0 routes with the cost of 10000 to IS-IS 1.
is-name Kaility-ASG-B
timer spf 1 50 50
traffic-eng level-2
log-peer-change
set-overload on-startup allow external
#
ip address 10.1.25.49 255.255.255.252
isis enable 1
isis cost 2000
#
ip address 10.1.25.46 255.255.255.252
isis enable 1
isis cost 100
#
RSG(Nifas Silk-RSG-A)：
#
#
isis 100
is-level level-2
cost-style wide
flash-flood level-2
-134-

network-entity 25.1100.0100.0000.5009.00
is-name Nifas Silk-RSG-A
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
portswitch
port link-type trunk
#
ip address 10.1.23.29 255.255.255.252
isis enable 100
isis cost 10
#
eth-trunk 1
#
eth-trunk 1
#
ip address 10.1.23.69 255.255.255.252
isis enable 100
isis cost 10
#
eth-trunk 4
#
eth-trunk 4
-135-
#
interface LoopBack0
ip address 10.0.5.9 255.255.255.255
isis enable 100
#
RSG(Nifas Silk-RSG-B)：
#
#
isis 100
is-level level-2
cost-style wide
flash-flood level-2
network-entity 25.1100.0100.0000.5010.00
is-name Nifas Silk-RSG-B
timer spf 1 50 50
traffic-eng level-2
log-peer-change
#
portswitch
#
ip address 10.1.23.30 255.255.255.252
isis enable 100
isis cost 10
#
eth-trunk 1
-136-
#
eth-trunk 1
#
ip address 10.1.23.110 255.255.255.252
isis enable 100
isis cost 10
#
eth-trunk 4
#
eth-trunk 4
#
interface LoopBack0
ip address 10.0.5.10 255.255.255.255
isis enable 100
#
-137-
7.2 BGP Design

7.2.1 Overview
Figure 7- 5 Bgp design overview
The border gateway protocol (BGP) is deployed on CSGs, ASGs, and RSGs to support L3VPN
services. The master and slave ASGs establish BGP VPNv4 peer relationships with the master and
slave RSGs and CSGs.
The common RR-client mode is recommended to configure HVPN on ASGs and RSGs. It is
applicable to HVPN, and supports transmission over the shortest path in the LDP-LSP scenario,
satisfy X2 service traffic model scenario.

Table 7- 2 Basic functions design
BGP process ID User-defined

Router ID This parameter takes the address of Loopback0.
GR Disabled. Use the non-stop routing (NSR), instead.
Reflctor cluster-id The RR pair in same AS use the same cluster-id.
-138-
7.2.3 Designing Routing Priorities

The primary and secondary routes on ring CSGs, ASGs, and RSGs can be selected randomly or
manually using routing policies.
Routing Policy Design for Access Side
On the access side, ASGs distinguish primary and secondary routes by CSG peer and implement
load sharing based on MED values set for routes from different peers. On ASGs, configure routing
policies at both ingress and egress interfaces so that RSGs and CSGs can identify the master ASG.
It is recommended that each ASG be configured with two peer groups, in which the ASG is specified
as the master ASG and slave ASG respectively. Use one of the ways to deploy access-side peers for
each ASG pair as required: by individual CSG, by CSGs on an access ring, and by all CSGs
connected to the ASG pair.
Master/slave determination by CSG:
Figure 7- 6 Routing policy design for access side
Last Mile Access
CSG1
ß103à
192.168.1.1
3à
10
ß
ß
20
3à
ß203à
CSG2
192.168.4.1
If CSGs are single-homed to one ASG on the network, configure the ASG as the master ASG during
route design to facilitate future dual-homing transformation.
Routing Policy Design for Aggregation Side
Each ASG pair/RSG pair must be configured to receive primary and secondary routes from each
other so that VPN-FRR can be implemented. And when no standalone RR is deployed on the
-139-
aggregation ring or RR functions are provided by RSG in this project, we have no need to configure
a routing policy.
Routing Policy Design for Core Side
On the core side, when private routes are advertised to BGP, a routing policy is used to set route
priorities. RSGs can distinguish primary and secondary routes by RSG pair or by RNC/MME.
Routing Policy Design Examples
The following figure show the scenario that Master/slave determination by CSG and RNC on a
network with RSGs functioning as RR
Figure 7- 7 Routing Policy Design
7.2.4 Designing Route Advertisement

Figure 7- 8 Route advertisement design (LTE X2)
-140-
RR will be deployed on the ASG which will reflect the private route from one CSG to another CSG
without the next-hop changed to implement the X2 Service (LTE X2 service refers to the traffic
between wireless base stations and wireless base stations. In an IP backhaul network, It’s mainly
deployed to implement communication between CSGs.) transmission in an access ring. The same
Configuration will be deployed between RSG and ASG to implement the X2 Service transmission
between the ASGs.
Figure 7- 9 Route advertisement design (2G/3G/LTE S1)
2G/3G/LTE S1 Eth Service: when a CSG advertises private network routes to an ASG, the ASG
advertises the specific routes to RSGs with the next hop modified. When an RSG advertises private
network routes to an ASG, the ASG does not advertise the specific routes but sends the default
routes to CSGs.
7.2.5 Designing Route Reflectors

RR is needed to configure if full mesh services are transmitted such as LTE X2 Service, especially
when a network is large in scale. Moreover the RRs in the same area generally play the same role
and back up each other and it is recommended that the cluster IDs should be the same to avoid
preferential selection flaps due to multiple routing reflections. Two RSG pairs in Microwave and
Nifas Silk are defined as redundancy RR for ASG in this project.
-141-
Figure 7- 10 Route Reflectors design
As shown in the following figure, there are two scenarios in this network which demand the bgp peer
to be established between RSGs (RSG1&RSG2 RSG3&RSG4) to exchange the private network
routes with each other.
Figure 7- 11 BGP neighbor requirement between RSGs (scenarios 1)
Scenarios one: the access rings & chains will be connected to some RSGs (RSG1&RSG2) directly
while the Manager System M2000 will be connected to some other RSGs (RSG3&RSG4) which is
used to manage the base station as long as the RSGs (RSG3&RSG4) and base stations are private
network routes reachable.
-142-
Figure 7- 12 BGP neighbor requirement between RSGs (scenarios 2)
Scenarios two: the BSC/RNCs in the same network are demanded to communicate with each other
by IUR logical interface as long as they are private network routes reachable.
7.2.6 Detail Parameter Designs

The BGP Connect Retry timer is configured to reduce routing flaps due to peer flaps so that routes
can be fast converged.
The Connect Retry interval is recommended to be 300s. To avoid that the access side is restored
from an ASG fault sooner than the aggregation side in the non-RR HVPN scenario with S1/3G
services on multiple RSG pairs or LTE ring-crossing X2 services on the aggregation side, default
routes are sent to CSGs in advance and transient route black holes are generated. The peer x.x.x.x
timer connect-retry 300 command only needs to be configured on the BGP peer on the access side.
#
bgp 100
peer CSG-as-master timer connect-retry 300
#
Forcing an ASG to Select Base Station Routes Advertised by CSGs Preferentially
The ASGs must be configured to forcibly select VPN routes advertised by CSGs preferentially so
that the ASGs do not select base station routes advertised by RRs/RSGs. If the forcible selection
function is not configured, base station routes advertised by RRs may be preferentially selected.
-143-
Table 7- 3 Forcing an ASG to Select Base Station Routes Advertised by CSGs Preferentially
Function Description Remarks

Forcing an ASG to Configure an inbound routing By default, preferred-value 0 is
Select base station policy for the ASG interface used. The greater the value, the
routes advertised by connected to the CSG peer, with higher the priority. The route optional
CSGs preferentially the route optional value value configured here takes
increased. For example, apply precedence over that configured
preferred-value 10 is when an ASG is forced to select local
configured in the inbound routes preferentially.
routing policy for the ASG The master and slave ASGs can have
interface connected to the CSG the same value.
peer. Correctly configure the RR function
on the two CSG peer groups so that
base station routes advertised by
RRs/RSGs are not preferentially
selected.
Forcing an ASG to Select Local Routes Preferably
The ASGs need to select the local default static routes preferably as well, to prevent the ASG select
routes reflected by RRs preferably.
Table 7- 4 Forcing an ASG to Select Local Routes Preferably
Function Policy Description Remarks
-144-
Function Policy Description Remarks
Forcing an ASG to select On the ASG, configure In the scenario of independent RRs, when
local routes preferably routing policies when the ASGs are dually home, routes on an
private network routes ASG at one end are reflected to the other
are advertised to the ASG. If the Local Preference value on the
BGP. Set the route RR on the aggregation side is changed, the
optional values, for route is selected by another ASG,
example, set to VPN-FRR will be invalid or routes will be
preferred-value 32768 incorrectly selected (the Local Preference
value of the local route is 100).
For example, 1: in the HVPN scenario, a
default route initiates from an ASG. If the
filtering policy is not set on the RR
direction, network-wide ASG/CSGs may
select wrong routes.
The preferred-value is recommended to be
higher than the preferred-value of the CSG
base station side route that is forcibly
selected by the ASG, to prevent the CSG
from wrongly advertising routes which
affects normal route selection on the ASG.
-145-
7.2.7 Configure Example for BGP

In this solution, CSGs advertise specific routes to ASGs. Based on the RT planning and routing
policy, ASGs advertise the default route only to the access ring and advertise specific routes between
CSGs on the same access ring connected to an ASG pair. During route advertisement, ASGs do not
change the next hop the routes. CSGs do not have routes to RSGs.
Route selection in the upstream direction
CSGs advertise routes to the master and slave ASGs.
The master ASG sets the MED value to 103 for routes transmitted to and received from the access
ring. The slave ASG sets the MED value to 203 for routes transmitted to and received from the
access ring.
The master and slave ASGs directly advertise received routes to RSGs without modifying the MED
value.
After receiving identical routes with different MED values from the master and slave ASGs, both the
master and slave RSGs select routes received from the master ASG.
Route selection in the downstream direction
RNCs advertise routes to the master and slave RSGs.

-146-
The master RSG sets the MED value to 103 for received routes. The slave RSG sets the MED value
to 203 for received routes.
The master and slave RSGs directly advertise received routes to the master and slave ASGs without
modifying the MED value.
After receiving identical routes with different MED values from the master and slave RSGs, both the
master and slave ASGs select routes received from the master RSG.
The master ASG sets the MED value to 103 for the default route advertised to CSGs. The slave ASG
sets the MED value to 203 for the default route advertised to CSGs. The CSGs select the route
received from the master ASG.
CSG(125D-CSG)：
#
bgp 65109
router-id 10.0.5.140
peer 10.0.5.33 as-number 65109
//Establish a peer relationship between the CSG and the master ASG.
peer 10.0.5.33 connect-interface LoopBack0
//Configure the source interface that sends BGP packets to be loopback0
//Establish a peer relationship between the CSG and the slave ASG.
#
ipv4-family unicast
undo synchronization
undo peer 10.0.5.33 enable
#
ipv4-family vpnv4
peer 10.0.5.33 enable
#
D-CSG(45N-DCSG)：
#
-147-
bgp 65109
router-id 10.0.5.146
#
ipv4-family unicast
#
ipv4-family vpnv4
#
ASG-Master (Kality-ASG-A)：
#
ip ip-prefix nodefault index 10 deny 0.0.0.0 0
ip ip-prefix nodefault index 20 permit 0.0.0.0 0 less-equal 32
#
route-policy to-csg-as-master permit node 10
apply cost 103
//Advertise the default route to CSGs, with the MED value in the default route being set to 103.
#
route-policy from-csg-as-master permit node 10
apply cost 103
//Receive routes from CSGs, with the MED value in the received routes being set to 103.
apply preferred-value 10
#
route-policy to-rsg permit node 10
if-match ip-prefix nodefault
//Advertise routes to the RSG without modifying the MED value.
#
-148-
ip route-static vpn-instance RAN 0.0.0.0 0 10.0.5.250

#
route-policy preferred-value permit node 10
#
tunnel-selector IPRAN permit node 10
apply tunnel-policy IPRAN
#
bgp 65109
router-id 10.0.5.33
group CSG-as-master internal
peer CSG-as-master connect-interface LoopBack0
peer CSG-as-master timer connect-retry 300
peer 10.0.5.140 as-number 65109
peer 10.0.5.140 group CSG-as-master
group RSG internal
peer RSG connect-interface LoopBack0
peer 10.0.5.9 group RSG
#
ipv4-family unicast
undo peer CSG-as-master enable
undo peer10.0.5.140 enable
undo peer RSG enable
#
ipv4-family vpnv4
reflect change-path-attribute
//Enable the ASG to modify attributes of BGP routes using the export policy.
policy vpn-target
-149-
tunnel-selector IPRAN
peer CSG-as-master enable
peer CSG-as-master route-policy from-csg-as-master import
peer CSG-as-master route-policy to-csg-as-master export
peer CSG-as-master reflect-client
peer 10.0.5.140 group CSG-as-master
peer RSG next-hop-local
peer RSG route-policy to-rsg export
#
ipv4-family vpn-instance RAN
network 0.0.0.0 route-policy preferred-value
#
ASG-Slave (Kality-ASG-B)：
#
#
route-policy to-csg-as-slave permit node 10
apply cost 203
//Advertise the default route to CSGs, with the MED value in the default route being set to 103.
#
route-policy from-csg-as-slave permit node 10
apply cost 203
//Receive routes from CSGs, with the MED value in the received routes being set to 203.
#
if-match ip-prefix nodefault // //Advertise routes to the RSG without modifying the MED value.
#
-150-
ip route-static vpn-instance RAN 0.0.0.0 0 10.0.5.250

#
#
#
bgp 65109
router-id 10.0.5.34
group CSG-as-slave internal
peer CSG-as-slave connect-interface LoopBack0
peer CSG-as-slave timer connect-retry 300
peer 10.0.5.140 as-number 65109
peer 10.0.5.140 group CSG-as-slave
group RSG internal
# #
ipv4-family unicast
undo peer CSG-as-slave enable
undo peer10.0.5.140 enable
#
ipv4-family vpnv4
//Enable the ASG to modify attributes of BGP routes using the export policy.
policy vpn-target
-151-
peer CSG-as-slave enable
peer CSG-as-slave route-policy from-csg-as-slave import
peer CSG-as-slave route-policy to-csg-as-slave export
peer CSG-as-slave reflect-client
peer 10.0.5.140 group CSG-as-slave
peer RSG next-hop-local
#
#
RSG-Master (Nifas silk RSG-A):
#
ip ip-prefix default index 10 permit 0.0.0.0 0
#
ip community-filter basic dscg permit 1000:3
#
route-policy to-csg-as-master permit node 10
if-match ip-prefix default
apply cost 103
#
route-policy from-csg-as-master permit node 10
apply cost 103
apply community 1000:3
#
-152-
route-policy to-asg permit node 10

if-match community-filter dscg
apply ip-address next-hop peer-address
#
#
#
#
route-policy rnc&bsc permit node 100
apply cost 103
#
#
bgp 65109
router-id 10.0.5.9
group DCSG-as-master internal
peer DCSG-as-master connect-interface LoopBack0
peer DCSG-as-master timer connect-retry 300
peer 10.0.5.146 as-number 65109
peer 10.0.5.146 group DCSG-as-master
group ASG internal
peer ASG connect-interface LoopBack0
peer 10.0.5.33 group ASG
-153-

group RSG internal
#
ipv4-family unicast
undo peer DCSG-as-master enable
undo peer ASG enable
#
ipv4-family vpnv4
policy vpn-target
peer DCSG-as-master enable
peer DCSG-as-master route-policy from-csg-as-master import
peer DCSG-as-master route-policy to-csg-as-master export
peer DCSG-as-master reflect-client
peer 10.0.5.146 group DCSG-as-master
peer ASG enable
peer ASG route-policy to-asg export
peer ASG reflect-client
peer RSG enable
#
-154-

import-route direct route-policy bsc&rnc
import-route static route-policy bsc&rnc
#
RSG-Slave (Nifas silk RSG-A):
#
#
ip community-filter basic dscg permit 1000:3
#
route-policy to-csg-as-slave permit node 10
apply cost 203
#
route-policy from-csg-as-slave permit node 10
apply cost 203
apply community 1000:3
#
#
#
#
-155-

#
route-policy rnc&bsc permit node 100
apply cost 203
#
#
bgp 65109
router-id 10.0.5.10
group DCSG-as-slave internal
peer DCSG-as-slave connect-interface LoopBack0
peer DCSG-as-slave timer connect-retry 300
peer 10.0.5.146 as-number 65109
peer 10.0.5.146 group DCSG-as-slave
group ASG internal
peer ASG connect-interface LoopBack0
group RSG internal
#
ipv4-family unicast
undo peer DCSG-as-slave enable
undo peer ASG enable
-156-
#
ipv4-family vpnv4
policy vpn-target
peer DCSG-as-slave enable
peer DCSG-as-slave route-policy from-csg-as-slave import
peer DCSG-as-slave route-policy to-csg-as-slave export
peer DCSG-as-slave reflect-client
peer 10.0.5.146 group DCSG-as-slave
peer ASG enable
peer ASG route-policy to-asg export
peer ASG reflect-client
peer RSG enable
#
#
-157-
8 MPLS Protocol design
8.1 MPLS LDP design

By deployed the LDP LSP, LTE X2 service data can be transmitted through a shortest path using
intra-ring full mesh tunnels, and the service data forwarding procedure is simple.
8.1.1 Overview
This solution uses LDP as a dynamic tunnel protocol.
All LDP LSPs are configured with IGP fast convergence using route protocols.

Table 8- 1 Basic Functions design
Parameter Design Guideline
LSR ID The LSR ID is 32-bit, same as the IP address of a loopback interface.
LDP GR Disabled. Use NSR, instead.
Non-null, Configure the function that the egress assigns non-null labels to the
Label advertise
penultimate hop. ATN devices function as that by default
Lsp-trigger Host, A policy of establishing LSPs is to trigger FEC for all IGP routes.
8.1.3 Designing Paths

 All interfaces advertising public IGP routes at the access layer are deployed with LDP. A closed
or open LDP loop is configured with ASGs depending on project requirements. An open LDP loop
is easy to deploy. A closed LDP loop can ensure that the uplink and downlink paths overlap during a
service switchover.
 When IS-IS multi-process is configured as IGP, LDP tunnels totally depend on routes. If a closed
loop is configured between the master and slave ASGs, the cost of access links must be larger than
that of aggregation links to prevent traffic from traversing access rings.
-158-

 By default, the ATN MPLS PHP feature is non-null and the CX MPLS PHP feature is
implicit-null. It is recommended that the CX MPLS PHP feature should be non-null for CX-ATN
interconnection.
#
label advertise non-null
#
 IGP-LDP synchronization is required to ensure that IGP routes are always consistent with LDP
LSPs. Keep the LDP-enabled interfaces advertising the maximum cost for a period 60s.
#
isis ldp-sync
isis timer ldp-sync hold-max-cost 60
#
8.1.5 Configure Example for MPLS LDP

-159-
If IGP routes are deployed and the cost value is configured as planned on a network, route selection
can be controlled. In this case, MPLS LDP LSPs of the host on the network can be triggered based
on the routing table.
Configuration of MPLS LDP LSPs is as follows:
 Enable MPLS globally.
 Enable MPLS LDP globally.
 Enable MPLS and MPLS LDP on the interface.
 Configure LDP route selection to be consistent with IGP route selection.
CSG(125D-CSG)：
#
mpls lsr-id 10.0.5.140 //Configure the MPLS LSR ID. It is recommended to use the IP
address of the loopback0
#
mpls // //Enable MPLS globally.
#
mpls ldp // Enable MPLS LDP globally.
#
ip address 10.1.25.30 255.255.255.252isis enable 1
isis cost 100
isis ldp-sync
isis timer ldp-sync hold-max-cost infinite 60
//Configure to export routes using the maximum cost in 60 seconds, when the LDP and IGP
are not consistent.
MPLS // Enable MPLS on the interface.
mpls ldp //Enable MPLS LDP on the interface.
#
ip address 10.1.25.33 255.255.255.252
isis enable 1
isis cost 100
-160-
isis ldp-sync
mpls
mpls ldp
#
interface Loopback0
isis enable 1
ip address 10.0.5.140 32
#
ASG(Kality-ASG-A):
#
mpls lsr-id 10.0.5.33
#
mpls
lsp-trigger host
#
mpls ldp
#
ip address 10.1.23.90 255.255.255.252
isis enable 100
isis cost 10
isis ldp-sync
mpls
mpls ldp
#
eth-trunk 1
#
eth-trunk 1
#
-161-
ip address 10.1.23.93 255.255.255.252
isis enable 100
isis cost 10
isis ldp-sync
mpls
mpls ldp
#
eth-trunk 2
#
eth-trunk 2
#
ip address 10.1.25.50 255.255.255.252
isis enable 1
isis cost 2000
isis ldp-sync
mpls
mpls ldp
#
ip address 10.1.25.29 255.255.255.252
isis enable 1
isis cost 100
isis ldp-sync
mpls
mpls ldp
#
interface Loopback0
-162-
isis enable 100

ip address 10.0.5.33 255.255.255.255
#
ASG(Kality-ASG-B):
#
#
mpls
lsp-trigger host
#
mpls ldp
#
ip address 10.1.23.89 255.255.255.252
isis enable 100
isis cost 10
isis ldp-sync
mpls
mpls ldp
#
eth-trunk 1
#
eth-trunk 1
#
ip address 10.1.23.86 255.255.255.252
isis enable 100
isis cost 10
isis ldp-sync
-163-
mpls
mpls ldp
#
eth-trunk 2
#
eth-trunk 2
#
ip address 10.1.25.49 255.255.255.252
isis enable 1
isis cost 2000
isis ldp-sync
mpls
mpls ldp
#
ip address 10.1.25.46 255.255.255.252
isis enable 1
isis cost 100
isis ldp-sync
mpls
mpls ldp
#
interface Loopback0
isis enable 100
ip address 10.0.5.34 255.255.255.255
#
RSG(Nafas silk-RSG-A)：
#
-164-
#
mpls
lsp-trigger host
#
mpls ldp
#
portswitch
#
vlan-type dot1q 100
undo shutdown
ip address 10.1.23.29 255.255.255.252
isis enable 100
isis cost 10
isis ldp-sync
mpls
mpls ldp
#
eth-trunk 1
#
eth-trunk 1
#
ip address 10.1.23.69 255.255.255.252
isis enable 100
isis cost 10
isis ldp-sync
-165-
mpls
mpls ldp
#
eth-trunk 4
#
eth-trunk 4
#
interface Loopback0
isis enable 100
ip address 10.0.5.9 255.255.255.255
#
RSG(Nafas silk-RSG-B)：
#
#
mpls
lsp-trigger host
#
mpls ldp
#
portswitch
#
vlan-type dot1q 100
undo shutdown
ip address 10.1.23.30 255.255.255.252
isis enable 100
isis cost 10
isis ldp-sync
-166-

mpls
mpls ldp
#
eth-trunk 1
#
eth-trunk 1
#
ip address 10.1.23.110 255.255.255.252
isis enable 100
isis cost 10
isis ldp-sync
mpls
mpls ldp
#
eth-trunk 4
#
interface GigabitEthernt8/0/1
eth-trunk 4
#
interface Loopback0
isis enable 100
ip address 10.0.5.9 255.255.255.255
#
-167-
8.2 MPLS TE design

In the hierarchy VPN solutions, MPLS can be designed as Resource Reservation Protocol-Traffic
Engineering (RSVP-TE) or Label Distribution Protocol (LDP). RSVP-TE is recommended in this
project for the 2G/3G/LTE S1 services, because of the advantages of RSVP-TE as follows:
 Tunnel setup can be controlled, and tunnel setup is not based on FECs.
 Bandwidth can be highly controlled, and bandwidth allocation can be automatically adjusted or
optimized.
 The security is high. Authentication can be based on peers and interfaces.
 RSVP-TE provides various protection switching modes and supports tunnel protection groups.
TE hot-standby is recommended.
 RSVP-TE has the following disadvantage: RSVP-TE configurations are complex and destination
nodes need to be manually specified.
 Paths of TE tunnels include explicit paths and CSPF selected paths.
 Although TE explicit paths are actually-controlled paths, they require huge data planning and
configuration workload when the network scale is large. In addition, nodes need to be added or
removed frequently during expansion.
 CSPF selects paths based on path cost values and does not require the configuration of explicit
paths. Although deployment of CSPF selected paths require less constraints, network planning
personnel need to be familiar with service objectives and network topologies (for example, two-ring
network).
-168-
8.2.1 Overview
Figure 8- 2 MPLS TE design overview
This solution uses RSVP-TE as a dynamic tunnel protocol that allows co-source, co-destination
multi-services to share the same tunnel. As shown in Figure above, the following tunnels need to be
set up:
 Tunnels from a CSG to the master and slave ASGs. See tunnels 1 and 3.
 Tunnels from the master and slave ASGs to the master and slave RSGs. See tunnels 2, 4, 5, and
6.
 Tunnel between the master and slave RSGs. See tunnel 7.
 It is recommended that the hot standby protection should be enabled for all TEs network-wide.

Table 8- 2 MPLS parameters
Parameter Value Remarks
Address of the
Configuring LSR IDs is the prerequisite
mpls lsr-id LSR loopback
for configuring other MPLS commands.
0 interface
To ensure that ATN and CX devices can
interconnect successfully using MPLS,
label advertise non-null this command must be configured on CX
devices, because the ATN device
functioning as the egress assigns non-null
-169-
labels to the penultimate hop by default.
mpls te - Enables the MPLS-TE function.

mpls rsvp-te - Enables the MPLS RSVP-TE function.
Enables the RSVP-TE Hello mechanism
mpls rsvp-te hello -
globally.
mpls te cspf - Enables the MPLS TE CSPF algorithm.
mpls rsvp-te srefresh - Enables the RSVP Srefresh feature.
Enables the MPLS RSVP-TE bfd
mpls rsvp-te bfd all-interfaces enable
function.
mpls rsvp-te bfd all-interfaces
Configures the BFD detection period as
min-tx-interval XXX 100
100 ms.
min-rx-interval XXX
Table 8- 3 MPLS TE tunnel parameters
Parameter Value Remarks
interface Tunnel Tunnel number: 0/0/XY Creates a tunnel interface.

XY: device numbers of
the source and destination
nodes
ip address unnumbered interface LoopBack0 Configures the tunnel to borrow the
IP address of the loopback0
interface.
tunnel-protocol mpls te Sets the tunnel mode to the
CR-LSP mode.
destination Address of the loopback Specifies the IP address of the
0 interface on the remote destination.
device
mpls te tunnel-id Tunnel ID format: XY Sets a tunnel ID.
XY: device numbers of
the source and destination
nodes
-170-
mpls te backup hot-standby wtr 60 Sets the WTR time (for example,
60s) for the tunnel in hot-standby
mode.
mpls te reoptimization frequency 3600 Sets the re-optimization interval.
The default value 3600s is
recommended.
bfd bind mpls-te interface discriminator local Configures BFD to detect status of
Tunnel te-lsp the primary LSP that is bound to
the VPN primary tunnel.
discriminator remote The local discriminator is the same
as the remote discriminator. The
local discriminator value for ATN
devices ranges from 1 to 255, and
that for CX600 devices ranges from
1 to 8191.
process-pst The minimum sending and
receiving intervals for BFD packets
need to be configured according to
configurations of the live network.
Detection period = Detection
multiple x Sending/Receiving
interval (3x10 ms)
To speed up the switchover, the
BFD session is allowed to modify
the port state table (PST).
bfd bind mpls-te interface discriminator local Configures BFD to detect status of
Tunnel the VPN primary tunnel.
discriminator remote The local discriminator is the same
as the remote discriminator. The
local discriminator value for ATN
devices ranges from 1 to 255, and
that for CX600 devices ranges from
1 to 8191.
-171-
process-pst The minimum sending and

receiving intervals for BFD packets
need to be configured according to
configurations of the live network.
Detection period = Detection
multiple x Sending/Receiving
interval (3x5 ms)
To speed up the switchover, the
BFD session is allowed to modify
the PST.
tunnel-policy Tunnel policy name: Configures a tunnel policy. In the
IPRAN policy, specify CR-LSP tunnels as
tunnel select-seq cr-lsp the tunnels to be selected first.
load-balance-number 1
8.2.3 Designing Paths

TE tunnels are designed so that traffic can be forwarded along specified paths in normal cases. Two
TE tunnels functions will be deploy at the same time, explicit paths and constraint shortest path first
(CSPF) paths. Explicit path have two type, loose and strict. We need include all the node in the path
for strict explicit path TE, and we only need include some of the node in the path for the loose
explicit TE. CSPF paths are shortest paths, computed using IGP cost (in ET IPRAN is isis).
Compare with MPLS LDP, The MPLS TE are recommended for the 2G/3G/LTE S1 Service in this
project because of the high reliability.
Design Guidelines
The following figure shows the design guidelines for explicit paths. A to G are constraint interfaces
on tunnels 1 to 7, respectively.
-172-
Figure 8- 3 MPLS TE Path design
If tunnels are configured with hot standby protection, the interface IP addresses of target NEs are
loosely constrained using the include mode on the primary LSP in the uplink and downlink. That is,
in a dual-homing scenario, the configuration principles for TE between the CSG and slave ASG and
between all master/slave ASGs and master/slave RSGs are the same as those for TE between
primary nodes.
Table 8- 4 Constrained interfaces of TE tunnels
TE Tunnel Constrained Interface Constraint Mode
TE1 A Loose
TE2 B Loose
TE3 C Loose
TE4 B Loose
TE5 D Loose
TE6 D Loose
TE7 E Strict
The preceding path restriction solution is only for the described topology. If the topology is more
complex, restriction points can be added (for example, add a restriction point at the egress port of a
head node), to ensure consistency between LSP and the planned paths. However, the number of
restriction points should be as small as possible to prevent impact on path adjustment.
Design Results
After loose constraint is configured, services are forwarded as follows in normal cases.
-173-
Figure 8- 4 MPLS TE Path design result
Designing Other Paths
 TE tunnels are configured with hot standby protection to ensure swift switching. TE tunnels are
recommended to be looped on the access side.
 When routes are computed using CSPF, TE tunnels can select routes as required using the IGP
cost. To avoid affecting native IP traffic, TE cost can be used instead of IGP cost. It is recommended
that re-optimization (default interval: 60 minutes) and the overlap function should be enabled for TE
tunnels.
 The path overlap function is configured to protect traffic on the primary CR-LSP under hot
standby protection. In addition, the entire router in the network need configure with the CR-LSP
overlap-path function to provide hot standby protection.
 It is recommended that the overlap function be enabled on TE tunnels on the aggregation side.
 If multi-convergence is present on the aggregation layer, it is recommended that the egress

interfaces of the key cross-connect nodes (including ingress nodes) should be loosely constrained.
 When primary and backup LSPs are constrained, best-effort paths are recommended.
Designing Paths in Other Scenarios
-174-
Figure 8- 5 MPLS TE design result
In some scenarios, there are more than two intersecting aggregation rings between ASG and RSG,
the primary and secondary LSP should contain the IP addresses of inbound interfaces on loose
explicit nodes. For example:
A1 to R1: includes interface P1 on A5 and interface P2 on R1.
R1 to A1: includes interface P2 on R1 and interface P1 on A5.
A1 to R2: includes interface P3 on A6 and interface P4 on R2.
R2 to A1: includes interface P4 on R2 and interface P3 on A6.
Avoid changing the IP addresses of included nodes if the two access rings needs to be broken for
adding nodes. If the IP addresses of included nodes must be changed, switch services to the backup
LSP. Then, manually switch services back to the primary LSP. If an aggregation ring covers many
nodes, increase nodes included and specify paths.
8.2.4 Designing BFD for TE-LSP/TE-Tunnel

 Static BFD is used to detect a TE-LSP with a tracking interval of 10 ms x 3.
bfd LSP35 bind mpls-te interface Tunnel0/0/35 te-lsp

discriminator local 305
discriminator remote 503
min-tx-interval 10
min-rx-interval 10
process-pst
-175-
commit
 Static BFD is used to detect the TE tunnel with a tracking interval three or more times larger
than that of BFD for TE-LSP. Generally, a static BFD period is 50 ms x 3.
bfd te35 bind mpls-te interface Tunnel0/0/35

min-tx-interval 50
min-rx-interval 50
process-pst
commit
 BFD for TE-tunnel and BFD for TE-LSP are recommended for all primary and secondary
tunnels at the aggregation layer and the access layer.

 By default, the ATN MPLS penultimate hop popping (PHP) feature is non-null and the CX
MPLS PHP feature is implicit-null. It is recommended that the CX MPLS PHP feature should be
non-null for CX-ATN interconnection.
mpls
 A record of routes and labels of MPLS is enabled for future maintenance.
mpls te record-route label
 The CR-LSP is preferentially selected, and then comes the LDP LSP.
tunnel-policy IPRAN Permanent
tunnel select-seq cr-lsp lsp load-balance-number 1
 NSR is used on the network instead of GR to improve reliability.
 To speed up fault detection on a network with a single fiber or a network traversed by a

third-party network, you need to enable BFD for RSVP-TE (dynamic BFD for RSVP-TE is
recommended), with the detection interval set to the recommended 100 ms x 3 for the
-176-
access/aggregation side.
8.2.6 Configure Example for MPLS TE

Figure 8- 6 configure example topology
The configuration principle for MPLS TE tunnels is as follows:
 Enable IGP TE (the detail information please refer to section 7.1 “ISIS Design”).
 Configure LSR IDs, enable MPLS, MPLS TE, MPLS TE CSPF and BFD for RSVP-TE globally
for nodes on the tunnels, and enable MPLS and MPLS TE for interfaces on the tunnels.
 Configure tunnel paths.
 Create Ethernet service tunnels.
Create the VPN working tunnel.
Create the VPN backup tunnel.
 Configuring BFD for TE-LSP.
 Configure BFD for TE.
 Create a tunnel policy.
-177-
Specify CR-LSP tunnels as the tunnels to be selected first.
Take the configuration of the Tunnel 1 and Tunnel 3 for example:
CSG1(125D-CSG):
#
mpls lsr-id 10.0.5.140////Configure an MPLS LSR ID. The address of a loopback interface is
recommended.
#
mpls
mpls te
mpls rsvp-te //Enable MPLS TE globally.
mpls rsvp-te bfd all-interfaces enable //Enable BFD for RSVP-TE.
mpls rsvp-te bfd all-interfaces min-tx-interval 100 min-rx-interval 100
//Configure the BFD detection period as 100 ms.
mpls rsvp-te hello //Enable the Hello mechanism for RSVP-TE globally.
mpls te cspf //Enable the CSPF algorithm.
mpls rsvp-te srefresh //Enable the RSVP-TE Srefresh feature.
#
ip address 10.1.25.30 255.255.255.252
mpls //Enable MPLS for interfaces.
mpls te //Enable MPLS TE for interfaces.
mpls rsvp-te //Enable RSVP-TE for interfaces.
mpls rsvp-te hello //Enable the Hello mechanism for RSVP-TE on interfaces.
#
ip address 10.1.25.33 255.255.255.252
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
explicit-path main_1to3 //Specify the primary CR-LSP that is from CSG1 to ASG3.
next hop 10.1.25.29 include loose
-178-
//Set the next hop of the LSP to the IP address of the interface that connects the master ASG
and the access ring.
//The path constraint mode is loose constraint.
//The loose profile is recommended for configuring explicit paths to facilitate node addition
in future.
interface Tunnel0/0/13 //Specify the tunnel that is from CSG to ASG (master ASG).
ip address unnumbered interface LoopBack0
//Use the IP of loopback0 for the IP address of the tunnel.
tunnel-protocol mpls te //Set the tunnel protocol to MPLS TE.
destination 10.0.5.33 //Set the destination address of the tunnel to the IP address of ASG3.
mpls te tunnel-id 13 //Configure the tunnel ID.
//The tunnel ID must be valid and unique on the local device.
mpls te record-route label //Enable the record of routes and labels.
mpls te backup hot-standby wtr 60 //Set the tunnel mode to hot-standby.
mpls te backup hot-standby overlap-path
mpls te reoptimization //Enable the re-optimzation function for the primary tunnel
mpls te commit //Commit all MPLS TE configurations for the tunnel.
#
ASG 3(Kality-ASG-A):
#
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
label advertise non-null ////Configure the function that the egress assigns non-null labels to
the penultimate hop.
mpls te cspf
mpls rsvp-te srefresh
#
ip address 10.1.23.90 255.255.255.252
-179-
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
eth-trunk 1
#
eth-trunk 1
#
ip address 10.1.23.93 255.255.255.252
mpls
mpls ldp
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
eth-trunk 2
#
eth-trunk 2
#
vlan-type dot1q 1
ip address 10.1.25.50 255.255.255.252
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
-180-
ip address 10.1.25.29 255.255.255.252

mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
explicit-path main_3to1//Specify the primary CR-LSP that is from ASG3 to CSG1.
//Set the next hop of the LSP to the IP address of the interface that connects the master ASG
and the access ring.
//The path constraint mode is loose constraint.
#
interface Tunnel0/0/31
tunnel-protocol mpls te
destination 10.0.5.140
mpls te tunnel-id 31
mpls te backup hot-standby wtr 60
mpls te reoptimization
mpls te commit
#
explicit-path main_3to5
#
mpls te path explicit-path main_3to5
-181-

mpls te commit
#
RSG5 (Nifas silk-RSG-A):
#
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
mpls te cspf
mpls rsvp-te srefresh
#
description To Nifas Silk-RSG-B-Eth 1
portswitch
vlan-type dot1q 100

undo shutdown
ip address 10.1.23.29 255.255.255.252
mpls
mpls ldp
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
ip address 10.1.23.69 255.255.255.252
-182-
mpls
mpls te
mpls rsvp-te
mpls rsvp-te hello
#
eth-trunk 4
#
eth-trunk 4
#
explicit-path main_5to3
#
mpls te path explicit-path main_5to3
mpls te commit
-183-
9 Mobile Services Implement
9.1 2G/3G/LTE S1 Mobile Service

The hierarchy VPN will be deployed to carry 2G/3G/LTE S1 Mobile services in ET IPRAN
Network.
The LTE S1 refers to the RAN-side end-to-end service, which includes signaling, voice and video
services that are required to be authenticated by MME and the data traffic interacts with the SGW. In
an IP RAN network, it is mainly deployed to implement communication between CSGs and RSGs.
9.1.1 Overview
Figure 9- 1 Mobile services Traffic Flow
In ET IPRAN network, the 2G, 3G and LTE S1 ip-based services design are the same and the
services flow are described below:
In the upstream:
 BTS/NodeB/eNodeB: sends the IP packets to an ATN device through its GE interfaces, where
different types of services carry different VLAN IDs.
 CSG (Cell Site Gateway): receives different types of services through its sub interfaces configured
with different L3VPNs based on their VLAN IDs, and forwards the services to the ASG through
LSPs.
-184-
 ASG (Aggregation Site Gateway): in the upstream, remove the MPLS label and forwards services in
IP mode to L3VPNs and then to the RSG.
 RSG (Radio Service Gateway): terminates L3VPN through its VLANIF interface and forwards
packets to the RNC/BSC through its Layer 2 interface (set by using the portswitch command).
In the downstream:
Traffic is forwarded to NodeBs/eNodeBs through hierarchical L3VPN.
9.1.2 Basic Design

Service Access Design
VLAN IDs and IP addresses will be planned to identify wireless services.
 Each base station will use multiple VLANs and IP addresses for service transmission. There are
several logical ports on the base station as well.
 Multiple VRF instances and static routes need to be configured on ATNs a towards the service ip
of Base stations.
 The same service provided by different base station should use the different vlan when they
connected to the same CSG through the RTNs.
Table 9- 1 the IP and VLAN design at the Access side
Base Station Service VLAN Port IP Service IP

2G 101 10.204.4.2/30 10.204.7.1/32
3G 201 10.204.31.2/30 10.204.34.1/32
111130 LTE-C 301 10.204.58.2/30 10.204.70.1/32
LTE-U 401 10.204.64.2/30 10.204.72.1/32
WOAM 501 10.204.86.2/30 10.204.89.1/32
2G 102 10.204.4.6/30 10.204.7.2/32
3G 202 10.204.31.6/30 10.204.34.2/32
111389 LTE-C 302 10.204.58.6/30 10.204.70.2/32
LTE-U 402 10.204.64.6/30 10.204.72.2/32
WOAM 502 10.204.86.6/30 10.204.89.2/32
2G 101 10.204.7.78/30 10.204.7.140/32
3G 201 10.204.33.78/30 10.204.34.140/32
111001 LTE-C 301 10.204.63.58/30 10.204.71.70/32
LTE-U 401 10.204.69.58/30 10.204.73.70/32
WOAM 501 10.204.88.78/30 10.204.89.140/32
-185-
Figure 9- 2 The two scenarios at the Service access side
CSG(004D):
Scenario one: the base station connect to RTN then CSG
#
The first and second GE port on ATN will be bundled into an Eth-Trunk using the link aggregation
technique to meet the bandwidth of the wireless part.
The Eth-Trunk interface is a logical interface, having all functions of an Ethernet interface and is
more reliable.
#
#
vlan-type dot1q 101
ip binding vpn-instance 2G //Bind the VPN instance to a specific service interface.
ip address 10.204.4.1 255.255.255.252
#
eth-trunk 1
#
-186-
eth-trunk 1
#
ip route-static vpn-instance IPRAN 10.204.7.1255.255.255.255 10.204.4.2
//The static route pointing to logical interface ip address of the base staion
#
Scenario two: the base station connect to CSG directly
#
The third GE port on ATN is obliged to connect with base station directly.
#
interface GigabitEthernet0/1/2.101
vlan-type dot1q 101
ip address 10.204.7.77 255.255.255.252
#
ip route-static vpn-instance IPRAN 10.204.7.140 255.255.255.255 10.204.7.78
#
Service Bearer Design
The CSG identifies services based on VLAN IDs. Different services are transmitted with different
L3VPNs.
Table 9- 2 Service Bearer design
VPN instance Set this parameter based on requirements in a specific project.

name
RD The RDs will be use the same vlaue networkwide for each VRF.
RT A CSG receives only an ASG route. Devices at the aggregation
layer and core layer receive network-wide routes. Routes are
filtered based on the RTs in the ingress and egress directions.
Labeling by To save label resources when VRF is deployed, the labels will be
VPN instance distributed by VPN instance.
Tunnel policy The Tunnel policy will be design to choose the TE-LSP at first,
only when there is no TE-LSP exsited between two nodes, the
LDP-LSP will be used
-187-
DHCP relay When base stations need to get online automatically, you need to
enable DHCP on CSGs to automatically allocate IP addresses for
base stations.
Table 9- 3 BGP VPNv4 route design
CSG Configure common L3VPN, including MP-BGP and VRF. The

CSG imports private network direct routes or static routes
(optional) to BGP VPN instances.
ASG The ASG advertises default routes to CSGs. Default routes are
originated locally and are advertised in network mode in BGP
private network instances. To forcibly make the ASG to select the
local default routes, instead of remote default ASG/RSG routes, the
local Pref-Value needs to be increased, for example to 32768, when
default routes are advertised to the BGP.
The ASG advertises all specific routes to the RSGs or RRs,
modifies the next hops of routes, and forwards traffic by specific
routes.
The ASG will use the RR-client configuration as follow:
Configure a common RR client on the CSG.
Configure a common IBGP on the RSG/RR so that an RSG does
not reflect its received routes to another RSG.
Configure the peers at both sides to modify the next hops of routes.
In the RR-client configuration, RT filtering is preferred for route
control. That is, plan different import/export RT values for the
CSGs, ASGs, and RSGs, ensuring that the CSGs prefer only routes
required by the ASG and RSGs. Route control can also be achieved
based on the routing policy.
-188-
RSG For details, see the CSG design guidelines. The RSG also functions
as an RR in this project for X2 service only. To force an RSG to
prefer local RNC/MME core side routes to core side routes
advertised by RRs, configure the RSG to increase the local
Pref-Value (for example, to 32768) that is contained in routes
advertised to BGP.
VRF RT Design
Figure 9- 3 VRF RT Design
 The CSGs, ASGs, and RSGs are configured with RT out = 100:1. The ASGs and RSGs are
configured with RT in = 100:1 to receive traffic from network-wide routes.
 The ASGs are also configured with RT out = 200:1. The CSGs are configured with RT in =
200:1 to receive traffic from the default routes of ASGs
 In some scenarios, CSGs will be directly connected to RSGs which we abbreviated it to D-CSG
(directly connected CSG). In this condition an E2E L3VPN will be deployed on them to carry the
mobile service.
Table 9- 4 RD and RT design table
Service Role RD Import RT Export RT
D-CSG 65109:1 65109:1

2G CSG 65109:1 65109:2 65109:1
ASG 65109:1 65109:1 65109:2
-189-
RSG 65109:1 65109:1

D-CSG 65109:3 65109:3
CSG 65109:4 65109:3
3G 65109:3
ASG 65109:3 65109:3 65109:4
RSG 65109:3 65109:3
D-CSG 65109:5 65109:5
LTE-C CSG 65109:6 65109:5
65109:5
(to MME) ASG 65109:5 65109:5 65109:6
RSG 65109:5 65109:5
D-CSG 65109:7 65109:7
LTE-U CSG 65109:8 65109:7
65109:7
(to SGW) ASG 65109:7 65109:7 65109:8
RSG 65109:7 65109:7
9.1.3 Reliability Design

In ET IPRAN network, mobile services are carried on HVPN scheme. The following table lists fault
detection and protection mechanisms applicable to the mobile services
Table 9- 5 Reliability Design
Fault Detection/Protection Point Detection Mechanism Protection Mechanism
Access ring and aggregation ring BFD for TE LSP TE hot-standby

ASG BFD for TE VPN FRR
RSG BFD for TE VPN FRR
BFD for VRRP VRRP or route backup
Physical link detection
Access side of the RSG Physical link detection VRRP or route backup
For design details of BFD for TE LSP and BFD for TE refer to MPLS design details.
VPN FRR
Deploy VPN FRR on CSGs, ASGs, and RSGs. The auto FRR mode is preferred.
route-policy nms-vpn-frr permit node 10

apply backup-nexthop auto
#
-190-
ip vpn-instance IPRAN
vpn frr route-policy nms-vpn-frr
#
VRRP
When an RNC uses master/slave interfaces to interwork with RSGs, deploy VRRP over VLANIF on
the master and slave RSGs.
 Configure the interconnection interfaces between the master and slave RSGs and the access
interface as VLANIF interfaces.
 Configure the VRRP preemption delay to 180s.
 In compliance with layered-protection principles, set the BFD for VRRP time to 3 x 50 ms.
Figure 9- 4 VRRP Design
RSG(Nifas silk RSG-A):

#
ip vpn-instance 2G
ipv4-family
route-distinguisher 65109:1
apply-label per-instance
tunnel-policy IPRAN
-191-
vpn-target 65109:1 export-extcommunity

vpn-target 65109:1 import-extcommunity
#
interface Eth-Trunk 1 // Configure a VLAN trunk between the master and slave RSGs.
portswitch
undo shutdown
//Configure the interfaces connecting the master and backup RSGs to be trunk interfaces.
port trunk allow-pass vlan 1430
//Configure the trunk interfaces to allow packets that carry VLAN to pass 1430.
#
negotiation auto
//It is recommended that the auto-negotiation mode be used on the GE interface connected to the
wireless equipment.
portswitch
port-tx-enabling-delay 300000
//Without this configuration, services will be interrupted during master RSG reset.
undo shutdown
//The link type must match that of the peer device. In this example, the link type is trunk.
#
bfd vrrp bind peer-ip 10.204.115.74 vpn-instance 2G interface Vlanif1430 source-ip
10.204.115.75
min-tx-interval 50
min-rx-interval 50
commit
#
interface Vlanif 1430
ip binding vpn-instance 2G
ip address 10.204.115.74 28
-192-
vrrp vrid 1 virtual-ip 10.204.115.73

vrrp vrid 1 priority 120
vrrp vrid 1 preempt-mode timer delay 180
#
ip route-static vpn-instance 2G 10.204.114.37 32 10.204.115.78 preference 5 description TO BSC
RSG(Nifas silk RSG-B):
#
ip vpn-instance 2G
ipv4-family
tunnel-policy IPRAN
#
interface Eth-Trunk 1
portswitch
undo shutdown
#
negotiation auto
portswitch
port-tx-enabling-delay 300000
undo shutdown
#
bfd vrrp bind peer-ip 10.204.115.75 vpn-instance 2G interface Vlanif1430 source-ip
10.204.115.74
min-tx-interval 50
-193-
min-rx-interval 50
commit
#
ip address 10.204.115.75 255.255.255.0
vrrp vrid 1 track bfd-session 1430 increased 40
#
Design Results
The figure below shows the traffic flow before and after any node (A, B, or C) or link between the
CSG and ASG is faulty.
Figure 9- 5 Reliability Design result in Access ring
The following figure shows the traffic flow before and after the master ASG is faulty.
Figure 9- 6 Reliability Design result on ASG node
-194-
The following figure shows the traffic flow before and after the master ASG is faulty.
Figure 9- 7 Reliability Design result in Aggregation ring
The following figure shows the traffic flow before and after the master RSG is faulty.
Figure 9- 8 Reliability Design result on RSG node
The following figure shows the traffic flow before and after an AC-side link is faulty on the RSG.
Figure 9- 9 Reliability Design result in base station controller side
9.1.4 Scalability Design

As services develop, the IPRAN capacity must be expanded. Available capacity expansion methods
include adding nodes to the access ring, aggregation ring and links.
-195-
The following figure shows capacity expansion by adding a node to the access ring.
Figure 9- 10 Adding a node to the access ring
Fiber disconnections are performed by field engineers. Other operations are performed on the U2000
or Router devices.
The operations have the following impacts on the access ring:
Tunnel services on the live network: Disconnecting fibers to add nodes will trigger the switchovers
of dynamic tunnels, and services will switch to the protection tunnels. Services running on other NEs
on the access ring will not be interrupted.
PW services on the live network: If the PW services running on the NEs have primary and backup
paths, these services will switch to the backup path for transmission and will not be interrupted.
IP address: Interfaces P1 and P3 must be on the same network segment, and interfaces P2 and P4
must be on the same network segment after capacity expansion, as shown in Figure above. When
adjusting IP addresses, configure P3 to use the IP address of P2, allocate new IP addresses to P2 and
P4, and keep the IP address of P1 unchanged.
Scenario 1: Adding a node between two CSGs on the access ring
CSG3 is added between CSG1 and CSG2, as shown in the following figure, P1 on the source CSG2
is interconnected with P3 on the new CSG, and P2 on the sink CSG1 is interconnected with P4 on
the new CSG.
-196-
Figure 9- 11 Adding a node between two CSGs on the access ring
Scenario 2: Adding a node between the source ASG and sink CSG on the access ring
CSG3 is added between ASG1 and CSG2, as shown in the following figure, ASG1 is specified as
the source NE, and CSG2 is specified as the sink NE. P1 on the source ASG1 is interconnected with
P3 on the new CSG, and P2 on the sink CSG2 is interconnected with P4 on the new CSG.
Figure 9- 12 Adding a node between the source ASG and sink CSG on the access ring
-197-
Scenario 3: Adding a node between two ASGs on the aggregation ring
ASG5 is added between ASG1 and ASG3, as shown in the following figure, P1 on the source ASG1
is interconnected with P3 on the new ASG, and P2 on the sink ASG3 is interconnected with P4 on
the new ASG.
Figure 9- 13 Adding a node between two ASGs on the aggregation ring
Scenario 4: Adding a node between the source RSG and sink ASG on the aggregation ring
ASG5 is added between RSG1 and ASG4, as shown in the following figure, RSG1 is specified as
the source NE, and ASG4 is specified as the sink NE. P1 on the source RSG1 is interconnected with
P3 on the new ASG, and P2 on the sink ASG4 is interconnected with P4 on the new ASG.
-198-
Figure 9- 14 Adding a node between the source RSG and sink ASG on the aggregation ring
Scenario 5: Adding a node to a link
CSG4 is added between two ASGs or between an ASG and a CSG. In the following figure, a node is
added between two CSGs.
Figure 9- 15 Adding a node to a link
Scenario 6: Adding a node between two CSGs:
P1 on the source CSG1 is interconnected with P3 on the new CSG, and P2 on the sink CSG2 is
interconnected with P4 on the new CSG.
-199-
Figure 9- 16 Adding a node between two CSGs
Adding a node between an ASG and a CSG:
The ASG is specified as the source NE, and the CSG is specified as the sink NE. P1 on the source
ASG is interconnected with P3 on the new CSG, and P2 on the sink CSG is interconnected with P4
on the new CSG.
9.1.5 QoS Design

Table 9- 6 QoS Mapping
Service Priority Congestion

DSCP Scheduler Weight
Queue avoidance
Network Control
CS6 48 PQ N.A. Tail-drop
2/3G O&M
LTE O&M
2/3G Voice EF 46 PQ N.A. Tail-drop
VoIP
-200-
9.1.6 Configure Example for 2G/3G/LTE S1 Service

The principle for configuring E2E mobile service and protection in HVPN mode is as follows:
 Configure MP-iBGP (the detail information please refer to section 7.2 “BGP Design”)
Set up MP-iBGP peer relationships between CSGs and the master ASG, and between the master
ASG and the master RSG.
To protect the master ASG, set up MP-iBGP peer relationships between CSGs and the slave ASG,
and between the slave ASG and the master RSG and the slave RSG.
To protect the master RSG, set up MP-iBGP peer relationship between the master ASG and the slave
RSG.
 Deploy VPN services.
Deploy VPN instances on CSGs, ASGs, and RSGs. access interfaces do not need to be configured
for VPN instances on ASGs.
Plan a route target (RT) to make traffic from CSGs to RSGs traverse the default routes and traffic
from RSGs to CSGs traverse on the explicit routes.
-201-
 Deploy protection switching.
Increase the ConnectRetry interval for re-establishing the peer relationship between a CSG and the
master ASG.
Configure VPN fast reroute (FRR) on CSGs, ASGs and RSGs.
 Configure Virtual Router Redundancy Protocol (VRRP) to implement RSG dual-homing

protection.
To protect the links between RSGs and the radio network controller (RNC), configure VRRP over
VLANIF between the master and slave RSGs.
Configure the interfaces that connect the master and slave RSGs and the interfaces that connect the
master and slave RSGs to the RNC as Layer 2 switch interfaces, and add these interfaces to a
VLAN.
Create VLAN interfaces on the master and slave RSGs and configure VRRP.
Configure BFD between the master and slave RSGs to check Layer 2 links and remote private
network addresses, to speed up protection switching.
Configure VRRP switchback delay on the master RSG.
-202-
CSG(125D-CSG):
ip vpn-instance 2G //Create a VPN instance.
ipv4-family
route-distinguisher 65109:1 //The IPv4 family of the VPN instance takes effect only after the RD is
configured.
//Enable to allocate private network route labels based on the one label-to-one VPN instance rule.
tunnel-policy IPRAN //Select TE tunnels first for the VPN instance.
vpn frr route-policy frr
#
route-policy frr permit node 10 //Configure a routing policy for VPN FRR.
apply backup-nexthop auto //Set the backup next hop to auto for the VPN.
#
tunnel-policy IPRAN
#
interface Eth-trunk 1.101//the sub-interface conneted tobase station
vlan-type dot1q 101
ip address 10.204.4.1 255.255.255.0
#
eth-trunk 1
#
eth-trunk 1
#
ip route-static vpn-instance IPRAN 10.204.7.1255.255.255.255 10.204.4.2
// If the base station uses a logical IP address, configure a static route leading to the logical address of the
base station.
#
bgp 65109
-203-
ipv4-family vpn-instance 2G
import-route direct
import-route static
#
DCSG(45N-CSG):
ip vpn-instance 2G //Create a VPN instance.
ipv4-family
route-distinguisher 65109:1 //The IPv4 family of the VPN instance takes effect only after the RD is
configured.
//Enable to allocate private network route labels based on the one label-to-one VPN instance rule.
tunnel-policy IPRAN //Select TE tunnels first for the VPN instance.
#
#
tunnel-policy IPRAN
#
vlan-type dot1q 101
ip address 10.204.12.101 255.255.255.0
#
eth-trunk 1
#
eth-trunk 1
#
ip route-static vpn-instance IPRAN 10.204.15.26 255.255.255.255 10.204.12.102
-204-
// If the base station uses a logical IP address, configure a static route leading to the logical address of the
base station.
#
bgp 65109
import-route direct
import-route static
#
ASG (Kality-ASG-A):
#
ip vpn-instance 2G
ipv4-family
tunnel-policy IPRAN
vpn-target 65109:1 65109:2 export-extcommunity
#
ip route-static vpn-instance 2G 0.0.0.0 0 10.0.5.250
#
#
#
#
route-policy to-csg permit node 10
#
-205-

#
#
bgp 65109
ipv4-family vpn-instance IPRAN
#
ASG (Kality-ASG-B):
#
ip vpn-instance 2G
ipv4-family
tunnel-policy IPRAN
#
ip route-static vpn-instance 2G 0.0.0.0 0 10.0.5.250
#
#
#
#
-206-
route-policy to-csg permit node 10

#
#
#
bgp 65109
#
RSG(Nafas silk RSG-A):
#
ip vpn-instance 2G
ipv4-family
tunnel-policy IPRAN
#
portswitch
undo shutdown
port link-type trunk //Configure the interfaces connecting the master and backup RSGs to be trunk
interfaces.
port trunk allow-pass vlan 1430 //Configure the trunk interfaces to allow packets that carry VLAN to pass
1430.
#
negotiation auto //It is recommended that the auto-negotiation mode be used on the GE interface connected
-207-
to the wireless equipment.

portswitch
port-tx-enabling-delay 300000 //This configuration is mandatory. Without this configuration, services will
be interrupted during master RSG reset.
undo shutdown
port link-type trunk //The link type must match that of the peer device. In this example, the link type is trunk.
#
bfd vrrp bind peer-ip 10.204.115.74 vpn-instance 2G interface Vlanif1430 source-ip 10.204.115.75
min-tx-interval 50
min-rx-interval 50
commit
#
ip address 10.204.115.74 255.255.255.0
#
#
route-policy bsc&rnc permit node 10
apply cost 103
##
ip route-static vpn-instance 2G 0.0.0.0 0.0.0.0 NULL0 //for direct-coupled CSG
#
bgp 65109
-208-
network 0.0.0.0 0 route-policy preferred-value

#
RSG(Nafas silk RSG-B):
#
ip vpn-instance 2G
ipv4-family
tunnel-policy IPRAN
#
portswitch
undo shutdown
port link-type trunk //Configure the interfaces connecting the master and backup RSGs to be trunk
interfaces.
port trunk allow-pass vlan 1430 //Configure the trunk interfaces to allow packets that carry VLAN to
pass1430
#
negotiation auto //It is recommended that the auto-negotiation mode be used on the GE interface connected
to the wireless equipment.
portswitch
port-tx-enabling-delay 300000 //This configuration is mandatory. Without this configuration, services will
be interrupted during master RSG reset.
undo shutdown
port link-type trunk //The link type must match that of the peer device. In this example, the link type is trunk.
#
bfd vrrp bind peer-ip 10.204.115.75 vpn-instance 2G interface Vlanif1430 source-ip 10.204.115.74
min-tx-interval 50
-209-
min-rx-interval 50
commit
#
ip address 10.204.115.75 255.255.255.0
vrrp vrid 1 track bfd-session 1430 increased 40
#
#
route-policy bsc&rnc permit node 10
apply cost 203
#
ip route-static vpn-instance 2G 0.0.0.0 0.0.0.0 NULL0 //for direct-coupled CSG
#
bgp 65109
network 0.0.0.0 0 route-policy preferred-value
#
9.2 LTE X2 Mobile Service

9.2.1 Overview
LTE X2 refers to a locally switched mobile service with the taffic from one base station to another
one. In an IP backhaul network, it is a communication between CSGs.
-210-
Figure 9- 18 LTE X2 service Traffic Flow
9.2.2 Basic Design

VRF designs for LTE X2 services are similar to those for LTE S1 services and LTE X2 services are
carried on HVPN as well. Actually in ET IP RAN network the LTE X2 and LTE S1 services share
the same VPN instance (LTE-U) for the data plane
Figure 9- 19 LTE X2 service basic designs in BGP relationship
-211-
The LDP LSPs will be deployed to make sure that the X2 services can be forwarded along the
shortest path within an access ring or between ASGs. On different access rings of the same ASG or
on an access ring consisting of different ASGs, X2 services are transmitted to ASGs along the
HVPN default route.Then forwarded along ASG to the destination CSG.
The design guidelines for forwarding services along the shortest path on LDP LSPs are as follows:
 On an ASG device, configure its CSG-side BGP peers as RR clients and configure the
ASG/RSG not to modify the next hops of routes.
 On an RSG device, configure its ASG-side BGP peers as RR clients and configure the
ASG/RSG not to modify the next hops of routes.
 In this case, between CSGs connected to an ASG pair, aggregation ASGs can reflect routes to
each other and forward traffic along the shortest LDP LSP.
 To prevent mutual and frequent route reflection between ASGs (RRs) and aggregation RRs,
disable the RR client role between the RSG peers.
Figure 9- 20 VRF RT design
To prevent CSGs from receiving whole private network routes, RT filtering is preferred to control
CSG routes. We will plan different RTs for CSGs when they connected to diffrent ASGs in pairs.
Table 9- 7 VRF RT design example
CSG ASG RSG
CSG RT-in RT-out ASG Pair ASG RT-in RT-out RT-in RT-out
-212-
CSG ASG RSG
CSG RT-in RT-out ASG Pair ASG RT-in RT-out RT-in RT-out
1:1; 1:1; 200:1;

Access ring 1 ASG pair 1 ASG1 100:1
200:1 100:1 100:1
1:1; 1:1; 200:1;

Access ring 2 ASG pair 1 ASG2 100:1
200:1 100:1 100:1
1:2; 1:2; 200:1;

Access ring 3 ASG pair 2 ASG3 100:1 100:1; 100:1
200:1 100:1 100:1
1:m; 1:m; ASG pair 200:1;

Access ring m ASG4 100:1
200:1 100:1 m 100:1
1:m; 1:m; ASG pair 200:1;

Access ring n ASG5 100:1
200:1 100:1 m 100:1
 Configure RT-out 100:1 on CSGs, ASGs, and RSGs. Configure RT-in 100:1 on ASGs and RSGs
so that the ASGs and RSGs receive whole network routes.
 Configure RT-out 200:1 on ASGs. Configure RT-in 200:1 on CSGs so that the CSGs receive
default routes originated by the ASGs.
 Configure RT-in and RT-out for CSGs in each access ring connected to an ASG pair. On a
network with nodes added to access rings, you can configure an RT for each access ring. As for the
previous example, you can configure an RT for access rings 1, 2, 3, m, and n.
The following table shows the RD&RT design result for the LTE X2 Service.
Table 9- 8 VRF RT design result
LTE-U D-CSG 65109:7 65109:7 65109:7

CSG 65109:8 1:n 65109:7 1:n
ASG 65109:7 65109:7 65109:8
RSG 65109:7 65109:7

The faults are similar to common LDP LSP faults.
-213-
9.2.4 QoS Design

The following table shows LTE service priority mapping and scheduling
Table 9- 9 Qos design
Service Priority Congestion

DSCP Scheduler Weight
Queue avoidance
Network
Control CS6 48 PQ N.A. Tail-drop
2/3G O&M
LTE O&M
VoIP
9.2.5 Configure Example for LTE X2 Service

interface with CSG ASG and RSG.
The principle for configuring LTE X2 service bearer is as follows:
 Configure MP-iBGP.
-214-
MP-IBGP has been configured during LTE S1 service deployment and does not need to be
configured again for the LTE X2 service.
 Deploy VPN services.
The LTE X2 and LTE S1 services will be bound to the same VPN instance for LTE data plane.
 Configure VPN instances on CSGs and ASGs.
 Deploy protection switching.
For other protection switching configurations, refer to those for LTE S1 services.
Because the VPN instance and VPN route advertisement have been configured when you deployed
the S1 service, therefore we only need to configure a service interface and bind it to the VPN
instance.
CSG(33N-CSG):
ip vpn-instance LTE-U
ipv4-family
tunnel-policy IPRAN
vpn-target 65109:2 1:1 import-extcommunity
#
CSG(152D-CSG):
ip vpn-instance LTE-U
ipv4-family
tunnel-policy IPRAN
vpn-target 65109:2 1:1 import-extcommunity
#
-215-
9.3 2G TDM Service Design

CDMA service will be swapped to the IP Backhaul network. And this solution is prepared for
bearing such services.
9.3.1 Overview
Figure 9- 22 2G TDM service design Traffic Flow
In the upstream:
 BTS: transmits TDM cell to an ATN device (CSG) through its TDM E1 interfaces.
 CSG: maps TDM cell to PWs in CESoP (Circuit Emulation Service over Packet) mode, performs
LSP encapsulation, and then forwards the CES services to the ASG.
 ASG: removes the outer LSP label, and swaps the inner PW1 to PW2 label, adds another LSP
label, and then forwards the CES services through the LSP tunnel to the RSG.
 RSG: terminates PWs from the ASG, decapsulates CES services, and then forwards the
decapsulated services through E1 links to the BSC.
In the downstream:
The signal flow is reverse to that in the upstream. Traffic is forwarded through MS-PWs from the
BSC to BTSs.
9.3.2 Basic Design

Service Access Design
-216-
Ensure that E1 interface attributes on the ATN devices are consistent with those on the BTSs.
Service Bearer Design
Multi-segment PWs need to be created between CSGs and RSGs to carry time division multiplexing
(TDM) services. In some scenarios, CSGs will be directly connected to RSGs which we abbreviated
it to D-CSG (directly connected CSG). In this condition an E2E PW will be deployed on them to
carry the TDM service.
Table 9- 10 2G TDM service basic design
Number of TDM Configure the same number of TDM frames to be encapsulated in a

frames CES packet on both the ATN and CX600 devices.
encapsulated in a By default, eight TDM frames are encapsulated in a CES packet on
CES packet ATN devices and 32 TDM frames are encapsulated in a CES packet
on CX600 devices. It is recommended that you set the number to 8
on both the ATN and CX600 devices. That is, the encapsulation
time is 1 ms. If you use the same NMS to configure this parameter,
retain the default parameter value.
Jitter buffer time Configure the same jitter buffer time on both the ATN and CX600
devices.By default, the jitter buffer time is 8 ms on ATN devices,
and is 20 ms on CX600 devices. If you use the same NMS to
configure this parameter, retain the default parameter value.
Control word Enable the control word function.
PW VC ID Set this parameter based on project requirements. If you use the
same NMS, the NMS will automatically assign the parameter value.
RTP header By default, no RTP header is used. It is recommended that you
retain the default parameter setting.
Tunnel policy Prefer the CR-LSP mode as the tunnel policy and set the number of
routes used for load balancing to 1. When TE-LSPs are deployed,
set this parameter to CR-LSP or manually bind TE interfaces.
-217-

Figure 9- 23 2G TDM service reliability design
In this scenario, TDM services are carried by MS-PWs.
The following table list fault detection and protection mechanisms applicable to the TDM services
Table 9- 11 2G TDM service reliability design
Fault Detection/Protection Detection Mechanism Protection Mechanism
Point
Access ring and BFD for TE LSP TE hot-standby (HSB)

aggregation ring
ASG/RSG BFD for PW PW redundancy
Physical link
detection
PW Redundancy
Deploy PW redundancy protection on CSGs and RSG.
 Configure PW services between CSG and RSG and PW switching on ASG.
 Configure PW redundancy in master/slave mode on the CSG and RSG.
Follow the following principles to deploy PW redundancy:
 A single RSG is connected to the RNC at the sink node, configure master/slave PW redundancy
on the CSG at the source node and on the RSG at the destenation node.
-218-
BFD for PW
 Deploy end-to-end BFD for PW between the CSG and the RSG, implementing static BFD for
MS-PWs.
 Set the detection period to be longer than three times the detection period for BFD for LSP.
Design Results
The following figure shows the traffic flow before and after the node or link between the CSG and
ASG is faulty.
Figure 9- 24 2G TDM service reliability result in access ring
The following figure shows the traffic flow before and after ASG node is faulty.
-219-
Figure 9- 25 2G TDM service reliability result on ASG node
The following figure shows the traffic flow before and after any node or link between the ASG and
RSG is faulty.
Figure 9- 26 2G TDM service reliability result in aggregation ring
9.3.4 QoS Design

The following table shows the 2G service priority mapping and scheduling
Table 9- 12 Qos design
Service Type EXP PHB Scheduling Mode
-220-
Service Type EXP PHB Scheduling Mode
All services 5 EF PQ
9.3.5 Configure Example for 2G TDM Service

The configuration principles for single-homing MS-PW services are as follows:
 Enable the MPLS L2VPN function on the device.
 Configure remote LDP sessions between CSG and ASG, and between ASG and RSG.
 Configure service interfaces on CSG and RSG.
 Configure PW redundancy services on CSG.
 Configure PW redundancy services on RSG.
 Configure PW switching for the primary PW on Kality-ASG-A.
 Configure PW switching for the secondary PW on Kality-ASG-B.
 Configure BFD for PW.
-221-
CSG1(125D-CSG)
mpls l2vpn
mpls ldp//Configure MPLS LDP globally.
#
mpls ldp remote-peer 10.0.5.33 //PWs use extended LDP protocol to distribute PW labels.
remote-ip 10.0.5.33
mpls ldp remote-peer 10.0.5.34
remote-ip 10.0.5.34
#
pw-template tdm //Create a PW template for TDM services.
control-word //Enable the control word so that alarm and clock information can be transmitted.
tnl-policy IPRAN //Configure a tunnel policy for the PW.
jitter-buffer depth 4 //Set the depth of the jitter buffer to 4ms.
tdm-encapsulation-number 8 //Set the number of frames encapsulated in a packet to 8.
#
controller E1 0/2/3
using e1 //Configure the clear channel mode.
#
interface Serial0/2/3:0
link-protocol tdm //Configure the link protocol as TDM.
#
mpls l2vc 10.0.5.33 pw-template tdm 500 //Configure the primary PW (between the CSG and the master
ASG).
mpls l2vc 10.0.5.34 pw-template tdm 501 secondary // between the CSG and the slave ASG
mpls l2vpn redundancy master //Configure PW redundancy in Master mode.
mpls l2vpn reroute delay 500//Configure PW switching back time as 500s.
mpls l2vpn stream-dual-receiving //Allow both the primary and secondary PWs to receive packets.
mpls l2vpn oam-mapping //Enable the mapping between the AC status and the network side status.
#
bfd tdm_primary_pw bind pw interface Serial0/2/3:0
min-tx-interval 50
-222-
min-rx-interval 50
commit
#
ASG3(Kality-ASG-A)
mpls l2vpn
#
#
remote-ip 10.0.5.140
remote-ip 10.0.5.9
#
mpls switch-l2vc 10.0.5.9 1200 tunnel-policy IPRAN between 10.0.5.140 500 tunnel-policy IPRAN
encapsulation satop-e1 control-word-transparent
#
ASG4(Kality-ASG-B)
mpls l2vpn
remote-ip 10.0.5.140
remote-ip 10.0.5.9
#
mpls switch-l2vc 10.0.5.9 1201 tunnel-policy IPRAN between 10.0.5.140 501 tunnel-policy IPRAN
encapsulation satop-e1 control-word-transparent
#
RSG5(Nafas silk RSG-A)：
mpls l2vpn
#
#
mpls ldp remote-peer 10.0.5.33//PWs use extended LDP protocol to distribute PW labels.
remote-ip 10.0.5.33
-223-

remote-ip 10.0.5.34
#
pw-template tdm //Create a PW template for TDM services.
control-word //Enable the control word so that alarm and clock information can be transmitted.
tnl-policy IPRAN //Configure a tunnel policy for the PW.
jitter-buffer depth 4 //Set the depth of the jitter buffer to 4ms.
tdm-encapsulation-number 8 //Set the number of frames encapsulated in a packet to 8.
#
controller E1 1/2/1
using e1 //Configure the clear channel mode.
#
interface Serial 1/2/1:0
link-protocol tdm //Configure the link protocol as TDM.
#
mpls l2vc 10.0.5.33 pw-template tdm 1200 //Configure the primary PW (between the RSG and the master
ASG).
mpls l2vc 10.0.5.34 pw-template tdm 1201 secondary // between the RSG and the slave ASG
mpls l2vpn redundancy master
mpls l2vpn reroute delay 500
mpls l2vpn stream-dual-receiving
mpls l2vpn oam-mapping
#
bfd tdm_primary_pw bind pw interface Trunk-Serial2/1:0
min-tx-interval 50
min-rx-interval 50
commit
#
-224-
9.4 CS Service Design

9.4.1 CS Service Scenario overview
Active and Standby Interface Scenario
 MSOFT3000/UMG8900 only active interface can receive packets.
 RSG configure Eth-Trunk + VRRP to protect link and node failure.
Figure 9- 28 CS Active and Standby Interface Scenario
NE40E-X8
Port1:10.15.0.2/29->VPN_Billing
S9300
Port1:10.15.0.5/29->VPN_Billing
MSOFT3000
VRRP
Port1:10.15.0.1/29->VPN_Billing S9300
Dual Active Interfaces Scenario
 The UMG8900 Media service use dual active interface
 RSG use IP FRR+BFD to protect link and node failure.
Figure 9- 29 CS Dual Active Interface Scenario
NE40E-X8
Port5:10.17.0.57/30->VPN_Signal
Port3:10.17.0.58/30->VPN_Signal
Ospf
UMG8900
Ospf
Port3:10.17.0.62/30 ->VPN_Signal
Port5:10.17.0.61/30 ->VPN_Signal
9.4.2 Physical Connection

CS Domain physical Topology in NifasSilk
-225-
MSC_01.HW.NS.AA
NE40E_01.HW.NS.AA NS_SW_CS_A
GMSC_01.HW.NS.AA
10G
1G
MGW_01.HW.NS.AA
NE40E_02.HW.NS.AA NS_SW_CS_B
GMGW_01.HW.NS.AA
Physical port connection in NafasSilk list below
Source Source Destination Destination

Source NE Physical Port LogicalPort Destination NE Physical Port LogicalPort
NE40E_01.H XGE6/1/0 XGE1/0/0 Eth-Trunk3
Eth-Trunk30 NS_SW_CS_A
W.NS.AA XGE7/1/0 XGE1/0/1 0
NE40E_02.H XGE6/1/0 XGE1/0/0 Eth-Trunk3
Eth-Trunk30 NS_SW_CS_B
W.NS.AA XGE7/1/0 XGE1/0/1 0
NS_SW_CS_ XGE1/0/14 XGE1/0/14 Eth-Trunk1
Eth-Trunk10 NS_SW_CS_B
A XGE1/0/15 XGE1/0/15 0
NS_SW_CS_ MGW_01.HW.NF.A
A GE2/0/0 - A F1S10-A -
A GE2/0/1 - A F1S10-B -
A GE2/0/2 - A F1S12-A -
A GE2/0/3 - A F1S12-B -
A GE2/0/4 - A F1S14-A -
A GE2/0/5 - A F1S14-B -
A GE2/0/6 - A F2S00-A -
A GE2/0/7 - A F2S00-B -
A GE2/0/8 - A F2S02-A -
NS_SW_CS_ GE2/0/9 - MGW_01.HW.NF.A F2S02-B -
-226-
A A
A GE2/0/10 - A F2S10-A -
A GE2/0/11 - A F2S10-B -
A GE2/0/12 - A F2S12-A -
A GE2/0/13 - A F2S12-B -
A GE2/0/14 - A F2S14-A -
A GE2/0/15 - A F2S14-B -
A GE2/0/16 - A F3S10-A -
A GE2/0/17 - A F3S10-B -
A GE2/0/18 - A F3S12-A -
A GE2/0/19 - A F3S12-B -
A GE2/0/20 - A F3S14-A -
A GE2/0/21 - A F3S14-B -
NS_SW_CS_ GMGW_01.HW.NF.
A GE2/0/22 - AA F1S10-A -
A GE2/0/23 - AA F1S10-B -
A GE2/0/24 - AA F2S10-A -
A GE2/0/25 - AA F2S10-B -
A GE2/0/26 - AA F3S10-A -
A GE2/0/27 - AA F3S10-B -
NS_SW_CS_ F00-S00-Card
A GE3/0/0 - MSC_01.HW.NF.AA 4/LAN0 -
A GE3/0/1 - MSC_01.HW.NF.AA 4/LAN0 -
A GE3/0/2 - A F1-S7-MC -
-227-
NS_SW_CS_ GMSC_01.HW.NF.A F00-S00-Card

A GE3/0/3 - A 4/LAN0 -
A GE3/0/4 - A 4/LAN0 -
A GE3/0/5 - AA F1-S7-MC -
NS_SW_CS_
A GE3/0/10 - MSC_01.HW.NF.AA O&M0 -
A GE3/0/11 - A O&M0 -
NS_SW_CS_ GMSC_01.HW.NF.A
A GE3/0/12 - A O&M0 -
A GE3/0/13 - AA O&M0 -
NS_SW_CS_ F00-S04-CAR
A GE3/0/14 - MSC_01.HW.NF.AA D4/LAN0 -
NS_SW_CS_
A GE3/0/20 - MSC_01.HW.NF.AA F0S08 -
NS_SW_CS_
A GE3/0/21 - MSC_01.HW.NF.AA F1S08 -
A GE3/0/22 - A F0S08 -
B GE2/0/0 - A F1S11-A -
B GE2/0/1 - A F1S11-B -
B GE2/0/2 - A F1S13-A -
B GE2/0/3 - A F1S13-B -
B GE2/0/4 - A F1S15-A -
B GE2/0/5 - A F1S15-B -
B GE2/0/6 - A F2S01-A -
B GE2/0/7 - A F2S01-B -
B GE2/0/8 - A F2S03-A -
B GE2/0/9 - A F2S03-B -
NS_SW_CS_ GE2/0/10 - MGW_01.HW.NF.A F2S11-A -
-228-
B A
B GE2/0/11 - A F2S11-B -
B GE2/0/12 - A F2S13-A -
B GE2/0/13 - A F2S13-B -
B GE2/0/14 - A F2S15-A -
B GE2/0/15 - A F2S15-B -
B GE2/0/16 - A F3S11-A -
B GE2/0/17 - A F3S11-B -
B GE2/0/18 - A F3S13-A -
B GE2/0/19 - A F3S13-B -
B GE2/0/20 - A F3S15-A -
B GE2/0/21 - A F3S15-B -
B GE2/0/22 - AA F1S11-A -
B GE2/0/23 - AA F1S11-B -
B GE2/0/24 - AA F2S11-A -
B GE2/0/25 - AA F2S11-B -
B GE2/0/26 - AA F3S11-A -
B GE2/0/27 - AA F3S11-B -
B GE3/0/0 - MSC_01.HW.NF.AA 4/LAN0 -
B GE3/0/1 - MSC_01.HW.NF.AA 4/LAN0 -
B GE3/0/2 - A F1-S8-MC -
B GE3/0/3 - A 4/LAN0 -
-229-

B GE3/0/4 - A 4/LAN0 -
B GE3/0/5 - AA F1-S8-MC -
NS_SW_CS_
B GE3/0/10 - MSC_01.HW.NF.AA O&M1 -
B GE3/0/11 - A O&M1 -
B GE3/0/12 - A O&M1 -
B GE3/0/13 - AA O&M1 -
NS_SW_CS_ F00-S05-CAR
B GE3/0/14 - MSC_01.HW.NF.AA D4/LAN0 -
NS_SW_CS_
B GE3/0/20 - MSC_01.HW.NF.AA F0S09 -
NS_SW_CS_
B GE3/0/21 - MSC_01.HW.NF.AA F1S09 -
B GE3/0/22 - A F0S09 -
CS Domain physical Topology in Microwave
MSC_01.HW.MW.AA
NE40E_01.HW.MW.AA MW_SW_CS_A
GMSC_01.HW.MW.AA
10G
1G
MGW_01.HW.MW.AA
NE40E_02.HW.MW.AA MW_SW_CS_B
GMGW_01.HW.MW.AA
Physical port connection in Microwave list below

NE40E_01.HW. XGE6/1/0 Eth-Trunk3 MW_SW_CS_ XGE1/0/0
MW.AA XGE7/1/0 0 A XGE1/0/1 Eth-Trunk30
NE40E_02.HW. XGE6/1/0 Eth-Trunk3 MW_SW_CS_ XGE1/0/0
MW.AA XGE7/1/0 0 B XGE1/0/1 Eth-Trunk30
MW_SW_CS_A XGE1/0/14 Eth-Trunk1 MW_SW_CS_ XGE1/0/14 Eth-Trunk10
-230-
XGE1/0/15 0 B XGE1/0/15
MGW_01.HW.
MW_SW_CS_A GE2/0/0 - MW.AA F1S10-A -
MGW_01.HW.
MW_SW_CS_A GE2/0/1 - MW.AA F1S10-B -
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
-231-
MGW_01.HW.
GMGW_01.H
MW_SW_CS_A GE2/0/22 - W.MW.AA F1S10-A -
GMGW_01.H
MW_SW_CS_A GE2/0/23 - W.MW.AA F1S10-B -
GMGW_01.H
GMGW_01.H
GMGW_01.H
GMGW_01.H
MSC_01.HW. F00-S00-Car
MW_SW_CS_A GE3/0/0 - MW.AA d4/LAN0 -
MW_SW_CS_A GE3/0/1 - MW.AA d4/LAN0 -
MGW_01.HW.
MW_SW_CS_A GE3/0/2 - MW.AA F1-S7-MC -
GMSC_01.HW F00-S00-Car
MW_SW_CS_A GE3/0/3 - .MW.AA d4/LAN0 -
MW_SW_CS_A GE3/0/4 - .MW.AA d4/LAN0 -
GMGW_01.H
MW_SW_CS_A GE3/0/5 - W.MW.AA F1-S7-MC -
MSC_01.HW.
MW_SW_CS_A GE3/0/10 - MW.AA O&M0 -
MGW_01.HW.
MW_SW_CS_A GE3/0/11 - MW.AA O&M0 -
GMSC_01.HW
MW_SW_CS_A GE3/0/12 - .MW.AA O&M0 -
GMGW_01.H
MW_SW_CS_A GE3/0/13 - W.MW.AA O&M0 -
MSC_01.HW. F00-S04-CA
MW_SW_CS_A GE3/0/14 - MW.AA RD4/LAN0 -
MSC_01.HW.
MW_SW_CS_A GE3/0/20 - MW.AA F0S08 -
MSC_01.HW.
MW_SW_CS_A GE3/0/21 - MW.AA F1S08 -
GMSC_01.HW
MW_SW_CS_A GE3/0/22 - .MW.AA F0S08 -
MW_SW_CS_B GE2/0/0 - MGW_01.HW. F1S11-A -
-232-
MW.AA
MGW_01.HW.
MW_SW_CS_B GE2/0/1 - MW.AA F1S11-B -
MGW_01.HW.
MW_SW_CS_B GE2/0/2 - MW.AA F1S13-A -
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
-233-
GMGW_01.H
MW_SW_CS_B GE2/0/22 - W.MW.AA F1S11-A -
GMGW_01.H
MW_SW_CS_B GE2/0/23 - W.MW.AA F1S11-B -
GMGW_01.H
GMGW_01.H
GMGW_01.H
GMGW_01.H
MW_SW_CS_B GE3/0/0 - MW.AA d4/LAN0 -
MW_SW_CS_B GE3/0/1 - MW.AA d4/LAN0 -
MGW_01.HW.
MW_SW_CS_B GE3/0/2 - MW.AA F1-S8-MC -
MW_SW_CS_B GE3/0/3 - .MW.AA d4/LAN0 -
MW_SW_CS_B GE3/0/4 - .MW.AA d4/LAN0 -
GMGW_01.H
MW_SW_CS_B GE3/0/5 - W.MW.AA F1-S8-MC -
MSC_01.HW.
MW_SW_CS_B GE3/0/10 - MW.AA O&M1 -
MGW_01.HW.
MW_SW_CS_B GE3/0/11 - MW.AA O&M1 -
GMSC_01.HW
MW_SW_CS_B GE3/0/12 - .MW.AA O&M1 -
GMGW_01.H
MW_SW_CS_B GE3/0/13 - W.MW.AA O&M1 -
MW_SW_CS_B GE3/0/14 - MW.AA RD4/LAN0 -
MSC_01.HW.
MW_SW_CS_B GE3/0/20 - MW.AA F0S09 -
MSC_01.HW.
MW_SW_CS_B GE3/0/21 - MW.AA F1S09 -
GMSC_01.HW
MW_SW_CS_B GE3/0/22 - .MW.AA F0S09 -
CS Domain physical Topology in Kirkos
-234-
NE40E_01.HW.KK.AA KK_SW_CS_A
MSC_01.HW.KK.AA
10G
1G
MGW_01.HW.KK.AA
NE40E_02.HW.KK.AA KK_SW_CS_B
Physical port connection in Kirkos list below

NE40E_01.HW. XGE6/1/0 Eth-Trunk3 KK_SW_CS_ XGE1/0/0
Eth-Trunk30
KK.AA XGE7/1/0 0 A XGE1/0/1
NE40E_02.HW. XGE6/1/0 Eth-Trunk3 XGE1/0/0
KK_SW_CS_B Eth-Trunk30
KK.AA XGE7/1/0 0 XGE1/0/1
XGE1/0/14 Eth-Trunk1 XGE1/0/14
KK_SW_CS_A KK_SW_CS_B Eth-Trunk10
XGE1/0/15 0 XGE1/0/15
MGW_01.HW.
KK_SW_CS_A GE2/0/0 - KK.AA F1S10-A -
MGW_01.HW.
KK_SW_CS_A GE2/0/1 - KK.AA F1S10-B -
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
-235-
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
KK_SW_CS_A GE3/0/0 - KK.AA d4/LAN0 -
KK_SW_CS_A GE3/0/1 - KK.AA d4/LAN0 -
MGW_01.HW.
KK_SW_CS_A GE3/0/2 - KK.AA F1-S7-MC -
MSC_01.HW.
KK_SW_CS_A GE3/0/10 - KK.AA O&M0 -
MGW_01.HW.
KK_SW_CS_A GE3/0/11 - KK.AA O&M0 -
KK_SW_CS_A GE3/0/14 - KK.AA RD4/LAN0 -
MSC_01.HW.
KK_SW_CS_A GE3/0/20 - KK.AA F0S08 -
MSC_01.HW.
KK_SW_CS_A GE3/0/21 - KK.AA F1S08 -
MGW_01.HW.
KK_SW_CS_B GE2/0/0 - KK.AA F1S11-A -
MGW_01.HW.
KK_SW_CS_B GE2/0/1 - KK.AA F1S11-B -
MGW_01.HW.
KK_SW_CS_B GE2/0/3 - MGW_01.HW. F1S13-B -
-236-
KK.AA
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
KK_SW_CS_B GE3/0/0 - KK.AA d4/LAN0 -
KK_SW_CS_B GE3/0/1 - KK.AA d4/LAN0 -
MGW_01.HW.
KK_SW_CS_B GE3/0/2 - KK.AA F1-S8-MC -
-237-
MSC_01.HW.
KK_SW_CS_B GE3/0/10 - KK.AA O&M1 -
MGW_01.HW.
KK_SW_CS_B GE3/0/11 - KK.AA O&M1 -
KK_SW_CS_B GE3/0/14 - KK.AA RD4/LAN0 -
MSC_01.HW.
KK_SW_CS_B GE3/0/20 - KK.AA F0S09 -
MSC_01.HW.
KK_SW_CS_B GE3/0/21 - KK.AA F1S09 -
CS Domain physical Topology in Bole
NE40E_01.HW.BL.AA BL_SW_CS_A
10G
MGW_01.HW.BL.AA 1G
NE40E_02.HW.BL.AA BL_SW_CS_B
Physical port connection in Bole list below:

BL_SW_CS_A Eth-Trunk30
BL.AA XGE7/1/0 0 XGE1/0/1
BL_SW_CS_B Eth-Trunk30
BL.AA XGE7/1/0 0 XGE1/0/1
BL_SW_CS_A BL_SW_CS_B Eth-Trunk10
XGE1/0/15 0 XGE1/0/15
MGW_01.HW.
BL_SW_CS_A GE2/0/0 - BL.AA F1S10-A -
MGW_01.HW.
BL_SW_CS_A GE2/0/1 - BL.AA F1S10-B -
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
-238-
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
BL_SW_CS_A GE3/0/0 - BL.AA F1-S7-MC -
MGW_01.HW.
BL_SW_CS_A GE3/0/10 - BL.AA O&M0 -
MGW_01.HW.
BL_SW_CS_B GE2/0/0 - BL.AA F1S11-A -
MGW_01.HW.
BL_SW_CS_B GE2/0/1 - BL.AA F1S11-B -
MGW_01.HW.
BL_SW_CS_B GE2/0/3 - MGW_01.HW. F1S13-B -
-239-
BL.AA
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
BL_SW_CS_B GE3/0/0 - BL.AA F1-S8-MC -
MGW_01.HW.
BL_SW_CS_B GE3/0/10 - BL.AA O&M1 -
CS Domain physical Topology in Arada
-240-
NE40E_01.HW.AD.AA AD_SW_CS_A
10G
MGW_01.HW.AD.AA 1G
NE40E_02.HW.AD.AA AD_SW_CS_B
Physical port connection in Arada list below:

NE40E_01.HW. XGE6/1/0 Eth-Trunk3 AD_SW_CS_ XGE1/0/0
Eth-Trunk30
AD.AA XGE7/1/0 0 A XGE1/0/1
AD_SW_CS_B Eth-Trunk30
AD.AA XGE7/1/0 0 XGE1/0/1
AD_SW_CS_A AD_SW_CS_B Eth-Trunk10
XGE1/0/15 0 XGE1/0/15
MGW_01.HW.
AD_SW_CS_A GE2/0/0 - AD.AA F1S10-A -
MGW_01.HW.
AD_SW_CS_A GE2/0/1 - AD.AA F1S10-B -
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
AD_SW_CS_A GE2/0/11 - MGW_01.HW. F2S10-B -
-241-
AD.AA
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
AD_SW_CS_A GE3/0/0 - AD.AA F1-S7-MC -
MGW_01.HW.
AD_SW_CS_A GE3/0/10 - AD.AA O&M0 -
MGW_01.HW.
AD_SW_CS_B GE2/0/0 - AD.AA F1S11-A -
MGW_01.HW.
AD_SW_CS_B GE2/0/1 - AD.AA F1S11-B -
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
-242-
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
MGW_01.HW.
AD_SW_CS_B GE3/0/0 - AD.AA F1-S8-MC -
MGW_01.HW.
AD_SW_CS_B GE3/0/10 - AD.AA O&M1 -
9.4.3 CS IP Address Planning

IP Address Planning is list below
SubInt NE40E_01.HW.K NE40E_02.HW.KK.

Site LogicalPort erface Vrf K.AA AA Vrrp Virtual IP Vrrp
710 VPN_OM 10.203.32.29/27 10.203.32.30/27 10.203.32.31/27 Yes
720 VPN_Sig 10.203.32.47/28 10.203.32.63/28
NF Trunk3 730 VPN_Media 10.203.32.95/27 10.203.32.127/27
740 VPN_Bi 10.203.32.141/28 10.203.32.142/28 10.203.32.143/28 Yes
750 VPN_Li 10.203.32.29/27 10.203.32.30/27 10.203.32.31/27 Yes
MW Trunk3 710 VPN_OM 10.186.128.29/27 10.186.128.30/27 10.186.128.31/27 Yes
-243-
720 VPN_Sig 10.186.128.47/28 10.186.128.63/28

730 VPN_Media 10.186.128.95/27 10.186.128.127/27
740 VPN_Bi 10.186.128.141/28 10.186.128.142/28 10.186.128.143/28 Yes
750 VPN_Li 10.186.128.29/27 10.186.128.30/27 10.186.128.31/27 Yes
710 VPN_OM 10.202.32.13/27 10.202.32.14/27 10.202.32.15/27 Yes
720 VPN_Sig 10.202.32.47/28 10.202.32.63/28
KK Trunk3 730 VPN_Media 10.202.32.95/27 10.202.32.127/27
740 VPN_Bi 10.202.32.141/28 10.202.32.142/28 10.202.32.143/28 Yes
750 VPN_Li 10.202.32.29/27 10.202.32.30/27 10.202.32.31/27 Yes
710 VPN_OM 10.184.128.13/27 10.184.128.14/27 10.184.128.15/27 Yes
Bole Trunk3 720 VPN_Sig 10.184.128.47/28 10.184.128.63/28
730 VPN_Media 10.184.128.95/27 10.184.128.127/27
710 VPN_OM 10.185.128.13/27 10.185.128.14/27 10.185.128.15
Arada Trunk3 720 VPN_Sig 10.185.128.47/28 10.185.128.63/28
730 VPN_Media 10.185.128.95/27 10.185.128.127/27
9.4.4 CS Vlan Planning

CS VLAN Planning is list below for site NifasSilk
NS_SW_CS_A GE2/0/0 vlan730

-244-

NS_SW_CS_B GE2/0/0 vlan730
-245-

CS VLAN Planning is list below for site Microwave
MW_SW_CS_A GE2/0/0 vlan730

-246-

MW_SW_CS_B GE2/0/0 vlan730
-247-

CS VLAN Planning is list below for site Kirkos
KK_SW_CS_A GE2/0/0 vlan730

-248-

KK_SW_CS_B GE2/0/0 vlan730
CS VLAN Planning is list below for site Bole
-249-
BL_SW_CS_A GE2/0/0 vlan730

BL_SW_CS_B GE2/0/0 vlan730
-250-

CS VLAN Planning is list below for site Arada
AD_SW_CS_A GE2/0/0 vlan730

AD_SW_CS_B GE2/0/0 vlan730
-251-

9.4.5 Configure Example for CS service

 Active and Standby Interface Scenario
Configuration on Master NE40E-X8

Create a VPN instance.
ip vpn-instance VPN_OM
ipv4-family
Configure VRRP on a Trunk sub interface.
interface Eth-Trunk3.710 //Create a VLANIF interface.
vlan-type dot1q 710
ip binding vpn-instance VPN_OM //Bind the VPN instance to a specific service interface.
ip address 10.203.32.29 255.255.255.224 //Configure an IP address for the VLANIF interface.
//Create a VRRP backup group and configure a virtual IP address as the MBB core-to-NodeB/eNodeB
gateway IP address.
//Set the priority of RSG5 to 120 in the VRRP backup group to allow RSG5 to become the master device.
-252-
//Set the preemption delay to 180s for RSG5 in the VRRP backup group.
Configure the VRRP recovery delay.
vrrp recover-delay 60 //Set the delay for restoring the status of a VRRP backup
group to 60 seconds.
Configure VPN to import routes.
The following uses direct routes and static routes as an example. You can import a required
routing protocol according to actual conditions.
bgp 100
ipv4-family vpn-instance VPN_OM
import-route direct
import-route static
Configuration on Slave NE40E-X8
ip vpn-instance VPN_OM
ipv4-family
Configure VRRP on a VLANIF interface.
ip binding vpn-instance VPN_OM
ip address 10.203.32.30 255.255.255.224
Configure VRRP on the slave RSG. The VRRP priority can be modified by monitoring the status
of BFD sessions. Therefore, fast VRRP primary/backup switchover can be achieved.
interface Eth-Trunk3.710
vrrp vrid 100 track bfd-session 300 increased 40 //Configure VRRP on the slave RSG. The VRRP
priority can be modified by monitoring the status of BFD sessions.
//Therefore, fast VRRP primary/backup
switchover can be
vrrp recover-delay 60 //Set the delay for restoring the status of a VRRP backup group to 60 seconds.
The following uses direct routes and static routes as an example. You can import a required routing
-253-
protocol according to actual conditions.

bgp 100
ipv4-family vpn-instance VPN_OM
import-route direct
import-route static

ip vpn-instance VPN_Sig
ipv4-family
Bind the VPN instance to the the sub-interfaces that connect the two RSGs
vlan-type dot1q 720
description to VPN_Sig
undo shutdown
ip binding vpn-instance VPN_Sig
ip address 10.203.32.4728
Import VPN routes.
bgp 100
import-route direct
import-route static
import-route direct
ipv4-family
-254-
vlan-type dot1q 720
undo shutdown
ip address 10.203.32.63 28
Import VPN routes.
bgp 100
import-route direct
import-route static
import-route ospf 100
9.5 PS Service Design

9.5.1 PS Service Scenario
Active and Standby Interface Scenario
 SGSN/GGSN/CG only active interface can receive packets.
 RSG configure Eth-Trunk + VRRP to protect link and node failure.
Figure 9- 30 PS Active and Standby Interface Scenario

Trunk1:10.31.0.4/29->Vlan500
Trunk2:10.31.0.12/29->Vlan501
……
Subif500:10.31.0.1/29 ->VPN_Ga
NE40E-X8 Subif501:10.31.0.9/29 ->VPN_Gom Port1:->Vlan500
SGSN9810
……
S9300 Port1:->Vlan501
Trunk1:10.31.0.5/29->Vlan500
Trunk2:10.31.0.13/29->Vlan501
……
Vrrp500:10.31.0.3/29:GW
Vrrp501:10.31.0.11/29:GW CG9812
Subif500:10.31.0.2/29 ->VPN_Ga Port1:->Vlan500

Subif501:10.31.0.10/29 ->VPN_Gom Port1:->Vlan501 GGSN9811
……
Trunk1:10.31.0.6/29->Vlan500
Trunk2:10.31.0.14/29->Vlan501
……
-255-
Dual Active Interfaces Scenario
 GGSN/SGSN Gn/Gi/Iu_C service use dual active interface ,enable OSPF with RSG
 RSG use IP FRR+BFD to protect link and node failure.
Connect Gn,Gn_DT interface on SGSN/GGSN to NE40E-X8
Figure 9- 31 PS Dual Active Interface Scenario
NE40E-X8 Subif200:10.15.0.89/30 ->VPN_Gn

Subif300:10.16.0.89/30 ->VPN_Gn_DT S9300 Port1:->Vlan200 300 SGSN9810
Ospf Vpn_Gn
Ospf VPN_Gi
Port1:->Vlan201 301 GGSN9811

Subif201:10.15.0.93/30 ->VPN_Gn
Subif301:10.16.0.93/30 ->VPN_Gn_DT
Connect Gi interface on GGSN to NE40E-X8
Figure 9- 32 PS Gi Interface Scenario
NE40E-X8
Subif1000:10.39.0.1/30 ->VPN_Gi
Ospf Vpn_Gi
SGSN9810
Subif1001:10.39.0.5/30 ->VPN_Gi
9.5.2 Physical Connection

PS Domain physical Topology in NifasSilk
-256-
SGSN
NE40E_01.HW.NS.AA NS_SW_PS_A
CG
NS_SW_PS_B GGSN
NE40E_02.HW.NS.AA
DNS
Physical port connection in NafasSilk list below

Source NE Destination NE
Physical Port LogicalPort Physical Port LogicalPort
XGE2/1/2 XGE3/0/8
NE40EX8_NS_ER XGE6/1/2 XGE3/0/9
Eth-Trunk25 NS_SW_PS_A Eth-Trunk25
_NEW_A XGE7/1/2 XGE4/0/8
XGE2/1/3 XGE4/0/9
XGE2/1/2 XGE3/0/8
NE40EX8_NS_ER XGE6/1/2 XGE3/0/9
Eth-Trunk25 NS_SW_PS_B Eth-Trunk25
_NEW_B XGE7/1/2 XGE4/0/8
XGE2/1/3 XGE4/0/9
XGE3/0/14 XGE3/0/14
XGE3/0/15 XGE3/0/15
NS_SW_CS_A Eth-Trunk10 NS_SW_CS_B Eth-Trunk10
XGE4/0/14 XGE4/0/14
XGE4/0/15 XGE4/0/15
USN_01.HW.N OMU0/0card4la
NS_SW_PS_A GE1/0/0 - -
S.AA n0
CG_01.HW.NS. CGU0/5Card3/L
AA an0
AA an0
AA an0
AA an0
DNS_01.HW.N
NS_SW_PS_A GE1/0/5 - eth0 -
S.AA
-257-
DNS_01.HW.N
NS_SW_PS_A GE1/0/6 - eth1 -
S.AA
DNS_01.HW.N
NS_SW_PS_A GE1/0/7 - iLO -
S.AA
UGW_01.HW.
NS_SW_PS_A GE1/0/8 - MPU0/17/0 -
NS.AA
E8000E_01.HW
NS_SW_PS_A GE1/0/9 - SRU4/0/0 -
.NS.AA
E8000E_02.HW
NS_SW_PS_A GE1/0/10 - SRU4/0/0 -
.NF.AA
USN_01.HW.N
NS_SW_PS_A GE1/0/11 - EPU/PFI0/11/3 -
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
UGW_01.HW.
NS_SW_PS_A GE1/0/18 - Giga1/0/2 -
NS.AA
UGW_01.HW.
NS_SW_PS_A GE1/0/19 - Giga1/0/3 -
NS.AA
UGW_01.HW.
NS_SW_PS_A GE1/0/20 - Giga1/0/0 -
NS.AA
UGW_01.HW.
NS_SW_PS_A GE1/0/21 - Giga1/0/1 -
NS.AA
UGW_01.HW.
NS_SW_PS_A GE1/0/22 - Giga1/0/4 -
NS.AA
UGW_01.HW.
NS_SW_PS_A GE1/0/23 - Giga1/0/5 -
NS.AA
USN_01.HW.N
NS_SW_PS_A GE1/0/24 - EPU/PFI 0/11/2 -
S.AA
NS_SW_PS_B GE1/0/0 - -
S.AA n0
AA an1
NS_SW_PS_B GE1/0/2 - CG_01.HW.NS. CGU0/8Card3/L -
-258-
AA an1
AA an1
AA an1
DNS_01.HW.N
NS_SW_PS_B GE1/0/6 - eth2 -
S.AA
UGW_01.HW.
NS_SW_PS_B GE1/0/8 - MPU0/18/0 -
NS.AA
E8000E_01.HW
NS_SW_PS_B GE1/0/9 - SRU5/0/0 -
.NS.AA
E8000E_02.HW
NS_SW_PS_B GE1/0/10 - SRU5/0/0 -
.NF.AA
USN_01.HW.N
NS_SW_PS_B GE1/0/11 - EPU/PFI0/13/3 -
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
UGW_01.HW.
NS_SW_PS_B GE1/0/18 - Giga2/0/2 -
NS.AA
UGW_01.HW.
NS_SW_PS_B GE1/0/19 - Giga2/0/3 -
NS.AA
UGW_01.HW.
NS_SW_PS_B GE1/0/20 - Giga2/0/0 -
NS.AA
UGW_01.HW.
NS_SW_PS_B GE1/0/21 - Giga2/0/1 -
NS.AA
UGW_01.HW.
NS_SW_PS_B GE1/0/22 - Giga2/0/4 -
NS.AA
UGW_01.HW.
NS_SW_PS_B GE1/0/23 - Giga2/0/5 -
NS.AA
USN_01.HW.N
NS_SW_PS_B GE1/0/24 - EPU/PFI 0/13/2 -
S.AA
PS Domain physical Topology in Microwave

-259-
SGSN
NE40E_01.HW.MW.AA MW_SW_PS_A
CG
MW_SW_PS_B GGSN
NE40E_02.HW.MW.AA
DNS
Physical port connection in Microwave list below

XGE2/1/2 XGE3/0/8
NE40EX8_MW_E XGE6/1/2 Eth-Trunk2 XGE3/0/9
MW_SW_PS_A Eth-Trunk25
R_NEW_A XGE7/1/2 5 XGE4/0/8
XGE2/1/3 XGE4/0/9
XGE2/1/2 XGE3/0/8
NE40EX8_MW_E XGE6/1/2 Eth-Trunk2 XGE3/0/9
MW_SW_PS_B Eth-Trunk25
R_NEW_B XGE7/1/2 5 XGE4/0/8
XGE2/1/3 XGE4/0/9
XGE3/0/14 XGE3/0/14
MW_SW_CS_A MW_SW_CS_B Eth-Trunk10
XGE4/0/14 0 XGE4/0/14
XGE4/0/15 XGE4/0/15
USN_01.HW.M OMU0/0card4la
MW_SW_PS_A GE1/0/0 - -
W.AA n0
CG_01.HW.MW CGU0/5Card3/L
.AA an0
.AA an0
.AA an0
.AA an0
DMW_01.HW.
MW_SW_PS_A GE1/0/5 - eth0 -
MW.AA
-260-
DMW_01.HW.
MW_SW_PS_A GE1/0/6 - eth1 -
MW.AA
DMW_01.HW.
MW_SW_PS_A GE1/0/7 - iLO -
MW.AA
UGW_01.HW.
MW_SW_PS_A GE1/0/8 - MPU0/17/0 -
MW.AA
E8000E_01.HW.
MW_SW_PS_A GE1/0/9 - SRU4/0/0 -
MW.AA
E8000E_02.HW.
MW_SW_PS_A GE1/0/10 - SRU4/0/0 -
NF.AA
USN_01.HW.M
MW_SW_PS_A GE1/0/11 - EPU/PFI0/11/3 -
W.AA
USN_01.HW.M
W.AA
USN_01.HW.M
W.AA
USN_01.HW.M
W.AA
USN_01.HW.M
W.AA
USN_01.HW.M
W.AA
USN_01.HW.M
W.AA
UGW_01.HW.
MW_SW_PS_A GE1/0/18 - Giga1/0/2 -
MW.AA
UGW_01.HW.
MW_SW_PS_A GE1/0/19 - Giga1/0/3 -
MW.AA
UGW_01.HW.
MW_SW_PS_A GE1/0/20 - Giga1/0/0 -
MW.AA
UGW_01.HW.
MW_SW_PS_A GE1/0/21 - Giga1/0/1 -
MW.AA
UGW_01.HW.
MW_SW_PS_A GE1/0/22 - Giga1/0/4 -
MW.AA
UGW_01.HW.
MW_SW_PS_A GE1/0/23 - Giga1/0/5 -
MW.AA
USN_01.HW.M
MW_SW_PS_A GE1/0/24 - EPU/PFI 0/11/2 -
W.AA
MW_SW_PS_B GE1/0/0 - -
S.AA n0
AA an1
MW_SW_PS_B GE1/0/2 - CG_01.HW.NS. CGU0/8Card3/L -
-261-
AA an1
AA an1
AA an1
DNS_01.HW.N
MW_SW_PS_B GE1/0/6 - eth2 -
S.AA
UGW_01.HW.N
MW_SW_PS_B GE1/0/8 - MPU0/18/0 -
S.AA
E8000E_01.HW.
MW_SW_PS_B GE1/0/9 - SRU5/0/0 -
NS.AA
E8000E_02.HW.
MW_SW_PS_B GE1/0/10 - SRU5/0/0 -
NF.AA
USN_01.HW.N
MW_SW_PS_B GE1/0/11 - EPU/PFI0/13/3 -
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
UGW_01.HW.N
MW_SW_PS_B GE1/0/18 - Giga2/0/2 -
S.AA
UGW_01.HW.N
MW_SW_PS_B GE1/0/19 - Giga2/0/3 -
S.AA
UGW_01.HW.N
MW_SW_PS_B GE1/0/20 - Giga2/0/0 -
S.AA
UGW_01.HW.N
MW_SW_PS_B GE1/0/21 - Giga2/0/1 -
S.AA
UGW_01.HW.N
MW_SW_PS_B GE1/0/22 - Giga2/0/4 -
S.AA
UGW_01.HW.N
MW_SW_PS_B GE1/0/23 - Giga2/0/5 -
S.AA
USN_01.HW.N
MW_SW_PS_B GE1/0/24 - EPU/PFI 0/13/2 -
S.AA
PS Domain physical Topology in Kirkos

-262-
SGSN
NE40E_01.HW.KK.AA KK_SW_PS_A
CG
KK_SW_PS_B GGSN
NE40E_02.HW.KK.AA
Physical port connection in Kirkos list below

XGE2/1/2 XGE3/0/8
NE40EX8_KK_ER XGE6/1/2 XGE3/0/9
Eth-Trunk25 KK_SW_PS_A Eth-Trunk25
_NEW_A XGE7/1/2 XGE4/0/8
XGE2/1/3 XGE4/0/9
XGE2/1/2 XGE3/0/8
NE40EX8_KK_ER XGE6/1/2 XGE3/0/9
Eth-Trunk25 KK_SW_PS_B Eth-Trunk25
_NEW_B XGE7/1/2 XGE4/0/8
XGE2/1/3 XGE4/0/9
XGE3/0/14 XGE3/0/14
XGE3/0/15 XGE3/0/15
KK_SW_CS_A Eth-Trunk10 KK_SW_CS_B Eth-Trunk10
XGE4/0/14 XGE4/0/14
XGE4/0/15 XGE4/0/15
USN_01.HW.K OMU0/0card4la
KK_SW_PS_A GE1/0/0 - -
K.AA n0
CG_01.HW.KK. CGU0/5Card3/L
AA an0
AA an0
AA an0
AA an0
UGW_01.HW.
KK_SW_PS_A GE1/0/8 - MPU0/17/0 -
KK.AA
E8000E_01.HW
KK_SW_PS_A GE1/0/9 - SRU4/0/0 -
.KK.AA
E8000E_02.HW
KK_SW_PS_A GE1/0/10 - SRU4/0/0 -
.NF.AA
-263-
USN_01.HW.K
KK_SW_PS_A GE1/0/11 - EPU/PFI0/11/3 -
K.AA
USN_01.HW.K
K.AA
USN_01.HW.K
K.AA
USN_01.HW.K
K.AA
USN_01.HW.K
K.AA
USN_01.HW.K
K.AA
USN_01.HW.K
K.AA
UGW_01.HW.
KK_SW_PS_A GE1/0/18 - Giga1/0/2 -
KK.AA
UGW_01.HW.
KK_SW_PS_A GE1/0/19 - Giga1/0/3 -
KK.AA
UGW_01.HW.
KK_SW_PS_A GE1/0/20 - Giga1/0/0 -
KK.AA
UGW_01.HW.
KK_SW_PS_A GE1/0/21 - Giga1/0/1 -
KK.AA
UGW_01.HW.
KK_SW_PS_A GE1/0/22 - Giga1/0/4 -
KK.AA
UGW_01.HW.
KK_SW_PS_A GE1/0/23 - Giga1/0/5 -
KK.AA
USN_01.HW.K
KK_SW_PS_A GE1/0/24 - EPU/PFI 0/11/2 -
K.AA
KK_SW_PS_B GE1/0/0 - -
S.AA n0
AA an1
AA an1
AA an1
AA an1
UGW_01.HW.
KK_SW_PS_B GE1/0/8 - MPU0/18/0 -
NS.AA
E8000E_01.HW
KK_SW_PS_B GE1/0/9 - SRU5/0/0 -
.NS.AA
KK_SW_PS_B GE1/0/10 - E8000E_02.HW SRU5/0/0 -
-264-
.NF.AA
USN_01.HW.N
KK_SW_PS_B GE1/0/11 - EPU/PFI0/13/3 -
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
USN_01.HW.N
S.AA
UGW_01.HW.
KK_SW_PS_B GE1/0/18 - Giga2/0/2 -
NS.AA
UGW_01.HW.
KK_SW_PS_B GE1/0/19 - Giga2/0/3 -
NS.AA
UGW_01.HW.
KK_SW_PS_B GE1/0/20 - Giga2/0/0 -
NS.AA
UGW_01.HW.
KK_SW_PS_B GE1/0/21 - Giga2/0/1 -
NS.AA
UGW_01.HW.
KK_SW_PS_B GE1/0/22 - Giga2/0/4 -
NS.AA
UGW_01.HW.
KK_SW_PS_B GE1/0/23 - Giga2/0/5 -
NS.AA
USN_01.HW.N
KK_SW_PS_B GE1/0/24 - EPU/PFI 0/13/2 -
S.AA
9.5.3 PS IP Address Planning

IP Address Planning is list below
LogicalPo SubInterfa NE40E_01.HW.KK. NE40E_02.HW.KK. Vrrp Virtual Vrr

rt ce Vrf AA AA IP p
10.203.0.89/2
910 VPN_Gb 10.203.0.90/29 10.203.0.91/29 9 Yes
VPN_Si
Trunk1 920 g 10.203.0.65/30 - -
VPN_Si
921 g - 10.203.0.69/30 -
930 VPN_Iu 10.203.0.82/29 10.203.0.83/29 10.203.0.81/2 Yes
-265-
u 9
940 VPN_Gn 10.203.0.17/29 - -
941 VPN_Gn - 10.203.0.25/29 -
10.203.0.33/2
950 VPN_Ga 10.203.0.34/28 10.203.0.35/28 Yes
8
VPN_O 10.203.0.129/
960 10.203.0.130/27 10.203.0.131/27 Yes
M 27
10.203.0.193/
970 VPN_Gy 10.203.0.194/29 10.203.0.195/29 29 Yes
10.203.0.121/
980 VPN_Li 10.203.0.122/28 10.203.0.123/28
28 Yes
990 VPN_Gn 10.203.0.201/30 - -
991 VPN_Gn - 10.203.0.205/30 -
10.203.0.105/
1020 VPN_S1 10.203.0.106/29 10.203.0.107/29 29 Yes
VPN_S1
1030 U 10.203.0.225/30 - -
VPN_S1
1031 U - 10.203.0.229/30 -
10.203.1.17/2
1040 VPN_Gx 10.203.1.18/29 10.203.1.19/29 9 Yes
10.203.0.249/
1010 VPN_Bi 10.203.0.250/29 10.203.0.251/29 29 Yes
9.5.4 PS Vlan Planning

CS VLAN Planning is list below for site Microwave
MW_SW_PS_A GE1/0/0 vlan960

-266-

MW_SW_PS_B GE1/0/0 vlan960
CS VLAN Planning is list below for site NifasSilk
-267-
NS_SW_PS_A GE1/0/0 vlan960

NS_SW_PS_B GE1/0/0 vlan960
-268-

CS VLAN Planning is list below for site Kirkos
KK_SW_PS_B GE1/0/0 vlan960

9.5.5 Configure Example for PS service

Configure Example
 Active and Standby Interface Scenario

-269-
ip vpn-instance VPN_Gb
ipv4-family
Configure VRRP on a Trunk sub interface.
vlan-type dot1q 910
ip binding vpn-instance VPN_Gb//Bind the VPN instance to a specific service interface.
ip address 10.202.0.90 29 //Configure an IP address for the VLANIF interface.
vrrp vrid 100 virtual-ip 10.202.0.89 //Create a VRRP backup group and configure a virtual IP
address as the MBB core-to-NodeB/eNodeB gateway IP address.
vrrp vrid 100 priority 120 //Set the priority of RSG5 to 120 in the VRRP backup group to allow
RSG5 to become the master device.
vrrp vrid 100 preempt-mode timer delay 180 //Set the preemption delay to 180s for RSG5 in the
VRRP backup group.
vrrp recover-delay 60 //Set the delay for restoring the status of a VRRP backup
group to 60 seconds.
bgp 100
ipv4-family vpn-instance VPN_Gb
import-route direct
import-route static
ip vpn-instance VPN_Gb
ipv4-family
-270-

Configure VRRP on a VLANIF interface.
ip binding vpn-instance VPN_Gb
ip address 10.202.0.91 29
Configure VRRP on the slave RSG. The VRRP priority can be modified by monitoring the status of
BFD sessions. Therefore, fast VRRP primary/backup switchover can be achieved.
vrrp vrid 100 track bfd-session 300 increased 40 //Configure VRRP on the slave RSG. The VRRP
priority can be modified by monitoring the status of BFD sessions.
//Therefore, fast VRRP primary/backup switchover can be
vrrp recover-delay 60 //Set the delay for restoring the status of a VRRP backup group to 60 seconds.
bgp 100
ipv4-family vpn-instance VPN_Gb
import-route direct
import-route static
 Dual Active Interfaces Scenario

ipv4-family
vlan-type dot1q 920
-271-
undo shutdown
ip address 10.202.0.65 30
Import VPN routes.
bgp 100
ipv4-family vpn-instance VPN_Sig
import-route direct
import-route static
import-route direct
ip vpn-instance IPRAN
ipv4-family
vlan-type dot1q 920
undo shutdown
ip address 10.202.0.69 30
Import VPN routes.
bgp 100
ipv4-family vpn-instance VPN_Sig
import-route direct
import-route static
import-route ospf 100
-272-
10 Fixed-Line Services Implement
10.1 HSI Services Design

10.1.1 HSI Services Overview
Residential HSI services dynamically obtain IP addresses using PPPoE. Following Figure shows the
residential HSI service transmission process.
Figure 10- 1 Residential HSI service transmission process
RGW OLT
PC ONT UPE AGG BRAS NAT AAA Server
initiates a PPPoE dialup sends authentication info
assigns an IP address authentication succeeds
The RGW initiates a PPPoE dialup.
The BRAS responds to the PPPoE dialup and sends authentication information to the AAA server
for remote authentication.
If authentication succeeds, the BRAS assigns an IP address from its address pool to the RGW. If
the BRAS assigns a private network IP address to the RGW, the IP address must be translated into a
public network IP address using NAT.below lists major functions of devices on the residential HSI
service bearer network.
Table 10- 1 major functions of devices on the residential HSI service bearer network
Device Function
RGW Works in routed mode to initiate PPPoE dialups.

ONT/Modem Transparently transmits PPPoE services.
Inserts PPPoE+ information into packets to identify the physical
MxU/MSAG
interfaces to which users are connected.
UPE/AGG Transparently transmits PPPoE packets with PPPoE+ information.
-273-
Device Function
 Terminates PPPoE tags and sends the residential HSI service

authentication information to an AAA server.
BRAS
 Assigns an IP address from the local address pool to the RGW after
authentication succeeds.
Translates the private network IP address assigned by the BRAS to the

NAT
RGW into a public network IP address.
 Saves user authentication information, including the user name and
AAA password.
 Implements user authentication, authorization, and accounting.
10.1.2 Bearer Requirements

HSI services are high-speed Internet services provided by ET IPRAN networks. Following figure shows
the residential HSI service bearer mode.
Figure 10- 2 residential HSI service bearer mode
AAA U2000
Server Farm
VLAN PVC VLAN

MxU
RGW Modem BRAS NAT
Aggregation
Network
PC RGW ONT OLT UPE AGG P
HSI VLAN L2VPN VLAN Private IP Public IP
Details about service bearer are as follows:
 The RGW adds a single VLAN tag to each HSI packet and sends the tagged packets to the
MSAG. The MSAG sends the packets to the UPE.
 The UPE terminates VLAN tags and sends the HSI packets received from the MSAG through
VSIs to the AGG over a VPLS network.
 The AGG terminates VPLS labels, adds VLAN tags to the packets, and transmits the packets to
the BRAS. The BRAS terminates the VLAN tags.
-274-
 The BRAS assigns IP addresses to HSI packets. If private network IP addresses are assigned,
these addresses are translated into public network IP addresses using NAT before the packets are
transmitted to the backbone network.
10.1.3 Service Deploy

Figure 10- 3 HSI service deploy
Huawei IPRAN HVPLS Solution will be Deployed for HIS Service in ET IP RAN Network
 IS-IS multi-process are used for the access and aggregation rings.
 LDP lsps are established between the CSGs and ASGs and between the ASGs and RSGs, but not
between the CSGs and RSGs.
 MPLS LDP remote peer relationships are established between the CSGs and ASGs and between
the ASGs and RSGs, but not between the UPEs and NPEs.
 HVPLS Will be deployed on the network
There is the typical Scenarios in ET IP RAN Network:
-275-
Figure 10- 4 HSI service typical topology
Akaki-CX600-X8-A&B
ATN950B
CX600-X8
Kality-CX600-X3-A NifasSilk-CX600-X16-A
ATN950B
Kality-CX600-X3-B NifasSilk-CX600-X16-B
ATN950B
Lebu-CX600-X8-A&B
VPLS Design:
− HVPLS Will be deployed on ASG towards to CSG. And Spoken PW will be Create on ASG
− VLL will be deployed on CSG towards to ASG. And Hub Pw will be Create On CSG
− VPLS will be deployed on ASG and RSG, and Hub PW will be create on them.
− Each MSAG need configured one VSI on ASG And RSG
Figure 10- 5 HIS service overview
ATN950B
Akaki-CX600-X8-A&B
NafaSilk-CX600-X16-A
Hub Pw Hub Pw
V SI V SI
Hu Pw
Spk
Pw b
Pw Hub
Pw
Hub Kality-CX600-X3-A
V LL
Hub
Pw Hu
ATN950B Pw b
Spk Hub Pw
Pw V SI V SI
Hub Pw Hub Pw
Kality-CX600-X3-B NafaSilk-CX600-X16-B
ATN950B
Lebu-CX600-X8-A&B
VLAN Design:
− The ATN interface connected the MSAG will be configured as dot1q mode; ATN identification the
MSAG by Service Vlan.
− The Service Vlan for the MSAG must be different
-276-
Figure 10- 6 HSI service VLAN design
Figure 10- 7 HSI packet forwarding overview
Access Tunnel Aggregate Tunnel

L3VPN L3VPN
HVPN
ATN950B Kaliti-CX600-X3-A
PDU PDU PDU PDU

IP IP IP IP
C-Vlan C-Vlan C-Vlan C-Vlan
S-Vlan L2-Eth Mac Fwd L2-Eth S-Vlan
L2-Eth Mpls Mpls L2-Eth
Mpls Mpls
L2-Eth L2-Eth
From Bras to MSAG Station:
− The RSG checks the private Mac forward table, remove S-Vlan adds an inner-label for VSI
service and an outer-label for Aggregate MPLS tunnel, and forwards the packets to the next hop
ASG.
− The ASG checks the dual-layer label table and remove the inner-label and outer-label, check the
private mac forward table and adds two labels for VSI service and access MPLS tunnel, and
forwards the packets to the specified next hop CSG (ATN950B).
− Upon receipt, the CSG (ATN950B) removes the inner and outer labels, searches the private Mac
forward table, and finds the outbound interface. The CSG(ATN950B) then add S-Vlan forwards the
packets through the outbound interface to the MSAG.
-277-
From MSAG to Bras:
− The CSG (ATN950B) checks the private Mac Forward Table, remove S-Vlan adds an inner-label
for VSI service and an outer-label for access MPLS tunnel, and forwards the packets to the next hop
ASG.
− The ASG checks the dual-layer label table and remove the dual-layer label, check the Mac
forward table, and adds inner-label for vsi and outer-label for aggregate MPLS tunnel, and
forwards the packets to the specified next hop RSG .
− Upon receipt, the RSG removes the inner and outer labels, searches the private Mac forward table,
and finds the outbound interface. The RSG then forwards the packets through the outbound interface
to the Bras
10.1.4 HA
Figure 10- 8 HSI reliability design
Akaki-CX600-X8-A&B
ATN950B 3
3 3
1 1 NifasSilk-CX600-X16-A
1 V SI2 Hub Pw Hub Pw V SI

5
Hub
Pw Spk
Pw
Hu
b
Pw
Kality-CX600-X3-A
Hub
Pw
4 6
V LL
Hub
Pw Hu
ATN950B Pw b
Spk Hub Pw
Pw V SI V SI
Hub Pw Hub Pw
Kality-CX600-X3-B NifasSilk-CX600-X16-B
ATN950B
Lebu-CX600-X8-A&B
Table 10- 2 Service protects information
Fault Location Fault Protection Backup Path

Detection Switching
Method Technique
Fault1 BFD for IGP IGP FC Red Path
(Link between ATN950B in on the access LDP convergence
Access Ring) ring
Fault2 BFD for IGP PW redundancy Blue Path
(ASG) on the access IGP FC
ring LDP convergence
-278-
BFD for IGP Mac withdraw will

on the agg be send
ring Delete Mac
forward table.
Unknown packet
broadcast in the Vsi
Fault3 BFD for IGP IGP FC Green Path
(Link between CX600s in on the agg LDP convergence
Agg Ring) ring
Fault4 BFD for IGP Delete Mac Yellow Path
(RSG) on the agg forward table.
ring BFD for Unknown packet
VRRP broadcast in the Vsi
Fault5 Interface fast Delete Mac Yellow Path
(Link between RSG and feeling forward table.
Bras) Unknown packet
Fault6 Interface fast Delete Mac Yellow Path
(RSG) feeling forward table.
Unknown packet
10.2 VOIP Services Design

10.2.1 VOIP Services Overview
Individual VoIP services connect to core network equipment using SIP/H.248 and obtain the private network's IP addresses
through the DHCP server. Following figure shows VoIP service procedure
-279-
Figure 10- 9 VoIP service procedure
POTS Phone ONT OLT

RGW UPE AGG DHCP Server SBC
DHCP Client(Option60/61) DHCP Relay
authenticate，assign IP、distribute SBC domain name
VoIP session setup

conversation
 A VoIP user uses a POTS phone to set up a VoIP session.
 The RGW/ONT converts analog signals to digital signals, initiates the VoIP session request, and
sends the DHCP authentication request to the remote DHCP server.
 The UPE relays and transparently transmits DHCP packets to the DHCP server.
 The DHCP server authenticates the VoIP user and assigns private network's IP address for the
RGW/ONT (integrating IAD).
 The SBC registers the VoIP user to set up the VoIP session with the RGW/ONT.
The following table lists main functions of devices deployed at different network layers.
Table 10- 3 Main functions of devices deployed at different network layers
Device Function
1. Initiates DHCP authentication requests and encapsulates option

60/61 information. Option 60 identifies the IAD type, usually used as
the domain name for authentication. Option 61 carries the MAC
RGW/ONT
address of the IAD module.
2. Encapsulates POTS phone signals into SIP media/signaling flows
and initiates a VoIP session.
MxU/MSAG Transparently transmits DHCP packets.
Functions as the DHCP relay agent to transparently transmit DHCP
UPE
packets to the DHCP server in the unicast way.
1. Authenticates the VoIP user based on option 60/61.
DHCP server 2. Assigns a private network IP address to the RGW/ONT (with IAD
integrated) and sends the SBC domain name.
-280-
Registers the VoIP user to set up the VoIP session with the
SBC
RGW/ONT.
Integrated in the RGW/ONT and implements voice- and digital-signal
IAD
conversion.
10.2.2 Bearer Requirements

VoIP services are voice services provided over an IP network. According to different user access
terminals, this FBB version includes the following two scenarios (with the same service bearer
mode):
POTS phone+RGW (with IAD integrated)
POTS phone+ONT (with IAD integrated)
Figure 10- 10 VoIP service bearer mode
U2000 DHCP server

Server Farm
VLAN PVC VLAN
RGW
Scenario 2
Modem MxU
POTS phone SBC
Aggregation
Scenario 1 Network NGN/IMS
RGW
POTS phone ONT OLT UPE AGG SoftX
P
VoIP VLAN L3VPN
As shown in Figure 10-10, VoIP services are transmitted to the CSG from the RGW through VLANs and
then sent to the NGN/IMS core network using MPLS L3VPN. The detailed service bearer solution is as
follows:
After the RGW adds VLAN tags to VoIP packets and sends the tagged packets to the MSAG, the
MSAG sends the packets to the UPE.
The UPE terminates the service VLAN of VoIP services, specifies VPN instances, and sends the
signaling and media flows to the session border control (SBC) over an L3VPN network. Devices on
the core network implement VoIP communication.
The Network from CSG to RSG is the Targets Network of ET IPRAN Project
10.2.3 Service Deploy

Design Principles
-281-
L3 Network will be provide for this service. So the HVPN solution will be deployed in the network. The
principles is the same as the Wireless RAN Side service. More detail please check “chapter 9.1
2G/3G/LTE S1 Ethernet Service”
Route Advertisement:
Route Reflectors Design:
The route reflectors design is the same as the Wireless RAN Side service. More detail please check
“chapter 9.1 2G/3G/LTE S1 Ethernet Service”
Route Advertisement Design:
The route reflectors Design is the same as the Wireless RAN Side service. More detail please check
Route Priorities Design:
The Route Priorities design is the same as the Wireless RAN Side service. More detail please check
RD-RT Design:
The Route Priorities design is the same as the Wireless RAN Side service. More detail please check
Vrf Design:
Vrf which named “VPN_VOIP” will be assign for VOIP service.
Packet Forwarding
The packet forwarding design is the same as the Wireless RAN Side service. More detail please check
-282-
10.2.4 HA
The Protection Switching design is the same as the Wireless RAN Side service. More detail please check
-283-
11 Interconnection Implement
11.1 Overview
This chapter describes the Interconnection implement between existing IP Core network and
expansion network. It involves various aspects of Physical Network Design, Logical Network
Design, Network Site Design, IGP Design, BGP Design, MPLS Design, Services Bearer and VRF
Design.
Here we provide IPCORE traffic model general overview, include inter-stie traffic model, inter-site
traffic model, inter-vendor traffic model and PS traffic model.
Figure 11- 1 Inter-site Traffic Model

BR-1 BR-2
IP CORE
ZTE IP NGN ZTE IP NGN
Inter-Site
ERA-1 ERA-2 ERB-1 ERB-2
Traffic
Intra-Site
Traffic
NE40E-X8 NE40E-X8
S9303
SITEA SITEB
A/Iu_CS/Signalin A/Iu_CS/Signalin Gom

g Gom g
Signaling Signaling
CX600-
CX600-
A/Abis/Gb X16 A/Abis/Gb X16
Iu_b/Iu_CS/Iu_U/Iu- Iu_b/Iu_CS/Iu_U/Iu-
C C
IP BH
-284-
Figure 11- 2 Inter-site CS Traffic Model

BR-1 BR-2
IP CORE
Inter-Site
Traffic
ZTE CS ZTE CS
NE40E-X8 NE40E-X8
S9303
SITEA SITEB

g Gom g
Signaling Signaling
CX600-
CX600-
IP BHA/Abis/Gb X16
A/Abis/Gb X16 Iu_b/Iu_CS/Iu_U/Iu-
Iu_b/Iu_CS/Iu_U/Iu-
C C
Figure 11- 3 Inter-Vendor Traffic Model

BR-1 BR-2
IP CORE
Inter-Site
Traffic
Intra-Site
Traffic
ZTE CS ZTE CS
NE40E-X8 NE40E-X8
S9303
SITEA SITEB

g Gom g
Signaling Signaling
CX600-
CX600-
A/Abis/Gb X16 A/Abis/Gb X16
Iu_b/Iu_CS/Iu_U/Iu- Iu_b/Iu_CS/Iu_U/Iu-
C C
IP BH
Figure 11- 4 PS Traffic Model from SGSN/GGSN to RNC

BR1 BR2
IP CORE Inter-Site
ZTE IP NGN ZTE IP NGN Traffic
ER ER ER ER Intra-Site
Traffic
NE40E-X8
NE40E-X8
E8000E S9303
S9303 E1000E
Gn/Gp/Ga/Iu_C/
Gi Gi Gr/Signaling/Gb/Li Gn/Gp/Ga/Iu_C/
Gi
Gr/Signaling/Gb/Li Gi
Gn/Gp/ Gn/Gp/
Signaling/Li/Gy Signaling/Li/Gy
CX600-X16 CX600-X16
IP BH
A/Abis/Gb A/Abis/Gb
Iu_b/Iu_CS/Iu_U/Iu-C Iu_b/Iu_CS/Iu_U/Iu-C
-285-
11.2 Interconnection Topology Design

11.2.1 Overview
This section describes the Interconnection of physical network between existing IP Core network
and expansion network. It involves physical connection in various sites of Kirkos, Bole, Nifas Silk,
Microwave and Arada.
11.2.2 Physical Network Scope

Interconnection network involves followed devices: Existing Core Router, Existing Edge Router,
expansion Edge Router (NE40E), expansion PS&CS, and expansion IP RAN RSG. As shown
followed:
Figure 11- 5 physical Network design in core site
IGW
1. Mekele 2. Bahirdar 3.Addis(Bole) 5. Dire Dawa
T8000
BR Layer T1200/M6000
NE40E-X8
Bole RR
CR Layer MicroWave CX600-X16
E8000E
8 8 8 8 Arada
S9300
10G POS
ER Layer Bole Nifas Silk Kirkos 10G LAN
10GE LAG
GE LAG
PS
CS PS PS
CS CS
CS CS
Capital IP RAN
In expansion project, 10 NE40Es (ER) will be connected to existing IP Core Network. Through
these ERs, 3 PS networks, 5 CS networks and IP RAN will be connected to existing IP Core
network.
In current phase of expansion project, NE40Es are connected to existing IP core in two ways:
 NE40Es are connected to existing CRs directly in Microwave, Bole, Kirkos and Arada site. 8
GE LAG will be used to connect NE40Es to CR in Microwave site and Kirkos site. 10GE direct
connect in Bole and Arada.
 NE40Es are connected to existing ERs in Nifas Silk site, because there are no enough CR port
resources or fiber resources in Nifas Silk site.
-286-
11.2.3 Logical Network Scope

Figure 11- 6 logical network design
IGW
1. Mekele 5. Dire Dawa T8000
2. Bahirdar 3.Addis(Bole)
NE40E-X8
CR Layer Bole Arada

RR
Bole Nifas Silk MicroWave Kirkos Arada

ER Layer
11.3 Naming & Addressing

11.3.1 Network Device Naming
Following naming convention is proposed for Globe Nemesis Network:
Name format：[Site]- [Type] - [Function] - [Plane]
- Site – Indicate the site name
- Function – Indicates the application/service of equipment installed (CS,PS,ER,CR)
- Type – Indicates type of equipment (FW for e8000e, SW for switch)
- Plane – Indicates the equipment is a Plane A Device or Plane B Device
Following table details the names of sites used for the interconnection:
Table 11- 1 core site list
No Sites
1 Arada
2 Bole
3 Kirkos
4 Microwave
5 Nifas Silk
Table 11- 2 core site equipment list
NO Site Device Name of the

-287-
Device
M6000 AD_CR_A
M6000 AD_CR_B
NE40E-X8 AD_ER_HW_A
NE40E-X8 AD_ER_HW_B
1 Arada CX600-X16 AD_RSG_A
CX600-X16 AD_RSG_B
S9303 AD_SW_CS_A
S9303 AD_SW_CS_B
M6000 BL_CR_A
M6000 BL_CR_B
NE40E-X8 BL_ER_HW_A
NE40E-X8 BL_ER_HW_B
2 Bole CX600-X16 BL_RSG_A
CX600-X16 BL_RSG_B
S9303 BL_SW_CS_A
S9303 BL_SW_CS_B
NE40E-X8 KK_ER_HW_A
NE40E-X8 KK_ER_HW_B
CX600-X16 KK_RSG_A
CX600-X16 KK_RSG_B
S9303 KK_SW_CS_A
3 Kirkos
S9303 KK_SW_CS_B
E8000E KK_FW_PS_A
E8000E KK_FW_PS_B
S9306 KK_SW_PS_A
S9306 KK_SW_PS_B
M6000 MW_CR_A
M6000 MW_CR_B
4 MicroWave NE40E-X8 MW_ER_HW_A
NE40E-X8 MW_ER_HW_B
CX600-X16 MW_RSG_A
-288-
CX600-X16 MW_RSG_B
S9303 MW_SW_CS_A
S9303 MW_SW_CS_B
E8000E MW_FW_PS_A
E8000E MW_FW_PS_B
S9303 MW_SW_PS_A
S9303 MW_SW_PS_B
M6000 NS_ER_Data_A
M6000 NS_ER_Data_B
NE40E-X8 NS_ER_HW_A
NE40E-X8 NS_ER_HW_B
CX600-X16 NS_RSG_A
CX600-X16 NS_RSG_B
5 Nifas Silk
S9303 NS_SW_CS_A
S9303 NS_SW_CS_B
E8000E NS_FW_PS_A
E8000E NS_FW_PS_B
S9306 NS_SW_PS_A
S9306 NS_SW_PS_B
11.3.2 IP Address Planning for Interconnection

There are three categories of address in NE40Es:
 Equipment loopback address
 Interface address
 Service address
This section mainly deals with address planning for equipment loopback and interface address.
Service address will be covered in wireless core design. The available IP addresses for
interconnection are:
 loopback address:
 Interface address provided
The loopback addresses planning for NE40E equipments are shown below:
Table 11- 3 Loopback assignment design
Site Device Loopback IP

Nifas Silk NS_ER_HW_A 10.0.5.239
Nifas Silk NS_ER_HW_B 10.0.5.240
-289-
MicroWave MW_ER_HW_A 10.0.5.231

MicroWave MW_ER_HW_B 10.0.5.232
Kirkos KK_ER_HW_A 10.0.5.237

Kirkos KK_ER_HW_B 10.0.5.238
Bole BL_ER_HW_A 10.0.5.233

Bole BL_ER_HW_B 10.0.5.234
Arada AD_ER_HW_A 10.0.5.235

Arada AD_ER_HW_B 10.0.5.236
The IP addresses planning for interfaces are shown below:
Table 11- 4 Interconnection IP assignment design
Site Device IP Peer Site Peer Device Peer IP

Nifas Silk NS_ER_HW_A 10.1.33.101 Nifas Silk NS_ER_DATA_A 10.1.33.102
Nifas Silk NS_ER_HW_A 10.1.33.105 Nifas Silk NS_ER_HW_B 10.1.33.106
Nifas Silk NS_ER_HW_B 10.1.33.109 Nifas Silk NS_ER_DATA_B 10.1.33.110
MicroWave MW_ER_HW_A 10.1.29.101 MicroWave MW_CR_A 10.1.29.102

MicroWave MW_ER_HW_A 10.1.29.105 MicroWave MW_ER_HW_B 10.1.29.106
MicroWave MW_ER_HW_B 10.1.29.109 MicroWave MW_CR_B 10.1.29.110
Kirkos KK_ER_HW_A 10.1.32.101 Arada AD_CR_A 10.1.32.102

Kirkos KK_ER_HW_A 10.1.32.105 Kirkos KK_ER_HW_B 10.1.32.106
Kirkos KK_ER_HW_B 10.1.32.109 Arada AD_CR_B 10.1.32.110
Bole BL_ER_HW_A 10.1.30.101 Bole BL_CR_A 10.1.30.102

Bole BL_ER_HW_A 10.1.30.105 Bole BL_ER_HW_B 10.1.30.106
Bole BL_ER_HW_B 10.1.30.109 Bole BL_CR_B 10.1.30.110
Arada AD_ER_HW_A 10.1.31.101 Arada AD_CR_A 10.1.31.102

Arada AD_ER_HW_A 10.1.31.105 Arada AD_ER_HW_B 10.1.31.106
Arada AD_ER_HW_B 10.1.31.109 Arada AD_CR_B 10.1.31.110
-290-
11.4 Site Network Design

11.4.1 Overview
This section describes the Interconnection of physical network site design between existing IP Core
network and expansion network. It involves detailed sites design in various sites of Kirkos, Bole,
Nifas Silk, Microwave and Arada.
11.4.2 Nifas Silk Site

 Device Connection Scope
As shown followed, in Nifas Silk Site, 2 Firewalls (E8000E), 4 LAN Switches (S9300), 2
NE40E-X8s and 2 CX600-x16s will be deployed.
Figure 11- 7 physical connection design in Nifas Silk

NS_ER_ NS_ER_
Data_A Data_B
Nifas Silk
M6000
Eth-Trunk5 Eth-Trunk5
NS_ER_ Eth-Trunk10
NS_ER_ NE40E-X8
HW_A HW_B
3
CX600-X16
Eth-Trunk30
S9300
Eth-Trunk20
4 4 4 43 2Eth-Trunk30
2 E8000E
Eth-Trunk15
3
Eth-Trunk15
Eth-Trunk25 10G LAG
Eth-Trunk25
Eth-Trunk20
Eth-Trunk10
Eth-Trunk10
BSC/RNC NS_SW NS_SW
NS_FW NS_FW NS_SW NS_SW _CS_A _CS_B
_PS_A _PS_B _PS_A _PS_B Eth-Trunk1
PS CS
NS_RSG_A NS_RSG_B
To To
KK_RSG_B BL_RSG_A
Table 11- 5 Port Connections in Nifas Silk Site
Peer
Site Device Port Logic Port Peer Device Peer Port Logic Port
Site
NS_ER_HW_A Gi2/0/2 Eth-Trunk5 NS-ER-DATA-A Xgei-0/0/1/1 Smartgroup5
NS_ER_HW_A Gi2/0/0 NS_ER_HW_B Gi2/0/0
NS_ER_HW_A Gi6/0/0 Eth-Trunk10 NS_ER_HW_B Gi6/0/0 Eth-Trunk10
NS_ER_HW_A Gi7/0/0 NS_ER_HW_B Gi7/0/0
NS_ER_HW_A Gi2/0/1 NS_RSG_A Gi6/1/4
NS NS
NS_ER_HW_A Gi6/0/1 Eth-Trunk15 NS_RSG_A Gi8/1/4 Eth-Trunk15
NS_ER_HW_A Gi7/0/1 NS_RSG_A Gi14/1/4
NS_ER_HW_A Gi2/1/1 NS_FW_PS_A Gi1/0/0
NS_ER_HW_A Gi2/1/2 Eth-Trunk20 NS_FW_PS_A Gi1/0/1 Eth-Trunk20
-291-

NS_ER_HW_A Gi2/1/3 NS_SW_PS_A Gi3/0/8
NS_ER_HW_A Gi6/1/0 NS_SW_CS_A Gi1/0/0
NS_ER_HW_A Gi7/1/0 NS_SW_CS_A Gi1/0/1
NS_ER_HW_B Gi1/0/0 Eth-Trunk5 NS-ER-DATA-B Xgei-0/0/1/1 Smartgroup5
NS_ER_HW_B Gi2/0/1 NS_RSG_B Gi6/1/4
NS_ER_HW_B Gi6/0/1 Eth-Trunk15 NS_RSG_B Gi8/1/4 Eth-Trunk15
NS_ER_HW_B Gi7/0/1 NS_RSG_B Gi14/1/4
NS_ER_HW_B Gi2/1/1 NS_FW_PS_B Gi1/0/0
NS_ER_HW_B Gi2/1/3 NS_SW_PS_B Gi3/0/8
NS_ER_HW_B Gi6/1/0 NS_SW_CS_A Gi1/0/0
NS_ER_HW_B Gi7/1/0 NS_SW_CS_A Gi1/0/1
 NE40Es Connectivity Planning
The connectivity planning of NE40Es is shown below. The Ethernet Trunk members should be on
different slot to protect against board failures, as shown followed.
Figure 11- 8 NE40E layout in Nifas Silk site

10GE (SFP+) GE(SFP) Fiber
NS_ER_DATA_A NS_ER_DATA_B
NS_ER_NEW_A(NE40E-X8) NS_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 LAG-15 8 9
2 2 2 2 2 2
10 11 10 11
12 13
NS_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
20 21 SRU SFU SRU 20 21 SRU SFU SRU
22 23 NS_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 LAG-30 26 27 1 1 1
28 29 28 29
30 31 2 2 2 NS_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
36 37 LAG-30 36 37
4 4 4 NS_SW_CS_A 4 4 4
38 39 38 39
LAG-20 LAG-20
NS_FW_PS_A NS_FW_PS_B
LAG-25
LAG-25
NS_SW_PS_A
NS_SW_PS_B
-292-
11.4.3 Kirkos Site

As shown followed, in Kirkos Site, 2 Firewalls (E8000E), 4 LAN Switches (S9300), 2 NE40E-X8s
and 2 CX600-x16s will be deployed.
Figure 11- 9 physical connection design in Kirkos

AD_CR_A AD_CR_B
Arada
8 8
M6000
KK_ER_ Eth-Trunk10 KK_ER_ NE40E-X8

HW_A HW_B
3
CX600-X16
S9300
Eth-Trunk20 Eth-Trunk25 Eth-Trunk30
Kirkos
4 4 4 43 2 2 E8000E
Eth-Trunk15
3
Eth-Trunk15
Eth-Trunk30
Eth-Trunk20
3 3*10G LAG
Eth-Trunk25
Eth-Trunk10
Eth-Trunk10 Eth-Trunk10 8 8*GE LAG
BSC/RNC KK_SW KK_SW
KK_FW KK_FW KK_SW KK_SW
_PS_A _CS_A _CS_B
_PS_B _PS_A _PS_B Eth-Trunk1
PS CS
KK_RSG_A KK_RSG_B
To To
NS_ASG_B NS_RSG_A
Table 11- 6 Port Connections in Kirkos Site
Peer
Site
KK_ER_HW_A Gi1/0/0 AD_CR_A
Eth-Trunk5 AD Smartgroup5
KK_ER_HW_A Gi2/0/0 KK_ER_HW_B Gi2/0/0
KK
KK_ER_HW_A Gi6/0/0 Eth-Trunk10 KK_ER_HW_B Gi6/0/0 Eth-Trunk10
KK_ER_HW_A Gi7/0/0 KK_ER_HW_B Gi7/0/0
KK_ER_HW_A Gi2/0/1 KK_RSG_A Gi6/1/4
KK_ER_HW_A Gi6/0/1 Eth-Trunk15 KK_RSG_A Gi8/1/4 Eth-Trunk15
KK
KK_ER_HW_A Gi7/0/1 KK_RSG_A Gi14/1/4
KK_ER_HW_A Gi2/1/1 KK_FW_PS_A Gi1/0/0
-293-
KK_ER_HW_A Gi2/1/2 KK_SW_PS_A Gi3/0/8

KK_ER_HW_A Gi6/1/0 KK_SW_CS_A Gi1/0/0
KK_ER_HW_A Gi7/1/0 KK_SW_CS_A Gi1/0/1
KK_ER_HW_B Gi1/0/0 AD_CR_B
Eth-Trunk5 AD Smartgroup5
KK_ER_HW_B Gi2/0/1 KK_RSG_B Gi6/1/4
KK_ER_HW_B Gi6/0/1 Eth-Trunk15 KK_RSG_B Gi8/1/4 Eth-Trunk15
KK_ER_HW_B Gi7/0/1 KK_RSG_B Gi14/1/4
KK_ER_HW_B Gi2/1/1 KK_FW_PS_B Gi1/0/0
KK_ER_HW_B Gi6/1/3 KK KK_FW_PS_B Gi2/0/1
KK_ER_HW_B Gi2/1/2 KK_SW_PS_B Gi3/0/8
KK_ER_HW_B Gi6/1/0 KK_SW_CS_B Gi1/0/0
KK_ER_HW_B Gi7/1/0 KK_SW_CS_B Gi1/0/1
 NE40E in Kirkos Connectivity Planning
The connectivity planning of NE40E is shown below. The Ethernet Trunk members should be on
different slot to protect against board failures, as show followed.
-294-
Figure 11- 10 NE40E layout in Kirkos site

AD_CR_A AD_CR_B
KK_ER_NEW_A(NE40E-X8) KK_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 2 2 2 LAG-15 8 9 2 2 2
10 11 10 11
12 13
KK_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
22 23 KK_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 LAG-30
26 27 1 1 1
28 29 28 29
30 31 2 2 2 KK_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
LAG-30
36 37 36 37
4 4 4 KK_SW_CS_A 4 4 4
38 39 38 39
LAG-20 LAG-20
KK_FW_PS_A KK_FW_PS_B
LAG-25
LAG-25
KK_SW_PS_A
KK_SW_PS_B
11.4.4 Bole Site

As shown followed, in Bole Site, 2 LAN Switches (S9300), 2 NE40E-X8s and 2 CX600-x16s will
be deployed.
Figure 11- 11 physical connection design in Bole
BL_CR_A BL_CR_B
Bole
Eth-Trunk5 Eth-Trunk5 M6000
BL_ER_ Eth-Trunk10 BL_ER_ NE40E-X8

HW_A HW_B
3
CX600-X16
S9300
2 2 E8000E
3 3 Eth-Trunk30 Eth-Trunk30
Eth-Trunk15 Eth-Trunk15 3 3*10G LAG
Eth-Trunk10
BSC/RNC BL_SW BL_SW
_CS_A _CS_B
Eth-Trunk1
CS
BL_RSG_A BL_RSG_B
To To
NS_RSG_B Filowoha_RSG_A
Table 11- 7 Port Connections in Bole Site
Peer
Site
-295-
BL_ER_HW_A Gi2/0/2 Eth-Trunk5 BL_CR_A Xgei-0/2/1/1 Smartgroup5

BL_ER_HW_A Gi2/0/0 BL_ER_HW_B Gi2/0/0
BL_ER_HW_A Gi6/0/0 Eth-Trunk10 BL_ER_HW_B Gi6/0/0 Eth-Trunk10
BL_ER_HW_A Gi7/0/0 BL_ER_HW_B Gi7/0/0
BL_ER_HW_A Gi2/0/1 BL_RSG_A Gi6/1/4
BL_ER_HW_A Gi6/0/1 Eth-Trunk15 BL_RSG_A Gi8/1/4 Eth-Trunk15
BL_ER_HW_A Gi7/0/1 BL_RSG_A Gi14/1/4
BL BL_ER_HW_A Gi6/1/0 BL BL_SW_CS_A Gi1/0/0
BL_ER_HW_A Gi7/1/0 BL_SW_CS_A Gi1/0/1
BL_ER_HW_B Gi2/0/2 Eth-Trunk5 BL_CR_B Xgei-0/2/1/1 Eth-Trunk5
BL_ER_HW_B Gi2/0/1 BL_RSG_B Gi6/1/4
BL_ER_HW_B Gi6/0/1 Eth-Trunk15 BL_RSG_B Gi8/1/4 Eth-Trunk15
BL_ER_HW_B Gi7/0/1 BL_RSG_B Gi14/1/4
BL_ER_HW_B Gi6/1/0 BL_SW_CS_B Gi1/0/0
BL_ER_HW_B Gi7/1/0 BL_SW_CS_B Gi1/0/1
 NE40E in Bole Site Connectivity Planning
Figure 11- 12 NE40E layout in Bole site

BL_CR_A BL_CR_B
BL_ER_NEW_A(NE40E-X8) BL_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 2 2 2 LAG-15 8 9 2 2 2
10 11 10 11
12 13
BL_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
22 23 BL_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 26 27 1 1 1
LAG-30
28 29 28 29
30 31 2 2 2 BL_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
36 37 LAG-30 36 37
4 4 4 BL_SW_CS_A 4 4 4
38 39 38 39
11.4.5 Microwave Site

As shown followed, in Microwave Site, 2 Firewalls (E8000E), 4 LAN Switches (S9300), 2

NE40E-X8s and 2 CX600-x16s will be deployed.
-296-
Figure 11- 13 physical connection design in Microwave
MW_CR_A MW_CR_B
MicroWave
8 8 M6000
MW_ER_ NE40E-X8
Eth-Trunk10 MW_ER_
HW_A 3 HW_B
CX600-X16
S9300
4 4 4 43 2 2 E8000E
3 Eth-Trunk30 Eth-Trunk30
3 3*10G LAG
Eth-Trunk25
Eth-Trunk20 Eth-Trunk15 Eth-Trunk15 Eth-Trunk10 8 8*GE LAG RJ45
BSC/RNC MW_SW MW_SW
MW_FW MW_FW MW_SW MW_SW _CS_A _CS_B
_PS_A _PS_B _PS_A _PS_B Eth-Trunk1
PS CS
MW_RSG_A MW_RSG_B
To Filowoha_ASG_B To OA_ASG_A
Table 11- 8 Port Connections in Microwave Site
Peer
Site
MW_ER_HW_A Gi1/0/0 MW_CR_A gei-0/3/0/2
Eth-Trunk5 SmartGroup5
MW_ER_HW_A Gi2/0/0 MW_ER_HW_B Gi2/0/0
MW_ER_HW_A Gi6/0/0 Eth-Trunk10 MW_ER_HW_B Gi6/0/0 Eth-Trunk10
MW_ER_HW_A Gi7/0/0 MW_ER_HW_B Gi7/0/0
MW_ER_HW_A Gi2/0/1 MW_RSG_A Gi6/1/4
MW MW_ER_HW_A Gi6/0/1 Eth-Trunk15 MW MW_RSG_A Gi8/1/4 Eth-Trunk15
MW_ER_HW_A Gi7/0/1 MW_RSG_A Gi14/1/4
MW_ER_HW_A Gi2/1/1 MW_FW_PS_A Gi1/0/0
MW_ER_HW_A Gi2/1/3 MW_SW_PS_A Gi3/0/8
MW_ER_HW_A Gi6/1/0 MW_SW_CS_A Gi1/0/0
MW_ER_HW_A Gi7/1/0 MW_SW_CS_A Gi1/0/1
MW_ER_HW_B Gi1/0/0 Eth-Trunk5 MW_CR_B gei-0/3/0/2 Smartgroup5
-297-
MW_ER_HW_B Gi1/0/1 MW_CR_B gei-0/3/0/3

MW_ER_HW_B Gi2/0/1 MW_RSG_B Gi6/1/4
MW_ER_HW_B Gi6/0/1 Eth-Trunk15 MW_RSG_B Gi8/1/4 Eth-Trunk15
MW_ER_HW_B Gi7/0/1 MW_RSG_B Gi14/1/4
MW_ER_HW_B Gi2/1/1 MW_FW_PS_B Gi1/0/0
MW_ER_HW_B Gi2/1/3 MW_SW_PS_B Gi3/0/8
MW_ER_HW_B Gi6/1/0 MW_SW_CS_B Gi1/0/0
MW_ER_HW_B Gi7/1/0 MW_SW_CS_B Gi1/0/1
 NE40E in Microwave Connectivity Planning
Figure 11- 2 NE40E layout in Microwave site
MW_CR_A 10GE (SFP+) GE(SFP) Fiber

MW_CR_B
gei-0/3/0/8,6,4,2,3,5,7.9 Cat7 Cable gei-0/3/0/8,6,4,2,3,5,7.9
MW_ER_NEW_A(NE40E-X8) MW_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 2 2 2 LAG-15 8 9 2 2 2
10 11 10 11
12 13
MW_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
22 23 MW_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 LAG-30 26 27 1 1 1
28 29 28 29
30 31 2 2 2 MW_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
LAG-30
36 37 36 37
4 4 4 MW_SW_CS_A 4 4 4
38 39 38 39
LAG-20 LAG-20
MW_FW_PS_A MW_FW_PS_B
LAG-25
LAG-25
MW_SW_PS_A
MW_SW_PS_B
-298-
11.4.6 Arada Site

As shown followed, in Arada Site, 2 LAN Switches (S9300), 2 NE40E-X8s and 2 CX600-x16s will
be deployed.
Figure 11- 3 physical connection design in Arada

AD_CR_A AD_CR_B
Arada M6000
AD_ER_ Eth-Trunk10 AD_ER_ NE40E-X8
HW_A HW_B
3
CX600-X16
S9300
Eth-Trunk15
2 2 E8000E
3 3 Eth-Trunk30 Eth-Trunk30
3 3*10G LAG
Eth-Trunk10
Eth-Trunk15 8 8*GE LAG
BSC/RNC AD_SW AD_SW
_CS_A _CS_B
Eth-Trunk1 CS
AD_RSG_A AD_RSG_B
To To
KTM_ASG_B SK_ASG_B
Figure 11- 4 NE40E layout in Arada site
Peer
Site
AD_ER_HW_A Gi2/0/2 Eth-Trunk5 AD_CR_A xgei-0/2/1/1 Smartgroup5
AD_ER_HW_A Gi2/0/0 AD_ER_HW_B Gi2/0/0
AD_ER_HW_A Gi6/0/0 Eth-Trunk10 AD_ER_HW_B Gi6/0/0 Eth-Trunk10
AD_ER_HW_A Gi7/0/0 AD_ER_HW_B Gi7/0/0
AD_ER_HW_A Gi2/0/1 AD_RSG_A Gi6/1/4
AD_ER_HW_A Gi6/0/1 Eth-Trunk15 AD_RSG_A Gi8/1/4 Eth-Trunk15
AD_ER_HW_A Gi7/0/1 AD_RSG_A Gi14/1/4
Arada AD_ER_HW_A Gi6/1/0 Arada AD_SW_CS_A Gi1/0/0
AD_ER_HW_A Gi7/1/0 AD_SW_CS_A Gi1/0/1
AD_ER_HW_B Gi2/0/2 Eth-Trunk5 AD_CR_B xgei-0/2/1/1 Smartgroup5
AD_ER_HW_B Gi2/0/1 AD_RSG_B Gi6/1/4
AD_ER_HW_B Gi6/0/1 Eth-Trunk15 AD_RSG_B Gi8/1/4 Eth-Trunk15
AD_ER_HW_B Gi7/0/1 AD_RSG_B Gi14/1/4
AD_ER_HW_B Gi6/1/0 AD_SW_CS_B Gi1/0/0
AD_ER_HW_B Gi7/1/0 AD_SW_CS_B Gi1/0/1
 NE40E in Arada Site Connectivity Planning
-299-
Figure 11- 5 NE40E layout in Arada site

AD_CR_A AD_CR_B
AD_ER_NEW_A(NE40E-X8) AD_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 2 2 2 LAG-15 8 9 2 2 2
10 11 10 11
12 13
AD_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
22 23 AD_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 26 27 1 1 1
LAG-30
28 29 28 29
30 31 2 2 2 AD_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
36 37 LAG-30 36 37
4 4 4 AD_SW_CS_A 4 4 4
38 39 38 39
As described above, Link Aggregation (LAG) Technology will be used to enlarge bandwidth in 5
sites of expansion network. For HUAWEI’s term, we name LAG as Eth-Trunk. We will give a
configuration template for Eth-Trunk below.
11.4.7 Configuration Template for Eth-Trunk

#
<HUAWEI> system-view
[HUAWEI] interface eth-Trunk 1 //Create Eth-Trunk interface
[HUAWEI-Eth-Trunk1]mode lacp-static //Configure LACP mode
NE40E-X8 [HUAWEI-Eth-Trunk1]lacp timeout fast // Configure LACP short period
[HUAWEI-Eth-Trunk1]least active-linknumber 2 //Configure minimum ports
[HUAWEI] interface gigabitethernet 1/0/1
[HUAWEI-GigabitEthernet1/0/1] eth-trunk 1 //add port to Eth_Trunk 1
11.5 IGP Design

11.5.1 Overview
This section describes the IGP design and configuration used in Interconnection Network. It
involves various aspects of IGP design including link metric planning, security, and high
availability design.
-300-
11.5.2 IGP Deployment Scope

IGP Design in interconnection network applies ISIS protocol, overall network is deployed in ISIS
level-2 region, the detailed planning is as followed:
1. Enable ISIS on all interconnected interfaces between CR/ER(M6000) and Huawei ER(NE40E) ,
all interconnected interfaces between Huawei ER routers and loopback interface;
2. ISIS only carries routes of interconnected port of CR and ER, Loopback route and default routes.
3. All downlink interfaces of New ER (NE40E) router (connected to CX600 or S9300) does not run
ISIS.
For interfaces of CR and ER routers, the protocol deployment is as follows:
Figure 11- 6 ISIS deployment design
ISIS T1200/M6000
NE40E-X8
CR
RR
500
500
OLD ER 500
500
500
500 Arada
500 500
Bole 11500
New ER 500
500 Kirkos
11500
Nifas Silk MicroWave
12000 11500
11500
11.5.3 ISIS Design Rule

The basic ISIS design rules are:
 The ISIS in IP Core is a flat topology within ISIS Level-2.
 The ISIS uses manual link cost for flexibility of tuning the metric
 The ISIS should deploy high availability features to minimize traffic loss during router restart or
protocol convergence. This includes LDP-IGP synchronization.
 The ISIS should secure against unintended connection with MD5 authentication and silence
interface.
Table 11- 9 ISIS design result
ISIS Relation Data Configuration
-301-
Level level-2
Area ID. 88.0251
Loopback interface
System ID
address expansion
Metric style Wide-metric
ISIS route priority Default value applies
ISIS protocol authentication MD5 authentication
11.5.4 ISIS Metric Planning

ISIS metric plan for interconnection network shown as followed.
Table 11- 10 ISIS metric planning in Microwave
Links ISIS Metric
New ER-CR 500

New ER-New ER 11500
Table 11- 11 ISIS metric planning in Kirkos
Links ISIS Metric
New ER-CR 500

New ER-New ER 11500
Table 11- 12 ISIS metric planning in Bole
Links ISIS Metric
New ER-CR 500

New ER-New ER 11500
Table 11- 13 ISIS metric planning in Arada
Links ISIS Metric
New ER-CR 500

New ER-New ER 11500
Table 11- 14 ISIS metric planning in Nifas Silk
Links ISIS Metric
New ER-Old ER 500

New ER-New ER 12000
-302-
11.5.5 LDP-IGP Synchronization

LDP-IGP synchronization is implemented to suppress IGP convergence until LDP is converged.
When a fault occurs over the active link, LDP-IGP synchronization keeps forwarding traffic over
the backup link LSP until the new LSP is set up on the active link. When the LDP converged, the
backup link LSP is deleted. This is required as IPv4 traffic or VPN traffic are commonly
recursively lookup and iterated into MPLS LSP based on BGP next hop information. If the IGP
converged too early and send the traffic to active link over naked IP, intermediate router may not
have the route entry/label to perform forwarding causing the traffic to drop at the intermediate
router. The configuration is shown below:
Configuration template for ISIS LDP-IGP synchronization
[NE40E]interface GigabitEthernet 0/0/0

NE40E-X8
[NE40E-GigabitEthernet0/0/0]isis ldp-sync //enable ldp igp synchronization
11.5.6 ISIS Authentication and Silent Interface

The deployment of protocol security measures protects the router from unauthorized ISIS peering
connection. This protects against unauthorized client injecting false routes into the network.
Huawei will deploy ISIS interface based MD5 authentication.
The configuration template for OSPF interface based authentication
[NE40E]interface GigabitEthernet 1/0/0

NE40E-X8 [NE40E-GigabitEthernet1/0/0]ISIS authentication-mode md5 1 cipher
XX //enable md5 authentication on isis interface
ISIS silent interface feature by default disables the advertising or receiving of ISIS protocol packets
from any interface by default. It is required to manually enable to allow the interface to start
processing ISIS protocol packets. This avoids running ISIS protocol on interface accidentally. The
configuration is shown below:
Configuration template for ISIS silent interface
[NE40E]isis 1
[NE40E-isis-1]silent-interface all //enable silent ISIS interface
NE40E-X8
[NE40E-isis-1]undo silent-interface GigabitEthernet1/0/0 //Cancel
silent ISIS interface
-303-
11.5.7 Configuration Template for ISIS

#
[HUAWEI] isis 1
[HUAWEI-isis-1] network-entity 88.0251.0100.0000.0002.00
NE40E-X8 [HUAWEI-isis-1] is-level level-2 //Configure ISIS level-2
[HUAWEI-isis-1] cost-style wide //Configure metric-type
[HUAWEI-GigabitEthernet1/0/0] isis authentication-mode simple huawei
#
11.6 BGP Design

11.6.1 Overview
This section describes the BGP design and configuration being used in Interconnection Network. It
involves various aspects of BGP design including basic parameter planning, security design, traffic
flow design, high availability and route reflector design (RR).
11.6.2 BGP Deployment Scope

Shown as followed, MP-IBGP will be deployed between all PEs and RRs, and each PE establishes
MP-IBGP with two RRs. Two RRs are redundancy as mutually backups, are responsible for route
convergence and forwarding only, not responsible for service traffic forwarding; each RR reflects
VPNv4 route, not IPv4 route. Two RRs are uplinked to two local CRs via double-link respectively.
RR equipment establishes IBGP neighbors.
Run VRF EBGP between PE (NE40E-X8) and RSG (CX600-X16), each PE establish EBGP peer
with its adjacent RSG, and exchange VRF routes.
-304-
Figure 11- 7 BGP deployment design
Mekele-RR MicroWave-RR
AS65108 T1200
NE40E-X8
CX600-X16
Kir MP-IBGP Peer

kos
a
Arad EBGP Peer
Bole MicroWave
Nifas Silk
AS65109
11.6.3 BGP Design Rule

The basic BGP design rules are:
 Existing IP core network is running with AS 65108.
 BGP route reflector (RR) for VPNv4 routes distribution among PE routers. There should be
redundant RR to protect against failure.
 Deploy BGP peer group features not only to simplify configuration, but also reducing the CPU
processing that the router needs to perform.
 Set the BGP router ID with loopback 0.
 Deploy BGP with protocol security measures (MD5 authentication) to protect the router from
unauthorized connection injecting false routes ET.
 Deploy BGP attribute and community features for PE selection for traffic flow in a dual
redundant PE scenario.
BGP Peer Group
BGP peer group feature provides a mechanism for grouping peers with same update policy. Setting
update policy on the defined peer group will apply the same policy towards all its members within
the group. This not only reduce the number of repetitive configurations needed, but also saving the
CPU cycles of the router since the router can just replicate the policy for the group members. The
configuration is shown below:
Configuration template for BGP peer group
-305-
[NE40E]bgp <AS No>

[NE40E-bgp]group BGP-CLIENT internal //Create peer-group
NE40E-X8
[NE40E-bgp]peer x.x.x.x group BGP-CLIENT //add member to peer-group,
and x.x.x.x is IP addres of its neighbor
BGP Router ID
Setting BGP router ID manually with Loopback0 IP to avoid BGP randomly select other loopback
or interface IP as its router ID. The configuration is shown below:
Configuration template for BGP router ID
[NE40E]bgp <AS No> //enter BGP view

NE40E-X8 [NE40E-bgp]router-id X.X.X.X //configure BGP router-ID,
and generally X.X.X.X is IP address of Loopback
BGP MD5 Authentication
For similar reason deploying MD5 authentication for ISIS, the deployment of MD5 authentication
protects the router from unauthorized BGP peering connection. Differs to ISIS, it does not
authenticate the BGP packets, instead it uses MD5 authentication password for TCP connection.
The configuration is shown below:
Configuration template for BGP MD5 authentication
[NE40E]bgp <AS No>

NE40E-X8 [NE40E-bgp]peer X.X.X.X password cipher XXX //enable BGP authentication,
and X.X.X.X is IP address of its neighbor, XXX is the password
11.6.4 BGP Route Advertisement & Control Design

BGP Route Control for Redundant PEs (Dual Plane)
-306-
Figure 11- 8 BGP Route Control for Redundant PEs
T1200
NE40E-X8
IBGP Peer RR
RR
Inter-site Traffic
A
PE
A Site 2
IP Core
PE
Site 1 B
PE
B
PE
ET IP Core is a double plane flat topology network. When PE of Plane A received routes from
remote PEs of both plane, it can select routes from the same plane as itself by IGP path.
BGP for IP RAN Mobile Services Interconnection
 BGP/MPLS L3vpn Option A Solution
Figure 11- 90 BGP/MPLS L3vpn Option A Solution
MPLS L3vpn Option A MPLS L3vpn

T1200
NE40E-X8
RR
CX600-X16
RR
IP RAN IP Core
Capital RSG ER AS 65108
AS65109
RSG ER
Interconnection network transports the services coming from IP RAN covering the whole country
in Ethiopia. Thus the scale of network is tremendously larger and it is logical to divide it into a
smaller entity of manageability reasons. Also, hierarchical design separates the IGP domain of
IPRAN from the IP core and avoids the IPRAN instability affecting operation of IP core.
To this end, the design adopts inter-AS option A for IP core and IP RAN internal peering. Capital
region will belong to a single routing domain (IGP/BGP. For Inter-AS Option A peering, IP Core
-307-
and IP RAN connects to each other over the sub-interfaces within the VRF. VPN Routes are
exchange via normal EBGP. In this sense, the boundary PE treats the PE of the remote end as its
CE router. The configuration of Inter- AS Option A VPN is shown below:
Configuration template for MPLS Inter- AS Option A VPN
[NE40E] bgp 65109

[NE40E-bgp] ipv4-family vpn-instance xx //enter VRF BGP view,
NE40E-X8 XX is the name of vpn-instance
[NE40E-bgp-xx] peer x.x.x.x as-number xx //create BGP peer,
x.x.x.x is ip address of its neighbor, xx is AS-Number of its neighbor.
For inter- AS Option A MPLS L3VPN inter-connection, the peering is needed for each type of
services. The services that require peering are GSM VRF, OAM VRF and PS_GB VRF, etc.
BGP for Fixed-Line Services Interconnection
 Inter-AS BGP/MPLS L3vpn Option C Solution
Figure 11- 210 Inter-AS BGP/MPLS L3vpn Option C Solution
MPLS L3vpn Option C MPLS L3vpn M6000
NE40E-X8
CX600-X16
Other Network
ET Network
ASBR-1 ASBR-2 AS 65108
AS65109
PE-1 PE-2
Inter-AS MPLS VPN Option C. PEs in different ASs establishes multi-hop EBGP connections
with each other and exchanges VPN-IPv4 routes.
ASBRs advertise labeled IPv4 routes to PEs in their respective ASs through MP-IBGP, and
advertise labeled IPv4 routes received on PEs in the local AS to the ASBR peers in other ASs.
ASBRs in the transit AS also advertise labeled IPv4 routes. Therefore, a BGP LSP can be
established between the ingress PE and egress PE.
The ASBRs do not store VPN-IPv4 routes or advertise VPN-IPv4 routes to each other
Configuration template for MPLS Inter- AS Option C VPN
-308-
[PE1] bgp 65109

[PE1-bgp] peer <ASBR-1_IP_Address> label-route-capability //Enable label BGP
[PE1-bgp] peer <PE2-IP-Address> as-number 65108 //Establish EBGP session with PE2
[PE1-bgp] peer <PE2-IP-Address> connect-interface LoopBack 1 //Assign Source IP address
[PE1-bgp] peer <PE2-IP-Address> ebgp-max-hop 10 // enable EBGP multi-hop
[PE1-bgp] ipv4-family vpnv4
[PE1-bgp-af-vpnv4] peer <PE2-IP-Address> enable //Enable VPNv4 capability
[ASBR1] interface Gi2/0/0

[ASBR1-GigabitEthernet2/0/0]MPLS //Enable MPLS between ASBRs
[ASBR1] route-policy policy1 permit node 1 //Create route-policy
[ASBR1-route-policy] apply mpls-label //Enable label advertise
[ASBR1-route-policy] quit
[ASBR1-route-policy] if-match mpls-label //Match mpls-label
[ASBR1-route-policy] apply mpls-label //Swap mpls-label
[ASBR1] bgp 65109
[ASBR1-bgp] peer <PE-1_IP_Address> route-policy policy2 export //apply route-policy for label
swap
[ASBR1-bgp] peer <PE-1_IP_Address> label-route-capability //enable label capability
[ASBR1-bgp] peer <ASBR-2_IP_Address> as-number 65108
[ASBR1-bgp] peer <ASBR-2_IP_Address> route-policy policy1 export //apply route-policy for label
advertisement
[ASBR1-bgp] peer <ASBR-2_IP_Address> label-route-capability //enable label capability
[ASBR1-bgp] network <PE-1_loopback-IP-Address> 32 //Advertise bgp route
-309-
[PE2] bgp 65108

[PE2-bgp] peer <ASBR-2_IP_Address> label-route-capability //Enable label BGP
[PE2-bgp] peer <PE1-IP-Address> as-number 65109 //Establish EBGP session with PE2
[PE2-bgp] peer <PE1-IP-Address> connect-interface LoopBack 1 //Assign Source IP address
[PE2-bgp] peer <PE1-IP-Address> ebgp-max-hop 10 // enable EBGP multi-hop
[PE2-bgp] ipv4-family vpnv4
[PE2-bgp-af-vpnv4] peer <PE2-IP-Address> enable //Enable VPNv4 capability
[ASBR2] interface Gi2/0/0

[ASBR2-GigabitEthernet2/0/0]MPLS //Enable MPLS between ASBRs
[ASBR2-route-policy] apply mpls-label //Enable label advertise
[ASBR2-route-policy] if-match mpls-label //Match mpls-label
[ASBR2-route-policy] apply mpls-label //Swap mpls-label
[ASBR2] bgp 65108
[ASBR2-bgp] peer <PE-2_IP_Address> route-policy policy2 export //apply route-policy for label
swap
[ASBR2-bgp] peer <PE-2_IP_Address> label-route-capability //enable label capability
[ASBR2-bgp] peer <ASBR-1_IP_Address> as-number 65108
[ASBR2-bgp] peer <ASBR-1_IP_Address> route-policy policy1 export //apply route-policy for label
advertisement
[ASBR2-bgp] peer <ASBR-1_IP_Address> label-route-capability //enable label capability
[ASBR2-bgp] network <PE-1_loopback-IP-Address> 32 //Advertise bgp route
11.6.5 Configure Example for BGP

 Configuration for Nifas Silk PE-A
-310-
Nifas Silk PE-A

interface loopback0
ip address 10.0.5.239 255.255.255.255
isis 1 enable
#
bgp 65108
peer 10.0.2.113 as-number 65108 //configure peer with Mekele RR
peer 10.0.2.113 connect-interface LoopBack0 //Source IP address
peer 10.0.2.114 as-number 65108 //configure peer with Microwave RR
peer 10.0.2.114 connect-interface LoopBack0 //Source IP address
#
NE40E-X8
ipv4-family unicast
undo synchronization //disable synchronization
undo peer 10.0.2.113 enable //disable IPv4 unicast capability
undo peer 10.0.2.114 enable //disable IPv4 unicast capability
ipv4-family vpnv4
policy vpn-target //filter VPN route without local RT
peer 10.0.2.113 enable //enable vpnv4 unicast capability
peer 10.0.2.114 enable //enable vpnv4 unicast capability

ipv4-family vpn-instance GSM //enter VRF BGP vies
import-route directed //redistribute connected route
11.7 MPLS Design

11.7.1 Overview
Shown as followed, MPLS LDP had been deployed in existing IP Core Network. For
interconnection between expansion network and existing network, ONLY MPLS LDP will be
deployed between NEW ER, OLD ER and CR.
-311-
Figure 11- 22 MPLS design overview
IGW
1. Mekele 2. Bahirdar 5. Dire Dawa T8000
3.Addis(Bole)
NE40E-X8
CR Layer Bole Arada

RR
MPLS LDP Arada
ER Layer Kirkos
Bole Nifas Silk MicroWave
11.7.2 MPLS and MPLS VPN Design Rule

The basic MPLS design rules are:
 Deploy MPLS with LSR ID being the IP of interface loopback0
 Deploy MPLS LSP/label allocation for host loopback IP only
 Deploy MPLS LDP MD5 packet authentication for security
 Deploy MPLS VPN instance prefix limit to avoid user injecting excessive routes into network
 Deploy MPLS LDP high availability feature i.e. NSR features to provide nonstop LSP/label
forwarding during MPU switchover or reset.
11.7.3 MPLS LSR ID

MPLS LSR-ID is a unique identifier of each MPLS routers. It is used to establish the relationship
with other MPLS routers. LSR-ID is as IP address of loopback0 for each router. The configuration
is shown below:
Configuration template for MPLS LSR ID & enabling MPLS on router
[NE40E]mpls lsr-id <x.x.x.x> //Configure lsr-id

[NE40E]mpls //Enable mpls on router
NE40E-X8 [NE40E-mpls]quit
[NE40E]mpls ldp //Enable mpls ldp
[NE40E-mpls-ldp]
-312-
11.7.4 MPLS LSP Trigger / Label allocation

Interconnection network deploys BGP/MPLS jointly to provide LSP tunnel for carrying services
either IP or VPN traffic by means of recursively lookup the next hop IP which is the loopback IP
(or host) of the egress router. There is no longer need to establish LSP for individual router entry.
In order to avoid the existence of unnecessary LSP, LSP-trigger method is designed to be “host”
meaning LSP is only establish for loopback addresses. The configuration is shown below:
Configuration template for MPLS LSP trigger by host
[NE40E]mpls
NE40E-X8
[NE40E-mpls]lsp-trigger host //Enable only distribute 32 bits FEC
11.7.5 MPLS LDP GR

LDP Graceful Restart (GR) allows the MPLS enabled router to provide nonstop traffic forwarding
during MPU switchover or reset. This minimizes the service interruption and ensure high quality
network. Deploy LDP GR in all the routers except RR in IP core network. The configuration for
MPLS LDP GR is shown below:
Configuration template for MPLS LDP GR
[NE40E]mpls ldp
NE40E-X8
[NE40E-mpls-ldp]graceful-restart
Configuration template for MPLS

mpls
#
mpls ldp
graceful-restart //Enable LDP GR
#
NE40E-X8
undo shutdown
ip address 10.0.1.1 255.255.255.252
mpls //enable MPLS on interface
mpls ldp //enable MPLS LDP on interface
-313-
11.8 Service Bearer and VRF Design

11.8.1 Overview
There are two kinds of major services to ET Mobile Network: 1. Circuit Switch (CS) Service and;
2. Packet Switch (PS) Services. This section summarizes the association between CS & PS Core
interfaces with service VRFs. This documentation will not discuss the details of every interface
type. Please refer to the relevant 3GPP document.
11.8.2 CS Service Bearer

Figure 11- 23 CS service bearer overview
VRF of GSM VRF of FL
VRF of DATA_Center VRF of BOLE-OCS

NGN-SS
VRF of CDMA FL
ER_Data_A
VRF of OAM
ER_Data_B
CRBT
Signal
MSC
STP Signal
BOLE-OCS
GSM
Billing
ER_A IP Core ER_Voice_A VMS
STP
Media CDMA Signal MSCe
ER_B
ER_Voice_B
OAM GMSC
MGW
A GSM
Iu_CS
OAM DATA_Center HLR
O&M
Media
Billing
BSC RNC G&VMGW
IP RAN
Billing
NMS Center
The diagram above shows the type of major interface in CS domain beared in IP Core. The table
below classifies the interfaces into different type and its target service VRF type.
Table 11- 15 CS device interface and target VRF
Device Interface Traffic type VRF

type
BSC A signaling GSM

media GSM
RNC IuCS signaling GSM
media GSM
MGW Mc signaling GSM
Nb media GSM
MSC Mc/Nc signaling GSM
-314-
Device Interface Traffic type VRF

type
HLR Gr signaling(communicate with other GSM

CS/PS device)
signaling(synchronize HLR data) GSM
STP Mc/Nc signaling GSM
MSC/MG O&M Management OAM
W
MSC Bi Billing OAM
MSC Li Listening OAM
In expansion project, bearer solution had been deployed in existing network, so this part of design
will follow the existing IP Core network.
11.8.3 PS Service Bearer

Figure 11- 24 PS service bearer
VRF of GSM VRF of PS_GN WAP Proxy
VRF of OAM VRF of DATA_Center MMS Proxy

VRF of DATA VRF of BOLE-OCS Internet
OCS
ER_Voice_A
BR_B BOLE-OCS
Gi GGSN
BR_A
Gy DNS
ER_A ER_Voice_B
UGW PS_GN
Gn/Gp PS_GN IP Core GTPU
Gn/Gp Gn_DT GTPC GGSN
GSM
Gr/Iu-C/Iu-U/S6a/SGs GSM
SGSN
PS_GB ER_B
Gb
USN
Bi/Ga OAM DATA_Center
OAM
HLR GMSC
O&M/Li
Iu-C/Iu-U
Gb OM/E&I
NMS Billing
BSC Center
RNC
IP RAN
The diagram above shows the type of major interconnecting interface in PS domain. The table
below classifies the interfaces into different type and its target service VRF type.
Table 11- 16 PS device interface and target VRF
Device
Interface Traffic Type VRF
Name
Gb PS_GB
USN/SGSN
Gr/Iu-C/Sig/S6a signaling GSM
-315-
Iu-U data GSM

Gn/Gp/S10/S11 Data/data roaming PS_GN
Li Listening OAM
Ga billing OAM
S1-MME LTE signaling LTE-C
OM management OAM
Gn/Gp/S5/S8/S11 data PS_GN
Gy ocs GGSN
Li listening OAM
Ga billing OAM
UGW/GGSN OM management OAM
Gn-DT Direct tunnel GSM
Gi/SGi data GGSN
S1-U Lte data LTE-U
Gx GGSN
Ga billing OAM
CG
Bi billing OAM
OM management OAM
DNS
Gn data PS_GN
In expansion project, bearer solution had been deployed in existing network, so this part of design
will follow the existing IP Core network.
11.8.1 Service VPN Design

The following naming convention is proposed for all the ER routers that requires VRF
configuration within ET Network. This description has a goal to identify the type of services that
the VRF carries. The VRF will be named as follows:
Format: <Service Classification>_<Service Name>
The following RD & RT design is proposed for all the ER routers that requires VPN / VRF
configuration within ET Network.
Format of RD: <AS Number>:<Service Number>
Format of Import RT: <AS Number>:<Service Number>
Format of Export RT: <AS Number>:<Service Number>
The service number range, RD & RT assignment are described below:
-316-
Table 11- 17 VPN Naming, RD and RT design
Service VRF RD Import-RT Export-RT

Type Name
65108:10001
65432:10232
65108:30001
65108:20001
65108:70001
65108:70002
65432:2200
65108:70007
GSM GSM 65108:10001 65108:10001
65432:10233
65108:12000001
65108:40100
65108:80026
65108:80001
65108:40001
65108:800174
65108:700041111
CDMA CDMA 65108:20001 65108:20001 65108:20001
FL FL 65108:30001 65108:30001 65108:30001
65108:40001
65108:70002
65108:10002
65108:70007
65432:10232
OAM OAM 65108:40001 65108:80026 65108:40001
65108:40001
65108:2000
65432:1111
65108:80020
65108:70001
DATA DATA 65108:50001 65108:50001 65108:50001
65108:700041110
PS_GB PS_GB 65108:700041110 65108:700041110
65108:70004
65108:700041111
PS_GN PS_GN 65108:700041111 65108:70004 65108:700041111
65108:10001
65108:70004
GGSN GGSN 65108:70004 65108:70001
65432:1100
-317-
65432:8901
65108:10001
65108:50001
65108:13000004
65108:70002
65108:800173
65108:700041110
65432:5000
LTE-C
LTE-U
PS_Gx
Configuration template for RD, import target and export target
[NE40E]ip vpn-instance vpn1 //Create a VRF instance

[NE40E-vpn-instance-vpn1]ipv4-family //configure IPv4 VRF
[NE40E-vpn-instance-vpn1-af-ipv4]route-distinguisher
NE40E-X8
<AS Number:service number> //configure RD
[NE40E-vpn-instance-vpn1-af-ipv4]vpn-target
<as number:service number> both //Configure RT
-318-
12 Synchronization Design
12.1 IP Clock Solution and Capacity

All the Mobile services carried on ET IPRAN network except the exsiting CDMA service have now
evolved into using the IP technology, and the IP clock (Huawei IPCLK) is the solution provided for
keeping the frequency synchronization between the ip-based base stations. Huawei IPCLK uses
UDP protocol (udp port: 319&320) to encapsulate timestamp and send to remote base station to
synchronize clock.
Figure 12- 1 The traffic module of the IP CLK Solution
In ET IPRAN network, there will be 2 IP CLK servers deployed in Microwave and Nifas Silk site
for redundancy; each of them will provide 3 interface (each interface ip act as a logical Clock server
for bases tations) connections to the RSG, and the IPCLK’s sync message will be treated as normal
service packet carried by WOAM service VRF. L3VPN protection technologies can also apply to the
IPCLK high availability.
-319-
Table 12-1 IP Planning table for the IP Clock
Port on Port on
Gateway IP
SERVER Server Service IP Router Router VRF
PA2: PA1:
IPCLK Server 1
0 10.204.104.2/30 Microwave 2/0/5 10.204.104.1/30 WOAM
PB2: PB1:
IPCLK Server 2
0 10.204.104.6/30 Nifas Silk 2/0/5 10.204.104.5/30 WOAM
PA4: PA3:
IPCLK Server 1
1 10.204.104.10/30 Microwave 2/0/6 10.204.104.9/30 WOAM
PB4: PB3
IPCLK Server 2
1 10.204.104.14/30 Nifas Silk 2/0/6 10.204.104.13/30 WOAM
PC6: PA5
IPCLK Server 1
2 10.204.104.18/30 Microwave 2/0/7 10.204.104.17/30 WOAM
PC6: PB5
IPCLK Server 2
2 10.204.104.22/30 Nifas Silk 2/0/7 10.204.104.21/30 WOAM
Configuration for IP Clock on RSG
Microwave-RSG-A:
#
ip vpn-instance WOAM
ipv4-family
#
ip binding vpn-instance WOAM //Bind the VPN instance to a specific service interface.
ip address 10.204.104.1 255.255.255.252
#
bgp 65109
ipv4-family vpn-instance WOAM
import-route direct
#
Nifas Silk-RSG-A:
#
-320-
ipv4-family
#
ip binding vpn-instance WOAM //Bind the VPN instance to a specific service interface.
ip address 10.204.104.5 255.255.255.252
#
bgp 65109
import-route direct
#
12.2 Synchronous Ethernet Clock

Ethernet clock synchronization technology is used to transmit clock signals over the physical layer
on the Ethernet network. For bearing the existing 2G CDMA service (TDM) in IP RAN Network,
the Sync.E solution will be used to keep the frequency synchronization between the CSGs and RSGs,
on which the TDM frames encapsulation and decapsulation happens.
The existing BITS (Building Integrated Timing Supply System) will be used as the external clock
sources. For the existing CDMA base stations, the external reference clock source is the GPS
statellites; there have no need to provide the frequency and phase by IP RAN network.
12.2.1 Design Guidelines

The guidelines for designing the synchronous Ethernet clock are as follows:
-321-
Figure 12- 2 The connection between the BITS and RSGs
 ET is in charge for the Configuration of two existing BITS in Microwave site as master and slave
external clock sources to implement device-level protection for clock sources. When the master
clock fails, the slave clock can be switched to work as the master clock.
Figure 12- 3 The external clock interface of the RSGs
 The RSGs in Microwave site just trace the clock signals from an external BITS using the 2
Mbit/s external clock interface as the figure above (BITS0/BITS1/BITS2). To improve the clock
reliability, the external clock interfaces on both system control boards will be used to connect to the
external clock source.
 The active and standby tracing paths will be decided by the planned clock priority values. This
clock priority will be properly desinged and configured on the interface to avoid timing loop. The
Synchronization Status Message (SSM) will be enabled for network-wide devices to reflect
transmission level of a synchronous timing signal.
 For an ETH-TRUNK on a ring network, add only one member link port of the ETH-TRUNK to
the clock source list. To prevent a timing loop, do not add all the member ports to the clock source
list.
-322-
12.2.2 Design Result

Figure 12- 4 Clock priority planning on ET IP RAN network
12.2.3 Configure Example for Synchronous Ethernet clock

-323-
Selecting the Clock Source
Microwave-RSG-A
Configure the clock source information in the system view.
clock bits-type bits2 2mbps //Specify the type of clock signals from the external reference
clock source. 2 Mbit/s signals are used in this example.
clock source bits2 priority 10 //Configure the priority for the external clock port according to
the network plan.
clock source bits2 synchronization enable //Enable clock synchronization for the external time
port.
Microwave-RSG-B
clock bits-type bits2 2mbps //Specify the type of clock signals from the external reference
clock source. 2 Mbit/s signals are used in this example.
clock source bits2 priority 20 //Configure the priority for the external clock port according
to the network plan.
clock source bits2 synchronization enable //Enable the priority for the external time port.
Configuring Synchronous Ethernet
Microwave-RSG-A
clock ethernet-synchronization enable //Enable synchronous Ethernet in the system view.
clock ssm-control on //By default, SSM control is enabled on ATN device.
clock synchronization enable
clock priority 20
-324-
Yeka-ASG-A:
clock ethernet-synchronization enable //Enable synchronous Ethernet in the system view.
clock ssm-control on //By default, SSM control is enabled on ATN device.
clock priority 10 //Assign a clock priority to the reference clock source on the port.
clock synchronization enable //Enable synchronous Ethernet in the interface view.
clock priority 10
287E-CSG
clock ethernet-synchronization enable
clock priority 10
clock priority 20
-325-
13 QoS Design
13.1 Traffic Classification and Marking

Simple traffic classification implements the mapping between the internal priority and the external
priority. Packets are classified based on DSCP values of IP packets, EXP values of MPLS packets.
Then, the mapping between the priorities of the packets on different networks is created. The
Diff-Serv (DS) domain is comprised of the DS nodes that adopt the same service policies and
Per-Hop Behavior (PHB) set. The traffic policies are defined in a DS domain that is bound to an
interface to implement simple traffic classification.
IP & MPLS Forward Traffic Classification
The following figure shows the deployment of QOS from base station to the base station Controller.
Figure 13-1 IP & MPLS Forward Traffic Classification
The following figure shows the deployment of QOS from the BSC/RNC to CS/PS device in two
scenerio:
-326-
Figure 13-2 Scenerio one: RNC/BSC and CS/PS domain in the same site
Figure 13-3 Scenerio two: RNC/BSC and CS/PS domain in the diffrent site
IP & MPLS Forward Traffic Marking
The MPLS DiffServ model defines two factors for the packets that are transmitted over an MPLS
network: in which the DSCP field and the EXP field are propagated. In this manner, differentiated
QoS is guaranteed for transmission
The ingress PE adds a label to the packet by copying the DSCP value to the EXP field. If the EXP
value is changed in the MPLS network, the change affects the PHB adopted when the packet leaves
the MPLS network. That is, the egress PE adopts the PHB according to the EXP value.
The following figure shows the QOS behaviour from base station to base station controller.
-327-
Figure 13-4 The qos marking behavior from base station to base station controller
The following figure shows the QOS behaviour from base station Controller to CS/PS domain.
Figure 13-5 The qos marking behavior from base station Controller to CS/PS domain.
13.2 Congestion Management and Avoidance

13.2.1 Congestion Management
When congestion occurs on the network, delay-sensitive services like voice require better QoS
treatment than others, thus demanding the deployment of congestion management measures. This
section discusses the congestion management and avoidance measures. In the ET IP RAN network
we used the combination of Strict Priority Queue (PQ) and Weighted Fair Queuing (PQ+WFQ) for
scheduling services.
-328-
PQ is recommended for services sensitive to delay and jitter or service critical to the management of
equipment. This includes routing protocol packets, voice calls, signaling and network management
service. The basic working mechanism of PQ is that low priority packets can only be processed after
the high priority packets are scheduled in a strict manner.
For all other traffic classes WFQ will be used .This is to ensure certain percentage of bandwidth is
always reserved for the remaining class of service. This is achieved by setting WFQ weight for the
designated traffic class. The following table shows the queue scheduler design. These default values
are proposed by wireless department for the mobile service.
Table 13-1 PQ+WFQ Design
Service Congestion
Priority Queue DSCP Scheduler Weight
avoidance
Network Control CS7 56 PQ N.A. Tail-drop
Network Control
CS6 48 PQ N.A. Tail-drop
2/3G O&M
LTE O&M
VoIP
High-priority PS
AF41 34 WFQ 15% Tail-drop
data
Medium-priority
PS data
Low-priority PS
data
Enterprise service AF11 10 WFQ 10% Tail-drop
HSI BE 0 WFQ 10% Tail-drop
13.2.2 Congestion Avoidance

WRED is a mechanism for the deployment of randomly dropped TCP traffics as the service class
queue build up and exceeds the lower threshold. The packet dropping probability increases as the
queue length increases from the lower threshold to the higher one. Different thresholds are used for
each traffic queue with different coloring (priority within sub-class). Sample thresholds designs are
shown in table 13-2.
-329-
Table 13-2 WRED Drop Threshold for Different Packet Color
Color Lower limit percentage Higher limit percentage
Green 80 100
Yellow 70 100
Red 60 100
Congestion Management and Avoidance takes effect on the output port (packets leaving the router)
and they use default configuration.
The following figure shows where the congestion management and avoidance takes effect.
Figure 13- 6 The congestion management and avoidance from basestation to basestation controller
Figure 13- 7 The congestion management and avoidance from BSC/RNC to CS/PS domain
-330-
13.3 Configure Example for Qos deployment

CSG:
The CSG performs traffic classification and priority mapping based on DSCP values and performs
priority-based scheduling using the default DiffServ mode.
ASG:
The ASG performs priority mapping based on MPLS EXP values and then performs priority-based
scheduling.To prevent changes of DSCP values in IP packets of the wireless side, disable PHB
mapping at all interfaces of CSGs and RSGs.
RSG:
VLANIF interfaces support disabling of PHB mapping. You can configure a solution in which the
RNC is configured with master/slave interfaces for interworking with RSGs and RSGs are
configured with VRRP-enabled VLANIF interfaces.
CSG (125D-CSG):
#
interface GigabitEthernet 01/2 //to basestation
trust upstream default
#
interface GigabitEthernet 0/5/0 //to ASG
-331-

#
interface GigabitEthernet 0/6/0 //to another csg
#
ASG (Kality-ASG-A):
#
qos phb disable
#
eth-trunk 1
#
eth-trunk 1
#
qos phb disable
#
eth-trunk 2
#
eth-trunk 2
#
qos phb disable
#

qos phb disable
-332-
#
RSG (Nifas silk-RSG-A):
#
portswitch
trust upstream default vlan 1430

qos phb disable vlan 1430
#
portswitch
trust upstream default vlan 1430

qos phb disable vlan 1430
#
ineterface VLANIF 1430

qos phb disable
#
qos phb disable
eth-trunk 4
#
eth-trunk 4
#
-333-
14 Network Mangement System
14.1 End to End NMS Design

The U2000 is a management system for IPRAN Network elements such as 93Switch, RTN, ATN,
CX, and NE40E. It is also a major future-oriented network management solution that provides
powerful element management and network management functions.
Figure 14- 1 Design for end to end NMS
14.1.1 ATN&CX &NE40E&93Switch

An NMS server U2000 is connected with master and slave NE40E through a Layer 2 93Switch to
manage and maintain devices on IP backhaul network. The NMS can manage 93Switch, ATNs, CXs
and NE40Es as long as these devices are reachable to the server.
Management IP Address Design
The loopback ip address is used for route management, while 93Switch use the vlanif ip for
management.
-334-
Management Route Design
Figure 14- 2 Design for Mangement Route
 Configure a VRRP backup group on NE40E in pairs with one as the master and the other one as
the backup.
Microwave-NE40E-A
#
-type dot1q 4092
-ip 10.204.204.4

#
Eth-trunk 30
Eth-trunk 30
Eth-trunk 30
Eth-trunk 30
#
Microwave-NE40E-B:
#
-335-

-type dot1q 4092
ip address 10.204.204.3 28
-ip 10.204.204.4
#
Eth-trunk 30
Eth-trunk 30
Eth-trunk 30
Eth-trunk 30
 Configure a static aggregate route pointing to the RSG router for all loopback address of CX and
ATN.
Microwave-NE40E-A
#
ip route-static 10.0.5.0 24 interface Eth-trunk 15.100 10.1.29.91 preference 5
#// The default preference value of the static route is 60 which is lower than ISIS (15)
Microwave-NE40E-B:
#
 Configure a static route on each RSG in microwave and Nifas Silk Site with the destination being
the U2000. And then the RSGs need to import the NMS server's IP address into aggregation IGP
process.
Microwave-RSG-A
#
#
ip ip-prefix U2000 index 10 permit 10.204.204.0 28
route-policy U2000 permit node 10
if-match ip-prefix U200
-336-
#
isis 100
import-route static cost 100 route-policy U2000
#
Microwave-RSG-B:
#
#
#
isis 100
import-route static cost 200 route-policy U2000
 ASGs are responsible to advertise routes between the access and aggregation side. ASGs only
import the ip addresses of the U2000 to IGP processes of the access ring and all loopback addresses
of the CSG to the IGP process of aggregation ring . Tags are added to routes imported to the ASG so
that routes learned from the aggregation ring are not advertised to the aggregation ring again and
routes learned from the access ring are not advertised to the access ring again. This prevents route
loops.
ASG
#
//Configure the IP prefix for the network segment route of the U2000.
#
apply tag 2
#
route-policy pref-nms permit node 10
if-match tag 2
apply preference 255
#
-337-
isis 1
import-route isis 100 inherit-cost route-policy U2000
preference route-policy pref-nms
#
ip ip-prefix acc index 10 permit 0.0.0.0 0 greater-equal 30 less-equal 32
//Configure all the routes with the mask from 30 to 32
#
route-policy acc deny node 5
#
route-policy acc permit node 10
if-match ip-prefix acc
apply tag 2
#
isis 100
import-route isis 1 inherit-cost route-policy acc
14.1.2 RTN
The special RTN which connect to ATN directly used the management port will be defined as GNE
(gateway network element). The GNE RTNs and NMS are needed to be IP reachable by advertise
the ip segment route between the ATN and RTN on the ATN. Then the other RTNs can be managed
by NMS through GNE RTN.
Figure 14- 3 Design for RTN
CSG:
Interface Eth-trunk 1.4093
-338-
vlan-type dot1q 4093

isis enable 1
isis silent //Configure the IS-IS interface in passive state
# //the first and second GE port of ATN will be used to connect to RTN

eth-trunk 1
#
eth-trunk 1
#
14.1.3 BASE STATION OAM

Apart from the routers such as ATN、CX and NE40E, for HW BTS/NodeB/eNodeB base station, the
OAM traffic will be carried by WOAM VRF deployed on IPRAN Network. Then it goes to M2000
(the mange system for the base station).
Figure 14- 4 Traffic module of the Base Station OAM
Table 14- 1 VRF design of base station OAM
O&M for Base D-CSG 65109:9 65109:9 65109:9

Station CSG 65109:10 65109:9
ASG 65109:9 65109:9 65109:10
RSG 65109:9 65109:9
-339-
Microwave-NE40E-A
#
ipv4-family
#
ip binding vpn-instance WOAM
ip address 10.204.202.16 255.255.255.224
3 priority 120
#
vlan-type dot1q 3
ip address 10.1.29.10 255.255.255.252
#
bgp 65108
import direct-route
#
Microwave-NE40E-B
#
ipv4-family
#
-340-

ip address 10.204.202.17 255.255.255.224
#
vlan-type dot1q 3
ip address 10.1.29.42 255.255.255.252
#
bgp 65108
peer 10.1.29.41 as-number 65109
import direct-route
#
Microwave-RSG-A
#
ipv4-family
#
vlan-type dot1q 3
ip address 10.1.29.9 255.255.255.252
#
bgp 65109
peer 10.1.29.10 as-number 65108
#
-341-
Microwave-RSG-B
#
ipv4-family
#
vlan-type dot1q 3
ip address 10.1.29.41 255.255.255.252
#
bgp 65109
peer 10.1.29.42 as-number 65108
#
14.2 U2000 Planning

There will be 2 U2000 Servers deployed in two different locations Microwave and Nifas Silk for IP
RAN network configured with active-standby mode.This will eliminate the risk of any hardware or
line failure as one will be activated when primary server has been detected down.
The following figure shows the design for the heartbeat communication and the basic requirement of
the transmission network (bandwidth >30M, packet loss <1% and time delay < 50ms). This
heartbeat traffic can keep the data synchronization between the 2 U2000 servers. ET will provide us
100M bandwidth for U2000 heartbeat traffic through SDH network.
-342-
Figure 14- 5 The IP design for the heartbeat communication
The following figure shows the IP design for the NE Management between the NE40E and U2000.
Figure 14- 6 The IP design for the NE Management
The following figure shows the IP design for the Server & Disk array Management, and there are 2
disk arrays server (16GB Cache,12*600G 10K SAS Harddisk,8 FC Host Port,8 Fiber,HS Storage
Array Control System Software) configuration are propose to meet the required capacity of the
U2000 NMS in this network.
-343-
Figure 14- 7 The IP design for the Server & Disk array Management
Table 14- 2 The IP design result for U2000
Primary Site (Microwave)

PORT IP Address Gateway Usage
U2000 server
IP address for the
NET
IPC6:10.204.204.6/28 IPC5:10.204.204.14/28 workstation primary
MGT1
controller
IPC5:10.204.204.14/28
NET0 IPC1:10.204.204.1/28 System IP address
IPC4:10.204.204.4/28(VIP)
IP address of the heartbeat
NET1 IPA1:10.204.204.243/30
network service
disk array
NET IP address for the disk
IPC7:10.204.204.7/28 IPC5:10.204.204.14/28
MGT1 array primary controller
IPC8:10.204.204.8/28 IPC5:10.204.204.14/28
MGT2 array secondary controller
NE40E
IP address for Master
NE40E IPC2:10.204.204.2/28
NE40E
IP address for Slave
NE40E IPC3:10.204.204.3/28
NE40E
Secondary Site (NifaSilk)
PORT IP Address Gateway Usage
U2000 server
NET IP address for the
IPD6:10.204.204.22/28 IPD5:10.204.204.30/28
MGT1 workstation primary
-344-
controller
IPD5:10.204.204.30/28
NET0 IPD1:10.204.204.17/28 System IP address
IPD4:10.204.204.20/28
IP address of the heartbeat
NET1 IPA2:10.204.204.244/30
network service
Disk array
IPD7:10.204.204.23/28 IPD5:10.204.204.30/28
MGT1 array primary controller
IPD8:10.204.204.24/28 IPD5:10.204.204.30/28
MGT2 array secondary controller
NE40E
IP address for Master
NE40E IPD2:10.204.204.18/28
NE40E
IP address for Slave
NE40E IPD3:10.204.204.19/28
NE40E
14.3 U2000 NBI Overview

The U2000 offers network monitoring information, such as the alarm, performance, and inventory
information, for OSSs through NBIs. The NBIs support network management functions, such as
service provisioning and diagnostic tests.
Table 14- 3 Supported NBI functions by U2000
Service Feature Network
Interface Elements
XML Alarm ■
Performance ■
Inventory ■
Service provisioning ■
CORBA Alarm ■
Performance ■
Inventory ■
Service provisioning ■
SNMP Alarm ■
Text Performance ■
TL1 Inventory □
-345-
Service Feature Network
Interface Elements
Service provisioning □
Customer OSS Test Diagnostics □
-346-
15 Security Design
15.1 Security Overview

All the devices in network won’t directly expose to external potential attacker, and almost services
of ET Network are transported through MPLS that provides better security than IP transportation.
To summary up, ET IP RAN Network faces relatively low security threats. We propose to deploy the
following security measures in the Network.
All the routers and switches enable Control Plane Protection function to protect CPU from attacking.
(Enable by default)
ISIS, LDP, BGP and NTP runs in ET network enable MD5 neighbor authentication to prevent DOS
attacking. Regarding the detailed information, please refer to the previous corresponding sections.
Secure operation and management measures like SSH, AAA, SNMP community. Regarding the
detailed information, please refer to the previous corresponding sections.
Application-layer service association function will create the security policy dynamically.
Disable all the unnecessary services.
15.2 Security in Equipment

15.2.1 SSH: STELNET and SFTP
Conventional Telnet and FTP transfer data unencrypted. This is because the Telnet/FTP sends
password in plain text and can be easily sniffed. The secure shell (SSH) feature, however, offers
security guarantee and powerful authentication to protect devices from attacks such as IP address
spoofing and interception of plain text passwords. Therefore, Huawei recommends SSH must be
enabled on the devices on the entire network for remote access. There are two applications for SSH:
stelnet and sftp.
In stelnet, Huawei will configure local authentication for the users. The configuration steps are as
follows:
-347-
Configuration examle for the csg router :
1. Create an asymmetric local key pair on the SSH server(ATN will be the server).
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA] rsa local-key-pair create

[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA] stelnet server enable
2. Create the user, and configure authentication type and service type
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA] ssh user root

[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA] ssh user root
authentication-type password
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA] ssh user root service-type
stelnet
Configure the mode of authentication in VTY interface.
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA] user-interface maximum-vty
15
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA -ui-vty0-4] authentication-mode
aaa
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA -ui-vty0-4] protocol inbound all
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA -ui-vty0-4] idle-timeout 5 0
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA -ui-vty0-4] quit
15.2.2 Local User List

local user accounts will be configured in equipments.
Table 15- 1 Local User List
Username Service Type Password

huawei Telnet/SSH EThuawei2012
hwsubcon Telnet/SSH HWsubcon2012
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA] aaa
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA-aaa] local-user huawei password cipher
EThuawei2012
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA-aaa] local-user huawei service-type ftp
terminal telnet ssh
-348-
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA-aaa] local-user huawei level 1
15.2.3 ACL for Remote Access

One ACL list will be configure in VTY interface to limit the access users. Only some user with
specific source address can access equipment. The specific source address table is in below table:
Configuration template for remote access ACL
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA]acl number 3999

[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA -acl-3999]rule 1 permit ip source 10.204.204.16
255.255.255.240
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA -acl-3999]rule 1 permit ip source 10.204.204.0
255.255.255.240
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA]user-interface vty 0 4
[111095_ATN_01_CSG_A.HW.Gerji.EAAZ.AA -user-interface-vty]acl 3999 inbound
15.3 Security in Network

15.3.1 ISIS MD5 Authentication
Huawei recommends the deployment of protocol security measures to protect the router from
unauthorized ISIS peering connection. This protects against unauthorized client injecting false routes
into the network. Following the same practice from existing ZTE core network, Huawei will deploy
ISIS interface based MD5 authentication and silence interface between Huawei NE40E and ZTE
ER/CR router.
The topology is shown below:
ISIS
Eth-trunk 5
111051_NE_01_ER_A.HW.Microwave.CAAZ.AA ZTE_ER_ROUTER
The configuration is shown below:
[111051_NE_01_ER_A.HW.Microwave.CAAZ.AA] interface Eth-trunk 5

[111051_NE_01_ER_A.HW.Microwave.CAAZ.AA - Eth-trunk 5] isis authentication-mode md5
-349-
cipher ISIS_PWD level-2

[111051_NE_01_ER_A.HW.Microwave.CAAZ.AA - Eth-trunk 5]isis silent
15.3.2 BGP MD5 Authentication

For similar reason deploying MD5 authentication for ISIS, Huawei recommends the deployment of
MD5 authentication to protect the router from unauthorized BGP peering connection. Differs to ISIS,
it does not authenticate the BGP packets, instead it uses MD5 authentication password for TCP
connection. Huawei will deploy BGP based MD5 authentication between Huawei NE40E and ZTE
ER/CR router. The configuration is shown below:
AS:65108
BGP
Eth-trunk 5
10.0.2.113
111051_NE_01_ER_A.HW.Microwave.CAAZ.AA ZTE_ER_ROUTER
Configuration template for BGP MD5 authentication
[111051_NE_01_ER_A.HW.Microwave.CAAZ.AA] bgp 65108

[111051_NE_01_ER_A.HW.Microwave.CAAZ.AA -bgp] peer 10.0.2.113 password cipher
BGP_PWD
15.3.3 MPLS LDP MD5

Huawei routers support the option of authenticating LDP packets by using MD5 message digest.
This will provide additional security against tampering/forging of LDP packets if required. Huawei
will deploy LDP based MD5 authentication between Huawei NE40E and ZTE ER/CR router.
LDP
Eth-trunk 5
10.0.5.231
111051_NE_01_ER_A.HW.Microwave.CAAZ.AA 111051_NE_01_ER_B.HW.Microwave.CAAZ.AA
-350-
Configuration template for MPLS LDP MD5 authentication
[111051_NE_01_ER_A.HW.Microwave.CAAZ.AA] mpls ldp

[111051_NE_01_ER_A.HW.Microwave.CAAZ.AA] md5-password cipher 10.0.5.231
LDP_PWD
16 Future IPV6
16.1 IPV6 Overview

16.1.1 Definition
Internet Protocol Version 6 (IPv6), also called IP Next Generation (IPng), is the second-generation
standard protocol of network layer protocols. As a set of specifications defined by the Internet
Engineering Task Force (IETF), IPv6 is the upgraded version of Internet Protocol Version 4 (IPv4).
The most obvious difference between IPv6 and IPv4 is that IP addresses are lengthened from 32
bits to 128 bits. Featuring the simplified header format, sufficient address space, hierarchical
address structure, flexible extended header, and enhanced neighbor discovery (ND) mechanism,
IPv6 is competitive in the future market.
CX600/NE40E/ATN950B supports IPv6 on the all interfaces:
16.1.2 Purpose
The IPv4-based Internet achieves a great success. Consequently, the IP technology is widely
applied. With the rapid development of the Internet, however, deficiencies in IPv4 become
increasingly obvious in the following aspects:
 The IPv4 address space is insufficient.
An IPv4 address is identified by using 32 bits. In theory, a maximum of 4.3 billion addresses can be
provided. In actual applications, less than 4.3 billion addresses are available because of address
allocation. In addition, IPv4 address resources are allocated unevenly. Address resources of the
-351-
USA occupy almost half of the global address space; the address resources of Europe are relatively
fewer than those of the USA; the address resources of the Asian-Pacific region are much fewer. The
development of mobile IP and broadband technology requires more IP addresses. Consequently,
limited IPv4 address resources directly restrict the further development of the IP technology.
There are several solutions to IPv4 address shortage. Classless Interdomain Routing (CIDR) and
Network Address Translator (NAT) are two representative solutions to IPv4 address shortage.
CIDR and NAT, however, have their disadvantages and unsolved problems. This promotes the
development of IPv6.
 The backbone device maintains too many routing entries.
Many discontinuous IPv4 addresses are allocated because of the problems in the initial IPv4
address allocation planning. As a result, routes cannot be aggregated effectively. The increasingly
large routing table consumes a lot of memory, degrading forwarding efficiency. Subsequently,
device manufacturers have to upgrade products to improve route addressing and forwarding
performance.
 Address auto-configuration and readdressing cannot be performed easily.
An IPv4 address occupies only 32 bits and IP addresses are allocated unevenly. Consequently, IP
addresses need to be reallocated during network expansion or network replanning. The workload
for maintenance is heavy.
 Security cannot be well guaranteed.
As the Internet develops, security problems become more serious. The IPv4 design does not fully
consider security, so the original framework cannot ensure end-to-end security. IPv6 provides
end-to-end security by using IP security (IPSec) as the standard extended header.
IPv6 radically solves the problem of IP address shortage. Moreover, IPv6 has the following
advantages: It is easy to deploy, compatible with various applications, easy for IPv4 networks to
transit to IPv6 networks. With so many obvious advantages over IPv4, IPv6 is rapidly developed.
16.2 Supported IPv6 related RFCs and usage in each proposed

device
The following table lists the references support by NE40E/CX600/ATN950B.
RFC Description
-352-
RFC 793 Transmission Control Protocol

RFC 768 User Datagram Protocol
RFC 1887 An Architecture for IPv6 Unicast Address Allocation
RFC 1981 Path MTU Discovery for IP version 6
RFC 2373 IP Version 6 Addressing Architecture
RFC 2374 An IPv6 Aggregatable Global Unicast Address Format
RFC 2375 IPv6 Multicast Address Assignments
Version 6 of the Internet Protocol (IPv6), also sometimes referred to
RFC 2460 as IP Next Generation or IPng.
RFC 2461 Neighbor Discovery for IP Version 6 (IPv6)
Internet Control Message Protocol for the Internet Protocol Version 6
RFC 2463 Specification
RFC 2464 Transmission of IPv6 Packets over Ethernet Networks
Management Information Base for IP Version 6: Textual Conventions
RFC 2465 and General Group
RFC 2466 Management Information Base for IP Version 6: ICMPv6 Group
RFC 2473 Generic Packet Tunneling in IPv6 Specification
RFC 2711 IPv6 Router Alert Option
RFC 2893 Transition Mechanisms for IPv6 Hosts and Routers
RFC 3056 Connection of IPv6 Domains via IPv4 Clouds
RFC 3068 An Anycast Prefix for 6to4 Relay Routers
Default Address Selection for Internet Protocol Version 6
RFC 3484 (IPv6)Section 2.1
RFC 3513 IP Version 6 Addressing Architecture
RFC 3971 SEcure Neighbor Discovery (SEND)
RFC 3972 Cryptographically Generated Addresses (CGA)
RFC 4191 Default Router Preferences and More-Specific Routes
RFC 4214 Intra-Site Automatic Tunnel Addressing Protocol(ISATAP)
RFC 4291 Internet Protocol Version 6 (IPv6) Addressing Architecture
Internet Control Message Protocol (ICMPv6) for the Internet Protocol
RFC 4443 Version 6 (IPv6) Specification
RFC 4861 Neighbor Discovery for IP version 6 (IPv6)
RFC 4943 IPv6 Neighbor Discovery On-Link Assumption Considered Harmful
RFC 4982 Security (CGA) Support for Multiple Hash Algos
The OAM port of RTN support IPv6. And Ipv6 static route also can be configured in RTN device. This is enough for U2000
manage the RTN. The service port on the RTN is not necessary to support IPv6 beacase RTN work as L2 device in ET
IPRAN network.
-353-
16.3 IPV6 Evolution

IPv4 addresses would be used up. According to address storage and service development, addresses
would be exhausted at the end of 2011. This improves the transition process of IPv6 and speeds up
IPv6 deployment in the world. With the improvements of IPv6 industry chain, technical standards
are gradually mature and commercial use in a large scale is possible.
To achieve sustainable development, carriers all over the world actively support smooth
IPv4-to-IPv6 transition. U.S.A and European countries focus on research and experiment on IPv6.
Asian countries such as China and Korea are on top of the industry in terms of commercial and
service development of IPv6. During the transitional period from IPv4 to IPv6, IPv4 address and
IPv6 address mainly coexist to ensure service compatibility and maximize the investment return.
16.4 Supported Migration techniques

16.4.1 ISIS for IPv6
Extended IS-IS for IPv6 is defined in the draft-ietf-isis-ipv6 of IETF. Extended IS-IS processes and
calculates IPv6 routes. The draft introduces two TLVs and a Network Layer Protocol Identifier
(NLPID) for extended IS-IS to support IPv6.
The two new TLVs are:
 IPv6 Reachability
The type value is 236 (0xEC). It illustrates the reachability of the network by defining the
routing prefix and metric.
 IPv6 Interface Address
The type value is 232 (0xE8). It is equal to the IP interface address TLV of IPv4, except that it
changes the original 32-bit IPv4 address to a 128-bit IPv6 address.
The NLPID is an 8-bit field that identifies the protocol packets of the network layer. The NLPID of
IPv6 is 142 (0x8E). If IS-IS supports IPv6, it advertises routing information through the NLPID
value.
16.4.2 BGP for IPv6

BGP4+ is mainly used to control route transmission and select optimal routes.
-354-
BGP4+ is a dynamic routing protocol used between Autonomous Systems (ASs), and it is an
extension of BGP.
The traditional BGP4 can manage only the IPv4 routing information. For other network layer
protocols such as IPv6, the traditional BGP4 has a limited capability to transmit routing information.
The IETF introduces BGP4+ as a supplement to BGP4 to support multiple network layer protocols.
The RFC for BGP4+ is RFC 2858 (Multiprotocol Extensions for BGP4).
To support IPv6, BGP4 needs to reflect the IPv6 protocol information to the Network Layer
Reachable Information (NLRI) attribute and the Next_Hop attribute.
BGP4+ introduces two NLRI attributes:
 Multiprotocol Reachable NLRI (MP_REACH_NLRI): advertises the reachable routes and the
next hop information.
 Multiprotocol Unreachable NLRI (MP_UNREACH_NLRI): withdraws the unreachable routes.
The Next_Hop attribute of BGP4+ is in the format of an IPv6 address. It can be an IPv6 global
unicast address or the link-local address of the next hop.
BGP4+ can be applied to an IPv6 network by using the BGP attribute of multiple protocol extension.
The message and routing mechanisms of BGP remain unaltered.
16.4.3 IPv6 over IPv4

An IPv6 packet is transparently transmitted after being encapsulated into an IPv4 packet.
During the transition from the IPv4 Internet to the IPv6 Internet, IPv4 networks have been widely
deployed while IPv6 domains are isolated and dispersed around the world. It is not economical to
connect these isolated sites with private lines.
The usual method is tunnel technology. This technology creates tunnels over IPv4 networks to
connect isolated IPv6 domains. This is similar to the situation where the tunnel technology is used to
deploy VPNs on the IP networks.
The tunnel used to connect isolated IPv6 domains over IPv4 networks is called IPv6 over IPv4 tunnel.
To implement this tunnel, enable IPv4/IPv6 dual stacks on the devices at the border of the IPv4
network and the IPv6 network.
-355-

You can create tunnels on the IPv6 networks to connect IPv4 isolated sites so that IPv4 isolated sites
can access other IPv4 networks through the IPv6 Internet.
During the transition from the IPv4 Internet to the IPv6 Internet, IPv6 networks have been widely
deployed, whereas IPv4 networks are isolated. The tunnel technology can be adopted to establish
tunnels over IPv6 networks to connect isolated IPv4 networks. This is similar to the situation where
the tunnel technology is used to deploy VPNs on the IP networks. The tunnel used to connect isolated
IPv4 networks over IPv6 networks is called an IPv4 over IPv6 tunnel.
16.4.5 DS-Lite
Definition
Dual-Stack Lite (DS-Lite) is an IPv6 transition technology. DS-Lite enables an IPv4 in an IPv6
tunnel to be established between the CPE and CGN devices. Also, a private IP address can be
encapsulated for NAT on the CGN. And, a private IP address can be translated to a public network
IPv4 address.
Purpose
IPv6 replacing IPv4 is a trend of network development. The transition from IPv4 to IPv6 is a long
process and IPv4 networks will exist for a long time. Carriers still therefore need to support IPv4
networks and endeavor to alleviate the consequences of IPv4 address exhaustion.
DS-Lite offers a solution to carriers using tunneling and NAT. User terminals using private network
IPv4 addresses can access public IPv4 networks through an IPv6 network between the CPE and
CGN devices.
Benefits
Benefits to carriers
 DS-Lite allows the setup of IPv6 networks to carry the existing IPv4 service when the number
of IPv4 addresses is insufficient.

 DS-Lite provides a technical plan for the transition from IPv4 to IPv6 and protects the
investment of carriers.
Example
-356-
16.5 IPv6 Deployment Strategy

16.5.1 ISIS for IPv6
This part provides an example for interconnecting IPv6 networks through IS-IS.
Networking Requirements
As shown in below Figure:
 CX-A, CX-B, CX-C, and CX-D belong to the same AS. They are interconnected through IS-IS in
the IPv6 network.
 CX-A, CX-B, and CX-C belong to area 10. CX-D belongs to area 20.
 CX-A and CX-B are Level-1 routers. CX-C is a Level-1-2 router. CX-D is a Level-2 router.
Figure :Networking diagram of basic IS-IS IPv6 feature
Configuration Roadmap
The configuration roadmap is as follows:
1. Enable the capability of IPv6 forwarding on each CX device.
2. Configure an IPv6 address for each interface.
3. Enable IS-IS on each CX device.
4. Configure the level.
5. Specify the network entity.
Data Preparation
-357-
To complete the configuration, you need the following data:
 IPv6 address of each interface on CX-A, CX-B, CX-C, and CX-D
 Area numbers of CX-A, CX-B, CX-C, and CX-D
 Levels of CX-A, CX-B, CX-C, and CX-D
Procedure
1. Enable the capability of IPv6 forwarding, and configure IPv6 address for each interface. Take the
display on CX-A as an example. The configurations of CX-B, CX-C and CX-D are similar to that
of CX-A. The detailed configurations are not mentioned here.
[HUAWEI] sysname CX-A
[CX-A] ipv6
[CX-A] interface pos 1/0/0
[CX-A-Pos1/0/0] ipv6 enable
[CX-A-Pos1/0/0] ipv6 address 10:1::2/64
2. Configure IS-IS.
# Configure CX-A.
[CX-A] isis 1
[CX-A-isis-1] is-level level-1
[CX-A-isis-1] network-entity 10.0000.0000.0001.00
[CX-A-isis-1] ipv6 enable
[CX-A-isis-1] quit
[CX-A] interface pos 1/0/0
[CX-A-Pos1/0/0] isis ipv6 enable 1
[CX-A-Pos1/0/0] quit
# Configure CX-B.
[CX-B] isis 1
[CX-B-isis-1] is-level level-1
[CX-B-isis-1] network-entity 10.0000.0000.0002.00
[CX-B-isis-1] ipv6 enable
[CX-B-isis-1] quit
[CX-B] interface pos 1/0/0
[CX-B-Pos1/0/0] isis ipv6 enable 1
[CX-B-Pos1/0/0] quit
# Configure CX-C.
-358-
[CX-C] isis 1
[CX-C-isis-1] network-entity 10.0000.0000.0003.00
[CX-C-isis-1] ipv6 enable
[CX-C-isis-1] quit
[CX-C] interface pos 1/0/0
[CX-C-Pos1/0/0] isis ipv6 enable 1
[CX-C-Pos1/0/0] quit
[CX-C-Pos3/0/0] isis circuit-level level-2
# Configure CX-D.
[CX-D] isis 1
[CX-D-isis-1] is-level level-2
[CX-D-isis-1] network-entity 20.0000.0000.0004.00
[CX-D-isis-1] ipv6 enable
[CX-D-isis-1] quit
[CX-D] interface pos 1/0/0
[CX-D-Pos1/0/0] isis ipv6 enable 1
[CX-D-Pos1/0/0] quit
[CX-D] interface gigabitethernet 2/0/0
[CX-D-GigabitEthernet2/0/0] isis ipv6 enable 1
[CX-D-GigabitEthernet2/0/0] quit
16.5.2 BGP for IPv6

Networking Requirement
As shown in below, there are two ASs: 65008 and 65009. CX-A belongs to AS 65008; CX-B, CX-C, and
CX-D belong to AS65009. BGP4+ is required to exchange the routing information between the two ASs.
-359-
Figure: Networking diagram of configuring basic BGP4+ functions
1. Configure the IBGP connections among CX-B, CX-C, and CX-D.
2. Configure the EBGP connection between CX-A and CX-B.
Data Preparation
 The router ID of CX-A is 1.1.1.1. Its AS number is 65008.
 The router IDs of CX-B, CX-C, and CX-D are 2.2.2.2, 3.3.3.3, and 4.4.4.4 respectively. Their AS
number is 65009.
Procedure
1. Configure the IBGP.
# Configure CX-B.
[CX-B] ipv6
[CX-B] bgp 65009
[CX-B-bgp] router-id 2.2.2.2
[CX-B-bgp] peer 9:1::2 as-number 65009
[CX-B-bgp] peer 9:3::2 as-number 65009
[CX-B-bgp] ipv6-family unicast
[CX-B-bgp-af-ipv6] peer 9:1::2 enable
[CX-B-bgp-af-ipv6] peer 9:3::2 enable
[CX-B-bgp-af-ipv6] network 9:1:: 64
[CX-B-bgp-af-ipv6] network 9:3:: 64
-360-
# Configure CX-C.
[CX-C] ipv6
[CX-C] bgp 65009
[CX-C-bgp] router-id 3.3.3.3
[CX-C-bgp] peer 9:3::1 as-number 65009
[CX-C-bgp] peer 9:2::2 as-number 65009
[CX-C-bgp] ipv6-family unicast
[CX-C-bgp-af-ipv6] peer 9:3::1 enable
[CX-C-bgp-af-ipv6] peer 9:2::2 enable
[CX-C-bgp-af-ipv6] network 9:3:: 64
[CX-C-bgp-af-ipv6] network 9:2:: 64
# Configure CX-D.
[CX-D] ipv6
[CX-D] bgp 65009
[CX-D-bgp] router-id 4.4.4.4
[CX-D-bgp] peer 9:1::1 as-number 65009
[CX-D-bgp] peer 9:2::1 as-number 65009
[CX-D-bgp] ipv6-family unicast
[CX-D-bgp-af-ipv6] peer 9:1::1 enable
[CX-D-bgp-af-ipv6] peer 9:2::1 enable
[CX-D-bgp-af-ipv6] network 9:2:: 64
[CX-D-bgp-af-ipv6] network 9:1:: 64
2. Configure the EBGP.
# Configure CX-A.
[CX-A] ipv6
[CX-A] bgp 65008
[CX-A-bgp] router-id 1.1.1.1
[CX-A-bgp] peer 10::1 as-number 65009
[CX-A-bgp] ipv6-family unicast
[CX-A-bgp-af-ipv6] peer 10::1 enable
[CX-A-bgp-af-ipv6] network 10:: 64
[CX-A-bgp-af-ipv6] network 8:: 64
# Configure CX-B.
[CX-B] bgp 65009

[CX-B-bgp] peer 10::2 as-number 65008
[CX-B-bgp] ipv6-family unicast
[CX-B-bgp-af-ipv6] peer 10::2 enable
-361-
[CX-B-bgp-af-ipv6] network 10:: 64
# Check the connection status of BGP4+ peers.
[CX-B] display bgp ipv6 peer

BGP local router ID : 2.2.2.2
Local AS number : 65009
Total number of peers : 3 Peers in established state : 3
Peer V AS MsgRcvd MsgSent OutQ Up/Down State PrefRcv
9:1::2 4 65009 8 9 0 00:05:37 Established 2
9:3::2 4 65009 2 2 0 00:00:09 Established 2
10::2 4 65008 9 7 0 00:05:38 Established 2

As shown in blew Figure, two IPv6 networks are connected to CX-B in the IPv4 backbone network
respectively through CX-A and CX-C. To enable communication between two IPv6 networks,
configure an IPv6 over IPv4 manual tunnel between CX-A and CX-C.
Figure 1 Networking diagram of the IPv6 over IPv4 manual tunnel
The configuration roadmap of IPv6 over IPv4 manual tunnel is as follows:
1. Configure IP addresses for physical interfaces.
2. Configure IPv6 addresses, the source interface, and the destination addresses for the tunnel
interfaces.
3. Set the tunnel protocol as IPv6-IPv4.
Data Preparation
-362-
 IP addresses of interfaces
 IPv6 addresses, the source interfaces and the destination addresses of the tunnel interfaces
Procedure
1. Configure CX-A.
# Configure an IP address for the interface.
[HUAWEI] sysname CX-A
[CX-A] ipv6 //Enable IPV6 function
[CX-A] interface gigabitethernet 1/0/0
[CX-A-GigabitEthernet1/0/0] ip address 192.168.50.2 255.255.255.0
[CX-A-GigabitEthernet1/0/0] undo shutdown
[CX-A-GigabitEthernet1/0/0] quit
# Set the tunnel protocol as IPv6-IPv4.
[CX-A] interface tunnel 1/0/0

[CX-A-Tunnel1/0/0] tunnel-protocol ipv6-ipv4
# Configure the IPv6 address, source interface, and destination address for the tunnel interface.
[CX-A-Tunnel1/0/0] ipv6 enable

[CX-A-Tunnel1/0/0] ipv6 address 3001::1/64
[CX-A-Tunnel1/0/0] source 192.168.50.2
[CX-A-Tunnel1/0/0] destination 192.168.51.2
[CX-A-Tunnel1/0/0] quit
# Configure static routes.
[CX-A] ip route-static 192.168.51.2 255.255.255.0 192.168.50.1
2. Configure CX-B.
[HUAWEI] sysname CX-B
[CX-B] interface gigabitethernet 1/0/0
[CX-B-GigabitEthernet1/0/0] ip address 192.168.50.1 255.255.255.0
[CX-B-GigabitEthernet1/0/0] undo shutdown
[CX-B-GigabitEthernet1/0/0] quit
[CX-B] interface gigabitethernet 2/0/0
-363-
[CX-B-GigabitEthernet2/0/0] ip address 192.168.51.1 255.255.255.0

[CX-B-GigabitEthernet2/0/0] undo shutdown
[CX-B-GigabitEthernet2/0/0] quit
3. Configure CX-C.
[HUAWEI] sysname CX-C
[CX-C] ipv6
[CX-C] interface gigabitethernet 1/0/0
[CX-C-GigabitEthernet1/0/0] ip address 192.168.51.2 255.255.255.0
[CX-C-GigabitEthernet1/0/0] undo shutdown
[CX-C-GigabitEthernet1/0/0] quit
# Set the tunnel protocol as IPv6-IPv4.
[CX-C] interface tunnel 1/0/0

[CX-C-Tunnel1/0/0] tunnel-protocol ipv6-ipv4
# Configure the IPv6 address, source interface, and destination address for the tunnel interface.
[CX-C-Tunnel1/0/0] ipv6 enable

[CX-C-Tunnel1/0/0] ipv6 address 3001::2/64
[CX-C-Tunnel1/0/0] source 192.168.51.2
[CX-C-Tunnel1/0/0] destination 192.168.50.2
[CX-C-Tunnel1/0/0] quit
# Configure a static route.
[CX-C] ip route-static 192.168.50.2 255.255.255.0 192.168.51.1

As shown in Below Figure, two IPv4 networks are connected to an IPv6 network through CX-1 and
CX-5, respectively. Border devices CX-2 and CX-4 of the IPv6 network support IPv4 and IPv6 dual
stacks. To enable communications between the two IPv4 networks, configure an IPv4 over IPv6
tunnel between CX-2 and CX-4.
Figure: Networking diagram of an IPv4 over IPv6 tunnel
-364-
1. Configure an IPv4 over IPv6 tunnel on the border devices at both ends of the IPv6 network.
2. Use a dynamic routing protocol to configure the route with the outgoing interface as the tunnel
interface.
Data Preparation
 Routing protocols applied to the IPv6 and IPv4 networks
 Source and destination IPv6 addresses of the tunnel
 IPv4 address of the tunnel interface
Procedure
1. Configure the IPv6 address of the physical interface and IS-ISv6 of the IPv6 network to
implement the connectivity of the IPv6 network.
# Configure CX-2.
[HUAWEI] sysname CX-2
[CX-2] ipv6
[CX-2] interface pos 2/0/0
[CX-2-Pos2/0/0] ipv6 enable
[CX-2-Pos2/0/0] ipv6 address 2001::1 64
[CX-2-Pos2/0/0] undo shutdown
-365-
[CX-2-Pos2/0/0] quit
[CX-2] isis 1
[CX-2-isis-1] network-entity 10.0000.0000.0001.00
[CX-2-isis-1] ipv6 enable topology standard
[CX-2-isis-1] quit
[CX-2-Pos2/0/0] isis ipv6 enable 1
# Create a loopback interface, assign an IPv6 address to it, and enable IS-ISv6.
[CX-2] interface Loopback 1

[CX-2-LoopBack1] ipv6 enable
[CX-2-LoopBack1] ipv6 address 2::2 64
[CX-2-LoopBack1] isis ipv6 enable 1
[CX-2-LoopBack1] quit
# Configure CX-3.
[CX-3] ipv6
[CX-3] isis 1
[CX-3-isis-1] quit
# Configure CX-4.
-366-
[CX-4] ipv6
[CX-4] isis 1
[CX-4-isis-1] quit
# Create a loopback interface, assign an IPv6 address to it, and enable IS-ISv6.

[CX-4-LoopBack1] ipv6 enable
[CX-4-LoopBack1] ipv6 address 4::4 64
[CX-4-LoopBack1] isis ipv6 enable 1
2. Configure the IPv4 address and OSPF of the physical interfaces for the IPv4 networks to
implement the connectivity of the IPv4 networks.
# Configure CX-1.
[CX-1-Pos1/0/0] ip address 10.1.2.2 30
[CX-1] ospf 1
[CX-1-ospf-1] area 0
[CX-1-ospf-1-area-0.0.0.0] network 10.1.2.0 0.0.0.3
# Configure CX-2.
<CX-2> system-view
-367-
[CX-2-Pos1/0/0] ip address 10.1.2.1 30

[CX-2] ospf 1
# Configure CX-4.
<CX-4> system-view
[CX-4-Pos1/0/0] ip address 10.1.3.1 30
[CX-4] ospf 1
# Configure CX-5.
[CX-5-Pos1/0/0] ip address 10.1.3.2 30
[CX-5] ospf 1
3. Configure the tunnel interface.
# Create a tunnel interface and configure the IPv4 address, source IPv6 address (or source interface),
and destination IPv6 address of the tunnel interface. Bind the SPUC to the tunnel.
# Configure CX-2.
<CX-2> set board-type slot 6 tunnel

<CX-2> system-view
[CX-2-LoopBack1] target-board 6
[CX-2-LoopBack1] binding tunnel ipv4-ipv6
[CX-2] interface tunnel 6/0/0
[CX-2-Tunnel6/0/0] tunnel-protocol ipv4-ipv6
[CX-2-Tunnel6/0/0] ip address 10.1.1.1 30
-368-
[CX-2-Tunnel6/0/0] source loopback1

[CX-2-Tunnel6/0/0] destination 4::4
# Configure CX-4.
<CX-4> set board-type slot 6 tunnel

<CX-4> system-view
[CX-4-LoopBack1] target-board 6
[CX-4-LoopBack1] binding tunnel ipv4-ipv6
[CX-4] interface tunnel 6/0/0
[CX-4-Tunnel6/0/0] tunnel-protocol ipv4-ipv6
[CX-4-Tunnel6/0/0] ip address 10.1.1.2 30
[CX-4-Tunnel6/0/0] source loopback1
[CX-4-Tunnel6/0/0] destination 2::2
4. Configure the route with the outgoing interface as the tunnel interface.
# Configure CX-2.
<CX-2> system-view
[CX-2] ospf 1
[CX-2-ospf-1-area-0.0.0.0] quit
[CX-2-ospf-1] quit
# Configure CX-4.
<CX-4> system-view
[CX-4] ospf 1
16.5.5 DS-Lite
DS-Lite uses IPv4 in IPv6 tunneling and IPv4 NAT techniques to help IPv4 private network users access IPv4 public
network resources across an IPv6 network. This example shows how to configure centralized DS-Lite.
Networking Requirements
As shown in below figure, hosts using IPv4 private network addresses are connected to an IPv6 MAN through a CPE that
supports IPv4/IPv6 dual stack and DS-Lite. A DS-Lite tunnel is established between the CPE and DS-Lite device. The CPE
encapsulates IPv4 data into IPv6 packets and sends the packets through the tunnel to the DS-Lite device. The DS-Lite device
-369-
decapsulates the IPv6 packets, translates IPv4 private addresses in the packets into IPv4 public addresses, and sends the IPv4
packets to the IPv4 Internet. The DS-Lite device has two DS-Lite service boards (one in slot 3 and one in slot 4). GE 2/0/0
on the DS-Lite device is connected to the IPv6 MAN and POS 1/0/0 is connected to the IPv4 Internet. The carrier has 10
public IPv4 addresses ranging from 202.38.160.100 to 202.38.160.110.
The following requirements must be met after the configuration:
 PCs on the IPv4 private network can access the IPv4 Internet across the IPv6 MAN.
 IPv4 private network addresses and IPv4 public network addresses can be translated into each other.
Figure 1 Networking diagram for applying DS-Lite
1. Configure user access.
2. Configure a DS-Lite instance and associate DS-Lite service boards with the DS-Lite instance.
3. Configure a DS-Lite tunnel.
4. Configure a DS-Lite address pool.
5. Configure a traffic policy for the DS-Lite tunnel.
6. Bind the DS-Lite tunnel to the address pool.
7. Configure interfaces and a routing protocol.
8. Advertise routes destined for the local IP address and address pool.
Data Preparation
To complete the configuration, you need the following data.
-370-
 DS-Lite instance name
 Slot ID of a service board associated with a DS-Lite instance
 Local and remote IP addresses of a DS-Lite tunnel
 Information about an address pool used by DS-Lite, including the address pool number and the start
and end IP addresses
 Number of an ACL6 rule for filtering DS-Lite traffic
 Number of an ACL6 rule bound to the address pool for DS-Lite
Procedure
1. Configure a DS-Lite instance and associate DS-Lite service boards with the DS-Lite instance.
# A DS-Lite instance can be associated with two DS-Lite service boards (one master and one
slave). If the master board fails, services are switched to the slave board.
 For the VSUI-20 service board:
[HUAWEI] DS-Lite instance cpe1
[HUAWEI-ds-lite-instance-cpe1] add slot 3 master
[HUAWEI-ds-lite-instance-cpe1] add slot 4 slave
[HUAWEI-ds-lite-instance-cpe1] quit
 For the VSUF-80/160 service board:
HUAWEI> system-view
[HUAWEI] service-location 1
[HUAWEI-service-location-1] location slot 3 engine 0 backup slot 4 engine 0
[HUAWEI-service-location-1] quit
[HUAWEI] service-instance-group 1
[HUAWEI-instance-group-1] service-location 1
[HUAWEI-instance-group-1] quit
[HUAWEI] ds-lite instance cpe1 id 1
[HUAWEI-ds-lite-instance-cpe1] service-instance-group 1
2. Configure the local and remote IPv6 addresses for a DS-Lite tunnel.
[HUAWEI] ds-lite instance cpe1

[HUAWEI-ds-lite-instance-cpe1] local-ipv6 2010::1 prefix-length 128
[HUAWEI-ds-lite-instance-cpe1] remote-ipv6 2::2 prefix-length 64

-371-
[HUAWEI-ds-lite-instance-cpe1] local-ipv6 2010::1 prefix-length 128

[HUAWEI-ds-lite-instance-cpe1] remote-ipv6 2::2 prefix-length 64
3. Configure a DS-Lite address pool. The address pool contains addresses ranging from 202.38.160.100 to
202.38.160.110.

[HUAWEI-ds-lite-instance-cpe1] ds-lite address-group group1 202.38.160.100
202.38.160.110

[HUAWEI-ds-lite-instance-cpe1] ds-lite address-group group1 group-id 1 202.38.160.100
202.38.160.110
4. Configure a traffic policy for the DS-Lite tunnel.
 Configure an ACL6 rule for traffic classification.
[HUAWEI] acl ipv6 2999

[HUAWEI-acl6-basic-2999] rule permit source 2::2 64
[HUAWEI-acl6-basic-2999] quit
 Configure a traffic classifier.
[HUAWEI] traffic classifier c1

[HUAWEI-classifier-c1] if-match ipv6 acl 2999
[HUAWEI-classifier-c1] quit
 Configure the traffic behavior to bind traffic actions to DS-Lite instance cpe1.
[HUAWEI] traffic behavior b1

[HUAWEI-behavior-b1] ds-lite bind instance cpe1
[HUAWEI-behavior-b1] quit
 Create a DS-Lite traffic policy to associate the ACL6 rule with the traffic behavior.
[HUAWEI] traffic policy p1

[HUAWEI-trafficpolicy-p1] classifier c1 behavior b1
[HUAWEI-trafficpolicy-p1] quit
 Apply this traffic policy to GE 2/0/0.

[HUAWEI-GigabitEthernet2/0/0] traffic-policy p1 inbound
[HUAWEI-GigabitEthernet2/0/0] quit
-372-
5. Bind the DS-Lite tunnel to the address pool.
 Configure an ACL6 rule and specify the source address of tunnel packets to be translated into
an address in the address pool group1 as 2::2/128.
[HUAWEI] acl ipv6 3000

[HUAWEI-acl6-adv-3000] rule permit ipv6 source 2::2 128
[HUAWEI-acl6-adv-3000] quit
 Associate the ACL6 rule with the DS-Lite address pool. In this example, ACL6 3000 is bound
to an address pool named group1 in DS-Lite instance cpe1.

[HUAWEI-ds-lite-instance-cpe1] ds-lite outbound 3000 address-group group1

[HUAWEI-ds-lite-instance-cpe1] ds-lite outbound 3000 address-group group1
6. Configure interfaces and a routing protocol.
 Configure Intermediate System to Intermediate System (IS-IS).
[HUAWEI] isis 100

[HUAWEI-isis-100] network-entity 10.1000.1000.1000.00
[HUAWEI-isis-100] quit
[HUAWEI] isis 1000
[HUAWEI-isis-1000] network-entity 10.1000.1000.1002.00
[HUAWEI-isis-1000] ipv6 enable
 Configure the interface connecting the DS-Lite device to the IPv6 MAN.
[HUAWEI] interface gigabitethernet2/0/0

[HUAWEI--GigabitEthernet2/0/0] ipv6 enable
[HUAWEI--GigabitEthernet2/0/0] ipv6 address 5010::1 64
[HUAWEI--GigabitEthernet2/0/0] isis ipv6 enable 1000
[HUAWEI--GigabitEthernet2/0/0] quit
p. Configure the interface connecting the DS-Lite device to the IPv4 Internet.
[HUAWEI] interface pos1/0/0
[HUAWEI-Pos1/0/0] ip address 52.1.1.1 24
[HUAWEI-Pos1/0/0] isis enable 100
[HUAWEI-Pos1/0/0] quit
-373-
7. Advertise the route destined for the local IP address to the IPv6 MAN and the route destined for the address pool to the
IPv4 Internet. First, import routes destined for the local IP address and address pool to IS-IS. In this product version,
routes destined for the local IP address and address pool are UNR routes.
[HUAWEI] isis 1000

[HUAWEI-isis-1000] ipv6 import-route unr
[HUAWEI] isis 100
[HUAWEI-isis-100] import-route unr
16.6 Upcoming IPv6 related features and how to update each

proposed devices
16.6.1 NE40E/CX600
The following lists the feature will be support in V600R007C00(13Q3) for NE40E and CX600.
 NAT 64
 PCP
 IPv6 DAA
 IPv6 Hot-Backup
 IPv6 DHCP PD relay
 IPv6 CP-CAR
 IPv6 Black/White List
Update Software can support the feature above
16.6.2 ATN
ATN V200R002 will be deployed in ET network. The IPv6 is support in this version. The feature list
please check chapter 16.2.
There is no upcoming IPv6 feature for ATN950B.
-374-
17 Future Multicast
17.1 Multicast Service Overview

Similar to the deployment of a unicast routing protocol, deploying a multicast routing protocol aims
to build a forwarding tunnel for multicast data. The multicast technology provides efficient P2MP
or multipoint-to-multipoint data transmission on networks, saving a large amount of bandwidth
resources and reducing network burden. IP multicast is widely used in such fields as multimedia
conferences, data copy, online games, and video services. On the Ethiopia IP Backhaul network, for
self-operated personal services, PIM-SSM is deployed on the public network; for non-self-operated
personal services, MVPN is deployed.
17.2 Supported Multicast related RFCs and usage in each proposed

device
The following table lists the references of this document.
 RFC 1112 Host Extensions for IP Multicasting
 RFC 2236 Internet Group Management Protocol, Version 2
 RFC 3376 Internet Group Management Protocol, Version 3
 RFC 3810 Multicast Listener Discovery Version 2 (MLDv2) for IPv6
 RFC 4601 Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification
(Revised)
 RFC 3618 Multicast Source Discovery Protocol (MSDP)
 RFC 3973 Protocol Independent Multicast - Dense Mode (PIM-DM)
17.3 Multicast Routing Protocols

Multicast protocols are classified into two types: group membership protocol running between a
host and a router and multicast routing protocol running between routers. IGMP is a group
-375-
membership protocol and multicast routing protocols contain intra-domain multicast routing
protocols and inter-domain multicast routing protocols. Inter-domain multicast routing protocols
include PIM-DM and PIM-SM, and PIM-SM includes ASM and SSM. Generally, PIM-SM
indicates the ASM model.
IGMP
IGMP runs on a host and its connected multicast router. By using IGMP, the host notifies the
connected router that it wants to join a specific multicast group and receives all multicast data for
this group. By using IGMP, the router periodically queries whether there are active members in a
specific multicast group on the LAN and maintains multicast group memberships for all connected
networks.
IGMP has three versions: IGMPv1 defined in RFC 1112, IGMPv2 defined in RFC 2236, and
IGMPv3 defined in RFC 4604. IGMPv1 defines basic group member query and report processes;
compared with IGMPv1, IGMPv2 supports prompt leave for multicast group members; IGMPv3
supports a function of enabling the members to receive or reject the packets sent from specified
multicast sources. In ET IPRAN, Huawei will deploy IGMPv2 for FL IPTV service.
 PIM-DM
PIM-DM is mainly used on a multicast LAN or a campus network but Ethiopia IP Backhaul is a
carrier's network. Therefore, PIM-DM is not described in details here.
 PIM-SM
PIM-SM is a multicast routing protocol applied on a large-scaled network although it may use the
underlying unicast routing to provide reverse-path information for multicast tree building. It does
not depend on any particular unicast routing protocol.
The process of building a PIM-SM forwarding path is also called the process of building a
multicast tree, namely a shared tree and a source tree. PIM-SM uses an RP as the root of a shared
tree. Each group has an RP and all sources need to send multicast data to RPs and all the routers
connected with receivers need to send group information towards the RPs. The group information is
sent to the RP along other PIM routers hop by hop by searching the unicast routing table. In this
manner, a shared tree is established finally and multicast data can be sent from a source to a
receiver along the shared tree. If the volume of multicast traffic reaches a threshold, source tree
building is triggered. Different from a shared tree, a source tree is established from a receiver router
towards a source but not an RP. In the aspect of unicast routing, each source tree equals a shortest
-376-
path tree. After a source tree is established, traffic needs to be switched from a shared tree to the
source tree to implement short path forwarding and save network bandwidth.
In ET IPRAN, Huawei will use PIM-SM protocal for FL IPTV service.
17.4 Multicast Deployment

 Multicast Deployment Hierarchies
Multicast deployment involves multicast source deployment, Layer 3 multicast deployment, and
Layer 2 multicast deployment.
Multicast source deployment should consider fault tolerance, disaster recovery, and reliability
designs.
Layer 3 multicast is deployed on ASs and RSGs. On the Ethiopia IP Backhaul network, for
self-operated personal services, public network multicast is required; for non-self-operated personal
services such as wholesale services, MVPN is deployed. In MVPN deployment, whether SSM or
ASM is deployment on the public network should be taken into consideration; SSM is deployed in
VPNs. If SSM is also deployed on the public network, Anycast RP needs to be deployed.
To accelerate multicast processing, statically pushing the popular channels or all channels on RSGs
to MSAGs is recommended and configuring multicast service traffic to be known multicast traffic
on MSAGs is required.
Layer 2 multicast is deployed on MSAGs or a lower-layer device. PIM-SM is not needed. Because
a family may have many STBs, Level-1 IGMP proxy needs to be deployed on RGWs and IGMP
snooping needs to be deployed on ONTs. Multicast data for many families is then converged on
MSAGs, which requires that Level-2 IGMP proxy be configured on MSAGs.
 Configuring RSGs as Multicast Replication Points
If the networks attached to RSGs do not support multicast replication or the performance of
MSAGs cannot meet the requirement of large-amount multicast data replication, multicast
replication can be configured on RSGs. This deployment scheme requires the VLAN QinQ
technology, with the outer tags representing MSAGs and inner tags representing users. If RSGs
have a large number of attached users, the replication workload is heavy. In such a case, if the
VLAN dot1q technology is deployed on the ET network, users cannot be differentiated. Therefore,
this deployment scheme is not recommended.
-377-
 Configuring MSAGs as Multicast Replication Points
If MSAGs have the multicast replication capability, VLAN-based multicast replication can be
deployed. User VLANs and multicast VLANs cannot be the same. IGMP proxy is required for
VLAN-based multicast replication. This deployment scheme requires that the upstream devices of
MSAGs send only copy of multicast data downstream, which saves network bandwidth.
 Configuring RGWs as Multicast Replication Points
If a family has multiple STBs, RGWs can be configured as multicast replication points to prevent
the multicast traffic from using additional bandwidth and protect other services for the family.
In conclusion, configuring MSAG as multicast replication points is recommended. If there are

multiple STBs in a family, RGWs can be configured as multicast replication points.
 Multicast Source Deployment
Multicast source deployment should be of reliability and support disaster recovery. When
deploying multiple multicast sources, how to implement multicast source synchronization and
consistent multicast data transmission delay should be taken into consideration. If multicast sources
are not synchronized or the delay is inconsistent, the program switches or the program fluency is
interrupted.
Multicast sources connect with SPEs and therefore IGMP and PIM-SM need to be enabled on the
interfaces connecting SPEs to multicast sources. The interfaces can be main interfaces or
sub-interfaces. The IP addresses of the interfaces are recommended to be on the same network
segment with those of the multicast sources.
 Layer 3 Multicast Deployment
1. Multicast deployment for self-operated services
For self-operated services on the MAXIS network, PIM-SSM is recommended to be deployed on

the public network. The deployment methods on SPEs and RSGs are the same: Enable PIM-SM on
the interfaces connecting SPEs and RSGs and apply SSM group policies on SPEs and RSGs.
On the interfaces connecting RSGs to MSAGs, create sub-interfaces for multicast services and add
the interfaces to multicast groups statically to import multicast traffic (for example traffic for
popular programs or all multicast traffic) to MSAGs.
Configure PIM-SSM on SPEs and RSGs.
2. MVPN Deployment
-378-
IPTV MVPN deployment
Figure 17- 1 IPTV MVPN deployment

Multicast VPN Access Point
DHCP
RP Server
IGMP IGMP IGMP DHCP
Proxy Snooping Proxy Relay
TV MSDP
STB SPE-2
TV RGW ONT Splitter RP
STB OLT PE-AGG SPE BTV Headend
SPE-1
L2 Multicast Multicast VPN PIM
In multicast VPN domain,
 Create MDs, share-groups and switch-group pools on the MVPN PE routers.
 Enable PIM-SM for the public multicast domain.
 Configure SPE-1 and SPE-2 as RPs. Run MSDP between two RPs for backup of the SPE's
interfaces connected to the Maxis BTV headend.
 Enable MVPN and PIM on the interface connecting the SPE to the headend to allow the interface
to receive multicast traffic from the headend.
 Anycast source is recommended for headend redundancy.
RSGs' interfaces to MSAGs:
 Create sub-interfaces for the multicast VLAN (single Q) on RSGs, and configure the RSGs to
terminate BTV services that access the MVPN.
 Enable IGMP, SSM-mapping, PIM, VRRP, and DHCP relay on sub-interfaces.
MSAGs and ONTs:
 Enable IGMP snooping on ONTs.
 Enable IGMP proxy and static IGMP join on MSAGs.
 Configure MSAGs to add a multicast VLAN tag (single Q) that identifies different service
providers, such as Maxis.
RGWs:
 Configure RGWs to allocate local LAN IP addresses to STBs through DHCP.
-379-
 Configure RGWs to obtain one WAN IP address for the BTV service from Maxis DHCP server
through DHCP.
 Enable IGMP proxy for the BTV service on RGWs. IGMP packets are sent to BTV service WAN
interfaces, and are tagged with unique VLAN IDs.
The following figure shows IPTV multicast service deployment, including DHCP signaling flows
and multicast data flows.
IPTV multicast service
Figure 17- 2 IPTV multicast service

Multicast VPN Access Point
DHCP Flow
Multicast Flow
DHCP
RP Server
TV SPE-2
STB
TV RGW ONT Splitter RP
STB OLT PE-AGG SPE BTV Headend
SPE-1
L2 Multicast Multicast VPN PIM
The RGW sends a request for setting up a DHCP connection with the DHCP server and applying
for an IP address. The PE-AGG functions as a Layer 3 gateway. DHCP signaling flows are
transmitted on the same VLAN and VPN with multicast flows.
 The RGW adds multicast VLAN IDs to DHCP packets.
 The ONT and MSAG transparently transmit the DHCP packets to the PE-AGG.
 The PE-AGG relays the DHCP packets to the DHCP server. At the aggregation layer, the DHCP
packets are transmitted on the Layer 3 VPN (MVPN).
The process of implementing the communication between PIM C-instances on the PEs through
MVPN is as follows:
 Establish a virtual MT between PIM C-instances.
 Each PIM C-instance creates an MTI to connect to the MT.
 Each VPN instance joins the corresponding MT based on the configured Share-Groups.
-380-
In this manner, the PIM C-instances configured with the same Share-Group address form an MD.
An MD is a set of VPN instances that can send and receive multicast packets on PEs.
PIM C-instances on a PE use the interface of an MT as a LAN interface to set up PIM neighbor
relationships with the remote PIM C-instances, perform DR election, send Join/Prune message, and
forward and receive multicast data.
After receiving PIM protocol packets or multicast data packets from PIM C-instances, the interface
of the MT encapsulates the packets. The packets are public multicast data packets after
encapsulation and are to be forwarded by the PIM P-instance on the public network. In conclusion,
an MT is actually a multicast distribution tree on the public network.
Different VPNs use different MTs and different MTs use different encapsulation modes. This
requires the isolated transmission of multicast data for different VPNs.
The PIM C-instances on the PEs in the same VPN use the same MT and communicate through this
MT.
Either PIM-SM or PIM-SSM can be configured on the VPNs and the public network. Section 17.3
has described the advantages of PIM-SSM. Therefore, PIM-SSM is recommended.
Multicast Service Establishment Process
IPTV service establishment includes STBs' access to the broadband network (IP address
acquirement) and STBs' access to the IPTV system.
The general process of STBs' access to the IPTV system is described as follows:
 STBs use IPTV accounts to send access authentication requests to the IPTV system. The system
then starts to authenticate the accounts.
 After the authentication is finished, STBs exchange information with EPG servers to obtain user
authorization information (including products ordered by users) and EPG homepages and channel
lists.
The details on the process are not the emphases of this document and will not be provided.
The following figure shows the process of an STB's access to the broadband network.
The process of an STB's access to the broadband network
-381-
Figure 17- 3 The process of an STB's access to the broadband network
STB RGW ONT OLT PE-AGG SPE BRAS DHCP VOD BTV
Server Server Server
PPPoE WAN
PPPoE
WAN
DHCP WAN DHCP

WAN
DHCP DHCP Relay
PPPoE WAN VOD Request

Route and NAT
WAN
VOD
DHCP WAN
WAN
PPPoE WAN
WAN
BTV
DHCP WAN IGMP PIM
WAN
IGMP Proxy
 The two WAN interfaces on the RGW obtain network-side private IP addresses through PPPoE
and DHCP. The PPPoE WAN interface is used to transmit IPTV unicast services, whereas the DHCP
WAN interface is used to transmit IPTV multicast services.
 The STB accesses the RGW and sets up a DHCP connection with the RGW. The RGW functions
as the DHCP server inside the home network and allocates a local LAN private IP address to the
STB.
 The STB sends a unicast service request packet, such as a VoD request packet to the RGW. The
RGW routes the request packet to the PPPoE WAN interface. After the PPPoE WAN interface has
performed NAT on the packet, the ONT/MSAG/PE-AGG/SPE forwards the packet to the BRAS.
Then, the DPI/NAT device forwards the packet to the VoD server.
 The MSAG is configured with the static IGMP join function. All multicast program traffic is
pushed to the MSAG in advance. The multicast traffic is transmitted through the MVPN on the
aggregation layer.
 The STB sends an IGMP report message to obtain multicast programs.
 The RGW is enabled with IGMP proxy. The ONT performs IGMP snooping. The MSAG is
enabled with IGMP proxy. The requested multicast traffic is forwarded to the STB through the
MSAGs, ONT, and RGW in sequence.
Configuration Examples
Multicast Configuration refer to Service Implement IPTV and Multicast wholesale service
-382-
17.5 Multicast Deployment Example

17.5.1 Deployment Topology
ASG-1 RSG-1
CSG-1
Eth-Trunk5
Eth-Trunk5
ISIS Eth-Trunk10
Eth-Trunk6
Level2 Eth-Trunk5
Multicast MSAN Eth-Trunk25 Eth-Trunk5 Multicast
Client Server
CSG-2 ASG-2 RSG-2
IGMP Proxy/IGMP PIM SM
Figure 17- 4 Multicast deployment topology
17.5.2 IP Plan for Multicast Deployment Example

NE Interface IP Addr Peer NE Peer Port Peer IP Addr
RSG-1 Eth-Trunk10 10.1.23.1 RSG-2 Eth-Trunk10 10.1.23.2
RSG-1 Eth-Trunk15 10.1.23.5 ASG-1 Eth-Trunk15 10.1.23.6
RSG-2 Eth-Trunk15 10.1.23.9 ASG-2 Eth-Trunk15 10.1.23.10
ASG-1 Eth-Trunk10 10.1.23.13 ASG-2 Eth-Trunk10 10.1.23.14
ASG-1 Eth-Trunk25 10.1.23.17 CSG-1 Eth-Trunk25 10.1.23.18
ASG-2 Eth-Trunk25 10.1.23.21 CSG-2 Eth-Trunk25 10.1.23.22
CSG-1 Eth-Trunk10 10.1.23.25 CSG-2 Eth-Trunk10 10.1.23.26
RSG-1 Eth-Trunk5 10.1.24.1 Server Eth-Trunk5 10.1.31.254
RSG-2 Eth-Trunk5 10.1.24.2 Server Eth-Trunk5 10.1.31.255
CSG-1 Eth-Trunk5 10.1.25.1 MASN Eth-Trunk5 N/A
CSG-2 Eth-Trunk5 10.1.25.2 MASN Eth-Trunk5 N/A
17.5.3 Configuration Template for Multicast
RSG(RSG-1)：
multicast routing-enable
#
interface loopback1
ip address 10.0.5.9 255.255.255.255
isis enable 100
-383-
pim sm
#
pim
pimstatic-rp 10.0.5.9
#
isis 100
is-level level-2
cost-style wide
network-entity 88.0251.0100.0000.5009.00
set-overload on-startup 400
#
ip address 10.1.23.1 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.23.5 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.24.1 255.255.255.0
isis enable 100
pim sm
#
RSG(RSG-2)：
#
interface loopback1
ip address 10.0.5.10 255.255.255.255
isis enable 100
-384-
pim sm
#
pim
#
isis 100
is-level level-2
cost-style wide
network-entity 88.0251.0100.0000.5010.00
#
ip address 10.1.23.2 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.23.9 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.24.2 255.255.255.0
isis enable 100
pim sm
ASG(ASG-1)：
#
pim
-385-
#
isis 100
is-level level-2
cost-style wide
network-entity 88.0251.0100.0000.5011.00
#
ip address 10.1.23.13 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.23.6 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.23.17 255.255.255.252
isis enable 100
pim sm
#
ASG(ASG-2)：
#
pim
#
isis 100
is-level level-2
cost-style wide
-386-

network-entity 88.0251.0100.0000.5012.00
#
ip address 10.1.23.14 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.23.10 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.24.21 255.255.255.252
isis enable 100
pim sm
CSG(CSG-1)：
#
pim
#
isis 100
is-level level-2
cost-style wide
network-entity 88.0251.0100.0000.5013.00
#
-387-
ip address 10.1.23.25 255.255.255.252
isis enable 100
pim sm
#
ip address 10.1.25.1 255.255.255.0
isis enable 100
pim sm
IGMP enable
#
ip address 10.1.23.18 255.255.255.252
isis enable 100
pim sm
#
CSG(CSG-2)：
#
pim
#
isis 100
is-level level-2
cost-style wide
network-entity 88.0251.0100.0000.5014.00
#
ip address 10.1.23.26 255.255.255.252
isis enable 100
pim sm
-388-
#
ip address 10.1.25.2 255.255.255.0
isis enable 100
pim sm
IGMP enable
#
ip address 10.1.23.22 255.255.255.252
isis enable 100
pim sm
#
-389-
18 Physical Layout
18.1 Core Site NE40E Layout

18.1.1 NE40E-X8 in Arada
AD_T160G_Voice_A AD_T160G_Voice_B
AD_ER_NEW_A(NE40E-X8) AD_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 2 2 2 LAG-15 8 9 2 2 2
10 11 10 11
12 13
AD_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
20 21 SRU SPU SRU 20 21 SRU SPU SRU
22 23 AD_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 26 27 1 1 1
28 29 28 29
30 31 2 2 2 AD_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
36 37 36 37
4 4 4 AD_SW_CS_A 4 4 4
38 39 38 39
18.1.2 NE40E-X8 in Bole

BL_CR_A BL_CR_B
BL_ER_NEW_A(NE40E-X8) BL_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 2 2 2 LAG-15 8 9 2 2 2
10 11 10 11
12 13
BL_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
22 23 BL_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 26 27 1 1 1
LAG-30
28 29 28 29
30 31 2 2 2 BL_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
36 37 LAG-30 36 37
4 4 4 BL_SW_CS_A 4 4 4
38 39 38 39
18.1.3 NE40E-X8 in Kirkos

c
-390-
18.1.4 NE40E-X8 in Microwave

MW_CR_A 10GE (SFP+) GE(SFP) Fiber
MW_CR_B
gei-0/3/0/8,6,4,2,3,5,7.9 Cat7 Cable gei-0/3/0/8,6,4,2,3,5,7.9
MW_ER_NEW_A(NE40E-X8) MW_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 2 2 2 LAG-15 8 9 2 2 2
10 11 10 11
12 13
MW_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
22 23 MW_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 LAG-30 26 27 1 1 1
28 29 28 29
30 31 2 2 2 MW_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
LAG-30
36 37 36 37
4 4 4 MW_SW_CS_A 4 4 4
38 39 38 39
LAG-20 LAG-20
MW_FW_PS_A MW_FW_PS_B
LAG-25
LAG-25
MW_SW_PS_A
MW_SW_PS_B
18.1.5 NE40E-X8 in NifasSilk

NS_ER_DATA_A NS_ER_DATA_B
NS_ER_NEW_A(NE40E-X8) NS_ER_NEW_B(NE40E-X8)
LAG-10 LAG-10
1 2 3 4 9 11 10 5 6 7 8 1 2 3 4 9 11 10 5 6 7 8
0 1 0 1
2 3 0 0 0 2 3 0 0 0
4 5 4 5
1 1 1 1 1 1
6 7 6 7
8 9 LAG-15 8 9
2 2 2 2 2 2
10 11 10 11
12 13
NS_RSG_A 12 13
3 3 3 3 3 3
14 15 14 15
16 17 16 17
4 4 4 4 4 4
18 19 LAG-15 18 19
22 23 NS_RSG_B 22 23
0 0 0 0 0 0
24 25 24 25
26 27 1 1 1 LAG-30 26 27 1 1 1
28 29 28 29
30 31 2 2 2 NS_SW_CS_B 30 31 2 2 2
32 33 32 33
34 35 3 3 3 34 35 3 3 3
36 37 LAG-30 36 37
4 4 4 NS_SW_CS_A 4 4 4
38 39 38 39
LAG-20 LAG-20
NS_FW_PS_A NS_FW_PS_B
LAG-25
LAG-25
NS_SW_PS_A
NS_SW_PS_B
-391-
18.2 RSG Site CX600 Layout

18.2.1 CX600-X16 in Arada
CX600-X16 | Arada-RSG-A
GE 40GE 10GE 40GE

To Arada-RSG-B - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Sidis Kilo-ASG-B - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

To Ferensail-ASG-B - XGE 8/0/1
To Ferensail-ASG-B - XGE 8/0/0 10GE 10GE
0 1 0 1
To 70 - XGE 0/5/0
2 3 2 3
4 4
10GE 8 9 10 11 12 13 10GE14 15 16
0 1 0 1
2 3 2 3
C C
4 R 4 R
5 5
D D
0 0
L L
A A
X X
F F
A A
7 7
1 1
8 14
-392-
CX600-X16 | Arada-RSG-B
GE 40GE 10GE 40GE

To Arada-RSG-A - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Addis Ketema-ASG-A - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
To Addisu Gebeya-ASG-A - XGE 8/0/1 Lower cable trough

To Addisu Gebeya-ASG-A - XGE 8/0/0 10GE 10GE
To 74 - XGE 0/5/0
0 1 0 1
To 52N - XGE 0/6/0

2 3 2 3
To 010 - XGE 0/5/0

4 4
10GE 8 9 10 11 12 13 10GE14 15 16
0 1 0 1
2 3 2 3
C C
4 R 4 R
5 5
D D
0 0
L L
A A
X X
F F
A A
7 7
1 1
8 14
18.2.2 CX600-X16 in Bole
-393-
CX600-X16 | Bole-RSG-A
C C C C
R R R R
5 5 5 5
To Bole-RSG-B - 40GE 3/0/0 E1 3
-
E1 3
-
GE 40GE E1 3
-
E1 3
-
10GE 40GE
To Nifas Silk-RSG-B - 40GE 7/0/0
P P P P
1 1 1 1
1 0 1 0 2 0 5 0 5 0 0 1 0
- - - -
2 2 2 2
4 4 4 4
x x x x
c c c c 2 3
E E C E E
1 1 R 1 1
- / - / - 5 - / - /
c c D c c
T
1
T
1
0
E
C C T
1
T
1
4
-
D
-
D
F
G
X X -
D
-
D
B
1
B
1
C
R
F
A
C
R
6 6 B
1
B
1
C
R
2 0
0
0 0
0
5 0 7
0
5 D D 2 0
0
0 0
0
5
D D 0 0 D
1-2 C 1-0 C L 2-0 L 5-2 C 5-0 C L
R P
R P M M R P
R
To Bole-RSG-B - 40GE 3/2/0 E1

5
3 1E1 5
3
U
F 2
U
F 40GE 3 P
17 P
18 4 E1
5
3 5E1 5
3
U
F 10GE 6 40GE 7 To Nifas Silk-RSG-B - 40GE 7/2/0
-
P
-
P 5 5 U U -
P
-
P 5
1 1
0 1 1
0
0
7 2
1
7 0 B B 5 1
0 5 1
0
0
7 0 1 0
-
2
-
2 0 0 4 4 -
2
-
2 0
4
x
4
x
1 1 4
x
4
x
c
E
c
E
0 0 c
E
c
E
2 3
1 1 1 1
- / - / - - / - /
c c C c c C C
T T R T T 4 R R
1 1 5 1 1 5 5
- - D - - D D
D D 0 D D 0 0
B B 0 B B L 0
1 1 E 1 1 A E
3 0 1 0 1 2 3 0 1 0 X 2
0 0 M 0 0 F M
C A C
1-3 1-1 7 5-3 5-1 7 7
0 1 0
1 2 3 17 18 5 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

To 16N - XGE 0/5/0 C
R
C
R
C
R
C
R
5 5 5 5
To 130D - XGE 0/5/0 10GE 40GE E1 3
-
E1 3
-
10GE E1 3
-
E1 3
-
P P P P
0 1 0
1 1 1 1 0 1
1 1 1 1
0 0 0 0
1 - 1 - 5 - 5 -
2 2 2 2
4 4 4 4
x x x x
2 3 c c 2 3 c c
E E E E
1 1 1 1
/ / / /
- c - c - c - c
4 T T 4 T T
1 1 1 1
- - - -
D D D D
B B C B B C
1 1 R 1 1 R
2 0
0 0 5 2 0
0 0 5
0 0 0 0
D D
11-2 C 11-0 C L 15-2 C 15-0 C L
R R P R R P
5 5 U 5 5 U
To Yeka-ASG-A - 40GE 7/2/0 10GE 8 9 40GE10 E1 3
-
11E1 3
-
F 12 13 10GE 14 E1 3
-
15E1 3
-
F 16
P P 5 P P 5
0 1 0
1 1 1 1 0 0 1
1 1 1 1 0
1 0
1 0 7 5 0
5 0 7
- - 0 - - 0
2 2 2 2
4 4 4 4
x x x x
2 3 c c 2 3 c c
E E E E
1 1 1 1
/ / / /
C C - c - c C - c - c
4 R R T T 4 R T T
5 5 1 1 5 1 1
D D - - D - -
0 0 D D 0 D D
L 0 B B L B B
A E 1 1 A 1 1
X 2 0 0 X 0 0
F M 3 0 1 0 F 3 0 1 0
A C A
7 7 11-3 11-1 7 15-3 15-1
1 0 1
8 10 11 14 15
-394-
CX600-X16 | Bole-RSG-B
To Bole-RSG-A - 40GE 3/0/0 GE 40GE 10GE 40GE

To Filowoha-ASG-A - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
To Bole-RSG-A - 40GE 3/2/0 1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Filowoha-ASG-A - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

To 180D - XGE 0/5/0
To 70N - XGE 0/6/0 10GE 10GE
0 1 0 1
2 3 2 3
4 4
10GE 8 9 10 11 12 13 10GE14 15 16
0 1 0 1
2 3 2 3
C C
4 R 4 R
5 5
D D
0 0
L L
A A
X X
F F
A A
7 7
1 1
8 14
-395-
18.2.3 CX600-X16 in Kirkos

CX600-X16 | Kirkos-RSG-A
To Kirkos-RSG-B - 40GE 3/0/0 GE 40GE 10GE 40GE

To Old Airport-ASG-B - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
To Kirkos-RSG-B - 40GE 3/2/0 1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Old Airport-ASG-B - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

To 56N - XGE 0/5/0 10GE 10GE
0 1 0 1
2 3 2 3
4 4
10GE 8 9 10 11 12 13 10GE14 15 16
0 1 0 1
2 3 2 3
C C
4 R 4 R
5 5
D D
0 0
L L
A A
X X
F F
A A
7 7
1 1
8 14
-396-
CX600-X16 | Kirkos-RSG-B
To Kirkos-RSG-A - 40GE 3/0/0 GE 40GE 10GE 40GE

To Nifas Silk-RSG-A - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
To Kirkos-RSG-A - 40GE 3/2/0 1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Nifas Silk-RSG-A - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

To 49N - XGE 0/5/0 10GE 10GE
0 1 0 1
2 3 2 3
4 4
10GE 8 9 10 11 12 13 10GE14 15 16
0 1 0 1
2 3 2 3
C C
4 R 4 R
5 5
D D
0 0
L L
A A
X X
F F
A A
7 7
1 1
8 14
-397-
18.2.4 CX600-X16 in Microwave
-398-
CX600-X16 | Microwave-RSG-A
To Microwave-RSG-B - 40GE 3/0/0 GE 40GE 10GE 40GE

To Filowoha-ASG-B - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
To Microwave-RSG-B - 40GE 3/2/0 1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Filowoha-ASG-B - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

10GE 10GE
0 1 0 1
2 3 2 3
4 4
10GE 8 9 10 11 12 13 10GE14 15 16
0 1 0 1
2 3 2 3
C C
4 R 4 R
5 5
D D
0 0
L L
A A
X X
F F
A A
7 7
1 1
8 14
-399-
CX600-X16 | Microwave-RSG-B
To Microwave-RSG-A - 40GE 3/0/0 GE 40GE 10GE 40GE

To Old Airport-ASG-A - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
To Microwave-RSG-A - 40GE 3/2/0 1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Old Airport-ASG-A - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

10GE 40GE 10GE
0 1 0 0 1
2 3 2 3
4 4
To Addis Ketema-ASG-B - 40GE 7/2/0 10GE 8 9 40GE10 11 12 13 10GE14 15 16

0 1 0 0 1
2 3 2 3
C C C
4 R R 4 R
5 5 5
D D D
0 0 0
L 0 L
A E A
X 2 X
F M F
A C A
7 7 7
1 0 1
8 10 14
-400-
18.2.5 CX600-X16in NifasSilk

CX600-X16 | Nifas Silk-RSG-A
To Nifas Silk-RSG-B - 40GE 3/0/0 GE 40GE 10GE 40GE

To Kirkos-RSG-B - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
To Nifas Silk-RSG-B - 40GE 3/2/0 1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Kirkos-RSG-B - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

To Hanna Mariam-ASG-B - XGE 8/0/1
To Hanna Mariam-ASG-B - XGE 8/0/0 10GE 10GE
0 1 0 1
To 45N - XGE 0/5/0

2 3 2 3
4 4
10GE 8 9 10 11 12 13 10GE14 15 16
0 1 0 1
2 3 2 3
C C
4 R 4 R
5 5
D D
0 0
L L
A A
X X
F F
A A
7 7
1 1
8 14
-401-
CX600-X16 | Nifas Silk-RSG-B
To Nifas Silk-RSG-A - 40GE 3/0/0 GE 40GE 10GE 40GE

To Bole-RSG-A - 40GE 7/0/0
2 0 0 1 0
2 3
C
R
- 5
D
0
E
C C 4
F
G
X X
F
A
C
R
6 6
0 7
0
5 D D
D
L
0 0
2-0
P M M
To Nifas Silk-RSG-A - 40GE 3/2/0 1 2
U
F 40GE 3 P
17 P
18 4 5 10GE 6 40GE 7 To Bole-RSG-A - 40GE 7/2/0
5 U U
2
1
7 0 B B 0 1 0
0 4 4
1 1
0 0 2 3
-
C C C
R 4 R R
5 5 5
D D D
0 0 0
0 L 0
1 E A E
2 X 2
M F M
C A C
7 7 7
0 1 0
2 3 17 18 6 7
Upper cable trough
19 CX6DSFUI401B
19
20 CX6DSFUI401B
20
21 CX6DSFUI401B
21
22 CX6DSFUI401B
22
Lower cable trough

To Bole Micheal-ASG-A - XGE 8/0/0
To Bole Micheal-ASG-A - XGE 8/0/1 10GE 10GE
0 1 0 1
To 46N - XGE 0/6/0

2 3 2 3
4 4
10GE 8 9 10 11 12 13 10GE14 15 16
0 1 0 1
2 3 2 3
C C
4 R 4 R
5 5
D D
0 0
L L
A A
X X
F F
A A
7 7
1 1
8 14
-402-
18.3 ASG Site CX600 Layout

18.3.1 CX600-X8 in Addis Ketema
CX600-X8 | Addis Ketema-ASG-A
Air intake vent

To Shegole-ASG-B - XGE 8/0/1
To Shegole-ASG-B - XGE 8/0/0
C
R
E1
5
3 GE 40GE 10GE To Addis Ketema-ASG-B - 40GE 7/0/0
-
P
1
To 168 - XGE 0/5/0
1 0 1 2 0 0 1
-
2
To 03N - XGE 0/5/0
4
x
c 2 3
E C
1 R To 188D - XGE 0/5/0
- / - - 5
c D
T
1
0
E
C C C 4
-
D
F
G
X X X
B
1
C
R
C
R
F
A
6 6 6
2 0
0
0 5 05 7
0
D D D
D
L
D 0 S 0
1-2 2-0 L
P P S F S
1
U
F 2
U
F 3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Arada-RSG-B - 40GE 7/2/0
5 5 U I U
1 1
0
7 2 7
1 A 4 A 0 0 1
0 0 4 0 4
1 1 1
0 C 0 2 3
- - -
C C
R 4 R
5 5
D D
0 0
0 L
3 1 1 E A
2 X
M F
C A
7 7
0 1
1 2 9 11 10 7 8
Cable trough
CX600-X8 | Addis Ketema-ASG-B
Air intake vent

To Addis Ketema-ASG-A - 40GE 7/0/0
To Kolfe-ASG-A - XGE 8/0/1
GE 40GE 10GE To Kolfe-ASG-A - XGE 8/0/0
To 72N - XGE 0/5/0
2 0 0 1
To 002D - XGE 0/5/0

2 3
C
R To 004D - XGE 0/5/0
- 5
D
0
E
C C C 4
F
G
X X X
C
R
F
A
6 6 6
05 7
0
D D D
D 0 S 0
2-0 L
P S F S
1 2
U
F 3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Microwave-RSG-B - 40GE 10/2/0
5 U I U
2 7
1 A 4 A 0 0 1
0 4 0 4
1 1 1
0 C 0 2 3
-
C C
R 4 R
5 5
D D
0 0
0 L
1 E A
2 X
M F
C A
7 7
0 1
2 9 11 10 7 8
Cable trough
-403-
18.3.2 CX600-X8 in Addis SidisKilo

CX600-X8 | Sidis Kilo-ASG-A
Air intake vent
To 201 - XGE 0/5/0

GE 40GE 10GE
To 24N - XGE 0/5/0
2 0 0 1 To Sidis Kilo-ASG-B - 40GE 7/0/0
2 3
C
R
- 5
D
0
E
C C C 4
F
G
X X X
C
R
F
A
6 6 6
05 7
0
D D D
D 0 S 0
2-0 L
P S F S
1 2
U
F 3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Yeka-ASG-B - 40GE 7/2/0
5 U I U
2 7
1 A 4 A 0 0 1
0 4 0 4
1 1 1
0 C 0 2 3
-
C C
R 4 R
5 5
D D
0 0
0 L
1 E A
2 X
M F
C A
7 7
0 1
2 9 11 10 7 8
Cable trough
CX600-X8 | Sidis Kilo-ASG-B
Air intake vent

To 53N - XGE 0/6/0
GE 40GE 10GE To 012 - XGE 0/6/0
To 39N - XGE 0/5/0
2 0 0 1
To 83N - XGE 0/5/0

2 3 To Sidis Kilo-ASG-A - 40GE 7/0/0
C
R
- 5
D
0
E
C C C 4
F
G
X X X
C F 6 6 6
0 R5
A
7 D D D
0
D 0 S 0
2-0 L
P S F S
1 2
U
F 3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Arada-RSG-A - 40GE 7/2/0
5 U I U
2 7
1 A 4 A 0 0 1
0 4 0 4
1 1 1
0 C 0 2 3
-
C C
R 4 R
5 5
D D
0 0
0 L
1 E A
2 X
M F
C A
7 7
0 1
2 9 11 10 7 8
Cable trough
-404-
18.3.3 CX600-X8 in Yeka

CX600-X8 | Yeka-ASG-A
Air intake vent

To Gerji-ASG-B - XGE 8/0/1
To Gerji-ASG-B - XGE 8/0/0
C
R
E1
5
3 GE 40GE 10GE To Yeka-ASG-B - 40GE 7/0/0
-
P
1
To 310N - XGE 0/5/0
1 0 1 2 0 0 1
-
2
To 287E - XGE 0/5/0
4
x
c 2 3
E C
1 R To 285E - XGE 0/5/0
- / - - 5
c D
T
1
0
E
C C C 4
-
D
F
G
X X X
B
1
C
R
C
R
F
A
6 6 6
2 0
0
0 5 05 7
0
D D D
D
L
D 0 S 0
1-2 2-0 L
P P S F S
1
U
F 2
U
F 3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Bole-RSG-A - 40GE 10/2/0
5 5 U I U
1 1
0
7 2 7
1 A 4 A 0 0 1
0 0 4 0 4
1 1 1
0 C 0 2 3
- - -
C C
R 4 R
5 5
D D
0 0
0 L
3 1 1 E A
2 X
M F
C A
7 7
0 1
1 2 9 11 10 7 8
Cable trough
CX600-X8 | Yeka-ASG-B
Air intake vent

To Kotebe-ASG-A - XGE 8/0/1
GE 40GE 10GE To Kotebe-ASG-A - XGE 8/0/0
To 306N - XGE 0/6/0
2 0 0 1
To 292E - XGE 0/6/0

2 3 To Yeka-ASG-A - 40GE 7/0/0
C
R
- 5
D
0
E
C C C 4
F
G
X X X
C F 6 6 6
0 R5
A
7 D D D
0
D 0 S 0
2-0 L
P S F S
1 2
U
F 3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Sidis Kilo-ASG-A - 40GE 7/2/0
5 U I U
2 7
1 A 4 A 0 0 1
0 4 0 4
1 1 1
0 C 0 2 3
-
C C
R 4 R
5 5
D D
0 0
0 L
1 E A
2 X
M F
C A
7 7
0 1
2 9 11 10 7 8
Cable trough
-405-
18.3.4 CX600-X8 in Filowaha

CX600-X8 | Filowoha-ASG-A
Air intake vent

To 35D - XGE 0/5/0
C To 35N - XGE 0/5/0
R
5
To Filowoha-ASG-B - 40GE 3/0/0 E1
3
-
GE 40GE 40GE 40GE 10GE
To Bole-RSG-B - 40GE 7/0/0
P
1
1 0 1 2 0 0 0 0 1
-
2
To 45D - XGE 0/5/0
4
x
c 2 3
E C
1 R
- / - - 5
c D
T
1
0
E
C C C 4
-
D
F
G
X X X
B
1
C
R
C
R
F
A
6 6 6
2 0
0
0 5 05 7
0
D D D
D
L
D 0 S 0
1-2 2-0 L
P P S F S
To Filowoha-ASG-B - 40GE 3/2/0 1
U
F 2
U
F 40GE
3 40GE
4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Bole-RSG-B - 40GE 7/2/0
5 5 U I U
1 1
0
7 2 7
1 0 0 A 4 A 0 0 1
0 0 4 0 4
1 1 1
0 C 0 2 3
- - -
C C C C
R R R 4 R
5 5 5 5
D D D D
0 0 0 0
0 0 0 L
3 1 1 E E E A
2 2 2 X
M M M F
C C C A
7 7 7 7
0 0 0 1
1 2 3 4 9 11 10 7 8
Cable trough
CX600-X8 | Filowoha-ASG-B
Air intake vent

To 84N - XGE 0/6/0
To 22D - XGE 0/6/0
To Filowoha-ASG-A - 40GE 3/0/0 GE 40GE 40GE 10GE
To Microwave-RSG-A - 40GE 7/0/0
2 0 0 0 1
To 194D - XGE 0/6/0

2 3
C
R
- 5
D
0
E
C C C 4
F
G
X X X
C
R
F
A
6 6 6
5 0 7
0
D D D
D 0 S 0
2-0 L
P S F S
To Filowoha-ASG-A - 40GE 3/2/0 1 2
U
F 40GE
3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Microwave-RSG-A - 40GE 7/2/0
5 U I U
2 7
1 0 A 4 A 0 0 1
0 4 0 4
1 1 1
0 C 0 2 3
-
C C C
R R 4 R
5 5 5
D D D
0 0 0
0 0 L
1 E E A
2 2 X
M M F
C C A
7 7 7
0 0 1
2 3 9 11 10 7 8
Cable trough
-406-
18.3.5 CX600-X8 in OldAirport

CX600-X8 | Old Airport-ASG-A
Air intake vent

To Karanyo-ASG-B - XGE 8/0/1
C To Karanyo-ASG-B - XGE 8/0/0
R
5
To Old Airport-ASG-B - 40GE 3/0/0 E1
3
-
GE 40GE 40GE 10GE
To Microwave-RSG-B - 40GE 7/0/0
P
1
1 0 1 2 0 0 0 1
-
2
To 61N - XGE 0/5/0
4
x
c 2 3 To 38N - XGE 0/5/0
E C
1 R
- / - - 5
c D
T
1
0
E
C C C 4
-
D
F
G
X X X
B
1
C
R
F
A
C
R
6 6 6
2 0
0
0 5 0 7
0
5 D D D
D
L
D
L
0 S 0
1-2 2-0
P P S F S
To Old Airport-ASG-B - 40GE 3/2/0 1
U
F 2
U
F 40GE
3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Microwave-RSG-B - 40GE 7/2/0
5 5 U I U
1 1
0
7 2
1
7
0 A 4 A 0 0 1
0 0 4 0 4
1 1 1
0 C 0 2 3
- - -
C C C
R R 4 R
5 5 5
D D D
0 0 0
0 0 L
3 1 1 E E A
2 2 X
M M F
C C A
7 7 7
0 0 1
1 2 3 9 11 10 7 8
Cable trough
CX600-X8 | Old Airport-ASG-B
Air intake vent

To Mekanisa-ASG-A - XGE 8/0/1
To Old Airport-ASG-A - 40GE 3/0/0 GE 40GE 40GE 10GE
To Kirkos-RSG-A - 40GE 7/0/0
2 0 0 0 1
To 62N - XGE 0/6/0

2 3 To 63N - XGE 0/6/0
C
R
- 5
D
0
E
C C C 4
F
G
X X X
F
A
C
R
6 6 6
0 7
0
5 D D D
D
L
0 S 0
2-0
P S F S
To Old Airport-ASG-A - 40GE 3/2/0 1 2
U
F 40GE
3 4 R
9 U
11 R
10 5 6 40GE
7 10GE
8 To Kirkos-RSG-A - 40GE 7/2/0
5 U I U
2
1
7
0 A 4 A 0 0 1
0 4 0 4
1 1 1
0 C 0 2 3
-
C C C
R R 4 R
5 5 5
D D D
0 0 0
0 0 L
1 E E A
2 2 X
M M F
C C A
7 7 7
0 0 1
2 3 9 11 10 7 8
Cable trough
18.3.6 CX600-X8 in Karanyo

CX600-X8 | Karanyo-ASG-A
Air intake vent

To Mekanisa-ASG-B - XGE 8/0/1
To Karanyo-ASG-B - XGE 2/0/1 C
R
5 To Mekanisa-ASG-B - XGE 8/0/0
To Karanyo-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
P
1
To 43N - XGE 0/5/0
1 0 1 0 1 0 1
-
2
To 59N - XGE 0/5/0
4
x GE
c 2 3
E
1
0 1
To 76N - XGE 0/5/0
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
-407-
CX600-X8 | Karanyo-ASG-B
Air intake vent
To Karanyo-ASG-A - XGE 2/0/1 To Old Airport-ASG-A - XGE 8/0/1

To Karanyo-ASG-A - XGE 2/0/0 10GE 10GE
To Old Airport-ASG-A - XGE 8/0/0
0 1 0 1
To 79N - XGE 0/6/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
18.3.7 CX600-X8 in Mekanisa

CX600-X8 | Mekanisa-ASG-A
Air intake vent

To Old Airport-ASG-B - XGE 8/0/1
To Mekanisa-ASG-B - XGE 2/0/1 C
R
5 To Old Airport-ASG-B - XGE 8/0/0
To Mekanisa-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
P
1
To 145D - XGE 0/5/0
1 0 1 0 1 0 1
-
2
To 29N - XGE 0/5/0
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
-408-
CX600-X8 | Mekanisa-ASG-B
Air intake vent

To Karanyo-ASG-A - XGE 8/0/1
To Karanyo-ASG-A - XGE 8/0/0
To Mekanisa-ASG-A - XGE 2/0/0 10GE 10GE
To 80N - XGE 0/6/0

0 1 0 1
To 65N - XGE 0/6/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
18.3.8 CX600-X8 in Bole Micheal

CX600-X8 | Bole Micheal-ASG-A
Air intake vent
To Bole Micheal-ASG-B - XGE 2/0/1 C To Nifas Silk-RSG-B - XGE 8/0/0

R
5
To Bole Micheal-ASG-B - XGE 2/0/0 E1
3
-
10GE 40GE 40GE 10GE
To Nifas Silk-RSG-B - XGE 8/0/1
P
1
1 0 1 0 1 0 0 0 1
-
2
To 82N - XGE 0/5/0
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 40GE
6 40GE
7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 0 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C C C
R R R 4 R
18 19 5 5 5 5
D D D D
L 0 0 0
2 0 0 L
3 1 20 21 X E E A
E 2 2 X
F M M F
22 23 G C C A
7 7 7 7
A 0 0 1
1 2 9 11 10 6 7 8
Cable trough
CX600-X8 | Bole Micheal-ASG-B
Air intake vent
To Bole Micheal-ASG-A - XGE 2/0/1 To Akaki-ASG-A - XGE 8/0/1

To Bole Micheal-ASG-A - XGE 2/0/0 10GE 40GE 40GE 10GE
To Akaki-ASG-A - XGE 8/0/0
0 1 0 0 0 1
GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 40GE
6 40GE
7 10GE
8
10 11 U I U
A 4 A 0 0 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C C C
R R R 4 R
18 19 5 5 5 5
D D D D
L 0 0 0
2 0 0 L
20 21 X E E A
E 2 2 X
F M M F
22 23 G C C A
7 7 7 7
A 0 0 1
2 9 11 10 6 7 8
Cable trough
-409-
18.3.9 CX600-X8 in Akaki

CX600-X8 | Akaki-ASG-A
Air intake vent
To Akaki-ASG-B - XGE 2/0/1 C To Bole Micheal-ASG-B - XGE 8/0/1

R
5
To Akaki-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
To Bole Micheal-ASG-B - XGE 8/0/0
P
1
1 0 1 0 1 0 1
-
2
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
CX600-X8 | Akaki-ASG-B
Air intake vent
To Akaki-ASG-A - XGE 2/0/1 To Kality-ASG-A - XGE 8/0/1

To Akaki-ASG-A - XGE 2/0/0 10GE 10GE
To Kality-ASG-A - XGE 8/0/0
0 1 0 1
To 122 - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 8
10GE
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-410-
18.3.10 CX600-X8 in Kality

CX600-X8 | Kality-ASG-A
Air intake vent
To Kality-ASG-B - XGE 2/0/1 To Akaki-ASG-B - XGE 8/0/1

To Kality-ASG-B - XGE 2/0/0 10GE 10GE
To Akaki-ASG-B - XGE 8/0/0
0 1 0 1
To 125D - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
CX600-X8 | Kality-ASG-B
Air intake vent
To Kality-ASG-A - XGE 2/0/1 To Lebu-ASG-A - XGE 8/0/1

To Kality-ASG-A - XGE 2/0/0 10GE 10GE
To Lebu-ASG-A - XGE 8/0/0
0 1 0 1
To 33N - XGE 0/6/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-411-
18.3.11 CX600-X8 in Lebu

CX600-X8 | Lebu-ASG-A
Air intake vent
To Lebu-ASG-B - XGE 2/0/1 To Kality-ASG-B - XGE 8/0/1

To Lebu-ASG-B - XGE 2/0/0 10GE 10GE
To Kality-ASG-B - XGE 8/0/0
0 1 0 1
To 317N - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
CX600-X8 | Lebu-ASG-B
Air intake vent
To Lebu-ASG-A - XGE 2/0/1 To Hanna Mariam-ASG-A - XGE 8/0/1

To Lebu-ASG-A - XGE 2/0/0 10GE 10GE
To Hanna Mariam-ASG-A - XGE 8/0/0
0 1 0 1
To 71N - XGE 0/6/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-412-
18.3.12 CX600-X8 in HannaMariam

CX600-X8 | Hanna Mariam-ASG-A
Air intake vent
To Hanna Mariam-ASG-B - XGE 2/0/1 C To Lebu-ASG-B - XGE 8/0/1

R
5
To Hanna Mariam-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
To Lebu-ASG-B - XGE 8/0/0
P
1
1 0 1 0 1 0 1
-
2
To 85N - XGE 0/5/0
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
CX600-X8 | Hanna Mariam-ASG-B
Air intake vent
To Hanna Mariam-ASG-A - XGE 2/0/1 To Nifas Silk-RSG-A - XGE 8/0/1

To Hanna Mariam-ASG-A - XGE 2/0/0 10GE 10GE
To Nifas Silk-RSG-A - XGE 8/0/0
0 1 0 1
To 30N - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
18.3.13 CX600-X8 in Kolfe

CX600-X8 | Kolfe-ASG-A
Air intake vent
To Kolfe-ASG-B - XGE 2/0/1 C To Addis Ketema-ASG-B - XGE 8/0/1

R
5
To Kolfe-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
To Addis Ketema-ASG-B - XGE 8/0/0
P
1
1 0 1 0 1 0 1
-
2
To 42N - XGE 0/5/0
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
-413-
CX600-X8 | Kolfe-ASG-B
Air intake vent

To Burau-ASG-A - XGE 8/0/1
To Kolfe-ASG-A - XGE 2/0/1
To Burau-ASG-A - XGE 8/0/0
To Kolfe-ASG-A - XGE 2/0/0 10GE 10GE
To 78N - XGE 0/5/0

0 1 0 1
To 04N - XGE 0/6/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
18.3.14 CX600-X8 in Burau

CX600-X8 | Burau-ASG-A
Air intake vent
To Burau-ASG-B - XGE 2/0/1 C To Kolfe-ASG-B - XGE 8/0/1

R
5
To Burau-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
To Kolfe-ASG-B - XGE 8/0/0
P
1
1 0 1 0 1 0 1
-
2
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
CX600-X8 | Burau-ASG-B
Air intake vent
To Burau-ASG-A - XGE 2/0/1 To Asko-ASG-A - XGE 8/0/1

To Burau-ASG-A - XGE 2/0/0 10GE 10GE
To Asko-ASG-A - XGE 8/0/0
0 1 0 1
GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-414-
18.3.15 CX600-X8 in Asko

CX600-X8 | Asko-ASG-A
Air intake vent
To Asko-ASG-B - XGE 2/0/1 C To Burau-ASG-B - XGE 8/0/1

R
5
To Asko-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
To Burau-ASG-B - XGE 8/0/0
P
1
1 0 1 0 1 0 1
-
2
To 286E - XGE 0/5/0
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
CX600-X8 | Asko-ASG-B
Air intake vent

To Shegole-ASG-A - XGE 8/0/1
To Asko-ASG-A - XGE 2/0/1
To Shegole-ASG-A - XGE 8/0/0
To Asko-ASG-A - XGE 2/0/0 10GE 10GE
To 08N - XGE 0/5/0

0 1 0 1
To 25N - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-415-
18.3.16 CX600-X8 in Shegole

CX600-X8 | Shegole-ASG-A
Air intake vent
To Shegole-ASG-B - XGE 2/0/1 C To Asko-ASG-B - XGE 8/0/1

R
5
To Shegole-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
To Asko-ASG-B - XGE 8/0/0
P
1
1 0 1 0 1 0 1
-
2
To 136D - XGE 0/5/0
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
CX600-X8 | Shegole-ASG-B
Air intake vent
To Shegole-ASG-A - XGE 2/0/1 To Addis Ketema-ASG-A - XGE 8/0/1

To Shegole-ASG-A - XGE 2/0/0 10GE 10GE
To Addis Ketema-ASG-A - XGE 8/0/0
0 1 0 1
To 57N - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-416-
18.3.17 CX600-X8 in Gebeya

CX600-X8 | Addisu Gebeya-ASG-A
Air intake vent

To Arada-RSG-B - XGE 8/0/1
To Addisu Gebeya-ASG-B - XGE 2/0/1 C
R
5 To Arada-RSG-B - XGE 8/0/0
To Addisu Gebeya-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
P
1
To 60N - XGE 0/5/0
1 0 1 0 1 0 1
-
2
To 05N - XGE 0/5/0
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
CX600-X8 | Addisu Gebeya-ASG-B
Air intake vent
To Addisu Gebeya-ASG-A - XGE 2/0/1 To Ferensail-ASG-A - XGE 8/0/1

To Addisu Gebeya-ASG-A - XGE 2/0/0 10GE 10GE
To Ferensail-ASG-A - XGE 8/0/0
0 1 0 1
GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-417-
18.3.18 CX600-X8 in Ferensail

CX600-X8 | Ferensail-ASG-A
Air intake vent
To Ferensail-ASG-B - XGE 2/0/1 C To Addisu Gebeya-ASG-B - XGE 8/0/1

R
5
To Ferensail-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
To Addisu Gebeya-ASG-B - XGE 8/0/0
P
1
1 0 1 0 1 0 1
-
2
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
CX600-X8 | Ferensail-ASG-B
Air intake vent
To Ferensail-ASG-A - XGE 2/0/1 To Arada-RSG-A - XGE 8/0/1

To Ferensail-ASG-A - XGE 2/0/0 10GE 10GE
To Arada-RSG-A - XGE 8/0/0
0 1 0 1
To 23N - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-418-
18.3.19 CX600-X8 in Kotebe

CX600-X8 | Kotebe-ASG-A
Air intake vent

To Yeka-ASG-B - XGE 8/0/1
To Kotebe-ASG-B - XGE 2/0/1
To Yeka-ASG-B - XGE 8/0/0
To Kotebe-ASG-B - XGE 2/0/0 10GE 10GE
To 73N - XGE 0/5/0

0 1 0 1
To 316N - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 8
10GE
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
CX600-X8 | Kotebe-ASG-B
Air intake vent

To Ayat Meronia-ASG-A - XGE 8/0/1
To Kotebe-ASG-A - XGE 2/0/1
To Ayat Meronia-ASG-A - XGE 8/0/0
To Kotebe-ASG-A - XGE 2/0/0 10GE 10GE
To 309N - XGE 0/6/0

0 1 0 1
To 296E - XGE 0/6/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-419-
18.3.20 CX600-X8 in Ayat

CX600-X8 | Ayat Meronia-ASG-A
Air intake vent
To Ayat Meronia-ASG-B - XGE 2/0/1 C To Kotebe-ASG-B - XGE 8/0/1

R
5
To Ayat Meronia-ASG-B - XGE 2/0/0 E1
3
-
10GE 10GE
To Kotebe-ASG-B - XGE 8/0/0
P
1
1 0 1 0 1 0 1
-
2
To 75N - XGE 0/5/0
4
x GE
c 2 3
E 0 1
1
- / -
c
T
1
2 3 C C C 4
-
D
X X X
B
1
C
R
4 5
6 6 6
2 0
0
0 5 6 7
D D D
D
L
0 S 0
1-2
P 8 9 S F S
1
U
F 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
5 10 11 U I U
1 1
0
7
A 4 A 0 1
0 12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
- - 16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
3 1 20 21 X A
E X
F F
22 23 G A
7 7
A 1
1 2 9 11 10 8
Cable trough
CX600-X8 | Ayat Meronia-ASG-B
Air intake vent
To Ayat Meronia-ASG-A - XGE 2/0/1 To Gerji-ASG-A - XGE 8/0/1

To Ayat Meronia-ASG-A - XGE 2/0/0 10GE 10GE
To Gerji-ASG-A - XGE 8/0/0
0 1 0 1
GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-420-
18.3.21 CX600-X8 in Gerji

CX600-X8 | Gerji-ASG-A
Air intake vent
To Gerji-ASG-B - XGE 2/0/1 To Ayat Meronia-ASG-B - XGE 8/0/1

To Gerji-ASG-B - XGE 2/0/0 10GE 10GE
To Ayat Meronia-ASG-B - XGE 8/0/0
0 1 0 1
To 290E - XGE 0/5/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
CX600-X8 | Gerji-ASG-B
Air intake vent

To Yeka-ASG-A - XGE 8/0/1
To Yeka-ASG-A - XGE 8/0/0
To Gerji-ASG-A - XGE 2/0/0 10GE 10GE
To 307N - XGE 0/5/0

0 1 0 1
To 299E - XGE 0/6/0

GE
2 3
0 1
2 3 C C C 4
X X X
4 5
6 6 6
6 7
D D D
0 S 0
8 9 S F S
1 2 3 4 R
9 U
11 R
10 5 6 7 10GE
8
10 11 U I U
A 4 A 0 1
12 13
4 0 4
1 1 1
14 15
0 C 0 2 3
16 17
C C
R 4 R
18 19 5 5
D D
L 0
2 L
20 21 X A
E X
F F
22 23 G A
7 7
A 1
2 9 11 10 8
Cable trough
-421-
18.4 CSG Site ATN Layout

18.4.1 Scenarios1: ATN 1x10GE without E1
To Hanna Mariam-ASG-B - XGE 8/0/2
ATN950B 30N
7 ANDD00CXPB01
7 8 ANDD00CXPB01
8
ATN950B | 30N
P
I ANDD000EX100
U 5 5 6
10GE
F 0
A
N 3 4
P
I ANDD00EM8F00
U 1 0 2 1 4 6 2
GE
1 3 5 7
Below ATN site is belong to this Scenarios:

122,188D,05N,08N,56N,67N,69N,291E,13N,30N,175,141,171D,03N,75N,49N.
-422-
18.4.2 Scenarios2: ATN 1x10GE with E1
To Bole-RSG-B - XGE 8/0/1
ATN950B 180D
ATN950B | 180D
7 7 8 8
P
I ANDD000EX100
U 5 5 6
10GE
F 0
A
N 3 4
P
U 1 0 2 1 4 6 2 0 2 4 2 6 8 10 12 14
GE
E1
1 3 5 7 1 3 5 7 9 11 13 15
Below ATN site is belong to this Scenarios:

004D,010,18D,10N,25N,57N,60N,307N,74N,43N,85N,83N,136D,180D,23N,76N,168,82N,39N,
-423-
To 50N - XGE 0/6/0
To 15N - XGE 0/5/0

ATN950B 41D
7 ANDD00CXPB01
7 8 ANDD00CXPB01
8
ATN950B | 41D
P
U 5 5 6 6
10GE
10GE
F 0 0
A
N 3 4
P
I ANDD00EM8F00
U 1 0 2 1 4 6 2
GE
1 3 5 7
Below ATN is belong to this Scenarios:

192D,201,286E,34N,45N,47N,53N,279E,281E,287E,288E,293E,300E,306N,309N,311N,312N,314N,315N,316N,292E,81
N,126,134,29N,46N,002D,137D,33N,42N,72N,44N,65N,22N,41D,125,22D,38N,59N,77N,61N,54N,296E,45D,012,295E,
35D,04N,70N,73N,297E,298E,74,130D,
18.4.4 Scenarios4: ATN 2x10GE with E1
-424-
To 299E - XGE 0/5/0

ATN950B 290E
ATN950B | 290E
7 7 8 8
P
U 5 5 6 6
10GE
10GE
F 0 0
A
N 3 4
P
U 1 0 2 1 4 6 2 0 2 4 2 6 8 10 12 14
GE
E1
1 3 5 7 1 3 5 7 9 11 13 15
Below ATN is belong to this Scenarios:

185D,194D,06N,15N,16N,17N,36N,37N,48N,51N,52N,280E,294E,308N,310N,14N,285E,01N,301E,53D,290E,283E,299
E,313N,55N,80N,62N,24N,317N,71N,78N,70,35N,40N,09N,50N,84N,63N,79N,145D,28N.
-425-
To 55N - XGE 0/6/0
To 79N - XGE 0/5/0

ATN950B 64N
7 ANDD00CXPB01
7 8 ANDD00CXPB01
8
ATN950B | 64N
P
U 5 5 6 6
10GE
10GE
F 0 0
A ANDD000EX100
N 3 3 4
10GE
P 0
I ANDD00EM8F00
U 1 0 2 1 4 6 2
GE
1 3 5 7
To 141 - XGE 0/5/0
Below ATN is belong to this Scenarios:64N
-426-
Appendix
Acronyms and Abbreviations
A
AA Addis Ababa
ASG Aggregation Site Gateway
B
BFD Bidirectional Forwarding Detection
BGP Border Gateway Protocol
BITS Building Integrated Timing Supply
BTS Base Transceiver Station
BSC Base Station Controller
C
CE
CS Circuit Service
CSG Cell Site Gateway
E
E2E End to End
F
FE Fast Ethernet
FRR Fast Reroute
G
GE Gigabit Ethernet
GPS Global Position System
H
HA High Availability
HSDPA High Speed Downlink Packet Access
HVPN Hierarchical Virtual Private Network
I
IGP Internal Gateway Protocol
-427-
IS-IS Intermediate System-to-Intermediate System protocol

IPRAN IP Radio Access Network
L
LDP Label Distribution Protocol
LTE Long Term Evolution
M
MBB Mobile Broadband
MCE Multi-vpn-instance Customer Edge
MPLS Multiprotocol Label Switching
MME MME mobility management entities
MS-PW Multiple Segment PWE3
N
NBI Northbound Interface
NMS Network Management System
NSR None Stop Routing
NTP Network Time Protocol
O
OSPF Open Shortest Path First
OC Ordinary Clock
P
P Provider node
PE Provider Edge
PDV Packet Delay Variation
PRC Primary Reference Clock
PS Packet Service
PTP Precision Time Protocol
Q
QoS Quality of Service
R
RD Route Distinguisher
RNC Radio Network Controller
RR Route Reflector
RSG Radio Service Gateway
RT Route Target
RTN Radio Transmission Network
-428-
S
SDH Synchronous Digital Hierarchy
SLA Service Level Agreement
SNMP Simple Network Management Protocol
SSM Synchronization Status Message
STM Synchronous Transfer Mode
SyncE Synchronous Ethernet
SGW Service Gateway
T
TE Traffic Engineering
TDM Time Division Multiplexing
V
VLL Virtual Leased Line
VRF Virtual Routing and Forwarding
VPN Virtual Private Network
VPLS Virtual Private LAN Service
VPN FRR VPN Fast Reroute
-429-

Low Level Design For IP Backhaul 0205-Final

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Low Level Design For IP Backhaul 0205-Final

Uploaded by

Copyright:

Available Formats

Low Level Design for IP Backhaul

Low Level Design for IP Backhaul

HUAWEI TECHNOLOGIES CO., LTD.

ethio telecom TEP Confidential [键入文字]

ethio telecom TEP Confidential

5.3.2 NE40E Product .............................................................................................................. 31

ethio telecom TEP Confidential

8.2.1 Overview ...................................................................................................................... 169

ethio telecom TEP Confidential

10 Fixed-Line Services Implement ........................................................................................ 273

ethio telecom TEP Confidential

11.6.2 BGP Deployment Scope .............................................................................................. 304

ethio telecom TEP Confidential

15.2.2 Local User List ........................................................................................................... 348

ethio telecom TEP Confidential

18.1.1 NE40E-X8 in Arada.................................................................................................... 390

ethio telecom TEP Confidential

18.4.5 Scenarios5: ATN 3x10GE without E1......................................................................... 426

ethio telecom TEP Confidential

Figure 2- 1 Services Interruption time Requirement ........................................................................................................................8

ethio telecom TEP Confidential

Figure 9- 3 VRF RT Design ........................................................................................................................................................189

ethio telecom TEP Confidential

Figure 11- 5 physical connection design in Kirkos ......................................................................................................................293

ethio telecom TEP Confidential

Table 2- 1 Data traffic please check following table .......................................................................................................................5

Table 11- 2 core site equipment list .............................................................................................................................................287

The ET IPRAN archtectrue is show below:

CR/ER CR/ER CR/ER CR/ER

MSOFT3000 UMG8900 MSOFT3000 UMG8900

BSC RNC BSC RNC

MSAG ATN RTN MSAG ATN ATN

 Chapter 1:Project Overview

 Chapter 2:Network Requirement

 Chapter 3: Solution Overview

 Chapter 4: Network Architecture Design

 Chapter 5: Product and Naming

 Chapter 6: Logical Planning and Design

 Chapter 7: Routing protocol Design

 Chapter 8: MPLS Protocol design

 Chapter 9: Mobile Services Implement

 Chapter 10: Fixed-Line Services Implement

 Chapter 11: Interconnection Implement

 Chapter 12: Synchronization Design

 Chapter 13: QoS Design

 Chapter 14: Network Management System

 Chapter 15: Security Design

 Chapter 16: Future IPV6 Evolution

 Chapter 17: Future Multicast

2.1 Performance Requirement

Table 2- 1 Data traffic please check following table

PS Interface Single Subscriber Rate Total Subscribers Total Bandwidth

AMR12.2, Activity Factor: 0.67

PerUser@BusyHour Rate=Erl@BH*ActivityFactor*Ri =0.025*0.67*30K=0.503Kbps

Table 2- 2 Voice traffic please check following table

CS Interface Erl Codec Total Subscriber Total Bandwidth

RF new plan 722 swapping/new BTS/NodeB/e-NodeB

Table 2- 3 Service Bandwidth

System Total Bandwidth Count Bandwidth Requirement

2.2 QoS Requirement

Jitter: refers to the difference between delays of each packet.

Type Latency Jitter PLR

Best 20ms 4ms 0.0001%

PerUser@BusyHour Rate=Erl@BHActivityFactorRi =0.0250.6730K=0.503Kbps