100% found this document useful (1 vote)
249 views

Basic Command On Troubleshooting of TCU

This document describes common commands for troubleshooting a Transport Connectivity Unit (TCU) including: 1) Checking alarms with the "getalarmlist" command. 2) Viewing managed objects (MOs) within the TCU configuration using "getcontainment". 3) Checking MO attributes like status and settings using "getmoattribute". 4) Viewing the MAC address table associated with network ports using "showMACFwTable". 5) Checking counters with commands to monitor traffic, errors, and performance.

Uploaded by

Moctar Moumouni
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
100% found this document useful (1 vote)
249 views

Basic Command On Troubleshooting of TCU

This document describes common commands for troubleshooting a Transport Connectivity Unit (TCU) including: 1) Checking alarms with the "getalarmlist" command. 2) Viewing managed objects (MOs) within the TCU configuration using "getcontainment". 3) Checking MO attributes like status and settings using "getmoattribute". 4) Viewing the MAC address table associated with network ports using "showMACFwTable". 5) Checking counters with commands to monitor traffic, errors, and performance.

Uploaded by

Moctar Moumouni
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 16

Basic command

on
troubleshooting
of TCU

By: ahmad fauzi


Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 1
table of contents
1. Abstract
2. Alarm Check
3. Containment Check
4. MO Attribute Check
5. MAC-Address Table check
6. Counters Check
7. Closing

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 2


1. abstract
This document will describe a common command usually
implemented to check on troubleshooting phase of TCU
(Transport Connectivity Unit) implementation. TCU implemented
in ABIS-over-IP integration of 2G BTS and it’s also as a bridge for
3G Node-B.
The reader of this document assumed already familiar with TCU
operations, integration, and/or ABIS-over-IP integration.

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 3


2. Alarm check
This command will show all alarms occur in TCU:
OSmon> getalarmlist
 STN=0,E1T1Interface=3;
 alarmId= 94;
 eventTime= 2013-05-29 T08:12:31;
 eventType= "communicationsAlarm(2)";
 perceivedSeverity= "minor(3)";
 probableCause= "x733LossOfSignal(329)";
 specificProblem= "E1/T1 Loss of Signal";
 additionalText= "LOS";

 STN=0,E1T1Interface=3;
 alarmId= 100;
 eventTime= 2013-05-29 T08:12:41;
 eventType= "communicationsAlarm(2)";
 perceivedSeverity= "warning(4)";
 probableCause= "x736OutOfService(347)";
 specificProblem= "E1/T1 unavailable time";
 additionalText= "E1/T1 Interface in unavailable state due to set of consecutive SES events";
 OperationSucceeded

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 4


3. Containment Check
This command will show the list of MO inside TCU configuration.
If needed to show the detail status of each MO then use
getmoattribute command (point no. 4).
OSmon> getcontainment STN=0
STN=0;
STN=0,Bridge=Iub;
STN=0,Bridge=Iub900;
STN=0,Bridge=Iub_Backup;
STN=0,Bridge=Mub;
STN=0,Bridge=Mub900;
STN=0,Bridge=Mub_Backup;
STN=0,E1T1Interface=0;
STN=0,E1T1Interface=1;
STN=0,E1T1Interface=2;
STN=0,E1T1Interface=3;
STN=0,E1T1Interface=4;
STN=0,E1T1Interface=5;
STN=0,E1T1Interface=6;
STN=0,E1T1Interface=7;
STN=0,Equipment=0;
STN=0,EthernetInterface=Node_B;
STN=0,EthernetInterface=U900;

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 5


