Juniper Junos Space Virtual Appliance Installation Manual

Junos Space Virtual Appliance Installation

and Configuration Guide

Published

Release

2021-04-09

21.1

ii

Juniper Networks, Inc. 1133 Innovation Way Sunnyvale, California 94089 USA

408-745-2000 www.juniper.net

JuniperNetworks,theJuniperNetworkslogo,Juniper,andJunosareregisteredtrademarksofJuniperNetworks,Inc. in theUnitedStatesandothercountries. Allothertrademarks,servicemarks,registeredmarks,orregisteredservicemarks are the property of their respective owners.

Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify, transfer, or otherwise revise this publication without notice.

JunosSpaceVirtualApplianceInstallationandConfigurationGuide

21.1

Copyright © 2021 Juniper Networks, Inc. All rights reserved.

The information in this document is current as of the date on the title page.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the year 2038. However, the NTP application is known to have some difficulty in the year 2036.

END USER LICENSE AGREEMENT

TheJuniperNetworksproductthatisthesubjectofthistechnicaldocumentationconsistsof(orisintendedforusewith) JuniperNetworkssoftware.UseofsuchsoftwareissubjecttothetermsandconditionsoftheEndUserLicenseAgreement (“EULA”) posted at https://support.juniper.net/support/eula/. By downloading, installing or using such software, you agree to the terms and conditions of that EULA.

iii

Table of Contents

About the Documentation | vi

Documentation and Release Notes | vi

Documentation Conventions | vi

Documentation Feedback | ix

Requesting Technical Support | ix

Self-Help Online Tools and Resources | x

Creating a Service Request with JTAC | x

1Virtual Appliance Overview

Junos Space Virtual Appliance Overview | 12

Configuring an NTP Time Source for Each Appliance Overview | 12

Ethernet Interfaces in a Junos Space Virtual Appliance Overview | 13

2Deploying the Junos Space Virtual Appliance

Junos Space Virtual Appliance Deployment Overview | 19

Deploying a Junos Space Virtual Appliance on a VMware ESXi Server | 20

Installing the VMware ESXi Server | 21

Installing a Junos Space Virtual Appliance on a VMware ESXi Server | 22

Installing a Junos Space Virtual Appliance by Using vSphere Client | 22

Installing a Junos Space Virtual Appliance by Using the OVF Tool | 23

Modifying RAM Settings for a Junos Space Virtual Appliance | 24

Adding Disk Resources for a Junos Space Virtual Appliance | 25

Deploying a Junos Space Virtual Appliance on a KVM Server | 25

Installing a Junos Space Virtual Appliance on the KVM Server by Using VMM | 26

Modifying the Type of Virtual Disk Interface | 28

Modifying RAM for a Junos Space Virtual Appliance | 29

Adding Disk Resources for a Junos Space Virtual Appliance | 29

Enabling Multicast on Bridged Interfaces of a KVM-Host Machine | 29

iv

Adding Disk Resources for a Junos Space Virtual Appliance | 30

Adding Disk Resources for a Junos Space Virtual Appliance Deployed on a VMware ESX or

VMware ESXi Server | 32

Adding Disk Resources for a Junos Space Virtual Appliance Deployed on a KVM Server | 33

Starting Open VM Tools in Junos Space Platform | 34

Installing VI Toolkit for Perl on Junos Space Virtual Appliance | 37

3Configuring the Junos Space Virtual Appliance

Configuring a Junos Space Virtual Appliance as a Junos Space Node | 41

Configuring a Junos Space Virtual Appliance | 43

Configuring Access to Junos Space Through a NAT Gateway | 60

Configuring the eth1 Ethernet Interface | 66

Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM

Node | 68

Configuring the Junos Space Virtual Appliance as the Primary FMPM Node | 69

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

Configuring a Junos Space Virtual Appliance as a Backup or Secondary FMPM Node | 81

Changing the Network and System Settings of a Junos Space Virtual Appliance | 87

Changing the admin User Password of a Junos Space Virtual Appliance | 88

Changing the Network Settings of a Junos Space Virtual Appliance | 90

Adding a DNS Server | 91

Deleting a DNS Server | 93

Modifying the Virtual IP Address | 94

Modifying the IP Address of the eth0 Interface | 98

Modifying the NAT Configuration | 104

Modifying the IP Address of the eth1 Interface | 109

Modifying the IP Address of the eth3 Interface | 111

Adding Static Routes to a Junos Space Virtual Appliance | 117

v

Deleting Static Routes from a Junos Space Virtual Appliance | 122

Changing Time Options of a Junos Space Virtual Appliance | 124

Changing the Time Zone | 124

Changing NTP Settings | 126

Retrieving System Log Files from a Junos Space Virtual Appliance | 128

Expanding the Drive Size of a Junos Space Virtual Appliance | 130

Setting Security Options on a Junos Space Virtual Appliance | 133

Enabling the Firewall on a Junos Space Virtual Appliance | 133

Disabling the Firewall on a Junos Space Virtual Appliance | 134

Disabling SSH on a Junos Space Virtual Appliance | 134

Enabling SSH on a Junos Space Virtual Appliance | 135

Running Shell in a Junos Space Virtual Appliance | 136

4Viewing and Adding Nodes to a Fabric

Adding a Node to an Existing Junos Space Fabric | 139

Adding a Junos Space Node to the Junos Space Fabric | 140

Adding an FMPM Node to the Junos Space Fabric | 145

Obtaining Fingerprint of a Junos Space Node | 147

Viewing Nodes in the Fabric | 148

Changing Views | 148

Viewing Fabric Node Details | 149

vi

About the Documentation

IN THIS SECTION

Documentation and Release Notes | vi

Documentation Conventions | vi

Documentation Feedback | ix

Requesting Technical Support | ix

UsethisguidetoinstallandconfiguretheJunosSpaceVirtualAppliance. Aftercompletingtheinstallation andbasicconfigurationprocedurescoveredinthisguide,refertotheJunosSpaceNetworkManagement Platform documentation for information about further software configuration.

Documentation and Release Notes

To obtain the most current version of all Juniper Networks® technical documentation, see the product documentation page on the Juniper Networks website at https://www.juniper.net/documentation/.

Iftheinformationinthelatestreleasenotesdiffersfromtheinformationinthedocumentation,followthe product Release Notes.

Juniper Networks Books publishes books by Juniper Networks engineers and subject matter experts. These books go beyond the technical documentation to explore the nuances of network architecture, deployment, and administration. The current list can be viewed at https://www.juniper.net/books.

Documentation Conventions

Table 1 on page vii defines notice icons used in this guide.

vii

Table 1: Notice Icons
Icon	Meaning	Description
	Informational note	Indicates important features or instructions.
	Caution	Indicates a situation that might result in loss of data or hardware
		damage.
	Warning	Alerts you to the risk of personal injury or death.
	Laser warning	Alerts you to the risk of personal injury from a laser.
	Tip	Indicates helpful information.
	Best practice	Alerts you to a recommended use or implementation.

Table 2 on page vii defines the text and syntax conventions used in this guide.

Table 2: Text and Syntax Conventions

Convention	Description	Examples
Bold text like this	Represents text that you type.	To enter configuration mode, type
		the configure command:
		user@host> configure
Fixed-width text like this	Represents output that appears on	user@host> show chassis alarms
	the terminal screen.	No alarms currently active

Italictextlikethis	• Introducesoremphasizesimportant
	new terms.
	• Identifies guide names.
	• Identifies RFC and Internet draft
	titles.

•A policy term is a named structure that defines match conditions and actions.

•JunosOSCLIUserGuide

•RFC 1997, BGPCommunities Attribute

viii

Table 2: Text and Syntax Conventions (continued)

Convention	Description
Italictextlikethis	Represents variables (options for
	which you substitute a value) in
	commands or configuration
	statements.

Examples

Configure the machine’s domain name:

[edit]

root@# set system domain-name domain-name

Text like this	Represents names of configuration
	statements, commands, files, and
	directories; configuration hierarchy
	levels; or labels on routing platform
	components.

•To configure a stub area, include the stub statement at the [edit protocols ospf area area-id] hierarchy level.

•The console port is labeled

CONSOLE.

< > (angle brackets)	Encloses optional keywords or
	variables.
| (pipe symbol)	Indicates a choice between the
	mutually exclusive keywords or
	variablesoneithersideofthesymbol.
	The set of choices is often enclosed
	in parentheses for clarity.

stub <default-metric metric>;

broadcast | multicast

(string1 | string2 | string3)

# (pound sign)

[ ] (square brackets)

Indention and braces ( { } )

; (semicolon)

Indicatesacommentspecifiedonthe	rsvp{#RequiredfordynamicMPLS
same line as the configuration	only
statement to which it applies.
Enclosesavariableforwhichyoucan	community name members [
substitute one or more values.	community-ids ]
Identifies a level in the configuration	[edit]
hierarchy.	routing-options {
	static {
Identifies a leaf statement at a	route default {
configuration hierarchy level.	nexthop address;
	retain;
	}
	}
	}

GUI Conventions

ix

Table 2: Text and Syntax Conventions (continued)
Convention	Description	Examples
Bold text like this	Represents graphical user interface	• IntheLogicalInterfacesbox,select
	(GUI) items you click or select.	All Interfaces.
		• To cancel the configuration, click
		Cancel.
> (bold right angle bracket)	Separates levels in a hierarchy of	Intheconfigurationeditorhierarchy,
	menu selections.	select Protocols>Ospf.

Documentation Feedback

We encourage you to provide feedback so that we can improve our documentation. You can use either of the following methods:

•Online feedback system—Click TechLibrary Feedback, on the lower right of any page on the Juniper Networks TechLibrary site, and do one of the following:

•Click the thumbs-up icon if the information on the page was helpful to you.

•Click the thumbs-down icon if the information on the page was not helpful to you or if you have suggestions for improvement, and use the pop-up form to provide feedback.

•E-mail—[e-mail]cname, URL or page number, and software version (if applicable).

Requesting Technical Support

TechnicalproductsupportisavailablethroughtheJuniperNetworksTechnicalAssistanceCenter(JTAC). If you are a customer with an active Juniper Care or Partner Support Services support contract, or are

x

covered under warranty, and need post-sales technical support, you can access our tools and resources online or open a case with JTAC.

•JTACpolicies—ForacompleteunderstandingofourJTACproceduresandpolicies,reviewtheJTACUser Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.

•Productwarranties—Forproductwarrantyinformation,visithttps://www.juniper.net/support/warranty/.

•JTAC hours of operation—The JTAC centers have resources available 24 hours a day, 7 days a week, 365 days a year.

Self-Help Online Tools and Resources

Forquickandeasyproblemresolution,JuniperNetworkshasdesignedanonlineself-serviceportalcalled the Customer Support Center (CSC) that provides you with the following features:

•Find CSC offerings: https://www.juniper.net/customers/support/

•Search for known bugs: https://prsearch.juniper.net/

•Find product documentation: https://www.juniper.net/documentation/

•Find solutions and answer questions using our Knowledge Base: https://kb.juniper.net/

•Download the latest versions of software and review release notes: https://www.juniper.net/customers/csc/software/

•Search technical bulletins for relevant hardware and software notifications: https://kb.juniper.net/InfoCenter/

•Join and participate in the Juniper Networks Community Forum: https://www.juniper.net/company/communities/

•Create a service request online: https://myjuniper.juniper.net

To verify service entitlement by product serial number, use our Serial Number Entitlement (SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/

Creating a Service Request with JTAC

You can create a service request with JTAC on the Web or by telephone.

•Visit https://myjuniper.juniper.net.

•Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).

For international or direct-dial options in countries without toll-free numbers, see https://support.juniper.net/support/requesting-support/.

1

CHAPTER

Virtual Appliance Overview

Junos Space Virtual Appliance Overview | 12

Ethernet Interfaces in a Junos Space Virtual Appliance Overview | 13

12

Junos Space Virtual Appliance Overview

TheJunosSpaceVirtualApplianceconsistsofpreconfiguredJunosSpaceNetworkManagementPlatform softwarewithabuilt-inoperatingsystemandapplicationstackthatiseasytodeploy,manage,andmaintain.

A Junos Space Virtual Appliance includes the same software and all the functionality available in a Junos Space physical appliance. However, you must deploy the virtual appliance on a VMware ESX, VMWare ESXi or KVM server, which provides a CPU, hard disk, RAM, and a network controller, but requires installation of an operating system and applications to become fully functional.

Justasyoucaninstalladditionalphysicalappliancestocreateafabrictoprovidescalabilityandavailability, you can deploy multiple virtual appliances to create a fabric that provides the same scalability and high availability as a fabric of physical appliances.

AJunosSpacefabriccancontainonlyphysicalappliances(JA2500),onlyvirtualappliances,oracombination of both physical and virtual appliances.

Configuring an NTP Time Source for Each Appliance Overview

To ensure consistent behavior among all nodes in a multinode fabric, the time on each node must be synchronized with every other node in the fabric. When you configure the first Junos Space Virtual Appliance with a Network Time Protocol (NTP) server, you must ensure that, if the first node (which is used to synchronize time for all nodes in the fabric) goes down, all the other nodes in the fabric remain synchronized. Additional nodes installed in the same fabric automatically get their time setting from the first node in the fabric without any additional NTP server configuration.

NOTE: By default, Junos Space Network Management Platform synchronizes the local time zone of the client computer with the time zone of the server so that the Web user interface displays the Junos Space server time in the local time zone. However, the CLI server displays time as per the time zone configured on the Junos Space server.

To ensure that time remains synchronized across all nodes in a fabric, we strongly recommend that you add an NTP server to the first appliance (physical or virtual) during the initial setup.

NOTE: You must add the NTP server before you add the appliance or node to the fabric from the Junos Space user interface.

13

RELATED DOCUMENTATION

Junos Space Virtual Appliance Deployment Overview | 19

Configuring a Junos Space Virtual Appliance as a Junos Space Node | 41

Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM Node | 68

Adding a Node to an Existing Junos Space Fabric | 139

EthernetInterfacesinaJunosSpaceVirtualAppliance

Overview

AJunosSpaceVirtualAppliancecontainsfourEthernetinterfaces—eth0,eth1,eth2,andeth3.TheEthernet interfaces eth0 and eth3 support both IPv4 and IPv6 addresses. As a separate IP address is available for each IP stack, for any connection initiated by Junos Space, the source IP address (that is, the IPv4 or IPv6 address)oftheconnectionisboundbytheIPaddresstypeofamanageddevice.Foraconnectioninitiated by a managed device, Junos Space listens on both IPv4 and IPv6 addresses of the device management interface(eth3).Therefore,amanageddevicecancommunicatewithJunosSpacebyusingitsIPv4orIPv6 address.

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.

Junos Space supports managed devices based on the IP address type (that is, the IPv4 or IPv6 address) configuredforthedevicemanagementinterface.YoucanconfigureanIPv4orIPv6addressforthedevice management interface. If the device management interface is not configured, the IP address type of the node management interface (eth0) is considered for communication with managed devices.

Table 3 on page 14 details the support matrix for IPv4 and IPv6 address configurations on the device management interface.

14

Table 3: Matrix for IP Address Versions Supported on Devices
				IP Address of
				Managed Devices
				Supported by Junos
eth0		eth3		Space
IPv4 Address	IPv6 Address	IPv4 Address	IPv6 Address
Configured	Not Configured	Not Configured	Not Configured	IPv4
Configured	Configured	Not Configured	Not Configured	IPv4 and IPv6
Configured	Not Configured	Configured	Not Configured	IPv4
Configured	Not Configured	Configured	Configured	IPv4 and IPv6
Configured	Not Configured	Not Configured	Configured	IPv6
Configured	Configured	Configured	Configured	IPv4 and IPv6

You can use the Ethernet interfaces of Junos Space as follows:

•eth0—Use the eth0 interface to configure the virtual IP (VIP) address of a fabric and the IP address of the node as well as to access the managed devices. The VIP address and the IP address of the node should be on the same subnet.

The eth0:0 subinterface provides access to the Junos Space Network Management Platform GUI. You can access the GUI by using the VIP address of the fabric.

•eth1—Use the eth1 interface as an administrative interface of a Junos Space node. Use SSH to access aJunosSpacenodethroughthisinterface.Theeth0interfaceandtheeth1interfacecanbeondifferent subnets.

If you configure eth1, SSH stops running on the eth0 and the eth3 interfaces. You can access the CLI of the Junos Space virtual appliance only through the eth1 interface.

NOTE: From Junos Space Network Management Platform Release 14.1R1 onward, you can configure the eth1 Ethernet interface as an administrative interface.

•eth2—The eth2 interface is reserved for future use.

•eth3—Use the eth3 interface for SSH access to managed devices when the managed devices are on an out-of-band management subnet or on a subnet not accessible through the eth0 interface.

15

NOTE:

•Ifthemanageddevicesarenotaccessiblethroughthedefaultgateway,youmustconfigure static routes. Any static route configured manually is populated in the main routing table, which is used to route traffic through the eth0 interface.

•When the eth3 interface is configured as a device management interface, Junos Space PlatformdoesnotforwardICMPpacketsthroughtheeth3interface.ToallowICMPpackets through the eth3 interface, routes must be added manually.

NOTE: When you configure a node as an FMPM node, you can use only the eth0 and eth1 interfaces.

•When you configure an appliance as a Junos Space node, you can configure the Ethernet interfaces as follows:

•Configure only the eth0 interface.

WhenonlyEthernetinterface(eth0)isused,theJunosSpacenodesinthefabric,virtualIP(VIP)address of the fabric, and the devices being managed by Junos Space are on the same subnet.

•Configure the eth0 and eth3 interfaces.

WhenEthernetinterfaceseth0andeth3areused,theJunosSpacenodesinthefabricandVIPaddress of the fabric are on the same subnet and are reachable through Ethernet interface eth0. The devices being managed by Junos Space are on the same subnet, which is different from the one reachable through Ethernet interface eth0, and are reachable through Ethernet interface eth3.

•Configure the eth0 and eth1 interfaces.

When Ethernet interfaces eth0 and eth1 are used, the Junos Space nodes in the fabric and the VIP address of the fabric may or may not be on the same subnet. The eth1 interface provides SSH access to the Junos Space nodes.

The VIP address and the devices being managed by Junos Space are on the same subnet.

•Configure the eth0, eth1, and eth3 interfaces.

When Ethernet interfaces eth0, eth1, and eth3 are used, the Junos Space nodes in the fabric and the VIPaddressofthefabricmayormaynotbeonthesamesubnet.TheJunosSpacenodesarereachable (SSH access) only through the eth1 interface.

The managed devices can be reached through the eth0 interface if they are configured on the same subnet as the VIP address; on any other subnet, the managed devices can be reached through the eth3 interface.

16

NOTE: If the managed devices are not reachable through the default gateway configured for the eth3 interface, you must configure static routes for the eth3 interface. The eth3 interface refers to the devint routing table.

Any static route configured manually is populated in the main routing table, which is used to route traffic through the eth0 interface.

•When you configure an appliance as a specialized node used for fault monitoring and performance monitoring (FMPM), you can use only the Ethernet interfaces eth0 and eth1.

Ethernet interface eth1 provides SSH access to FMPM nodes.

NOTE: For more information about the Junos Space fabric, refer to the ManagingNodesinthe JunosSpaceFabric chapterinthe JunosSpaceNetworkManagementPlatformWorkspacesFeature Guide(availableathttps://www.juniper.net/documentation/en_US/junos-space18.1/index.html).

Table4onpage16summarizesthefunctionsofEthernetinterfacesontheJunosSpaceVirtualAppliance.

Table 4: Junos Space Virtual Appliance Ethernet Interfaces

Interface	Function
eth0	SSH and device management, if only the Ethernet interface ETH0 or
	Ethernet interface 0 is used
eth0:0	GUI interface
eth1	SSH access to the Junos Space nodes
	NOTE: SSH is disabled on the eth0 and eth3 interfaces when eth1 is
	configured.
eth2	Reserved for future use
eth3	Device management when managed devices are on an out-of-band
	management subnet and not reachable by the Ethernet interface eth0

RELATED DOCUMENTATION

Configuring a Junos Space Virtual Appliance as a Junos Space Node | 41

17

Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM Node | 68

Changing the Network and System Settings of a Junos Space Virtual Appliance | 87

2

CHAPTER

Deploying the Junos Space Virtual

Appliance

Junos Space Virtual Appliance Deployment Overview | 19

Deploying a Junos Space Virtual Appliance on a VMware ESXi Server | 20

Deploying a Junos Space Virtual Appliance on a KVM Server | 25

Adding Disk Resources for a Junos Space Virtual Appliance | 30

Starting Open VM Tools in Junos Space Platform | 34

Installing VI Toolkit for Perl on Junos Space Virtual Appliance | 37

19

JunosSpaceVirtualApplianceDeploymentOverview

The Junos Space Virtual Appliance is distributed in the Open Virtualization Appliance (OVA) and qcow2 formats.

You can deploy the Junos Space Virtual Appliance *.ova file on a VMware ESXi server version 5.5, 6.0, or 6.5andthe*.qcow2onaKernel-basedVirtualMachine(KVM)server. TheJunosSpaceVirtualAppliance Release16.1R1andlatercanbedeployedonqemu-kvm(KVM)Release1.5.3-105.el7orlaterwhichruns on CentOS Release 7.2. From Junos Space Network Management Platform Release 18.2 onward, Junos Space Virtual Appliance will be installed with VM Hardware version 8.

NOTE: Though a KVM server on other Linux distributions is supported, we recommend that you use KVM on CentOS.

After the Junos Space Virtual Appliance is deployed, you can use the VMware vSphere client or Virtual Machine Manager (VMM) to connect to the VMware ESX (or VMware ESXi ) server or KVM server respectively and configure the Junos Space Virtual Appliance.

The minimum hardware requirements for deploying a Junos Space Virtual Appliance are as follows:

•64-bit quad processor with a clock speed of at least 2.66 GHz

•Four virtual CPUs

•1-Gbps network

•32-GBRAMtoconfigurethevirtualapplianceasaJunosSpacenodeorfaultmonitoringandperformance monitoring (FMPM) node

NOTE: 64-GB RAM is required if the number of rules per firewall (SRX) cluster is more than 6000 and if firewall policies of similar sizes are being concurrently published.

•500-GB hard disk

Ensure that 100-GB free disk space is available if the Junos Space Virtual Appliance is to be configured as a FMPM node. For information about adding disk resources, refer to “Adding Disk Resources for a Junos Space Virtual Appliance” on page 30.

•1-TB hard disk if you are configuring Database nodes

•ConfigureOpenVMtools(see“StartingOpenVMToolsinJunosSpacePlatform”onpage34fordetails.)

20

NOTE:

•We recommend that you use disks with I/O speed of 200 MBps or above. For information about determining I/O speed of a disk used in the node of a Junos Space cluster, see Howdo IDeterminetheDiskI/OSpeedofaNodeintheJunosSpaceFabric?intheJunosSpaceHardware and Virtual Appliances FAQ.

•WerecommendagainstcloningadeployedJunosSpaceImageandusingitasanotherinstance of a Junos Space Virtual Appliance.

RELATED DOCUMENTATION

Deploying a Junos Space Virtual Appliance on a VMware ESXi Server | 20

Deploying a Junos Space Virtual Appliance on a KVM Server | 25

Adding Disk Resources for a Junos Space Virtual Appliance | 30

Deploying a Junos Space Virtual Appliance on a VMware ESXi Server

The Junos Space Virtual Appliance requires a VMware ESXi server 5.5, 6.0, 6.5, or 6.7 that can support a virtual machine with the following configuration:

NOTE:

•The ESXi host server must include a Standard or Enterprise edition license, which may not be installed on the host server by default.

•VMwareVMotionissupportedformovingJunosSpaceVirtualAppliancesfromoneVMware ESXi server to another VMware ESXi server.

ForinformationabouttheminimumhardwarerequirementsfordeployingaJunosSpaceVirtualAppliance, see “Junos Space Virtual Appliance Deployment Overview” on page 19.

21

BESTPRACTICE: WerecommendthefollowingbestpracticesafteryoudeploytheJunosSpace Virtual Appliance on a VMWare ESXi server:

•VMWare ESXi server snapshots should be taken after shutting down Junos Space servers. Ensure snapshots are taken simultaneously across all the nodes in the fabric.

•To ensure optimal performance of Junos Space, configure purging policies for the VMWare host one month after the Junos Space fabric is functional.

ThedeploymentofaJunosSpaceVirtualApplianceonaVMwareESXiserverincludesthefollowingtasks:

1.Installing the VMware ESXi Server | 21

2.Installing a Junos Space Virtual Appliance on a VMware ESXi Server | 22

3.Modifying RAM Settings for a Junos Space Virtual Appliance | 24

4.Adding Disk Resources for a Junos Space Virtual Appliance | 25

Installing the VMware ESXi Server

To install the VMware ESXi server:

1.DownloadtheVMwareESXiserverinstallationpackagefromhttps://www.vmware.com/download/vi/.

2.Install the VMware ESXi server.

For instructions to install the VMware ESXi server, go to https://www.vmware.com/support/pubs/vi_pubs.html.

NOTE: YoucaninstalltheVMwarevSphereClientwhenyouinstalltheVMwareESXiserver 5.5, 6.0, or 6.5. Contact VMware for support with installing ESXi server.

NOTE: JunosSpaceNetworkManagementPlatformisnotcertifiedtobeusedwithVMware tools.

22

Installing a Junos Space Virtual Appliance on a VMware ESXi Server

IN THIS SECTION

Installing a Junos Space Virtual Appliance by Using vSphere Client | 22

Installing a Junos Space Virtual Appliance by Using the OVF Tool | 23

You can use vSphere Client 4.0 or later or OVF Tool 2.01 or later to deploy the Junos Space Virtual Appliance image on a VMWare ESXi server.

Installing a Junos Space Virtual Appliance by Using vSphere Client

To create a Junos Space Virtual Appliance by using vSphere Client 4.0:

1.Download the Junos Space Virtual Appliance image from https://www.juniper.net/support/downloads/?p=space#sw to your local system.

NOTE: Do not change the name of the Junos Space Virtual Appliance image file that you downloadfromtheJuniperNetworkssupportsite. Ifyouchangethenameoftheimagefile, the creation of the Junos Space Virtual Appliance can fail.

2.LaunchthevSphereClientthatisconnectedtotheESXiserverwheretheJunosSpaceVirtualAppliance is to be deployed.

3.Select File > Deploy OVF Template from the menu bar. The Deploy OVF Template page appears.

4.Click the Deploy from file option and click Browse, and then upload the OVA file from your storage location.

NOTE: You can use the same image to deploy both Junos Space and fault monitoring and performance monitoring (FMPM) nodes.

5. Click Next.

23

6.Verify the OVF Template details and then click Next.

7.Specify a name and location for the deployed template and then click Next.

A template name can contain a maximum of 80 characters. Template names are not case-sensitive.

8.Verify your settings and then click Finish to create the Junos Space Virtual Appliance.

Installing a Junos Space Virtual Appliance by Using the OVF Tool

Before you use the OVF Tool to create a Junos Space Virtual Appliance, ensure that the OVF Tool is installed on the system where you save the Junos Space Virtual Appliance image file (*.ova).

To create a Junos Space Virtual Appliance by using the OVF Tool:

1.Download the Junos Space Virtual Appliance image from https://www.juniper.net/support/downloads/?p=space#sw to your local system.

NOTE: Do not change the name of the Junos Space Virtual Appliance image file that you downloadfromtheJuniperNetworkssupportsite. Ifyouchangethenameoftheimagefile, the creation of the Junos Space Virtual Appliance can fail.

2.LogintothelocalsystemandnavigatetothelocationwheretheJunosSpaceVirtualApplianceimage file is saved.

3.Run the following command:

/usr/bin/ovftool/ovftool --name=virtual-appliance image-file vi://username:password@host-id

where:

•virtual-appliance is the name you assign to the Junos Space Virtual Appliance.

•image-file is the name of the Junos Space Virtual Appliance image file.

•username istheusernameofthehostmachinewhereyoudeploytheJunosSpaceVirtualAppliance.

•password is the password of the host machine where you deploy the Junos Space Virtual Appliance.

•host-id is the IP address of the host machine where you deploy the Junos Space Virtual Appliance.

Example:

24

/usr/bin/ovftool/ovftool -name=space1vm space-19.3R1.0.ova

vi://username:password@10.157.10.1

The Junos Space Virtual Appliance is deployed on the host machine.

4.Log in to the host machine and edit the settings (number of processors, memory) of the Junos Space Virtual Appliance. For information about editing the settings of a Junos Space Virtual Appliance by using the OVF Tool, see the OVF Tool documentation at https://www.vmware.com/support/developer/ovf/ .

Modifying RAM Settings for a Junos Space Virtual Appliance

To add RAM for a Junos Space Virtual Appliance:

1.LaunchtheVMwarevSphereClientandlogintotheESXiserverwheretheJunosSpaceVirtualAppliance is deployed.

2.Select the Junos Space Virtual Appliance from the inventory view.

3.If the Junos Space Virtual Appliance is powered on, you must power off the appliance to configure RAM.

TopowerofftheJunosSpaceVirtualAppliance,right-clicktheJunosSpaceVirtualApplianceiconand select Power > Power Off.

4.Select the Summary tab to view the Junos Space virtual machine settings.

5.Select Edit Settings to view and edit the virtual memory settings.

6.Select Memory.

7.Update the RAM to 32 GB to operate the Junos Space Virtual Appliance as a Junos Space node or as an FMPM node.

8.Click OK.

RAM is added to the Junos Space Virtual Appliance.

25

Adding Disk Resources for a Junos Space Virtual Appliance

ForinformationaboutaddingdiskresourcesforJunosSpaceVirtualAppliance,see“AddingDiskResources for a Junos Space Virtual Appliance” on page 30.

RELATED DOCUMENTATION

Configuring a Junos Space Virtual Appliance as a Junos Space Node | 41

Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM Node | 68

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

Adding a Node to an Existing Junos Space Fabric | 139

Viewing Nodes in the Fabric | 148

DeployingaJunosSpaceVirtualApplianceonaKVM

Server

TheJunosSpaceVirtualApplianceRelease16.1R1andlatercanbedeployedonqemu-kvm(KVM)Release 1.5.3 or later.

NOTE: Juniper Networks does not provide any support for installing and configuring the KVM server. You must install the virtual appliance image and configure it as per the recommended specifications for the virtual appliance. Juniper Networks will provide support only after the Junos Space Virtual Appliance has booted successfully.

The prerequisites to deploy a Junos Space Virtual Appliance on a KVM server are as follows:

•Knowledge about configuring and installing a KVM server.

•KVMserverandsupportedpackagesmustbeinstalledonyourLinux-basedsystem. ContactyourLinux vendor or documentation for information about installing KVM.

•An application or method to view the remote system virtual monitor, such as Virtual Machine Manager (VMM), Virtual Network Computing (VNC) Viewer, or any other application.

•Bridge Interface configured according to your environment and at least two free static IP addresses.

26

ForinformationabouttheminimumhardwarerequirementsfordeployingaJunosSpaceVirtualAppliance, see “Junos Space Virtual Appliance Deployment Overview” on page 19.

ThedeploymentofaJunosSpaceVirtualApplianceonaKVMserverbyusingVMMincludesthefollowing tasks:

NOTE: ThoughdeployingtheJunosSpaceVirtualApplianceontheKVMserverbyusingvirtual machine clients other than VMM is possible, Juniper Networks does not provide support for installing the Junos Space Virtual Appliance using clients other than VMM.

1.Installing a Junos Space Virtual Appliance on the KVM Server by Using VMM | 26

2.Modifying the Type of Virtual Disk Interface | 28

3.Modifying RAM for a Junos Space Virtual Appliance | 29

4.Adding Disk Resources for a Junos Space Virtual Appliance | 29

5.Enabling Multicast on Bridged Interfaces of a KVM-Host Machine | 29

Installing a Junos Space Virtual Appliance on the KVM Server by Using VMM

Use the VMM virtual machine client to install the Junos Space Virtual Appliance on a KVM server. To install the Junos Space Virtual Appliance on a KVM server by using VMM:

1.Download the Junos Space Virtual Appliance image from https://www.juniper.net/support/downloads/?p=space#sw to your local system.

NOTE: Do not change the name of the Junos Space Virtual Appliance image file that you downloadfromtheJuniperNetworkssupportsite. Ifyouchangethenameoftheimagefile, the creation of the Junos Space Virtual Appliance can fail.

2.Launch the VMM client.

3.Select File>NewVirtualMachine onthemenubarofVMMtoinstallanewvirtualmachineonaKVM server.

The New VM dialog box appears and displays Step 1 of 4 of the New VM installation.

27

4.Under Choose how you would like to install the operating system, click Import existing disk image.

5.Click Forward to go to the next step. Step 2 of 4 is displayed.

6.Under Provide the existing storage path, click Browse.

7.UnderChoosestoragevolume,click BrowseLocal atthebottomofthedialogboxtolocateandselect the Junos Space Virtual Appliance image file (.qcow2) saved on your system.

8.UnderChooseanoperatingsystemtypeandversion,selectLinuxfor OStype andRedHatEnterprise Linux versionnumber for Version.

NOTE: We recommend to use the same Linux version as Junos Space Platform is using.

9.Click Forward to go to the next step. Step 3 of 4 is displayed.

10.UnderChooseMemoryandCPUsettings,ensurethat4issetforCPUs andselectorenterthefollowing value for Memory (RAM):

•32768 MB–For the Junos Space Virtual Appliance to be deployed as a Junos Space node or as an FMPM node

11.Click Forward to go to the next step. Step 4 of 4 is displayed.

12.Under Ready to begin the installation, in the Name field, enter a name for the Junos Space Virtual Appliance.

13.Under Network selection, select the options based on how you want to configure network communication on the Junos Space Platform setup.

14.Click Finish.

TheNewVMdialogboxcloses.TheJunosSpaceVirtualApplianceisstartedandtheconsoleisdisplayed. The Junos Space Virtual Appliance is created and listed with the name that you entered in the VMM.

28

Modifying the Type of Virtual Disk Interface

After the Junos Space Virtual Appliance is created, you must change the hard disk interface type to Integrated Drive Electronics (IDE) to avoid any issues with the booting up of the Junos Space Virtual Appliance due to kernel panic.

NOTE: If you are using CLI of VMM to set up KVM, you set the type of virtual disk interface to IDE at the start of the set up. You do not have to reset the type of interface again.

To change the hard disk interface type to IDE:

1.SelecttheJunosSpaceVirtualAppliancejustcreatedandselect Edit>VirtualMachineDetails onthe menu bar of VMM to edit the hardware settings.

2.Click the Show virtual hardware details icon in the Virtual Machine Details dialog box.

3.Click VirtIO Disk1 (Virtual Disk) on the left of the dialog box to change the type of the disk interface to IDE.

The details of the Virtual disk is displayed on the right of the dialog box.

4.Under Advanced Options, select IDE for Disk Bus and qcow2 for Storage format.

5.Click Apply.

6.(Optional) To apply the changes immediately, shut down and restart the virtual appliance if the Junos Space Virtual Appliance is already powered on.

To restart the Junos Space Virtual Appliance:

a.Right-clicktheJunosSpaceVirtualApplianceiconandselect Shutdown > PowerOff,toshutdown the Junos Space Virtual Appliance.

b.Select the Junos Space Virtual Appliance icon and click the Power on the virtual machine icon to start the Junos Space Virtual Appliance. Alternatively, you can right-click the Junos Space Virtual Appliance icon and select Run.

29

Modifying RAM for a Junos Space Virtual Appliance

The Junos Space Virtual Appliance file is distributed with 8 GB of RAM and four virtual CPUs. You need 32-GB RAM to configure the Junos Space Virtual Appliance as a Junos Space node or as an FMPM node.

To modify RAM for the Junos Space Virtual Appliance:

1.Launch VMM and select the Junos Space Virtual Appliance for which you want to modify RAM.

2.(Optional)IftheJunosSpaceVirtualApplianceisrunning,youmustshutdowntheappliancetomodify

RAM.

To shut down the Junos Space Virtual Appliance, right-click the Junos Space Virtual Appliance icon and select Shutdown > Power Off.

3.ToviewandchangeRAMallocatedtotheJunosSpaceVirtualAppliance,selectEdit>VirtualMachine Details on the menu bar of VMM to edit the hardware settings.

4.Click the Show virtual hardware details icon in the Virtual Machine Details dialog box.

5.Click Memory on the left side of the dialog box.

The RAM details of the virtual machine is displayed on the right of the dialog box.

6.Enter the required memory in the Current allocation and Maximum allocation fields.

7.Click Apply to modify the RAM allocation.

Adding Disk Resources for a Junos Space Virtual Appliance

ForinformationaboutaddingdiskresourcesforJunosSpaceVirtualAppliance,see“AddingDiskResources for a Junos Space Virtual Appliance” on page 30.

Enabling Multicast on Bridged Interfaces of a KVM-Host Machine

For creating Junos Space clusters, multicast must be enabled on the bridged interface of a KVM-host machine on which Junos Space node is deployed to allow multicast traffic to flow between the nodes of the cluster.. If Junos Space nodes in a cluster are deployed on different host machines, multicast must be enabled on the bridged interface of each host machine.

30

To configure multicast on a bridged interface of a KVM-host machine, log in to the KVM-host machine after the UI of the Junos Space node is up and execute the ifconfig InterfaceName allmulti command, where InterfaceName is the name of the interface.

Example:

-bash-4.1$ ifconfig macvtap0 allmulti

NOTE: Configure multicast on all the KVM-host machines before adding a Junos Space node to a cluster.

RELATED DOCUMENTATION

Configuring a Junos Space Virtual Appliance as a Junos Space Node | 41

Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM Node | 68

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

Adding a Node to an Existing Junos Space Fabric | 139

Viewing Nodes in the Fabric | 148

Adding Disk Resources for a Junos Space Virtual Appliance

IN THIS SECTION

Adding Disk Resources for a Junos Space Virtual Appliance Deployed on a VMware ESX or VMware ESXi Server | 32

Adding Disk Resources for a Junos Space Virtual Appliance Deployed on a KVM Server | 33

The Junos Space Virtual Appliance files are distributed with 250-GB of disk space.