When you upgrade a secure VCS 6.x cluster to VCS 7.3, the upgrade does not migrate the old broker configuration to the new broker because of the change in architecture. Both the old broker (
/opt/VRTSat/bin/vxatd) and new broker (
/opt/VRTSvcs/bin/vcsauth/vcsauthserver/bin/vcsauthserver) continue to run. In such a scenario, you must consider the following:
The HA commands that you run in VCS 7.3 are processed by the new broker by default. To ensure that the HA commands are processed by the old broker, set the VCS_REMOTE_BROKER environment variable as follows:
# export VCS_REMOTE_BROKER=localhost IP,2821
VCS 7.3 does not prompt non-root users who run HA commands for passwords. In 6.x, non-root users required a password to run HA commands. If you want non-root users to enter passwords before they run HA commands, set the VCS_DOMAINTYPE environment variable to unixpwd.
Trust relationships are not migrated during the upgrade. If you had configured secure GCO or secure steward, ensure that trust relationships are recreated between the clusters and the steward.
For WPARs, the HA commands run within the container and use credentials that were deployed by the old broker. However, you can migrate to the newer credentials from the new broker by running hawparsetup again.
When the old broker is not used anymore, you can delete the old VRTSat fileset.