[Check_mk (english)] too many snmp output

Archive checkmk-en
1

hi,
I recently added an old d-link switch but can not get any output from discovery!

try to run cmk command

OMD[me]:~$ snmpwalk -v1 -c ‘public’ 172.16.0.2 sysDescr

SNMPv2-MIB::sysDescr.0 = STRING: D-Link DES-3052P Fast Ethernet Switch

but this command give me a very long output. :

OMD[me]:~$ snmpwalk -v1 -c ‘EHSANALISNMP’ 172.16.0.2

for eg:

…

IF-MIB::ifIndex.1232 = INTEGER: 1232

IF-MIB::ifIndex.1233 = INTEGER: 1233

IF-MIB::ifIndex.1234 = INTEGER: 1234

IF-MIB::ifIndex.1235 = INTEGER: 1235

IF-MIB::ifIndex.1236 = INTEGER: 1236

IF-MIB::ifIndex.1237 = INTEGER: 1237

IF-MIB::ifIndex.1238 = INTEGER: 1238

IF-MIB::ifIndex.1239 = INTEGER: 1239

IF-MIB::ifIndex.1240 = INTEGER: 1240

IF-MIB::ifIndex.1241 = INTEGER: 1241

IF-MIB::ifIndex.1242 = INTEGER: 1242

IF-MIB::ifIndex.1243 = INTEGER: 1243

IF-MIB::ifIndex.1244 = INTEGER: 1244

IF-MIB::ifIndex.1245 = INTEGER: 1245

IF-MIB::ifIndex.1246 = INTEGER: 1246

IF-MIB::ifIndex.1247 = INTEGER: 1247

IF-MIB::ifIndex.1248 = INTEGER: 1248

IF-MIB::ifIndex.1249 = INTEGER: 1249

IF-MIB::ifIndex.1250 = INTEGER: 1250

IF-MIB::ifIndex.1251 = INTEGER: 1251

IF-MIB::ifIndex.1252 = INTEGER: 1252

IF-MIB::ifIndex.1253 = INTEGER: 1253

IF-MIB::ifIndex.1254 = INTEGER: 1254

IF-MIB::ifIndex.1255 = INTEGER: 1255

IF-MIB::ifIndex.1256 = INTEGER: 1256

IF-MIB::ifIndex.1257 = INTEGER: 1257

IF-MIB::ifIndex.1258 = INTEGER: 1258

…

any help?!

2

Configure the host to get polled with snmp-v1 in WATO and you should get some services discovered.

Regards,
Marcel

···

Mr.Pine pine5514@gmail.com schrieb am Mo., 26. Dez. 2016 12:38:

hi,
I recently added an old d-link switch but can not get any output from discovery!

try to run cmk command

OMD[me]:~$ snmpwalk -v1 -c ‘public’ 172.16.0.2 sysDescr

SNMPv2-MIB::sysDescr.0 = STRING: D-Link DES-3052P Fast Ethernet Switch

but this command give me a very long output. :

OMD[me]:~$ snmpwalk -v1 -c ‘EHSANALISNMP’ 172.16.0.2

for eg:

…

IF-MIB::ifIndex.1232 = INTEGER: 1232

IF-MIB::ifIndex.1233 = INTEGER: 1233

IF-MIB::ifIndex.1234 = INTEGER: 1234

IF-MIB::ifIndex.1235 = INTEGER: 1235

IF-MIB::ifIndex.1236 = INTEGER: 1236

IF-MIB::ifIndex.1237 = INTEGER: 1237

IF-MIB::ifIndex.1238 = INTEGER: 1238

IF-MIB::ifIndex.1239 = INTEGER: 1239

IF-MIB::ifIndex.1240 = INTEGER: 1240

IF-MIB::ifIndex.1241 = INTEGER: 1241

IF-MIB::ifIndex.1242 = INTEGER: 1242

IF-MIB::ifIndex.1243 = INTEGER: 1243

IF-MIB::ifIndex.1244 = INTEGER: 1244

IF-MIB::ifIndex.1245 = INTEGER: 1245

IF-MIB::ifIndex.1246 = INTEGER: 1246

IF-MIB::ifIndex.1247 = INTEGER: 1247

IF-MIB::ifIndex.1248 = INTEGER: 1248

IF-MIB::ifIndex.1249 = INTEGER: 1249

IF-MIB::ifIndex.1250 = INTEGER: 1250

IF-MIB::ifIndex.1251 = INTEGER: 1251

IF-MIB::ifIndex.1252 = INTEGER: 1252

IF-MIB::ifIndex.1253 = INTEGER: 1253

IF-MIB::ifIndex.1254 = INTEGER: 1254

IF-MIB::ifIndex.1255 = INTEGER: 1255

IF-MIB::ifIndex.1256 = INTEGER: 1256

IF-MIB::ifIndex.1257 = INTEGER: 1257

IF-MIB::ifIndex.1258 = INTEGER: 1258

…

any help?!

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

3

try with snmp-v1 , got the same output.

···

On Mon, Dec 26, 2016 at 7:22 PM, Marcel Schulte schulte.marcel@gmail.com wrote:

Configure the host to get polled with snmp-v1 in WATO and you should get some services discovered.

Regards,
Marcel

Mr.Pine pine5514@gmail.com schrieb am Mo., 26. Dez. 2016 12:38:

hi,
I recently added an old d-link switch but can not get any output from discovery!

try to run cmk command

OMD[me]:~$ snmpwalk -v1 -c ‘public’ 172.16.0.2 sysDescr

SNMPv2-MIB::sysDescr.0 = STRING: D-Link DES-3052P Fast Ethernet Switch

but this command give me a very long output. :

OMD[me]:~$ snmpwalk -v1 -c ‘EHSANALISNMP’ 172.16.0.2

for eg:

…

IF-MIB::ifIndex.1232 = INTEGER: 1232

IF-MIB::ifIndex.1233 = INTEGER: 1233

IF-MIB::ifIndex.1234 = INTEGER: 1234

IF-MIB::ifIndex.1235 = INTEGER: 1235

IF-MIB::ifIndex.1236 = INTEGER: 1236

IF-MIB::ifIndex.1237 = INTEGER: 1237

IF-MIB::ifIndex.1238 = INTEGER: 1238

IF-MIB::ifIndex.1239 = INTEGER: 1239

IF-MIB::ifIndex.1240 = INTEGER: 1240

IF-MIB::ifIndex.1241 = INTEGER: 1241

IF-MIB::ifIndex.1242 = INTEGER: 1242

IF-MIB::ifIndex.1243 = INTEGER: 1243

IF-MIB::ifIndex.1244 = INTEGER: 1244

IF-MIB::ifIndex.1245 = INTEGER: 1245

IF-MIB::ifIndex.1246 = INTEGER: 1246

IF-MIB::ifIndex.1247 = INTEGER: 1247

IF-MIB::ifIndex.1248 = INTEGER: 1248

IF-MIB::ifIndex.1249 = INTEGER: 1249

IF-MIB::ifIndex.1250 = INTEGER: 1250

IF-MIB::ifIndex.1251 = INTEGER: 1251

IF-MIB::ifIndex.1252 = INTEGER: 1252

IF-MIB::ifIndex.1253 = INTEGER: 1253

IF-MIB::ifIndex.1254 = INTEGER: 1254

IF-MIB::ifIndex.1255 = INTEGER: 1255

IF-MIB::ifIndex.1256 = INTEGER: 1256

IF-MIB::ifIndex.1257 = INTEGER: 1257

IF-MIB::ifIndex.1258 = INTEGER: 1258

…

any help?!

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

4

That your first example lists only a single line is easy to explain. In
your command, you tell snmpwalk to only walk a specific OID: sysDescr.

Also, I notice in your commands, that for the second one you specify a
different community. Depending on how you configured your switch, more
or less information may be available depending on the community specified.

Regards,

Evy

···

On 26/12/16 17:08, Mr.Pine wrote:

try with snmp-v1 , got the same output.

On Mon, Dec 26, 2016 at 7:22 PM, Marcel Schulte > <schulte.marcel@gmail.com <mailto:schulte.marcel@gmail.com>> wrote:

    Configure the host to get polled with snmp-v1 in WATO and you should
    get some services discovered.

    Regards,
    Marcel

    Mr.Pine <pine5514@gmail.com <mailto:pine5514@gmail.com>> schrieb am
    Mo., 26. Dez. 2016 12:38:

        hi,
        I recently added an old d-link switch but can not get any output
        from discovery!
        try to run cmk command
        OMD[me]:~$ snmpwalk -v1 -c 'public' 172.16.0.2 sysDescr
        SNMPv2-MIB::sysDescr.0 = STRING: D-Link DES-3052P Fast Ethernet
        Switch

        but this command give me a very long output. :
        OMD[me]:~$ snmpwalk -v1 -c 'EHSANALISNMP' 172.16.0.2

        for eg:
        ...
        IF-MIB::ifIndex.1232 = INTEGER: 1232
        IF-MIB::ifIndex.1233 = INTEGER: 1233
        IF-MIB::ifIndex.1234 = INTEGER: 1234
        IF-MIB::ifIndex.1235 = INTEGER: 1235
        IF-MIB::ifIndex.1236 = INTEGER: 1236
        IF-MIB::ifIndex.1237 = INTEGER: 1237
        IF-MIB::ifIndex.1238 = INTEGER: 1238
        IF-MIB::ifIndex.1239 = INTEGER: 1239
        IF-MIB::ifIndex.1240 = INTEGER: 1240
        IF-MIB::ifIndex.1241 = INTEGER: 1241
        IF-MIB::ifIndex.1242 = INTEGER: 1242
        IF-MIB::ifIndex.1243 = INTEGER: 1243
        IF-MIB::ifIndex.1244 = INTEGER: 1244
        IF-MIB::ifIndex.1245 = INTEGER: 1245
        IF-MIB::ifIndex.1246 = INTEGER: 1246
        IF-MIB::ifIndex.1247 = INTEGER: 1247
        IF-MIB::ifIndex.1248 = INTEGER: 1248
        IF-MIB::ifIndex.1249 = INTEGER: 1249
        IF-MIB::ifIndex.1250 = INTEGER: 1250
        IF-MIB::ifIndex.1251 = INTEGER: 1251
        IF-MIB::ifIndex.1252 = INTEGER: 1252
        IF-MIB::ifIndex.1253 = INTEGER: 1253
        IF-MIB::ifIndex.1254 = INTEGER: 1254
        IF-MIB::ifIndex.1255 = INTEGER: 1255
        IF-MIB::ifIndex.1256 = INTEGER: 1256
        IF-MIB::ifIndex.1257 = INTEGER: 1257
        IF-MIB::ifIndex.1258 = INTEGER: 1258
        ....

        any help?!
        _______________________________________________
        checkmk-en mailing list
        checkmk-en@lists.mathias-kettner.de
        <mailto:checkmk-en@lists.mathias-kettner.de>
        http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en
        <http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en&gt;

_______________________________________________
checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de
http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

5

I think there is sth with my sw configuration!!
my sw has only 52 ports but snmp output shows me many extra ports (1024 to 5117). it taks a lot of time and check_mk web gui got timeout from apache.

any help?!

#snmpwalk -On -v1 -c ‘mycom’ 172.16.0.7 ifOperStatus

.1.3.6.1.2.1.2.2.1.8.1 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.2 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.3 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.4 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.5 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.6 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.7 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.8 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.9 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.10 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.11 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.12 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.13 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.14 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.15 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.16 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.17 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.18 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.19 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.20 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.21 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.22 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.23 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.24 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.25 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.26 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.27 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.28 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.29 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.30 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.31 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.32 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.33 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.34 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.35 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.36 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.37 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.38 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.39 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.40 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.41 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.42 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.43 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.44 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.45 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.46 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.47 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.48 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.49 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.50 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.51 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.52 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1024 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1025 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1026 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1027 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1028 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1029 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1030 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1031 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1032 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1033 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1034 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1035 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1036 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1037 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1038 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1039 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1040 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1041 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1042 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1043 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1044 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1045 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1046 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1047 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1048 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1049 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1050 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1051 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1052 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1053 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1054 = INTEGER: up(1)

…

.1.3.6.1.2.1.2.2.1.8.5117 = INTEGER: up(1)

···

On Tue, Dec 27, 2016 at 8:29 PM, Evy Bongers lists+check-mk@evybongers.nl wrote:

That your first example lists only a single line is easy to explain. In

your command, you tell snmpwalk to only walk a specific OID: sysDescr.

Also, I notice in your commands, that for the second one you specify a

different community. Depending on how you configured your switch, more

or less information may be available depending on the community specified.

Regards,

Evy

On 26/12/16 17:08, Mr.Pine wrote:

try with snmp-v1 , got the same output.

On Mon, Dec 26, 2016 at 7:22 PM, Marcel Schulte

<schulte.marcel@gmail.com mailto:schulte.marcel@gmail.com> wrote:

Configure the host to get polled with snmp-v1 in WATO and you should

get some services discovered.

Regards,

Marcel

