Description

This KB explains the cause of Log message "Failed to report license violation, <Error:libjuniper++ class=8, code=2>" and the ways to fix it.

Symptoms

When a Device is upgraded  Device is upgraded to a release that supports agile licensing while the existing release is legacy license based then the installed license might show as invalid and below logs be seen in syslog messages :-

Apr  5 06:31:56  device authd[7953]: %DAEMON-3-LICENSE_INVALID_INFRA_CALL: Invalid legacy call since nextgen licensing infra is active
Apr  5 06:31:56  device authd[7953]: %DAEMON-3: Failed to report license violation, <Error:libjuniper++ class=8, code=2>

 

Solution

There is a change in licensing infra from 20.3R1 onwards where device expects the license key to be using agile key format instead of the legacy format and hence this error logs are seen.

Below Link can be referred for more details on above :-

https://www.juniper.net/documentation/en_US/junos/information-products/topic-collections/release-notes/20.3/jd0e18951.html



This however does not have any funtional impact and the licenses are still valid and in use and no mitigation is needed .
However to suppress these logs license needs to be installed with agile key.

Below Link can be referred for steps on how to activate Agile license on the device :-

https://www.juniper.net/documentation/us/en/software/license/juniper-licensing-user-guide/topics/topic-map/activate-license.html#:~:text=Log%20in%20to%20the%20Juniper,Click%20the%20Activate.

Modification History

2023/08/30 :- Version 1
2023/09/07 :- Version 2

Related Information

https://prsearch.juniper.net/PR1684842
2023-0405-671089