9.5.3 ahf configuration
Use the ahf configuration command to change AHF
configuration.
AHF 25.8
Automating Excluded Compliance Checks
AHF 25.8 introduces a new mechanism to automate the management of excluded compliance checks.
Previously, to skip certain checks in compliance reports, the excluded_check_ids.txt file had to be manually created on each node.
With this release, the process is automated, and updates are automatically propagated to all nodes.
- No need to manually create or distribute
excluded_check_ids.txtacross nodes. - Excluded check IDs can now be added, listed, replaced, or removed using the
ahf configurationcommands. - Changes are automatically propagated to all nodes.
Use case scenarios:
- When
excluded_check_ids.txtexists with valid checksTo print the excluded check IDs:
ahf configuration get --property ahf.compliance.excluded-check-idsExample output:
Excluded checks: ahf.compliance.excluded-check-ids: ['CHECKID1', 'CHECKID2', 'CHECKID3'] - When
excluded_check_ids.txtdoes not existTo exclude a check ID:
ahf configuration set --property ahf.compliance.excluded-check-ids --value CHECKID2Example output:
Successfully updated.This creates or updates the
excluded_check_ids.txtfile. - Overwriting the list of excluded checks
If the file already exists with valid checks, you can replace the list:
ahf configuration set --property ahf.compliance.excluded-check-ids --value CHECKID3 --replaceExample output:
Excluded checks: Successfully updated.This replaces the existing list with the new check ID(s).
- Unsetting excluded checks
To remove specific excluded checks:
ahf configuration unset --type compliance --excluded-check-ids LIST_OF_EXCLUDED_CHECKSTo unset all excluded checks:
ahf configuration reset --property ahf.compliance.excluded-check-ids
AHF 25.5
Upgrade Configuration Management
The AHF commands for managing upgrade configurations have been replaced with new SDK CLI commands. You are encouraged to transition to the new SDK CLI commands, as the existing ahfctl commands will be deprecated and be removed in a future release.
ahfctl command line, which is also slated for deprecation, currently provides the following commands for managing AHF upgrades:
ahf configuration command category, offering a simplified way to manage AHF upgrade configurations. However, to ensure compatibility with future releases and to benefit from enhanced functionality, you must adopt the new SDK CLI commands for upgrade management.
- To set AHF upgrade configuration parameters, run:
ahf configuration set --type upgrade [--software-stage SOFTWARE_STAGE] [--auto-upgrade AUTO_UPGRADE] [--upgrade-time UPGRADE_TIME][--file-system-type FILE_SYSTEM_TYPE] [–temporary-location TEMPORARY_LOCATION] [--remove-installer REMOVE_INSTALLER] [–frequency FREQUENCY] [--service-name SERVICE_NAME] [--auto-update AUTO_UPDATE] - To get AHF upgrade configuration parameter details, run:
ahf configuration get --type upgrade [--to-json] - To unset AHF upgrade configuration parameters, run:
ahf configuration unset --type upgrade [--software-stage SOFTWARE_STAGE] [--auto-upgrade AUTO_UPGRADE] [--upgrade-time UPGRADE_TIME][--file-system-type FILE_SYSTEM_TYPE] [–temporary-location TEMPORARY_LOCATION] [--remove-installer REMOVE_INSTALLER] [–frequency FREQUENCY] [--service-name SERVICE_NAME] [--auto-update AUTO_UPDATE]
AHF 25.1
Update Configuration Management
The AHF commands for managing update configurations have been replaced with new SDK CLI commands. You are encouraged to transition to the new SDK CLI commands, as the existing ahfctl commands will be deprecated and be removed in a future release.
ahfctl command line, which is also slated for deprecation, currently provides the following commands for managing AHF updates:
ahf configuration command category, offering a simplified way to manage AHF update configurations. However, to ensure compatibility with future releases and to benefit from enhanced functionality, you must adopt the new SDK CLI commands for update management.
- To set AHF update configuration parameters, run:
ahf configuration set --type update [--all] [--software-stage SOFTWARE_STAGE] [--auto-update AUTO_UPDATE] [--file-system-type FILE_SYSTEM_TYPE] [–frequency FREQUENCY] [--service-name SERVICE_NAME] [--update-time UPDATE_TIME] - To get AHF update configuration parameter details, run:
ahf configuration get --type update --all - To unset AHF update configuration parameters, run:
ahf configuration unset [--all] [--software-stage SOFTWARE_STAGE] [--auto-update AUTO_UPDATE] [--file-system-type FILE_SYSTEM_TYPE] [–frequency FREQUENCY] [--service-name SERVICE_NAME] [--update-time UPDATE_TIME]
Syntax: ahf configuration
ahf configuration action [options]| Actions | Description |
|---|---|
|
|
Sets configuration property and value. |
|
|
Gets configuration property and value. |
|
|
Unsets configuration property and value. |
|
|
Checks configuration. |
ahf configuration set
ahf configuration set --type CONFIGURATION_TYPE [OPTIONS]| Parameter | Description |
|---|---|
|
|
Show this help and exit. |
|
|
Specify to display the output in JSON format. |
|
|
Specify the type of configuration to access. |
|
|
Specify the name of the component or configuration. |
|
|
Specify the name of the property to set. |
|
|
Specify the value of the property. |
|
|
Note: Running this command will prompt you to enter the password for the Oracle Enterprise Manager repository user. The Oracle Enterprise Manager repository user can be any Enterprise Manager (EM) user with Target Privilege: View any Target. AHF Balance connects to an EM repository instance as the specified user.
For example: Ensure that Transparent Application Failover (TAF) is not enabled for this service. |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Specify the node name to configure a cell or the For example:
Note: Configurations set through the AHF CLI are securely stored in the AHF wallet.
|
|
|
|
|
|
|
|
|
|
|
|
CPU range of values: 0.5 <= value <= max_value
Kmem range of values: 1600 <= value <= max_value
SWMEM range of values: 1600 <= value <= max_value
|
Note:
--user-nameis the Oracle Enterprise Manager Repository user name if--type impact--user-nameis the API registration user if--type fleet-insights--user-nameis the upload configuration user if--type upload--user-nameis the GoldenGate service manager user if--type goldengate--nameis the component name if--type repository--nameis the configuration name if--type goldengate
Values supported for --property:
- Repository properties:
reposizeMBrepositorydir
- Global properties:
gather_ahf_feature_usage - User properties:
ahf.insights.max-collection-intervalahf.collectors.enhanced_os_metrics
- Resource limit properties:
ahf.tfa.resource-cpuahf.tfa.resource-kmemahf.tfa.resource-swmem
- Excluded check IDs:
ahf.compliance.excluded-check-ids
Syntax: ahf configuration get
ahf configuration get [OPTIONS]| Parameter | Description |
|---|---|
|
|
Specify the type of configuration to get. Valid values:
|
|
|
Specify unique configuration name for |
|
|
Specify the name of the property. |
|
|
|
|
|
Specify the node name to get the configuration status of a cell or the For example:
|
|
|
|
|
|
|
|
|
|
Syntax: ahf configuration check
ahf configuration check [OPTIONS]| Parameter | Description |
|---|---|
|
|
Specify the type of configuration to check. |
|
|
Specify to display the output in JSON format. |
|
|
Specify configuration name to check if |
|
|
Specify the node name to validate the configuration of a cell or the For example:
Note: Use the--to-json flag to get status of cells configuration in JSON format.
|
|
|
|
Syntax: ahf configuration unset
ahf configuration unset [OPTIONS]| Parameter | Description |
|---|---|
|
|
Specify the type of configuration to unset. |
|
|
|
|
|
|
|
|
|
|
|
Specify the node name to delete the configuration a cell or the For example:
|
|
|
|
|
|
|
|
|
|
Syntax: AHF Balance
ahf configuration set --type CONFIGURATION_TYPE [OPTIONS]
Parameters
Table 9-128 ahf configuration set Command Parameters
| Parameter | Description |
|---|---|
|
|
Show this help and exit. |
|
|
Specify the type of configuration ( |
|
|
Specify the connect string for the Oracle Enterprise Manager repository. |
|
|
Specify Oracle Enterprise Manager repository user name. |
Note:
Running this command will prompt you to enter the password for the Oracle Enterprise Manager repository user. The Oracle Enterprise Manager repository user can be any Enterprise Manager (EM) user with Target Privilege: View any Target. AHF Balance connects to an EM repository instance as the specified user.
Parent topic: Running Unified AHF CLI Administration Commands
9.5.3.1 Store Exadata Infrastructure Details for Best Practice Checking
The ahf CLI stores the details of Exadata Dom0s, storage servers, and switches. These stored details are subsequently used for Best Practice checks.
AHF may not discover all Exadata infrastructure when run on Dom0. As a result, Best Practice checks might miss peer Dom0s, storage servers, and switches.
The ahf CLI provides the ability to save the details of Exadata Dom0s, storage servers, and switches, using the command:ahf configuration set --type cell --node {nodename} --password. The Best Practice checks will then use this saved configuration for full infrastructure analysis.
AHF discovers peer DomUs from the Oracle Cluster Registry. By merging Oracle Exachk reports from DomU and Dom0, it provides a comprehensive report for the entire Exadata rack.
To merge Oracle Exachk reports, run exachk -merge report_1,report_2.
Parent topic: ahf configuration