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).
SVF Setup

SVF Setup

Operations Performed by Different Roles During SVF Setup

NOTE:

The parent can be a standalone device, a stack, or a cluster switch system (CSS). An AS can be a standalone device or a stack. If an AS is a stack, see "Restrictions on SVF Roles" in Licensing Requirements and Limitations for SVF.

Figure 4-5  SVF networking

In Figure 4-5, SVF allows the parent and client to establish a Control And Provisioning of Wireless Access Points (CAPWAP) link as the control channel for unified client configuration and management. This process is similar to AP management by an AC in WLANs. During SVF setup, some operations need to be performed on the parent and client to establish a CAPWAP link.

The parent is directly connected to level-1 ASs, but level-1 ASs are not connected to level-2 ASs.

No.

Role

Operations

1

Parent

  • Create a management VLAN for Layer 2 communication with the client.
  • Configure a DHCP address pool to allocate a management IP address to the client.
  • Create a CAPWAP source interface for communication with the client.
  • Enable the SVF function on the parent.
2

Fabric port between the parent and a level-1 AS

  • Parent-side fabric port (numbered 1 in Figure 4-5): Manually add a physical member port of the level-1 AS to the fabric port.
  • Level-1 AS-side fabric port (numbered 2 in Figure 4-5): Enable the level-1 AS and parent to automatically negotiate a fabric port after the parent-side fabric port is configured.
3

Level-1 AS

  • Change to the client mode.

    A switch in client mode has no independent configuration file, and you cannot configure services on it directly. All configurations are delivered to client switches from the parent. If a switch has no configuration file and no input on the console port, it performs auto-negotiation with the parent to change its mode.

    If the switch negotiating as the client is not connected to the parent within 10 minutes after restarting, the switch changes to the standalone mode again. You can also forcibly change the switch from the client mode to standalone mode.

  • Obtain management VLAN information automatically through the parent.

The parent is directly connected to level-1 ASs, and level-1 ASs are connected to level-2 ASs.

No.

Role

Operations

1

Parent

  • Create a management VLAN for Layer 2 communication with the client.
  • Configure a DHCP address pool to allocate a management IP address to the client.
  • Create a CAPWAP source interface for communication with the client.
  • Enable the SVF function on the parent.
2

Fabric port between the parent and a level-1 AS

  • Parent-side fabric port (numbered 1 in Figure 4-5): Manually add a physical member port of the level-1 AS to the fabric port.
  • Level-1 AS-side fabric port (numbered 2 in Figure 4-5): Enable the level-1 AS and parent to automatically negotiate a fabric port after the parent-side fabric port is configured.
3

Level-1 AS

  • Change to the client mode.

    A switch in client mode has no independent configuration file, and you cannot configure services on it directly. All configurations are delivered to client switches from the parent. If a switch has no configuration file and no input on the console port, it performs auto-negotiation with the parent to change its mode.

    If the switch negotiating as the client is not connected to the parent within 10 minutes after restarting, the switch changes to the standalone mode again. You can also forcibly change the switch from the client mode to standalone mode.

  • Obtain management VLAN information automatically through the parent.

4

Fabric port between a level-1 AS and a level-2 AS

  • Level-1 AS-side fabric port (numbered 5 in Figure 4-5): On the parent, manually add a physical member port of the level-2 AS to the fabric port.
  • Level-2 AS-side fabric port (numbered 6 in Figure 4-5): Enable the level-2 AS and level-1 AS to automatically negotiate a fabric port.
5

Level-2 AS

  • Change to the client mode, similarly to the way a level-1 AS changes to the client mode.

  • Obtain management VLAN information automatically through the parent.

The parent is connected to level-1 AS across a network.

No.

Role

Operations

1

Parent

  • Create a management VLAN for Layer 2 communication with the client.
  • Configure a DHCP address pool to allocate a management IP address to the client.
  • Create a CAPWAP source interface for communication with the client.
  • Enable the SVF function on the parent.
2

Fabric port between the parent and a level-1 AS

  • Parent-side fabric port (numbered 3 in Figure 4-5): Manually add a physical member port of the level-1 AS to the fabric port, and change the fabric port to the indirect connection mode.
  • Level-1 AS-side fabric port (numbered 4 in Figure 4-5): Manually add a physical member port that connects the level-1 AS to the parent.
3

Level-1 AS

  • Manually force the level-1 AS to change to the client mode.

  • Configure a management VLAN on the level-1 AS, which must be consistent with the management VLAN of the parent.

SVF Setup Process

An SVF system goes through the following phases before being setting up:
  1. Neighbor discovery: A parent sends information including the management VLAN to an AS through neighbor discovery.

  2. Device management: The AS obtains an IP address through DHCP and establishes a Control And Provisioning of Wireless Access Points (CAPWAP) link with the parent and registers with the parent.

  3. Version management: The AS checks whether its software version is the same as that of the parent. If not, the AS downloads the system software from the parent to upgrade and synchronize its software version with that of the parent.

  4. Topology management: The parent collects LLDP neighbor information of all ASs and calculates the SVF topology.

  5. Service configuration: In direct configuration mode, the parent sends service configurations to ASs over CAPWAP links. In independent configuration mode, service configurations are performed on ASs independently.

Figure 4-6  Flowchart for SVF setup
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100065674

Views: 50172

Downloads: 435

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