Appliance conditions | No SSH/HTTPS channels | There is SSH/HTTPS channel already over IPv4 | There is SSH/HTTPS channel already over IPv6 |
SteelHead & SCC reachable over IPv4 and IPv6 | To establish an SSH/HTTPS channels: scc hostname <ip-address> scc enable | Until the existing SSH/HTTPS channel is broken explicitly the IPv4 SSH/HTTPS channel will continue to exist. Break the channels using the procedures described above. To reestablish the SSH/HTTPS channels: scc hostname <ip-address> scc enable | Until the existing SSH/HTTPS channel is broken explicitly the IPv6 SSH/HTTPS channel will continue to exist. Break the channels using the procedures described above. To reestablish the SSH/HTTPS channels: scc hostname <ip-address> scc enable |
SteelHead & SCC reachable over IPv4 only | To establish the SSH/HTTPS channel over IPv4: scc hostname <ip-address> scc enable | To establish the SSH/HTTPS channel over IPv4: scc hostname <ip-address> scc enable | Not applicable |
SteelHead & SCC reachable over IPv6 only | To establish the SSH/HTTPS channel over IPv6: scc hostname <ip-address> scc enable | Not applicable | To establish the SSH/HTTPS channel over IPv6: scc hostname <ip-address> scc enable |
Control | Description |
Primary DNS Server | Specify the IP address for the primary name server. The IP address can be either IPv4 or IPv6. For IPv6 specify an IP address using this format: eight 16-bit hexadecimal strings separated by colons, 128-bits. For example: 2001:38dc:0052:0000:0000:e9a4:00c5:6282 You don’t need to include leading zeros. For example: 2001:38dc:52:0:0:e9a4:c5:6282 You can replace consecutive zero strings with double colons (::). For example: 2001:38dc:52::e9a4:c5:6282 |
Secondary DNS Server | Optionally, specify the IP address for the secondary name server. |
Tertiary DNS Server | Optionally, specify the IP address for the tertiary name server. |
DNS Domain List | Specify an ordered list of domain names. If you specify domains, the system automatically finds the appropriate domain for each of the hosts that you specify in the system. |
Control | Description |
Add a New Host | Displays the controls for adding a new host. |
IP Address | Specify the IP address, either IPv4 or IPv6, for the host. For IPv6 specify an IP address using this format: eight 16-bit hexadecimal strings separated by colons, 128-bits. For example: 2001:38dc:0052:0000:0000:e9a4:00c5:6282 You don’t need to include leading zeros. For example: 2001:38dc:52:0:0:e9a4:c5:6282 You can replace consecutive zero strings with double colons (::). For example: 2001:38dc:52::e9a4:c5:6282 |
Hostname | Specify a hostname. |
Add | Adds the host. |
Remove Selected | Select the check box next to the name and click Remove Selected. |
Apply | Applies your settings to the running configuration. |
Control | Description |
Enable Proxy Settings | Provides network proxy access to the SteelHead. Enables the SteelHead to use a proxy to contact the Riverbed licensing portal and fetch licenses in a secure environment. You can optionally require user credentials to communicate with the proxy, and you can specify the method used to authenticate and negotiate user credentials. Proxy access is disabled by default. RiOS supports these proxies: Squid, Blue Coat Proxy SG, Microsoft WebSense, and McAfee Web Gateway. |
Web/FTP Proxy | Specify the IP address, either IPv4 or IPv6, for the network or FTP proxy. For IPv6 specify an IP address using this format: eight 16-bit hexadecimal strings separated by colons, 128-bits. For example: 2001:38dc:0052:0000:0000:e9a4:00c5:6282 You don’t need to include leading zeros. For example: 2001:38dc:52:0:0:e9a4:c5:6282 You can replace consecutive zero strings with double colons (::). For example: 2001:38dc:52::e9a4:c5:6282 |
Port | Optionally, specify the port for the network or FTP proxy. The default port is 1080. |
Enable Authentication | Optionally, select to require user credentials for use with network or FTP proxy traffic. Specify these values to authenticate the users: • User Name - Specify a username. • Password - Specify a password. • Authentication Type - Select an authentication method from the drop-down list: – Basic - Authenticates user credentials by requesting a valid username and password. This is the default setting. – NTLM - Authenticates user credentials based on an authentication challenge and response. – Digest - Provides the same functionality as basic authentication; however, digest authentication improves security because the system sends the user credentials across the network as a Message Digest 5 (MD5) hash. |
Proxy Whitelist | Optionally, add or remove domains from a proxy whitelist. |
Apply | Applies your changes to the running configuration. |