Cannot Launch Solarwinds Mac Address Discovery
If they look identical there, then it is time to go to the device and see if the packet is making it there and if the device has SNMP logging, why I did an import on what was left. It also contains network discovery tools including a MAC address discovery tool, a port scanner and an SNMP scanner, just to list a few. When I ran it again with the first subnet, the topology data swapped back. have a peek at this web-site
Reply Josh Stephens says June 14, 2011 at 4:17 PM Thanks for the great review Ethan. Clicking the "New" button allows you to add a subnet name, subnet address, and subnet mask. If UDT is looking out for that host on your behalf, it make you more proactive and less reactive. When these nodes were detected via Scheduled discovery I added them to the ignore list because they already existed in Orion and the interfaces (uplinks) were already being monitored.
Frankly, the customer did not know what IP addresses were in use on their network. CDP would have all the needed information. And as for your suggestions... I'd like the scheduled discoveries to have an option of ONLY reporting on, and importing, interfaces that HAVE topology data AND are discoverable via SNMP-only.
Login to the Cisco device2. Does anyone know why on devices of the same make and model, same IOS, and using the same template for configuration these OID's are not getting populated? Each Juniper interface has a physical interface and one or more logical interfaces. that you've flagged pops up on the wire.
I ran workspace studio from the same machine NPM is running on and can poll the 3750's with same community string with out issue.I have no idea what it did but I had some challenges using the Google Chrome browser with UDT, although this complaint is not unique to the UDT product. The system returned: (22) Invalid argument The remote host or network may be down. check here Click the Columns tab, then select the columns to display in your discovery results.
First Name E-Mail Address * We will never share your personal information. Correct4. I did mean /16. Maybe a space snuck in there.Run the wireshark and do a poll now and a list resources on the same node and see what the difference in the packets is.Let me
If you delete a discovery profile, does the topology data already discovered get deleted? 1. Importing (to NPM) has no affect on the Scheduled Discovery Results. Obvious Apr 26, 2010 2:21 PM (in response to pyro13g) This could be due to an '@' symbol in your community string.On cisco devices the @ symbol indicates 'Community string indexing' Type logging monitor debugging 4.
You can use the drop-down filter to see all of the uses or available addresses on the network. Check This Out You'll note in the figure below that IP address management is listed in this quick start menu and that it's one of Solarwinds most used tools. for me, it works to connect switches (The only thing on VLAN 1). I'm sure it could be advanced to do things like DNS queries on the IP etc… but it works just fine for what we need.
why isn't it able to determine it is the same device as LANSurveyor does?thanks for the quick responses and work on this. Filed Under: Productivity, Reviews, Tutorials Tagged With: ip address management, nfd6, reviews, solarwinds Leave a Reply Cancel reply Your email address will not be published. all despite that NPM is correctly polling the 3750's still with snmp without issue... Source You're right.
seeing how you mentioned routers seem to need cdp it may be the reason I'm not getting topology data populated... Obvious and Karlo for helping me work this out :} Like Show 0 Likes(0) Actions Re: Connect Now Topology Discovery Problems Capt. How MAC address discovery works After you perform a discovery, the MAC Address Discovery tool allows you to transfer that information to other tools through exporting and copy and paste capabilities.
I'm imagining it's possible to fire off an Expect script to do something more powerful, though. (I guess I'll have to try that.) One thing UDT does not do in the
I really haven't found a common cause. I'd like the ability to ignore a node from discovery AND be able to delete a node directly from the Node Details "Node Details Resource"4. Is this in relation to the previous Discovery, or new to managed devices in NPM?Also, what triggers the Banner message on new devices? Here are the errors doing list resources or edit test snmp, and the same nodes current interface status gather with the snmp is says doesn't work:Seems like the same comm.
He co-hosts the Packet Pushers Weekly, Datanauts, and Citizens of Tech podcasts and co-chairs Interop's Infrastructure track. There is possible to add nodes into ignore list, import them or run discovery again. IE seemed to work reliably, although I dislike IE intensely. have a peek here Like Show 0 Likes(0) Actions Re: Connect Now Topology Discovery Problems ecklerwr1 Apr 26, 2010 4:02 PM (in response to Capt.
Using wireshark you can look at the bytes and the decoded SNMP to see what the difference is in the SNMP packets being sent.