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.
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.
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 100 GB free disk space is available before configuring a node as an FMPM node.
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.
IPv4 address or URL of NTP source to synchronize time
(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.
(Optional) IPv4 address for the NAT trap
(Optional) IPv6 address for the NAT trap
(Optional) Port number for the NAT trap
Before you begin, ensure that you have the following information available:
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: