Oracle® Solaris Cluster Geographic Edition Installation and Configuration Guide

Exit Print View

Updated: July 2014, E39666-01
 
 

How to Configure IPsec for Secure Cluster Communication

The following example procedure configures a cluster, cluster-paris, for IPsec secure communication with another cluster, cluster-newyork. The procedure assumes that the local logical hostname on cluster-paris is lh-paris-1 and that the remote logical hostname is lh-newyork-1. Inbound messages are sent to lh-paris-1 and outbound messages are sent to lh-newyork-1.

Perform the following procedure on each node of cluster-paris.

  1. Log in to the first node of the primary cluster, phys-paris-1, as the root role.

    For a reminder of which node is phys-paris-1, see Example Geographic Edition Cluster Configuration in Oracle Solaris Cluster Geographic Edition System Administration Guide .

  2. Set up an entry for the local address and remote address in the IPsec policy file.

    The policy file is located at /etc/inet/ipsecinit.conf. Permissions on this file should be 644. For more information about this file, see the ipsecconf (1M) man page.

    For information about the names and values that are supported by Geographic Edition software, see Appendix B, Legal Names and Values of Geographic Edition Entities, in Oracle Solaris Cluster Geographic Edition System Administration Guide .

    1. Configure the communication policy.

      The default port for the tcp_udp plug-in is 2084. You can specify this value in the etc/cacao/instances/default/modules/com.sun.cluster.geocontrol.xml file.

      The following entry in the /etc/inet/ipsecinit.conf file configures a policy with no preference for authorization or encryption algorithms.

      # {raddr lh-newyork-1 rport 2084} ipsec {auth_algs any encr_algs any \
      sa shared} {laddr lh-paris-1 lport 2084} ipsec {auth_algs any encr_algs \
      any sa shared}

      When you configure the communication policy on the secondary cluster, cluster-newyork, you must reverse the policies.

      # {laddr lh-newyork-1 lport 2084} ipsec {auth_algs any encr_algs \
      any sa shared} {raddr lh-paris-1 rport 2084} ipsec {auth_algs any encr_algs \
      any sa shared}
    2. Add the policy by rebooting the node or by running the following command.
      # ipsecconf -a /etc/inet/ipsecinit.conf
  3. Set up encryption and authentication keys for inbound and outbound communication.

    The communication file is located at /etc/init/secret/ipseckeys. Permissions on the file should be 600.

    Add keys:

    # ipseckey -f /etc/init/secret/ipseckeys

    Key entries have the following general format:

    # inbound to cluster-paris
    add esp spi paris-encr-spi dst lh-paris-1 encr_alg paris-encr-algorithm \
    encrkey paris-encrkey-value
    add ah spi newyork-auth-spi dst lh-paris-1 auth_alg paris-auth-algorithm \
    authkey paris-authkey-value
    
    # outbound to cluster-newyork
    add esp spi newyork-encr-spi dst lh-newyork-1 encr_alg newyork-encr-algorithm \
    encrkey newyork-encrkey-value
    add ah spi newyork-auth-spi dst lh-newyork-1 auth_alg newyork-auth-algorithm \
    authkey newyork-authkey-value

    For more information about the communication files, see the ipsecconf (1M) man page.

Next Steps

If you are configuring a zone cluster as a member of a partnership, go to Preparing a Zone Cluster for Partner Membership.

Otherwise, go to Enabling the Geographic Edition Infrastructure.