Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

What MIB Module does the Smarts Trap Notifier use? (319577)

Last Updated: 3/22/2024Categories: How toTotal Views: 2364Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Resolution

What MIB Module does the Smarts Trap Notifier use?

What does the trap generated by the Smarts Trap Notifier look like

SMARTS-MIB.my:  Smarts corporate MIB
Copyright (C) 1999-2005 by System Management ARTS, Inc.

All Rights Reserved

RCS $Id: SMARTS-MIB.my,v 1.1.78.1 2005/08/23 18:00:29 ku1 Exp $

SMARTS-MIB DEFINITIONS ::= BEGIN

IMPORTS
enterprises, Counter32, OBJECT-TYPE,
MODULE-IDENTITY, OBJECT-IDENTITY, NOTIFICATION-TYPE
FROM SNMPv2-SMI;

smartsMIB MODULE-IDENTITY
LAST-UPDATED "9909232300Z"
ORGANIZATION "System Management ARTS"
CONTACT-INFO
"       Support
Postal: System Management ARTS
14 Mamaroneck Avenue
White Plains, NY 10601
US
Phone: +1 914 948 6200
Fax: +1 914 948 6270
E-mail: [email-masked]"
DESCRIPTION
"The MIB module for entities defined by
System Management ARTS, Inc."
::= { enterprises 733 }

top level groups in the SMARTS-MIB

The smNotificationTrap Group.

smNotificationTrap OBJECT-IDENTITY
STATUS  current
DESCRIPTION
"This group is acutally the prefix one uses when creating
enterprise-specific trap OID's for an SNMPv2 trap.  It is
used in the Smarts MIBS when defining traps."
::= { smartsMIB 0 }

The smNotificationData Group.

smNotificationData OBJECT-IDENTITY
STATUS  current
DESCRIPTION
"The members of this group are the OIDs for VarBinds
containing notification data."
::= { smartsMIB 2 }

Group for generic notification data.

smGenericNotify OBJECT-IDENTITY
STATUS  current
DESCRIPTION
"The members of this group are the OIDs for VarBinds
containing generic notification data."
::= { smNotificationData 1 }

smNotifTimestamp OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS accessible-for-notify
STATUS  current
DESCRIPTION
"The timestamp of the notification."
::= { smGenericNotify 1 }

smNotifServer OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The name of the server that is sending the notification."
::= { smGenericNotify 2 }

smNotifClass OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The class of the object associated with the notification."
::= { smGenericNotify 3 }

smNotifInstance OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The instance name of the object associated with the notification."
::= { smGenericNotify 4 }

smNotifEventName OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The name of the event causing the notification."
::= { smGenericNotify 5 }

smNotifInstanceID OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The unique InCharge inventory identification
for the object associated with the notification."
::= { smGenericNotify 6 }

smNotifDescription OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"A complete description of the event."
::= { smGenericNotify 7 }

smNotifCertainty OBJECT-TYPE
SYNTAX OCTET STRING
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The certainty of the event.  Floating-point number in the
range 0-100, stored as a string."
::= { smGenericNotify 8 }

smNotifSeverity OBJECT-TYPE
SYNTAX INTEGER {
notApplicable (1),
informational (2),
warning (3),
minor (4),
major (5),
severe (6)
}
MAX-ACCESS accessible-for-notify
STATUS  current
DESCRIPTION
"The severity of the event.  Integer number in the range 1-6."
::= { smGenericNotify 9 }

The Smarts enterprise Traps

These are the enterprise-specific trap codes currently in-use in
SMARTS software.  The final sub-OID of each object is the code sent
in the "specific-trap" field of an SNMPv1 Trap-PDU.

The definition of these objects mimics the SNMPv2 convention for
sending traps:  Take the enterprise OID, append 0, then append the
trap code.

TRAP NUMBER USE: Trap code 0 is reserved (by SNMP).
Trap codes 1-3 are used by the SMARTS-OV-NV-MIB.

TRAPS 4-7: The "smTrap*" series of traps define "base" trap
numbers, ones with a generic purpose.  These traps are
also used by the generic Trap Adapter.

smTrapNotification NOTIFICATION-TYPE
OBJECTS {   smNotifTimestamp,
smNotifServer,
smNotifClass,
smNotifInstance,
smNotifEventName,
smNotifInstanceID,
smNotifDescription,
smNotifCertainty,
smNotifSeverity
}
STATUS current
DESCRIPTION
"A trap describing an InCharge root cause notification.
The text in smNotifDescription indicates the nature of
the problem."
::= { smNotificationTrap 4 }

smTrapCertaintyChange NOTIFICATION-TYPE
OBJECTS {   smNotifTimestamp,
smNotifServer,
smNotifClass,
smNotifInstance,
smNotifEventName,
smNotifInstanceID,
smNotifDescription,
smNotifCertainty,
smNotifSeverity
}
STATUS current
DESCRIPTION
"A trap indicating a certainty change of an InCharge
notification. The text in smNotifDescription indicates
the nature of the problem."
::= { smNotificationTrap 5 }

smTrapSeverityChange NOTIFICATION-TYPE
OBJECTS {   smNotifTimestamp,
smNotifServer,
smNotifClass,
smNotifInstance,
smNotifEventName,
smNotifInstanceID,
smNotifDescription,
smNotifCertainty,
smNotifSeverity
}
STATUS current
DESCRIPTION
"A trap indicating a severity change of an InCharge
notification. The text in smNotifDescription indicates
the nature of the notification."
::= { smNotificationTrap 6 }

smTrapNotificationClear NOTIFICATION-TYPE
OBJECTS {   smNotifTimestamp,
smNotifServer,
smNotifClass,
smNotifInstance,
smNotifEventName,
smNotifInstanceID,
smNotifDescription,
smNotifCertainty,
smNotifSeverity
}
STATUS current
DESCRIPTION
"A trap indicating the clear of an InCharge notification."
::= { smNotificationTrap 7 }

smTrapNotificationChange NOTIFICATION-TYPE
OBJECTS {   smNotifTimestamp,
smNotifServer,
smNotifClass,
smNotifInstance,
smNotifEventName,
smNotifInstanceID,
smNotifDescription,
smNotifCertainty,
smNotifSeverity
}
STATUS current
DESCRIPTION
"A trap indicating the change of an InCharge notification."
::= { smNotificationTrap 98 }

smTrapNotificationDelete NOTIFICATION-TYPE
OBJECTS {   smNotifTimestamp,
smNotifServer,
smNotifClass,
smNotifInstance,
smNotifEventName,
smNotifInstanceID,
smNotifDescription,
smNotifCertainty,
smNotifSeverity
}
STATUS current
DESCRIPTION
"A trap indicating the delete of an InCharge notification."
::= { smNotificationTrap 99 }

TRAP NUMBER USE: Trap codes 8-99 are reserved for future "base trap number"
use.

Trap codes 100-133 are used by SMARTS-PERFORMANCE-MIB.
Trap codes 134-199 are reserved for future use by
SMARTS-PERFORMANCE-MIB.

END

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware Smart Assurance - SMARTS

Take Our Survey

Support Assistant