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

Configuration Guide - Device Management

S2720, S5700, and S6720 V200R013C00

This document describes the configurations of Device Management, including device status query, hardware management, Stack, SVF, cloud-based management, PoE, monitoring interface, OPS, energy-saving management, information center, fault management, NTP, synchronous ethernet, PTP.
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).
Obtaining the Device Management Mode and Cloud Management Platform's Address Information Through a DHCP Server

Obtaining the Device Management Mode and Cloud Management Platform's Address Information Through a DHCP Server

Process

In the Huawei Cloud Managed Network Solution, DHCP can implement plug-and-play deployment of switches, removing the need to manually change the switch management mode and configure the cloud management platform's address information.

Figure 5-1  Obtaining the device management mode and cloud management platform's address information through a DHCP server
In Figure 5-1:
  1. The administrator needs to deploy the DHCP server function on the network egress gateway or deploy an independent DHCP server on the network, and then configure DHCP Option 148, which includes the cloud-based management mode and cloud management platform's IP address/URL and port number.
  2. An unconfigured switch starts and sends a request packet containing VLAN 1 to the DHCP server.
    • If the VLAN for the IP address pool of the DHCP server is not VLAN 1, the switch cannot use VLAN 1 to communicate with the DHCP server. The switch then uses the upstream device's PNP VLAN negotiated through the Link Layer Discovery Protocol (LLDP) to initiate a request to the DHCP server again. For details about the PNP VLAN negotiation process, see PNP VLAN Auto-Negotiation.
    • If the VLAN for the IP address pool of the DHCP server is VLAN 1, the switch can use VLAN 1 to communicate with the DHCP server and register with the cloud management platform. If the switch negotiates a PNP VLAN with an upstream device, the switch uses this PNP VLAN to register with the cloud management platform again.
  3. The DHCP server receives the request and sends a DHCP packet containing Option 148 to the switch.
  4. The switch changes from the traditional management mode to the cloud-based management mode based on Option 148 and restarts.
  5. After the switch restarts, all its configurations are cleared. Therefore, the switch needs to send a DHCP request again to obtain its management IP address.
  6. The DHCP server receives the request and sends a DHCP packet containing Option 148 to the switch again.
  7. The switch obtains its management IP address and obtains the cloud management platform's IP address/URL and port number based on Option 148.
The switch uses the obtained cloud management platform's IP address/URL and port number to register with the cloud management platform for authentication.

PNP VLAN Auto-Negotiation

  • Background

    In Figure 5-2, SwitchA and SwitchB register with the cloud management platform, and then the cloud management platform changes the management VLAN to another VLAN, which is not the default one, VLAN 1. The VLAN for the IP address pool of the DHCP server is also changed to the management VLAN. An unconfigured switch, SwitchC, is connected to SwitchA. After SwitchC is powered on and starts, it sends a request packet containing VLAN 1 to the DHCP server to obtain the device management mode and cloud management platform's address information. However, the VLAN for the IP address pool of the DHCP server has been changed to a VLAN, which is not VLAN 1, so SwitchC cannot obtain the device management mode and cloud management platform's address information and cannot register with the cloud management platform.

    To solve this problem, PNP VLAN auto-negotiation is used:
    1. SwitchA registers with the cloud management platform successfully, and then the cloud management platform delivers a PNP VLAN to SwitchA based on the preconfiguration. SwitchA can use this PNP VLAN to communicate with the DHCP server normally.
    2. SwitchC connects to the network and auto-negotiates a PNP VLAN with the upstream device, SwitchA.
    3. SwitchC uses the negotiated PNP VLAN to obtain the device management mode and cloud management platform's address information from the DHCP server. This process implements plug and play of newly added devices.
    Figure 5-2  Cloud management platform
    PNP VLAN auto-negotiation provides the following advantages:
    • A new device can connect to the cloud network through any interface of an upstream device, and the upstream device can identify the access interface and adds it to the PNP VLAN.
    • If an upstream device and a downstream device are connected through multiple links, they can auto-negotiate the multiple links as an Eth-Trunk interface and auto-negotiate the working mode of the Eth-Trunk interface as Link Aggregation Control Protocol (LACP) mode.
  • Addition of a new unconfigured switch to a cloud network

    In Figure 5-3:
    1. An unconfigured switch starts and sends LLDP packets to negotiate with the upstream device in an effort to obtain the PNP VLAN configured on the upstream device.
    2. The switch uses the negotiated PNP VLAN to obtain the device management mode and cloud management platform's address information from the DHCP server. The switch uses the negotiated PNP VLAN to send DHCP request packets regardless of whether it can use VLAN 1 to receive DHCP response packets. That is, a PNP VLAN takes precedence over VLAN 1.
    3. The switch determines whether to change to the cloud-based management mode and restart based on the device management mode obtained from the DHCP server. If the switch is working in cloud-based management mode, it does not need to change its management mode and restart.
    4. The switch registers with the cloud management platform based on the cloud management platform's address information obtained from the DHCP server.
    5. The cloud management platform delivers the PNP VLAN configuration to the switch based on the preconfiguration so that a new switch connected to this switch can perform PNP VLAN auto-negotiation with this switch. The PNP VLAN configuration includes: PNP VLAN ID, enabling the function of transmitting a PNP VLAN to a downstream device, enabling the function of sending LLDP packets containing PNP VLAN information to a downstream device (this function is enabled by default), and enabling the function of transmitting the flag indicating whether to establish an Eth-Trunk to a downstream device.
    Figure 5-3  Adding a new unconfigured switch to a cloud network
  • Processing PNP VLAN switchover

    In Figure 5-4, the cloud management platform changes the PNP VLAN of an upstream device to enable a downstream device to use a new PNP VLAN to register with the cloud management platform again.

    The upstream device's PNP VLAN and management VLAN are two concepts. The two VLANs can be the same or different. The downstream device can register with the cloud management platform normally when the cloud management platform can communicate with the upstream device normally.

    Changing the PNP VLAN enables only the downstream device but not the upstream device to register with the cloud management platform again. Whether the upstream device registers with the cloud management platform again depends on whether its management VLAN is changed.

    Figure 5-4  Processing PNP VLAN switchover
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100065674

Views: 41535

Downloads: 356

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