Sponsored Content
Operating Systems AIX Uninstall native MPIO driver on AIX Post 302415234 by zxmaus on Thursday 22nd of April 2010 04:24:45 AM
Old 04-22-2010
Why do you want to deinstall it at all - if it is because you want to use something like powerpath or EMC MPIO instead, you don't have to deinstall the native MPIO - you only need to drop disks, adapters and so on , than install the powerpath software and reboot the system - when it comes up, it will use powerpath instead of MPIO.

Hope this helps
zxmaus
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

AIX MPIO and EMC

We are looking at running MPIO for it's redundancy and load balancing benefits. Does anyone know what pieces of software or modules are needed on the VIO server to get load balancing to work. Remember we are using EMC's DMX3500 storage system. We no longer want to use Powerpath. :rolleyes: ... (2 Replies)
Discussion started by: vxg0wa3
2 Replies

2. Solaris

Perl - How to uninstall? Will pkgrm uninstall all versions?

Hello, I'm working on a Solaris 9/Sparc machine and it has the Solaris 10 version of Perl (5.8.8) installed on it, which always requires all kinds of library files that Solaris 9 doesn't come with. I think the best way to do is to uninstall this wrong version and install the correct Solaris 9... (1 Reply)
Discussion started by: alanlh
1 Replies

3. AIX

AIX 5.3 MPIO vs RDAC on DS4000 range

Hi I would like to ask what the benefits are of changing from RDAC to MPIO when connecting to a DS4000 on AIX 5.3? I have heard that IBM MPIO "might" support more than 1 active path to a LUN when connecting to a DS4800 through more than 1 host connection on the same AIX client. I understand that... (8 Replies)
Discussion started by: kimyo
8 Replies

4. AIX

AIX native MPIO

Hi folks, does anybody have a link to a documentation how to implement native MPIO on AIX? We are using EMC PowerPath and Datacore SanSymphony/Cambex for this so far and I wasn't able to find a good description on that topic. All I know so far is that mkpath, chpath and lspath are used to... (3 Replies)
Discussion started by: zaxxon
3 Replies

5. AIX

MPIO Driver

On a particular LPAR, I was running AIX 5.3 TL 3. On Monday I did an update of the LPAR to 5.3 TL 9 SP2. The install was smooth, but then I ran into a problem. The MPIO driver does not work with LSI's StoreAge (SVM4). I did some looking, and looks like 5.3 TL3 = IBM.MPIO 5.3.0.30 5.3... (0 Replies)
Discussion started by: clking
0 Replies

6. AIX

Upgrading from native MPIO to SDDPCM AIX 6.1

We have AIX 6.1 system attached to SAN disks (DS4700 and DS8100) thru SVC. Initially when the system was I forgot to install sddpcm drivers. and wanted to know how can i go with the installation of the sddpcm drivers. My understandin going thru the manual ... (3 Replies)
Discussion started by: mk8570
3 Replies

7. AIX

Uninstall and reinstall AIX

Hi All, Currently I have a machine running on AIX5.3 (standalone). I plan to remove this AIX5.3 and install with new AIX6.1. This is a testing server so no backup are required. I just want to know, what is the best way to do this. For your information, I'm still new in AIX, so i dont have much... (1 Reply)
Discussion started by: aremint
1 Replies

8. AIX

AIX native SNMP producing limited results when walking MIB tree

The company I work for has various AIX servers that I've recently migrated to AIX 7.1 (from 6.1). Some are powerHA clusters some are not. Likewise, the systems engineer that I replaced had net-snmp installed on said clustered systems. Long story short I am re-invoking AIX's native SNMP (v3) for... (1 Reply)
Discussion started by: davix
1 Replies

9. AIX

issue AIX MPIO path closed

Hello, I have encountered the issue on my AIX 6.1. As you can see below, the hdisk1 & hdisk8 are not recognized by the system / > lspv hdisk0 00fa6d1288c820aa rootvg active hdisk1 00fa6d1288c8213c None hdisk2 ... (9 Replies)
Discussion started by: Phat
9 Replies

10. UNIX for Beginners Questions & Answers

Native AIX TL Upgrade on a VIO Server

What happens if we perform a Native AIX TL Upgrade on a VIO server? I mean instead of updateios I logged into oem_setup_env and ran a update_all to a new TL. (2 Replies)
Discussion started by: wibhore
2 Replies
PKG_DELETE(1)						    BSD General Commands Manual 					     PKG_DELETE(1)

