Smart Management Center (SmartMC) centrally manages and maintains dispersed network devices at network edges. In a SmartMC network, only one device acts as the commander and the remaining devices all act as members. SmartMC provides the following features for you to manage the members from the commander:

· Configuration file backup and download.

· Software upgrade.

· Configuration deployment.

· Faulty member replacement.

SmartMC network framework

Figure 1 shows the basic framework of a SmartMC network.

The SmartMC network contains the following elements:

· Commander—Also called topology master (TM), which manages all members in the SmartMC network.

· Member—Also called topology client (TC), which is managed by the commander.

· FTP server—Stores startup software images and configuration files for the commander and members.

Figure 1 SmartMC network framework

‌

Self-mesh SmartMC and non-self-mesh SmartMC

SmartMC supports two operating modes: self-mesh and non-self-mesh, depending on the role selection method.

· Non-mesh mode: Allows users to manually configure TM or TC roles. In a non-self-mesh SmartMC network, the administrator must log into each member device individually and manually specify the device role in the SmartMC network as either a TM or a TC through command lines. After the other necessary settings are configured, devices connect to each other. Each device joins the SmartMC network according to the assigned role, with the TM managing the TCs. In a non-self-mesh SmartMC network, it is the administrator's responsibility to ensure that only one TM exists within the SmartMC network.

· Self-mesh mode: Automatically elects TM or TC roles in the network. Non-self-mesh SmartMC is also known as SmartMC 1.0, and self-mesh SmartMC is referred to as SmartMC 2.0.

¡ Switches require role configuration through command lines. Switches of this series come with the necessary configuration for self-mesh SmartMC, allowing for plug-and-play functionality. This means that once the switch is powered on and connected to the network, it can automatically form a SmartMC network with other devices based on its factory configuration.

¡ For devices that support self-mesh SmartMC, such as AC, AP, router, or gateway, auto TM election is supported:

- If a TM already exists in the current SmartMC network, the other devices automatically act as TCs.

- If no TM exists in the current SmartMC network, the devices perform auto TM election to elect a TM and the other devices act as TCs.

Table 1 Differences between self-mesh SmartMC and non-self-mesh SmartMC

Item	Non-self-mesh SmartMC	Self-mesh SmartMC
Setup	Require manual role (TM or TC) configuration	The network administrator must log in to the Web interface of the TM to configure setup deployment for a SmartMC network to be automatically established. ACs, APs, routers, firewall devices, and specific switches can use factory default settings to automatically establish a SmartMC network to achieve plug-and-play. Switches of this series come with SmartMC enabled and are specified with the TC role in the factory configuration (smartmc tc enable). To change the device role to TM, execute the smartmc enable auto tm command.
Role election	Not supported. All devices must be manually specified with a role (TM or TC).	Switches require manual role configuration (TM or TC). ACs, APs, routers, and firewall devices support auto TM election and also support manual role specification.
Management method	Use the CLI, the SmartMC network management platform, or both (the SmartMC network management platform is a primary feature of the device local web interface).	Use the UWEB platform, a lightweight Web management platform parallel to the device local web interface.
Applicable network scenarios	Wired access.	· Wired access. · Unified wired and wireless access.
Supported commands	All SmartMC commands except the smartmc password command.	Only the smartmc enable, smartmc password, and smartmc ftp-server commands.

Configuring non-self-mesh SmartMC (SmartMC 1.0)

NOTE:

For simplicity purposes, the term "SmartMC" in this chapter refers to non-mesh SmartMC. For more information about self-mesh SmartMC, see "Configuring self-mesh SmartMC."

About non-mesh SmartMC

Non-mesh SmartMC is a technology where network administrators manually configure devices as TM or TC in the SmartMC network using command lines and complete other relevant configurations before interconnecting them. The devices will join the SmartMC network according to the specified roles and complete the network formation. The TM manages TCs. It is the administrator's responsibility in a non-mesh SmartMC network to ensure that only one TM is present.

SmartMC network establishment

A SmartMC network can be established automatically. During automatic establishment, the commander obtains member information through NETCONF sessions to form the network topology. The member information includes port information, LLDP neighbor information, STP information, device type, and software version.

The commander and members use the following procedure to establish a SmartMC network:

1. After SmartMC is enabled, the commander broadcasts a SmartMC packet at an interval of 15 seconds to detect members in the network. The SmartMC packet contains information of the commander, such as its bridge MAC address and the IP address of VLAN-interface 1.

2. When a member receives the packet, it records the commander information, and returns a response packet to the commander. The response packet contains information of the member, such as its bridge MAC address and the IP address of VLAN-interface 1.

3. When the commander receives the response packet, it initiates a NETCONF session to the member with the default username admin and the default password admin and sets up TCP keepalive. The commander then obtains detailed information about the member through the session, including port information, LLDP neighbor information, STP information, device type, and software version.

4. The commander notifies the member of online success, and adds the member to the SmartMC network.

5. Based on the LLDP neighbor information obtained from all members, the commander forms a SmartMC topology.

After the successful establishment of the SmartMC network, the commander becomes aware of members through NETCONF session status, while members become aware of each other through SmartMC broadcast messages sent by the commander:

· When a member receives a SmartMC broadcast packet from the commander, it compares the bridge MAC address in the packet with the recorded bridge MAC address. If the two bridge MAC addresses are the same and the device with the MAC address is offline, the member returns a response packet to the commander. If the member does not receive a broadcast packet from the commander within the time limit, the member determines that the commander does not exist in the network anymore. Then, the member clears the commander information. The time limit is a random value in the range of 60 to 120 seconds.

· When the commander receives a response message from a member, it establishes a NETCONF session with the member and sets up TCP keepalive. If no data packet is exchanged within 40 seconds, TCP keepalive detection will be triggered. The device initiates a detection every 5 seconds. If the detection fails 4 times in a row, the member is considered offline, and the commander sets it to offline status. This means that if the commander does not receive any packets from the member within 60 seconds, it sets the member to offline status.

SmartMC features

Bulk configuration deployment for members

This feature allows you to deploy multiple command lines to members from the commander, eliminating the need to log in to members and configure the command one by one.

The procedure for bulk configuration deployment is as follows:

1. The commander acts as a Telnet client and establishes Telnet connections to the members.

2. The commander deploys a batch file to the members through NETCONF sessions. The batch file is created on the commander and contains command lines to be deployed.

3. The members run the command lines in the file.

Bulk configuration deployment for ports connecting APs and IP phones

With batch file deployment enabled, the commander automatically deploys configurations in the specified batch file to a port connecting an AP or IP phone, simplifying access port configuration.

When the commander first detects the association of an AP or IP phone on a port through LLDP, it deploys the command lines in the specified batch file to the port. If no batch file is specified for the device type, the configurations on the port remain unchanged.

If the AP or IP phone disconnects from the port, the configurations on the port remain. When a new device comes online from the port, configurations used by the port depend on the new device type.

· If the new device is an AP or IP phone and has the same type as the disconnected device, the configurations on the port remain unchanged.

· If the new device is an AP or IP phone but has a different type as the disconnected device, the commander deploys the command lines in the specified batch file to the port. If no batch file is specified for the device type, the configurations on the port remain unchanged.

· If the new device is neither an AP nor an IP phone, the configurations on the port remain unchanged.

To disable the commander from deploying a batch file to ports, remove the specified batch file or execute the undo smartmc batch-file-apply enable command to disable batch file deployment.

Configuration file backup

You can use the following methods to back up the next-startup configuration file on the commander and members:

· Automatic backup—Enable this feature for the commander and all members in the network to immediately perform a backup. After that, the commander and members back up the configuration file at a user-specified interval.

· Manual backup—Manually trigger a backup on the commander or the specified members or SmartMC groups.

To back up the configuration file on a member, the commander instructs the member by unicasting a SmartMC packet. When a member receives the packet, it saves the running configuration to the next-startup configuration file and uploads the file to the file server.

Startup software and configuration file upgrade

This feature enables users to upgrade startup software and the configuration file of member devices from the commander.

Before upgrade, you must upload the upgrade files from the commander to the file server and specify the upgrade files on the file server for the members to download.

The procedure for startup software and configuration file upgrade is as follows:

1. The commander instructs the members (or SmartMC group) to download the upgrade files from the file server.

2. The members download the upgrade files from the file server.

3. The members upgrade the startup software and configuration file as follows:

¡ Startup software upgrade—Performs an ISSU with the upgrade startup software files. The members might be restarted during the upgrade process.

¡ Configuration file upgrade—Replaces the current configuration file with the upgrade configuration file. The members will not be restarted during the upgrade process.

Faulty member replacement

You can use the following methods to replace a faulty member:

· Automatic replacement—Enables the commander to record the positions of all members in the topology for replacement. When the commander discovers that the new member has physically replaced the faulty member, it compares the new member with the faulty one. The commander performs a replacement if the following requirements are met:

¡ The new member is deployed at the same topological position as the faulty one.

¡ The models of the new member and faulty member are the same.

The commander then instructs the new member to download the configuration file of the faulty member from the file server. After downloading the configuration file, the new member runs the configuration file to complete the replacement.

· Manual replacement—After the faulty member is physically replaced, you manually trigger a configuration replacement. The new member will download the configuration file of the faulty member from the file server and run the file to complete the replacement.

Outgoing interface for a SmartMC network

The outgoing interface feature allows hosts connecting to an outgoing interface to access all the members in a SmartMC network. You can configure multiple outgoing interfaces for a SmartMC network.

