To: | nv-l@lists.us.ibm.com |
---|---|
Subject: | RE: [nv-l] Switch Analyzer and Layer 3 switches |
From: | Oliver Bruchhaeuser <oliver.bruchhaeuser@de.ibm.com> |
Date: | Fri, 23 Apr 2004 11:03:04 +0200 |
Delivery-date: | Fri, 23 Apr 2004 10:10:59 +0100 |
Envelope-to: | nv-l-archive@lists.skills-1st.co.uk |
In-reply-to: | <6353E0AB365A984BADDD6ED03C3598E6102901@tecnologia.tecsystem.com.ar> |
Reply-to: | nv-l@lists.us.ibm.com |
Sender: | owner-nv-l@lists.us.ibm.com |
Chris, is your switch in the "ovtopodump -X" output? If not ... what is the value for " Layer 2 OID" in the "ovtopodump -X <switch>" output? I assume something like ".... (node is a gateway)". If so ... is your switch in the topo db as a router: ovtopodump -v <switch> | grep "^DOES IP FORWARDING:" If so ... does your switch reports this per SNMP: snmpget <switch> ip.ipForwarding.0 If so .... The actual version of ITSA will not handle Routers as Layer2 devices. If you cannot disable routing on the device .... only one idea .... have you tried to block snmp access to "ip.ipForwarding.0" with an access list? You may be able to fool NetView and so ITSA. Oliver
Christopher, ONE of the means by which netview determines a device to be a router is if it has the ipforwarding mib value to true (1). Disabling routing may turn it to false. Have you then tried itsa's importoid command? Federico Vidal -----Mensaje original----- De: Christopher J Petrina [mailto:cjp8@meadwestvaco.com] Enviado el: Thursday, April 22, 2004 4:28 PM Para: nv-l@lists.us.ibm.com Asunto: [nv-l] Switch Analyzer and Layer 3 switches Greetings all, The subject is ominous but here is my situation. We haev some Alcatel 5024's. These devices by default have some built in routing capabilites. As such they contain a routing table where populated or not it is still there, however these devices are trully only being used as a layer2 switch; but Switch Analyzer is not recognizing them as such. The reason I found out from Magnum is that One of the means by which netview determines a device to be a router is if it contains a routing table. Well the moment it finds the table ont hese devices it calls it a router and switch analyzer will not attempt to do any layer2 discovery on it. My question is, is there a way to override Netviews discovery and force these devices to show as layer2 devices only? In the oid_to_type this particular device is listed as a HB (Hub Bridge) with no mention of G(gateway). Thanks Chris Petrina ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service._______________________________________________________________ This electronic message contains information from MeadWestvaco Corporation or subsidiary companies, which may be confidential, privileged or otherwise protected from disclosure. The information is intended to be used solely by the recipient(s) named. If you are not an intended recipient, be aware that any review, disclosure, copying, distribution or use of this transmission or its contents is prohibited. If you have received this transmission in error, please notify MeadWestvaco immediately at postmaster@MeadWestvaco.com. _______________________________________________________________________ |
<Prev in Thread] | Current Thread | [Next in Thread> |
---|---|---|
|
Previous by Date: | RE: [nv-l] False alarm, Oliver Bruchhaeuser |
---|---|
Next by Date: | RE: [nv-l] False alarm, Ioannis Yerou |
Previous by Thread: | RE: [nv-l] Switch Analyzer and Layer 3 switches, Federico Vidal |
Next by Thread: | RE: [nv-l] Switch Analyzer and Layer 3 switches, Christopher J Petrina |
Indexes: | [Date] [Thread] [Top] [All Lists] |
Archive operated by Skills 1st Ltd
See also: The NetView Web