Login
| Title | Size | Downloads |
|---|---|---|
| 16-Stack Management Configuration.pdf | 125 KB |
- Table of Contents
- Related Documents
-
| Title | Size | Download |
|---|---|---|
| 16-Stack Management Configuration | 125 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
Stack Configuration Overview
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.
Introduction to Stack
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.
Establishing a Stack
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.
Stack Configuration Task List
Complete the following tasks to configure stack:
|
Task |
Remarks |
|
|
Required |
||
|
Required |
||
|
Required |
||
|
Required |
||
|
Optional |
||
Configuring the Master Device of a Stack
Configuring 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 By default, no IP address pool is configured for a stack. |
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.
Configuring Stack Ports
On the master device, configure ports that connect to slave devices as stack ports.
Follow the steps below 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. |
l You can configure only 1000 Mbps SFP ports working in bridge mode as stack ports for the S3610 series switches. For how to change the working mode of an interface, refer to Ethernet Port Configuration in the Access Volume.
l A 1000 Mbps SFP port configured as a stack port must use a dedicated SFP stack module to form a stack; if you plug in an SFP module of other types, the switch will shut down the SFP port. For the introduction to SFP stack modules, refer to H3C Low End Series Ethernet Switches Pluggable Modules Manual.
Creating a Stack
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 the steps below 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.
Configuring Stack Ports of a Slave 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 the steps below 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. |
l You can configure only 1000 Mbps SFP ports working in bridge mode as stack ports for the S3610 series switches. For how to change the working mode of an interface, refer to Ethernet Port Configuration in the Access Volume.
l A 1000 Mbps SFP port configured as a stack port must use a dedicated SFP stack module to form a stack; if you plug in an SFP module of other types, the switch will shut down the SFP port. For the introduction to SFP stack modules, refer to H3C Low End Series Ethernet Switches Pluggable Modules Manual.
l 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.
Logging In to the CLI of a Slave from the Master
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.
Displaying and Maintaining Stack Configuration
|
To do… |
Use the command… |
Remarks |
|
Display the stack information of stack members |
display stack [ members ] |
Available in any view |
Stack Configuration Example
Stack Configuration Example
Network requirements
l 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.
Network diagram
Figure 1-2 Network diagram for stack management
Configuration procedure
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 GigabitEthernet 1/1/1 as a stack port on Switch A.
[SwitchA] stack stack-port 1 port gigabitethernet 1/1/1
# Configure switch A as the master device.
[SwitchA] stack role master
2) Configure the slave devices
# On Switch B, configure local ports GigabitEthernet 1/1/2, GigabitEthernet 1/1/1, and GigabitEthernet 1/1/3 as stack ports.
<SwitchB> system-view
[SwitchB] stack stack-port 3 port gigabitethernet 1/1/1 gigabitethernet 1/1/2 gigabitethernet 1/1/3
# On Switch C, configure local port GigabitEthernet 1/1/1 as a stack port.
<SwitchC> system-view
[SwitchC] stack stack-port 1 port gigabitethernet 1/1/1
# On Switch D, configure local port GigabitEthernet 1/1/1 as a stack port.
<SwitchD> system-view
[SwitchD] stack stack-port 1 port gigabitethernet 1/1/1
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: S3610-28P
MAC address: 000f-e200-1000
Number : 1
Role : Slave
Sysname : stack_1. SwitchB
Device type: S3610-28P
MAC address: 000f-e200-1001
Number : 2
Role : Slave
Sysname : stack_2. SwitchC
Device type: S3610-52P
MAC address: 000f-e200-1002
Number : 3
Role : Slave
Sysname : stack_3. SwitchD
Device type: S3610-28P
MAC address: 000f-e200-1003
