Cdot Maxng Migration Man V02 PDF

C-DOT MAX-NG
MAX-TO MAX-NG
MIGRATION MANUAL
CENTRE FOR
DEVELOPMENT OF TELEMATICS
Section No.431-316-1061
System Issue 02 May 2017
Practices
C-DOT MAX-NG
MAX-TO MAX-NG
MIGRATION MANUAL
© 2017, C-DOT
Printed in India
C-DOT MAX-NG
MAX TO MAX-NG MIGRATION MANUAL
ISSUE 02
MAY 2017
JYESTHA 2073
SERIES 100: PLANNING
CSP SECTION NO. 431-101-1061
THIS C–DOT SYSTEM PRACTICE REFERS TO THE C–DOT DIGITAL
SWITCHING SYSTEM MAIN AUTOMATIC EXCHANGE NEXT GENERATION
(ABBREVIATED AS C-DOT MAX-NG IN THE REST OF THIS PUBLICATION).
THE INFORMATION IN THIS SYSTEM PRACTICE IS FOR INFORMATION
PURPOSES AND IS SUBJECT TO CHANGE WITHOUT NOTICE.
ANY FEEDBACK ON THE DOCUMENT MAY BE SENT AT
MXNGPMTC@CDOT.IN.
© 2017 BY C–DOT, NEW DELHI

Table of Contents
CChapter 1. Introduction ................................................................................................................................. 5
1.1. Overview ................................................................................................................................ 5
1.2. NGN Core Network ............................................................................................................... 5
1.3. NGN Access Network............................................................................................................6
1.4. BSNL C-DOT MAX Network................................................................................................ 6
1.5. Migration PLAN of MBM to MAXNG .................................................................................. 6
Chapter 2. Pre-Retrofit Activity – Core Network ...................................................................................... 8
2.1. Pre-Requisites ....................................................................................................................... 8
Chapter 3. Pre-Retrofit Activity – Access Network ................................................................................. 21
3.1. Steps for Access Site Migration TO MAXNG .................................................................... 21
3.2. Pre Requisites ..................................................................................................................... 21
3.3. Physical Installation of Cacu System ................................................................................ 22
3.4. Network Related Configuration and Testing .................................................................... 23
3.5. Extraction of Data from IOP for Different BM’S .............................................................. 26
3.6. Preparation of NGTJ Cards (LAG) for Different BM’S/RSU ........................................... 26
Chapter 4. Physical Installation of LAGU System ................................................................................. 28
4.1. BM Migration to LAG ......................................................................................................... 28
Chapter 5. Exchange Details and IP Allocation of 48 Access Sites to be Migrated by BEL/ECIL
with C-DOT ................................................................................................................................. 32
5.1. Udalguri (ASSAM Circle) ................................................................................................... 32
5.2. Billawar (J&K Circle) .........................................................................................................33
5.3. Joshimath (UTTARAKHAND Circle) ................................................................................ 34
5.4. Nalagarh (HP Circle) ..........................................................................................................36
5.5. Nurpurbedi (PUNJAB Circle) ............................................................................................ 38
Annexure - 1 List of SDCAs Proposed for Migration by ECIL/BEL /C-DOT.......................................... 40
Annexure - 2 Automated Installation & Configuration Manual for Cacu Cards (SLM/NGTJ/EBM)
(For XEYEPL1_1_2.12_1 Release) .......................................................................................... 42
Annexure - 3 LAG/V5AG Data Extraction Procedure ................................................................................ 55
Annexure - 4 IP Address Details & Exchange Data of Sites Proposed to be Migrated ...................... 81
Annexure - 5 IP Address Configuration IN MLS Card ............................................................................. 83
Annexure - 6 C-DOT MAX-NG Network Connectivity ............................................................................... 84
H:\HOME\NG-MAX\User\FinalCDOT-MAXNG-MIGRATION-MAN-V02.doc May 29. 2017

Chapter 1.
Introduction
1.1. OVERVIEW
The MAX-NG network is an IP based platform for delivery of voice, video, data and
multimedia services to subscribers. It supports seamless traversal of calls between
IP, PSTN and PLMN networks.
The MAX-NG network is structurally divided into the following four sub-network
segments:
 NGN Core Network for delivery of Services
 NGN Access Network consisting of MAX exchanges upgraded to MAX-NG
exchanges
 Operations Support Network consisting of
i. MAX-NG Billing System Interface
ii. MAX-NG Service Provisioning Interface
iii. MAX-NG Network Management
 The existing IP/MPLS based NIB/NIB-II Transport Network
1.2. NGN CORE NETWORK
The NGN Core Network handles all Session Establishment, Call Processing and
Service Delivery functions centrally. The core network consists mainly of following
servers.
 C5 Softswitch
 C4 Softswitch
 Session Border controller (SBC)
 Rating Engine
 SG Server
 EMS Server
 LIS Server
 NOC
MAX-TO MAX-NG MIGRATION MANUAL 5

Chapter 1.
1.3. NGN ACCESS NETWORK

The NGN Access Network is the C-DOT DSS MAX exchanges upgraded to MAX-
NG. After the upgrade to MAX-NG, the Base Processor Unit and Time Switch Unit
in Base Modules of MAX exchanges are no longer required. Only TSI cards from
Time switch unit will be required and terminal Units (TU) which terminate PSTN
subscribers are retained for providing migration of existing users to MAX-NG. The
TUs are connected to a new unit called the Line Access Gateway (LAG). The LAG
converts PSTN connections to SIP/IP sessions and forwards them to a central
software based switching exchange (Soft switch).
Central Access Control Unit (CACU Chassis): Every Central Module of MBM
system will be converted to CACU System with 6-Slot Chassis which will house 02
Nos. of Network Access Gateway Cards (for SG/MG/V5/PRI applications), 02 Nos. of
Main LAN Switch (C-DOT Aggregator) and 02 Nos. of Ethernet to E1 Main Card
along with Shelf Manager (SLM) Card.
1.4. BSNL C-DOT MAX NETWORK
The whole BSNL Network administratively and technically partitioned into 24
Telecom Circle. Most of the telecom circles are equivalent to states except UP-E
&UP- W, NE-1 & NE-2 and the head quarter of telecom circles are mainly the
capital of the state. SDCA is the smallest administrative division of telecom. In
every SDCA there is a Main exchange. Remote exchanges or RSU’s are parented to
SDCAs main exchange and some rural exchanges i.e. AN-RAX/WLLs are also
parented to Main exchanges of SDCA. The main exchanges (ILT Exchange) are
connected to L2 TAX of SSA over CC7 interface. C-DOT MBM is working at most of
the SDCAs and as per the migration plan, every C-DOT MBM will be converted to
MAX-Next Generation (i.e. MAX-NG).All SDCA MBMs which are comprise of Local
BMs, Remote BMs, AN-RAXs, WLLs & PRI PBXs will became Access Equipment
and will be a part of access network. At every SDCA a CACU chassis will be
installed, a detail description of CACU is discussed in the later section of this
document. The access network will be controlled by centrally located C-DOT Soft
switch i.e. core network. Each CACU will be directly connected to IPTAX over IP
wherever possible otherwise it will be connected to next higher level exchange or
IPTAX over SS7.
1.5. MIGRATION PLAN OF MBM TO MAXNG
There will be a total of 8 core sites having MAXNG core equipment’s. as mentioned
in section 1.2 Al four zones of India i.e. North, South, East & West will have 2 core
sites each .One site will act as Primary site & other site will act as geographical
redundant site for that Primary site and vice versa
North Zone will have two sites at Gurgaon and Chandigarh.
South Zone will have two sites at Bengaluru and Hyderabad.
West Zone will have two sites at Bhopal and Pune.
6 C-DOT MAX-NG
INTRODUCTION
East Zone will have two sites at Cuttack and Kolkata.

In each circle two sites will be migrated by BEL & ECIL teams with the help of C-
DOT Thus a total 48 SDCAs of 24 circles (See Annexure 1) are planned to be
migrated by BEL & ECIL with the help of C-DOT.
Circle level BSNL teams designated for further conversions of sites in their
respective circles will be trained hands on these two sites in respective circles.
Each exchange will take around 15 days for migration including pre-retrofit
activity, migration to MAXNG and AT of the site.
The list of 48 sites to be migrated by BEL/ECIL with help of C-DOT along with IP
details can be referred from annexure 4.
The migration strategy has been planned in such a manner so as to minimize the
actual system downtime.
The data of sites to be migrated will be created offline in advance at core sites in
softswitch & rater.
The downtime will be from 90 to 120 minutes on an average for each BM. During
migration downtime will be there for BM being migrated only. Other BM’s will
continue to work in normal manner. Thus a total partial downtime of a complete
MBM will vary depending on the number of BM’s working and depending on the
BM’s being converted parallel or sequentially due to availability of trained
manpower for migration.
During migration the BM’s migrated to LAGU will be able to make outgoing calls
only as incoming route will be activated only after complete site migration. So
incoming calls to BM converted to LAGU will be activated only after all BM’s of the
site are converted.

Chapter 2.
Pre-Retrofit Activity – Core Network

2.1. PRE-REQUISITES
The sites to be migrated will be identified beforehand The corresponding data of
sites to be migrated will be created in core network elements like C5 & C4 before
actual migration of site to minimise the downtime of services to existing subscribers
.
The site will be created in C5 along with an operator with Admin rights by the core
operator.
The login id & default password for the sites will be informed by core operator to all
site administrators
The site operator will login to the soft switch with given login id & default password
for the site.
On first login the site operator shall change his password & login to softswitch with
changed password.
The core operator or the site operator can create corresponding LAG’s with given IP
addresses for the site in soft switch
All current access site BM data has to be compiled into a file using a utility
provided by C-DOT and same has to be injected to softswitch.
2.1.1. C5 Softswitch
 Data creation in Soft switch is done using soft switch GUI (super user by
C-DOT only) till the creation of site administrator. After the creation of
site administrator, the credentials will be shared to the BSNL operators
(SDCA specific) to create/modify/delete subscribers. Following is an
example of the same for NUH (SDCA site) in Haryana:-
Access the C5 GUI of the particular zone using URL:-https://<ip>/softswitch
COUNTRY CREATION
INDIA
91
8 C-DOT MAX-NG
PRE-RETROFIT ACTIVITY – CORE NETWORK
STATE CREATION
STATE NAME : HARYANA
STATE CODE : HA

Chapter 2.
CITY CREATION
CITY CREATION : NUH
CITY CODE : 1267
10 C-DOT MAX-NG
AREA CODE GROUP CREATION

AREA CODE GROUP NAME : C5GROUP_NORTH
AREA CODE : 1267

Chapter 2.
ROUTE DEVICE CREATION

ROUTING DEVICE NAME : C4_NORTH
ROUTING DEVICE IP&PORT : 10.187.0.29:5060
ROUTING DEVICE TYPE : C4
12 C-DOT MAX-NG
GROUP CREATION
GROUP NAME: GROUP_HA

Chapter 2.
OPERATOR CREATION
LOGIN NAME : Admin_1267
OPERATOR PASSWORD : Admin123
EXCHANGE CODE : 271,278,274,275
14 C-DOT MAX-NG
ZONE CREATION
{ LOG IN WITH OPERATOR }
ZONE NAME : NZ1267

Chapter 2.
LAG ADDITION
LOG IN WITH OPERATOR
LAG NAME : LAG_NUHU
LAG IP : 10.187.212.38
LAG PASSWORD : 1234
16 C-DOT MAX-NG
LAG ADDITION
LAG NAME : LAG_UJJINA
LAG IP : 10.187.212.46
LAG PASSWORD : 1234

Chapter 2.
LAG ADDITION
LAG NAME : LAG_PARA
LAG IP : 10.187.212.54
LAG PASSWORD : 1234
18 C-DOT MAX-NG
LAG EXCHANGE MAP

LAG_NUH:271 274
LAG_UJJINA: 275
LAG_PARA: 278
BILLING INFO
PRIMARY SERVER IP: 10.187.0.18 (IP OF RATER)
PRIMARY SECRET: secret

Chapter 2.
All current access site BM data has to be compiled into a file using a utility
provided by C-DOT and same has to be injected to softswitch. (as per the
annexure attached)
At this point site in charge of access has to be informed that after injection of
site data at soft switch all the modifications done at site data has to be
recorded manually in a register on daily basis.
After site migration is complete, then the site in-charge has to do
modification of all manual records into CDOT MAXNG system by his login id.
2.1.2. C4 Softswitch
All specific levels of a particular SDCA have to be opened to respective
IPTAXs/L2TAX/L1TAX in C4 softswitch.
20 C-DOT MAX-NG
Chapter 3.
Pre-Retrofit Activity – Access Network

3.1. STEPS FOR ACCESS SITE MIGRATION TO MAXNG
3.2. PRE REQUISITES
i. Receiving of MAX-NG Equipment (as per BoM)
a) Login to the C-DOT Project Management site & click on MAX-NG
Project Management option on top. (URL-
http://www.cDOThelpline.ernet.in) as per the SDCA login.
b) Download the BoM of SDCA.
c) Check the list of received material as per BoM.
ii. Verify the Site Survey Document already prepared & the list of received
material as per BOM.
iii. Verification of the IP addresses as per the Web-portal data for respective site
for all the Access hardware.
For migration of LAGU and CACU sites, please watch installation videos
before proceeding further which can be downloaded on official website of C-
DOT http://www.cDOThelpline.ernet.in/
a) At home page click MAX-NG PROJECT MANAGEMENT
b) Login to your account
c) Click on the Documents
d) Select VIDEOS
3.2.1. IP Address requirement for access equipments:
MAX-NG ACCESS NODES IP ADDRESS REQUIREMENTS and allocations
as per the following sequence:
I. 2 IP addresses for the SDCA in the range allocated will be used as
follows:
a) 1 Network IP address (1st IP address in the allocated range for
SDCA) and
b) 1 Broadcast IP address (Last IP address in the allocated range
for SDCA)

