NNM not discovering networks beyond WAN routers

[LadyeVon]

I'm having problems getting NNM to detect the networks for each router at all of the WAN sites. There are 100+ routers, all of which are the same router and the same config. I had to use loadhosts to get NNM to discover the routers, and now some routers show their networks, but others don't.

Is there some way to add a network that connects to the routers? Perhaps NNM isn't seeing the interface that connects to the LAN on that side?

Any ideas are greatly appreciated.
Thanks!

 

[bluedragon2]

A couple of things:

Can you ping the routers?

If they are on different subnets, do you have route statements to access those subnets?

 

[LadyeVon]

I can ping the routers and they're the same subnet.
I'm quite perplexed.

 

[bluedragon2]

Under the Fault menu/Network Connectivity/Trace Route, if you put in a router that is not listed, is it showing a route to it, and after you run the trace route, does OV pick it up?

Blue

 

[LadyeVon]

I don't have the tracert option on my menu... I'm trying to find where to add it. it's been awhile since i've messed with the registration files. AS soon as I get it working, I'll give that a shot.

Thanks.

 

[LadyeVon]

currently all my routers are in the topology. I removed one and used traceroute. After running traceroute, the device showed up but it's network did not.

 

[bluedragon2]

What happens if you run a traceroute on a device on the routers network?

 

[LadyeVon]

I don't have a list of devices on the other side of the network.. that's that division's responsibility, whereas routers and everything on our side is corporate's responsibility.

I've attempted a few ips that should bring something up, but no such luck. perhaps i'll write a script to find devices on their network.

 

[LadyeVon]

Ok, I turned off all my filters, once again. It appears taht all the devices which should be in the individual networks for each location (plant) router are going into the network that contains the routers. (ie. the division, not the location network). Any ideas for a fix?

 

[vlan52]

Hi LadyeVon, well, if you are able to perform a snmpwalk on some of this routers, the ones "closer" to your management server, and if the routers "know" every route to the next ones, NNM should discover everything properly.

Now, if, because of the subnet or supernet config. (net masks), and also depending on the IP addresing selected for the routers, they may show up in the same network or segment, which is not completly incorrect.

NNM is going to discover the devices through icmp + snmp, you've already told us you can get icmp replies, but are you getting snmp responses?Since NNM needs to get the routing tables + networks throught it.

Les us know please, regards,
vlan52


vlan52
The end of wisdom is freedom. The end of culture is perfection. The end of
education is character. The end of knowledge is love.

 

[LadyeVon]

Thanks so much for the help!

I wrote a script to traceroute all my plant routers, and that fixed the problem. It makes sense in hindsight.
Thanks again