CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
CLI procedures for Traffic Node’s
1. Connecting to a Traffic Node with Telnet
1.1 Finding IP address of the Traffic node
1.2 Connecting with a Traffic Node with Telnet .
2. Procedures
2.1 Show E1 trails / connections
2.2 Show position of the units in the rack
2.3 Show boards information (Serial ,Type Software version)
2.4 Worm restart on Traffic Node
2.5 How to check the temperature
2.6 How to place loops E1 trails
2.7 How to check the configuration of a port :
2.8 How to make a TDM E1 connection between two units (MMU/NPU)
2.9 Crash logs / syslog
2.10 Alarms on ports
3. Shortcomings
Regards to Ion Laurentui Dorin
1 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
1. Connecting to a Traffic Node with Telnet
1.1 Finding IP address of the Traffic node :
- From Visio file (fig.1)
Fig. 1
- From SOM , by click on Network Data List (fig 2) , we can obtain the
IP address from the new window wich it will appear in the right workspace
(fig. 3)
2 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Fig.2
Fig. 3
Rev
Reference
Error!
Error! Unknown
Unknow document property
3 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
1.2 Connecting with a Traffic Node with Telnet .
- Open command prompt (Start->cmd)
- For testing if the site is reachable we can try to “ping” it
- To connect we use Telente :
>telnet <IP_Address>
- Password used : ericsson
Fig.4
- Now we are in Exec Mode , CLI commands for the TN are sorted
into classes (Fig. 5),
Fig. 5
4 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
- To enable Privileged Exec Mode we enter
NE-CL17-2-1> enable
Password : ericsson
NE-CL17-2-1#
NOTE: Privileged mode offer the capability to change configuration
on TN , be careful when using “configure” command. (please don’t try
commands witch are not cover by this paper )
- For more power on configuration and debug on TN we can enable
hidden command by entering :
NE-CL17-2-1# cliunlock
NOTE: Hidden command offer more power on configuring and debug
, use it with caution (please don’t try commands witch are not cover by this
paper )
2. Procedures
2.1 Show E1 trails / connections:
(privilege+cliunlock)# show connections <ID>
<ID> is optional , if it is not inserted it will display all connection on the TN.
We can see in the next figure the correlation between Minilink craft and CLI.
5 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
Fig.6
2.2 Show position of the units in the rack :
NE-CL17-2-1# show subrack <subrack_number>
<subrack_number > usually is “1” , in the next figure we can see the
correlation between Minilink craft and CLI.
Fig. 7
6 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Date
Error!
Unknown
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
2.3 Show boards information (Serial ,Type Software version)
NE-CL17-2-1#show board <Subrack/Slot>
Note: In the next figure we displayed info regarding the MMU2 C (1/2) , we
can se the correlation with the minilink craft
Fig. 8
For more board info we can use the following arguments :
NE-CL17-2-1#show board 1 / 2 config
- check if it is in service and if it is enable
NE-CL17-2-1#show board 1 / 2 status
- check if board is in repair mode.
2.4 Worm restart on Traffic Node.
NE-CL17-2-1#reload
2.5 How to check the temperature
NE-CL17-2-1#show temp
Note: it will show the current temperature of each board, and the high /
exceed values .
7 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Date
Error!
Unknown
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
2.6 How to place loops E1 trails
Fig 9
Enter configuration mode :
NE-CL17 -2-1#config
Select the e1 controller (use show trail to identify where to place the loop
and what tipe of loop (line loop , or local loop , usually we use local loop):
Enter controller configuration mode:
NE-CL17-2-1#controller e1 <Rack/Slot/Port>
For MMU wich uses an E2 (example) we use the following syntax:
NE-CL17-2-1#controller e2 “Rack/Slot/Port Port.number”
Fig. 10
8 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
When you are on controller configuration mode we can place tha
loca/line loop :
NE-CL17-2-1<config-contr>#loopback local/line
For removing the loop use
NE-CL17-2-1<config-contr># no loopback local/line
Exiting configuration mode or controller configuration mode is made by
entering “exit” in CLI .
2.7 How to check the configuration of a port :
NE-CL17-2-1#show configuration <Rack/Slot/Port>
NOTE: when ports configured with next pathern 1/1/4A (usually on NPU)
we can use “1/1/0”
Fig. 11
Note : we can use this command to determine if there is any loops on our
E1 trail , also different configuration option , if ais-alarm si active , interface
name , correlation between physical position of port and name of the port,
if the connection is active .
9 (15)
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
10 (15)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
Fig. 12
2.8 How to make a TDM E1 connection between two units
(MMU/NPU)
There are 2 methods to make a connection between :
- easy way , by declaring a E1 connection between 2 units
(NPU/MMU) with the following procedure:
a. enter configuration mode
b. enter :
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
11 (15)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
NE-CL17-2-1(config)#connect “Name_connection” <e1/ds1> “port a”
<e1/ds1> “port b”
NOTE : to be able to make this configuration we need that the TN to
all redy have an configuration uploaded . To find witch port correspond the
name we can use show configuration .
Example we will take the following situation:
On NPU position 1/1 we have port 1/1/4A , for this command we will need
the physical position of the port , and we can find it by using show
configuration <Rack/Slot/Port> . In the next picture we will see the
correlation between physical position and connection name.
Fig. 13
- The hard way , to note this method works only when the TN is not in
Operational mode (used only in configuration ).
a. Firs we creat a cross connection by referring to the interface by
name . Used for not disrupting traffic during a warm restart.
local(config)#cc <if name 1> <if name 2> <cc name> <TS
serie id (future use)>
b. Second we create a cross connection using specified TDM
Local(config)#connect-tdm “Name” e1 1/1/0 e1 1/2/1 tdms 33 tdminfo
0-36;0-37;0-231;0-232;0-427;0-428;0-623;0-624;0-820;0-821;0-1016;0-1017;01212;0-1213;0-1408;0-1409;0-1605;0-1606;0-1801;0-1802;0-1998;0-1999;02194;0-2195;0-2390;0-2391;0-2586;0-2587;0-2783;0-2784;0-2979;0-2980;03176;0-3177;0-3372;0-3373;0-3568;0-3569;0-3764;0-3765;0-3961;0-3962;0-
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
12 (15)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
4157;0-4158;0-4354;0-4355;0-4550;0-4551;0-4746;0-4747;0-4942;0-4943;05139;0-5140;0-5335;0-5336;0-5531;0-5532;0-5728;0-5729;0-5924;0-5925;06120;0-6121;0-6317;0-6318;
Note :this method is used only in making the configuration file.
2.9 Crash logs / syslog
For finding out last actions made on the TN we can use the following
command :
NE-CL17-2-1#show x crashlog
Note : it will display the entire crashlog on the screen starting with the past
till last changes made on equipment.
Crash log example :
We can see that simulation of cold restart on NPU was tested.
For viewing the syslog we can use the next command :
NE-CL17-2-1#show x tail-syslog
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
13 (15)
No.
Alexandru Aldea
Approved
Checked
Date
Error!
Unknown
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
2.10 Alarms on physical ports.
To display alarms on physical ports we need the following command.
NE-CL17-2-1# show pm_int_port phy <Slot> <Physic_PORT>
In the next figure we can see an view with no alarms on the port
In the next figure we can see an view with alarms on the port
Second Error Set alarm on the E1 port.
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
14 (15)
No.
Alexandru Aldea
Approved
Checked
Date
Error!
Unknown
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property
3. Shortcomings
CLI offers configuration and debugging options only for NPU and MMU ,
between E1 trails , configuring management , routing , routing protocols
witch will be use .
From
Till now I didn’t find out any method to obtain info regarding the radio part
(signal strength , alarms on RAU , IF ,RF only Rx loop by using line loop on
MMU E1 port ).
The only info regarding the Radio link we can obtain from the tables
declared for the radio link application (rl ) but I couldn’t decipher it.
CLI JOB AID FOR TRAFFIC NODE
Prepared (also subject responsible if other)
15 (15)
No.
Alexandru Aldea
Approved
Checked
Error!
Unknown
Date
02/08/2010
Rev
Reference
Error!
Error! Unknown
Unknow document property