Containment Check ……cont
 STN=0,EthernetInterface=WAN;
 STN=0,IPInterface=2G;
 STN=0,IPInterface=OM;
 STN=0,IPv6RoutingTable=0;
 STN=0,MeasurementDefinition=0;
 STN=0,QosPolicy=0;
 STN=0,RoutingTable=0;
 STN=0,RoutingTable=0,IpRoute=NTPS;
 STN=0,RoutingTable=0,IpRoute=NWIE;
 STN=0,RoutingTable=0,IpRoute=PGW;
 STN=0,RoutingTable=0,IpRouteSys=2G;
 STN=0,RoutingTable=0,IpRouteSys=DefaultGateway;
 STN=0,RoutingTable=0,IpRouteSys=OM;
 STN=0,Synchronization=0;
 STN=0,Synchronization=0,TimeServer=TS1;
 STN=0,Synchronization=0,TimeServer=TS2;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI,SuperChannel=0;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI,SuperChannel=1;
 STN=0,TGTransport=DHIP_BEJI_PERMAI;
 STN=0,TGTransport=DHIP_BEJI_PERMAI,SuperChannel=0;
 STN=0,TGTransport=DHIP_BEJI_PERMAI,SuperChannel=1;

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 6


Containment Check ……cont
 STN=0,TGTransport=DIP_BEJI_PERMAI;
 STN=0,TGTransport=DIP_BEJI_PERMAI,SuperChannel=0;
 STN=0,TGTransport=DIP_BEJI_PERMAI,SuperChannel=1;
 STN=0,TGTransport=GIP_BEJI_PERMAI;
 STN=0,TGTransport=GIP_BEJI_PERMAI,SuperChannel=0;
 STN=0,TGTransport=GIP_BEJI_PERMAI,SuperChannel=1;
 STN=0,TrafficManager=QoS;
 STN=0,VLANGroup=Node_B;
 STN=0,VLANGroup=Node_B,VLAN=VLAN_Iub;
 STN=0,VLANGroup=Node_B,VLAN=VLAN_Iub_Backup;
 STN=0,VLANGroup=Node_B,VLAN=VLAN_Mub;
 STN=0,VLANGroup=Node_B,VLAN=VLAN_Mub_Backup;
 STN=0,VLANGroup=U900;
 STN=0,VLANGroup=U900,VLAN=VLAN_Iub900;
 STN=0,VLANGroup=U900,VLAN=VLAN_Mub900;
 STN=0,VLANGroup=WAN;
 STN=0,VLANGroup=WAN,VLAN=2G;
 STN=0,VLANGroup=WAN,VLAN=OM;
 STN=0,VLANGroup=WAN,VLAN=VLAN_Iub;
 STN=0,VLANGroup=WAN,VLAN=VLAN_Iub900;
 STN=0,VLANGroup=WAN,VLAN=VLAN_Iub_Backup;
 STN=0,VLANGroup=WAN,VLAN=VLAN_Mub;
 STN=0,VLANGroup=WAN,VLAN=VLAN_Mub900;
 STN=0,VLANGroup=WAN,VLAN=VLAN_Mub_Backup;
 OperationSucceeded

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 7


4. MO Attribute Check
This command will show the detail status of each MO. For
example if needed to check the status of all TGTransport as
below:
 OSmon> getmoattribute STN=0,TGTransport=all
 STN=0,TGTransport=DIP_BEJI_PERMAI; instanceId= DIP_BEJI_PERMAI;
 STN=0,TGTransport=DIP_BEJI_PERMAI; operationalState= enabled;
 STN=0,TGTransport=DIP_BEJI_PERMAI; PGW_IP_Address= 10.249.255.131;
 STN=0,TGTransport=DIP_BEJI_PERMAI; depIP_Interface= STN=0,IPInterface=2G;
 STN=0,TGTransport=DIP_BEJI_PERMAI; STN_PGW_LinkStatus= up;
 STN=0,TGTransport=DIP_BEJI_PERMAI; overloadThreshold= 1000;
 STN=0,TGTransport=DIP_BEJI_PERMAI; overloadReportInterval= 1;
 STN=0,TGTransport=DIP_BEJI_PERMAI; DSCP_L2TP_CP= 47;
 STN=0,TGTransport=GIP_BEJI_PERMAI; instanceId= GIP_BEJI_PERMAI;
 STN=0,TGTransport=GIP_BEJI_PERMAI; operationalState= enabled;
 STN=0,TGTransport=GIP_BEJI_PERMAI; PGW_IP_Address= 10.249.255.131;
 STN=0,TGTransport=GIP_BEJI_PERMAI; depIP_Interface= STN=0,IPInterface=2G;
 STN=0,TGTransport=GIP_BEJI_PERMAI; STN_PGW_LinkStatus= up;
 STN=0,TGTransport=GIP_BEJI_PERMAI; overloadThreshold= 1000;
 STN=0,TGTransport=GIP_BEJI_PERMAI; overloadReportInterval= 1;
 STN=0,TGTransport=GIP_BEJI_PERMAI; DSCP_L2TP_CP= 47;

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 8


