| Title: | DEChub/HUBwatch/PROBEwatch CONFERENCE |
| Notice: | Firmware -2, Doc -3, Power -4, HW kits -5, firm load -6&7 |
| Moderator: | NETCAD::COLELLA DT |
| Created: | Wed Nov 13 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 4455 |
| Total number of notes: | 16761 |
One of our customer's is reporting the following problem with the
Sysuptime counter. Is this problem known? Is there a fix?
-------------------------------------------------------------- Rick -
this is a trace from the sniffer showing the requests and answers from
the gigaswitch when I double click on the SCP module. THe important
point is the response to the SYSUPTIME request (packet #2). In the
decoded portion the uptime is reported as 0092 hundredths of a second
but in the hex dump the corresponding location is 00A2 (third byte in
the 00A0 row) which has the value: 43 05 00 92 E8 44 FB. The 43
indicates a time value, 05 indicates 5 data bytes so the total hex time
in hundredths of seconds is 0092E844FB. However according to the SNMP
MIB the time value is always 4 bytes long this creates a problem for
any software that tries to decode the time. Specifically HUBWATCH
returns with a SYSTEM or GENERAL ERROR. This 5 byte value is returned
by any bridge (including the gigaswitches) that has the high order bit
set (corresponding time is 248.55 days). Because the HUBWATCH software
tries to read the time whenever the management screen is entered I
cannot control the devices. If you can find out if there is a fix for
this I would appreciate it. We are running the latest versions of
firmware on the gigaswitch and V1.5.0 on the bridges.
Thanks - Art
Sniffer Network Analyzer data from 26-Feb-96 at 11:26:20, unsaved
capture data, Page 1
- - - - - - - - - - - - - - - - Frame 1 - - - - - - - - - - - - - - - -
-
SUMMARY Abs Time Delta T Destination Source Summary
M 1 11:26:28.8786 [142.153.24.29] [142.153.144... SNMP
GetNext DEC.2.15.3.3.3.1.4.2 .. DEC.2.15.3.3.3.1.2.7 (15 items)
SNMP: ----- Simple Network Management Protocol (Version 1) -----
SNMP:
SNMP: Version = 0
SNMP: Community = torch
SNMP: Command = Get next request
SNMP: Request ID = 825379788
SNMP: Error status = 0 (No error)
SNMP: Error index = 0
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.4.2} (DEC.2.15.3.3.3.1.4.2)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.2.1.1.2} (sysObjectID)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.2.1.1.4} (sysContact)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.2.1.1.6} (sysLocation)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.2.1.1.3} (sysUpTime)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.18.1.2.3.2} (DEC.2.18.1.2.3.2)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.18.1.2.3.3} (DEC.2.18.1.2.3.3)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.18.1.2.3.1} (DEC.2.18.1.2.3.1)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.2.4} (DEC.2.15.3.3.3.1.2.4)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.3.1} (DEC.2.15.3.3.3.1.3.1)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.3.4} (DEC.2.15.3.3.3.1.3.4)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.5.3} (DEC.2.15.3.3.3.1.5.3)
SNMP: Value = NULL
Sniffer Network Analyzer data from 26-Feb-96 at 11:26:20, unsaved
capture data, Page 2
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.5.2} (DEC.2.15.3.3.3.1.5.2)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.2.1} (DEC.2.15.3.3.3.1.2.1)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.2.7} (DEC.2.15.3.3.3.1.2.7)
SNMP: Value = NULL
SNMP:
ADDR HEX ASCII
0000 08 00 2B A3 16 64 00 AA 00 36 81 16 08 00 45 00
..+..d...6....E.
0010 01 48 01 33 00 00 40 11 B3 13 8E 99 90 0F 8E 99
.H.3..@.........
0020 18 1D 05 30 00 A1 01 34 D8 D6 30 82 01 28 02 01
...0...4..0..(..
0030 00 04 05 74 6F 72 63 68 A1 82 01 1A 02 04 31 32
...torch......12
0040 4B CC 02 01 00 02 01 00 30 82 01 0A 30 12 06 0E
K.......0...0...
0050 2B 06 01 04 01 24 02 0F 03 03 03 01 04 02 05 00
+....$..........
0060 30 0B 06 07 2B 06 01 02 01 01 02 05 00 30 0B 06
0...+........0..
0070 07 2B 06 01 02 01 01 04 05 00 30 0B 06 07 2B 06
.+........0...+.
0080 01 02 01 01 06 05 00 30 0B 06 07 2B 06 01 02 01
.......0...+....
0090 01 03 05 00 30 10 06 0C 2B 06 01 04 01 24 02 12
....0...+....$..
00A0 01 02 03 02 05 00 30 10 06 0C 2B 06 01 04 01 24
......0...+....$
00B0 02 12 01 02 03 03 05 00 30 10 06 0C 2B 06 01 04
........0...+...
00C0 01 24 02 12 01 02 03 01 05 00 30 12 06 0E 2B 06
.$........0...+.
00D0 01 04 01 24 02 0F 03 03 03 01 02 04 05 00 30 12
...$..........0.
00E0 06 0E 2B 06 01 04 01 24 02 0F 03 03 03 01 03 01
..+....$........
00F0 05 00 30 12 06 0E 2B 06 01 04 01 24 02 0F 03 03
..0...+....$....
0100 03 01 03 04 05 00 30 12 06 0E 2B 06 01 04 01 24
......0...+....$
0110 02 0F 03 03 03 01 05 03 05 00 30 12 06 0E 2B 06
..........0...+.
0120 01 04 01 24 02 0F 03 03 03 01 05 02 05 00 30 12
...$..........0.
0130 06 0E 2B 06 01 04 01 24 02 0F 03 03 03 01 02 01
..+....$........
0140 05 00 30 12 06 0E 2B 06 01 04 01 24 02 0F 03 03
..0...+....$....
0150 03 01 02 07 05 00 ......
- - - - - - - - - - - - - - - - Frame 2 - - - - - - - - - - - - - - - -
-
SUMMARY Abs Time Delta T Destination Source Summary
2 11:26:28.8822 0.0036 [142.153.144... [142.153.24.78] SNMP
GetReply DEC.2.15.3.3.3.1.4.2.0 .. DEC.2.15.3.3.3.1.2.7.0 (15 items)
SNMP: ----- Simple Network Management Protocol (Version 1) -----
SNMP:
SNMP: Version = 0
SNMP: Community = torch
SNMP: Command = Get response
SNMP: Request ID = 825379788
SNMP: Error status = 0 (No error)
SNMP: Error index = 0
SNMP:
Sniffer Network Analyzer data from 26-Feb-96 at 11:26:20, unsaved
capture data, Page 3
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.4.2.0}
(DEC.2.15.3.3.3.1.4.2.0)
SNMP: Value = 4
SNMP:
SNMP: Object = {1.3.6.1.2.1.1.2.0} (sysObjectID.0)
SNMP: Value = {1.3.6.1.4.1.36.2.15.3.3}
SNMP:
SNMP: Object = {1.3.6.1.2.1.1.4.0} (sysContact.0)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.2.1.1.6.0} (sysLocation.0)
SNMP: Value = NULL
SNMP:
SNMP: Object = {1.3.6.1.2.1.1.3.0} (sysUpTime.0)
SNMP: Value = 0092 hundredths of a second
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.18.1.2.3.2.0} (DEC.2.18.1.2.3.2.0)
SNMP: Value = 0 (counter)
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.18.1.3.1.1.1.5} (DEC.2.18.1.3.1.1.1.5)
SNMP: Value = 5
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.18.1.2.3.1.0} (DEC.2.18.1.2.3.1.0)
SNMP: Value = 1 (counter)
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.2.4.0}
(DEC.2.15.3.3.3.1.2.4.0)
SNMP: Value = 5
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.3.1.0}
(DEC.2.15.3.3.3.1.3.1.0)
SNMP: Value = 2
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.3.4.0}
(DEC.2.15.3.3.3.1.3.4.0)
SNMP: Value = 2
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.5.3.0}
(DEC.2.15.3.3.3.1.5.3.0)
SNMP: Value = 2
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.5.2.0}
(DEC.2.15.3.3.3.1.5.2.0)
SNMP: Value = 2
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.2.1.0}
(DEC.2.15.3.3.3.1.2.1.0)
SNMP: Value = 2
SNMP:
SNMP: Object = {1.3.6.1.4.1.36.2.15.3.3.3.1.2.7.0}
(DEC.2.15.3.3.3.1.2.7.0)
SNMP: Value = 1
SNMP:
ADDR HEX ASCII
0000 00 AA 00 36 81 16 08 00 2B A3 16 1C 08 00 45 04
...6....+.....E.
0010 01 72 C1 79 00 00 20 11 12 6E 8E 99 18 4E 8E 99 .r.y..
..n...N..
0020 90 0F 00 A1 05 30 01 5E D3 9C 30 82 01 52 02 01
.....0.^..0..R..
0030 00 04 05 74 6F 72 63 68 A2 82 01 44 02 04 31 32
...torch...D..12
Sniffer Network Analyzer data from 26-Feb-96 at 11:26:20, unsaved
capture data, Page 4
0040 4B CC 02 01 00 02 01 00 30 82 01 34 30 14 06 0F
K.......0..40...
0050 2B 06 01 04 01 24 02 0F 03 03 03 01 04 02 00 02
+....$..........
0060 01 04 30 16 06 08 2B 06 01 02 01 01 02 00 06 0A
..0...+.........
0070 2B 06 01 04 01 24 02 0F 03 03 30 0C 06 08 2B 06
+....$....0...+.
0080 01 02 01 01 04 00 04 00 30 0C 06 08 2B 06 01 02
........0...+...
0090 01 01 06 00 04 00 30 11 06 08 2B 06 01 02 01 01
......0...+.....
00A0 03 00 43 05 00 92 E8 44 FB 30 12 06 0D 2B 06 01
..C....D.0...+..
00B0 04 01 24 02 12 01 02 03 02 00 41 01 00 30 13 06
..$.......A..0..
00C0 0E 2B 06 01 04 01 24 02 12 01 03 01 01 01 05 02
.+....$.........
00D0 01 05 30 12 06 0D 2B 06 01 04 01 24 02 12 01 02
..0...+....$....
00E0 03 01 00 41 01 01 30 14 06 0F 2B 06 01 04 01 24
...A..0...+....$
00F0 02 0F 03 03 03 01 02 04 00 02 01 05 30 14 06 0F
............0...
0100 2B 06 01 04 01 24 02 0F 03 03 03 01 03 01 00 02
+....$..........
0110 01 02 30 14 06 0F 2B 06 01 04 01 24 02 0F 03 03
..0...+....$....
0120 03 01 03 04 00 02 01 02 30 14 06 0F 2B 06 01 04
........0...+...
0130 01 24 02 0F 03 03 03 01 05 03 00 02 01 02 30 14
.$............0.
0140 06 0F 2B 06 01 04 01 24 02 0F 03 03 03 01 05 02
..+....$........
0150 00 02 01 02 30 14 06 0F 2B 06 01 04 01 24 02 0F
....0...+....$..
0160 03 03 03 01 02 01 00 02 01 02 30 14 06 0F 2B 06
..........0...+.
0170 01 04 01 24 02 0F 03 03 03 01 02 07 00 02 01 01
...$............
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3312.1 | Problem is not in the GIGAswitch. | NETCAD::GALLAGHER | Tue Feb 27 1996 09:13 | 44 | |
> this is a trace from the sniffer showing the requests and answers from
> the gigaswitch when I double click on the SCP module. THe important
> point is the response to the SYSUPTIME request (packet #2). In the
> decoded portion the uptime is reported as 0092 hundredths of a second
> but in the hex dump the corresponding location is 00A2 (third byte in
> the 00A0 row) which has the value: 43 05 00 92 E8 44 FB. The 43
> indicates a time value, 05 indicates 5 data bytes so the total hex time
> in hundredths of seconds is 0092E844FB. However according to the SNMP
> MIB the time value is always 4 bytes long this creates a problem for
> any software that tries to decode the time.
The encoding is correct. Although sysUpTime is a TimeTicks (32-bit
unsigned INTEGER) it must be ASN.1 encoded into 5 octets in order to
keep the sign bit. i.e.
0x80 00 00 01 = -1 (and we all know that time doesn't go negative.)
0x00 80 00 00 00 = 2,147,483,648 = 248 days.
sysUpTime can reach 0xff ff ff ff, (encoded into 0x00 ff ff ff ff), then
it wraps back to zero. Wrapping can cause problems with NMSs. This is a
known problem with SNMP/MIB-II/SMI.
So the GIGAswitch is right.
> Specifically HUBWATCH
> returns with a SYSTEM or GENERAL ERROR. This 5 byte value is returned
> by any bridge (including the gigaswitches) that has the high order bit
> set (corresponding time is 248.55 days). Because the HUBWATCH software
> tries to read the time whenever the management screen is entered I
> cannot control the devices. If you can find out if there is a fix for
> this I would appreciate it. We are running the latest versions of
> firmware on the gigaswitch and V1.5.0 on the bridges.
This is a known problem in HUBwatch. Feel free to elevate the problem to
make sure it's fixed in a timely manner.
It's kinda a nice problem to see. I like seeing equipment that's been up
for more than 248 days. Wish the equipment I use would have this problem.
Nice investigation though.
-Shawn
| |||||
| 3312.2 | how do I escalate | KAOFS::R_YURKIW | reward those who bring bad news!! | Tue Feb 27 1996 13:43 | 5 |
Can you please let me know what the process is to excalate this
problem?
Thanks
| |||||
| 3312.3 | CSC32::B_GOODWIN | MCI Mission Critical Support Team | Tue Feb 27 1996 15:23 | 2 | |
You escalate problems via IPMT. If you don't know how to do this, contact your local MCS group. | |||||
| 3312.4 | Will Escalate | TROOA::MCCHARLES | Wed Feb 28 1996 11:17 | 3 | |
Thanks for the quick answer. I will escalate.
Rick
| |||||
| 3312.5 | more info | CSC32::D_PERRIN | Mon Apr 08 1996 14:54 | 4 | |
I've got a customer seeing this problem with Hubwatch/osf. Will
this be fixed in the next version? Will there be a next version
for osf?
| |||||
| 3312.6 | bad news bear says "Yes" twice | SLINK::HOOD | Your bad news bear | Mon Apr 08 1996 15:05 | 6 |
> I've got a customer seeing this problem with Hubwatch/osf. Will > this be fixed in the next version? Will there be a next version > for osf? Yes, and yes. | |||||