Chapter 3.
II. 6-Slot Chassis CACU: One CACU is required for every exchange
(MBM or SBM) to be migrated to MAX-NG. Each CACU requires 24 IP
addresses as follows:
a) 2 MLS cards : 6 IP addresses ( 3 IPs for each MLS card ).The
three IP addresses allocated for each MLS are as follows:
i. One Gateway IP for the Network to which the core network is to
be connected.
ii. One Gateway IP for other side of Network connectivity to BSNL.
iii. One IP for Software management.
b) 2 SLM cards : 3 IP addresses (one floating IP and 2 physical IPs)
c) 2 EEB cards : 2 IP addresses (one for each)
d) 2 NGTJ cards : 12 IP addresses (6 IP addresses for each NGTJ
card as given below):-
i. 1 physical IP address (eth0) for each NGTJ card
ii. 1 DSP IP address for each NGTJ card
iii. 4 virtual IP addresses for 4 Gateway applications in the order
MG, SG, V5 and PRI
d) Client terminal IP Addresses : 1
 Total IP addresses per CACU: 24 (6+3+2+12+1)
III. 2-Slot Chassis LAGU: Each BM/RSU will be replaced with one
LAGU. Each LAGU has two copies of LAGs for support of duplex mode.
A total of seven IP addresses are required for each LAGU as follows:
a) 1 physical IP for each LAG card.
b) 1 IP for each DSP interface in both the LAGs.
c) 1 Floating IP for the LAGU.
d) 1 fixed IP each for Mate eth1 link communication between 2
LAGs.
e) Total IPs addresses per LAGU : 7 (2+2+1+2)
 Total IP Address required for each SDCA = 2+ 24 + 7* (No. of LAGU)
3.3. PHYSICAL INSTALLATION OF CACU SYSTEM
Find a spare BM in which CACU System is to be installed and do the following
activities:-
1. Switch OFF the power of the Rack.
2. Remove all the TT, TB and power cables.
3. Remove the filter boxes.
22 C-DOT MAX-NG
PRE-RETROFIT ACTIVITY – ACCESS NETWORK
4. Unscrew and remove all the frames of rack.

5. Now install the new filter box at Copy 0 and Copy 1 side of Bus bar.
6. For physical installation of CACU chassis a fixture needs to be installed first.
The fixture will be installed at 2nd and 3rd TU position in a BM, which will be
required to hold the CACU chassis in vertical direction.
7. Install the CACU chassis in this vacant space. Put the CACU chassis in the
fixture, now place this frame support assembly and screw it properly.
8. At the top of the MAX-NG BM i.e. at first TU’s position, put a card cage
without backplane, of any spare frame to mount a DDF TAG block for the
termination of the E1/PCMs being used in the MAX-NG system.
9. There are PCM cables delivered with the CACU chassis for the termination of
E1’s to the new MAX-NG hardware i.e. NGTJ or EBM.
10. Now connect the power cable for copy-0 and copy-1 of CACU chassis to the
newly installed filter box and make sure that the cables are connected properly.
NOTE: The existing E1s from the AN-RAXs, IP-TAX, PRI, RSUs etc. are
currently routed to the Trunk BM or VU BM or Central Module (CM) of the
exchange. Now we need to identify these E1s at the Cable entry point and
during the migration when the Central Module will be shut down re-route
the E1s to this newly installed TAG block. Make sure that the length of E1
cables is sufficient to reroute them to the TAG block during migration. Till
the central module is shut the existing E1’s (connected to DTU’s as trunks)
will work in normal manner while other E1’s will be disconnected from CM
and connected to CACU (in case when a RSU is being migrated) and E1’s will
be disconnected from BM having VU (V5.2 unit) and connected to CACU (in
case when an ANRAX is being migrated)
From TAG Block, these E1 cables are to be extended through a PCM cable to
the respective connectors at the back plane of CACU that is 3C, 4C, 5C and
6C.
Slot 3C and 4C are for the termination of TAX/POI E1s, AN-RAX E1s and
PRI E1s to the NGTJ card depending upon which
application(SG/MG/V5AG/PRIAG) is installed in the NGTJ card. Slot 5C and
6C are for the termination of RSU E1s to EBM card as per the requirement.
3.4. NETWORK RELATED CONFIGURATION AND TESTING
i. Jack in delivered cards in each slot of CACU chassis.
ii. Connect Thin Client to MLS card and assign IP address to thin Client if not
configured.
For assigning the IP address to thin client do the following:
Go To setting
Select Network setting Select IPV4

Chapter 3.
Select Connection Name CDOT-MAX-NG (Give Any Name to The

connection)
Select Method type Manual
Address Give any spare IP from the allocated IP
addresses of this site
Netmask Give netmask of subnet
Gateway Give default Gateway address.
iii. MLS cards are powered on by itself, when jacked-in the CACU Chassis.
iv. Access MLS cards through minicom and configure IP in MLS card.
Note: Refer MLS installation document for the same. (Annexure-3)
v. Install optical patch cord between one optical port of each MLS card and
BSNL switch (OCLAN/T2/T1 SW) for reachability with BSNL MPLS
network.
vi. Configure the MLS card for Uplink connectivity to MPLS.
vii. Configuration at BSNL MPLS end is also required. This has to be done by
MPLS NOC.
viii. After the configuration, the bidirectional connectivity between the Access site
and core site shall be tested by Pinging the TEST-IP of the MAX-NG core site
node. For the IP addresses of core network, please refer IP address list of
corresponding Zone.
ix. Ensure the reachability by pinging the IP address of IPTAX, SSTP, CDR and
MAX-NG core.
From the thin client prompt do the following
# ping 192.168.3.72 (where 192.168.3.72 is the IP of IPTAX)
Following print will appear if the connectivity is through.
PING 192.168.3.72 (192.168.3.72): 56 data bytes
64 bytes from 192.168.3.72: icmp_seq=0 ttl=64 time=5.080 ms
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 2.362/3.188/5.080/1.111 ms
Similarly ping the IP addresses of corresponding SSTP,CDR and MAX-NG
core and verify that their connectivity is through with this access site.
x. Verify IP addresses of other cards as well i.e. SLM, EBM and NGTJ.
24 C-DOT MAX-NG
For verifying the IP of the NGTJ card login in to the card through serial
cable, a root prompt will appear. At the prompt do the following.
root@NGTK] cd /jffs2/conf
root@NGTK] cat net
/sbin/ifconfig eth0 down
/sbin/ifconfig eth0 10.187.3.228 netmask 255.255.255.0 broadcast
10.187.3.255
/sbin/route add default gw 10.187.3.2
/sbin/ifconfig eth0 10.187.3.228 up
All the IP’s should be as per the allocated list. The modification can be done
through vim editor if required
xi. Install applications in all the cards delivered with CACU chassis.
Please refer CACU Installation Procedure Document (Annexure-3)
xii. Login to SLM, NGTJ, EBM and check processes once cards come UP. For
checking processes, refer installation manual of CACU system.
xiii. After installation of CACU chassis and insertion of cards, connect configured
SIP phone to MLS card.
For configuring the IP phone select CONFIG from the menu, and define the
following
Number = 91-1360-250000 [Country code -Area code- Subscriber
number]
This number and the reg password must be created in the C5 softswitch first
PASS = **** [Default registration password 0000]
Select IP allocation type STATIC.
Give the valid IP against IP =10.197.5.175
Give the valid netmask against NETMASK =255.255.255.0
Give the valid Gateway IP against G/w =10.197.5.175
Give reboot from the menu.
xiv. Make a call from SIP phone to core site to test speech and signalling.
One test Number is already created and available at the core site of that
ZONE which can be called to check the speech quality.
xv. Make all types of calls i.e. Local and STD to PSTN/PLMN networks.
The routing data for each SDCA will be already created in the C4 softswitch
therefore all the PSTN/PLMN network must be reachable and call should be
successful.

Chapter 3.
3.5. EXTRACTION OF DATA FROM IOP FOR DIFFERENT BM’S

1. Data will be extracted from IOP, through “IOP DATA EXTRACTION
UTILITY”. This utility can be downloaded from Helpline portal
http://cDOThelpline.ernet.in
2. The above utility will generate the following output:-
a) Gateway Bulk data generation utility.
b) Subscriber data file for core.
c) Frozen subscriber list.
d) File containing miscellaneous information (for e.g. Area Code, Site ID,
TTC equipage information, etc.)
Note: Refer DATA EXTRACTION MANUAL for LAG (ANNEXURE-4)
3. By running the above utility the cmd files for the data creation for V5AG will
also be generated which will be required to create data related to AI and its
subscriber.
Note: Refer DATA EXTRACTION MANUAL for V5AG (ANNEXURE-4)
3.6. PREPARATION OF NGTJ CARDS (LAG) FOR DIFFERENT BM’S/RSU
1. First jack out NGTJ card from CACU chassis i.e. 3rd slot of CACU chassis.
2. Jack in NGTJ card which has to be prepared for LAGU site.
3. Access NGTJ card through serial RS-232 (minicom cable) and check net file
in /jffs2/conf/net file. Follow the sequence of commands to access net file, the
IP’s in the net file should be as per the IP allocation for that LAG.
# mount /dev/mtdblock0 /jffs2
# cd /jffs2/conf
# cat net
# chmod 777 net
4. Assign IP address of LAG card as per the IP list in the net file of same NGTJ
card. Refer IP address list for the same.
5. Gracefully shutdown and reboot NGTJ card so that it can be accessed on
same IP segment.
6. Ping IP address of NGTJ card i.e. self IP address of NGTJ card in the net file.
7. Prepare mmc in the NGTJ card and card should come UP and check Level 5
of NGTJ card at the same time.
Create data for specific BM from files which were extracted from IOP.
8. Prepared NGTJ card has to be installed in the specific BM for which this card
is prepared.
26 C-DOT MAX-NG
9. Shutdown NGTJ card and jack out from CACU chassis. LABEL site name,
copy of specific BM, IP address and BM number. Similarly, prepare NGTJ
cards for all co-located BMs and RBMs.
10. NGTJ card which was earlier working can be inserted back in the same slot
of CACU chassis. Check processes again in NGTJ card.
11. All prepared NGTJ cards have to be installed in the specific BM for which
these cards are prepared.
12. After migration, the PCM’s from RSU’s and TAX need to be diverted to the
TAG block installed in the MAX-NG BM itself.
13. Before migration some of the PCM’s from TAX can be diverted to TAG block
and for PCM connectivity of RSUs, PCM cable can be laid from the
Exchange’s DDF to the TAG block of CACU system.
This is to note that uptill now the existing MBM will be working with CM in normal
manner and no downtime for the site will be there.

Chapter 4.
Physical Installation of LAGU System

On following steps mentioned in this chapter actual system downtime will start and
normally it shall vary from 90-120 minutes per BM at the site.
4.1. BM MIGRATION TO LAG
1. Note down the status of all TIC’s,TSI’s working in the BM i.e. which copy of
TIC/TSI is active and which copy is standby(if TIC’s and/or TSI’s are in
duplex). Also Take a note of the status of Announcement card and TTC card.
2. This is important because we will bring the LAGU( after conversion of BM it
will become LAGU) up with same set of TIC and TSI copies as active and
standby.
3. Shut off the Power of the BM to be migrated.
4. Un-screw the BPU and TSU frame.
5. Remove the cables connected at the back plane of TSU and BPU. These
cables are TT cables, TB cables and power cables.
6. Remove the filters of BPU and TSU frames from the BUS BAR.
7. Pull out the TSU and BPU frames from the BM cabinet.
8. Install the new filter box in place of BPU filter boxes at Copy 0 and Copy 1
side of Bus bar. First the yellow cable will be connected to the black bus
bar. Then after installing the filter box, Blue cable will be connected to blue
point and red to the red point of filter box.
9. For physical installation of LAGU chassis fixture needs to be installed first,
which will be required to hold the LAGU chassis in vertical direction. Now in
this space install the LAGU chassis
10. Put the LAGU chassis in the fixture and screw it properly.
11. Connect the TT cables; TT cables at TU side will remain same. At LAGU end
TT cables have to be connected in position 1A, 1B, 2A and 2B connector in the
same way as it was connected in the TSU of MAX BM.
12. Now we will connect the power cable for copy-0 and copy-1 of LAGU chassis
and make sure that the cables are connected properly to the newly installed
filter box of LAGU chassis.
For TSI cards the power is to be fed from ATU’s . The TSI power cables at
LAGU end will be connected to the D-Type connectors , two D-Type
connectors respectively for copy-0 and copy-1 of TSI cards are given at the
28 C-DOT MAX-NG
PHYSICAL INSTALLATION OF LAGU SYSTEM
back plane of LAGU chassis. The other end of the TSI power cable will be
connected at the back plane of ATU motherboard, behind any LCC card slot
B, Tab3 and Tab4. These TSI power csbles, for copy-0 and copy-1 should be
connected to different ATU’s to provide redundancy to the TSI cards.
In this power cable, red is 5 Volts DC and it can vary between 5 to 7 volts.
The black cable is Digital ground and the yellow cable is -12 Volts which can
vary from -10 to -15 Volts.
Before connecting these TSI power cables at LAGU mother Board, power-ON
the ATU’s and verify the voltages at the connector through multimeter. The
voltage must be as per the specified range. In case you are not getting the
desired voltage the connectors should be tried in different LCC slot. After
verifying these voltages, we will connect these TSI power cables at LAGU
motherboard in the given positions.
13. In case of local connectivity through serial cable we will connect client PC /
Thin client through the minicom cable i.e. RS232 cable. This serial cable has
to be connected in this position, for copy-0 of LAG card and for copy-1 this
cable will be connected here.
14. The LAG converts the TDM voice samples to IP based VoIP packets. These IP
packets are then uplinked towards Main LAN switch of MBM site through
Ethernet cable in case of collocated BM. The Ethernet cables will be
connected here at eth1 port of LAG -0 and in this position for copy-1 card of
LAG. If both the copies of LAG are inserted, then this Ethernet cable can be
connected in any of these ports.
In case of RSU’s it may be possible that the transport medium is E-1. In that
case the existing PCM cable of RSU can be directly connected at tab-1
position of 3A and 4A connectors. The Ethernet cable for uplink is not
required in that case. But if the RSU has STM connectivity then eth cable
can be used for unlinking in the same way as it is done in Co-located BM.
15. Now insert the NGTJ cards in the given slots corresponding to copy-0 and
copy-1 and similarly the TSI cards are inserted in their respective slots. The
NGTJ card here are working as a Line Access Gateway.Line Access Gateway
converts Time Division Multiplexed voice sample to Voice Packets. These
NGTJ card will be delivered to site with pre-installed software, root file
system, configuration and system data etc. as per site specific requirement.
The pre-configured data is stored in the storage device of NGTJ card i.e.
Micro SD card. .
16. Now after the cards are inserted Switch-ON the power of all the ATU's
and LAGU. The prints in the minicom terminal will appear showing the
booting sequence and then wait for the LAG to come UP.
17. When the LAG comes up make intra LAG, PSTN & PLMN calls and verify
that proper CDR’s are being made in soft switch.

Chapter 4.
18. If CDR’s are not proper or calls are not through then either fix the problems
or revert back the LAGU to BM as a fall-back option. In this scenario call the
CDOT helpline for assistance before going for fall-back option.
19. When all LAGU’s of the exchange comes up then power off the CM and now
create incoming routes in IPTAX corresponding to these LAGU’s so that
incoming calls are also through.
20. Make inter Lag, intra LAG, PSTN & PLMN calls and verify that proper
CDR’s are being made in soft switch.
21. Now the installer can test all tests mentioned in AT schedule of
LAGU,CACU-1and CACU-2(if applicable to that site) and if all test are
working then the site can can be offered for AT. If some test are failing then
fix the tests before offering it to AT
Table 1 below displays the activities to be performed & approximate no. of days
required for migration of one exchange to MAX-NG.
Table 2: Planned activities for MAX to MAX-NG migration (one exchange)
CACU Hardware and Software Installation and making IP Connectivity of
MAX Site to BSNL MPLS N/W 4 DAYS
1 CACU Physical Installation
2 Last Mile connectivity between MAX-NG MLS in CACU and T2/T1
Network/IP Configuration between SDCA and Core switch by Data
3 Network NOC and verification
Network Data Creation in Class-4 SS for connectivity of SDCA to
4 L2/L1 TAX and POIs
PSTN & PLMN call testing from SIP Phone and alternate ISUP
5 Connectivity
Retrofit data preparation for MAX to MAX-NG migration for Core
6 and Access Nodes
7 Installation of CACU DDF
8 Termination of alternate media PCM's towards distant exchange.
Configuration w.r.t Billing and Provisioning through BSNL CDR
9 system
LAGU's Hardware and software Installation at co-located and RSU Site 5 DAYS
1 Physical Installation of LAGU at collocated BM & RBM
2 Configuration of Line Access Gateways.
30 C-DOT MAX-NG
PHYSICAL INSTALLATION OF LAGU SYSTEM
3 Termination and configuration of ANRAX's & PRI's to CACU

Post Migration verification Checks of MAX Site 2 DAYS
1 Testing of Different Call scenarios, PCO Calls etc.
2 Verification of processing of CDR & Interworking with CLARITY
A/T and commissioning of MAX Site 4 DAYS
1 Successful Completion of Acceptance Testing of SDCA
2 Taking Over Certificate by BSNL
3 Commissioning of the site
Total No. of DAYS for Migration of one MAX exchange 15 DAYS

Chapter 5.
Exchange Details and IP Allocation of

48 Access Sites to be Migrated by
BEL/ECIL with C-DOT
5.1. UDALGURI (ASSAM CIRCLE)
Exchange Details
SITE NAME : UDALGURI
CIRCLE : ASSAM
SSA : TEZPUR
SDCA : UDALGURI
AREA CODE : 03711
1. No. of Co-located BM 01
2. No. of RSU’s 02
RSUs with IP NIL

connectivity
RSUs without IP 02
connectivity
3. Availability of spare BM Rack (If spare BM is not available 01

then before migration any Trunk BM will have to be made
spare)
4. No. of AI Interface 07
5. No. of PRI Links NIL
6. No. of BRI subs NIL
7. SS7 links and number of links. If it is towards IPTAX/TAX IPTAX-GHY-1
Kindly specify the name of IPTAX/TAX TZP-TAX-02
8. No. of PCMs Working in each direction 03
9. No. of PCM towards POI(if any) NIL
10. Availability of GE Port at ADM or T1/T2 SW/ and approximate 2 GE Ports available
distance of GE port from switch room. 15 meters from switch
room.
32 C-DOT MAX-NG
EXCHANGE DETAILS AND IP ALLOCATION OF 48 ACCESS SITES TO BE MIGRATED BY BEL/ECIL WITH C-DOT
Equipment & IP Address Allocation

As per the given information total No.s of line BM (Co-located) and RSUs = 3
Total No.s of LAGU = 3
Therefore the NGTJ required for Line Access Gateways 1x2 = 02 of type (B00)
NGTJ cards required for Line Access Gateways for RSUs 2x2 = 04 of type (A00)
NGTJ cards required of type B00 for (MG, V5AG, PRIAG) = 02
Note: Type A00 is EEB (Ethernet to E-1 converter) integrated while type B00 is
without EEB.
Total No. of LAGU = 03
Total No. of IP required =2 +24+7*3 =47
Therefore an IP pool of 64 addresses will be allocated for this site.
Range of IP addresses assigned 10.187.24.128 to 10.187.24.191 and subnet mask
255.255.255.192
Note:- For specific IP addresses of each LAGU/CACU system , refer Annexure-5
5.2. BILLAWAR (J&K CIRCLE)
Exchange Details
SITE NAME : BILLAWAR
CIRCLE :J&K
SSA : JAMMU
SDCA : BASHOLI
AREA CODE : 01921
2. No. of RSU’s 03
RSUs with IP NIL

connectivity
RSUs without IP 03
connectivity
3. Availability of spare BM Rack (If spare BM is not available YES

spare)

Chapter 5.

7. SS7 links and number of links in each direction. If it is IPTAX
towards IPTAX/TAX Kindly specify the name of IPTAX/TAX JALANDHAR
04-LINKS
10. Availability of GE Port at ADM or T1/T2 SW/ and approximate YES
distance of GE port from switch room. 20 Mtrs.

As per the given information total No. of line BM (Co-located) and RSUs = 4
without EEB.
255.255.255.192
Note:- For specific IP addresses of each LAGU/CACU system, refer Annexure-6
5.3. JOSHIMATH (UTTARAKHAND CIRCLE)
Exchange Details
SITE NAME : JOSHIMATH
CIRCLE : UTTARAKHAND
SSA : SRINAGAR
SDCA : JOSHIMATH
AREA CODE : 01389
34 C-DOT MAX-NG
Line BM 01
Trunk BM 01
VU BM 01
2. No. of RSU’s NIL
RSUs with IP NIL

connectivity
RSUs without IP NIL

connectivity
3. Availability of spare BM Rack (If spare BM is not available NIL

spare)

7. SS7 links and number of links in each direction. If it is JAIPUR, 04 LINKS
towards IPTAX/TAX Kindly specify the name of IPTAX/TAX LUCKNOW, 01 LINK
10. Availability of GE Port at ADM or T1/T2 SW/ and approximate GE PORT ZTE T1
distance of GE port from switch room. SW, 40 Metres, TWO
PORTS, GIGA
OPTICAL PORT
WITH 1.2G
WAVELENGTH SFP

Chapter 5.

without EEB.
255.255.255.192
Note:- For specific IP addresses of each LAGU/CACU system , refer Annexure-6.
5.4. NALAGARH (HP CIRCLE)
Exchange Details
SITE NAME : NALAGARH
CIRCLE : HP
SSA : SOLAN
SDCA : NALAGARH
AREA CODE : 01795
1. No. of Co-located LINE BM 3 nos. ( BM-1 has 3
racks , BM-2 has 2
Racks & BM -5 has 2
Racks)
2. No. of RSU’s 10 (including one RSU-12 with ITU frame only)
RSUs with IP nil

connectivity
RSUs without IP 10
connectivity
3. Availability of spare BM Rack (If spare BM is not available 2 (one without frames)
spare)
36 C-DOT MAX-NG
5. No. of PRI Links 1 in SUM BM-3

6. No. of BRI subs 11 in SUM BM-3 & 24
in RSU-12
7. Specify every direction of SS7 links and number of links in NLG-SOL TAX – 4 nos.
each direction. If it is towards IPTAX/TAX Kindly specify the NLG-SMLWLL MSC- 1
name of IPTAX/TAX nos.
RELINCE POI- 2 nos.(2
POI TOWARDS
RELIANCE )
TATA POI – 1 no.
Vodafone POI – 1 no.
Airtel POI – 1 nos.
8. No. of PCMs Working in each direction 6 PCM TO SOLAN TAX
1 PCM TO WLL SML
5 PCM TO 5 PIO
9. No. of PCM towards POI(if any) 5 PCM TO 5 POI
10. Availability of GE Port at ADM or T1/T2 SW/ and approximate 1 no. GE port with 1310
distance of GE port from switch room. nm SFP
Distance-40 mtrs

As per the given information total No.s of line BM (Co-located) and RSUs = 13
Total No.s of Lagu = 13
without EEB.
255.255.255.128

Chapter 5.
5.5. NURPURBEDI (PUNJAB CIRCLE)

Exchange Details
SITE NAME : NURPURBEDI
CIRCLE : PUNJAB
SSA : ROPAR
SDCA : NANGAL
AREA CODE : 01887
1. No. of Co-located LINE BM 1
2. No. of RSU’s 5
RSUs with IP 3
connectivity
RSUs without IP 2
connectivity
3. Availability of spare BM Rack (If spare BM is not available NO

spare)
5. No. of PRI Links/E1 LINKS 1 E1 LINK EPABX

6. No. of BRI subs
7. Specify every direction of SS7 links and number of links in 6
each direction. If it is towards IPTAX/TAX Kindly specify the
name of IPTAX/TAX
8. No. of PCMs Working in each direction 1pcm to aps,1 pcm
ngl,6 tax
9. No. of PCM towards POI(if any) NO
10. Availability of GE Port at ADM or T1/T2 SW/ and approximate YES DISTANCE 25
distance of GE port from switch room. MTRS APROX
38 C-DOT MAX-NG

NGTJ cards required for Line Access Gateways for RSUs = 5x2 = 10 of type (A00)
without EEB.
255.255.255.128

Annexure - 1
List of SDCAs Proposed for Migration

by ECIL/BEL /C-DOT
Proposed first phase migration of total 48 SDCAs of in circles
CIRCLE SITE LBM RSU ANRAX PRI
Andhra Pradesh Dharmavaram 1 2 7 0

Hindupur 3 6 13 2
Indiranagar 8 3 0 0
Karnataka
Bangarpet 1 2 3 0
Kodungallur 5 0 0 0
Kerala
Payyanur 0 6 0 0
Kagal 1 2 7 3
Maharashtra
Lonavala 1 1 2 0
Tamil Nadu Tiruvattipuram 2 1 7 2

Denganikotta 2 1 6 0
nurpurbedi 1 5 3 1
Punjab
Morinda 2 6 1 1
Tosham 0 0 8 2
Haryana
Siwani 0 1 6 0
Chhata 1 3 6 1
UP WEST
Sadabad 0 2 9 0
Nalagarh 3 8 14 1
HP
Poanta 3 6 10 0
UP EAST Dumariyaganj 5 1 8 1
Bansi 2 1 14 2
Chamoli 3 2 6 1
UK
Joshimath-I 2 0 2 0
RAJASTHAN Gangapur 1 2 7 5
40 C-DOT MAX-NG
LIST OF SDCAS PROPOSED FOR MIGRATION BY ECIL/BEL /C-DOT
CIRCLE SITE LBM RSU ANRAX PRI

Bhilwara 5 1 8 0
Samba 2 2 3 0
J&K
Billawar 1 1 6 0
BIHAR Simri Bakhtiarpur 1 1 9 0

Supaul 2 2 8 0
Koraput 2 3 10 1
ORISSA
Gunupur 2 1 8 0
Gumla 2 0 7 1
JHARKHAND
Lohardaga 2 2 7 0
BURDWAN (GALSHI ) 1 2 10 2
WEST BENGAL
BURDWAN (BHATAR) 2 1 10 0
PASSIGHAT 5 2 3 0
N.E.- II
TAWANG 3 0 5 0
Tura 2 5 8 0
N.E.-I
Jowai 2 2 2 0
Mangaldoi 2 3 9 2
ASSAM
Udalguri 1 2 7 0
Port Blair 5 5 12 1
ANDAMAN
Diglipur 1 1 5 0
MP Bina 1 3 2 1
Sagar 2 5 15 0
Rajnangaon 2 7 21 2
Chhatisgarh
Balod 1 2 9 0
Patel colony, Jamnagar 2 6 13 1

Gujarat
Mehul Nagar, Jamnagar 2 10 12 0

Annexure - 2
Automated Installation & Configuration

Manual for CACU Cards
(SLM/NGTJ/EBM) (For
XEYEPL1_1_2.12_1 Release)
PRE-REQUISITES:
Before proceeding to actual installation, firstly following pre-requisites should be
checked and ensured:
1) INFORMATION REGARDING THE FOLLOWINGS:
A range of 24 IP addresses to be used in the CACU chassis (Start and End IPs).
Gateway Addresses, Broadcast Address and Netmask.
IP addresses of NGEMS Manager and NGSM Server.
IP address of one linux machine to be used as NTP server for date and time sync to
the CACU cards. It shall be ensured that ntpd daemon is configured and running on
the machine.
2) Following is one example of 24 IP addresses range
(192.168.115.229 to 192.168.115.252) with distribution of these IP to the MAX-NG
CACU cards :
(Gateway Address 1: 192.168.115.231, Gateway Address 2: 192.168.115.234,
Broadcast Address: 192.168.115.255 and Netmask:255.255.255.0)
 MLS Card (Slot-7) Gateway IP : 192.168.115.229 (Start IP + 0)
 MLS Card (Slot-7) Management IP : 192.168.115.231 (Start IP + 2)
 MLS Card (Slot-8) Management IP : 192.168.115.234 (Start IP + 5)
 SLM (Shelf Manager) (Active Copy) FVIP : 192.168.115.235 (Start IP + 6)
 SLM (Shelf Manager) (Slot-1) Card IP : 192.168.115.236 (Start IP + 7)
 SLM (Shelf Manager) (Slot-2) Card IP : 192.168.115.237 (Start IP + 8)
 EBM (Slot-5) Card IP : 192.168.115.238 (Start IP + 9)
42 C-DOT MAX-NG
AUTOMATED INSTALLATION & CONFIGURATION MANUAL FOR CACU CARDS (SLM/NGTJ/EBM) (FOR XEYEPL
 EBM (Slot-6) Card IP : 192.168.115.239 (Start IP + 10)

 NGTJ (Slot-3) IPs
 Card IP = 192.168.115.240 (Start IP + 11)
 DSP_IP =192.168.115.241 (Start IP + 12)
 TMG_IP=192.168.115.242(Start IP + 13)
 SGL2_IP=192.168.115.243(Start IP + 14)
 V5_IP=192.168.115.244(Start IP + 15)
 PRI_IP=192.168.115.245(Start IP + 16)
 NGTJ (Slot-4) IPs
 Card IP = 192.168.115.246 (Start IP + 17)
 DSP_IP =192.168.115.247 (Start IP + 18)
 TMG_IP=192.168.115.248(Start IP + 19)
 SGL2_IP=192.168.115.249(Start IP + 20)
 V5_IP=192.168.115.250(Start IP + 21)
 PRI_IP=192.168.115.251(Start IP + 22)
 IP For Thin-Client Terminal/PC = 192.168.115.252 (Start IP + 23)
3. Ensure that the LATEST PSG DELIVERABLE VERSIONS (for uboot,
dtb, Linux Image and RFS) and latest FPGA version loaded on the CACU
cards :
Refer to Steps in the Appendix-A for fusing the PSG deliverables (uboot, Image, rfs
and dtb)
a) SLM card :
New SLM cards having following support are to be used :
 FPGA ver 5 POF file SLM-U2-VER5.pof (as displayed in “fpga” command)
 MAXNG SLM PSG environment ver 1.07 (displayed as MAXNG SLM
Console Rel 1.07 in /etc/issue ) for new SLM card version SLM-AE2
(Chassis Version)
 FCL PCB should be one which has only FAN support and not
FAN+POWER-SUPPLY support from same register.
Sr. Deliverable-Name Size(in bytes) Checksum
1. SLM.u-boot.bin.VER17 (UBOOT) 386764 3549688794
2. SLM.uImage.VER17 (LINUX 2012475 3842143430
IMAGE)
3. SLM.dtb.VER17 (DTB) 6832 1913953694
4. SLM.rfs.s.VER17 (RAM-RFS) 15100203 1546615846
5. SLM-U2-VER5.pof 524492 2000988671

Annexure - 3
b) CACU NGTJ card:

 FPGA V21 POF file NGTJ_VER21.pof (as displayed in “fpga” command).
 MAXNG NGTJ PSG Environment ver 1.52 (displayed as MAXNG NGTK
Console Rel 1.52 in /etc/issue) which contains uboot, linux image, dtb and
ram-rfs.
S/no Deliverable-Name Size(in bytes) Checksum
1. NGTJ.u-boot.bin.VER52 369880 1475384766
(UBOOT)
2. NGTJ.uImage.VER52 (LINUX 3806124 2389537443
IMAGE)
3. NGTJ.dtb.VER52 (DTB) 10055 3563750536
4. NGTJ.rfs.s.VER52 (RAM-RFS) 19078430 933627270
c) RFS V05 for MMC/NAND (MXNG-NGTJ-LTIB-V05.tar)

EBM card:
 FPGA ver 6 file ebmj22_VER6.pof (EBM_FPGA-V06)
 MAXNG EBM PSG Environment ver 1.09 (displayed as MAXNG EBM
Console Rel 1.09 in /etc/issue) which contains uboot, linux image, dtb and
ram-rfs.
S/no Deliverable-Name Size(in bytes) Checksum
1. EBM.u-boot.bin.VER18 (UBOOT) 386276 4217636884
2. EBM.uImage.VER18 (LINUX 2001528 2438892729
IMAGE)
3. EBM.dtb.VER18 (DTB) 6470 3467466183
4. EBM.rfs.s.VER19 (RAM-RFS) 14747787 3158571756
5. ebmj22_VER6.pof 524492 483868767
4. Allocate the unique MAC addresses and IP addresses to the CACU

cards for accessing these cards from the thin-client/PC for automated
installation of applications:
MAC-Address Setting:
 Using minicom or known existing IP; login to the CACU card through root
user and give command ‘ifconfig’ to check the allocated MAC address against
‘HWaddr’ for the eth0(for EBM & NGTJ) or eth1(for SLM) interface. In case
the desired MAC address is not set as per the serial number of card in MAC-
Mgmt System; then set the correct MAC address through uboot (See step#6
below under “PROCEDURE TO FUSE UBOOT AND
RFS/DTB/KERNELFILE USING TFTP SERVER” for setting the MAC
address of SLM/EBM cards)
44 C-DOT MAX-NG
IP-Address Setting:
 For SLM cards IP settings (eth1 port is used)
 #mount -t jffs2 /dev/mtdblock5 /jffs2
 #cd /jffs2/conf
 open ‘net’ file and edit with following 2 lines using ‘vi’ and save the net file
(using :wq commad on vi editor)
ifconfig eth1 <SLM-CARD-IP-ADDR> up
route add default gw <Gateway-IP-Addr>
 give execute permission to net file using command : # chmod +x net
 execute net file to set the card ip address: # ./net
 For NGTJ card IP settings; eth0 port is used
 #mount /dev/mtdblock0 /jffs2
 #cd /jffs2/conf
 open ‘net’ file and edit with following 2 lines using ‘vi’ and save the net file.
ifconfig eth0 <NGTJ-CARD-IP-ADDR> up
 For EBM card IP settings (eth0 port is used )
 #mount -t jffs2 /dev/mtdblock5 /jffs2
 #cd /jffs2/conf
 open ‘net’ file and edit with following 2 lines using ‘vi’ and save the net file
(using :wq commad on vi editor)
ifconfig eth0 <EBM-CARD-IP-ADDR> up
cd /cdot/bin
./bcm_rst
 For MLS card IP settings; set the VLAN1 (native default VLAN) IP
address. See Appendix-C for reference.

Annexure - 3
5. Files to be downloaded from CRS:

 The files will be downloaded from the CRS in form of two zip files, one
containing the application software release tar files of XEYEPL1_1_2.12_1
release and the other having the NGTJ driver release.
 All the release and patch deliverables for SLM, NGTJ and EBM.
 SLM card applications:
1. CACU-SLM.tar or equivalent Patch consisting of
a) SLM_DELIV.tar
b) CACU_DELIV.tar
2. SLM Chassis Agent Release or Patch File
3. install_cacu_cards.sh (Script Responsible for Auto Installation)
 NGTJ Card applications:
1. ngtj.tar
2. NGTJ_DELIV.tar
3. PRIAG Release Tar file or Patch Tar file
4. SGL Release Tar file or Patch Tar file
5. AGL Release Tar file or Patch Tar file
6. CDTMG-NGTJ-CACU Release Tar file or Patch Tar file
7. NGTJCardAgent Release Tar file or Patch Tar file
8. PRI Agent Release Tar file or Patch Tar file
9. V5AG Agent Release Tar file or Patch Tar file
10. TMG Agent Release Tar file or Patch Tar file
 NGTJ card PSG drivers:
1. NGTJ_DRIVER_CACU-REL Tar file (Under Integrated Release
NGTJ_DRIVERS-REL)
2. install_ngtj_drivers.sh (Under Integrated Release NGTJ_DRIVERS-
REL)
 EBM card applications:
1. ebm Card Agent Release or Patch TAR file
2. eeb manager Release or Patch TAR file
3. Patch for showing VLAN on EBM cards
 Deliverables Information Text Files (Used for checking size of tar files)
1. XEYEPL1_1_2.X_1-Deliverables.txt having size information of
all applicable product release tar files.
46 C-DOT MAX-NG
2. NGTJ_DRIVERS-REL3-Deliverables.txt having size information

about following:
a) NGTJ_DRIVER_CACU-REL3.tar
b) install_ngtj_drivers.sh
INSTALLATION STEPS TO BE USED ON LINUX THIN-CLIENT / PC
1. Downloading Required deliverables from CRS :
a) Go to website www.crs.cdotd.ernet.in with proper login and password.
b) In Left frame, Click on the option “Integrated Release” followed by
“Download Deliverables”.
c) Out of available three options, Click on option “By Selecting File”
d) For main CACU Application software Deliverables, Select
following Values from listed options:
Project=MAX-NG ,
Integrated Release = XEYEPL1_1_2.X_1
File = XEYEPL1_1_2.X_1-Deliverables.txt
Out of the two available options “Download Hierarchically” and “
Download in Single Directory”, Click on the latter option i.e.
“Download in Single Directory”.
In window appeared, Go for “Save File” option and ZIP File named as
XEYEPL1_1_2.X_1.zip will be saved in local machine (from where
Web Browser was run) at mentioned path. This zip file contains all
required TAR files required for installation (Refer Appendix F)
For example, if X=12; Contents of ZIP File XEYEPL1_1_2.12_1.zip
1. XEYEPL1_1_2.12_1-Deliverables.txt
2. agl1_1_3.4_1.tar
3. CDTMG-NGTJ-CACU-1_1_1.8_1.tar.gz
4. ebml1_1_1.6_1-EBMCardAgent.tar
5. eebrel_1.6.tar
6. PATCH2-Over-EBML1_1_1.6_1-show_vlan.tar
7. gwyagentl3_1_1.5_1-NGTJCardAgent.tar
8. gwyagentl3_1_1.5_1_tmg_agent_ngtj.tar
9. gwyagentl3_1_1.5_1_v5ag_agent_ngtj.tar
10. gwyagentl3_1_1.5_1_pri_agent_ngtj.tar
11. ngtj.tar

Annexure - 3
12. priagl1_1_2.5_1.tar
13. NGTJ_DELIV.tar
14. sgl1_3_1.8_1.tar
15. install_cacu_cards.sh
16. CACU-SLM.tar
17. slml1_1_1.5_1-ChassisAgent.tar
Contents of ZIP File NGTJ_DRIVERS-REL3.zip
1. NGTJ_DRIVERS-REL3-Deliverables.txt
2. NGTJ_DRIVER_CACU-REL3.tar
3. install_ngtj_drivers.sh
a) For NGTJ Card Deliverables (which are to be installed during
software installation), Select following values from listed options :
Project=NGTJ Card Drivers Deliverables
Integrated Release = NGTJ_DRIVERS-REL3
File = NGTJ_DRIVERS-REL3.Deliverables.txt
Out of the two available options “Download Hierarchically” and
“Download in Single Directory”, Click on the latter option i.e.
“Download in Single Directory”.
ZIP File named as NGTJ_DRIVERS-REL3.zip will be saved in local
machine (from where Web Browser was run).
b) For downloading installation script file install_cacu_cards.sh, use the
following steps
i) Log in to CRS with a valid user name and password.
ii) Go to ‘Display All Integrated Release Details’ in the left hand
side pane.
iii) Select Project as MAX-NG.
iv) Go to integrated release XEYEPL1_1_2.X_1 and from there,
SLML1_1_1.X_1.
v) From there, download the script named as
‘install_cacu_cards.sh’
vi) Login at the PC/thin client (PC-RJ) as root user (Mandatory)
and make some directory (say CACU).
48 C-DOT MAX-NG
1. Make sure that following files downloaded from CRS in Step-1 are available
at current path (eg /root/CACU) either by copying in USB or though network
transfer such as ftp, scp etc.
a) XEYEPL1_1_2.X_1.zip
b) NGTJ_DRIVERS-REL3.zip
c) install_cacu_cards.sh
d) cacu_sys.conf (Optional, configuration file formed during any previous
installation having same configuration values)
2. Ensure execution permission and then Run "install_cacu_cards.sh" script
as follows :
chmod +x install_cacu_cards.sh
./ install_cacu_cards.sh
Script will interactively ask for some conformations and values.
Major activities done by this script are as above :
a) Unzipping XEYEPL1_1_2.X_1.zip & NGTJ_DRIVERS-REL3.zip files
and copying the respective TAR files in appropriate folders like
CACUrel/NGTJ, CACUrel/EBM and CACUrel/SLM.
b) Checking the size availability of 1 GB at the host machine / Thin
Client.
c) Verification of the Sizes of deliverables TAR files in reference to
deliverables info text files.
d) If cacu_sys.conf file is not present, then Asking the entries for
configuration, to be used in the various cards of CACU.
(Configuration-Type =1 for MAX-NG Network),
e) After taking all configuration input parameters, a list of recommended
physical card IPs for all CACU Cards will be displayed. Operator has
to be ensured only these IPs for respective Cards.
Note: If not SET, then access the card through minicom, make entry in
/jffs2/conf/net file for setting that IP and reboot the card.
3. Three configuration/Installation options are displayed :
1. For Installation and configuration
2. For Installation Only (No Configuration Changes)
3. For Configuration Only (No Release Installation)

Annexure - 3
4. Three Cards Types are displayed :

1. SLM
2. NGTJ
3. EBM
Recommended sequence is First SLM Cards and then NGTJ or EBM cards.
1. After giving card type, Physical IP of the Card is to be provided (as
mentioned in step 4.e) followed by user-name and password information.
2. After this, Space availability at the given SLM/NGTJ/EBM Card is verified,
FPGA & PSG Release Version are asked to be confirmed. Card is shutdown,
Deliverables are transferred to the card and after installation, processes are
started at that card
3. After this step, Some Card wise configuration/installation specifics are asked.
Like for NGTJ card,
a) Option regarding installation of ngtj/v5ag/priag/mg modules
b) Configuration parameters required for above applications etc are
asked.
c) In the end of installation, reboot is to be given.
For SLM card
a) Simplex/Duplex Configuration is asked.
b) Mate SLM copy public key setting related information is asked.
4. After this installation at a card is complete, go for the next card or exit.
Information about various parameters asked during auto-installation:
 Configuration:
1 for MAX-NG means CACU having at max 2 SLM, 2 EBM, 2 NGTJ and
2 MLS.) (2 for Red Network means CACU having at max 2 SLM, 4 EBM
and 2 MLS.)
 Start IP: The initial IP address of the IP range to be used in the CACU.
 End IP: The last IP address of the IP range to be used in the CACU.
 Gateway IP, Broadcast and Netmask are self explainatory.
 Offset: It is the number of IPs not used in the range for some reason, though
it is 0.
 System Name: Name of the CACU to be used for display in NGEMS, e.g.
CACU.
 Region Name: Region name used in NGEMS, eg North_HA etc.
 Number of EMS managers: It is the number of the NGEMS used.
50 C-DOT MAX-NG
 IP Address of EMS Manager(s): These are the IP addresses of the NGEMS

servers to be used. It will be limited by the entry filled above, viz the
"Number of EMS managers".
 IP Address of the NTP server: IP address of the NTP server to be used for
time sync.
 Periodicity: The periodicity of syncing of time in CACU cards with NTP
server, filled in seconds, preferably above 900.
NOTE:
 After selecting the card, information regarding the card are also shown
such as available space, FPGA and PSG release version, which should be
checked and only after it is confirmed for the release, installation should
be proceeded.
 Other information: The installation uses ssh without password at the
linux-PC/Thin-client from which the remote installation is done and thus
requires to be run as the root user.
 At least 1.5 GB space should be present on the machine from which
installation is done for a smooth operation.
 In case of any error, an error file will be generated.
PROCEDURE TO FUSE UBOOT AND RFS/DTB/KERNELFILE USING TFTP
SERVER
On the server ip (PC) :
Note: server ip linux PC is the machine in which, at the /tftpboot path; the latest
DTB, RFS, UBOOT and Kernel-Image files loaded for fusing into the SLM/EBM
cards
1. Login with root user on the server IP; say 20.0.1.100
2. ftp the latest linux-Image, Uboot, RFS and DTB files at path /tftpboot
Over the SLM/ EBM CARD:
1. Connect the serial cable from linux PC to the RS232 port of the SLM card
and start the minicom from the PC.
2. Login to SLM with root account
3. Reboot the SLM card (using command ‘reboot’)
4. When the message "Autoboot in 6 seconds. Hit 'a' to stop from Autoboot" is
displayed; press ‘a’ to stop the boot sequence.
5. Type the command "pri" to view the already set environment variables.

Annexure - 3
Also, any variable can be changed using the command:

"set <variable name> <value>". After each change, it is advised to save the new
value using command "saveenv".
1. Set the Ethernet port eth1 MAC address as follows (as allocated for the SLM
card serial number in MAC Management System: Refer Appendix-B) :
Command for SLM: "set eth1addr <eth1-mac-addr in Hexadecimal>"
Command for EBM: "set ethaddr <eth0-mac-addr in Hexadecimal>"
Note: for EBM card ethaddr has to be set.
2. Set the active ethernet port eth1(for SLM) & eth0(for EBM) to be used as
follows
Command for SLM: "set ethact FSL UEC1"
Command for EBM: "set ethact FSL UEC0"
3. Set serverip as the ip address of the tftpserver (from where the
dtb/rfs/uboot/kernel to be fused into SLM card)
Command: "set serverip <ip address of tftpserver>".
1. Set applicable gatewayip.
Command: "set gatewayip <gateway ip>".
2. Set netmask.
Command: "set netmask <value>".
3. Set ipaddr of the card as such to make it communicable with the above
tftpserver.
Command: "set ipaddr <ip_address>".
Note: The following commands in steps below assume SLM VER16/ EBM
VER15 as the new environment release for SLM. These files should be
present on the said tftpserver.
4. Set the kernelfile as the new uImage file.
Command for SLM: "set kernelfile SLM.uImage.VER17"
(Command for EBM: "set kernelfile EBM.uImage.VER18")
5. Set rfsfile with the new rfs file of SLM.
Command for SLM: "set rfsfile SLM.rfs.s.VER17".
(Command for EBM: "set rfsfile EBM.rfs.s.VER19".)
6. Set dtbfile as the new version of the dtb file.
Command for SLM: "set dtbfile SLM.dtb.VER17".
(Command for EBM: "set dtbfile EBM.dtb.VER18".)
52 C-DOT MAX-NG
7. Set ubootfile with the new version of u-boot file.

Command for SLM: "set ubootfile SLM.u-boot.bin.VER17".
(Command for EBM: "set ubootfile EBM.u-boot.bin.VER18". )
1. Save the above values. Command : "saveenv". This can also be done
after above steps.
2. Check if the entered tftpserver is communicable with the card using
ping.
3. Command: "ping <tftpserver ip>".
For the tftpserver that is pingable, following should be the output:
"host <tftpserver ip> is alive". Note that for SLM, ethact must be FSL
UEC1, as described in step 5, else connectivity from SLM fails.
4. To fuse uboot, use the following command:
Command: "run FUSE_UBOOT".
It will take around 2 sec.
8. Then to fuse the DTB/RFS and Linux Image on SLM use fuse SLM command
as follows:
Command: "run FUSE_SLM"
It will take around 3-4 minutes.
(Command for EBM : “run FUSE_EBM”)
9. After these are complete, enter command reset to boot the card with the fused
PSG deliverables.
Command: "reset"
10. Let the card boot, login with root to the SLM and check the new version
using: "cat /etc/issue"
It should display:
Welcome to MAXNG SLM Console Rel 1.07
cat /cdot/bin/commands to know list of commands supported on SLM
( Where 1.07 is the new release just fused.)
11. Now reformat jffs2
Command: "flash_eraseall -j /dev/mtd5"
12. Mount jffs2.
Command: "mount -t jffs2 /dev/mtdblock5 /jffs2"
13. Make a directory named conf in jffs2 and make a file named net inside it.
Commands:

Annexure - 3
# cd /jffs2
# mkdir conf
# cd conf
# vi net
14. The file ‘net’ should contain the entries of the ip address to be allocated to the
card. Thus following lines should be put in it.
The following sets of commands are for the SLM card
ifconfig eth1 down
ifconfig eth1 <ip address> up
route add default gw <gateway ip>
(save the file and exit the editor using ‘wq’)
For the EBM card, the eth device should be replaced with eth0 instead of
eth1 above.
In the /jffs2/conf/net file of the EBM cards, the following additional entries
are to be added at the end
cd /cdot/bin
./bcm_rst
15. Give execute permissions to the net file and execute it.
Commands:
# chmod +x net
# ./net
16. Give command ‘ifconfig’ to verify the MAC-Address, IP address, GW
Address, Netmask and Broadcast address set.
17. In case the MAC address is changed due to loading of latest PSG deliverables
images (uboot/rfs/dtb/linux); then reboot the card again and press ‘a’ on uboot
and change the MAC address as follows in uboot :
Command for SLM: "set eth1addr <eth1-mac-addr in Hexadecimal>"
Command for EBM: "set ethaddr <eth0-mac-addr in Hexadecimal>"
18. The processes that can be checked (after auto installation) on SLM card are:
shm.exe and snmpd (chassisagent). On EBM they are: eeb_manager.exe,
eeb_i2c_agent.exe and snmpd (ebmcardagent).
19. On the active shelf manager (SLM card), shmiltest.exe (present at
/jffs2_ram/SLM/bin) can be used for CLI view after a successful automated
installation.
54 C-DOT MAX-NG
Annexure - 3
LAG/V5AG Data Extraction Procedure

Software Retrofit Philosophy and Pre-Retrofit Checks
GENERAL CONSIDERTIONS
It is expected that the person, who is going to attempt this retrofit, should go
through this document before starting the retrofit procedure.
For the software retrofit the utility is maxng.util_target which is to be procured
from C-DOT.
The retrofit procedure is to be carried at the IOP over the ED of the MAX exchange
required to be converted to MAX-NG.
The detailed procedure for retrofit is given in the subsequent chapter.
S/W deliverables, cart ridges of UNIX, BASE, PATCH and BMDC are to be
prepared from the master set.
PRE-RETROFIT CHECKS
 Take the list of the Ai characteristic of all the AI’s of the BM which is
 Required to be convert to MAX-NG.
 Take the list of the subs-l3addr.
 Take the list of the subs facility and access level.
The above data can be retrieved using the rgen utility, and will be required to
match the data once the s/w retrofit activity is over.
AI related Data retrieval from IOP :
Copy the utility file maxng.util_target to /data/exdata/glbdata directory, the file can
be down loaded from C-DOT helpline site and can be transfer to IOP through sz-rz
utility.
After copying the file in the IOP go to $GLBDATAP
iop5C>pwd
/data/exdata/glbdata
iop5C>mkdir /tmp/drlog
execute the utility file ..
iop5C> ./maxng.util_target <Physical BM No.> e.g.