MO Attribute Check…..CONT
 STN=0,TGTransport=DHIP_BEJI_PERMAI; instanceId= DHIP_BEJI_PERMAI;
 STN=0,TGTransport=DHIP_BEJI_PERMAI; operationalState= disabled;
 STN=0,TGTransport=DHIP_BEJI_PERMAI; PGW_IP_Address= 10.249.255.131;
 STN=0,TGTransport=DHIP_BEJI_PERMAI; depIP_Interface= STN=0,IPInterface=2G;
 STN=0,TGTransport=DHIP_BEJI_PERMAI; STN_PGW_LinkStatus= lost;
 STN=0,TGTransport=DHIP_BEJI_PERMAI; overloadThreshold= 10;
 STN=0,TGTransport=DHIP_BEJI_PERMAI; overloadReportInterval= 1;
 STN=0,TGTransport=DHIP_BEJI_PERMAI; DSCP_L2TP_CP= 47;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI; instanceId= DHHIP_BEJI_PERMAI;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI; operationalState= disabled;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI; PGW_IP_Address= 10.249.255.131;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI; depIP_Interface= STN=0,IPInterface=2G;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI; STN_PGW_LinkStatus= lost;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI; overloadThreshold= 10;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI; overloadReportInterval= 1;
 STN=0,TGTransport=DHHIP_BEJI_PERMAI; DSCP_L2TP_CP= 47;
 OperationSucceeded

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 9


5. mac address table Check
This command will show the mac-address table related to WAN port
and Node-B (both 3G 2100 and 3G 900) port.
OSmon> showMACFwTable all
 MAC Port tagValue Forward Timeout
 3c19.7dbd.5bbd STN=0,EthernetInterface=Node_B 1418 True 300
 3c19.7dbd.5bbd STN=0,EthernetInterface=Node_B 1403 True 300
 0021.05e0.b210 STN=0,EthernetInterface=WAN 1405 True 300
 0021.05e0.b210 STN=0,EthernetInterface=WAN 1403 True 300
 0000.5e00.010a STN=0,EthernetInterface=WAN 1418 True 300
 0000.5e00.010a STN=0,EthernetInterface=WAN 1405 True 300
 0000.5e00.010a STN=0,EthernetInterface=WAN 1420 True 300
 0000.5e00.010a STN=0,EthernetInterface=WAN 1403 True 300
 0023.3ee4.24fa STN=0,EthernetInterface=WAN 1420 True 300
 0023.3ee4.24f8 STN=0,EthernetInterface=WAN 1418 True 300
 0021.05e0.b20b STN=0,EthernetInterface=WAN 1420 True 300
 3407.fb17.4532 STN=0,EthernetInterface=U900 1420 True 300
 3407.fb17.4532 STN=0,EthernetInterface=U900 1405 True 300

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 10


6. Check counters
 There are several common counters usually checked during

troubleshooting phase:

1. Ethernet Interface (WAN) => to check the error number in

WAN Ethernet interface of TCU that going to transport

equipment (ML-TN or Metro Ethernet).

2. TG Transport => to check the error and lost number in Abis

packets/octets.

3. E1T1 Interface => to check the error seconds and

unavailability time in E1T1 interface going to DUGs.


Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 11
6.1 ethernet interface
Counters

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 12


6.2 TG Transport Counters

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 13


6.2 TG Transport Counters

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 14


7. closing

 Those 6 common commands are not the only command we can

explore in troubleshooting of TCU, but those are the most

frequently use and they are quite enough to make sure that

TCU has no problem but others part are.

Basic Command on Troubleshooting of TCU | Ericsson ID | 2013-10-23 | Page 15

You might also like