Contents

Configuring the AON Ethernet system·· 1

About the AON Ethernet system·· 1

AON Ethernet system framework· 1

Benefits· 2

AON node IDs· 2

AON node management methods· 2

Restrictions: Hardware compatibility with AON Ethernet system·· 3

AON Ethernet system tasks at a glance· 3

Prerequisites· 3

Configuring the SmartMC management VLAN· 4

Enabling automatic upgrade for AON nodes· 5

Enabling SmartMC for the AON aggregation· 6

Managing an AON node in AON node view· 7

Configuring a description and a name for an AON node· 7

Configuring VLANs for an AON node· 7

Enabling interface isolation for an AON node· 9

Configuring PoE for an AON node· 9

Performing an internal loopback test for an interface of an AON node· 10

Shutting down interfaces on an AON node· 10

Rebooting an AON node· 11

Managing AON nodes in bulk by using an AON node configuration template· 11

Replacing a faulty AON node· 13

Display and maintenance commands for the AON Ethernet system·· 13

 

Configuring the AON Ethernet system

About the AON Ethernet system

The AON Ethernet system is a network management and maintenance solution based on a distributed deployment architecture. In the system, the AON aggregation (also called iOptic host) manages and maintains AON nodes (also called iOptic nodes), similar to how an AC manages APs in an AC+fit AP network. The AON aggregation functions like an AC, and the AON nodes function like APs. You can perform centralized control and management over campus access network devices by configuring and managing the AON aggregation.

AON Ethernet system framework

Figure 1 shows the basic framework of the AON Ethernet system.

Figure 1 AON Ethernet system framework

 

The AON Ethernet system contains the following types of physical devices:

·     AON aggregation—The AON aggregation, core of the AON Ethernet system, automatically discovers and manages the AON nodes, forwards packets from the AON nodes, and performs centralized O&M on the AON nodes. On the AON aggregation, you can configure the AON nodes and obtain the interface status, interface statistics, PoE power, and transceiver module data of the AON nodes.

·     AON node—An AON node acts as an expansion module of the AON aggregation, connecting to the external network through the AON aggregation. It is lightweight firmware that uses the manufacturer's built-in Microcontroller Unit (MCU) and achieves fast startup (within 10 seconds). Some AON node models support the Comware system, and others do not have an operating system. In the AON Ethernet system, the AON nodes require zero configuration and are plug and play, functioning similarly as hubs.

Benefits

The AON Ethernet system offers the following benefits:

·     Streamlined architecture. The traditional aggregation + access architecture has been transformed into an AON aggregation + AON nodes architecture, where an AON node operates as an expansion module to extend the capacity of the AON aggregation. This streamlined approach not only makes the network simpler but also allows for flexible expansion of the interface capacity for the AON aggregation.

·     Plug-and-play AON nodes, simplifying network planning and deployment, and routine Ops.

AON node IDs

In the AON Ethernet system, an AON node is uniquely identified by its ID. The AON aggregation automatically allocates IDs to AON nodes as follows:

1.     Enabled with SmartMC, the AON aggregation automatically broadcasts a discovery packet to discover AON nodes.

2.     Upon receiving the discovery packets, the AON nodes automatically register with the AON aggregation.

3.     The AON aggregation automatically allocates an ID to each AON node. The ID is bound to the SN and MAC address of an AON node. To view the mappings between AON nodes and their IDs, execute the display smartmc light-unit command on the AON aggregation. After an AON node goes offline, the AON aggregation still reserves the ID for the AON node until you execute the undo smartmc light-unit command to delete the AON node. Then, the device reclaims the ID of the AON node and allocates it to another AON node.

The AON aggregation uses AON node IDs to manage AON nodes. You can use the ID of an AON node to enter AON node view, where you can configure the name, description, interface VLANs, and PoE settings for the AON node.

AON node management methods

Managing a single AON node

When an AON node registers with the AON aggregation, the AON aggregation automatically allocates an ID to that AON node. The AON node is uniquely identified by the ID. The AON aggregation can manage AON nodes. After an AON node goes offline, the AON aggregation still reserves the ID for the AON node until you execute the undo smartmc light-unit command to delete the AON node. You can use the ID to enter AON node view and then configure parameters for the AON node.

Managing AON nodes in bulk

You can use an AON node configuration template to configure multiple AON nodes in bulk.

