H3C S3100-52P User manual

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Table of Contents
i
Table of Contents
Chapter 1 Stack .............................................................................................................................1-1
1.1 Stack Function Overview...................................................................................................1-1
1.1.1 The Main Switch of a Stack.....................................................................................1-1
1.1.2 The Slave Switches of a Stack................................................................................1-1
1.1.3 Creating a Stack......................................................................................................1-1
1.2 Main Switch Configuration.................................................................................................1-2
1.2.1 Configuring the IP Address Pool and Creating the Stack.......................................1-2
1.2.2 Switching to Slave Switch View ..............................................................................1-3
1.2.3 Stack-Port Function Configuration..........................................................................1-3
1.3 Slave Switch Configuration................................................................................................1-4
1.4 Displaying and Debugging a Stack....................................................................................1-4
1.5 Stack Configuration Example ............................................................................................1-5
Chapter 2 Cluster...........................................................................................................................2-1
2.1 Cluster Overview................................................................................................................2-1
2.1.1 Introduction to HGMP..............................................................................................2-1
2.1.2 Roles in a Cluster....................................................................................................2-2
2.1.3 How a Cluster Works ..............................................................................................2-4
2.2 Cluster Configuration Task List........................................................................................2-10
2.2.1 Configuring the Management Device....................................................................2-11
2.2.2 Configuring Member Devices................................................................................2-16
2.2.3 Managing a Cluster through the Management Device..........................................2-18
2.2.4 Configuring the Enhanced Cluster Features.........................................................2-19
2.3 Displaying and Maintaining Cluster Configuration...........................................................2-22
2.4 Cluster Configuration Examples......................................................................................2-22
2.4.1 Basic Cluster Configuration Example....................................................................2-22
2.4.2 Enhanced Cluster Feature Configuration Example...............................................2-26

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 1 Stack
1-1
Chapter 1 Stack
1.1 Stack Function Overview
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.
1.1.1 The Main Switch of a Stack
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:
zConfiguring an IP address pool for the stack
zCreating the stack
zSwitching 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 IPaddress 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.
1.1.2 The Slave Switches of a Stack
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.
1.1.3 Creating a Stack
The following are the phases undergone when a stack is created.
zConnect the intended main switch and slave switches through stack modules and
dedicated stack cables. (Refer to H3C S3100-52P Ethernet Switch Installation
Manual for the information about stack modules and stack cables.)
zConfigure 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.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 1 Stack
1-2
zWhen adding a switch joins in a stack, the main switchautomatically assigns an IP
address to it.
zThe main switch automatically adds any switches that are newly connected to the
stack through their stack ports to the stack.
1.2 Main Switch Configuration
The main switch configuration includes:
zConfiguring the IP Address Pool and Creating the Stack
zSwitching to Slave Switch View
1.2.1 Configuring the IP Address Pool and Creating the Stack
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
Note:
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:
zAfter a stack is created, the main switch automatically adds the switches
connected to its stack ports to the stack.
zIf a stack port connection is disconnected, the corresponding slave switch quits
the stack automatically.
zThe IP address pool of an existing stack cannot be modified.
zTo add a switch to a stack successfully, make sure the IP address pool contains at
least one unoccupied IP address.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 1 Stack
1-3
zMake 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.
zIP 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.
zIf 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.
zSince both stack and cluster use the management VLAN and only one VLAN
interface is available on the S3100-52P switch, stack and cluster must share the
same management VLAN if you want to configure stack within a cluster.
1.2.2 Switching to Slave Switch View
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.
1.2.3 Stack-Port Function Configuration
I. Introduction to the Stack-Port Function
If you enable the stack function on a stack-supporting device, the device will send

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 1 Stack
1-4
join-in requests to the connected stack ports of all the switches connected with the
device. This may cause switches not expecting to join in the stack to join in the stack
automatically, affecting network stability.
You can configure the stack-port function on the stack ports that are connected with
other switches to choose whether to send join-in requests to the switches, so as to
prevent the switches that do not belong to the local stack from joining in.
II. Stack-Port Function Configuration
Follow these steps to configure the stack port function:
To do… Use the command… Remarks
Enter system view system-view —
Enter port view interface interface-type
interface-number —
Enable the
stack-port function
on the stack port stack-port enable
Required
Enabled by default.
After a switch joins in a stack or
becomes the master switch of a
stack, the switch will
send/forward stack join-in
requests through this stack port.
1.3 Slave Switch Configuration
Just make sure the slave switch is connected to the main switch through the stack ports.
No configuration is needed.
1.4 Displaying and Debugging a Stack
Use the display command to display the information about a stack. The display
command can be executed in any view.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 1 Stack
1-5
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.
1.5 Stack Configuration Example
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 Switch B and C act as
slave switches.
Configure Switch B and Switch C through Switch A.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 1 Stack
1-6
II. Network diagram
Figure 1-1 Network diagram for stack configuration
III. Configuration procedure
# Configure the IP address pool for the stack on SwitchA.
<Sysname> system-view
[Sysname] stacking ip-pool 129.10.1.15 3
# Create the stack on switch A.
[Sysname] stacking enable
[stack_0.Sysname] quit
<stack_0.Sysname>
# Display the information about the stack on switch A.
<stack_0.Sysname> display stacking
Main device for stack.
Total members:3
Management-vlan:1(default vlan)
# Display the information about the stack members on switchA.
<stack_0.Sysname> display stacking members
Member number: 0
Name:stack_0.Sysname
Device: S3100-52P
MAC Address:000f-e20f-c43a
Member status:Admin
IP: 129.10.1.15 /16

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 1 Stack
1-7
Member number: 1
Name:stack_1.Sysname
Device: S3100-52P
MAC Address: 000f-e200-3130
Member status:Up
IP: 129.10.1.16/16
Member number: 2
Name:stack_2.Sysname
Device: S3100-52P
MAC Address: 000f-e200-3135
Member status:Up
IP: 129.10.1.17/16
# Switch to Switch B (a slave switch).
<stack_0.Sysname> stacking 1
<stack_1.Sysname>
# Display the information about the stack on switch B.
<stack_1.Sysname> display stacking
Slave device for stack.
Member number:1
Management-vlan:1(default vlan)
Main device mac address: 000f-e20f-c43a
# Switch back to Switch A.
<stack_1. H3C> quit
<stack_0.Sysname>
# Switch to Switch C (a slave switch).
<stack_0.Sysname> stacking 2
<stack_2.Sysname>
# Switch back to Switch A.
<stack_2.Sysname> quit
<stack_0.Sysname>

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-1
Chapter 2 Cluster
When configuring cluster, go to these sections for information you are interested in:
zCluster Overview
zCluster Configuration Task List
zDisplaying and Maintaining Cluster Configuration
zCluster Configuration Examples
2.1 Cluster Overview
2.1.1 Introduction to HGMP
Acluster contains a group of switches. Through cluster management, you can manage
multiple geographically dispersed in a centralized way.
Cluster management is implemented through Huawei Group Management Protocol
(HGMP). HGMP version 2 (HGMPv2) is used at present.
A switch in a cluster plays one of the following three roles:
zManagement device
zMember device
zCandidate device
A cluster comprises of a management device and multiple member devices. To
manage the devices in a cluster, you need only to configure an external IP address for
the management switch. Cluster management enables you to configure and manage
remote devices in batches, reducing the workload of the network configuration.
Normally, there is no need to configure external IP addresses for member devices.
Figure 2-1 illustrates a cluster implementation.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-2
Figure 2-1 A cluster implementation
HGMP V2 has the following advantages:
zIt eases the configuration and management of multiple switches: You just need to
configure a public IP address for the management device instead of for all the
devices in the cluster; and then you can configure and manage all the member
devices through the management device without the need to log onto them one by
one.
zIt provides the topology discovery and display function, which assists in monitoring
and maintaining the network.
zIt allows you to configure and upgrade multiple switches at the same time.
zIt enables you to manage your remotely devices conveniently regardless of
network topology and physical distance.
zIt saves IP address resource.
2.1.2 Roles in a Cluster
The switches in a cluster play different roles according to their functions and status. You
can specify the role a switch plays. A switch in a cluster can also switch to other roles
under specific conditions.
As mentioned above, the three cluster roles are management device, member device,
and candidate device.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-3
Table 2-1 Description on cluster roles
Role Configuration Function
Management
device
Configured
with a external
IP address
zProvides an interface for managing all the
switches in a cluster
zManages member devices through command
redirection, that is, it forwards the commands
intended for specific member devices.
zDiscovers neighbors, collects the information
about network topology, manages and
maintains the cluster. Management device also
supports FTP server and SNMP host proxy.
zProcesses the commands issued by users
through the public network
Member
device
Normally, a
member
device is not
assigned an
external IP
address
zMembers of a cluster
zDiscovers the information about its neighbors,
processes the commands forwarded by the
management device, and reports log. The
member devices of a luster are under the
management of the management device.
Candidate
device
Normally, a
candidate
device is not
assigned an
external IP
address
Candidate device refers to the devices that do not
belong to any clusters but are cluster-capable.
Figure 2-2 illustrates the state machine of cluster role.
Candidate Switch
Designates as a
management switch
Member switchManagement switch
Cancels the
designated
management
switch
Joins a
cluster
Leaves a
cluster
Figure 2-2 State machine of cluster role
zA candidate device becomes a management device when you create a cluster on
it. Note that a cluster must have one (and only one) management device. On
becoming a management device, the device collects network topology information
and tries to discover and determine candidate devices, which can then be added
to the cluster through configurations.
zA candidate device becomes a member device after being added to a cluster.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-4
zA member device becomes a candidate device after it is removed from the cluster.
zA management device becomes a candidate device only after the cluster is
removed.
Note:
After you create a cluster on an S3100-52P switch, the switch collects the network
topology information periodically and adds the candidate switches it finds to the cluster.
The interval for a management device to collect network topology information is
determined by the NTDP timer. If you do not want the candidate switches to be added
to a cluster automatically, you can set the topology collection interval to 0 by using the
ntdp timer command. In this case, the switch does not collect network topology
information periodically.
2.1.3 How a Cluster Works
HGMPv2 consists of the following three protocols:
zNeighbor Discovery Protocol (NDP)
zNeighbor Topology Discovery Protocol (NTDP)
zCluster
A cluster configures and manages the devices in it through the above three protocols.
Cluster management involves topology information collection and the
establishment/maintenance of a cluster. Topology information collection and cluster
establishment/maintenance are independent from each other. The former, as described
below, starts before a cluster is established.
zAll devices use NDP to collect the information about their neighbors, including
software version, host name, MAC address, and port name.
zThe management device uses NTDP to collect the information about the devices
within specific hops and the topology information about the devices. It also
determines the candidate devices according to the information collected.
zThe management device adds the candidate devices to the cluster or removes
member devices from the cluster according to the candidate device information
collected through NTDP.
I. Introduction to NDP
NDP is a protocol used to discover adjacent devices and provide information about
them. NDP operates on the data link layer, and therefore it supports different network
layer protocols.
NDP is able to discover directly connected neighbors and provide the following

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-5
neighbor information: device type, software/hardware version, and connecting port. In
addition, it may provide the following neighbor information: device ID, port full/half
duplex mode, product version, the Boot ROM version and so on.
zAn NDP-enabled device maintains an NDP neighbor table. Each entry in the NDP
table can automatically ages out. You can also clear the current NDP information
manually to have neighbor information collected again.
zAn NDP-enabled device regularly broadcasts NDP packet through all its active
ports. An NDP packet carries a holdtime field, which indicates how long the
receiving devices will keep the NDP packet data. The receiving devices store the
information carried in the NDP packet into the NDP table but do not forward the
NDP packet. When they receive another NDP packet, if the information carried in
the packet is different from the stored one, the corresponding entry in the NDP
table is updated, otherwise only the holdtime of the entry is updated.
II. Introduction to NTDP
NTDP is a protocol used to collect network topology information. NTDP provides
information required for cluster management: it collects topology information about the
switches within the specified hop count, so as to provide the information of which
devices can be added to a cluster.
Based on the neighbor information stored in the neighbor table maintained by NDP,
NTDP on the management device advertises NTDP topology collection requests to
collect the NDP information of each device in a specific network range as well as the
connection information of all its neighbors. The information collected will be used by the
management device or the network management software to implement required
functions.
When a member device detects a change on its neighbors through its NDP table, it
informs the management device through handshake packets, and the management
device triggers its NTDP to perform specific topology collection, so that its NTDP can
discover topology changes timely.
The management device collects the topology information periodically. You can also
launch an operation of topology information collection by executing related commands.
The process of topology information collection is as follows.
zThe management device sends NTDP topology collection requests periodically
through its NTDP-enabled ports.
zUpon receiving an NTDP topology collection request, the device returns a NTDP
topology collection response to the management device and forwards the request
to its neighbor devices through its NTDP-enable ports. The topology collection
response packet contains the information about the local device and the NDP
information about all the neighbor devices.
zThe neighbor devices perform the same operation until the NTDP topology
collection request is propagated to all the devices within the specified hops.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-6
When an NTDP topology collection request is propagated in the network, it is received
and forwarded by large numbers of network devices, which may cause network
congestion and the management device busy processing of the NTDP topology
collection responses. To avoid such cases, the following methods can be used to
control the NTDP topology collection request advertisement speed.
zConfiguring the devices not to forward the NTDP topology collection request
immediately after they receive an NTDP topology collection request. That is,
configure the devices to wait for a period before they forward the NTDP topology
collection request.
zConfiguring each NTDP-enabled port on a device to forward an NTDP topology
collection request after a specific period since the previous port on the device
forwards the NTDP topology collection request.
Note:
zTo implement NTDP, you need to enable NTDP both globally and on specific ports
on the management device, and configure NTDP parameters.
zOn member/candidate devices, you only need to enable NTDP globally and on
specific ports.
zMember and candidate devices adopt the NTDP settings of the management
device.
III. Introduction to Cluster
A cluster must have one and only one management device. Note the following when
creating a cluster:
zYou need to designate a management device for the cluster. The management
device of a cluster is the portal of the cluster. That is, any operations from outside
the network intended for the member devices of the cluster, such as accessing,
configuring, managing, and monitoring, can only be implemented through the
management device.
zThe management device of the cluster recognizes and controls all the member
devices in the cluster, no matter where they are located in the network and how
they are connected.
zThe management device collects topology information about all
member/candidate devices to provide useful information for you to establish the
cluster.
zBy collecting NDP/NTDP information, the management device learns network
topology, so as to manage and monitor network devices.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-7
zBefore performing any cluster-related configuration task, you need to enable the
cluster function first.
Note:
On the management device, you need to enable the cluster function and configure
cluster parameters. On the member/candidate devices, however, you only need to
enable the cluster function so that they can be managed by the management device.
IV. Cluster maintenance
1) Adding a candidate device to a cluster
To create a cluster, you need to determine the device to operate as the management
device first. The management device discovers and determines candidate devices
through NDP and NTDP, and adds them to the cluster. You can also add candidate
devices to a cluster manually.
After a candidate device is added to a cluster, the management device assigns a
member number and a private IP address (used for cluster management) to it.
2) Communications within a cluster
In a cluster, the management device maintains the connections to the member devices
through handshake packets. Figure 2-3 illustrates the state machine of the connection
between the management device and a member device.
Receives the
handshake or
management
packets
Fails to receive
handshake
packets in three
consecutive
intervals
State holdtime exceeds
the specified value
Disconnect state
is recovered
Active
Connect Disconnect
Figure 2-3 State machine of the connection between the management device and a
member device
zAfter a cluster is created and a candidate device is added to the cluster as a
member device, both the management device and the member device store the
state information of the member device and mark the member device as Active.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-8
zThe management device and the member devices exchange handshake packets
periodically. Note that the handshake packets exchanged keep the states of the
member devices to be Active and are not responded.
zIf the management device does not receive a handshake packet from a member
device after a period three times of the interval to send handshake packets, it
changes the state of the member device from Active to Connect. Likewise, if a
member device fails to receive a handshake packet from the management device
after a period three times of the interval to send handshake packets, the state of
the member device will also be changed from Active to Connect.
zIf the management device receives a handshake packet or management packet
from a member device that is in Connect state within the information holdtime, it
changes the state of the member device to Active; otherwise, it changes the state
of the member device (in Connect state) to Disconnect, in which case the
management device considers the member device disconnected. Likewise, if this
member device, which is in Connect state, receives a handshake packet or
management packet from the management device within the information holdtime,
it changes its state to Active; otherwise, it changes its state to Disconnect.
zIf the connection between the management device and a member device in
Disconnect state is recovered, the member device will be added to the cluster
again. After that, the state of the member device will turn to Active both locally and
on the management device.
Besides, handshake packets are also used by member devices to inform the
management device of topology changes.
Additionally, on the management device, you can configure the FTP server, TFTP
server, logging host and SNMP host to be shared by the whole cluster. When a member
device in the cluster communicates with an external server, the member device first
transmits data to the management device, which then forwards the data to the external
server. The management device is the default shared FTP/TFTP server for the cluster;
it serves as the shared FTP/TFTP server when no shared FTP/TFTP server is
configured for the cluster.
V. Management VLAN
Management VLAN limits the range of cluster management. Through management
VLAN configuration, the following functions can be implemented:
zEnabling the management packets (including NDP packets, NTDP packets, and
handshake packets) to be transmitted in the management VLAN only, through
which the management packets are isolated from other packets and network
security is improved.
zEnabling the management device and the member devices to communicate with
each other in the management VLAN.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-9
Cluster management requires the packets of the management VLAN be permitted on
ports connecting the management device and the member/candidate devices.
Therefore:
zIf the packets of management VLAN are not permitted on a candidate device port
connecting to the management device, the candidate device cannot be added to
the cluster. In this case, you can enable the packets of the management VLAN to
be permitted on the port through the management VLAN auto-negotiation
function.
zPackets of the management VLAN can be exchanged between the management
device and a member device/candidate device without carrying VLAN tags only
when the default VLAN ID of both the two ports connecting the management
device and the member/candidate device is the management VLAN. If the VLAN
IDs of the both sides are not that of the management VLAN, packets of the
management VLAN need to be tagged.
Note:
zThe management VLAN interface is used as the network management interface.
zThere is only one network management interface on a management device; any
newly configured network management interface will overwrite the old one.
VI. Tracing a device in a cluster through destination address
In practice, you may need to do the following:
zCheck whether there is a loop in a cluster.
zLocate which port on which device in a cluster generates the network attacks.
zDetermine the device and the port to which a MAC address corresponds.
zLocate the fault device in a cluster.
zCheck whether a link in a cluster and the devices on the link are consistent with the
original design.
To do the above things, you can use the tracemac command to trace a device in a
cluster by specifying the destination MAC address or IP address.
The following describes the process:
1) Choose to use the destination MAC address or the destination IP address to trace
a device in a cluster:
zIf you specify a destination MAC address in the tracemac command, the switch
will query its local MAC address table according to the MAC address and VLAN ID
specified in the command parameters to find out the port connected with a
downlink switch.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-10
zIf you specify a destination IP address in the tracemac command, the switch will
query its local ARP address table according to the IP address to find out the
corresponding MAC address and VLAN ID. In this way, the switch can find out the
port connected with a downlink switch.
2) After the switch finds out the port connected with a downlink switch, it sends a
multicast packet carrying the VLAN ID and hop limit to the port. After the downlink
switch receives the packet, it compares its MAC address with the specified
destination MAC address:
zIf the same, the downlink switch will send a response to the switch sending the
multicast packet, indicating that the tracemac command is executed successfully.
zIf different, the downlink switch will find the port connected with a downlink switch
according to the destination MAC address and VLAN ID, and forwards the
multicast packet to its downlink switch through the port. If a switch matching the
destination MAC address is found within the specified hops, the switch will send a
response to the switch sending the multicast packet, indicating that the tracemac
command is executed successfully. If no switch matches the destination MAC
address (or IP address) within the specified hops, the multicast packet will not be
forwarded to a downlink switch anymore.
Note:
zIf the queried IP address has a corresponding ARP entry, but the MAC address
entry corresponding to the IP address does not exist, the trace of the device fails.
zTo trace a specific device using the tracemac command, make sure that all the
devices passed support the tracemac function.
zTo trace a specific device in a management VLAN using the tracemac command,
make sure that all the devices passed are within the same management VLAN as
the device to be traced.
2.2 Cluster Configuration Task List
Before configuring a cluster, you need to determine the roles and functions the
switches play. You also need to configure the related functions, preparing for the
communication between devices within the cluster.
Complete the following tasks to configure cluster:
Task Remarks
Configuring the Management Device Required
Configuring Member Devices Required
Managing a Cluster through the Management Device Optional

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-11
Task Remarks
Configuring the Enhanced Cluster Features Optional
2.2.1 Configuring the Management Device
I. Management device configuration task list
Complete the following tasks to configure management device:
Task Remarks
Enabling NDP globally and on specific ports Required
Configuring NDP-related parameters Optional
Enabling NTDP globally and on a specific port Required
Configuring NTDP-related parameters Optional
Enabling the cluster function Required
Configuring cluster parameters Required
Configuring inside-outside interaction for a cluster Optional
Note:
To reduce the risk of being attacked by malicious users against opened socket and
enhance switch security, the S3100-52P Ethernet switch provide the following
functions, so that a cluster socket is opened only when it is needed:
zOpening UDP port 40000 (used for cluster) only when the cluster function is
implemented,
zClosing UDP port 40000 at the same time when the cluster function is closed.
On the management device, the preceding functions are implemented as follows:
zWhen you create a cluster by using the build or auto-build command, UDP port
40000 is opened at the same time.
zWhen you remove a cluster by using the undo build or undo cluster enable
command, UDP port 40000 is closed at the same time.