As shown in Figure 2, the host is connected to port 1 on the TM and TC 1 and TC 2 are in a different network segment than the host. The host can access the Web interface of the TM but cannot access the Web interface of any member.

If port 1 on the TM is configured as the outgoing interface, the system mirrors the IP address of each member to a new address. The new address contains the IP address of the outgoing interface and the port number assigned by the commander to the member in the format of IP address:Port number. This enables the host to access the Web interfaces of members from the Web interface of the TM.

To access the Web interface of a member, enter the Web interface of the commander, and click Visibility from the navigation pane. Then, click the Topology tab, select the target member, and click Login to Web interface.

Figure 2 SmartMC network

‌

NOTE:

The S5560X-EI switch series does not support management from the Web interface.

‌

Automatic link aggregation

Automatic link aggregation automatically bundles multiple physical Ethernet links between two members into one logical link, called an aggregate link. This feature provides increased link bandwidth and improved link reliability.

NOTE:

· Automatic link aggregation cannot be performed between the commander and a member, or between a member and a device outside the SmartMC network. You can aggregate the links between the commander and a member manually. For more information about manual link aggregation, see Ethernet link aggregation in Layer 2—LAN Switching Configuration Guide.

· If a member enabled with automatic link aggregation joins a SmartMC network whose commander is disabled with the aggregation feature, the feature will be disabled for the member as well. This might affect service traffic forwarding on the member.

‌

VLAN creation for members

To simplify configuration and management, you can create a VLAN for members. Then, all access ports on a member that are not connected to other members or the commander are assigned to the VLAN.

If a member has access ports that are connected to offline devices, you must remove the offline devices before creating a VLAN for the member.

The VLAN creation fails for a member if one or more access ports cannot be assigned to the VLAN. If the VLAN creation fails, the VLAN memberships for the access ports are restored to the state before the VLAN was created.

The failure to create a VLAN for a member does not affect the VLAN creation for other members.

Resource monitoring

Resource monitoring allows you to view CPU usage, memory usage, temperature information, and packet dropping information of commanders and members on the commander. Packet dropping monitoring monitors packet dropping on members and on interfaces.

You can view the usage and temperature information on the commander, and view packet dropping information from the SmartMC > Intelligent O&M > Resource monitoring page of the commander's Web interface (The S5560X-EI series switches do not support management from the Web interface).

QuickNet solution

The H3C QuickNet solution relies on H3C intelligence-native technology to achieve automatic discovery of network devices, automatic networking, one-click onboarding, and network-wide management. Users can perform lightweight management of the network through a mobile browser with domain name login and an extremely simple interface. Additionally, users can manage QuickNet locally through the Cloudnet App.

The device supports functioning as a TC and can join QuickNet through SmartMC to be managed by QuickNet. The device's factory configuration includes a local user named admin and password admin, along with the smartmc tc enable command. For devices to join QuickNet, make sure the TCs and the TM in QuickNet have Layer 2 and Layer 3 VLAN 1 connectivity. No additional configuration is required.

Restrictions: Hardware compatibility with SmartMC

The ES5500 switch series does not support SmartMC.

Restrictions and guidelines: SmartMC configuration

Only users with the network-admin role can configure SmartMC. For more information about user roles, see RBAC in Fundamentals Configuration Guide.

Devices exchange SmartMC protocol packets and establish and maintain the SmartMC network only in VLAN 1. To ensure the proper functioning of SmartMC, make sure the interfaces connecting member devices within the SmartMC network allow VLAN 1 packets to pass through.

You need to enable SmartMC on both the commander and members and perform all the other SmartMC tasks only on the commander.

The following features take effect only on members automatically added to the network:

· Backing up configuration files.

· Replacing faulty members.

· Upgrading the startup software and configuration file on members.

· Configuring automatic Ethernet link aggregation.

SmartMC tasks at a glance

To configure SmartMC, perform the following tasks:

1. Enabling SmartMC

2. Specifying a file server

This task is required for configuring automatic configuration file backup, replacing faulty members, and upgrading the startup software and configuration file on members.

3. (Optional.) Configuring an outgoing interface for the SmartMC network

4. (Optional.) Enabling automatic Ethernet link aggregation

5. (Optional.) Modifying the password of the default user for members

6. Creating a SmartMC group

This task is required for upgrading the startup software and configuration file on members and deploying a batch file to a SmartMC group.

7. (Optional.) Deploying and managing configuration

¡ Creating a VLAN for members

¡ Deploying a batch file to members

¡ Configuring a batch file for ports connecting APs or IP phones

¡ Backing up configuration files

8. (Optional.) Monitoring and maintaining the SmartMC network

¡ Configuring SmartMC health check

¡ Configuring resource monitoring

¡ Upgrading the startup software and configuration file on members

¡ Managing the network topology

¡ Replacing faulty members

Prerequisites for SmartMC

Before you configure SmartMC, perform the following tasks on the commander and members:

· Enable the Telnet service, and configure scheme authentication for VTY user lines. For information about Telnet service and VTY user lines, see CLI login configuration in Fundamentals Configuration Guide.

· Configure a local user.

¡ Specify the username and password.

- On the commander, make sure the username and password are the same as the username and password configured by using the smartmc tm username username password { cipher | simple } string enable command.

- On a member, set both the username and password to admin, and execute the password-control length 4, password-control composition type-number 1 type-length 1, and undo password-control complexity user-name check commands to lower the password complexity requirements.

This is because SmartMC requires that the commander use username admin and password admin to communicate with members, which does not meet the default password complexity requirements. For more information about these commands, see password control commands in Security Command Reference.

After the SmartMC network is established, you can increase the password complexity requirements and use the smartmc tc password command to modify the username and password.

¡ Specify the Telnet, SSH, HTTP, and HTTPS services for the user.

¡ Set the RBAC role of the local user to network-admin.

For information about local users, see AAA configuration in Security Configuration Guide. For information about user roles, see RBAC configuration in Fundamentals Configuration Guide.

· Enable NETCONF over SOAP over HTTP. For information about NETCONF over SOAP, see NETCONF configuration in Network Management and Monitoring Configuration Guide.

· Enable NETCONF over SSH. For more information about NETCONF over SSH, see "Configuring NETCONF."

· Configure public key management for SSH authentication. Execute the ssh user admin service-type netconf authentication-type publickey assign publickey -smartmc-publickey- command on the member to configure the authentication method for SSH users. Digital signature is supported. The username must be admin for an SSH user and the public key name must be -smartmc-publickey- for the SSH client. For more information about public key management, see Security Configuration Guide.

· Enable LLDP globally. For information about LLDP, see Layer 2—LAN Switching Configuration Guide.

Enabling SmartMC

About this task

Enable this feature on both the commander and members to enable management of members from the commander.

Restrictions and guidelines

You can also configure a device as the commander by pressing the MODE button on the device's front panel for 3 to 5 seconds. In this case, the system sets both the username and password of the commander to admin.

A SmartMC network must have one and only one commander.

If you change the role of the commander to member or disable SmartMC on the commander, all SmartMC settings in its running configuration will be cleared.

SmartMC fails to be enabled if ACL resources are insufficient. If ACL resources are insufficient, use the undo acl command to delete unnecessary ACLs and then enable SmartMC. You can execute the display acl command to view ACL configuration and match statistics. For more information about ACLs, see ACL and QoS Configuration Guide.

SmartMC fails to be enabled if ports 80 and 443 have been used.

If you execute the smartmc enable command multiple times, the most recent configuration takes effect. You can execute the command to change the device role or the password.

Procedure

1. Enter system view.

system-view

2. Enable SmartMC and set the device role.

smartmc { tc | tm username username password { cipher | simple } string } enable

By default, SmartMC is disabled.

Specifying a file server

About this task

In a SmartMC network, a file server is used to store the following files:

· Upgrade startup software files and upgrade configuration file for members.

· Backup configuration files of the commander and members.

The system supports using an FTP or SFTP server as the file server. For information about FTP servers, see configuring FTP in Fundamentals Configuration Guide. For information about SFTP servers, see configuring SSH in Security Configuration Guide.

Restrictions and guidelines

You can use the following methods to specify a file server:

· Specify the IP address of a file server.

· Specify the IP address of the commander. The commander will act as a file server.

To configure the commander to act as a file server, make sure the commander has enough storage space for storing the files required by members.

To use an independent file server, connect the file server to the commander instead of the members as a best practice. The file server uses VLAN 1 to communicate with the SmartMC network. If you connect the file server to members, creating a VLAN for members will assign member interfaces connecting to the file server to the created VLAN, causing file server disconnection. For more information about member VLAN creation, see "Creating a VLAN for members."

Procedure

1. Enter system view.

system-view

2. Specify a file server.

smartmc { ftp-server | sftp-server } { ipv4-address | ipv6 ipv6-address } [ port port ] [ vpn-instance vpn-instance-name ] [ directory directory ] username username password { cipher | simple } string

By default, no file server is specified.

Configuring an outgoing interface for the SmartMC network

Restrictions and guidelines

VLAN-interface 1 cannot be used as an outgoing interface, because the SmartMC network is established in VLAN 1.

A member port of a Layer 3 aggregation group cannot be used as an outgoing interface for SmartMC, and vice versa. If a configured outgoing interface is a member port of a Layer 3 aggregation group, the outgoing interface does not take effect. For more information about Layer 3 aggregation groups, see Ethernet link aggregation in Layer 2—LAN Switching Configuration Guide.

