000-221 · Question #57
An administrator has noticed that root receives email every day, stating that the Electronic Service Agent (ESA) has not been configured. The company does not use ESA and the administrator would…
The correct answer is A. Use SMIT to configure the Electronic Service Agent. Configuring Electronic Service Agent through SMIT marks it as configured and stops the daily warning emails sent to root, even if the organization does not actively use ESA's reporting features.
Question
An administrator has noticed that root receives email every day, stating that the Electronic Service Agent (ESA) has not been configured. The company does not use ESA and the administrator would like the daily emails to stop. How can this be achieved?
Options
- AUse SMIT to configure the Electronic Service Agent.
- BRemove the entry generating the email from root's crontab.
- CHave an IBM SSR add the ESA keys to the HMC.
- DOrder an MES for the system, specifying the feature code to refuse ESA.
How the community answered
(49 responses)- A84% (41)
- B8% (4)
- C6% (3)
- D2% (1)
Why each option
Configuring Electronic Service Agent through SMIT marks it as configured and stops the daily warning emails sent to root, even if the organization does not actively use ESA's reporting features.
The daily emails are generated by a cron-triggered check that detects ESA is in an unconfigured state. Running the ESA configuration wizard through SMIT (smitty esa_config or similar) completes the initial setup and sets the configured flag, which causes the check to stop generating warning messages. The company does not need to actively use ESA's IBM call-home features after configuring it - configuration simply satisfies the state check.
The ESA status check is typically scheduled in the system crontab or a dedicated cron file owned by the ESA subsystem, not in root's personal crontab, so editing root's crontab would not remove the offending job.
Adding ESA keys to the HMC is an IBM service action related to activating service contracts and would not resolve a local configuration warning generated on the AIX system itself.
Ordering a Machine-Executable Specification (MES) with a feature code is a hardware order process and has no mechanism to suppress software-level configuration warnings on a running AIX system.
Concept tested: AIX Electronic Service Agent configuration to suppress warnings
Source: https://www.ibm.com/docs/en/aix/7.2?topic=agent-electronic-service-overview
Topics
Community Discussion
No community discussion yet for this question.