ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Traps sent to netcool are not in the same order as defined in the MIB

book

Article ID: 32539

calendar_today

Updated On:

Products

CA Infrastructure Management CA Infrastructure Management CA Performance Management - Usage and Administration

Issue/Introduction

Issue:

Event Manager Notification traps are not sent in the format specified by the variables clause in the netqos-em-mib.

 

Environment:

2.3.3 and 2.3.4

 

Cause:

defect

 

Resolution:

.As of the 2.3.4 October update you will need to modify the /opt/CA/PerformanceCenter/EM/webapps/EventManager/WEB-INF/em.properties file on CAPC.  The property “em.notification.trap.eventmanager_trap_use_new_format” needs to be set to true and Event Manager restarted with the following command:

 

  1. /etc/init.d/caperfcenter_eventmanager stop
  2. /etc/init.d/caperfcenter_eventmanager start

 

This will allow traps to be received in a more netcool compatible format

Here is the setting in the /opt/CA/PerformanceCenter/EM/webapps/EventManager/WEB-INF/em.properties file:

 

# Whether we will send NetQOS (Event Manager) traps using the existing format, or the format that matches the variables clause in the MIB

 

# Setting this value to false will use the existing format, true will use new format that matches the variables clause in the MIB

em.notification.trap.eventmanager_trap_use_new_format=false

 

 

 

Environment

Release: IMDAGG99000-2.5-Infrastructure Management-Data Aggregator
Component:
Powered by Wolken Software