NAME
pkg_delete -- a utility for deleting previously installed software package distributions SYNOPSIS
pkg_delete [-ADFfkNnORrVv] [-K pkg_dbdir] [-P destdir] [-p prefix] pkg-name ... DESCRIPTION
The pkg_delete command is used to delete packages that have been previously installed with the pkg_add(1) command. The given packages are sorted, so that the dependencies needed by a package are deleted after the package. Before any action is executed, pkg_delete checks for packages that are marked as preserved or have depending packages left. If the -k flag is given, preserved packages are skipped and not removed. Unless the -f flag is given, pkg_delete stops on the first error. WARNING
Since the pkg_delete command may execute scripts or programs provided by a package file, your system may be susceptible to ``Trojan horses'' or other subtle attacks from miscreants who create dangerous package files. You are advised to verify the competence and identity of those who provide installable package files. For extra protection, examine all the package control files in the package record directory <PKG_DBDIR>/<pkg-name>/). Pay particular attention to any +INSTALL or +DEINSTALL files, and inspect the +CONTENTS file for @cwd, @mode (check for setuid), @dirrm, @exec, and @unexec directives, and/or use the pkg_info(1) command to examine the installed package control files. OPTIONS
The following command line options are supported: pkg-name ... The named packages are deinstalled, wildcards can be used, see pkg_info(1). If no version is given, the one currently installed will be removed. If the -F flag is given, one or more (absolute) filenames may be specified and the package database will be consulted for the package to which the given file belongs. These packages are then deinstalled. -A Recursively remove all automatically installed packages that were needed by the given packages and are no longer required. Does not remove manually installed packages; see also the -R flag. -D If a deinstallation script exists for a given package, do not execute it. -F Any pkg-name given will be interpreted as pathname which is subsequently transformed in a (real) package name via the package data- base. That way, packages can be deleted by giving a filename instead of the package-name. -f Force removal of the package, even if a dependency is recorded or the deinstall script fails. This might break the package database; see pkg_admin(1) on how to repair it. -ff Force removal of the package, even if the package is marked as a preserved package. Note that this is a dangerous operation. See also the -k option. -K pkg_dbdir Override the value of the PKG_DBDIR configuration option with the value pkg_dbdir. -k Silently skip all packages that are marked as preserved. -N Remove the package's registration and its entries from the package database, but leave the files installed. Don't run any deinstall scripts or @unexec lines either. -n Don't actually deinstall a package, just report the steps that would be taken. -O Only delete the package's entries from the package database; do not touch the package or its files itself. -P destdir Prefix all file and directory names with destdir. For packages without install scripts this has the same behavior as using chroot(8). -p prefix Set prefix as the directory in which to delete files from any installed packages which do not explicitly set theirs. For most pack- ages, the prefix will be set automatically to the installed location by pkg_add(1). -R Recursively remove all packages that were needed by the given packages and are no longer required. This option overrides the -A flag. -r Recursively remove all packages that require one of the packages given. -V Print version number and exit. -v Turn on verbose output. TECHNICAL DETAILS
pkg_delete does pretty much what it says. It examines installed package records in <PKG_DBDIR>/<pkg-name>, deletes the package contents, and finally removes the package records. If a package is required by other installed packages, pkg_delete will list those dependent packages and refuse to delete the package (unless the -f option is given). If a package has been marked as a preserved package, it will not be able to be deleted (unless more than one occurrence of the -f option is given). If a filename is given instead of a package name, the package of which the given file belongs to can be deleted if the -F flag is given. The filename needs to be absolute, see the output produced by the pkg_info(1) -aF command. If a deinstall script exists for the package, it is executed before and after any files are removed. It is this script's responsibility to clean up any additional messy details around the package's installation, since all pkg_delete knows how to do is delete the files created in the original distribution. The deinstall script is called as: deinstall <pkg-name> VIEW-DEINSTALL before removing the package from a view, and as: deinstall <pkg-name> DEINSTALL before deleting all files and as: deinstall <pkg-name> POST-DEINSTALL after deleting them. Passing the keywords VIEW-DEINSTALL, DEINSTALL, and POST-DEINSTALL lets you potentially write only one program/script that handles all aspects of installation and deletion. All scripts are called with the environment variable PKG_PREFIX set to the installation prefix (see the -p option above). This allows a package author to write a script that reliably performs some action on the directory where the package is installed, even if the user might have changed it by specifying the -p option when running pkg_delete or pkg_add(1). The scripts are also called with the PKG_METADATA_DIR environment variable set to the location of the +* meta-data files, and with the PKG_REFCOUNT_DBDIR environment variable set to the location of the package reference counts database directory. If the -P flag was given to pkg_delete, PKG_DESTDIR will be set to destdir. ENVIRONMENT
See pkg_install.conf(5) for options, that can also be specified using the environment. SEE ALSO
pkg_add(1), pkg_admin(1), pkg_create(1), pkg_info(1), pkg_install.conf(5) pkgsrc(7) AUTHORS
Jordan Hubbard most of the work John Kohl refined it for NetBSD Hubert Feyrer NetBSD wildcard dependency processing, pkgdb, recursive "down" delete, etc. Joerg Sonnenberger Rewrote most of the code to compute correct order of deinstallation and to improve error handling. BSD
January 20, 2010 BSD
All times are GMT -4. The time now is 01:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy