•schedule an appliance reboot or shut down.

•generate multiple TCP trace dumps on a specific date and time.

•Feature-tier licensing, available only on SteelHead CX580, CX780, and CX3080 models, provides license tiers that define the available features. For details, see Feature-tier licensing.

•Specification licensing, for all other SteelHead appliances, provides a license to define the appliance specifications, such as bandwidth capacity and number of optimized connections. For details, see Specification licensing.

•Connect a new SteelHead to the network.

•Purchase new downloadable licenses to replace the expired license.

•Replacing a SteelHead appliance - If you are replacing one SteelHead for another, you can import all of the network information (although not the licenses) and disconnect the old SteelHead before you switch configurations on the new SteelHead.

•Configuration template for a large deployment - You can avoid entering the complete SteelHead configuration for every appliance in a large deployment by setting up a template SteelHead and importing template settings to the configuration list.

•Admin - The system administrator user has full privileges. For example, as an administrator you may set and modify configuration settings, add and delete users, restart the optimization service, reboot the SteelHead, and create and view performance and system reports. The system administrator role allows you to add or remove a system administrator role for any other user, but not for yourself.

•Monitor - A monitor user may view reports, view user logs, and change their password. A monitor user can’t make configuration changes, modify private keys, view logs, or manage cryptographic modules in the system.

•Read-only - With read-only privileges you can view current configuration settings but you can’t change them.

•Read/Write - With read and write privileges you can view settings and make configuration changes for a feature.

•Deny - With deny privileges you can’t view settings or save configuration changes for a feature.

•Strong - Sets the password policy to more stringent enforcement settings. Selecting this template automatically prepopulates the password policy with stricter settings commonly required by higher security standards such as for the Department of Defense.

•Basic - Reverts the password policy to its predefined settings so you can customize your policy.

•The configured lockout time elapses.

•The administrator unlocks the account. RiOS never locks out administrator accounts.

•An administrator enables account control.

•The expiration time for a password elapses.

•An administrator disables a user account and then enables it.

•An administrator uses a CLI command to encrypt a password.

•restrict access to certain interfaces or protocols of a SteelHead.

•restrict inbound IP access to a SteelHead, protecting it from access by hosts that don’t have permission without using a separate device (such as a router or firewall).

•specify which hosts or groups of hosts can access and manage a SteelHead by IP address, simplifying the integration of SteelHeads into your network.

•It detects the IP address you are connecting from and displays a warning if you add a rule that denies connections to that address.

•It always allows the default SteelHead ports 7800, 7801, 7810, 7820, and 7850.

•It always allows a previously connected SCC to connect and tracks any changes to the IP address of the SCC to prevent disconnection.

•It converts well-known port and protocol combinations such as SSH, Telnet, HTTP, HTTPS, SNMP, and SOAP into their default management service and protects these services from disconnection. For example, if you specify protocol 6 (TCP) and port 22, the management ACL converts this port and protocol combination into SSH and protects it from denial.

•It tracks changes to default service ports and automatically updates any references to changed ports in the access rules.

•When you change the default port of services such as SSH, HTTP, HTTPS, on either the client-side or server-side SteelHead and create a management ACL rule denying that service, the rule will not work as expected. The SteelHead on the other end (either server or client) of an in-path deployment doesn’t know that the default service port has changed, and consequently optimizes the packets to that service port. To work around this problem, add a pass-through rule to the client-side SteelHead for the management interfaces. The pass-through rule prevents the traffic from coming from the local host when optimized.

•A management ACL rule that denies access from port 20 on the server-side SteelHead in an out-of-path deployment prevents data transfer using active FTP. In this deployment, the FTP server and client can’t establish a data connection because the FTP server initiates the SYN packet and the management rule on the server-side SteelHead blocks the SYN packet. To work around this problem:

•Generate the certificate and key pairs on the SteelHead. This method overwrites the existing certificate and key pair regardless of whether the previous certificate and key pair was self-signed or user added. The new self-signed certificate lasts for one year (365 days).

•Create certificate signing requests from the certificate and key pairs.

•Replace a signed certificate with one created by an administrator or generated by a third-party certificate authority.

•Copy the access code copied from the Management Console REST API Access page into the configuration file of your external script. The script uses the access code to make a call to the appliance or system to request an access token. The appliance/system validates the access code and returns an access token for use by the script. Generally the access token is kept by the script for a session only (defined within your script), but note that the script can make many requests using the same access token. These access tokens have some lifetime—usually around an hour—in which they’re valid. When they expire, the access code must fetch a new access token. The script uses the access token to make REST API calls with the appliance or system.