SNMP trap values differ in version 24.3 HF3 compared to previous releases.
SYMPTOMS:
SNMP integration receives unexpected values for specific trap entries
MIB definitions for businessAreas and subsequent entries have shifted
New property lateStartTime appears in trap data
CAUSE: The terma.mib configuration file was updated to include the lateStartTime property. This insertion caused a shift in the index numbers for subsequent alertVarEntry objects.
AAI 24.3 HF3
1.REVIEW MIB CHANGES
The lateStartTime property uses alertVarEntry 26. This shifts subsequent entries by one index number compared to previous versions.
New MIB Definition Structure:
Entry: lateStartTime (New) Index: alertVarEntry 26 Description: "Late start time of the jobstream run"
Entry: businessAreas (Shifted) Index: alertVarEntry 27 (Previously 26) Description: "The list of business areas the jobstream is defined in, comma-separated"
Entry: currentlyRunningJobNames (Shifted) Index: alertVarEntry 28 Description: "List of jobs currently in running status"
Entry: jobStreamAnnotation (Shifted) Index: alertVarEntry 29 Description: "Jobstream annotation"
2. UPDATE SNMP RECEIVER CONFIGURATION
Modify the configuration of your external SNMP trap receiver or monitoring tool to align with these new index values.
Below is the current values as of 24.3 HF3: