AESV-LNK error log entries and recommended actions

Last Updated : Jul 09, 2015 |
AESV-LNK Error Log Entries
Error Type
Aux Data
Associated Test
Alarm Level
On/Off Board
Command to resolve the error
513a
WRN
Off
none
769 b
AESVCS Link Heartbeat Test (#1624)
Log only
test aesvcs link link#
1537 c
Any
Log only
2561 d
Log only
Note:
  1. a Error Type 513: is displayed when an AESVCS Link is hyperactive. The hyperactivity might be caused by fluctuations in the engineered traffic load being generated by the AESVCS Server. Both an AESVCS Session level and Link level alarm are generated to indicate that a link is overloaded.
    Once the problem has been resolved, it might take up to 45 minutes for the alarm to clear. If the hyperactivity persists, escalate the problem.
  2. b Error type 769: is a log only error and is displayed when Communication Manager does not receive a response from the AESVCS Server to a heartbeat message that was sent over the AESVCS Link. Failure to receive a response to a heartbeat message results in the deletion of the AESVCS Link by Communication Manager. Both an AESVCS Session Level and Link level error are generated against this condition. Escalate if the error persists.
  3. c Error type 1537: is a log only error and displayed when an AESVCS Link is deleted from an AESVCS Session for reasons other than a heartbeat failure. Both an AESVCS Session Level and Link level error are generated against this condition. The Aux Data field contains the reason code.
    Aux Data
    Description
    1
    The far end closed the socket connection. Check the error logs on the AEVCS Server for more information.
    100
    The reset aecvcs-link command was used to close the socket connection
    101
    The AESVCS Interface on the IP Services form was disabled.
    102
    The AESVCS Interface was removed from the IP Services form.
    103
    The AE Services Server was disabled on the AE Services Administration page of the IP Services form.
    104
    The AE Services Server was deleted on the AE Services Administration page of the IP Services form.
    200
    The socket connection closed due to an internal error. Escalate if the problem persists.
    201
    The socket connection was unexpectedly closed by Communication Manager. Escalate if the problem persists.
    202
    Communication Manager detected an error and closed the socket connection. Escalate if the problem persists.
    203
    Communication Manager detected an error reading from the socket and closed the connection. Escalate if the problem persists.
    204
    Communication Manager failed to write a complete message and closed the socket connection. Escalate if the problem persists.
    205
    AE Server established a new connection causing Communication Manager to close the existing one. Escalate if the problem persists.
    206
    Communication Manager failed to send a heartbeat request and closed the socket connection. Escalate if the problem persists.
    207
    Communication Manager detected a protocol violation and closed the socket connection. Escalate if the problem persists.
    208
    Communication Manager detected processing the data from the AESVCS Server and closed the socket connection. Escalate if the problem persists.
    209
    Communication Manager could not read data from the socket and closed the connection. Escalate if the problem persists.
  4. d Error Type 2561 is a log only error and is displayed when an AESVCS message is discarded due to a link buffer overflow. Both an AESVCS Session Level and Link level error is generated against this condition. Escalate if the problem persists.