15-Stack Management Configuration
Chapters Download (130.68 KB)
Table of Contents
Configuring the Master Device of a Stack
Configuring a Private IP Address Pool for a Stack
Configuring Stack Ports of a Slave Device
Logging In to the CLI of a Slave from the Master
Displaying and Maintaining Stack Configuration
When configuring stack, go to these sections for information you are interested in:
l Stack Configuration Overview
l Stack Configuration Task List
l Configuring the Master Device of a Stack
l Configuring Stack Ports of a Slave Device
l Logging In to the CLI of a Slave from the Master
l Displaying and Maintaining Stack Configuration
A stack is a set of network devices. Administrators can group multiple network devices into a stack and manage them as a whole. Therefore, stack management can help reduce customer investments and simplify network management.
A stack is a management domain that comprises several network devices connected to one another through stack ports. In a stack, there is a master device and several slave devices.
An administrator can manage all the devices in a stack through the master device. Figure 1-1 shows a network diagram for stack management.
Figure 1-1 Network diagram for stack management
l Master device: In a stack, the master device acts as the configuration interface in stack management. Management and monitoring of all the devices in the stack are performed through the master device.
l Slave devices: Managed devices in a stack.
l Stack port: Ports between stack devices.
For the S5810 series switches, only the 10 GE ports can be configured as the stack ports and the switches can be connected to establish stacks only through some dedicated stack cables, which include:
l LSWM1STK
l LSWM2STK
l LSWM3STK
If you plug some other SFP+ modules to the 10 GE port after you configure the port as a stack port, the state of the port will become down automatically.
An administrator can establish a stack as follows:
l Configure a private IP address pool for a stack and create the stack on the network device which is desired to be the master device.
l Configure ports between the stack devices as stack ports.
l The master device automatically adds the slave devices into the stack, and assigns a number for each stack member.
l The administrator can log in to any slave device from the master device of the stack, and perform configurations for the slave device.
You cannot configure both stack management and cluster management functions for the device. For details of the cluster management function, refer to Cluster Management Configuration in the System Volume.
Complete the following tasks to configure stack:
|
Task |
Remarks |
|
|
Required |
||
|
Required |
||
|
Required |
||
|
Required |
||
|
Optional |
||
Follow these steps to configure a private IP address pool for a stack:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Configure a private IP address pool for the stack |
stack ip-pool ip-address { mask | mask-length } |
Required Not configured by default. |
l If a device is already configured as the master device of a stack or is already a slave device of a stack, you cannot configure a private IP address pool on the device.
l When you configure a private IP address pool for a stack, the number of IP addresses in the address pool needs to be equal to or greater than the number of devices to be added to the stack. Otherwise, some devices may not be able to join the stack automatically for lack of private IP addresses.
On the master device, configure ports that connect to slave devices as stack ports.
Follow these steps to configure stack ports:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Configure the specified ports as stack ports |
stack stack-port stack-port-num port interface-list |
Required By default, a port is not a stack port. |
After you execute the stack role master command on a stack-capable device, the device becomes the master device of a stack and automatically adds the devices connected with its stack ports to the stack.
Follow these steps to create a stack:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Create a stack |
stack role master |
Required |
After you configure a device as the master device of a stack, the prompt changes to <stack_0.Sysname>, where Sysname is the system name of the device.
You need to configure stack ports to add a slave device to the stack.
The ports of a slave device that connect to other stack devices need to be configured as stack ports.
Follow these steps to configure stack ports:
|
To do… |
Use the command… |
Remarks |
|
Enter system view |
system-view |
— |
|
Configure the specified ports as stack ports |
stack stack-port stack-port-num port interface-list |
Required By default, a port is not a stack port. |
After a device joins a stack and becomes a slave device of the stack, the prompt changes to <stack_n.Sysname>, where n is the stack number assigned by the master device, and Sysname is the system name of the device.
In a stack, you can log in to the CLI of a slave device from the master device and perform configurations for the slave device.
Follow the step below to log in to the CLI of a slave device from the master device:
|
Use the command… |
Remarks |
|
|
Log in to the CLI of the specified slave device from the master device |
stack switch-to member-id |
Required Available in user view |
The stack switch-to command is used to log in to the CLI of a slave device from the master with the user level being unchanged. To return to the master device, use the quit command.
|
To do… |
Use the command… |
Remarks |
|
Display the stack information of stack members |
display stack [ members ] |
Available in any view |
You can view the stack status through not only the command lines, but also the seven-segment display on the front panel of the device to judge the role of the device in the stack, as described in the following table:
Table 1-1 Seven-segment display description
|
Mark |
Status |
Description |
|
|
System LED (SYS) status |
Seven-segment LED status |
||
|
Unit |
Steady green |
The LED displays the specific numbers.
|
The member ID of the device. |
l As shown in Figure 1-2, Switch A, Switch B, Switch C, and Switch D are connected with one another.
l Create a stack, where Switch A is the master device, Switch B, Switch C, and Switch D are slave devices. An administrator can log in to Switch B, Switch C and Switch D through Switch A to perform remote configurations.
Figure 1-2 Network diagram for stack management
1) Configure the master device
# Configure a private IP address pool for the stack on Switch A.
<SwitchA> system-view
[SwitchA] stack ip-pool 192.168.1.1 24
# Configure port Ten-GigabitEthernet1/0/51 as a stack port on Switch A.
[SwitchA] stack stack-port 1 port ten-gigabitethernet 1/0/51
# Configure switch A as the master device.
[SwitchA] stack role master
2) Configure the slave devices
# On Switch B, configure local ports Ten-GigabitEthernet 1/0/52 and Ten-GigabitEthernet 1/0/51 as stack ports.
<SwitchB> system-view
[SwitchB] stack stack-port 2 port ten-gigabitethernet 1/0/51 ten-gigabitethernet 1/0/52
# On Switch C, configure local port Ten-GigabitEthernet 1/0/51 and Ten-GigabitEthernet 1/0/52 as a stack port.
<SwitchC> system-view
[SwitchC] stack stack-port 2 port ten-gigabitethernet 1/0/51 ten-gigabitethernet 1/0/52
# On Switch D, configure local port Ten-GigabitEthernet 1/0/51 as a stack port.
<SwitchD> system-view
[SwitchD] stack stack-port 1 port ten-gigabitethernet 1/0/51
3) Verify the configuration
# Display stack information of the stack members on Switch A.
<stack_0.SwitchA> display stack members
Number : 0
Role : Master
Sysname : stack_0. SwitchA
Switch type: S5810-50S
MAC address: 000f-e200-1000
Number : 1
Role : Slave
Sysname : stack_1. SwitchB
Device type: S5810-50S
MAC address: 000f-e200-1001
Number : 2
Role : Slave
Sysname : stack_2. DeviceC
Device type: S5810-50S
MAC address: 000f-e200-1002
Number : 3
Role : Slave
Sysname : stack_3. DeviceD
Device type: S5810-50S
MAC address: 000f-e200-1003
