HPE6-A84 · Question #57
Refer to the scenario. An organization wants the AOS-CX switch to trigger an alert if its RADIUS server (cp.acnsxtest.local) rejects an unusual number of client authentication requests per hour…
The correct answer is D. Defining a parameter and referring to it (self ^ramsfname]) for the value. This is because a parameter is a variable that can be defined and modified by the user or the script, and can be used to customize the behavior and output of the NAE script. A parameter can be referred to by using the syntax self ^ramsfname], where ramsfname is the name of the…
Question
Refer to the scenario. An organization wants the AOS-CX switch to trigger an alert if its RADIUS server (cp.acnsxtest.local) rejects an unusual number of client authentication requests per hour. After some discussions with other Aruba admins, you are still not sure how many rejections are usual or unusual. You expect that the value could be different on each switch. You are helping the developer understand how to develop an NAE script for this use case. The developer explains that they plan to define the rule with logic like this: monitor > value However, the developer asks you what value to include. What should you recommend?
Options
- AChecking one of the access switches' RADIUS statistics and adding 10 to the number listed for
- BDefining a baseline and referring to it for the value
- CUsing 10 (per hour) as a good starting point for the value
- DDefining a parameter and referring to it (self ^ramsfname]) for the value
How the community answered
(24 responses)- A8% (2)
- B13% (3)
- C25% (6)
- D54% (13)
Explanation
This is because a parameter is a variable that can be defined and modified by the user or the script, and can be used to customize the behavior and output of the NAE script. A parameter can be referred to by using the syntax self ^ramsfname], where ramsfname is the name of the parameter. By defining a parameter for the value, the developer can make the NAE script more flexible and adaptable to different scenarios and switches. The parameter can be set to a default value, such as 10, but it can also be changed by the user or the script based on the network conditions and requirements. For example, the parameter can be adjusted dynamically based on the average or standard deviation of the number of rejects per hour, or based on the feedback from the user or other admins. This way, the NAE script can trigger an alert only when the number of rejects is truly unusual and not just arbitrary.
Topics
Community Discussion
No community discussion yet for this question.