Chapter 1 Stack
Among S3100-SI
series switches, the S3100-26T-SI and S3100-26TP-SI switches support aggregation
of fixed Gigabit Ethernet ports.
Among S3100-SI
series switches, the S3100-26C-SI and S3100-16C-SI switches support aggregation
of the Gigabit Ethernet expansion modules, including Gigabit Ethernet optical
ports, Gigabit Ethernet electric ports and Gigabit Ethernet stack boards.
A stack is a management domain formed by a
group of Ethernet switches interconnected through their stack ports. A stack
contains a main switch and multiple slave switches.
Logically, you can consider a stack a
single device and manage all the switches in a stack through the main switch.
You can configure multiple Ethernet
switches interconnected through their stack ports to form a stack by performing
configurations on one of the switches. In this case, the switch becomes the main
switch of the stack.
You can perform the following operations on
a main switch:
l
Configuring an IP address pool for the stack
l
Creating the stack
l
Switching to slave switch view
Before creating a stack, you need to configure
an IP address pool for the stack on the main switch. When adding a switch to a
stack, the main switch picks an IP address from the IP address pool and assigns
the IP address to it automatically.
After a stack is created, the main switch
automatically adds the switches that connected to its stack ports to the stack.
If a stack port connection is disconnected, the corresponding slave switch quits
the stack automatically.
All the switches in a stack except the main
switch are slave switches.
You can configure a slave switch in a stack
on the main switch.
The following are the phases undergone when
a stack is created.
l
Connect the intended main switch and slave
switches through stack modules and dedicated stack cables. (Refer to H3C S3100-SI
Series Ethernet Switches Installation Manual for the information about
stack modules and stack cables.)
l
Configure the IP address pool for the stack and
enable the stack function. The main switch then automatically adds the switches
connected to its stack ports to the stack.
l
When adding a switch joins in a stack, the main
switch automatically assigns an IP address to it.
l
The main switch automatically adds any switches
that are newly connected to the stack through their stack ports to the stack.
The main switch configuration includes:
l
Configuring the IP Address
Pool and Creating the Stack
l
Switching to Slave Switch
View
Table 1-1 Configure the IP address pool and create the stack
|
Operation
|
Command
|
Description
|
|
Enter system view
|
system-view
|
—
|
|
Configure an IP address pool for a stack
|
stacking ip-pool from-ip-address ip-address-number [
ip-mask ]
|
Required
from-ip-address:
Start address of the IP address pool.
ip-address-number:
Number of the IP addresses in the IP addresses pool. A pool contains 16
addresses by default.
ip-mask:
Mask of the IP address pool.
By default, the IP addresses pool is not
configured.
|
|
Create a stack
|
stacking enable
|
Required
|
Remove the IP address configured for the existing Layer 3 interface
first if you want to cancel the stack-related configuration, otherwise, IP
address conflicts may occur.
As for the stack-related configurations
performed on a main switch, note that:
l
After a stack is created, the main switch
automatically adds the switches connected to its stack ports to the stack.
l
If a stack port connection is disconnected, the corresponding
slave switch quits the stack automatically.
l
The IP address pool of an existing stack cannot
be modified.
l
To add a switch to a stack successfully, make
sure the IP address pool contains at least one unoccupied IP address.
l
Make sure the IP addresses in the IP address
pool of a stack are successive so that they can be assigned successively. For
example, the IP addresses in an IP address pool with its start IP address
something like 223.255.255.254 are not successive. In this case, errors may occur
when adding a switch to the stack.
l
IP addresses in the IP address pool of a stack
must be of the same network segment. For example, the 1.1.255.254 is not a
qualified start address for a stack IP address pool.
l
If the IP address of the management VLAN
interface of the main switch (or a slave switch) is not of the same network
segment as that of the stack address pool, the main switch (or the slave
switch) automatically removes the existing IP address and picks a new one from
the stack address pool as its IP address.
l
Since both stack and cluster use the management
VLAN and only one VLAN interface is available on the S3100-SI switch, stack and
cluster must share the same management VLAN if you want to configure stack
within a cluster.
After creating a stack, you can switch to
slave switch view from the main switch to configure slave switches.
Table 1-2 Switch to slave switch view
|
Operation
|
Command
|
Description
|
|
Switch to slave switch view
|
stacking number
|
Required
Number:
Number of the slave switch to switch to.
This command can be used to switch from
user view of the main switch to user view of a slave switch. The user level
remains the same while switching.
|
You can quit slave switch view after slave
switch configuration.
Table 1-3 Quit slave switch view
|
Operation
|
Command
|
Description
|
|
Quit slave switch view
|
quit
|
You can quit slave switch view only by
executing this command in user view of a slave switch.
|
Just make sure the slave switch is
connected to the main switch through the stack ports. No configuration is
needed.
Use the display command to display
the information about a stack. The display command can be executed in
any view.
Table 1-4 Display and maintain stack configurations
|
Operation
|
Command
|
Description
|
|
Display the stack status information on
the main switch
|
display stacking [ members ]
|
Optional
The display command can be
executed in any view.
When being executed with the members
keyword not specified, this command displays the main switch and the number
of switches in the stack.
When being executed with the members
keyword specified, this command displays the member information of the stack,
including stack number , device name, MAC addresses and status of the main
switch/slave switches.
|
|
Display the stack status information on a
slave switch
|
display stacking
|
Optional
The display command can be
executed in any view.
The displayed information indicates that
the local switch is a slave switch. The information such as stack number of
the local switch, and the MAC address of the main switch in the stack is also
displayed.
|
I. Network requirements
Connect Switch A, Switch B and Switch C
with each other through their stack ports to form a stack, in which Switch A acts
as the main switch, while Switches B and C act as slave switches.
Configure Switches B and Switch C through Switch
A.
Figure 1-1 Network diagram for stack configuration
# Configure the IP address pool for the
stack on Switch A.
<H3C> system-view
[H3C] stacking ip-pool 129.10.1.15 3
# Create the stack on switch A.
[H3C] stacking enable
[stack_0.H3C] quit
<stack_0.H3C>
# Display the information about the stack
on switch A.
<stack_0.H3C> display stacking
Main device for stack.
Total members:3
Management-vlan:1(default vlan)
# Display the information about the stack
members on switch A.
<stack_0. H3C> display stacking
members
Member number: 0
Name:stack_0.H3C
Device: S3600-52M-HI
MAC Address:000f-e20f-c43a
Member status:Admin
IP: 129.10.1.15
/16
Member number: 1
Name:stack_1.H3C
Device: S3100-SI
MAC Address: 000f-e20f-3130
Member status:Up
IP: 129.10.1.16/16
Member number: 2
Name:stack_2.H3C
Device: S3100-SI
MAC Address: 000f-e20f-3135
Member status:Up
IP: 129.10.1.17/16
# Switch to Switch B (a slave switch).
<stack_0.H3C> stacking 1
<stack_1.H3C>
# Display the information about the stack on
switch B.
<stack_1.H3C> display stacking
Slave device for stack.
Member number: 1
Main switch mac address: 000f-e20f-3130
# Switch back to Switch A.
<stack_1. H3C> quit
<stack_0.H3C>
# Switch to Switch C (a slave switch).
<stack_0.H3C> stacking 2
<stack_2.H3C>
# Switch back to Switch A.
<stack_2.H3C> quit
<stack_0.H3C>
A cluster is implemented through HGMP V2.
By employing HGMP V2, a network administrator can manage multiple switches using
the public IP address of a switch known as a management device. The switches under
the management of the management device are member devices. The management
device, along with the member devices, forms a cluster. Normally, a cluster
member device is not assigned a public IP address. Management and maintenance operations
intended for the member devices in a cluster are redirected by the management
device. Figure 2-1 illustrates a typical cluster implementation.
Figure 2-1 Diagram
for cluster
HGMP V2 offers the following advantages:
l
The procedures to configure multiple switches
remarkably simplified. When the management device is assigned a public IP
address, you can configure/manage a specific member device on the management
device instead of logging into it in advance.
l
Functions of topology discovery and display provided,
which assist network monitoring and debugging
l
Software upgrading and parameter configuring can
be performed simultaneously on multiple switches.
l
Free of topology and distance limitations
l
Saving IP address resource
HGMP V2 provides the following functions:
l
Topology discovery: HGMP V2 implements NDP (neighbor
discovery protocol) to discover the information about the directly connected
neighbor devices, including device type, software/hardware version, connecting
port and so on. The information such as device ID, port mode (duplex or half duplex),
product version, and BootROM version can also be given.
l
Topology information collection: HGMP V2
implements NTDP (neighbor topology discovery protocol) to collect the information
about device connections and candidate devices within a specified hop range.
l
Member recognition: A management device can
locate and recognize the member devices in the cluster and then deliver
configuration and management commands to them.
l
Member management: You can add a device to a
cluster or remove a device from a cluster on the management device. You can
also configure management device authentication and handshake interval for a
member device on the management device.
Cluster-related configurations are
described in the following sections.
According to their functions and status in
a cluster, switches in the cluster play different roles. You can specify the
role a switch plays. A switch also changes its role according to specific
rules.
Following three cluster roles exist: management
device, member device, and candidate device.
Table 2-1 Cluster role
|
Role
|
Configurations
|
Functions
|
|
Management device
|
l Configured with a public IP address.
l Receiving management commands from the public network and
processing the received commands
|
l Providing management interfaces for all switches in the cluster
l Managing member devices by redirecting commands
l Forwarding commands to the intended member devices
l Neighbor discovery, topology information collection, cluster
management, cluster state maintenance, and proxies
|
|
Member device
|
Normally, a member device is not
configured with a public IP address.
|
l Cluster member
l Neighbor discovery, being managed by the management device,
running commands forwarded by proxies, and failure/log reporting.
|
|
Candidate device
|
Normally, a candidate device is not configured
with a public IP address.
|
A candidate device is a switch that does not
belong to any cluster, although it can be added to a cluster.
|
Figure 2-2 shows the role changing rule.
Figure 2-2 Role changing rule
l
Each cluster has one (and only one) management
device. A management device collects NDP/NTDP information to discover and determine
candidate devices, which can be then added into the cluster through manual
configurations.
l
A candidate device becomes a member device after
being added to a cluster.
l
A member device becomes a candidate device after
being removed from the cluster.
NDP is the protocol for discovering the
information about the adjacent nodes. NDP operates on the data link layer, so it
supports different network layer protocols.
NDP is used to discover the information about
directly connected neighbors, including the device type, software/hardware
version, and connecting port of the adjacent devices. It can also provide the
information concerning device ID, port address, hardware platform and so on.
A device with NDP enabled maintains an NDP
information table. Each entry in an NDP table ages with time. You can also
clear the current NDP information manually to have adjacent information collected
again.
A device with NDP enabled broadcasts NDP packets
regularly through all its ports that are in up state. An NDP packet carries the
holdtime, which indicates the period for the receiving devices to keep the information
the packet carries. Receiving devices only store the information carried in the
received NDP packets rather than forward them. The corresponding data entry in
the NDP table is updated when the information carried in a received NDP packet
if the received information differs from the existing one, otherwise, only the holdtime
of the corresponding entry is updated.
NTDP is a protocol for network topology
information collection. NTDP provides the information about the devices that
can be added to clusters and collects the topology information within the
specified hops for cluster management.
Based on the NDP information table created
by NDP, NTDP transmits and forwards NTDP topology collection request to collect
the NDP information and neighboring connection information of each device in a specific
network range for the management device or the network administrator to implement
needed functions.
Upon detecting a change occurred on a
neighbor, a member device informs the management device of the change through handshake
packets. The management device then collects the specified topology information
through NTDP. Such a mechanism enables topology changes to be tracked in time.
As for NTDP
implementing, you need to perform configurations on the management device, the
member devices, and the candidate devices as follows:
l
On the management device, enable NTDP both
globally and for specific ports, and configure the NTDP settings.
l
On each member device and candidate device, enable
NTDP both globally and for specific ports. As member devices and candidate
devices adopt the NTDP settings configured for the management device, NTDP
setting configurations are not needed.
2.1.5 Introduction to Cluster
A cluster has one (and only one) management
device. Note the following when creating a cluster:
l
You need to designate the management device
first. The management device of a cluster is the portal of the cluster. That
is, any operations performed in external networks and intended for the member
devices of a cluster, such as accessing, configuring, managing, and monitoring,
can only be implemented through the management device.
l
The management device of a cluster recognizes
and controls all the member devices in the cluster, no matter where they are
located on the network or how they are connected.
l
The management device collects topology
information about all the member and candidate devices to provide useful
information for users to establish a cluster.
l
A management device manages and monitors the
devices in the cluster by collecting and processing NDP/NTDP packets. NDP/NTDP
packets contain network topology information.
All the above-mentioned operations need the
support of the cluster function.
You need to enable the cluster function and configure cluster
parameters on a management device. However, you only need to enable the cluster
function on the member devices and candidate devices.
Additionally, you can configure public FTP server, TFTP server,
logging host and SNMP host for the whole cluster. When the members in the cluster
communicate with external servers, the data is transmitted to the management
device first and then transmitted to external servers through the management
device. When the public FTP/TFTP server is not configured for the cluster, the
management device is the default FTP/TFTP server of the cluster.
Management device configuration involves:
l
Enabling NDP globally and for specific ports
l
Configuring NDP-related parameters
l
Enable NTDP globally and for a specific port
l
Configuring NTDP-related parameters
l
Enable the cluster function
l
Configuring cluster parameters
l
Configuring Interaction for the Cluster
Table 2-2 Enable NDP globally and for a specific
port
|
Operation
|
Command
|
Description
|
|
Enter system view
|
system-view
|
—
|
|
Enable NDP globally
|
ndp enable
|
Required
|
|
Enable NDP for specified ports
|
ndp enable interface port-list
|
Optional
|
|
Enter Ethernet port view
|
interface interface-type interface-number
|
—
|
|
Enable NDP for the Ethernet port
|
ndp enable
|
Required
|
Table 2-3 Configure NDP-related parameters
|
Operation
|
Command
|
Description
|
|
Enter system view
|
system-view
|
—
|
|
Configure the holdtime of NDP information
|
ndp timer aging aging-in-seconds
|
The aging-in-seconds argument is
the holdtime of NDP information.
|
|
Configure the interval to send NDP
packets
|
ndp timer hello seconds
|
The seconds argument is the
interval to send NDP packets.
|
Table 2-4 Enable NTDP globally and for specific
ports
|
Operation
|
Command
|
Description
|
|
Enter system view
|
system-view
|
—
|
|
Enable NTDP globally
|
ntdp enable
|
Required
|
|
Enter Ethernet port view
|
interface interface-type interface-number
|
—
|
|
Enable NTDP for the Ethernet port
|
ntdp enable
|
Required
|
Table 2-5 Configure NTDP parameters
|
Operation
|
Command
|
Description
|
|
Enter system view
|
system-view
|
—
|
|
Configure the range topology information
within which is to be collected
|
ntdp hop hop-value
|
Optional
The hop-value argument is the
range measured in hop count.
|
|
Configure the hop delay to forward
topology-collection request packets
|
ntdp timer hop-delay time
|
Optional
The time argument is the delay
time.
|
|
Configure the port delay to forward
topology collection request packets
|
ntdp timer port-delay time
|
Optional
The time argument is the delay
time.
|
|
Configure the interval to collect topology
information
|
ntdp timer interval-in-minutes
|
Optional
The interval-in-minutes argument is
the desired interval.
|
|
Quit system view.
|
quit
|
—
|
|
Start topology information collection
|
ntdp explore
|
Optional
|
By default, an S3100-SI
series switch operating as a candidate switch joins a cluster automatically.
You can disable the switch from operating in this way by setting the ntdp timer
to 0.
Table 2-6 Enable the cluster function
|
Operation
|
Command
|
Description
|
|
Enter system view
|
system-view
|
—
|
|
Enable the cluster function globally
|
cluster enable
|
Required
|
I. Configuring cluster parameters
manually
Table 2-7 Configure cluster parameters manually
|
Operation
|
Command
|
Description
|
|
Enter system view
|
system-view
|
—
|
|
Specify the management VLAN
|
management-vlan vlan-id
|
This is to specify the management VLAN on
the switch
|
|
Enter cluster view
|
cluster
|
—
|
|
Configure an IP address pool for the cluster
|
ip-pool administrator-ip-address
{ ip-mask | ip-mask-length }
|
Required
|
|
Configure a cluster with the current
switch as the management device
|
build name
|
Optional
The name argument is the name to
be assigned to the cluster.
|
|
Configure a multicast MAC address for the
cluster
|
cluster-mac H-H-H
|
Optional
This is to set a multicast MAC address
for the cluster.
|
|
Set the interval for the management
device to send multicast packets
|
cluster-mac syn-interval time-interval
|
Optional
The time-interval argument is the
interval to send multicast packets.
|
|
Configure the holdtime for a switch
|
holdtime seconds
|
Optional
The seconds argument is the holdtime,
which is 60 seconds by default.
|
|
Set the interval to send handshake
packets
|
timer interval
|
Optional
The interval argument is the
interval to send handshake packets, which is 10 seconds by default.
|
|
Quit cluster view
|
quit
|
—
|
II. Building a cluster automatically
Table 2-8 Enable the cluster function
automatically
|
Operation
|
Command
|
Description
|
|
Enter
system view
|
system-view
|
—
|
|
Enter
cluster view
|
cluster
|
—
|
|
Configure
the rang e of the IP addresses of the cluster
|
ip-pool administrator-ip-address { ip-mask | ip-mask-length }
|
Required
|
|
Build a
cluster automatically
|
auto-build
[ recover ]
|
Optional
You can
build clusters according to corresponding prompts
|
Table 2-9 Configure interaction for the
cluster
|
Operation
|
Command
|
Description
|
|
Enter system view
|
system-view
|
—
|
|
Enter cluster view
|
cluster
|
Required
|
|
Configure the public FTP server for the
cluster
|
ftp-server
ip-address
|
Optional
|
|
Configure the TFTP server for the cluster
|
tftp-server ip-address
|
Optional
|
|
Configure the logging host for the
cluster
|
logging-host ip-address
|
Optional
|
|
Configure the SNMP host for the cluster
|
snmp-host ip-address
|
Optional
|
Member device configuration involves:
l
Enabling NDP globally and for specific ports
l
Enabling NTDP globally and for specific ports
l
Enabling the cluster function
l
Configure member devices to access FTP/TFTP
server of the cluster
Table 2-10
Enable NDP globally and
for specific ports
