Re: SNMP Data Collection on ifIndex > 2^31

--===============7269630054166470728==
Content-Type: multipart/alternative; boundary="0000000000002a12af0579b37745"

--0000000000002a12af0579b37745
Content-Type: text/plain; charset="UTF-8"

It looks like NMS-8179 dealt with this issue and at some point there was a
commit and it was marked resolved.

Is there any reason why the patch did not make it into Horizon 23?

Is it actually back to unresolved, maybe due to some incompatible upstream
feature?

https://issues.opennms.org/plugins/servlet/mobile#issue/NMS-8179

It looks like this is the standard implementation of ifIndex on the Huawei
access gear.  That's a lot of service ports worldwide, considering their
VDSL2 / GPON and XG-PON footprint across the major carriers with the MA56xx
lines.

Cheers,
Ian




On Tue, Oct 30, 2018, 11:37 PM Ian MacDonald <[email protected] wrote:

> David,
>
> Thanks for the feedback.
>
> On Mon, Oct 29, 2018 at 9:16 PM David Hustace <[email protected]> wrote:
>
>> > The CPE access interfaces however have much higher ifIndex numbers
>> (seen in snmpwalk immediately below) which appear as negative integers as
>> the ifIndex
>>
>> From the RFC it seems index values are to be non-negative so I'm assuming
>> that's making the underlying protocol library (SNMP4J) very unhappy and the
>> manager (OpenNMS) is calling "no joy".
>>
>
> I agree it seemed like an obvious stretch of the RFC to accommodate very
> large interface numbers by using all 32 bits of the non-negative integer
> space.   It might be worthwhile to consider this stretching of the RFC to
> support a very large number of ports.
>
> On Tue, Oct 30, 2018 at 5:17 AM Seibold, Michael <[email protected]>
> wrote:
>
>> It seems that when writing the RFC they didn't expect such high index
>> numbers. Otherwise they should have written more detailed "unsigned 32 bit
>> integer". As they wrote "this works only for non-negative numbers" they
>> obviously limited the ifindex range to 0 - 2^31.
>>
>> So I assume that somewhere in the code 32-bit signed integers are used,
>> which will lead to the observed negative numbers. Using 32-bit unsigned
>> integers should avoid this problem, but might also be seen as a violation
>> of the RFC.
>> It would be interesting if the underlying SNMP4J and other snmp stacks
>> are using unsigned integers or not. As the manufacturer probably uses some
>> free available snmp stack this one obviously is coded with unsigned
>> integers.
>
>
> It would seem that the unsigned integer does get some joy, as we can see
> the mib-2 data being parsed by collectd for the interfaces with ifIndex >
> 2^31 ; I shows a small excerpt from debug in my initial post
>
> It almost looks like the only issue might be the be the value of the
> initial OID instance of the ifIndex which uses the signed integers as a
> value even though the same ifIndex appears unsigned in the same OID
> identifier.
>
> Maybe a cast of the ifIndex to an unsigned value (which would match the
> RFC requirement) would solve the issue - it seems that collectd has no
> trouble with the unsiged int values and all the OID identifiers use an
> unsigned value.  I suspect this would solve a similar issue for the GPON
> boards as well, if it worked.
>
> cheers,
> Ian
>
> ~$ snmpwalk -cXXXXXXXXX -v2c 10.1.1.94 | grep 4160757760
> IF-MIB::ifIndex.4160757760 = INTEGER: -134209536
> IF-MIB::ifDescr.4160757760 = STRING: Huawei-MA5616-V800R018-VDSL
> IF-MIB::ifType.4160757760 = INTEGER: vdsl2(251)
> IF-MIB::ifMtu.4160757760 = INTEGER: 0
> IF-MIB::ifSpeed.4160757760 = Gauge32: 200000000
> IF-MIB::ifPhysAddress.4160757760 = STRING: 0:0:0:0:0:0
> IF-MIB::ifAdminStatus.4160757760 = INTEGER: up(1)
> IF-MIB::ifOperStatus.4160757760 = INTEGER: up(1)
> IF-MIB::ifLastChange.4160757760 = Timeticks: (169555985) 19 days,
> 14:59:19.85
> IF-MIB::ifInOctets.4160757760 = Counter32: 2979832157
> IF-MIB::ifInUcastPkts.4160757760 = Counter32: 0
> IF-MIB::ifInNUcastPkts.4160757760 = Counter32: 0
> IF-MIB::ifInDiscards.4160757760 = Counter32: 0
> IF-MIB::ifInErrors.4160757760 = Counter32: 0
> IF-MIB::ifInUnknownProtos.4160757760 = Counter32: 0
> IF-MIB::ifOutOctets.4160757760 = Counter32: 1076222843
> IF-MIB::ifOutUcastPkts.4160757760 = Counter32: 0
> IF-MIB::ifOutNUcastPkts.4160757760 = Counter32: 0
> IF-MIB::ifOutDiscards.4160757760 = Counter32: 0
> IF-MIB::ifOutErrors.4160757760 = Counter32: 0
> IF-MIB::ifOutQLen.4160757760 = Gauge32: 4294967295
> IF-MIB::ifSpecific.4160757760 = OID: SNMPv2-SMI::zeroDotZero
> SNMPv2-SMI::transmission.94.1.1.65538.1.1.4160757760 = INTEGER: 255
> SNMPv2-SMI::transmission.94.1.1.65538.1.2.4160757760 = INTEGER: 0
> SNMPv2-SMI::transmission.94.1.1.65538.1.4.4160757760 = Gauge32: 4294967295
> SNMPv2-SMI::transmission.94.1.1.65538.1.5.4160757760 = Gauge32: 4294967295
> SNMPv2-SMI::transmission.94.1.1.65538.1.6.4160757760 = INTEGER: 2
> SNMPv2-SMI::transmission.94.1.1.65538.1.7.4160757760 = Counter32: 3069875
> SNMPv2-SMI::transmission.94.1.1.65538.1.8.4160757760 = INTEGER: 1
> SNMPv2-SMI::transmission.94.1.1.65538.1.600.4160757760 = INTEGER: 1
> SNMPv2-SMI::transmission.94.1.1.65538.1.601.4160757760 = INTEGER: -1
> SNMPv2-SMI::transmission.94.1.1.65538.1.702.4160757760 = Hex-STRING: 07 E2
> 09 19 0A 26 2E 00 2D 04 00
> SNMPv2-SMI::transmission.94.1.1.65538.1.703.4160757760 = Hex-STRING: 07 E2
> 09 19 0A 25 27 00 2D 04 00
> SNMPv2-SMI::transmission.94.1.1.65551.1.1.4160757760 = INTEGER: -1
> SNMPv2-SMI::transmission.94.1.1.65551.1.2.4160757760 = INTEGER: -1
> IF-MIB::ifName.4160757760 = STRING: VDSL 0/1/0
> IF-MIB::ifInMulticastPkts.4160757760 = Counter32: 0
> IF-MIB::ifInBroadcastPkts.4160757760 = Counter32: 0
> IF-MIB::ifOutMulticastPkts.4160757760 = Counter32: 0
> IF-MIB::ifOutBroadcastPkts.4160757760 = Counter32: 0
> IF-MIB::ifHCInOctets.4160757760 = Counter64: 7276592905
> IF-MIB::ifHCInUcastPkts.4160757760 = Counter64: 0
> IF-MIB::ifHCInMulticastPkts.4160757760 = Counter64: 0
> IF-MIB::ifHCInBroadcastPkts.4160757760 = Counter64: 0
> IF-MIB::ifHCOutOctets.4160757760 = Counter64: 121390831116
> IF-MIB::ifHCOutUcastPkts.4160757760 = Counter64: 0
> IF-MIB::ifHCOutMulticastPkts.4160757760 = Counter64: 0
> IF-MIB::ifHCOutBroadcastPkts.4160757760 = Counter64: 0
> IF-MIB::ifLinkUpDownTrapEnable.4160757760 = INTEGER: disabled(2)
> IF-MIB::ifHighSpeed.4160757760 = Gauge32: 200
> IF-MIB::ifPromiscuousMode.4160757760 = INTEGER: true(1)
> IF-MIB::ifConnectorPresent.4160757760 = INTEGER: true(1)
> IF-MIB::ifAlias.4160757760 = STRING:
> IF-MIB::ifCounterDiscontinuityTime.4160757760 = Timeticks: (0) 0:00:00.00
> SNMPv2-SMI::mib-2.158.1.1.1.1.4160757760 = INTEGER: 2
> SNMPv2-SMI::mib-2.158.1.1.1.2.4160757760 = INTEGER: 1
> SNMPv2-SMI::mib-2.158.1.1.1.3.4160757760 = INTEGER: 2
> SNMPv2-SMI::mib-2.158.1.1.1.4.4160757760 = Gauge32: 1514
> SNMPv2-SMI::mib-2.158.1.1.1.5.4160757760 = Gauge32: 0
> SNMPv2-SMI::mib-2.158.1.1.1.6.4160757760 = STRING: " "
> SNMPv2-SMI::mib-2.158.1.2.1.1.4160757760 = Hex-STRING: 00 00 00 00 00 00
> SNMPv2-SMI::mib-2.158.1.2.1.2.4160757760 = Hex-STRING: 00 00 00
> SNMPv2-SMI::mib-2.158.1.2.1.3.4160757760 = Gauge32: 0
> SNMPv2-SMI::mib-2.158.1.2.1.4.4160757760 = INTEGER: 3
> SNMPv2-SMI::mib-2.158.1.2.1.5.4160757760 = Gauge32: 0
> SNMPv2-SMI::mib-2.158.1.2.1.6.4160757760 = Gauge32: 0
> SNMPv2-SMI::mib-2.158.1.2.1.7.4160757760 = Hex-STRING: 00
> SNMPv2-SMI::mib-2.158.1.3.1.1.4160757760 = INTEGER: 1
> SNMPv2-SMI::mib-2.158.1.3.1.2.4160757760 = INTEGER: 1
> SNMPv2-SMI::mib-2.158.1.4.1.1.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.2.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.3.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.4.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.5.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.6.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.7.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.8.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.9.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.10.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.11.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.12.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.13.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.14.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.15.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.16.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.4.1.17.4160757760 = Counter32: 0
> SNMPv2-SMI::mib-2.158.1.5.1.1.4160757760 = Gauge32: 4294967295
> SNMPv2-SMI::mib-2.158.1.5.1.2.4160757760 = Gauge32: 4294967295
> SNMPv2-SMI::mib-2.158.1.5.1.3.4160757760 = Gauge32: 4294967295
> SNMPv2-SMI::mib-2.158.1.5.1.4.4160757760 = Gauge32: 4294967295
> SNMPv2-SMI::mib-2.158.1.5.1.5.4160757760 = INTEGER: 2
> SNMPv2-SMI::mib-2.158.1.5.1.6.4160757760 = Gauge32: 4294967295
> SNMPv2-SMI::mib-2.158.1.5.1.7.4160757760 = Gauge32: 4294967295
> SNMPv2-SMI::mib-2.158.1.5.1.8.4160757760 = INTEGER: 2
> SNMPv2-SMI::mib-2.158.1.5.1.9.4160757760 = Gauge32: 10
> SNMPv2-SMI::mib-2.158.1.5.1.10.4160757760 = Gauge32: 1
> SNMPv2-SMI::mib-2.158.1.5.1.11.4160757760 = INTEGER: 2
> SNMPv2-SMI::mib-2.158.1.5.1.12.4160757760 = INTEGER: 100
> SNMPv2-SMI::mib-2.158.1.5.1.13.4160757760 = INTEGER: 1
> SNMPv2-SMI::mib-2.158.1.5.1.14.4160757760 = INTEGER: 2
> SNMPv2-SMI::mib-2.158.1.5.1.15.4160757760 = INTEGER: 2
> SNMPv2-SMI::mib-2.158.1.5.1.16.4160757760 = INTEGER: 2
>
>
>
>
>
>

--0000000000002a12af0579b37745
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"auto">It looks like NMS-8179 dealt with this issue and at some =
point there was a commit and it was marked resolved.<div dir=3D"auto"><br><=
/div><div dir=3D"auto">Is there any reason why the patch did not make it in=
to Horizon 23?</div><div dir=3D"auto"><br></div><div dir=3D"auto">Is it act=
ually back to unresolved, maybe due to some incompatible upstream feature?<=
br><div dir=3D"auto"><br></div><div dir=3D"auto"><a href=3D"https://issues.=
opennms.org/plugins/servlet/mobile#issue/NMS-8179">https://issues.opennms.o=
rg/plugins/servlet/mobile#issue/NMS-8179</a><br></div><div dir=3D"auto"><br=
></div><div dir=3D"auto">It looks like this is the standard implementation =
of ifIndex on the Huawei access gear.=C2=A0 That&#39;s a lot of service por=
ts worldwide, considering their VDSL2 / GPON and XG-PON footprint across th=
e major carriers with the MA56xx lines.=C2=A0</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">Cheers,</div><div dir=3D"auto">Ian=C2=A0=C2=A0</div><=
div dir=3D"auto"><br></div><div dir=3D"auto"><br></div><div dir=3D"auto"><b=
r></div></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Tue,=
 Oct 30, 2018, 11:37 PM Ian MacDonald &lt;<a href=3D"mailto:[email protected]=
