Contents

Configuring the iOptic system·· 1

About the iOptic system·· 1

iOptic system framework· 1

Benefits· 2

Restrictions: Hardware compatibility with iOptic system·· 2

iOptic system tasks at a glance· 2

Configuring the SmartMC management VLAN· 2

Enabling automatic upgrade for iOptic nodes· 3

Enabling SmartMC for the iOptic host 4

Managing iOptic nodes· 5

Configuring a description and a name for an iOptic node· 5

Configuring VLANs for an iOptic node· 5

Enabling interface isolation for an iOptic node· 7

Configuring PoE for an iOptic node· 7

Performing an internal loopback test for an interface of an iOptic node· 8

Shutting down interfaces on an iOptic node· 8

Rebooting an iOptic node· 9

Display and maintenance commands for the iOptic system·· 9

 

Configuring the iOptic system

About the iOptic system

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

iOptic system framework

Figure 1 shows the basic framework of the iOptic system.

Figure 1 iOptic system framework

 

The iOptic system contains the following types of physical devices:

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

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

Benefits

The iOptic system offers the following benefits:

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

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

Restrictions: Hardware compatibility with iOptic system

The iOptic host in the iOptic system must be a device on which all interfaces are optical interfaces.

iOptic system tasks at a glance

To configure the iOptic system, perform the following tasks:

1.     (Optional.) Configuring the SmartMC management VLAN

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

3.     Enabling SmartMC for the iOptic host

4.     (Optional.) Managing iOptic nodes

¡     Configuring a description and a name for an iOptic node

¡     Configuring VLANs for an iOptic node

¡     Enabling interface isolation for an iOptic node

¡     Configuring PoE for an iOptic node

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

¡     Shutting down interfaces on an iOptic node

¡     Rebooting an iOptic node

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 iOptic system.

Operating mechanism

An iOptic system is set up as follows:

1.     Enabled with SmartMC, the iOptic host broadcasts a SmartMC scanning packet to discover iOptic nodes. Upon receiving the scanning packet, an iOptic node sends a response to register with the iOptic host.

2.     If the SmartMC management VLAN is configured, the iOptic host establishes the CoAP session with the iOptic node in the SmartMC management VLAN.

3.     By default, the iOptic host actively establishes a CoAP session (management channel) with the iOptic node in VLAN 1.

4.     The iOptic host sends a successful registration packet to the iOptic node and the iOptic node joins the iOptic system.

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

Restrictions and guidelines

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

Procedure

1.     Enter system view.

system-view

2.     Configure the SmartMC management VLAN.

smartmc management-vlan vlan-id

By default, the SmartMC management VLAN is VLAN 1.

Enabling automatic upgrade for iOptic nodes

About this task

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

Restrictions and guidelines

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

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

Prerequisites

1.     Execute the display version command on the iOptic host to obtain its running software version.

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

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

Procedure

1.     Enter system view.

system-view

2.     Enable automatic upgrade for iOptic nodes.

smartmc auto-upgrade enable

By default, automatic upgrade is disabled for iOptic nodes.

Enabling SmartMC for the iOptic host

About this task

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

An iOptic host supports both the SmartMC and iOptic system features. For information about configuring a pure SmartMC network, see Network Management and Monitoring Configuration Guide. For information about configuring an iOptic network, see the configuration guide. Do not deploy both networks on an iOptic host. An iOptic host 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 iOptic host.

Changing the iOptic host to an iOptic node or disabling SmartMC for the iOptic host 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 iOptic or SmartMC network. The SmartMC network requires a username and password, but the iOptic network does not.

Procedure

1.     Enter system view.

system-view

2.     Enable SmartMC for the iOptic host.

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

By default, SmartMC is disabled for the iOptic host.

Managing iOptic nodes

Configuring a description and a name for an iOptic node

About this task

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

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

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

Restrictions and guidelines

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

Procedure

1.     Enter system view.

system-view

2.     Enter iOptic node view.

smartmc light-unit { id | name name }

3.     Configure a name for the iOptic node.

name sysname

By default, the iOptic host uses the MAC address of an iOptic node as its name.

4.     Configure a description for the iOptic node.

description text

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

Configuring VLANs for an iOptic node

VLAN modes

An iOptic node supports the following VLAN modes:

·     Transparent mode—In this mode, the iOptic 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 iOptic node. To configure VLANs based on MAC addresses or subnets for service packets, perform the configuration on the interface that connects the iOptic host to the iOptic node.

·     Manual mode—In this 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 iOptic node

An iOptic node uses a physical interface as the uplink interface to connect to an iOptic host. For iOptic 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 iOptic nodes. An iOptic host can automatically identify whether an iOptic node supports uplink interface aggregation. Use the uplink keyword or port-id-list argument as prompted.

·     For iOptic 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 iOptic 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 iOptic 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 iOptic node supports uplink interface aggregation, see the documentation for the iOptic node.

·     For iOptic 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 iOptic nodes.

Restrictions and guidelines

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

Procedure

1.     Enter system view.

system-view

2.     Enter iOptic node view.

smartmc light-unit { id | name name }

3.     Specify the VLAN mode for the iOptic node.

vlan mode { manual | transparent }

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

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

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

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

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

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

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

Enabling interface isolation for an iOptic node

About this task

Application scenarios

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

Operating mechanism

By default, all interfaces on an iOptic 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 iOptic node and enables the endpoints connected to the iOptic node to forward packets through the iOptic host. This allows you to manage the traffic of iOptic nodes on the iOptic host, which enhances LAN security.

Procedure

1.     Enter system view.

system-view

2.     Enter iOptic node view.

smartmc light-unit { id | name name }

3.     Enable interface isolation for the iOptic node.

isolate enable

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

Configuring PoE for an iOptic node

About this task

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

Forced PoE power supply

Before supplying power to a PD, an iOptic 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 iOptic 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 iOptic 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 iOptic node meets the PD specifications before configuring this feature.

Procedure

1.     Enter system view.

system-view

2.     Enter iOptic node view.

smartmc light-unit { id | name name }

3.     Enable PoE for PIs on the iOptic node.

poe enable port port-id-list

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

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

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

By default, the IEEE 802.3at standard is used.

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

poe force-power port port-id-list

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

6.     Restart PoE on PIs of the iOptic node.

restart poe port port-id-list

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

About this task

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

After you configure this feature on an interface of an iOptic 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.

Procedure

1.     Enter system view.

system-view

2.     Enter iOptic node view.

smartmc light-unit { id | name name }

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

loopback-test internal port port-id

Shutting down interfaces on an iOptic 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 iOptic system automatically discovers and records the uplink interfaces of iOptic nodes. Do not use this command to shut down the uplink interfaces of iOptic nodes.

Procedure

1.     Enter system view.

system-view

2.     Enter iOptic node view.

smartmc light-unit { id | name name }

3.     Shut down interfaces on the iOptic node.

shutdown port port-id-list

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

Rebooting an iOptic node

About this task

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

Procedure

1.     Enter system view.

system-view

2.     Enter iOptic node view.

smartmc light-unit { id | name name }

3.     Reboot the iOptic node.

reboot

Display and maintenance commands for the iOptic system

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

 

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