Junos Space Junos Space Frequently Asked Questions 14.1

Junos Space
Junos® Space Frequently Asked Questions
Release
14.1
Published: 2014-11-06
Copyright © 2014, Juniper Networks, Inc.
Juniper Networks, Inc.
1194 North Mathilda Avenue
Sunnyvale, California 94089
USA
408-745-2000
www.juniper.net
Copyright © 2014, Juniper Networks, Inc. All rights reserved.
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.
®
Junos Space Junos Space Frequently Asked Questions
14.1
Copyright © 2014, 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
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
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
that EULA.
ii
Copyright © 2014, Juniper Networks, Inc.
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Part 1
FAQ
Chapter 1
Junos Space Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
What Is the Supported Junos Space Release Upgrade Path? . . . . . . . . . . . . . . . . . 3
How Do I Back Up the Junos Space Software To the Database Before
Upgrading? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
How Do I Upgrade Junos Space? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Chapter 2
Junos Space User Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
What Web Browsers Does Junos Space User Interface Support? . . . . . . . . . . . . . . 5
Which Web Browser Plug-Ins Does the Junos Space User Interface Require? . . . . 5
Which Operating Systems Does the Junos Space User Interface Support? . . . . . . 6
What Display Resolution Is Recommended for Running the Junos Space User
Interface? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Does the Junos Space User Interface Support Both HTTP and HTTPS? . . . . . . . . 6
What URL Should Be Used to Access the Junos Space User Interface? . . . . . . . . . 6
What Is the Default Userid/Password for the Junos Space User Interface? . . . . . . 6
Chapter 3
Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Which Juniper Networks Platforms Does Junos Space Network Management
Platform Software Support? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
What Junos Releases Are Supported in Different Junos Space Applications? . . . 10
What Minimum Configuration Do Network Devices Require for Junos Space
Software to Manage Them? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
What Port on the Junos Space Node Does a Device Connect To? . . . . . . . . . . . . . 12
Does Using Junos Space Software to Discover Devices That Are Connected to
AIS and SRC Affect Those Connections? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
IPv6 and Junos Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Chapter 4
Junos Space Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What Are the Hardware Specifications for the Junos Space JA1500
Appliance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What Configuration Does Junos Space Require to Run the Virtual Appliance? . . . 13
Copyright © 2014, Juniper Networks, Inc.
iii
®
Junos Space Frequently Asked Questions
Can I Change the IP Address of a Junos Space Node That Has Been
Deployed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
After Installing a Junos Space Virtual Appliance, Why Do I Get a “Login Incorrect”
Error When I Try to Log In to the Virtual Appliance from the Console? . . . . . . 15
Chapter 5
Running Junos Space on NSM3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Installing the Junos Space Software on Network and Security Manager
NSM3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Chapter 6
Fabric Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Can I Mix Hardware Appliances and Virtual Appliances When I Create a
Fabric? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Chapter 7
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Where Are the Log Files Required for Troubleshooting? . . . . . . . . . . . . . . . . . . . . . 21
Chapter 8
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
How Does Junos Space Look For a Topology? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
How Is Topology Discovery Different from Device Discovery? . . . . . . . . . . . . . . . . 23
What Is a Target Device in Topology Discovery? . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
What Topology Discovery Methods Are Supported Per Platform Device for
Network Monitoring? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 9
Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
What are WW Junos OS devices? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
How Is Connecting to Devices Running on Worldwide Junos OS Different From
Connecting to Those Running Domestic Junos OS? . . . . . . . . . . . . . . . . . . . . 27
Chapter 10
High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
What Steps Do I Need to Take When One of the High Availability Nodes in the
Cluster Shows the Status “Down”? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
What Algorithm Does the Apache HTTP Load Balancer Use to Distribute Load
Among Nodes in the Cluster? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
How Do I Determine Which Node in the Cluster Is Handling My Network
Management Platform User Interface Session? . . . . . . . . . . . . . . . . . . . . . . . 30
How Do I Determine Which Device Connections Are Being Handled by a
Node? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
How Can I Simulate a Virtual IP (VIP) Failover? . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Part 2
Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
iv
Copyright © 2014, Juniper Networks, Inc.
List of Figures
Part 1
FAQ
Chapter 10
High Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 1: Using the netstat Command to SSH to the Console of a Node . . . . . . . . 30
Copyright © 2014, Juniper Networks, Inc.
v
®
Junos Space Frequently Asked Questions
vi
Copyright © 2014, Juniper Networks, Inc.
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Part 1
FAQ
Chapter 3
Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Table 3: Junos Space Network Management Platform Device Support . . . . . . . . . . 7
Chapter 8
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 4: Topology Discovery Methods Supported Per Platform Device for Network
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Copyright © 2014, Juniper Networks, Inc.
vii
®
Junos Space Frequently Asked Questions
viii
Copyright © 2014, Juniper Networks, Inc.
About the Documentation
•
Documentation and Release Notes on page ix
•
Documentation Conventions on page ix
•
Documentation Feedback on page xi
•
Requesting Technical Support on page xii
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
http://www.juniper.net/techpubs/.
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 http://www.juniper.net/books.
Documentation Conventions
Table 1 on page x defines notice icons used in this guide.
Copyright © 2014, Juniper Networks, Inc.
ix
®
Junos Space Frequently Asked Questions
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 x 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:
[email protected]> configure
Fixed-width text like this
Italic text like this
Italic text like this
x
Represents output that appears on the
terminal screen.
[email protected]> show chassis alarms
•
Introduces or emphasizes important
new terms.
•
•
Identifies guide names.
A policy term is a named structure
that defines match conditions and
actions.
•
Identifies RFC and Internet draft titles.
•
Junos OS CLI User Guide
•
RFC 1997, BGP Communities Attribute
Represents variables (options for which
you substitute a value) in commands or
configuration statements.
No alarms currently active
Configure the machine’s domain name:
[edit]
[email protected]# set system domain-name
domain-name
Copyright © 2014, Juniper Networks, Inc.
About the Documentation
Table 2: Text and Syntax Conventions (continued)
Convention
Description
Examples
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.
stub <default-metric metric>;
| (pipe symbol)
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.
broadcast | multicast
# (pound sign)
Indicates a comment specified on the
same line as the configuration statement
to which it applies.
rsvp { # Required for dynamic MPLS only
[ ] (square brackets)
Encloses a variable for which you can
substitute one or more values.
community name members [
community-ids ]
Indention and braces ( { } )
Identifies a level in the configuration
hierarchy.
; (semicolon)
Identifies a leaf statement at a
configuration hierarchy level.
(string1 | string2 | string3)
[edit]
routing-options {
static {
route default {
nexthop address;
retain;
}
}
}
GUI Conventions
Bold text like this
Represents graphical user interface (GUI)
items you click or select.
> (bold right angle bracket)
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, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•
Online feedback rating system—On any page at the Juniper Networks Technical
Documentation site at http://www.juniper.net/techpubs/index.html, simply click the
stars to rate the content, and use the pop-up form to provide us with information about
your experience. Alternately, you can use the online feedback form at
https://www.juniper.net/cgi-bin/docbugreport/.
Copyright © 2014, Juniper Networks, Inc.
xi
®
Junos Space Frequently Asked Questions
•
E-mail—Send your comments to [email protected] 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 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.
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:
http://kb.juniper.net/InfoCenter/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number 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.
xii
•
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).
Copyright © 2014, Juniper Networks, Inc.
About the Documentation
For international or direct-dial options in countries without toll-free numbers, see
http://www.juniper.net/support/requesting-support.html.
Copyright © 2014, Juniper Networks, Inc.
xiii
®
Junos Space Frequently Asked Questions
xiv
Copyright © 2014, Juniper Networks, Inc.
PART 1
FAQ
•
Junos Space Software Upgrade on page 3
•
Junos Space User Interface on page 5
•
Device Management on page 7
•
Junos Space Appliance on page 13
•
Running Junos Space on NSM3000 on page 17
•
Fabric Management on page 19
•
Troubleshooting on page 21
•
Topology on page 23
•
Adapters on page 27
•
High Availability on page 29
Copyright © 2014, Juniper Networks, Inc.
1
®
Junos Space Frequently Asked Questions
2
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 1
Junos Space Software Upgrade
•
What Is the Supported Junos Space Release Upgrade Path? on page 3
•
How Do I Back Up the Junos Space Software To the Database Before
Upgrading? on page 3
•
How Do I Upgrade Junos Space? on page 4
What Is the Supported Junos Space Release Upgrade Path?
Junos Space Network Management Platform Release supports an upgrade to 14.1R1 from
the following releases : 13.3R1.9, 13.3R2.6, 13.1R1.6 13.1P5.3, 13.1P6.3, and 13.1P1.14.
Related
Documentation
•
How Do I Upgrade Junos Space? on page 4
•
How Do I Back Up the Junos Space Software To the Database Before Upgrading? on
page 3
•
Upgrading Junos Space Software Overview
How Do I Back Up the Junos Space Software To the Database Before Upgrading?
To back up the database:
1.
Select Network Management Platform > Administration > Database Backup and Restore
> Database Backup.
The Database Backup dialog box appears.
2. Choose to back up the database locally or remotely.
3. If you choose to back up the database locally, be sure to move the backup files to a
safe location off of the Junos Space server.
The local backup files are saved in /var/cache/jboss/backup.
NOTE: Be sure to back up ALL of the files (db, index and ip) in the backup
directory.
Copyright © 2014, Juniper Networks, Inc.
3
®
Junos Space Frequently Asked Questions
Related
Documentation
•
What Is the Supported Junos Space Release Upgrade Path? on page 3
•
How Do I Upgrade Junos Space? on page 4
How Do I Upgrade Junos Space?
NOTE: We recommend that you use Mozilla Firefox. See “What Web Browsers
Does Junos Space User Interface Support?” on page 5.
The “What Is the Supported Junos Space Release Upgrade Path?” on page 3 topic
provides information about the release from which you can upgrade to the current release.
NOTE: When you perform an upgrade on a single- or multi-node fabric, the
installation status is shown during the installation process.
For instructions on how to upgrade Junos Space Network Management Platform, refer
to the Upgrading Junos Space Network Management Platform topic.
Related
Documentation
4
•
What Is the Supported Junos Space Release Upgrade Path? on page 3
•
How Do I Back Up the Junos Space Software To the Database Before Upgrading? on
page 3
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 2
Junos Space User Interface
•
What Web Browsers Does Junos Space User Interface Support? on page 5
•
Which Web Browser Plug-Ins Does the Junos Space User Interface Require? on page 5
•
Which Operating Systems Does the Junos Space User Interface Support? on page 6
•
What Display Resolution Is Recommended for Running the Junos Space User
Interface? on page 6
•
Does the Junos Space User Interface Support Both HTTP and HTTPS? on page 6
•
What URL Should Be Used to Access the Junos Space User Interface? on page 6
•
What Is the Default Userid/Password for the Junos Space User Interface? on page 6
What Web Browsers Does Junos Space User Interface Support?
The Junos Space user interface supports the following Web browsers:
•
Mozilla Firefox versions 3.6 and later
•
Internet Explorer versions 8.0 and 9.0
•
Google Chrome version 17 and later
NOTE: Before you log in to Junos Space, ensure that the Adobe Flash version
10 or later plug-in is installed in your browser.
NOTE: Chrome Frame plugin is required along with the Internet Explorer
browser to use the Topology Discovery feature.
Related
Documentation
•
Junos® Space Frequently Asked Questions
Which Web Browser Plug-Ins Does the Junos Space User Interface Require?
The following plug-in is required:
•
Flash Player 10 or later
Copyright © 2014, Juniper Networks, Inc.
5
®
Junos Space Frequently Asked Questions
•
Chrome Frame plugin with the Internet Explorer browser.
Which Operating Systems Does the Junos Space User Interface Support?
The Junos Space user interface is accessed via a Web browser and there are no
dependencies on the operating system.
What Display Resolution Is Recommended for Running the Junos Space User Interface?
The Junos Space user interface has been optimized for a display resolution of 1280x1024.
If the resolution is lower, the complete Junos Space user interface screen cannot be
displayed within the browser page and scroll bars will not appear.
Does the Junos Space User Interface Support Both HTTP and HTTPS?
No, the Junos Space software supports only HTTPS.
What URL Should Be Used to Access the Junos Space User Interface?
Access the Junos Space user interface through the URL https://virtual-IP, where virtual-IP
is the Virtual IP address assigned to the Junos Space Fabric. This IP address is assigned
to the eth0:0 interface on the fabric node that hosts the active load balancer.
WARNING: To avoid a BEAST TLS 1.0 attack, whenever you log in to Junos
Space in a browser tab or window, make sure that tab or window was not
previously used to access a non-https website. Best practice is to close your
browser and relaunch it before logging in to Junos Space.
Related
Documentation
•
Logging In to Junos Space
What Is the Default Userid/Password for the Junos Space User Interface?
The default username is super. The default password is juniper123. This user ID has system
administrator privileges and has complete access to all user interface functionality.
Related
Documentation
6
•
What URL Should Be Used to Access the Junos Space User Interface? on page 6
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 3
Device Management
•
Which Juniper Networks Platforms Does Junos Space Network Management Platform
Software Support? on page 7
•
What Junos Releases Are Supported in Different Junos Space Applications? on page 10
•
What Minimum Configuration Do Network Devices Require for Junos Space Software
to Manage Them? on page 11
•
What Port on the Junos Space Node Does a Device Connect To? on page 12
•
Does Using Junos Space Software to Discover Devices That Are Connected to AIS and
SRC Affect Those Connections? on page 12
•
IPv6 and Junos Space on page 12
Which Juniper Networks Platforms Does Junos Space Network Management Platform
Software Support?
Table 3 on page 7 lists all the product series and devices supported by Junos Space
Network Management Platform software. The Junos Space Network Management
Platform release notes lists only the new devices that are supported with that release.
Table 3: Junos Space Network Management Platform Device Support
Product Series
Devices
ACX Series
ACX1000
ACX1100
ACX2000
ACX2100
ACX2200
ACX4000
BX Series
Copyright © 2014, Juniper Networks, Inc.
BX7000
7
®
Junos Space Frequently Asked Questions
Table 3: Junos Space Network Management Platform Device Support (continued)
Product Series
Devices
EX Series
EX2200
EX3200
EX3300
EX4200
EX4200-Copper
EX4300
EX4500
EX4550
EX4550-40G
EX6200
EX8208
EX8216
EX9200
EX9204
EX9208
EX Virtual Chassis
EX3300-VC
EX4200-VC
EX4500-VC
EX6200-VC
MIXED-MODE-EX-VC
EX-XRE
Firefly
VSRX-Firefly
J Series
J2320
J2350
J4350
J6350
LN Series
LN1000
LN2600
8
Copyright © 2014, Juniper Networks, Inc.
Chapter 3: Device Management
Table 3: Junos Space Network Management Platform Device Support (continued)
Product Series
Devices
M Series
M7i
M10i
M40e
M120
M320
MCG Series
MCG5000
MX Series
MX5
MX10
MX80
MX104
MX240
MX480
MX960
MX2010
MX2020
MX Virtual Chassis
MX-VC
PTX Series
PTX3000
PTX5000
QFX Series
QFX3000
QFX3000-G
QFX3000-M
QFX3500
QFX3600
QFX5100
QFX5100-96S
QFX Virtual Chassis
Copyright © 2014, Juniper Networks, Inc.
QFX-VC
9
®
Junos Space Frequently Asked Questions
Table 3: Junos Space Network Management Platform Device Support (continued)
Product Series
Devices
SRX Series
SRX100
SRX110H-VB
SRX210
SRX220
SRX240
SRX550
SRX650
SRX1400
SRX3400
SRX3600
SRX5400
SRX5600
SRX5800
X45-Major 3 - SW
X44-D10-Minor-SW
T Series
T320
T640
T1600
T4000
TX Matrix
TX Matrix Plus
TXP-3D
WLC Series
WLC device
What Junos Releases Are Supported in Different Junos Space Applications?
The following Junos software releases are supported in different Junos Space applications:
10
•
Junos OS Release 9.3
•
Junos OS Release 9.4
•
Junos OS Release 9.5
Copyright © 2014, Juniper Networks, Inc.
Chapter 3: Device Management
•
Junos OS Release 9.6
•
Junos OS Release 10.0
•
Junos OS Release 10.1
•
Junos OS Release 10.2
•
Junos OS Release 10.3
•
Junos OS Release 10.4
•
Junos OS Release 11.1
•
Junos OS Release 11.2
•
Junos OS Release 11.3
•
Junos OS Release 11.4
•
Junos OS Release 12.1
•
Junos OS Release 12.2
•
Junos OS Release 12.3
•
Junos OS Release 13.1
•
Junos OS Release 13.2
•
Junos OS Release 13.3
•
Junos OS Release 14.1
What Minimum Configuration Do Network Devices Require for Junos Space Software
to Manage Them?
Junos Space software requires that the devices have the following minimum configuration
as a prerequisite to discover and manage them:
•
An in-band or out-of-band static management IP configured on the device. This IP
address must be reachable from the Junos Space server.
•
A user ID belonging to the superuser class exists on the device. The Junos Space
software uses this user ID to authenticate the SSH connection with the device.
•
SSH v2 is enabled on the device. You can use the following command to enable SSH
v2 on the device:
set system services ssh protocol-version v2
Related
Documentation
•
Ping and SNMP is enabled on the device. Ping and SNMP is used to confirm whether
the device is reachable and whether it is a Juniper Networks device, before adding it
to the system.
•
SNMP is enabled on the device with appropriate read-only V1/V2C/V3 credentials if
you plan to use SNMP to probe devices as part of the device discovery process.
•
Discovering Devices
Copyright © 2014, Juniper Networks, Inc.
11
®
Junos Space Frequently Asked Questions
What Port on the Junos Space Node Does a Device Connect To?
Devices managed by Junos Space connect to port 7804 on the Junos Space node.
Does Using Junos Space Software to Discover Devices That Are Connected to AIS and
SRC Affect Those Connections?
No, using Junos Space software to discover devices that are connected to AIS and SRC
does not affect the existing connections these devices might have. When Junos Space
software discovers and manages these devices, it automatically configures them to
connect to the Junos Space server by adding a new client entry under the
system/services/outbound-ssh stanza.
IPv6 and Junos Space
You can use Configuration Editor or Device Templates to configure IPv6 on devices
running Junos Release 10.2 and above.
12
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 4
Junos Space Appliance
•
What Are the Hardware Specifications for the Junos Space JA1500
Appliance? on page 13
•
What Configuration Does Junos Space Require to Run the Virtual Appliance? on page 13
•
Can I Change the IP Address of a Junos Space Node That Has Been
Deployed? on page 15
•
After Installing a Junos Space Virtual Appliance, Why Do I Get a “Login Incorrect” Error
When I Try to Log In to the Virtual Appliance from the Console? on page 15
What Are the Hardware Specifications for the Junos Space JA1500 Appliance?
For the latest Junos Space JA1500 appliance hardware specifications, see the Junos
Space Product Datasheet at
http://www.juniper.net/us/en/products-services/software/junos-platform/junos-space/platform/#specifications.
Related
Documentation
•
Junos Space JA1500 Appliance Overview
•
Parts of the Junos Space JA1500 Appliance
What Configuration Does Junos Space Require to Run the Virtual Appliance?
In order to deploy a Junos Space Virtual Appliance, you must be running a VMware ESX
server version 4.0 or later that can support a virtual machine with the following
configuration:
•
64-bit Quad processor with at least 2.66 GHz
•
Four virtual CPUs
•
16-GB RAM to configure the virtual appliance as a Junos Space node or 32 GB RAM to
configure the virtual appliance as a fault monitoring and performance monitoring
(FMPM) node
NOTE: Though 16-GB RAM is sufficient for a Junos Space node, we
recommend that you use 32-GB RAM for better performance. For an FMPM
node, you need 32-GB RAM.
Copyright © 2014, Juniper Networks, Inc.
13
®
Junos Space Frequently Asked Questions
•
One RJ-45 10/100/1000 Network Interface Connector
•
16-GB hard disk
When configuring the virtual appliance as a Junos Space node, you must add a minimum
of 100-GB disk resources as follows for expanding the partitions:
•
40 GB for /var
•
25 GB for /var/log
•
15 GB for /tmp
•
20 GB for /
When configuring the virtual appliance as a specialized or FMPM node, you must add
a minimum of 200 GB disk resources as follows for expanding the partitions:
•
120 GB for /var
•
40 GB for /var/log
•
20 GB for /tmp
•
20 GB for /
NOTE: The free space available in all the partitions should be monitored
periodically and the available free disk space increased if required. The /var
and /var/log partitions should be monitored more frequently as most of
the data are stored in these partitions and space utilization is high.
For information about disk space needed for installing a Junos Space
application, refer to the respective application documentation available
at Junos® Space Software, Release 14.1.
For more information about configuring a Junos Space Virtual Appliance, refer to the
following:
Related
Documentation
14
•
Deploying a Junos Space Virtual Appliance
•
Configuring the Basic Settings of a Junos Space Virtual Appliance
•
Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM Node
•
Deploying a Junos Space Virtual Appliance
•
Configuring the Basic Settings of a Junos Space Virtual Appliance
•
Configuring a Junos Space Virtual Appliance as a Standalone or Primary FMPM Node
•
Adding an FMPM Node for High Availability
Copyright © 2014, Juniper Networks, Inc.
Chapter 4: Junos Space Appliance
Can I Change the IP Address of a Junos Space Node That Has Been Deployed?
Yes, you can do it from the Administration workspace in Network Application Platform.
Related
Documentation
•
Configuring the Network Settings of a Node in the Junos Space Fabric
After Installing a Junos Space Virtual Appliance, Why Do I Get a “Login Incorrect” Error
When I Try to Log In to the Virtual Appliance from the Console?
You might be experiencing a VMware slow connection, which can occur when you connect
over a VPN or slow wireless. To address this problem you can try increasing the type
delay for slow connections to virtual machine consoles by changing the
keyboard.typematicMinDelay setting, which you perform from the .VMX file for the virtual
machine. You can edit the *.VMX files directly, but we recommend that you configure
this value with the vSphere Client for a virtual machine template. For additional
information on the keyboard.typematicMinDelay setting, access the VMware Knowledge
Base at http://kb.vmware.com/selfservice/microsites/microsite.do and search on article
196.
Copyright © 2014, Juniper Networks, Inc.
15
®
Junos Space Frequently Asked Questions
16
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 5
Running Junos Space on NSM3000
•
Installing the Junos Space Software on Network and Security Manager
NSM3000 on page 17
Installing the Junos Space Software on Network and Security Manager NSM3000
Starting with Junos Space Release 12.2, Junos Space can be run on an NSM3000, which
is an appliance version of Network and Security Manager (NSM).
To install Junos Space on an NSM3000, follow the steps in Booting and Configuring the
Junos Space JA1500 Appliance from a USB Drive, at
http://www.juniper.net/techpubs/en_US/release-independent/junos-space/topics/task/installation/junos-space-appliance-booting-usb.html.
Related
Documentation
•
Configuring the Basic Settings of a JA1500 Junos Space Appliance
•
Network and Security Manager (formerly Netscreen-Security Manager) Documentation
Copyright © 2014, Juniper Networks, Inc.
17
®
Junos Space Frequently Asked Questions
18
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 6
Fabric Management
•
Can I Mix Hardware Appliances and Virtual Appliances When I Create a
Fabric? on page 19
Can I Mix Hardware Appliances and Virtual Appliances When I Create a Fabric?
Yes. This is supported.
Related
Documentation
•
Fabric Management Overview
Copyright © 2014, Juniper Networks, Inc.
19
®
Junos Space Frequently Asked Questions
20
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 7
Troubleshooting
•
Where Are the Log Files Required for Troubleshooting? on page 21
Where Are the Log Files Required for Troubleshooting?
You can download the troubleshooting log file from the Junos Space user interface in
sever mode, by accessing the Junos Space Appliance URL in maintenance mode, or from
the Junos Space Appliance console in CLI mode. The troubleshooting log file is
downloaded as a zip package in server mode and maintenance mode, and as a tar
package in CLI mode.
The troubleshooting log file is a zip or tar package that contains the log files generated
by different software components of Junos Space and service provisioning data files.
Related
Documentation
•
Downloading the Troubleshooting Log File in the Server Mode
•
Downloading Troubleshooting System Log Files Through the CLI
•
Downloading the Troubleshooting Log File in the Maintenance Mode
Copyright © 2014, Juniper Networks, Inc.
21
®
Junos Space Frequently Asked Questions
22
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 8
Topology
•
How Does Junos Space Look For a Topology? on page 23
•
How Is Topology Discovery Different from Device Discovery? on page 23
•
What Is a Target Device in Topology Discovery? on page 23
•
What Topology Discovery Methods Are Supported Per Platform Device for Network
Monitoring? on page 24
How Does Junos Space Look For a Topology?
Junos Space uses SNMP to discover network elements (devices, links, ports) that are
connected to the specified target devices and subnets. The Junos Space server uses
SNMP probes to contact the targeted devices and get the relevant management
information base (MIB) information needed to compute the topology.
Related
Documentation
•
Working with Topology
How Is Topology Discovery Different from Device Discovery?
The topology discovery job discovers both devices and how they are connected (link
association).
The device discovery job discovers only devices.
Related
Documentation
•
Device Discovery Overview
•
Working with Topology
What Is a Target Device in Topology Discovery?
A device target acts as a seed device in initiating a topology discovery. Junos Space
searches for all the devices and subnets that are connected to the specified device. You
can specify either the hostname or IP address of the device target. You can also use a
range of IP addresses or an IP subnet to initiate the topology discovery.
Related
Documentation
•
Working with Topology
Copyright © 2014, Juniper Networks, Inc.
23
®
Junos Space Frequently Asked Questions
What Topology Discovery Methods Are Supported Per Platform Device for Network
Monitoring?
Table 4 on page 24 lists the supported topology discovery methods for all the product
series and devices in the Junos Space Network Application Platform software. For more
information about network topology discovery using Bridge Forwarding Table, IP Routes,
Link Layer Discovery Protocol (LLDP), and Open Short Path First (OSPF), see the
OPENNMS Linkd Wiki documentation.
Table 4: Topology Discovery Methods Supported Per Platform Device for Network Monitoring
Product Series
Devices
Topology Discovery Methods
ACX Series
ACX1000
IP-Route, OSPF
ACX1100
ACX2000
ACX2100
ACX2200
ACX4000
BX Series
BX7000
IP-Route, OSPF
EX Series
EX2200
Bridge-MIB, IP-Route, LLDP, OSPF
EX3200
EX3300
EX4200
EX4200-Copper
EX4500
EX4550
EX4550-40G
EX6200
EX8208
EX8216
EX9200
24
Copyright © 2014, Juniper Networks, Inc.
Chapter 8: Topology
Table 4: Topology Discovery Methods Supported Per Platform Device for Network
Monitoring (continued)
Product Series
Devices
Topology Discovery Methods
EX Virtual Chassis
EX3300-VC
Bridge-MIB, IP-Route, LLDP, OSPF
EX4200-VC
EX4500-VC
EX6200-VC
MIXED-MODE-EX-VC
EX-XRE
Firefly
VSRX-Firefly
IP-Route, OSPF
J Series
J2320
IP-Route, OSPF
J2350
J4350
J6350
LN Series
LN1000
IP-Route, OSPF
LN2600
M Series
M7i
IP-Route, OSPF
M10i
M40e
M120
M320
MCG Series
MCG5000
IP-Route
MX Series
MX5
IP-Route, LLDP, OSPF
MX10
MX80
MX240
MX480
MX960
MX2010
MX2020
Copyright © 2014, Juniper Networks, Inc.
25
®
Junos Space Frequently Asked Questions
Table 4: Topology Discovery Methods Supported Per Platform Device for Network
Monitoring (continued)
Product Series
Devices
Topology Discovery Methods
PTX Series
Sangria PTX5000
IP-Route, OSPF
QFX Series
QFX3000
IP-Route, OSPF
QFX3500
QFX3500-G
QFX3500S
QFX3600
SRX Series
SRX100
IP-Route, OSPF
SRX110H-VB
SRX210
SRX220
SRX240
SRX550
SRX650
SRX1400
SRX3400
SRX3600
SRX5600
SRX5800
X45-Major 3 - SW
X44-D10-Minor-SW
T Series
T320
IP-Route, OSPF
T640
T1600
T4000
TX Matrix
TX Matrix Plusa
TXP-3D
WLC Series
26
WLC device
IP-Route
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 9
Adapters
•
What are WW Junos OS devices? on page 27
•
How Is Connecting to Devices Running on Worldwide Junos OS Different From
Connecting to Those Running Domestic Junos OS? on page 27
What are WW Junos OS devices?
WW Junos OS devices are devices running the world wide version of Junos OS. These
devices use Telnet protocol instead of Secure Shell protocol (SSHv2) for communication.
Related
Documentation
•
Worldwide Junos OS Adapter Overview
•
Installing the Worldwide Junos OS Adapter
How Is Connecting to Devices Running on Worldwide Junos OS Different From
Connecting to Those Running Domestic Junos OS?
Devices running the worldwide version of Junos OS use the Telnet protocol instead of
the Secure Shell protocol (SSHv2) for communication. Because Junos Space does not
support Telnet, it uses an adapter to act as a medium to connect to these devices. For
more information, see Worldwide Junos OS Adapter Overview.
Related
Documentation
•
Worldwide Junos OS Adapter Overview
•
Installing the Worldwide Junos OS Adapter
Copyright © 2014, Juniper Networks, Inc.
27
®
Junos Space Frequently Asked Questions
28
Copyright © 2014, Juniper Networks, Inc.
CHAPTER 10
High Availability
•
What Steps Do I Need to Take When One of the High Availability Nodes in the Cluster
Shows the Status “Down”? on page 29
•
What Algorithm Does the Apache HTTP Load Balancer Use to Distribute Load Among
Nodes in the Cluster? on page 30
•
How Do I Determine Which Node in the Cluster Is Handling My Network Management
Platform User Interface Session? on page 30
•
How Do I Determine Which Device Connections Are Being Handled by a
Node? on page 30
•
How Can I Simulate a Virtual IP (VIP) Failover? on page 30
What Steps Do I Need to Take When One of the High Availability Nodes in the Cluster
Shows the Status “Down”?
The first step is to collect all the logs from the cluster as you will want these logs for
troubleshooting later on. Navigate to the Network Management Platform > Administration
> Space Troubleshooting workspace to download troubleshooting data and logs from
the cluster. Then try to log in to the console of the appliance that is down. If you are able
to log in, access the debug shell and check to see whether the jmp-watchdog and jboss
services are up. If the services are not up, do a restart on them and wait 15 to 20 minutes
to see if the node status changes to “Up”. If not, perform a reboot. Once these services
are up, navigate to the Network Management Platform > Administration > Fabric workspace
to add the appliance back to the cluster. If the node does not come up, perform a reboot
and wait 15 to 20 minutes for the node status to change to “Up” in the Network
Management Platform > Administration > Fabric workspace.
If you are unable to log in to the console, or a reboot does not solve the issue, navigate
to the Network Management Platform > Administration > Fabric workspace and delete
the node from the cluster. You can then promote another node (if available) as an HA
node.
You can then try to re image the appliance from a USB stick that has the same version
of Junos Space that is currently running on the other nodes in the cluster. If you are unable
to re-image the appliance, you must get a replacement appliance and re image it.
Copyright © 2014, Juniper Networks, Inc.
29
®
Junos Space Frequently Asked Questions
NOTE: Whether you re-image the existing appliance or get a replacement
appliance, you must reconfigure the appliance with exactly the same network
settings that were configured previously.
Once the appliance is configured, navigate to the Network Management Platform >
Administration > Fabric workspace to add the appliance back to the cluster.
What Algorithm Does the Apache HTTP Load Balancer Use to Distribute Load Among
Nodes in the Cluster?
Junos Space uses the mod_proxy load balancer module within the Apache HTTP server.
The load balancer module is configured to use the default load-balancing method
(Ibmethod=byrequests), which provides a weighted round-robin algorithm. However,
because all nodes in the cluster have the same weight, a round-robin strategy is used for
load distribution. The load balancer is also configured to use sticky sessions (using the
JSESSIONID cookie), which ensures that all HTTP requests that are part of the same
login session are forwarded to the same node in the cluster.
How Do I Determine Which Node in the Cluster Is Handling My Network Management
Platform User Interface Session?
Open you browser’s dialog, which lists all the stored cookies, then find the site with the
VIP address of the Junos Space cluster and expand it. The content of the cookie named
JSESSIONID contains the hostname of the node which is serving your current session.
How Do I Determine Which Device Connections Are Being Handled by a Node?
The easiest way is to SSH to the console of the node and use the netstat command, as
shown in Figure 1 on page 30. The output will show one line for each device connected
to this node. In this example, the node includes two device initiated connections and five
space initiated connections. The IP addresses of the devices are displayed in the fifth
column.
Figure 1: Using the netstat Command to SSH to the Console of a Node
How Can I Simulate a Virtual IP (VIP) Failover?
To simulate a VIP failover, you can shut down the heartbeat service on the node that
currently owns the VIP.
1.
30
Log in to the console of the node and enter “service heartbeat stop”.
Copyright © 2014, Juniper Networks, Inc.
Chapter 10: High Availability
The heartbeat service on this node will shut down, at which point a message is
automatically sent to its peer node. The peer node will take over the VIP in response
to this message.
2. You can monitor the /var/log/messages file on both nodes to view the log entries
related to the failover.
As the messages will show, VIP failover is almost instantaneous in this case.
Copyright © 2014, Juniper Networks, Inc.
31
®
Junos Space Frequently Asked Questions
32
Copyright © 2014, Juniper Networks, Inc.
PART 2
Index
•
Index on page 35
Copyright © 2014, Juniper Networks, Inc.
33
®
Junos Space Frequently Asked Questions
34
Copyright © 2014, Juniper Networks, Inc.
syntax conventions...................................................................x
T
Index
technical support
contacting JTAC...............................................................xii
Symbols
#, comments in configuration statements.....................xi
( ), in syntax descriptions.......................................................xi
< >, in syntax descriptions.....................................................xi
[ ], in configuration statements...........................................xi
{ }, in configuration statements..........................................xi
| (pipe), in syntax descriptions............................................xi
B
braces, in configuration statements..................................xi
brackets
angle, in syntax descriptions........................................xi
square, in configuration statements.........................xi
C
comments, in configuration statements.........................xi
conventions
text and syntax...................................................................x
curly braces, in configuration statements.......................xi
customer support....................................................................xii
contacting JTAC...............................................................xii
D
documentation
comments on....................................................................xi
F
font conventions........................................................................x
I
IPv6 support...............................................................................12
M
manuals
comments on....................................................................xi
P
parentheses, in syntax descriptions..................................xi
S
support, technical See technical support
Copyright © 2014, Juniper Networks, Inc.
35
®
Junos Space Frequently Asked Questions
36
Copyright © 2014, Juniper Networks, Inc.
`