Experience case for troubleshooting incorrect direct device information displayed in ADCampus solution access details

The fault phenomenon is that the direct device displays incorrectly or is empty, and the device name, device interface, etc. display abnormally.

The access location information displayed in the access details can be used to match the access scenario and display the terminal's access location.

Overview: In the ADCampus solution, VLAN planning is performed for the access interface, and the link relationship between leaf and access is pushed to the EIA side. After terminal access authentication, the authentication packet carries the corresponding VLAN and leaf downlink port information, and the terminal's access location information is obtained by querying the link relationship database.

If a fault occurs here, troubleshoot it as follows:

1. Acknowledge the downlink port of the leaf device at the terminal authentication point and the access device

You can check the details of the access device on the controller (CTL), which displays the downlink port of the corresponding leaf device. If this is incorrect, it is recommended to troubleshoot the LLDP between the leaf and access devices and verify whether the devices are properly activated.

2. Check the access interface configuration. The controller (CTL)-managed access is per-interface per-VLAN. For the access and cascading access on the same leaf downlink port, VLAN allocation starts from VLAN101. If multiple cascading access interfaces share the same VLAN, it will affect the display of terminal authentication locations. Modifying the VLAN configuration issued by the controller (CTL) is not recommended.

3. Check the access controller (CTL) data synchronization status. If manual configuration changes cause discrepancies, it is recommended to align with the controller (CTL) for smooth operation

4. Check whether the VLAN planning in the access controller (AC) is normal. Click the configure interface VLAN button to check if any interface PVID shows --. If so, troubleshoot the configuration of the -- interface and verify whether this interface is connected to an H3C device not managed by the controller (CTL). If connected to an H3C device, disable LLDP on this interface by executing undo lldp enable.

5. In network parameters, audit AAA to check for inconsistencies between the controller (CTL) and AAA data. There may be cases where the controller (CTL) has not pushed link information to EIA.

click audit to check for discrepancies

6 open EIA-DM debug level logs reconnect terminals without displayed location information and check the logs to view specific information carried in the authentication messages confirm terminal access location through access vlan id101 and nas port ten2/0/10

7 query the EIA database to view corresponding link information

Troubleshoot according to the above method

Related cases

 What does direct device mean in the ADcampus EIA online table? - Zhiliao Community

A case study on incorrect display of direct devices for online users at a specific site - Zhiliao Community