RE: [nv-l] ? about specific trap numbers
2005-08-08 11:51:27
Brilliant! Obviously, I need to brush up on my math -
but I was able to follow your explanation and leverage it for my
issue.
This was exactly what I needed - thx very
much,
Glen Warn
PEMCO Corporation Computer Services
(PCCS)
206-628-5770
Glen,
your problem is related to signed vs unsigned 32 bit
integers. In other words : 2^32 =
4294967296 = 3221232503 + 1073734793.
Microsoft rightly considers that specific = 3221232503 is a legal
value, since the SNMP RFCs explain that
specific is an unsigned integer.
The
NetView programmers made a small mistake by using signed integers.
They made the same mistake when handling MIB
variables, etc. I still have a few
scripts which add 2^32 in case of negative values.
About 2 years ago I opened a ticket about SNMP having no
negative integers. Your findings prove
that this bug has not been fixed in every case.
Hope this helps, Philippe.
-----
Forwarded by Philippe Menard/France/Contr/IBM on 08/08/2005 10:54 -----
"Glen Warn"
<Glen.Warn AT pemcocorp DOT com> Sent by: owner-nv-l AT lists.us.ibm DOT com
06/08/2005 02:40
|
To
| <nv-l AT lists.us.ibm DOT com>
|
cc
|
|
Subject
| [nv-l] ? about specific
trap numbers |
|
NV 7.1.4 FP3 RH Linux AS 2.1
I am trying to modify some event configurations and
have a puzzling problem. Microsoft gives me the decimal "specific trap"
number I will see and I can convert that number to HEX (which I can see is
referenced in the control desk) but the actual events I have to specify are
neither. One example of my problem is this: SPECIFIC : -1073734793 (hex: c0001b77) Decimal: 3221232503 I do not understand how the c0001b77 is converted into
-1073734793. The only way I've been able to figure these out so far has
been to create an event that forces this trap. Some of the remaining ones
(3221232481 specifically) I cannot force out and don't know how to calculate the
Netview specific. Any ideas?? Glen Warn PEMCO Corporation Computer
Services (PCCS) glen.warn AT pemcocorp DOT com 206-628-5770
|
|
|