The trap "aggregateStateTrap" is not mapped correctly in CA Spectrum
Article ID: 48839
Updated On:
Products
Issue/Introduction
The trap "aggregateStateTrap" is not mapped correctly in CA Spectrum
Environment
Release: Any
Component:
Cause
The aggregateStateTrap is mapped in the $SPECROOT//SS/CsVendor/Ctron_Gen_HOST/AlertMap file as follows:
# aggregateStateTrap aggIndex
1.3.6.1.4.1.546.1.1.0.20 0x1169b39 1.3.6.1.4.1.546.17.1.1.1(1,0)\
# aggObjClass
1.3.6.1.4.1.546.17.1.1.2(2,0)\
# aggObjInstance
1.3.6.1.4.1.546.17.1.1.3(3,0)\
# aggObjAttribute
1.3.6.1.4.1.546.17.1.1.4(4,0)\
# aggCurrState
1.3.6.1.4.1.546.17.1.1.6(5,0)\
# aggPrevState
1.3.6.1.4.1.546.17.1.1.7(6,0)\
# aggMonTable
1.3.6.1.4.1.546.17.1.1.15(7,0)\
# aggMonIndex
1.3.6.1.4.1.546.17.1.1.16(8,0)\
# aggMonCurrVal
1.3.6.1.4.1.546.17.1.1.17(9,0)\
# aggMonOperator
1.3.6.1.4.1.546.17.1.1.18(10,0)\
# aggMonValue
1.3.6.1.4.1.546.17.1.1.19(11,0)
The 0x1169b39 event is defined in the $SPECROOT//SS/CsVendor/Ctron_Gen_HOST/EventDisp file as follows:
0x1169b39
As you can see from the above configuration in the EventDisp file for the 0x1169b39 event, this event is not logged and is not configured to assert an alarm.
Resolution
This is by design.
Event 0x01169b39 is a dummy event (not logged). Internal code registers an event handler for this event.
Spectrum examines some variables in this event and generates either 0x06210046 or 0x01169b18 events.
If the event is cluster specific, 0x06210046 is generated otherwise 0x01169b18 is generated.
Please check for these events which should be logged and customize alarm creation as needed.
Feedback
