No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R009C00 Operation Guide 10

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Troubleshooting

Troubleshooting

This section describes common faults frequently encountered by users, helping users rectify faults in a timely manner.

eSight Fails to Discover Links

eSight supports link discovery through Link Layer Discovery Protocol (LLDP) or Cisco Discovery Protocol (CDP). You can select a link discovery mode based on the device vendor or device type. Automatic link discovery can be used if there is a direct LLDP link between two devices and LLDP data exists in devices' MIB tables.

Common Causes
  • Two devices are not directly connected.
  • The MIB view is not specified on the devices, or the MIB view does not contain the complete ISO node.
  • The SNMP configuration on eSight is incorrect.
  • The devices do not support LLDP or CDP.
  • LLDP or CDP is disabled on the devices.
  • 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.
Procedure
  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 > Network > Equipment > Link Management from the main menu.
    2. Click on the toolbar to create a link manually.

  2. Check whether the SNMP configuration on the devices is correct.

    1. Choose Resource > Network > Equipment > Network Device from the main menu.
    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 12-5 Checking the SNMP configuration on devices

    Protocol

    Check Result

    Solution

    SNMP V2c

    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

    SNMP V3

    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

  3. Check whether the SNMP configuration on eSight is correct.

    1. Choose Resource > Network > Equipment > Network Device from the main menu.
    2. Find the devices in the network device list, and click the device name to access the NE Manager.
    3. In the navigation tree on the left, choose Protocol Parameters > SNMP Parameters.
    4. Check that the SNMP write community is set and the SNMP parameter test succeeds, and click Apply.

  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 > Network > Equipment > Link Management from the main menu.
    2. Click on the toolbar to create a link manually.

  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 12-6 Checking whether LLDP or CDP is enabled

    Protocol

    Check Whether LLDP or CDP Is Enabled

    Enable LLDP/CDP

    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

  6. Check whether the MIB tables contain LLDP data.

    1. Choose Resource > Network > Configuration > MIB Management from the main menu.
    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.

  7. If the fault persists, contact technical support personnel.

Device Addition Failure

The reasons causing device addition failures vary depending on scenarios. This section describes the reasons of device addition failures and troubleshooting methods based on error codes for device addition failures.

Common Causes

Error Code

Common Causes

Network is busy, the device is overloaded, or SNMP parameters are incorrect.

  • The network between the device and eSight is disconnected.
  • The SNMP parameters configured during device addition to eSight are inconsistent with those of the device.
  • The SNMP configuration on the device is incorrect.
  • The password for the SNMP read-write community name of the device does not meet complexity requirement.
  • The device adds the IP address of eSight server to its blacklist (USG firewall).
  • Third-party equipment's sysObjectID does not exist.
  • The device is working abnormally.

The device already exists.

The device to be added has a different IP address and the same MAC address with the device that already exists on eSight.

Database operation fails.

The database is abnormal.

