(Optional) Deploying Multi-Controller Storage Systems

Procedure

1. Use the serial port to log in to a switch.
2. Run the system-view command to go to the system view.
3. Run the command-privilege level rearrange command to improve command levels in batches.
4. Run the commit command to commit the configuration.
5. Run the aaa command to enter the AAA view.
6. Configure the SSH login user for the switch.
   1. Run the undo local-user policy security-enhance command to delete SSH login security policies.
   2. Run the local-user username password irreversible-cipher password command to add a user.

      username is the user name and password is the user's password.

   3. Run the local-user username service-type ssh command to set the user service model.
   4. Run the local-user username level 15 command to set the user level.

7. Change the IP address of the management network port of the switch.
   1. Run the interface MEth0/0/0 command to enter the management network port view.
   2. Run the ip address ipaddress mask command to set the IP address.

      ipaddress is the new IP address of the management network port and mask is the subnet mask of the management network port.

   3. Optional: Run the ip route-static ipaddress mask gateway command to set the switch gateway.

      ipaddress indicates the destination network segment, mask indicates the subnet mask of the destination network segment, and gateway indicates the gateway.

   If the switches, the maintenance terminal where SmartKit resides, and the original storage system are not on the same network, you need to set the switch gateway. To ensure that IP addresses on all network segments can access switches, you are advised to set a default gateway, namely, set ipaddress and mask to 0.0.0.0 and 0.0.0.0.

8. Run the user-interface maximum-vty number command to change the number of SSH connections.

   number is the maximum number of SSH connections and the value ranges from 0 to 21.

   If SmartKit is used to configure switches, you are advised to set number to a value larger than six.

9. Run the stelnet server enable command to enable the SSH service.
10. Run the ssh authentication-type default password command to set the SSH user authentication mode to password authentication.
11. Run the user-interface vty 0 n command to set the number of concurrent users.

    n indicates the number of concurrent users and the value must be smaller than that set in 8.

12. Run the authentication-mode aaa command to set the user authentication mode.
13. Run the user privilege level 15 command to set the user level.
14. Run the protocol inbound ssh command to enable the user to support the SSH protocol.
15. Run the quit command to return to the system view.
16. Run the rsa local-key-pair create command to generate the SSH public key for the user.
17. Run the commit command to submit the configuration file.
18. Run the quit command to exit the system view.
19. Run the save command to save the configuration file.

Context

If you use SmartKit to configure a switch, modify the IP address of the switch's management network port to ensure that this IP address resides in the same network with that of the storage system.

Before modifying the IP address of a switch's management network port and the SSH account, run the reset saved-configuration command to reset the configuration file of the switch. In the mean time, run the reboot command to restart the switch for the resetting to take effect.

• The two switches used for controller expansion must be of the same model.
• Switches for controller expansion can only be used for scale-out networking. Do not use them for front-end service networking or other purposes.
• Switches used for controller expansion cannot be stacked or cascaded.
• Do not upgrade the firmware of the switches used for controller expansion.

Procedure

1. Log in to the switch using the serial port.
2. Run the system-view command to go to the system view.
3. Change the IP address of the management network port of the switch.
   1. Run the interface MEth 0/0/0 command to enter the management network port.
   2. Run the undo ip binding vpn-instance _management_vpn_ command to unbind the interface from the VPN instance.

      If the following error message is displayed, the interface has been unbound from the VPN instance. Ignore the error message.

      [*HUAWEI-MEth0/0/0]undo ip binding vpn-instance _management_vpn_
      Error: The VPN instance is not bound to the interface.

   3. Run the commit command to commit the configuration.
   4. Run the ip address ipaddress mask command to set the IP address.

      ipaddress is the new IP address of the management network port and mask is the subnet mask.

   5. (Optional) Run the ip route-static ipaddress mask gateway command to set the switch gateway.

      ipaddress is the destination network segment, mask is the subnet mask of the destination network segment, and gateway is the gateway.

      If the switches, the maintenance terminal where SmartKit resides, and the original storage system are not on the same network, you must set the switch gateway. To ensure that IP addresses on all network segments can access the switches, you are advised to use the default gateway, that is, set ipaddress and mask to 0.0.0.0 and 0.0.0.0.

   6. Run the commit command to commit the configuration.
   7. Run the quit command.

4. Set the user authentication mode and enable the user to support the SSH protocol.
   1. Run the system-view command to go to the system view.
   2. Run the user-interface vty 0 4 command to set the number of concurrent users.
   3. Run the authentication-mode aaa command to set the user authentication mode.
   4. Run the protocol inbound ssh command to enable the user to support the SSH protocol.
   5. Run the quit command to return to the system view.
   6. Run the commit command to commit the configuration.

5. Set the AAA local user name and password.
   1. Run the aaa command to enter the AAA view.
   2. Run the local-user username password irreversible-cipher password command to add an AAA local user.

      In the command, username indicates the user name, and password indicates the password of the user.

   3. Run the local-user username service-type ssh terminal command to set the user service mode.
   4. Run the local-user username privilege level 3 command to set the user level.
   5. Run the quit command to return to the system view.
   6. Run the commit command to commit the configuration.

6. Create an SSH user and configure the authentication mode and service type for the user.
   1. Run the ssh user username command to create an SSH user with the same name as the AAA local user.
   2. Run the ssh user username authentication-type password command to set the SSH user authentication mode to password authentication.
   3. Run the ssh user username service-type stelnet command to set the service type of the SSH user to STelnet.
   4. Run the ssh server-source -i meth 0/0/0 command to configure the source interface of the SSH server.

      If the login address is an IPv6 address, run the ssh ipv6 server-source -a ipv6-address command to configure the source IP address of the SSH server.

   5. Run the stelnet server enable command to enable the STelnet server functions.
   6. Run the commit command to commit the configuration.

7. Run the ssh server publickey ecc rsa rsa_sha2_256 rsa_sha2_512 command to enable the ECC and RSA encryption algorithms.
8. Run the quit command to exit the system view.
9. Run the save command to save the configuration file.
10. Run the reboot command to restart the switch for the configurations to take effect.
11. Log in to the switch using SSH as the SSH user created in 6 and set the password as prompted.

Procedure for Configuring Switch 0

1. Set the global parameters of the spanning tree.

   //Enter the system view.
   system-view 
   //Set the spanning tree mode to MSTP.
   stp mode mstp 
   //Validate the spanning tree configuration.
   commit 
   //Enter the spanning tree configuration view.
   stp region-configuration 
   //Configure a spanning tree instance.
   instance 1 vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 1200 to 1203 1300 to 1303 4005 4007 
   instance 1 vlan 4010 4011 
   instance 2 vlan 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4008 
   //Validate the spanning tree configuration.
   commit 
   //Exit the spanning tree configuration view.
   quit

2. Configure spanning tree ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations for other spanning tree functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Enable root bridge protection on the ports.
     stp root-protection 
     //Enable the edge port function.
     stp edged-port enable 
     //Validate the port configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Enable root bridge protection on the port.
     stp root-protection 
     //Enable the edge port function.
     stp edged-port enable 
     //Validate the port configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

3. Configure global LLDP parameters.

   //Configure the system name.
   sysname STORAGE-SCALE-SW-0 
   //Enable LLDP globally.
   lldp enable 
   //Set the number of LLDP packets to be quickly sent.
   lldp fast-count 3 
   //Set the LLDP restart delay.
   lldp restart 1 
   //Set the interval for sending LLDP packets.
   lldp transmit interval 20 
   //Configure the LLDP keepalive factor.
   lldp transmit multiplier 10 
   //Validate all the preceding configurations.
   commit

4. Configure LLDP ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other LLDP functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Enable LLDP on the ports.
     undo lldp disable 
     //Allow LLDP packet transmission and reception.
     lldp admin-status txrx 
     //Validate all the preceding configurations.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Enable LLDP on the port.
     undo lldp disable 
     //Allow LLDP packet transmission and reception.
     lldp admin-status txrx 
     //Validate all the preceding configurations.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

5. Configure global RDMA parameters.

   //Create a WRED drop profile and enter the WRED drop profile view.
   drop-profile ecn_100G 
   //Configure ECN parameters.
   ecn buffer-size low-limit 7000 high-limit 750000 discard-percentage 30 
   //Validate the configuration.
   commit 
   //Exit the WRED drop profile view.
   quit 
   //Configure the accuracy of the hardware-based PFC deadlock detection interval and recovery time.
   dcb pfc deadlock-detect interval 100 
   //Validate the configuration.
   commit 
   //Enter the default PFC configuration view.
   dcb pfc 
   //Configure the RDMA link forwarding priority.
   priority 2 3 
   //Configure PFC deadlock detection.
   priority 2 deadlock-detect time 2 deadlock-recovery time 15 
   priority 2 turn-off threshold 20 
   priority 3 deadlock-detect time 2 deadlock-recovery time 15 
   priority 3 turn-off threshold 20 
   //Validate the configuration.
   commit 
   //Exit the global RDMA configuration view.
   quit 

6. Configure the RDMA parameters of ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other RDMA functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Configure the port forwarding priority and QoS parameters.
     undo flow-control 
     dcb pfc enable mode manual 
     dcb pfc buffer 2 xoff dynamic 4 
     dcb pfc buffer 3 xoff dynamic 4 
     qos drr 0 2 3 
     qos queue 0 drr weight 10 
     qos queue 2 drr weight 90 
     qos queue 3 drr weight 90 
     qos buffer queue 0 shared-threshold dynamic 1 
     qos buffer queue 2 shared-threshold dynamic 10 
     qos buffer queue 3 shared-threshold dynamic 10 
     qos queue 2 wred ecn_100G 
     qos queue 3 wred ecn_100G 
     qos queue 2 ecn 
     qos queue 3 ecn 
     //Validate the configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Configure the port forwarding priority and QoS parameters.
     undo flow-control 
     dcb pfc enable mode manual 
     dcb pfc buffer 2 xoff dynamic 4 
     dcb pfc buffer 3 xoff dynamic 4 
     qos drr 0 2 3 
     qos queue 0 drr weight 10 
     qos queue 2 drr weight 90 
     qos queue 3 drr weight 90 
     qos buffer queue 0 shared-threshold dynamic 1 
     qos buffer queue 2 shared-threshold dynamic 10 
     qos buffer queue 3 shared-threshold dynamic 10 
     qos queue 2 wred ecn_100G 
     qos queue 3 wred ecn_100G 
     qos queue 2 ecn 
     qos queue 3 ecn 
     //Validate the configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

7. Configure global VLAN parameters.

   //Create VLANs in a batch.
   vlan batch 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
   vlan batch 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
   //Validate the configuration.
   commit

8. Set port VLAN parameters.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other VLAN functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Set the ports to work in trunk mode.
     port link-type trunk 
     //Configure the PVID.
     port trunk pvid vlan 1 
     //Configure allowed VLAN IDs.
     port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
     port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
     //Validate the port configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Set the port to work in trunk mode.
     port link-type trunk 
     //Configure the PVID.
     port trunk pvid vlan 1 
     //Configure allowed VLAN IDs.
     port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
     port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
     //Validate the port configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit 
     

9. Save the settings.

   //Enter the user view.
   quit
   //Save the settings.
   save STORAGE-SCALE-SW-0.cfg 
   //Modify the boot items for the next startup.
   startup saved-configuration STORAGE-SCALE-SW-0.cfg

Procedure for Configuring Switch 1

1. Set the global parameters of the spanning tree.

   //Enter the system view.
   system-view 
   //Set the spanning tree mode to MSTP.
   stp mode mstp 
   //Validate the spanning tree configuration.
   commit 
   //Enter the spanning tree configuration view.
   stp region-configuration 
   //Configure a spanning tree instance.
   instance 1 vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 1200 to 1203 1300 to 1303 4005 4007 
   instance 1 vlan 4010 4011 
   instance 2 vlan 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4008 
   //Validate the spanning tree configuration.
   commit 
   //Exit the spanning tree configuration view.
   quit

2. Configure spanning tree ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations for other spanning tree functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Enable root bridge protection on the ports.
     stp root-protection 
     //Enable the edge port function.
     stp edged-port enable 
     //Validate the port configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Enable root bridge protection on the port.
     stp root-protection 
     //Enable the edge port function.
     stp edged-port enable 
     //Validate the port configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

3. Configure global LLDP parameters.

   //Configure the system name.
   sysname STORAGE-SCALE-SW-1 
   //Enable LLDP globally.
   lldp enable 
   //Set the number of LLDP packets to be quickly sent.
   lldp fast-count 3 
   //Set the LLDP restart delay.
   lldp restart 1 
   //Set the interval for sending LLDP packets.
   lldp transmit interval 20 
   //Configure the LLDP keepalive factor.
   lldp transmit multiplier 10 
   //Validate all the preceding configurations.
   commit

4. Configure LLDP ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other LLDP functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Enable LLDP on the ports.
     undo lldp disable 
     //Allow LLDP packet transmission and reception.
     lldp admin-status txrx 
     //Validate all the preceding configurations.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Enable LLDP on the port.
     undo lldp disable 
     //Allow LLDP packet transmission and reception.
     lldp admin-status txrx 
     //Validate all the preceding configurations.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

