Method of Procedure to Upgrade RMS OS to Red Hat Enterprise Linux 6.7

Transcription

1 First Published: November 20, 2015

2 Contents Scope of MOP... 4 Release Components... 4 Pre Requisites... 4 Assumptions... 4 Process Information... 5 Upgrade Timing... 5 Requirements... 5 Pre Maintenance... 6 Enable VAMI Login... 6 Clone the System... 6 Clone Central Node... 6 Clone Serving Node Clone Upload Node Maintenance Activity Verify the RHEL Version Staging the RHEL 6.7 ISO Mount the ISO File Verify the Mounter Partition Create the Local Repository File Cleaning Existing Yum Configuration Verify the RPMs to be upgraded Update the RPMs Install the RHEL Security Patch Central Node Updates Reboot the System Verify the RedHat Version Start the VMWare Tools Application after OS Upgrade Cloning the RHEL Upgraded VMs Maintenance Verification

3 Glossary Appendix Appendix A Escalation Contacts Appendix B Document Variables Obtaining Documentation and Submitting a Service Request

4 Scope of MOP Scope of MOP This document describes the procedure required to upgrade OS from Red Hat Enterprise Linux 6 x64 Update 1 or Red Hat Enterprise Linux 6 x64 Update 6 to Red Hat Enterprise Linux 6 (Santiago) x64 Update 7. Release Components This section contains a list of component dependencies for this procedure. Component Version Red Hat Enterprise Linux 6 (Santiago) x64 Update 7 Kernel kernel el6.x86_64 This is RHEL 6 Update 7 Pre Requisites RMS 4.1 setup running on OS RHEL 6.1 RMS 5.1 setup running on OS RHEL 6.6 Assumptions It is assumed that the user has firm knowledge and familiarity with using LINUX from the shell command line. For example, the user should know about the following (this is not a comprehensive list): How to login to a command line session (typically as root) How to edit files with vi or vim How to view files (cat, more, less) How to SSH to server using putty or terminal. Basic IP networking (IP addresses, network masks, etc.) VMWare vsphere access MOP assumes VMware ESXi5.1 and ESXi5.5 RHEL 6.7 ISO should be available on the local system. IPs of the central node and DNS entries are available and user can login to central node and execute commands in super user mode. Assuming Distributed RMS deployment mode. Assuming the data store has sufficient free space to clone the nodes. 4

5 Process Information Process Information Upgrade Timing This table describes the proposed timeline for this activity. Step Start Time Duration Pre-Maintenance (backup all VMs) T 15 minutes Maintenance Activities(Upgrade the VMs) T+15 1 hours 15 minutes Total 1 hour 30 minutes Requirements This MOP has the following staffing requirements: Cisco Ops Team Cisco AS Team 5

6 Pre Maintenance Pre Maintenance Enable VAMI Login On each of the nodes (CN, SN, UN), login as a root user and enable the VAMI_login. # echo /opt/vmware/share/vami/vami_login > /etc/rc.local The system responds with the command prompt Clone the System Clone Central Node 1. Locate the vapp of the Central Node to be cloned In VMWare vsphere Client check on the left navigation panel and locate the vapp of central node. 2. Power off the vapp Right click on Central node vapp. 6

7 Pre Maintenance Click [Power Off] Click [Yes]. The status can be seen on the right side. 3. Clone the VM Select the vapp for central node again, right click 7

8 Pre Maintenance select Clone under All vcenter Actions Select the creation type as Clone an existing vapp and click on Next 8

9 Pre Maintenance Browse the host where to keep the clone. Once selected It will do automatically run a compatibility test once Validation Succeed message is seen under Compatibility Click [Next] Otherwise try for another host. Provide a unique name to the clone and select the folder in which the clone should be present 9

10 Pre Maintenance Select the storage data store and Click [Next] Click [Next] 10

11 Pre Maintenance Click [Next] 11

12 Pre Maintenance Click [Finish] and check the below Tab Recent Tasks 4. Verify the completion of the clone Verify the clone is created successfully by checking inventory of the host selected for cloning. In the example below check for Clone of CENTRAL-BACKUP2-MAY17 12

13 Pre Maintenance 5. Power On the vapp Select the Cloned VM then right click and then Power On VM will boot. If VM is booted successfully and you can login to VM via SSH, Clone is properly done. Otherwise delete this clone and recreate it. Clone Serving Node Locate the Serving Node vapp on the vsphere Client and repeat the steps mentioned in the above Clone Central Node section. Clone Upload Node Locate the Upload Node vapp on the vsphere Client and repeat the steps mentioned in the above Clone Central Node section. 13

14 Maintenance Activity Maintenance Activity Note: The procedure remains same for RHEL upgrade from 6.1/6.6 to RHEL6.7 Verify the RHEL Version 1. Login to the RMS Nodes (Central, Serving, Upload) as a root user and verify the RHEL version # cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.1 (Santiago) Red Hat Enterprise Linux Server release 6.6 (Santiago) Staging the RHEL 6.7 ISO 2. Verify the RHEL 6.7 ISO file is present on the / directory of the server (Central, Serving, Upload) else follow the step (A) # cd /; # ls grep rhel rhel-server-6.7-x86_64-dvd.iso A. To copy the ISO file that is not present on the VM then download the RHEL6.7-tar.gz package onto the / directory of the server (Central, Serving, Upload) and untar. # cd /; # tar zxvf RHEL6.7-tar.gz; # mv RHEL6.7/rhel-server-6.7-x86_64-dvd.iso /; # rm -rf RHEL6.7 RHEL6.7-tar.gz; # ls grep rhel rhel-server-6.7-x86_64-dvd.iso 14

15 Maintenance Activity Mount the ISO File 3. Mount the ISO under /rhel67 directory # mkdir /rhel67 # mount -o rw,loop rhel-server-6.7-x86_64-dvd.iso /rhel67 The system responds with the command prompt. Verify the Mounter Partition 4. Verify if the partition is mounted to /mnt directory # df -h Filesystem Size Used Avail Use% Mounted on /dev/sda3 99G 15G 79G 16% / tmpfs 7.8G 0 7.8G 0% /dev/shm /dev/sda1 /dev/sdb1 /dev/sdc1 /dev/sdd1 124M 28M 91M 24% /boot 47G 24G 21G 54% /rms/data 24G 711M 22G 4% /rms/app/cscoar 24G 357M 22G 2% /rms/app/nwreg2 /rhel-server-6.7-x86_64-dvd.iso 3.6G 3.6G 0 100% /rhel67 Create the Local Repository File 5. Create a yum local repository file pointing to mounted RHEL6.7 ISO directory with the below provided content # vi /etc/yum.repos.d/system.repo [systemrepo] name=systemrepo baseurl=file:///rhel67/ gpgcheck=0 enabled=1 15

16 Maintenance Activity Cleaning Existing Yum Configuration 6. Clean any existing yum configuration from the system Note: Please skip the below warnings observed during the execution of the below clean command. This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. # yum clean all Loaded plugins: product-id, subscription-manager Updating Red Hat repositories. Cleaning repos: systemrepo Cleaning up Everything Verify the RPMs to be upgraded 7. Check the list of RPMs whose updates are available Note: Please skip the below warnings observed during the execution of the below command. This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. # yum check-update The system responds with the list of upgradable rpms Update the RPMs 8. Apply the command to update the rpms Note: Please skip the warnings observed during the execution of the below update command. # yum update -y The system responds with the command prompt. 16

17 Maintenance Activity Install the RHEL Security Patch Note: Please skip the below warnings observed during the execution of the below command. This system is not registered to Red Hat Subscription Management. You can use subscription-manager to register. # yum install yum-security The system responds with the command prompt. Central Node Updates Note: Skip these updates on Serving and Upload Nodes Skip these updates if the RHEL upgrade path is from 6.6 to After the successful rpm upgrades perform the below steps on the CENTRAL NODE a. As a root user revert the postgres port setting. # sed -i 's/pgport=5432/pgport=5435/' /etc/rc.d/init.d/postgresql The system responds with the command prompt. b. Stop the Network Manager and update the DNS server entries in /etc/resolv.conf file using vi editor. service NetworkManager stop chkconfig NetworkManager off echo nameserver >> /etc/resolv.conf echo nameserver >> /etc/resolv.conf The system responds with the command prompt. 17

18 Maintenance Activity Reboot the System 10. Reboot the system for the changes to reflect # reboot The system goes down for reboot. Verify the RedHat Version 11. Once the system is up after the reboot, as a root user verify that the redhat version is updated to 6.7 # cat /etc/redhat-release Red Hat Enterprise Linux Server release 6.7 (Santiago) 18

19 Maintenance Activity Start the VMWare Tools Application after OS Upgrade 12. After verifying the redhat version start the vmware tools application on all the RMS nodes and verify the same from vsphere client on the VMs Summary tab # /usr/bin/vmware-config-tools.pl -d The system responds with the command prompt. 19

20 Cloning the RHEL Upgraded VMs Cloning the RHEL Upgraded VMs 13. As a root user execute the below command on all the RMS Nodes (Central/Serving/Upload) to avoid network unreachability issue while cloning the VM after RHEL upgrade # mv /etc/udev/rules.d/70-persistent-net.rules /root The system responds with the command prompt. Maintenance Verification 14. Verify that all the VMs (Central, Serving, Upload) are up and running and are accessible 15. Login to all the VMs (Central, Serving, Upload) as a root user and verify the installed kernel on the machine $ ssh System returns with the password prompt. $ su - System returns with the password prompt. # uname r el6.x86_64 20

21 Glossary Glossary Terminology Active-Active BAC DB FAP AP FGW RDU Primary Standby CSG CSG ID Definition Redundant system supporting near-real-time failover from primary to standby. Broadband Access Center Database Femtocell Access Point Access Point (Generic form of Femto Access Point) Femto Gateway Regional Distribution Unit, a part of the BAC that interfaces with the OSS north bound and DPE south bound and is the master data store Currently desired active system at any point in time (East RDU) Currently desired inactive system at any point in time (West RDU) Closed Subscriber Group Closed Subscriber Group ID SIA SP ZTPS Service Interface Agreement Service Provider Zero-Touch Provisioning System 21

22 Appendix Appendix Appendix A Escalation Contacts Appendix B Document Variables This section contains a list of all the server-related document variables and the codes necessary to update them. CENTRAL_VM_DNS1 CENTRAL_VM_DNS2 Do not update these variables

23 Obtaining Documentation and Submitting a Service Request Obtaining Documentation and Submitting a Service Request For information on obtaining documentation, using the Cisco Bug Search Tool (BST), submitting a service request, and gathering additional information, see What s New in Cisco Product Documentation at: Subscribe to what s New in Cisco Product Documentation, which lists all new and revised Cisco technical documentation, as an RSS feed and deliver content directly to your desktop using a reader application. The RSS feeds are a free service. 23

24 THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS. THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY. The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB s public domain version of the UNIX operating system. All rights reserved. Copyright 1981, Regents of the University of California. NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED AS IS WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE. IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental. All printed copies and duplicate soft copies are considered un-controlled copies and the original on-line version should be referred to for latest version. Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at /go/offices. Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: /go/trademarks. Third-party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1110R) 2015 All rights reserved.