S220, S310, S530, and S620 V600R024C00 Configuration Guide - Virtualization

Stack Login and Management

Stack Login and Management

A stack is logically managed as one device. Hardware resources (such as fans and power modules) are managed locally by each device, while services are controlled and processed by the master device.

Stack IP Address

After a stack is set up, the configuration file of the master device takes effect. The original IP addresses configured on the master device become the IP addresses of the stack, including the IP addresses of the management port and other Layer 3 interfaces.

Stack MAC Address

By default, the stack MAC address is the MAC address of the master device when the stack is set up for the first time. When the master device leaves the stack, the stack MAC address changes as follows by default:
  • If the master device joins the stack again within 10 minutes, the stack continues using the MAC address of this device.
  • If the master device does not join the stack again within 10 minutes, the stack MAC address is changed to the MAC address of the new master device.

Switching the stack MAC address will interrupt traffic. To prevent this, you can manually configure a fixed MAC address for the stack. For details, see Configuring the Stack MAC Address.

Login Modes

You can log in to a stack from any of its member devices to manage and maintain the entire stack. When you log in to a stack, you actually log in to the master device, regardless of what login method you use and which member device you connect to.

Two methods are available to log in to the stack:

  • Local management: Log in through the console port of any member device.

  • Remote management: Log in through the management port or another Layer 3 interface of any member device. STelnet and SNMP can be used for remote management as long as routes are reachable.

After a stack is set up, the management ports of all member devices use the same IP address: the IP address of the management port of the master device. When the management ports of multiple member devices are connected to the management network, only the management port of one member device takes effect. By default, the management port of the master device takes effect. If the management port of the master device is abnormal or unavailable, the management port of another member device takes effect.

Slot and Interface Numbering Rules

After a stack is set up, devices' slot IDs and interface numbers change, as listed in Table 2-2.

Table 2-2 Slot and interface numbering rules before and after a stack is set up

Item

Standalone Device

Stack

Slot ID

slot 1 by default

slot stack ID

Interface number

slot ID/subcard ID/port number

Example: 1/0/1

stack ID/subcard ID/port number

For example, if the stack ID is 2, the interface number changes to 2/0/1.

The stack management port is numbered MEth 0/0/0.

File System Management

When performing operations on the file system, note the difference between the storage names on a standalone device and a stack member device.
  • On a standalone device:

    flash: specifies the root directory of the storage on the local device.

  • On a stack member device:
    • flash: specifies the root directory of the storage on the stack master device.

    • stack ID#flash: specifies the root directory of the storage on the stack standby or slave device. For example, 2#flash indicates the root directory of the storage on the device whose stack ID is 2.

To copy files to all devices in a stack, run the copy source-filename destination-filename all command. To delete files from all devices, run the delete filename all command.

For details about the file system, see "File System Management Configuration" in CLI Configuration Guide > Basic Configuration.