The Teradata Alerts (CAM) SNMP notification does not have a field called priority in the MIB definition, nor anything we label as NORMAL, so I am suspecting these attributes are specific to your management application. What application are you sending the traps to? Is the priority defined by the application receiving the SNMP trap notification? Is there a way to assign the priority based on fields in the arriving trap - some type of custom rule you can create in the application?
If you are defining the alerts using the Teradata Systems portlet, when you define the alert conditions, the severity of the alert is specified at that time and that is what is sent in the SNMP notification. The MIB has a field called severity which will contain the alert severity. Here are two traps I received using snmptrapd. The first one is LOW, the second one is HIGH.
kobol.td.teradata.com [UDP: [153.64.107.96]:58412]: Trap , SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (1937044299) 224 days, 4:40:42.99, SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: TERADATA-CAM-MIB::tdCamAlertTrap, TERADATA-CAM-MIB::alertId.0 = INTEGER: 9, TERADATA-CAM-MIB::alertName.0 = STRING: sys-snmp-low, TERADATA-CAM-MIB::source.0 = STRING: Viewpoint, TERADATA-CAM-MIB::subcomponent.0 = STRING: , TERADATA-CAM-MIB::timestamp.0 = STRING: 2013-02-04T10:06:21.227-08:00, TERADATA-CAM-MIB::severity.0 = STRING: LOW, TERADATA-CAM-MIB::systemName.0 = STRING: camtest, TERADATA-CAM-MIB::details.0 = STRING: (Average Node Disk Usage > 10.0),
kobol.td.teradata.com [UDP: [153.64.107.96]:58412]: Trap , SNMPv2-SMI::mib-2.1.3.0 = Timeticks: (1937044299) 224 days, 4:40:42.99, SNMPv2-SMI::snmpModules.1.1.4.1.0 = OID: TERADATA-CAM-MIB::tdCamAlertTrap, TERADATA-CAM-MIB::alertId.0 = INTEGER: 11, TERADATA-CAM-MIB::alertName.0 = STRING: sys-snmp-high, TERADATA-CAM-MIB::source.0 = STRING: Viewpoint, TERADATA-CAM-MIB::subcomponent.0 = STRING: , TERADATA-CAM-MIB::timestamp.0 = STRING: 2013-02-04T10:06:21.227-08:00, TERADATA-CAM-MIB::severity.0 = STRING: HIGH, TERADATA-CAM-MIB::systemName.0 = STRING: camtest, TERADATA-CAM-MIB::details.0 = STRING: (Average Node Disk Usage > 10.0),
If the alerts being defined are from the Server Management portlet, the severity field is automatically mapped based on the server management severity attribute in the alert which ranges from 0-6. 0-2 are LOW, 3 is MED, 4 is HIGH, 5-6 are CRITICAL. But again, the data is in the severity attribute defined in the MIB and will vary based on the severity of the alert at runtime.
↧