If you specify a VLAN interface as the outgoing interface, the system issues the service slot slot-number command to the outgoing interface and VLAN-interface 1. The slot-number argument represents the member ID of the master device. If you specify a Layer 3 Ethernet interface as the outgoing interface, the system issues the command only to VLAN-interface 1. If you remove the outgoing interface configuration, the service slot slot-number configuration remains, and you can modify the configuration manually as needed.

For more information about the service command, see VLAN commands in Layer 2—LAN Switching Command Reference.

Procedure

1. Enter system view.

system-view

2. Enter VLAN interface view or Layer 3 Ethernet interface view.

¡ Enter VLAN interface view.

interface vlan interface-number

¡ Enter Layer 3 Ethernet interface view.

interface interface-type interface-number

3. Configure the interface as an outgoing interface.

smartmc outbound

By default, no interface is used as an outgoing interface.

Enabling automatic Ethernet link aggregation

Restrictions and guidelines

Enabling or disabling automatic link aggregation might cause network flapping, and the members might go offline for a short period of time.

Procedure

1. Enter system view.

system-view

2. Enable automatic Ethernet link aggregation.

smartmc auto-link-aggregation enable

By default, automatic Ethernet link aggregation is disabled.

Modifying the password of the default user for members

About this task

During SmartMC network establishment, the commander uses the default username and password to establish NETCONF sessions to members automatically added to the network. The default username and password of the members for NETCONF session establishment are admin and admin.

To enhance security, you can perform this task to change the password for the default user admin of the members after the commander adds the members to the network.

Restrictions and guidelines

Do not modify the password for members that are manually added to the SmartMC network. If you modify the password for a manually added member, you will not be able to manage that member from the commander.

You can use the display smartmc tc verbose command to identify the method used to add the members.

Procedure

1. Enter system view.

system-view

2. Modify the password of the default user for members.

smartmc tc password [ cipher ] string

Creating a SmartMC group

About this task

This feature allows you to create a SmartMC group on the commander and add members to the group. When you perform the following operations, you can specify a SmartMC group to apply the operations to all members in the group:

· Startup software upgrade.

· Configuration file upgrade.

· Configuration deployment.

Procedure

1. Enter system view.

system-view

2. Create a SmartMC group and enter its view.

smartmc group group-name

3. (Optional.) Display predefined device types.

match device-type ?

4. Set a match criterion.

match { device-type device-type | ip-address ip-address { ip-mask-length | ip-mask } | mac-address mac-address mac-mask-length }

By default, no match criterion is set.

5. If the device type of the members is not predefined on the commander, perform the following tasks to manually define the device type on the commander:

a. Return to system view.

quit

b. Define a device type on the commander.

smartmc tc sysoid sysoid device-type device-type

To obtain the SYSOID of a member, execute the display smartmc tc verbose command.

You cannot define a predefined member type as another type.

Creating a VLAN for members

Restrictions and guidelines

If you perform this task multiple times to create a VLAN for members, the most recent configuration takes effect.

Procedure

1. Enter system view.

system-view

2. Creating a VLAN for members and assign access ports on the members to the VLAN.

smartmc vlan vlan-id { group group-name-list | tc tc-id-list }

Deploying a batch file to members

About this task

Perform this task to distribute the configurations from a specified configuration file to multiple member devices at once, in order to reduce the workload of configuring each device individually.

Restrictions and guidelines

Make sure the configuration file does not contain the undo smartmc enable and undo telnet server enable commands as these two commands might cause the configuration link to disconnect, leading to the failure of the remaining configuration distribution.

Procedure

1. Execute the following command in user view to create a batch file and edit the command lines to be deployed to members.

create batch-file cmd-filename

Each command occupies a line in the batch file. When you finish editing, enter a percent sign (%) to return to user view.

Make sure the command lines that you enter are correct because the system does not verify whether the command lines are correct.

2. Enter system view.

system-view

3. Deploy the batch file to a list of members or SmartMC groups.

smartmc batch-file cmd-filename deploy { group group-name-list | tc tc-id-list }

Configuring a batch file for ports connecting APs or IP phones

About this task

This feature is designed to automatically detect the connection of APs and IP phones, and to automatically distribute configurations in bulk to the access ports. This simplifies and accelerates the process of configuring network devices, providing network administrators with an efficient management method.

The working mechanism of this feature is as follows:

1. Create batch files: The network administrator creates and binds command line batch files for APs and IP phones through the Web interface.

2. Device access: APs or IP phones connect to the SmartMC network through a TC.

3. Configuration deployment: Once the TM detects the connection of an AP or IP phone using the LLDP protocol, it sends the configurations from the corresponding command line batch file to the access port of the AP or IP phone, thus achieving automated configuration for the APs and IP phones.

Restrictions and guidelines

All commands in the batch file must be commands used in interface view.

The size of the batch file cannot exceed 8190 characters.

Make sure the file name is correct when specifying the batch file because the system does not verify whether the file name is correct. After specifying the batch file, do not delete the file or rename the file.

Content changes of a batch file and binding of a different batch file on the device affect only APs and IP phones that come online afterwards. The APs and IP phones that are already connected are not affected.

Procedure

1. Execute the following command in user view to create a batch file and edit the command lines to be deployed to members.

create batch-file cmd-filename

Each command occupies a line in the batch file. When you finish editing, enter a percent sign (%) to return to user view.

Make sure the command lines that you enter are correct because the system does not verify whether the command lines are correct.

2. Enter system view.

system-view

3. Specify the batch file for ports connecting APs or IP phones.

smartmc batch-file batch-file-name apply { ap | phone }

4. (Optional.) Disable batch file deployment.

undo smartmc batch-file-apply enable

By default, batch file deployment is enabled.

Backing up configuration files

About this task

Perform this task to back up the configuration file of the commander or the specified members. Configuration files automatically backed up to the file server are named in the format of device_bridge_MAC_address_backup.cfg.

Restrictions and guidelines

When you change the commander in the SmartMC network, make sure the backup configuration file of the original commander on the file server is deleted. If the file still exists, the new commander might download the file and run the settings. This will cause a conflict in the network.

The maximum number of members that can perform automatic configuration at the same time is limited by the performance of the file server. If automatic configuration backup fails, set the maximum number of members to a smaller value.

Prerequisites

Before performing this task, you must specify a file server (see "Specifying a file server").

Procedure

1. Enter system view.

system-view

2. Set the maximum number of members that can perform configuration file backup at the same time.

smartmc backup configuration max-number max-number

By default, a maximum of five members can perform automatic configuration backup at the same time.

3. Back up configuration files.

Choose one option as needed:

¡ Enable automatic configuration file backup and set the backup interval.

smartmc backup startup-configuration interval interval-time

By default, automatic configuration file backup is disabled.

¡ Manually back up the configuration file on the commander or the specified members.

smartmc backup configuration { group group-name-list | tc [ tc-id-list ] }

TC ID 0 represents the commander.

Configuring SmartMC health check

About this task

Application scenarios

After adding devices to the SmartMC network, you can log in to the SmartMC network management platform and manage the entire SmartMC network through the Web interface. To use the health check function on the SmartMC platform, first enable SmartMC health check on devices.

Operating mechanism

With SmartMC health check enabled, the system collects environment, capacity, performance, and status health statistics on the specified devices at intervals of 30 minutes. Through summarization and calculation, SmartMC displays the statistics in graph format on the Web interface for network administrators to obtain the member status and the overall network status in time.

Network administrators can also trigger statistics collection manually to collect the sampling or trigger values for the most recent collection immediately even if the 30-minute interval is not reached.

Prerequisites

The SmartMC health check feature requires the data provided by the Key Performance Indicator (KPI) module. For SmartMC health check to operate correctly, you must first configure KPI data collection. For more information about KPI data collection, see "Configuring KPI data collection."

SmartMC health check uses the NETCONF over SSH channels established at SmartMC creation to transmit data.

Restrictions and guidelines

Make sure SmartMC is already enabled.

Collecting health check information consumes device performance. If health check is not necessary for a member device, disable health check on the device.

Procedure

1. Enter system view.

system-view

2. Enable SmartMC health check.

smartmc health-check enable [ tc tc-id-list | tm ]

By default, SmartMC health check is disabled.

3. (Optional.) Trigger an immediate collection of the health check data.

smartmc health-check collect

Configuring resource monitoring

Restrictions and guidelines

Enable and disable this feature as needed. Enabling resource monitoring when the number of online members reaches a certain threshold may cause the commander's CPU to become busy and memory space to be insufficient.

Procedure

1. Enter system view.

system-view

2. Set the interval for the commander to obtain resource monitoring information.

smartmc resource-monitor interval interval

The default setting is 1 minute.

3. Set the aging time for resource monitoring information.

smartmc resource-monitor max-age max-age

The default setting is 24 hours.

4. Enable resource monitoring.

smartmc resource-monitor [ cpu | memory | packet-drop | temperature ] * [ group group-name-list | tc { tc-id-list | mac-address mac-address } | tm ]

By default, resource monitoring is disabled.

If you do not specify a resource type, this command enables resource monitoring for all resource types.

If you do not specify a device to monitor (member or commander), this command enables resource monitoring on the commander and all members.

Upgrading the startup software and configuration file on members

About upgrading the startup software and configuration file on members

You can use the following methods to upgrade the startup software and configuration file on members:

· Schedule an upgrade by specifying an upgrade time or upgrade delay.

· Upgrade immediately by not specifying an upgrade time or upgrade delay.

Restrictions and guidelines for startup software and configuration file upgrade

A member can perform only one upgrade task at a time.

An immediate upgrade cannot be cancelled. If you specify a delay time or upgrade time to perform a scheduled upgrade, the upgrade operation can be cancelled by using the undo smartmc upgrade command before it starts.

Prerequisites

Before performing this task, you must specify a file server (see "Specifying a file server").

Upgrading the startup software and configuration file on members

Upgrading the startup software and configuration file in one step

1. Enter system view.

system-view

2. Upgrade the startup software on members in one step.

smartmc upgrade boot-loader tc { tc-id-list { boot boot-filename system system-filename | file ipe-filename } }&<1-40> [ delay delay-time | time in-time ]

CAUTION:

Upgrading the startup software might interrupt services. Before upgrading the startup software, make sure no services will be interrupted.

3. Upgrade the configuration file on members in one step.

smartmc upgrade startup-configuration tc { tc-id-list cfg-filename }&<1-40> [ delay delay-time | time in-time ]

CAUTION:

After you update the configuration file, the configuration in the new configuration file will become the running configuration. Before upgrading the configuration file, make sure the contents of the new configuration file are correct.

‌

Configuring startup software and configuration file upgrade step by step

1. Enter system view.

system-view

2. Configure startup software upgrade for members step by step:

a. Specify the upgrade startup software files.

smartmc tc tc-id boot-loader { ipe-filename | boot boot-filename system system-filename }

b. Upgrade the startup software on members.

smartmc upgrade boot-loader tc tc-id-list

CAUTION:

Upgrading the startup software might interrupt services. Before upgrading the startup software, make sure no services will be interrupted.

3. Configure configuration file upgrade for members step by step:

a. Specify the upgrade configuration file.

smartmc tc tc-id startup-configuration cfg-filename

b. Upgrade the configuration file on members.

smartmc upgrade startup-configuration tc tc-id-list

CAUTION:

‌

Upgrading the startup software and configuration file on all members in SmartMC groups

Upgrading the startup software and configuration file in one step

1. Enter system view.

system-view

2. Upgrade the startup software on all members in SmartMC groups in one step.

smartmc upgrade boot-loader group { group-name-list [ boot boot-filename system system-filename | file ipe-filename ] }&<1-40> [ delay minutes | time in-time ]

CAUTION:

Upgrading the startup software might interrupt services. Before upgrading the startup software, make sure no services will be interrupted.

3. Upgrade the configuration file on all members in SmartMC groups in one step.

smartmc upgrade startup-configuration group { group-name-list file cfg-filename }&<1-40> [ delay minutes | time in-time ]

CAUTION:

‌

Configuring startup software and configuration file upgrade step by step

1. Enter system view.

system-view

2. Enter SmartMC group view.

smartmc group group-name

3. Specify the upgrade startup software files for the SmartMC group.

boot-loader file { ipe-filename | boot boot-filename system system-filename }

By default, no upgrade startup software files are specified for a SmartMC group.

4. Specify the upgrade configuration file for the SmartMC group.

startup-configuration cfgfile

By default, no upgrade configuration file is specified for a SmartMC group.

5. Return to system view.

quit

6. Upgrade the startup software and configuration file on all members in the SmartMC group.

Choose one option as needed:

¡ Upgrade the startup software.

smartmc upgrade boot-loader group group-name-list [ delay minutes | time in-time ]

CAUTION:

Upgrading the startup software might interrupt services. Before upgrading the startup software, make sure no services will be interrupted.

¡ Upgrade the configuration file.

smartmc upgrade startup-configuration group group-name-list [ delay minutes | time in-time ]

CAUTION:

‌

Managing the network topology

Refreshing the network topology

About this task

You can use the following methods to refresh the network topology:

· Automatic topology refresh—Specify the refresh interval to allow the commander to refresh the network topology periodically.

· Manual topology refresh—Execute the smartmc topology-refresh command to manually refresh the network topology.

Restrictions and guidelines

The topology refresh time depends on the number of members in the network.

When the number of online members in the network is greater than 64, the commander calculates the refresh interval of the network topology based on the number of online members. The calculation formula is (N+64)/64 multiplied by the set refresh interval, where N represents the number of online members.

Procedure

Choose one option as needed:

· Manually refresh the network topology in any view.

smartmc topology-refresh

· Configure automatic network topology refresh.

a. Enter system view.

system-view

b. Set the automatic topology refresh interval.

smartmc topology-refresh interval interval

By default, the automatic topology refresh interval is 60 seconds.

Saving the network topology

About this task

This task allows you to save the current network topology to the topology.dba file in the flash memory. After the commander reboots, it uses the topology.dba file to restore the network topology.

Procedure

1. Enter system view.

system-view

2. Save the network topology.

smartmc topology-save

Replacing faulty members

Restrictions and guidelines

Make sure the new member for replacement and the faulty member have the same neighbor relationship and device model.

Make sure the new member has a different member ID than all the members in the SmartMC network, including offline members. Faulty members are considered offline.

To automatically replace a faulty member, first enable automatic replacement, and then install the new member at the location where the faulty member was installed and connect all cables.

To manually replace a faulty member, first install the new member at the location where the faulty member was installed, connect all cables, and then execute the manual replacement command.

Prerequisites

Before you replace a faulty member, specify a file server (see "Specifying a file server").

Procedure

1. Enter system view.

system-view

2. Replace faulty members.

Choose one option as needed:

¡ Enable automatic faulty member replacement.

smartmc auto-replace enable

By default, automatic faulty member replacement is disabled.

¡ Manually replace a faulty member.

smartmc replace tc tc-id1 faulty-tc tc-id2

Display and maintenance commands for SmartMC

Execute display commands in any view.

Task	Command
Display the backup status on members.	display smartmc backup configuration status
Display the batch file execution results.	display smartmc batch-file status [ ap \| last number \| phone ]
Display SmartMC configuration.	display smartmc configuration
Display connections between the devices in the SmartMC network.	display smartmc device-link
Display SmartMC group information.	display smartmc group [ group-name ] [ verbose ]
Display the faulty member replacement status.	display smartmc replace status
Display resource monitoring information.	display smartmc resource-monitor [ cpu \| memory \| temperature ] * [ tc tc-id \| tm ]
Display resource monitoring configuration.	display smartmc resource-monitor configuration
Display member information.	display smartmc tc [ tc-id ] [ verbose ]
Display log information in the log buffer on a member.	display smartmc tc tc-id log buffer [ module module-name [ mnemonic mnemonic-value ] ]
Display restart log information for a member.	display smartmc tc tc-id log restart
Display VLAN creation results for members.	display smartmc vlan
Display member upgrade status.	display smartmc upgrade status

‌

SmartMC configuration examples

Example: Configuring SmartMC

Network configuration

As shown in Figure 3, member 1, member 2, and member 3 belong to the same device type: S5560X-EI series. The IP address of the file server is 192.168.2.1. The username and password for accessing the file server are admin and hello12345, respectively.

Perform the following tasks to establish a SmartMC network and upgrade the configuration file on the members:

1. Configure the commander and members to automatically establish a SmartMC network.

2. Configure interface GigabitEthernet 1/0/1 as the outgoing interface for the SmartMC network.

3. Create a SmartMC group and add the members to the group.

4. Upgrade the configuration file on all members in the SmartMC group.

5. Save configuration file startup.cfg on the file server.

Figure 3 Network diagram

‌

Procedure

1. Configure TC 1:

# Configure VLAN-interface 1.

<TC1> system-view

[TC1] interface vlan-interface 1

[TC1-Vlan-interface1] ip address 192.168.2.3 24

[TC1-Vlan-interface1] quit

# Enable HTTP and HTTPS.

[TC1] ip http enable

[TC1] ip https enable

# Enable the Telnet service.

[TC1] telnet server enable

# Enable NETCONF over SOAP over HTTP.

[TC1] netconf soap http enable

# Enable NETCONF over SSH.

[TC1] netconf ssh server enable

# Enable LLDP globally.

[TC1] lldp global enable

# Create a user.

[TC1] local-user admin

# Lower password complexity requirements. For more information about these commands, see password control commands in Security Command Reference.

[TC1-luser-manage-admin] password-control length 4

[TC1-luser-manage-admin] password-control composition type-number 1 type-length 1

[TC1-luser-manage-admin] undo password-control complexity user-name check

# Set the username and password to admin, add the telnet, http, and https service types, and authorize the user to use the network-admin user role.

[TC1-luser-manage-admin] password simple admin

[TC1-luser-manage-admin] service-type telnet http https ssh

[TC1-luser-manage-admin] authorization-attribute user-role network-admin

[TC1-luser-manage-admin] quit

# Set the system to support public key authentication for the administrator to login through SSH. The public key name must be -smartmc-publickey-.

[TC1] ssh user admin service-type netconf authentication-type publickey assign publickey -smartmc-publickey-

# Set scheme authentication for VTY user lines 0 to 63.

[TC1] line vty 0 63

[TC1-line-vty0-63] authentication-mode scheme

[TC1-line-vty0-63] quit

# Enable SmartMC and set the device role to tc.

[TC1] smartmc tc enable

2. Configure TC 2 and TC 3 in the same way TC 1 is configured. (Details not shown.)

3. Configure the TM:

