Juniper Junos Space Virtual Appliance Installation Manual
Junos Space Virtual Appliance Installation
Published
2021-04-09
and Configuration Guide
Release
21.1
Juniper Networks, Inc.
1133 Innovation Way
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Juniper Networks, the Juniper Networks logo, Juniper, and Junos are registered trademarks of Juniper Networks, Inc. in
the United States and other countries. All other trademarks, service marks, registered marks, or registered service marks
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.
Junos Space Virtual Appliance Installation and Configuration Guide
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.
ii
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
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with)
Juniper Networks software. Use of such software is subject to the terms and conditions of the End User License Agreement
(“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.
Table of Contents
1
2
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
Virtual Appliance Overview
Junos Space Virtual Appliance Overview | 12
Configuring an NTP Time Source for Each Appliance Overview | 12
iii
Ethernet Interfaces in a Junos Space Virtual Appliance Overview | 13
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
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
Adding Disk Resources for a Junos Space Virtual Appliance | 30
3
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
Configuring 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
iv
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
Deleting Static Routes from a Junos Space Virtual Appliance | 122
4
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
Viewing and Adding Nodes to a Fabric
v
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
About the Documentation
IN THIS SECTION
Documentation and Release Notes | vi
Documentation Conventions | vi
Documentation Feedback | ix
Requesting Technical Support | ix
Use this guide to install and configure the Junos Space Virtual Appliance. After completing the installation
and basic configuration procedures covered in this guide, refer to the Junos Space Network Management
Platform documentation for information about further software configuration.
vi
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/.
If the information in the latest release notes differs from the information in the documentation, follow the
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.
Table 1: Notice Icons
vii
DescriptionMeaningIcon
Indicates important features or instructions.Informational note
Caution
Indicates a situation that might result in loss of data or hardware
damage.
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
Indicates helpful information.Tip
Alerts you to a recommended use or implementation.Best practice
Table 2 on page vii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
ExamplesDescriptionConvention
Fixed-width text like this
Italic text like this
Represents text that you type.Bold text like this
Represents output that appears on
the terminal screen.
Introduces or emphasizes important
•
new terms.
Identifies guide names.
•
Identifies RFC and Internet draft
•
titles.
To enter configuration mode, type
the configure command:
user@host> configure
user@host> show chassis alarms
No alarms currently active
A policy term is a named structure
•
that defines match conditions and
actions.
Junos OS CLI User Guide
•
RFC 1997, BGP Communities
•
Attribute
Table 2: Text and Syntax Conventions (continued)
viii
ExamplesDescriptionConvention
Italic text like this
Text like this
< > (angle brackets)
| (pipe symbol)
Represents variables (options for
which you substitute a value) in
commands or configuration
statements.
Represents names of configuration
statements, commands, files, and
directories; configuration hierarchy
levels; or labels on routing platform
components.
variables.
Indicates a choice between the
mutually exclusive keywords or
variables on either side of the symbol.
The set of choices is often enclosed
in parentheses for clarity.
Configure the machine’s domain
name:
[edit]
root@# set system domain-name
domain-name
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.
stub <default-metric metric>;Encloses optional keywords or
broadcast | multicast
(string1 | string2 | string3)
# (pound sign)
[ ] (square brackets)
Indention and braces ( { } )
; (semicolon)
GUI Conventions
Indicates a comment specified on the
same line as the configuration
statement to which it applies.
Encloses a variable for which you can
substitute one or more values.
Identifies a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
rsvp { # Required for dynamic MPLS
only
community name members [
community-ids ]
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
Table 2: Text and Syntax Conventions (continued)
ix
ExamplesDescriptionConvention
Bold text like this
> (bold right angle bracket)
Represents graphical user interface
(GUI) items you click or select.
Separates levels in a hierarchy of
menu selections.
In the Logical Interfaces box, select
•
All Interfaces.
To cancel the configuration, click
•
Cancel.
In the configuration editor hierarchy,
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—Send your comments to techpubs-comments@juniper.net. Include the document or topic name,
•
URL or page number, and software version (if applicable).
Requesting Technical Support
Technical product support is available through the Juniper Networks Technical Assistance Center (JTAC).
If you are a customer with an active Juniper Care or Partner Support Services support contract, or are
covered under warranty, and need post-sales technical support, you can access our tools and resources
online or open a case with JTAC.
JTAC policies—For a complete understanding of our JTAC procedures and policies, review the JTAC User
•
Guide located at https://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf.
Product warranties—For product warranty information, visit https://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
For quick and easy problem resolution, Juniper Networks has designed an online self-service portal called
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/
•
x
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
Junos Space Virtual Appliance Overview
The Junos Space Virtual Appliance consists of preconfigured Junos Space Network Management Platform
software with a built-in operating system and application stack that is easy to deploy, manage, and maintain.
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.
Just as you can install additional physical appliances to create a fabric to provide scalability and availability,
you can deploy multiple virtual appliances to create a fabric that provides the same scalability and high
availability as a fabric of physical appliances.
A Junos Space fabric can contain only physical appliances ( JA2500), only virtual appliances, or a combination
of both physical and virtual appliances.
12
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.
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
Ethernet Interfaces in a Junos Space Virtual Appliance Overview
A Junos Space Virtual Appliance contains four Ethernet interfaces—eth0, eth1, eth2, and eth3. The Ethernet
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) of the connection is bound by the IP address type of a managed device. For a connection initiated
by a managed device, Junos Space listens on both IPv4 and IPv6 addresses of the device management
interface (eth3). Therefore, a managed device can communicate with Junos Space by using its IPv4 or IPv6
address.
13
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)
configured for the device management interface. You can configure an IPv4 or IPv6 address for the device
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.
Table 3: Matrix for IP Address Versions Supported on Devices
14
IP Address of
Managed Devices
Supported by Junos
Spaceeth3eth0
IPv6 AddressIPv4 AddressIPv6 AddressIPv4 Address
IPv4Not ConfiguredNot ConfiguredNot ConfiguredConfigured
IPv4 and IPv6Not ConfiguredNot ConfiguredConfiguredConfigured
IPv4Not ConfiguredConfiguredNot ConfiguredConfigured
IPv4 and IPv6ConfiguredConfiguredNot ConfiguredConfigured
IPv6ConfiguredNot ConfiguredNot ConfiguredConfigured
IPv4 and IPv6ConfiguredConfiguredConfiguredConfigured
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
•
a Junos Space node through this interface. The eth0 interface and the eth1 interface can be on different
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.
NOTE:
If the managed devices are not accessible through the default gateway, you must configure
•
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
•
Platform does not forward ICMP packets through the eth3 interface. To allow ICMP packets
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:
15
Configure only the eth0 interface.
•
When only Ethernet interface (eth0) is used, the Junos Space nodes in the fabric, virtual IP (VIP) address
of the fabric, and the devices being managed by Junos Space are on the same subnet.
Configure the eth0 and eth3 interfaces.
•
When Ethernet interfaces eth0 and eth3 are used, the Junos Space nodes in the fabric and VIP address
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
VIP address of the fabric may or may not be on the same subnet. The Junos Space nodes are reachable
(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.
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 Managing Nodes in the
Junos Space Fabric chapter in the Junos Space Network Management Platform Workspaces Feature
Guide (available at https://www.juniper.net/documentation/en_US/junos-space18.1/index.html).
16
Table 4 on page 16 summarizes the functions of Ethernet interfaces on the Junos Space Virtual Appliance.
Table 4: Junos Space Virtual Appliance Ethernet Interfaces
FunctionInterface
eth0
eth1
eth3
SSH and device management, if only the Ethernet interface ETH0 or
Ethernet interface 0 is used
GUI interfaceeth0:0
SSH access to the Junos Space nodes
NOTE: SSH is disabled on the eth0 and eth3 interfaces when eth1 is
configured.
Reserved for future useeth2
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
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
17
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
Junos Space Virtual Appliance Deployment Overview
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.5 and the *.qcow2 on a Kernel-based Virtual Machine (KVM) server. The Junos Space Virtual Appliance
Release 16.1R1 and later can be deployed on qemu-kvm (KVM) Release 1.5.3-105.el7 or later which runs
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.
19
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-GB RAM to configure the virtual appliance as a Junos Space node or fault monitoring and performance
•
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
•
Configure Open VM tools (see “Starting Open VM Tools in Junos Space Platform” on page 34 for details.)
•
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 How do
I Determine the Disk I/O Speed of a Node in the Junos Space Fabric? in the Junos Space Hardware
and Virtual Appliances FAQ.
We recommend against cloning a deployed Junos Space Image and using it as another instance
•
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
20
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.
VMware VMotion is supported for moving Junos Space Virtual Appliances from one VMware
•
ESXi server to another VMware ESXi server.
For information about the minimum hardware requirements for deploying a Junos Space Virtual Appliance,
see “Junos Space Virtual Appliance Deployment Overview” on page 19.
BEST PRACTICE: We recommend the following best practices after you deploy the Junos Space
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.
The deployment of a Junos Space Virtual Appliance on a VMware ESXi server includes the following tasks:
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
21
Installing the VMware ESXi Server
To install the VMware ESXi server:
1. Download the VMware ESXi server installation package from https://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: You can install the VMware vSphere Client when you install the VMware ESXi server
5.5, 6.0, or 6.5. Contact VMware for support with installing ESXi server.
NOTE: Junos Space Network Management Platform is not certified to be used with VMware
tools.
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:
22
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
download from the Juniper Networks support site. If you change the name of the image file,
the creation of the Junos Space Virtual Appliance can fail.
2. Launch the vSphere Client that is connected to the ESXi server where the Junos Space Virtual Appliance
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.
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.
23
NOTE: Do not change the name of the Junos Space Virtual Appliance image file that you
download from the Juniper Networks support site. If you change the name of the image file,
the creation of the Junos Space Virtual Appliance can fail.
2. Log in to the local system and navigate to the location where the Junos Space Virtual Appliance image
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 is the username of the host machine where you deploy the Junos Space Virtual Appliance.
•
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:
/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:
24
1. Launch the VMware vSphere Client and log in to the ESXi server where the Junos Space Virtual Appliance
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.
To power off the Junos Space Virtual Appliance, right-click the Junos Space Virtual Appliance icon and
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.
Adding Disk Resources for a Junos Space Virtual Appliance
For information about adding disk resources for Junos Space Virtual Appliance, see “Adding Disk Resources
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
25
Deploying a Junos Space Virtual Appliance on a KVM Server
The Junos Space Virtual Appliance Release 16.1R1 and later can be deployed on qemu-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.
•
KVM server and supported packages must be installed on your Linux-based system. Contact your Linux
•
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.
•
For information about the minimum hardware requirements for deploying a Junos Space Virtual Appliance,
see “Junos Space Virtual Appliance Deployment Overview” on page 19.
The deployment of a Junos Space Virtual Appliance on a KVM server by using VMM includes the following
tasks:
NOTE: Though deploying the Junos Space Virtual Appliance on the KVM server by using virtual
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
26
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
download from the Juniper Networks support site. If you change the name of the image file,
the creation of the Junos Space Virtual Appliance can fail.
2. Launch the VMM client.
3. Select File > New Virtual Machine on the menu bar of VMM to install a new virtual machine on a KVM
server.
The New VM dialog box appears and displays Step 1 of 4 of the New VM installation.
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. Under Choose storage volume , click Browse Local at the bottom of the dialog box to locate and select
the Junos Space Virtual Appliance image file (.qcow2) saved on your system.
8. Under Choose an operating system type and version, select Linux for OS type and Red Hat Enterprise
Linux version number for Version.
NOTE: We recommend to use the same Linux version as Junos Space Platform is using.
27
9. Click Forward to go to the next step.
Step 3 of 4 is displayed.
10. Under Choose Memory and CPU settings, ensure that 4 is set for CPUs and select or enter the following
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.
The New VM dialog box closes. The Junos Space Virtual Appliance is started and the console is displayed.
The Junos Space Virtual Appliance is created and listed with the name that you entered in the VMM.
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. Select the Junos Space Virtual Appliance just created and select Edit > Virtual Machine Details on the
menu bar of VMM to edit the hardware settings.
2. Click the Show virtual hardware details icon in the Virtual Machine Details dialog box.
28
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-click the Junos Space Virtual Appliance icon and select Shutdown > Power Off, to shut down
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.
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) If the Junos Space Virtual Appliance is running, you must shut down the appliance to modify
RAM.
To shut down the Junos Space Virtual Appliance, right-click the Junos Space Virtual Appliance icon
and select Shutdown > Power Off.
3. To view and change RAM allocated to the Junos Space Virtual Appliance, select Edit > Virtual Machine
Details on the menu bar of VMM to edit the hardware settings.
29
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
For information about adding disk resources for Junos Space Virtual Appliance, see “Adding Disk Resources
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.
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
30
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.
Loading...