All Forums Viewpoint
StevenSchmid 33 posts Joined 07/11
03 Feb 2013
SNMP traps - changing severity of messages

Hi
We have alerts being sent via SNMP traps, however they all appear as NORMAL priority, nothing seems to be sent as CRITICAL for example.  We have run tests were we have brought nodes down, restarted the database, had failed power supplies, but we haven't seen any raised as CRITICAL.  The reason we need the higher levels is that these generate incidents in the system that need to be investigated.
I have checked the Viewpoint Alerting manuals  and there is no mention on how to update the MIB file.  The only files I have found are:
DOHA_DR_VP_1-8:/opt/teradata/cam/alert/config # ls -l
total 24
-rw-r--r-- 1 root root 3149 Aug  3  2011 alertservice-log.config.xml
-rw-r--r-- 1 root root  100 Aug  3  2011 amq.distributed.cluster.properties
-rw-r--r-- 1 root root 1024 Aug  3  2011 amq.local.cluster.properties
-rw-r--r-- 1 root root 1208 Aug  3  2011 cam.properties.template
-rw-r--r-- 1 root root 2546 Aug  3  2011 cluster-protocol-stacks.xml
-rw-r--r-- 1 root root 4025 Aug  3  2011 teradataCamMib.txt
We are running TD 13.10 and Viewpoint 14.00
Can anybody advise how I go about updating the MIB of another file to change alert priorities.
cheers
Steven
 

Steven Schmid Teradata DBA Canberra, Australia
lloftin 3 posts Joined 02/11
04 Feb 2013

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.

 
 

StevenSchmid 33 posts Joined 07/11
13 Feb 2013

Hi
Thanks for replying.
We are sending alerts to HP BSM.
I tried sending a database space alert from Viewpoint, and set the severity as CRITICAL, however BSM reported it as normal.  The alert was also sent as an email, however the email does not display the severity, but with the alert viewer portlet I see that it was issued as a CRITICAL alert.
I would have thought that BSM would just report the severity as advised by the alert.  The BSM team advised that they have 2 mib files for Teradata, teradataCamMib.txt (should be for viewpoint alerts) and smalertingmib.txt (should be fo SWS alerts), I have included these files below.
If I logon to the viewpoint server or sws, I can see that there are many MIB files under /usr/share/snmp/mibs, but not those mentioned above, are there specific mibs that are required by BSM ?
Cheers 
 
teradataCamMib.txt:
--*********************************************************************
-- This MIB defines the Teradata Common Alerting notification (trap).
--*********************************************************************
TERADATA-CAM-MIB DEFINITIONS ::= BEGIN
IMPORTS
    MODULE-IDENTITY,
    NOTIFICATION-TYPE,
    OBJECT-IDENTITY,
    OBJECT-TYPE,
    Integer32,
    enterprises
        FROM SNMPv2-SMI
    DisplayString
        FROM SNMPv2-TC
    OBJECT-GROUP,
    NOTIFICATION-GROUP
        FROM SNMPv2-CONF;
tdcamMIB MODULE-IDENTITY
  LAST-UPDATED "201009010000Z"
  ORGANIZATION "TERADATA CORPORATION"
  CONTACT-INFO "TERADATA CORPORATION Customer Support
   17095 Via Del Campo
   San Diego, CA 92127
   US "
  DESCRIPTION "This MIB module defines a basic notification (trap)
                 provided by the Teradata Common Alerting Mechanism."
  REVISION "201009010000Z"
  DESCRIPTION "Updated for v2 compliance."
  REVISION "200906010000Z"
  DESCRIPTION "Initial."
  ::= { tdcam 100 }

teradata OBJECT-IDENTITY
    STATUS          current
    DESCRIPTION     "Teradata"
    ::= { enterprises 28698 }
td-products OBJECT-IDENTITY
    STATUS          current
    DESCRIPTION     "Subtree for Teradata products"
    ::= { teradata 4}
tdcam OBJECT-IDENTITY
    STATUS          current
    DESCRIPTION    "Root of the Teradata Common Alerting Mechanism subtree."
  ::= { td-products 303 }
tdcamNotifications OBJECT-IDENTITY
    STATUS          current
    DESCRIPTION     "Subtree for notifications"
    ::= { tdcam 0 }
tdcamMibGroup OBJECT-GROUP
    OBJECTS {
        alertId,
        alertName,
        source,
        subcomponent,
        timestamp,
        severity,
        systemName,
        description
        }
    STATUS          current
    DESCRIPTION     "The objects included in a notification."
    ::= { tdcamMIB 1 }
tdcamNotificationGroup NOTIFICATION-GROUP
    NOTIFICATIONS { tdCamAlertTrap }
    STATUS          current
    DESCRIPTION     "The notifications defined in this MIB."
    ::= { tdcamMIB 2 }
tdcamExp OBJECT-IDENTITY
    STATUS          current
    DESCRIPTION     "Subtree for experimental (unsupported) definitions"
    ::= { tdcam 200 }
--******************************************************************************
-- Default trap for common alerting.
--******************************************************************************
tdCamAlertTrap NOTIFICATION-TYPE
  OBJECTS {
   alertId,
   alertName,
   source,
   subcomponent,
   timestamp,
   severity,
   systemName,
   description}
  STATUS current
  DESCRIPTION "Teradata common alert"
  ::= { tdcamNotifications 303 }
alertId  OBJECT-TYPE
  SYNTAX Integer32
  MAX-ACCESS read-only
  STATUS current
  DESCRIPTION "Alert ID"
  ::= { tdCamAlertTrap 1 }
alertName OBJECT-TYPE
  SYNTAX DisplayString
  MAX-ACCESS read-only
  STATUS current
  DESCRIPTION "Source-specified alert or event name"
  ::= { tdCamAlertTrap 2 }
source  OBJECT-TYPE
  SYNTAX DisplayString
  MAX-ACCESS read-only
  STATUS current
  DESCRIPTION "The source of this alert"
  ::= { tdCamAlertTrap 3 }
subcomponent OBJECT-TYPE
  SYNTAX DisplayString
  MAX-ACCESS read-only
  STATUS current
  DESCRIPTION "The source subcomponent"
  ::= { tdCamAlertTrap 4 }
timestamp OBJECT-TYPE
  SYNTAX DisplayString
  MAX-ACCESS read-only
  STATUS current
  DESCRIPTION "Timestamp for this alert"
  ::= { tdCamAlertTrap 5 }
severity OBJECT-TYPE
  SYNTAX DisplayString
  MAX-ACCESS read-only
  STATUS current
  DESCRIPTION "Severity (CRITICAL, HIGH, MEDIUM, LOW)"
  ::= { tdCamAlertTrap 6 }
systemName OBJECT-TYPE
  SYNTAX DisplayString
  MAX-ACCESS read-only
  STATUS current
  DESCRIPTION "System name. TDPID when applicable."
  ::= { tdCamAlertTrap 7 }
description OBJECT-TYPE
  SYNTAX DisplayString
  MAX-ACCESS read-only
  STATUS current
  DESCRIPTION "Alert conditions."
  ::= { tdCamAlertTrap 8 }
END
 
smalertingmib.txt:
TERADATA-SMA-MIB DEFINITIONS ::= BEGIN
IMPORTS
  MODULE-IDENTITY,
  OBJECT-TYPE,
  NOTIFICATION-TYPE,
  Integer32,
  Counter64,
  enterprises FROM SNMPv2-SMI
;
sma MODULE-IDENTITY
  LAST-UPDATED    "201009160950Z"
  ORGANIZATION    "TERADATA CORPORATION"
  CONTACT-INFO    "postal: TERADATA CORPORATION Customer Support
                      17095 Via Del Campo
                      San Diego, CA 92127
                      US "
  DESCRIPTION     "This MIB module defines an alert event
                      for Teradata SM3G SM Alerting."
  REVISION        "201009160950Z"
  DESCRIPTION     "Initial."
  ::= { td-products 301 }
