DUP Event ID 2

Last Updated : Oct 07, 2020 |
Alarm level

MAJ

Alarm text

Duplication link down

Cause

One Duplication Manager server cannot communicate with the other Duplication Manager server.

Proposed Solution 1

Procedure

  1. Access the trace log:
    1. Select the View System Logs diagnostic and Logmanager Debug trace.
    2. Specify the Event Range for the appropriate time frame.
    3. Match the “ndm” or DUPLICATION pattern.
  2. Examine the output of the trace-log query for one of the following messages:
  3. “mainlp: get_addrs returned ***. Could not get IP address for other server.Verify name and address in servers.conf. ndm exiting.” “san_check_msg() sync_msg failed: DUPLINK DOWN.”
  4. Check if the dup link status is “up” from the Server section of the Web interface by selecting Status Summary.
  5. If the dup link status is up, manually clear the alarm by selecting Current Alarms and the appropriate alarm, and click Clear.
  6. If the dup link status does not show up, check the Ethernet interface of the duplication interface by selecting the Execute Ping diagnostic.
  7. If pingall passes, check the applications of the other server by selecting View Process Status.

Proposed Solution 2

Procedure

  1. Access the trace log by entering logv -t ts.
  2. Examine the output of trace-log query for one of the following messages:

    “mainlp: get_addrs returned ***. Could not get IP address for other server.Verify name and address in servers.conf. ndm exiting.” “san_check_msg() sync_msg failed: DUPLINK DOWN.”

  3. Enter server and check if the dup link is up.
  4. If the dup link status shows up, manually clear the alarm by entering almclear -n #id.
  5. If the dup link status does not show up, check the Ethernet connectivity of the duplication interface by entering pingall -d.
  6. If pingall passes, enter statapp and check the applications of the other server.