Configuring a Junos Space Appliance as a Standalone or Primary FMPM Node
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. This topic explains how you can configure an appliance as a primary FMPM node.
You must have at least one appliance already configured as a Junos Space node to configure a different appliance as an FMPM node.
To configure a Junos Space Appliance as a standalone or primary FMPM node, you must configure basic network and system settings to make the appliance 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.
From Junos Space Network Management Platform Release 16.1R1 onward, you can configure access to Junos Space through a Network Address Translation (NAT) gateway.
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.
IPv4 address or URI of NTP source to synchronize time
(Optional) IPv4 address for the NAT trap
(Optional) IPv6 address for the NAT trap
(Optional) IPv4 port number for the NAT trap
(Optional) IPv6 port number for the NAT trap
This topic discusses the following tasks:
Configuring a Junos Space Appliance as the Primary FMPM Node
You can configure a Junos Space Appliance as an FMPM node.
To configure the appliance as a standalone or primary FMPM node:
The configuration of the appliance as a standalone or primary FMPM node is now complete.
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.
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 then access the CLI of the Junos Space appliance only through the eth1 interface.
To configure the eth1 interface:
To troubleshoot issues in configuring the eth1 interface, refer to the /var/log/changeEth1.log file.