| Installation GuideChapter 35. Your Next Steps35.1. Updating Your SystemRed Hat releases updated software packages for Red Hat Enterprise Linux throughout the support period of each version. Updated packages add new features, improve reliability, resolve bugs, or remove security vulnerabilities. To ensure the security of your system, update regularly, and as soon as possible after Red Hat issues a security announcement. 35.1.1. Driver update rpm packagesDo not install a driver update rpm unless you are certain that your system requires it. Installing a driver update on a system for which it was not intended can cause system difficulties. To see a list of driver updates already installed on your system, click ⤍ ⤍ on your desktop, and enter the root password if prompted for it. Click the Search tab, enter the word kmod- (notice the final -) and click Search. Alternatively, you can use the command line, as follows: $ rpm -�qa | egrep ^kmod- Note the - on the end of kmod. This will list all installed packages that begin with kmod-, which should include all driver updates that are currently installed on your system. Additional drivers provided by third-party update software are not listed in this output. Contact the third-party vendor for details. To install a new driver update rpm package: Download the driver update rpm package from the location specified by Red Hat or your hardware vendor. The package file name will begin with kmod (short for kernel module) and have a form similar to this example: kmod-foo-�1.05-2.el6.i686
In the example, the driver update rpm package supplies a driver update named foo with version number 1.05-2 for Red Hat Enterprise Linux 6, on i686 systems. Driver update rpm packages are signed packages, and like all other software packages, they are automatically validated at install time. To perform this step manually, type the following at a command line: $ rpm --��checksig -�v filename.rpm where filename.rpm is the driver update rpm package file name. This verifies the package against using the standard Red Hat GPG package signing key that is already installed on any Red Hat Enterprise Linux 6 system. If you need this key for verification purposes on another system, you can can obtain it from: https://access.redhat.com/security/team/key/Locate and double-click the file that you downloaded. The system might prompt you for the root password, after which it will present the following Installing Packages box: Click Apply to complete the package installation. Alternatively, you can install a driver update manually on the command line: $ rpm -�ivh kmod-foo-�1.05-2.el6.i686 Whether you used a graphical install, or a command line install, reboot your system to ensure your system is using the new driver.
If Red Hat ships a kernel errata update before the next release of Red Hat Enterprise Linux, your system will continue to use the driver updates that you have installed. There is no need to re-install driver updates following an errata update. Generally, when Red Hat releases a new version of Red Hat Enterprise Linux, all driver updates for the previous version are incorporated in the new version. However, if it was not possible to include a particular driver, you will need to perform another driver update when you install the new version of Red Hat Enterprise Linux. In this case, Red Hat or your hardware party vendor will inform you of the location of the update. 35.2. Finishing an UpgradeMost software repository configurations are stored in packages that end with the term release. Check the old package list for the repositories that were installed: awk '{print $1}' ~/old-pkglist.txt | grep 'release$'
If necessary, retrieve and install these packages from their original sources on the Internet. Follow the instructions at the originating site to install the repository configuration packages for use by yum and other software management tools on your Red Hat Enterprise Linux system. Then run the following commands to make a list of other missing software packages: awk '{print $1}' ~/old-pkglist.txt | sort | uniq > ~/old-pkgnames.txtrpm -qa --qf '%{NAME}\n' | sort | uniq > ~/new-pkgnames.txtdiff -u ~/old-pkgnames.txt ~/new-pkgnames.txt | grep '^-' | sed 's/^-//' > /tmp/pkgs-to-install.txt
Now use the file /tmp/pkgs-to-install.txt with the yum command to restore most or all of your old software: su -c 'yum install `cat /tmp/pkgs-to-install.txt`'
Due to changes in package complements between Red Hat Enterprise Linux releases, it is possible this method may not restore all the software on your system. You can use the routines above to again compare the software on your system, and remedy any problems you find. 35.3. Switching to a Graphical LoginTo use a graphical user interface on System z, use vncserver instead. If you installed using a text login and wish to switch to a graphical login, follow this procedure. If you are not already root, switch users to the root account: su -
Provide the administrator password when prompted. If you have not already done so, install the X Window System and a graphical desktop environment. For example, to install the GNOME desktop environment, use this command: yum groupinstall "X Window System" Desktop
To install the KDE desktop environment, use: yum groupinstall "X Window System" "KDE Desktop"
This step may take some time as your Red Hat Enterprise Linux system downloads and installs additional software. You may be asked to provide the installation media depending on your original installation source. Run the following command to edit the /etc/inittab file: vi /etc/inittab
Press the I key to enter insert mode. Find the line that includes the text initdefault. Change the numeral 3 to 5. Type :wq and press the Enter key to save the file and exit the vi text editor.
Reboot the system using the reboot command. Your system will restart and present a graphical login. 35.3.1. Enabling Access to Software Repositories from the Command LineThe usual way to install new software on a Red Hat Enterprise Linux system is through a software repository. You can access Red Hat Enterprise Linux repositories through the Internet with your Red Hat Network subscription, or use a Red Hat Enterprise Linux installation DVD as a repository. The software that you access through online repositories is more up-to-date than what is available on an installation DVD. Furthermore, configuring a Red Hat Enterprise Linux system to access online repositories is generally easier than configuring the system to use an installation DVD as a repository, as long as you have an existing, wired network connection available. 35.3.1.1. Enabling Access to Software Repositories Through the InternetIf you supplied your Red Hat Network subscription number during the installation process, your system is already configured to access Red Hat Enterprise Linux repositories through the Internet. Therefore, all you must do is ensure that the system can access the Internet. If you have an existing, wired network connection available, this process is straightforward: If you are not already root, switch users to the root account: su -
Ensure that the system is plugged into your network. Note that your network might be as small as two devices - a computer and an external modem/router. Run system-config-network. The network configuration tool starts and displays the Select Action screen. Select and press Enter. The network configuration tool displays the Select A Device screen with a list of network interfaces present on your system. The first interface is named eth0 by default. Select a network interface to configure and press Enter. The network configuration tool takes you to the Network Configuration screen. You can manually configure a static IP, gateway, and DNS servers on this screen or leave these fields blank to accept the default values. When you have chosen a configuration, select OK, and press Enter. The network configuration tool takes you back to the Select A Device screen. Select Save and press Enter. The network configuration tool takes you back to the Select Action screen. Select Save&Quit and press Enter. The network configuration tool saves your settings and exits. Run ifup interface, where interface is the network interface that you configured with the network configuration tool. For example, run ifup eth0 to start eth0.
Configuration of dial-up or wireless Internet connections is more complicated and beyond the scope of this guide. 35.3.1.2. Using a Red Hat Enterprise Linux Installation DVD as a Software RepositoryTo use a Red Hat Enterprise Linux installation DVD as a software repository, either in the form of a physical disc, or in the form of an ISO image file. If you are using a physical DVD, insert the disc into your computer. If you are not already root, switch users to the root account: su -
Create a mount point for the repository: mkdir -p /path/to/repo
where /path/to/repo is a location for the repository, for example, /mnt/repo Mount the DVD on the mount point that you just created. If you are using a physical disc, you need to know the device name of your DVD drive. You can find the names of any CD or DVD drives on your system with the command cat /proc/sys/dev/cdrom/info. The first CD or DVD drive on the system is typically named sr0. When you know the device name, mount the DVD: mount -r -t iso9660 /dev/device_name /path/to/repo
For example: mount -r -t iso9660 /dev/sr0 /mnt/repo If you are using an ISO image file of a disc, mount the image file like this: mount -r -t iso9660 -o loop /path/to/image/file.iso /path/to/repo
For example: mount -r -o loop /home/root/Downloads/RHEL6-Server-i386-DVD.iso /mnt/repo Note that you can only mount an image file if the storage device that holds the image file is itself mounted. For example, if the image file is stored on a hard drive that is not mounted automatically when the system boots, you must mount the hard drive before you mount an image file stored on that hard drive. Consider a hard drive named /dev/sdb that is not automatically mounted at boot time and which has an image file stored in a directory named Downloads on its first partition: mkdir /mnt/tempmount /dev/sdb1 /mnt/tempmkdir /mnt/repomount -r -t iso9660 -o loop mount -r -o loop /mnt/temp/Downloads/RHEL6-Server-i386-DVD.iso /mnt/repo
If you are not sure whether a storage device is mounted, run the mount command to obtain a list of current mounts. If you are not sure of the device name or partition number of a storage device, run fdisk -l and try to identify it in the output. Create a new repo file in the /etc/yum.repos.d/ directory. The name of the file is not important, as long as it ends in .repo. For example, dvd.repo is an obvious choice. Choose a name for the repo file and open it as a new file with the vi text editor. For example: vi /etc/yum.repos.d/dvd.repo
Press the I key to enter insert mode. Supply the details of the repository. For example: [dvd]baseurl=file:///mnt/repo/Serverenabled=1gpgcheck=1gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release The name of the repository is specified in square brackets - in this example, [dvd]. The name is not important, but you should choose something that is meaningful and recognizable. The line that specifies the baseurl should contain the path to the mount point that you created previously, suffixed with /Server for a Red Hat Enterprise Linux server installation DVD, or with /Client for a Red Hat Enterprise Linux client installation DVD. Press the Esc key to exit insert mode. Type :wq and press the Enter key to save the file and exit the vi text editor. After installing or upgrading software from the DVD, delete the repo file that you created.
Chapter 36. Basic System RecoveryWhen things go wrong, there are ways to fix problems. However, these methods require that you understand the system well. This chapter describes how to boot into rescue mode, single-user mode, and emergency mode, where you can use your own knowledge to repair the system. You might need to boot into one of these recovery modes for any of the following reasons: You are unable to boot normally into Red Hat Enterprise Linux (runlevel 3 or 5). You are having hardware or software problems, and you want to get a few important files off of your system's hard drive. You forgot the root password.
36.1.1.1. Unable to Boot into Red Hat Enterprise LinuxThis problem is often caused by the installation of another operating system after you have installed Red Hat Enterprise Linux. Some other operating systems assume that you have no other operating system(s) on your computer. They overwrite the Master Boot Record (MBR) that originally contained the GRUB boot loader. If the boot loader is overwritten in this manner, you cannot boot Red Hat Enterprise Linux unless you can get into rescue mode and reconfigure the boot loader. Another common problem occurs when using a partitioning tool to resize a partition or create a new partition from free space after installation, and it changes the order of your partitions. If the partition number of your / partition changes, the boot loader might not be able to find it to mount the partition. To fix this problem, boot in rescue mode and modify the /boot/grub/grub.conf file. 36.1.1.2. Hardware/Software ProblemsThis category includes a wide variety of different situations. Two examples include failing hard drives and specifying an invalid root device or kernel in the boot loader configuration file. If either of these occur, you might not be able to reboot into Red Hat Enterprise Linux. However, if you boot into one of the system recovery modes, you might be able to resolve the problem or at least get copies of your most important files. What can you do if you forget your root password? To reset it to a different password, boot into rescue mode or single-user mode, and use the passwd command to reset the root password. 36.1.2. Booting into Rescue ModeRescue mode provides the ability to boot a small Red Hat Enterprise Linux environment entirely from CD-ROM, or some other boot method, instead of the system's hard drive. As the name implies, rescue mode is provided to rescue you from something. During normal operation, your Red Hat Enterprise Linux system uses files located on your system's hard drive to do everything - run programs, store your files, and more. However, there may be times when you are unable to get Red Hat Enterprise Linux running completely enough to access files on your system's hard drive. Using rescue mode, you can access the files stored on your system's hard drive, even if you cannot actually run Red Hat Enterprise Linux from that hard drive. To boot into rescue mode, you must be able to boot the system using one of the following methods : By booting the system from a boot CD-ROM or DVD. By booting the system from other installation boot media, such as USB flash devices. By booting the system from the Red Hat Enterprise Linux installation DVD.
Once you have booted using one of the described methods, add the keyword rescue as a kernel parameter. For example, for an x86 system, type the following command at the installation boot prompt: linux rescue
If your system requires a third-party driver provided on a driver disc to boot, load the driver with the additional option dd: linux rescue dd
If a driver that is part of the Red Hat Enterprise Linux 6 distribution prevents the system from booting, blacklist that driver with the rdblacklist option. For example, to boot into rescue mode without the foobar driver, run: linux rescue rdblacklist=foobar
You are prompted to answer a few basic questions, including which language to use. It also prompts you to select where a valid rescue image is located. Select from Local CD-ROM, Hard Drive, NFS image, FTP, or HTTP. The location selected must contain a valid installation tree, and the installation tree must be for the same version of Red Hat Enterprise Linux as the Red Hat Enterprise Linux disk from which you booted. If you used a boot CD-ROM or other media to start rescue mode, the installation tree must be from the same tree from which the media was created. For more information about how to setup an installation tree on a hard drive, NFS server, FTP server, or HTTP server, refer to the earlier section of this guide. If you select a rescue image that does not require a network connection, you are asked whether or not you want to establish a network connection. A network connection is useful if you need to backup files to a different computer or install some RPM packages from a shared network location, for example. The following message is displayed: The rescue environment will now attempt to find your Linux installation and mount it under the directory /mnt/sysimage. You can then make any changes required to your system. If you want to proceed with this step choose 'Continue'. You can also choose to mount your file systems read-only instead of read-write by choosing 'Read-only'. If for some reason this process fails you can choose 'Skip' and this step will be skipped and you will go directly to a command shell.
If you select Continue, it attempts to mount your file system under the directory /mnt/sysimage/. If it fails to mount a partition, it notifies you. If you select Read-Only, it attempts to mount your file system under the directory /mnt/sysimage/, but in read-only mode. If you select Skip, your file system is not mounted. Choose Skip if you think your file system is corrupted. Once you have your system in rescue mode, a prompt appears on VC (virtual console) 1 and VC 2 (use the Ctrl-Alt-F1 key combination to access VC 1 and Ctrl-Alt-F2 to access VC 2): sh-3.00b#
If you selected Continue to mount your partitions automatically and they were mounted successfully, you are in single-user mode. Even if your file system is mounted, the default root partition while in rescue mode is a temporary root partition, not the root partition of the file system used during normal user mode (runlevel 3 or 5). If you selected to mount your file system and it mounted successfully, you can change the root partition of the rescue mode environment to the root partition of your file system by executing the following command: chroot /mnt/sysimage
This is useful if you need to run commands such as rpm that require your root partition to be mounted as /. To exit the chroot environment, type exit to return to the prompt. If you selected Skip, you can still try to mount a partition or LVM2 logical volume manually inside rescue mode by creating a directory such as /foo mount -t ext4 /dev/mapper/VolGroup00-LogVol02 /foo
In the above command, /foo/dev/mapper/VolGroup00-LogVol02ext2 or ext3 replace ext4 with ext2 or ext3 respectively. If you do not know the names of all physical partitions, use the following command to list them: fdisk -l
If you do not know the names of all LVM2 physical volumes, volume groups, or logical volumes, use the following commands to list them: pvdisplay
vgdisplay
lvdisplay
From the prompt, you can run many useful commands, such as: ssh, scp, and ping if the network is started
dump and restore for users with tape drives
parted and fdisk for managing partitions
rpm for installing or upgrading software
vi for editing text files
36.1.2.1. Reinstalling the Boot LoaderIn many cases, the GRUB boot loader can mistakenly be deleted, corrupted, or replaced by other operating systems. The following steps detail the process on how GRUB is reinstalled on the master boot record: Boot the system from an installation boot medium. Type linux rescue at the installation boot prompt to enter the rescue environment. Type chroot /mnt/sysimage to mount the root partition. Type /sbin/grub-install bootpart to reinstall the GRUB boot loader, where bootpart is the boot partition (typically, /dev/sda). Review the /boot/grub/grub.conf file, as additional entries may be needed for GRUB to control additional operating systems. Reboot the system.
36.1.3. Booting into Single-User ModeOne of the advantages of single-user mode is that you do not need a boot CD-ROM; however, it does not give you the option to mount the file systems as read-only or not mount them at all. If your system boots, but does not allow you to log in when it has completed booting, try single-user mode. In single-user mode, your computer boots to runlevel 1. Your local file systems are mounted, but your network is not activated. You have a usable system maintenance shell. Unlike rescue mode, single-user mode automatically tries to mount your file system. Do not use single-user mode if your file system cannot be mounted successfully. You cannot use single-user mode if the runlevel 1 configuration on your system is corrupted. On an x86 system using GRUB, use the following steps to boot into single-user mode: At the GRUB splash screen at boot time, press any key to enter the GRUB interactive menu. Select Red Hat Enterprise Linux with the version of the kernel that you wish to boot and type a to append the line. Go to the end of the line and type single as a separate word (press the Spacebar and then type single). Press Enter to exit edit mode.
36.1.4. Booting into Emergency ModeIn emergency mode, you are booted into the most minimal environment possible. The root file system is mounted read-only and almost nothing is set up. The main advantage of emergency mode over single-user mode is that the init files are not loaded. If init is corrupted or not working, you can still mount file systems to recover data that could be lost during a re-installation. 36.2. Rescue Mode on Power Systems serversYou can use the installation disks in rescue mode, in case your system does not boot. Rescue mode gives you access to the disk partitions on your system so you can make any changes necessary to rescue your installation. After the Language Selection screen ( Section 15.2, "Language Selection"), the installation program attempts to mount the disk partitions on your system. It then presents you with a shell prompt where you can make the changes you need. These changes may include storing the kernel and command line into the IPL source, as described in the Installation Complete section ( Section 16.21, "Installation Complete"). When your changes are complete, you can exit the shell using exit 0. This causes a reboot from the C side. To reboot from the A or B side or from *NWSSTG, you should vary off the system instead of exiting the shell. 36.2.1. Special Considerations for Accessing the SCSI Utilities from Rescue ModeIf your system uses Native DASD disks, you may need access to the SCSI utilities from rescue mode. These utilities are located on the driver disc CD. The driver disc CD cannot be mounted from rescue mode unless special steps are taken. These steps are described below. If you have a second CD-ROM drive assigned to your Linux system, you can mount the driver disc CD in the second drive. If you have only one CD-ROM drive, you must set up an NFS boot, using the following steps: Boot from the CD-ROM with the linux rescue askmethod command. This allows you to manually select NFS as the source of your rescue media instead of defaulting to the CD-ROM drive. Copy the first installation disc onto a file system of another Linux system. Make this copy of the installation disc available through NFS or FTP. Vary off or power down the system you need to rescue. Set its IPL parameters as instructed for booting the Installation discs in rescue mode, except that the IPL source should point to the copy of boot.img on your IFS (from step 1, above). Make sure the installation disc is not in your DVD drive. IPL the Linux system. When the Linux system has booted into rescue mode, the CD-ROM drive is available for use and you can mount the driver media to access the SCSI utilities.
36.3. Using rescue mode to fix or work around driver problemsA malfunctioning or missing driver can prevent a system from booting normally. Rescue mode provides an environment in which you can add, remove, or replace a driver even when the system fails to boot. Wherever possible, we recommend that you use the RPM package manager to remove malfunctioning drivers or to add updated or missing drivers. If you cannot remove a malfunctioning driver for some reason, you can instead blacklist the driver so that it does not load at boot time. Note that when you install a driver from a driver disc, the driver disc updates all initramfs images on the system to use this driver. If a problem with a driver prevents a system from booting, you cannot rely on booting the system from another initramfs image. 36.3.1. Using RPM to add, remove, or replace a driverIn rescue mode, you can use RPM to install, remove, or update packages from the installed system, even though you did not boot the installed system. To remove a malfunctioning driver: Boot the system into rescue mode with the linux rescue command at the boot prompt, or the linux rescue dd command if you need to load a third-party driver from a driver disc. Follow the instructions in Section 36.1.2, "Booting into Rescue Mode" and do not choose to mount the installed system as read only. Change the root directory to /mnt/sysimage/: chroot /mnt/sysimage/
Use the rpm -e command to remove the driver package. For example, to remove the kmod-foobar driver package, run: rpm -e kmod-foobar
Exit the chroot environment: exit
Installing a driver is a similar process, but the RPM package that contains the driver must be available on the system. Boot the system into rescue mode with the linux rescue command at the boot prompt, or the linux rescue dd command if you need to load a third-party driver from a driver disc. Follow the instructions in Section 36.1.2, "Booting into Rescue Mode" and do not choose to mount the installed system as read only. Make the RPM package that contains the driver available. For example, mount a CD or USB flash drive and copy the RPM package to a location of your choice under /mnt/sysimage/, for example: /mnt/sysimage/root/drivers/. Change the root directory to /mnt/sysimage/: chroot /mnt/sysimage/
Use the rpm -ivh command to install the driver package. For example, to install the kmod-foobar driver package from /root/drivers/, run: rpm -�ivh /root/drivers/kmod-foobar-�1.2.0�4.17.el6.i686
Note that /root/drivers/ in this chroot environment is /mnt/sysimage/root/drivers/ in the original rescue environment.
When you have finished removing and installing drivers, reboot the system. 36.3.2. Blacklisting a driverAs described in Section 36.1.2, "Booting into Rescue Mode", the rdblacklist kernel option blacklists a driver at boot time. To continue to blacklist the driver on subsequent boots, add the rdblacklist option to the line in /boot/grub/grub.conf that describes your kernel. To blacklist the driver when the root device is mounted, add a blacklist entry in a file under /etc/modprobe.d/. Boot the system into rescue mode with the command linux rescue rdblacklist=name_of_driver, where name_of_driver is the driver that you need to blacklist. Follow the instructions in Section 36.1.2, "Booting into Rescue Mode" and do not choose to mount the installed system as read only. Open the /mnt/sysimage/boot/grub/grub.conf file with the vi text editor: vi /mnt/sysimage/boot/grub/grub.conf
Identify the default kernel used to boot the system. Each kernel is specified in the grub.conf file with a group of lines that begins title. The default kernel is specified by the default parameter near the start of the file. A value of 0 refers to the kernel described in the first group of lines, a value of 1 refers to the kernel described in the second group, and higher values refer to subsequent kernels in turn. Edit the kernel line of the group to include the option rdblacklist=name_of_driver, where name_of_driver is the driver that you need to blacklist. For example, to blacklist the driver named foobar: kernel /vmlinuz-2.6.32-71.18-2.el6.i686 ro root=/dev/sda1 rhgb quiet rdblacklist=foobar Save the file and exit vi. Create a new file under /etc/modprobe.d/ that contains the command blacklist name_of_driver. Give the file a descriptive name that will help you find it in future, and use the filename extension .conf. For example, to continue to blacklist the driver foobar when the root device is mounted, run: echo "blacklist foobar" >> /mnt/sysimage/etc/modprobe.d/blacklist-foobar.conf
Reboot the system. You no longer need to supply rdblacklist manually as a kernel option until you next update the default kernel. If you update the default kernel before the problem with the driver has been fixed, you must edit grub.conf again to ensure that the faulty driver is not loaded at boot time.
Chapter 37. Upgrading Your Current SystemRed Hat does not support in-place upgrades between any major versions of Red Hat Enterprise Linux. A major version is denoted by a whole number version change. For example, Red Hat Enterprise Linux 5 and Red Hat Enterprise Linux 6 are both major versions of Red Hat Enterprise Linux. In-place upgrades across major releases do not preserve all system settings, services or custom configurations. Consequently, Red Hat strongly recommends fresh installations when upgrading from one major version to another. Although upgrading from Red Hat Enterprise Linux 5 is technically possible, you are more likely to have a consistent experience by backing up your data and then installing this release of Red Hat Enterprise Linux 6 over your previous Red Hat Enterprise Linux installation. Upgrading your system installs updated versions of the packages which are currently installed on your system. The upgrade process preserves existing configuration files by renaming them with an .rpmsave extension (for example, sendmail.cf.rpmsave). The upgrade process also creates a log of its actions in /root/upgrade.log. However, note the following limitations before you choose to upgrade your system: Individual package configuration files may or may not work after performing an upgrade due to changes in various configuration file formats or layouts. If you have one of Red Hat's layered products (such as the Cluster Suite) installed, it may need to be manually upgraded after the Red Hat Enterprise Linux upgrade has been completed. Third party or ISV applications may not work correctly following the upgrade.
Procedure 37.1. Upgrading Your System Bring your system up to date using RHN. Back up any important data on the system. Reboot the system from a Red Hat Enterprise Linux 6 installation DVD or minimal boot media. Press the Esc key during the first 60 seconds to access the boot: prompt. Enter the kernel option linux upgradeany at the boot: prompt.
Some upgraded packages may require the installation of other packages for proper operation. If you choose to customize your packages to upgrade, you may be required to resolve dependency problems. Otherwise, the upgrade procedure takes care of these dependencies, but it may need to install additional packages which are not on your system. Chapter 38. Unregistering from Red Hat Subscription Management ServicesA system can only be registered with one subscription service. If you need to change which service your system is registered with or need to delete the registration in general, then the method to unregister depends on which type of subscription service the system was originally registered with. 38.1. Systems Registered with Red Hat Subscription ManagementSeveral different subscription services use the same, certificate-based framework to identify systems, installed products, and attached subscriptions. These services are Customer Portal Subscription Management (hosted), Subscription Asset Manager (on-premise subscription service), and CloudForms System Engine (on-premise subscription and content delivery services). These are all part of Red Hat Subscription Management. For all services within Red Hat Subscription Management, the systems are managed with the Red Hat Subscription Manager client tools. To unregister a system registered with a Red Hat Subscription Management server, use the unregister command. [root@server ~]# subscription-manager unregister --username=name This command must be run as root. 38.2. Systems Registered with RHN ClassicThere is no command to specifically unregister a system which is registered with RHN Classic. To delete the registration locally, remove the file with the system ID assigned to the system when it was registered: [root@server ~]# rm -rf /etc/sysconfig/rhn/systemid If the system is being unregistered in order to register it with Red Hat Subscription Management (Customer Portal Subscription Management, Subscription Asset Manager, or CloudForms System Engine), then instead of unregistering the system, use the rhn-migrate-classic-to-rhsm script to migrate the system and all its attached subscriptions to the specified Red Hat Subscription Management server. 38.3. Systems Registered with SatelliteFor a Satellite registration on the server, locate the system in the Systems tab and delete the profile. |
| |
