Top
PRIMECLUSTER  Cluster Foundation Configuration and Administration Guide 4.6
FUJITSU Software
Chapter 7 Shutdown Facility > 7.4 Configuring the Shutdown Facility > 7.4.2 Shutdown Agents
PreviousNext

7.4.2 Shutdown Agents

This section contains information on how to configure the following SAs with CLI.

Blade

To configure the Blade shutdown agent (SA_blade), you can create or modify the following file:

/etc/opt/SMAW/SMAWsf/SA_blade.cfg

The template of SA_blade.cfg file can be found at the following location:

/etc/opt/SMAW/SMAWsf/SA_blade.cfg.template

The format of SA_blade.cfg file is as follows:

community-string           SNMP community string
management-blade-ip        IP address
cfname        slot-no         Action

Additionally, you can add the IP address of the management Blade for a second Blade chassis. In this case, you would need to add one or more lines to specify the Blades in that chassis.

Note

management-blade-ip, community-string, cycle, and leave-off are reserved words. They must be described in lowercase letters.

The editable fields are defined as follows:

The following is an example of SA_blade.cfg file:

community-string public
management-blade-ip 123.45.56.78
shasta1 1 cycle
shasta2 3 leave-off
management-blade-ip 123.45.56.79
shasta3 1 cycle
shasta4 2 cycle

The log file is stored in the following:

/var/opt/SMAWsf/log/SA_blade.log

IPMI

To configure the IPMI shutdown agent (SA_ipmi), you need to create or modify the following file:

/etc/opt/SMAW/SMAWsf/SA_ipmi.cfg

The template of SA_ipmi.cfg file can be found at the following location:

/etc/opt/SMAW/SMAWsf/SA_ipmi.cfg.template

SA_ipmi.cfg file contains lines with four fields (and some subfields) on each line. Each line defines a node in the cluster that can be powered off (leaving it off) or powered off and then on again (power cycle). The fields are as follows:

Note

The permissions of the SA_ipmi.cfg file are read/write by root only. This is to protect the password to the iRMC/BMC unit.

The following is an example of SA_ipmi.cfg file:

shasta1 192.168.200.1::root:ipmipwd cycle
shasta2 192.168.200.2::root:ipmipwd cycle
shasta3 192.168.200.3::root:ipmipwd leave-off
shasta4 192.168.200.4::root:ipmipwd leave-off

The log file is stored in the following:

/var/opt/SMAWsf/log/SA_ipmi.log

ICMP

To configure the ICMP shutdown agent (SA_icmp), you need to create or modify the following file:

/etc/opt/SMAW/SMAWsf/SA_icmp.cfg

The template of SA_icmp.cfg file can be found at the following location:

/etc/opt/SMAW/SMAWsf/SA_icmp.cfg.template

The format of SA_icmp.cfg file is as follows:

TIME_OUT=value
cfname:ip-address-of-node:NIC-name1,NIC-name2

The editable fields are defined as follows:

Note

Note the following when you describe network interfaces:

  • When duplicating the network by GLS, you need to describe all redundant network interfaces. (For example, eth0,eth1)

  • When bonding NICs, you need to describe a bonding device after the IP address. (For example, bond0)

  • When describing cluster interconnects, you need to describe all network interfaces used in all paths of the cluster interconnects. (For example, eth2,eth3)

The following is an example of SA_icmp.cfg file:

TIME_OUT=5
shasta1:10.20.30.100:eth0,eth1
shasta1:10.20.40.200:eth2
shasta2:10.20.30.101:eth0,eth1
shasta2:10.20.40.201:eth2

The log file is stored in the following:

/opt/SMAW/SMAsf/log/SA_icmp.log

VMCHKHOST

To configure the Shutdown Agent (SA_vmchkhost) to switch the HOST OS in the event of an error in the virtual machine environment, you must create or modify the following file:

/etc/opt/SMAW/SMAWsf/SA_vmchkhost.cfg

