ZTE LLD For MSAG Upgrade Project (V1.9)
ZTE LLD For MSAG Upgrade Project (V1.9)
ZTE LLD For MSAG Upgrade Project (V1.9)
TABLE OF CONTENTS
Records of Change...................................................................................................................................................7
1 Background...........................................................................................................................................................9
5 Network Reliability.............................................................................................................................................76
6.1 Overview..................................................................................................................................................80
7 Service Deployment............................................................................................................................................84
8 DATA planning...................................................................................................................................................87
9 Power Solution..................................................................................................................................................103
9.1 Overview................................................................................................................................................103
10 Acronyms........................................................................................................................................................109
Figure 3-5 Then connection between master shelf and slave shelf......................................................................67
Table 6-1 Software Deployment for Remote 1+1 Redundant System (Server-based) .......................................82
Records of Change
Updated documentation
V1.6 18-12-19 GuoHongBo
template
Updated IP/VLAN/MSTP
V1.9 15-01-20 GuoHongBo planning, added iENERGY
contents
1 Background
In the existing MSAG network of Ethio Telecom, most of the AA Zones (819+ MSAGs) and regional main
towns (more than 61 towns having 1110 + MSAGs) are covered by MSAG giving to more than 640K
POTs (voice), 640K ADSL and 40K Combo services (voice + data). There are also around 1543 Ethernet
passive optical network (EPON) cards (fiber connection) all over the country.
The MSAGs have been serving for 10 years and the MSAGs will be challenged to fulfill the subscribers’
requirements in the coming future. Hence, it time to plan and take prompt move to upgrade these access
equipment
The decline of the data package tariff has contributed a lot in subscribers increasing and higher
bandwidth demand. The existing MSAG covers most of the major area in a large scale and is close
to the major broadband subscribers in the country, if Ethio Telecom continues to use the
geographical advantage of MSAG to access broadband users, it will greatly save investment in
passive optical network. However, after 10 years’ operation, there are some challenges in the
existing MSAG network.
To provide higher bandwidth, advanced access technology should be deployed in the MSAG
network, such as VDSL vectoring and GPON. Moreover, the EPON card that is used to provide high
speed data/internet services with fiber cable has already been stopped manufacturing. And the
widely deployed MSAGs don’t support GPON and VDSL vectoring. So the existing MSAG network
needs to upgrade to meet the higher bandwidth demand.
Because of the rectifier system, battery, and MSAG integrated design, the battery space has the
same temperature with MSAG. But there is only one heat-exchanger for the whole cabinet. And the
aged heat-exchanger and rectifier system result in low efficiency. The heat generated from different
cards is found to shorten the life time of the battery systems. Due to the above mentioned
temperature issue and aging, the batteries backup time is reduced to 10-30 minutes. The MSAGs
require better solution to improve the power system performance.
The architecture of existing MSAGs which are connected in link or ring topologies using CWDM
system is complicated, resulting in low efficiency for maintenance and high OPEX. Besides, lack of
spares is a big challenge in the CWDM network. So the CWDM needs to be removed.
This LLD offer the direction of 42 MSAG sites deployment. For example, MSAG work principle,
topology information, data plan. The LLD document will be used as a primary reference for
deployment and to some extent for the operation and maintenance.
The architecture of existing MSAGs which are connected in link or ring topologies using CWDM
system is complicated, resulting in low efficiency for maintenance and high OPEX. Besides, lack of
spares is a big challenge in the CWDM network. So the CWDM needs to be removed
The upgraded MSAG provides multiple GE/10GE ports for uplink and ring network, then the CWDM
Transmission can be removed to simplify the network. Taking consideration of reliability and user
experience, 1 to 5 AG sites in one ring is recommended. The network architecture is as below:
In order to solve the problem of the power system and introduce new access service, MSAG
upgrade solution is described as below.
The existing cabinet is connected to new added cabinet with Ethernet & fiber cable, power cable.
The new service (GPON) will be introduced in enhanced MSAG shelf.
The new power system in new cabinet will provide the power for new and existing cabinets, and the
old power system in MSAG will be stopped or dismantled. This solution will solve the temperature
and backup time issue.
In the new cabinet, there will be two separate spaces to completely separate the MSAG equipment
and power system. Right side cabin is for new enhanced MSAG shelf with heat exchanger. The other
cabin is for power system and battery. DC air conditioner will be deployed for battery heat
dissipation.
Two new servers are installed to manage the new deployed MSAG. The servers work in active and
standby mode and they are installed at Kirkos and Old airport sites. Each NM server has three GE
uplinks by Ethernet cable. Two links are used for data synchronization and heart beat between two
servers. The third link is connected to CS and it’s in charge of equipment management and client
access. There are 5 PC worked as NM client.
We will deploy 42 C300M sites in Addis. The dual server should manage all devices.
The HSI services traffic module in Addis is shown in the figure below. The new connection is
created between MSAG C300M and CS/ASG in these 14 equipment room
(Yeka 、 Bole 、 Legehar 、 Nifasilk 、 Arada 、 Adis Ketema 、 Bole_Mchael 、 Kality 、 Akaki 、 Addis
Ketema 、 Ayat 、 Kotebe 、 Hanamariam and Gerji). The connection bandwidth is 10GE to the
CS/ASG. And they have to be co-site (two switches: one leg of the ring will be on CS/ASG A and
the other leg will be on CS/ASG B). The gateway of HSI is on BRAS.
IPoE & PPPoE service will adopt QinQ VLAN on MSAG C300M. Each MSAG C300M will be
assigned unique SVLAN. BRAS will terminate QinQ VLAN. VoIP service will adopt single VLAN on
MSAG. ER will terminate the single VLAN .
Old MSAG 5200 will adopt QINQ after upgrade. Both EPON/ADSL services will adopt unique
SVLAN and common CVLAN in Old MSAG 5200.
The gateway of broadband is located on BRAS. The customer VLAN is terminated on BRAS. The
traffic to IP-Backbone is forwarded by routing table. So it’s layer 3 network between two BRAS.
Figure 2-7 is the VOIP services traffic module in Addis. The gateway of VOIP is located on
CS/ASG. Each MSAG ring will be assigned unique VOIP VLAN. Signal and media will share the
same VLAN and IP address.
Old MSAG 5200 will keep adopt single VOIP VLAN after upgrade.
There are two ZTE softswitch in Addis. They are worked in master/backup mode. When the link to
master SS is down, MSAG signal traffic will be swap to backup SS. The softswitch IP is 10.208.0.4 in
Bole. The softswitch IP is 10.209.0.4 in Kirkos.
Normally one link between MSAG is block by MSTP protocol. Otherwise the ring is formed. It can
lead to broadcast storm. The traffic module is shown as above topology. For protocol detail
information you can find in “5.3 C300M MSTP protection”.
38.81909
NAAZ 9.023680
306 Yeka 7
ZTE Low Level Design for MSAG Upgrade Project
38.81690
EAAZ 9.019383
330 Yeka 5
1
326 Yeka NAAZ 9.020949 38.80495
38.82041
EAAZ 9.009396
321 Yeka 8
38.77990
EAAZ 9.003582
806 Bole 6
2504 abroad
All Rights reserved, No Spreading Yeka without Permission
EAAZ of9.03019
ZTE 38.87582 20
For each ring there are two IP nodes to be connected, the information is shown as
following figures.
Aggregation Remote
Site Name Local Port Equipment Port
xgei-
xgei_1/19/1 111082-YK-CS-A 0/2/0/2
New MSAG-306
xgei_1/20/1 New MSAG-330 xgei_1/19/1
Aggregation Remote
Site Name Local Port Equipment Port
xgei-
xgei_1/19/1 111136-BL-CS-A 0/2/0/2
New MSAG-806
xgei_1/20/1 New MSAG-817 xgei_1/19/1
xgei-
New MSAG-808
xgei_1/20/1 111136-BL-CS-B 0/2/0/2
There will be two MSTP instances in Ring 2, instance 2 will contain the BB/VOIP/MGMT service of
MSAG 5200 806/817/830,BB service of C300M 806/817/830 and VOIP/MGMT service of C300M
806/817/830/812/808. 111136-BL-CS-A will be Root of instance 2.
And instance 3 will contain the BB/VOIP/MGMT service of MSAG5200 812/808.BB service of C300M
812/808. 111136-BL-CS-B will be Root of instance 3.
Aggregation Remote
Site Name Local Port Equipment Port
xgei-
xgei_1/19/1 111058-LGH-CS-A 0/2/0/4
New MSAG-789
xgei_1/20/1 New MSAG-743 xgei_1/19/1
There will be two MSTP instances in Ring 3, instance 2 will contain the BB/VOIP/MGMT service of
MSAG 5200 789/743/794,BB service of C300M 789/743/794 and VOIP/MGMT service of C300M
789/743/794/737/730. 111058-LGH-CS-A will be Root of instance 2.
And instance 3 will contain the BB/VOIP/MGMT service of MSAG5200 737/730.BB service of C300M
737/730. 111058-LGH-CS-B will be Root of instance 3.
Aggregation Remote
Site Name Local Port Equipment Port
xgei-
xgei_1/19/1 111058-LGH-CS-A 0/2/0/5
New MSAG-793
xgei_1/20/1 New MSAG-729 xgei_1/19/1
There will be two MSTP instances in Ring 4, instance 4 will contain the BB/VOIP/MGMT service of MSAG
5200 793/729,BB service of C300M 793/729 and VOIP/MGMT service of C300M 793/729/727/720. 111058-
LGH-CS-A will be Root of instance 4.
And instance 5 will contain the BB/VOIP/MGMT service of MSAG5200 727/720.BB service of C300M
727/720. 111058-LGH-CS-B will be Root of instance 5.
Aggregation Remote
Site Name Local Port Equipment Port
xgei-
xgei_1/19/1 111136-BL-CS-A 0/2/0/6
New MSAG-870
xgei_1/20/1 New MSAG-804 xgei_1/19/1
There will be two MSTP instances in Ring 5, instance 4 will contain the BB/VOIP/MGMT service of MSAG
5200 870/804,BB service of C300M 870/804 and VOIP/MGMT service of C300M 870/804/805/855. 111136-
BL-CS-A will be Root of instance 4.
And instance 5 will contain the BB/VOIP/MGMT service of MSAG5200 805/855.BB service of C300M
805/855. 111136-BL-CS-B will be Root of instance 5.
Aggregation Remote
Site Name Local Port Equipment Port
111010_Bole_Mch GigabitEth
xgei_1/19/1 ael_ASG_A ernet8/0/3
There will be two MSTP instances in Ring 6, instance 2 will contain the BB/VOIP/MGMT service of MSAG
5200 839,111010_Bole_Mchael_ASG_A will be Root of instance 2.
And instance 3 will contain the BB/VOIP/MGMT service of C300M 839. 111010_Bole_Mchael_ASG_B will
be Root of instance 3.
Equipment Port
xgei-
xgei_1/19/1 111007-NS-CS-A 0/2/0/3
New MSAG-202
xgei_1/20/1 New MSAG-201 xgei_1/19/1
xgei-
New MSAG-221
xgei_1/20/1 111007-NS-CS-B 0/2/0/3
There will be two MSTP instances in Ring 7, instance 4 will contain the BB/VOIP/MGMT service of MSAG
5200 202/201/203,BB service of C300M 202/201/203 and VOIP/MGMT service of C300M
202/201/203/222/221. 111007-NS-CS-A will be Root of instance 4.
And instance 5 will contain the BB/VOIP/MGMT service of MSAG5200 222/221.BB service of C300M
222/221. 111007-NS-CS-B will be Root of instance 5.
Aggregation Remote
Site Name Local Port Equipment Port
111767_Kality_AS GigabitEth
xgei_1/19/1 G_A ernet8/2/0
New MSAG-2301
xgei_1/20/1 New MSAG-2309 xgei_1/19/1
111408_Akaki_AS GigabitEth
New MSAG-14
xgei_1/20/1 G_A ernet8/0/2
There will be two MSTP instances in Ring 8, instance 6 will contain the BB/VOIP/MGMT service of MSAG
5200 2301/2309,BB service of C300M 2301/2309 and VOIP/MGMT service of C300M
2301/2309/2307/14.111767_Kality_ASG_A will be Root of instance 6.
And instance 7 will contain the BB/VOIP/MGMT service of MSAG5200 2307/14.BB service of C300M
2307/14.111408_Akaki_ASG_A will be Root of instance 7.
Aggregation Remote
Site Name Local Port Equipment Port
111057_Addis_Ket GigabitEth
xgei_1/19/1 ema_ASG_A ernet8/2/1
There will be two MSTP instances in Ring 9, instance 2 will contain the BB/VOIP/MGMT service of MSAG
5200 630,111057_Addis_Ketema_ASG_A will be Root of instance 2.
And instance 3 will contain the BB/VOIP/MGMT service of C300M 630. 111057_Addis_Ketema_ASG_B will
be Root of instance 3.
Aggregation Remote
Site Name Local Port Equipment Port
xgei-
xgei_1/19/1 111055-AD-CS-A 0/2/0/4
There will be two MSTP instances in Ring 10, instance 2 will contain the BB/VOIP/MGMT service of MSAG
5200 485,111055-AD-CS-A will be Root of instance 2.
And instance 3 will contain the BB/VOIP/MGMT service of C300M 485. 111055-AD-CS-B will be Root of
instance 3.
Aggregation Remote
Site Name Local Port Equipment Port
111165_Ayat_ASG GigabitEth
xgei_1/19/1 _A ernet8/0/4
New MSAG-2504
xgei_1/20/1 New MSAG-1640 xgei_1/19/1
111086_Kotebe_A GigabitEther
New MSAG-1639
xgei_1/20/1 SG_A net8/0/4
There will be two MSTP instances in Ring 11, instance 4 will contain the BB/VOIP/MGMT service of MSAG
5200 2504/1640,BB service of C300M 2504/1640 and VOIP/MGMT service of C300M
2504/1640/1639.111165_Ayat_ASG_A will be Root of instance 4.
And instance 5 will contain the BB/VOIP/MGMT service of MSAG5200 1639.BB service of C300M
1639.111086_Kotebe_ASG_A will be Root of instance 5.
Equipment Port
111120_Hanamaria GigabitEth
xgei_1/19/1 m_ASG_A ernet8/2/0
There will be two MSTP instances in Ring 12, instance 8 will contain the BB/VOIP/MGMT service of MSAG
5200 1913,111120_Hanamariam_ASG_A will be Root of instance 8.
And instance 9 will contain the BB/VOIP/MGMT service of C300M 1913. 111120_Hanamariam_ASG_B will
be Root of instance 9.
Aggregation Remote
Site Name Local Port Equipment Port
111089_Gerji_ASG GigabitEth
xgei_1/19/1 _A ernet8/0/4
There will be two MSTP instances in Ring 13, instance 6 will contain the BB/VOIP/MGMT service of MSAG
5200 1102,111089_Gerji_ASG_A will be Root of instance 6.
And instance 7 will contain the BB/VOIP/MGMT service of C300M 1102. 111089_Gerji_ASG_B will be Root
of instance 7.
Aggregation Remote
Site Name Local Port Equipment Port
xgei-
xgei_1/19/1 111055-AD-CS-A 0/2/0/5
New MSAG-469
xgei_1/20/1 New MSAG-490 xgei_1/19/1
There will be two MSTP instances in Ring 14, instance 4 will contain the BB/VOIP/MGMT service of
MSAG 5200 469,BB service of C300M 469 and VOIP/MGMT service of C300M 469/490.111055-AD-
CS-A will be Root of instance 4.
And instance 5 will contain the BB/VOIP/MGMT service of MSAG5200 490.BB service of C300M
490.111055-AD-CS-A will be Root of instance 5.
Overall Architecture
The core technology in ZXA10 C300M is TDM + IP. It supports two switching types:
Circuit switching
Ethernet switching
As shown in Figure 3-1, the outmost block represents the system boundary. The dotted frame
represents the card functions. The dotted frame at the lower-right corner represents the sub-card on the
main control card.
At the user side, ZXA10 C300M provides POTS, ISDN, and xDSL access. At the network side, ZXA10
C300M provides IP uplink.
Narrowband service data enters the TDM switching module of SCXN card.
TDM switching module performs circuit switching on the voice signals and sends them
to VoIP processing card.
VoIP processing card converts voice traffic into IP packets and sends them to Ethernet
switching module.
Ethernet switching chip switches the IP packets and send them to NAT module for
network address translation.
IP packets enter the IP network through an uplink interface after Ethernet switching.
Broadband service data enters Ethernet switching chip of control and switching card
and directly goes to IP network through an uplink interface.
The dimensions of 19-inch service shelf are 443.7 mm × 482.6 mm × 270 mm (Height × Width × Depth).
As it is shown in the figure, the leftmost slots are Slots 0 and 1. Slot 0 and 1 are dedicated for the
power cards. The rightmost slots are Slots 19 and 20, which are dedicated for the network
interface cards.
12 – 17 Line card
The user lines are connected to MDF and extended to user’s side.
The uplink card of master shelf is connected to the uplink card of slave shelves. One pair of cascade
cables work in either 1+1 or 1:1 protection mode.
Figure 3-27 Then connection between master shelf and slave shelf
LC cards
LC: Line Card, including narrowband line card and broadband line card.
Active / Standby
redundancy
Load sharing
10 GE to any subscriber
card(for each card)
ISDN PRI
GPON(GTG Type of
MSAG No/Name TYPE
HK) MSAG
Table 3-4 describes the subsystem functions of the overall software architecture of the ZXA10
C300M&C350M system.
Service
The service subsystem is in the core layer of the total system
subsystem
software. It is responsible for the implementation of relevant
services. The service subsystem consists of the broadband
protocol subsystem and the narrowband protocol subsystem.
Protocol
The protocol subsystem implements TCP, UDP, IP, ICMP,
subsystem
ARP, RARP, TFTP, FTP, SNMP, Telnet, IGMP, MSTP, and
other protocols.
Bearer
Detection of subscriber circuits
subsystem
Announcement play
Version management
Memory management
Timer management
Operating
The real-time operating system consists of board support
system
package and drivers, supporting the upper-layer subsystem.
ZTE EC40CE Cabinet is an outdoor cabinet that is used for installing integrated access devices
the ZXA10 C300M and providing a reliable operating environment for them. It dissipates heat
through the heat exchanger. Figure 4-2 shows the appearance of ZTE EC40CE Cabinet:
5 Network Reliability
Providing 1+1 protection of the main control & switching unit, backplane bus and uplink card;
Link aggregation, also called trunking, binds multiple physical ports of the MSAG into a logic port. Link
aggregation is used to balance load of outgoing/incoming traffic among these ports. The maximum
port number is 4 in one link aggregation group. In this project the port number is 2 in one link
aggregation group. The total bandwidth is 2*GE. There are two free GE optical ports for the future
expansion.
At the same time, it provides backup. When some link is faulty, other uplink interfaces can work
normally to ensure the continuity of services. The load sharing adopts the algorithm based on L2 MAC
address, which evenly distributes service traffics to several links.
When any link is interrupted (signal interruption on the physical layer, such as broken optical fibers,
broken cables, damaged optical module and so on), the interrupted services on the interrupted link are
immediately switched over to another link to minimize the service interruption. After the interrupted link
recovers, the services on the original link automatically judge and readopt the load sharing mode.
The link aggregation not only provides a link protection function that's impossible in the single link
condition, but also evenly distributes services on different links to provide wider physical channels for
the service bearings.
Uplink Network
Aggregation
Support two link aggregation modes: static Trunk and LACP. Static trunk directly adds multiple
physical ports to a trunk group, thus forming a logical port. The realization of this mode is rather
simple, but it is not suitable for observing the status of the link aggregation port. LACP (Link
Aggregation Control Protocol) is link aggregation control protocol, which follows IEEE 802.3ad
standard.
LACP converges multiple physical ports into a trunk group to form a logical port and automatically
generates aggregation to obtain the maximum bandwidth.
At most eight Trunk groups can be configured, and each trunk group has at most eight member ports;
It supports cross-interface card aggregation, and member ports can be distributed on any interface
card, but member ports selected must operate in full duplex mode, with the consistent rate.
The logical port formed by link aggregation on the ZXA10 C300M is called a smartgroup. A
smartgroup can be used as a common port, and has the same default VLAN attributes as the common
Ethernet ports;
Configure the load-balance mode of link aggregation group: ZXA10 C300M supports two types of
load-balance: based on the source IP, and based on the source MAC. The default mode is based on
the source MAC addresses.
Produce a single spanning tree active topology for any given VLAN, ensuring that there is only
one data path between any two end stations for frames associated to said VLAN. Frames for
different VLANs may follow different paths.
Provide fault tolerance by automatically reconfiguring topology after Bridge or data path failures.
Eliminates the need for having a separate RSTP spanning tree for each VLAN.
The design of the multiple spanning tree protocol is based on RSTP and extended to allow for
different VLANs to travel along separate “instances” of spanning tree while allowing compatibility
with legacy STP devices.
bridge priorities may be different depending on the instance, frames may travel a different paths
in the active topology depending on what instance they are assigned to.
Configures the state of redundant switch ports as "Discard" to avoid loops formed in the
network.
SSTP
SSTP complies with the IEEE802.1d standard. The bridge running SSTP can interwork
with the bridges running RSTP and MSTP.
RSTP
RSTP converges faster than SSTP. When a topology changes, the state of a configured
redundant switch port transits rapidly in the point-to-point connection.
MSTP
MSTP provides the concepts of instances and VLAN mapping, and supports rapid VLAN
convergence and load balance. MSTP supports multiple spanning-tree instances and
different forwarding states of a port in different VLANs. It allows formation of multiple
independent sub-tree instances within an MST area for load balance.
6.1 Overview
NetNumen U31 is the integrated network management system developed by ZTE and is also the
future-oriented network management product and solution. It improves the capability, scalability
and ease of use with the mature and advanced network management architecture. It is a highly
customer-friendly, carrier-class and cross-platform integrated network management system.
NetNumen U31 provides centralized management and monitoring over network elements, helping
the operators to know the actual status of the network, adjust the equipment conveniently, and
make the network in its best status.
NetNumen U31 system adopts client/server architecture. The server software provides northbound
interfaces for BOSS/NMS, while southbound interfaces for NEs. The client software provides graphical
user interfaces to operate and maintain NEs.
For each site we deploy one IBM V5020 Disk Array, one Dell R740 Linux server and one KVM. Server
in Old airport is master. Server in Kirkos is backup one.
The EMS system should be able to quickly recover from disasters. When the active site fails to
function properly due to earthquakes, floods or snow disasters, the standby site should be able to
take over the charge of all the operations and continue the uninterrupted service to subscribers.
The active site should be far away from the standby sites so that the mentioned disasters cannot
affect both of the sites at the same time.
It is implemented by deploying the active EMS system, HA fault-tolerant software, and the standby
EMS system. Generally, O&M personnel can perform the remote backup and restore operations
from a subordinate network O&M center. Compared with local two-server redundancy, the remote
1+1 redundancy solution has two characteristics:
The active and standby sites are monitored by third-party products so that when one fails,
applications on it can be switched over to the other immediately.
Third-party products are used to implement remote data replication between the active and
standby sites.
Before the occurrence of failure, two EMS systems A and B have the same capabilities on which all
EMS applications and databases have been installed. But only A which is active to provide the
management service. If A fails to function properly due to disasters, B will takes over the charge as
the active site and continues the delivery of the services.
To supervise the condition of EMS servers and enable data replication and switchover between
them, we need to install a HA software system. The software configuration for a remote 1+1
redundant system is shown below:
Table 6-49 Software Deployment for Remote 1+1 Redundant System (Server-based)
7 Service Deployment
ZXA10 C300M supports voice services in NGN/IMS based on H.248 and SIP, including
POTS/ISDN voice, FAX, MODEM, PBX, and various supplementary services. From the view of
voice service, ZXA10 C300M acts as an AG (Access Gateway) in NGN/IMS.
When deployed in the softswitch based NGN, the ZXA10 C300M/C350M will be under the control
of the softswitch through H.248 or SIP protocol. When deployed in IMS, the ZXA10 C300M will be
under the control of the P-CSCF through SIP protocol or under the control of the AGCF through
H.248 or SIP protocol. In NGN/IMS, the ZXA10 C300M is acting as an AG to support various voice
related services, such as VoIP (voice over IP), FoIP (FAX over IP), MoIP (MODEM over IP),
through various subscriber interfaces ,such as POTS, ISDN BRA, and ISDN PRA.
ZXA10 C300M supports broadband access services based on copper, such as ADSL/2/2+, VDSL2, and
SHDSL.bis, with enhanced DSL features, to provide users with various broadband services such as
High Speed Internet (HSI) and video service.
The dial-up data of the users are transmitted transparently to the BRAS equipment via MSAG, or GPON
network, the BRAS sends the relevant authentication information and billing information to the AAA
server, after the authentication is passed, the BRAS allocated IP addresses for the users.
The STB of the IPTV user gets the IP address via DHCP or PPPoE, whether the request of On Demand
programs needs the authentication of the AAA server. After the user information authentication has
passed, IPTV platform forwards corresponding multicast flows to corresponding MSAG, or GPON
network.
ZXA10 C300M GPON card supports up to 16 GPON interfaces. A single shelf supports up to 128 GPON
interfaces, supports a split ratio of 1:128 and can be connected with up to 16384 ONUs.
8 DATA planning
EMS
Server 111128-OA-CS-A em1 Gei-0/7/0/39
Old EMS
Gei-0/7/0/40
airport Server 111128-OA-CS-A em2
EMS
Gei-0/7/0/41
Server 111128-OA-CS-A em3
EMS
Gei-0/7/0/42
Server 111168-KK-CS-B em1
EMS
Gei-0/7/0/46
Kirkos Server 111168-KK-CS-B em2
EMS
Gei-0/7/0/47
Server 111168-KK-CS-B em3
EMS 255.25
Heartbe
Serve 10.204.204.203 5.255. Em3 Float 3760
VRRP at ip
r 248
10.204.2
PE-A
10.204.2
04.36
VRRP
10.204.2
04.38
Rin
Site uplink CS device CS port
g
111010_Bole_Mch
GigabitEthernet8/0/3
ael_ASG_A
6 New MSAG_839
111010_Bole_Mch
GigabitEthernet8/0/3
ael_ASG_B
111767_Kality_AS
New MSAG_2301 GigabitEthernet8/2/0
G_A
8
111408_Akaki_AS
New MSAG_14 GigabitEthernet8/0/2
G_A
111057_Addis_Ket
GigabitEthernet8/2/1
ema_ASG_A
9 New MSAG_630
111057_Addis_Ket
GigabitEthernet8/2/1
ema_ASG_B
111055-AD-CS-A xgei-0/2/0/4
10 New MSAG_485
111055-AD-CS-B xgei-0/2/0/4
111165_Ayat_ASG
New MSAG_2504 GigabitEthernet8/0/4
_A
11
111086_Kotebe_A
New MSAG_1639 GigabitEthernet8/0/4
SG_A
111120_Hanamari
GigabitEthernet8/2/0
am_ASG_A
12 New MSAG_1913
111120_Hanamari
GigabitEthernet8/2/0
am_ASG_B
111089_Gerji_AS
GigabitEthernet8/0/4
G_A
13 New MSAG_1102
111089_Gerji_AS
GigabitEthernet8/0/4
G_B
VOI
BB MGMT
Ri P MGMT IP MGMT IP of MGMT &
site SVLA VLAN of VOIP IP VOIP GW
ng VLA of C300M ZXDU68 B301 DU GW
N C300M
N
2 New 2590 229 2299 10.109. 10.109.23 10.109.232.1 vrf FL vrf OAM
MSAG_80 234.1/2
10.109.234. 10.109.23
8 8 8 2.1/27 1/27
14 2.30
7 New 2391 229 2299 10.109. 10.109.23 10.109.232.1 vrf FL vrf OAM
MSAG_20 8 234.97/ 2.161/27 70/27
10.109.234. 10.109.23
2 28
110 2.190
10 New 2691 229 2297 10.109. 10.109.23 10.109.233.8 vrf FL vrf OAM
MSAG_48 MSAG_32234.145
2 2611 3196 3646 10.109.234. 10.109.23
5 3.1/28 /28
5 MSAG_321 /28 2667 3195 3645 158 3.14
MSAG_808
10.109. 2529 3123 3621 vrf FL vrf OAM
New 229 10.109.23 10.109.233.2
MSAG_25 2410 2297
MSAG_8 234.161 2539
12 3125 3627 10.109.234. 10.109.23
6 3.17/28 4/28
04 2 MSAG_830 /28 2511 3133 3622 174 3.30
MSAG_720
10.109. 2499 3107 3607 vrf FL vrf OAM
New 229 10.109.23 10.109.233.5
13 MSAG_11 2601 2293 234.193 2427
MSAG_870 3102 3602 10.109.234. 10.109.23
2 3.49/28 5/28
02 MSAG_804 /28 2499 3120 3634 206 3.62
5
MSAG_805 2435 3121 3619 vrf FL vrf OAM
New 10.109.
229 10.109.233136
10.109.233.7
MSAG_46 2689 2296 234.209 2497
MSAG_855 3620
10.109.234. 10.109.23
4 3.65/28 2/28
9 6 MSAG_839 /28 2721 3207 3601 222 3.78
14
MSAG_202 2613 3101 3607
10.109. vrf FL vrf OAM
New 229 10.109.233100
10.109.233.7
MSAG_201 2611 3606
MSAG_49 2690 2296 234.210 10.109.234. 10.109.23
74 MSAG_203 /28 3.66/28 3102 3/28
2557 3608
0 222 3.78
MSAG_222 2603 3119 3625
For example:
ZXAN#configure terminal
ZXAN(config)#set-pnp enable
ZXAN(config)#vlan 2405,2298,2299-2301,2615,3180,3310,3630
ZXAN(config-vlan)#exit
ZXAN(config)#interface xgei_1/19/1
ZXAN(config)#interface xgei_1/20/1
ZXAN(config-if)#exit
ZXAN(config-if-vlan100)#exit
ZXAN(config)#spanning-tree enable
ZXAN(config-mstp)#revision 10
ZXAN(config-mstp)#name MSAG_Ring01
ZXAN(config-mstp)#exit
ZXAN(config)#interface gei_1/19/3
ZXAN(config)#interface gei_1/20/3
ZXAN(config)#interface smartgroup1
ZXAN(config)#interface gei_1/19/3
ZXAN(config)#interface gei_1/20/3
ZXAN#write
ZXAN#configure terminal
ZXAN(config)#
ZXAN(config)#vlan 2300-2301,2615,3180,3310,3630
ZXAN(config-vlan)#exit
ZXAN(config-if)#exit
ZXAN(config)#interface gei_1/9/1
ZXAN(config-if)#exit
ZXAN(config)#interface gei_1/9/2
ZXAN(config-if)#exit
ZXAN(config)#interface smartgroup1
ZXAN(config-if)#exit
ZXAN(config)#interface gei_1/9/1-2
ZXAN(config-if-range)#smartgroup 1 mode on
ZXAN(config-if)#exit
ZXAN(config)#interface smartgroup1
ZXAN(config-if)#end
ZXAN(config)#vlan 1000-1200
ZXAN(config-vlan)#exit
ZXAN(config)#interface adsl_1/3/1-16
ZXAN(config-if-range)#exit
This profile does not exist. Would you like to create? [y/n][y]y ZXAN(config)#adsl profile 2Mprofile
AtucConfRateMode(1-fixed,2-adaptAtStartup,3-adaptAtRuntime):[2] AtucConfRateChanRatio(0..100%):[0]
AtucConfTargetSnrMgn(0..310(0.1dB)):[80] AtucConfMaxSnrMgn(80..310(0.1dB)):[310]
AtucConfMinSnrMgn(0..80(0.1dB)):[0] AtucConfDownshiftSnrMgn(0(0.1dB)):[0]
AtucConfUpshiftSnrMgn(0(0.1dB)):[0] AtucConfMinUpshiftTime(0..16383s):[0]
AtucConfMinDownshiftTime(0..16383s):[0] ConfProfileLineType(1-fast-only,2-interleaved-only):[2]
AtucChanConfFastMaxTxRate(0..131040kbps):[1024] AtucChanConfFastMinTxRate(0..1024kbps):[32]
AtucChanConfInterleaveMaxTxRate(0..131040kbps):[1024]2048
AtucChanConfInterleaveMinTxRate(0..1024kbps):[32] AtucChanConfMaxInterleaveDelay(0..255ms):[16]
AturConfRateMode(1-fixed,2-adaptAtStartup,3-adaptAtRuntime):[2] AturConfRateChanRatio(0..100%):[0]
AturConfTargetSnrMgn(0..310(0.1dB)):[80] AturConfMaxSnrMgn(80..310(0.1dB)):[310]
AturConfMinSnrMgn(0..80(0.1dB)):[0] AturConfDownshiftSnrMgn(0(0.1dB)):[0]
AturConfUpshiftSnrMgn(0(0.1dB)):[0] AturConfMinUpshiftTime(0..16383s):[0]
AturConfMinDownshiftTime(0..16383s):[0] AturChanConfFastMaxTxRate(0..10240kbps):[512]
AturChanConfFastMinTxRate(0..512kbps):[32] AturChanConfInterleaveMaxTxRate(0..10240kbps):[512]
AturChanConfInterleaveMinTxRate(0..512kbps):[32] AturChanConfMaxInterleaveDelay(0..255ms):[16]
AtucDMTConfFreqBinsOperType(1-open,2-cancel):[2] AturDMTConfFreqBinsOperType(1-open,2-cancel):
[2] LineDMTConfEOC(1-byte ,2-streaming ):[1]
ZXAN(config)#interface adsl_1/3/1-16
ZXAN#configure terminal
ZXAN(config)#vlan 1401
ZXAN(config-vlan)#exit
ZXAN(config)#interface gei_1/9/1
ZXAN(config-if)#no shutdown
ZXAN(config-if)#exit
SN : 0019c6000011
LOID : 0019c6000011
ZXAN(config)#interface epon-olt_1/4/1
ZXAN(config-if)#exit
ZXAN(config)#interface epon-onu_1/4/1:1
ZXAN(config-if)#exit
ZXAN(config)#pon-onu-mng epon-onu_1/8/1:1
ZXAN(epon-onu-mng)#end
ZXAN#configure terminal
ZXAN(config)#msag
ZXAN(config-msag)#exit
ZXAN(config)#vlan 3180
ZXAN(config-vlan)#
ZXAN(config-vlan)#voip-ctrl
ZXAN(config-vlan)#voip-bind
ZXAN(config-vlan)#exit
ZXAN(config)#
ZXAN(config)#interface gei_1/9/1
ZXAN(config-if)#
ZXAN(config)#exit
ZXAN#write
9 Power Solution
9.1 Overview
In the current fix line network, there two types of FL equipment, MSAG 5200(in NGN
project) and MSAG C300M (in TEP project). For existing MSAG sites, the power
system and MSAG have an integrated design, and has worked more than ten years.
The rectifier system is facing the shortage of spare parts, and the batteries are coming
to end of life.
At the same time, the rectifier system, the batteries and MSAG share the total space.
This design has leaded the internal temperature rising, and the batteries will work in
poor environment condition.
According to the environment of Ethiopia and the requirement from the upgraded MSAG, the
new power system should be designed for this project. The new power solution should provide
the main following functions:
Rectifier and battery spaces are independent with separated cooling system. The rectifier space
will adopt the heat ex-changer and the battery space will use DC air conditioner.
1. heat ex-changer inside of main equipment rack: power consumption is 200W, the heat
dissipation ability is 1800W.
2. heat ex-changer inside of main power system rack: power consumption is 100W, the heat
dissipation ability is 1000W.
3. air-conditioner inside of battery rack: power consumption is 320W.
Advanced rectifier system can provide more powerful functions, such as modular design, higher
efficiency (≥95% (peak efficiency); ≥94.5%(full load); ) power system, and fast charging.New cycling
batteries :ZXDC12 HL170 (170AH)to against the poor commercial power condition. Refer to PD
of battery.
Enough battery capacity guarantees backup time, and improves the customer experience and
network KPI.
The battery configuration is 3 banks of 170AH battery, based on the different load, back up time will be
change:
1.1-----Redundancy factor
I1----load current
MSAG Load Backup time(h) MSAG Load Backup time(h)
≤ 20A ≥ 23.2 26A 17.8
21A 22.1 27A 17.2
22A 21.1 28A 16.6
23A 20.2 29A 16
24A 19.3 30A 15.5
25A 18.5 ≥30A ≤ 15
This function can ensure that the MSAG load will work maximum time after the grid power off.
a) LLVD1 connect for the common loads, like the heat ex-changer, DC cooling
system and so on. Those equipment will be firstly down when the voltage drop
to LLVD1 voltage 45v.
b) BLVD for the important loads, like MSAG. Those load will be off when the
battery voltage drop to 43.2V(BLVD), and the important loads will be closed if
the AC power still not recovered.
The ZXDU68 B301 system is a 6U height, 19-inch width embedded DC power system.
The system can provide power to -48 V series communication equipment. When fully
configured, the system is equipped with four ZXD3000 rectifiers and can provide a
rated output current of 200A.
ZXD3000 power module can support high efficiency, in the sleep mode, the output
power of the rectifier is lower than 4W.
ZXDC12 HL series battery can achieve a high charge rate of 0.32C 10 , and has
excellent deep cycle performance with 1500 cycles@60%DOD at 25℃.The designed
life is 12 years.
U31 server
IP NETWORK
ip
IP network
NE
10 Acronyms
Table 10-56Acronyms
Acronyms English
Asymmetric Digital
ADSL
Subscriber Line
AC Alternating Current
AG Access Gateway
Dynamic Bandwidth
DBA
Allocation
DC Direct Current
Element Management
EMS
System
GE Gigabit Ethernet
Hypertext Transfer
HTTP
Protocol
Internet Group
IGMP
Management Protocol
IP Internet Protocol
Internet Protocol
IPTV
Television
Integrated Services
ISDN
Digital Network
International
Telecommunication
ITU-T Union -
Telecommunication
Standardization Sector
MG Media Gateway
Media Gateway
MGC
Controller
MSAG Packet
MPRB Processing & Resource
CardType B
Multi-Service Access
MSAG
Gateway
NE Network Element
Optical Distribution
ODF
Frame
Optical Distribution
ODN
Network
Public Switched
PSTN
Telephone Network
Real-time Transport
RTP
Protocol