Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-2054008.1
Update Date:2018-04-25
Keywords:

Solution Type  Problem Resolution Sure

Solution  2054008.1 :   MaxRep: Multiple Events PCP_EVT_REPL_SENTINEL_NODEDOWN are Reported in the Axiom 600 Events  


Related Items
  • Pillar Axiom Replication Engine (MaxRep)
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>Axiom>SN-DK: MaxRep-2x
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-11021807881>

Applies to:

Pillar Axiom Replication Engine (MaxRep) - Version 2.0 to 2.0 [Release 2.0]
Information in this document applies to any platform.

Symptoms

The Axiom is sending multiple Call-Homes for the following event:  PCP_EVT_REPL_SENTINEL_NODEDOWN

 

This issue does not apply to MaxRep R3

Cause

The MaxRep Engine sends alerts to the Axiom using SNMP (Simple Network Management Protocol). Depending on the trap (alert), the Axiom will start a log collection that would include the MaxRep logs and send it to the Call-Home server. The log bundle is processed by the ASR portal (Automated Service Request) that can create a new Service Request or add a note to an existing Service Request.

This issue is caused by the length of the trap exceeding 1024 characters that has been defined in the MIB file (Management Information Base).

Solution

Please open a Service Request if the ASR feature is not enabled on the Axiom.
Quote this knowledge article (Document 2054008.1 MaxRep: Multiple Events PCP_EVT_REPL_SENTINEL_NODEDOWN are reported in the Axiom 600 events) to the Support representative to modify the MIB file and restart the SNMP daemon (no impact on the Protection Plans).

To verify that the customer is experiencing this issue, open the following file on the MaxRep Engine or within the log bundle:  /home/svsystems/var/tman_monitor_alerts.log

Look for the following pattern:

2015-07-13 11:00:00 EXCEPTION : MONITOR_ALERTS : Error sending trap:  at /home/svsystems/pm/TimeShotManager.pm line 4907
Abhai-1-MIB-V1::trapAgentErrorMessage: Value out of range (Bad string length :: {(1..1024)})
2015-07-13 11:00:00 EXCEPTION : MONITOR_ALERTS : Error sending trap:  at /home/svsystems/pm/TimeShotManager.pm line 4907
Abhai-1-MIB-V1::trapAgentErrorMessage: Value out of range (Bad string length :: {(1..1024)})
2015-07-13 11:00:00 EXCEPTION : MONITOR_ALERTS : Error sending trap:  at /home/svsystems/pm/TimeShotManager.pm line 4907
Abhai-1-MIB-V1::trapAgentErrorMessage: Value out of range (Bad string length :: {(1..1024)})

It means that the string length used by the trap error message is exceeding the defined length.

The workaround is to increase the message string length in the SNMP MIB file:

  • Open the following file with vi: /usr/share/snmp/mibs/Abhai-1-MIB-V1.mib
  • Look for the following lines:
trapAgentErrorMessage OBJECT-TYPE
SYNTAX    OCTET STRING (SIZE (1..1024))
  • Replace 1024 with 65535:
SYNTAX    OCTET STRING (SIZE (1..65535))  
  • Restart the snmpd daemon:
[root@MAXREP ~]# service snmpd restart

 

References

<BUG:21439644> - RECEIVING SENTINEL NODE DOWN INDICATIONS

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback