Hello, everyone!
Physical Network Topology
Figure 1-1 Network where eSight fails to discover kinks
Fault Description
eSight cannot find the link between devices.
Troubleshooting Procedure
Step 1 Check whether two devices are directly connected.
If another device such as a transmission device exists between them, eSight does not support automatic link discovery. You need to create the link manually.
1. Choose Resource > Link Management.
2. Click
on the toolbar to create a
link manually.
Step 2 Check whether the SNMP configuration on the devices is correct.
1. Choose Resource > Network Device.
2. Find the devices in the network device list, and log in to them using Telnet.
3. Run the display current-configuration | include snmp command to check the device configuration.
Table 1-1Checking the SNMP configuration on devices
Protocol | Check Result | Solution |
SNMPv2c | The configured read and write communities do not contain the mib-view parameter, or the specified MIB view does not contain the complete ISO node. | 1. Enter system-view in the Telnet window to enter the device's system view. 2. Run the following commands: snmp-agent mib-view include View_ALL iso snmp-agent community write {SNMP write community} mib-view View_ALL snmp-agent community read {SNMP read community} mib-view View_ALL |
SNMPv3 | The configured user group does not contain the mib-view parameter, or the specified MIB view does not contain the complete ISO node. | 1. Enter system-view in the Telnet window to enter the device's system view. 2. Run the following commands: snmp-agent mib-view include View_ALL iso snmp-agent group v3 {SNMPV3 user group} privacy read-view View_ALL write-view View_ALL notify-view View_ALL |
Step 3 Check whether the SNMP configuration on eSight is correct.
1. Choose Resource > Network Device.
2. Find the devices in the network device list, and click the device name to access the NE Manager.
3. In the navigation tree, choose Protocol Parameters > SNMP Parameters.
4. Check that the SNMP write community is set and the SNMP parameter test succeeds, and click Apply.
Step 4 Check whether the devices support LLDP or CDP.
Check whether the devices support LLDP or CDP. If the devices do not support LLDP or CDP, manually add the link between them to eSight.
1. Choose Resource > Link Management.
2. Click
on the toolbar to create a
link manually.
Step 5 Check whether LLDP or CDP is enabled.
Log in to the devices using Telnet to check whether LLDP or CDP is enabled. If not, enable LLDP or CDP.
Table 1-2Checking whether LLDP or CDP is enabled
Protocol | Check Method | Command |
LLDP | In the configure terminal view, run the show running-config | include lldp command. | lldp enable |
CDP | In the system-view view, run the display current-configuration | include cdp command. | cdp run |
Step 6 Check whether the MIB tables contain LLDP data.
1. Choose Configuration > MIB Management.
2. Click
on the toolbar to select
devices whose MIB table is to be queried.
3. Find the corresponding MIB node, click the node, and click TableView on the toolbar to view LLDP data in the table. Check whether the LLDP data in the MIB tables of devices at two ends of the link is the same.
Query the MIB nodes at two ends of the link. The names are lldpRemEntry (OID: 1.0.8802.1.1.2.1.4.1.1) and lldpLocPortEntry (OID: 1.0.8802.1.1.2.1.3.7.1).
4. If the MIB tables on devices at two ends of the link do not contain LLDP data, or the data in the MIB tables is different, contact the device manager to check the LLDP data.
Common Cause
l Two devices are not directly connected.
l The MIB view is not specified on the devices, or the MIB view does not contain the complete ISO node.
l The SNMP configuration on eSight is incorrect.
l The devices do not support LLDP or CDP.
l LLDP or CDP is disabled on the devices.
l The MIB tables on devices at two ends of the link do not contain LLDP data, or the data in the MIB tables is different.
This is what I want to talk about/share with you today, thank you!
