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 09

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).
eSight Cannot Receive Device Alarms

eSight Cannot Receive Device Alarms

This section describes how to troubleshoot faults that eSight fails to receive alarms from all devices or from a specified device, or eSight fails to receive alarms of a specific type from a specified device.

Common Causes

  • The port mapping of the Linux server is incorrect.
  • Port 162 of the eSight server is in use.
  • The firewall function is enabled on the eSight server.
  • Devices are fault, or they cannot communicate with the eSight server.
  • Masking rules are created on eSight to mask specified alarms.
  • SNMP parameters on devices are incorrect or not proper.
  • The device is disabled from sending alarms of a specific type.

Procedure

  1. Check whether the port mapping of the Linux server is correct.

    • single-node system
      1. Log in to the server as the root user.
      2. Run the following command and check whether the following mapping records exist:

        iptables -t nat -nL

        eSight:~ # iptables -t nat -nL 
        Chain PREROUTING (policy ACCEPT) 
        target     prot opt source             destination 
        REDIRECT   udp  --  0.0.0.0/0          0.0.0.0/0           udp dpt:162 redir ports 10162 
        REDIRECT   tcp  --  0.0.0.0/0          0.0.0.0/0           tcp dpt:21 redir ports 31921 
        REDIRECT   udp  --  0.0.0.0/0          0.0.0.0/0           udp dpt:69 redir ports 32182 
        REDIRECT   udp  --  0.0.0.0/0          0.0.0.0/0           udp dpt:514 redir ports 32185 
        ...
    • HA system

      In an HA system, perform the following steps on both the active and standby nodes.

      1. Log in to the server as the root user.
      2. Run the following command and check whether the following mapping records exist:

        iptables -t nat -nL

        • When eSight is deployed in a local HA system, 10.137.58.80 is the floating IP address.
        • When eSight is deployed in a remote HA system, 10.137.58.80 is the system IP address of the current server.
        eSight:~ # iptables -t nat -nL 
        Chain PREROUTING (policy ACCEPT) 
        target     prot opt source               destination 
        DNAT       udp  --  0.0.0.0/0            10.137.58.80         udp dpt:162 to:10.137.58.80:10162 
        REDIRECT   udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:162 redir ports 10162 
        DNAT       tcp  --  0.0.0.0/0            10.137.58.80         tcp dpt:21 to:10.137.58.80:31921 
        REDIRECT   tcp  --  0.0.0.0/0            0.0.0.0/0            tcp dpt:21 redir ports 31921 
        DNAT       udp  --  0.0.0.0/0            10.137.58.80         udp dpt:69 to:10.137.58.80:32182 
        REDIRECT   udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:69 redir ports 32182 
        DNAT       udp  --  0.0.0.0/0            10.137.58.80         udp dpt:514 to:10.137.58.80:32185 
        REDIRECT   udp  --  0.0.0.0/0            0.0.0.0/0            udp dpt:514 redir ports 32185     

  2. Check whether eSight can normally start up and whether port 162 is in use.

    On Windows:

    1. Start eSight to check whether an error is reported.
    2. Run the netstat -aon command in the CLI to find the PID of UDP port 162. In this example, the PID of UDP port 162 is 1716.
      Figure 5-11 Port usage
    3. Check the process name of the PID in the Task Manager. If the name is not java, port 162 is being used by another software.
      Figure 5-12 Select Columns
      Figure 5-13 Select Process Page Columns
      Figure 5-14 Process list

    Solution:

    Uninstall the software that uses port 162.

    On Linux:

    1. Start eSight to check whether an error is reported.
    2. On Linux, the alarm monitoring port is automatically mapped to 10162. Run the following commands to check whether port 10162 is in listening state.

      Command 1: netstat –apn | grep 162 (Check the ID of the process that uses port 162. In this example, the process ID is 7898.)

      Figure 5-15 Port usage

      ps aux | grep 7898 (Check the process details to determine whether the port is used by eSight.)

      Figure 5-16 Port usage

    Solution:

    Uninstall the software that uses port 162.

  3. Check whether the operating system firewall is turned on.

    On Windows:

    Choose Control Panel > System and Security > Windows Firewall > Customize Settings.

    Figure 5-17 Windows firewall settings

    Solution:

    On Customize Settings, select Turn off Windows Firewall (not recommended) and click OK.

    NOTE:

    You are advised to turn on Windows firewall after troubleshooting is complete. Otherwise, the settings may cause information security risks.

  4. Check whether a firewall is deployed between the eSight server and devices.

    If a firewall exists, check whether policies on the firewall permit pass of trap messages. The policies are as follows:

    • Enabled ports: 162 and 10162
    • Supported protocol: UDP

  5. Ping the eSight server IP address from a device to check whether the device can communicate with eSight.

    Check method and solution:

    • If the ping fails, check the network between the device and eSight.
    • If the ping succeeds only when the vpn parameter is specified, configure the vpn parameter in the snmp target-host command.
    • If the ping succeeds only when the source address is specified, configure the trap source in the snmp-agent trap source command.

  6. Check whether alarm masking is enabled on eSight.

    1. 1. Check the alarm masking rule on eSight.

      Choose Fault > Alarm Settings from the main menu. Choose Masking Rule from the navigation tree on the left. 2. check whether an alarm masking rule is set.

    2. Check masked alarms on eSight.

      Choose Fault > Masked Alarms from the main menu.

    3. 3. Check whether traps of the device are recognized as events and stored in the event list.

      Choose Fault > Events from the main menu.

      Disable the alarm masking rule, and check whether devices can report alarms.

  7. Check the alarm configuration on the device.

    Check method:

    Run the display cur | inc snmp command on the device in the IP domain.

    The following lists the commands on a Huawei AC6605 as an example. (For other models, see the corresponding product documentation.)

    For SNMPv1/v2c, run the following commands:

    • snmp-agent local-engineid xxx
    • snmp-agent sys-info version all
    • snmp-agent community read public
    • snmp-agent community write private
    • snmp-agent mib-view included iso-view iso
    • snmp-agent target-host trap address udp-domain xx.xx.xx.xx params securityname public v2c private xxx

    Solution:

    [SNMPv1/v2c] (All the following commands are mandatory.)

    snmp-agent sys-info version v1 v2c 
    snmp-agent community write private mib-view View_ALL 
    snmp-agent community read public mib-view View_ALL 
    snmp-agent mib-view View_ALL include iso 
    snmp-agent trap source MEth0/0/1 
    snmp-agent trap enable 
    snmp-agent target-host trap-hostname xyp address 10.137.241.114 udp-port 162 trap-paramsname xyp 
    snmp-agent target-host trap-paramsname xyp v2c securityname public     
    Table 5-8 Parameter description

    Parameter

    Description

    version

    The SNMP version number must be the same as that specified on eSight and the trap version number for the target-host parameter on the device.

    community write

    The write community must be the same as that specified on eSight.

    community read

    The read community must be the same as that specified on eSight.

    mib-view

    This parameter must be configured next to the read and write communities, and it must contain the complete ISO node: snmp-agent mib-view View_ALL include iso.

    address

    The address must be the eSight server IP address. If not, the eSight server cannot receive alarms from devices.

    udp-port

    This parameter specifies the port used by the eSight server to receive alarms. The value can be 162 or 10162.

    trap source

    This parameter specifies the source that sends trap messages. The IP address of the source must be the same as the device IP address added on eSight.

    securityname

    The security name must be the same as the read community name.

    For SNMPv3, run the following commands:

    snmp-agent sys-info version v3 
    snmp-agent mib-view View_ALL include iso 
    snmp-agent group v3 snmpv3usergroup privacy read-view View_ALL write-view View_ALL notify-view View_ALL 
    snmp-agent usm-user v3 snmpv3user snmpv3usergroup authentication-mode md5 DCD56463205105262F43A56805AF04A0 privacy-mode des56 DCD56463205105262F43A56805AF04A0 
    snmp-agent target-host trap-hostname eSightServerIP address 10.137.240.91udp-port 162 trap-paramsname trapv3param  
    snmp-agent target-host trap-paramsname trapv3param v3 securityname snmpv3user privacy private-netmanager 
    snmp-agent trap source MEth0/0/1 
    snmp-agent trap enable     
    Table 5-9 Parameter description

    Parameter

    Description

    version

    The SNMP version number must be the same as that specified on eSight and the trap version number for the target-host parameter on the device.

    privacy

    This parameter specifies whether authentication and encryption are required for communication using SNMPv3. The value Privacy indicates authentication + encryption. The value Authentication indicates authentication + non-encryption. The value must be the same as the encryption mode for trap messages specified in the snmp target-host command.

    read-view/ write-view/ notify-view

    The three parameters are mandatory when you define an SNMPv3 group on a device. You can run the snmp-agent mib-view View_ALL include iso command to specify the complete ISO node. If they are not configured, the default read permission is internet, and the device does not have write and alarm reporting permission.

    snmpv3user

    The value of this parameter must be the same as the security name specified on eSight and the value of the securityname parameter next to target-host on the device.

    authentication-mode

    This parameter specifies an authentication mode. The value must be the same as that specified on eSight.

    privacy-mode

    This parameter specifies a privacy mode. The value must be the same as that specified on eSight.

    address

    The address must be the eSight server IP address. If not, the eSight server cannot receive alarms from devices.

    udp-port

    This parameter specifies the port used by the eSight server to receive alarms. The value can be 162 or 10162.

    trap source

    This parameter specifies the source that sends trap messages. The IP address of the source must be the same as the device IP address added on eSight.

  8. Clear the browser cache.

    If an alarm is displayed on the alarm list or NE Manager, but unavailable in the current or historical alarm list, check the alarm information in another browser or clear the browser cache.

  9. Collect the following log information and contact Huawei technical support personnel.

    eSight\AppBase\var\iemp\log\oms\fm\*.*

    eSight\AppBase\var\iemp\log\enterprise\fm\*.*

Download
Updated: 2019-05-17

Document ID: EDOC1100011877

Views: 285275

Downloads: 550

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