# Configure GigabitEthernet 1/0/1.

<TM> system-view

[TM] interface gigabitethernet 1/0/1

[TM-GigabitEthernet1/0/1] port link-mode route

[TM-GigabitEthernet1/0/1] ip address 192.168.52.2 24

[TM-GigabitEthernet1/0/1] quit

# Configure VLAN-interface 1.

[TM] interface vlan-interface 1

[TM-Vlan-interface1] ip address 192.168.2.2 24

[TM-Vlan-interface1] quit

# Enable HTTP and HTTPS.

[TM] ip http enable

[TM] ip https enable

# Enable the Telnet service.

[TM] telnet server enable

# Enable NETCONF over SOAP over HTTP.

[TM] netconf soap http enable

# Enable NETCONF over SSH.

[TM] netconf ssh server enable

# Enable LLDP globally.

[TM] lldp global enable

# Create a user. Set the username to admin and the password to hello12345, add the telnet, http, and https service types, and authorize the user to use the network-admin user role.

[TM] local-user admin

[TM-luser-manage-admin] password simple hello12345

[TM-luser-manage-admin] service-type telnet http https ssh

[TM-luser-manage-admin] authorization-attribute user-role network-admin

[TM-luser-manage-admin] quit

# Set scheme authentication for VTY user lines 0 to 63.

[TM] line vty 0 63

[TM-line-vty0-63] authentication-mode scheme

[TM-line-vty0-63] quit

# Enable SmartMC, set the device role to commander, and set the username to admin and the password (plaintext) to hello12345.

[TM] smartmc tm username admin password simple hello12345 enable

# Specify GigabitEthernet 1/0/1 as the outgoing interface.

[TM] interface gigabitethernet 1/0/1

[TM-GigabitEthernet1/0/1] smartmc outbound

[TM-GigabitEthernet1/0/1] quit

# Set the file server IP address, username, and plaintext password to 192.168.2.1, admin, and hello12345, respectively.

[TM] smartmc ftp-server 192.168.2.1 username admin password simple hello12345

# Create SmartMC group S1 and enter its view.

[TM] smartmc group S1

# Create an IP address match criterion to add all members in the specified network segment to SmartMC group S1.

[TM-smartmc-group-S1] match ip-address 192.168.2.0 24

# Specify the upgrade configuration file startup.cfg for SmartMC group S1.

[TM-smartmc-group-S1] startup-configuration startup.cfg

[TM-smartmc-group-S1] quit

# Upgrade the configuration file on all members in SmartMC group S1.

[TM] smartmc upgrade startup-configuration group S1 file startup.cfg

Verifying the configuration

# Display brief information about all members after the SmartMC network is established.

[TM] display smartmc tc

TCID DeviceType Sysname IpAddress MacAddress Status Version

1 S5560X-EI TC1 192.168.2.3 201c-e7c3-0300 Normal COMWAREV700R001

2 S5560X-EI TC2 192.168.2.4 201c-e7c3-0301 Normal COMWAREV700R001

3 S5560X-EI TC3 192.168.2.5 201c-e7c3-0302 Normal COMWAREV700R001

# Display the configuration file upgrade status on the members.

[TM] display smartmc upgrade status

ID IpAddress MacAddress Status UpdateTime UpdateFile

1 192.168.2.3 201c-e7c3-0300 Finished Immediately startup.cfg

2 192.168.2.4 201c-e7c3-0301 Finished Immediately startup.cfg

3 192.168.2.5 201c-e7c3-0302 Finished Immediately startup.cfg

Configuring self-mesh SmartMC (SmartMC 2.0)

About self-mesh SmartMC

Self-mesh SmartMC is a technology that enables devices to automatically form a SmartMC network. Its core objective is to allow devices in a user's network (such as ACs, APs, routers, firewalls, and switches) to achieve plug-and-play functionality and automatically form a SmartMC network using factory configurations. Within this network, one device is automatically elected as the TM, and the remaining devices act as TCs. Through the TM, network administrators can centrally manage all network access devices, reducing management complexity and improving efficiency.

In practical network applications, considering the network placement of switches, access switches are typically set to be TCs through their factory files, and core switches require manual configuration by the network administrator to be set as either TM or TC. Thus, in a SmartMC self-mesh network, switches do not support automatic election of TM or TC roles. Switches of this series come with SmartMC configurations and act as TCs by default.

Benefits of self-mesh SmartMC

Self-mesh SmartMC has the following advantages:

· Simplifies network setup by supporting device plug-and-play. By using factory default settings, self-mesh SmartMC initializes configurations from the Web interface and then allows devices to automatically form a SmartMC network.

· Simplifies network maintenance by enabling centralized management and maintenance of many network devices through simple web-based operations on the SmartMC network management platform. This effectively solves operational problems in small and medium-sized campus networks.

Self-mesh SmartMC application scenarios

Self-mesh SmartMC is typically used for plug-and-play and zero-configuration startup of LAN devices. The application scenarios of self-mesh SmartMC are divided into the following main categories: Pure wired self-mesh SmartMC and unified wired and wireless self-mesh SmartMC.

Scenario one: Pure wired self-mesh SmartMC

As shown in Figure 4, the network contains switches, routers, and security devices. Self-mesh SmartMC can be used to achieve the following if all of the devices support self-mesh SmartMC:

· The network administrator configures the role of the core switch as TM. The other switches are defined as TCs through manual configuration or in the factory configuration file.

· The router and the firewall automatically become TCs.

· The network administrator manages and maintains other switches, routers, and security devices centrally through the core switch.

Figure 4 Pure wired self-mesh SmartMC (switch acting as the TM)

Scenario two: Unified wired and wireless self-mesh SmartMC

As shown in Figure 5, the network contains switches, a router, a security device, a wireless AC, and APs. Assuming that all the devices support self-mesh SmartMC, configure the feature to achieve the following:

· The wireless AC is automatically elected as the TM.

· The switches are defined as TCs through manual configuration or in the factory configuration file.

· The router, the firewall, and the APs automatically become TCs.

· The network administrator manages and maintains the switches, the router, the firewall, and the APs centrally through the wireless AC.

Figure 5 Unified wired and wireless self-mesh SmartMC (AC acting as the TM)

As shown in Figure 6, the network contains switches and APs. Assuming that all the devices support self-mesh SmartMC, configure the feature to achieve the following:

· The AP automatically becomes the TM through TM election.

· The switches are defined as TCs through manual configuration or in the factory configuration file.

· The network administrator manages and maintains other APs and the switches centrally through the AP.

Figure 6 Unified wired and wireless self-mesh SmartMC (AC acting as the TM)

Basic concepts of self-mesh SmartMC

SmartMC device roles

In a self-mesh SmartMC network, the following device roles are available:

· Topology master (TM)—Manages all devices in the SmartMC network.

The TM can be automatically elected or manually specified by using the smartmc enable auto tm command. You can specify only one TM in the network. If the TM fails, the TCs automatically elect a new TM.

For a switch to act as the TM, you must execute the smartmc enable auto tm command on the switch.

· Topology client (TC)—Devices managed by the TM in the SmartMC network.

¡ For wireless devices, routers, and security devices, the TC roles are automatically elected. You can use the display smartmc configuration command to view the device roles. The role of an elected TC is displayed as TC(auto).

¡ To cooperate with the self-mesh SmartMC feature, switches of this series come with the SmartMC feature enabled and are configured with the TC role in factory settings (smartmc tc enable). You can use the display smartmc configuration command to verify that the device role is TC.

SmartMC network management platform (UWEB management platform)

The SmartMC network management platform is a Web-based operation interface provided by devices. On the SmartMC network management platform, users can perform simple Web operations to enable unified management and maintenance of numerous network devices, effectively addressing the operational and maintenance issues of small to medium-sized campus networks.

To distinguish from the non-self-mesh SmartMC network management platform, the self-mesh SmartMC network management platform is also called the UWEB management system. The UWEB management system is a lightweight web-based network management platform that uses the SmartMC technology to centrally manage and maintain a large number of dispersed network devices at the network edge. As long as network devices can send and receive Layer 2 packets and VLAN 1 packets, and have SmartMC enabled, they can automatically elect a TM and form a SmartMC network.

The UWEB management system operates on the TM. The UWEB management system can provide the following functions:

· Deployment: Configure the project name, network-wide password, Internet parameters, Wi-Fi settings, and time zone for the SmartMC network.

· Network-wide configuration: Configure WAN settings and wired settings. WAN settings include network access parameters and wired settings include the service VLAN.

· Device management: Add devices, delete offline devices, restart devices, upgrade devices, reset devices, view device details, configure device interfaces, create VLANs, edit VLANs, and delete VLANs.

· Endpoint management: View and manage wired users and wireless users.

· System management: Perform upgrade and restart operations, and change the network-wide password.

By combining the aforementioned functions, you can achieve the following objectives:

· Management the SmartMC network topology.

· Manage member devices in bulk.

In the self-mesh SmartMC chapter, the term "UWEB management platform" refers to the SmartMC network management platform.

Figure 7 UWEB management platform

SmartMC network deployment

After you connect devices, they can discover each other through SmartMC Layer 2 packets. You can execute the display smartmc configuration command on a device as an administrator to view its role, TM(auto) or TC(auto), and view the TM information. If you execute the display smartmc tc command on the TM, the output does not display TC information. You can connect a Web terminal to the TM, open a Web browser, and then enter quicknet.h3c.com in the address bar to access the UWEB management system. Then, you can perform deployment configuration as instructed. During the initial setup process, you can view the network status and configure the network-wide management password, Wi-Fi parameters, and time zone. The configurations will be deployed to all member devices of the SmartMC network and take effect.

