Table of Contents

Related Documents

17-Quicknet configuration

Title	Size	Download
17-Quicknet configuration	324.21 KB

Configuring Quicknet

About Quicknet

Quicknet is a lightweight network management topology used to centrally manage and maintain dispersed network devices at network edges. In a Quicknet network, only one device acts as the TM and the remaining devices all act as TCs. The TM manages the entire Quicknet network in a unified way.

Benefits

Quicknet provides the following benefits:

· Simplified network setup. Quicknet supports plug-and-play for devices. Once initial settings are configured from the Web interface, devices can automatically form a Quicknet network based on the factory configuration.

· Simplified network maintenance. After the Quicknet network is built, the network administrator can log into the Quicknet management system and, through simple Web operations, can achieve unified management and maintenance of a large number of network devices. This effectively solves operation and maintenance issues for small and medium-sized campus networks.

Quicknet network framework

Figure 1 shows the basic framework of a Quicknet network. The Quicknet network contains the following elements:

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

· Topology client (TC)—Managed by the TM.

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

Figure 1 Quicknet network framework

Quicknet network management

Introduction

Quicknet provides various flexible network device management solutions, allowing you to select any of the following methods as needed:

· Local unified management (mainly used for initial deployment)

Through the Quicknet management system, all network devices can be centrally managed on-site, significantly improving operational efficiency, and is especially suitable for rapid deployment and management of small to medium-sized campus networks.

· Cloudnet remote management (recommended for O&M)

With the Cloudnet management platform, you can remotely manage all devices in the Quicknet network anytime, anywhere.

· Single-device local configuration

¡ Web interface: Access the graphical web page through the device IP to intuitively configure a single device.

¡ CLI: Log in to the device command line interface and use commands for advanced configuration.

Quicknet management system

The Quicknet management system is a lightweight web-based network management platform and acts as the unified management entry for the Quicknet network running on TM. You can visit https://quicknet.h3c.com to access the Quicknet management system on the TM. It is mainly used for the deployment of Quicknet networks. After completing the initial deployment, you can perform simple operations and maintenance on all network devices through the Quicknet management system. To perform in-depth O&M, use the one-key onboarding function provided by the Quicknet management system as a best practice.

The Quicknet management system provides the following functions:

· Initialization—Configures the project name, network-wide password, Internet parameters, Wi-Fi settings, and time zone for the Quicknet network.

· Network Dashboard—Displays network connectivity information, alarm messages, wired network information, wireless service information, topology list, device list, and device details, and provides a portal for users to switch to local management.

· Network Configuration—Includes WAN and wired configuration. WAN settings include network access parameters and wired settings include the service VLAN.

· Device Management—Includes adding devices, removing offline devices, rebooting devices, upgrading devices, resetting devices, viewing device details, configuring device interfaces, creating VLANs, editing VLANs, and deleting VLANs.

· Terminal Management—Allows viewing and management of wired and wireless users.

· System Management—Includes upgrading, rebooting, and modifying the network-wide password.

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

· Management the Quicknet network topology.

· Manage member devices in bulk.

Quicknet network deployment

Quicknet provides an intelligent deployment solution, enabling network deployment in a few simple steps. The specific process is as follows:

1. Auto networking (plug and play)

¡ Networking conditions:

- Devices can reach each other at Layer 2 (allowing VLAN 1 packets to pass).

- Quicknet is enabled (whether Quicknet is enabled by default depends on the device model).

¡ Auto TM election: After the conditions are met, the devices automatically elect the TM and establish a Quicknet network.

2. Device role and information query

¡ After completing physical connections, you can execute the display quicknet configuration command on the TM to verify the TM device role and execute the display quicknet configuration command on a TC to verify the TC device role and view TM information.

¡ The network is not deployed yet. Executing the display quicknet tc command on the TM cannot display TC information.

3. Network deployment methods

¡ Wireless access (recommended)

- Connect to the Wi-Fi whose name includes the Quicknet string.

- Use a browser to visit https://quicknet.h3c.com and perform initial deployment as instructed.

¡ Wired access (login to TM Web interface)

- Connect your PC to the Quicknet network.

- Use a browser to visit https://quicknet.h3c.com and perform initial deployment as instructed.

4. Initial deployment configuration

¡ You can configure the network-wide password, Wi-Fi, and time zone settings.

¡ The configuration will be automatically synchronized to all member devices and take effect.

5. Deployment process on the TM

a. Generates a unique NetID for the current Quicknet network.

b. Requires the logged-in administrator to set a management password (the Quicknet network-wide password) and synchronizes this password along with the NetID to all member devices in the Quicknet network.

Set the devices with the network-wide password and NetID to the deployed state. The state will affect the TM election later.

Quicknet network-wide password

The Quicknet network-wide password is used to ensure the security of the NETCONF communication channel between TM and TC devices.

After Layer 2 connections are established in the Quicknet network, the TM must establish Layer 3 communication channels with TCs to synchronize configurations and obtain device information.

To ensure communication security, the TM and TCs must perform identity authentication (the authentication credentials are the local user admin and the corresponding password). The device comes with default credentials from the factory. The username admin in the default credentials cannot be changed, but the password can be modified. This password is also known as the Quicknet network-wide password.

You can use either method to configure the network-wide password:

1. Modify during initial configuration

Set the network-wide password in the Quicknet management system's deployment wizard.

2. Modify during device operation

¡ Modify from the Quicknet management system's Web interface.

¡ Modify from the TM's CLI.

The network-wide password synchronization mechanism is as follows:

· After the password is changed, the TM automatically synchronizes the new password to all network devices.

· The system will rebuild all communication channels based on the new password.

When you configure the network-wide password, follow these restrictions and guidelines:

· As a best practice for security purposes, change the default password upon initial deployment.

· Change password regularly to comply with corporate security policies.

· The password must contain a minimum of eight characters and contain uppercase and lowercase letters, digits, and special characters.

Quicknet NetID

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

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

The NetID is automatically generated by the Quicknet module at the initial deployment phase.

Figure 2 Multi-Quicknet networking

One-key onboarding

After completing the Quicknet deployment, to manage devices both locally and from the cloud, click the one-key onboarding icon in the top navigation bar of the Quicknet management system to register all network devices to Cloudnet.

After successfully executing one-key onboarding, the administrator can log in to the H3C Cloudnet management platform (https://cloudnet.h3c.com) to implement remote management.

Quicknet role selection

NOTE:

· A Quicknet network can be formed by devices of multiple models. For some devices, you can use the quicknet enable auto tm command to specify the device role as TM. With a TM manually specified, the other devices automatically operate as TCs and the election process is not triggered.

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

· Devices of this series can only act as TCs and do not participate in role election.

For devices that support Quicknet, the role is not determined in the factory settings, and the TM is automatically elected through role election. A Quicknet network conducts role election in the following situations:

· The devices are first interconnected, which triggers Quicknet network formation.

· The TM leaves the network or malfunctions.

· The Quicknet network splits.

· Two (or more) independent Quicknet networks merge into one.

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

1. The device with a higher Quicknet election priority is prioritized.

Each device comes with a priority in factory settings, which is determined by the device model and network location and cannot be modified from the CLI. The Quicknet election priorities of the following devices are in descending order: AC, router, security device, AP. The role of a switch requires manual configuration.

¡ If none of the devices participating in the role election have finished startup deployment, the device with the highest priority becomes the TM.

¡ When a device joins a deployed Quicknet network, if the priority of the new device is higher than the priority of the existing TM, the new device synchronizes configuration and then becomes the TM. If the priority of the new device is the same as or is lower than the priority of the existing TM, the new device joins the network as a TC.

2. Devices that have obtained Quicknet configuration and have been deployed are prioritized.

If two devices have the same priority, the device that has obtained Quicknet configuration and has been deployed becomes the TM.

3. The TM in the larger Quicknet network is prioritized.

When two Quicknet networks merge, the TM in the network with more members become the new TM.

4. Devices that have higher heath scores are prioritized.

5. Devices that have lower bridge MAC addresses are prioritized.

During the election process, the devices broadcast election packets at Layer 2 and follow the above rules until the only TM is selected.

Quicknet network establishment and changing

Quicknet network establishment

The network establishment process is as follows:

1. After a device starts up, it enters the automatic election process with the TC role and broadcasts Quicknet election packets at intervals of 5 seconds. The packet includes the device's bridge MAC, NetID, Quicknet election priority, network size, and the IP address of VLAN-interface 1.

2. After the automatic election, one device is elected as the TM and other devices become TCs.

¡ If the device receives an election packet from a device with better conditions within 20 seconds, it switches to TC. If the local device has better conditions, it becomes the TM.

¡ 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 Quicknet discovery ACK packet back to the TM. At this time, you can use the display quicknet configuration command on the device to view the Quicknet configuration.

5. The network administrator can use one of the following methods to perform initial deployment:

¡ Connect to the TM directly.

¡ Connect to the Wi-Fi whose name includes the Quicknet string.

Visit https://quicknet.h3c.com to log in to the management system. The system will automatically issue the LLDP and NETCONF configuration.

6. The TM obtains detailed information of each TC (including port, LLDP neighbors, and STP status) through a NETCONF session.

7. A TC sends a login request packet (containing device ID information).

8. The TM confirms the information and adds the TC to the network. You can use the display quicknet tc command to view TC information.

9. The TM constructs network topology based on LLDP information, which can be displayed in the management system.

10. The administrator sets the network-wide password and Internet parameters according to the system guide to complete the deployment.

11. The TM synchronizes the password and rebuilds all NETCONF connections.

The Quicknet network has been officially established and can be uniformly operated and maintained through the management system.

New device joining

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

1. After the Quicknet network is established, the TM broadcasts Quicknet 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 the TM or a TC by the factory, it directly joins the Quicknet network as the TM or a TC.

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

Member device leaving

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

· After the TM leaves, TCs will enter the role election state if they fail to receive Quicknet discovery packets from the TM within 20 seconds. TCs then re-elect an TM according to the role election rules.

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

Quicknet splitting

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

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

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

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

As shown in Figure 3, the roles of TM, TC 1, and TC 3 in the Quicknet network are decided through election, and the role of TC 2 is manually specified. Assuming that this Quicknet 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 Quicknet network, but its role remains as TC and its NetID remains as 1.

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

Figure 3 Quicknet splitting

Quicknet merging

The process of multiple stable Quicknet networks interconnecting to form a Quicknet network is called Quicknet merging.

The following rules are followed during the Quicknet merging:

· For Quicknet networks that have already been established, only Quicknet networks with the same NetID can be merged. Quicknet networks with different NetIDs cannot be merged. To make a device with a different NetID join the Quicknet network, restore the device to factory settings or disable and then enable the Quicknet feature on the device, which will delete the NetID.

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

· When merging, the two Quicknet networks will compete for the TM role. For more information about the TM election rules, see "Quicknet role selection."

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

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

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

Figure 4 Quicknet merging

Quicknet configuration synchronization

After member devices use Layer 2 connections to build the Quicknet 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 Quicknet network.

Quicknet supports the following configuration methods:

· Global configuration

Administrators can configure settings on the Quicknet management system'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, Quicknet network-wide password, and FTP server settings.

· Batch configuration

Administrators can configure multiple devices by selecting them on the Quicknet management system'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 Quicknet 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. To log in to a member device, use either of the following methods:

- Use the eWEB or CLI in the Quicknet management system to access the local Web interface or CLI.

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

Quicknet time synchronization (NTP)

After the Quicknet 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."

Quicknet synchronizes time settings across the network as follows:

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

2. The TM acts as an NTP client and synchronizes time settings 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 Quicknet network.

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

Figure 5 Quicknet time synchronization

Quicknet management system login with a fixed domain name

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, Quicknet supports accessing the Quicknet management system 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 Quicknet management system by connecting to any member device and entering the domain name.

Restrictions: Hardware compatibility with Quicknet

Only the S5120V3-EI (with product code LS-5120V3-28P-EI-H1, LS-5120V3-52P-EI-H1, LS-5120V3-28F-EI-H1, or LS-5120V3-52F-EI-H1), S5120V3-LI, and S5000V5-EI series switches support the Quicknet feature.

Switches of this series can only act as TCs and cannot act as the TM.

Restrictions: Software compatibility with Quicknet

Only F6377 and later versions support Quicknet.

Restrictions and guidelines: Quicknet configuration

The device starts up with factory settings. After the administrator completes initial deployment configuration from the Quicknet management system, the device can automatically establish a Quicknet network.

The devices exchange Quicknet protocol packets and establish and maintain the Quicknet 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. By default, VLAN 1 packets are permitted.

Quicknet tasks at a glance

To configure Quicknet, perform the following tasks:

· Enabling Quicknet

Enabling Quicknet

Restrictions and guidelines

One Quicknet network can have only one TM.

If you switch the device role from TM to TC or disable Quicknet, the system clears all the running configuration related to Quicknet on the device.

Quicknet requires specific ACL resources. If ACL resources are insufficient, Quicknet might fail to be enabled. You can use the display acl command to view the ACL configuration and operation status and use the undo acl command to delete useless ACLs based on the actual conditions. After releasing ACL resources, you can try again to enable Quicknet. For more information about ACL, see ACL and QoS Configuration Guide.

When you enable Quicknet, the device checks whether port 80 and port 443 are occupied, as HTTP and HTTPS services require these ports. If port 80 or port 443 is occupied, Quicknet cannot be enabled.

Procedure

1. Enter system view.

system-view

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

quicknet tc enable

By default, Quicknet is disabled and the device role is not specified.

Display and maintenance commands for Quicknet

Execute display commands in any view.

Table 1 Display and maintenance commands for Quicknet

Actions	Command
Display Quicknet configuration.	display quicknet configuration

Quicknet configuration examples

Example: Configuring a wired Quicknet network

Network configuration

As shown in Figure 6, the network contains devices of the following types: router, firewall, core switch, aggregation switch, and access switch. The gateway also acts as the DHCP server to assign an IP address to VLAN-interface 1 of each LAN device. 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 Quicknet for devices to automatically form a network after startup and use the Quicknet management system to perform unified management.

Figure 6 Network diagram

Configuration requirements

In the wired network:

· Use the core switch as the TM and other devices as TCs.

· Use the router, gateway, or a third-party device as the gateway.

· If the firewall acts as the gateway, configure the firewall to operate in routing mode and communicate with the core switch in Layer 2 transparent mode.

· Before the initial deployment, manually specify the core switch as the TM and complete the initial settings.

As a best practice, use one-key onboarding to register devices on Cloudnet after the initial deployment is complete, thus remote O&M can be performed from the Cloudnet platform.

Procedure

1. Power on all the devices with the factory settings. No extra configuration is required. In the factory settings, Quicknet is enabled, a role is specified according to device positioning, and SmartMC-required DHCP settings are configured.

2. Connect the PC to the device.

¡ Connect the PC to the Quicknet network: Use a network cable to connect the PC to a LAN port on any member device to add the PC to VLAN 1.

¡ Configure the IP address of the PC:

As a best practice, use the dynamic obtaining method. Configure the PC to automatically obtain an IP address and the DNS server address. To specify a static IP address, make sure the IP address is on the same subnet as the IP address of VLAN-interface 1 on the connected device.

3. Use the Quicknet management system to perform initial deployment.

Enter quicknet.h3c.com in the address bar of a browser to log in to the Quicknet management system. Complete deployment configuration as instructed to set up a Quicknet network.

NOTE:

Upon the first login to Quicknet, it takes 10 seconds or longer for the system to collect topology information. This time period increases with the number of devices in the network.

Verifying the configuration

Verify that you can view the network topology and information from the management system after the initial deployment is completed.

Example: Configuring a wired and wireless Quicknet network

Network configuration

As shown in Figure 7, the network contains devices of the following types: router, firewall, core switch, aggregation switch, access switch, AC, and AP. The gateway also acts as the DHCP server to assign an IP address to VLAN-interface 1 of each LAN device. The gateway comes with the DHCP server feature enabled, with the IP address as 192.168.0.1/24 and IP address for allocation as 192.168.0.0/24 (excluding 192.168.0.1).

Configure Quicknet for devices to automatically form a network after startup and to achieve unified management.

Figure 7 Network diagram

Configuration requirements

In the wired + wireless network:

· The AC acts as the TM and other Quicknet-capable devices act as TCs.

· Use the router, gateway, or a third-party device as the gateway.

· If the firewall acts as the gateway, configure the firewall to operate in routing mode and communicate with the core switch in Layer 2 transparent mode.

As a best practice, use one-key onboarding to register devices on Cloudnet after the initial deployment is complete, thus remote O&M can be performed from the Cloudnet platform.

Procedure

2. Connect the PC to the device.

¡ Connect your PC to the Quicknet network:

- Wired connection: Use a network cable to connect the PC to a LAN port on any member device to add the PC to VLAN 1.

- Wireless connection: Connect the PC to the Wi-Fi whose name includes the Quicknet string, and specify a static IP address for the PC or configure the PC to obtain an IP address automatically to add the PC to VLAN 1.

¡ Configure the IP address of the PC:

3. Use the Quicknet management system to perform initial deployment.

Enter quicknet.h3c.com in the address bar of a browser to log in to the Quicknet management system. Complete deployment configuration as instructed to set up a Quicknet network.

NOTE:

Upon the first login to Quicknet, it takes 10 seconds or longer for the system to collect topology information. This time period increases with the number of devices in the network.

4. Manage the AP license and software version.

If the AC does not have sufficient license seats, fit APs cannot register on the AC. As a best practice to ensure that the AC has sufficient license seats, click Continue Config after completing the deployment configuration, and go to the AP license management page to install AP licenses. Then, enter the AP software management page and upgrade the AP software as needed.

Verifying the configuration

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

10-Network Management and Monitoring Configuration Guide

Introduction

Quicknet management system

Quicknet network deployment

Quicknet network-wide password

Quicknet NetID

Quicknet network establishment

New device joining

Member device leaving

Quicknet management system login with a fixed domain name

Restrictions and guidelines

Procedure

Network configuration

Configuration requirements

Procedure

Verifying the configuration

Network configuration

Configuration requirements

Procedure

Verifying the configuration

Intelligent Terminal Products

Product Support Services

Technical Service Solutions

Resource Center

Policy

Online Help

Become a Partner

Partner Policy & Program

Global Learning

Partner Sales Resources

Service Business

News & Events

Contact Us