H3C S3100 Series Operation Manual page 642

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 serves as the default shared FTP
server when no shared FTP server is configured for the cluster.
Management VLAN
Management VLAN limits the range of cluster management. Through management VLAN configuration,
the following functions can be implemented:
Enabling 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.
Enabling the management device and the member devices to communicate with each other in the
management VLAN.
Cluster management requires the packets of the management VLAN be permitted on ports connecting
the management device and the member/candidate devices. Therefore:
If 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.
Packets 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.
By default, the management VLAN interface is used as the network management interface.
There is only one network management interface on a management device; any newly configured
network management interface will overwrite the old one.
Tracing a device in a cluster
In practice, you need to implement the following in a cluster sometimes:
Know whether there is a loop in the cluster
Locate which port on which switch initiates a network attack
Determine the port and switch that a MAC address corresponds to
Locate which switch in the cluster has a fault
Check whether a link in the cluster and the devices on the link comply with the original plan
In these situations, you can use the tracemac command to trace a device in the cluster by specifying a
destination MAC address or IP address.
The procedures are as follows:
2-7