The template of SA_vmchkhost.cfg file is stored in the following:

/etc/opt/SMAW/SMAWsf/SA_vmchkhost.cfg.template

Each line of SA_vmchkhost.cfg file includes the following five fields:

The following is an example of SA_vmchkhost.cfg file:

shasta1 hostos2 192.168.200.1 FJSVvmSP 3CA1wxVXKD8a93077BaEkA==
shasta2 hostos3 192.168.200.2 FJSVvmSP 3CA1wxVXKD8a93077BaEkA==

The log file is stored in the following:

/var/opt/SMAWsf/log/SA_vmchkhost.log

libvirt

To configure the Shutdown Agent (SA_libvirtgp) for PANIC or Shutdown Agent (SA_libvirtgr) for RESET of libvirt, you must create or modify the following files respectively. 

/etc/opt/SMAW/SMAWsf/SA_libvirtgp.cfg
/etc/opt/SMAW/SMAWsf/SA_libvirtgr.cfg

The templates of SA_libvirtgp.cfg file and SA_libvirtgr.cfg file are stored in the following: 

/etc/opt/SMAW/SMAWsf/SA_libvirtgp.cfg.template
/etc/opt/SMAW/SMAWsf/SA_libvirtgr.cfg.template

Each line of SA_libvirtgp.cfg file and SA_libvirtgr.cfg file includes the following five fields:

The following is an example of SA_libvirtgp.cfg file:

shasta1 domain2 192.168.200.1 user 3CA1wxVXKD8a93077BaEkA==
shasta2 domain3 192.168.200.2 user 3CA1wxVXKD8a93077BaEkA==

The following is an example of SA_libvirtgr.cfg file:

shasta1 domain2 192.168.200.1 user 3CA1wxVXKD8a93077BaEkA==
shasta2 domain3 192.168.200.2 user 3CA1wxVXKD8a93077BaEkA==

The log file is stored in the following:

/var/opt/SMAWsf/log/SA_libvirtgp.log
/var/opt/SMAWsf/log/SA_libvirtgr.log

VMware vCenter Server functional cooperation

To configure the VMware vCenter Server functional cooperation shutdown agent (SA_vwvmr), you need to create or modify the following file:

/etc/opt/SMAW/SMAWsf/SA_vwvmr.cfg

The template of SA_vwvmr.cfg file can be found at the following location:

/etc/opt/SMAW/SMAWsf/SA_vwvmr.cfg.template

The format of SA_vwvmr.cfg file is as follows:

CFName: cfname
VMName: vmname
vCenter_IP: IP address
vCenter_Port: port
user: user
passwd: passwd

The editable fields are defined as follows:

The following is an example of SA_vwvmr.cfg file:

Example: Port number of VMware vCenter Server is the default value (443)

CFName: shasta1
VMName: shasta1vm
vCenter_IP: 192.168.100.1
vCenter_Port:
user: PCL
passwd: 3CA1wxVXKD8a93077BaEkA==

Example: Port number of VMware vCenter Server is10443

CFName: shasta1
VMName: shasta1vm
vCenter_IP: 192.168.100.1
vCenter_Port: 10443
user: PCL
passwd: 3CA1wxVXKD8a93077BaEkA==

The log file is stored in the following:

/var/opt/SMAWsf/log/SA_vwvmr.log

FUJITSU Hybrid IT Service FJcloud-O/FJcloud-Baremetal API

To configure the FUJITSU Hybrid IT Service FJcloud-O/FJcloud-Baremetal API shutdown agent (SA_vmk5r), you must create or modify the following files:

/opt/SMAW/SMAWRrms/etc/k5_endpoint.cfg
/etc/opt/SMAW/SMAWsf/SA_vmk5r.cfg

The log file is stored in the following: 

/var/opt/SMAWsf/log/SA_vmk5r.log

OpenStack API

