Table 13-13 Tarp Pdu Types; Table 13-14 Tarp Timers; Tarp - Cisco ONS 15454 Reference Manual

13.7 13.7.5 TARP

Table 13-13
Type
3
4
5
13.7.5.1 TARP Processing
A TARP data cache (TDC) is created at each NE to facilitate TARP processing. In CTC, the TDC is
displayed and managed on the node view Maintenance > OSI > TDC subtab. The TDC subtab contains
the following TARP PDU fields:
•
•
•
Provisionable timers, shown in
Table 13-14
Timer
T1
T2
T3
T4
Table 13-15
process.
Cisco ONS 15454 Reference Manual, R7.0.1
13-40
TARP PDU Types (continued)
Description
Sent as a response to Type 1, Type 2, or
Type 5 PDUs.
Sent as a notification when a change
occurs locally, for example, a TID or
NSAP change. It might also be sent
when an NE initializes.
Sent when a device needs a TID that
corresponds to a specific NSAP.
TID—TID of the originating NE (tar-tor).
NSAP—NSAP of the originating NE.
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
Actions
After a TARP Request (Type 1 or 2) PDU is received,
a TARP Type 3 PDU is sent to the request originator.
Type 3 PDUs do not use the TARP propagation
procedures.
A Type 4 PDU is a notification of a TID or Protocol
Address change at the NE that originates the
notification. The PDU is sent to all adjacencies inside
and outside the NE's routing area.
When a Type 5 PDU is sent, the CLNP destination
address is known, so the PDU is sent to only that
address. Type 5 PDUs do not use the TARP
propagation procedures.
Table 13-14, control TARP processing.
Chapter 13 Management Network Connectivity
Default Range
(seconds) (seconds)
15 0–3600
25 0–3600
40 0–3600
20 0–3600
OL-9217-01