MXNG CACU LAGU INST CONF SITES v01 PDF

C-DOT MAX-NG
MAX-NG ACCESS SOFTWARE

INSTALLATION AND
CONFIGURATION
MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 1

MAX-NG ACCESS SOFTWARE INSTALLATION
AND CONFIGURATION
Important Notes/References:-
a) Please refer to the Audio/Video of CACU/LAGU installation to understand the

physical installation of CACU and LAGU at the sites.
b) For Pre-Migration, Migration and Post-Migration activities please refer the
separate document named MAX-NG-Migration_plan.
c) The list of major documents for migration related activities is mentioned in
Appendix M.
Following are the broad steps in brief for Access nodes (CACU and LAGU) Software
Installations and configuration at the C-DOT BSNL exchanges/sites.
a) The “IP ADDRESS DETAILS” sheet for the site is available with the CACU and
LAGU wise IP addresses allocated (as available in the MAX-NG Rollout Project
Management web portal). Refer Appendix-A.
b) Prepare the Thin Client machine and configure the minicom settings. Refer
Appendix-I (steps 1 to 6).
c) If the MAC address for the MLS cards (MLS1 & MLS2) are mentioned in the “IP
ADDRESS DETAILS”, against the parameter “MLS Card1/2 Management IP
(Gateway-1/2)” then only these need to be allocated to the CACU MLS cards
during IP configuration using minicom. Paste the stickers for the MAC address
allocated on the MLS cards face plate. Refer Appendix-B(Step A)
d) Configure the parameters on the BSNL MPLS routers to enable CACU Link
Redundancy. Refer Appendix J(Step A)
e) Do the MLS cards IP, VLAN and WAN-IP configurations as mentioned in detail in
a separate document named MLS CONFIGURATION MANUAL for MLS card
Configuration. Refer Appendix-D for broad steps.
f) Configure the IP of the Thin Client machine and setting up of TFTP server and
Access software loading as mentioned in the Appendix-I (step 7 onwards).
g) Load the revised MLS software file CEServices3_65-MLSSD1_SW002.dat over

the MLS through GUI. It takes around 5 minutes. Refer Appendix-C.
h) Ensure that the MAC addresses for the cards are allocated and the stickers for the
same are present/ pasted over the card face plates.

i) The NGTJ cards (both LAGU and CACU) have to be loaded with the provided
VER53 uboot and dtb files. It takes around 5 minutes to load these files over the
NGTJ cards. Refer the Appendix-E for uploading these PSG firmware. In case,
somebody needs to install all PSG firmware or FPGA, one can refer to a separate
document named PSG_LOADING_MANUAL.
NOTE: It should be ensured that the on the NGTJ SE3 card, only the revised dtb
file should be loaded and on the NGTJ AE3 card, the revised dtb and uboot files
should be loaded.
It is mandatory to load the uboot version 53 on the RSU LAGU NGTJ cards with
E1 connectivity and to load dtb version 53 on the CACU NGTJ cards.
j) Allocate the CARD-IP addresses to the cards for all the CACU cards using the
minicom cable. Refer to the CACU Installation procedure steps in Appendix-G
(PREREQUISITES: step 7).
k) Allocate the CARD-IP addresses to all the cards for all the LAGU NGTJ cards
using the minicom cable. Refer to the CACU Installation procedure steps in
Appendix-H (step 5).
l) Verify the Uplink connectivity for the CACU and LAGU cards connected and IP
addresses are configured as per IP ADDRESS DETAILS sheet. After that, test the
reachability of the LAGU and CACU cards from the core network.
m) Ensure that the LAGU, CACU and MISC software release/patch deliverables are
loaded over the thin client machine. The details of the deliverables are given in
Appendix-F.
n) Do the automated Installation and configurations for the CACU release software
over the CACU cards (SLM, NGTJ and EBM) which have already been configured
the IPs and are accessible from the thin client machine (having the CACU
deliverables) connected with MLS-1 card. Refer Appendix-G.
o) Kindly refer the guidelines regarding PCM cable (E1) connectivity between the
RSU-LAGU and the CACU-EBM for cable related information in Appendix-K.
p) Connect the LAGU system with the CACU MLS card over the MLS card ethernet
port and do the automated LAGU release software installation and configurations
from the thin client machine with the loaded LAGU release tarball. Refer
Appendix-H.
NOTE: Kindly ensure that the NGTJ Card which is made ACTIVE after
patch/release installation should have the latest/updated CdotLagDbConf.bin present
in /mmc/etc/ directory.
q) The procedure to load mmc RFS to recover a corrupted /mmc partition on the
NGTJ or while loading the mmc rfs for the first time is mentioned in Appendix – L.

Appendix-A
(An example of the IP ADDRESS DETAILS SHEET from Web Portal)
IP ADDRESS DETAILS
SDCA Nimbahera
Starting IP Address 10.188.168.0
Total Used
64 Using IP Range 10.188.168.0 - 10.188.168.63 Network IP 10.188.168.0
IP
CIDR 10.188.168.4
Subnet Mask 255.255.255.192 /26 Gateway(s) Broadcast 10.188.168.63
Prefix 10.188.168.7
WAN IP Details IP TAX WAN SSTP WAN CDOT WAN SPARE WAN
Uplink 1 10.189.73.64/30 10:189:73:68/30 10:189:73:72/30 10:189:73:76/30
Uplink 2 10:189:73:80/30 10:189:73:84/30 10:189:73:88/30 10:189:73:92/30
Total CACU System (with EBM-16) 1
CACU#1 10.188.168.2 - 10.188.168.30

MLS Card1 Network-Self IP 10.188.168.2
MLS Card1 Network-Other IP 10.188.168.3
MLS Card1 Management IP(Gateway-1) 10.188.168.4 (MAC - 00-1D-36-01-CF-51)
MLS Card2 Network-Self IP 10.188.168.5

MLS Card2 Network-Other IP 10.188.168.6
MLS Card2 Management IP(Gateway-2) 10.188.168.7 (MAC - 00-1D-36-01-CF-69)
SLM Floating IP 10.188.168.8
SLM Card1 IP 10.188.168.9
SLM Card2 IP 10.188.168.10
EBM Card1 IP 10.188.168.11
EBM Card2 IP 10.188.168.12
NGTJ Card1
Card IP 10.188.168.13
DSP IP 10.188.168.14
TMG IP 10.188.168.15
SGL2 IP 10.188.168.16
V5 IP 10.188.168.17
PRI IP 10.188.168.18
NGTJ Card2
Card IP 10.188.168.19
DSP IP 10.188.168.20
TMG IP 10.188.168.21
SGL2 IP 10.188.168.22
V5 IP 10.188.168.23
PRI IP 10.188.168.24

Terminal (Thin Client) IP 10.188.168.25
Free IP(s) 10.188.168.26 - 10.188.168.30
Total CACU System (with EBM-32) 0

Total LAGU System 4
LAGU#1 10.188.168.31 - 10.188.168.38

Self eth0 IP 10.188.168.31
Self eth1 IP 10.188.168.32
Mate eth0 IP 10.188.168.33
Mate eth1 IP 10.188.168.34
Floating IP 10.188.168.35
Active DSP IP 10.188.168.36
Standby DSP IP 10.188.168.37
Free IP(s) 10.188.168.38
LAGU#2 10.188.168.39 - 10.188.168.46
Self eth0 IP 10.188.168.39
Self eth1 IP 10.188.168.40
Mate eth0 IP 10.188.168.41
Mate eth1 IP 10.188.168.42

Free IP(s) 10.188.168.46
LAGU#3 10.188.168.47 - 10.188.168.54
Self eth0 IP 10.188.168.47
Self eth1 IP 10.188.168.48
Mate eth0 IP 10.188.168.49
Mate eth1 IP 10.188.168.50
Free IP(s) 10.188.168.54
LAGU#4 10.188.168.55 - 10.188.168.62
Self eth0 IP 10.188.168.55
Self eth1 IP 10.188.168.56
Mate eth0 IP 10.188.168.57
Mate eth1 IP 10.188.168.58
Free IP(s) 10.188.168.62

Appendix-B
(MLS Card MAC and IP Address Entry)
A. MAC ADDRESS ALLOCATIONS IN MLS CARD (with 3.65 static layer-3
version)
The MLS card requires one MAC address for the system itself (CPU) and one for each of the
front ports. The front port SMACs are needed for PAUSE frame generation. So, in total 24
MAC addresses get allocated to each MLS card. We have to reserve a pool of 24 MAC
addresses for each MLS card but need to enter only the first MAC address of the pool as per
the below mentioned steps. The rest of 23 MAC addresses get internally allocated upon entry
of the first MAC for CPU.
NOTE: This procedure is required to be executed only if pool of 24 MAC addresses
have not been already allocated to each MLS card (with steps as mentioned as below
to enter only the first MAC of the 24 MAC pool).
Steps for MAC address allocation:
1. Connect minicom
2. Login to the ICLI (login user: admin password : <enter>)

# platform debug allow
(Assuming MAC Address pool of MLS card is, say 00-01-c1-00-00-01 to 00-01-c1-00-00-18 in hex)
# debug board mac 00-01-c1-00-00-01
# platform debug deny
B. IP ADDRESS ALLOCATIONS IN MLS CARD:

(Refer to the detailed MLS configuration document with snapshots of the GUI
based configurations)
The Management IP address of each MLS card will be used as the gateway IP address
for the CACU cards. The configuration may be done through the CLI or GUI. The
first steps is for assigning IP address to the default VLAN 1 (if not assigned) and then
the GUI using a browser can be used to configure the MLS cards.
Note: The examples of the commands are shown starting with a '#' prompt.
C. LAN AND WAN IP POOL:

Suppose an access site is allocated with:
a) LAN IP pool starting from 10.187.35.0 to 10.187.35.255 of 256 IPs denoted as
10.187.35.0/24 with the two Gateway IPs as 10.187.35.4 & 10.187.35.7
b) The VLAN1 will be created at both MLS cards which is the native VLAN for
the LAN IP pool subnet allocated to that site.

For MLS-1 card VLAN1, configure the Gateway-1 IP as 10.187.35.4 with mask
length as 24.
For MLS-2 card VLAN1, configure the Gateway-2 IP as 10.187.35.7 with mask
length as 24.
The following Steps to be performed using a serial interface/minicom, unless a
default VLAN1 IP address is already assigned.
1. Ensure that the thin-client has been configured as per the details given in the
Appendix-I. Connect Minicom Cable from C-DOT MLS-1 card to Thin
Client/Client PC/ Laptop.
2. Launch Minicom Application in Thin Client/PC/Laptop as a root user.
# minicom
3. Assign an IP address to the VLAN 1 (default) of the C-DOT MLS-1 card as :
#configure terminal
#interface vlan 1
(ip address <ip address of VLAN 1> <netmask>)
#ip address 10.187.35.4 255.255.255.0
#exit
# copy running-config startup–config
# show ip interface brief
(This command will show the ip address which has been configured).
Example:
Interface Address Method Status
--------------------------------------------------
Vlan 1 10.187.35.4 Manual UP

Appendix-C
(MLS Card CEServices3_65-MLSSD1_SW002.dat loading)
Firmware update through GUI of MLS card:
1) Login to MLS through ‘admin’ login from the thin client machine with the MLS
Application software CEServices3_65-MLSSD1_SW002.dat loaded.
2) Ensure that the network configuration data is saved (MaintenanceConfiguration 

Save startup-config)
3) From Maintenance-> Software -> Upload page, Firmware of the card can be updated.
Browse the PC location for the firmware in CEServices3_65-MLSSD1_SW002.dat format.
Click ‘upload’ button. After the software image is uploaded, a page announces that the firmware
update is initiated. After about a minute, the firmware is updated and the switch restarts.
Warning: While the firmware is being updated, Web access appears to be defunct. The front LED
flashes Green/Off with a frequency of 10Hz while the firmware update is in progress. Do not restart
or power off the device at this time or the switch may fail to function afterwards.

Appendix-D
(MLS Card WAN IP CONFIGURATIONs)
NOTE: For exact details, please refer the MLS IP configuration document.
WAN IP POOL:
Suppose an access site is allocated with:
a) For uplink through MLS-1, WAN IP pools are 10.189.107.40/30, 10.189.107.44/30
and 10.189.107.48/30.
b) For redundant uplink through MLS-2 interface, the WAN 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 (MLS and MPLS Router)
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, as follows:
1) Create interfaces for other VLANs (IPTAX, SSTP and CDOT-VOIP) for uplink from
MLS-1 and MLS-2 cards.
2) After the interfaces are added, create IP routes. Create a default route with network
0.0.0.0 with 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.
3) 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 upon 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.
4) On selecting the required port as Trunk all the VLANs 1-4095 will be allowed and Egress
port setting will be by default set as Untag Port VLAN.
5) From the left pane select Spanning tree  Bridge setting and do the STP bridge
configuration with Protocol as RSTP with configuration values as mentioned in
Appendix-J ( Step B, Point no.3 )
6) After all the configurations is done, in the left pane select Configuration  Save startup
config to save the configuration.
7) 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.

Appendix-E
(UBOOT AND DTB FILES LOADING OVER NGTJ CARD)
This new uboot file (NGTJ.u-boot.bin.VER53) is being loaded on the LAGU NGTJ cards because till
the latest uboot releases, EEB modules on the NGTJ cards came up as soon as the card booted, thus
potentially caused network looping when the LAGU was connected to the EBM card of CACU using
the PCM/E1 links. The new release of uboot (version 53) disables the EEB module of the NGTJ card
on boot time and is enabled only by the LAG application.
The new DTB file (NGTJ.dtb.VER53) takes care of the issue of an unhandled interrupt crashing
kernel as soon as NAND flash was accessed through net file.
S/no Deliverable-Name Size(in bytes) Checksum
1. NGTJ.u-boot.bin.VER53 (UBOOT) 369880 4027088522
2. NGTJ.uImage.VER52 (LINUX IMAGE) 3806124 2389537443
3. NGTJ.dtb.VER53 (DTB) 10067 3601580650
4. NGTJ.rfs.s.VER52 (RAM-RFS) 19078430 933627270
5. uboot53.scr 798
6. dtb53.scr 959
NOTE: The revised scripts uboot53.scr and dtb53.scr are provided to avoid the Uboot corruption
issues, in case
 If there is issue with network and no file is transferred from server to NGTJ card.
 If file kept in /tftpboot folder is not correct. That means the file correspond to "ubootfile" or
"dtbfile" in uboot must be available in /tftpboot folder.
In above cases, the UBOOT will go for RESET. The earlier UBOOT or DTB file will be intact in the
NGTJ card and issue of card corruption is avoided.
The following NGTJ cards need to be MANDATORILY LOADED with the mentioned revised
UBOOT/DTB V53 files:
a) CACU NGTJ SE3 card has to be loaded with the revised DTB V53 (NGTJ.dtb.VER53) file only
to take care of NAND flash related issue.
b) The RSU LAGU NGTJ AE3 cards connected over E1 (PCM links) to the CACU-EBM cards
has to be loaded with revised UBOOT V53 (NGTJ.u-boot.bin.VER53) file (to take care of the
looping issues).

c) The spare NGTJ AE3 card supplied in the SDCA should be loaded with both UBOOT and DTB
V53 files; so that this card may be readily available for usage over CACU or LAGU Chassis for
any replacement requirements.
OPTIONALLY, the LAGU NGTJ AE3 cards being used as collocated LAGU and RSU LAGU
connected over Ethernet, may be loaded with both UBOOT and DTB V53 files. So that in case of
any card faults/corruptions, one card out of the duplex LAGU cards may also be used as temporary
replacement for CACU NGTJ SE3 card or RSU LAGU NGTJ AE3 cards connected over E1(PCM
links).
VERIFY THE CURRENT FIRMWARE LOADED IN NGTJ CARD AS FOLLOWS:
# fpga command should give output as:
Control FPGA version is 23 on (NGTJ)

Time switch FPGA version is 21 on (NGTJ)
# cat /etc/issue command gives output as: MAXNG NGTK Console Rel 1.52
(Which specifies the RFS version mainly)
THE UBOOT AND DTB V53 INSTALLATION PROCEDURE FOR

THE NGTJ CARDS :
1) Connect the Chassis with NGTJ card with the power supply and turn on the power.
2) Connect the minicom cable to one of the RS-232 ports for the respective NGTJ card on the
backplane of Chassis.
3) Connect an ethernet cable from the ThinClient/PC to the ethernet ports of LAGU/CACU chassis
with NGTJ card.
[NOTE: Ensure the Ethernet connectivity from NGTJ to thin-client by pinging NGTJ card
from thin-client or vice versa]
4) Ensure that the Appendix-I (I (step-10: c & d) for the Thin Client is followed already for the
TFTP server configuration and following files are copied/transferred at path /var/lib/tftpboot/ of
thinClient :
[As also mentioned at the end for ready reference (***)]
a) NGTJ.u-boot.bin.VER53
b) NGTJ.dtb.VER53
c) uboot53.scr
d) dtb53.scr
NOTE: Verify whether tftp is running on thinclient by executing the following command on
terminal of Thin-Client:
# ps -ef | grep tftp
Output of this command should be as follows:

ubuntu@CPRS:~$ ps -ef|grep tftp
root 29463 1 0 Mar20 ? 00:00:00 /usr/sbin/in.tftpd --listen --user tftp --
address 0.0.0.0:69 --secure /var/lib/tftpboot

5) Verify the correctness of deliverables at path /var/lib/tftpboot/ using the cksum command before
starting the loading procedure. The checksum displayed should match as mentioned in table
above.
# cksum /var/lib/tftpboot/NGTJ*VER53
[ NOTE :- The checksum displayed should match as mentioned in table above ]
6) On the ThinClient/PC, open the minicom application using the command 'minicom -s' to access
the serial port interface and set baud rate to 115200, no flow control as serial port parameters.
After applying the above settings, save them as default and exit to go to the minicom application.
7) Now, jack-in the NGTJ card in that slot to which minicom has been connected in step-2 and press
the reset button in the bottom part of the face plate of NGTJ card.
8) In the minicom terminal window, see if the print ''Autoboot in 6 seconds. Hit 'a' to stop from
Autoboot'' appears, then press the 'a' key to stop the booting so that NGTJ card comes in the uboot
prompt. The uboot prompt as => should appear. If the uboot prompt could not be stopped, press
the reset button on the NGTJ card and try again.
9) In the uboot prompt, do the following steps (steps a to k) :
Note: The IP address settings to be done as per the “IP ADDRESS DETAILS” sheet for the site
Note: “edit” command can also be used instead of “setenv” command in the below
mentioned steps. Usage of edit command:-
=> edit serverip
*existing value stored in the variable “serverip” will be displayed to which is to be edited*
Change it to the desired value and press “Enter” to save it
a) Ensure the IP address of the PC mentioned above is set as the serverip in u-boot command
prompt. To set it use the command:
=> setenv serverip <serverip/IP-address-of-tftp-server-ThinClient/PC>
e.g. => setenv serverip 10.188.168.25
b) Set the IP address of the NGTJ with IP address that is reachable from the ThinClient/PC,
using the command:
=> setenv ipaddr <NGTJ-card-IP>
e.g. => setenv ipaddr 10.188.168.13
c) Set the netmask of the NGTJ card in the uboot as per the “IP ADDRESS DETAILS” sheet
for the site, using the command:
=> setenv netmask <site-netmask>
e.g. => setenv netmask 255.255.255.192
d) Set the gateway IP address of the NGTJ cards as that MLS Card1 for the site.
The command is:
=>setenv gatewayip <MLS1-GW>
e.g. => setenv gatewayip 10.188.168.4
e) Now save the above entries using the command:

=> saveenv
f) Verify the variables which were set above using below mentioned commands(with exact IP
addresses in place of those mentioned in the example IPs below)
=> pri serverip
serverip=10.188.168.25
=> pri ipaddr
ipaddr=10.188.168.13
=> pri netmask
netmask=255.255.255.192
=> pri gatewayip
gatewayip=10.188.168.4
NOTE:- In case of any difference in variable’s value, use the appropriate command
from a) to d) to set that variable with correct value. After that, save the entry using saveenv
command.
g) ping the IP address of the tftp server using the command:

=> ping $serverip
An output as the following should come:

Using UEC0 device
host 10.188.168.25 is alive
NOTE: In case of any error in this step, check the physical ethernet connectivity b/w NGTJ and Thin-
Client. Also, verify that the ipaddr, gatewayip, netmask and serverip are set correctly.
RUN THE COMMANDS MENTIONED BELOW TO FUSE DTB V 53 [

Steps ‘h’ to ‘m’) ]:
Note: The Bytes transferred in the message on screen after execution of commands should be
non zero; else the command should be executed again.
h) => tftp 10000 dtb53.scr
On execution following messages-extract will be printed on screen :
Using UEC0 device

TFTP from server 10.188.168.25; our IP address is 10.188.168.13
Filename 'dtb53.scr'.
Load address: 0x10000
Loading: #
……
done
Bytes transferred = 959 (3bf hex)
[ Note: In case of any error in this step, check the presence of the file dtb53.scr in the /var/lib/tftpboot
directory of thin-client ]

i) => source 10000
On execution following messages-extract will be printed on screen :
## Executing script at 00010000

FUSE DTB(VER53) on NGTJ-V3
Saving Environment to Flash...
Un-Protected 1 sectors
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash...
9....8....7....6....5....4....3....2....1....9....8....7....6....5....4....3....2....1.
...done
Protected 1 sectors
Setting UPDATED
First Change dtbfile with appropriate name by using setenv or edit command
Copy the dtbfile to /tftpboot folder of serverip
Make sure the serverip is pinging. Dont proceed if server is not pinging
Then Type run FUSE_DTB and press Enter
j) => setenv dtbfile NGTJ.dtb.VER53
k) => saveenv
l) => run FUSE_DTB
Note: Following output must be seen on minicom

********************************************************
=> run FUSE_DTB
FUSING DTB
TFTP DTB File
Using UEC0 device
Filename 'NGTJ.dtb.VER53'.
Loading: #
….
done
Bytes transferred = 10067 (2753 hex)
ERASING DTB
.... done
Erased 4 sectors
COPING DTB to NOR
Copy to Flash... 9....8....7....6....5....4....3....2....1....done
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash...
9....8....7....6....5....4....3....2....1....9....8....7....6....5....4....3....2....1.
...done
Protected 1 sectors

FUSING DTB SUCCESS
***********************************************************
[ Note: In case of any error in this step, check the presence of the file NGTJ.dtb.VER53 in the
/var/lib/tftpboot directory of thin-client]
m) Reboot the card using below mentioned command

=> boot
RUN THE COMMANDs TO FUSE UBOOT [Steps ‘n’ to ‘u’) ]:

Note: The Bytes transferred in the message on screen after execution of commands should be
non zero; else the command should be executed again.
n) In the minicom terminal window, see if the print ‘Autoboot in 6 seconds. Hit 'a' to stop from
Autoboot'' appears, then press the 'a' key to stop the booting so that NGTJ card comes in the
uboot prompt. The uboot prompt as => should appear. If the uboot prompt could not be
stopped, press the reset button on the NGTJ card and try again
o) => tftp 10000 uboot53.scr

On execution following messages-extract be printed on screen :
Using UEC0 device

Filename 'uboot53.scr'.
Loading: #
…..
done
Bytes transferred = 798 (31e hex)
[ Note: In case of error of “file not found”, ensure the presence of the file uboot53.scr in the
/var/lib/tftpboot directory of thin-client]
p) => source 10000

On execution following messages-extract be printed on screen :
## Executing script at 00010000

FUSE UBOOT on NGTJ-V3
Setting UPDATED
First Change ubootfile with appropriate name by using setenv or edit command
Copy the ubootfile to /tftpboot folder of serverip
Make sure the serverip is pinging. Dont proceed if server is not pinging
Then Type run FUSE_UBOOT and press Enter
q) => setenv ubootfile NGTJ.u-boot.bin.VER53
r) => saveenv

s) => run FUSE_UBOOT
NOTE: Before executing command "=> run FUSE_UBOOT" it must be ensured that
the two commands "=> setenv ubootfile NGTJ.u-boot.bin.VER53" and thereafter
"=>saveenv" have been run.
Note: Following output must be seen on minicom

*******************************************************************************
=> run FUSE_UBOOT
Using UEC0 device
Filename 'NGTJ.u-boot.bin.VER53'.
Loading: ##########################
….
done
Bytes transferred = 369880 (5a4d8 hex)
Un-Protect Flash Sectors 0-10 in Bank # 1
Erase Flash Sectors 0-10 in Bank # 1
........... done
Copy to Flash... 9....8....7....6....5....4....3....2....1....done
Protect Flash Sectors 0-10 in Bank # 1
Erasing Flash...
. done
Erased 1 sectors
Writing to Flash...
9....8....7....6....5....4....3....2....1....9....8....7....6....5....4....3....2....1.
...done
Protected 1 sectors
FUSING UBOOT SUCCESS
*******************************************************************************
[ Note: In case of the error of “file not found”, ensure the presence of the file NGTJ.u-
boot.bin.VER53 in the /var/lib/tftpboot directory of thin-client.
VERY IMPORTANT NOTE:

 After execution of commands "=>run FUSE_DTB” or “=>run FUSE_UBOOT " if
one sees messages on screen like :
...
Load address : 0x7000000
Loading: T T T T ...
Then it means that that there is some network issue and in this case operator may
press “CTRL-C” to interrupt above messages and the card will reset on its own
thereafter. One may also physically reset the card by pressing “reset” button on the
NGTJ card front plate in such a case.
In case set “ubootfile” or “dtbfile” is absent in tftp-server, then the card will reset
automatically after displaying “Tftp error:file not found” message.

 Finally operator must check that after executing "=>reset" command that "U-boot
5.3..." is appearing on screen. If instead "U-boot 5.2 ...." is printed then it means
one has missed some step somewhere and will have to repeat the "U-boot loading"
procedure.
t) => reset
NOTE:-
operator must check that after executing "=>reset" command that "U-boot 5.3..." is
appearing on screen. If instead "U-boot 5.2 ...." is printed then it means one has missed some
step somewhere and will have to repeat the "U-boot loading" procedure.
u) Login into the card using “user/password = root/root”.
***FOR REFERENCE: Appendix-I Step- 10 (c & d) for Thin Client regarding TFTP
configuration & UBOOT/DTB V53 files copying
c. Following steps need to be followed for installation of the tftp server over thin client and
copy the relevant drivers at the /var/lib/tftpboot/ path:
(Please enter the Ubuntu user password when prompted)
a. cd <path-where-UBOOT_DTB-V53.tar is present>
b. tar –xvf UBOOT_DTB-V53.tar
c. sudo dpkg -i MXNG-1.0-tftpd-THIN-CLIENT.deb
d. sudo cp tftp /etc/xinetd.d/
NOTE: Verify whether tftp is successfully installed or not, check the presence
of the directory /var/lib/tftpboot/ by using following command.
# ls –lrt /var/lib/tftpboot
Output of this command should NOT show that “No such file or directory”
d. Now, copy the UBOOT-V53, DTB-V53 and other script files to /var/lib/tftpboot
a. sudo cp NGTJ.u-boot.bin.VER53 /var/lib/tftpboot/

b. sudo cp NGTJ.dtb.VER53 /var/lib/tftpboot/
c. sudo cp uboot53.scr /var/lib/tftpboot/
d. sudo cp dtb53.scr /var/lib/tftpboot/

Appendix-F
(LAGU and CACU Release Deliverables)
1) LAGU APPLICATION DELIVERABLE DETAILS:
1) MXNG-LAGU1.0.zip – 25963979 bytes

2) MXNG-LAGU1.0-Relnote.pdf
Details of product wise Release and Patches contained in the above zip file:
a) run_lagu_install.sh – 91829 bytes

b) XEYEPL1_1_2.12_1.zip – 137336 bytes :
1) LAGU-XEYEPL1_1_2.12_1-Deliverables.txt ( 372 bytes)
2) PATCH13-Over-SWINSTL1_1_2.16_1-SWBELAG-COMB.tar – 276480 bytes
3) bkrs_lagbackend.tar – 215040 bytes
4) PATCH5-Over-SWINSTL1_1_2.16_1-SCHDBACKUP_RESTORE.tar – 10240 bytes
c) TEMP-OVER-XEYEPL2.12.zip – 25204416 bytes :

1) LAGU-TEMP-OVER-XEYEPL2.12-Deliverables.txt (572 bytes)
2) clagl2_4_1.2_1-lagagent.tar – 10270720 bytes
3) clagl2_4_1.2_1-linuxagent.tar – 3532800 bytes
4) lagconf_1.2.tar – 8488960 bytes
5) lagrel_1.2.tar – 46202880 bytes
6) PATCH16-Over-CLAGL2_4_1.2_1-lagagent-KillingOnCliDataUpdation–10291200 bytes
7) PATCH17-Over-CLAGL2_4_1.2_1-DTMF_CDR_DSP_LAGU – 7270400 bytes
2) CACU APPLICATION DELIVERABLE DETAILS:
1) MXNG-CACU1.0.zip – 78353640 bytes

2) MXNG-CACU1.0- Relnote.docx
Details of product wise Release and Patches contained in the above zip files:
1. XEYEPL1_1_2.12_1.zip – 46437212 bytes

2. TEMP-OVER-XEYEPL2.12.zip – 30716982 bytes
3. NGTJ_DRIVERS-REL5.zip – 1178511 bytes
4. install_cacu_cards-v1.1.sh– 107397 bytes
a) XEYEPL1_1_2.12_1.zip:
1. XEYEPL1_1_2.12_1-Deliverables.txt (908 bytes)
2. V5AG Patch: PATCH9-Over-AGL1_1_3.4_1-AI-DEL-MOD.tar (113592320 bytes)
3. NGTJ card EMS Agent tar file: gwyagentl3_1_1.5_1-NGTJCardAgent.tar (8990720
bytes)
4. PRIAG EMS Agent tar file: PATCH1-Over-GWYAGENTL3_1_1.5_1-
PriAgentNGTJ.tar (686080 bytes)
5. TMG EMS Agent tar file: PATCH2-Over-GWYAGENTL3_1_1.5_1-
TmgAgentNGTJ.tar (460800 bytes)

6. V5AG EMS Agent tar file: PATCH4-Over-GWYAGENTL3_1_1.5_1-
V5AgentNGTJ.tar (1433600 bytes)
7. NGTJ I2C Agent Patch :PATCH7-Over-NGTJCDL1_1_1.6_1-I2CAGNT-READ-
UPDATE.tar (61440 bytes)
8. NGTJ Common deliverables patch: PATCH13-Over-NGTJCDL1_1_1.6_1-NEW-
PRIAG-COMPATIBLE-MASTER.tar (2508800 bytes)
9. CACU Chassis NGEMS Agent: slml1_1_1.5_1-ChassisAgent.tar (9144320 bytes)
10. SLM card patch deliverable: PATCH15-Over-SLML1_1_1.5_1-DUAL-NTP-
PRIAG-SHM.tar (163840 bytes)
b) TEMP-OVER-XEYEPL2.12.zip:
1. TEMP-OVER-XEYEPL2.12-Deliverables.txt (579 bytes)
2. CDOT Trunk Media Release TAR for CACU Solution: PATCH1-Over-
CDTMGL1_1_1.9_1-NGTJ-CACU.tar (5396480 bytes)
3. CACU EBM EMS Agent : ebml1_1_1.7_1-EBMCardAgent.tar ( 8970240 bytes)
4. EBM Release TAR : eebrel_1.7.tar (81920 bytes)
5. Patch Deliverables CACU EBML1_1_1.7_1: PATCH1-Over-EBML1_1_1.7_1-
DISPL-INVALID-PORT-NUM.tar (20480 bytes)
6. PRI Gateway Release: PRIGATEWAYL1_1_1.2_1.tar (73062400 bytes)
7. Patch Deliverables SGL1_3_1.9_1: PATCH1-Over-SGL1_3_1.9_1-INIT-CACU-
ONLY.tar (3225600 bytes)
c) NGTJ_DRIVERS-REL5.zip :
1. NGTJ_DRIVERS-REL5-Deliverables.txt (314 bytes)
2. CACU Drivers TAR : NGTJ_DRIVER_CACU-REL5.tar (4485120 bytes)
3. PSG Utilities TAR: PSG_NGTJ_UTILS_REL1.tar (778240 bytes)
4. Installation Script : install_ngtj_drivers.sh (2684 bytes)
3) MISC ACCESS SOFTWARE
1) MXNG-MISC1.0.zip – 139512487 bytes
Details of product wise Release and Patches contained in the above zip file:
a) MLS :
1) CEServices3_65-MLSSD1_SW002.dat (5,466,769 bytes)
b) NGTJ Card Drivers and loading scripts :
1) UBOOT_DTB-V53.tar (1556480 bytes)
c) THIN CLIENT Deliverables :
1) MXNG-1.0-NFS-SRVR-FOR-THIN-CLIENT.tar (4,085,760 bytes)
2) thin_client_nfs_installer.sh (2377 bytes)
3) MXNG-1.0-tftpd-THIN-CLIENT.deb (44,938 bytes)
4) tftp (384 bytes)
5) java.policy (4958 bytes)
6) thinclient_ipconf_gw.sh (14971 bytes)
d) BULK_RETROFIT Deliverables :
1) PATCH10-Over-MXMIGRL1_1_1.2_1-LAG_BULK_FROM_ITPC_VER2.tar(143660 bytes)
2) lagbulk_README.docx
3) anbulk.sh (4486 bytes)
4) anbulk_README
e) PSG_Deliverables

Appendix-G
(Automated Installations for CACU Application Release/Patch)
PREREQUISITES:
1) The application release CEServices3_65-MLSSD1_SW002.dat should be loaded on both
the MLS cards of the CACU.
2) The dtb file for the NGTJ card should be loaded on the SE3 or AE3 NGTJ card to be used
in the CACU.
3) The CACU deliverables described in the Appendix-F, part 2 should be copied to a
directory on the thin-client/PC from where application release installation has to be done
on the CACU cards.
4) A detailed list of IP addresses to be allocated to the cards of CAU should be present as
described in the Appendix - A.
5) The thin-client should have been configured and readied according to the Appendix-I.
6) Connect an RS-232/minicom cable to the thin-client at one end and with the minicom
serial port behind each card slot one by one to assign IP addresses to the cards.
7) Log-in to the cards via the minicom using the username “root” and password “root”. The
process to assign IP addresses to the every type of CACU cards is described as follows:
 For MLS card IP settings; set the VLAN1 (native default VLAN) IP address. See
Appendix-B for reference.
 For SLM cards IP settings (eth1 port is used)

 #mount -t jffs2 /dev/mtdblock5 /jffs2
 #cd /jffs2/conf
 # > net
 #vi net
 Press ‘i’ to enter the INSERT mode of vi editor and then add/edit the
following 3 lines of net file.
ifconfig eth1 down
ifconfig eth1 <SLM-CARD-IP-ADDR> netmask <netmask> up
route add default gw <Gateway-IP-Addr>
 After editing the file successfully, save and exit the net file by first pressing
the ‘ESC’ key and then “:wq” and then press ENTER key
 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)

Note: In case the CACU NGTJ card is not accessible from minicom, login to the NGTJ card from
the Thin /Client using “ssh root@<NGTJcard-IP-Address>” (with the default IP address allocated
to the card by the manufacturer). Before this step, the Thin Client should also be set with the default
IP subnet of the NGTJ card, so that the NGTJ card can be accessed from the Thin Client machine.
And after changing the IP of the NGTJ SE3 card for the site IP, the Thin Client IP should be
reverted to the site wise IP for the thin client.

 #mount /dev/mtdblock0 /jffs2
 #cd /jffs2/conf
 # > net
 #vi net
 Press ‘i’ to enter the INSERT mode of vi editor and then add/edit the
following 3 lines of net file.
ifconfig eth0 down
ifconfig eth0 <NGTJ-CARD-IP-ADDR> netmask <netmask> up
 Save the net file by pressing Esc key and then typing :wq and then press
Enter/Return key.
 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 4 lines using ‘vi’, with the i and save
the net file (using a sequence of Esc, :wq and Enter commad on vi editor)
ifconfig eth0 <EBM-CARD-IP-ADDR> netmask <netmask> up
cd /cdot/bin
./bcm_rst
After this, press “Esc” key then type “:wq!” and then press “Enter” key
Once the above is ensured, proceed with the actual installation of the application software
release as given below.
SOFTWARE INSTALLATION PROCEDURE:
1) Switch to the root user on the thin-client/PC (to be used for further installation process), if
not already using the command ‘su - root’.
2) Now connect the thin-client with any free Ethernet port (RJ-45) available on the MLS-1
card at the 7th slot of the CACU chassis.
3) Assign an IP address to the thin-client (or PC) using the IP address available at the site as
detailed in the Appendix I (steps 7 onwards).
4) Copy the CACU deliverable zip file named MXNG-CACU1.0.zip (mentioned in Appendix – F)
in the thin-client at a directory (such as /home/ubuntu/) and extract it using the command:
#unzip MXNG-CACU1.0.zip
Note that the operator can copy the deliverable zip file MXNG-CACU1.0.zip to any other
path such as /home/ubuntu/Desktop, but there should be NO blank space in the path name.

5) On the thin-client/PC for installation, go to the path where CACU application release
deliverables have been copied using the command (eg /home/ubuntu directory here):
#cd /home/ubuntu/MXNG-CACU1.0
6) Now, give the script named install_cacu_cards-v1.1.sh executable permission using the
command
#chmod +x *sh
7) Execute the script using the command:
#./install_cacu_cards-v1.1.sh
8) When the script is run for the first time on a particular thin-client/PC, the script will initiate the
unzipping of the release/patch files locally to arrange them in a structure as required during the
installation on the cards.
9) Once the unzipping is complete, the script asks for the Type of CACU system. For MAX-NG, it
must be entered as 1. Output is similar to
Enter Configuration Type, 1 for MAX-NG or 2 for The Red Network

The Configuration Selected for installation is 1
Enter Y/y to continue with above entered config or no to enter new one
Press y in this step
10) After this, the script will ask for input for various parameters such as the IP addresses for the
CACU, IP address of the NGEMS, NGSM, NTP server etc. The sample output is:
Configuration file is not present, all the values need to be filled

All the values need to be entered:
Enter the Configuration Type for CACU
Already Entered Configuration is 1. Want to continue with it?
Enter y/Y to Continue with Above entered configuration or n/N to enter
new one
y
Continuing with configuration 1
The Updated Configuration value is 1
Enter the Start IP for CACU
Enter Start IP For CACU Range
10.187.212.2
The updated Start-IP is 10.187.212.2
Enter the End IP for CACU
Enter End IP For CACU Range
10.187.212.25
Final output 10.187.212.25
End IP is as expected
The updated End-IP is 10.187.212.25
Enter the GateWay IP for CACU
Enter Gateway IP For CACU
10.187.212.4
The updated Gateway-IP is 10.187.212.4
Enter the BroadCast IP for CACU
Enter BroadCast IP For CACU
10.187.212.63

The updated Broadcast-IP is 10.187.212.63
Enter the NetMask for CACU
Enter NetMask for CACU
255.255.255.192
The updated Netmask value is 255.255.255.192
Enter the IP Offset for Usable IP
Enter Offset for Starting IP range, Default will be 0
0
The Updated Number of IP start offset is 0
Enter the System Name to be used in NGEMS Manager
Enter System Name For Agent Configuration
CACU_NUH
The Updated System Name is CACU_NUH
Enter the Region
Enter Region Code
North_HA_1267
The Updated Region Code is North_HA_1267
Enter the Number of NGEMS Manager
Enter Number of EMS Managers, Default will be 1
4
The Updated Number of EMS Managers is 4
Enter the IP Addresses for NGEMS Manager 1 to Number of Managers
[ Entered value is 4]
The Number of NGEMS Manager is 4
The NGEMS Manager IPs will be Entered Sequentially
First 2 IP Addresses for PR and the next 2 IP Addresses for GR
NGEMS Managers
Enter NGEMS Manager IP Address 1 [ PR 1 ]
10.187.0.39
Entered value NGEMS Manager 1 [ PR 1 ] IP Address is 10.187.0.39
Enter NGEMS Manager IP Address 2 [ PR 2 ]
10.187.0.40
Entered value for NGEMS Manager 2[PR 2 ]IP Address is 10.187.0.40
Enter NGEMS Manager IP Address 3 [ GR 1 ]
10.187.1.167
Entered value for NGEMS Manager 3[GR 1]IP Address is 10.187.1.167
Enter NGEMS Manager IP Address 4 [ GR 2 ]
10.187.1.168
Entered value for NGEMS Manager 4[GR 2]IP Address is 10.187.1.168
The updated NGEMS Manager IP(s) is/are
PR 1 NGEMS Manager IP Address: 10.187.0.39
PR 2 NGEMS Manager IP Address: 10.187.0.40
GR 1 NGEMS Manager IP Address: 10.187.1.167
GR 2 NGEMS Manager IP Address: 10.187.1.168
Enter the Number of NGSM
Enter Number of NGSM, Default will be 4
4
The Updated Number of NGSM is 4
Enter the IP Addresses for NGSM Manager 1 to Number of NGSM
Managers [ Entered value is 4]
The Number of NGSM is 4
The NGSM IP Addresses will be Entered Sequentially
First 2 IP Addresses for PR and the next 2 IP Addresses for GR
NGSMs

Enter NGSM IP Address 1 [ PR 1 ]
10.187.0.22
Entered value for NGSM 1 [ PR 1 ] IP Address is 10.187.0.22
Enter NGSM IP Address 2 [ PR 2 ]
10.187.0.23
Entered value for NGSM 2 [ PR 2 ] IP Address is 10.187.0.23
Enter NGSM IP Address 3 [ GR 1 ]
10.187.1.150
Entered value for NGSM 3 [ GR 1 ] IP Address is 10.187.1.150
Enter NGSM IP Address 4 [ GR 2 ]
10.187.1.151
Entered value for NGSM 4 [ GR 2 ] IP Address is 10.187.1.151
The updated NGSM IP(s) is/are
PR 1 NGSM IP Address: 10.187.0.22
PR 2 NGSM IP Address: 10.187.0.23
GR 1 NGSM IP Address: 10.187.1.150
GR 2 NGSM IP Address: 10.187.1.151
Enter the IP of the NTP Server
Enter PR NTP Server IP Address
10.187.4.12
The updated PR NTP server IP is 10.187.4.12
Enter the GR NTP Server IP Address
Enter the IP Address of the GR NTP Server
Enter GR NTP Server IP Address
10.187.4.140
The updated GR NTP server IP is 10.187.4.140
Enter the Periodicity to sync with NTP server (in seconds)
Enter Periodicity for syncing with NTP Server, Default will be
600 (Value will be in seconds)
900
The Updated NTP periodicity (in seconds) is 900
Note: The above IP address, ports, system name etc are just an
indicative example and the actual entries must be entered according
to the field data.
Sometimes an older configuration file is copied to the directory MXNG-CACU1.0 to

speed up the configuration entry, an additional entry for the GR NTP server IP address
will be asked. The output will be similar to:
An old configuration file was present

The NTP server IP address already present in the file will be
assigned as PR NTP server
A New GR NTP server IP address will be asked from the user
Enter GR NTP Server IP Address
10.187.4.140
In this case, the user should enter the IP address of the GR NTP server.
11) Now the user is displayed the values that have been entered so far and is asked whether these
values have to be changed (eg in case of some discrepancy). Note that these are the example
values which have been entered above and should be entered according to the site.

The conf file created is as follows:
Note 1: The values marked as <blank> are just for display, they
will not be sent to card.
Note 2: In case of Configuration 2 Entries corresponding to NGSM

will not be used, even if present.
Configuration File is present with values:

[1] Configuration Type for CACU: 1
[2] Start IP of the CACU range: 10.187.212.2
[3] End IP of the CACU range: 10.187.212.25
[4] Gateway IP for CACU: 10.187.212.4
[5] Broadcast IP for CACU: 10.187.212.63
[6] NetMask: 255.255.255.192
[7] Offest to Start usable IP: 0
[8] System Name used for EMS: CACU_NUH
[9] Region Name to be used in EMS: North_HA_1267
[10] Number of EMS Managers: 4
[11] IP Address of EMS Manager1: 10.187.0.39
IP Address of EMS Manager2: 10.187.0.40
[12] Number of NGSM: 4
[13] IP Address of NGSM 1: 10.187.0.22
IP Address of NGSM 2: 10.187.0.23
[14] IP Address of the PR NTP server: 10.187.4.12
[15] IP Address of the GR NTP server: 10.187.4.140
[16] Periodicity to sync with NTP server (In Seconds): 900
[0] To Proceed
Enter the option corresponding to the value to be changed
0
To change any value, enter the number corresponding to it, such as to change the
NGEMS Region Name, enter 9 or to change the broadcast IP address, enter 5.
To proceed (without changing these entries or after changing particular entry), enter 0.
12) After this the script asks whether the IP addresses on the CACU cards have been updated, this
should be confirmed by entering ‘Y’ if the steps in the prerequisites have been completed, else,
the script should be exited and the IP addresses should be first assigned to the cards.
********
The physical card IPs for CACU chassis are:
MLS1 = 10.187.212.4
MLS2 = 10.187.212.7
SLM1 = 10.187.212.9
SLM2 = 10.187.212.10
EBM1 = 10.187.212.11
EBM2 = 10.187.212.12
NGTJ1 = 10.187.212.13
NGTJ2 = 10.187.212.19
********

Above IPs present at
/home/ubuntu/MXNG-CACU1.0/physical_ip_list.txt for reference
Please make sure these values are assigned as card IPs,

Enter (y/Y) to confirm or 0 to exit installation and assign IPs
to cards
y
13) Once done that is ‘Y’ has been entered to confirm and proceed, the script will ask the following
option:
Available options are:

[1] For Release and Patch Installation and Configuration
[2] For Patch Only Installation (If Applicable)
[0] To Exit without Installation
Select your option
1
During the field migration installation of the CACU for the first time, the user must select the
option 1, that is for installation and configuration, since the patches are equivalent to release. Even
for the migrated sites, the option 1 should be selected and the data will be backup and restored.
The option 2 for patch installation will be used in the future releases and explained when to be
used.
14) After this step, the script prompts for the card on which the installation has to be done, through a
following menu:
Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[4] Go Back to Previous menu
[0] To Exit
Enter Your Option

The user should select each of the cards, that is for the SLM, NGTJ and EBM cards one by
one and the script returns to ask for this input again.
Once a card type is selected, the script will proceed with that card and after the installation is
complete on that card, the script will present the same menu for the other cards.
15) After any card type is selected, the user will be prompted for the IP address of the card to be
confirmed and then some other input parameters for the cards. For SLM card, the script will also
ask if the setup is in a simplex or duplex SLM configuration. Example, duplex SLM here.
Installation For SLM Selected
Is the system in Duplex (Y/y) or Simplex(Press Enter)

y
Duplex case selected

16) The user is shown a prompt to enter the IP address of the card(s):
Enter IP Address for 1st SLM
10.187.212.9
Enter IP Address for 2nd SLM
10.187.212.10

17) Now, when the user enters an IP addresses, here 10.187.212.9 is an example, the ssh
prompt is shown, something similar to the following:
Creating Connection for User:root to the Card(10.187.212.9)

The authenticity of host '10.187.212.9 (10.187.212.9)' can't be
established.
RSA key fingerprint is c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e.
Are you sure you want to continue connecting (yes/no)?
Here, type yes and press Enter.
In the above example, 10.187.212.9 is the IP address of the SLM card on which installation is
being done and c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e is the ssh RSA key for that
particular CACU card (SLM/EBM or NGTJ). These two values will be different for every card
depending upon the site.
18) This will display an output as the following and ask for the password for the root user of CACU
card (SLM/EBM/NGTJ) on which the installation option has been selected :
Warning: Permanently added '10.187.212.9' (RSA) to the list of
known hosts.
root@10.187.212.9's password: (Default is root)
Now try logging into the machine, with "ssh 'root@10.187.212.9'",
and check in:
.ssh/authorized_keys
to make sure we haven't added extra keys that you weren't

expecting.
NOTE: This “warning” is not actually an error or a warning and should be ignored.
Similar prints and entry for the password of the root used of the other SLM card (duplex case)
will be asked and should be entered.
19) After this, the user will be asked if the backup of the configuration has to be taken
Enter Y/y for taking and restoring backup Or N/n to skip backup
n
For the first time installation, the backup option should be selected as n.
20) During the installation of the SLM cards, some prints would be shown related to file transfer and
file creation. One input will be asked related to the secure connection between the active and
stand-by SLM cards, which will be something similar to the following:
******************************************************
* ssh key file not present on this system

* You will have to press enter thrice in a row
******************************************************
Here, the user will be have to press the Enter key thrice for the secure key creation.

21) Once the installation is finished on the SLM cards (simplex or duplex), the script will show the
following output
ssh: : Temporary failure in name resolution

Selected Operation Completed.
NOTE: This temporary failure is not an error or a failure, but is shown because the entry of
that particular SLM card was not yet present in the DNS. This should be ignored.
22) Now the user will again presented the main menu of the script and the user should select the
application release installation for other CACU card, say NGTJ card.
Select Option for Another Card

Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
2
Installation for NGTJ Selected
23) Again the IP address of the NGTJ card will be asked and output similar to steps 15 and 16 will be
presented. Such warnings are to be ignored The output will be similar to as follows:
Enter IP Address of NGTJ

10.187.212.13
Creating Connection for User:root to the Card(10.187.212.13)

established.
RSA key fingerprint is
ba:7f:2f:86:f5:6f:92:d8:05:7c:db:2e:65:df:07:dc.
Are you sure you want to continue connecting (yes/no)? yes
known hosts.
root@10.187.212.13's password: (Default is root)
Now try logging into the machine, with "ssh
'root@10.187.212.13'", and check in:
.ssh/authorized_keys
to make sure we haven't added extra keys that you weren't
expecting.
Here, the IP address 10.187.212.13 is just an example IP address for the CACU NGTJ card.
24) Now the operator is presented with some information regarding the NGTJ card OS release version
and the FPGA version. When asked to continue with the installation, the operator should enter ‘y’.
NGTJ release on NGTJ 10.187.212.13 is 1.52 and Control FPGA

version is 23 on (NGTJ)

NGTJ @ 10.187.212.13 has 72% free space left
Do you want to continue? (Y/y to continue, Press Enter to exit)
y
You have selected to Continue with the installation
25) After this, the user will be asked to take the backup of the configuration files.
Enter Y/y for taking and restoring backup Or N/n to skip backup
n
For the first time installation, the backup option should be selected as n.
The backup should be taken if the users and other data has already been created before.
26) Once the initial I2C driver related installation is done on the NGTJ card, a welcome message is
displayed to the operator, that looks similar to:
@@@@@@@@@@ @@@@@
@@@@@@@@@@ @@@@@
@@@@@@@@@@ @@@@@
@@@@@
@@@@@ @@@@@
@@@@@ @@@@@
@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@
@@@@@@@@@@@@@@@@@
C-DOT
At the end of this text it asks whether the operator wants to continue with the installation and
to modify the ‘default input’ file. The operator should continue (y) with the installation and
should not modify the ‘default input’ file. The screen output is:
:-continue?:-: :Want to continue with installation ?[ [n]/y ]:

y
Here, ‘y’ should be entered to proceed with the installation.
27) Upon continuing with the installation of the CACU NGTJ card, some other inputs will also be
taken from the user. These include the C5 server IP address, C4 server IP address, whether to
enable a particular gateway on the NGJT card and likewise. The output is shown as follows:
Want to install 'ALL NGTJ APPLICATION softwares' ?[n/y]: y
Want enable to run v5ag after installation?[n/y]: y
Want enable to run priag after installation?[n/y]: y
Want enable to run tmg after installation?[n/y]: y
Want enable to run sgl2_start after installation?[n/y]: y

::install (y,y,y,y,y)=--==> enable(y y y y)
Here the operator should select ‘y’ installing a particular gateway on the NGTJ card and for
enabling particular gateway according to the site (as shown in the example above).

28) Once the above fields are entered, some configuration entries will be asked from the operator,
such as the IP addresses of the C5 and C4 servers, enabling PR/DR feature configuration,
domain name, IP addresses of the nameservers, domain name of the sbc etc. (r may be
pressed in a later installation when these values are known to be present already, but for the
first time site migration configuration, the values should be entered according to the site. r is
for repeating and using the value being shown). The output shown is as follows:
: 'Want to enable PR/GR feature' ?[n/y]: y
Note: 'r' means the indicated value is correct
[120s] [1/3]:: INPUT THE VALUE OF DOMAIN NAME: maxng.bsnl.in

[r]: maxng.bsnl.in
[120s] [1/3]:: INPUT THE VALUE OF nameserver [SBC] of PR:

192.168.149.118 [r]: 10.187.1.12
[120s] [1/3]:: INPUT THE VALUE OF nameserver [SBC] of GR:

192.168.109.183 [r]:
10.187.4.12
[120s] [1/3]:: INPUT THE VALUE OF DOMAIN NAME of 'sbc':

sbc.maxng.bsnl.in [r]: sbc.maxng.bsnl.in
[120s] [1/3]:: Input 'P.R.' Floating Ip Of C4 (Primary_mgc):

192.168.103.159 [r]: 10.187.0.12
[120s] [1/3]:: Input 'G.R.' Floating Ip Of C4 (Secondary_mgc):

192.168.119.224 [r]: 10.187.0.15
In the example above, '10.187.212.13' is NGTJ card IP address.

10.187.0.12 is the ’P.R.’ Floating IP of C4 server, whereas 10.187.0.15 is the
‘G.R.’ Floating IP of C4 server.
29) Alternatively, if the operator does not want to configure the DR feature, the C5 IP address is
asked as well and the entries related to the domain name are not asked. The output shown is as
follows, when the DR feature is not configured:
Want to install 'Want to enable PR/GR feature' ?[n/y]: n
[120s] [1/3]:: INPUT THE VALUE OF C5: 196.1.106.100 [r]:

10.187.0.15
[120s] [1/3]:: Input The Value Of Primary C4: 192.168.103.159

[r]:
10.187.0.12
In the example above, the DR feature was not enabled selecting ‘n’,'10.187.0.15' is the
C5 server IP address and 10.187.0.12 is the C4 server IP address.
For points related to the PRI gateway configuration parameters, following (y,y,n) be entered.
Do you want to use country code in PRI GATEWAY ? [ y/n ]: y
Do you want to enable CDR at PRI GATEWAY ? [ y/n ]: y
Do you want to run PRI GATEWAY in CPE(PBX) mode? [ y/n ]: n
30) After these values are provided by the operator, the values are confirmed and the operator is asked
whether to proceed with the installation. ‘y’ should be entered to proceed/re-confirm proceeding
with the installation.
Press y to continue or n to modify above inputs? [ y/n ]: y
Verify these input values

prcd?(y)
[41s]:Want to proceed with these input values...[n/y]: y
31) In case the operator opts to not proceed with the installation, the options presented by the script
are
continue:Want to continue with installation ?[ [n]/y ]: n
: Want to continue installation?: :Press 'y' to Confirm , :

'n' no, I want to exit ... n
32) When the installation option is selected (Point 29), a list of the files to be installed on the NGTJ
card is shown and the file transfer to the NGTJ card starts, where you will be prompted to enter
‘y’ in intervals.
33) Once the installation step reaches the SG installation, it also asks for some inputs, related to the
SG server and PR-GR configuration.
The output is similar to the following and the user should enter the values asked:
Please wait... Processing.....
Enter Domain Name of SG : sgppp
Please wait.... SG tarball is processing.....

Enter PR SGP SERVER VIRTUAL_IP : 192.168.200.70
Enter PR SGP SERVER Bcast_ipAddr : 192.168.200.255
Enter PR SGP SERVER NodeId1 ipAddr : 192.168.200.2
Enter PR SGP SERVER NodeId2 ipAddr : 192.168.200.4
Enter GR SGP SERVER VIRTUAL_IP : 192.168.200.6

Enter GR SGP SERVER NodeId1 Bcast_ipAddr : 192.168.200.8
Enter GR SGP SERVER NodeId1 ipAddr : 192.168.200.10
Enter GR SGP SERVER NodeId2 ipAddr : 192.168.200.12
Please wait, Processing...
please wait... Building tarball for CACU : ngtj
Please wait....Installation in progress ..

TERM environment variable not set.
Sat Sep 23 15:06:10 IST 2017

Installing stk_sgl2 ........
stk_sgl2 installed ...
34) The installation for SGL2 starts after this and when the SGL2 installation is finished, a following
message is displayed:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
!!!! 10.187.212.21 :sgl2 installed sucessfully!!!!
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
35) When the installation of release is completed on the NGTJ card, the NGEMS agent installation on
the NGTJ card, per gateway is asked, and the user should enter ‘y’ according to the access
gateways installed on the CACU NGTJ card. An example output is:
Agent directory created on NGTJ card...

Do you want to install NGTJ card EMS Agent? (y/Y) or Enter to
skip
y
In the above example, the NGTJ card Agent has been selected for installation and the user has
selected y.
Similarly for other Agents, such as PRI EMS GatewayAgent , V5 EMS Gateway Agent and
SG EMS Gateway Agent, whichever is applicable, y should be entered to installed otherwise,
only Enter should be pressed to skip a particular gateway agent installation.
36) Finally when the installation is complete on the NGTJ card the NGTJ card must be given a
command to reboot:
NGTJ Card needs to go for a reboot now ...

Do you want to reboot NGTJ card now? (y/Y) or Enter to skip
y
reboot_ngtj.sh
100% 43 0.0KB/s 00:00
NGTJ card going for a Reboot now ...
37) Once the installation is completed on the NGTJ card , the script returns to the main menu as the
follows and the installation for EBM card should be selected after this

Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
3
38) Finally when all the installation is completed on the CACU cards and the option to exit the script
is selected, the output is shown as
Select Card Type:
[1] For SLM
[2] For NGTJ
[3] For EBM
[0] To Exit
Enter Your Option
0
OPERATION COMPLETED.
39) The estimated installation time for the cards is as follows:
a. SLM cards: 5 – 8 minutes

b. NGTJ cards: 8 – 15 minutes
c. EBM cards: 3 – 5 minutes
The above timing varies upon the space available and performance of the thin-client/PC being
used for installation, and the connection speed between the CACU cards and the thin-
client/PC.

Appendix-H
(Automated Installations for LAGU Application Release/Patch)
PREREQUISITES:
a) Ensure that the IP addresses are available with the user as described in Appendix –A.
b) The thin-client has been prepared/configured according to the Appendix-I.
c) For complete release and patches installations, MXNG-LAGU1.0.zip as mentioned in
the Appendix-F is present in the thin client folder, say “/home/Ubuntu/LAGU-
SOURCE/”.
d) The NGTJ cards have to be loaded with the provided VER53 uboot and dtb files.
Refer the Appendix-E.
Steps of LAGU Applications release and patch installations:

1) Connect the LAGU chassis with the power supply and turn on the power.
2) Connect the minicom cable to the RS-232 port of one of the NGTJ cards of the LAGU
chassis and log-in using the username “root” and password “root”.
3) Before proceeding for LAGU installations, do the following steps to shutdown the
LAG applications :
# /cdot/bin/mount_mmc_ext3
# chroot /mmc /etc/lag_shutdown.sh 2
4) Connect the LAGU with the CACU for uplink either using the Ethernet ports to the
CACU MLS card or via the E1/PCM links on the LAGU to the EBM cards of the
CACU.
It should be noted that both the Ethernet and E1 links for a same LAGU should not be
used, otherwise it may cause network looping.
5) Configure the site IP for the LAGU NGTJ cards through the minicom terminal using
the following four (4) commands to be typed on the terminal window of the NGTJ
card in the sequence given(replace values inside angular brackets < >) :
# /sbin/ifconfig eth0 down
# /sbin/ifconfig eth1 down
# /sbin/ifconfig eth0 <IP-Address-of-1st-LAGU-NGTJ-card> netmask

<Netmask-address-of-the-NGTJ-card> broadcast <broadcast-IP-address-
of-the-NGTJ-card> up
# /sbin/ip route flush 0/0
# /sbin/route add default gw <IP address of MLS-1>

6) For complete release and patches installations, ensure that MXNG-LAGU1.0.zip as
mentioned in the Appendix-F is present in the thin client folder, say
“/home/Ubuntu/LAGU-SOURCE/”.
7) Unzip the zip file MXNG-LAGU1.0.zip using following command.
# unzip –o MXNG-LAGU1.0.zip
8) Go to the directory MXNG-LAGU1.0 using following command.
# cd MXNG-LAGU1.0
9) Invoke the run_lagu_install.sh script as follows :
# ./run_install_lagu.sh
10) Following options are provided to user for installations:

Available options are:
[1] Installation of LAG Application Software Release on LAGU
[2] Installation of LAG Patch Release (including Backends) on
LAGU
[3] Installation of LAG Application Software Release and Patch
Release (including Backends) both
[0] Exit
Select your option
11) Currently for field migrations, option [2] will be invoked in case the base release
CLAGL2_4_1.2_1 is already installed over the LAGU cards and only the patches
need to be loaded.
12) The option [3] is executed in case the base release CLAGL2_4_1.2_1 and the latest
patches need to be installed over the LAGU cards.
13) Backend Release as well as patches will be installed as well, when the user will select
either option [2] or option [3].
14) In case we select the option [3], then following output/prompt is given to user:
Option selected for both Application Software Release and

Patch Release installation on LAGU NGTJ Cards
Checking for Release Tar files ...
Release files are present for LAGU NGTJ
15) The user is asked for an option to perform an installation on a simplex or duplex
LAGU system
Enter 2 for Duplex Installation and 1 for simplex installation
16) For a simplex installation, the user is shown the following output:
Option of Simplex Installation selected
Enter the COPY-ID(0/1) of LAGU's NGTJ Card
17) If the user selects the option for a duplex installation, the output shown is as:
Enter IP Address of the LAGU's 1st NGTJ Card(Copy-0)
Upon entering the IP address of the first NGTJ card, the user is prompted for the IP address of
the second NGTJ card:
Enter IP Address of the LAGU's 2nd NGTJ Card(copy-1)
The user is not prompted for a copy id in case the duplex option is selected.
18) The user is then asked whether a backup of existing configuration files on the LAGU
cards has to be taken or not, the output shown is:
Do you want to take backup of configuration files before

installation? (Warning: Existing files on the card may be
incorrect)
It is recommended that for the first time field migration installation, this option
must not be done. Output shown is:
Not taking backup due to user action ...

Enter new configuration value
For subsequent installation on the site, it may be input as Y.
19) After the above entries are taken, the following configuration values will be asked
from the user:
Is DNS Based routing to be done? Enter your choice [yes/no]

<yes or no entered>
It has to be entered as a YES if the DNS server is known

20) If the DNS based is selected as yes, the user is asked for the following entries:
(Note: The following values of the IP addresses, domain name, port, etc are just
indicative examples and must be something else at the site.)

yes
Enter the search domain
maxng.bsnl.in
Enter the IP address of primary DNS server
10.187.0.12
Enter the IP address of secondry DNS server
10.187.0.10

Enter the DNS Name for Softswitch
nzggnsbc.maxng.bsnl.in
Enter NTP Server IP
10.187.0.13
Enter the IP address for Feature Server
10.187.0.15
Enter the IP address for EMS Server
10.187.0.21
Enter the Port for EMS Server
8003
Is PR/DR EMS servers / Multiple EMS servers configured? Enter
your choice [yes/no]
yes
Enter the IP address for Secondary EMS Server
10.187.0.19
8003
Enter the IP address of the machine which is to be mounted on
LAG
192.168.200.20
Enter the Region Code for NGEMS
Example Region code is North_KT_12_254
NORTH_HA_126_276
21) If a no is input by the user for DNS based routing, the user prompts for input would be as
the followings:
(Note: These values are just examples, and must be replaced with actual values
at the site.)

no
Enter the IP address for Softswitch
192.168.200.73
Enter NTP Server IP
192.168.200.73
Enter the IP address for Feature Server
192.168.200.74
Enter the IP address for EMS Server
192.168.200.87
8003
Is PR/DR EMS servers / Multiple EMS servers configured? Enter
your choice [yes/no]
yes
Enter the IP address for Secondary EMS Server
192.168.200.100
8003
Enter the IP address of the machine which is to be mounted on
LAG e.g. IP of ThinClient
192.168.200.20
Enter the Region Code for NGEMS

Example Region code is North_KT_12_254
NORTH_HA_126_276
22) After these entries have been done, the user is then displayed the inputs received so
far and an option to change them.
The user may change any entry corresponding to its number if needed., eg, to change
the value of NTP Server IP Address, 6 should be entered.
The output is similar to:
The inputs received so far are:

[ 1 ] DNS Based Routing = yes
[ 2 ] Search Domain =
maxng.bsnl.in
[ 3 ] Primary DNS Entry = 10.187.0.12
[ 4 ] Secondary DNS Entry = 10.187.0.10
[ 5 ] Softswitch Name/IP Address =
nzggnsbc.maxng.bsnl.in
[ 6 ] NTP Server IP Address = 10.187.0.13
[ 7 ] Feature Server IP Address = 10.187.0.15
[ 8 ] EMS 1 Server IP Address = 10.187.0.21
[ 9 ] EMS 1 Port = 8003
[ 10] EMS 2 Server IP Address = 10.187.0.19
[ 11] EMS 2 Port = 8003
[ 12] IP of the machine to be mounted on LAG = 10.187.1.20
[ 13] Path of the machine to be mounted on LAG =
/home/Ubuntu/LAG
[ 14 ] Region code of LAGU for NGEMS = NORTH_HA_126_276
[ 0 ] To Proceed
Do you want to change any value? [yes/no]
no
User selected to proceed with the given configuration
23) In the next prompt, the script creates an ssh/scp connection between the PC/Thin-
client and the NGTJ cards. The user is asked to ensure the authenticity of the ssh host
(NGTJ cards) followed by the password of the NGTJ card, which should be entered as
root. The following output should be displayed:

established.
RSA key fingerprint is
c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e.
Are you sure you want to continue connecting (yes/no)?
Here, type yes and press Enter.
In the above example, 10.187.1.5 is the IP address of the NGTJ card on which
installation is being done and c9:66:1f:4e:6e:b9:c9:c3:cc:46:4c:44:1b:56:ad:1e is the
ssh RSA key for that particular NGTJ card. These two values will be different

depending upon the site.
24) After this step, the password for the root user of the NGTJ card is asked, with an
output similar to:
known hosts.
root@10.187.1.5's password:
Here, enter the password of the root user. The password as you type will not be
visible.
Note that the Warning shown here is not any error or warning, so should be
ignored.
25) Now, the installation proceeds and takes around half an hour for each NGTJ card, thus
around an hour for each LAGU. There would be continuous prints on the screen while
the installation progresses.
26) First the release is installed and the prints are shown as follows:
NGTJ release on simplex NGTJ 10.187.1.5 is 1.52 and Control

FPGA version is 23 on (NGTJ)
jjfs2 is already mounted on NGTJ1 @ 10.187.1.5, will initiate
mmc is mounted on NGTJ @ 10.187.1.5, will initiate
installation
Shutting down the LAG process before installation
Installing files on NGTJ - 10.187.1.5
lagconf_1.2.tar
100% 8290KB 2.0MB/s 00:04
lagrel_1.2.tar
100% 44MB 1.1MB/s 00:41
Untarring lagconf*.tar file...
Untarring lagrel*.tar file...
Executing conf_install.sh...
/etc/lag Exist
hosts.tmp arleady exists
Executing install.script...
CHECKING FOR LP ...
YES IT IS LP .... CONTINUE INSTALLATION
INTALLATION OF LAG IN PROGRESS
Creating Directories ....

Directories Created
Installing & Verifying FT module .. . . . . . . 100%
Installing & Verifying DB module . . 100%

Installing & Verifying Initialisation module . . 100%
Installing & Verifying Communication module . . . 100%
Installing & Verifying Libraries . . . . . . 100%
Installing & Verifying PSG Binaries . .. . . . 100%
Installing & Verifying CTSB Modules . . . . 100%
Installing & Verifying Utilities Modules . . . . . . 100%
Installing & Verifying Configuration Files . . . . . 100%
Installing & Verifying Call Processing PACKAGE ..........100%
MAKING DELIVERABLE LIST ....
Installing lag_pre_reboot & lag_ems_reboot.sh in /jffs2/conf
INSTALLATION OF LAG COMPLETED SUCCESSFULLY
PLEASE DO LAG EMS AGENT SOFTWARE INSTALLATION ....

clagl2_4_1.2_1-lagagent.tar
100% 10MB 436.1KB/s 00:23
Untarring clag*-lagagent.tar file...
clagl2_4_1.2_1-linuxagent.tar
100% 3450KB 1.7MB/s 00:02
Untarring clag*-linuxagent.tar file...
Editing install_run_lag.sh on 10.187.1.5
Editing install_run_lin.sh on 10.187.1.5
Executing install_run_lag.sh...
Enter the option : 1 Installation on HOST
2 Installation on PIC
3 Installation on SGTK
4 Installation on NGTJ
RELEASE IS INSTALLED SUCCESSFULLY ON PATH
/usr/local/bin/lag/AGENT
with directory name ^[[1m lagagent ^[[0m
....
....
....
....
PLEASE CREATE BASE REFERENCE FILE FOR AUDIT USING
/usr/local/bin/lag/AUDIT/auditBaseFileCreation.sh ...
Executing install_run_lin.sh...

with directory name ^[[1m linuxagent ^[[0m
....
....
....
....
Modifying /jffs2/conf/net file ...
Modifying the net file...
Modifying /mmc/etc/lag_sys.conf file ...
SELFIP0=10.187.1.5 MATEIP0=10.187.1.7 FLOATIP=10.187.1.9
ACTDSPIP=10.187.1.10 SBYDSPIP=10.187.1.11
SELFIP1=10.187.1.6 MATEIP1=10.187.1.8
The gateway 1 is 10.187.10.2
Please wait while we retrive the value of DSP MAC Address ....
DSP Booting...compiled on Aug 24 2016 11:51:53
RESETING TI Dsp through GPIO
TI DSP is OUT_OF_RESET and ready for HPI boot
Loading Core0
Loading Core1
Loading Core2
Loading Core3
Loading Core4
Loading Core5
Writing DEV_COMPLETE_STAT to bring all TI DSP cores out of
reset and start booting
DEV_COMPLETE_STAT = 3f
DSP Code version 2_1_5
32.195.143.7.141.120
NETMSK=255.255.255.0 BRDCST=10.187.1.255 GWAY=10.187.1.2
MACADDHEX=20:c3:8f:07:8d:78 DSPMACDECDOT=32.195.143.7.141.120
lag_sys.conf file updated on NGTJ card 10.187.1.5
LAGSystemInfo.txt
100% 108 0.1KB/s 00:00
lag_resolv.conf
100% 99 0.1KB/s 00:00
lag_resolv.conf
100% 99 0.1KB/s 00:00
27) After this, the backend for remote software installation and backup and restoration
modules are installed with LAGU and LAGAGENT patches when the option to install
patch installation was also selected in point 9. There is no need to manually install
them. The prints are shown as follows:
PATCH16-Over-CLAGL2_4_1.2_1-lagagent-KillingOnCliDataUpdation.tar
100% 10MB 2.5MB/s 00:04
Untarring PATCH16-Over-CLAGL2_4_1.2_1-lagagent-
KillingOnCliDataUpdation file...
Editing install_run_lag.sh on 10.187.1.5
Executing install_run_lag.sh...

with directory name ^[[1m lagagent ^[[0m
....
....
....
....
PLEASE CREATE BASE REFERENCE FILE FOR AUDIT USING
/usr/local/bin/lag/AUDIT/auditBaseFileCreation.sh ...
The patch PATCH16-Over-CLAGL2_4_1.2_1-lagagent-
KillingOnCliDataUpdation has been installed successfully...
PATCH5-Over-SWINSTL1_1_2.16_1-SCHDBACKUP_RESTORE.tar
100% 10KB 10.0KB/s 00:00
bkrs_lagbackend.tar
100% 210KB 210.0KB/s 00:00
Creating backend_install.sh file...
backend_install.sh
100% 43 0.0KB/s 00:00
Shutting down the lag_backup.exe process...
This script should be run from RAMDISK

This script is to STOP LAG backup and restoration process
Killed: lag_backup.exe
in RAMDISK Verify by command: ps | grep lag_backup.exe
mkdir: cannot create directory '/mmc/BKRS_RELEASE': File exists
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
BACKUP & RESTORATION INSTALLATION FOR LAG STARTED
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Installing backup.conf in /etc

Installing lag_backup.exe in /usr/bin
Installing lag_backupschd.exe in /usr/bin
Installing lagbkrs_start in /usr/bin
Installing lagbkrs_stop in /usr/bin
Installing CDS_FTP.sh in /usr/bin
================================================================
Installation of BACKUP-RESTORATION completed ...
Now configure /etc/backup.conf file with the required information
To start backup process usage : /usr/bin/lagbkrs_start
To stop the backup process usage : /usr/bin/lagbkrs_stop
================================================================
Creating config_install.sh file...

config_install.sh
100% 162 0.2KB/s 00:00
Restarting the lag_backup.exe process...

This script should be run from RAMDISK
This script is to START LAG backup and restoration process
mkdir: cannot create directory 'bkrs': File exists

!!!! lag_backup.exe found!!!!
lag_backup.exe: no process killed
Verify by command: ps -ef | grep lag_backup.exe
See log at : tail -f /tmp/bkrs.log
The release SWINSTL1_1_2.16_1-BKRSLAGBE and the patch PATCH5-Over-
SWINSTL1_1_2.16_1-SCHDBACKUP_RESTORE have been installed
successfully...
Shutting down the swbe_lag.exe process...

PATCH13-Over-SWINSTL1_1_2.16_1-SWBELAG-COMB.tar
100% 270KB 270.0KB/s 00:00
Creating Directory Structure for S/W Installation BE Software
Installing swbe_lag.exe ...
Installing CRS_FTP.sh ...
Installing CRS_FTP_root.sh ...
Installing INST.sh ...
Installing INST_root.sh ...
Installing conf_mod.sh ...
Installing conf_mod_root.sh ...
Installing ftpstatus.sh ...
Installing ftpstatus_root.sh ...
Installing patch_move.sh ...
Installing swbe_comn.conf ...
Installation over
Restarting the swbe_lag.exe process...
The patch PATCH13-Over-SWINSTL1_1_2.16_1-SWBELAG-COMB has been
installed successfully...
28) During the installation of PATCH17, script will ask for IP address/Domain name of
Rater Server. Enter the IP address/Domain name accordingly.
PATCH17-Over-CLAGL2_4_1.2_1-DTMF_CDR_DSP_LAGU.tar
100% 7100KB 2.0MB/s 00:03
Enter the IP adddress/Domain Name of Rater
192.168.103.108
Do You Want to Configure IP adddress/Domain Name of Rater
Enter [y/n]
n
NOTE:- Enter ‘n’ only. ‘y’ should not be entered.
Wait for the cron utility to start
The patch PATCH17-Over-CLAGL2_4_1.2_1-DTMF_CDR_DSP_LAGU has been
installed successfully...
Since backup was not taken, it is not to be restored

Release and Patch installation both done, will now go for a
Reboot/Process restart...
Installation on NGTJ card 101.101.101.30 of LAGU completed

Do you want to reboot the NGTJ Card 10.187.1.5 (Enter y for Yes, n
for No)?
n
Restart the process on the NGTJ card 10.187.1.5 using the command
lag_restart.sh

Appendix-I
(PREPARATION OF THE THIN CLIENT MACHINE)
Following are the steps for preparation of the Thin-client machine for usage in CACU
and LAGU cards access and software loading and configurations:
1) Connect the Thin-Client machine/box with the keyboard, monitor and mouse, power
source, and boot the thin client.
2) Log-in to the thin-client with the default user named Ubuntu (in case not directly
logged in).
3) Open the terminal window.
4) Set the password for the ‘root’ user at the thin client machine as mentioned in
procedure below:
a. In the terminal window opened in step 3, type the command:
sudo passwd root
b. This command firstly asks the operator to enter the password of the ubuntu user,
which is cdot123.
c. After this enter the password for the root user, as root123. The password will be
once input and then confirmed. Thus the password has to be entered twice. This
will update the password for the root user.
5) Now, connect the thin client with the CACU MLS-1 card at any free FE port (RJ-45)
with an Ethernet cable.
6) Connect the USB interface of the minicom device with any free USB port of the thin-
client. After this, configure the minicom settings using the following steps:
a. su – root
b. #ls -lrt /dev/*tty*
Note the last entry, it should be similar to something such as:
crw-rw---- 1 root dialout <some no.>, 0 <date> <time> /dev/ttyUSB0
c. Note the last entry that may be /dev/ttyUSB0 or /dev/ttyUSB1 etc. depending
upon the USB port used.
d. #minicom - s
e. It will ask Change Which Setting and present a menu list.
f. Go to the option ‘Serial Port Setup’ and press Enter.
g. In the input menu, press ‘A’ to edit the Serial Device to a value noted in the point
b/c above and press Enter to save it.
h. Set the option E, Bps/Par/Bits to 115200 8N1 if not set already.
i. Set option F, Hardware Flow Control to No.
j. Set the option G, Software Flow Control to No.
k. Press Enter to go back to the previous menu.
l. In this menu, go to the option Save Setup as dfl and press Enter. This will save
the settings made in the steps g through j. A message Configuration Saved will
be displayed.
m. Go to the Second Last option, Exit and press Enter. This exits from the Menu and
launches the minicom.
n. Note: In case the USB port is changed for the minicom, steps b to g must be
repeated.
o. root user should be exited if not using minicom.

7) Now connect the other end of the minicom cable to the MLS-1 card of CACU and
assign it VLAN-1 IP address according to the Appendix–B(Step C)
8) Ensure that the MLS cards have been configured for the Native VLAN IPs, gateways
and the WAN IPs/routes configurations have been completed for uplink as detailed in
Appendix–D.
9) Configure the thin client machine IP address settings as per the IP address available
in the IP ADDRESS DETAILS mentioned as “Terminal (Thin Client) IP” (in
Appendix – A) either using the script “thinclient_ipconf_gw.sh” provided for thin-
client mentioned below in part-a) OR the manual procedure mentioned in part-b) :
a) Using script “thinclient_ipconf_gw.sh” (Preferable)

 Copy the script thinclient_ipconf.sh to the any directory(e.g. /home/ubuntu) in
the thin-client
 Go to that Directory, where the script is copied on the thin-client.
 Execute the script “thinclient_ipconf_gw.sh” after giving executable
permission.
chmod +x thinclient_ipconf_gw.sh
./thinclient_ipconf_gw.sh
 The script will ask for following entries one by one:-
o IP address for the thin-client
o NetMask for Thin Client
o Network IP for Thin-Client
o Broadcast IP for thin-Client
o Gateway IP Addresses for thin-Client
o SBC IP Addresses for the network
 Enter the above mentioned IPs correctly
 Example Output (Must be different in the field) of this script will be as
follows:
*************************************************
ubuntu@CPRS:/tmp$ ./thinclient_ipconf_gw.sh
This is the Thin-Client IP address configuration utility
You may be asked the password of the user
Enter the IP address for Thin Client
101.101.101.160
Enter NetMask for Thin Client
255.255.255.0
Enter Network IP For Thin Client
101.101.101.1
Enter BroadCast IP For Thin Client
101.101.101.255
Enter Gateway IP For Thin Client
(This IP should be the management IP of the MLS-1 card)
101.101.101.4
Enter second Gateway IP For Thin Client
(This IP should be the management IP of the MLS-2 card)
101.101.101.7
Enter Primray SBC IP (P.R.)
192.168.103.75
Enter secondary SBC IP (G.R.)
10.187.1.69

* Reconfiguring network interfaces...
SIOCDELRT: No such process
ssh stop/waiting
ssh start/running, process 20077 [ OK ]
Creating thinclient_gw.sh script and sbcip.conf
Please wait while the configuration is being done ...
 After that, confirm the IP set above using the command ‘/sbin/ifconfig’ on the
terminal window.
b) Alternate Manual procedure for thin client IP configuration without script

 su - root
 #vi /etc/network/interfaces
 Type 100dd
 Press ‘i’ to enter into the insert mode in the editor and type the following (while
replacing the fields inside < > with the actual values):
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address <IP address of the thin client>
netmask <Netmask of the thin client>
network <Network address of the thin client>
broadcast <Broadcast IP address for the thin client>
gateway <Management IP Address of the MLS-1 card>
 Press the ‘Esc’ key to exit out of the insert mode of the editor and type ‘:wq’. After
this, press the Enter key.
 Now bring the network interface up using the command:
#ifconfig eth0 up
 Confirm the settings done above using the command ‘/sbin/ifconfig’ on the terminal
window and after that, ping the gateway IP address, that is the IP address of the MLS
card-0, using the command ‘ping <IP address of the MLS-1 card>’ in the terminal
window.
10) Now test the core nodes reachability as mentioned in the steps below:
a. Ping the Core Server using its domain name. The command to be used is:
#ping <Domain Name of the Core server>
In case the pinging results in a packet loss, ensure the IP connectivity is made.
b. If ping is known to be disabled, use the following command to check the IP

connectivity:
#nc –w 1 <Domain name of the Core Server> 22
This command should output something similar to
SSH-2.0-OpenSSH_5.3
This means that the IP connectivity is fine.
If the nc command does not output anything after some time, this means that there
is some issue in the reachability till the core. Ensure the IP Connectivity first.
c. Following steps need to be followed for installation of the tftp server over thin
client and copy the relevant drivers at the /var/lib/tftpboot/ path:

(Please enter the Ubuntu user password when prompted)
 cd <path-where-UBOOT_DTB-V53.tar is present>
 tar –xvf UBOOT-DTB-V53.tar
 sudo dpkg -i MXNG-1.0-tftpd-THIN-CLIENT.deb
 sudo cp tftp /etc/xinetd.d/
NOTE: Verify whether tftp is successfully installed or not, check the presence
of the directory /var/lib/tftpboot/ by using following command.
# ls –lrt /var/lib/tftpboot
Output of this command should NOT show that “No such file or directory”
d. Now, copy the UBOOT-V53, DTB-V53 and other script files to /var/lib/tftpboot
 sudo cp NGTJ.u-boot.bin.VER53 /var/lib/tftpboot/

 sudo cp NGTJ.dtb.VER53 /var/lib/tftpboot/
 sudo cp uboot53.scr /var/lib/tftpboot/
 sudo cp dtb53.scr /var/lib/tftpboot/
e. Following steps need to be followed for quicker response of EMS GUI in Thin
Client.
 Go to ejre1.6.0_25 path on the client machine

# cd /usr/lib/ejre1.6.0_25/bin/
 Invoke ControlPanel
# ./ControlPanel
 Click on Java tab in the Java Control Panel GUI
 In the Java Runtime Environment Settings GUI, enter in the Runtime
Parameters
-Xms128m –Xms1024m
 Click OK, Apply.
f. Copy the java.policy file at the path : /usr/lib/ejre1.6.0_25/lib/security/

(Present in the MISC folder in deliverables package)
g. Following steps need to be followed for installation of the NFS server over thin
client:
 Copy following deliverables to any directory on the thin-client
i. thin_client_nfs_installer.sh
ii. MXNG-1.0-NFS-SRVR-FOR-THIN-CLIENT.tar
 Go to the directory, where the above mentioned tarball and script are
copied
# cd <path-where-NFS-tarball-and-script-are-present>
 Execute the script named thin_client_nfs_installer.sh

# ./thin_client_nfs_installer.sh

NOTE:- Please enter the ubuntu user password when prompted
 Script will ask for reboot. Then, Enter “Y” or “y”

NOTE:- After that, thin-client will reboot. In case, thin-client hangs, kindly
turn OFF the Power-switch on the back of the thin-client and then turn it ON
again
 Execute the Script thin_client_nfs_installer.sh again, once the thin-client comes

up after reboot.
# ./thin_client_nfs_installer.sh
NOTE: Verify whether NFS is successfully installed/running or not, check the

output of the following command
# ps –ef|grep nfs
Output of this command should be similar to :

ubuntu@CPRS:~$ ps -ef|grep nfs
root 23 2 0 13:49 ? 00:00:00 [nfsiod]
root 651 2 0 13:49 ? 00:00:00 [nfsd]
root 652 2 0 13:49 ? 00:00:00 [nfsd]
root 653 2 0 13:49 ? 00:00:00 [nfsd]
root 654 2 0 13:49 ? 00:00:00 [nfsd]
root 655 2 0 13:49 ? 00:00:00 [nfsd]
root 656 2 0 13:49 ? 00:00:00 [nfsd]
root 657 2 0 13:49 ? 00:00:00 [nfsd]
root 658 2 0 13:49 ? 00:00:00 [nfsd]
ubuntu 1043 1025 0 13:50 pts/0 00:00:00 grep --color=auto nfs
NOTE: In case of a storage space issue over the Thin Client machine; check with the
following command for presence of large size files (say more than 100 MB)
# find / -size +100M
And then remove the unwanted files to create space.
NOTE: Once the installation and configuration of the thin-client and the
CACU cards is over, connect the Ethernet cable from the thin-client to the
port 5B_01 or 5B_02 or 6B_01 or 6B_02 on the CACU backplane. It must
be connected to a port in which a card is jacked in.

Appendix-J
(CACU LINK REDUNDANCY)
CONFIGURATION FOR CACU LINK REDUNDANCY (LR):
A. Following configurations are required at BSNL MPLS Router:
1) Both UP links of CACU should be Physical up and configured.
2) BFD ECO should be configured with following parameter.

bfd min-transmit-interval 200
bfd min-receive-interval 200
bfd min-echo-receive-interval 200
bfd detect-multiplier 3
3) Static Routing with BFD configuration for all VPN interface.
B. Following configurations are required at CACU and LAGU
1. Latest patches are required in both CACU and LAGU (already taken care of in the
appendices ‘G’ and ‘H’)
2. Static Routing at both MLS cards.
3. RSTP should be configure at Both MLS with following parameters.
Hello Time 1
Forward Delay 4
Max Age 6
Maximum Hop Count 6
Transmit Hold Count 2
 For Additional setting required for NTP, Trap and MLS Link Alarm configurations,
do the configurations as mentioned in detail in a separate document for MLS card
Configuration. Broad steps for these points are as follows:-
o For NTP related configurations , Go to Configuration -> System -> NTP
Mode should be Enabled and enter SBC FVIP of PR Site in Server 1 option
and in Server 2 option, enter SBC FVIP (GR Site) IP address.
o For trap configuration settings, go to Configuration -> System -> Security ->
SNMP -> Trap. Mode should be Enabled. Add three Entries of PR NGEMS
Server and one entry of GR NGEMS Server.
o For MLS Link removal Alarm related configurations, create static routing for
NGEMS server IP addresses in MLS-1 as well as MLS-2. MLS-1 should have
MLS-2 IP address as its gateway for uplink alarm purposes and vice versa.

Appendix-K
Guidelines regarding the PCM cable (E1) connectivity between the
RSU-LAGU and the CACU-EBM
1) The cable should be of 4 pair/8pair 120 ohm digital trunk (E1) cables. Subscriber cable should
NOT be used, which comes in 10+1 pair without individual pair shielding.
2) At RSU (LAGU) end, existing cable can be used.
3) For termination at CACU EBM, existing CM end connections CANNOT be used. The existing
MAX CM E1-cable connector should be removed & its wiring should be connected at the DDF
provided in CACU (to which the supplied 16/32 E1 cable extended from EBM is terminated on
the other side).
4) We can connect four nos. of E1 (two nos. per NGTJ copy) from the RSU LAGU. The 1st pair of
E1 connected between one copy of LAGU-NGTJ card to 1st EBM of exchange CACU and the
2nd pair of E1 is connected between other NGTJ card copy to 2nd EBM of exchange CACU.
Only one pair of E1 (i.e. 2 E1s) is enabled at a time from one NGTJ card copy of the RSU LAGU
system; the other pair remains in disabled state. The disabled E1 pair is enabled only in case the
Active E1 pair goes down/ jacked out or the NGTJ card with current active E1 pair is removed.
Thus, we will have one pair of E1 (2 E1s) enabled at a time to carry the RSU calls traffic.
5) If multiple RSU LAGUs are connected over E1 to the CACU EBM cards, then from each NGTJ
card one E1 pair should terminate over EBM E1 pair of (1,2) or (3,4) or (5,6) .. (31,32) etc. And
Not like (2,3) or (4,5) etc.

Appendix-L
MMC Partition formatting and mmc RFS loading procedure on the NGTJ cards
The corruption of the /mmc partition can be checked using any of the following cases:
1. Inability of performing the command chroot /mmc OR

2. Inability to create a file on the /mmc OR
3. Inability to read or write on /mmc
In case the /mmc partition of the NGTJ of becomes corrupt or it is for the first time that the mmc
partition is being created, the following steps are to be followed:
1. Try to go to the /mmc directory and transfer the database files to the thin-client or some PC if
possible. In case of extreme corruption cases, it would not be possible to read from the /mmc.
The files to be copied in case of a LAGU NGTJ card are:
1) /mmc/etc/ CdotLagDbConf.bin OR
/mmc/etc/ CdotLagDbConf.bak1 OR
/mmc/etc/ CdotLagDbConf.bak2
The files to be copied in case of a CACU NGTJ are:
1) /mmc/NGTJ*
2) /mmc/ngtj/run.sh
3) /mmc/sgstk/cdot_sgl2.conf
4) /mmc/etc/resolv.conf
5) /mmc/ag/CdotAgwDb.bin*
6) /mmc/etc/v5ag/extensions.conf
7) /mmc/etc/v5ag/v5ag.conf
8) /mmc/etc/priag/priag.conf
9) /mmc/etc/priag/extensions.conf
10) /mmc/opt/tmg/etc/cdot_tmg.cfg*
11) /mmc/AGENT/snmp/cardagent/snmpd.conf
12) /mmc/AGENT/snmp/cardagent/gatewayagentdev.conf
13) /mmc/AGENT/PRIAG/cagent/conf/agent.conf
14) /mmc/AGENT/PRIAG/cagent/conf/device.conf
15) /mmc/AGENT/PRIAG/cagent/conf/service.conf
16) /mmc/AGENT/PRIAG/cagent/conf/dev-conf-agent.conf
17) /mmc/AGENT/PRIAG/cagent/conf/ems-agent.conf
18) /mmc/AGENT/TMG/cagent/conf/agent.conf
19) /mmc/AGENT/TMG/cagent/conf/device.conf
20) /mmc/AGENT/TMG/cagent/conf/service.conf
21) /mmc/AGENT/TMG/cagent/conf/dev-conf-agent.conf
22) /mmc/AGENT/TMG/cagent/conf/ems-agent.conf
23) /mmc/AGENT/V5AG/cagent/conf/agent.conf
24) /mmc/AGENT/V5AG/cagent/conf/device.conf
25) /mmc/AGENT/V5AG/cagent/conf/service.conf
26) /mmc/AGENT/V5AG/cagent/conf/dev-conf-agent.conf
27) /mmc/AGENT/V5AG/cagent/conf/ems-agent.conf
2. Unmount the partition /mmc on the NGTJ card using the commands:
#cd /
#umount –l /mmc
Now execute following command to format the /mmc partition on the respective NGTJ cards:
For LAGU NGTJ card:
# /sbin/mkfs.ext3 /dev/mmcblk0
For CACU NGTJ card:

#format_nand_ext3 /dev/mtdblock3
3. Mount the /mmc partition on the NGTJ cards using following command
For LAGU NGTJ card:
# mount -t ext3 -o noatime,data=writeback, commit=200
/dev/mmcblk0 /mmc
For CACU NGTJ card:

#mount_nand_ext3
4. Transfer the MMC-RFS(MXNG-NGTJ-LTIB-V05.tar) to the NGTJ card from the thin-client

/PC using following command:
# scp MXNG-NGTJ-LTIB-V05.tar root@<NGTJ-IP>:/mmc
NOTE:- The above mentioned command is to be executed from thin-client/PC, where MXNG-
NGTJ-LTIB-V05.tar is present.
5. On the NGTJ card, execute the following commands to untar MXNG-NGTJ-LTIB-V05.tar:
# cd /mmc
# tar -xvf MXNG-NGTJ-LTIB-V05.tar
Untarring of RFS tarball will take around 15-20 minutes on LAGU NGTJ card and 5-10
minutes on the CACU NGTJ card.
6. After that, execute following command to check if RFS is installed properly:
# chroot /mmc
7. Now perform the installation of release and patch on the NGTJ cards as mentioned in the
above Appendices.
8. Restore the database/configuration files if backup was taken.

Appendix M
(REFERENCES)
Serial Document Name Purpose
No.
1 MAX-NG ACCESS For the overview of NGN CORE and ACCESS
MIGRATION DOC Network.
Steps mentioned in detail for Migration related
activities.
2 MAX-NG CACU Provides the information about connecting multiple
Aggregation Proposal exchange wise CACUs to an Aggregator CACU, in
case there is a requirement.
3 MLS CONFIGURATION All the information regarding configurations needed
MANUAL to be done on MLS card of CACU and PE Router
for dual uplink connectivity.
4 PSG_LOADING_MANUAL Information regarding loading of PSG Firmware
(rfs/uboot/uImage/dtb) and FPGA on SLM, EBM
and NGTJ Cards
5 Retrofit Procedure LAGU Steps to be followed for data retrofit on each LAGU
ANRAX and AN-RAX (V5AG)
6 V5AG-GUI For modifying ANRAX/V5 subscriber data later on
using the GUI (after the initial installation).
7 V5-PRI-HANDBOOK For the steps to be followed to migrate PRI and V5
(ANRAX) subscribers using the CLI interface. This
manual is to be used initially.
8 Data_Template_filled This template is an already filled template. One can
refer to this for the knowledge of filling a data
template
9 Data Template description Details related to the subscriber data template and
document the steps to be followed to fill the subscriber data
template.
10 LAG configuration and The details of LAG configuration for
discovery on IEMS/NGEMS IEMS/NGEMS discovery.
11 MAX-NG-LAGU-DATA- The details of LAGU bulk Data creation with .LST
RETROFIT-PROCEDURE files generated based on Data template sheets filled
for the site.
12 MAX-NG-ACCESS-SW- Detailed BOM for MAX-NG Access Software
BOM (CACU and LAGU Cards) containing the details of
MXNG-CACU1.0, MXNG-LAGU1.0 and MXNG-
MISC1.0 SW Packages.
13 Data backup and restoration Details of procedure for taking backup of data on
on LAGU EMS and restoring it again on LAGU
14 DSP Utility How to use This document contains steps to be used for
debugging NGTJ card DSP in call related issues.

MXNG CACU LAGU INST CONF SITES v01 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

MXNG CACU LAGU INST CONF SITES v01 PDF

Încărcat de

Drepturi de autor:

Formate disponibile

C-DOT MAX-NG

MAX-NG ACCESS SOFTWARE

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 1

a) Please refer to the Audio/Video of CACU/LAGU installation to understand the

g) Load the revised MLS software file CEServices3_65-MLSSD1_SW002.dat over

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 2

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 3

Total CACU System (with EBM-16) 1

CACU#1 10.188.168.2 - 10.188.168.30

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 4

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 5

Total CACU System (with EBM-32) 0

LAGU#1 10.188.168.31 - 10.188.168.38

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 6

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 7

2. Login to the ICLI (login user: admin password : <enter>)

B. IP ADDRESS ALLOCATIONS IN MLS CARD:

C. LAN AND WAN IP POOL:

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 8

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 9

2) Ensure that the network configuration data is saved (MaintenanceConfiguration 

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 10

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 11

S/no Deliverable-Name Size(in bytes) Checksum

1. NGTJ.u-boot.bin.VER53 (UBOOT) 369880 4027088522

2. NGTJ.uImage.VER52 (LINUX IMAGE) 3806124 2389537443

3. NGTJ.dtb.VER53 (DTB) 10067 3601580650

4. NGTJ.rfs.s.VER52 (RAM-RFS) 19078430 933627270

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 12

VERIFY THE CURRENT FIRMWARE LOADED IN NGTJ CARD AS FOLLOWS:

# fpga command should give output as:

Control FPGA version is 23 on (NGTJ)

THE UBOOT AND DTB V53 INSTALLATION PROCEDURE FOR

Output of this command should be as follows:

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 13

[ NOTE :- The checksum displayed should match as mentioned in table above ]

9) In the uboot prompt, do the following steps (steps a to k) :

e) Now save the above entries using the command:

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 14

g) ping the IP address of the tftp server using the command:

An output as the following should come:

RUN THE COMMANDS MENTIONED BELOW TO FUSE DTB V 53 [

h) => tftp 10000 dtb53.scr

On execution following messages-extract will be printed on screen :

Using UEC0 device

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 15

On execution following messages-extract will be printed on screen :

## Executing script at 00010000

l) => run FUSE_DTB

Note: Following output must be seen on minicom

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 16

m) Reboot the card using below mentioned command

RUN THE COMMANDs TO FUSE UBOOT [Steps ‘n’ to ‘u’) ]:

o) => tftp 10000 uboot53.scr

Using UEC0 device

p) => source 10000

## Executing script at 00010000

q) => setenv ubootfile NGTJ.u-boot.bin.VER53

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 17

Note: Following output must be seen on minicom

VERY IMPORTANT NOTE:

MAX-NG Access SW Inst & Config[v01] 29.May.2018 Page 18

u) Login into the card using “user/password = root/root”.