[NMS-12863] show-event-config displays unexpected content after adding new event definitions - The OpenNMS Issue Tracker

XML

Word

Printable

Details

Type: Bug
Status: Resolved (View Workflow)
Priority: Major
Resolution: Fixed
Affects Version/s: 26.1.3
Fix Version/s: 29.0.7
Component/s: Eventd, Events, OSGi
Security Level: Default (Default Security Scheme)
Labels:
- support

Story Points:
8
Sprint:
Horizon 22 - Feb 2 - Feb 16
HB Backlog Status:
Backlog CM

Description

A customer asked me if there is a way to alter the content of event definitions coming from OIA. In particular, an event defined by ALEC.

That is entirely possible by creating a new event definition with a priority element.

The problem is that after doing that, and instruction OpenNMS to reload the event configuration, the number of events displayed by the show-event-config command is incorrect.

Let me explain with an example:

admin@opennms> opennms:show-event-config -u uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop
Event #1
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>0</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop</event-label>
   <descr>&lt;p>This notification is generated when an IPsec Phase-1
            IKE Tunnel becomes inactive.&lt;/p>&lt;table>
            &lt;tr>&lt;td>&lt;b>
            cikePeerLocalAddr&lt;/b>&lt;/td>&lt;td>%parm[#1]%
            &lt;/td>&lt;td>&lt;p;>&lt;/p>&lt;/td;>&lt;/tr>&lt;tr>&lt;td>&lt;b>
            cikePeerRemoteAddr&lt;/b>&lt;/td>&lt;td>%parm[#2]%
            &lt;/td>&lt;td>&lt;p;>&lt;/p>&lt;/td;>&lt;/tr>&lt;tr>&lt;td>&lt;b>
            cikeTunActiveTime&lt;/b>&lt;/td>&lt;td>%parm[#3]%
            &lt;/td>&lt;td>&lt;p;>&lt;/p>&lt;/td;>&lt;/tr>&lt;/table></descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #2
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>0</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop</event-label>
   <descr>&lt;p>This notification is generated when an IPsec Phase-1
            IKE Tunnel becomes inactive.&lt;/p>&lt;table>
            &lt;tr>&lt;td>&lt;b>
            cikePeerLocalAddr&lt;/b>&lt;/td>&lt;td>%parm[#1]%
            &lt;/td>&lt;td>&lt;p;>&lt;/p>&lt;/td;>&lt;/tr>&lt;tr>&lt;td>&lt;b>
            cikePeerRemoteAddr&lt;/b>&lt;/td>&lt;td>%parm[#2]%
            &lt;/td>&lt;td>&lt;p;>&lt;/p>&lt;/td;>&lt;/tr>&lt;tr>&lt;td>&lt;b>
            cikeTunActiveTime&lt;/b>&lt;/td>&lt;td>%parm[#3]%
            &lt;/td>&lt;td>&lt;p;>&lt;/p>&lt;/td;>&lt;/tr>&lt;/table></descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>

The above is the expected result for that event definition. The first entry is coming from ALEC, as defined in the following link:

https://github.com/OpenNMS/alec/blob/v1.0.2/integrations/opennms/config/src/main/resources/events/Cisco.ext.events.xml#L475

The second one is part of the OpenNMS default configuration (defined inside /opt/opennms/etc/events/Cisco.events.xml).

As expected, event definitions coming via OIA takes more precedence than definitions that OpenNMS provides by default.

This can be altered with the priority field.

I added a new event definitions file with an altered version of the event offered by ALEC:

[root@horizon ~]# cat /opt/opennms/etc/events/ALEC-Altered.events.xml
<events xmlns="http://xmlns.opennms.org/xsd/eventconf">
  <event xmlns="http://xmlns.opennms.org/xsd/eventconf">
    <mask>
      <maskelement>
        <mename>id</mename>
        <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
        <mename>generic</mename>
        <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
        <mename>specific</mename>
        <mevalue>2</mevalue>
      </maskelement>
    </mask>
    <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
    <priority>10</priority>
    <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
    <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
    <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
    <severity>Warning</severity>
    <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
    <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
    <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
    <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
    </alarm-data>
  </event>
</events>

[root@horizon ~]# head -n 12 /opt/opennms/etc/eventconf.xml
<events xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <global>
      <security>
         <doNotOverride>logmsg</doNotOverride>
         <doNotOverride>operaction</doNotOverride>
         <doNotOverride>autoaction</doNotOverride>
         <doNotOverride>tticket</doNotOverride>
         <doNotOverride>script</doNotOverride>
      </security>
   </global>
   <event-file>events/ALEC-Altered.events.xml</event-file>
   <event-file>events/opennms.snmp.trap.translator.events.xml</event-file>

[root@horizon ~]# /opt/opennms/bin/send-event.pl -p 'daemonName Eventd' uei.opennms.org/internal/reloadDaemonConfig

If I run the show-event-config again, I would expect to see three (3) definitions, having the one I added at the top of the list due to its priority. Instead, I'm seeing six (6) copies of the definition I just added, and the ones that were already present are gone.

admin@opennms> opennms:show-event-config -u uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop
Event #1
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #2
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #3
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #4
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #5
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #6
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>

That is definitely not expected.

Interestingly, if I restart OpenNMS, to see if the behavior was due to the reload process, I found that the problem is now worst. It shows ten (10) entries:

admin@opennms> opennms:show-event-config -u uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop
Event #1
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #2
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #3
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #4
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #5
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #6
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #7
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #8
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #9
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>Event #10
<event xmlns="http://xmlns.opennms.org/xsd/eventconf">
   <mask>
      <maskelement>
         <mename>id</mename>
         <mevalue>.1.3.6.1.4.1.9.9.171.2</mevalue>
      </maskelement>
      <maskelement>
         <mename>generic</mename>
         <mevalue>6</mevalue>
      </maskelement>
      <maskelement>
         <mename>specific</mename>
         <mevalue>2</mevalue>
      </maskelement>
   </mask>
   <uei>uei.opennms.org/vendor/Cisco/traps/cikeTunnelStop</uei>
   <priority>10</priority>
   <event-label>CISCO-IPSEC-FLOW-MONITOR-MIB defined trap event: cikeTunnelStop (version 2)</event-label>
   <descr>This notification is generated when an IPsec Phase-1 IKE Tunnel becomes inactive for peer %parm[peerRemoteAddr]%</descr>
   <logmsg dest="logndisplay">Cisco Event: IPSEC Phase-1 IKE Tunnel inactive for peer %parm[peerRemoteAddr]%</logmsg>
   <severity>Warning</severity>
   <parameter name="peerLocalAddr" value="%parm[#1]%" expand="true"/>
   <parameter name="peerRemoteAddr" value="%parm[#2]%" expand="true"/>
   <parameter name="tunnelId" value="%parm[name-#3.-1]%" expand="true"/>
   <alarm-data reduction-key="%uei%:%dpname%:%nodeid%:%parm[peerLocalAddr]%:%parm[peerRemoteAddr]%:%parm[tunnelId]%" alarm-type="1" auto-clean="false">
      <managed-object type="vpn-tunnel"/>
   </alarm-data>
</event>

And, the original definitions are still not displayed.

I don't know if there are repercussions or now because of this. Probably not in terms of behavior, but I'm wondering about the algorithm to find event definitions. That because if this process is repeated for multiple definitions, that will exponentially increase the number of definitions kept in memory and could have side effects on the time invested in processing events before sending them to the Event Bus.

Attachments

Activity

People

Assignee:: Gerald Humphries

Reporter:: Alejandro Galue

Votes:: 0 Vote for this issue

Watchers:: 2 Start watching this issue

Dates

Created:: 20/Aug/20 1:29 PM

Updated:: 14/Feb/22 5:04 PM

Resolved:: 14/Feb/22 3:14 PM

Git Integration

Error rendering 'com.xiplink.jira.git.jira_git_plugin:git-issue-webpanel'. Please contact your Jira administrators.