Specifications

48 HW-MTP2 Level 2 - Level 3 Interfaces and Message Flows HighWire MTP-2 - 1.2, September 4, 2002
5-3-5. MTP3 Data Part failure
Figure 5-8 Message flows involved when the data part of MTP3 fails and is immediately
replaced.
When L2 is informed of the failure of the MTP3 Data Part, it behaves as if it
had received a Local Processor Outage signal from MTP3.
1. When L2 is informed of the replacement MTP3 Data Part, it sends a
CBI_M2_REGISTER to L3 to register with the new MTP3 data process.
2. L3 returns the signal as a response indicating whether the registration
was successful. If the registration was successful, further messages can
flow on the data interface in both directions.
3. L3 sends a CBI_M2_LOC_PROCSSR_RECOVRD to L2 to fully activate the
link again.
5-3-6. MTP3 Data Part
unavailability
Figure 5-9 Message flows involved when the data part of MTP3 fails and is not immedi-
ately replaced.
1. L2 sends a CBI_M2_UNAVAILABLE to notify L3 that the join to the L2-L3
data interface has permanently failed.
2. When L3 receives this signal, it issues a CBI_M2_UNREGISTER to
dissociate the L3 from the L2. L2 returns the signal as a response.