ENMS 10.5 Autotopology

[k1tsos]

Hi there,

Has anyone ever had experience with the autotopology feature on the ENMS 10.5? It has two options, router based and routerless discovery. As you guessed it, routerless just pings whatever is out there, which is time consuming to say the least but at least it works.

The smart(er) apporach would be to query the IP for the router based topology search that is, the IP for the VRRP of a vlan on dual ers 8600. This IP is also the default gw for the enms server. As you probably guessed it, the autopology comes back with nothing.

Is there something i am missing? Shouldn't the ers 8600 report back every known device to the enms?

thanks

 

[anthonyanderberg]

I don't have direct experience with this product, but that's never stopped me from posting before...

Sometimes these kind of products will query the router/core ARP tables and L2 forwarding databases to build their device lists and maps.

Baystack switches have an autotopology feature (under the SNMP menu), as I recall this causes them to produce and process special packets that help them discover each other and their interconnections. There are also CLI commands related to autotopology - 'show autotopology nmm-table'.

Hope this helps,
anthony

 

[k1tsos]

thanks anthony,

the show-autopology on the es470 is helpful in identifying essentially the smlt partners but the problem is not between the edge and core switches, it is between the enms server and the core switches.

Before I open a case with nortel, I ll try and reinstall everything from the top.
Any more ideas are welcome though

 

[andy88]

It sounds like you are using the default discovery seed, where you don't add anf information and rely on the ENMS to discover via its default gateway.

Try using regular discovery by;

define a start address(Can be the gateway device, but use a real IP address rather than VRRP)

define subnet range.

Make sure you have the correct read/write SNMP string defined on all boxes and in ENMS.

 

[k1tsos]

Thnaks andy

Well, I reinstalled the enms and its oracle db and now the router based autopology works but as andy suggested only through a "real" IP not VRRP. Don't know what the problem was though. I suspect a screwed up database.

Now the only problem is that autotopology won't detect my VPN Router 1100 although my view domain is within range...I need to investigatet this more carefully. Thanks for all the help so far