chsvc - change a service
Synopsis
Description
Options
Examples
Environment
Bugs
Author
See Also
To start or stop monitoring managed systems using SNMP:
chsvc -s snmp -o {start | stop} [-m managed-system] [--help]To add or remove a network management system to or from the SNMP trap notification list:
chsvc -s snmp -o {add | remove} --ip IP-address
[--traps trap-list] [--help]To start, stop, or restart the cloud connector:
chsvc -s cloudconn -o {start | stop | restart} [-k key]
[--http proxy-URI] [--socks proxy-URI]
[--auth {kerberos | ldap | digest-md5 | basic}]
[--addcert] [--purge] [--help]
chsvc changes the configuration of a service, such as SNMP or cloud connector, on the Hardware Managment Console (HMC).
-s The service for which to change the configuration. Valid values are snmp for Simple Network Management Protocol (SNMP) version 3, and cloudconn for the cloud connector. -o The operation to perform. Specify start to start monitoring managed systems on the HMC using SNMP. If the SNMPv3 agent is not already running on the HMC, it will be started. In addition, Virtual Local Area Network (VLAN) statistics collection for the managed systems will be enabled, and the sample rate will be set to 1 minute. The chstat command can be used to change the sample rate.
Specify start to start the cloud connector on the HMC.
Specify stop to stop monitoring managed systems on the HMC using SNMP. Also, VLAN statistics collection for the managed systems will be disabled. In addition, if there are no remaining managed systems on the HMC that are being monitored, the SNMPv3 agent on the HMC will be stopped.
Specify stop to stop the cloud connector on the HMC.
Specify add to add a network management system to the SNMP trap notification list.
Specify remove to remove a network management system from the SNMP trap notification list.
Specify restart to stop then start the cloud connector on the HMC.
-m The name of the managed system to start or stop being monitored by the SNMPv3 agent on the HMC. The name may either be the user-defined name for the managed system, or be in the form tttt-mmm*sssssss, where tttt is the machine type, mmm is the model, and sssssss is the serial number of the managed system. The tttt-mmm*sssssss form must be used if there are multiple managed systems with the same user-defined name. If this option is not specified for a start operation, then a maximum of five of the systems currently managed by the HMC will be monitored. If this option is not specified for a stop operation, then monitoring for all managed systems will be stopped.
--ip The IP address or host name of the network management system to add to or remove from the SNMP trap notification list. --traps A list of traps to send to the network management system. If multiple traps are specified, they must be comma separated. For a list of all of the traps supported by the SNMPv3 agent on the HMC, run the lssvc -s snmp -r trapnames command.
This option is required when adding a network management system to the SNMP trap notification list. This option is not valid otherwise.
-k The cloud connector key. This key is obtained from the Cloud Management Console Portal settings page under the Cloud Connector tab. This option is required when starting or restarting the cloud connector. This option is not valid otherwise.
--http The HTTP proxy URI. This URI must be specified in the format [user-ID:[password]@]host-name[:port]. If password is omitted, you will be prompted to enter the password. If port is omitted, it will default to 3128. host-name can either be the host name or IP address of the HTTP proxy server. This option is only valid when starting or restarting the cloud connector.
--socks The SOCKS proxy URI. This URI must be specified in the format [user-ID:[password]@]host-name[:port]. If password is omitted, you will be prompted to enter the password. If port is omitted, it will default to 1080. host-name can either be the host name or IP address of the SOCKS proxy server. This option is only valid when starting or restarting the cloud connector.
--auth The user authentication type for the proxy connection. Valid values are kerberos for remote Kerberos authentication, ldap for remote LDAP authentication, digest-md5 for digest authentication, and basic for basic authentication. If this option is omitted when starting or restarting the cloud connector with a proxy, the user authentication type defaults to basic.
This option is only valid when starting or restarting the cloud connector with a proxy.
--addcert The cloud connector must connect to cloud endpoints to start successfully. These endpoints are specified on the Cloud Management Console Portal settings page under the Cloud Connector tab. If the cloud connector encounters a non-trusted certificate chain in this communication path due to a proxy or a company’s network firewall settings, these non-trusted certificates must be added to the HMC’s truststore to enable communication between the cloud connector and the cloud endpoints. Specifying this --addcert option will automatically add the required certificates to the HMC’s truststore. Alternatively the user can run the chhmccert command to add the required certificates to the HMC’s truststore prior to starting or restarting the cloud connector. This option is only valid when starting or restarting the cloud connector.
--purge Specify this option to purge all data associated with this HMC in the cloud when the cloud connector is stopped. This option is only valid when stopping the cloud connector.
--help Display the help text for this command and exit.
Start the SNMPv3 agent on the HMC if it is not already running, and start monitoring managed system sys1:chsvc -s snmp -o start -m sys1
Stop monitoring managed system sys1 and stop the SNMPv3 agent on the HMC if no other managed systems are being monitored:
chsvc -s snmp -o stop -m sys1
Stop monitoring all managed systems and stop the SNMPv3 agent on the HMC:
chsvc -s snmp -o stop
Add notification of the network management system with IP address 9.3.99.100 of the linkUp and linkDown traps:
chsvc -s snmp -o add --ip 9.3.99.100 --traps linkUp,linkDown
Remove notification of the network management system with IP address 9.3.99.100:
chsvc -s snmp -o remove --ip 9.3.99.100
Start the cloud connector on the HMC. You will be prompted to enter the password for socksUser1:
chsvc -o start -s cloudconn --socks socksUser1:@socks.proxy.com:8080
-k DxyzUFBhMVVYZ0hOeV1232FtVi03aERFdkI4NURoTG0yMTc1dHMyZGlMYU02ZabcSD
V5ZEJRNFc2N3l3eU1EanNtTlExVXdZSENzc292cHAxZ95AzdR9elFfZzBYNnY1UjB1LUh
vVGdjVEFXWUVVM2lWYWJkb1hsT3lzSW1Fa634R2xhd0lXcGtQYnFXb054MUF5WGs2UkxF
S0ZUZ2Y1OFNJNDBRLWgzWE5DemlVbXVuSkZTZHN6ZDNzeHNuZmlKcXhlbHQtVStuV3lzM
zQ0dEVMUUMzdFZyV2E1MndhekhSd1RxMS1pOXR0SpidRkFDR3lfdUFJcVBXVThWUnRKR1
BzeVRFXDJTTGNpSncyY3U2SE83VVF2VXBGQkRMVHRrbGRBaldGOEVDNGpITkh3T1RmQWp
uWDdYMkExWUZreEdLZ05ENkdNOTw4OHh3WXhRdF9WeDVBOnRyaMYsLXBvd2VyY2xvdWQp
resibHVlbWl4Lm5ldAStop the cloud connector on the HMC:
chsvc -o stop -s cloudconn
None
None
IBM Austin
chhmccert, chstat, lsstat, lssvc
| Linux | CHSVC (1) | November 2020 |