Terminal Identification and Policy Automation Design
Overview
On large- and medium-sized campus networks, access terminals include smart terminals (such as PCs and mobile phones) and dumb terminals (such as IP phones, printers, and IP cameras). Currently, terminal management on campus networks faces the following challenges:
- The network management system (NMS) can only display the IP and MAC addresses of access terminals, but cannot identify what the specific terminal is. As a result, the NMS cannot manage network terminals in a refined manner.
- Network service configurations and policies required vary according to different types of terminals. Consequently, the administrator needs to manually configure different service configurations and policies for each type of service terminals, resulting in complex service deployment and operations.
To tackle the preceding challenges, Huawei offers the terminal identification and automatic policy delivery solution, which supports the following functions:
- iMaster NCE-Campus can display the type, system, and other information of network-wide terminals, for example, dumb terminals including printers, IP cameras, e-cards, and access control devices, as well as collect statistics and display traffic by terminal type.
- The administrator does not need to manually configure different services and policies for each type of dumb terminals such as IP phones, printers, and IP cameras on the campus network. iMaster NCE-Campus is able to auto-identify terminals and deliver corresponding admission policies and service configurations to them.
To deploy the terminal identification and automatic policy delivery solution, the network administrator needs to design terminal identification methods and terminal policies.
Terminal Identification Overview
The terminal management function of iMaster NCE-Campus can help identify terminals and display the terminal type, operating system, and manufacturer.
The following table describes terminal identification methods.
Category |
Identification Method |
Description |
Applicable Scenario |
---|---|---|---|
Passive fingerprint-based identification |
MAC OUI |
The first three bytes of a MAC address indicate the ID number of the manufacturer. This method is inaccurate in most cases. |
Identify the device manufacturer only |
HTTP UserAgent |
A browser's User-Agent string contains the manufacturer, terminal type, operating system, browser type, and other information. |
Identify the following device types: Mobile phone, tablet, PC, workstation, and intelligent audio/video terminal |
|
DHCP Option |
Some options of a terminal's DHCP packets can be used to classify terminals, including common DHCP options 55, 60, and 12. |
Identify the following device types: Mobile phone, tablet, PC, workstation, IP camera, IP phone, and printer |
|
LLDP |
LLDP packets carry device model information. |
Identify the following device types: IP phone, IP camera, and network device |
|
mDNS |
mDNS packets contain terminal model and service information. |
Identify the following device types: Apple device, printer, and IP camera |
|
Active scanning and identification |
SNMP Query |
This method obtains identification information by querying device information-related objects among SNMP MIB objects. |
Identify the following device types: Network device and printer |
NMAP |
Nmap is used to scan the OS and services of terminals to detect the terminal model and OS information. |
Identify the following device types: PC, workstation, printer, phone, and IP camera |
Passive fingerprint-based identification: Network devices collect fingerprints of terminal packets and report the fingerprints to the SDN controller for terminal type identification.
Active scanning and identification: The SDN controller actively detects or scans terminals, and identifies terminal types based on feedback information from the terminals.
When terminals access the network, iMaster NCE-Campus can automatically identify the type, operating system, and manufacturer of the terminals, either by actively scanning terminal information or by using the information collected and reported by network devices.
Terminal Identification Method Design
To display terminal types and perform network management based on the terminal types through iMaster NCE-Campus, the network administrator needs to perform the following operations:
- Collect the types of terminals on the network, such as PCs, mobile phones, printers, IP cameras, and access control devices.
- Check whether Portal authentication is deployed on the network.
- Check whether the IP addresses of the terminals are dynamically assigned by the DHCP server or statically assigned.
Based on the collected information, traverse the items listed in the following table and select the required terminal identification methods. All the identification methods that meet requirements must be enabled.
Identification Method |
Identifiable Terminal Type |
Application Scenario |
---|---|---|
MAC OUI |
All IP terminals (identifying only the device manufacturer) |
Common scenarios (authentication, non-authentication, and dynamic/static IP address assignment scenarios) |
HTTP UserAgent |
Mobile phone, tablet, PC, workstation Intelligent audio/video terminal |
Portal authentication scenarios |
DHCP Option |
Mobile phone, tablet, PC, workstation IP camera, IP phone, printer |
Dynamic IP address assignment scenarios |
LLDP |
IP phone, IP camera, network device |
Common scenarios |
mDNS |
Apple device, printer, IP camera |
Common scenarios |
SNMP Query |
Network device, printer |
On-premises scenarios |
Nmap |
PC, workstation Printer, phone, IP camera |
On-premises scenarios |
Determine the terminal identification methods that need to be enabled on iMaster NCE-Campus based on the preceding information. If the network administrator cannot determine the required terminal identification methods, the following methods for passive fingerprint-based identification are recommended: MAC OUI, HTTP UserAgent, DHCP Option, LLDP, and mDNS.
It is recommended that Nmap be disabled by default because its identification period is long. If the preceding methods for passive fingerprint-based identification cannot meet requirements, enable Nmap.
The network administrator can enable terminal identification and its dependent functions on corresponding devices through iMaster NCE-Campus. Refer to the following table for more information.
Identification Method |
Enabled On |
Function to Be Enabled at the Same Time |
---|---|---|
MAC OUI |
Access switch and AP |
- |
HTTP UserAgent |
Portal authentication device |
- |
DHCP Option |
Access switch and AP |
DHCP snooping needs to be enabled on access switches. By default, DHCP snooping is enabled on APs. |
LLDP |
Access switch and AP |
- |
mDNS |
Access switch and AP |
mDNS snooping needs to be enabled on access switches and APs. |
SNMP Query |
Controller |
- |
Nmap |
Controller |
- |
- In non-authentication scenarios, the controller can display information about wired terminals only after the ARP snooping function is enabled on access devices.
- In the deployment scenario where iMaster NCE-Campus communicates with access devices through a NAT device, the terminal identification methods SNMP Query and Nmap are not supported.
- When deploying the terminal identification methods SNMP Query and Nmap, ensure that iMaster NCE-Campus can communicate with terminals.
Terminal Policy Design
The network administrator can use iMaster NCE-Campus to automatically deliver policies to terminals, without the need to manually configure different services and policies for each type of service terminals. Terminal policies can be delivered based on the terminal type, operating system, or manufacturer.
The administrator needs to perform the following operations:
- Enable automatic policy delivery based on terminal types to authorize policies depending on access authentication. Access authentication must be deployed on access switches and APs. For details about how to select an access authentication mode, see Authentication Technology Selection. MAC address authentication needs to be enabled on access switches and APs in scenarios where dumb terminals are present.
- Enable the terminal identification function for the network. For details, see the preceding section.
- Sort out the types of terminals that require automatic policy delivery on the network, design corresponding authorization policies, and configure the policies on iMaster NCE-Campus.
For details about the policy design logic, refer to the following table.
Condition |
Admission Policy |
Authorization Policy |
---|---|---|
Operating system: Android |
User admission |
Authorize ACL 1 |
Operating system: iOS |
User admission |
Authorize ACL 2 |
Terminal type: printer |
Automatic admission |
Authorize VLAN 10 |
Terminal type: IP camera |
Automatic admission |
Authorize VLAN 20 |
Terminal type: IP phone |
Automatic admission |
Authorize VLAN 30; DSCP 48 |
Terminal type: access control device |
Automatic admission |
Authorize VLAN 40 |
Manufacturer: ABC |
User admission |
Authorize ACL 100 |
It is recommended that admission and authorization policies be automatically delivered to dumb terminals (such as printers, IP phones, and IP cameras) based on terminal types. This helps implement automatic service provisioning and plug-and-play for dumb terminals.
Figure 3-19 illustrates the process of automatic policy delivery based on terminal types.
On the iMaster NCE-Campus web UI, the administrator enables the terminal identification function, selects terminal types, and specifies corresponding policies. When a terminal accesses the network, the network device can collect the fingerprint information of the terminal and report the information to iMaster NCE-Campus. Then iMaster NCE-Campus automatically matches the information against the terminal fingerprint database, identifies the terminal type, and delivers the corresponding admission and authorization policies to the terminal based on the policies defined by the administrator.
When terminal identification is used together with the VLAN authorization policy, you can disable pre-connection in 802.1X and MAC address authentication scenarios to prevent IP address re-assignment.