teradata                  OBJECT IDENTIFIER ::= { enterprises 28698 }
td-products               OBJECT IDENTIFIER ::= { teradata 4}
smaNotifications          OBJECT IDENTIFIER ::= { sma 1 }
smaNotificationObjects    OBJECT IDENTIFIER ::= { smaNotifications 1 }
severity          OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "Severity"
                  ::= { smaNotificationObjects 1 }
domain            OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "Domain."
                  ::= { smaNotificationObjects 2 }
managedElementAlias OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "ManagedElementAlias."
                  ::= { smaNotificationObjects 3 }
description       OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "Description."
                  ::= { smaNotificationObjects 4 }
details           OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "Details."
                  ::= { smaNotificationObjects 5 }
iD                OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "GUID."
                  ::= { smaNotificationObjects 6 }
managedElement    OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "ManagedElement."
                  ::= { smaNotificationObjects 7 }
messageID         OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "MessageID."
                  ::= { smaNotificationObjects 8 }
reporterType      OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "ReporterType."
                  ::= { smaNotificationObjects 9 }
sequence          OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "Sequence"
                  ::= { smaNotificationObjects 10 }
requestID         OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "RequestID."
                  ::= { smaNotificationObjects 11 }
subType           OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "SubType."
                  ::= { smaNotificationObjects 12 }
timeStamp         OBJECT-TYPE
                  SYNTAX Counter64
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "TimeStamp."
                  ::= { smaNotificationObjects 13 }
systemID          OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "SystemID."
                  ::= { smaNotificationObjects 14 }
collectiveID      OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "CollectiveID."
                  ::= { smaNotificationObjects 15 }
cabinetID         OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "CabinetID."
                  ::= { smaNotificationObjects 16 }
chassisID         OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "ChassisID."
                  ::= { smaNotificationObjects 17 }
objectClass       OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "ObjectClass."
                  ::= { smaNotificationObjects 18 }
timeReceived      OBJECT-TYPE
                  SYNTAX Counter64
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "TimeReceived."
                  ::= { smaNotificationObjects 19 }
status            OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "Status."
                  ::= { smaNotificationObjects 20 }
tviDisposition    OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "tviDisposition."
                  ::= { smaNotificationObjects 21 }
subsystem         OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "Subsystem."
                  ::= { smaNotificationObjects 22 }
repeatCount       OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "RepeatCount."
                  ::= { smaNotificationObjects 23 }
isInGroup         OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "IsInGroup."
                  ::= { smaNotificationObjects 24 }
repeatStartTime   OBJECT-TYPE
                  SYNTAX Counter64
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "RepeatStartTime."
                  ::= { smaNotificationObjects 25 }
trackingID         OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "TrackingID."
                  ::= { smaNotificationObjects 26 }
knowledgeID       OBJECT-TYPE
                  SYNTAX OCTET STRING
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "KnowledgeID."
                  ::= { smaNotificationObjects 27 }
         
autoSolvable      OBJECT-TYPE
                  SYNTAX Integer32
                  ACCESS read-only
                  STATUS current
                  DESCRIPTION "AutoSolvable."
                  ::= { smaNotificationObjects 28 }
smaAlertTrap      NOTIFICATION-TYPE
                  OBJECTS {
                      severity, domain, managedElementAlias, description,
                      details,iD, managedElement, messageID, reporterType,
                      sequence, requestID, subType, timeStamp, systemID,
                      collectiveID, cabinetID, chassisID, objectClass,
                      timeReceived, status, tviDisposition, subsystem,
                      repeatCount, isInGroup, repeatStartTime, trackingID,
                      knowledgeID, autoSolvable
                  }
                  STATUS    current
                  DESCRIPTION "no description supplied"
                  ::= { smaNotifications 2 }
END
 
 

Steven Schmid
Teradata DBA
Canberra, Australia

Ramubukka 7 posts Joined 01/11
22 Dec 2013

Hi ,
I dont think you need to use HP BSM MIB, we tried with Tivioli SNMP trap , we are able to receive taps and its showing severity also, you might have to do some settings in BSM side.

You must sign in to leave a comment.