CX II upgraded to 9.1.0.95 still went to License Violation

[petr.necas]

I upgraded one CXII controller to the latest release 9.1 PR1 (9.1.0.95) but still after 20th August went to the license violation state.

License Manager - ARID                 : XXXXXXXXX
License Violation Level                : Critical
Time at current License Violation Level: less than 1 hour
Time remaining until next escalation   : 21 days
Local Violation Cause(s):
   - The License Keys cannot be validated

It does not seem that any of the educational videos from Mitel would apply...
MiVoice Business Security Certificate Upgrade MiVB FINAL.mp4
MiVoice Business Security Certificate Upgrade physical FINAL.mp4

I tried this:
root@mvb-xxxxx-42:/sysro# ls root*
rootCert2040_ppc
root@mvb-xxxxx-42:/sysro# mcdDebug
Connecting to mcd, please wait...
Press Ctrl-C to finish session
value = 0 = 0x0
Enter mcd command -> ld </sysro/rootCert2040_ppc
dlopen for "</sysro/rootCert2040_ppc" failed. Error=</sysro/rootCert2040_ppc: cannot open shared object file: No such file or directory
value = 772686824 = 0x2e0e43e8
Enter mcd command ->

Any ideas?

[petr.necas]

AMC server seems to be accessible:

root@mvb-xxxx-42:/sysro# ping register.mitel-amc.com
PING register.mitel-amc.com (216.191.234.91) 56(84) bytes of data.
64 bytes from www.mitel-amc.com (216.191.234.91): icmp_seq=1 ttl=45 time=119 ms
64 bytes from www.mitel-amc.com (216.191.234.91): icmp_seq=2 ttl=45 time=118 ms
64 bytes from www.mitel-amc.com (216.191.234.91): icmp_seq=3 ttl=45 time=119 ms
64 bytes from www.mitel-amc.com (216.191.234.91): icmp_seq=4 ttl=45 time=118 ms
64 bytes from www.mitel-amc.com (216.191.234.91): icmp_seq=5 ttl=45 time=119 ms

I ran Sync in the Server Manager:

ServiceLink Status Information
SUCCESS   
Operation status report
The sync completed successfully! Your new ServiceLink status information is shown below.

[sunspark]

Do you have DLM? if yes, open the garid form, make sure that your master (dlm server) set to yes. Don't make any modifications, just open the form and save.
The license violation should disappear after few seconds

[petr.necas]

No there is no DLM, it is simple standalone system. I suspect the license violation alarm is there not due to the expired certificate but due to the expired SWAS when the customer is not allowed to use the latest release. Unfortunately I do not have access to their ARID on the AMC server to verify.

I will try to switch it to the inactive SW load that is still on 9.0.X but there is still the problem how to update the certificate on CX II systems running linux with the version older than
the the 9.0 SP3.

[sunspark]

You can t upgrade (validate licenses) if you dont have swas.

I think you didn't upload the root cert with bin transfert ftp.
This is why you cant apply the cert,

[sunspark]

I tried this:
root@mvb-xxxxx-42:/sysro# ls root*
rootCert2040_ppc
root@mvb-xxxxx-42:/sysro# mcdDebug
Connecting to mcd, please wait...
Press Ctrl-C to finish session
value = 0 = 0x0
Enter mcd command -> ld </sysro/rootCert2040_ppc
dlopen for "</sysro/rootCert2040_ppc" failed. Error=</sysro/rootCert2040_ppc: cannot open shared object file: No such file or directory
value = 772686824 = 0x2e0e43e8
Enter mcd command ->


But did you transfer the cert wirh ftp to your Cx ?

Another think, you talk about rootCert2040_ppc ( this is for version between 5 and
This you have to download the v9 cert

[ibo422]

Indeed. The 9.1.x doesn't need the patch. The 9.0.x for CX needs the other file.

Step 1   WinSCP or SFTP rootCert2040-9.0_ppc.tar to the /tmp folder of MSL based server in Binary mode

Step 2   To establish SSH session to MSL based server and then untar rootCert2040-9.0_pp.tar
    Launch Putty to establish SSH session to MSL based server and login as root user
Type: tar -C / -xvf /tmp/rootCert2040-9.0_ppc.tar

Step 3   To load the patch, type: sh /tmp/installRootCert2040
    
Step 4   To perform AMC sync to update ARID and/or GARID with the newly installed certificate
   4a> Launch https://<MIVB IP>/server-manager  > ServiceLink -> Status, then click Sync button

4b> For GRAID if applicable, launch ESM -> the Application Group Licensing form, click Change, click Save.

Step 5   To validate if the new certificate is in use after AMC sync.
   View the ARID/GARID record in AMC to confirm that “.9” is appended to software version.