Avaya DEFINITY Server CSI Maintenance Manual page 1486

Maintenance Objects
h. PBX buffer overflows due to either heavy call traffic or PMS protocol
message rate being faster than the PMS/PBX protocol specifications allow.
The PMS Link is torn down. PMS Link maintenance software waits for five
minutes before attempting to set up the link again. If this error type recurs
frequently (that is, more than once a month), advise the customer to call
the vendor of the PMS to check out the PMS device. Once the PMS Link is
successfully established, this error disappears from the Hardware Error
Log (see Note).
i. The attempt to swap the database between PBX and PMS failed 3 times
consecutively due to excessive PMS/PBX protocol violations, buffer
overflows, or PMS Link outages. The PMS Link is NOT torn down. If this
error type recurs frequently (that is, more than once a month), then advise
the customer to call the vendor of the PMS to check out the PMS device.
Once the PMS Link is successfully established, this error disappears from
the Hardware Error Log. No alarm is raised against this error.
j. The PMS Link has been busied out for system technician-demanded
maintenance via the busyout pms-link command or has been brought
down via the test pms-link long command. The PMS Link is torn down,
and PMS Link maintenance stops attempting to reestablish the link in the
case where the busyout pms-link command has been used. When the
test pms-link long command has been used, PMS Link maintenance
continues to try to reset the link. To restore the PMS Link after use of the
busyout pms-link command, issue the release pms-link command. To
restore the PMS Link after use of the test pms-link long command, issue
the test pms-link command.
k. The PMS Link is physically established, but the protocol has not been
started by the PMS before the protocol timer expires. The PMS Link is NOT
torn down. If this error type recurs frequently (that is, more than once a
month), advise the customer to call the vendor of the PMS to check out the
PMS device. Once the PMS Link is successfully established, this error
disappears from the Hardware Error Log.
1486
Issue 5 October 2002
NOTE:
The PMS should be checked for adherence to message rate defined
in the PMS/PBX protocol specifications. No alarm is raised against
this error.
NOTE:
The PMS should be checked to make sure that it attempts to start the
protocol according to the PMS/PBX protocol specifications. No alarm
is raised against this error.