Limitations for Wired Clients Monitoring

Listed below are the limitations of wired client monitoring in HPE Aruba Networking Central:

• Clients with static IP configuration—Static IP or static binding clients will enter L3 timeout state, as DHCP process will not be triggered for them.

• L2 and L3 stage timeout values are configured as 3 minutes and 2 minutes. These values cannot be modified.

• For MAC authenticated clients, with concurrent onboarding or authentication priority, there is a delay in initiating the onboarding event. This is because authentication precedence and priority status is published only after the 802.1X authentication process is complete.

• If the client onboarding is successful after the onboarding timeout, no new event is generated. To check the current onboarding status, HPE Aruba Networking Central must monitor the events from appropriate features (port access, DHCP snooping). The same is applicable for clients where the onboarding fails.

• Old L3 latency values are published when the port to which clients are connected flaps, as the client will not trigger DHCP process after L2 authentication on rejoin.

• ND-snooping binding clients will enter L3 timeout state, as DHCP process will not be triggered for them.

• UBT clients will not be monitored.

• Clients that are onboarded on the LAG interfaces will not be monitored.