Index
Index
Please download following documents for detailed description from cdothelpline portal
1. MLS Configuration Manual
2. MAX-NG Access Software Installation & Configuration
3. IP Entries for CACU & LAGU
4. Enable V5 and PRI logs
1
CHAPTER-1
2
Q4. How to do BFD Configuration?
Ans.
Configuration in PE Router ( in BSNL IP/MPLS/NIB Network)
BFD ECO configured should be with parameters
bfd min-transmit-interval 200
bfd min-receive-interval 200
bfd min-echo-receive-interval 200
bfd detect-multiplier 3
Static routing with track configuration for all VPN interfaces
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.
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.
For MLS Link removal Alarm related configurations, create static routing for NGEMS server IP addresses in
MLS-1 as well as MLS-2.
3
MLS-1 should have MLS-2 IP address as its gateway for uplink alarm purposes and vice versa.
# cd /jffs2_ram/SLM/bin
# ./shm_shutdown.sh
Shm.exe processes will be shut down. After this, messages in minicom terminal will be stopped.
# cd /jffs2_ram/eeb/bin
# ./eeb_stop.sh
# cd /mmc/ngtj
# ./stopall
Note: All processes will be shutdown and messages in minicom terminal stops.
Login prompt will appear. Before proceeding this, connect Thin Client PC with minicom and Ethernet cable through USB
port and Ethernet port.
4
Q6. How to install TMPCH Patch in NGTJ (CACU) card for One Way Speech & RBT issue in
AN-RAX?
Ans.
1. Download TMPCH.tar from cdot helpline portal in CACU and copy below link and paste in
Internet browser.
http://cdothelpline.cdot.in/helpline/latest_updates/MAX_NG/maxng_doc.jsp
2. Go to Access Software Package Downloads Patches CACU PATCH TAR.
3. Untar CACU PATCHES TAR Ball using below command and is follows:
5
Go to /mmc location in NGTJ card using below command
cd /mmc
Type mp TMPCH.tgz and press y and Enter key
Type bye and press Enter key.
5. Login into card using ssh and default Password root using below command.
cd /mmc
7. Untar TMPCH.tgz in the same location in NGTJ card and run Read_dsp_ch & command in same
location.
Note: If still problem persists then re-install RFS and Release in NGTJ card from scratch after
formatting mmc as per the procedure.
6
Q8. How to check if correct installation in CACU System is done or not?
Ans.
a. SLM Card
#cat /jffs2_ram/SLM/conf/slm_sys.conf
b. EBM Card
Check processes by ps –ef command in EBM card and should show eeb.exe.
c. NGTJ Card
Check processes by ps –ef command in NGTJ card and must show ag,tmg,priag processes in NGTJ card.
#ps –ef
#cd /mmc/ngtj
Please open FE
#cd /mmc/ngtj
#./service ag fe
#cd /mmc/ngtj
#./service pag fe
Rest will be checked after creation of Data in NGTJ card related to AN-RAXs, PRI and POI.
7
Q9. How to check the releases installed in NGTJ card?
cd /mmc/ngtj
./service rel
8
Q10. How to check the processes installed in NGTJ card?
cd /mmc/ngtj
ps –ef
After giving ps –ef command, then check application manager 1, tmg, v5 and pri processes.NGTJ card
will take 10 to 12 minutes for making all processes UP.
Q11. How to start /stop AG, TMG, and PRIAG process in NGTJ card?
Ans. To start /stop AG, TMG, and PRIAG process in NGTJ card,
cd /mmc/ngtj
9
Q12. If AI links not coming up, how to enable & disable logs?
Ans.
For enabling V5AG and PRIAG logs following is the below procedure:
Signaling group
:apmrelinfo: NGTJCD1_1_1.6-PATCH_12 1 47.0 Wed, 21 Mar 2018 10:59:01 +0530
press 1 to continue...default(1): 1
.
NGTJ REL:NGTJCD1_1_1.6-PATCH_12
V5AG REL:AGL1_1_3.4Patch7_1
PRIAG REL:PRIAG1_1_2.6_1
TMG REL:CDTMG-NGTJ-CACU-1_1_1.9_1
SGL2 REL:PATCH1-Over-SGL1_3_1.9_1-INIT
10
Event Configuration Menu (Enter number)
1. MAC
2. ENV
3. LAPV5-DL
4. V5L3
5. Back to main Menu
6. Quit
Enter AI Num[1-150]: 1
12
--->A Rx: fc e1 fc e1 01 03 :RR(1):PSTN sp=0 (Wed Mar 21 10:57:39 2018) p=26
((1))
<--A Tx: fc e1 fc e1 01 03 :RR(1):PSTN sp=0 (Wed Mar 21 10:57:39 2018) p=26
U ((1))
--->A Rx: fc e5 fc e5 01 03 :RR(1):BCC sp=0 (Wed Mar 21 10:57:39 2018) p=26 ((1))
<--A Tx: fc e5 fc e5 01 03 :RR(1):BCC sp=0 (Wed Mar 21 10:57:39 2018) p=26
U ((1))
--->A Rx: fc e3 fc e3 01 01 :RR(0):CONTROL sp=0 (Wed Mar 21 10:57:39 2018) p=26
((1))
<--A Tx: fc e3 fc e3 01 7d :RR(62):CONTROL sp=0 (Wed Mar 21 10:57:39 2018)
p=26 U ((1))
--->A Rx: fc e9 fc e9 01 01 :RR(0):LINK-CONTROL sp=0 (Wed Mar 21 10:57:44 2018)
p=26 ((1))
<--A Tx: fc e9 fc e9 01 01 :RR(0):LINK-CONTROL sp=0 (Wed Mar 21 10:57:44 2018)
p=26 U ((1))
--->A Rx: fc e1 fc e1 01 03 :RR(1):PSTN sp=0 (Wed Mar 21 10:57:48 2018) p=26
((1))
<--A Tx: fc e1 fc e1 01 03 :RR(1):PSTN sp=0 (Wed Mar 21 10:57:48 2018) p=26
U ((1))
--->A Rx: fc e5 fc e5 01 03 :RR(1):BCC sp=0 (Wed Mar 21 10:57:48 2018) p=26 ((1))
<--A Tx: fc e5 fc e5 01 03 :RR(1):BCC sp=0 (Wed Mar 21 10:57:48 2018) p=26
U ((1))
--->A Rx: fc e3 fc e3 01 01 :RR(0):CONTROL sp=0 (Wed Mar 21 10:57:48 2018) p=26
((1))
<--A Tx: fc e3 fc e3 01 7d :RR(62):CONTROL sp=0 (Wed Mar 21 10:57:48 2018)
p=26 U ((1))
--->A Rx: fc e9 fc e9 01 01 :RR(0):LINK-CONTROL sp=0 (Wed Mar 21 10:57:54 2018)
p=26 ((1))
Important Note: Check for Rx and TX messages messages. Both should come.
1. MAC
2. ENV
3. LAPV5-DL
4. V5L3
13
5. Back to main Menu
6. Quit
Enter AI Num[1-150]: 1
15
TST(sp:0) Rx --> (25,18), e1-PSTN, 2-SIGNAL, port(3): SN=0-->(STEADY SIGNAL:0x4-OFF
HOOK), (8176) m=16) p=26 ani=1
TST(sp:0) Rx --> (26,18), e1-PSTN, 2-SIGNAL, port(3): SN=1-->(STEADY SIGNAL:0x5-ON
HOOK), (8176) m=16) p=26 ani=1
TST(sp:0) Tx <-- (18,27), e1-PSTN,== 3-SIGNAL ACK ==, port(3) SN=2, (8176) m=13)
p=26 ani=1
TST(sp:0) Rx --> (27,19), e1-PSTN, 2-SIGNAL, port(2): SN=0-->(STEADY SIGNAL:0x5-ON
HOOK), (8176) m=16) p=26 ani=1
TST(sp:0) Tx <-- (16,16), e5-BCC, 23-DEALLOCATION, Port(2) <--> V5TsId(L=0 TS=8),
ref(11,11) LE, (8178) m=18) p=26 ani=1
TST(sp:0) Tx <-- (19,28), e1-PSTN, 8-DISCONNECT, port(2), (8176) m=10) p=26 ani=1
TST(sp:0) Tx <-- (17,16), e5-BCC, 23-DEALLOCATION, Port(3) <--> V5TsId(L=0 TS=9),
ref(12,12) LE, (8178) m=18) p=26 ani=1
TST(sp:0) Tx <-- (20,28), e1-PSTN, 8-DISCONNECT, port(3), (8176) m=10) p=26 ani=1
TST(sp:0) Rx --> (16,17), e5-BCC,== 24-DEALLOCATION-COMPLETE ==, ref(11), (8178)
m=10) p=26 ani=1
TST(sp:0) Rx --> (17,18), e5-BCC,== 24-DEALLOCATION-COMPLETE ==, ref(12), (8178)
m=10) p=26 ani=1
TST(sp:0) Rx --> (28,21), e1-PSTN,== 9-DISCONNECT COMPLETE ==, port(2), (8176) m=10)
p=26 ani=1
TST(sp:0) Rx --> (29,21), e1-PSTN,== 9-DISCONNECT COMPLETE ==, port(3), (8176) m=10)
p=26 ani=1
7. To check e1 status
Shmid 65538
DSP_status 1
DSP_eth0_status 1
DSP_eth1_status 0
EEB 0 status is 0
EEB 1 status is 0
EEB 2 status is 0
EEB 3 status is 0
Framer_status 1
17
LIU_status 1
TimeSwitch_status 1
FPGA_status 1
CPU_eth0_status 1
CPU_eth1_status 1
Selected_clock 0
HW_status_copy0 1
HW_status_copy1 0
I2C_status 1
Slot_id 2
Chasi_Id 0
E1's Master/Slave status E1 0 status 0
E1 1 status 0
E1 2 status 0
E1 3 status 0
E1 4 status 0
E1 5 status 1
E1 6 status 0
E1 7 status 0
E1 8 status 0
E1 9 status 0
E1 10 status 0
E1 11 status 1
E1 12 status 0
E1 13 status 0
E1 14 status 0
E1 15 status 0
E1 16 status 0
E1 17 status 0
E1 18 status 0
E1 19 status 0
E1 20 status 0
E1 21 status 0
E1 22 status 0
E1 23 status 0
E1 24 status 0
E1 25 status 1
E1 26 status 1
E1 27 status 0
E1 28 status 1
E1 29 status 1
E1 30 status 0
E1 31 status 0
Fpga_clockselection 0
Active_Passive_Status 1 *********CHECK*************
dsp_boot_status 1 *********CHECK*************
dsp_ip_status 1 *********CHECK*************
System_status 1 *********CHECK*************
E1 Configuration Data
E1[0] : 8,0,0.0.0.0,0
E1[1] : 1,27999,192.168.103.145,1 ******CHECK V5 IP **********
E1[2] : 0,0,0.0.0.0,0
18
E1[3] : 0,0,0.0.0.0,0
E1[4] : 0,0,0.0.0.0,0
E1[5] : 12,26000,192.168.103.143,5 ******CHECK TMG IP **********
E1[6] : 0,0,0.0.0.0,0
E1[7] : 0,0,0.0.0.0,0
E1[8] : 0,0,0.0.0.0,0
E1[9] : 0,0,0.0.0.0,0
E1[10] : 0,0,0.0.0.0,0
E1[11] : 8,0,0.0.0.0,11
E1[12] : 4,26000,192.168.103.143,12 ******CHECK TMG IP **********
E1[13] : 4,26000,192.168.103.143,13 ******CHECK TMG IP **********
E1[14] : 4,26000,192.168.103.143,14 ******CHECK TMG IP **********
E1[15] : 4,26000,192.168.103.143,15 ******CHECK TMG IP **********
E1[16] : 0,0,0.0.0.0,0
E1[17] : 0,0,0.0.0.0,0
E1[18] : 0,0,0.0.0.0,0
E1[19] : 0,0,0.0.0.0,0
E1[20] : 0,0,0.0.0.0,0
E1[21] : 0,0,0.0.0.0,0
E1[22] : 0,0,0.0.0.0,0
E1[23] : 0,0,0.0.0.0,0
E1[24] : 0,0,0.0.0.0,0
E1[25] : 0,0,0.0.0.0,25
E1[26] : 1,27999,192.168.103.145,26 ******CHECK V5AG IP **********
E1[27] : 0,0,0.0.0.0,0
E1[28] : 2,28002,192.168.103.146,28 ******CHECK PAG IP **********
E1[29] : 2,28002,192.168.103.146,29 ******CHECK TMG IP **********
E1[30] : 0,0,0.0.0.0,0
E1[31] : 0,0,0.0.0.0,0
unlocking shared memory
released shared memory lock
10.
------------------------------------------------------------------------------
/mmc/etc/v5ag
[root@NGTK v5ag]# tail -f logger.conf
; /mmc/var/log/v5ag/full :: atleast one of the following "full" should be
uncommnented
;full => notice,warning,error,debug,verbose
;full => warning,error,notice
full => error,warning,notice,debug
;full =>
;
/mmc/ag/cmlog/Tcdotagt.log
/mmc/var/log/v5ag/full
-------------------------------------------------------------------------------
------
/mmc/ag/cmlog/Tcdotagt.log
/mmc/var/log/v5ag/full
19
_
To chek the logs of PAG
****************************************************************************
****************************** LOGIN TO FE
*******************************
****************************************************************************
****************************************************************************
++++++++++++++++++++++++++++++++++++++++++++++++
+ PRI-ACCESS GATEWAY Main Menu +
++++++++++++++++++++++++++++++++++++++++++++++++
1. Create
2. Delete
3. Display
4. Misc...
5. Back to Main Menu
++++++++++++++++++++++++++++++++++++++++++++++++
+ PRI-ACCESS GATEWAY Misc commands Menu +
++++++++++++++++++++++++++++++++++++++++++++++++
-----------------------------------------------------
Edit the LOG files for PRIAG Call Controller
-------------------------------------------------------
/mmc/var/log/priag/full
to check logs
Note: Disable all types of logs for V5/PRI after taking logs otherwise it may slow down NGTJ card and also may
interrupt call handling of NGTJ card.
#cd /mmc/ngtj
#./service status all
#./service ag stop
#./service ag start
#./service status all
Run TMPCH patch
#cd /mmc/TMPCH
#./Read_dsp_ch&
Note: If problem still persists after giving ag stop start, running TMPCH patch then
please reinstall and reconfigure RFS and NGTJ card using CACU LAGU Installation &
Configuration.
Make sure Data Backup should be taken and restored backed after installation and
21
reconfiguration.
22
If again problem persists, please contact C-DOT MAX-NG Control Room.
Q14. What to do if FE of V5AG is not opening & Connecting to port 9001 error comes ?
Ans.
Check if DB is OK or not. If DB is not working then restore Backup.
Open terminal in Thin Client PC
Go to directory where Backup is saved.
#cd /home/ubuntu/Desktop/Backup/V5_Backup
#ssh root@<IP address of NGTJ card>
#cd /mmc/ngtj
#./service ag stop
Transfer saved file CdotAgwDb.bin file to /mmc/ag location from Thin Client PC to NGTJ card using
FTP.
ftp <Card IP>
Note: Default Username and Password is root and root.
Type bi and press Enter
Type ha and press Enter
Go to /mmc/ag location in NGTJ card
cd /mmc/ag
mp CdotAgwDb.bin
bye
Again login into NGTJ card,
<ssh root@<NGTJ card IP>
Default password is root
cd /mmc/ngtj
./service ag start
23
Q15. How to check PRI D channel status?
Ans.
Login into NGTJ card
#ssh root@<self NGTJ card IP> (Default Password is root)
#cd /mmc/ngtj
#./service pag fe
(Default Username is root and Password is root)
List of options will appear.
Select option 1, Go to 3 that is Display option, Display port option, then press 1 for all ports.
Q16. What to check if in V5AG Incoming calls are working but Outgoing calls are not working?
Ans. Make sure that CACU is connected to Core network. To check same, ping SBC IP of core network.
#ping <FVIP of SBC IP of respective core network>
#ping 10.187.0.12 ( For Gurugram Core Network)
#ping ggnsbc.maxng.bsnl.in (For Gurugram Core Network)
Note 1: Please check traces in Core whether call originating from NGTJ card is reaching to core
site or not.
Please check hosts file and resolv.conf which must have IPs and Domain Name of respective Core
(PR Site) only. If PR shifted to GR then IP of GR site must be present.
#cat /mmc/etc/hosts
Hosts File must contain IPs of respective core network.
#cat /mmc/etc/resolv.conf
24
Q17. How to enable logs of PRI?
Ans. To enable logs of PRI follow procedure as given below:
****************************************************************************
****************************** LOGIN TO FE
*******************************
****************************************************************************
****************************************************************************
++++++++++++++++++++++++++++++++++++++++++++++++
+ PRI-ACCESS GATEWAY Main Menu +
++++++++++++++++++++++++++++++++++++++++++++++++
1. Create
2. Delete
3. Display
4. Misc...
5. Back to Main Menu
++++++++++++++++++++++++++++++++++++++++++++++++
+ PRI-ACCESS GATEWAY Misc commands Menu +
++++++++++++++++++++++++++++++++++++++++++++++++
-----------------------------------------------------
Edit the LOG files for PRIAG Call Controller
-------------------------------------------------------
/mmc/var/log/priag/full
to check logs
26
#bi
27
#ha
#cd /mmc/ag
#get CdotAgwDb.bin
#bye
#cd ../NGTJ2
To take AI Data Backup, please follow below steps and are as follows:
#ftp IP Address of NGTJ2 card
Default Username and Password is root.
#bi
#ha
#cd /mmc/ag
#get CdotAgwDb.bin
#bye
#cat net
Note : Check for rwx permission of net file using ls –ls command.
#cd MXNG-CACU2.0/CACUrel/NGTJ/
#ls
If ngtj folder is not present, please transfer ngtj.tar present in Deliverables at /mmc location in NGTJ card using
FTP command.Open terminal in Thin Client PC.
#cd /mmc
#mp ngtj.tar
Important Note:
MXNG-CACU2.0/CACUrel/NGTJ/PATCH13-Over-NGTJCDL1_1_1.6_1-NEW-PRIAG-COMPATIBLE-
MASTER.tar is tar ball having ngtj.tar file which has to be transferred at /mmc location in NGTJ card.
ftp ngtj.tar in /mmc path in NGTJ card.Then login into card and Untar using tar –xvf ngtj.tar.
29
Q22. If Chassis not getting discovered on NGEMS. Check region code.
Ans.
For both SLM cards, Login into SLM card
ssh root@<SLM IP>
Default password is root.
Go to conf folder where slm_sys.conf file is present.
cd /jffs2_ram/SLM/conf
cat slm_sys.conf
Check for Region Code for example region code for NUH Site is North_HA_1267 where HA stands for
Haryana Circle and 1267 is Area Code for Nuh Site.
Please enter Region Code for respective site where CACU Chassis is installed.
If other cards are not getting discovered then please re-install CACU release using Automated script
using Installation Document.
Q23. What to do if CACU Chassis not showing proper on Thin Client PC?
Ans.
If CACU chassis is not properly on Thin Client PC, make sure Thin Client Settings must be done as per
the document. Please follow installation manual for the same.
Ping NGEMS IP for example 10.187.0.41 and 10.187.1.41 for Gurugram & Chandigarh Core Network.
Make sure that Firefox plugins must be installed.
Make sure that Firefox Browser must be installed in Thin Client PC.
If still problem persists then Contact Manufacturer ECIL or BEL Team and ask to replace with working
and tested Thin Client PC.
30
Q24. What to do if all LAGU units are not shown in LAGEMS?
Ans.
If all LAGU units are not shown in LAGEMS, then on right topmost corner three options are available
to minimize, maximize Window.
Q25. What to do if SNMP error Task Failed comes while giving commands in IEMS/LAGEMS
GUI?
Ans. In LAGEMS,
USM User refresh command is used if operator opened SNMP error while working
through GUI.
While giving USM Users refresh, please give FVIP of LAGU System and 8020 default port number.
If problem is not resolved, please contact C-DOT Core Team.
Make sure that Thin Client PC must be configured as per the Installation & Configuration Document.
1. Connect minicom
2. Login to the ICLI (login user: admin password: )
31
# 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
Q28. How to prepare NGTJ AE3 card as NGTJ SE3 card for CACU System?
Ans.
Take LAGU card which is AE3 card specific for RSU site only.
1. Take the backup of the following files from the existing SE3 NGTJ card:
1. I2C/SLM related files:
1. /mmc/NGTJ<1/2> (Depending upon the NGTJ card ID mapped with IP)
2. /mmc/slm/IP/ipconf.txt
3. /mmc/slm/ngtj_sys.conf
4. /mmc/slm/IP/ngtjip.txt (Optional)
5. /mmc/ngtj/run.sh (Optional)
2. SGL2 related files:
1. mmc/sgstk/cdot_sgl2.conf
3. V5AG related files:
1. /mmc/ag/cdotAGdb.bin
2. /mmc/etc/v5ag/extensions.conf
3. /mmc/etc/v5ag/v5.conf
4. PRIAG related files:
1. /mmc/etc/priag/priag.conf
2. /mmc/etc/priag/extensions.conf
5. TMG related files:
1. /mmc/opt/tmg/etc/cdot_tmg.conf
6. AGENT related files:
1. NGTJ Card Agent:
1. /mmc/AGENT/snmp/cardagent/snmpd.conf
2. /mmc/AGENT/snmp/cardagent/gatewayagentdev.conf
2. PRIAG Agent:
1. /mmc/AGENT/PRIAG/cagent/conf/agent.conf
2. /mmc/AGENT/PRIAG/cagent/conf/device.conf
3. /mmc/AGENT/PRIAG/cagent/conf/service.conf
4. /mmc/AGENT/PRIAG/cagent/conf/dev-conf-agent.conf
5. /mmc/AGENT/PRIAG/cagent/conf/ems-agent.conf
3. TMG Agent:
1. /mmc/AGENT/TMG/cagent/conf/agent.conf
2. /mmc/AGENT/TMG/cagent/conf/device.conf
3. /mmc/AGENT/TMG/cagent/conf/service.conf
4. /mmc/AGENT/TMG/cagent/conf/dev-conf-agent.conf
5. /mmc/AGENT/TMG/cagent/conf/ems-agent.conf
4. V5AG Agent:
1. /mmc/AGENT/V5AG/cagent/conf/agent.conf
2. /mmc/AGENT/V5AG/cagent/conf/device.conf
3. /mmc/AGENT/V5AG/cagent/conf/service.conf
4. /mmc/AGENT/V5AG/cagent/conf/dev-conf-agent.conf
5. /mmc/AGENT/V5AG/cagent/conf/ems-agent.conf
2. Ensure that the latest PSG deliverables are loaded on the NGTJ AE3 card as :
S/no Deliverable-Name
1. NGTJ.u-boot.bin.VER53 (UBOOT)
2. NGTJ.uImage.VER52 (LINUX IMAGE)
3. NGTJ.dtb.VER53 (DTB)
4. NGTJ.rfs.s.VER52 (RAM-RFS)
4. Jack-in a spare AE3 card in a free slot, such as for a slot of non-working EBM card.
8. Transfer mmc RFS file RFS_MMC-V05 to the /mmc partition of the NGTJ AE3 card and
untar it on /mmc to copy the mmc rfs on the NGTJ AE3 card.
10. Do not reboot the card and load the backed-up files from the SE3 card in the step-1
to the NGTJ AE3 card.
11. Jack-out the NGTJ AE3 card from the temporary slot to the designated slot where the
SE3 card was previously jacked in and E1s etc are terminating.
33
Procedure to check whether V5/AN-RAXs are working or not
Go to /mmc/ngtj folder.
#cd /mmc/ngtj
Give command ./service status all at /mmc/ngtj location and ensure all applications must be UP.
At /mmc/ngtj location, give command ./service v5 fe and login into V5 FE using Username admin
and Password admin123.
For checking status of AN-RAXs, select 3, 2, 3 and then 7 option for ALL Status for all AN-RAXs.
Then it will display status of all AN-RAXs. AN-RAXs AI status may be in AI-INS, AI-OOS or AI –
Transient.
34
If AN-RAXs are in OOS then again launch V5 FE using Username admin and admin123 and
then select option 3, 2 and then 1. Then give 3 option Start-AI. Success message will be
displayed.
Then check for the status in Display-All-AI-Info option after selecting 3, 2, 3, 7 options and then
1 for ALL AI info. AI status must be AI-INS.
If AI are not in service then check E1 connectivity of particular AN-RAX and reset AN-RAX if
required. LED on front face plate of NGTJ card must be Green. If LED turns Red then physically
E1 is Down.
Dial particular number of same AN-RAX, check for RBT and speech.
For checking PCM AN-RAX wise, use following command to check TX & RX for particular AN-RAX
Note: if PCM is connected on DTK 5 physically then cat 4 and TX, RX both should increase.
b. Following cases that is No RBT and No Dial-tone are observed at actual operational site,
In Case of No Dial-tone
1. If no dial-tone is observed then please make sure that all processes must be UP.
#cd /mmc/ngtj
#. /service ag stop
#. /service ag start
#cd /mmc/ngtj
#./service status all
35
In Case of No RBT
1. If no RBT is observed in NGTJ (CACU) card then please install TMPCH patch.
2. Download TMPCH.tar from cdot helpline portal in CACU and copy below link and paste in Internet
browser.
http://cdothelpline.cdot.in/helpline/latest_updates/MAX_NG/maxng_doc.jsp
3. Go to Access Software Package Downloads --- Patches --- CACU PATCH TAR.
4. Untar CACU PATCHES TAR Ball using below command and is follows:
36
Go to /mmc location in NGTJ card using below command
cd /mmc
Type mp TMPCH.tgz and press y and Enter key
Type bye and press Enter key.
cd /mmc
8. Untar TMPCH.tgz in the same location in NGTJ card and run Read_dsp_ch & command in same
location.
Note: If still problem persists then re-install RFS and Release in NGTJ card from scratch after
formatting mmc as per the procedure.
Q30. How to configure and connect POI to CACU and MAX-NG Core Network?
Ans.
For connecting POI to CACU System,
Please identify E1/PCM and identify Trans and Receive from distant end.
After logging into NGTJ card,
#cd /cdot/bin
#./check_e1_status
For example, if PCM is connected to 5th port physically then logically while checking E1 status
E1 [4] must be UP.
Then after this, please contact respective C-DOT Core Team for configuration of POI.
37
Q31. How to modify AI using MOD-AI command?
Ans.
First block all the links in the AI, and then use this command with expected
input:
we can modify only following parameters of AI:
AI Name, areaCode, numLinks, logical port number, logical link id
**********************************
38
CHAPTER-2
Q1. How to login into NGTJ card and stop all processes in NGTJ card?
Ans.
Please give below command to login into NGTJ card and is as follows:
#chroot /mmc
#cd /etc
#./lag_shutdown.sh 1 or 2 ( 1 for Simplex and 2 for Duplex)
If TIC card is out of service, take DGN of particular TIC card after making TIC card out of
service. If DGN is OK then make TIC card in service. If DGN fails them change TIC card by
working TIC card
3. Check status of LCC card and line status of particular subscriber or LCC card.
#displ card_sts rack=1 frame=1 slot=5 (which will show subscriber status as IDLE,
BUSY)
4. Check whether this problem is of particular subscriber or all subscribers of
particular frame or all frames in Exchange.
5. If still dial tone is not coming, then replace TIC, SPC and TUI cards by
working set of TIC, SPC and TUI cards.
39
6. Also change SPC and TUI card if problem persists.
40
7. Also take dgn of PIC/NGTJ card as well. PIC/NGTJ card should be out
of service.
8. If DGN is OK, then make TIC card in service in another copy of same frame.
9. If problem still persists, change NGTJ card by working and prepared NGTJ
card and check dial-tone after making NGTJ card UP.
10. Even after changing NGTJ card, problem still persists then contact C-DOT
Access Team.
11. If problem got resolved then check all types of calls from LAGU System.
12. If all TIC cards are not coming in service, also check TSI card and TSI card
fuse. If TIC 1, TIC 2, TIC 3 and TIC 4 are not coming in service, also check type of
TIC card for example C type TIC card.
41
Q3. What to do in case of Speech Related Issue?
42
This can also be seen from IP list and also from lag_sys.conf file at /mmc/etc path
in NGTJ card.
After logging into NGTJ card,
#cd /mmc/etc
#cat lag_sys.conf
10. If. Even after hard rebooting NGTJ card, problem persists then please
change NGTJ card by prepared and working NGTJ card.
11. Even if problem is not getting solved then please contact C-DOT
MAX-NG Access Team.
43
Q4. What to do in case of Incoming/Outgoing Calls Related Issue?
1. Check NGTJ card status. Card must be UP and should be in Level 4 or Level 5
depending on connectivity.
#ssh root@<FVIP of NGTJ card>
#tail -f /mmc/tmp/lag_init.log
#ping <Core SBC DomainName>
Note: Domain Name should ping for getting NGTJ card in Level 5.
2. Check intra-LAG call and speech after disconnecting E1/Ethernet cable from Core
network. Please check subscriber status in Class 5 Soft switch through GUI. If in
Level 4 call is OK then please ask Core team to take trace and if problem is related
to Core Network.
3. Check for outgoing barred and incoming barred facilities in Class 5 Softswitch
GUI.
4. Also check Inter-LAG call after reconnecting E1/Ethernet cable.
5. If call is not connecting in Level 4 then kindly contact C-DOT MAX-NG
Access Team.
6. If any announcement is heard after dialing number, kindly contact C-DOT
MAX-NG Core team in this case.
7. If Speech found OK in NGTJ card then problem is not related to LAGU
System. Kindly contact C-DOT MAX-NG Core Team in this case.
8. After getting checked by MAX-NG Core as well as Access team, check all types
of intra-LAG, inter-LAG, Local Mobile, STD Mobile, PCO and ISD calls.
44
Q5. If problem is being faced in logging into NGTJ card through
ssh/telnet/minicom ?
Ans.
1. Before installation, it is very mandatory to note old IP segment of CACU NGTJ cards prepared
& delivered by manufacturer.In SLM card,EBM card IP can be seen through ifconfig command.
2. But in NGTJ (SE3) card,card will be accessed only through Ethernet connection and ssh
command.Give command ssh [email protected] for setup number 1 but
102.21,103.21,….,192.168.108.21 for NGTJ1 for setup number 2,3,4,5,6,7,8. For 5th setup
number, IP will be 192.168.105.21 and 192.168.105.27 for second NGTJ card.
3. For LAGU (AE3) NGTJ cards, we can easily login into NGTJ card through minicom.
4. Please note the IP segment of cards prepared by manufacturer (ECIL/BEL). The segment may be
192.168.101.8, 192.168.102.8, 192.168.103.8, 192.168.104.8, 192.168.105.8, 192.168.106.8,
192. 168.107.8, 192.168.108.8 for SLM card depending on setup number.
5. This was for setup number 1. For setup number 2 IPs will be 192.168.102.8, The total number of
setups prepared by manufacturer at a time is 8. Therefore 192.168.10x.xx will be the segment of
cards where 10x may vary from 101 to 108.
6. IP of CACU cards considering setup number 1 may be as follows:
SLM- 192.168.101.16 (FVIP), SLM1- 192.168.101.17, SLM2-192.168.101.18 NGTJ1 –
192.168.101.21, NGTJ2 – 192.168.101.27,
EBM1- - 192.168.101.19, EBM2 – 192.168.101.20
MLS1 – 192.168.101.12, MLS2 – 192.168.101.15
45
Q6. How to login into NGTJ card?
Ans . To login into NGTJ card , please use ssh command
Ans.
For checking NGTJ card (LAGU), please login into NGTJ card using ssh command.
Give command
tail –f /mmc/tmp/lag_init.log
46
Q8. How to check DSP MAC address and DSP IP
Ans. To check DSP MAC address, give command. /get_dspmac at /cdot/bin location.
#cd /cdot/bin
#./get_dspmac
cd /mmc/etc
cat lag_sys.conf
or
cat /mmc/etc/lag_sys.conf
In this file, DSP MAC is present and entry is in decimal only. Convert Hexadecimal
to decimal. DSP MAC in Hexadecimal can be seen by this procedure after logging
into NGTJ card.
cd /cdot/bin
./get_dspmac
#cat /mmc/etc/lag_sys.conf
Entry in decimal format must be shown.
dspipmac=180.153.76.94.167.218
47
Q9. How to change DSP MAC address in lag_sys.conf?
Ans. If DSP address is clashing with other card in same network then we need to change after verifying
with manufacturer.
In this file, DSP MAC is present and entry is in decimal only. Convert Hexadecimal
to decimal. DSP MAC in Hexadecimal can be seen by this procedure after logging
into NGTJ card.
48
Q10. How to change MAC Address of SLM, EBM, NGTJ, MLS cards?
Ans. To check MAC Address of cards, login into respective cards use ifconfig command.
If any of MAC address clashes with some other entity in same network then please contact Manufacturer
and ask MAC address for card type and Serial Number.
After booting card stop Auto boot after pressing a key and use setenv command.
Ans. For checking connectivity to core network, ping SBC IP of the corresponding core
network. For example, ping 10.187.0.12 for Gurugram Core Network, 10.187.1.12 for
Chandigarh Core Network, 10.187.3.12 for Cuttack core Network. Refer MAX-NG core
IP details for complete Core IP details.
In case core network is not reachable, use traceroute command from CACU cards &
tracepath command from Thin Client PC to check upto which node MAX-NG Access
Network is reachable.
49
Q12. How to give soft reboot and hard reboot to NGTJ card?
cd /etc
50
Q13. How to verify the current patch installed on LAG?
Ans. Login into NGTJ card using ssh command.
#ssh root@< IP Address of NGTJ card>
Q14. How to check the gateway entries in lag_sys.conf file in case one Uplink is down and
call is not getting connected while testing Uplink Redundancy?
In lag_sys.conf file , dspipgw and dspipgw1 should be MLS1 and MLS2 IP for example 10.x.x.4 and
10.x.x.7.
If wrong entries are present then please edit lag_sys.conf file using vi editor in NGTJ card.
#vi /mmc/etc/lag_sys.conf
Press í’ for insert mode and edit file using up,down,left,right and backspace keys then after making
changes please press Esc key ‘:wq!’ to save file. Then file can be checked using cat command.
#cat /mmc/etc/lag_sys.conf
51
Q15. How to check packet loss between LAG & Core network and how to resolve?
Note: For example Gurugram Core Network, SBC IP is 10.187.0.12 and Chandigarh Core Network is
10.187.1.12.
If there is packet loss, then it will show Packet loss when Ctrl+C is pressed and command prompt
comes. Then please make sure that traffic passes through Active MLS link (Uplink) which is MLS1
and MLS2 in the MAX-NG network.
#route –n
In routes, MLS1 and MLS2 IPs are shown.
If wrong IPs are present, then please check gateway IP in lag_sys.conf file in NGTJ card
After logging into NGTJ card,
#cat /mmc/etc/lag_sys.conf
Please check dspipgw and dspipgw1 entries, if found wrong then please edit using vi editor in NGTJ
card.
#vi /mmc/etc/lag_sys.conf
Press í’ for insert mode and edit file using up,down,left,right and backspace keys then after making
changes please press Esc key ‘:wq!’ to save file. Then file can be checked using cat command.
#cat /mmc/etc/lag_sys.conf
#exit
After editing lag_sys.conf file, then please give soft shutdown and restart to NGTJ card.
#ssh root@<self IP address of NGTJ card> (For copy0 use selfeth0)
#cd /mmc/etc
#./lag_shutdown.sh 1 or 2
(1 for Simplex and 2 for Duplex)
#./lag_restart.sh
#tail –f /tmp/lag_init.log
Note: Check for Level 5 in NGTJ card.
52
Q16. How to check status of TIC card, LCC card and subscriber status?
Ans.
For CLI,
displ card_sts rack= frame= slot= (Rack=1,2; Frame=1,2,3,4 slot= 3-10 & 17-24)
And check call once LAG card is in Level 4. If call is not getting connected in Level 4 then
contact MAX-NG Access team and if problem is coming after connecting core network to
LAGU System then please contact MAX-NG Core team of corresponding core network.
53
Q18. How to replace faulty NGTJ card?
Ans. If you are having another NGTJ card with different IP address, following are the
solutions
(A) Replace mmc card from original card in the card which has to be replaced.
#cd /jffs2/conf
#vi net
Change IP address of same working copy in net file at /jffs2/conf location and DSP MAC
address in /mmc/etc/lag_sys.conf file in NGTJ card through minicom cable. Give lag
pre-reboot and give restart to NGTJ card.
Press í’ key for insert mode and edit IP address of self-copy that is for either copy-0 or
copy-1 and press wq! , and then press Enter.
#cat net
#cd /cdot/bin
#./get_dspmc
#cat /mmc/etc/lag_sys.conf
#reboot
49
(B) Take the prepared NGTJ card having latest software as per the site requirement.
#cd /jffs2/conf
#vi net
Press í’ key for insert mode and edit IP address of self-copy that is for either copy-0 or
copy-1 and press wq! and then press Enter.
#cat net
#cd /jffs2/conf
For instance-:
#cat net
#reboot
50
2 ) Format the mmc
#sync
Note: - After mounting the mmc check it's size by df command,It should be 2% to 3%
#df -h
Example -:
Note: 10.187.182.19 is IP Address of NGTJ card and /dev is the location in the NGTJ card. Then it
will ask for NGTJ card Password.
#sync
#cd /mmc
5 ) Give command chroot /mmc after logging into NGTJ card. If prompt sh-2.05b# comes, that
means your RFS install successfully.
#chroot /mmc
51
Q20. How to assign & activate Hotline Facility to LAG Subscriber?
Ans.
52
Q21. How to deactivate Hotline Facility to LAG Subscriber?
Ans.
Q22. How to prepare LAGU copy 0 to copy 1 or vice-versa at RSU site or co-located BM?
Ans. To prepare copy 0 to copy1 or vice versa, please mount jffs2 first and change IP address in NGTJ
card as per copy 0 and copy 1. For example, IP address of copy0 is 10.187.160.31 and 10.187.160.33 and
floating IP address is 10.187.160.35.
chroot /mmc
cd /etc
vi lag_sys.conf
copy =0
selfeth0 = 10.187.160.31
selfeth1 = 10.187.160.32
mateeth0 = 10.187.160.33
mateeth1 = 10.187.160.34
floatip = 10.187.160.35
softswip = ctksbc.maxng.bsnl.in
portno = 5060
actdspipaddr = 10.187.160.36
sbydspipaddr = 10.187.160.37
dspipmask = 255.255.255.0
dspipbrod = 10.187.160.255
dspipgw = 10.187.160.7
dspipgw1 = 10.187.160.10
dspipsrvr = 10.187.160.31
53
dspipmac = 212.54.57.41.69.96
ntpsrvr = 10.187.3.12
featserver = 10.187.3.15
dnsbasedrouting = yes
prssip = 10.187.3.12Hello,
For changing copy 0 to copy 1 of NGTJ card , please make following changes:
Net file
Note : For changing IP address make sure IP address corresponding to required copy
must be entered . Above is the example for copy 0
54
CHAPTER-3
MISCELLANEOUS QUERIES
Ans.
Ans.
Step 1:
Insert digit 55 (choose any digits, which is not having any level or route in the MAX System) as prefix digits in the incoming
TGP of POI.
Step 2:
Create a route 552 having the TGP choice towards CACU end as 55 is prefixed.
Step 3:
Set the ROD=3 for the outgoing TGP towards CACU end.
Step 4:
Insert digit 56 (choose any digits, which is not having any level or route in the MAX System) as prefix digits in the incoming
TGP of CACU.
Step 5:
Create a route 56X (depending on Level of POI and X is the level) having the TGP choice towards POI end.
Step 6:
Set the ROD=3 for the outgoing TGP towards the POI end.
55
CHAPTER-4
THIN CLIENT PC RELATED QUERIES
56
Note: Above entries are indicative only. Please enter Entries as per specific site details.
Download IP Details from MAX-NG Rollout Management portal.
Link: cdothelpline.cdot.in
a. Open Terminal.
#cd /home/ubuntu/Desktop
Q4. How to transfer file from NGTJ card to Thin Client PC?
Ans. Open terminal in Thin Client PC and make sure that IP and Gateway should be added.
#ifconfig
#cd /mmc/ngtj (Go to specific directory in NGTJ card where file is required to be
transferred)
#mp <filename>
#bye
57
Q5. If a user forgets the root password in Thin Client PC then how to change the password?
Ans.
It is mandatory to load the uboot version 53 on the RSU LAGU NGTJ cards with E1 connectivity for
2 E1s or more than 2 E1s and to load dtb version 53 on the CACU NGTJ cards.
58
CHAPTER-5
C-DOT
MAX-NG ACCESS DUAL
GATEWAY
REACHABILITY &
VERIFICATION
59
Basic configuration
To configure the network with dual Gateway, given configuration have to be done.
1. Make sure that Both the MLS card must be configured as per the Document.
2. Cross check the VLAN ID provided, it should be same at both end (PE Router and MLS).
3. Port configuration is also same as per the PE Router side (Either Auto or 1GB).
4. Priority must be save for both MLS, it should be higher for 1st MLS and lower for 2nd (0
being highest priority)
5. BFD Configuration at PE Router must be done.
6. LAN pool must be published at PE router end, behind each WAN Interface (IPTAX, SSTP,
CDOT-VOIP).
7. The corresponding uplink must be in sync i.e. LED corresponding to the uplink (Port 21,
22) in MLS must be glowing green.
To crosscheck for dual uplink connectivity, we have make sure that core is reachable from the
CACU for both the uplinks. To verify it, follow the given points.
1. Connect the Thinclient and CACU with the LAN IP provided. Crosscheck with ifconfig
command.
2. Check the gateway in Thinclient, it should be IP of 1st MLS. Crosscheck with route -n
command. If gateway is not present, add with command “route add default gw <IP of
MLS 1st > “.
3. Remove 2nd uplink and ping both the MLS card and other CACU cards, all IP must ping
without packet loss.
4. Ping WAN IP of PE Router side, all IP must ping without packet loss.
5. Ping CORE server, all IP should ping without any packet loss. (If CORE IP is not pinging,
make sure that LAN pool is published at PE Router end).
6. Take traceroute from Thin client to CORE IP, it must be passed from the 1st uplink IP. Use
command traceroute< IP > or tracepath< IP>.
58
60
9. Repeat the points 3,4,5,6 for 2nd uplink also.
10. Now insert the both uplink, and ping all the network again. It must be ping without any
packet loss.
11. Once CACU is installed with the latest patch and release, Gateway must change
automatically in all cards of CACU when remove any of the uplink. While in Thin Client
PC, user have to be added the Gateway IP manually.
59
LAGU to PE Router YES No
60