Manualshelf

H06.08 Release Version Update Compendium

ManualsBrandsHP ManualsServerHP Integrity NonStop Release and Migration
21222324252627282930
Manageability Products
H06.08 Release Version Update Compendium—543560-001
6-5
Fallback in a Safeguard Environment
Migration steps specific to the OSS ACL feature are:
1. Set the AUDIT-CLIENT-OSS attribute to ON. If you do not want to audit client
subsystems other than OSS, you can disable the AUDIT-CLIENT-GUARDIAN
attribute after migration.
2. Roll the audit file using the SAFECOM NEXTFILE command.
Fallback in a Safeguard Environment
The RVUs eligible for fallback from H06.08 are H06.06 and H06.07.
Fallback Considerations Specific to the Longer Password
Feature
Fallback requires advance planning because Standard Security now supports longer
passwords, which are not accepted by previous RVUs. When fallback is planned, the
super ID user password must contain eight or fewer characters. The fallback steps,
performed by the System Administrator, are as follows:
1. If the super ID user password is longer than 8 characters, set or change the
password to be contain 8 or fewer characters long with
PASSWORD-COMPATIBILITY-MODE set to ON.
2. Before starting Safeguard, log on using the shorter password.
3. If the value of the PASSWORD-MINIMUM-LENGTH attribute is greater than or
equal to 8, use the PWCONFIG utility to change it to a value less than or equal to
8.
4. Start Safeguard.
Users whose passwords contain eight or fewer characters long can successfully log on
after fallback because the previous RVUs support the shorter passwords.
For users whose passwords exceed eight characters, the system administrator must
reset their passwords to contain 8 or fewer characters.
Fallback Considerations Specific to the OSS ACL Feature
The Safeguard configuration attribute AUDIT-CLIENT-GUARDIAN, which is a synonym
for AUDIT-CLIENT-SERVICE, is no longer applicable after fallback. After fallback:
1. If OSS related operations are to be audited, the Safeguard configuration
attribute AUDIT-CLIENT-SERVICE must be enabled, if it is not already
enabled.
2. Roll the audit using the SAFECOM NEXTFILE command.