|
Please allow me to ask this simple question. When you walk the system MIB for your device, do you get the same OID as listed in the oid_to_type file? Just curious. I know that you said your oid_to_type file is correct, but I am not sure how you came to that conclusion.
MIchael, Correct. These however are Alcatel 5024's which have a built in capability to do some routing. (Virtual Router) it allows for routing of things like IP-OSPF IP-RIP II etc. Alcatel designed these so that you could do some routing without the cost of an external router. I think this will end up being a PMR, because as I walked through all the switch analyzer stuff, it is all dependent on how Netview discovers the device. My oid_to_type files are correct. so either we actually are doing some routing on them or it is not processing the oid_to_type correctly -Chris Petrina
Switches that are only layer 2 devices (normal switches) do not have routing tables and will not return routing table MIB stuff when queried. Plain layer 2 switches actually use a default gateway as opposed to a default route. A workstation can have IP forwarding enabled and become a router, unlike a normal switch. Michael Webb, IBM Tivoli Q1CA Distributed NetView / ITSA SVT Email: mlwebb@us.ibm.com Ext: (919) 224-1410, T/L: 687-1410  "Barr, Scott" <Scott_Barr@csgsystems.com>
Um, I might be off base here, but EVERY TCP/IP device has a routing table. From: owner-nv-l@lists.us.ibm.com [mailto:owner-nv-l@lists.us.ibm.com] On Behalf Of Michael Webb Sent: Thursday, April 22, 2004 2:47 PM To: nv-l@lists.us.ibm.com Subject: Re: [nv-l] Switch Analyzer and Layer 3 switches Have you tried configuring one of your 5024s to actually disable the routing capability? I would be curious to see if that would get rid of the routing table information.
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. _______________________________________________________________________ ________________________________________________________________________ This email has been scanned for all viruses by the MessageLabs SkyScan service._______________________________________________________________ ________________________________________________________________________ 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. _______________________________________________________________________
|
"Christopher J Petrina" <cjp8@meadwestvaco.com>
"Christopher J Petrina" <cjp8@meadwestvaco.com>
