From: "Ali, Khurram" <Khurram_Ali@mentor.com>
To: "Yuriy Coureelo" <coureelo@micran.ru>, <ecos-discuss@sources.redhat.com>
Subject: RE: Re[2]: [ECOS] snmpTrapOID
Date: Tue, 07 Jun 2005 14:19:00 -0000 [thread overview]
Message-ID: <32A0F6EE19ECF646A9CF370C3AB15EBE0163D875@SVR-ALH-EXC-02.mgc.mentorg.com> (raw)
I have not really worked with the SNMP implementation that comes with
eCos. But yes, the value in snmpTrapOID is also an OID of the trap being
sent.
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 10:17 PM
To: ecos-discuss@sources.redhat.com
Subject: Re[2]: [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?
> 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
From RFC 1448:
The second variable is snmpTrapOID.0, which contains
the administratively assigned name of the notification.
What does snmpTrapOID->OID should contain? I mean, snmpTrapOID
contains OID, which contains something else.
Should snmpTrapOID point to some variable OID, which is reason of
generating the trap?
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-07 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-07 14:19 Ali, Khurram [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-06-06 15:18 Ali, Khurram
2005-06-07 2:16 ` Re[2]: " Yuriy Coureelo
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=32A0F6EE19ECF646A9CF370C3AB15EBE0163D875@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).