After you create an AON node configuration template, you can bind it to AON nodes and configure parameters for the AON nodes. When an AON node comes online, the configuration in AON node view, if any, applies. If the AON node does not have any configuration in AON node view and it matches the AON node configuration template, the AON aggregation automatically deploys configuration in AON node configuration template view to the AON node. If the deployment succeeds, the configuration in the template is converted to the configuration in AON node view. If the deployment fails, the configuration in the template is not converted to the configuration in AON node view.

You can bind an AON node configuration template to AON nodes in the following methods:

·     Bind the template to the interface connected to the AON nodes on the AON aggregation. In this method, all AON nodes that come online via the interface can use the configuration in the template.

When the uplink interfaces of an AON node supports aggregation and are connected to the AON aggregation, you must also configure an aggregate interface on the AON aggregation and bind the AON node configuration template to this aggregate interface.

·     Bind the template to the device type of the AON nodes. In this method, all AON nodes of that type can use the configuration in the template when they come online.

·     Bind the template to the serial numbers of the AON nodes. In this method, only AON nodes of the specified serial numbers can use the configuration in the template when they come online. This method allows for both bulk and differentiated configuration.

Restrictions: Hardware compatibility with AON Ethernet system

This feature is not available on the S5130S-EI-G, S5100-D-G, or S5500-D-G switch series.

AON Ethernet system tasks at a glance

To configure the AON Ethernet system, perform the following tasks:

1.     (Optional.) Configuring the SmartMC management VLAN

To modify the SmartMC management VLAN, make sure SmartMC is disabled. If you modify the SmartMC management VLAN when SmartMC is enabled, the modification does not take effect. For the modification to take effect, first disable SmartMC and enable SmartMC again.

2.     (Optional.) Enabling automatic upgrade for AON nodes

3.     Enabling automatic upgrade for AON nodes

4.     (Optional.) Managing an AON node in AON node view

¡     Configuring a description and a name for an AON node

¡     Configuring VLANs for an AON node

¡     Enabling interface isolation for an AON node

¡     Configuring PoE for an AON node

¡     Performing an internal loopback test for an interface of an AON node

¡     Shutting down interfaces on an AON node

¡     Rebooting an AON node

5.     (Optional.) Managing AON nodes in bulk by using an AON node configuration template

Use an AON node configuration template for deployment configuration of AON nodes that come online for the first time. The AON node configuration template does not take effect on an AON node in the following conditions:

¡     The AON node has been online.

¡     Configuration exists in the corresponding AON node view.

6.     (Optional.) Replacing a faulty AON node

Prerequisites

Make sure the IP address of the management VLAN interface on the AON aggregation and the IP addresses of AON nodes reside in the same network segment. The default management VLAN is VLAN 1. The IP addresses can be manually configured or automatically obtained through DHCP. As a best practice, configure the IP addresses to be automatically obtained through DHCP and deploy the DHCP server on the AON aggregation. Configure address pools for VLAN 1 and the management VLAN of the AON Ethernet system on the DHCP server. This makes sure the IP address of the management VLAN on the AON aggregation and the AON node IP addresses reside in the same network segment, allowing for Layer 3 management channel establishment. For information about configuring the DHCP server on the AON aggregation, see DHCP configuration in Layer 3—IP Services Configuration Guide.

Configuring the SmartMC management VLAN

About this task

Application scenarios

Use the SmartMC management VLAN to separate the management packets from other service packets in the AON Ethernet system.

Operating mechanism

An AON Ethernet system is set up as follows:

1.     Enabled with SmartMC, the AON aggregation broadcasts a SmartMC scanning packet in VLAN 1 to discover AON nodes. Upon receiving the scanning packet, an AON node sends a response to register with the AON aggregation.

2.     The AON aggregation and AON node establish a CoAP session within the management VLAN. This CoAP session acts as the Layer 3 management channel between them.

By default, the management VLAN is VLAN 1. In VLAN 1, the AON aggregation and AON node automatically request IP addresses and the AON aggregation actively establishes a CoAP session with the AON node.

3.     If the SmartMC management VLAN is configured, the AON aggregation and AON node work as follows:

a.     The downlink interface on the AON aggregation and the uplink interfaces of the AON node automatically permit management VLAN packets.

b.     If you use the AON aggregation as the DHCP server, you must manually configure the IP address of the management VLAN interface, enable DHCP, and configure address pools on the AON aggregation. If you use another device as the DHCP server, the management VLAN interface of the AON aggregation automatically requests an IP address.

c.     The AON node automatically requests an IP address within the management VLAN.

d.     The AON aggregation and AON node re-establish a COAP session by using the IP addresses obtained within the management VLAN.