om">[email protected]</a> wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><d=
iv dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">David,=C2=A0</div><div dir=
=3D"ltr"><br></div><div dir=3D"ltr">Thanks for the feedback.<br><div><br></=
div><div>On Mon, Oct 29, 2018 at 9:16 PM David Hustace &lt;<a href=3D"mailt=
o:[email protected]" target=3D"_blank" rel=3D"noreferrer">[email protected]=
</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
&gt; The CPE access interfaces however have much higher ifIndex numbers (se=
en in snmpwalk immediately below) which appear as negative integers as the =
ifIndex<br><br>From the RFC it seems index values are to be non-negative so=
 I&#39;m assuming that&#39;s making the underlying protocol library (SNMP4J=
) very unhappy and the manager (OpenNMS) is calling &quot;no joy&quot;.<br>=
</blockquote><div>=C2=A0</div><div><div>I agree it seemed like an obvious s=
tretch of the RFC to accommodate very large interface numbers by using all =
32 bits of the non-negative integer space.=C2=A0 =C2=A0It might be worthwhi=
le to consider this stretching of the RFC to support a very large number of=
 ports.</div><div><br></div></div><div><div dir=3D"ltr">On Tue, Oct 30, 201=
8 at 5:17 AM Seibold, Michael &lt;<a href=3D"mailto:[email protected]=
" target=3D"_blank" rel=3D"noreferrer">[email protected]</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">It seems that=
 when writing the RFC they didn&#39;t expect such high index numbers. Other=
wise they should have written more detailed &quot;unsigned 32 bit integer&q=
uot;. As they wrote &quot;this works only for non-negative numbers&quot; th=
ey obviously limited the ifindex range to 0 - 2^31.<br><br>So I assume that=
 somewhere in the code 32-bit signed integers are used, which will lead to =
the observed negative numbers. Using 32-bit unsigned integers should avoid =
this problem, but might also be seen as a violation of the RFC.<br>It would=
 be interesting if the underlying SNMP4J and other snmp stacks are using un=
signed integers or not. As the manufacturer probably uses some free availab=
le snmp stack this one obviously is coded with unsigned integers.</blockquo=
te></div><div><br></div><div>It would seem that the unsigned integer does g=
et some joy, as we can see the mib-2 data being parsed by collectd for the =
interfaces with ifIndex &gt; 2^31 ; I shows a small excerpt from debug in m=
y initial post</div><div><br></div><div>It almost looks like the only issue=
 might be the be the value of the initial OID instance of the ifIndex which=
 uses the signed integers as a value even though the same ifIndex appears u=
nsigned in the same OID identifier.=C2=A0</div><div><br></div><div>Maybe a =
cast of the ifIndex to an unsigned value (which would match the RFC require=
ment) would solve the issue - it seems that collectd has no trouble with th=
e unsiged int values and all the OID identifiers use an unsigned value.=C2=
=A0 I suspect this would solve a similar issue for the GPON boards as well,=
 if it worked.=C2=A0=C2=A0</div><div><br></div><div>cheers,</div><div>Ian</=
div><div><br></div><div><div>~$ snmpwalk -cXXXXXXXXX -v2c 10.1.1.94 | grep =
4160757760</div><div>IF-MIB::ifIndex.4160757760 =3D INTEGER: -134209536</di=
v><div>IF-MIB::ifDescr.4160757760 =3D STRING: Huawei-MA5616-V800R018-VDSL</=
div><div>IF-MIB::ifType.4160757760 =3D INTEGER: vdsl2(251)</div><div>IF-MIB=
::ifMtu.4160757760 =3D INTEGER: 0</div><div>IF-MIB::ifSpeed.4160757760 =3D =
Gauge32: 200000000</div><div>IF-MIB::ifPhysAddress.4160757760 =3D STRING: 0=
:0:0:0:0:0</div><div>IF-MIB::ifAdminStatus.4160757760 =3D INTEGER: up(1)</d=
iv><div>IF-MIB::ifOperStatus.4160757760 =3D INTEGER: up(1)</div><div>IF-MIB=
::ifLastChange.4160757760 =3D Timeticks: (169555985) 19 days, 14:59:19.85</=
div><div>IF-MIB::ifInOctets.4160757760 =3D Counter32: 2979832157</div><div>=
IF-MIB::ifInUcastPkts.4160757760 =3D Counter32: 0</div><div>IF-MIB::ifInNUc=
astPkts.4160757760 =3D Counter32: 0</div><div>IF-MIB::ifInDiscards.41607577=
60 =3D Counter32: 0</div><div>IF-MIB::ifInErrors.4160757760 =3D Counter32: =
0</div><div>IF-MIB::ifInUnknownProtos.4160757760 =3D Counter32: 0</div><div=
>IF-MIB::ifOutOctets.4160757760 =3D Counter32: 1076222843</div><div>IF-MIB:=
:ifOutUcastPkts.4160757760 =3D Counter32: 0</div><div>IF-MIB::ifOutNUcastPk=
ts.4160757760 =3D Counter32: 0</div><div>IF-MIB::ifOutDiscards.4160757760 =
=3D Counter32: 0</div><div>IF-MIB::ifOutErrors.4160757760 =3D Counter32: 0<=
/div><div>IF-MIB::ifOutQLen.4160757760 =3D Gauge32: 4294967295</div><div>IF=
-MIB::ifSpecific.4160757760 =3D OID: SNMPv2-SMI::zeroDotZero</div><div>SNMP=
v2-SMI::transmission.94.1.1.65538.1.1.4160757760 =3D INTEGER: 255</div><div=
>SNMPv2-SMI::transmission.94.1.1.65538.1.2.4160757760 =3D INTEGER: 0</div><=
div>SNMPv2-SMI::transmission.94.1.1.65538.1.4.4160757760 =3D Gauge32: 42949=
67295</div><div>SNMPv2-SMI::transmission.94.1.1.65538.1.5.4160757760 =3D Ga=
uge32: 4294967295</div><div>SNMPv2-SMI::transmission.94.1.1.65538.1.6.41607=
57760 =3D INTEGER: 2</div><div>SNMPv2-SMI::transmission.94.1.1.65538.1.7.41=
60757760 =3D Counter32: 3069875</div><div>SNMPv2-SMI::transmission.94.1.1.6=
5538.1.8.4160757760 =3D INTEGER: 1</div><div>SNMPv2-SMI::transmission.94.1.=
1.65538.1.600.4160757760 =3D INTEGER: 1</div><div>SNMPv2-SMI::transmission.=
94.1.1.65538.1.601.4160757760 =3D INTEGER: -1</div><div>SNMPv2-SMI::transmi=
ssion.94.1.1.65538.1.702.4160757760 =3D Hex-STRING: 07 E2 09 19 0A 26 2E 00=
 2D 04 00=C2=A0</div><div>SNMPv2-SMI::transmission.94.1.1.65538.1.703.41607=
57760 =3D Hex-STRING: 07 E2 09 19 0A 25 27 00 2D 04 00=C2=A0</div><div>SNMP=
v2-SMI::transmission.94.1.1.65551.1.1.4160757760 =3D INTEGER: -1</div><div>=
SNMPv2-SMI::transmission.94.1.1.65551.1.2.4160757760 =3D INTEGER: -1</div><=
div>IF-MIB::ifName.4160757760 =3D STRING: VDSL 0/1/0</div><div>IF-MIB::ifIn=
MulticastPkts.4160757760 =3D Counter32: 0</div><div>IF-MIB::ifInBroadcastPk=
ts.4160757760 =3D Counter32: 0</div><div>IF-MIB::ifOutMulticastPkts.4160757=
760 =3D Counter32: 0</div><div>IF-MIB::ifOutBroadcastPkts.4160757760 =3D Co=
unter32: 0</div><div>IF-MIB::ifHCInOctets.4160757760 =3D Counter64: 7276592=
905</div><div>IF-MIB::ifHCInUcastPkts.4160757760 =3D Counter64: 0</div><div=
>IF-MIB::ifHCInMulticastPkts.4160757760 =3D Counter64: 0</div><div>IF-MIB::=
ifHCInBroadcastPkts.4160757760 =3D Counter64: 0</div><div>IF-MIB::ifHCOutOc=
tets.4160757760 =3D Counter64: 121390831116</div><div>IF-MIB::ifHCOutUcastP=
kts.4160757760 =3D Counter64: 0</div><div>IF-MIB::ifHCOutMulticastPkts.4160=
757760 =3D Counter64: 0</div><div>IF-MIB::ifHCOutBroadcastPkts.4160757760 =
=3D Counter64: 0</div><div>IF-MIB::ifLinkUpDownTrapEnable.4160757760 =3D IN=
TEGER: disabled(2)</div><div>IF-MIB::ifHighSpeed.4160757760 =3D Gauge32: 20=
0</div><div>IF-MIB::ifPromiscuousMode.4160757760 =3D INTEGER: true(1)</div>=
<div>IF-MIB::ifConnectorPresent.4160757760 =3D INTEGER: true(1)</div><div>I=
F-MIB::ifAlias.4160757760 =3D STRING:=C2=A0</div><div>IF-MIB::ifCounterDisc=
ontinuityTime.4160757760 =3D Timeticks: (0) 0:00:00.00</div><div>SNMPv2-SMI=
::mib-2.158.1.1.1.1.4160757760 =3D INTEGER: 2</div><div>SNMPv2-SMI::mib-2.1=
58.1.1.1.2.4160757760 =3D INTEGER: 1</div><div>SNMPv2-SMI::mib-2.158.1.1.1.=
3.4160757760 =3D INTEGER: 2</div><div>SNMPv2-SMI::mib-2.158.1.1.1.4.4160757=
760 =3D Gauge32: 1514</div><div>SNMPv2-SMI::mib-2.158.1.1.1.5.4160757760 =
=3D Gauge32: 0</div><div>SNMPv2-SMI::mib-2.158.1.1.1.6.4160757760 =3D STRIN=
G: &quot; &quot;</div><div>SNMPv2-SMI::mib-2.158.1.2.1.1.4160757760 =3D Hex=
-STRING: 00 00 00 00 00 00=C2=A0</div><div>SNMPv2-SMI::mib-2.158.1.2.1.2.41=
60757760 =3D Hex-STRING: 00 00 00=C2=A0</div><div>SNMPv2-SMI::mib-2.158.1.2=
.1.3.4160757760 =3D Gauge32: 0</div><div>SNMPv2-SMI::mib-2.158.1.2.1.4.4160=
757760 =3D INTEGER: 3</div><div>SNMPv2-SMI::mib-2.158.1.2.1.5.4160757760 =
=3D Gauge32: 0</div><div>SNMPv2-SMI::mib-2.158.1.2.1.6.4160757760 =3D Gauge=
32: 0</div><div>SNMPv2-SMI::mib-2.158.1.2.1.7.4160757760 =3D Hex-STRING: 00=
=C2=A0</div><div>SNMPv2-SMI::mib-2.158.1.3.1.1.4160757760 =3D INTEGER: 1</d=
iv><div>SNMPv2-SMI::mib-2.158.1.3.1.2.4160757760 =3D INTEGER: 1</div><div>S=
NMPv2-SMI::mib-2.158.1.4.1.1.4160757760 =3D Counter32: 0</div><div>SNMPv2-S=
MI::mib-2.158.1.4.1.2.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib=
-2.158.1.4.1.3.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib-2.158.=
1.4.1.4.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib-2.158.1.4.1.5=
.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib-2.158.1.4.1.6.416075=
7760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib-2.158.1.4.1.7.4160757760 =
=3D Counter32: 0</div><div>SNMPv2-SMI::mib-2.158.1.4.1.8.4160757760 =3D Cou=
nter32: 0</div><div>SNMPv2-SMI::mib-2.158.1.4.1.9.4160757760 =3D Counter32:=
 0</div><div>SNMPv2-SMI::mib-2.158.1.4.1.10.4160757760 =3D Counter32: 0</di=
v><div>SNMPv2-SMI::mib-2.158.1.4.1.11.4160757760 =3D Counter32: 0</div><div=
>SNMPv2-SMI::mib-2.158.1.4.1.12.4160757760 =3D Counter32: 0</div><div>SNMPv=
2-SMI::mib-2.158.1.4.1.13.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI:=
:mib-2.158.1.4.1.14.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib-2=
.158.1.4.1.15.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib-2.158.1=
.4.1.16.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib-2.158.1.4.1.1=
7.4160757760 =3D Counter32: 0</div><div>SNMPv2-SMI::mib-2.158.1.5.1.1.41607=
57760 =3D Gauge32: 4294967295</div><div>SNMPv2-SMI::mib-2.158.1.5.1.2.41607=
57760 =3D Gauge32: 4294967295</div><div>SNMPv2-SMI::mib-2.158.1.5.1.3.41607=
57760 =3D Gauge32: 4294967295</div><div>SNMPv2-SMI::mib-2.158.1.5.1.4.41607=
57760 =3D Gauge32: 4294967295</div><div>SNMPv2-SMI::mib-2.158.1.5.1.5.41607=
57760 =3D INTEGER: 2</div><div>SNMPv2-SMI::mib-2.158.1.5.1.6.4160757760 =3D=
 Gauge32: 4294967295</div><div>SNMPv2-SMI::mib-2.158.1.5.1.7.4160757760 =3D=
 Gauge32: 4294967295</div><div>SNMPv2-SMI::mib-2.158.1.5.1.8.4160757760 =3D=
 INTEGER: 2</div><div>SNMPv2-SMI::mib-2.158.1.5.1.9.4160757760 =3D Gauge32:=
 10</div><div>SNMPv2-SMI::mib-2.158.1.5.1.10.4160757760 =3D Gauge32: 1</div=
><div>SNMPv2-SMI::mib-2.158.1.5.1.11.4160757760 =3D INTEGER: 2</div><div>SN=
MPv2-SMI::mib-2.158.1.5.1.12.4160757760 =3D INTEGER: 100</div><div>SNMPv2-S=
MI::mib-2.158.1.5.1.13.4160757760 =3D INTEGER: 1</div><div>SNMPv2-SMI::mib-=
2.158.1.5.1.14.4160757760 =3D INTEGER: 2</div><div>SNMPv2-SMI::mib-2.158.1.=
5.1.15.4160757760 =3D INTEGER: 2</div><div>SNMPv2-SMI::mib-2.158.1.5.1.16.4=
160757760 =3D INTEGER: 2</div></div><div><br></div><div><br></div><div><br>=
</div><div><br></div><div><br></div></div></div></div>
</blockquote></div>

--0000000000002a12af0579b37745--


--===============7269630054166470728==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline


--===============7269630054166470728==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Please read the OpenNMS Mailing List FAQ:
http://www.opennms.org/index.php/Mailing_List_FAQ

opennms-discuss mailing list

To *unsubscribe* or change your subscription options, see the bottom of this page:
https://lists.sourceforge.net/lists/listinfo/opennms-discuss
--===============7269630054166470728==--