Please enter search query.
Search <book_title>...
InfoScale™ 9.0 Cluster Server Administrator's Guide - Linux
Last Published:
2025-08-11
Product(s):
InfoScale & Storage Foundation (9.0)
Platform: Linux
- Section I. Clustering concepts and terminology
- Introducing Cluster Server
- About Cluster Server
- About cluster control guidelines
- About the physical components of VCS
- Logical components of VCS
- Types of service groups
- About resource monitoring
- Agent classifications
- About cluster control, communications, and membership
- About security services
- Components for administering VCS
- About cluster topologies
- VCS configuration concepts
- Introducing Cluster Server
- Section II. Administration - Putting VCS to work
- About the VCS user privilege model
- Administering the cluster from the command line
- About administering VCS from the command line
- About installing a VCS license
- Administering LLT
- Configuring IPsec for encrypted communication over LLT
- Starting VCS
- Stopping the VCS engine and related processes
- Logging on to VCS
- About managing VCS configuration files
- About managing VCS users from the command line
- About querying VCS
- About administering service groups
- Modifying service group attributes
- About administering resources
- Enabling and disabling IMF for agents by using script
- Linking and unlinking resources
- About administering resource types
- About administering clusters
- Configuring applications and resources in VCS
- VCS bundled agents for UNIX
- About application monitoring on single-node clusters
- Configuring NFS service groups
- About NFS
- Configuring NFS service groups
- Sample configurations
- About configuring the RemoteGroup agent
- About configuring Samba service groups
- About testing resource failover by using HA fire drills
- Section III. VCS communication and operations
- About communications, membership, and data protection in the cluster
- About cluster communications
- About cluster membership
- About membership arbitration
- About membership arbitration components
- About server-based I/O fencing
- About majority-based fencing
- About the CP server service group
- About secure communication between the VCS cluster and CP server
- About data protection
- Examples of VCS operation with I/O fencing
- About cluster membership and data protection without I/O fencing
- Examples of VCS operation without I/O fencing
- Administering I/O fencing
- About the vxfentsthdw utility
- Testing the coordinator disk group using the -c option of vxfentsthdw
- About the vxfenadm utility
- About the vxfenclearpre utility
- About the vxfenswap utility
- About administering the coordination point server
- About configuring a CP server to support IPv6 or dual stack
- About migrating between disk-based and server-based fencing configurations
- Migrating between fencing configurations using response files
- Controlling VCS behavior
- VCS behavior on resource faults
- About controlling VCS behavior at the service group level
- About AdaptiveHA
- Customized behavior diagrams
- About preventing concurrency violation
- VCS behavior for resources that support the intentional offline functionality
- VCS behavior when a service group is restarted
- About controlling VCS behavior at the resource level
- VCS behavior on loss of storage connectivity
- Service group workload management
- Sample configurations depicting workload management
- The role of service group dependencies
- About communications, membership, and data protection in the cluster
- Section IV. Administration - Beyond the basics
- VCS event notification
- VCS event triggers
- Using event triggers
- List of event triggers
- Virtual Business Services
- Section V. Cluster configurations for disaster recovery
- Connecting clusters–Creating global clusters
- VCS global clusters: The building blocks
- About global cluster management
- About serialization - The Authority attribute
- Prerequisites for global clusters
- Setting up a global cluster
- Configuring clusters for global cluster setup
- Configuring service groups for global cluster setup
- About IPv6 support with global clusters
- About cluster faults
- About setting up a disaster recovery fire drill
- Test scenario for a multi-tiered environment
- Administering global clusters from the command line
- About global querying in a global cluster setup
- Administering clusters in global cluster setup
- Setting up replicated data clusters
- Setting up campus clusters
- Connecting clusters–Creating global clusters
- Section VI. Troubleshooting and performance
- VCS performance considerations
- How cluster components affect performance
- How cluster operations affect performance
- VCS performance consideration when a system panics
- About scheduling class and priority configuration
- VCS agent statistics
- About VCS tunable parameters
- Troubleshooting and recovery for VCS
- VCS message logging
- Gathering VCS information for support analysis
- Troubleshooting the VCS engine
- Troubleshooting Low Latency Transport (LLT)
- Troubleshooting Group Membership Services/Atomic Broadcast (GAB)
- Troubleshooting VCS startup
- Troubleshooting issues with systemd unit service files
- Troubleshooting service groups
- Troubleshooting resources
- Troubleshooting sites
- Troubleshooting I/O fencing
- Fencing startup reports preexisting split-brain
- Troubleshooting CP server
- Troubleshooting server-based fencing on the VCS cluster nodes
- Issues during online migration of coordination points
- Troubleshooting notification
- Troubleshooting and recovery for global clusters
- Troubleshooting licensing
- Licensing error messages
- Troubleshooting secure configurations
- VCS message logging
- VCS performance considerations
- Section VII. Appendixes
Configuring IPsec using strongSwan on SLES systems
This process involves installing strongSwan and then using it to create a secure VPN configuration. All the commands described in this process need to be run with the root user privileges.
To install strongSwan
- Install strongSwan and the related RPMs.
# zypper install strongswan*
- Verify that strongSwan is installed.
# rpm -qa | grep strongswan
To create a secure host-to-host VPN configuration
- Create the
/etc/ipsec.conf
file.Sample entries in the configuration file:
# ipsec.conf - strongSwan IPsec configuration file # basic configuration config setup charon.start_all=true conn %default <-------- This need not be changed as this is default. keyexchange=ikev2 ikelifetime=60m keylife=20m rekeymargin=3m keyingtries=1 authby=secret conn myvpn <-------- Connection 1 created for link1 left=10.10.10.1 <-------- Local node IP address of first private LLT link leftsubnet=10.10.255.255 <-------- Subnet of first Private LLT link of local node right=10.10.10.2 <-------- Remote node IP address of first private LLT link rightsubnet=10.10.255.255 <-------- Subnet of first Private LLT link of remote node auto=start conn myvpn1 <-------- Connection 1 created for link2 left=20.20.20.1 <-------- Local node IP address of second private LLT link leftsubnet=20.20.255.255 <-------- Subnet of second Private LLT link of local node right=20.20.20.2 rightsubnet=20.20.255.255 auto=start
- Create the
/etc/ipsec.secrets
file, which contains information about the private keys and the mechanism used for the IPSec configuration.Sample entries in the secrets file:
# ipsec.secrets # This file holds the RSA private keys or the PSK preshared secrets for the IKE/IPsec authentication. See the ipsec.secrets(5) manual page. 10.10.10.1 10.10.10.2 : PSK "vcs1234" ---------- 10.10.10.1 is local/left node IP and 10.10.10.2 is remote/right node IP. ---------- Pre-shared key (PSK) is a mechanism similar to RSA, EAP.
To enable strongSwan and start the service
- To view the IPsec VPN configuration.
# systemctl enable strongswan-starter.service
- Restart the service.
# systemctl restart strongswan-starter.service
This service internally starts the IPsec service as well.
To verify the host-to-host VPN
- Enable the strongSwan service.
# ipsec status Security Associations (1 up, 0 connecting): myvpn[2]: ESTABLISHED 17 minutes ago, 10.10.10.1[10.10.10.1]...10.10.10.2[10.10.10.2] myvpn{3}: INSTALLED, TUNNEL, reqid 1, ESP SPIs: cf633b82_i cba64c78_o myvpn{3}: 10.10.255.255/32 === 10.10.255.255/32
- To view further details about the IPsec configuration.
# ipsec statusall Status of IKE charon daemon (strongSwan 5.9.11, Linux 5.14.21-150500.53-default, x86_64): uptime: 17 minutes, since May 22 14:11:46 2025 malloc: sbrk 3170304, mmap 0, used 1174208, free 1996096 worker threads: 10 of 16 idle, 6/0/0/0 working, job queue: 0/0/0/0, scheduled: 4 loaded plugins: charon ldap pkcs11 mgf1 nonce x509 revocation constraints pubkey pkcs1 pkcs7 pkcs12 pgp dnskey sshkey pem openssl pkcs8 af-alg fips-prf gmp curve25519 agent hmac kdf gcm drbg curl soup attr kernel-netlink resolve socket-default farp stroke vici smp updown eap-identity eap-sim eap-sim-pcsc eap-aka eap-aka-3gpp2 eap-simaka-pseudonym eap-simaka-reauth eap-md5 eap-gtc eap-mschapv2 eap-dynamic eap-radius eap-tls eap-ttls eap-peap eap-tnc xauth-generic xauth-eap xauth-pam tnc-imc tnc-imv tnc-tnccs tnccs-20 tnccs-11 tnccs-dynamic dhcp certexpire led duplicheck radattr addrblock unity counters Listening IP addresses: 30.30.30.30 10.10.10.1 20.20.20.1 Connections: myvpn: 10.10.10.1...10.10.10.2 IKEv2 myvpn: local: [10.10.10.1] uses pre-shared key authentication myvpn: remote: [10.10.10.2] uses pre-shared key authentication myvpn: child: 10.10.255.255/32 === 10.10.255.255/32 TUNNEL Security Associations (1 up, 0 connecting): myvpn[2]: ESTABLISHED 16 minutes ago, 10.10.10.1[10.10.10.1]...10.10.10.2[10.10.10.2] myvpn[2]: IKEv2 SPIs: b28588f4fd24c13b_i 1287cf3c3b31e804_r*, pre-shared key reauthentication in 38 minutes myvpn[2]: IKE proposal: AES_CBC_128/HMAC_SHA2_256_128/PRF_HMAC_SHA2_256/ECP_256 myvpn{3}: INSTALLED, TUNNEL, reqid 1, ESP SPIs: cf633b82_i cba64c78_o myvpn{3}: AES_CBC_128/HMAC_SHA2_256_128, 0 bytes_i, 0 bytes_o, rekeying in 14 minutes myvpn{3}: 10.10.255.255/32 === 10.10.255.255/32