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.

Figure 1 SmartMC network framework

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.

SmartMC network establishment

A SmartMC network can be established automatically or manually. In an automatically established SmartMC network, 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. In a manually established SmartMC network, the commander obtains member's LLDP neighbor information through NETCONF sessions and member's hardware information through SNMP Get operations.

Automatic SmartMC network establishment

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 15-second intervals 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. 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 establishes a connection to the member for tracking the liveliness of the member, 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 SmartMC network is established, the commander and members check for the existence of each other by exchanging SmartMC packets.

· 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, the member returns a response packet to the commander. If the member does not receive a broadcast packet from the commander within 45 seconds, the member determines that the commander does not exist in the network anymore. Then, the member clears the commander information.

· When the commander receives a response packet from a member, it compares the bridge MAC address in the packet with the recorded bridge MAC address. If the two bridge MAC addresses are the same, the commander determines that the member still exists in the network. If the commander does not receive a response packet from a member within 150 seconds, the commander determines that the member is offline. Then, the commander sets the status of the member to offline.

Manual SmartMC network establishment

You can log in to the Web interface of the commander, and enter the IP address, username, and password of the members to manually add them to the network. The members can join the network without exchanging SmartMC packets with the commander. For more information, see the online help for the Web interface.

After the members join the SmartMC network, the commander obtains the following information from the members to form a SmartMC topology:

· LLDP neighbor information (through NETCONF).

· Hardware information (through SNMP Get operations).

SmartMC features

Bulk configuration deployment

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 Telnet connections. 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.

Batch files for ports connecting APs and IP phones

You can specify a batch file to deploy to ports connecting APs or IP phones. When the commander detects that an AP or IP phone comes online on a port, it obtains the access device type through LLDP and deploys the command lines in the specified file to the port.

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 commander does not deploy new configurations. The port uses the configurations deployed last time.

· If the new device is an AP or IP phone but has a different type as the disconnected device, the commander deploys new configurations to the port based on the device type.

· If the new device is neither an AP nor an IP phone, the commander restores the default settings on the port.

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 specified members or SmartMC groups.

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

Startup software and configuration file upgrade

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

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 FTP server.

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

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

? Startup software upgrade—The members act as NETCONF clients, establish NETCONF sessions to themselves, and perform ISSU with the upgrade startup software files.

? Configuration file upgrade—The members act as Telnet clients, establish Telnet connections to themselves, and run the upgrade configuration file.

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 a 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 FTP 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 FTP server and run the file to complete the replacement.

Automatic Ethernet link aggregation

Automatic Ethernet 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. For more information, see Ethernet link aggregation in Layer 2—LAN Switching Configuration Guide.

NOTE:

· Automatic Ethernet link aggregation is not performed between the commander and a member.

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

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 resource usage of commanders and members on the commander, such as CPU usage, memory usage, and temperature information.

Restrictions and guidelines: SmartMC configuration

SmartMC is supported only on the default MDC.

A SmartMC network is established in VLAN 1. For the network to work correctly, do not configure security settings in VLAN 1.

If a member is a PEX in an IRF 3 system, all the member's ports except for the port connecting the parent fabric will be shut down after the member starts up with empty configuration. The member cannot communicate with the commander or join the SmartMC network. For more information about PEXs, see IRF in Virtual Technologies Configuration Guide.

SmartMC tasks at a glance

To configure SmartMC, perform the following tasks:

1. Enabling SmartMC

Enable SmartMC on both the commander and members and perform all subsequent tasks only on the commander.

2. Setting the FTP server information

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 for SmartMC groups and performing bulk configuration deployment to SmartMC groups.

7. (Optional.) Deploying and managing configurations

? 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 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.

? Specify the Telnet, 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 LLDP globally. For information about LLDP, see Layer 2—LAN Switching Configuration Guide.

· To manage the commander and members through a Web interface, you must enable the HTTP and HTTPS services, and set the service type to HTTP and HTTPS for the local user. For information about Web login, HTTP, and HTTPS, see login management configuration in Fundamentals Configuration Guide.

· To manually establish a SmartMC network, you must configure the snmp-agent community read public and snmp-agent sys-info version all commands on the members. For information about SNMP, see Network Management and Monitoring Configuration Guide.

Enabling SmartMC

Restrictions and guidelines

A SmartMC network must have one and only one commander.

Perform this task on both the commander and members and perform all subsequent tasks only on the 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.

