Nortel Networks 3500 User Manual
Operation, administration, and maintenance (OAM) features 2-61
Planning and Ordering Guide—Part 1 of 2 NTRN10AN Rel 12.1 Standard Iss 1 Apr 2004
Path trace is used by an STS path terminating equipment (PTE) to verify its
continuous connection to the intended transmitting STS PTE. Path trace can be
monitored on a DS3 STS-1 path facility. It can also be monitored on an OC-3,
OC-12, or OC-48 STS-1 path facility if the STS is virtual tributary
(VT)-managed. For OPTera Metro 3500 equipped with STX-192 circuit packs
(STS-managed), path trace must be monitored on the path terminating
equipment such as DSM module, DS3, 10/100BT- P2P, 2xGigE/FC-P2P
circuit packs.
continuous connection to the intended transmitting STS PTE. Path trace can be
monitored on a DS3 STS-1 path facility. It can also be monitored on an OC-3,
OC-12, or OC-48 STS-1 path facility if the STS is virtual tributary
(VT)-managed. For OPTera Metro 3500 equipped with STX-192 circuit packs
(STS-managed), path trace must be monitored on the path terminating
equipment such as DSM module, DS3, 10/100BT- P2P, 2xGigE/FC-P2P
circuit packs.
Note 1: The following special characters are not supported:
! ” # $ % ’ () * + - . / < = > @ [ ] ^ _ ‘{|} ~
! ” # $ % ’ () * + - . / < = > @ [ ] ^ _ ‘{|} ~
Note 2: Path trace can be monitored on the 2x100BT-P2P circuit pack
WAN port for STS-1 and STS-3c path facilities.
WAN port for STS-1 and STS-3c path facilities.
Note 3: Path trace can be monitored on the 2xGigE/FC-P2P circuit pack
for STS-1 STS-3c, STS12c and STS-24c path facilities.
for STS-1 STS-3c, STS12c and STS-24c path facilities.
Section trace
Section trace is a user-provisionable message transmitted so that a receiving
terminal in a section can verify its continued connection to the intended
transmitter. Section trace is a user-provisionable message in one of two
formats:
terminal in a section can verify its continued connection to the intended
transmitter. Section trace is a user-provisionable message in one of two
formats:
•
STRING - 15 bytes long printable alphanumeric ASCII string
Note: The following special characters are not supported:
! ” # $ % ’ () * + - . / < = > @ [ ] ^ _ ‘{|} ~
! ” # $ % ’ () * + - . / < = > @ [ ] ^ _ ‘{|} ~
•
NUMERIC - any value from 0 through 255 in decimal integer form
Use either of these formats to verify proper fiber connections or detect
reflections from optical couplers. When the section trace function is not
supported or if no value has been programmed, a numerical value of 01 is
transmitted.
reflections from optical couplers. When the section trace function is not
supported or if no value has been programmed, a numerical value of 01 is
transmitted.
TID address resolution protocol (TARP)
The TID address resolution protocol (TARP) is used by TL1-based network
elements to convert target identifiers (TIDs) into network service access points
(NSAPs). An NSAP is used internally in a SONET communications network
as a means of addressing a network element.
elements to convert target identifiers (TIDs) into network service access points
(NSAPs). An NSAP is used internally in a SONET communications network
as a means of addressing a network element.
TARP is a propagation protocol. TARP uses this propagation method with a
distributed database of learned TID/network entity title (NET) mappings.
TARP allows network elements to translate between TID and NET by
automatically exchanging mapping information with other TL1-based network
elements without the need for craftsperson intervention. No additional address
provisioning is required at the network element to support TARP.
distributed database of learned TID/network entity title (NET) mappings.
TARP allows network elements to translate between TID and NET by
automatically exchanging mapping information with other TL1-based network
elements without the need for craftsperson intervention. No additional address
provisioning is required at the network element to support TARP.