Patch-ID# 113880-01
Keywords: VxVM VCS Capacity Reporter 6.0.0
Synopsis: Various Veritas Volume Manager and Veritas Cluster Server Issues resolved.
Date: Mar/04/2003

Install Requirements: None                      
Solaris Release: 

SunOS Release: 

Unbundled Product: Resource Management Suite

Unbundled Release: 6.0

Xref: 

Topic: 

Relevant Architectures: sparc, i386

BugId's fixed with this patch: 4785166 4789087 4789107 4789113 4792351 4810798 4812636 4814942 4817341 4817343 4818249 4820470 4820783

Changes incorporated in this version: 4812636 4814942 4817341 4817343 
4818249 4820470 4820783 4789107

Patches accumulated and obsoleted by this patch: 

Patches which conflict with this patch: 

Patches required with this patch: 113285-03 or greater

Obsoleted by: 

Files included with this patch: 

README.113880-01 113880-01.exe solarisagent.tar.Z installsrm

Problem Description:

4785166 - Solaris Agent Fails To Show Veritas Volumes When Their Disks Are Non - Standard De
4789087 - Volume group free space reported incorrectly
4789113 - Veritas Volume Manager Volumes incorrectly reported RAID Levels
4792351 - Error message when there are no disks in a volume disks report contains incorrec
4810798 - Scans using VCS and enclosure - based names has missing or incorrect resources
4812636 - Missng disks that would have enclosure name but not under VxVM control.
4814942 - scanning VCS virtual server using disks not under volume manager control fails.
4817341 - A disk group with no volumes will mess up disk group's volume and disk listings
4817343 - A VXVM disk group with no volumes will mess up disk group's volume and disk list
4818249 - Disks in seperate VXVM disk groups using the same name cause inaccurate results
4820470 - Vxvm volumes report incorrect sizes
4820783 - Computer Scans Fail When Shares Are Not Mounted To The Full Volume Name
4789107 - Disks list under volume group does not always match the number of disks in volume
 
*Patch does not include any fixes for existing Solaris Volume Manager issues in the Capacity Reporter Solaris Agent. 
An update will be posted to Sun Solve at a later date.

Patch Installation Instructions:
-------------------------------- 
Download and unzip the file 113880-01.zip. Ther are two components to this patch a Windows SRM Server component and a solaris agent component.
 
For the Solaris Agent:
Download the Zip file 113875-01.zip.  Follow the Special Install Instructions below to install solarisagent.tar.Z.  
If there is a previous version of the Solaris Agent on the system to be upgraded, it is recommended that you use 
the 'pkgrm' utility to remove the old version before installing  the new one. After removing the exisitng version 
of the Agent, simply follow the steps below for installing the new version. The command to remove the old Solaris 
Agent package is as follows: pkgrm SUNWsrmag 
 
For the Capacity Reporter Server:
Copy the executable file 113880-01.exe to a Capacity Reporter Server of at least version 6.0.1.  Run the executable file.

Special Install Instructions:
----------------------------- 
Capacity Reporter Agent for Solaris
 
Capacity Reporter Agent for Solaris supports the VERITAS Cluster Server (VCS)
software environment, which lets the Agent scan and report on shared cluster
resources without counting them multiple times in Capacity Reporter Server reports.
You must follow configuration guidelines for the Agent to scan and report all shared
cluster resources properly.
If you are not running Capacity Reporter in a VCS environment, go to ?Install a Capacity Reporter Agent for Solaris?.
 
Before Installing a Capacity Reporter Agent for Solaris in the VERITAS Cluster Server Environment
 
Before you install Capacity Reporter Agent for Solaris in the VCS environment please note the following:
1. Install the Agent on all VCS cluster member nodes.
2. Configure all Agents in the cluster to use the same port number to communicate
with the Capacity Reporter Server.
3. Register the cluster itself with the Capacity Reporter Server using a unique cluster
alias, or name, to scan and report the shared cluster resources.
 
Also, you must determine the following:
1. A port number that is open on all member node systems that you can configure
the Agent to use.
2. Which member node is assigned the lowest LLT number in the cluster. This is the
system from which you must register the cluster with the Capacity Reporter
Server before any shared resources can be properly reported.
3. A suitable cluster alias for the cluster, which you use to register the cluster with
the Capacity Reporter Server. The installation procedure suggests a cluster alias.
Make sure that the cluster alias is not the same as another managed computer or
cluster alias on the Capacity Reporter Server. The cluster alias must be a properly
formatted computer system name that is unique on your network, however it
does not necessarily have to exist. The Capacity Reporter Server uses a proxy IP
address from your cluster to contact the Agent(s) in the cluster to perform scans
of shared resources.
4. Which IP address (that is associated with the cluster) the Capacity Reporter
Server will use as the proxy for scans of the cluster shared resources. The
installation procedure recommends the first service group IP address that it finds
as the default value, however this may not be the optimal choice for the proxy.
There are many ways to configure VCS clusters and cluster services, so selecting
the correct proxy is as much art is it is science. As a general guideline, select a
service group IP address that is capable of running on as many nodes in the
cluster as possible to allow the Capacity Reporter Server to take advantage of the
redundancy in the cluster.
 
Install a Capacity Reporter Agent for Solaris
 
Capacity Reporter Agent for Solaris can be installed with superuser privileges; no
additional privileged account information is required. Follow these steps to install
Capacity Reporter Agent for Solaris:
1. The Capacity Reporter Installation CD includes the unix_agents directory, which
contains the solarisagent.tar.z file of installation files for Solaris systems.
2. Copy or make accessible all the files from the proper directory on the Installation
CD to each target system. You can do this with FTP or through an NFS mount.
Note ? If you copy the files, you may delete them when Capacity Reporter is fully
installed.
3. Use chmod to make the installsrm script executable.
4. Type ./installsrm to unpack the installation files and start the pkgadd process.
Note ? You may also extract the package from the Solaris tar file and run pkgadd
manually.
5. If an earlier version of Capacity Reporter Agent exists, indicate whether you want
the installation procedure to remove the older version now. You can remove the
older installation at a later time by executing the command:
/usr/srmagent/removesrm.
6. The installation script proceeds with the following dialog. Accept the default
values or respond to the messages appropriately.
Enter the directory where SUNWsrmag will be installed [/opt]:
The Capacity Reporter Agent will be installed to
/opt/SUNWsrmag/6.0.0...
Enter the service name for the Capacity Reporter Agent to use [an
available service name]:
The Capacity Reporter Agent will be installed as service "an available
service name"...
Enter the network port number for the Agent to use [an available port
number]:
Port number an available port number will be reserved for use by the
Capacity Reporter Agent...
The installation procedure makes an entry in the /etc/services file and uses
the service name and port number you specified to reserve the port for use by the
Agent. You cannot specify a service name or port number that is already in use in
the /etc/services file.
7. Next, the installation procedure prompts you for a run mode; respond
appropriately. Note that inetd is the default run mode.
You must configure the Agent to start automatically in order
for the Capacity Reporter Server to be able to contact it. This
version of the Agent supports the following run modes:
inetd - AVAILABLE
xinetd - NOT DETECTED
daemon - AVAILABLE
Select an available run mode, (i)netd, (x)inetd or (d)aemon [i]:
8. You can now register the Agent with a Capacity Reporter Server or register it at a
later time by executing the registersrm command. Note that if you take the
installation path default, the command is
/opt/SUNWsrmagent/6.0.0/install/registersrm. If you choose to register
the Agent now, respond to the following prompts appropriately.
Do you want to enter Server registration information now? [y,n,?,q] y
Enter the name or IP address of the Server with which to register:
Enter the HTTP port to connect to on server server name [ 80]:
Enter the Capacity Reporter Service Login Account on server name
[SRMSvcUser]:
Enter the NT Domain for SRMSvcUser on server name:
Enter the password for account domain name\service on server name:
Re-enter the password for confirmation:
9. The installation procedure requires an IP address.
The Server requires an IP address for this system in order to contact
the Agent for scans. The installer can register the
correct IP address automatically in most cases, however if this
system has multiple IP addresses you may need to enter the
correct address manually.
Select (a)utomatic or (m)anual IP address selection [a]:
10. Enter a or m.
 If you enter a, the installation procedure selects an available IP address for
registration.
 If you enter m, the installation procedure prompts for an IP address.
Please enter the IP address that you wish to register with [IP
address]:
Note that if the system on which you install the Agent has multiple IP addresses
(that is, multi-homed) you may need to specify the correct IP address for the
Capacity Reporter Server to contact the Agent successfully.
11. The installation procedure redisplays your responses and prompts you with the
following:
Is this information correct? (y, n to re-enter, q to skip
registration)?
12. Enter y, n, or q.
 If you enter n, the script loops back in the procedure to allow you to change your
responses.
 If you enter q, you bypass the registration portion of the installation procedure.
 If you enter y, the installation procedure attempts the registration.
13. If the installation procedure detects VERITAS Cluster Server software on the
system, it attempts to determine if the system is assigned the lowest LLT number.
If your system is not the lowest-numbered LLT node, you need not supply
additional configuration information. Go to Step 19.
If your system is the lowest-numbered LLT node, you must supply additional
configuration information. The installation procedure prompts:
Do you want to enter cluster alias registration information now?
[y,n,?,q]
14. Enter y, n, or ?.
 If you enter n, you can register the cluster alias manually at a later time by
executing the registerca command Note that if you take the installation path
default, the command is /opt/SUNWsrmagent/6.0.0/install/registerca.
Note that if you choose to register the cluster alias after the agent installation,
your system may be more prone to errors. Go to Step 19.
 If you enter y, the installation procedure prompts for a cluster alias:
You must specify the name by which the Server will call
this cluster, also known as the cluster alias. The name
must not match the name of any computer or cluster that is
already managed by the Server with which you will be registering
the cluster.
The installer suggests the following cluster alias based on your
cluster configuration: "suggested cluster alias"
Enter a name to use as the cluster alias [vcseng1]:
15. Note that the installation procedure recommends a cluster alias name. Either
accept the default cluster alias or enter a different cluster alias.
The installation procedure then prompts for an IP address for the cluster alias:
You must specify an IP address through which the SRM Server will scan
the cluster "cluster alias" for shared resources. This IP address
can be the address of a member node, or one of the IP addresses
assigned to a service group in the cluster. You may enter the address
manually, or elect to have the installer automatically choose one from
the list of IP addresses assigned to service groups and/or member
nodes in this cluster.
Would you like the installer to select an IP address (a)utomatically,
or will you (m)anually enter one? [a,m,?]
16. Enter a or m.
 If you enter a, the installation procedure chooses an available IP address.
 If you enter m, the installation procedure displays a list of IP addresses from
which you can choose (note that this is the default and the recommended choice).
Enter an IP address at the dialog prompt.
17. The installation procedure redisplays your responses:
You have automatically/manually entered the following IP address to
be used as the proxy address by the Server when scanning cluster
"cluster alias":
IP address (computer name)
The cluster alias registration with Server "IP address" will
be attempted using the following information:
Cluster alias(name) is "cluster alias".
Cluster scan proxy IP address is "IP address".
Is this information correct (y, n to re-enter, q to skip
registration)? y
18. Enter y, n, or q.
 If you enter n, the script loops back to allow you to change your responses.
 If you enter q, the installation procedure does not register the cluster with a
Capacity Reporter Server, and continues with routine package verification. Note
that scans may not function properly until you complete this step.
 If you enter y, the installation procedure performs both the registration and
routine package verification.
19. After routine package verification, the dialog prompts:
Do you want to continue with the installation of <SUNsrmag> [y,n,?)
20. Enter y or n.
 If you enter n, the installation procedure exits and does not complete the Capacity
Reporter Agent for Solaris installation.
 If you enter y, the installation procedure executes preinstallation, installation, and
postinstallation scripts, and installs the Agent files on the system
21. The installation procedure displays installation and registration progress and
status messages:
Installation of <SUNWsrmag> was successful.
Note that if you receive a message that indicates the registration portion of the
installation procedure has failed, the installation itself is successful.
22. The installation procedure then removes temporary installation files, indicates
completion of the installation and returns you to the command line prompt.
Installation of <SUNWsrmag> was successful.
Removing temporary installation files
 
End of installsrm for Solaris
 
After Installing Capacity Reporter Agent for Solaris in a VCS Environment
The installation procedure is designed to configure the Agent correctly for execution
in a VCS cluster environment. However, if you skip the cluster alias registration, or
if errors occur during the registration of the cluster alias with the Capacity Reporter
Server from the node with the lowest LLT number, you can complete or correct the
configuration by running the following scripts:
 <install path>/SUNWsrmag/6.0.0/install/registerca on the node
with the lowest LLT number, which lets you register a cluster alias with a
Capacity Reporter Server.
 <install path>/SUNWsrmag/6.0.0/install/updatecaproxy, which
lets you update the proxy IP address information with a registered cluster alias
on a Capacity Reporter Server.
 
Readme Items for Solaris Agent:
Solaris Agent Upgrade Causes Disks to be Rediscovered
If you upgrade from a version 5.0.5 (or earlier) Solaris agent to the version 6.0.1 Solaris agent, 
subsequent scans "rediscover" existing disk drives. The original disk drives are reported as 
missing and will be removed by automatic, scheduled maintenance routines.
 
Solaris Agent Upgrade Installation Directory
When you upgrade a Solaris agent from version 6.0.0 to version 6.0.1, 
the installation directory remains 6.0.0.
 
Uninstall of Solaris Agent Running in Daemon Mode Does Not Delete Agent Process
If you uninstall a Solaris agent that is running in daemon mode, the daemon process is not deleted. 
You must delete the daemon process manually.

README -- Last modified date:  Tuesday, March 4, 2003