The TM then performs the following operations:

1. Generate a NetID for the SmartMC network.

2. Request the login administrator to set the management password (network-wide password of SmartMC), and then synchronize the password and NetID to all member devices in the SmartMC network.

3. Set all the devices that have the password and NetID in deployment state.

The deployment state is a crucial factor of TM election.

SmartMC network-wide password

After establishing Layer 2 connections in the SmartMC network, the SmartMC module on the TM must establish Layer 3 communication channels with the NETCONF module on the TM and each TC to synchronize configurations and manage devices.

To ensure secure communication, a username and password are required for identity authentication between member devices during Layer 3 communication channel establishment. Devices are factory-set with default usernames and passwords. For both security and convenience purposes, SmartMC supports changing the Layer 3 communication channel password using the network-wide password function. When the TM changes the SmartMC network-wide password, it syncs with all member devices (including the TM and TCs), and all devices use the new password to establish new Layer 3 communication channels.

When you perform network deployment on the UWEB management platform, you can set the SmartMC network-wide password. During TM operation, you can access the UWEB management platform or the CLI of the TM to change the SmartMC network-wide password.

SmartMC NetID

NetID is the identifier of a SmartMC network in the SmartMC system, and one SmartMC network corresponds to only one NetID.

To adapt to various networking applications, multiple SmartMC networks can be deployed in the same network, and NetID is used to distinguish between different SmartMC networks. One device can only join one SmartMC network. As shown in Figure 8, the TM broadcasts SmartMC protocol packets to discover TCs in the respective SmartMC network. To avoid interference between SmartMC protocol packets of two SmartMC networks, SmartMC uses NetID to distinguish between different SmartMC networks. When a member device in a SmartMC network receives a SmartMC packet with a different NetID, it directly discards it.

NetID is automatically generated by the SmartMC module during deployment on the UWEB management system.

Figure 8 Multi-SmartMC networking

Role selection in self-mesh SmartMC

CAUTION:

· The device manually specified as the TM by using the smartmc enable auto tm command does not participate in role election and its role is fixed at TM. The other devices in the network act as TCs and role election will not be performed.

· Device manually specified as TCs by using the smartmc tc enable command does not participate in role election and their roles are fixed at TC.

· The device specified as the TM by using the smartmc tm enable command operates in SmartMC 1.0 state and cannot join a SmartMC network formed automatically.

The roles of switches are specified through the CLI, but ACs, APs, routers, and firewall devices support auto role election. In a self-mesh SmartMC network, role election is triggered if one of the following conditions exist:

· Device interconnection is complete. This triggers auto SmartMC deployment.

· The TM leaves or fails.

· The auto SmartMC network splits.

· Two or more independent SmartMC networks merge into one auto SmartMC network.

The following priority order is used to select the TM in the role election:

1. The current TM.

If a TM already exists in the current SmartMC network, other devices that support role election will automatically become TCs and join the SmartMC network.

2. The device with the highest SmartMC election priority.

¡ The priority of a device is carried by the factory parameters of the device, which is determined by the product according to the device model, the network location of the device, and other information. It cannot be modified by command line. The election priorities of the following devices are in descending order: AC, router, security device, and AP. For example, if an AC, a switch, and an AP exist in the network at the same time, the AC has the highest priority and is prioritized as the TM.

¡ If none of the devices participating in the role election have finished startup deployment, the device with higher SmartMC priority will be selected as the TM.

¡ If the SmartMC network has finished startup deployment and a new device with a higher priority than the TM joins, the new device synchronizes the global configuration of the current TM and runs as the TM. The new TM notifies the original TM to change to TC. If the SmartMC election priority of the new device is equal to or lower than that of the current TM, the role of the current TM remains unchanged, and the new device joins as a TC.

3. Devices in the startup state.

If the election priority is the same, and some devices have started while others have not, devices that have started will be selected as the TM first.

4. The TM with the most member devices.

When two SmartMC networks merge, the two SmartMC networks compete for the TM. The SmartMC network with more member devices wins the election, and the TM in the winning SmartMC network becomes the TM for the entire merged SmartMC network. All member devices in the losing SmartMC network run as TC and synchronize the global configuration of the new TM.

5. The device with the highest health score.

6. The device with the lowest bridge MAC address.

Devices running in self-mesh mode broadcast SmartMC election packets at Layer 2 and follow the above rules for judging from the first rule. If a rule matches multiple devices, the next rule will be used until a unique optimal member device is found. The unique optimal member device becomes the TM, and the other member devices become TCs.

Self-mesh SmartMC network establishment and changing

Self-mesh SmartMC network establishment

If a device is manually specified as the TM, the self-mesh SmartMC network is established as follows:

1. The TM broadcasts SmartMC discovery messages every 5 seconds to announce its role as the TM.

2. After being powered on, AC, AP, router, and firewall devices start with the role set to TC(auto). They wait for a certain period to determine if a TM exists in the network. If they receive a SmartMC discovery packet from the TM, they immediately register as TCs with the TM and come under its management, bypassing the role election process.

If no device is manually specified as the TM, the self-mesh SmartMC network is established as follows:

1. After being powered on, AC, AP, router, and firewall devices start with the role set to TC(auto). They wait for a certain period to determine if a TM exists in the network. If no SmartMC discovery packet is received in the period, the devices enter the auto election process. Each device broadcasts SmartMC election packets at intervals of 5 seconds. A SmartMC election packets carries the bridge MAC address, NetID, SmartMC election priority, network size (number of member devices in the SmartMC network), and the IP address of VLAN-interface 1 of the device.

2. One device is elected as the TM and the other devices operate as TCs. (Switches have their roles manually specified from the CLI and do not participate in the role election process.)

¡ If the device receives an election packet from other devices within 20 seconds, it compares its local parameters and the received SmartMC election packet according to the election rules. If the received packet is more optimal, the device switches to TC. If the device is more optimal, it continues to send SmartMC election packets to participate in the role election.

¡ If the device does not receive any election packets from other devices within 20 seconds, it switches to TM.

3. The TM broadcasts SmartMC discovery packets at intervals of 5 seconds to announce its TM identity.

4. Each TC records the device information of the TM and sends a SmartMC discovery ACK packet back to TM. At this time, you can use the display smartmc configuration command on the device to display the configured information of SmartMC.

5. The administrator visits https://quicknet.h3c.com to log in to the UWEB management system to perform the deployment. The UWEB management platform automatically distributes LLDP, NETCONF, and local user configurations to member devices.

6. After receiving the TC's SmartMC discovery ACK packet, the TM uses the default username (admin) and password to establish a NETCONF connection with each member device, and obtains detailed information (such as port information, LLDP neighbor information, STP information, device type, and software version) through this connection. The default password for APs is h3capadmin, and the default password for other types of devices is admin.

7. A TC sends a SmartMC unicast login request packet to the TM. The packet includes the device's bridge MAC and the IP address of VLAN-interface 1.

8. After receiving the TC's login request packet, the TM replies with a login confirmation packet and adds the TC to the SmartMC network. At this point, the TC completes the online process. You can use the display smartmc tc command on the TM to view information about all TCs.

9. The TM forms the SmartMC network topology by using NETCONF connections to obtain its own and TCs' LLDP neighbor information. At this time, you can view the SmartMC network topology diagram on the UWEB management platform, or use the display smartmc device-link command to display the connection information between devices in the SmartMC network.

10. The administrator selects the networking method, sets the administrator password (SmartMC network-wide password), and configures the Internet access parameters as instructed. Then, SmartMC network deployment is completed.

11. The TM synchronizes the network-wide password to itself and all TCs, and establishes a NETCONF connection with each device using the default username and network-wide password.

New device joining

The mechanism for automatically electing TM when a new device joins is as follows:

1. After the SmartMC network is established, the TM broadcasts SmartMC discovery packets every 5 seconds, inquiring if there are member devices in the network.

2. When a new device is connected and powered on:

¡ If the device is a switch and has already been configured as a TM or TC by the factory, it directly joins the SmartMC network as a TM or TC.

¡ If the device is a non-switch device, the device's SmartMC function is enabled by default and it operates in self-mesh mode. The device enters the role election state and, according to the election rules, decides whether to run as TM or TC.

Member device leaving

After the SmartMC network is successfully established, the TM and TCs perceive each other's existence through SmartMC broadcast packets and response packets:

· After the TM leaves, a TC will enter the role election state if it fails to receive TM's SmartMC discovery packets within 20 seconds. TCs will then re-elect a TM according to the role election rules.

· After a TC leaves, the TM considers a TC as offline if it fails to receive any SmartMC discovery ACK packet from the TC within 20 seconds.

Self-mesh SmartMC splitting

If link failures occur between member devices in a self-mesh SmartMC network, TCs and TM may fail to reach each other, causing the SmartMC network to split into multiple SmartMC networks. After the splitting, one SmartMC network contains the original TM, while other SmartMC networks do not have a TM.

During the splitting, the SmartMC software module handles the situation as follows:

· For the SmartMC network that contains the original TM, the SmartMC network continues to operate normally, and the departing member devices become offline.

· For the other SmartMC networks, if some devices work in self-mesh mode, they consider the TM as faulty and trigger role election after 20 seconds without receiving any SmartMC broadcast discovery packets from the TM.

