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

Switchport Mapper and Nexus Nx-os

I am migrating from Catalyst 6500 switches to Nexus 9500 switches but switch port mapper is not returning IP, DNS, etc for any of the ports. I am trying to figure out what is wrong.

I am using SNMP v2c on the switch and SNMP v3 on the Layer 3 switch to gather the data.

Anyone else experiencing this with NX-OS. It works correctly with Catalyst IOS devices.

Find more posts tagged with

Accepted answers

All comments

kurtrh

SolarWinds is working on getting the Nexus Product line integrated into Engineers Toolset. I run into this problem with the Nexus 5k, 7k series.

jkump

Good to hear. The drawback is that I utilize the tool all the time to determine device connections, etc. Now, I don't have a usable way of doing that without manually performing the tasks of showing the IP arp table and then tracking the MAC address. Hopefully, they will get it updated soon. We are looking at purchasing the SW UDT but that will not be until the next fiscal year.

cpacifico

I have a client that we just migrated to Nexus switches as well....I am having the same issue, not a big deal right now as it is not in production yet, but will be soon......

jkump

I ended up for another reason enabling IP Routing on my switches. At least then, I can use the option for layer 3 from the switch to map out my ports. It is not ideal but at least I get the necessary data that I need when I need it. Just waiting patiently for the tool to be updated........

rschroeder

I, too, have this same problem with Switch Port Mapper and DNS output from Nexus switches.

If you are aware of a fix or an efficient work around, I'd love to learn it.

jkump

A slight update that I have not had a chance to test in SW. I download another application for a remote clinic and it had a feature with more detail that Switch Port Mapper. However, it could not handle SNMPv3 at all. I needed to resolve an issue so I temporary enabled a SNMPv2c community string on both the target switch and one of my NX-OS boxes. It was able to produce the desired result. I have it on my list to try that in SW but I have not yet got to that list. If you try it, please update and advise.

THanks!

rschroeder

I'm slightly confused by your comment. Are you saying the different application provided the desired result, or is your hypothesis that snmp-v2 works better than snmp-v3 for Solarwinds Switch Port Mapper working with Nexus?

I've tried snmp-v2--it does not get the Nexus hardware to provide the DNS info to Switch Port Mapper.

What other snmp-based switch port mapper application did you try, which got you the information you expected, but did not receive, from Solarwinds Switch Port Mapper?

jkump

Sorry, did not mean to confuse. I used version 4 of the Switch Miner application. I found it on SourceForge. SwitchMiner | Switch Port Mapper | Switch Port Mapping | Port Mapping | Port Mapper

So, I configured my target by re-enabling v2c with a community string. I also put the same v2c community string on the Core NX-OS box. I was then able to use SM (SwitchMiner) to extract all the details provided from Switch Port Mapper plus some additional details.

I do not really want the plaintext v2c running but I enable when I need it and disable when I am done. Not quite as convenient but .....

Also, I have not tried to do the same thing with Switch Port Mapper but I may ....

Hopes this removes some confusion. I really like the tool and really need it some times.