A team member has admin partition permissions but cannot use aaad.debug in the CLI. What is the likely reason?

A team member has admin partition permissions but cannot use aaad.debug in the CLI. What is the likely reason?

• A. The team member is NOT using the CLI correctly.
• B. The team member needs to troubleshoot from the GUI.
• C. The team member does NOT have permission to use the CLI.
• D. The team member does NOT have shell access by design.

Answer: (D)

The important idea here is that admin rights for partitions don’t automatically grant access to the underlying shell where diagnostic commands live. The aaad.debug command is a shell-level diagnostic tool for the AAA daemon, and running it requires direct shell access to the appliance. By design, many admin accounts are allowed to manage partitions and use the NetScaler/ADC CLI, but they don’t have shell access. Without that shell access, you can’t execute aaad.debug, even if you have partition admin permissions. If you need to run this diagnostic, you must obtain shell access (or have someone with shell access run it) in accordance with security policies.

The important idea here is that admin rights for partitions don’t automatically grant access to the underlying shell where diagnostic commands live. The aaad.debug command is a shell-level diagnostic tool for the AAA daemon, and running it requires direct shell access to the appliance. By design, many admin accounts are allowed to manage partitions and use the NetScaler/ADC CLI, but they don’t have shell access. Without that shell access, you can’t execute aaad.debug, even if you have partition admin permissions. If you need to run this diagnostic, you must obtain shell access (or have someone with shell access run it) in accordance with security policies.