Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

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

    You can configure a Junos Space Virtual 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 Junos Space node, and a primary FMPM node, before you configure a secondary FMPM node.

    To configure a Junos Space Virtual Appliance as a backup or secondary FMPM node, you must configure basic network and system settings to make the node 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, 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 Virtual Appliance as a Backup or Secondary FMPM Node

    You can configure a Junos Space Virtual Appliance as a backup FMPM node.

    To add a secondary or backup FMPM node to the Junos Space cluster:

    1. Using a virtual machine client (such as VMware vSphere Client or Virtual Machine Manager [VMM]), log in and power on the Junos Space Virtual Appliance.
    2. Access the console on the virtual machine client to view the Junos Space login prompt.
    3. At the Junos Space login prompt, type admin as your default login name and press Enter.
    4. Type abc123 as your default password and press Enter.

      Junos Space prompts you to change your default password.

    5. Type the default password again and press Enter.
    6. Type the new password and press Enter.

      Note: You can choose a password that is at least eight characters long and 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. 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.

      Passwords and passphrases are case-sensitive.

    7. Retype your new password.

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

    8. Type F to configure the virtual appliance as a standalone or primary FMPM node and press Enter when prompted Choose the type of node to be installed.
      Choose the type of node to be installed [S/F] F
    9. Configure the IP address of the eth0 Ethernet interface.

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

      Configuring Eth0 :
      
      1> Configure IPv4
      2> Configure Both IPv4 and IPv6
      
      R> Redraw Menu
      
      Choice [1-2,R]: 
      • 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.
          Please enter new IPv4 address for interface eth0: 
          192.0.2.53

          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.
          Please enter new IPv4 subnet mask for interface eth0: 
          255.255.0.0
        4. Type the IP address of the default gateway for the eth0 Ethernet interface in dotted-decimal notation and press Enter.
          Enter the default IPv4 gateway as a dotted-decimal IP address: 
          192.0.2.155
      • 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.
          Please enter new IPv4 address for interface eth0
          192.0.2.53
        3. Type a subnet mask for the eth0 interface in dotted-decimal notation and press Enter.
          Please enter new IPv4 subnet mask for interface eth0: 
          255.255.0.0
        4. Type the IPv4 address of the default gateway for the eth0 interface in dotted-decimal notation and press Enter.
          Enter the default IPv4 gateway as a dotted-decimal IP address: 
          192.0.2.155
        5. Type the IPv6 address and prefix for the eth0 interface and press Enter.
          Please enter new IPv6 address with prefix (IPv6 Address/prefix) for interface eth0:
          2001:db8:0:1:192:10:2:51/64
        6. Type the IPv6 address of the default gateway for the eth0 interface and press Enter.
          Enter the IPv6 gateway:
          2001:db8:0:1:192:10:2:150
    10. Type the IPv4 address of the name server and press Enter.
      Please type the IPv4 nameserver address in dotted decimal notation:
      192.0.2.15
    11. Type the IPv6 address of the name server and press Enter.
      Please type the IPv6 nameserver address:
      2001:db8:0:1:192:10:2:10
    12. Enter B when prompted Choose the role for this FMPM specialized node [P/B].

      Choosing B installs the node as the secondary or backup node in an FMPM HA setup. The PostgreSQL database containing the fault and performance monitoring data is replicated from the master node to this node. When the master node is down or being rebooted, the backup node automatically assumes charge.

      The settings summary is displayed, as shown in the following example:

      1> IP Change: eth0 is 10.205.56.136 / 255.255.0.0
      2> Default Gateway = 10.205.255.254 on eth0
      3> DNS add: 10.209.194.14
      4> This node will be the backup FMPM specialized node.
      
      1> IPv4 Change: eth0 is 192.0.2.53 / 255.255.0.0
      2> Default IPv4 Gateway = 192.0.2.155 on eth0
      3> IPV6 Change: eth0 is 2001:db8:0:1:192:10:2:51 / 64
      4> Default IPv6 Gateway = 2001:db8:0:1:192:10:2:150 on eth0
      5> IPv4 DNS add: 192.0.2.15
      6> DNS add: 2001:db8:0:1:192:10:2:10
      8> This node will be the backup FMPM specialized node.
      
      A> Apply settings
      C> Change settings
      Q> Quit and set up later
      R> Redraw Menu
      
      Choice [ACQR]:
    13. Confirm that the information in the settings summary is correct:
      • If all summary information is correct, enter A to apply the settings
      • If any summary information is incorrect, enter C to change the settings

        If you enter C, you are prompted to reenter all the basic configuration information that you have configured up to this point.

    14. Expand the VM drive size.

      Expand the /var partition by 120 GB.

      1. Type 6 to expand the VM drive size.

        Note: Before expanding the VM drive size, ensure free disk space is available for allocation to the partitions. For information about adding disk resources, refer to Deploying a Junos Space Virtual Appliance on a VMware ESX or VMware ESXi Server.

        The minimum disk space required for the /var partition is 120 GB.

      2. Enter the administrator password.

        Note: No caution is displayed for node reboot while expanding the drive size for an FMPM node. However, the FMPM node is rebooted after the drive size is expanded.

      3. Type y to continue expanding the drive size or type n to return to the Junos Space Settings Menu.
        Do you want to continue? [y/n]
        y

        If you type y, you are prompted to specify the partition that you want to expand.

      4. Enter the number present against the partition that you want to expand; for example, type 2 to expand the /var partition or 5 to quit expanding disks and return to the Junos Space Settings Menu.

        The free space that can be allocated is displayed and you are prompted to enter the space that you want to allocate to the partition.

        Begin to stop Jboss ...
        Service Jboss stopped
        
        Which partition do you want to expand?
        
        1) /
        2) /var
        3) /var/log
        4) /tmp
        5) Quit
        Select a partition: 1 
        
      5. Enter the additional disk space that you want to allocate.

        You can enter the disk space in megabytes (M), gigabytes (G), or terabytes (T). Do not add a space between the number and the unit; for example, 50M and not 50 M, 10G and not 10 G, and so on.

        Current disk partition size of / is 22G
        Total 4.97G free disk space can be allocated
        
        How much additional disk space is to be added(Acceptable suffixes: M|G|T): 1M

        You are prompted whether you want to expand more drives.

        Increasing size of LV /dev/jmpvgnocf/lvroot
          Extending logical volume lvroot to 22.59 GB
          Logical volume lvroot successfully resized
        Resizing / onto new space, this will take a few minutes
        resize4fs 1.41.12 (17-May-2010)
        Filesystem at /dev/jmpvgnocf/lvroot is mounted on /; on-line resizing required
        old desc_blocks = 2, new_desc_blocks = 2
        Performing an on-line resize of /dev/jmpvgnocf/lvroot to 5922816 (4k) blocks.
        The filesystem on /dev/jmpvgnocf/lvroot is now 5922816 blocks long.
        
        4.94G free disk space available
        Do you want to expand more disks? [y/N]
        N
      6. Type y to continue adding disk space or n to return to the Junos Space Settings Menu.

        When you type n, the node is rebooted and the opennms process that was stopped is resumed. If the VM drive size was expanded on a primary node, the node becomes secondary when it comes up.

    15. Type Q to exit the Junos Space Settings Menu.

      The FMPM node is ready to be added to the Junos Space cluster. See Adding a Node to an Existing Junos Space Fabric for information about adding a node to the Junos Space cluster.

    Configuring the eth1 Ethernet 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 virtual appliance only through the eth1 interface.

    To configure the eth1 interface:

    1. On the Junos Space Settings Menu, type 7 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.

    Modified: 2017-06-19