Problems with SNMP Bridge-Mib dot1dBasePortIfIndex

Unanswered Question
Sep 22nd, 2010

Hi,

I'm experiencing a strange issue. I have two Cat4000 L3's running:

IOS (tm) Catalyst 4000 L3 Switch Software (cat4000-I9S-M), Version 12.2(20)EWA4, RELEASE SOFTWARE (fc2)

both with ROM 12.2(31r)SGA1

Both switches were purchased at the same time, have the same image installed from the same TFTP server, and are configured identically with respect to features, SNMP, etc. I even diffed the configs and only vlans, VTP domain, and interfaces are different.

I have a homegrown PHP script that does a SNMP walk, correlates MAC addresses with ports, and then integrates this into our documentation wiki (for all connected devices, the wiki has their MAC addresses, the script automatically updates with switch and port number).

On one switch, I can walk .1.3.6.1.2.1.17.1.4.1.2 (BRIDGE-MIB::dot1dBasePortIfIndex) fine using community string indexing, and I get back correct results. On the second switch, I don't get any results at all, for any VLAN...

Any suggestions? This really has me stumped, granted I'm more of a programmer than a netadmin...

Thanks,

Jason

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
Loading.
jason.gomes@bt.com Sat, 05/07/2016 - 04:35

This is an old post, but was looking for solution to similar problem

To work on some switches it seams, the dot1dBasePortIfIndex table is virtualised

In order work you need to append VLAN ID to the string after adding @ symbol.

  • snmpwalk -c Community@<vlan> -v 2c 10.29.123.1 .1.3.6.1.2.1.17.1.4.1.2
  • snmpwalk -c public@54 -v 2c 10.29.123.1 .1.3.6.1.2.1.17.1.4.1.2

My problem was different. Discovered today a bug on our old 4507R's

Catalyst 4000 L3 Switch Software (cat4000-I5K91S-M), Version 12.2(25)EWA6

We have '@' in our community String:

It does not work Cat4k, but works fine other newer switches

  • snmpwalk -c C@mmunity@<vlan> -v 2c 10.29.123.1 .1.3.6.1.2.1.17.1.4.1.2 

Whe removing @ symbol from string it works fine on Cat4k

  • snmpwalk -c Community@<vlan> -v 2c 10.69.123.1 .1.3.6.1.2.1.17.1.4.1.2 

Hope this helps somehow searching for same issues.

Cheers,

Jason

Actions

This Discussion

Related Content