The following table lists the SunScreen ssadm sub-commands and their descriptions. Many ssadm sub-commands duplicate administration GUI functions, while others provide a context for other sub-commands.
Table A-2 SunScreen ssadm Sub-Command Summary
ssadm Sub-command |
Description |
---|---|
activate |
Activate a Screen policy. |
active |
List information about the currently active policy. |
algorithm |
List algorithms supported by SKIP. |
backup |
Write a SunScreen backup file to standard output. |
debug_level |
Set or clear the level of debugging output generated by a Screen. |
edit |
Run the SunScreen configuration editor. See Configuration Editor Sub-Command Summary. |
ha |
Configure the features of a High Availability (HA) Screen. |
lock |
Examine or remove the protection lock that the configuration editor places on a policy file. |
log |
Maintain the Screen log file. |
logdump |
Interpret Screen logs and displays their contents. |
login |
Authenticate a user for administrative access through ssadm to a Screen from a remote Administration Station. |
logmacro |
Expands SunScreen logmacro objects. |
logout |
Terminate the session created by ssadm login. |
logstats |
Print information about the SunScreen log. |
patch |
Install patch, as needed. |
policy |
Create, delete, list, rename Screen policies. |
product |
Print single line of descriptive SunScreen use. |
restore |
Read a backup file from standard input. |
securid |
Configure the client layer of the SecurID system. |
sys_info |
Print a description of running SunScreen software. |
traffic_stats |
Report summary information about the traffic flowing through the SunScreen, classified by interface. |
You maintain user-controlled data by using the edit command that is a sub-command of ssadm.
When you need to look at or change a policy in some way like Move or Delete, you invoke the configuration editor and enter a series of commands that end with save and quit requests.
Be sure to save change commands, such as add, del, rename, renamereference, insert, replace, and move, before you quit. Run save just before the quit command to avoid accumulating too many policy versions.