Annexure - 3
iop5C>./maxng.util_target 19 (where 19 is a BM No. for which data is to be

retrieved) #following message will be displayed in
the IOP
1.*****DATA RETROFIT PROCEDURE STARTING *********
mkdir: cannot make directory –p export GLBDATAP=/data/exdata/glbdata/ :
[Starting MAX to LAG Data Extraction Utility (BM:19) ...
EXCHANGE CODE DATA:( abexcd.{dat,idx,lok })to file --->
/tmp/drlog/echcg_cod_19.txt
>>>>>>>>>>>>>>total_num_of_exc(36)<<<<<<<<<<<<<<[0m
AINAME DATA: ( ioenmp.{dat,idx,lok} ) IOENMP_RELID(118)to file --->
/tmp/drlog/ai_name_19.txt AI ATTRIBUTE DATA:( bpaiod18.{dat,idx,lok} ) to file --
->
/tmp/drlog/ai_19.txt [33m >>>>>>>>>>>>>>total_num_of_ai(10) in BM-
19<<<<<<<<<<<<<<[0m
[Extracting Subscriber Data ... [0m
BPAOD_RELID:( bpaod18.{dat,idx,lok} ) ---->output is: ( /tmp/drlog/sub_19.txt )
CRESUB:13: 9: 278089: 1: 1: 0: 0: 0: 0: 0
CRESUB:13: 56: 278051: 1: 1: 0: 0: 0: 0: 0
CRESUB:13: 60: 278054: 1: 1: 0: 0: 0: 0: 0
CRESUB: 7: 115: 277528: 1: 1: 0: 0: 0: 0: 0
CRESUB:12: 73: 236198: 1: 1: 3: 0: 0: 0: 0
CRESUB: 8: 148: 276126: 1: 1: 0: 0: 0: 0: 0
CRESUB:10: 99: 231634: 1: 1: 0: 0: 0: 0: 0
CRESUB:10: 119: 231562: 2: 1: 9: 0: 0: 0: 0
CRESUB:16: 40: 287622: 2: 1: 9: 0: 0: 0: 0
CRESUB: 9: 79: 231520: 1: 1: 0: 0: 0: 0: 0
CRESUB: 9: 93: 231078: 1: 1: 0: 0: 0: 0: 0
CRESUB: 9: 135: 231542: 1: 1: 0: 0: 0: 0: 0
CRESUB: 9: 218: 231644: 1: 1: 0: 0: 0: 0: 0
CRESUB: 9: 126: 231067: 1: 1: 0: 0: 0: 0: 0
CRESUB:12: 94: 236562: 1: 1: 0: 0: 0: 0: 0
CRESUB:12: 35: 236077: 1: 1: 0: 0: 0: 0: 0
56 C-DOT MAX-NG
LAG/V5AG DATA EXTRACTION PROCEDURE
CRESUB: 8: 199: 276058: 1: 1: 0: 0: 0: 0: 0

CRESUB:15: 241: 239533: 1: 1: 0: 0: 0: 0: 0
CRESUB:15: 120: 239658: 1: 1: 0: 0: 0: 0: 0
CRESUB:10: 127: 231164: 1: 1: 0: 0: 0: 0: 0
CRESUB:10: 125: 231011: 1: 1: 0: 0: 0: 0: 0
CRESUB:10: 160: 231012: 1: 1: 0: 0: 0: 0: 0
CRESUB:12: 202: 236152: 1: 1: 0: 0: 0: 0: 0
CRESUB: 9: 247: 231069: 1: 1: 0: 0: 0: 0: 0
CRESUB:14: 52: 273015: 1: 1: 0: 0: 0: 0: 0
CRESUB:11: 175: 236511: 1: 1: 0: 0: 0: 0: 0
CRESUB:11: 142: 236174: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 124: 276187: 1: 1: 0: 0: 0: 0: 0
CRESUB:13: 50: 278116: 1: 1: 0: 0: 0: 0: 0
total subscribers in BM-19 is (608) / AI_subs=608
Data Extraction Utility Over ...
take following files: /tmp/drlog/ai_19.txt /tmp/drlog/sub_19.txt
/tmp/drlog/mysubslog_19.txt
iop5C> cd /tmp/drlog
iop5C> ls -lrt
total 196
-rw-rw-r-- 1 admn admin 758 Oct 5 15:49 echcg_cod_19.t
-rw-rw-r-- 1 admn admin 673 Oct 5 15:49 ai_name_19.txt
-rw-rw-r-- 1 admn admin 364 Oct 5 15:49 ai_19.txt
-rw-rw-r-- 1 admn admin 67479 Oct 5 15:50 mysubslog_19.t
-rw-rw-r-- 1 admn admin 0 Oct 5 15:50 sub_19.txt_10
-rw-rw-r-- 1 admn admin 28730 Oct 5 15:50 sub_19.txt
The file ai_19.txt and sub_19.txt are used for the data creation related to AI’s.
iop5C> cat sub_19.txt
;CRESUB:aiNum:l3_addr:dir_num:line_type:line_ctg:priority:reg_fclty_org:act_org:r
eg_fclty_trm:act_trm
CRESUB:13: 9: 278089: 1: 1: 0: 0: 0: 0: 0
CRESUB:13: 56: 278051: 1: 1: 0: 0: 0: 0: 0

Annexure - 3
CRESUB:13: 60: 278054: 1: 1: 0: 0: 0: 0: 0

CRESUB: 7: 115: 277528: 1: 1: 0: 0: 0: 0: 0
CRESUB:12: 73: 236198: 1: 1: 3: 0: 0: 0: 0
CRESUB: 8: 148: 276126: 1: 1: 0: 0: 0: 0: 0
CRESUB:11: 166: 236199: 1: 1: 0: 0: 0: 0: 0
CRESUB: 7: 51: 277580: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 160: 276065: 1: 1: 0: 0: 0: 0: 0
CRESUB:14: 19: 273043: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 12: 276109: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 146: 276091: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 196: 276041: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 221: 276035: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 18: 276072: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 15: 276073: 1: 1: 0: 0: 0: 0: 0
CRESUB:12: 169: 236063: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 195: 276076: 1: 1: 0: 0: 0: 0: 0
CRESUB:12: 89: 236147: 1: 1: 0: 0: 0: 0: 0
CRESUB:14: 31: 273033: 1: 1: 0: 0: 0: 0: 0
CRESUB: 8: 84: 276092: 1: 1: 3: 0: 0: 0: 0
CRESUB: 8: 87: 276062: 1: 1: 0: 0: 0: 0: 0
CRESUB: 9: 28: 231581: 1: 1: 0: 0: 0: 0: 0
CRESUB:12: 99: 236005: 1: 1: 0: 0: 0: 0: 0
CRESUB:14: 10: 273034: 1: 1: 0: 0: 0: 0: 0
CRESUB:14: 14: 273514: 1: 1: 0: 0: 0: 0: 0
CRESUB:14: 28: 273537: 1: 1: 0: 0: 0: 0: 0
CRESUB:14: 30: 273515: 1: 1: 0: 0: 0: 0: 0
CRESUB:16: 107: 287714: 1: 1: 0: 0: 0: 0: 0CRESUB: 9: 87: 231068: 1: 1: 0: 0: 0:
0: 0
iop5C>
iop5C> ls
iop5C> cat ai_19.txt # This will show the list of AI
; OPCODE:aiNum:aiName:variant:no_of_links:pri_link:sec_link:ordLink:start_l3
58 C-DOT MAX-NG
CREAI: 7 : LKH: 7: 1: 0: 1
CREAI: 8:KALSI:8:1:0:1
CREAI: 9:RUD1:9:1:0:1
CREAI:10:RUD2:10:1:0:1
CREAI:11:HOR1:11:1:0:1
CREAI:12:HOR2:12:1:0:1
CREAI:13:NAGTHAT:13:1:0:1
CREAI:14:KORWA:14:1:0:1
CREAI:15:SBA:15:1:0:1
CREAI:16:KOTI:16:1:0:1
;>>>>>>>>>>>>>>total_num_of_ai(10) in BM-19<<<<<<<<<<<<<<
iop5C>
iop5C> iop5C>
V5AG Card Preparation:
For this, NGTJ card will be installed and configured as V5/PRIAG delivered at co-
located BM site. For this, refer to installation document of CACU installation as
given in Appendix-III.
For data creation in V5AG/PRIAG card, refer to Appendix-IV.
STEP-1:-
[root@lenlin54] ssh root@10.187.xx.yy
Password: ******
After successful logging into the card ,command prompt will appear.
$
$ cd /mmc/ag
/mmc/ag $ cat relinfo # verify the release have been installed
AGL1_1_2.14_1
total 55900
-rwxr-xr-x 1 root root 34971433 Sep 5 12:01 cDOTagt_t_sgtk
-rwxr-xr-x 1 root root 5124020 Sep 5 12:01 ag_stk.strip
-rwxr-xr-x 1 root root 152 Sep 5 12:01 v5ag_alm_pannel.html
-rw
-rwxr-xr-x 1 root root 48373 Sep 5 12:03 cremon_sgtk
-rwxr-xr-x 1 root root 37904 Sep 5 12:03 cremon_h

Annexure - 3
/mmc/ag $ cd /mmc/scripts
/mmc/scripts$ ./agreboot # reboot the card
login to the card again and check the following process are UP.
~ $ ps
PID Uid VmSize Stat Command
1 root SW [swapper]
2 root SWN [ksoftirqd/0]
3 root SW< [events/0]
4 root SW< [khelper]
5 root SW< [kthread]
6 root SW< [kblockd/0]
7 root SW [pdflush]
8 root SW [pdflush]
9 root SW< [kswapd0]
10 root SW< [aio/0]
11 root SW [mtdblockd]
14 root 340 S init
22 root 100 S init
23 root 336 S /bin/sh /etc/rc.sh
26 root 840 S /usr/sbin/xinetd -stayalive -reuse -pidfile /tmp/xinetd.pid
29 root SWN [msdreq]
30 root SW< [msdbusy]
39 nobody 380 S /usr/local/boa/boa -c /usr/local/boa
41 root SWN [jffs2_gcd_mtd1]
42 root 344 S /bin/sh /jffs2/conf/net
82 root SW< [DSP Receive thr]
83 root DW< [DSP Main Thread]
84 root DW< [DSP Restart Thr]
85 root SW< [DSP Dummy Threa]
90 root 304 S ./v5_aggregator_sgtk 8000 0
60 C-DOT MAX-NG

100 root 384 S /bin/sh ./aginit 5
101 root 1124 S /bin/sh /AGENT/cagent/agentdService
118 root 1156 S /bin/sh /scripts/v5ag_init.s
126 root 596 S ./cremon_sgtk
143 root Z [cDOTagt]
144 root 756 S ./beExe_sgtk
159 root 5208 S ./v5ag -vc
160 root 440 S ./v5msghlr -t0
664 root 772 S in.telnetd: 192.168.61.210
665 root 440 S -sh
669 root 588 S sleep 20
673 root 364 R ps
$ exit
[root@lenlin54]
DATA CREATION
[root@lenlin54]./feExe 10.187.xx.yy 9001 #Run FE to go to CLI prompt
*************************************************************************
LOGIN TO FE **********************************************
PLS ENTER ->
+-----------------------------+
| |
| USRNAME : admin |
| PASSWORD : admin123
+-----------------------------+
*************************************************************************

Annexure - 3
Main Menu ( Enter number )

1. Existing Configuration Display
2. Subscriber And Miscllaneous Commands
3. V5 Protocol Commands
4. Traffic Commands
5. Event Configuration
6. Trace level
7. Logger file
8. Site-Id
9. Update-timer-value
10. ADP Panel Restart/Refresh
11. Stop(1)/Start(2) ADP mozilla Pop-Up
12. Change Password for admin
13. Change Password for cDOT
14. Quit
Enter Your Choice = 2
Subscriber Commands Menu ( Enter number )
1. Management Commands
2. Facilities Management Commands
3. Misc Commands
4. Back to main Menu
5. Quit
Misc Commands ( Enter Number )
1.Display System Parameter
2.Modify System Parameter
3.CRE-CMD-FILE
4.EXEC-CMD-FILE
5.Database Backup
6.Database Restore and Reboot
7.Processes ReCreate
8.Audit
62 C-DOT MAX-NG
9.Displ-sys-release
10.Displ-sys-all
11.Displ-V5AG-Physical-Sts
12.Change the Timer value for Front End Time Out
13. Back to Subscriber Commands Menu
14. Back to Main Menu
15. Quit
Enter CMD FILE NAME : ai_19.txt #This will create all the AI
3.CRE-CMD-FILE
4.EXEC-CMD-FILE
5.Database Backup
8.Audit
9.Displ-sys-release
10.Displ-sys-all
15. Quit
Enter CMD FILE NAME : sub_19.txt #This will create all the Subs
On executing this command the subscriber corresponding to the V5ag will be
created.

Annexure - 3
Before doing the cut-through verify the data corresponding to AI and subscriber.
3.CRE-CMD-FILE
4.EXEC-CMD-FILE
5.Database Backup
8.Audit
9.Displ-sys-release
10.Displ-sys-all
15. Quit
4. Traffic Commands
6. Trace level
7. Logger file
8. Site-Id
64 C-DOT MAX-NG
14. Quit
Protocol-Commands Menu ( Enter number )
1. Mac Layer Commands
2. V5 Layer 3 Commands
4. Quit
Select Any Command-Group for Layer V5_LAYER3 ( Enter number )
1. Create
2. Delete/Modify
3. Display
4. Back to V5 Protocol Command Menu
6. Quit
Display Commands ( Enter number )
1. Displ-V5Gen-Attr
2. Displ-AI-Attr
3. Displ-V5L3-Statistics
4. Displ-V5L3-Status
5. Displ-V5 AI or Link Status
7. DISPL ALL AI INFO
8. Back to Command-Group Menu For V5L3
9. Back to Protocol Commands Menu
11. Quit.

Annexure - 3
Parameters required ( DISPL-AI-CHAR )

*******************************
Enter AI Num : ( 1 - 25 ) 9
Want to Repeat/Terminate/Execute the command (R/T/E) : e
DISPL-AI-CHAR ...
AN Interface Number =9
AI Name = RUD1
AN Variant Id =9
AN Interface Version = 1999
AN Interface Type = V5.2
AI numLinks =1
AI linkId[ ] = 2-2,
AI PriLnkId =2
AI SecLnkId = NOT-CONFIGURED
AI startL3Address =1
AI Area Code = 01360
Num Self Exch Code =1
SelfExchCode =2
No of digits in Subscriber No.=6
Status : SUCCESS
Verify the data for all the AI's and compare it with MAX-Data in the IOP.
V5L3 Display Commands (Enter number)
1. Displ-V5Gen-Attr
2. Displ-AI-Attr
4. Displ-V5L3-Status
5. Displ-V5 AI or Link Status
7. DISPL ALL AI INFO
8. Back to Command-Group Menu For V5L3
9. Back to Protocol Commands Menu
66 C-DOT MAX-NG
11. Quit.
4. Traffic Commands
6. Trace level
7. Logger file
8. Site-Id
14. Quit
Subscriber Commands Menu (Enter number)
1. Management Commands
2. Facilities Management Commands
3. Misc Commands
4. Back to main Menu
5. Quit
Management Commands (Enter Number)
1. Create Subscriber
2. Delete Subscriber
3. Modify Subscriber Priority
4. Modify Subscriber Line Type
5. Modify Subscriber Line Status
6. Modify Subscriber Centrex facility

Annexure - 3
7. Modify Subscriber Status: Block / Unblock

8. UnFreeze Directory Number
9. Display Subscriber Char
10. Display Subscriber Status
11. Display Subscribers List
12. Display Call Info
13. Display Freezed Directory Numbers
16. Quit
(Display Subscribers List)
Select Option :
1. Subscriber List
2. Subscriber List IDLE
3. Subscriber List BLOCK
4. Subscriber List CP-BUSY
5. Subscriber List INS-LLO
6. Subscriber List TIMED_HTLINE
7. Subscriber List UNTIMED_HTLINE
8. Subscriber List NO FACILITY
9. Subscriber List Dir Num Range
10. L3 ADDR ASSIGNED
11. DIR NUM ASSIGNED
12. Subscriber List LINE STATUS BNP-ANNC
13. Subscriber List LINE STATUS BNP-DISCONNECT
Enter Choice: 1
Enter Choice (1.ALL 2.AI 3.AI L3ADDR RANGE): 1
Want to Repeat/Terminate/Execute the command (R/T/E) : e
Display Subscribers List Executed
Check Subscriber data file (mmc/tmp/subs_list.txt) at TARGET
68 C-DOT MAX-NG
Summary
+---------+---------------------+
+ Ai Num | Num of Subscribers |
+---------+---------------------+
4| 120 |. # Verify the total No's of
9| 79 |. Subscribers/interfaces and
10 | 41 |. Compare it with IOP data
11 | 5 |.
12 | 89 |.
13 | 25 |.
Total Subscribers(359)
#The list will be displayed
[SeqNo] AiNum, L3Addr, DirectoryNumber
[ 1] 4 2 214002 # Also verify the subs-l3addr
[ 2] 4 3 214003 List with IOP data
[ 3] 4 9 214009
[ 4] 4 11 214001
[ 5] 4 12 214012
[ 6] 4 14 214147
[ 7] 4 18 214018
[ 8] 4 21 214021
[ 9] 4 24 214024
[ 10] 4 25 214025
[ 11] 4 26 214026
[ 12] 4 29 214029
[ 13] 4 33 214033
[ 14] 4 34 214034
[ 15] 4 37 214037
[ 16] 4 39 214039
[ 17] 4 42 214042
[ 18] 4 43 214043
[ 19] 4 44 214044

Annexure - 3
[ 20] 4 45 214045
[ 21] 4 47 214047
[ 22] 4 48 214048
[ 23] 4 49 214049
[ 24] 4 50 214050
[ 25] 4 51 214051
Press return to continue...
[ 26] 4 52 214052
[ 27] 4 53 214053
[ 28] 4 54 214054
[ 29] 4 56 214056
[ 30] 4 57 214057
[ 31] 4 68 214068
[ 32] 4 71 214071
[ 33] 4 81 214081
[ 34] 4 84 214084
[ 35] 4 87 214087
[ 36] 4 88 214088
[ 37] 4 89 214089
[ 38] 4 90 214090
[ 39] 4 96 214096
[ 40] 4 106 214106
[ 41] 4 116 214116
[ 42] 4 118 214118
[ 43] 4 119 214119
[ 44] 4 133 214133
[ 45] 4 134 214134
[ 46] 4 135 214135
[ 47] 4 140 214140
[ 48] 4 141 214141
[ 49] 4 142 214142
[ 50] 4 143 214143
70 C-DOT MAX-NG

[ 74] 4 179 214179
[ 75] 4 180 214180
[ 76] 4 181 214181
[ 77] 4 182 214182
[ 78] 4 183 214183
[ 79] 4 184 214184
[ 80] 4 185 214185
[ 81] 4 186 214186
[ 82] 4 187 214187
[ 83] 4 189 214189
[ 84] 4 192 214192
[ 85] 4 194 214194
[ 86] 4 196 214196
[ 87] 4 197 214197
[ 88] 4 199 214199
[ 89] 4 239 214239
[ 90] 4 460 214060
[ 91] 4 1013 215013
[ 92] 4 1028 215028
[ 93] 4 1034 215034
[ 94] 4 1038 215038
[ 95] 4 1039 215039
[ 96] 4 1043 215043
[ 97] 4 1045 215045
[ 98] 4 1046 215046
[ 99] 4 1047 215047
[100] 4 1049 215049

[101] 4 1052 215052

Annexure - 3
[102] 4 1053 215053

[103] 4 1054 215054
[104] 4 1055 215055
[105] 4 1056 215056
[106] 4 1057 215057
[126] 9 17 231650
[127] 9 22 231564
[128] 9 30 231510
[129] 9 37 231543
[130] 9 39 231175
[131] 9 59 231519
[132] 9 66 231649
[133] 9 67 231066
[134] 9 68 231541
[135] 9 70 231642
[136] 9 71 231098
[137] 9 72 231188
[138] 9 76 231522
[139] 9 79 231520
[140] 9 87 231068
[141] 9 88 231549
[142] 9 90 231518
[143] 9 92 231048
[144] 9 93 231078
[145] 9 95 231596
[146] 9 96 231533
[147] 9 114 231620
[148] 9 116 231161
[149] 9 117 231514
[150] 9 119 231509
72 C-DOT MAX-NG

[151] 9 121 231021
[152] 9 124 231015
[153] 9 126 231067
[154] 9 129 231190
[155] 9 130 231108
[156] 9 131 231636
[157] 9 134 231544
[158] 9 136 231598
[159] 9 139 231648
[160] 9 151 231637
[161] 9 154 231654
[162] 9 161 231506
[163] 9 163 231566
[164] 9 164 231569
[165] 9 165 231560
[166] 9 166 231169
[167] 9 167 231559
[168] 9 168 231653
[169] 9 172 231183
[170] 9 173 231059
[171] 9 181 231041
[172] 9 183 231655
[173] 9 190 231630
[174] 9 191 231592
[175] 9 193 231558
[176] 9 194 231577
[177] 9 198 231619
[178] 9 200 231626
[179] 9 202 231618
[180] 9 203 231122

Annexure - 3
[181] 9 204 231124

[182] 9 205 231517
[183] 9 206 231013
[184] 9 207 231574
[185] 9 218 231644
[186] 9 220 231024
[187] 9 221 231009
[188] 9 222 231032
[189] 9 224 231524
[190] 9 226 231635
[191] 9 228 231180
[192] 9 230 231594
[193] 9 231 231610
[194] 9 240 231043
[195] 9 242 231615
[196] 9 243 231568
[197] 9 244 231676
[198] 9 245 231047
[199] 9 248 231515
[200] 10 2 231573
[201] 10 5 231026
[202] 10 7 231049
[203] 10 8 231044
[204] 10 12 231061
[205] 10 13 231008
[206] 10 14 231039
[207] 10 15 231526
[208] 10 66 231070
[209] 10 67 231046
[210] 10 69 231547
[211] 10 71 231029
74 C-DOT MAX-NG
[212] 10 72 231632
[213] 10 82 231523
[214] 10 85 231050
[215] 10 87 231176
[216] 10 95 231007
[217] 10 97 231599
[218] 10 99 231634
[219] 10 106 231638
[220] 10 111 231038
[221] 10 117 231621
[222] 10 119 231562
[223] 10 120 231563
[224] 10 125 231011
[225] 10 127 231164
[226] 10 129 231198
[227] 10 134 231025
[228] 10 135 231099
[229] 10 136 231589
[230] 10 137 231014
[231] 10 138 231628
[232] 10 140 231625
[233] 10 141 231624
[234] 10 144 231612
[235] 10 148 231557
[236] 10 149 231505
[237] 10 155 231018
[238] 10 158 231537
[239] 10 159 231182
[240] 10 160 231012
[241] 11 20 236121
[242] 11 28 236599

Annexure - 3
[243] 11 29 236518
[244] 11 78 236584
[245] 11 215 236021
[246] 12 10 236006
[247] 12 11 236083
[248] 12 12 236563
[249] 12 14 236165
[250] 12 15 236159
[251] 12 16 236560
[252] 12 18 236123
[253] 12 19 236087
[254] 12 20 236093
[255] 12 21 236575
[256] 12 22 236154
[257] 12 23 236586
[258] 12 24 236146
[259] 12 25 236550
[260] 12 27 236137
[261] 12 28 236023
[262] 12 29 236597
[263] 12 31 236067
[264] 12 32 236174
[265] 12 35 236077
[266] 12 36 236003
[267] 12 39 236519
[268] 12 50 236111
[269] 12 51 236030
[270] 12 52 236587
[271] 12 53 236583
[272] 12 54 236069
[273] 12 56 236107
76 C-DOT MAX-NG
[274] 12 57 236539
[275] 12 62 236579
[276] 12 63 236044
[277] 12 73 236198
[278] 12 74 236017
[279] 12 75 236108
[280] 12 76 236065
[281] 12 77 236101
[282] 12 78 236025
[305] 12 146 236056
[306] 12 168 236192
[307] 12 169 236063
[308] 12 170 236010
[309] 12 171 236153
[310] 12 178 236127
[311] 12 179 236061
[312] 12 181 236041
[313] 12 185 236514
[314] 12 186 236004
[315] 12 187 236561
[316] 12 189 236081
[317] 12 190 236556
[318] 12 192 236538
[319] 12 197 236113
[320] 12 201 236020
[321] 12 202 236152
[322] 12 206 236580
[323] 12 207 236050
[324] 12 208 236001
[325] 12 210 236112

Annexure - 3

[326] 12 212 236170
[327] 12 216 236080
[328] 12 218 236581
[329] 12 221 236588
[330] 12 222 236059
[331] 12 224 236011
[332] 12 227 236508
[333] 12 243 236199
[334] 12 245 236195
[335] 13 9 278089
[336] 13 10 278078
[337] 13 13 278126
[338] 13 15 278067
[339] 13 16 278055
[340] 13 33 278122
[341] 13 36 278178
[342] 13 37 278051
[343] 13 38 278091
[344] 13 39 278007
[345] 13 60 278054
[346] 13 61 278015
[347] 13 63 278021
[348] 13 81 278009
[349] 13 82 278058
[350] 13 83 278048
[351] 13 84 278102
[352] 13 85 278116
[353] 13 86 278020
[354] 13 87 278103
[355] 13 88 278072
78 C-DOT MAX-NG
[356] 13 89 278198
[357] 13 92 278168
[358] 13 94 278038
[359] 13 95 278053
Status : SUCCESS
Management Commands ( Enter Number )
1. Create Subscriber
2. Delete Subscriber
3. Modify Subscriber Priority
4. Modify Subscriber Line Type
5. Modify Subscriber Line Status
6. Modify Subscriber Centrex facility
7. Modify Subscriber Status: Block / Unblock
8. UnFreeze Directory Number
9. Display Subscriber Char
10. Display Subscriber Status
11. Display Subscribers List
12. Display Call Info
13. Display Freezed Directory Numbers
16. Quit
Are you sure to exit? [1.Yes 0.No] 1
1
Killed
[root@lenlin54]

Annexure - 3
CONTACT NOS. OF C-DOT CONTROL ROOM

In case of any emergency contact to the following Nos.
09818822909,
08800742266,
08800732266,
Go to C-DOT Help Desk through C-DOT Helpline Portal
(www.cDOThelpline.ernet.in)
80 C-DOT MAX-NG
Annexure - 4
IP Address Details & Exchange Data of

Sites Proposed to be Migrated
IP Addresses
CIRCLE SITE LBM RSU ANRAX PRI allocated
Andhra Pradesh Dharmavaram 1 2 7 0

Hindupur 3 6 13 2
Indiranagar 8 3 0 0
Karnataka
Bangarpet 1 2 3 0
Kodungallur 5 0 0 0
Kerala
Payyanur 0 6 0 0
Kagal 1 2 7 3
Maharashtra
Lonavala 1 1 2 0
Tamil Nadu Tiruvattipuram 2 1 7 2

Denganikotta 2 1 6 0
nurpurbedi 1 5 3 1 10.187.198.128/25
Punjab
Morinda 2 6 1 1 10.187.197.128/25
Tosham 0 0 8 2 10.187.229.0/26
Haryana
Siwani 0 1 6 0 10.187.229.64/26
Chhata 1 3 6 1 10.187.241.192/26
UP WEST
Sadabad 0 2 9 0 10.187.241.128/26
Nalagarh 3 8 14 1 10.188.13.128/25
HP
Poanta 3 6 10 0 10.188.14.0/25
10.188.30.0/26
UP EAST Dumariyaganj 5 1 8 1
Bansi 2 1 14 2 10.188.30.64/26
Chamoli 3 2 6 1 10.188.79.128/25
UK
Joshimath-I 2 0 2 0 10.188.79.64/26
RAJASTHAN Gangapur 1 2 7 5 10.188.92.192/26

Annexure - 4
IP Addresses
CIRCLE SITE LBM RSU ANRAX PRI allocated
Bhilwara 5 1 8 0 10.188.93.128/25
Samba 2 2 3 0 10.188.137.128/26
J&K
Billawar 1 1 6 0 10.188.137.192/26
Simri 10.187.138.192/26
BIHAR Bakhtiarpur 1 1 9 0
Supaul 2 2 8 0 10.187.139.0/26
Koraput 2 3 10 1 10.187.95.0/25
ORISSA
Gunupur 2 1 8 0 10.187.94.0/26
Gumla 2 0 7 1 10.187.93.128/26
JHARKHAND
Lohardaga 2 2 7 0 10.187.93.0/26
BURDWAN 10.187.79.0/26
(GALSHI ) 1 2 10 2
WEST BENGAL
BURDWAN 10.187.79.64/26
(BHATAR) 2 1 10 0
PASSIGHAT 5 2 3 0 10.187.35.0/25
N.E.- II
TAWANG 3 0 5 0 10.187.36.0/26
Tura 2 5 8 0 10.187.26.0/25
N.E.-I
Jowai 2 2 2 0 10.187.26.128/26
Mangaldoi 2 3 9 2 10.187.24.0/25
ASSAM
Udalguri 1 2 7 0 10.187.24.128/26
Port Blair 5 5 12 1 10.187.10.0/25
ANDAMAN
Diglipur 1 1 5 0 10.187.11.64/26
MP Bina 1 3 2 1
Sagar 2 5 15 0
Rajnangaon 2 7 21 2
Chhatisgarh
Balod 1 2 9 0
Patel colony,
Jamnagar 2 6 13 1
Gujarat
Mehul Nagar,
Jamnagar 2 10 12 0
82 C-DOT MAX-NG
Annexure - 5
IP Address Configuration IN MLS Card

1. Log in to the MLS card with the serial interface (minicom) if the default IP address
is not set, or login using ssh or telnet if an IP address is already assigned. The user
credentials are username ‘admin’ and the password is blank.
2. Type the following commands on the terminal:
(The commands are shown starting with a ‘#’ prompt)
# configure terminal
# interface vlan1
ip address <ip address to be assigned to the VLAN 1> <netmask> eg:
#ip address 192.168.101.12 255.255.255.0
#exit
3. Exit the terminal using the command
# logout
Note: The above steps are only for assigning the VLAN 1 IP address to the
MLS card and the same will be used as a gateway address in the cards. The
procedure to create Layer-3 routing is not written here.

Annexure - 6
C-DOT MAX-NG Network Connectivity

PURPOSE AND SCOPE
This chapter provides an overview of C-DOT MAX-NG access site connectivity to
the core network. It also provides information regarding LAN and WAN IP
provisioning and the procedure to configure MLS card.
1.2 INTRODUCTION
During the migration of MAX system to MAXNG the most important point is the
reachability of the access site to the core network. Each access site is allocated an IP
pool of 64, 128 or 256 IPs depending upon the capacity of the MAX system. This pool
of IP is referred as LAN IP pool. Similarly, three WAN IP pools of 4 IPs in
redundant mode are allocated to each site for creation of interfaces between access
site and MPLS network. These interfaces are created in redundant mode. For
getting accessibility between MAX-NG access node and core network, information
pertaining to WAN IPs need to be shared with the administrator of the MAX
exchange at least 15 days before migration so that the configuration at the BSNL’s
MPLS PE router can be done. The information consists of the IP pool for LAN and
WAN interfaces, VLAN numbers, interface IPs to be configured at BSNL PE router
end etc. Three VLANs, IPTAX, SSTP and CDOT-VOIP are created at both BSNL
PE router and CDOT MLS card. Each VLAN is provided an unique VRF-ID. A
unique LAN IP pool is given to each SDCA which is required for the configuration of
all the access gateways which will be installed at access site in each BM/RBMs and
in CACU chassis. This IP pool is required to be publish at PE router for all the three
VRFs.
ACCESS SITE CONNECTIVITY
2.1 CONNECTING AN ACCESS SITE
Suppose an access site is allocated, LAN IP pool starting from 10.187.35.0 to
10.187.35.255 of 256 IPs denoted as 10.187.35.0/24 and WAN IP pool
10.189.107.40/30, 10.189.107.44/30 and 10.189.107.48/30. For redundant interfaces
the IP pools are 10.189.107.52/30, 10.189.107.56/30 and 10.189.107.60/30 . These
WAN IPs are required to create interfaces between different VLANs. These VLANs
are IPTAX , SSTP and CDOT-VOIP VLAN with unique VRF ID and required to be
created at both the end.
2.2 MLS CONFIGURATION
Once configuration at PE router is done, configuration at MAX-NG access node is
required. For configuration at MAX-NG node, CACU chassis need to be physically
installed and power-on. Once the physical installation of CACU is done insert the
84 C-DOT MAX-NG
C-DOT MAX-NG NETWORK CONNECTIVITY
MLS card in the corresponding slot at CACU chassis and connect the minicom cable
to the thin client. Allocate an IP to the thin client from the list of LAN IPs allocated
to the given site, run minicom from the thin client as shown in fig-1 and configure
the management IP of MLS as given in the IP list (fig-3). The management IP of
the MLS will act as a gateway IP for the given pool. As there is a provision of two
MLS cards, dual gateways support is available.

Fig-1
Fig-2

Annexure - 6
Fig-3 (IP configuration in MLS)

Once the IP of the MLS is set, it can be accessed through internet browser and rest
of the configuration can be done through GUI interface of the MLS.

Fig-4 MLS Card GUI Interface
86 C-DOT MAX-NG
Now create WAN interfaces at MLS card, these interfaces should be as per the
WAN IPs allocated and as per the configuration done at PE router end. For
creation of the IP interfaces from the left pane select Configuration IP, a window
will open showing the VLAN 1 configuration (fig-5) which is the native VLAN for
the subnet allocated to that site.
Fig -5 VLAN1 Configuration of the MLS

Now as per the example mentioned in the section above , at BSNL MPLS end
interfaces are created at two different PE routers for redundancy. At a cisco
routers interfaces created using WAN IP pools 10.189.107.40/30, 10.189.107.44/30
and 10.189.107.48/30. One interface is for IPTAX VLAN (VLAN ID=2900) and IP
given to this interface is 10.189.107.42 at BSNL end. Similarly SSTP VLAN and
CDOT-VOIP VLANS are created with VLAN ID 2901 and 2902 and IPs
10.189.107.46 and 10.189.107.50 respectively.
For redundant interfaces the IP pools are 10.189.107.52/30, 10.189.107.56/30 and
10.189.107.60/30 used at Huawai router VLAN created are 2700, 2701 and 2702 for
IPTAX, SSTP and CDOT-VOIP VLANs and the interface IPs are 10.189.107.54,
10.189.107.58 and 10.189.107.62.
Similar interfaces need to be created at MAX-NG node also. An interface towards
cisco PE router need to be created at MLS1 and towards huawai router the interface
will be created from MLS2. With respect to Huawai router at MLS2 , VLANs 2700,
2701 and 2702 will be created with the interface IPs 10.189.107.53, 10.189.107.57
and 10.189.107.61 respectively as shown in fig-6. For creating interfaces click on
“add interface” and enter the VLAN id, Ip address and mask length. After the
interfaces are added, create IP routes. Create a default route with network 0.0.0.0

Annexure - 6
mask length 0, the default gateway for this default route will be the interface IP of
IPTAX VLAN. This indicates that any network IP other than the specified network
will be routed towards IPTAX VLAN as it may be the address belonging to media IP
of IPTAX. Similarly a network 10.187.0.0/24, is a pool allocated to MAX-NG and
will be routed towards CDOT-VOIP VLAN and the gateway IP will be 10.189.107.60
which is an IP address for CDOT-VOIP interface created at Huawai PE router,
refer fig-7. Select mode as “router” from the drop down and click to “save” button
once interfaces and routes are added.
Fig-6 Adding Interfaces
88 C-DOT MAX-NG
Fig-7 Add IP Routes

From the left pane select Spanning tree  Bridge setting and do the STP bridge
configuration as shown in fig-8

Fig-8 STP Bridge Configuration

Annexure - 6
Now from the left pane click on VLANs Configuration a window will open
showing Global VLAN configuration. Here all the ports of MLS are visible with
their mode and Port VLAN as shown in fig-9
Fig -9 Global VLAN Configuration
90 C-DOT MAX-NG
The mode of the port can be Access or Trunk and can be selected from the drop
down and Port VLAN can be defined according to the configuration. Default value of
Port VLAN is 1.
Fig-10 Allowing Access VLAN

It is also to be noted that against the field “allowed access VLAN” all the VLANs
number to be given see fig-10.
In the face plate of MLS card two optical ports 21 and 22 are available which are
used for uplink connectivity. An SFP of 1310 or 1550 nm wavelength can be used in
these ports depending the SFP type available at BSNL end. An optical patch cord is
used for the connectivity of MLS and PE router. The “Mode” of the port 21 or 22
which is being used for uplink is to be set as Trunk port as shown in fig-11.

Annexure - 6

Fig-11
On selecting the required port as Trunk all the VLANs 1-4095 will be allowed and
Egress port setting wiil be by default set as Untag Port VLAN now save the setting
from the button given below. After all the configuration is done, in the left pane
select Configuration  save startup config to save the configuration as shown in fig-
12.
92 C-DOT MAX-NG

Fig-12 Saving the Configuration
After the configuration is done, one should be able to ping the core network from
MLS and behind MLS i.e. from LAGU, thin client etc.

Cdot Maxng Migration Man V02 PDF

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Cdot Maxng Migration Man V02 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

C-DOT MAX-NG

MAX TO MAX-NG MIGRATION MANUAL

SERIES 100: PLANNING

CSP SECTION NO. 431-101-1061

THIS C–DOT SYSTEM PRACTICE REFERS TO THE C–DOT DIGITAL

SWITCHING SYSTEM MAIN AUTOMATIC EXCHANGE NEXT GENERATION

(ABBREVIATED AS C-DOT MAX-NG IN THE REST OF THIS PUBLICATION).

THE INFORMATION IN THIS SYSTEM PRACTICE IS FOR INFORMATION

PURPOSES AND IS SUBJECT TO CHANGE WITHOUT NOTICE.

ANY FEEDBACK ON THE DOCUMENT MAY BE SENT AT

© 2017 BY C–DOT, NEW DELHI

H:\HOME\NG-MAX\User\FinalCDOT-MAXNG-MIGRATION-MAN-V02.doc May 29. 2017

MAX-TO MAX-NG MIGRATION MANUAL 5

1.3. NGN ACCESS NETWORK

East Zone will have two sites at Cuttack and Kolkata.

MAX-TO MAX-NG MIGRATION MANUAL 7

Pre-Retrofit Activity – Core Network

MAX-TO MAX-NG MIGRATION MANUAL 9

AREA CODE GROUP CREATION

MAX-TO MAX-NG MIGRATION MANUAL 11

ROUTE DEVICE CREATION

MAX-TO MAX-NG MIGRATION MANUAL 13

MAX-TO MAX-NG MIGRATION MANUAL 15

MAX-TO MAX-NG MIGRATION MANUAL 17

LAG EXCHANGE MAP

MAX-TO MAX-NG MIGRATION MANUAL 19

Pre-Retrofit Activity – Access Network

MAX-TO MAX-NG MIGRATION MANUAL 21

4. Unscrew and remove all the frames of rack.

MAX-TO MAX-NG MIGRATION MANUAL 23

Select Connection Name CDOT-MAX-NG (Give Any Name to The

MAX-TO MAX-NG MIGRATION MANUAL 25

3.5. EXTRACTION OF DATA FROM IOP FOR DIFFERENT BM’S

MAX-TO MAX-NG MIGRATION MANUAL 27

Physical Installation of LAGU System

MAX-TO MAX-NG MIGRATION MANUAL 29

3 Termination and configuration of ANRAX's & PRI's to CACU

Total No. of DAYS for Migration of one MAX exchange 15 DAYS

MAX-TO MAX-NG MIGRATION MANUAL 31

Exchange Details and IP Allocation of

RSUs with IP NIL

3. Availability of spare BM Rack (If spare BM is not available 01

Equipment & IP Address Allocation

RSUs with IP NIL

3. Availability of spare BM Rack (If spare BM is not available YES

MAX-TO MAX-NG MIGRATION MANUAL 33

6. No. of BRI subs NIL

Equipment & IP Address Allocation

RSUs with IP NIL

RSUs without IP NIL

3. Availability of spare BM Rack (If spare BM is not available NIL

5. No. of PRI Links NIL

MAX-TO MAX-NG MIGRATION MANUAL 35

Equipment & IP Address Allocation

RSUs with IP nil

5. No. of PRI Links 1 in SUM BM-3

Equipment & IP Address Allocation

MAX-TO MAX-NG MIGRATION MANUAL 37

5.5. NURPURBEDI (PUNJAB CIRCLE)

1. No. of Co-located LINE BM 1

3. Availability of spare BM Rack (If spare BM is not available NO

5. No. of PRI Links/E1 LINKS 1 E1 LINK EPABX

Equipment & IP Address Allocation