Storage Foundation 7.4.1 Configuration and Upgrade Guide - Solaris
- Section I. Introduction and configuration of Storage Foundation
- Section II. Upgrade of Storage Foundation
- Planning to upgrade Storage Foundation
- About the upgrade
- Supported upgrade paths
- Preparing to upgrade SF
- Using Install Bundles to simultaneously install or upgrade full releases (base, maintenance, rolling patch), and individual patches
- Upgrading Storage Foundation
- Performing an automated SF upgrade using response files
- Upgrading SF using Boot Environment upgrade
- Performing post-upgrade tasks
- Optional configuration steps
- Recovering VVR if automatic upgrade fails
- Resetting DAS disk names to include host name in FSS environments
- Upgrading disk layout versions
- Upgrading VxVM disk group versions
- Updating variables
- Setting the default disk group
- Upgrading the Array Support Library
- Converting from QuickLog to Multi-Volume support
- Verifying the Storage Foundation upgrade
- Planning to upgrade Storage Foundation
- Section III. Post configuration tasks
- Section IV. Configuration and Upgrade reference
- Appendix A. Installation scripts
- Appendix B. Configuring the secure shell or the remote shell for communications
- About configuring secure shell or remote shell communication modes before installing products
- Manually configuring passwordless ssh
- Setting up ssh and rsh connection using the installer -comsetup command
- Setting up ssh and rsh connection using the pwdutil.pl utility
- Restarting the ssh session
- Enabling and disabling rsh for Solaris
Starting and enabling the configuration daemon
The VxVM configuration daemon (vxconfigd) maintains VxVM disk and disk group configurations. The vxconfigd communicates configuration changes to the kernel and modifies configuration information stored on disk.
Startup scripts usually invoke vxconfigd at system boot time. The vxconfigd daemon must be running for VxVM to operate properly.
The following procedures describe how to check that vxconfigd is started, whether it is enabled or disabled, how to start it manually, or how to enable it as required.
To determine whether vxconfigd is enabled, use the following command:
# vxdctl mode
The following message indicates that the vxconfigd daemon is running and enabled:
mode: enabled
This message indicates that vxconfigd is not running:
mode: not-running
This message indicates that vxconfigd is running, but not enabled:
mode: disabled
To start the vxconfigd daemon, enter the following command:
# vxconfigd
To enable the vxconfigd daemon, enter the following command:
# vxdctl enable
Once started, vxconfigd automatically becomes a background process.
By default, vxconfigd writes error messages to the console. However, you can configure it to write errors to a log file. For more information, see the vxconfigd(1M) and vxdctl(1M) manual pages.