To configure the OpenStack API shutdown agent (SA_vmosr), you must create or modify the following files:

/opt/SMAW/SMAWRrms/etc/os_endpoint.cfg
/etc/opt/SMAW/SMAWsf/SA_vmosr.cfg

The log file is stored in the following: 

/var/opt/SMAWsf/log/SA_vmosr.log

AWS CLI

To configure the AWS CLI shutdown agent (SA_vmawsAsyncReset), you must create or modify the following file:

/etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg

The template of the SA_vmawsAsyncReset.cfg file is in the following location:

/etc/opt/SMAW/SMAWsf/SA_vmawsAsyncReset.cfg.template

The format of the SA_vmawsAsyncReset.cfg file is as follows:

cfname InstanceID [ProfileName]

Each line of the SA_vmawsAsyncReset.cfg file includes three fields. Each line defines a node in the cluster. The fields are as follows:

The following is an example of the SA_vmawsAsyncReset.cfg file:

node1 i-abcdef0123456789a userprofile1
node2 i-abcdef0123456789b userprofile1

The log file is stored in the following:

/var/opt/SMAWsf/log/SA_vmawsAsyncReset.log

Azure CLI

To configure the Azure CLI shutdown agent (SA_vmazureReset), you must create or modify the following file:

/etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg

The template of the SA_vmazureReset.cfg file is in the following location:

/etc/opt/SMAW/SMAWsf/SA_vmazureReset.cfg.template

The format of the SA_vmazureReset.cfg file is as follows:

cfname ResourceID AppID TenantID CertPath {cycle | leave-off}

Each line of the SA_vmazureReset.cfg file includes six fields. Each line defines a node in the cluster. The fields are as follows:

The following is an example of the SA_vmazureReset.cfg file:

node1 /subscriptions/1e234d12-39b8-49db-881a-35aa03b402b9/resourceGroups/pcl-mw1/providers/Microsoft.Compute/virtualMachines/node1 d5b7dac1-718f-448b-8e11-4a8cca6d9004 8ff7ddfd-fbcb-4700-ae52-6d071ac8d1b4 /root/examplecert.pem cycle
node2 /subscriptions/1e234d12-39b8-49db-881a-35aa03b402b9/resourceGroups/pcl-mw1/providers/Microsoft.Compute/virtualMachines/node2 d5b7dac1-718f-448b-8e11-4a8cca6d9004 8ff7ddfd-fbcb-4700-ae52-6d071ac8d1b4 /root/examplecert.pem cycle

The log file is stored in the following:

/var/opt/SMAWsf/log/SA_vmazureReset.log

NIFCLOUD API

To configure the NIFCLOUD API shutdown agent (SA_vmnifclAsyncReset), you must create or modify the following file:

/etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg

The template of the SA_vmnifclAsyncReset.cfg file is in the following location:

/etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg.template

The format of the SA_vmnifclAsyncReset.cfg file is as follows:

CFNameX ServerName Region Accesskey SecretAccesskey

Each line of the SA_vmnifclAsyncReset.cfg file includes five fields. Each line defines a node in the cluster. The fields are as follows:

The following is an example of the SA_vmnifclAsyncReset.cfg file:

# cat /etc/opt/SMAW/SMAWsf/SA_vmnifclAsyncReset.cfg
node1 pclserver1 jp-east-1 123456789ABCDEFGHIJK PIJgi9wm4sYJlfWShOxWP6fpz0Xb6t9KmRc4sPDsRBIGfm6gT5m0xH2H2xf1r38G
node2 pclserver2 jp-east-1 123456789ABCDEFGHIJK PIJgi9wm4sYJlfWShOxWP6fpz0Xb6t9KmRc4sPDsRBIGfm6gT5m0xH2H2xf1r38G

The log file is stored in the following:

/var/opt/SMAWsf/log/SA_vmnifclAsyncReset.log
PreviousNext
Copyright FUJITSU LIMITED 2019-2022