As shown in Figure 9, the roles of TM, TC 1, and TC 3 in the self-mesh SmartMC network are generated through election, and the role of TC 2 is manually specified. Assuming that this self-mesh SmartMC network has been established with a NetID of 1, the following scenarios might occur:

· When the link fails between TC 2 and the TM, TC 2 leaves the self-mesh SmartMC network, but its role remains as TC and its NetID remains as 1.

· When the link fails between TC3 and the TM, TC 3 leaves the self-mesh SmartMC network. After 20 seconds without receiving any SmartMC broadcast discovery packets from the TM, TC 3 re-elects itself as TM with a NetID of 1.

Figure 9 Self-mesh SmartMC splitting

Self-mesh SmartMC merging

The process of multiple stable SmartMC networks interconnecting to form a self-mesh SmartMC network is called self-mesh SmartMC merging.

The following rules are followed during the self-mesh SmartMC merging:

· For SmartMC networks that have already been established, only SmartMC networks with the same NetID can be merged. SmartMC networks with different NetIDs cannot be merged. To add a device with a different NetID to an existing SmartMC network, you must restore the device to factory settings or disable SmartMC on the device to delete the NetID.

· Established SmartMC networks can be merged with non-established SmartMC networks.

When merging, the two SmartMC networks will compete for the TM role. For more information about the TM election rules, see "Role selection in self-mesh SmartMC."

As shown in Figure 10, three SmartMC networks exist in the current network. SmartMC network 1 and SmartMC network 3 have the same NetID, and SmartMC network 2 has a different NetID. When the link failure is recovered, the SmartMC networks will try to merge, as follows:

· SmartMC network 1 has two member devices, which is greater than the number of member devices in SmartMC network 2. Therefore, SmartMC network 1 wins the election and its TM will become the TM of the merged SmartMC network.

· The NetID of SmartMC network 2 is different from that of the other SmartMC networks, so it cannot be merged with any of the other SmartMC networks.

Figure 10 Self-mesh SmartMC merging

Self-mesh SmartMC configuration management

After member devices use Layer 2 connections to build the SmartMC network, the TM automatically establishes a NETCONF session with each TC using VLAN-interface 1. The TM uses the NETCONF sessions to distribute configurations to the TCs and obtain the values of some parameters on the TCs in order to manage and maintain the SmartMC network.

SmartMC supports the following configuration methods:

· Global configuration

Administrators can configure settings on the UWEB management platform's web page or from the TM's CLI. These configurations are distributed to and take effect on all member devices. Global synchronized configurations include wireless, wired, Internet access, SmartMC network-wide password, and FTP server settings.

· Batch configuration

Administrators can configure multiple devices by selecting them on the UWEB management platform's web page. These configurations are distributed to and take effect on the selected member devices. Batch synchronization operations include batch reboot and factory reset.

· Single device configuration

In addition to SmartMC global configuration and batch configuration, administrators can configure parameters for a single member device in the following methods:

¡ Configure the settings for the specified device on the web page. These configurations will be distributed to and take effect on that device.

¡ For configurations not supported by the web page, such as disabling/enabling interfaces or adding interfaces to VLANs, administrators must log in to the member device and use the CLI to configure the settings. Login methods include:

- Use the eWEB or CLI features on the UWEB management platform to log into the local Web interface or CLI of the device.

- Use the IP address of the device to log in to the local Web interface or CLI of the device.

Time synchronization (NTP) for self-mesh SmartMC

After the SmartMC network is deployed, the TM synchronizes the time to all TCs using Network Time Protocol (NTP). The time synchronization precision of NTP is in milliseconds, which can meet the time synchronization requirements of general computer networks. For more information about NTP, see "Configuring NTP."

SmartMC synchronizes time settings across the network as follows:

1. When the SmartMC network is deployed, the TM automatically deletes the existing NTP configuration on the device and generates a new NTP configuration specific to the SmartMC network.

2. The TM acts as an NTP client and synchronizes time with external NTP servers.

The device supports a default of five external NTP servers. When the device receives clock signals from multiple default NTP servers, it selects the optimal clock signal for synchronization. The addresses of the default clock servers are as follows:

¡ registry.h3c.com (H3C time server)

¡ s2f.time.edu.cn (Northeast network center)

¡ cn.pool.ntp.org (NTP project domestic time server)

¡ 1.cn.pool.ntp.org (NTP project domestic time server)

¡ asia.pool.ntp.cn (NTP project Asian time server)

3. If all the five external NTP servers are unavailable, the TM modifies the level of the local clock to 6 and uses the local clock as the clock source for the SmartMC network.

4. The TM acts as an NTP server, and TCs act as NTP clients and synchronize time with the TM.

Figure 11 Time synchronization (NTP) for self-mesh SmartMC

‌

Auto-switching of the DHCP server in SmartMC self-mesh networking

The auto-switching function of the DHCP server refers to the device automatically enabling or disabling its own DHCP server function based on networking needs:

· If the device detects an existing DHCP server in the current network, it automatically disables its own DHCP server function.

· If the device does not detect a DHCP server in the current network, it automatically enables its own DHCP server function.

Both AC and firewall devices support the DHCP server auto-switching function. When both AC and firewall are present in the network, only the DHCP server auto-switching function on the TM is active, and the auto-switching and DHCP server functions are disabled on TCs. The auto-switching function ensures that only one DHCP server exists in the self-mesh SmartMC network at any given time.

To support the self-mesh SmartMC function, the DHCP server function is enabled on VLAN-interface 1 on ACs, firewalls, and routers that support self-mesh SmartMC by default. This setup allows VLAN interface 1 to assign IP addresses to VLAN-interface 1 of the connected switches and APs when only AC, firewall, or router devices are present in the network. This enables these devices to automatically form a SmartMC network using factory settings, as shown in Figure 12.

Figure 12 Using the AC as the DHCP server when no firewall or router exists in the network

However, when the network contains two or more types of devices (ACs, firewalls, and routers), multiple DHCP servers might be present, which might cause IP address conflicts and prevent the devices from automatically form a SmartMC network. To ensure that only one DHCP server is operational at any given time in the self-mesh SmartMC network, SmartMC stipulates:

· For an operational self-mesh SmartMC network, the gateway specified at the start acts as the DHCP server. The DHCP server function must be disabled on the AC and firewall devices in the network and the auto-switching function of the DHCP server must also be disabled.

· For an undeployed self-mesh network:

¡ If a router is deployed (only one router is allowed) and the router acts as the DHCP server, the router does not support auto-switching of the DHCP server.

Figure 13 Using the router as the DHCP server

¡ The AC and firewall devices acting as TCs must be disabled with the DHCP server function and the auto-switching function of the DHCP server.

¡ The AC or firewall device acting as the TM must be enabled with the auto-switching function of the DHCP server. The TM will continuously detect if a DHCP server exists in the network.

- If a DHCP server is detected, the TM disables the DHCP server function.

- If no DHCP server is detected, the TM enables the DHCP server function and resets the IP addresses of VLAN-interface 1 on all TCs. The TCs re-obtain IP addresses for VLAN-interface 1 assigned by the new DHCP server.

This ensures that only one operating DHCP server exists in the network before the SmartMC network is deployed.

Figure 14 Using the TM as the DHCP server when no router exists in the network

UWEB management platform login with a fixed domain name

In a self-mesh SmartMC network, use the UWEB management platform for managing and configuring the network as a best practice. The platform is a web-based interface provided by the devices, allowing for easy management and maintenance of numerous network devices, addressing operational issues in small and medium-sized networks.

Typically, accessing the device's web interface requires its IP address or domain name. If you use a domain name, a DNS server must be deployed in the network and the domain-to-IP mapping must be configured. To simplify network deployment and user operations, SmartMC supports accessing the UWEB management platform using fixed domain name quicknet.h3c.com, even without a DNS server.

The TM automatically establishes a mapping between quicknet.h3c.com and the IP address of the TM's VLAN-interface 1 and synchronizes it with all member devices. Users can log into the UWEB management platform by connecting to any member device and entering the domain name quicknet.h3c.com.

Restrictions and guidelines: Self-mesh SmartMC configuration

The device is initially started with factory settings. After administrators initialize the devices on the UWEB management platform at https://quicknet.h3c.com, the devices can automatically form a SmartMC network.

Device exchange SmartMC protocol packets and establish/maintain the SmartMC network within VLAN 1. To ensure normal operation of SmartMC, make sure that VLAN 1 packets are allowed to pass through interfaces that connect member devices to each other.

Self-mesh SmartMC tasks at a glance

To configure self-mesh SmartMC, perform the following tasks:

1. Enabling SmartMC

2. Setting the network-wide SmartMC password

For security purposes, set the network-wide SmartMC password as a best practice.

3. (Optional.) _Ref142482103

Enabling SmartMC

Restrictions and guidelines

In a self-mesh SmartMC network, do not manually specify the role of devices except for switches as TM or TC.

Make sure only one management device exists in a SmartMC network.

SmartMC requires some ACL resources. Insufficient resources can result in enabling failure of SmartMC. You can use the display acl command to view ACL configuration and running status, and use the undo acl command to delete unused ACLs to release resources. For more information about ACLs, see the ACL and QoS Configuration Guide.

When you enable SmartMC, the device examines if ports 80 and 443 are in use. If they are occupied, SmartMC cannot be enabled because HTTP and HTTPS services require the ports.