Operation Manual – Stack-Cluster
H3C S3100-52P Ethernet Switch Chapter 2 Cluste
r
2-12
II. Enabling NDP globally and on specific ports
Follow these steps to enable NDP globally and on specific ports:
To do… Use the command… Remarks
Enter system view system-view —
Enable NDP globally ndp enable Required
By default, NDP is
enabled globally.
In system view ndp enable
interface port-list
Enter
Ethernet
port view
interface
interface-type
interface-number
Enable
NDP on
specified
Ethernet
ports
In
Ethernet
port view Enable
NDP on the
port ndp enable
Use either
approach.
By default, NDP is
enabled on a port.
III. Configuring NDP-related parameters
Follow these steps to configure NDP-related parameters:
To do… Use the command… Remarks
Enter system view system-view —
Configure the holdtime of
NDP information ndp timer aging
aging-in-seconds
Optional
By default, the holdtime of
NDP information is 180
seconds.
Configure the interval to
send NDP packets ndp timer hello seconds
Optional
By default, the interval to
send NDP packets is 60
seconds.
IV. Enabling NTDP globally and on a specific port
Follow these steps to enable NTDP globally and on a specific port:
To do… Use the command… Remarks
Enter system view system-view —
Enable NTDP globally ntdp enable Required
Enabled by default
Enter Ethernet port view interface interface-type
interface-number —