5. Configure global RDMA parameters.

   //Create a WRED drop profile and enter the WRED drop profile view.
   drop-profile ecn_100G 
   //Configure ECN parameters.
   ecn buffer-size low-limit 7000 high-limit 750000 discard-percentage 30 
   //Validate the configuration.
   commit 
   //Exit the WRED drop profile view.
   quit 
   //Configure the accuracy of the hardware-based PFC deadlock detection interval and recovery time.
   dcb pfc deadlock-detect interval 100 
   //Validate the configuration.
   commit 
   //Enter the default PFC configuration view.
   dcb pfc 
   //Configure the RDMA link forwarding priority.
   priority 2 3 
   //Configure PFC deadlock detection.
   priority 2 deadlock-detect time 2 deadlock-recovery time 15 
   priority 2 turn-off threshold 20 
   priority 3 deadlock-detect time 2 deadlock-recovery time 15 
   priority 3 turn-off threshold 20 
   //Validate the configuration.
   commit 
   //Exit the global RDMA configuration view.
   quit 

6. Configure the RDMA parameters of ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other RDMA functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Configure the port forwarding priority and QoS parameters.
     undo flow-control 
     dcb pfc enable mode manual 
     dcb pfc buffer 2 xoff dynamic 4 
     dcb pfc buffer 3 xoff dynamic 4 
     qos drr 0 2 3 
     qos queue 0 drr weight 10 
     qos queue 2 drr weight 90 
     qos queue 3 drr weight 90 
     qos buffer queue 0 shared-threshold dynamic 1 
     qos buffer queue 2 shared-threshold dynamic 10 
     qos buffer queue 3 shared-threshold dynamic 10 
     qos queue 2 wred ecn_100G 
     qos queue 3 wred ecn_100G 
     qos queue 2 ecn 
     qos queue 3 ecn 
     //Validate the configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Configure the port forwarding priority and QoS parameters.
     undo flow-control 
     dcb pfc enable mode manual 
     dcb pfc buffer 2 xoff dynamic 4 
     dcb pfc buffer 3 xoff dynamic 4 
     qos drr 0 2 3 
     qos queue 0 drr weight 10 
     qos queue 2 drr weight 90 
     qos queue 3 drr weight 90 
     qos buffer queue 0 shared-threshold dynamic 1 
     qos buffer queue 2 shared-threshold dynamic 10 
     qos buffer queue 3 shared-threshold dynamic 10 
     qos queue 2 wred ecn_100G 
     qos queue 3 wred ecn_100G 
     qos queue 2 ecn 
     qos queue 3 ecn 
     //Validate the configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

7. Configure global VLAN parameters.

   //Create VLANs in a batch.
   vlan batch 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
   vlan batch 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
   //Validate the configuration.
   commit

8. Set port VLAN parameters.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other VLAN functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Set the ports to work in trunk mode.
     port link-type trunk 
     //Configure the PVID.
     port trunk pvid vlan 1 
     //Configure allowed VLAN IDs.
     port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
     port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
     //Validate the port configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Set the port to work in trunk mode.
     port link-type trunk 
     //Configure the PVID.
     port trunk pvid vlan 1 
     //Configure allowed VLAN IDs.
     port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
     port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
     //Validate the port configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit 
     

9. Save the settings.

   //Enter the user view.
   quit
   //Save the settings.
   save STORAGE-SCALE-SW-1.cfg 
   //Modify the boot items for the next startup.
   startup saved-configuration STORAGE-SCALE-SW-1.cfg

Procedure for Configuring Switch 0

1. Set the global parameters of the spanning tree.

   //Enter the system view.
   system-view 
   //Set the spanning tree mode to MSTP.
   stp mode mstp 
   //Validate the spanning tree configuration.
   commit 
   //Enter the spanning tree configuration view.
   stp region-configuration 
   //Configure a spanning tree instance.
   instance 1 vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 1200 to 1203 1300 to 1303 4005 4007
   instance 1 vlan 4010 4011
   instance 2 vlan 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4008
   //Validate the spanning tree configuration.
   commit 
   //Exit the spanning tree configuration view.
   quit

2. Configure spanning tree ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations for other spanning tree functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Enable root bridge protection on the ports.
     stp root-protection 
     //Enable the edge port function.
     stp edged-port enable 
     //Validate the port configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Enable root bridge protection on the port.
     stp root-protection 
     //Enable the edge port function.
     stp edged-port enable 
     //Validate the port configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

3. Configure global LLDP parameters.

   //Configure the system name.
   sysname STORAGE-SCALE-SW-0 
   //Enable LLDP globally.
   lldp enable 
   //Set the number of LLDP packets to be quickly sent.
   lldp fast-count 3 
   //Set the LLDP restart delay.
   lldp restart 1 
   //Set the interval for sending LLDP packets.
   lldp transmit interval 20 
   //Configure the LLDP keepalive factor.
   lldp transmit multiplier 10 
   //Validate all the preceding configurations.
   commit

4. Configure LLDP ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other LLDP functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Enable LLDP on the ports.
     undo lldp disable 
     //Allow LLDP packet transmission and reception.
     lldp admin-status txrx 
     //Validate all the preceding configurations.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Enable LLDP on the port.
     undo lldp disable 
     //Allow LLDP packet transmission and reception.
     lldp admin-status txrx 
     //Validate all the preceding configurations.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

5. Configure global RDMA parameters.

   //Create a WRED drop profile and enter the WRED drop profile view.
   drop-profile ecn_100G 
   //Configure ECN parameters.
   ecn buffer-size low-limit 7000 high-limit 750000 discard-percentage 30 
   //Validate the configuration.
   commit 
   //Exit the WRED drop profile view.
   quit 
   //Configure the accuracy of the hardware-based PFC deadlock detection interval and recovery time.
   dcb pfc deadlock-detect timer 100 
   //Validate the configuration.
   commit 
   //Enter the default PFC configuration view.
   dcb pfc 
   //Configure the RDMA link forwarding priority.
   priority 2 3 
   //Configure PFC deadlock detection.
   priority 2 turn-off threshold 30
   priority 3 turn-off threshold 30
   dcb pfc deadlock recovery-behavior forwarding slot 1
   dcb pfc deadlock-detect timer 200
   dcb pfc deadlock-recovery timer 1500
   //Validate the configuration.
   commit 
   //Exit the global RDMA configuration view.
   quit 

6. Configure the RDMA parameters of ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other RDMA functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Configure the port forwarding priority and QoS parameters.
     dcb pfc enable mode manual
     dcb pfc buffer 2 xon dynamic 6 xoff dynamic 9
     dcb pfc buffer 3 xon dynamic 6 xoff dynamic 9
     qos drr 0 2 3
     qos queue 0 drr weight 10
     qos queue 2 drr weight 90
     qos queue 3 drr weight 90
     qos buffer queue 0 shared-threshold dynamic 1
     qos buffer queue 2 shared-threshold dynamic 10
     qos buffer queue 3 shared-threshold dynamic 10
     qos queue 2 wred ecn_100G
     qos queue 3 wred ecn_100G
     qos queue 2 ecn
     qos queue 3 ecn
     //Validate the configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Configure the port forwarding priority and QoS parameters.
     dcb pfc enable mode manual
     dcb pfc buffer 2 xon dynamic 6 xoff dynamic 9 
     dcb pfc buffer 3 xon dynamic 6 xoff dynamic 9
     qos drr 0 2 3        
     qos queue 0 drr weight 10
     qos queue 2 drr weight 90
     qos queue 3 drr weight 90
     qos buffer queue 0 shared-threshold dynamic 1
     qos buffer queue 2 shared-threshold dynamic 10
     qos buffer queue 3 shared-threshold dynamic 10
     qos queue 2 wred ecn_100G
     qos queue 3 wred ecn_100G
     qos queue 2 ecn
     qos queue 3 ecn
     //Validate the configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

7. Configure global VLAN parameters.

   //Create VLANs in a batch.
   vlan batch 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
   vlan batch 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
   //Validate the configuration.
   commit

8. Set port VLAN parameters.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other VLAN functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Set the ports to work in trunk mode.
     port link-type trunk 
     //Configure the PVID.
     port trunk pvid vlan 1 
     //Configure allowed VLAN IDs.
     port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
     port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
     //Validate the port configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Set the port to work in trunk mode.
     port link-type trunk 
     //Configure the PVID.
     port trunk pvid vlan 1 
     //Configure allowed VLAN IDs.
     port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
     port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
     //Validate the port configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit 
     

9. Save the settings.

   //Enter the user view.
   quit
   //Save the settings.
   save STORAGE-SCALE-SW-0.cfg 
   //Modify the boot items for the next startup.
   startup saved-configuration STORAGE-SCALE-SW-0.cfg

Procedure for Configuring Switch 1

1. Set the global parameters of the spanning tree.

   //Enter the system view.
   system-view 
   //Set the spanning tree mode to MSTP.
   stp mode mstp 
   //Validate the spanning tree configuration.
   commit 
   //Enter the spanning tree configuration view.
   stp region-configuration 
   //Configure a spanning tree instance.
   instance 1 vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 1200 to 1203 1300 to 1303 4005 4007
   instance 1 vlan 4010 4011
   instance 2 vlan 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4008
   //Validate the spanning tree configuration.
   commit 
   //Exit the spanning tree configuration view.
   quit