4.     The AON aggregation sends a successful registration packet to the AON node and the AON node joins the AON Ethernet system.

The SmartMC management VLAN is dedicated to transmitting protocol packets for the AON Ethernet system management plane. Broadcast packets are restricted within the management VLAN, effectively separating protocol packets on the AON Ethernet system management plane from the service packets and other protocol packets. This facilitates the construction and maintenance of the AON Ethernet and enhances its security.

Restrictions and guidelines

When the device runs as a SmartMC TC, the system automatically deletes the smartmc management-vlan command.

This feature is supported only when the device acts as an AON aggregation. When the device also acts as the TM in a SmartMC network, if you change the SmartMC management VLAN to a VLAN other than VLAN 1, TCs cannot come online.

Procedure

1.     Enter system view.

system-view

2.     Create the management VLAN.

vlan vlan-id

By default, only VLAN 1 exists on the device.

To successfully configure the SmartMC management VLAN, first create the management VLAN.

3.     Return to system view.

quit

4.     Create a management VLAN interface.

interface vlan-interface vlan-id

By default, no VLAN interface exists.

5.     Return to system view.

quit

6.     Configure the SmartMC management VLAN.

smartmc management-vlan vlan-id

By default, the SmartMC management VLAN is VLAN 1.

Enabling automatic upgrade for AON nodes

About this task

Configured with this feature, the AON aggregation automatically identifies whether the software version of an onboarding AON node is compatible with its own. If they are not compatible, the AON node software is automatically upgraded.

Restrictions and guidelines

In a distributed deployment scenario, you must also upload the target AON node version to the AON aggregation.

If you do not enable this feature and the AON node software version is incompatible with that of the AON aggregation, an AON node can still come online and forward packets. To avoid affecting AON node management on the AON aggregation, upgrade the AON node immediately.

Prerequisites

1.     Execute the display version command on the AON aggregation to obtain its running software version.

2.     Obtain the most recent software version of the AON nodes that is compatible with the AON aggregation software version based on the release notes of the AON aggregation.

3.     Upload the startup software package of the AON nodes to the AON aggregation. For the automatic upgrade feature to take effect, make sure the AON aggregation has the startup software package of the AON nodes.

Procedure

1.     Enter system view.

system-view

2.     Enable automatic upgrade for AON nodes.

smartmc auto-upgrade enable

By default, automatic upgrade is disabled for AON nodes.

Enabling SmartMC for the AON aggregation

About this task

An AON aggregation and its connected AON nodes form an AON Ethernet system. The members in the AON Ethernet system discover each other at Layer 2 through SmartMC. In this way, the AON Ethernet system is also a SmartMC network. With this feature configured, the AON aggregation acts as the topology master (TM), and the AON nodes act as topology clients (TCs). Enabled with the AON node mode, an AON node is automatically enabled with SmartMC and operates as a TC. In the AON Ethernet system, you only need to enable the AON node mode on AON nodes and no other settings are required for them. For information about the factory default mode of an AON node, see its product documentation. For more information about SmartMC, see Network Management and Monitoring Configuration Guide.

An AON aggregation supports both the SmartMC and AON Ethernet system features. For information about configuring a pure SmartMC network, see Network Management and Monitoring Configuration Guide. For information about configuring an AON Ethernet, see the configuration guide. Do not deploy both networks on an AON aggregation. An AON aggregation broadcasts scanning packets to discover TCs and determines the network type based on the type of the first TC that responds to the scanning packet.

Restrictions and guidelines

A SmartMC network can have only one AON aggregation.

Changing the AON aggregation to an AON node or disabling SmartMC for the AON aggregation clears the running configuration related to SmartMC.

The SmartMC feature consumes certain ACL resources. If the ACL resources are insufficient, SmartMC will fail to be enabled. To resolve such an issue, perform the following tasks:

1.     Obtain the ACL configuration and running status by using the display acl command.

2.     Delete unnecessary ACLs by using the undo acl command as required.

3.     Enable SmartMC again.

For more information about ACL, see ACL and QoS Configuration Guide.

When you enable SmartMC, the device identifies whether HTTP port 80, HTTPS port 443, and CoAP port 5683 are in use. If any of these ports is occupied, SmartMC will fail to be enabled.

If you execute this command multiple times, the most recent configuration takes effect. You can use the smartmc enable command to enable SmartMC on an AON Ethernet or SmartMC network. The SmartMC network requires a username and password, but the AON Ethernet does not.

Procedure

1.     Enter system view.

system-view

2.     Enable SmartMC for the AON aggregation.

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

By default, SmartMC is disabled for the AON aggregation.

Managing an AON node in AON node view

Configuring a description and a name for an AON node

About this task

In the AON Ethernet system, each AON node is uniquely identified by its ID. However, the AON node ID, a string of digits, is difficult to remember. To resolve such an issue, you can configure a name for each AON node for easier management.

To enter the configuration view of an AON node, configure a name for that AON node and then execute the smartmc light-unit name name command.

The system name of an AON node can contain only 1 to 31 characters. To manage AON nodes efficiently, you can also configure the IDs, geographic locations, and IP addresses as descriptions for them. The AON node description is a string of 1 to 255 characters.

Restrictions and guidelines

Do not configure the name of an AON node as the MAC address of another AON node.

Procedure

1.     Enter system view.

system-view

2.     Enter AON node view.

smartmc light-unit { id | name name }

3.     Configure a name for the AON node.

name sysname

By default, the AON aggregation uses the MAC address of an AON node as its name.

4.     Configure a description for the AON node.

description text

By default, an AON node does not have a description.

Configuring VLANs for an AON node

VLAN modes

An AON node supports the following VLAN modes:

·     Transparent mode—In this mode, the AON node forwards packets based on the destination MAC address no matter whether service packets carry the VLAN tag or their VLAN IDs or not. In transparent mode, you cannot edit the VLAN settings of interfaces on the AON node. To configure VLANs based on MAC addresses or subnets for service packets, perform the configuration on the interface that connects the AON aggregation to the AON node.

·     Manual mode—In transparent mode, an interface operates in hybrid mode and VLANs are configured based on interfaces. After you switch the VLAN mode to manual, the interface uses PVID VLAN 1, which is added to the permitted VLAN list of the interface as an untagged member. To change the PVID of the interface, use the port hybrid pvid command. To assign the interface to specified VLANs, use the port hybrid vlan command.

VLAN configuration guidelines for the uplink interface on an AON node

An AON node uses a physical interface as the uplink interface to connect to an AON aggregation. For AON nodes that have two uplink interfaces, they can aggregate the two interfaces automatically. Support for auto uplink interface aggregation depends on the model and software version of AON nodes. An AON aggregation can automatically identify whether an AON node supports uplink interface aggregation. Use the uplink keyword or port-id-list argument as prompted.

·     For AON nodes that aggregate uplink interfaces automatically, the two uplink interfaces operate as follows:

¡     In versions earlier than a specific version, the two interfaces back up each other, but only one interface is active for packet forwarding at the same time. In this case, the uplink keyword is not supported. Use the port-id-list argument when you configure VLANs for AON nodes.

¡     In a specific version and later versions, the two interfaces back up each other, and can forward traffic at the same time for load balancing. In this case, use the uplink keyword when you configure VLANs for AON nodes. To avoid configuration failures, do not use the port-id-list argument.

-     If you upgrade a device from a version that does not support the uplink keyword to a version that supports the uplink keyword, the port-id-list configuration in the configuration file still takes effect for backward compatibility.

-     If you downgrade a device from a version that supports the uplink keyword to a version that does not support the uplink keyword, and then upgrade the device back to a version that supports the keyword, the configuration file of the device contains both the uplink and port-id-list configurations. In this case, the uplink configuration takes effect.

For information about the version from which an AON node supports uplink interface aggregation, see the documentation for the AON node.

·     For AON nodes that do not support uplink interface aggregation, the two interfaces back up each other, but only one interface is active for packet forwarding at the same time. Use the port-id-list argument when you configure VLANs for AON nodes.

Restrictions and guidelines

In transparent mode, user traffic cannot be isolated based on VLANs on an AON node. To isolate user traffic, configure the interface isolation feature for the AON node or isolate user traffic on the AON aggregation.

Procedure

1.     Enter system view.

system-view

2.     Enter AON node view.

smartmc light-unit { id | name name }

3.     Specify the VLAN mode for the AON node.

vlan mode { manual | transparent }

By default, the VLAN mode for an AON node is transparent.

4.     Set the PVID of hybrid interfaces on the AON node.

port { uplink | port-id-list } * hybrid pvid vlan vlan-id

By default, the interfaces on an AON node do not check VLAN information for packets and transparently transmit all the packets.

5.     Assign hybrid interfaces on the AON node to the specified VLANs.

