DEFINITY Enterprise Communications Server Release 7
Maintenance for R7r
555-230-126
Issue 4
June 1999
Maintenance Object Repair Procedures
9-1199PGATE-BD (Packet Gateway Circuit Pack)
9
2.
List configuration
shows that the circuit pack and ports are
properly installed.
3. A busyout/release of the circuit pack brings the board back into
service.
4. Error type 3999 indicates that the circuit pack sent a large number
of control channel messages to the switch within a short period of
time. If error type 3586 is also present, then the circuit pack was
taken out-of-service due to hyperactivity. If error type 3586 is not
present, then the circuit pack has not been taken out-of-service, but
it has generated 50% of the messages necessary to be considered
hyperactive. This may be completely normal during heavy traffic
periods. However, if this error type is logged when the circuit pack
is being lightly used, it may indicate a problem with the circuit pack
or the equipment attached to it.
This condition should clear itself within 30 minutes. It is recommended that
the error be allowed to clear itself. If this error reoccurs within 15 minutes
of being cleared, replace the circuit pack. If the same error occurs on a
different circuit pack, follow normal escalation procedures.
The circuit pack can be manually brought back into service in the
following ways.
— Busyout and release the circuit pack.
— Busyout, reset and release the circuit pack.
q. These errors are not service-affecting and can be ignored.
These errors are reported by the circuit pack when it receives a bad
control channel message from the switch. The auxiliary data identifies the
following error events:
r. By themselves, these errors are not service-affecting and can be ignored.
They may cause other errors which are service-affecting to be reported.
The error type indicates the following:
4096: Bad major heading
4097: Bad port number
4098: Bad data
4099: Bad sub-qualifier
4100: State inconsistency
3841: Internal firmware error
3843: Bad translation RAM detected, but call continues by using
another translation location