2. Configure spanning tree ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations for other spanning tree functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Enable root bridge protection on the ports.
     stp root-protection 
     //Enable the edge port function.
     stp edged-port enable 
     //Validate the port configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Enable root bridge protection on the port.
     stp root-protection 
     //Enable the edge port function.
     stp edged-port enable 
     //Validate the port configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

3. Configure global LLDP parameters.

   //Configure the system name.
   sysname STORAGE-SCALE-SW-1 
   //Enable LLDP globally.
   lldp enable 
   //Set the number of LLDP packets to be quickly sent.
   lldp fast-count 3 
   //Set the LLDP restart delay.
   lldp restart 1 
   //Set the interval for sending LLDP packets.
   lldp transmit interval 20 
   //Configure the LLDP keepalive factor.
   lldp transmit multiplier 10 
   //Validate all the preceding configurations.
   commit

4. Configure LLDP ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other LLDP functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Enable LLDP on the ports.
     undo lldp disable 
     //Allow LLDP packet transmission and reception.
     lldp admin-status txrx 
     //Validate all the preceding configurations.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Enable LLDP on the port.
     undo lldp disable 
     //Allow LLDP packet transmission and reception.
     lldp admin-status txrx 
     //Validate all the preceding configurations.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

5. Configure global RDMA parameters.

   //Create a WRED drop profile and enter the WRED drop profile view.
   drop-profile ecn_100G 
   //Configure ECN parameters.
   ecn buffer-size low-limit 7000 high-limit 750000 discard-percentage 30 
   //Validate the configuration.
   commit 
   //Exit the WRED drop profile view.
   quit 
   //Configure the accuracy of the hardware-based PFC deadlock detection interval and recovery time.
   dcb pfc deadlock-detect timer 100 
   //Validate the configuration.
   commit 
   //Enter the default PFC configuration view.
   dcb pfc 
   //Configure the RDMA link forwarding priority.
   priority 2 3 
   //Configure PFC deadlock detection.
   priority 2 turn-off threshold 30
   priority 3 turn-off threshold 30
   dcb pfc deadlock recovery-behavior forwarding slot 1
   dcb pfc deadlock-detect timer 200
   dcb pfc deadlock-recovery timer 1500
   //Validate the configuration.
   commit 
   //Exit the global RDMA configuration view.
   quit 

6. Configure the RDMA parameters of ports.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other RDMA functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Configure the port forwarding priority and QoS parameters.
     dcb pfc enable mode manual
     dcb pfc buffer 2 xon dynamic 6 xoff dynamic 9
     dcb pfc buffer 3 xon dynamic 6 xoff dynamic 9
     qos drr 0 2 3
     qos queue 0 drr weight 10
     qos queue 2 drr weight 90
     qos queue 3 drr weight 90
     qos buffer queue 0 shared-threshold dynamic 1
     qos buffer queue 2 shared-threshold dynamic 10
     qos buffer queue 3 shared-threshold dynamic 10
     qos queue 2 wred ecn_100G
     qos queue 3 wred ecn_100G
     qos queue 2 ecn
     qos queue 3 ecn
     //Validate the configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Configure the port forwarding priority and QoS parameters.
     dcb pfc enable mode manual
     dcb pfc buffer 2 xon dynamic 6 xoff dynamic 9 
     dcb pfc buffer 3 xon dynamic 6 xoff dynamic 9
     qos drr 0 2 3        
     qos queue 0 drr weight 10
     qos queue 2 drr weight 90
     qos queue 3 drr weight 90
     qos buffer queue 0 shared-threshold dynamic 1
     qos buffer queue 2 shared-threshold dynamic 10
     qos buffer queue 3 shared-threshold dynamic 10
     qos queue 2 wred ecn_100G
     qos queue 3 wred ecn_100G
     qos queue 2 ecn
     qos queue 3 ecn
     //Validate the configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit

7. Configure global VLAN parameters.

   //Create VLANs in a batch.
   vlan batch 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
   vlan batch 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
   //Validate the configuration.
   commit

8. Set port VLAN parameters.
   • Ports can be configured in batches or one by one.
   • Retain the default configurations of other VLAN functions.
   • Method 1: Configure ports in batches.

     //Enter the batch port configuration view.
     port-group group-member 100GE 1/0/1 to 100GE 1/0/32 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Set the ports to work in trunk mode.
     port link-type trunk 
     //Configure the PVID.
     port trunk pvid vlan 1 
     //Configure allowed VLAN IDs.
     port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
     port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
     //Validate the port configuration.
     commit 
     //Exit the batch port configuration view.
     quit

   • Method 2: Configure each port separately.

     The following uses port 100GE 1/0/1 as an example. Perform this step on ports 100GE 1/0/1 to 100GE 1/0/32 in sequence.

     //Enter the configuration view of port 100GE 1/0/1.
     interface 100GE 1/0/1 
     //Change the mode of an Ethernet interface from Layer 3 to Layer 2.
     portswitch
     //Set the port to work in trunk mode.
     port link-type trunk 
     //Configure the PVID.
     port trunk pvid vlan 1 
     //Configure allowed VLAN IDs.
     port trunk allow-pass vlan 200 to 203 300 to 303 400 to 403 500 to 503 1000 to 1004 1100 to 1104 4011 
     port trunk allow-pass vlan 1200 to 1203 1300 to 1303 2000 to 2003 2100 to 2103 2200 to 2203 2300 to 2303 4005 4007 4008 4010 
     //Validate the port configuration.
     commit 
     //Exit the configuration view of port 100GE 1/0/1.
     quit 
     

9. Save the settings.

   //Enter the user view.
   quit
   //Save the settings.
   save STORAGE-SCALE-SW-1.cfg 
   //Modify the boot items for the next startup.
   startup saved-configuration STORAGE-SCALE-SW-1.cfg

Procedure

1. Roll back controller expansion in the original storage system in normal mode.
   1. Run the change user_mode current_mode user_mode=developer command to go to the developer view.
   2. Run the debug command to go to the engineer view.
   3. Run the sys showcls command to query the total number of controllers in the cluster, as shown in the following figure. node cfg indicates the total number of controllers in the cluster.

      admin:/diagnose>sys showcls 
      mode             : normal 
      status           : none 
      node cfg         : 2 
      node max         : 8 
      group cfg        : 1 
      group max        : 4 
      product          : 0 
      serial           : 2102350SHW10G3000001 
      WWN              : 0x2100e4a8b63bd03e 
      local node id    : 0 
      normalNodeBitmap : 3 
      faultNodeBitmap  : 0 
      offlineNodeBitmap: 0 
      standbyNodeBitmap: 0 
                id                    role                  status        
       --------------------   --------------------   -------------------- 
       0                      master                 normal               
       1                      slave                  normal               
               group                  engine            nodeSessionID
       --------------------   --------------------   -------------------- 
       0                      0                      1
       0                      0                      1

   4. Run the exit command to exit the diagnose view.
   5. Run the change user_mode current_mode user_mode=engineer command to go to the engineer view.
   6. Run the change controllers_expansion cancel controller_total=m command to roll back controller expansion.

      In the command, m indicates the total number of controllers in the original cluster.

   Do not restart the controllers to minimize the impact on cluster services.

2. Perform the operations described in Clearing the Controllers That Failed to Be Added.

Prerequisites

You have removed the cables of storage systems that have not been added to the cluster to isolate controllers.

Procedure

1. Log in to a controller that failed to be added via its serial port or management network port and check whether the following information is displayed in the CLI.

   Storage: minisystem>

   • If yes, the controller is in minisystem mode. Go to 2.
   • If no, the controller is not in minisystem mode. You must enter the minisystem mode before proceeding with 2. You can manually enter the minisystem mode as follows:
     • Run change user_mode current_mode user_mode=developer to enter the developer mode and then run minisystem to enter the minisystem mode.

       developer:/>minisystem 
       Storage: minisystem>

     • When the storage system is starting, System is not ready, Please wait(Ctrl+c to exit or Input minisystem to minisystem mode) is displayed on the CLI. Run minisystem to enter the minisystem mode.

       Authorized users only. All activities may be monitored and reported. 
       WARNING! The remote SSH server rejected X11 forwarding request. 
        
       WARNING: You have accessed the system. 
       You are required to have a personal authorisation from the system administrator before you use this computer. Unauthorised access to or misuse of this system is prohibited. 
        
       System is not ready, Please wait(Ctrl+c to exit or Input minisystem to minisystem mode).\minisystem     

   If you cannot log in to a controller (for example, controller A) using the serial port or management network port, log in to another controller in the controller enclosure (for example, controller B) and run the sshtoremoteExt SlotId command in minisystem mode to log in to controller A. SlotId is controller A's slot number and its value ranges from 0 to N–1, where N indicates the total number of controllers after controller expansion.

   2 U controller enclosures are used as an example. The slot IDs of controllers A and B in controller enclosure 0 are 0 and 1, those in controller enclosure 1 are 2 and 3, and so on.

   4 U controller enclosures are used as an example. The slot IDs of controllers A, B, C, and D in controller enclosure 0 are 0, 1, 2, and 3, those in controller enclosure 1 are 4, 5, 6, and 7, and so on.

2. Query the status of coffer disks.
   • If the configuration disk enclosure (DAE000) is a smart SAS or NVMe disk enclosure, run the sys.sh showallspecdiskinfo command to check whether the State value of coffer disks (Engine ID is 0 and Slot ranges from 0 to 3) is 0.
     • If yes, go to 4.
     • If no, go to 3.

   • If the configuration disk enclosure (DAE000) is a SAS disk enclosure, run bdm_diskbomlist.sh showdisk and check whether Valid of coffer disks (Slot ranges from 0 to 3 and ID is greater than 63) is Normal.
     • If yes, go to 4.
     • If no, go to 3.

3. Wait for 20 minutes. If the configuration disk enclosure is a smart SAS or NVMe disk enclosure, run the sys.sh showallspecdiskinfo command again to check whether coffer disks are connected. If the configuration disk enclosure is a SAS disk enclosure, run the bdm_diskbomlist.sh showdisk command again to check whether coffer disks are connected.
   • If yes, go to 4.
   • If no, go to 6.

4. Run showsysstatus. The value of local node id is the ID of the current controller. Check whether the controller's status is normal.
   • If yes, perform 1 to 4 on each controller that failed to be added separately. If all controllers' status are normal, expand controllers again using the expansion tool.

     If you still want to clear information about the new controller, go to 7.

   • If no, go to 5.

5. Run sys.sh clearnode -d -all in minisystem mode. The system will clear information automatically. This process typically takes about 6 minutes and will not exceed 30 minutes.

   Check whether Success is returned.

   • If yes, go to 9.
   • If no, go to 8.
   • This operation will restore all services and configurations of the controller to the initial state.
   • This operation will initialize user passwords. For the default password of the system administrator, see Security Configuration Guide of the corresponding product model.

6. Run sys.sh clearnode -df -all in minisystem mode. The system will clear information automatically. This process typically takes about 6 minutes and will not exceed 30 minutes.

   Check whether Success is returned.

   • If yes, go to 9.
   • If no, go to 8.
   • This operation will restore all services and configurations of the controller to the initial state.
   • This operation will initialize user passwords. For the default password of the system administrator, see Security Configuration Guide of the corresponding product model.

7. Run sys.sh clearnode -d in minisystem mode. The system will clear information automatically. This process typically takes about 6 minutes and will not exceed 30 minutes.

   After the system clears information automatically, check whether the "FAILED" message is not displayed.

   • If the message is not displayed, go to 9.
   • If the message is displayed, go to 8.
   • This operation can only clear the information on the controller that you have logged in to. Therefore, you must log in to all of the new controllers one by one and run this command.
   • This operation will restore all services and configurations of the controller to the initial state.
   • This operation will initialize user passwords. For the default password of the system administrator, see Security Configuration Guide of the corresponding product model.

8. Observe the indicators to determine whether the controller is running properly and the coffer disks are normal. For the indicator meanings, see the Product Description of the corresponding product model.
   • If the controller and coffer disks are normal, return to 1 and perform the operations again.
   • If the controller or coffer disks are abnormal, go to 11.

9. After all controllers have been cleared, log in to any of them and run sys.sh resetengine -n to reset all controllers in the current controller enclosure.
   • If the controller enclosure becomes normal after the controllers have been reset, go to 10.
   • If the controller enclosure fails to recover, go to 11.

10. Use the expansion tool to expand controllers again.
    • If the expansion is successful, no further action is required.
    • If expansion fails, go to 11.

11. Collect system logs and contact technical support engineers for assistance.

    To collect system logs:

    • Log in to DeviceManager. If you can access the console, choose Settings > Export Data. Select All logs under System Log and click Log List. The system starts collecting logs.
    Figure 3-93 Exporting system logs
    
    • If Failed to start the system is displayed when you log in to DeviceManager, click Download Log to download system logs.
    Figure 3-94 Downloading logs
    
    • If a controller fails to be powered on, log in to the controller and enter the minisystem mode. Then run os_backup_info.sh to collect logs and access the log path to obtain the logs.