port { uplink | port-id-list } * hybrid vlan vlan-id-list { tagged | untagged }

By default, the interfaces on an AON node do not check VLAN information for packets and transparently transmit all the packets.

Enabling interface isolation for an AON node

About this task

Application scenarios

This feature prevents the endpoints connected to an AON node from accessing each other at Layer 2 to enhance LAN security.

Operating mechanism

By default, all interfaces on an AON node belong to the same VLAN and the endpoints connected to the interfaces can access each other at Layer 2.

This feature isolates the interfaces on an AON node and enables the endpoints connected to the AON node to forward packets through the AON aggregation. This allows you to manage the traffic of AON nodes on the AON aggregation, which enhances LAN security.

Procedure

1.     Enter system view.

system-view

2.     Enter AON node view.

smartmc light-unit { id | name name }

3.     Enable interface isolation for the AON node.

isolate enable

By default, interface isolation is disabled for an AON node.

Configuring PoE for an AON node

About this task

Enabled with PoE, the PIs on an AON node can provide PoE power for PDs if they support PoE output.

Forced PoE power supply

Before supplying power to a PD, an AON node performs a detection of the PD by default. It supplies power to the PD only after the PD passes the detection. If the PD fails the detection but the power provided by the AON node meets the PD specifications, you can enable forced power supply to the PD.

PoE power supply standards

IEEE released 802.3af (PoE) and 802.3at (PoE+) standards in chronological sequence. The standards are backward compatible but forwards incompatible. Before supplying power to a PD, a PI will detect the PD, determine the power class for the PD based on its power requirement, and supply power to the PD based on the power class.

·     802.3af—Defines four power classes 0 to 3 and provides a maximum power of 12.95 W.

·     802.3at—Adds class 4 in addition to the four power classes defined by 802.3af and provides a maximum power of 25.5 W.

Specify a PoE standard based on the power requirement of the PD. If the maximum power allowed by the standard is less than that required by the PD, the PI will not supply power to the PD.

Restrictions and guidelines

The forced PoE power supply feature enables an AON node to supply power to a PD directly without performing a detection of the PD. To avoid damaging the PD, make sure the power provided by the AON node meets the PD specifications before configuring this feature.

Disabling PoE for PIs on an AON node restores the default settings for the poe force-power and standard commands on the PIs.

Procedure

1.     ‍Enter system view.

system-view

2.     Enter AON node view.

smartmc light-unit { id | name name }

3.     Enable PoE for PIs on the AON node.

poe enable port port-id-list

By default, PoE is enabled for PIs on an AON node.

4.     Specify a PoE standard for PIs on the AON node.

poe standard { af | at } port port-id-list

By default, the IEEE 802.3af standard is used.

5.     Enable forced PoE power supply for PIs on the AON node.

poe force-power port port-id-list

By default, forced PoE power supply is disabled for PIs on an AON node.

6.     Restart PoE on PIs of the AON node.

restart poe port port-id-list

Performing an internal loopback test for an interface of an AON node

About this task

Use this feature to identify whether the interfaces on an AON node can forward packets correctly.

After you configure this feature on an interface of an AON node, the interface returns the packets to be forwarded to the device, allowing the packets to loop through the internal line. Then, you can identify whether the Ethernet forwarding path within the device can operate correctly.

Restrictions and guidelines

If you enable loop guard on an interface of an AON node, you cannot perform an internal loopback test for that interface on the AON aggregation.

Procedure

1.     Enter system view.

system-view

2.     Enter AON node view.

smartmc light-unit { id | name name }

3.     Perform an internal loopback test for an interface of the AON node.

loopback-test internal port port-id

Shutting down interfaces on an AON node

About this task

Some interface settings might require an interface restart before they can take effect.

Restrictions and guidelines

	CAUTION: Executing the shutdown command disconnects the links of the specified interfaces and interrupts communication. Use this command with caution.

 

The AON Ethernet system automatically discovers and records the uplink interfaces of AON nodes. Do not use this command to shut down the uplink interfaces of AON nodes.

Procedure

1.     Enter system view.

system-view

2.     Enter AON node view.

smartmc light-unit { id | name name }

3.     Shut down interfaces on the AON node.

shutdown port port-id-list

By default, the interfaces on an AON node are up.

Rebooting an AON node

About this task

Use this feature to reboot an AON node when it is faulty.

Procedure

1.     Enter system view.

system-view

2.     Enter AON node view.

smartmc light-unit { id | name name }

3.     Reboot the AON node.

Reboot