Mr.Pine <pine5514@gmail.com <mailto:pine5514@gmail.com>> schrieb am
Mo., 26. Dez. 2016 12:38:

    hi,

    I recently added an old d-link switch but can not get any output

    from discovery!

    try to run cmk command

    OMD[me]:~$ snmpwalk -v1 -c 'public' 172.16.0.2 sysDescr

    SNMPv2-MIB::sysDescr.0 = STRING: D-Link DES-3052P Fast Ethernet

    Switch

    but this command give me a very long output. :

    OMD[me]:~$ snmpwalk -v1 -c 'EHSANALISNMP' 172.16.0.2

    for eg:

    ...

    IF-MIB::ifIndex.1232 = INTEGER: 1232

    IF-MIB::ifIndex.1233 = INTEGER: 1233

    IF-MIB::ifIndex.1234 = INTEGER: 1234

    IF-MIB::ifIndex.1235 = INTEGER: 1235

    IF-MIB::ifIndex.1236 = INTEGER: 1236

    IF-MIB::ifIndex.1237 = INTEGER: 1237

    IF-MIB::ifIndex.1238 = INTEGER: 1238

    IF-MIB::ifIndex.1239 = INTEGER: 1239

    IF-MIB::ifIndex.1240 = INTEGER: 1240

    IF-MIB::ifIndex.1241 = INTEGER: 1241

    IF-MIB::ifIndex.1242 = INTEGER: 1242

    IF-MIB::ifIndex.1243 = INTEGER: 1243

    IF-MIB::ifIndex.1244 = INTEGER: 1244

    IF-MIB::ifIndex.1245 = INTEGER: 1245

    IF-MIB::ifIndex.1246 = INTEGER: 1246

    IF-MIB::ifIndex.1247 = INTEGER: 1247

    IF-MIB::ifIndex.1248 = INTEGER: 1248

    IF-MIB::ifIndex.1249 = INTEGER: 1249

    IF-MIB::ifIndex.1250 = INTEGER: 1250

    IF-MIB::ifIndex.1251 = INTEGER: 1251

    IF-MIB::ifIndex.1252 = INTEGER: 1252

    IF-MIB::ifIndex.1253 = INTEGER: 1253

    IF-MIB::ifIndex.1254 = INTEGER: 1254

    IF-MIB::ifIndex.1255 = INTEGER: 1255

    IF-MIB::ifIndex.1256 = INTEGER: 1256

    IF-MIB::ifIndex.1257 = INTEGER: 1257

    IF-MIB::ifIndex.1258 = INTEGER: 1258

    ....

    any help?!

    _______________________________________________

    checkmk-en mailing list

    checkmk-en@lists.mathias-kettner.de

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

    <mailto:checkmk-en@lists.mathias-kettner.de>

    [http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)

    <[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)>
6

For the timing issue:

If the switch supports SNMP v2c (not sure if it does) best use that instead of v1 and use snmpbulkwalk instead of snmpwalk
(in Check_MK that is).

Could be a bit faster.

Port count:

The >1024 values could be other port settings (like VLAN status, PoE power status), although it seems more sensible to
me to place that kind of info in other OID’s.

I guess you should check the manual (or google
J ) to see what’s in
this OID (and possibly write your own SNMP script for this type of switch).

Arno Wijnhoven

On Behalf Of Mr.Pine

···

I think there is sth with my sw configuration!!

my sw has only 52 ports but snmp output shows me many extra ports (1024 to
5117). it taks a lot of time and check_mk web gui got timeout from apache.

any help?!

#snmpwalk -On -v1 -c ‘mycom’ 172.16.0.7 ifOperStatus

.1.3.6.1.2.1.2.2.1.8.1 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.2 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.3 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.4 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.5 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.6 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.7 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.8 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.9 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.10 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.11 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.12 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.13 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.14 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.15 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.16 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.17 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.18 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.19 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.20 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.21 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.22 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.23 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.24 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.25 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.26 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.27 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.28 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.29 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.30 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.31 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.32 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.33 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.34 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.35 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.36 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.37 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.38 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.39 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.40 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.41 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.42 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.43 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.44 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.45 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.46 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.47 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.48 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.49 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.50 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.51 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.52 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1024 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1025 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1026 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1027 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1028 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1029 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1030 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1031 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1032 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1033 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1034 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1035 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1036 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1037 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1038 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1039 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1040 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1041 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1042 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1043 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1044 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1045 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1046 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1047 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1048 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1049 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1050 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1051 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1052 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1053 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1054 = INTEGER: up(1)

…

.1.3.6.1.2.1.2.2.1.8.5117 = INTEGER: up(1)

On Tue, Dec 27, 2016 at 8:29 PM, Evy Bongers lists+check-mk@evybongers.nl wrote:

That your first example lists only a single line is easy to explain. In
your command, you tell snmpwalk to only walk a specific OID: sysDescr.

Also, I notice in your commands, that for the second one you specify a
different community. Depending on how you configured your switch, more
or less information may be available depending on the community specified.

Regards,

Evy

On 26/12/16 17:08, Mr.Pine wrote:

try with snmp-v1 , got the same output.

On Mon, Dec 26, 2016 at 7:22 PM, Marcel Schulte
<schulte.marcel@gmail.com mailto:schulte.marcel@gmail.com> wrote:

Configure the host to get polled with snmp-v1 in WATO and you should
get some services discovered.

Regards,
Marcel


Mr.Pine <pine5514@gmail.com <mailto:pine5514@gmail.com>> schrieb am

Mo., 26. Dez. 2016 12:38:

    hi,
    I recently added an old d-link switch but can not get any output
    from discovery!
    try to run cmk command
    OMD[me]:~$ snmpwalk -v1 -c 'public' 172.16.0.2 sysDescr
    SNMPv2-MIB::sysDescr.0 = STRING: D-Link DES-3052P Fast Ethernet
    Switch

    but this command give me a very long output. :
    OMD[me]:~$ snmpwalk -v1 -c 'EHSANALISNMP' 172.16.0.2

    for eg:
    ...
    IF-MIB::ifIndex.1232 = INTEGER: 1232
    IF-MIB::ifIndex.1233 = INTEGER: 1233
    IF-MIB::ifIndex.1234 = INTEGER: 1234
    IF-MIB::ifIndex.1235 = INTEGER: 1235
    IF-MIB::ifIndex.1236 = INTEGER: 1236
    IF-MIB::ifIndex.1237 = INTEGER: 1237
    IF-MIB::ifIndex.1238 = INTEGER: 1238
    IF-MIB::ifIndex.1239 = INTEGER: 1239
    IF-MIB::ifIndex.1240 = INTEGER: 1240
    IF-MIB::ifIndex.1241 = INTEGER: 1241
    IF-MIB::ifIndex.1242 = INTEGER: 1242
    IF-MIB::ifIndex.1243 = INTEGER: 1243
    IF-MIB::ifIndex.1244 = INTEGER: 1244
    IF-MIB::ifIndex.1245 = INTEGER: 1245
    IF-MIB::ifIndex.1246 = INTEGER: 1246
    IF-MIB::ifIndex.1247 = INTEGER: 1247
    IF-MIB::ifIndex.1248 = INTEGER: 1248
    IF-MIB::ifIndex.1249 = INTEGER: 1249
    IF-MIB::ifIndex.1250 = INTEGER: 1250
    IF-MIB::ifIndex.1251 = INTEGER: 1251
    IF-MIB::ifIndex.1252 = INTEGER: 1252
    IF-MIB::ifIndex.1253 = INTEGER: 1253
    IF-MIB::ifIndex.1254 = INTEGER: 1254
    IF-MIB::ifIndex.1255 = INTEGER: 1255
    IF-MIB::ifIndex.1256 = INTEGER: 1256
    IF-MIB::ifIndex.1257 = INTEGER: 1257
    IF-MIB::ifIndex.1258 = INTEGER: 1258
    ....

    any help?!
    _______________________________________________
    checkmk-en mailing list
    checkmk-en@lists.mathias-kettner.de

    <mailto:checkmk-en@lists.mathias-kettner.de>
    [http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
    <[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)>

checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

7

TNN for your reply
I try to find out the interface type of 1024 to 5117. got this :

…

.1.3.6.1.2.1.2.2.1.2.51 = “RMON Port 51 on Unit 1”

.1.3.6.1.2.1.2.2.1.2.52 = “RMON Port 52 on Unit 1”

.1.3.6.1.2.1.2.2.1.2.1024 = “802.1Q Encapsulation Tag 0001”

.1.3.6.1.2.1.2.2.1.2.1025 = “802.1Q Encapsulation Tag 0002”

.1.3.6.1.2.1.2.2.1.2.1026 = “802.1Q Encapsulation Tag 0003”

.1.3.6.1.2.1.2.2.1.2.1027 = “802.1Q Encapsulation Tag 0004”

…

#check_mk --debug -II Swich1
Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.1.1.0’

SNMP answer: ==> [“D-Link DES-3052P Fast Ethernet Switch”]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.231.2.10.2.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.1.2.0’

SNMP answer: ==> [.1.3.6.1.4.1.171.10.63.9]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.232.2.2.4.2.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.1.6.0’

SNMP answer: ==> [“”]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.43.11.1.1.6.1.1’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.13742.6.3.2.1.1.3.1’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.43.10.2.1.4.1.1’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.14848.2.1.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.25.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.789.1.2.1.3.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.1.4.0’

SNMP answer: ==> [“”]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.8691.10.2242.2.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.789.1.17.20.0’

Running ‘snmpgetnext -Cf -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.31.1.1.1.6’

SNMP answer: ==> [1]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.6302.2.1.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.9.9.48.1.1.1.6.1’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.1602.1.1.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.2.1.0’

SNMP answer: ==> [4147]

Running ‘snmpgetnext -Cf -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.31.1.1.1.6’

SNMP answer: ==> [1]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.33.1.1.1.0’

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.2.2.1.8.1

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.2.2.1.8.2

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.2.2.1.8.3

[[‘1’, ‘2’, ‘2’]]

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.1.0

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.4.0

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.5.0

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.6.0

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.3.0

···

On Mon, Jan 2, 2017 at 6:20 PM, Arno Wijnhoven arnow@vsnsystemen.nl wrote:

For the timing issue:

If the switch supports SNMP v2c (not sure if it does) best use that instead of v1 and use snmpbulkwalk instead of snmpwalk
(in Check_MK that is).

Could be a bit faster.

Port count:

The >1024 values could be other port settings (like VLAN status, PoE power status), although it seems more sensible to
me to place that kind of info in other OID’s.

I guess you should check the manual (or google
J ) to see what’s in
this OID (and possibly write your own SNMP script for this type of switch).

Arno Wijnhoven

From: checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Mr.Pine
Sent: maandag 2 januari 2017 08:20
To: Evy Bongers lists+check-mk@evybongers.nl
Cc: checkmk-en checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] too many snmp output

I think there is sth with my sw configuration!!

my sw has only 52 ports but snmp output shows me many extra ports (1024 to
5117). it taks a lot of time and check_mk web gui got timeout from apache.

any help?!

#snmpwalk -On -v1 -c ‘mycom’ 172.16.0.7 ifOperStatus

.1.3.6.1.2.1.2.2.1.8.1 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.2 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.3 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.4 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.5 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.6 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.7 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.8 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.9 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.10 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.11 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.12 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.13 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.14 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.15 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.16 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.17 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.18 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.19 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.20 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.21 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.22 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.23 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.24 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.25 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.26 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.27 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.28 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.29 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.30 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.31 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.32 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.33 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.34 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.35 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.36 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.37 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.38 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.39 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.40 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.41 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.42 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.43 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.44 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.45 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.46 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.47 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.48 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.49 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.50 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.51 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.52 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1024 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1025 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1026 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1027 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1028 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1029 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1030 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1031 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1032 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1033 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1034 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1035 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1036 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1037 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1038 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1039 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1040 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1041 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1042 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1043 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1044 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1045 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1046 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1047 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1048 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1049 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1050 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1051 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1052 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1053 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1054 = INTEGER: up(1)

…

.1.3.6.1.2.1.2.2.1.8.5117 = INTEGER: up(1)

On Tue, Dec 27, 2016 at 8:29 PM, Evy Bongers lists+check-mk@evybongers.nl wrote:

That your first example lists only a single line is easy to explain. In
your command, you tell snmpwalk to only walk a specific OID: sysDescr.

Also, I notice in your commands, that for the second one you specify a
different community. Depending on how you configured your switch, more
or less information may be available depending on the community specified.

Regards,

Evy

On 26/12/16 17:08, Mr.Pine wrote:

try with snmp-v1 , got the same output.

On Mon, Dec 26, 2016 at 7:22 PM, Marcel Schulte
<schulte.marcel@gmail.com mailto:schulte.marcel@gmail.com> wrote:

Configure the host to get polled with snmp-v1 in WATO and you should
get some services discovered.

Regards,
Marcel


Mr.Pine <pine5514@gmail.com <mailto:pine5514@gmail.com>> schrieb am

