Avaya PKI Certificate Expiry of 11 March 2009
On 11th March 2009, the certificates in certain releases of Avaya Communication Manager, Application Enablement Services, and Modular Messaging will expire. How will this effect your business? Make sure you don't get caught out!
Check your systems PKI certificate
If your certificate expires on 11 March…
Option 1 – Self-service
There are two ways to obtain a new RFA License file, which contains a new PKI certificate. There is no charge for either. First, you can use the Get PKI Certificate License File tool. The new RFA license file is delivered via email, which you must then install on the system. Click on the video tutorial links below for help with license file installation. Installation of the RFA license will update the PKI certificate.
Another option, available only to Communication Manager 3.1.4 or 4.0.1 customers, is to schedule an automatic update (PIE connectivity required). These methods are not service-affecting. Note that if any type of troubleshooting license is or has been installed on the CM system, you will receive a message to that effect when you request a license file. In this case, you will need to contact your support partner.
If that is not possible, new certificates are delivered in the Service Packs that are available for some product releases (refer to product release table below). Installing the Service Pack will require a system reboot.
Option 2: Release upgrade
Customers planning to upgrade to Communication Manager 5.x (avaya cm5), Modular Messaging 4.x (avaya cm4) or Application Enablement Services 4.1 before March 11, 2009, will receive new PKI certificates as part of the upgrade. No additional action is necessary in the interim.
What happens if you do nothing?
Failure to obtain a new RFA licence will not cause these applications to stop working, but it will cause a variety of service outages if the PKI certificates are not updated, including:
Failure of translation file synchronization between main server and remote survivable servers (service failover not affected) Failure to create new SIP trunks (existing SIP trunks not affected) Failure of encrypted software duplication for S87xx server pairs (unencrypted software duplication not affected) Failure of links between Communication Manager and Application Enablement Services or Modular Messaging adjuncts Failure of the Communication Manager Upgrade Tool Warning messages on server maintenance web pages (pages will function normally under Microsoft Internet Explorer after clicking through warnings)
Your current Avaya support partner should have provided you with the guidance you need to ensure your systems are not affected.
