Product Support Notice © 2020 Avaya Inc. All Rights Reserved. PSN # PSN005178u Original publication date: April 23, 2018. This is Issue #5, published date: Severity/risk level Low Urgency When convenient December 28, 2020. Name of problem NFS mount not working after upgrade to CMS 18.0.2.0 or later releases Products affected CMS R18, CMS R19 Problem description Beginning with CMS R18.0.2.0, customers may have NFS mount point connection problems. This may affect backups. Many customers have NFS mount points created to provide CMS backups. Beginning with CMS R18.0.2.0, only NFS v4 is supported by default. If your NFS mount point is running NFS v3 and you upgrade to CMS R18.0.2.0 (or a later release), the mount point will fail and thus your backups will fail.
How to determine if NFS is mounted to an NFS v3 or NFS v4 server: Run the command: mount –v | grep nfs Or run the command: nfsstat –m The system will display all the NFS mounted file systems. You may have to filter for a specific NFS mount point that you use for CMS backups.
Example of using the ‘mount’ command: (cmsserver)-(root)=# mount -v | grep nfs Output looks similar to this: sunrpc on /var/lib/nfs/rpc_pipefs type rpc_pipefs (rw) cms-store:/store on /nfsbu type nfs (rw,nosuid,bg,soft,intr,vers=4,addr=135.9.86.57,clientaddr=135.9.131.175)
Example using the ‘nfsstat’ command: (cmsserver)-(root)=# nfsstat –m Output looks similar to this: /nfsbu from cms-store:/store/ Flags: rw,nosuid,relatime,vers=4,rsize=1048576,wsize=1048576,namlen=255,soft,proto=tcp,port=0,timeo=600 ,retrans=2,sec=sys,clientaddr=135.9.131.175,minorversion=0,local_lock=none,addr=135.9.86.57
Resolution This situation will never be resolved in a future CMS release. CMS will continue to be deployed using only NFSv4 by default. The use of versions of NFS older than v4 is considered a security risk. Customers should upgrade to the use of NFSv4.
To workaround the use of NFSv4, the following two options are available: One option is to modify the /etc/fstab to force NFSv3 for an individual mount point Edit the /etc/fstab file and add nfsvers=3 to only the line item for the mount point used for NFS backups For example, the standard /etc/fstab entries follow this format:
The other option is to install the rpcbind rpm on your CMS system to resolve the problem. NFS v3 requires the use of rpcbind. Thus installing the rpcbind rpm will resolve the problem.
How to obtain and install the rpcbind rpm:
NOTE: By performing the following instructions, customers agree that the security improvement in CMS R18.0.2.0 (and later releases) with respect to NFS mounted file systems will be invalidated. If you have questions about the operations, discuss with Avaya Services Support before proceeding.
The rpcbind rpm is found on the CMS software DVD. To obtain the rpm from the CMS software DVD and install the rpcbind rpm, do the following:
1. Load the Avaya Call Management System software disc into the disc drive. 2. Change to the root directory by entering: cd / 3. Mount the disc drive. Enter: mount /dev/dvd /mnt The system displays the following message: mount: block device /dev/sr0 is write-protected, mounting read-only CAUTION: You must turn off CMS in order to install RHEL Linux® rpms. 4. Turn off CMS. Enter: cmssvc The system displays the CMSSVC Menu. 5. Enter the number associated with the run_cms option. 6. Enter the number associated with the Turn off both CMS and IDS option. The system returns to the command prompt. 7. Navigate to the directory with the rpcbind rpm, Enter: cd /mnt/rpm_updates/cmsrepo 8. To install the rpcbind rpm, enter: rpm -ivh rpcbind-0.2.0-13.el6_9.1.x86_64.rpm 9. Unmount the DVD. cd / umount /dev/dvd /mnt You can now safely eject the DVD 10. The rpcbind service must be started. Execute the following commands for CMS R18.x versions: /etc/init.d/rpcbind start /etc/init.d/nfslock start Execute the following commands for CMS R19.x versions: systemctl start rpcbind systemctl start nfslock 11. Turn on CMS. Enter: cmssvc The system displays the CMSSVC Menu. 12. Enter the number associated with run_cms option. 13. Enter the number associated with the Turn On both CMS and IDS option.
Workaround or alternative remediation n/a Remarks n/a Patch Notes The information in this section concerns the patch, if any, recommended in the Resolution above. Backup before applying the patch n/a Download n/a Patch install instructions Service-interrupting? n/a No Verification n/a Failure n/a Patch uninstall instructions n/a Security Notes The information in this section concerns the security risk, if any, represented by the topic of this PSN. Security risks n/a Avaya Security Vulnerability Classification Not Susceptible Mitigation n/a
If you require further information or assistance please contact your Authorized Service Provider, or visit support.avaya.com. There you can access more product information, chat with an Agent, or open an online Service Request. Support is provided per your warranty or service contract terms unless otherwise specified in the Avaya support Terms of Use. Disclaimer: ALL INFORMATION IS BELIEVED TO BE CORRECT AT THE TIME OF PUBLICATION AND IS PROVIDED “AS IS”. AVAYA INC., ON BEHALF OF ITSELF AND ITS SUBSIDIARIES AND AFFILIATES (HEREINAFTER COLLECTIVELY REFERRED TO AS “AVAYA”), DISCLAIMS ALL WARRANTIES, EITHER EXPRESS OR IMPLIED, INCLUDING THE WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AND FURTHERMORE, AVAYA MAKES NO REPRESENTATIONS OR WARRANTIES THAT THE STEPS RECOMMENDED WILL ELIMINATE SECURITY OR VIRUS THREATS TO CUSTOMERS’ SYSTEMS. IN NO EVENT SHALL AVAYA BE LIABLE FOR ANY DAMAGES WHATSOEVER ARISING OUT OF OR IN CONNECTION WITH THE INFORMATION OR RECOMMENDED ACTIONS PROVIDED HEREIN, INCLUDING DIRECT, INDIRECT, CONSEQUENTIAL DAMAGES, LOSS OF BUSINESS PROFITS OR SPECIAL DAMAGES, EVEN IF AVAYA HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. THE INFORMATION PROVIDED HERE DOES NOT AFFECT THE SUPPORT AGREEMENTS IN PLACE FOR AVAYA PRODUCTS. SUPPORT FOR AVAYA PRODUCTS CONTINUES TO BE EXECUTED AS PER EXISTING AGREEMENTS WITH AVAYA. All trademarks identified by ® or TM are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners.