Analyze General Message Transport (GMT) Error Reports
....................................................................................................................................................................................................................................
Purpose
This procedure addresses failure reports of internal message transport
that is detected by recovery software. Autonomous reports provide
enough information to identify the GSM/NGSM combinations with
GMT problems or possibly GQPH QPipes or GQPH Links
(GQPHLNKs) causing these problems.
Note:Analyze General Message Transport (GMT) Error Reports does
not apply to DRM/VCDX.
When to use
Procedural steps point to appropriate problem clearing based on GMT
mechanism/error type identified. When multiple reports are generated,
indicating different levels of GMT disruptions have occurred,
resolution of the problems should follow the severity order.
Related information
Refer to the Input Messages Manual, 235-600-700, and the Output
Messages Manual, 235-600-750, for additional information.
Admonishments
These autonomous messages indicate that a GMT problem has
occurred some time in the past, so the problems may have already
been addressed by automatic recovery strategies, or some of the
dependent hardware resources may have been recovered or repaired
independently before intervention. Reports may also be a result of
valid maintenance personnel actions, even though signaling operation
is severely impacted.
Before you begin
Required Tools
• Use of the Master Control Center (MCC) or Supplementary
Trunk Line Workstation (STLWS).
Required Material
• The switch must be running a 5E16.2 FR3 software release or
later with the SIP for Packet Trunking feature software.
Required Information
• None.
Required Conditions
• None required.
Maintenance Considerations
....................................................................................................................................................................................................................................
235-200-118
Issue 3.02B, March 2007
Lucent Technologies
7-59