Procedure
  • Network is busy, the device is overloaded, or SNMP parameters are incorrect.
    • Check the current network configuration.
      1. Check whether the device and eSight can ping each other. If the link between eSight and the device is reachable uni-directionally, configure the corresponding route.
      2. Check whether a firewall/NAT device exists between the device and eSight. If a firewall exists, disable the firewall. If a NAT device exists, ensure that NAT configuration is consistent with that planned in the communication matrix.
    • Check whether the SNMP parameters filled during device addition are inconsistent with those of the device.

      Read-write community name is encrypted both on the device and eSight. If you are uncertain of the SNMP parameters configured on the device, reconfigure the SNMP parameters on the device and then add the device again.

    • Check whether the SNMP configuration on the device is correct.
      1. Telnet to the device failing to be added.
      2. Run the display current-configuration | include snmp command to check the SNMP configuration of the device.

        Protocol

        Check Result

        Solution

        SNMP V2c

        The configured read-write community name does not carry the mib-view parameter or the mib-view parameter does not include the whole ISO node.

        1. Run the system-view command in the Telnet window and enter the system view.
        2. Run the following command:

          snmp-agent mib-view include View_ALL iso

          snmp-agent community write {SNMP write community name} mib-view View_ALL

          snmp-agent community write {SNMP read community name} mib-view View_ALL

        SNMP V3

        The configured user group does not carry the mib-view parameter or the mib-view parameter does not include the whole ISO node.

        1. Run the system-view command in the Telnet window and enter the system view.
        2. Run the following command:

          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

          snmp-agent usm-user v3 {user name} {SNMPv3 user group}

          snmp-agent usm-user v3 {user name} authentication-mode md5 {authentication password}

          snmp-agent usm-user v3 {user name} privacy-mode aes128 {encryption password}

    • Check whether the password for the SNMP read-write community name of the device meets complexity requirement.
      NOTE:

      If no, the following possible causes may exist: SNMP parameters may be configured when the community name password complexity check function is disabled and the configured community name is simple (for example, public or private). The check function is enabled after SNMP parameters have been configured.

      This operation is only applicable to devices supporting complexity check function. For those that do not support complexity check function, ignore this step.

      1. Telnet to the device failing to be added.
      2. Take S9700s as an example. Run the display current-configuration | include snmp command to check whether snmp-agent community-check displays disable. If it displays disable, run the undo snmp-agent community complexity-check disable command to enable community password complexity check function. If it does not display disable, go to the next step.
      3. Reconfigure the SNMP parameters to meet the complexity requirement.
      4. Add the device again.
    • Check whether the device adds the IP address of the eSight server to the blacklist (USG firewall).
      1. Telnet to the device failing to be added and enter the system view.
      2. Run the display firewall blacklist item command to check whether the IP address of eSight server is in the blacklist of the device. If so, run the undo firewall blacklist item all command to empty the device blacklist.
    • Check whether the third-party equipment's sysObjectID exists.
      NOTE:

      sysObjectID is the unique identifier of the device during device addition process. The missing of sysObjectID MIB object may cause device addition failures.

      1. Choose Resource > Network > Configuration > MIB Management from the main menu.
      2. Connect to device failing to be added through the MIB management tool.
      3. In the filtering box of MIB navigation tree, enter 1.3.6.1.2.1.1.2 and check whether any data exists on sysObjectID object. If there is no data, the failure is caused by faulty device. Contact the supplier to locate the fault.
    • Check whether the device is abnormal.
      NOTE:

      If so, you can check logs and error message on eSight or check logs on the device to determine whether the device is abnormal.

      1. Telnet to the device failing to be added and enter the system view.
      2. Run the display logbuffer command to check log information.
      3. If the logbuffer is abnormal, for example, the following error message is displayed,
        Jan  2 2008 00:45:39-05:13 R6_U26_S2700 %%01SNMP/4/DECODE_ERR(l)[11]:Failed to login through SNMP, because of the decoded PDU error. (Ip=192.168.32.166, Times=1)

        The failure is caused by a faulty device. Contact the supplier to locate the fault.

  • The device already exists.

    Check whether the to-be-added device and added device have different IP addresses but the same MAC address.

    1. Choose Resource > Network > Configuration > MIB Management from the main menu.
    2. Check whether the conflicting devices have the same MAC address.

      Connect to the device through the MIB management tool. In the filtering box of the MIB navigation tree, enter 1.3.6.1.2.1.17.1.1, click the found object, click Walk on the toolbar, and check the MAC addresses.

    3. If the MAC addresses of the two devices are the same, check whether the two devices are the same physical device (the IP addresses used for adding the two devices are different). If yes, delete the added device and add the current device. If no, the hardware of the device is faulty. In this case, contact the device vendor to locate the fault.
  • Database operation fails.

    Check whether the database is abnormal (MySQL).

    1. Open the file stored in eSight directory eSight/MySQL/data/eSight.err. Check the database log information to determine whether the database is abnormal.
    2. If an error message, such as the following message, occurs, some of the database files are corrupted. Go to the next step, recover the corrupted files, and start eSight.
      [ERROR] D:\eSight\MySQL\bin\mysqld.exe: Table '.\mysql\proc' is marked as crashed and should be repaired
    3. Stop eSight.
    4. Stop the MySQL service and back up the files stored in MySQL directory on eSight server. (D:\eSight\MySQL)
      1. Log in to the eSight server as an Administrator.
      2. Choose Start> Run and enter cmd. The CMD window is displayed.
      3. Run the following commands to stop the MySQL service.

        > cd /d D:\eSight\MySQL\bin

        > uninstmysqlsvc.bat

      4. Back up the files stored in MySQL directory. (D:\eSight\MySQL)
    5. Run the following commands in the CMD window, start the MySQL service, and recover the corrupted database files.

      > instmysqlsvc.bat

      > cd /d D:\eSight\MySQL\bin

      > myisamchk -c -r ../data/mysql/proc.MYI

    6. Start eSight.
  • If the fault persists after the preceding operations, contact Huawei engineers.

