000-221 · Question #149
The cfgmgr command appears to be taking an excessive time to complete. The administrator was able to quit the command and return to the command prompt. The administrator does not have access to the…
The correct answer is C. Re-issue the command with the W flag. Running cfgmgr with its verbose flag writes each configuration method name and return code to stdout, allowing the administrator to pinpoint exactly which device or method is causing the delay.
Question
The cfgmgr command appears to be taking an excessive time to complete. The administrator was able to quit the command and return to the command prompt. The administrator does not have access to the managing HMC and unable to check for any LED codes. How else can the cause of the observed delay be determined?
Options
- AReview the latest entry within /var/log/cfgdb.out.
- BStart the syslog daemon before re-issuing the command.
- CRe-issue the command with the W flag.
- DInitiate the ledmon command from a separate session, then re-issue cfgmgr.
How the community answered
(50 responses)- A4% (2)
- B10% (5)
- C84% (42)
- D2% (1)
Why each option
Running cfgmgr with its verbose flag writes each configuration method name and return code to stdout, allowing the administrator to pinpoint exactly which device or method is causing the delay.
/var/log/cfgdb.out does not exist as a standard AIX cfgmgr log path, so reviewing it would yield no useful output.
The syslog daemon logs kernel and application messages but cfgmgr does not write per-device timing or progress information to syslog, so starting it would not reveal the delay cause.
The cfgmgr -v flag (the verbose or 'W' output flag referenced in this context) causes the command to print each configuration method as it executes along with its exit status. Re-issuing the command with this flag lets the administrator watch in real time which step stalls, providing the diagnostic information that LED codes would otherwise supply.
The ledmon command monitors front-panel LED state changes and requires communication with a managing HMC or FSP; since HMC access is already unavailable, ledmon would not provide additional diagnostic data.
Concept tested: Using cfgmgr verbose flag for device configuration diagnostics
Source: https://www.ibm.com/docs/en/aix/7.3?topic=c-cfgmgr-command
Topics
Community Discussion
No community discussion yet for this question.