Cisco Cisco ASR 5500 Guida Dell'Amministratore
InTracer Overview
▀ Cisco InTracer Architecture
▄ Cisco InTracer Installation and Administration Guide
12
Figure 2.
3GPP Trace
InTracer Architecture Scalability
Although the above architecture diagram shows a 1:1 mapping between the Gateway and the R-InTracer / R-TCE
server, the architecture is scalable.
server, the architecture is scalable.
Nodal Trace
In this trace, since a copy of all signaling packets for each subscriber session is sent from the Gateway to the R-
InTracer, deployments with high subscriber session rates might require more than one R-InTracer servers to be
configured per Gateway. This feature is supported.
InTracer, deployments with high subscriber session rates might require more than one R-InTracer servers to be
configured per Gateway. This feature is supported.
3GPP Trace
In this trace, since signaling packets for only activated subscriber sessions are sent from the Gateway to the R-TCE,
multiple Gateways should be able to send XML trace files to a single R-TCE server. This feature is supported.
multiple Gateways should be able to send XML trace files to a single R-TCE server. This feature is supported.
InTracer Components
This section provides the physical / logical components of InTracer solution.
Component Table
Component
Nodal Trace
3GPP Trace
InTracer client
When configured sends a copy of all
signaling packets for all sessions to the R-
InTracer over UDP.
signaling packets for all sessions to the R-
InTracer over UDP.
When configured, sends a copy of all signaling packets for
activated trace sessions to the R-TCE by pushing the
generated XML trace files via FTP/SFTP.
activated trace sessions to the R-TCE by pushing the
generated XML trace files via FTP/SFTP.