When you switch the management device to a member device or disable SmartMC, the system clears SmartMC-related settings in the running configuration.

Configuring a device to act as the TM

1. Enter system view.

system-view

2. Enable SmartMC and specify the device role as TM.

smartmc enable auto tm

By default, the SmartMC feature is disabled.

Configuring a device to act as a TC

1. Enter system view.

system-view

2. Enable SmartMC and specify the device role as TC.

smartmc tc enable

By default, the SmartMC feature is disabled.

Setting the network-wide SmartMC password

About this task

To manage and maintain a SmartMC network, the TM establishes a NETCONF channel with each TC by using the local username (admin) and the default password. To increase device security, you can perform this task to change the password used for NETCONF channel establishment. With the network-wide password set on the TM, the TM issues the password to all member devices. The TM and TCs use the password to re-establish NETCONF channels.

Procedure

1. Enter system view.

system-view

2. Set the network-wide SmartMC password.

smartmc password [ cipher ] string

By default, the default password is h3capadmin for APs and admin for devices of other types.

Setting the FTP server information

About this task

In a SmartMC network, an FTP server is used to store the following files:

· Upgrade startup software files and upgrade configuration file for members.

· Backup configuration files of the commander and members.

After you configure FTP server information on the TM, the TM deploys the information to all member devices. This ensures that the FTP configuration remains active when another device takes up the TM role.

Restrictions and guidelines

You can use the following methods to specify an FTP server:

· Use the TM as the FTP server. Make sure the TM has sufficient space to save files required by TCs. For more information about FTP servers, see Fundamentals Configuration Guide.

· Use an independent FTP server. To use an independent FTP server, connect the FTP server to the TM as a best practice. The FTP server uses VLAN 1 to communicate with the SmartMC network. If you connect the FTP server to TCs, creating a VLAN for members will assign member interfaces connecting to the FTP server to the created VLAN, causing FTP server disconnection.

Procedure

1. Enter system view.

system-view

2. Configure FTP server information.

smartmc ftp-server server-address username username password { cipher | simple } string

By default, no FTP server is specified.

Display and maintenance commands for self-mesh SmartMC

Execute display commands in any view.

Task	Command
Display SmartMC configuration.	display smartmc configuration
Display member device information.	display smartmc tc [ tc-id ] [ verbose ]
Display information about inter-device connections in the SmartMC network.	display smartmc device-link

Self-mesh SmartMC configuration examples

Example: Configuring self-mesh SmartMC with switches acting as TCs (with factory-default SmartMC configuration)

Network configuration

As shown in Figure 15, the network contains a gateway, an aggregation switch, access switches, and fat APs. The gateway acts as the DHCP server to assign an IP address to VLAN-interface 1. The IP address of the DHCP server is 192.168.0.1/24 and the allocable address range for address allocation is 192.168.0.0/24 (excluding 192.168.0.1).

Configure self-mesh SmartMC for devices to automatically form a SmartMC network upon starting up and allow users to manage all the network devices through the UWEB management platform.

Figure 15 Network diagram

Procedure

1. Power on all devices with the default factory configuration. No additional settings are required.

2. Once devices finish booting up, use a PC to connect to the TM. Enter the fixed URL (https://quicknet.h3c.com) in a browser's address bar to log in to the UWEB management platform.

3. Follow the prompts to complete the deployment. Then, the SmartMC network is established automatically.

Figure 16 Home page of the UWEB management platform

Verifying the configuration

On the system summary page of the UWEB management system, you can view the topology of all member devices and view related information.

Example: Configuring self-mesh SmartMC with switches acting as TCs (without factory-default SmartMC configuration)

Network configuration

As shown in Figure 17, the network contains a gateway, an aggregation switch, access switches, and fat APs. The gateway acts as the DHCP server to assign an IP address to VLAN-interface 1. The IP address of the DHCP server is 192.168.0.1/24 and the allocable address range for address allocation is 192.168.0.0/24 (excluding 192.168.0.1).

The aggregation switch does not come with self-mesh SmartMC configuration, but the access switches come with self-mesh SmartMC configuration.

Configure self-mesh SmartMC for devices to automatically form a SmartMC network upon starting up and allow users to manage all the network devices through the UWEB management platform.

Figure 17 Network diagram

Procedure

1. Power on all devices with the default factory configuration. No additional settings are required.

2. Configure the aggregation switch (Device A):

# Enable SmartMC and specify the device role as TC.

<DeviceA> system-view

[DeviceA] smartmc tc enable

# Lower password complexity requirements, create a local user named admin, set the password to admin, and specify the user role as network-admin.

[DeviceA] password-control length 4

[DeviceA] password-control composition type-number 1 type-length 1

[DeviceA] undo password-control complexity user-name check

[DeviceA] local-user admin

[DeviceA-luser-manage-admin] password simple admin

[DeviceA-luser-manage-admin] authorization-attribute user-role network-admin

[DeviceA-luser-manage-admin] quit

3. Wait for all devices to finish booting up, use a PC to connect to the TM. Enter the fixed URL (https://quicknet.h3c.com) in a browser's address bar to log in to the UWEB management platform.

4. Follow the prompts to complete the deployment. Then, the SmartMC network is established automatically.

Figure 18 Home page of the UWEB management platform

Verifying the configuration

On the system summary page of the UWEB management system, you can view the topology of all member devices and view related information.

Example: Configuring self-mesh SmartMC with a switch acting as the TM

Network configuration

As shown in Figure 19, in a pure wired network, the gateway acts as the DHCP server at the same time to assign the IP address of VLAN-interface 1 to LAN devices. The gateway comes with the DHCP server feature enabled, with the IP address as 192.168.0.1/24 and IP address range for allocation as 192.168.0.0/24 (excluding 192.168.0.1). Configure self-mesh SmartMC for devices to automatically establish a SmartMC network after startup, and use the UWEB management platform provided by devices to manage all network devices.

Figure 19 Network diagram

Procedure

1. Configure Device A:

# Enable the SmartMC feature and specify the device role as TM for the device to enter self-mesh mode.

<DeviceA> system-view

[DeviceA] smartmc enable auto tm

# Lower password complexity requirements, create a local user named admin, set the password to admin, and specify the user role as network-admin.

[DeviceA] password-control length 4

[DeviceA] password-control composition type-number 1 type-length 1

[DeviceA] undo password-control complexity user-name check

[DeviceA] local-user admin

[DeviceA-luser-manage-admin] password simple admin

[DeviceA-luser-manage-admin] authorization-attribute user-role network-admin

[DeviceA-luser-manage-admin] quit

# Enable DNS proxy for users to use domain name quicknet.h3c.com to access the UWEB platform.

[DeviceA] dns proxy enable

# Specify the IP address excluded from address allocation.

[DeviceA] dhcp server forbidden-ip 192.168.0.1

# Create DHCP address pool 1 and specify subnet 192.168.0.0/24 for address allocation to clients.

[DeviceA] dhcp server ip-pool 1

[DeviceA-dhcp-pool-1] network 192.168.0.0 mask 255.255.255.0

[DeviceA-dhcp-pool-1] expired day 10 hour 12

[DeviceA-dhcp-pool-1] quit

# Enable the DHCP service.

[DeviceA] dhcp enable

# Specify the IP address of VLAN-interface 1 as 192.168.0.1 and configure the interface to operate in DHCP server mode.

[DeviceA] interface vlan-interface 1

[DeviceA-Vlan-interface1] ip address 192.168.0.1 24

[DeviceA-Vlan-interface1] dhcp select server

[DeviceA-Vlan-interface1] quit

2. Power on the other switches with the factory default settings. No extra configuration is required.

3. Wait for all the devices to start up, connect a PC to Device A, and visit https://quicknet.h3c.com through a browser to log in to the UWEB management system. Complete deployment configuration as instructed to set up a SmartMC network.

Verifying the configuration

On the system summary page of the UWEB management system, you can view the topology of all member devices and view related information.

11-Network Management and Monitoring Configuration Guide

Configuring non-self-mesh SmartMC (SmartMC 1.0)

Bulk configuration deployment for members

Bulk configuration deployment for ports connecting APs and IP phones

Configuration file backup

Startup software and configuration file upgrade

Faulty member replacement

Outgoing interface for a SmartMC network

Automatic link aggregation

VLAN creation for members

Resource monitoring

QuickNet solution

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Modifying the password of the default user for members

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Procedure

About this task

Restrictions and guidelines

Prerequisites

Procedure

About this task

Prerequisites

Restrictions and guidelines

Procedure

Restrictions and guidelines

Procedure

Upgrading the startup software and configuration file on members

Upgrading the startup software and configuration file in one step

Configuring startup software and configuration file upgrade step by step

Upgrading the startup software and configuration file in one step

Configuring startup software and configuration file upgrade step by step

About this task

Restrictions and guidelines

Procedure

About this task

Procedure

Restrictions and guidelines

Prerequisites

Procedure

Network configuration

Procedure

Verifying the configuration

Configuring self-mesh SmartMC (SmartMC 2.0)

Self-mesh SmartMC splitting

Restrictions and guidelines

Configuring a device to act as the TM

Configuring a device to act as a TC

About this task

Procedure

About this task

Restrictions and guidelines

Procedure

Example: Configuring self-mesh SmartMC with switches acting as TCs (with factory-default SmartMC configuration)

Network configuration

Procedure

Verifying the configuration

Network configuration

Procedure

Verifying the configuration

Network configuration