Tarp Loop Detection Buffer; Table 9-11 Tarp Timers; Table 9-12 Tarp Processing Flow - Cisco ONS 15600 Reference Manual

9.6.5 TARP
•
Provisionable timers, shown in
Table 9-11
Timer
T1
T2
T3
T4
Table 9-12
process.
Table 9-12
Process
Find a NET that
matches a TID
Find a TID that
matches a NET
Send a notification
of TID or protocol
address change

9.6.5.2 TARP Loop Detection Buffer

The TARP loop detection buffer (LDB) can be enabled to prevent duplicate TARP PDUs from entering
the TDC. When a TARP Type 1, 2, or 4 PDU arrives, TARP checks its LDB for a NET address (tar-por)
of the PDU originator match. If no match is found, TARP processes the PDU and assigns a tar-por,
tar-seq (sequence) entry for the PDU to the LDB. If the tar-seq is zero, a timer associated with the LDB
entry is started using the provisionable LDB entry timer on the node view OSI > TARP > Config tab. If
a match exists, the tar-seq is compared to the LDB entry. If the tar-seq is not zero and is less than or equal
to the LDB entry, the PDU is discarded. If the tar-seq is greater than the LDB entry, the PDU is processed
and the tar-seq field in the LDB entry is updated with the new value. The ONS 15600 SDH LDB holds
approximately 500 entries. The LDB is flushed periodically based on the time set in the LDB Flush timer
on the node view OSI > TARP > Config tab.
Cisco ONS 15600 SDH Reference Manual, Release 9.0
9-34
Type— Indicates whether the TARP PDU was created through the TARP propagation process
(dynamic) or manually created (static).
TARP Timers
Description
Waiting for response to TARP Type 1 Request PDU
Waiting for response to TARP Type 2 Request PDU
Waiting for response to address resolution request
Timer starts when T2 expires (used during error recovery)
shows the main TARP processes and the general sequence of events that occurs in each
TARP Processing Flow
General TARP Flow
TARP checks its TDC for a match. If a match is found, TARP returns the
1.
result to the requesting application.
If no match is found, a TARP Type 1 PDU is generated and Timer T1 is
2.
started.
If Timer T1 expires before a match if found, a Type 2 PDU is generated and
3.
Timer T2 is started.
4. If Timer T2 expires before a match is found, Timer T4 is started.
5. If Timer T4 expires before a match is found, a Type 2 PDU is generated and
Timer T2 is started.
A Type 5 PDU is generated. Timer T3 is used. However, if the timer expires, no
error recovery procedure occurs, and a status message is provided to indicate
that the TID cannot be found.
TARP generates a Type 4 PDU in which the tar-ttg field contains the NE's TID
value that existed prior to the change of TID or protocol address. Confirmation
that other NEs successfully received the address change is not sent.
Table 9-11, control TARP processing.
Chapter 9 Management Network Connectivity
Default Range
(seconds) (seconds)
15 0–3600
25 0–3600
40 0–3600
20 0–3600
78-18400-01