Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations wOOdy-Soft on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Autotopology woes

Status
Not open for further replies.

Guest_imported

New member
Jan 1, 1970
0
I've run the Autotopology a number of times and for some reason, one of our stacks (two BS450 cascaded switches) is identified as a generic router while two other stacks (also BS450s) aren't identified at all. I do have some success as three other stacks are properly identified and connected. I'm attempting to manually input the data on the missing devices but it's proving to be a difficult task to say the least. Any ideas? I've already looked at the community strings and they are all the same.
 
Update: I managed to get Autotopology to detect the missing switches by editting the topology.cnf file on the Optivity server. I changed the value of 'beyond_arp_enable' from 0 to 2 and then re-ran Autotopology. It appeared to force Autotopoloy to scan every IP address in the detected subnets looking for devices as opposed to only scanning IP addresses from the router's ARP table. Presto, there are all the switches. Unfortunately I still have the BS450 switch being detected as a router problem. Any idea anyone?
 
Check the version of code on your 450 switches.You should be at version 3.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top