You must specify the username and password for the commander.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enable SmartMC and set the device role.	smartmc { tc \| tm username username password { cipher \| simple } string } enable	By default, SmartMC is disabled.

Setting the FTP server information

About files stored on the FTP server

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.

Restrictions and guidelines

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

· Specify the IP address of an FTP server.

· Specify the IP address of the commander. The commander will act as an FTP server.

To configure the commander to act as an FTP server, make sure the commander has enough storage space for storing the files required by members. For information about FTP, see Fundamentals Configuration Guide.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Set the FTP server information.	smartmc ftp-server server-address username username password { cipher \| simple } string	By default, no FTP server information is set.

Configuring an outgoing interface for the SmartMC network

About outgoing interfaces for the SmartMC network

An outgoing interface is an interface used for communication between the SmartMC network and an outside network. You can configure multiple outgoing interfaces for the SmartMC network to communicate with outside networks.

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.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter interface view.	interface interface-type interface-number	N/A
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

Step	Command	Remarks
1. Enter system view.	system-view	N/A
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 modifying the password of the default user for members

During SmartMC network establishment, the commander establishes NETCONF sessions to members and adds them 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 that is used to add the members.

Procedure

Step	Command
1. Enter system view.	system-view
2. Modify the password of the default user for members.	smartmc tc password string

Creating a SmartMC group

About SmartMC groups

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

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Create a SmartMC group and enter its view.	smartmc group group-name	N/A
3. (Optional.) Display predefined device types.	match device-type ?	If the device type of the members is not predefined on the commander, you must manually add the device type to the commander. This enables members of an undefined type to join a SmartMC group created on the commander.
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. Return to system view.	quit	N/A
6. (Optional.) Add a device type to the commander.	smartmc tc sysoid sysoid device-type device-type	To obtain the SYSOID of a member, execute the display smartmc tc verbose command. The device type added to the commander cannot be the same as any predefined type on the commander.

Creating a VLAN for members

Step	Command
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

Step	Command	Remarks
1. Execute the command in user view to create a batch file and edit the command lines to be deployed to members.	create batch-file cmd-filename	Execute this command in user view. 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	N/A
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 }	N/A

Configuring a batch file for ports connecting APs or 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 or rename the file.

Procedure

Step	Command	Remarks
1. (Optional.) Execute the command in user view to create a batch file and edit the command lines to be deployed to ports.	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	N/A
3. Specify the batch file for ports connecting APs or IP phones.	smartmc batch-file batch-file-name apply { ap \| phone }	N/A

Backing up configuration files

About backing up configuration files

Configuration files backed up to the FTP server by automatic configuration file backup 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 FTP 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.

Prerequisites

Before performing this task, you must set the FTP server information (see "Setting the FTP server information").

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
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 configuration file backup at the same time.
3. Back up configuration files.	· Enable automatic configuration file backup and set the backup interval: smartmc backup startup-configuration interval interval-time · Manually back up the configuration file on members: smartmc backup configuration { group group-name-list \| tc [ tc-id-list ] }	By default, automatic configuration file backup is disabled.

Configuring resource monitoring

Step	Command	Remarks
1. Enter system view.	system-view	N/A
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 \| 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

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

Prerequisites

Before performing this task, you must set the FTP server information (see "Setting the FTP server information").

Upgrading the startup software and configuration file on members

Upgrading the startup software and configuration file in one step

Step	Command
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 ]
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 ]

Configuring startup software and configuration file upgrade step by step

Step	Command
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
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

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

Upgrading the startup software and configuration file in one step

Step	Command
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 ]
3. Upgrade the configuration file on all members in SmartMC groups in one step.	smartmc upgrade startup-configuration group { group-name-list cfg-filename }&<1-40> [ delay minutes \| time in-time ]

Configuring startup software and configuration file upgrade step by step

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Enter SmartMC group view.	smartmc group group-name	N/A
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	N/A
6. Upgrade the startup software and configuration file on all members in the SmartMC group.	· Upgrade the startup software: smartmc upgrade boot-loader group group-name-list [ delay minutes \| time in-time ] · Upgrade the configuration file: smartmc upgrade startup-configuration group group-name-list [ delay minutes \| time in-time ]	N/A

Managing the network topology

Refreshing the network topology

About refreshing the network topology

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.

Procedure

To manually refresh the network topology, execute the smartmc topology-refresh command in any view.

