Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Toolset V9 Port Mapper

Currently using V9.0.5 and have run into an issue running program against a Cisco 6509. I am getting the error message "Does not support the Bridge-Mib"

Has anyone ran into this yet? It worked fine in version 8.

Thanks,

Find more posts tagged with

mib_walk

version_9

SNMP

mib

Accepted answers

All comments

billsardine

I had the same problem and i got the following message

Thank you for contacting SolarWinds. I apologize for this inconvinence, this issue is currently being researched by our Development Team. Once we have a resolution for you I will contact you.

support

If you have not done so already I encourage you to open a ticket with support and I would ask that you run a packet sniffer of the conversation between SwitchPort Mapper and the switch so that we can better diagnose the issue-

Don331

We have the same problem - I tried to submit a ticket, but you can't email a ticket in, and the friggin' WWW form doesn't let you attach files.

Ouch! (or Thwack!)

Don

mark_wiggans

Don-

You can add an attachment via the initial auto-reply you recieve after submitting a ticket to support-

acamilo

We are having the exact same problem. I called this morning and gave up waiting on the phone for support after 20 minutes. Opened a ticket this morning and I have yet to hear from them. I feel like we flushed $1200.00 down the drain.

mark_wiggans

The bridge-MIB error message could mean a couple of things- Sometimes this could be an error with credentials for that device-

What version of SNMP are you using with this device?

netbum

In working with their support team we did find an issue regarding the 6500's. They gave me a workaround and it will be fixed in an upcoming release.

Here is the work around.

Thank you so much for the help, development have found the issue and also have a workaround for it till we can roll this out.

Now if you do add the VLAN # after the community string it will return the info that you are looking for. For example if you want VLAN 12 then in the community string box put in

"[community string]@12" and this will return all the ports assigned to VLAN 12

But if you have multiple VLANS on the switch you will need to run it for each VLAN.

light

We have the problem too, my switch is 3com 4228G

Please,How to fix the problem

Thanks

light

leemcclendon

The switch port mapper problem that is described in this thread was fixed in version 9.0.1 which was released a little over a week ago. Are you experiencing the problem with the 3com switch with version 9.0.1 of the Toolset?

light

I upgrade Toolset v9 to v9.0.1,It's work fine

Thanks