Prerequisites to check if VLAN not discovered or status shows Unknown

Prerequisites to check if VLAN not discovered or status shows Unknown


Prerequisites to check if VLAN not discovered or status shows Unknown.
Based on below OIDs result, we are showing VLANs information for Routers/Switches in OpManager.

For Cisco category devices, load these two mib files CISCO-VTP-MIB and CISCO-VLAN-MEMBERSHIP and check.

Open MIB browser, provide the concern device details with correct SNMP community, then provide the OID one by one to check the response.

VlanIndex - .1.3.6.1.4.1.9.9.68.1.2.2.1.2
VlanName - .1.3.6.1.4.1.9.9.46.1.3.1.1.4
VlanStatus - .1.3.6.1.4.1.9.9.68.1.1.7.1.3

For Non Cisco, load Q-BRIDGE-MIB

VlanIndex - .1.3.6.1.2.1.17.7.1.4.5.1.1
VlanName - .1.3.6.1.2.1.17.7.1.4.3.1.1
VlanStatus - .1.3.6.1.2.1.17.7.1.4.3.1.5
                New to ADManager Plus?

                  New to ADSelfService Plus?

                    • Related Articles

                    • Device discovered as unknown even through configured with SNMP credential in OpManager

                      Issue: Device discovered as unknown even after adding the SNMP read community. Reason: The device may not be configured properly with SNMP or  OpManager is not configured properly with device SNMP community. Resolution: You may check for the ...
                    • Prerequisites for onboarding

                    • AD Monitors Shows N/A in OpManager

                      This problem could due to the following reasons: 1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor AD servers). 2)Required Monitors are not associated to the device  in OpManager. 3)WMI might not be responding to ...
                    • MSSQL Monitors not working - Shows N/A in OpManager

                      This problem could due to the following reasons: 1)WMI is not configured properly in OpManager (OpManager uses WMI credential to monitor MSSQL servers). 2)Required Monitors are not associated to the device  in OpManager. 3)WMI might not be responding ...
                    • Printer status OIDs

                      Here are the below OIDs we use to get the status of the printer which are hard coded in OpManager: 1.   .1.3.6.1.2.1.25.3.2.1.5.1 Printer Operational status like Up, Down or Warning 2.    .1.3.6.1.2.1.25.3.5.1.1.1  Printer Current status like idle, ...