Mo., 26. Dez. 2016 12:38:

    hi,
    I recently added an old d-link switch but can not get any output
    from discovery!
    try to run cmk command
    OMD[me]:~$ snmpwalk -v1 -c 'public' 172.16.0.2 sysDescr
    SNMPv2-MIB::sysDescr.0 = STRING: D-Link DES-3052P Fast Ethernet
    Switch

    but this command give me a very long output. :
    OMD[me]:~$ snmpwalk -v1 -c 'EHSANALISNMP' 172.16.0.2

    for eg:
    ...
    IF-MIB::ifIndex.1232 = INTEGER: 1232
    IF-MIB::ifIndex.1233 = INTEGER: 1233
    IF-MIB::ifIndex.1234 = INTEGER: 1234
    IF-MIB::ifIndex.1235 = INTEGER: 1235
    IF-MIB::ifIndex.1236 = INTEGER: 1236
    IF-MIB::ifIndex.1237 = INTEGER: 1237
    IF-MIB::ifIndex.1238 = INTEGER: 1238
    IF-MIB::ifIndex.1239 = INTEGER: 1239
    IF-MIB::ifIndex.1240 = INTEGER: 1240
    IF-MIB::ifIndex.1241 = INTEGER: 1241
    IF-MIB::ifIndex.1242 = INTEGER: 1242
    IF-MIB::ifIndex.1243 = INTEGER: 1243
    IF-MIB::ifIndex.1244 = INTEGER: 1244
    IF-MIB::ifIndex.1245 = INTEGER: 1245
    IF-MIB::ifIndex.1246 = INTEGER: 1246
    IF-MIB::ifIndex.1247 = INTEGER: 1247
    IF-MIB::ifIndex.1248 = INTEGER: 1248
    IF-MIB::ifIndex.1249 = INTEGER: 1249
    IF-MIB::ifIndex.1250 = INTEGER: 1250
    IF-MIB::ifIndex.1251 = INTEGER: 1251
    IF-MIB::ifIndex.1252 = INTEGER: 1252
    IF-MIB::ifIndex.1253 = INTEGER: 1253
    IF-MIB::ifIndex.1254 = INTEGER: 1254
    IF-MIB::ifIndex.1255 = INTEGER: 1255
    IF-MIB::ifIndex.1256 = INTEGER: 1256
    IF-MIB::ifIndex.1257 = INTEGER: 1257
    IF-MIB::ifIndex.1258 = INTEGER: 1258
    ....

    any help?!
    _______________________________________________

    checkmk-en mailing list

    checkmk-en@lists.mathias-kettner.de

    <mailto:checkmk-en@lists.mathias-kettner.de>
    [http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
    <[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)>

checkmk-en mailing list

checkmk-en@lists.mathias-kettner.de


http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en

8

802.1Q Encapsulation Tag 0001 =
VLAN stuff, but I’m not sure how it’s used on your switch.

Encapsulation Tag 0001 is VLAN1 I think, 0002 = VLAN2 etc.

Anyhow, you probably don’t need this stuff for regular port status.

As far as I know this means creating your own D-Link SNMP script in Python (or find a script that someone else wrote,
you’re probably not the first to bump into this issue).

Perhaps anyone else on this mailing list is aware of any settings to ignore these ‘additional entries’.

Arno Wijnhoven

T: 2580

···

TNN for your reply

I try to find out the interface type of 1024 to 5117. got this :

…

.1.3.6.1.2.1.2.2.1.2.51 = “RMON Port 51 on Unit 1”

.1.3.6.1.2.1.2.2.1.2.52 = “RMON Port 52 on Unit 1”

.1.3.6.1.2.1.2.2.1.2.1024 = “802.1Q Encapsulation Tag 0001”

.1.3.6.1.2.1.2.2.1.2.1025 = “802.1Q Encapsulation Tag 0002”

.1.3.6.1.2.1.2.2.1.2.1026 = “802.1Q Encapsulation Tag 0003”

.1.3.6.1.2.1.2.2.1.2.1027 = “802.1Q Encapsulation Tag 0004”

…

#check_mk --debug -II Swich1

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.1.1.0’

SNMP answer: ==> [“D-Link DES-3052P Fast Ethernet Switch”]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.231.2.10.2.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.1.2.0’

SNMP answer: ==> [.1.3.6.1.4.1.171.10.63.9]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.232.2.2.4.2.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.1.6.0’

SNMP answer: ==> [“”]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.43.11.1.1.6.1.1’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.13742.6.3.2.1.1.3.1’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.43.10.2.1.4.1.1’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.14848.2.1.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.25.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.789.1.2.1.3.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.1.4.0’

SNMP answer: ==> [“”]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.8691.10.2242.2.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.789.1.17.20.0’

Running ‘snmpgetnext -Cf -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.31.1.1.1.6’

SNMP answer: ==> [1]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.6302.2.1.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.9.9.48.1.1.1.6.1’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.4.1.1602.1.1.1.1.0’

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.2.1.0’

SNMP answer: ==> [4147]

Running ‘snmpgetnext -Cf -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.31.1.1.1.6’

SNMP answer: ==> [1]

Running ‘snmpget -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -On -OQ -Oe -Ot 172.16.0.7 .1.3.6.1.2.1.33.1.1.1.0’

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.2.2.1.8.1

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.2.2.1.8.2

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.2.2.1.8.3

[[‘1’, ‘2’, ‘2’]]

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.1.0

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.4.0

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.5.0

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.6.0

Running snmpwalk -v1 -c ‘mypub’ -m ‘’ -M ‘’ -t 5.00 -r 2 -Cc -OQ -OU -On -Ot 172.16.0.7 .1.3.6.1.2.1.1.3.0

On Mon, Jan 2, 2017 at 6:20 PM, Arno Wijnhoven arnow@vsnsystemen.nl wrote:

For the timing issue:

If the switch supports SNMP v2c (not sure if it does) best use that instead of v1 and
use snmpbulkwalk instead of snmpwalk (in Check_MK that is).

Could be a bit faster.

Port count:

The >1024 values could be other port settings (like VLAN status, PoE power status), although
it seems more sensible to me to place that kind of info in other OID’s.

I guess you should check the manual (or google
J ) to see what’s in this OID (and possibly write your own SNMP script for
this type of switch).

Arno Wijnhoven

From:
checkmk-en-bounces@lists.mathias-kettner.de [mailto:checkmk-en-bounces@lists.mathias-kettner.de]
On Behalf Of Mr.Pine
Sent: maandag 2 januari 2017 08:20
To: Evy Bongers lists+check-mk@evybongers.nl
Cc: checkmk-en checkmk-en@lists.mathias-kettner.de
Subject: Re: [Check_mk (english)] too many snmp output

I think there is sth with my sw configuration!!

my sw has only 52 ports but snmp output shows me many extra ports (1024 to
5117). it taks a lot of time and check_mk web gui got timeout from apache.

any help?!

#snmpwalk -On -v1 -c ‘mycom’ 172.16.0.7 ifOperStatus

.1.3.6.1.2.1.2.2.1.8.1 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.2 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.3 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.4 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.5 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.6 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.7 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.8 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.9 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.10 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.11 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.12 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.13 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.14 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.15 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.16 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.17 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.18 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.19 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.20 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.21 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.22 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.23 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.24 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.25 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.26 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.27 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.28 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.29 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.30 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.31 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.32 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.33 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.34 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.35 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.36 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.37 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.38 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.39 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.40 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.41 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.42 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.43 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.44 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.45 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.46 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.47 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.48 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.49 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.50 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.51 = INTEGER: down(2)

.1.3.6.1.2.1.2.2.1.8.52 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1024 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1025 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1026 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1027 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1028 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1029 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1030 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1031 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1032 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1033 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1034 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1035 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1036 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1037 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1038 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1039 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1040 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1041 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1042 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1043 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1044 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1045 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1046 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1047 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1048 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1049 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1050 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1051 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1052 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1053 = INTEGER: up(1)

.1.3.6.1.2.1.2.2.1.8.1054 = INTEGER: up(1)

…

.1.3.6.1.2.1.2.2.1.8.5117 = INTEGER: up(1)

On Tue, Dec 27, 2016 at 8:29 PM, Evy Bongers lists+check-mk@evybongers.nl wrote:

That your first example lists only a single line is easy to explain. In
your command, you tell snmpwalk to only walk a specific OID: sysDescr.

Also, I notice in your commands, that for the second one you specify a
different community. Depending on how you configured your switch, more
or less information may be available depending on the community specified.

Regards,

Evy

On 26/12/16 17:08, Mr.Pine wrote:

try with snmp-v1 , got the same output.

On Mon, Dec 26, 2016 at 7:22 PM, Marcel Schulte
<schulte.marcel@gmail.com mailto:schulte.marcel@gmail.com> wrote:

Configure the host to get polled with snmp-v1 in WATO and you should
get some services discovered.

Regards,
Marcel


Mr.Pine <pine5514@gmail.com <mailto:pine5514@gmail.com>> schrieb am

Mo., 26. Dez. 2016 12:38:

    hi,
    I recently added an old d-link switch but can not get any output
    from discovery!
    try to run cmk command
    OMD[me]:~$ snmpwalk -v1 -c 'public' 172.16.0.2 sysDescr
    SNMPv2-MIB::sysDescr.0 = STRING: D-Link DES-3052P Fast Ethernet
    Switch

    but this command give me a very long output. :
    OMD[me]:~$ snmpwalk -v1 -c 'EHSANALISNMP' 172.16.0.2

    for eg:
    ...
    IF-MIB::ifIndex.1232 = INTEGER: 1232
    IF-MIB::ifIndex.1233 = INTEGER: 1233
    IF-MIB::ifIndex.1234 = INTEGER: 1234
    IF-MIB::ifIndex.1235 = INTEGER: 1235
    IF-MIB::ifIndex.1236 = INTEGER: 1236
    IF-MIB::ifIndex.1237 = INTEGER: 1237
    IF-MIB::ifIndex.1238 = INTEGER: 1238
    IF-MIB::ifIndex.1239 = INTEGER: 1239
    IF-MIB::ifIndex.1240 = INTEGER: 1240
    IF-MIB::ifIndex.1241 = INTEGER: 1241
    IF-MIB::ifIndex.1242 = INTEGER: 1242
    IF-MIB::ifIndex.1243 = INTEGER: 1243
    IF-MIB::ifIndex.1244 = INTEGER: 1244
    IF-MIB::ifIndex.1245 = INTEGER: 1245
    IF-MIB::ifIndex.1246 = INTEGER: 1246
    IF-MIB::ifIndex.1247 = INTEGER: 1247
    IF-MIB::ifIndex.1248 = INTEGER: 1248
    IF-MIB::ifIndex.1249 = INTEGER: 1249
    IF-MIB::ifIndex.1250 = INTEGER: 1250
    IF-MIB::ifIndex.1251 = INTEGER: 1251
    IF-MIB::ifIndex.1252 = INTEGER: 1252
    IF-MIB::ifIndex.1253 = INTEGER: 1253
    IF-MIB::ifIndex.1254 = INTEGER: 1254
    IF-MIB::ifIndex.1255 = INTEGER: 1255
    IF-MIB::ifIndex.1256 = INTEGER: 1256
    IF-MIB::ifIndex.1257 = INTEGER: 1257
    IF-MIB::ifIndex.1258 = INTEGER: 1258
    ....

    any help?!
    _______________________________________________
    checkmk-en mailing list
    checkmk-en@lists.mathias-kettner.de

    <mailto:checkmk-en@lists.mathias-kettner.de>
    [http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)
    <[http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en](http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en)>

checkmk-en mailing list
checkmk-en@lists.mathias-kettner.de

http://lists.mathias-kettner.de/mailman/listinfo/checkmk-en