Cisco Systems 15454 13.7.5.2 TARP Loop Detection Buffer, 13.7.5.3 Manual TARP Adjacencies

13-39
Cisco ONS 15454 Reference Manual, R7.0
78-17191-01
Chapter 13 Management Network Connectivity
13.7 13.7.5 TARP
13.7.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 Cisco ONS 15454 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.
13.7.5.3 Manual TARP Adjacencies
TARP adjacencies can be manually provisioned in networks where ONS 15454s must communicate
across routers or non-SONET NEs that lack TARP capability. In CTC, manual TARP adjacencies are
provisioned on the node view Provisioning > OSI > TARP > MAT (Manual Area Table) subtab. The
manual adjacency causes a TARP request to hop through the general router or non-SONET NE, as shown
in Figure 13-23.
Table 13-15 TARP Processing Flow
Process General TARP Flow
Find a NET that
matches a TID
1. TARP checks its TDC for a match. If a match is found, TARP returns the
result to the requesting application.
2. If no match is found, a TARP Type 1 PDU is generated and Timer T1 is
started.
3. If Timer T1 expires before a match if found, a Type 2 PDU is generated and
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.
Find a TID that
matches a NET
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.
Send a notification
of TID or protocol
address change
TARP generates a Type 4 PDU in which the tar-ttg field contains the NE 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.