Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring a Junos Space Appliance as a Backup or Secondary FMPM Node for High Availability

 

You can configure a Junos Space Appliance as a Junos Space node or as a specialized network monitoring node used for fault monitoring and performance monitoring (FMPM).

An FMPM node can be configured as a standalone or primary FMPM node, or as a secondary or backup FMPM node. The first FMPM node that you configure is always the standalone or primary node; this node performs fault and performance monitoring of the devices and nodes, and any events or alarms are stored in a PostgreSQL database on this node. The second FMPM node that you configure is the backup or secondary FMPM node. The PostgreSQL database containing the fault and performance monitoring data is replicated from the primary FMPM node to the secondary FMPM node. When the primary node is down or being rebooted, the secondary node automatically assumes charge.

A primary and a secondary FMPM node are referred to as a cluster or a team; therefore, an FMPM team can consist of a maximum of two nodes.

Note

You must have at least one appliance already configured as a Junos Space node, and an appliance configured as a primary FMPM node, before you configure a different appliance as a secondary FMPM node.

To configure a Junos Space Appliance as a backup or secondary FMPM node, you must configure basic network and system settings to make the appliance accessible on the network.

Note

From Junos Space Network Management Platform Release 14.1R2 onward, you can configure Junos Space Ethernet interfaces with only IPv4 addresses, or both IPv4 and IPv6 addresses.

Before you begin, do the following:

  • Ensure that the Junos Space Appliance is connected to a management console and that the management device is powered on.

  • Ensure that the appliance is booted and displays the login prompt at the console.

  • Ensure that 100 GB free disk space is available before configuring a node as an FMPM node.

  • Ensure that you have the following information available:

    • IPv4 address and subnet mask for the eth0 Ethernet interface

    • (Optional) IPv6 address and prefix for the eth0 Ethernet interface

    • IPv4 address of the default gateway

    • (Optional) IPv6 address of the default gateway

    • IPv4 address of the name server

    • (Optional) IPv6 address of the name server

    • Virtual IP (VIP) address of the FMPM nodes in IPv4 and IPv6 formats

      The VIP address is used for communications between Junos Space nodes and FMPM nodes. This IP address must be in the same subnet as the IP address assigned to the eth0 Ethernet interface, and the VIP address must be different from the VIP address used to access the Web GUI.

    • (Optional) IPv4 address of the eth1 Ethernet interface

      If the IP address of the eth1 interface Is not in the same subnet as the VIP address, ensure that you have the subnet mask and the default gateway for the eth1 interface.

This topic discusses the following tasks:

Configuring a Junos Space Appliance as the Secondary FMPM Node

You can configure the Junos Space Appliance as the backup or secondary FMPM node.

To configure an appliance as a backup or secondary FMPM node:

  1. At the serial console login prompt, type the default username (admin) and press Enter.
  2. Type the default password (abc123) and press Enter.

    You are prompted to change your password.

  3. To change the default password, do the following:
    1. Type the default password and press Enter.
    2. Type your new password and press Enter.
    3. Retype your new password and press Enter.

    If the password is changed successfully, the message passwd: all authentication tokens updated successfully is displayed.

    Note
    • All passwords are case-sensitive.

    • You can choose a password that is at least eight characters long, and that contains characters from at least three of the following four character classes: uppercase letters, lowercase letters, numbers (0 through 9), and special characters.

      However, if a password satisfies the preceding criteria but contains only a single uppercase letter at the beginning or only a single number at the end, then that password is considered invalid. In order to be counted as a valid character class, a single uppercase letter must not be at the beginning of the password, and a single number must not be at the end. For example, Abcdwip9, Qc9rdiwt, and bRfjvin9 are invalid passwords, but AAbcdwip99, Qc9rdiwtQ, and bRfjvin99 are valid passwords.

    • Alternatively, instead of using a string of characters, you can choose a passphrase that is between 16 and 40 characters long, and contains at least three dictionary words separated by at least one special character. For example, big#three;fork (14 characters long) and circlefaceglass (no special characters) are invalid passphrases, but @big#three;fork& and circle;face;glass are valid passphrases.

  4. Type the new password to log in to the appliance and press Enter.
  5. Type F to proceed with the configuration of the appliance as an FMPM node.
  6. Configure the IP address of the eth0 Ethernet interface.

    This IP address is used as the IP address of the FMPM node.

    • To configure the IPv4 address of the eth0 interface:

      1. Type 1.
      2. Type the IPv4 address for the eth0 interface in dotted-decimal notation and press Enter.
        Note

        All nodes that you configure in a cluster (fabric) must be in the same subnet.

      3. Type the new subnet mask for the IPv4 address and press Enter.
      4. Type the IP address of the default gateway for the eth0 Ethernet interface in dotted-decimal notation and press Enter.
    • To configure both IPv4 and IPv6 addresses:

      1. Type 2.
      2. Type the IPv4 address for the eth0 interface in dotted-decimal notation and press Enter.
      3. Type a subnet mask for the eth0 interface in dotted-decimal notation and press Enter.
      4. Type the IPv4 address of the default gateway for the eth0 interface in dotted-decimal notation and press Enter.
      5. Type the IPv6 address and prefix for the eth0 interface and press Enter.
      6. Type the IPv6 address of the default gateway for the eth0 interface and press Enter.
  7. Type the IPv4 address of the name server and press Enter.
  8. Type the IPv6 address of the name server and press Enter.
  9. Type B to configure the node as the backup or secondary FMPM node.

    The settings summary is displayed as follows:

  10. Review the settings that you configured.
  11. You can change the settings, quit without applying the settings, or apply the settings. Do one of the following:
    • To apply the settings, type A. The settings that you configured are applied and a series of messages is displayed on the console, and then the Junos Space Settings Menu is displayed, as follows:

    • To change the settings, type C, and follow the prompts on the CLI.

    • To quit the configuration without applying the settings, type Q.

      Caution

      If you quit the configuration without applying the settings, then all the settings are discarded.

  12. (Optional) If you have applied the settings, then type Q to quit.

    You are taken to the console login prompt.

The configuration of the appliance as a backup or secondary FMPM node is now complete.

Note

After you configure an FMPM node, you must add it to the Junos Space fabric using the Junos Space Network Management Platform. For more information, see the Adding a Node to an Existing Junos Space Fabric topic in the Junos Space Network Management Platform Workspaces Feature Guide (available at http://www.juniper.net/techpubs/en_US/release-independent/junos-space/index.html).

You can specify the name of the FMPM node when you add the node to the Junos Space fabric.

Configuring the eth1 Interface

From Junos Space Network Management Platform Release 14.1R1 onward, you can configure the eth1 Ethernet interface as an administrative interface. For the FMPM node, configure the eth1 interface when the node reboots after the basic configuration is complete.

Note
  • The eth1 interface must be configured separately for each node in a multinode fabric.

  • If you configure the eth1 interface, SSH is disabled on the eth0 interface. You can access the CLI of the Junos Space appliance only through the eth1 interface.

To configure the eth1 interface:

  1. On the Junos Space Settings Menu, type 6 to access the shell.

    You are prompted to enter your password.

  2. Type your password and press Enter.

    The shell prompt appears.

  3. At the shell prompt, type jmp_config and press Enter.

    You are prompted to enter the IP address of the eth1 interface.

  4. Type the IP address of the eth1 interface in dotted decimal notation and press Enter.

    The IP address can be in the same subnet as the virtual IP (VIP) address or in a different subnet. If the IP address is not in the same subnet as the VIP address, you are prompted to enter the subnet mask and then the default gateway for the eth1 interface.

  5. (Optional) Type the subnet mask for the eth1 interface in dotted decimal notation and press Enter.
  6. (Optional) Type the default gateway in dotted decimal notation and press Enter.

    The eth1 interface is configured.

  7. To verify that the eth1 address is configured, run the ifconfig eth1 command and check that the IP address displayed for eth1 is the same as the one that you configured.

    You can now access the FMPM node through the eth1 interface to perform administrative tasks.

To troubleshoot issues in configuring the eth1 interface, refer to the /var/log/changeEth1.log file.