To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | Re: [nv-l] Switch Analyzer and Enterasys Switches |
From: | Michael Webb <mlwebb@us.ibm.com> |
Date: | Tue, 10 May 2005 07:44:42 -0400 |
Delivery-date: | Tue, 10 May 2005 12:45:54 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <OF926FC022.CF295000-ON45256FFD.00364C36-45256FFD.0037FEED@s-iii.com> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
The accuracy and completeness of IBM Tivoli Switch Analyzer’s layer 2 discovery depends primarily on the availability of enough accurate information accessible from the Bridge MIB forwarding tables and certain private MIBs. The switch must support the RFC 1493 Bridge MIB, which is the minimum requirement for switch management. So technically we support them all if they, in turn, support the MIBs we need for discovery.
Hi, We have NetView 7.1.4 FP3 on Windows2000. We have installed switch analyzer on that. For some reason the switch analyzer is not showing some Layer-2 options it shows on a Cisco switch. Like the Layer-2 Physical view does not shows all the nodes attached to that switch. Can any one help me out on this. Do i need to load vendor specific MIBs to get that information? or the Switch analyzer doesn't support Enterasys switches?
Regards, |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | FW: [nv-l] Automatic actions - how to reference the source address / hostname with example - thanks, Pretorius, Vynita |
---|---|
Next by Date: | Re: [nv-l] Switch Analyzer and Enterasys Switches, usman . taokeer |
Previous by Thread: | [nv-l] Switch Analyzer and Enterasys Switches, usman . taokeer |
Next by Thread: | Re: [nv-l] Switch Analyzer and Enterasys Switches, usman . taokeer |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web