public inbox for ecos-discuss@sourceware.org
 help / color / mirror / Atom feed
* RE: Re[2]: [ECOS] snmpTrapOID
@ 2005-06-07 14:19 Ali, Khurram
  0 siblings, 0 replies; 2+ messages in thread
From: Ali, Khurram @ 2005-06-07 14:19 UTC (permalink / raw)
  To: Yuriy Coureelo, ecos-discuss

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re[2]: [ECOS] snmpTrapOID
  2005-06-06 15:18 Ali, Khurram
@ 2005-06-07  2:16 ` Yuriy Coureelo
  0 siblings, 0 replies; 2+ messages in thread
From: Yuriy Coureelo @ 2005-06-07  2:16 UTC (permalink / raw)
  To: ecos-discuss

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

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2005-06-07 14:19 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-06-07 14:19 Re[2]: [ECOS] snmpTrapOID Ali, Khurram
  -- 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

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).