Scribd
Upload
147 views23 pages

SME PPT TCU02 Technical Description

This document provides an overview of SIU02/TCU02 devices and their features. It describes the hardware components, network topology, and key functions of the STN (Site Transmission Unit) and TCU (Transport Connectivity Unit) such as Abis over IP, circuit emulation, synchronization, and policy-based routing. It also provides examples of basic commands used to check the status, configuration, and troubleshoot SIU/TCU devices.

Uploaded by

abhinav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
147 views23 pages

SME PPT TCU02 Technical Description

This document provides an overview of SIU02/TCU02 devices and their features. It describes the hardware components, network topology, and key functions of the STN (Site Transmission Unit) and TCU (Transport Connectivity Unit) such as Abis over IP, circuit emulation, synchronization, and policy-based routing. It also provides examples of basic commands used to check the status, configuration, and troubleshoot SIU/TCU devices.

Uploaded by

abhinav
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 23

SIU02/TCU02 Overview , Technical

Description
Content

• Overview
• Types of STN (Site Transmission Unit)
• STN Hardware Description
• Network Topology
• TCU Features (Transport Connectivity Unit)
• How to access SIU/TCU Basic commands
• Benefits
• Summary
Overview
Overview
TYPE OF STN
SIU-01 HARDWARE
SIU-02 HARDWARE
TCU-02 HARDWARE
FEATURES

• Bidirectional Forwarding Detection


• ABIS over IP
• Circuit Emulation
• Synchronization
• IP Loopback
• Policy based Routing
Bidirectional Forwarding Detection

• BFD facilitates minimal traffic


interruption in case of link/path
failures
• BFD rapidly detects failures along
the path within milliseconds
(depending on configured
transmission intervals and retry
attempts). This facilitates rapid
repair mechanisms to minimize
service disruption.
• The feature reduces the impact of
faults in the backhaul network by
providing fast detection and fast
reroute to an alternate path (if
present).
Abis over IP
 GSM RBSs use TDM (E1/T1) as their transport connection
 The Abis over IP function enables the RBS to use an IP/Ethernet transport network for backhauling instead
 Using the existing TDM backhaul for IP transport facilitates the migration to all-IP. The benefits if IP transport
can be reaped without replacing the existing TDM backhaul.
Circuit Emulation
• The Circuit Emulation (CES) feature enables the TCU/SIU to backhaul TDM based equipment
over IP networks. The TDM service provided is structured E1/T1s with support for 1-31/24
DS0s per E1/T1.
• Moving from a TDM based transport network to one based on IP enables higher capacities at
lower costs. To fully utilize IP networks and to avoid operating parallel transport
infrastructures it is important to be able to move all traffic on an RBS site to IP.
• Using this feature, the customer is able to backhaul legacy RBSs and other TDM based
equipment over an IP based network.
Frequency Synchronization Client with NTP
over IP
• This feature enables NTP frequency
synchronization for an IP-only connected
SIU/TCU.
• This solution is cost efficient compared to the
alternative of providing an external clock source,
such as a GPS receiver.
• The feature also supports quick roll-out of new IP-
based RBSs, or move from TDM to IP backhaul,
as no synchronization support in the transport
network is required.
• Stable oscillator in TCU/SIU provides long-term
stability
Access TCU

• Connect TCU via Local Management Terminal


• RJ45 connector to Local Management port
• telnet 192.168.1.1/24
• username: admin
• password: hidden
• TCU prompt: OSmon>
BASIC COMMANDS &
MAC from DUW

• Check Neighbour status :-

MAC from Router


Connected Interface
Conclusion:If MAC address is getting learned it means that layer
2 connectivity from TCU to Router is clear. .
BASIC COMMANDS & TROUBLESHOOTING

• Check BFD status :

Conclusion : If BFD status is Up that means L3 connectivity is through


between router and TCU .
BASIC COMMANDS & TROUBLESHOOTING

• BFD session Counter

perfSessUpCount : The number of times this BFD session has


gone into the "up" state.
BASIC COMMANDS & TROUBLESHOOTING

• To check whether TCU is reachable for all Interfaces regarding Abis, IUB and MUB

For Abis Service : # ping <PGW_IP>

For IuB Service : # ping <NTP_IP>

For MuB Service : # ping <OSS_IP>


If 0% packet Loss , its clear that no transmission path issue is there from TCU to Router i.e in south bound part.
If partial packet loss is observed , then there might be issue in Transmission path or some local cabling interface in TCU end that
need to taken care of…Mostly issue is being observed in transmission MW path.
Such ping drop will result in HS drops and throughput issues.
Also to check TCU port health , TCU may be replaced at Site with Laptop and configure VLAN & interface IP and check the ping
status. In this way we can isolate TCU from network and isolate media issues.
In critical cases we can suggest for End to end media testing with Ethernet tester.
BASIC COMMANDS & TROUBLESHOOTING
• PATH & ROUTE CHECK-
TCU_5895-OSmon> show ip route
Codes: K - kernel, C - connected, S - static, R - RIP, B - BGP
O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, ia - IS-IS inter area
ew - East-West API * - candidate default
show ip route command output
C 10.28.23.108/32 is directly connected, lo
C 10.28.55.108/32 is directly connected, lo
C 10.40.20.64/30 is directly connected, eth4.1630 will show all the ip routes,
C 10.40.20.68/30 is directly connected, eth4.1631
C 10.40.20.72/30 is directly connected, eth4.1632 which helped us to structure
C 10.40.20.76/30 is directly connected, eth4.1633
C 10.40.20.80/30 is directly connected, eth4.1634 the ping command quickly.
C 10.40.20.84/30 is directly connected, eth4.1635
C 10.40.20.88/30 is directly connected, eth6.100
C 10.40.20.92/30 is directly connected, eth6.200
S 10.223.6.0/24 [2/0] via 10.40.20.69, eth4.1631
S 10.223.36.128/26 [2/0] via 10.40.20.65, eth4.1630
S 10.223.60.0/24 [2/0] via 10.40.20.73, eth4.1632
C 127.0.0.0/8 is directly connected, lo
BASIC COMMANDS & TROUBLESHOOTING

• Traceroute
With traceroute command from TCU we can check the IP routes
via which traffic is reaching destination node.
TCU_4113-OSmon> traceroute 10.223.2.6
traceroute to 10.223.2.6 (10.223.2.6), 30 hops max, 60 byte packets
1 10.30.47.81 (10.30.47.81) 14.794 ms 13.615 ms 11.559 ms
2 10.220.66.169 (10.220.66.169) 6.330 ms 7.234 ms 10.749 ms
3 10.223.2.6 (10.223.2.6) 5.457 ms 6.379 ms 5.919 ms
In several occasion during integration process destination Node like OSS/NTP is not
reachable from TCU where as next hop address is reachable ,we may use traceroute
command to isolate the issue after which hop IP packet is getting dropped.
BASIC COMMANDS & TROUBLESHOOTING
 To get the TG detail and PGW IP- getmoattribute STN=0, TGtransport=all

 To get the Virtual IP address - getmoattribute STN=0, VirtualIPInterface=all

 To get the NTP IP address - getmoattribute STN=0, synchronization=0,timeserver=all


BASIC COMMANDS & TROUBLESHOOTING
• To get alarms in TCU :

 To check the Status of E1 in TCU :

The status of the E1T1 interface should be enabled


and port labels are marked in yellow.
BASIC COMMANDS & TROUBLESHOOTING
• To check TCU Sync quality status:-

• To check the routing table of TCU :-

• To Check The System Logs

You might also like