InTracer Network Requirements

This chapter identifies the network requirements of various InTracer components. It includes the following sub-sections:

Network Considerations

Interface between InTracer Client and R-InTracer

For Nodal trace, the InTracer traffic does not use the management interface of the gateway, but requires a data interface. This means that there has to be connectivity from one of the ASR5xxx Line Cards to the R-InTracer.

Following interface parameter values should be met to ensure proper operation of InTracer:

Interface Parameters Values for Nodal Trace

Throughput

Minimum of 100 Mbps

NAT

Not allowed

Firewall

Not tested



Interface between InTracer Client and R-TCE

For 3GPP trace, the XML files are pushed from the 7600 / ASR5K gateway services to the R-TCE.

Following interface parameter values should be met to ensure proper operation of InTracer:

Interface Parameters Values for 3GPP trace

Throughput

Minimum of 100 Mbps

NAT

May be used

Firewall

May be used



Interface between R-InTracer and C-InTracer

For performance reasons, it is recommended to use a separate physical interface on the R-InTracer to communicate with the InTracer Client and the C-InTracer.

Following interface parameter values should be met to ensure proper operation of InTracer:

Interface Parameters Values

Throughput

Minimum of 100 Mbps

NAT

May be used

Firewall

Not tested



Network Default Port Utilization

InTracer components use various TCP/UDP ports for communicating with each other. If firewalls are used on these network interfaces, appropriate ports need to be opened. Following tables provide the default ports used by the corresponding InTracer component.

InTracer Client

Port number Port type Description

UDP

For Nodal Trace only

On the interface with the R-InTracer

Opened by the InTracer Heart-beat Controller task to receive responses from configured R-InTracer(s)



R-InTracer

Port number Port type Description

45000

TCP

On the interface with the C-InTracer

For InTracer configuration and statistics management traffic

45000

UDP

On the interface with the C-InTracer

For internal use

45001

TCP

On the interface with the C-InTracer

For InTracer user query traffic

45001-45004

UDP

For Nodal Trace only

On the interface with InTracer Client

For receiving signaling packets from the Gateway



C-InTracer

Port number Port type Description

45000

TCP

On the management interface

For InTracer configuration and statistics management traffic

45000

UDP

On the management interface

For internal use

45001

TCP

On the management interface

For InTracer user query traffic

45002

TCP

On the management interface

For InTracer user query background scheduling using RPC

For receiving signaling packets from the Gateway

8080

TCP

On the management interface

Apache HTTP server listen port

8443

TCP

Apache HTTP SSL Port

5432

TCP

On the management interface

PostgreSQL Database server listen port



CAUTION:

Same ports should be used during configuration which you have selected during InTracer installation.

Time Synchronization

To ensure proper operation and near real time functioning of InTracer search queries, all Intracer components including the Client, R-InTracer(s) and the C-InTracer along with ASR5K should be time synchronized. It is recommended to use NTP or similar supported protocol to perform this time synchronization.

CAUTION:

If the InTracer components are not time synchronized it may result packet loss. In statistics it is displayed as "Old dropped". This may impact the loss of call data and important events. It can also impact the in tracer functionality.