Application Error: Object reference not set to an instance of an object

once I click on OK the app,  it dies and discovery stops.

Anytime that WhatsConnected is experiencing discovery failures, we can usually get a long way to tracking them down when we look at the discovery.log file.

The discovery.log file is located under the WhatsConnected/Logs directory.  Please post it here along with your message and we will use that to determine the fault.

Thanks,

Brian

WhatsConnected Product Team

-Brian

WhatsConnected Product Team

I would think, since it does use CDP, ARP and SNMP, we should be able to get a pretty acrurate mapping of whats connected to that layer 2 switch.. For example- if I have 23 servers having off of a 3570 switch, WC should have the ability (because it is in WUG) to "ping" that device w/SNMP and pull the system info. I dont expect WC to be able to use any type of WMI or other discovery protocols for OS's but if SNMP is enabled, configured properly on the host, and is directly connected to a switch i am already discovering, then, to me anyway, it makes sense that we should reach out and see whats on the other end of that cable.

perhaps I am asking too much for this tool to be more like "lan surveyor" ? (hate to mention a competitor, but after all, thats what you guys want to do? make something we buy from you instead of your competition?

Don Click
Network Manager
Denton County, Texas

Are you specifying an INCLUDE scope or just a SEED IP Scope.

When you configure the discovery engine with an INCLUDE scope or a specific IP range in a PING sweep; it will stay inside that range and not use SNMP to "see" other devices that might be connected but are on other IP ranges /subnets.

So, can you give me some details on the discover scope setup.

Thanks,

Brian

WhatsConnected Product Team

i came back and modified my original post, but if that isnt enough -  here is an example.

Lets say i have a server subnet - 192.168.3.0.  On that subnet, I have at least 2 switches (.2 and .3) When I "discover" that subnet, using that ip range (ping, not arp) AND put in the read only snmp values, I only get back my 2 switches. I would think I should get something on the other 153 servers/fiber switches/APC ups's/Avocent KVM's, etc - all of which have the SAME read only snmp values as my switches.   Again, maybe I am expecting to much out of the product "at this time" (hint).

If I scan my "backbone" subnet (85% of my switches are on the same VLAN/Subnet for easy management) it finds all my switches, routes and other things like a Cisco VGA (even though device type is "unknown") and it actually classified a Cisco NAM2 (Network Analysis Module) as a Wireless Access Point (um, huh?).

Don Click
Network Manager
Denton County, Texas

The problem you are having is that the discovery engine is trying to STAY inside the subnet range that you specified.

You can do create a discovery like:

ARP Cache discovery

IP Seed Scope: 192.168.3.0/24

No INCLUDE/No EXCLUDE

This will seed the discovery engine with all devices in the 192.168.3.0 range (PING through them) and then allow the ARP/CDP to take over and crawl and find the devices that are connected.

It won't work exactly like the use case scenario that you mentioned; but it is very similar.  We will look into the question you posted about examing the devices that are directly connected.