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 V300R010C00 Operation Guide 07

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).
Discovering Server Links

Discovering Server Links

eSight can automatically discover only physical links of rack servers and blade servers.

Discovering Links of Rack Servers

eSight can automatically discover physical links of rack servers through the MAC forwarding table or LLDP protocol.

Prerequisite
  • The Network Device Manager has been installed.
  • The Server Manager has been installed.
  • To discover links through the LLDP protocol, ensure that FusionSphere 6.3 or a later version has been installed on the rack server and LLDP link auto-discovery has been enabled on the FusionSphere OpenStack. The scenario restrictions are as follows:
    • When the network plane of the host NIC adopts the OVS, EVS, or SR-IOV VF mode, LLDP link discovery is supported.
    • When the network plane of the host NIC adopts the SR-IOV PF mode, LLDP link discovery is not supported.
Context
Table 7-4 lists the rack server links that can be discovered.
Table 7-4 Rack server links that can be discovered

Link Name

Link Discovery Mode

Link between the management port of a rack server and a switch

MAC

Link between the LOM NIC of a rack server and a switch

MAC and LLDP

Link between the PCIe NIC of a rack server and a switch

MAC and LLDP

Procedure
  • Link discovery based on the MAC forwarding table
    1. Configure automatic discovery for terminals.
      1. Choose Resource > Network > Equipment > Terminal Resources from the main menu.
      2. In the navigation tree on the left, choose Resource Management > Discovery Rule.
      3. Set Automatic Terminal Discovery to Enable.
      4. Click Apply.
    2. Connect a rack server.

      For details about how to connect a rack server, see Auto Discovery for Devices, Adding a Single Server Device, or Adding Server Devices in Batches.

    3. Connect a switch.

      For details about how to connect a switch to eSight, see Adding Devices to eSight.

    4. Discover the terminals immediately.
      1. Choose Resource > Network > Equipment > Terminal Resources from the main menu.
      2. In the navigation tree on the left, choose Resource Management > Terminal Access Record.
      3. Click Immediate Discovery.
    5. Update the rack server.
      Choose Resource > Server from the main menu.
      1. In the navigation tree on the left, choose Server Device > Rack Server.
      2. In the information area on the right, click in the Operation column of the server to update the server.
  • Link discovery based on LLDP
    After a rack server is connected to eSight, eSight automatically discovers the link.
    1. Connect a rack server.

      For details about how to connect a rack server, see Auto Discovery for Devices, Adding a Single Server Device, or Adding Server Devices in Batches.

    2. Connect a switch.

      For details about how to connect a switch to eSight, see Adding Devices to eSight.

Troubleshooting
  • Check the link between the management port of a rack server and a switch.
    The link between the management port of the rack server and the switch is discovered through the MAC forwarding table. Update the server and synchronize data.
    1. Choose Resource > Server from the main menu.
    2. In the navigation tree on the left, choose Server Device > Rack Server.
    3. In the information area on the right, click in the Operation column of the server to update the server.
  • Check the link between the LOM NIC of a rack server and a switch.
    • If the link between the LOM NIC of the rack server and the switch is discovered through the LLDP protocol, check whether the LLDP protocol of the server has been enabled.
      1. Log in to the switch as the root user in SSH mode, and run the following command to check whether the LLDP protocol is enabled:

        disp cur | inc lldp

      2. If the LLDP protocol is not enabled on the switch, run the following commands to enable the LLDP protocol:

        system-view

        lldp enable

        commit

    • If the link between the LOM NIC of the rack server and the switch is discovered through the MAC forwarding table, update the server and synchronize data.
      1. Choose Resource > Server from the main menu.
      2. In the navigation tree on the left, choose Server Device > Rack Server.
      3. In the information area on the right, click in the Operation column of the server to update the server.
  • Check the link between the PCIe NIC of a rack server and a switch.
    • If the link between the PCIe NIC of the rack server and the switch is discovered through the LLDP protocol, check whether the LLDP protocol of the server has been enabled.
      1. Log in to the switch as the root user in SSH mode, and run the following command to check whether the LLDP protocol is enabled:

        disp cur | inc lldp

      2. If the LLDP protocol is not enabled on the switch, run the following commands to enable the LLDP protocol:

        system-view

        lldp enable

        commit

    • If the link between the PCIe NIC of the rack server and the switch is discovered through the MAC forwarding table, update the server and synchronize data.
      1. Choose Resource > Server from the main menu.
      2. In the navigation tree on the left, choose Server Device > Rack Server.
      3. In the information area on the right, click in the Operation column of the server to update the server.

Discovering Links of Blade Servers

eSight can automatically discover physical links of blade servers through the MAC forwarding table or LLDP protocol.

Prerequisite
  • The Network Device Manager has been installed.
  • The Server Manager has been installed.
  • The HMM version is 6.88 or another version that supports topology visualization. To check the HMM version, see 1.
Context
Table 7-5 lists the blade server links that can be discovered.
Table 7-5 Blade server links that can be discovered

Link Name

Link Discovery Mode

Link between an E9000 switch module and a blade

-

Link between an E9000 switch module and a switch

LLDP

Link between an E9000 management module and a switch

MAC

Procedure
  • Link discovery based on the MAC forwarding table
    1. Configure automatic discovery for terminals.
      1. Choose Resource > Network > Equipment > Terminal Resources from the main menu.
      2. In the navigation tree on the left, choose Resource Management > Discovery Rule.
      3. Set Automatic Terminal Discovery to Enable.
      4. Click Apply.
    2. Connect a blade server.

      For details about how to connect a blade server, see Auto Discovery for Devices, Adding a Single Server Device, or Adding Server Devices in Batches.

    3. Connect a switch.

      For details about how to connect a switch to eSight, see Adding Devices to eSight.

    4. Discover the terminals immediately.
      1. Choose Resource > Network > Equipment > Terminal Resources from the main menu.
      2. In the navigation tree on the left, choose Resource Management > Terminal Access Record.
      3. Click Immediate Discovery.
    5. Update the blade server.
      Choose Resource > Server from the main menu.
      1. In the navigation tree on the left, choose Server Device > Blade Server.
      2. In the information area on the right, click in the Operation column of the server to update the server.
  • Link discovery based on LLDP
    1. Connect a blade server.

      For details about how to connect a blade server, see Auto Discovery for Devices, Adding a Single Server Device, or Adding Server Devices in Batches.

    2. Connect a switch.

      For details about how to connect a switch to eSight, see Adding Devices to eSight.

Troubleshooting
  • Check the link between an E9000 switch module and a blade.
    1. Check the HMM firmware version on the E9000.

      Log in to the E9000 as the root user in SSH mode and run the following command to check the HMM firmware version. Ensure that the HMM version is 6.88 or another HMM version that supports topology visualization. If the HMM firmware version is earlier than 6.88, upgrade the HMM firmware.

      smmget -d version
      SMM Version Information:
      Uboot    Version :(U54)3.03
      CPLD     Version :(U1082)108  161206
      PCB      Version :SMMA REV B
      BOM      Version :001
      FPGA     Version :(U1049)008  130605
      Software Version :(U54)6.88
      IPMI Module Built:Jul  6 2018 15:20:27

      In the preceding information, Software Version indicates the HMM version.

    2. Log in to the HMM web page of the E9000 and check the switch module status and blade status.

      Ensure that the switch module and blade are installed and the communication is normal.

    3. Contact technical support engineers.
  • Check the link between an E9000 switch module and a switch.
    The link between the switch module of the E9000 and the switch is discovered through the LLDP protocol. Check the LLDP protocol status and assign the ISO view permission to the SNMP user.
    1. Check whether the LLDP protocol is enabled on the server.
      1. Log in to the switch and switch module of the E9000 server as the root user in SSH mode, and run the following command to check whether the LLDP protocol is enabled:

        disp cur | inc lldp

      2. If the LLDP protocol is not enabled, run the following commands to enable the LLDP protocol:

        system-view

        lldp enable

        commit

    2. Check whether the SNMP user of the E9000 switch module has permission on the ISO view.
      1. Log in to the switch module as the root user in SSH mode and run the following command to check the view on which the user has the ISO permission:

        dis cur | inc snmp-agent mib-view included

        snmp-agent mib-view included v3-view iso 

        If iso is not displayed next to v3-view, v3-view does not have the ISO permission. Run the following commands to grant the ISO view permission to the SNMP user:

        snmp-agent mib-view included v3-view iso

        commit

      2. Check whether the ISO view permission on write-view and notify-view has been assigned.

        system-view

        dis cur | inc snmp-agent group v3 eSight privacy

        snmp-agent group v3 eSight privacy write-view iso-view notify-view iso-view

        If the command output displays write-view and notify-view, run the following command to change iso-view to v3-view:

        snmp-agent group v3 eSight privacy write-view v3-view notify-view v3-view

        NOTE:

        In the preceding information, v3-view is the view name. Set it as required.

  • Check the link between an E9000 management module and a switch.
    The link between the E9000 management module and the switch is discovered through the MAC forwarding table. Update the server and synchronize data.
    1. Choose Resource > Server from the main menu.
    2. In the navigation tree on the left, choose Server Device > Blade Server.
    3. In the information area on the right, click in the Operation column of the server to update the server.
Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044378

Views: 59901

Downloads: 274

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