chsra

Use the chsra command to configure support assistance.

Syntax

Read syntax diagramSkip visual syntax diagram chsra -enable-disable-updatetoken-remotesupport enabledisabletest-idletimeout timeout_in_minutes

Parameters

-enable
(Optional) Creates remote access accounts and enables local support assistance.
-disable
(Optional) Deletes all remote access accounts and disables local and remote support assistance.
Note: Remote Support Assistance cannot be disabled on IBM Storage Virtualize for Public Cloud (SVPC) if multifactor authentication has been enabled for the superuser.
-updatetoken
(Optional) Updates the shared security token that is used for support assistance.
-remotesupport enable | disable | test
(Optional) Configures remote support assistance directly over the internet or by a configured Remote Support Proxy server. The values are:
  • enable
  • disable
  • test
No default value exists.
-idletimeout timeout_in_minutes
(Optional) Enables remote support for a limited amount of time (specified in minutes). The value must be a positive number (integer) denoting how many minutes remote support assistance is idle (and timed out). This parameter does not time out when a support session is in progress on any of your system nodes. It is renewed as many times as needed and only times out after all active sessions are terminated.
Remember: If the idle timeout expires on all participating nodes in a system, remote system support is disabled. If remote system support is disabled, remote system support is not automatically started on events that include:
  • When new nodes join the system.
  • T3 recovery procedures.
  • Node warm or cold starts.
If you specify -idletimeout, you must also specify -remotesupport.

Description

This command configures local or remote support assistance.
Note: Turn on both local and remote support assistance to more efficiently resolve any problems that are encountered.
Remote support assistance is available either directly over the internet or by using a Remote Support Proxy server. Remote system support is routed by using the Remote Support Proxy server if any Remote Support Proxy servers are configured.
Note:
  • Remote Support Proxy servers are deprecated. You can configure HTTP proxy servers instead by using mkproxy or chproxy command. You can configure your firewall to allow traffic to pass directly from the system or you can route traffic through an HTTP proxy server within your environment. Do not configure an HTTP proxy server by using the mksystemsupportcenter command. For more information, see HTTP proxy server.
  • With the addition of the HTTP proxy support, Remote Support Proxy servers are no longer necessary, but they are still supported for existing configurations. Alternately, a Remote Support Proxy can be configured to consolidate firewall traffic from a number of storage systems. Remote upgrades cannot be completed through the Remote Support Proxy server.
You must do the following to turn on remote support assistance:
  1. Configure service IP addresses on all nodes.
  2. Configure call home on the system.
  3. Configure local support assistance on your system, which creates support and sets up authentication. For storage systems that have direct access to the internet, the firewall must allow outbound connections to Internet Protocol (IP) addresses 170.225.126.11, 170.225.126.12, 170.225.127.11, and 170.225.127.12 on port 22 or 443. If you must use a Remote Support Proxy server, configure it by using the mksystemsupportcenter command.

    For remote access, port 443 is suggested as it provides more security. If the connection from port 443 remote access is unsuccessful, then port 22 is used as a backup. When you configure the firewall rules with port 443, the fallback of remote access from port 443 to port 22 is not applicable.

An invocation example for creating support assistance accounts and enabling local support assistance

chsra -enable

The detailed resulting output:

No feedback