6-12 Feature implementation
555-4001-129 Standard 08.01 November 2000
this state, these messages may be discarded. If this occurs, the IPE sends an
exception report to inform the central controller (CC) through the XPM about
the number of messages that have been lost between the XPM and the IPE and
between the IPE and the P-side of the IPE at a predefined time interval (5
minutes).
The order of the PM logs during an overload cycle is given below.
•
A PM180 log is generated to indicate that the IPE has just entered overload
with the number of lost messages.
•
A PM128 log is generated to indicate the change of IPE state from INSV
to ISTB when an IPE enters overload. This action only applies if the
current state is INSV and if there are no other situations that may affect the
IPE to change from INSV to ISTB.
•
A PM180 log is generated to display the number of lost messages for an
overloaded IPE on a predefined time basis until the number is clear (zero)
within the last period.
•
A PM180 log is generated when the IPE is out of the overload condition.
•
Finally, a PM106 log is generated to indicate the change of IPE state from
(in-service trouble) ISTb to (in-service) InSv when the IPE is out of
overload. This action only applies if the current state is ISTb and if there
are no other situations in the IPE that may keep the IPE to be ISTb.
The following figure shows an example of PM106, PM128, and PM180 logs.
Figure 5 Examples of PM106, PM128, and PM180 logs
Note: The display of the logs shown in Figure 5 is only used to show the
type of information given in the associated logs. The contents or the formats
of the actual logs may vary.
*PM180 MAY 16 09:15:53 5575 TBL PM SW EXCEPTION REPORT
IPE HOST 01 1
IPE enters Overload: C-Side DMSX lost msg: 154
P-Side lost msg: 12 Seq: 1
*PM128 MAY 16 09:13:53 5574 TBL ISTB IPE HOST 01 1
Node : ISTB (PM Overloaded) From InSv
*PM106 MAY 16 09:25:09 5808 RTS IPE HOST 01 1
Node : InSv From ISTb
ISTb Cleared (PM Overloaded)
