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

S600-E V200R013C00 Configuration Guide - Device Management

This document describes the configurations of Device Management, including device status query, hardware management, Stack, SVF, cloud-based management, PoE, OPS, energy-saving management, information center, fault management, NTP.
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).
Process of Registering a Stack with the Cloud Management Platform

Process of Registering a Stack with the Cloud Management Platform

NOTE:

After a stack is changed to the cloud-based management mode, the stack does not support multi-active detection (MAD).

A stack can be registered with the cloud management platform only after being set up. Setting up a stack by delivering the stack configuration through the cloud management platform is not supported.

Stack members can be registered with the cloud management platform only when the platform has the ESNs of the members.

Stack Registration

Figure 5-8  Registering a stack with the cloud management platform
A stack can be registered successfully only when information about stack members is consistent with that configured on the cloud management platform.
  • If the stack status (standalone or stack mode) of the stack master is different from that configured on the cloud management platform, the stack cannot be registered.
  • When a stack member does not exist on the cloud management platform (determined based on the ESN), the cloud management platform instructs the stack member to restart after the stack master reports the stack member information to the cloud management platform. After a stack member is restarted and registered with the cloud management platform, the stack member is restarted again until it is removed from the stack or its ESN is added to the cloud management platform.
  • If the slot ID of a stack member is different from that configured on the cloud management platform, the cloud management platform instructs the stack member to use the slot ID configured on the cloud management platform to restart. After the restart, the stack member can be registered with the cloud management platform successfully.
  • If the stack priority of a stack member is different from that configured on the cloud management platform, the cloud management platform instructs the stack member to change its stack priority to the same as that configured on the cloud management platform. After the change, the stack member can be registered with the cloud management platform successfully.

Adding a Member Switch to a Stack

When a new stack member connects to a stack through an ordinary service port cable, it cannot be added to the stack or registered with the cloud management platform because the cloud management platform cannot configure stack port information for the stack.

When a new stack member connects to a stack using a dedicated stack cable or stack card, it can be added to the stack without having any configurations performed in the stack. After its ESN is added to the cloud management platform, the stack member can be registered with the cloud management platform successfully.

A new stack member can be registered with the cloud management platform only after its ESN is added to the cloud management platform. Otherwise, it will be restarted repeatedly.

When the stack master detects that a new stack member is added to the stack, the master sends information about the new member to the cloud management platform. The cloud management platform compares the configurations of the new member with those on the cloud management platform. The process is the same as that when a stack is registered with the cloud management platform for the first time.
  • If the configurations are the same, the cloud management platform allows the new member to register with it.
  • If the ESN of the new member does not exist on the cloud management platform, the cloud management platform instructs the new member to restart and does not allow the new member to register with it.
  • If the slot IDs are different, the new member needs to change its slot ID to the same as that configured on the cloud management platform, restart, and register the cloud management platform again.

Removing a Member Switch from a Stack

  • If a stack member or its stack link is faulty, the stack member needs to be removed from the stack. The stack master sends a message to the cloud management platform, which then sets the status of the stack member to offline.
  • If the cloud management platform removes the stack member from the stack, the cloud management platform instructs the stack to restart the stack member. Information about the stack member does not exist on the cloud management platform. If the stack member is not removed from the stack, the stack member will be restarted repeatedly.

Stack Version Upgrade

Figure 5-9  Stack version upgrade process
Translation
Download
Updated: 2019-04-20

Document ID: EDOC1100066159

Views: 25970

Downloads: 3

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