Extreme Networks Sentriant AG Software User's Manual page 324

System Administration
4 You can change the
the end-user sees in the access windows. This text also appears in the management user interface
when you run reports.
5 Every test must return a hash with the following keys:
status_code – 0 test did not run, error occurred, 1 test ran
result_code – pass, fail
result_message – the text to display to the user
NOTE
Do not change the status_code or the result_code for this example.
6 Once you have completed your edits and saved the
the following directory on the Sentriant AG MS:
/usr/local/nac/scripts/Custom/Tests
7 If you have created new base classes, copy them to the following directory on the Sentriant AG MS:
/usr/local/nac/scripts/Custom/BaseClasses
CAUTION
When updating or modifying files, use the Custom directory tree (Custom/BaseClasses, Custom/Tests). The Custom
directory tree is a mirror (with symbolic links) to the live test tree (scripts/BaseClasses and scripts/Tests). The live
tree is not modified directly, but is modified with the installCustomTests script and the RPM mechanism.
8 Once your custom test script is complete, and you are ready to push it out to all of the ESs, verify
that the scripts and base classes are under the Custom directory tree as specified above, and enter
the following on the command line of the Sentriant AG MS:
installCustomTests
This command compiles the Python source files, builds an RPM, updates the policy groups, and
sends these changes to all ESs. An example of the output from the
is shown as follows:
NOTE
This command affects all ESs, even those that are not currently up and running. Once a stopped ES comes back up,
the ES is updated.
324
result["result_message"]
to whatever text you want. This message is what
myCheckSoftwareNotAllowed.py
installCustomTests
Sentriant AG Software Users Guide, Version 5.3
file, copy it to
command