Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Creating a Unicast Junos Space Cluster

The nodes of a Junos Space cluster support only multicast traffic. But sometimes, for example, when Internet Group Management Protocol (IGMP) snooping is enabled on switches, unicast communication should be configured on the Junos Space nodes within a subnet so that these nodes can communicate with each other.

Junos Space provides the changeSettings2staticIP.sh script to enable you to toggle between unicast and multicast traffic on the nodes of a Junos Space cluster. This script is located in the /var/www/cgi-bin folder of a Junos Space node.

Script Syntax

sh changeSettings2StaticIP.sh

Options

  • backup—Backs up libraries and configuration files from the nodes of the Junos Space cluster

  • restore—Restores the libraries and configuration files on the nodes of the Junos Space cluster

  • multicast2unicast—Changes multicast communication to unicast communication on the nodes of a Junos Space cluster

  • unicast2multicast—Changes unicast communication to multicast communication on the nodes of a Junos Space cluster

When you run the script, the following subsystems in the domain.xml configuration file located at /usr/local/jboss/domain/configuration are modified:

Table 1: domain.xml Subsystem Parameters Affected When Toggling Between Multicast and Unicast Communication on Junos Space Nodes

Subsystem

Multicast Parameters

Unicast Parameters

mod-cluster

advertise=false, proxy-list

advertise=false, proxy-list

messaging

default-stack=udp, protocol (type=MPING)

default-stack=tcp, protocol (type=TCPPING)

jgroups

cluster-connections (discovery-group-ref)

connectors (netty-connector), cluster-connections (static-connectors)

You can create a unicast Junos Space cluster from a single node configured for unicast communication or by changing the multicast communication in an existing cluster to unicast communication.

Creating a Unicast Junos Space Cluster from a Single Node

To create a unicast Junos Space cluster from a single node:

  1. Create a standalone Junos Space node. For information about creating a standalone Junos Space node, see Configuring a Junos Space Appliance as a Junos Space Node.
  2. Log in to the CLI of the Junos Space node.
  3. On the Junos Space Settings Menu, to access the shell interface:

    • Type 6 if the Junos Space node is a JA2500 Junos Space hardware appliance.

    • Type 7 if the Junos Space node is a virtual appliance.

  4. Enter the administrator password.
  5. Take a backup of /usr/local/jboss/domain/configuration/domain.xml.
  6. Type cd /var/www/cgi-bin to navigate to the cgi-bin folder.
  7. Execute the changeSettings2StaticIP.sh script with the multicast2unicast option.
  8. Restart the jboss-dc process.
  9. Restart the jboss process.
  10. Add a node to form a cluster. For information about adding a node to a cluster, see the Adding a Node to an Existing Junos Space Fabric.
  11. Restart the jboss-dc and jboss processes on all the nodes.

    Restart the jboss-dc and jboss processes on all the nodes each time you add a node to the cluster. You can add a maximum of six nodes to a unicast cluster.

Creating a Unicast Junos Space Cluster from an Existing Multicast Junos Space Cluster

To change multicast communication in an existing cluster to unicast communication, you must stop jbosson all nodes and execute the sh changeSettings2StaticIP.sh script with the multicast2unicast option on the VIP node of the cluster and then restart the jboss-dc and start jboss processes.

Note:

You must stop the watchdog service before executing the below procedure.

To change multicast communication to unicast communication:

  1. Log in to the CLI of the Junos Space node on which the VIP or the eth0:0 interface is configured.
  2. On the Junos Space Settings Menu, to access the shell interface:

    • Type 6 if the Junos Space node is a JA2500 Junos Space hardware appliance.

    • Type 7 if the Junos Space node is a virtual appliance.

  3. Enter the administrator password.
  4. Take a backup of ’/usr/local/jboss/domain/configuration/domain.xml’ file.
  5. Type cd /var/www/cgi-bin to navigate to the cgi-bin folder.
  6. Stop the jboss process on all the nodes.
  7. Execute the changeSettings2StaticIP.sh script with the multicast2unicast option on the VIP node.
  8. Restart the jboss-dc process on the Junos Space node on which the VIP address is configured.
  9. Start the jboss process on all the nodes.
  10. (Optional) To confirm that the communication is changed from multicast to unicast, execute the $diff backup/domain.xml /usr/local/jboss/domain/configuration/domain.xml command on the VIP node to view the differences in the domain.xml file before and after executing the changeSettings2StaticIP.sh script. See Table 1 for the parameters that change when multicast communication is changed to unicast communication.

Changing Unicast Communication to Multicast Communication on a Junos Space Cluster

To change unicast communication in an existing cluster to multicast communication, you must execute the sh changeSettings2StaticIP.sh script with the unijcast2multicast option on the VIP node of the cluster and then restart the jboss-dc and jboss processes.

To change unicast communication to multicast communication:

  1. Log in to the CLI of the Junos Space node on which the VIP or the eth0:0 interface is configured.
  2. On the Junos Space Settings Menu, to access the shell interface:

    • Type 6 if the Junos Space node is a JA2500 Junos Space hardware appliance.

    • Type 7 if the Junos Space node is a virtual appliance.

  3. Enter the administrator password.
  4. Take a backup of ’/usr/local/jboss/domain/configuration/domain.xml’ file.
  5. Type cd /var/www/cgi-bin to navigate to the cgi-bin folder.
  6. Execute the changeSettings2StaticIP.sh script with the unicast2multicast option.
  7. Restart the jboss-dc process on the node on which the VIP address is configured.
  8. Restart the jboss process on all the nodes.
  9. (Optional) To confirm that the communication is changed from unicast to multicast, execute the $diff backup/domain.xml /usr/local/jboss/domain/configuration/domain.xml command to view the differences in the domain.xml file before and after executing the changeSettings2StaticIP.sh script. See Table 1 for the parameters that change when unicast communication is changed to multicast communication.

Related Documentation