Layer 2 Map Troubleshooting
Make sure DB Query is enabled under Settings->System Settings->General.
Once it is enabled, click on the support icon on the top right corner->DB Query, execute the below queries one by one, make sure all pages are selected at the bottom center of the page and save the output in .csv format and send it to OpManager support.
- Get the MAPID from LAYER2CONFIGURATION table (Select MAPID from LAYER2CONFIGURATION WHERE MAPNAME=<'MAPNAME'>
- Select * from LAYER2CONFIGURATION
- Select * from LAYER2SUBNETCONFIGURATION WHERE MAPID=<MAPID>
- Select * from LAYER2DEVICEPROPS WHERE MAPID=<MAPID>
- Select * from LAYER2MAPPING WHERE MAPID=<MAPID>
- Select * from LAYER2ROUTINGTABLE WHERE MAPID=<MAPID>
- Select * from ROUTERINTERFACETABLE WHERE MAPID=<MAPID>
- Select * from ROUTERARPCACHE WHERE MAPID=<MAPID>
- Select * from SWITCHARPCACHE WHERE MAPID=<MAPID>
- Select * from DTPFDBTABLE WHERE MAPID=<MAPID>
- Select * from CDPCACHE WHERE MAPID=<MAPID>
- Select * from LLDPCACHE WHERE MAPID=<MAPID>
- And, screen shot for the Discovery Page and Map page.
- Debug enabled logs folder
- MibBrowser output of the below oids for the devices which are not showing proper connection details in map.
Please click on Settings->Tools -> Mib Browser, select the seed device and its SNMP community, copy and paste the below OID's one by one, click on GET and send us the screenshot of the output.
List of OIDs used for Layer2 Discovery :BRIDGE-MIB :
- .1.3.6.1.2.1.17.4.3.1.1
- .1.3.6.1.2.1.17.4.3.1.2
- .1.3.6.1.2.1.17.4.3.1.3
- .1.3.6.1.2.1.17.1.4.1.1
- .1.3.6.1.2.1.17.1.4.1.2
RFC1213.MIB (NetToMediaTable)
- .1.3.6.1.2.1.4.22.1.1
- .1.3.6.1.2.1.4.22.1.2
- .1.3.6.1.2.1.4.22.1.3
- .1.3.6.1.2.1.4.22.1.4
RFC1213 (IPRouteTable)
- .1.3.6.1.2.1.4.21.1.1
- .1.3.6.1.2.1.4.21.1.2
- .1.3.6.1.2.1.4.21.1.7
- .1.3.6.1.2.1.4.21.1.8
- .1.3.6.1.2.1.4.21.1.11
CISCO-CDP.MIB (CDP) - MIB files attached
- .1.3.6.1.4.1.9.9.23.1.2.1.1.4
- .1.3.6.1.4.1.9.9.23.1.2.1.1.7
- .1.3.6.1.4.1.9.9.23.1.2.1.1.9
LLDP.MIB(LLDP)
- .1.0.8802.1.1.2.1.4.1.1.4
- .1.0.8802.1.1.2.1.4.1.1.5
- .1.0.8802.1.1.2.1.4.1.1.8
- .1.0.8802.1.1.2.1.4.1.1.9
- .1.0.8802.1.1.2.1.4.1.1.12
- .1.0.8802.1.1.2.1.4.2.1.2
- .1.0.8802.1.1.2.1.4.2.1.3
IF-MIB :
- ifIndex - .1.3.6.1.2.1.2.2.1.1
- ifName - .1.3.6.1.2.1.31.1.1.1.1
Router Discovery Algorithm:
WebNms algorithm used:
- "ipForwarding" of the device must be set to 1 - .1.3.6.1.2.1.4.1.0
- Object must have two or more interfaces. - .1.3.6.1.2.1.4.20.1.1
Switch Discovery Algorithm:
- Bridge mib OIDs should respond.
New to ADSelfService Plus?
Related Articles
Mail Server Troubleshooting
Below are few common issues faced during Mail Server Settings Configuration which are beyond OpManager control. 1. Connection Issue: Time Out Issue. Authentication required but not provided. TLS may be required but not configured. TLS might ...Network Path Analysis
Dependency field removal and prevent auto update
The dependency field of the devices can be entered manually or it can update itself when a layer 2 map is created. If you remove the dependency manually, it will be populated again since by default the layer 2 map will have a auto-discovery interval. ...Steps for configuring SNMPv3 on a Router
Steps for configuring SNMPv3 on a Router Here are the steps to configure SNMPv3 on a router and opmanager. Lets configure a privileged user called Henry with the relevant details below. username : Henry authProtocol : MD5 privProtocol : DES ...Modem Based SMS Configuration
Prerequisites: Any Modem that supports the following pre-requisite conditions can be used with OpManager. 1.Modem\Mobile must have GSM functionality. 2. Must have provision for inserting SIM. 3. Should support 7bit (GSM default alphabet), 8bit and ...