Juniper networks JUNOS SPACE 2.0 RELEASE NOTES User Manual

®

Junos

Virtual Appliance Installation Guide

Space

Release

2.0

Published: 2010-11-16

Revision 1

Copyright © 2010, Juniper Networks, Inc.

Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net

This productincludes the Envoy SNMP Engine, developed by Epilogue Technology, an Integrated Systems Company. Copyright© 1986-1997,
Epilogue Technology Corporation. All rights reserved. This program and its documentation were developed at private expense, and no part
of them is in the public domain.

This product includes memory allocation software developed by Mark Moraes, copyright © 1988, 1989, 1993, University of Toronto.

This product includes FreeBSD software developed by the University of California, Berkeley, and its contributors. All of the documentation
and software included in the 4.4BSD and 4.4BSD-Lite Releases is copyrighted by the Regents of the University of California. Copyright ©
1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994. The Regents of the University of California. All rights reserved.

GateD software copyright © 1995, the Regents of the University. All rights reserved. Gate Daemon was originated and developed through
release 3.0 by Cornell University and its collaborators. Gated is based on Kirton’s EGP, UC Berkeley’s routing daemon (routed), and DCN’s
HELLO routing protocol. Development of Gated has been supported in part by the National Science Foundation. Portions of the GateD
software copyright © 1988, Regents of the University of California. All rights reserved. Portions of the GateD software copyright © 1991, D.
L. S. Associates.

This product includes software developed by Maker Communications, Inc., copyright © 1996, 1997, Maker Communications, Inc.

Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, 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.

Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.

Junos Space JA1500 Appliance Installation Guide

Release 2.0. for Release Customer Testing
Copyright © 2010, Juniper Networks, Inc.
All rights reserved. Printed in USA.

Revision History
September, 2010—Junos Space JA1500 Appliance Installation Guide

The information in this document is current as of the date listed in the revision history.

YEAR 2000 NOTICE

Juniper Networks hardware and software products are Year 2000 compliant. The 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.

Copyright © 2010, Juniper Networks, Inc.ii

END USER LICENSE AGREEMENT

READ THIS END USER LICENSE AGREEMENT (“AGREEMENT”) BEFORE DOWNLOADING, INSTALLING, OR USING THE SOFTWARE.

BY DOWNLOADING, INSTALLING, OR USING THE SOFTWARE OR OTHERWISE EXPRESSING YOUR AGREEMENT TO THE TERMS
CONTAINED HEREIN, YOU (AS CUSTOMER OR IF YOU ARE NOT THE CUSTOMER, AS A REPRESENTATIVE/AGENT AUTHORIZED TO
BIND THE CUSTOMER) CONSENT TO BEBOUND BY THIS AGREEMENT. IF YOU DO NOTOR CANNOT AGREE TO THE TERMSCONTAINED
HEREIN, THEN (A) DO NOT DOWNLOAD, INSTALL, OR USE THE SOFTWARE, AND (B) YOU MAY CONTACT JUNIPER NETWORKS
REGARDING LICENSE TERMS.

1. The Parties. The parties to this Agreement are (i) Juniper Networks, Inc. (if the Customer’s principal office is located in the Americas) or
Juniper Networks (Cayman) Limited(if the Customer’s principaloffice is locatedoutside theAmericas) (such applicable entity being referred
to herein as “Juniper”), and(ii) theperson ororganizationthat originally purchasedfrom Juniper or an authorizedJuniper reseller the applicable
license(s) for use of the Software (“Customer”) (collectively, the “Parties”).

2. The Software. In this Agreement, “Software” means the program modules and features of the Juniper or Juniper-supplied software, for
which Customer has paid the applicable license or support fees to Juniper or an authorized Juniper reseller, or which was embedded by
Juniper in equipment which Customer purchased from Juniper or an authorized Juniper reseller. “Software” also includes updates, upgrades
and new releases of such software. “Embedded Software” means Software which Juniper has embedded in or loaded onto the Juniper
equipment and any updates, upgrades, additions or replacements which are subsequently embedded in or loaded onto the equipment.

3. License Grant. Subject to payment ofthe applicablefees andthe limitationsand restrictionsset forthherein, Juniper grants to Customer
a non-exclusive and non-transferable license, without right to sublicense, to use the Software, in executable form only, subject to the
following use restrictions:

a. Customer shall use Embedded Software solely as embedded in, and for execution on, Juniper equipment originally purchased by
Customer from Juniper or an authorized Juniper reseller.

b. Customer shall use the Software on a single hardware chassis having a single processing unit, or as many chassis or processing units
for which Customer has paid the applicable license fees; provided, however, with respect to the Steel-Belted Radius or Odyssey Access
Client software only, Customer shall use such Software on a single computer containing a single physical random access memory space
and containing any number of processors. Use of the Steel-Belted Radius or IMS AAA software on multiple computers or virtual machines
(e.g., Solaris zones) requires multiple licenses, regardless of whether such computers or virtualizations are physically contained on a single
chassis.

c. Product purchase documents, paper or electronic user documentation, and/or the particular licenses purchased by Customer may
specify limitsto Customer’s useof theSoftware.Such limitsmay restrict use to amaximum numberof seats, registeredendpoints, concurrent
users, sessions, calls, connections, subscribers, clusters, nodes, realms, devices, links, ports or transactions, or require the purchase of
separate licenses to use particular features, functionalities, services, applications, operations, or capabilities, or provide throughput,
performance, configuration, bandwidth, interface, processing, temporal, or geographical limits. In addition, such limits may restrict the use
of the Software to managing certain kinds of networks or require the Software to be used only in conjunction with other specific Software.
Customer’s use of the Software shall be subject to all such limitations and purchase of all applicable licenses.

d. For any trial copy of the Software, Customer’s right to use the Software expires 30 days after download, installation or use of the
Software. Customer may operate the Software after the 30-day trial period only if Customer pays for a license to do so. Customer may not
extend or create an additional trial period by re-installing the Software after the 30-day trial period.

e. The Global Enterprise Edition of the Steel-Belted Radius software may be used by Customer only to manage access to Customer’s
enterprise network. Specifically, service provider customers are expressly prohibited from using the Global Enterprise Edition of the
Steel-Belted Radius software to support any commercial network access services.

The foregoing license is not transferable or assignable by Customer. No license is granted herein to any user who did not originally purchase
the applicable license(s) for the Software from Juniper or an authorized Juniper reseller.

4. Use Prohibitions. Notwithstanding the foregoing, the license provided herein does not permit the Customer to, and Customer agrees
not to and shall not: (a) modify, unbundle, reverse engineer, or create derivative works based on the Software; (b) make unauthorized
copies of the Software (except as necessary for backup purposes); (c) rent, sell, transfer, or grant any rights in and to any copy of the
Software,in any form, to any third party; (d) remove any proprietary notices,labels, or marks on or inany copyof the Software orany product
in which the Software is embedded; (e) distribute any copy of the Software to any third party, including as may be embedded in Juniper
equipment sold inthe secondhandmarket; (f) use any‘locked’or key-restricted feature,function, service, application, operation,or capability
without first purchasing the applicable license(s) and obtaining a valid key from Juniper, even if such feature, function, service, application,
operation, or capability is enabled without a key; (g) distribute any key for the Software provided by Juniper to any third party; (h) use the

iiiCopyright © 2010, Juniper Networks, Inc.

Software in any manner that extends or is broader than the uses purchased by Customer from Juniper or an authorized Juniper reseller; (i)
use Embedded Software on non-Juniper equipment; (j) use Embedded Software (or make it available for use) on Juniper equipment that
the Customer did not originally purchase from Juniper or an authorized Juniper reseller; (k) disclose the results of testing or benchmarking
of the Software to any third party without the prior written consent of Juniper; or (l) use the Software in any manner other than as expressly
provided herein.

5. Audit. Customer shall maintain accurate records as necessary to verify compliance with this Agreement. Upon request by Juniper,
Customer shall furnish such records to Juniper and certify its compliance with this Agreement.

6. Confidentiality. The Parties agree that aspects of the Software and associated documentation are the confidential property of Juniper.
As such, Customer shall exercise all reasonable commercial efforts tomaintain the Software and associated documentation in confidence,
which at a minimum includes restricting access to the Software to Customer employees and contractors having a need to use the Software
for Customer’s internal business purposes.

7. Ownership. Juniper and Juniper’s licensors, respectively, retain ownership of all right, title, and interest (including copyright) in and to
the Software, associated documentation, and all copies of the Software. Nothing in this Agreement constitutes a transfer or conveyance
of any right, title, or interest in the Software or associated documentation, or a sale of the Software, associated documentation, or copies
of the Software.

8. Warranty, Limitation of Liability, Disclaimer of Warranty. The warranty applicable to the Software shall be as set forth in the warranty
statementthat accompanies theSoftware (the “WarrantyStatement”). Nothingin thisAgreement shall giverise toany obligation to support
the Software. Support services may be purchased separately. Any such support shall be governed by a separate, written support services
agreement. TO THE MAXIMUM EXTENT PERMITTED BY LAW, JUNIPER SHALL NOT BE LIABLE FOR ANY LOST PROFITS, LOSS OF DATA,
OR COSTSOR PROCUREMENTOF SUBSTITUTE GOODS ORSERVICES, ORFOR ANYSPECIAL, INDIRECT,OR CONSEQUENTIALDAMAGES
ARISING OUTOF THIS AGREEMENT,THE SOFTWARE, ORANY JUNIPER ORJUNIPER-SUPPLIED SOFTWARE.IN NOEVENT SHALL JUNIPER
BE LIABLE FOR DAMAGES ARISING FROM UNAUTHORIZED OR IMPROPER USE OF ANY JUNIPER OR JUNIPER-SUPPLIED SOFTWARE.
EXCEPT AS EXPRESSLY PROVIDED IN THE WARRANTY STATEMENT TO THE EXTENT PERMITTED BY LAW, JUNIPER DISCLAIMS ANY
AND ALL WARRANTIES IN AND TO THE SOFTWARE (WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE), INCLUDING ANY
IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NONINFRINGEMENT. IN NO EVENT DOES
JUNIPER WARRANT THAT THE SOFTWARE, OR ANY EQUIPMENT OR NETWORK RUNNING THE SOFTWARE, WILL OPERATE WITHOUT
ERROR OR INTERRUPTION, OR WILL BE FREE OF VULNERABILITY TO INTRUSION OR ATTACK. In no event shall Juniper’s or its suppliers’
or licensors’ liability to Customer, whether in contract, tort (including negligence), breach of warranty, or otherwise, exceed the price paid
by Customer for the Software that gave rise to the claim, or if the Software is embedded in another Juniper product, the price paid by
Customer for such other product. Customer acknowledges and agrees that Juniper has set its prices and entered into this Agreement in
reliance upon the disclaimers of warranty and the limitations of liability set forth herein, that the same reflect an allocation of risk between
the Parties (including the risk that a contract remedy may fail of its essential purpose and cause consequential loss), and that the same
form an essential basis of the bargain between the Parties.

9. Termination. Any breach of this Agreement or failure by Customer to pay any applicable fees due shall result in automatic termination
of the license granted herein. Upon such termination, Customer shall destroy or return to Juniper all copies of the Software and related
documentation in Customer’s possession or control.

10. Taxes. All license fees payable under this agreement are exclusive of tax. Customer shall be responsible for paying Taxes arising from
the purchase of the license, or importation or use of the Software. If applicable, valid exemption documentation for each taxing jurisdiction
shall be provided to Juniper prior to invoicing, and Customer shall promptly notify Juniper if their exemption is revoked or modified. All
payments made by Customer shall be net of any applicable withholding tax. Customer will provide reasonable assistance to Juniper in
connection with such withholding taxes by promptly: providing Juniper with valid tax receipts and other required documentation showing
Customer’s payment of any withholding taxes; completing appropriate applications that would reduce the amount of withholding tax to
be paid; and notifying and assisting Juniper in any audit or tax proceeding related to transactions hereunder. Customer shall comply with
all applicable tax laws and regulations, and Customer will promptly pay or reimburse Juniper for all costs and damages related to any
liability incurred by Juniper as a result of Customer’s non-compliance or delay with its responsibilities herein. Customer’s obligations under
this Section shall survive termination or expiration of this Agreement.

11. Export. Customer agrees to comply with all applicable export laws and restrictions and regulations of any United States and any
applicable foreign agency or authority, and not to export or re-export the Software or any direct product thereof in violation of any such
restrictions, laws or regulations, or without all necessary approvals. Customer shall be liable for any such violations. The version of the
Software supplied to Customer may contain encryption or other capabilities restricting Customer’s ability to export the Software without
an export license.

Copyright © 2010, Juniper Networks, Inc.iv

12. Commercial Computer Software. The Software is “commercial computer software” and is provided with restricted rights. Use,
duplication, or disclosure by the United States government is subject to restrictions set forth in this Agreement and as provided in DFARS

227.7201 through 227.7202-4, FAR 12.212, FAR 27.405(b)(2), FAR 52.227-19, or FAR 52.227-14(ALT III) as applicable.

13. Interface Information. To the extent required by applicable law, and at Customer's written request, Juniper shall provide Customer
with the interface information needed to achieve interoperability between the Software and another independently created program, on
payment of applicable fee, if any. Customer shall observe strict obligations of confidentiality with respect to such information and shall use
such information in compliance with any applicable terms and conditions upon which Juniper makes such information available.

14. Third Party Software. Any licensor of Juniper whose software is embedded inthe Softwareand any supplier ofJuniper whose products
or technology are embedded in (or services are accessed by) the Software shall be a third party beneficiary with respect to this Agreement,
and such licensor or vendor shall have the right to enforce this Agreement in its own name as if it were Juniper. In addition, certain third party
software may be provided with the Software and is subject to the accompanying license(s), if any, of its respective owner(s). To the extent
portions of the Software are distributed under and subject to open source licenses obligating Juniper to make the source code for such
portions publicly available (such as the GNU General Public License (“GPL”) or the GNU Library General Public License (“LGPL”)), Juniper
will make such source code portions (including Juniper modifications, as appropriate) available upon request for a period of up to three
years from the date of distribution. Such request can be made in writing to Juniper Networks, Inc., 1194 N. Mathilda Ave., Sunnyvale, CA
94089, ATTN: General Counsel. You may obtain a copy of the GPL at http://www.gnu.org/licenses/gpl.html, and a copy of the LGPL

at http://www.gnu.org/licenses/lgpl.html .

15. Miscellaneous. This Agreement shall be governed by the laws of the State of California without reference to its conflicts of laws
principles. The provisions of the U.N. Convention for the International Sale of Goods shall not apply to this Agreement. For any disputes
arising under this Agreement, the Parties hereby consent to the personal and exclusive jurisdiction of, and venue in, the state and federal
courts within Santa Clara County, California. This Agreement constitutes the entire and sole agreement between Juniper and the Customer
with respect to the Software, and supersedes all prior and contemporaneous agreements relating to the Software, whether oral or written
(including any inconsistent terms contained in a purchase order), except that the terms of a separate written agreement executed by an
authorized Juniper representative and Customer shall govern to the extent such terms are inconsistent or conflict with terms contained
herein. No modification to this Agreement nor any waiver of any rights hereunder shall be effective unless expressly assented to in writing
by the party to be charged. If any portion of this Agreement is held invalid, the Parties agree that such invalidity shall not affect the validity
of the remainder of this Agreement. This Agreement and associated documentation has been written in the English language, and the
Parties agree that the English version will govern. (For Canada: Les parties aux présentés confirment leur volonté que cette convention de
même que tous les documents y compris tout avis qui s'y rattaché, soient redigés en langue anglaise. (Translation: The parties confirm that
this Agreement and all related documentation is and will be in the English language)).

vCopyright © 2010, Juniper Networks, Inc.

Copyright © 2010, Juniper Networks, Inc.vi

Table of Contents

About The Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Junos OS Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii

Part 1 Overview

Chapter 1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Junos Space Virtual Appliance Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Understanding How Nodes Are Connected in a Fabric . . . . . . . . . . . . . . . . . . . 3

Virtual Appliance Deployment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Recommendations for Deploying Virtual Appliances on the VMware ESX

Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Configuring an NTP Time Source For Each Appliance . . . . . . . . . . . . . . . . . . . 5

Fabric Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Single Node Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Multinode Functionality . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Node Function Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Understanding How Junos Space Uses Ethernet Interfaces eth0 and eth3 . . . . . . 9

Part 2 Installation and Configuration

Chapter 2 Deploying a Virtual Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Deploying a Junos Space Virtual Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing the VMware ESX Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Extracting Files from the Junos Space Virtual Appliance Package . . . . . . . . . 14

Converting a Virtual Appliance to a Virtual Machine by Using the OVT

Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Increasing RAM and Virtual Processors (CPU) for a Junos Space Virtual

Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Adding Disk Resources for a Junos Space Virtual Appliance . . . . . . . . . . . . . . 17

viiCopyright © 2010, Juniper Networks, Inc.

Junos Space Virtual Appliance Installation Guide

Chapter 3 Configuring a Virtual Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Configuring Basic Settings for a Junos Space Virtual Appliance . . . . . . . . . . . . . . 19

Configuring an Appliance that is the First Node in a Cluster or that Will Not

Configuring an Appliance to Add to an Existing Cluster . . . . . . . . . . . . . . . . . 23

Changing Network and System Settings for a Junos Space Virtual Appliance . . . 25

Changing the Password . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Setting Routing Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Adding DNS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Setting the System Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Retrieve Logs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Expand VM Drive Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Setting Security Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

(Debug) Run Shell . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Part 3 Upgrades

Chapter 4 Upgrading Junos Space Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Junos Space Software Upgrade Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Upgrading Junos Space Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Junos Space 2.0 Release Highlights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Upgrading Junos Space Release 1.3 or 1.4 to Release 2.0 . . . . . . . . . . . . . . . . 35

Be Added to an Existing Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Part 4 Accessing the Junos Space User Interface

Chapter 5 Logging In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Logging In to the Junos Space User Interface as Super Administrator . . . . . . . . . 39

Chapter 6 Adding a Node to the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Adding a Node to an Existing Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Part 5 License Key Management

Chapter 7 Junos Space License Key Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Generating and Uploading the Junos Space License Key File . . . . . . . . . . . . . . . . 45

Generating the License Key File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Uploading the License Key File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Part 6 Index

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

Copyright © 2010, Juniper Networks, Inc.viii

List of Tables

About The Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi

Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii

Part 1 Overview

Chapter 1 Installation Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Table 2: How Junos Space IP Addresses Function . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Part 2 Installation and Configuration

Chapter 2 Deploying a Virtual Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Table 3: Files in the space-2.0R1.x Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

ixCopyright © 2010, Juniper Networks, Inc.

Junos Space Virtual Appliance Installation Guide

Copyright © 2010, Juniper Networks, Inc.x

About The Documentation

•

Junos OS Documentation and Release Notes on page xi

•

Documentation Conventions on page xii

•

Documentation Feedback on page xii

•

Requesting Technical Support on page xii

Junos OS Documentation and Release Notes

For a list of related Junos Space documentation, see

http://www.juniper.net/techpubs/en_US/release-independent/junos-space/index.html .

If the information in the latest release notes differs from the information in the
documentation, follow the Junos Space Release Notes.

To obtain the most current version of all Juniper Networks technical documentation, see
the technical documentation page at the Juniper Networks website at

http://www.juniper.net/techpubs/ .

Juniper Networks supportsa technical bookprogram to publish books byJuniper Networks
engineers and subject matter experts with book publishers around the world. These
books go beyond the technical documentation to explore the nuances of network
architecture, deployment, and administration using the Junos operating system (Junos
OS) and Juniper Networks devices. In addition, the Juniper Networks Technical Library,
published in conjunction with O'Reilly Media, explores improving network security,
reliability, and availability using Junos OS configuration techniques. All the books are for
sale at technical bookstores and book outlets around the world. The current list can be
viewed at http://www.juniper.net/books .

xiCopyright © 2010, Juniper Networks, Inc.

Junos Space Virtual Appliance Installation Guide

Documentation Conventions

Table 1: Notice Icons

DescriptionMeaningIcon

Indicates important features or instructions.Informational note

Indicates a situation that might result in loss of data or hardware damage.Caution

Alerts you to the risk of personal injury or death.Warning

Alerts you to the risk of personal injury from a laser.Laser warning

Documentation Feedback

We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to

[e-mail], or fill out the documentation feedback form at

https://www.juniper.net/cgi-bin/docbugreport/. If you are using e-mail, be sure to include

the following information with your comments:

•

Document or topic name

•

URL or page number

•

Software release version (if applicable)

Requesting Technical Support

Technical product support is available through the Juniper NetworksTechnical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC 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

http://www.juniper.net/us/en/local/pdf/resource-guides/7100059-en.pdf .

•

Product warranties—For product warranty information, visit

http://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.

Copyright © 2010, Juniper Networks, Inc.xii

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: http://www.juniper.net/customers/support/

•

Search for known bugs: http://www2.juniper.net/kb/

•

Find product documentation: http://www.juniper.net/techpubs/

•

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

•

Download the latest versions of software and review release notes:

http://www.juniper.net/customers/csc/software/

•

Search technical bulletins for relevant hardware and software notifications:

https://www.juniper.net/alerts/

•

Join and participate in the Juniper Networks Community Forum:

http://www.juniper.net/company/communities/

About The Documentation

•

Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/

To verify service entitlement byproduct serial number, useour SerialNumber Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/

Opening a Case with JTAC

You can open a case with JTAC on the Web or by telephone.

•

Use the Case Management tool in the CSC at http://www.juniper.net/cm/ .

•

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

http://www.juniper.net/support/requesting-support.html .

xiiiCopyright © 2010, Juniper Networks, Inc.

Junos Space Virtual Appliance Installation Guide

Copyright © 2010, Juniper Networks, Inc.xiv

PART 1

Overview

•

Installation Overview on page 3

1Copyright © 2010, Juniper Networks, Inc.

Junos Space Virtual Appliance Installation Guide

Copyright © 2010, Juniper Networks, Inc.2

CHAPTER 1

Installation Overview

•

Junos Space Virtual Appliance Overview on page 3

•

Fabric Management Overview on page 5

•

Understanding How Junos Space Uses Ethernet Interfaces eth0 and eth3 on page 9

Junos Space Virtual Appliance Overview

The Junos Space Virtual Appliance consists of preconfigured Junos Space 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 the VMware ESX or ESXi 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.

You cancreatea fabricof JA1500Junos Spaceappliances, Junos Space virtual appliances,
or a hybrid fabric of both physical and virtual appliances.

Understanding How Nodes Are Connected in a Fabric

Each Junos Space appliance (physical or virtual) that you install and configure is
represented as a single node in the fabric. You can add nodes without disrupting the
services that are running on the fabric. When you install and configure the first appliance,
Junos Space automatically creates a fabric with one node. For each additional appliance
you install and configure, you must add a node to logically represent the appliance in the
fabric. You add nodes to the fabric from the Administrationworkspace in the JunosSpace
user interface. Each node that you add to the fabric increases the resource pool for the
node functions to meet the scalability and availability requirements of your network. By
default, Junos Space automatically enables node functionality across the nodes in the
fabric to distribute workload. The nodes in the fabric work together to providea virtualized
resource pool for each of the node functions: load balancer, database, and application
logic.

3Copyright © 2010, Juniper Networks, Inc.

Junos Space Virtual Appliance Installation Guide

In a fabric comprising two or more nodes, Junos Space provides failover when a node
functioning as the active server (load balancer server or database server) goes down. By
default, Junos Space marks a particular node down and routes failover requests to the
node that Junos Space designates as standby server. Junos Space uses a heartbeat
mechanism to check whether the nodes in the fabric are running. When a node functioning
as the active server fails (the appliance crashes or stops sending heartbeats), the node
functioning as the standby server takes over all resources that were managed by the
node functioning as active server. Nodes in a Junos Space fabric rely on IP multicast
messagesto discover each other, therefore ensurethat IPmulticastpackets are reachable
between all nodes.

To add, manage, and monitor the nodes in the fabric, a Junos Space user connects to a
single Web IP address. The IP address of first (active) node and second (standby) node,
and the Web (virtual) IP address must all be in the same subnet. The Web IP needs to
work on both thefirst and second nodein the fabric. When both nodes are in same subnet,
and the first (active) node goes down, the second (standby) node becomes the active
node and packets continue to be directed from the router, to the Junos Space Web IP,
and then to the second node, because both nodes are in same subnet. However, if the
second (standby) node is configured in a different subnet than the first (active) node,
and the first node goes down, the second node becomes the active node, but because
the Web IP now points to the different subnet of the second node, all packets originally
destined for first node won’t be received by the second node.

Virtual Appliance Deployment

The Junos Space Virtual Appliance is stored in the Open Virtualization Format (OVF) 1.0
and is packaged as an *.ovf file, which is a tar file that contains all the files of the Junos
Space Virtual Appliance. OVF is not a bootable format, and you must deploy each Junos
Space Virtual Appliance to a hosted ESX or ESXi server before you can run the Junos
Space Virtual Appliance.

You can deploy a Junos Space Virtual Appliance on a VMware ESX server, version 3.5. or
higher, or ESXi version 4.0 or higher to convert the Junos Space Virtual Appliance to a
virtual machine. Afterthe Junos Space Virtual Appliance is converted toa virtual machine,
you use the VMware vSphere client that isconnected to the VMware ESX (orESXi) Server
to deploy the Junos Space Virtual Appliance on the server.

NOTE: Where the Junos Space Virtual Appliance documentation references

“ESX server” you can use either the ESX server Version 3.5 or later, or ESXi
server, Version 4.0 or later.

Recommendations for Deploying Virtual Appliances on the VMware ESX Server

The CPU, RAM, and disk space provided by the VMware ESX server must meet or exceed
the documented CPU, RAM, and disk space requirements for deploying a Junos Space
Virtual Appliance. In addition, Juniper recommends that, for a multi-node fabric, you
deploy the first and second virtual appliance on separate VMware ESX servers to ensure
failover support.

Copyright © 2010, Juniper Networks, Inc.4

The distributed Junos Space Virtual Appliance files are created with 5 GB of disk space,
and you add an additional 40GB of disk resources when you first deploy the virtual
appliance to a VMware ESX server. In many cases, the 45 GB of disk space will be
sufficient; however, if the percent of Junos Space disk resources utilized reaches 80%
capacity, Juniper recommends that you add another 40 GB of disk space to your virtual
appliance. You can monitor the percent of disk space utilized in the Fabric Monitor
inventory panel in the Junos Space user interface.

Configuring an NTP Time Source For Each Appliance

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

Chapter 1: Installation Overview

NOTE: By default, Junos Space translates time so that the time displayed in

the user interface corresponds to Junos Space server time, but the time is
mapped to the local time zone of your client computer.

To ensure time remains synchronized across all nodes in the fabric, Juniper strongly
recommends that youadd an NTP server to the first appliance(physical orvirtual) during
initial set up.

NOTE: You must add the NTP server before you add the appliance/node to

the fabric from the Junos Space user interface.

Fabric Management Overview

You can deploy Junos Space appliances to create a fabric that provides the scalability
and availability that your managed network requires as you add more devices, services,
and users.

A Junos Space fabric comprises one or more IP-connected nodes. A node is a logical
object that represents a single JA1500 Junos Space Appliance or Junos Space Virtual
Appliance, its operatingsystem, and the JunosSpace software thatruns onthe operating
system. Each Junos Space appliance or virtual appliance that you install and configure
is represented as a single node in the fabric. You can add nodes without disrupting the
services that arerunning on the fabric. Whenyou add nodesto the fabric, you canmanage
and monitor the nodes fromthe Administration workspace. Toadd, manage, and monitor
nodes in the fabric, a fabric administrator connects to asingle virtual IP address, asshown
in the illustration.

5Copyright © 2010, Juniper Networks, Inc.

Junos Space Virtual Appliance Installation Guide

Single Node Functionality

When thefabric comprises a single appliance,all devices in the managednetwork connect
to the appliance. When you install and configure the first appliance, Junos Space
automatically creates a fabric with one node. By default, a fabric that consists of a single
node provides completeJunos Space managementfunctionality,with thefollowingnode
functions enabled for the node:

•

Load Balancer— for processing HTTP requests from remote browsers and NBI clients

•

Database— for processing database requests (create, read, update, and delete
operations)

•

Application Logic— for processing back-end business logic (Junos Space service
requests) and DML workload (device connectivity, device events, and logging)

NOTE: All appliances (nodes) in a fabric must be from same Junos Space

release. For example, a fabric comprises Junos Space Release 1.4 appliances
or Junos Space Release 2.0 appliances, but not both.

NOTE: A fabric that comprises a single node providesno workload balancing
and no backup if the appliance goes down.

Copyright © 2010, Juniper Networks, Inc.6