To configure automatic network topology refresh:

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. 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 saving the network topology

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

Step	Command
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, device model, and IRF member ID.

Prerequisites

Before you replace a faulty member, perform the following tasks:

1. Set the FTP server information (see "Setting the FTP server information").

2. Install the new member at the location where the faulty member was installed.

3. Connect all cables to the new member.

Procedure

Step	Command	Remarks
1. Enter system view.	system-view	N/A
2. Replace faulty members.	· Enable automatic faulty member replacement: smartmc auto-replace enable · Manually replace a faulty member: smartmc replace tc tc-id1 faulty-tc tc-id2	By default, automatic faulty member replacement is disabled.

Step

Command

Remarks

1. Enter system view.

system-view

N/A

2. Replace faulty members.

· Enable automatic faulty member replacement:
smartmc auto-replace enable

· Manually replace a faulty member:
smartmc replace tc tc-id1 faulty-tc tc-id2

By default, automatic faulty member replacement is disabled.

Display and maintenance commands for SmartMC

Execute display commands in any view.

Task	Command
Display the configuration file backup status for 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 2, member 1, member 2, and member 3 belong to the same device type: S10500X series. The IP address of the FTP server is 192.168.2.1. The FTP username is admin and the FTP password is admin.

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. Create a SmartMC group and add the members to the group.

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

Figure 2 Network diagram

Procedure

1. Configure member 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 the Telnet service on member 1.

[TC1] telnet server enable

# Enable NETCONF over SOAP over HTTP.

[TC1] netconf soap http enable

Enable LLDP globally.

[TC1] lldp global enable

# Create a local user, and specify the username, password, service types, and RBAC role as admin, admin, Telnet, HTTP, and HTTPS, and network-admin, respectively.

[TC1] local-user admin

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

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

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

[TC1-luser-manage-admin] quit

# 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 member.

[TC1] smartmc tc enable

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

3. Configure the commander:

# Configure VLAN-interface 1.

<TM> system-view

[TM] interface vlan-interface 1

[TM-Vlan-interface1] ip address 192.168.2.2 24

[TM-Vlan-interface1] quit

# Enable the Telnet service.

[TM] telnet server enable

# Enable NETCONF over SOAP over HTTP.

[TM] netconf soap http enable

# Enable LLDP globally.

[TM] lldp global enable

# Create a local user, and specify the username, password, service types, and RBAC role as admin, admin, Telnet, HTTP, and HTTPS, and network-admin, respectively.

[TM] local-user admin

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

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

[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 both the username and password (plaintext) to admin.

[TM] smartmc tm username admin password simple admin enable

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

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

# Create SmartMC group S1 and enter its view.

[TM] smartmc group S1

# Create a device type match criterion to add all members to SmartMC group S1.

[TM-smartmc-group-S1] match device-type S10508X-V

# 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 startup.cfg

Verifying the configuration

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

[TM] display smartmc tc

TCID DeviceType IpAddress MacAddress Status Version Sysname

1 S10508X-V 192.168.2.3 201c-e7c3-0300 Normal R7568 S1

2 S10508X-V 192.168.2.4 201c-e7c3-0301 Normal R7568 S2

3 S10508X-V 192.168.2.5 201c-e7c3-0302 Normal R7568 S3

# 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

12-Network Management and Monitoring Configuration Guide

Configuring SmartMC

Automatic SmartMC network establishment

Manual SmartMC network establishment

Bulk configuration deployment

Batch files for ports connecting APs and IP phones

Configuration file backup

Startup software and configuration file upgrade

Faulty member replacement

Automatic Ethernet link aggregation

VLAN creation for members

Resource monitoring

Restrictions and guidelines

Procedure

About files stored on the FTP server

Restrictions and guidelines

Procedure

About outgoing interfaces for the SmartMC network

Restrictions and guidelines

Procedure

Modifying the password of the default user for members

About modifying the password of the default user for members

Restrictions and guidelines

Procedure

About SmartMC groups

Procedure

Restrictions and guidelines

Procedure

About backing up configuration files

Restrictions and guidelines

Prerequisites

Procedure

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 refreshing the network topology

Restrictions and guidelines

Procedure

About saving the network topology

Procedure

Restrictions and guidelines

Prerequisites

Procedure

Network configuration

Procedure

Verifying the configuration

Cloud & AI

InterConnect

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Resources

Partner Business Management

Company Information

News & Events

Contact Us