Upon login, message displays that the license is invalid. But when viewing licenses, a valid license exists with expiration of 2025:
Last login: Tue Feb 27 09:18:19 2024 from 10.0.133.66
--- JUNOS 21.4R3-S4.9 Kernel 64-bit JNPR-12.1-20230515.19b0750_buil
Virtual Appliance License is invalid <----- Error message
root@vSRX01> show system license
License usage:
Licenses Licenses Licenses Expiry
Feature name used installed needed
idp-sig 0 1 0 expired
appid-sig 0 1 0 expired
Virtual Appliance 1 1 1 expired
remote-access-ipsec-vpn-client 0 2 0 permanent
remote-access-juniper-std 0 2 0 permanent
VCPU Scale 4 0 4 invalid
Licenses installed:
License identifier: JUNOS123456789
License version: 4
Order Type: commercial
Software Serial Number: 12345678000-aBCd
Customer ID: ABC DEFG
Features:
idp-sig - IDP Signature
date-based, 2020-01-07 19:00:00 EST - 2023-02-06 19:00:00 EST
appid-sig - APPID Signature
Virtual Appliance - Virtual Appliance
date-based, 2020-01-07 19:00:00 EST - 2023-02-06 19:00:00 EST <----- Old license
date-based, 2023-02-06 19:00:00 EST - 2024-02-06 19:00:00 EST <----- Old license
date-based, 2023-02-06 19:00:00 EST - 2024-02-06 19:00:00 EST
date-based, 2024-02-06 19:00:00 EST - 2025-02-06 19:00:00 EST <----- New and valid license with expiration of 2025
date-based, 2024-02-06 19:00:00 EST - 2025-02-06 19:00:00 EST
First, verify whether the correct license has been applied.
If the correct license is applied, a restart of the license-services daemon using the below command can help fix it:
> restart license-service
It seems like the licensing daemon gets glitched and doesn't recognize the valid license. After restarting the daemon, it reevaluated the licenses and therefore removed the error.
If that doesn't fix it, you may need to create an admin case so CCare can check the license status.
Note: Even if the License is expired, there will not be any impact to the production traffic. Juniper provides grace period of 30 days for production license, hence the FPC remains UP for next 30days of grace period.
2024-02-29 : Article Created
2024-12-30 : Updated the article with correct command for restarting license-service (restart license-service )