| Title: | DECmcc user notes file. Does not replace IPMT. |
| Notice: | Use IPMT for problems. Newsletter location in note 6187 |
| Moderator: | TAEC::BEROUD |
| Created: | Mon Aug 21 1989 |
| Last Modified: | Wed Jun 04 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 6497 |
| Total number of notes: | 27359 |
Hello,
I have a FT1.3 customer (Aerospace Corporation) that is experimenting
with TCP/IP traps and is having difficulty getting any of the trap
information into the notification event - in otherwords when the trap
fires they are always getting an "enterprise specific trap" rather then
a notification with the correct priority and text string.
When the trap fires there is a specific priority # that
is relevant to this trap. Additionally in the mib they have specific
text strings associated with the trap (node down etc.) that they would
like DECmcc notification to display. However no matter what they try
they cannot get this information passed through from the trap to the
event notification.
I have included a copy of the mib they are using in the next reply in
hopes that this will help.
Regards,
Peter Lamb
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 4477.1 | Sniffer Mib for Traps | DAGWST::LAMB | Peter Lamb - GSG Santa Clara | Mon Feb 01 1993 12:03 | 160 |
From: DECPA::"director@aero.org" 28-JAN-1993 10:48:06.92
To: mutton::lamb
0CC:
Subj: Sniffer MIB (hopefully)
Peter,
Here's a new attempt at delivering the MIB. The TRAP-TYPE portion of the added (it's what were asking Network General to supply). You can see the
eight fields of info sent to DECmcc, but like I mentioned before displaying
them meanningfully is the trick - Ecspecially the trPriority and trText
fields. As mentioned before we've played some games with the notification
fields to display (hardcoded) priority levels. Let me know if you receive
this MIB and on the progress (I leave for vacation at 3 PM thursday).
Thanks I'll talk to you when I get back.
Rob
NGC DEFINITIONS ::= BEGIN
IMPORTS
Counter,IpAddress
FROM RFC1155-SMI
OBJECT-TYPE
FROM RFC-1212
TRAP-TYPE
FROM RFC-1215
DisplayString
FROM RFC1213-MIB;
-- monitor OBJECT IDENTIFIER ::= { iso org(3) dod(6) internet(1) private(4) enterprises(1) ngc(110) ngcsystems(1) servers(1) monitor(1) }
-- consoles OBJECT IDENTIFIER ::= { iso org(3) dod(6) internet(1) private(4) enterprises(1) ngc(110) ngcsystems(1) consoles(2) }
ngc OBJECT IDENTIFIER ::= { enterprises 110 }
ngcsystems OBJECT IDENTIFIER ::= { ngc 1 }
servers OBJECT IDENTIFIER ::= { ngcsystems 1}
monitor OBJECT IDENTIFIER ::= { servers 1 }
consoles OBJECT IDENTIFIER ::= { ngcsystems 2 }
traps OBJECT IDENTIFIER ::= { monitor 1 }
pcc OBJECT IDENTIFIER ::= { consoles 1 }
-- The traps group
trapsTable OBJECT-TYPE
SYNTAX SEQUENCE OF TrapsEntry
ACCESS not-accessible
STATUS mandatory
::= { traps 1 }
trapsEntry OBJECT-TYPE
SYNTAX TrapsEntry
ACCESS not-accessible
STATUS mandatory
::= { trapsTable 1 }
TrapsEntry ::= SEQUENCE {
trSequence
Counter,
trID
INTEGER,
trText
OCTET STRING,
trPriority
INTEGER,
trClass
INTEGER,
trType
INTEGER,
trTime
Counter,
trSuspect
OCTET STRING
}
trSequence OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
::= { trapsEntry 1 }
trID OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
::= { trapsEntry 2 }
trText OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
::= { trapsEntry 3 }
trPriority OBJECT-TYPE
SYNTAX INTEGER {
None(0),
Inform(1),
Warning(2),
Minor(3),
Major(4),
Critical(5)
}
ACCESS read-only
STATUS mandatory
::= { trapsEntry 4 }
trClass OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
::= { trapsEntry 5 }
trType OBJECT-TYPE
SYNTAX INTEGER
ACCESS read-only
STATUS mandatory
::= { trapsEntry 6 }
trTime OBJECT-TYPE
SYNTAX Counter
ACCESS read-only
STATUS mandatory
::= { trapsEntry 7 }
trSuspect OBJECT-TYPE
SYNTAX OCTET STRING
ACCESS read-only
STATUS mandatory
::= { trapsEntry 8 }
relUsageExceeded TRAP-TYPE
ENTERPRISE ngc
VARIABLES { trSequence, trID, trText, trPriority,
trClass, trType, trTime, trSuspect }
DESCRIPTION
"A usageExceeded trap signifies that the monitor
detected a relative increase in usage higher than
the specified threshhold."
::= 4
absUsageExceeded TRAP-TYPE
ENTERPRISE ngc
VARIABLES { trSequence, trID, trText, trPriority,
trClass, trType, trTime, trSuspect }
DESCRIPTION
"A usageExceeded trap signifies that the monitor
detected an absolute usage higher than the specified
threshold."
::= 7
END
% ====== Internet headers and postmarks (see DECWRL::GATEWAY.DOC) ======
% Received: by mts-gw.pa.dec.com; id AA13950; Thu, 28 Jan 93 10:45:43 -0800
% Received: from antares.aero.org by aerospace.aero.org with SMTP (5.65c/6.0.GT) id AA04790 for lamb@mutton.enet.dec.com; Thu, 28 Jan 1993 10:45:37 -080
% Posted-Date: Thu, 28 Jan 93 10:44:49 -0800
% Message-Id: <199301281845.AA04790@aerospace.aero.org>
% Received: from director (director2.aero.org) by antares.aero.org (4.1/AMS-1.0) id AA05901 for lamb@mutton.enet.dec.com; Thu, 28 Jan 93 10:45:34 PS
% Date: Thu, 28 Jan 93 10:44:49 -0800
% From: director@aero.org
% To: mutton::lamb
% Subject: Sniffer MIB (hopefully)
| |||||
| 4477.2 | MOLAR::YAHEY::BOSE | Mon Feb 01 1993 16:38 | 9 | ||
Can they get the information back through FCL using the getevent directive? Remember that the getevent has to be posted against the mib child entity to get all the vendor specific trap information. MCC> GETEVENT SNMP agent_id NGC ANY CONFIGURATION EVENT ^^^ Rahul. | |||||