|Subject:||Re: [nv-l] Managing Layer-3 Switches with Switch Analyzer|
|From:||Michael Webb <email@example.com>|
|Date:||Fri, 24 Jun 2005 17:11:16 -0400|
|Delivery-date:||Fri, 24 Jun 2005 22:12:20 +0100|
The Layer-2 Status of all devices should be set to "unset" initially (blue). They will not have a value other than unset until a Vendor (V) event has been issued for each device.
We are using NetView 7.1.4 FP3 on windows with Switch analyzer. We have three Enterasys Layer-3 switches. Two of them are running in router mode and one is working on Layer2 only but has Layer-3 IOS installed. In the initial discovery of the network the devices were not discovered properly (they were in BadOID smartset) i manually edited the oid_to_type and oid_to_sym files to fix the problem.
Now the problem is the Layer-2 Status of these devices is set to "unset" when i run ovtopodump-X command, and in the IP MAP the Layer-2 status is "Unset or unknown" (Blued). What should i do to make them managable with Switch Analyzer? When i forcefully set the object type to switch (BH). Then the whole topology is disturbed. Any suggestions on how to FIX this?
Thanks in advance!
|<Prev in Thread]||Current Thread||[Next in Thread>|
|Previous by Date:||RE: [nv-l] Status Polling, Evans, Bill|
|Next by Date:||Re: [nv-l] Managing Layer-3 Switches with Switch Analyzer, usman . taokeer|
|Previous by Thread:||[nv-l] Managing Layer-3 Switches with Switch Analyzer, usman . taokeer|
|Next by Thread:||Re: [nv-l] Managing Layer-3 Switches with Switch Analyzer, usman . taokeer|
|Indexes:||[Date] [Thread] [Top] [All Lists]|
Archive operated by Skills 1st Ltd
See also: The NetView Web