Junos Space Frequently Asked Questions Published: 2014-11-06

Transcription

Junos Space Frequently Asked Questions
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.
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
Table of Contents
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Documentation and Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Documentation Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Documentation Feedback . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ix
Requesting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Self-Help Online Tools and Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
Opening a Case with JTAC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . x
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 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
What Web Browsers Does Junos Space User Interface Support? . . . . . . . . . . . . . . 9
Which Web browser plug-ins does the Junos Space user interface require? . . . . . 9
Which operating systems does the Junos Space user interface support? . . . . . . . 10
What display resolution is recommended for running the Junos Space user
interface? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Does the Junos Space user interface support both HTTP and HTTPS? . . . . . . . . 10
What URL should be used to access the Junos Space user interface? . . . . . . . . . 10
What is the default userid/password for the Junos Space user interface? . . . . . . 10
Chapter 3
Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Which Juniper Networks Platforms Does Junos Space Network Management
Platform Software Support? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
What Junos Releases Are Supported in Different Junos Space Applications? . . . . 16
What Minimum Configuration Do Network Devices Require for Junos Space
Software to Manage Them? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
What Port on the Junos Space Node Does a Device Connect To? . . . . . . . . . . . . . 18
Does Using Junos Space Software to Discover Devices That are Connected to
AIS and SRC Affect Those Connections? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
IPv6 and Junos Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Chapter 4
Junos Space Appliance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
What are the Hardware Specifications for the Junos Space JA1500
Appliance? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
What Configuration Does Junos Space Require to Run the Virtual Appliance? . . . 19
iii
Can I Change the IP Address of a Junos Space Node That Has Been
Deployed? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Chapter 5
Running Junos Space on NSM3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Installing the Junos Space Software on Network and Security Manager
NSM3000 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
Chapter 6
Fabric Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Can I Mix Hardware Appliances and Virtual Appliances When I Create a
Fabric? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Chapter 7
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Where Are the Log Files Required For Troubleshooting? . . . . . . . . . . . . . . . . . . . . 25
Chapter 8
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
How Does Junos Space Look For a Topology? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
How is topology discovery different from device discovery? . . . . . . . . . . . . . . . . . 27
What is a target device in topology discovery? . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
What Topology Discovery Methods Are Supported Per Platform Device for
Network Monitoring? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
Chapter 9
Adapters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
What are WW Junos OS devices? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
How Is Connecting to Devices Running on Worldwide Junos OS Different From
Connecting to Those Running Domestic Junos OS? . . . . . . . . . . . . . . . . . . . . 31
Part 2
Index
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
iv
List of Tables
About the Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii
Table 1: Notice Icons . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Table 2: Text and Syntax Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii
Part 1
FAQ
Chapter 3
Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 3: Junos Space Network Application Platform Device Support . . . . . . . . . . 13
Chapter 8
Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Table 4: Topology Discovery Methods Supported Per Platform Device for Network
Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
v
vi
About the Documentation
•
Documentation and Release Notes on page vii
•
Documentation Conventions on page vii
•
Documentation Feedback on page ix
•
Requesting Technical Support on page x
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 viii defines notice icons used in this guide.
vii
Table 1: Notice Icons
Icon
Meaning
Description
Informational note
Indicates important features or instructions.
Caution
Indicates a situation that might result in loss of data or hardware damage.
Warning
Alerts you to the risk of personal injury or death.
Laser warning
Alerts you to the risk of personal injury from a laser.
Tip
Indicates helpful information.
Best practice
Alerts you to a recommended use or implementation.
Table 2 on page viii defines the text and syntax conventions used in this guide.
Table 2: Text and Syntax Conventions
Convention
Description
Examples
Bold text like this
Represents text that you type.
To enter configuration mode, type the
configure command:
user@host> configure
Fixed-width text like this
Italic text like this
Italic text like this
viii
Represents output that appears on the
terminal screen.
user@host> 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]
root@# set system domain-name
domain-name
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/.
ix
•
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.
x
•
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.
xi
xii
PART 1
FAQ
•
Junos Space Software Upgrade on page 3
•
Junos Space User Interface on page 9
•
Device Management on page 13
•
Junos Space Appliance on page 19
•
Running Junos Space on NSM3000 on page 21
•
Fabric Management on page 23
•
Troubleshooting on page 25
•
Topology on page 27
•
Adapters on page 31
1
2
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 supports upgrades from the last two
versions. Junos Space Network Management Platform Release 13.1 supports upgrading
from 12.3 or 12.2. Versions prior to 12.1 may require a two-step upgrade. For example,
upgrading to 13.1 from 11.4 requires that you upgrade from 11.4 to 12.2 and from 12.2 to 13.1.
Related
Documentation
•
•
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 Platform > Administration >Manage Database > Backup Database.
The Backup Database 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.
3
Related
Documentation
•
•
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 9.
CAUTION: The Junos Space Upgrade supports only two consecutive releases;
see “What Is the Supported Junos Space Release Upgrade Path?” on page 3.
In a multi-node setup, you need not upgrade all nodes within the setup. You
just need to upgrade the primary node, which in turn upgrades the other nodes
in the setup.
To upgrade the Junos Space Network Management Platform:
1.
Ensure that the Junos Space Network Management Platform Upgrade image to which
you want to upgrade is downloaded to the local client file system from the
https://www.juniper.net/support/products/space/#sw website.
2. Select Platform > Administration > Applications.
The Applications inventory page appears.
3. Select the Network Management Platform application and select Upgrade Platform
from the Actions menu.
The Upgrade Platform page appears displaying all previously uploaded versions of
the Junos Space Network Management Platform image.
4. Do one of the following:
•
If the release to which you want to upgrade is listed on the Upgrade Platform page,
select the file, and click Upgrade.
The application upgrade process begins. (Go to the next step.)
•
If the release to which you want to upgrade is not listed on the Upgrade Platform
page, click Upload via HTTP or Upload via SCP to upload the necessary Platform
image to the Junos Space server.
To upload the new Platform image, perform one of the following steps:
a. Click Upload via HTTP.
The Software File dialog box appears.
i.
4
Type the name of the file (Junos Space Network Management Platform image)
or click Browse to navigate to where the new Junos Space Network Management
Platform image file is located on the local file system.
Chapter 1: Junos Space Software Upgrade
ii. Click Upload.
b. Click Upload via SCP.
The Upload Software via SCP dialog box appears. You must add the following
Secure Copy remote machine credentials.
i.
Add your username.
ii. Add your password.
iii. Conform by adding your password again.
iv. Add the host IP address.
v. Add the local path name of the Junos Software application file.
vi. Click Upload.
The new Junos Space Network Management Platform image file is uploaded from
the local file system into the Junos Space server and is displayed by application name,
filename, version, release type, and required Junos Space Network Management
Platform version.
When the upload is completed the Upgrade Platform Job Information dialog box
appears.
a. In the Upgrade Application Job Information dialog box, if you click the Job ID link,
you see the Upgrade Application job on the Jobs > Job Management inventory page.
i.
Ensure that the job is successful.
ii. Select Administration > Applications to continue with the add application
process.
The Applications inventory page appears.
b. Select the Network Management Platform application and select Upgrade Platform
from the Actions menu.
The Upgrade Platform dialog box appears. You see the application file that was
uploaded.
c. Select the release image file to which you want to upgrade, and click Upgrade.
5. An upgrade warning message appears informing you about the list of applications
that might be disabled after the upgrade. Make a note of these applications and
upgrade them after the Junos Space Network Management Platform upgrade is
completed successfully. Click OK.
5
NOTE: If you are upgrading from Junos Space Network Management
Platform Release 13.1 to a later version, say 13.2, another upgrade warning
message appears asking you whether you want the system to back up the
database before the platform upgrade. Click YES or NO depending on
whether you want the system to back up the Junos Space Network
Management Platform database before the upgrade.
Backing up the database before the upgrade helps you to recover the data
if the platform upgrade fails. However, the upgrade process might be
prolonged depending on the database size.
When you choose to back up the database before the upgrade, you are
directed to the “Database Backup and Restore” workspace. Follow the
instructions specified in Backing Up the Junos Space Network Management
Platform Database to back up the database.
After backing up the database, select Administration > Applications >
Network Management Platform > Upgrade Platform > Upgrade action to
upgrade Junos Space Network Management Platform. When prompted
for the second time, whether you want the system to back up the database,
click NO to proceed with the upgrade.
6. You enter Maintenance mode. Junos Space Network Management Platform prompts
you to enter a user name and password to enter maintenance mode. The user name
is maintenance; the password is one that the administrator created during the initial
installation process.
7. Enter the maintenance mode user name and password in the text field.
8. Click Log In.
The Junos Space Network Management Platform upgrade process begins. The
Software Install Status dialog box appears, which displays status messages using
which you can monitor the current upgrade status.
This process might take a while. Wait until the Return to Maintenance Menu link appears.
9. Click the Return to Maintenance Menu link.
The Maintenance Mode Actions dialog box appears.
10. Click the Log Out and Exit from Maintenance Mode link.
The installation progress dialog box appears, which displays the deployment status
of JBoss and various other applications as the system goes through a restart after the
upgrade. For example, this dialog box displays information about the applications
that are being deployed, the timestamp of the deployments, and whether the
applications are disabled after the deployment.
CAUTION: This process might take a while. Do not reboot the system for
a quick recovery. This action leaves the system in a bad state and affects
6
Chapter 1: Junos Space Software Upgrade
the upgrade operation. Wait until the login window is presented for you
to log in.
When the installation is complete, the Junos Space login prompt appears.
NOTE: If a blank page appears instead of the login prompt, click Refresh.
The login prompt is then displayed.
NOTE: We recommend that you clear the Web browser cache before
logging in to the upgraded software.
NOTE: We recommend that you perform a functional audit on all deployed
services after upgrading.
You can now log in to begin using the upgraded Junos Space Network Management
Platform software.
For any troubleshooting, see the following logs:
•
/var/log/install.log—This file captures information about the Junos Space Network
Management Platform upgrade and the installation of applications.
Related
Documentation
•
/var/log/jboss/server.log—This file captures information about JBoss.
•
•
How Do I Back Up the Junos Space Software To the Database Before Upgrading? on
page 3
7
8
CHAPTER 2
Junos Space User Interface
•
What Web Browsers Does Junos Space User Interface Support? on page 9
•
Which Web browser plug-ins does the Junos Space user interface require? on page 9
•
Which operating systems does the Junos Space user interface support? on page 10
•
What display resolution is recommended for running the Junos Space user
interface? on page 10
•
Does the Junos Space user interface support both HTTP and HTTPS? on page 10
•
What URL should be used to access the Junos Space user interface? on page 10
•
What is the default userid/password for the Junos Space user interface? on page 10
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
•
Which Web browser plug-ins does the Junos Space user interface require?
Following plug-in is required:
•
Flash Player 10 or later
9
Related
Documentation
•
Chrome Frame plugin with the Internet Explorer browser.
•
Which operating systems does the Junos Space user interface support? on page 10
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.
Related
Documentation
•
Which Web browser plug-ins does the Junos Space user interface require? on page 9
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.
Related
Documentation
•
What are the Hardware Specifications for the Junos Space JA1500 Appliance? on
page 19
Does the Junos Space user interface support both HTTP and HTTPS?
No, the Junos Space software supports only HTTPS.
Related
Documentation
•
What Web Browsers Does Junos Space User Interface Support? on page 9
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 which 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 surf 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.
10
Chapter 2: Junos Space User Interface
Related
Documentation
•
What URL should be used to access the Junos Space user interface? on page 10
11
12
CHAPTER 3
Device Management
•
Which Juniper Networks Platforms Does Junos Space Network Management Platform
Software Support? on page 13
•
What Junos Releases Are Supported in Different Junos Space Applications? on page 16
•
What Minimum Configuration Do Network Devices Require for Junos Space Software
to Manage Them? on page 17
•
What Port on the Junos Space Node Does a Device Connect To? on page 18
•
Does Using Junos Space Software to Discover Devices That are Connected to AIS and
SRC Affect Those Connections? on page 18
•
IPv6 and Junos Space on page 18
Software Support?
Table 3 on page 13 lists all the product series and devices supported by Junos Space
Network Application Platform software. The Junos Space Network Application Platform
release notes lists only the new devices that are supported with that release.
Table 3: Junos Space Network Application Platform Device Support
Product Series
Devices
ACX Series
ACX1000
ACX1100
ACX2000
ACX2100
ACX2200
ACX4000
BX Series
BX7000
13
Table 3: Junos Space Network Application Platform Device Support (continued)
Product Series
Devices
EX Series
EX2200
EX3200
EX3300
EX4200
EX4200-Copper
EX4500
EX4550
EX4550-40G
EX6200
EX8208
EX8216
EX9200
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
14
Chapter 3: Device Management
Product Series
Devices
M Series
M7i
M10i
M40e
M120
M320
MCG Series
MCG5000
MX Series
MX5
MX10
MX80
MX240
MX480
MX960
MX2010
MX2020
PTX Series
Sangria PTX5000
QFX Series
QFX3000
QFX3000-G
QFX3000-M
QFX3500
QFX3600
15
Product Series
Devices
SRX Series
SRX100
SRX110H-VB
SRX210
SRX220
SRX240
SRX550
SRX650
SRX1400
SRX3400
SRX3600
SRX5600
SRX5800
X45-Major 3 - SW
X44-D10-Minor-SW
T Series
T320
T640
T1600
T4000
TX Matrix
TX Matrix Plusa
TXP-3D
WLC Series
Related
Documentation
WLC device
•
What Port on the Junos Space Node Does a Device Connect To? on page 18
What Junos Releases Are Supported in Different Junos Space Applications?
The following Junos software releases are supported in different Junos Space applications.
16
Chapter 3: Device Management
Specific Junos OS releases and versions that are fully supported in Junos Space Network
Application Platform 12.3 are limited to the following:
Related
Documentation
•
Junos OS Release 9.3
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
What Minimum Configuration Do Network Devices Require for Junos Space Software
to Manage Them?
For the Junos Space software to discover and manage devices, the following minimum
configuration is expected as a prerequisite on the devices:
•
A static management IP is configured on the device. It could be in-band or out-of-band.
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.
•
If you plan to use SNMP to probe devices as part of device discovery, SNMP must be
enabled on the device with appropriate read-only V1/V2C/V3 credentials created.
•
SSH v2 is enabled on the device. Use the following command to enable SSH v2.
set system services ssh protocol-version v2
17
Related
Documentation
•
Ping/SNMP is enabled on the device. Ping/SNMP is used to confirm whether the device
is reachable and whether it is a Juniper Networks device before adding it to the system.
•
Discovering Devices
What Port on the Junos Space Node Does a Device Connect To?
As devices are brought under Junos Space management, they connect to port 7804 on
the Junos Space node.
Related
Documentation
•
Does Using Junos Space Software to Discover Devices That are Connected to AIS and
SRC Affect Those Connections?
When the Junos Space software discovers and manages these devices, it will
automatically configure them to connect to the Junos Space server by having a new
client entry under the system/services/outbound-ssh stanza. This connectivity will not
interfere with any existing connections that these devices might have.
IPv6 and Junos Space
You can use Configuration Editor or Device Templates to configure IPv6 on devices
running Junos Release 10.2 and above.
18
CHAPTER 4
Junos Space Appliance
•
What are the Hardware Specifications for the Junos Space JA1500
Appliance? on page 19
•
What Configuration Does Junos Space Require to Run the Virtual Appliance? on page 19
•
Can I Change the IP Address of a Junos Space Node That Has Been
Deployed? on page 20
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 3.5 or later that can support a virtual machine with the following
configuration:
Related
Documentation
•
64-bit Quad processor with at least 2.66 GHz
•
8 GB memory
•
One RJ-45 10/100/1000 Network Interface Connector
•
116 GB hard disk (16 GB initial disk resources + 100 GB disk resources to be added)
•
Deploying a Junos Space Virtual Appliance
19
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
20
•
Configuring the Network Settings of a Node in the Junos Space Fabric
CHAPTER 5
Running Junos Space on NSM3000
•
Installing the Junos Space Software on Network and Security Manager
NSM3000 on page 21
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 Basic Settings for a Junos Space JA1500 Appliance
•
Network and Security Manager (formerly Netscreen-Security Manager) Documentation
21
22
CHAPTER 6
Fabric Management
•
Can I Mix Hardware Appliances and Virtual Appliances When I Create a
Fabric? on page 23
Can I Mix Hardware Appliances and Virtual Appliances When I Create a Fabric?
Yes. This is supported.
Related
Documentation
•
Fabric Management Overview
23
24
CHAPTER 7
Troubleshooting
•
Where Are the Log Files Required For Troubleshooting? on page 25
Where Are the Log Files Required For Troubleshooting?
You can access the log files for the Junos Space application from the Junos Space user
interface or CLI.
Related
Documentation
•
Downloading the Troubleshooting Log File from the UI
•
Downloading Troubleshooting System Log Files Through the CLI
•
Downloading the Troubleshooting Log File In Maintenance Mode
25
26
CHAPTER 8
Topology
•
How Does Junos Space Look For a Topology? on page 27
•
How is topology discovery different from device discovery? on page 27
•
What is a target device in topology discovery? on page 27
•
What Topology Discovery Methods Are Supported Per Platform Device for Network
Monitoring? on page 28
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
•
Discovering a 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
•
Topology Discovery Overview
•
Device Discovery Overview
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
•
Discovering a Topology
•
Topology Discovery Overview
27
What Topology Discovery Methods Are Supported Per Platform Device for Network
Monitoring?
Table 4 on page 28 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
28
Chapter 8: Topology
Monitoring (continued)
Product Series
Devices
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
29
Monitoring (continued)
Product Series
Devices
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
30
WLC device
IP-Route
CHAPTER 9
Adapters
•
What are WW Junos OS devices? on page 31
•
Connecting to Those Running Domestic Junos OS? on page 31
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
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
31
32
PART 2
Index
•
Index on page 35
33
34
syntax conventions................................................................viii
T
Index
technical support
contacting JTAC.................................................................x
Symbols
#, comments in configuration statements.....................ix
( ), in syntax descriptions.......................................................ix
< >, in syntax descriptions.....................................................ix
[ ], in configuration statements...........................................ix
{ }, in configuration statements..........................................ix
| (pipe), in syntax descriptions............................................ix
B
braces, in configuration statements..................................ix
brackets
angle, in syntax descriptions........................................ix
square, in configuration statements.........................ix
C
comments, in configuration statements.........................ix
conventions
text and syntax................................................................viii
curly braces, in configuration statements.......................ix
customer support......................................................................x
contacting JTAC.................................................................x
D
documentation
comments on....................................................................ix
F
font conventions.....................................................................viii
I
IPv6 support..............................................................................18
M
manuals
comments on....................................................................ix
P
parentheses, in syntax descriptions..................................ix
S
support, technical See technical support
35
36

Junos Space Frequently Asked Questions Published: 2014-11-06

Transcription

Similar documents

February 2016 Growth Spurts

Junper Midrange Routing Solutons

Accessing TP SSL VPN - Student

Juniper Networks M-series : Product Overview

Juniper Parsoni

P4SC: Collaborative Design Presentation for Juniper Well Ranch

Hollywood Juniper

The New NeTwOrk fOr COllaBOraTION– OPTImIzINg UC&C DePlOYmeNT wITh