User Manual

ADCP-75-192 • Issue 1 • December 2005 • Section 3: Network and System Installation and Setup
Page 3-11
2005, ADC Telecommunications, Inc.
Figure 3-2. Tracing Pathtrace, Two Tenants
6.3.4 Pathtrace Reverse Transmission
The RDC is the originator of the pathtrace string in the reverse paths of the system. However, it
is desirable to maintain continuity between the forward and reverse pathtrace strings. To manage
this, the Pathtrace Process that runs in the RAN CPUs is responsible for reading pathtrace strings
from the RUC MIB, parsing out the Tenant ID sub-strings from the pathtrace strings, and writing
the Tenant IDs into the MIB’s of the RDC’s that are associated with the RUC’s.
The RDC HCP creates up to two new pathtrace strings (primary/diversity(if present)) starting
with the Tenant ID that was provided in its MIB by the Pathtrace Process. The RDC HCP
appends its own CPU IP Address to the pathtrace strings, and then appends the
primary/diversity flags ("P" or "D"). Finally, the RDC transmits the pathtrace strings out on up
to two outputs. The pathtrace strings are then transmitted back to the Hub reverse modules
belonging to this tenant.
6.3.5 Pathtrace Reverse Reception
In the reverse path, the SIF modules in the RAN’s that are connected to the RDC outputs, as well
as the SIF’s in the Hub, pass-through the pathtrace strings from their inputs to their outputs. In
addition, the SIF HCP’s report the passed-through pathtrace strings in the SIF MIB for use by
tenant processing and other higher-level processes.