Bill Fisher wrote: > > jlixfeld wrote: > > I have a map that started off displaying layer 3 connections. I then > > installed and enabled IMDC and went through all the steps to enable Layer 2 > > in Maps Settings and Server Settings. One I was done, I clicked "Change > > Now" in Map Settings and forced a layer 2 data collection in the Server > > settings. > > > > Once those steps were completed, I saw drastic changes to the maps as > > anticipated, but I'm not sure if what I saw was totally expected of if > > there is still some incompleteness going on: > > > > 1. While many networks and connections were removed, for devices that had > > adjacent devices connected, it still showed the network bubble that > > connected the devices together at layer 3 previously. I'm not sure if this > > is expected behaviour or not, as I would almost expect all the layer 3 info > > to be deleted and just have connections displayed between devices without > > the layer 3 bubble. > > > > > There are two things I have seen happen. > > 1. Sometimes a switch port is labeled with a Subnet list (usually ifIndex 1). > The L2 engine does not automatically change network labels to the port number > - you can do this manually. >
So what I hear you saying is that those ovals never disappear. They show a subnet it's a layer 3 connection and they (are normally supposed to) show a port number of it's a layer 2 connection. That said, if I manually change the label, it will be persistent regardless as to whether it is a layer 3 connection or a layer 2 connection? Bill Fisher wrote: > > 2. It is possible for devices to exist on your map that L2 cannot locate. > When this happens, the connection logic defaults to layer 3. In the Status > window for an interface, look for the "Interface Connection" section. If this > section exists, it will provide the L2 data used to locate the device. > This section does not exist, so it seems that it is defaulting to layer 3. Fast forwarding down the thread a bit, is it possible that if I'm hitting the limited mode bug, that might account for why L2 might not be able to locate some of the connections? Bill Fisher wrote: > > jlixfeld wrote: > > > > 2. I deleted some networks and connections from some devices that were > > discovered after I added a new network and rescanned it, but I realized > > afterwards that these connections should have been preserved, but > > re-scanning the network doesn't seem to bring back those connections. Is > > there a way I can have those networks and connections re-discovered or do I > > have to delete the device first and then re-discover the device or network? > > > > > The hidden connections are hidden interfaces. Open the Interfaces window for > a device and check the box next to the appropriate interface to make it > visible again. > Found it, thanks. Bill Fisher wrote: > > In 5.4.5, we are adding a "Show Adjacent" command available using a specific > keystroke. This will make it easier in certain cases to correct maps for > hidden connections. > Just out of curiosity, is there a release schedule for 5.4.5? Bill Fisher wrote: > > jlixfeld wrote: > > > > 3. I'm confused by the Layer 2 window. It shows 40 devices, which is the > > same number of devices I have in the map. Each device in the Device Filter > > pane seems to show all of the proper connections, but there is nothing > > displayed in the Endpoints pane when I check on a device in the Device > > Filter pane. > > > > > If you have all devices checked on the left side, do you ever see anything in > the endpoints pane on the right? If not, it sounds like you have "Limited" > mode enabled. Please open the Server Settings window and check which radio > button is selected. If the "Limit Layer 2 Discovery to CDP and LLDP" is > checked, then you are in limited mode. > I never see anything in the endpoints pane, even with all devices checked on the left side. I do indeed have limited mode set because I don't use spanning-tree on my network. Our network is completely routed, but we use CDP everywhere so from my perspective, limited mode is all we need. Besides, I'm a little leary about certain layer 2 detection mechanisms. I already know that there is a bug in the switch software I use that rears it's head if something polls dotidTpFdbTable. It will immediately crash any devices running the affected software, so I try to keep layer 2 detection limited to CDP, although I'm certainly amenable to enabling LLDP if the feeling is that it will help. Bill Fisher wrote: > > jlixfeld wrote: > > > > In the Connections pane, it only shows two connections (that is, two device > > names with "*" to the left of them). The rest of the entries in the > > Connections pane indicate that they are connected to a switch that is > > actually network, not a switch (see above where I say that my map still > > displays networks after the conversion to Layer 2). > > > > > If the connections pane only shows two connections with 40 devices, I suspect > you are running into a bug in Limited mode. If you can confirm that you are > running in Limited mode, Support can send you a new "switches.zip" file for > you to install. Great. I will ask them for a new switches.zip file. -------------------- m2f -------------------- Read this topic online here: http://forums.dartware.com/viewtopic.php?p=3520#3520 ____________________________________________________________________ List archives: http://www.mail-archive.com/intermapper-talk%40list.dartware.com/ To unsubscribe: send email to: [email protected]