Managing AON nodes in bulk by using an AON node configuration template

Restrictions and guidelines

Use an AON node configuration template for deployment configuration of AON nodes that come online for the first time. The AON node configuration template does not take effect on an AON node in the following conditions:

·     The AON node has been online.

·     Configuration exists in the corresponding AON node view.

You can repeat the smartmc light-unit bind template command to bind a template to different AON nodes. However, the same serial number, model, or connection interface (the interface connecting to AON nodes on the AON aggregation) can be bound to only one template. An AON node can match configuration templates by its serial number, model, and connection interface. When an AON node matches multiple templates, the following AON node configurations are in descending order: configuration in AON node view, configuration of the template bound to the serial number, configuration of the template bound to the device type, and configuration of the template bound to the connection interface.

Procedure

1.     Enter system view.

system-view

2.     Create an AON node configuration template and enter its view.

smartmc light-unit template template-name

3.     (Optional.) Configure a description for the template.

description text

By default, an AON node configuration template does not have a description.

4.     (Optional.) Configure VLAN parameters.

¡     Specify the VLAN mode for the AON node.

vlan mode { manual | transparent }

By default, the VLAN mode for an AON node is transparent.

¡     Set the PVID of hybrid interfaces on the AON node.

port port-id-list hybrid pvid vlan vlan-id

By default, the interfaces on an AON node do not check VLAN information for packets and transparently transmit all the packets.

¡     Assign hybrid interfaces on the AON node to the specified VLANs.

port port-id-list hybrid vlan vlan-id-list { tagged | untagged }

By default, the interfaces on an AON node do not check VLAN information for packets and transparently transmit all the packets.

5.     (Optional.) Enable interface isolation for the AON node.

isolate enable

By default, interface isolation is disabled for an AON node.

6.     (Optional.) Configure PoE.

¡     Enable PoE for PIs on the AON node.

poe enable port port-id-list

By default, PoE is enabled for PIs on an AON node.

¡     Specify a PoE standard for PIs on the AON node.

poe standard { af | at } port port-id-list

The IEEE 802.3af standard is used.

¡     Enable forced PoE power supply for PIs on the AON node.

poe force-power port port-id-list

By default, forced PoE power supply is disabled for PIs on an AON node.

7.     Return to system view.

quit

8.     Bind the AON node configuration template to AON nodes.

smartmc light-unit bind template template-name { with-interface interface-type interface-number | with-light-unit-type light-unit-type | with-sn sn }

By default, an AON node configuration template is not bound to any AON nodes.

Replacing a faulty AON node

About this task

When an AON node in the AON Ethernet system fails, you can use this feature to replace the faulty AON node.

1.     Connect a new AON node to the AON aggregation. Make sure the new AON node and the faulty AON node are the same model.

2.     The AON aggregation detects that the new AON node comes online. Execute the display smartmc light-unit command to view the ID and status of the new AON node. If the new AON node is in Normal status, the new AON node successfully comes online.

3.     Execute the smartmc replace command.

4.     The AON Ethernet system replaces the ID of the new AON node with that of the faulty AON node, and runs configuration of the faulty AON node on the new one.

Restrictions and guidelines

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

Prerequisites

Connect the new AON node to the AON Ethernet system and execute the display smartmc light-unit command to obtain the ID and status of the new AON node. You can configure this feature only when the new AON node is in Normal status.

Procedure

1.     Enter system view.

system-view

2.     Manually replace a faulty AON node.

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

Display and maintenance commands for the AON Ethernet system

Execute display commands in any view and the reset command in user view.

 

Task	Command
Display AON node information.	display smartmc light-unit [ id | name name ] [ verbose ]
Display the configuration deployed from the AON aggregation to AON nodes and successfully run on the AON nodes.	display smartmc light-unit configuration history
Display information about the PoE power supply status of an AON node.	display smartmc light-unit { id | name name } poe
Display power supply information for PIs on an AON node.	display smartmc light-unit { id | name name } poe port [ port-id ]
Display information about interfaces on an AON node.	display smartmc light-unit { id | name name } port [ port-id | brief | uplink ]
Display key parameters of transceiver modules on an AON node.	display smartmc light-unit { id | name name } transceiver port [ port-id ]
Display upgrade information for an AON node.	display smartmc light-unit { id | name name } upgrade-info
Display AON node configuration template information.	display smartmc light-unit template [ name template-name ]
Clear the configuration deployed from the AON aggregation to AON nodes.	reset smartmc light-unit configuration history