Well, you are correct, though you'll probably have to go search your own
RFC's. The trouble is that new ones keep modifying old ones.
You can verify that sysUpTime is defined as timeticks by just browsing
mib-2 data with the xnmbrowser.
Work down the tree from .iso.dod.internet to mgtmt.mib-2.system.sysUpTime
and click Describe. If you want to look at the MIB, look at
rfc-1213-MIB-II.
As late as RFC 3418 this has not changed. RFC 1905, which first defines
SNMP V2, says that the first two varbinds in an SNMP V2 trap are
sysUpTime and snmpTrapOID.
So the SNMP V2 trap formatting in trapd is expecting timeticks, or x'43'
for sysUpTime and not just an integer, and it is expecting sysUpTime as
the first element, or variable, of the V2 trap. Anything else will
tossed as invalid. X'02' is just any old integer string -- it could
mean anything -- and it cannot substitute for timeticks so far as I know.
We map SNMP V2 traps into an SNMP V1 structure for processing according
to RFC 2089, which defines how a "bilingual" agent (one that speaks both
SNMP V1 and SNMP V2) should handle V2 traps.
If you want to search RFC's, I use http://www.faqs.org/rfcs/index.html
I'd call the vendor if I were you and ask for an explanation.
James Shanks
Level 3 Support for Tivoli NetView for UNIX and NT
Tivoli Software / IBM Software Group
"Treptow, Craig" <Treptow.Craig@principal.com>
03/06/2003 02:45 PM
To: "NetView List (E-mail)" <nv-l@lists.tivoli.com>
cc:
Subject: [nv-l] V2 trap - sysUptime encoding
This isn't really specific to Netview, but I'm struggling to find the
information and hope that some kind soul out there can help me out.
Here is an snmpget output with the -d flag:
received 48 bytes from 162.131.0.25 at square2.net.principal.com:
0: 30 2e 02 01 00 04 08 64 6f 6e 74 77 61 6e 74 a2 0......dontwant.
16: 1f 02 02 46 85 02 01 00 02 01 00 30 13 30 11 06 ...F.......0.0..
32: 08 2b 06 01 02 01 01 03 00 43 05 00 84 32 23 6d .+.......C...2#m
0: SEQUENCE (0x30): 46 bytes
2: INTEGER VERSION (0x2) 1 bytes: 0
5: OCTET STRING COMMUNITY (0x4) 8 bytes: "dontwant"
15: GETRESPONSE-PDU (0xa2): 31 bytes
17: INTEGER REQUEST-ID (0x2) 2 bytes: 18053
21: INTEGER ERROR-STATUS (0x2) 1 bytes: noError(0)
24: INTEGER ERROR-INDEX (0x2) 1 bytes: 0
27: SEQUENCE (0x30): 19 bytes
29: SEQUENCE (0x30): 17 bytes
31: OBJECT ID (0x6) 8 bytes: .1.3.6.1.2.1.1.3.0
41: TIMETICKS (0x43) 5 bytes: 2217878381
system.sysUpTime.0 : Timeticks: (2217878381) 256 days, 16:46:23.81
0x43 seems to indicate it is timeticks and it will be 5 bytes long. We
are having a problem with some devices that are sending v2c traps. They
put 0x02 at that location, and ethereal says it wasn't a timeticks value
that it was expecting. We are theorizing that 0x43 = timeticks and 0x02 =
Signed 32-bit integer.
We'd like to know which RFC these encodings are defined in, so we can find
out what that value means and if the vendor is doing something wrong, of
if Netview is interpreting a valid trap incorrectly. I have been scouring
RFC's, but can't seem to find this detail defined anywhere.
Any help is greatly appreciated.
Thanks!
Craig
A dozen, a gross, and a score,
Plus three times the square root of four,
Divided by seven,
Plus five times eleven,
Equals nine squared plus zero, no more.
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
---------------------------------------------------------------------
To unsubscribe, e-mail: nv-l-unsubscribe@lists.tivoli.com
For additional commands, e-mail: nv-l-help@lists.tivoli.com
*NOTE*
This is not an Offical Tivoli Support forum. If you need immediate
assistance from Tivoli please call the IBM Tivoli Software Group
help line at 1-800-TIVOLI8(848-6548)
|