Device Synchronization Failure

This section describes the reasons causing device synchronization failures and troubleshooting methods.

Common Causes
  • The network between the device and eSight is disconnected.
  • The SNMP configuration on the device is incorrect.
  • The setting of SNMP timeout interval is incorrect.
Procedure
  • Check the current network configuration.

    Check whether the device and eSight can ping each other. If the link between eSight and the device is reachable uni-directionally, configure the corresponding route.

  • Check whether the SNMP configuration on the device is correct.
    1. Telnet to the device failing to be synchronized.
    2. Run the display current-configuration | include snmp command to check the device configuration.
      Table 12-7 Checking the device's SNMP configuration

      Protocol

      Check Result

      Solution

      SNMP V2c

      The configured read-write community name does not carry the mib-view parameter or the mib-view parameter does not include the whole iso object.

      1. Run the system-view command in the Telnet window and enter the system view.
      2. Run the following command.

        snmp-agent mib-view include View_ALL iso

        snmp-agent community write {SNMP write community name} mib-view View_ALL

        snmp-agent community write {SNMP read community name} mib-view View_ALL

      SNMP V3

      The configured user group does not carry the mib-view parameter or the mib-view parameter does not include the whole iso node.

      1. Run the system-view command in the Telnet window and enter the system view.
      2. Run the following command.

        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

  • Check the SNMP timeout interval setting.

    Access the NE Explorer, choose Protocol Parameters > SNMP Parameters in the navigation tree, and check the timeout interval. If the interval is too short, set it to a larger value, for example, 60s.

  • If the fault persists after the preceding operations, contact Huawei engineers.

NEs Fail to Be Added to eSight

Symptom

eSight starts abnormally and some modules cannot work properly. NEs fail to be added to eSight and a message is displayed indicating that the device type is invalid or the access type is not configured.

Possible Causes

The eSight server uses an operating system rather than Windows Server 2012 R2, and the NE access module fails to be loaded.

Procedure

Re-install eSight on a server running the Windows Server 2012 R2 operating system.

Synchronization of the Device's Management Interface Fails

Symptom

When eSight synchronizes data from an S2700-9TP-EI V100R006C03, the management interface fails to be synchronized. However, eSight can successfully synchronize management interfaces from other S2700-9TP-EI switches running the same version.

Possible Causes

The possible causes are as follows:

  • The SNMP configurations on the switch are incorrect.
  • eSight cannot normally collect the switch's interface information using SNMP packets due to packet loss on the network.
  • The switch does not correctly respond to the SNMP request packets from eSight.
Procedure
  1. Check the SNMP configurations on the switch.

    Run the display current-configuration | include snmp command on the switch to check the SNMP configurations. The command output shows that the SNMP configurations are correct and the SNMP trap function is enabled.

  2. Ping the switch from eSight. Ping packets are not lost, but ICMP packets have jitters and are unstable.

    As the switch sends ICMP packets to the CPU for processing, it is suspected that the CPU is highly occupied and not sufficient for processing protocol packets.

  3. Check the CPU usage of the switch. The CPU usage is higher than 50%, and the cpu-defend information shows that some SNMP packets are lost during the NE data synchronization.

    The switch does not correctly respond to the SNMP request packets from eSight because the number of SNMP packets sent to the CPU has reached the upper limit.

  4. Change the number of SNMP request packets sent by eSight each time. By default, eSight sends 10 SNMP request packets to the switch each time. Change the number to 1 or a larger value to ensure normal data reading.

    Modify the file in eSight installation directory\AppBase\etc\snmp\snmp.xml.

    After the modification:

    <!-- comment this config item to use get-next --> 
    <!-- rule: [5, 10, 100] --> 
    <param name="get-bulk">1</param>

  5. Synchronize data from the switch again. The management interface can be successfully synchronized to eSight.
Suggestion and Summary

If the monitored device traffic becomes abnormal or device data synchronization fails when eSightt is used to manage devices, troubleshoot the problem according to the following procedure:

  • Check whether the SNMP configurations on the switch are correct.
  • Check whether the network between eSight and the device is stable.
  • Check whether the CPU usage of the device is over high when the Huawei S-series switch sends SNMP packets to the CPU.
  • Check the cpu-defend information to determine whether the device can normally process protocol packets.

If the CPU usage is over high or the number of SNMP packets sent to the CPU has reached the upper limit, change the number of SNMP request packets sent by eSight each time to reduce the rate at which the device processes SNMP packets.

Devices on Different Network Segments Cannot Be Added to eSight Simultaneously When Public and Private Networks Coexist

Symptom

As shown in the following figure, the eSight server has two network adapters and they are configured with IP addresses of different network segments. If you select the network adapter IP segment where client A resides (for example, 10.10.10.10), client A can be added to eSight. However, client B that resides on the other network segment cannot be added to eSight.

If users log in to eSight using 10.10.10.10 in most cases, use 10.10.10.10 as the primary IP address and 192.168.10.10 as the secondary IP address.

Possible Causes

To reduce the risks that the eSight server is being attacked, eSight implements network isolation and listens to only the specific network adapter IP address during device management.

To add both client A and client B to eSight, you need change the settings to allow eSight to listen to both network adapter IP addresses.

Procedure
  • V300R003C20 and earlier versions
    1. Execute the configuration file.
      • Windows: Execute the open_med.bat file in eSight installation directory\Appbase\tools\multi-ip.
      • Linux: Execute the open_med.sh file in eSight installation directory\Appbase\tools\multi-ip.
    2. Restart eSight.
    3. Optional: Execute the network traffic collector (NTC) configuration file.

      Perform this step if the NTC and eSight are deployed separately.

      • Windows: Execute the open_multiIP.bat file in eSight installation directory\ntc\tools\multiIP.
      • Linux: Execute the open_multiIP.sh file in eSight installation directory\ntc\tools\multiIP.

        Restart the NTC for the modification to take effect.

  • V300R005C00 and later versions
    • Windows
      1. Log in to the eSight server as the Administrator user.
      2. Choose Start > All Programs > eSight > eSight Console.
      3. Choose Tools > Multi-subnetwork Management Tool in the eSight Console dialog box.

        The Multi-subnetwork Management Tool dialog box is displayed.

        NOTE:
        • eSight login via multiple subnetworks: allows you to log in to eSight from management clients in multiple subnets.
        • Manage all subnetwork devices: enables eSight to manage devices in all subnets.
        • Auto stop and start eSight: enables eSight to automatically start or stop.
      4. Select the required functions and click Modify.
      5. Restart the eSight service.
      6. Optional: Execute the network traffic collector (NTC) configuration file.

        Perform this step if the NTC and eSight are deployed separately.

        • Windows: Execute the open_multiIP.bat file in eSight installation directory\ntc\tools\multiIP.
        • Linux: Execute the open_multiIP.sh file in eSight installation directory\ntc\tools\multiIP.

          Restart the NTC for the modification to take effect.

    • Linux
      1. Log in to the eSight server as the ossuser user.
      2. Run the following commands to start the Multi-subnetwork Management Tool.

        > cd /opt/eSight/AppBase/tools

        > ./multi-subnetwork.sh

        NOTE:
        • eSight login via multiple subnetworks: allows you to log in to eSight from management clients in multiple subnets.
        • Manage all subnetwork devices: enables eSight to manage devices in all subnets.
        • If the tool window is not displayed in the Linux operating system, rectify the fault according to Installation and Commissioning > FAQ and Troubleshooting > Operating System > Linux Operating System > What Can I Do If the Tool Window Is Not Displayed in the Linux Operating System in the eSight Product Documentation.
      3. Select the required functions and click Modify.
      4. Restart the eSight service.
      5. Optional: Execute the network traffic collector (NTC) configuration file.

        Perform this step if the NTC and eSight are deployed separately.

        • Windows: Execute the open_multiIP.bat file in eSight installation directory\ntc\tools\multiIP.
        • Linux: Execute the open_multiIP.sh file in eSight installation directory\ntc\tools\multiIP.

          Restart the NTC for the modification to take effect.

Suggestion and Summary
  • When eSight is configured to listen to both network adapter IP addresses, the risks that the eSight server is attacked increase.
  • When the eSight server is equipped with multiple network adapters, only IPv4 addresses can be used.
  • To cancel the preceding configuration in V300R003C20 or earlier versions, perform the following operations:
    1. Execute the configuration file.
      • Windows: Execute the close_med.bat file in eSight installation directory\Appbase\tools\multi-ip.
      • Linux: Execute the close_med.sh file in eSight installation directory\Appbase\tools\multi-ip.
    2. Restart eSight.
    3. Optional: Execute the NTC configuration file.
      Perform this step if the NTC and eSight are deployed separately.
      • Windows: Execute the close_multiIP.bat file in eSight installation directory\ntc\tools\multiIP.
      • Linux: Execute the close_multiIP.sh file in eSight installation directory\ntc\tools\multiIP.

        Restart the NTC for the modification to take effect.

Related Information

When the IP address of the eSight server changes, perform the following operations:

  • Primary IP address change: For details, see Installation and Commissioning > FAQ and Troubleshooting > Operating System > Windows Operating System > How Do I Synchronize the eSight Server IP Address to eSight (Windows) in the eSight Product Documentation and Installation and Commissioning > FAQ and Troubleshooting > Operating System > How Do I Synchronize the eSight Server IP Address to eSight (Linux) in the eSight Product Documentation.
  • Secondary IP address change:
    • Windows operating system
      1. Access eSight installation directory\AppBase\etc\oms.sso.
      2. Open the files sso.xml and ssoclient.xml using the WordPad and replace the IP address that has changed. For example, change the IP address 192.168.1.2 to 192.168.2.2.
      3. Restart eSight.
    • Linux operating system
      1. Log in to the Linux operating system as the ossuser user.
      2. Access the eSight installation directory, for example, D:\eSight.

        cd /opt/eSight/AppBase/etc/oms.sso

      3. Open the configuration file, for example, sso.xml, and replace the IP address that has changed.
        vi sso.xml  
        <sso-config>  
        <param name="https-port">31942</param>  
        <param name="rmi-ip">10.137.59.87</param>  
        <param name="rmi-port">31909</param>  
        <param name="locale">en_US</param>  
        <param name="default-forward-url">http://10.137.59.87:8080</param>  
        <param name="client-trusted-ip">10.137.59.87</param>  
        </sso-config>  exit
      4. Restart eSight.
Translation
Download
Updated: 2019-08-10

Document ID: EDOC1100011877

Views: 298203

Downloads: 611

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next