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 pac k and ports are
properly installed.
3. A busyout/release of the circuit p ack brings the b oard back into
service.
4. Error type 3999 indicates that the c ircuit pack sent a large numb er
of control channel messages to th e switch within a short period of
time. If error type 3586 is also present, then the c ircuit pack was
taken out-of-service due to hyp eractivity. If error type 3586 is not
present, then the circuit p ack has not been taken out-of-servic e, but
it has generated 50% of the messag es necessary to be consid ered
hyperactive. This may be c ompletely normal during h eavy traffic
periods. However, if this error type is log ged when the circuit p ack
is being lightly used , it may indicate a prob lem with the circuit pac k
or the equipment attached to it.
This condition should cle ar itself within 30 minutes. It is recommended that
the error be allowed to clear itself. If this e rror reoccurs within 15 minutes
of being cleared, replace the circuit p ack. If the same error occurs on a
different circuit pac k, follow normal escalation proced ures.
The circuit pack c an be manually brought bac k into service in the
following ways.
— Busyout and release the circuit pack .
— Busyout, reset and release the circuit pac k.
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 swi tch. 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-affec ting 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