From: "Ali, Khurram" <Khurram_Ali@mentor.com>
To: "Yuriy Coureelo" <coureelo@micran.ru>, <ecos-discuss@sources.redhat.com>
Subject: RE: [ECOS] snmpTrapOID
Date: Mon, 06 Jun 2005 15:18:00 -0000 [thread overview]
Message-ID: <32A0F6EE19ECF646A9CF370C3AB15EBE0163D751@SVR-ALH-EXC-02.mgc.mentorg.com> (raw)
SNMP defines many traps.
The value of an SNMP object with sysUpTime as OID specifies the time
since the last reset for the SNMP node.
Likewise, the value of an SNMP object with snmpTrapOID as OID specifies
the trap that the SNMP message is referring to.
Hope this helps.
Khurram
-----Original Message-----
From: ecos-discuss-owner@ecos.sourceware.org
[mailto:ecos-discuss-owner@ecos.sourceware.org] On Behalf Of Yuriy
Coureelo
Sent: Monday, June 06, 2005 7:01 AM
To: ecos-discuss@sources.redhat.com
Subject: [ECOS] snmpTrapOID
Dear Sir!
snmp v2 trap consists of:
sysUpTime // {1.3.6.1.2.1.1.3.0}
snmpTrapOID // {1.3.6.1.6.3.1.1.4.1.0}
varList // optional, I can attach anyone variable or more
I can understand what is sysUpTime - it is a time, in timeticks, from
system power up till sending trap.
But what is snmpTrapOID? I know, it holds some OID, but what is sense
of the thing? What purpose it serves?
Sincerely yours
Yuriy Coureelo
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next reply other threads:[~2005-06-06 15:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-06 15:18 Ali, Khurram [this message]
2005-06-07 2:16 ` Re[2]: " Yuriy Coureelo
-- strict thread matches above, loose matches on Subject: below --
2005-06-06 11:01 Yuriy Coureelo
2005-06-06 11:16 ` Andrew Lunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32A0F6EE19ECF646A9CF370C3AB15EBE0163D751@SVR-ALH-EXC-02.mgc.mentorg.com \
--to=khurram_ali@mentor.com \
--cc=coureelo@micran.ru \
--cc=ecos-discuss@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).