Platform
Release
17.2
Modified: 2017-12-20
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.
The information in this document is current as of the date on the title page.
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.
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/. By downloading, installing or using such software, you agree to the terms and conditions of that
EULA.
Part 2 Devices
Chapter 7 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Device Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Managed and Unmanaged Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
IPv4 and IPv6 Address Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 180
Confirmed-commit from Junos Space Network Management Platform . . . . . . . 181
Viewing Managed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Juniper Networks Devices Supported by Junos Space Network Management
Platform . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 187
Uploading Device Tags by Using a CSV File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 192
Filtering Devices by CSV . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 194
Chapter 8 Systems of Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Systems of Record in Junos Space Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Systems of Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Implications on device management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196
Understanding How Junos Space Automatically Resynchronizes Managed
Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Network as System of Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197
Junos Space as System of Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199
Chapter 9 Device Discovery Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Device Discovery Profiles Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Connections Initiated by Junos Space or the Device . . . . . . . . . . . . . . . . . . . 202
Device Information Fetched During Device Discovery . . . . . . . . . . . . . . . . . . 203
Creating a Device Discovery Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
Specifying Device Targets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 205
Specifying Probes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
Selecting the Authentication Method and Specifying Credentials . . . . . . . . . 211
(Optional) Specifying SSH Fingerprints . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
Scheduling Device Discovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
Running Device Discovery Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 215
Modifying a Device Discovery Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 216
Cloning a Device Discovery Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 217
Viewing a Device Discovery Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 219
Deleting Device Discovery Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
Exporting the Device Discovery Details As a CSV File . . . . . . . . . . . . . . . . . . . . . . 220
Chapter 10 Modeling Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Rapid Deployment Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 224
Zero Touch Deployment Using Autoinstallation and Junos Space Network
Management Platform on ACX Series and SRX Series Devices . . . . . . . . . . 225
Zero-Touch Deployment Using the Autoinstallation and Model and Activate
Devices Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Zero-Touch Deployment Using the Autoinstallation Feature and the
Configuration Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 227
Model Devices Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 228
Creating a Connection Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 229
Creating a Modeled Instance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233
Part 6 Reports
Chapter 40 Reports Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Reports Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Audit Trail Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Device Inventory Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Device License Inventory Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 716
Device Logical Interface Inventory Report Type . . . . . . . . . . . . . . . . . . . . . . . 717
Device Physical Interface Inventory Report Type . . . . . . . . . . . . . . . . . . . . . . 718
Device Physical Inventory Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 719
Device Software Inventory Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
Job Inventory Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 720
User Account Report Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Chapter 41 Report Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Creating Report Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 723
Viewing Report Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 726
Modifying Report Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 727
Cloning Report Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 728
Deleting Report Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Viewing Report Definition Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 729
Part 9 Jobs
Chapter 56 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Jobs Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Chapter 57 Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
Viewing Statistics for Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
Viewing the Types of Jobs That Are Run . . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
Viewing the State of Jobs That Have Run . . . . . . . . . . . . . . . . . . . . . . . . . . . 906
Viewing Average Execution Times for Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . 906
Viewing Your Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 907
Viewing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 908
Viewing Objects on Which a Job is Executed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 911
Viewing Job Recurrence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913
Rescheduling and Modifying the Recurrence Settings of Jobs . . . . . . . . . . . . . . . 914
Retrying a Job on Failed Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 915
Reassigning Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 917
Canceling Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 920
Clearing Your Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
Archiving and Purging Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 921
Purging Jobs Without Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 922
Archiving Jobs to a Local Server and Purging the Jobs from the
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923
Archiving Jobs to a Remote Server and Purging the Jobs from the
Database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 925
Common Error Messages in Device-Related Operations . . . . . . . . . . . . . . . . . . . 927
Converting the Junos Space Audit Log File Timestamp from UTC to Local Time
Using Microsoft Excel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1039
Archiving and Purging or Only Purging Audit Logs . . . . . . . . . . . . . . . . . . . . . . . 1040
Purging Audit Logs Without Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1041
Purging Audit Logs After Archiving . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1044
Part 12 Administration
Chapter 67 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
Junos Space Administrators Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
Viewing the Administration Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Viewing System Health Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Viewing the System Health Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1053
Viewing System Alert Messages in the Last 30 Days . . . . . . . . . . . . . . . . . 1060
Junos Space IPv6 Support Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1062
Maintenance Mode Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1063
Maintenance Mode Access and System Locking . . . . . . . . . . . . . . . . . . . . . 1064
Maintenance-Mode User Administration . . . . . . . . . . . . . . . . . . . . . . . . . . . 1064
Chapter 68 Managing Nodes in the Junos Space Fabric . . . . . . . . . . . . . . . . . . . . . . . . . 1067
Fabric Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
Overall System Condition and Fabric Load History Overview . . . . . . . . . . . . . . 1069
Overall System Condition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1069
Fabric Load History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
Active Users History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
Junos Space Nodes and FMPM Nodes in the Junos Space Fabric Overview . . . 1072
Understanding the Junos Space Node Functions in a Fabric . . . . . . . . . . . . 1072
Understanding the FMPM Node Functions in a Fabric . . . . . . . . . . . . . . . . . 1075
Dedicated Database Nodes in the Junos Space Fabric Overview . . . . . . . . . . . . 1077
Cassandra Nodes in the Junos Space Fabric Overview . . . . . . . . . . . . . . . . . . . 1080
Adding a Node to an Existing Junos Space Fabric . . . . . . . . . . . . . . . . . . . . . . . 1083
Adding a Junos Space Node to the Junos Space Fabric . . . . . . . . . . . . . . . 1084
Adding an FMPM Node to the Junos Space Fabric . . . . . . . . . . . . . . . . . . . 1088
Obtaining Fingerprint of a Junos Space Node . . . . . . . . . . . . . . . . . . . . . . . 1090
Starting the Cassandra Service on a Junos Space Node . . . . . . . . . . . . . . . . . . . 1091
Viewing Nodes in the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092
Changing Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1092
Viewing Fabric Node Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1093
Monitoring Nodes in the Fabric . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1098
Viewing and Modifying the SNMP Configuration for a Fabric Node . . . . . . 1099
Starting SNMP Monitoring on Fabric Nodes . . . . . . . . . . . . . . . . . . . . . . . . . 1137
Stopping SNMP Monitoring on Fabric Nodes . . . . . . . . . . . . . . . . . . . . . . . . 1138
Restarting SNMP Monitoring on Fabric Nodes . . . . . . . . . . . . . . . . . . . . . . . 1138
Adding a Third-Party SNMP V1 or V2c Manager on a Fabric Node . . . . . . . . 1139
Adding a Third-Party SNMP V3 Manager on a Fabric Node . . . . . . . . . . . . . 1140
Deleting a Third-Party SNMP Manager from a Fabric Node . . . . . . . . . . . . . 1142
Installing StorMan RPM for Monitor RAID Functionality . . . . . . . . . . . . . . . . 1142
Viewing Alarms from a Fabric Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1142
Shutting Down or Rebooting Nodes in the Junos Space Fabric . . . . . . . . . . . . . . 1145
Disabling the Cassandra Service on a Junos Space Node . . . . . . . . . . . . . . . . . . 1147
Appendix: Sample Data of Time Taken for Backup and Restore While
Upgrading to Junos Space Platform Release 16.1R1 . . . . . . . . . . . . . . . . 1273
Upgrading Junos Space Network Management Platform . . . . . . . . . . . . . . . . . . 1273
Uninstalling a Junos Space Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1279
Chapter 72 Managing Troubleshooting Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
System Status Log File Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
System Status Log File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
Customizing Status Log File Content . . . . . . . . . . . . . . . . . . . . . . . . . . 1282
Downloading System Log Files for a Junos Space Appliance . . . . . . . . . . . 1282
Customizing Log Files to Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1283
Customizing Node System Status Log Checking . . . . . . . . . . . . . . . . . . . . . . . . 1283
Customizing Node Log Files to Download . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1284
Configuring JBoss and OpenNMS Logs in Junos Space . . . . . . . . . . . . . . . . . . . 1284
Generating JBoss Thread Dump for Junos Space Nodes . . . . . . . . . . . . . . . . . . 1286
Downloading the Troubleshooting Log File in Server Mode . . . . . . . . . . . . . . . . 1288
Downloading the Troubleshooting Log File in Maintenance Mode . . . . . . . . . . . 1292
Downloading Troubleshooting System Log Files Through the Junos Space
CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1293
Downloading a System Log File by Using a USB Device . . . . . . . . . . . . . . . 1293
Downloading System Log File by Using SCP . . . . . . . . . . . . . . . . . . . . . . . . 1294
Chapter 73 Managing Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
Certificate Management Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1300
Authentication Modes Workflow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1301
Custom Junos Space Server Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . 1302
Certificate Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1302
User Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304
CA Certificates and CRLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304
Changing the User Authentication Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . 1304
Certificate Expiry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1305
Invalid User Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1305
Changing User Authentication Modes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1306
Changing the User Authentication Mode from Password-Based to Complete
Certificate-Based from the User Interface . . . . . . . . . . . . . . . . . . . . . . 1307
Changing the User Authentication Mode from Complete Certificate-Based
to Certificate Parameter–Based from the User Interface . . . . . . . . . . 1309
Changing the User Authentication Mode from Certificate Parameter–Based
to Complete Certificate-Based from the User Interface . . . . . . . . . . . . . 1311
Changing the User Authentication Mode to Password-Based from the User
Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312
Changing the User Authentication Mode to Password-Based from the
CLI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1312
Installing a Custom SSL Certificate on the Junos Space Server . . . . . . . . . . . . . 1313
Installing an X.509 Junos Space Server Certificate . . . . . . . . . . . . . . . . . . . . 1313
Installing a Junos Space Server Certificate in the PKCS #12 Format . . . . . . 1314
Reverting to the Default Junos Space Server SSL Certificate . . . . . . . . . . . . 1315
Uploading a User Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1316
Uploading a User Certificate for a New User . . . . . . . . . . . . . . . . . . . . . . . . . 1316
Uploading a User Certificate for an Existing User . . . . . . . . . . . . . . . . . . . . . 1317
Part 1 Overview
Chapter 6 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Figure 44: Junos Space Platform Dashboard Page . . . . . . . . . . . . . . . . . . . . . . . . 174
Part 2 Devices
Chapter 7 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Figure 45: Device Management Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
Chapter 8 Systems of Record . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195
Figure 46: Resynchronization Process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 198
Part 12 Administration
Chapter 68 Managing Nodes in the Junos Space Fabric . . . . . . . . . . . . . . . . . . . . . . . . . 1067
Figure 49: Fabric Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1068
Figure 50: Overall System Condition Gauge . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1070
Figure 51: Fabric Load History Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
Figure 52: Active Users History Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1071
Figure 53: Fabric with One Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1072
Figure 54: Fabric with Two Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
Figure 55: Fabric with Three Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1074
Figure 56: Fabric with FMPM Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1076
Figure 57: Fabric with Database Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1078
Figure 58: Cassandra Service on JBoss Nodes . . . . . . . . . . . . . . . . . . . . . . . . . . 1080
Figure 59: Cassandra Service on Dedicated Cassandra Nodes . . . . . . . . . . . . . . 1081
Figure 60: Cassandra Service on JBoss and Dedicated Cassandra Nodes . . . . . 1081
Part 13 Overview
Chapter 84 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1451
Figure 142: Overall System Condition Gauge . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456
Figure 143: Fabric Load History Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1456
Figure 144: Active Users History Chart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1457
Part 1 Overview
Chapter 6 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171
Table 16: Junos Space Platform Workspaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 172
Part 2 Devices
Chapter 7 Device Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 179
Table 17: Managed Status in NSOR and SSOR Modes for confirmed-commit . . 182
Table 18: Fields in the Device Management Table . . . . . . . . . . . . . . . . . . . . . . . . . 184
Table 19: Devices Supported by Junos Space Platform . . . . . . . . . . . . . . . . . . . . . 187
Chapter 9 Device Discovery Profiles . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201
Table 20: View Discovery Profile Pop-up Window . . . . . . . . . . . . . . . . . . . . . . . . . 219
Chapter 10 Modeling Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 223
Table 21: View Modeled Instance Dialog Box Details . . . . . . . . . . . . . . . . . . . . . . 248
Table 22: Details of Devices Included in the Modeled Instance . . . . . . . . . . . . . . 249
Table 23: View Connection Profile Dialog Box Details . . . . . . . . . . . . . . . . . . . . . 252
Chapter 11 Device Authentication in Junos Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 255
Part 6 Reports
Chapter 40 Reports Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713
Table 92: Privileges Required to Generate Reports for Specific Report Definition
Categories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 714
Table 93: Audit Trail Report Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Table 94: Device Inventory Report Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 715
Table 95: Device License Inventory Report Attributes . . . . . . . . . . . . . . . . . . . . . . 716
Table 96: Device Logical Interface Inventory Report Attributes . . . . . . . . . . . . . . . 717
Table 97: Device Physical Interface Inventory Report Attributes . . . . . . . . . . . . . . 718
Table 98: Device Physical Inventory Report Attributes . . . . . . . . . . . . . . . . . . . . . 719
Table 99: Device Software Inventory Report Attributes . . . . . . . . . . . . . . . . . . . . 720
Table 100: Job Inventory Report Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Table 101: User Account Report Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 721
Chapter 42 Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 731
Table 102: View Report Dialog Box Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 736
Part 9 Jobs
Chapter 56 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 901
Table 118: Junos Space Platform Job Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 902
Chapter 57 Managing Jobs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 905
Table 119: Fields on the Job Management Page . . . . . . . . . . . . . . . . . . . . . . . . . . 909
Table 120: Fields on the Jobs Details Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
Table 121: Job Icon Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 910
Table 122: Jobs that Support Viewing Objects on Which a Job is Executed . . . . . 912
Table 123: Comon Error Messages in Device-Related Operations . . . . . . . . . . . . 927
Part 12 Administration
Chapter 67 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1051
Table 134: Junos Space Administrators and Junos Space UI Users . . . . . . . . . . . 1051
Table 135: System Health Report: Processes and Parameters . . . . . . . . . . . . . . 1054
Table 136: Extended Periods of High CPU Page . . . . . . . . . . . . . . . . . . . . . . . . . 1059
Table 174: Supported TLS Version 1.2 Algorithms for HTTPS Access When Weak
Algorithms Are Disabled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1234
Table 175: Health Monitoring Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1235
Table 176: X509 Certificate Parameter (Variable) Details . . . . . . . . . . . . . . . . . 1236
Table 177: Starting, Stopping, and Restarting Network Monitoring . . . . . . . . . . . 1240
Table 178: Items needed for upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1257
Table 179: Sample Data Showing Approximate Time Taken for Backup and
Restore . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1273
Chapter 72 Managing Troubleshooting Log Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1281
Table 180: Log Files included in the troubleshoot File . . . . . . . . . . . . . . . . . . . . . 1282
Table 181: Log Levels and their Descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1285
Table 182: Log Files in the Troubleshooting Log File and Their Location . . . . . . 1290
Chapter 73 Managing Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1299
Table 183: Certificate Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1302
Chapter 74 Configuring Authentication Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1327
Table 184: Login Behavior with Remote Authentication Only Enabled . . . . . . . . 1334
Table 185: Login Behavior with Remote-Local Authentication Enabled . . . . . . . 1335
Table 186: Remote Authentication Server Parameters . . . . . . . . . . . . . . . . . . . . 1338
Chapter 77 Managing Git Repositories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1355
Table 187: Git Repositories Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1360
Chapter 78 Audit Log Forwarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1361
Table 188: Audit Log Forwarding Page Fields . . . . . . . . . . . . . . . . . . . . . . . . . . . 1363
Chapter 80 Managing Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1375
Table 189: Tag Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1382
Table 190: Tagged Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1397
Table 191: List of Supported Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1398
Chapter 81 Managing DMI Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1403
Table 192: Information About DMI Schemas . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1405
Table 193: Information Displayed About Available Schemas . . . . . . . . . . . . . . . . 1411
Table 194: Information Displayed About Available Schemas . . . . . . . . . . . . . . . 1424
Table 195: Sample URLs for the Repository . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1426
Table 196: Schema Name Mapping Information . . . . . . . . . . . . . . . . . . . . . . . . . 1429
Chapter 83 Managing the Purging Policy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1439
Table 197: Purging Categories and Criteria . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1442
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.
Supported Platforms
For the features described in this document, the following platforms are supported:
Documentation Conventions
Caution Indicates a situation that might result in loss of data or hardware damage.
Laser warning Alerts you to the risk of personal injury from a laser.
Table 2 defines the text and syntax conventions used in this guide.
Bold text like this Represents text that you type. To enter configuration mode, type the
configure command:
user@host> configure
Fixed-width text like this Represents output that appears on the user@host> show chassis alarms
terminal screen.
No alarms currently active
Italic text like this • Introduces or emphasizes important • A policy term is a named structure
new terms. that defines match conditions and
• Identifies guide names. actions.
• Junos OS CLI User Guide
• Identifies RFC and Internet draft titles.
• RFC 1997, BGP Communities Attribute
Italic text like this Represents variables (options for which Configure the machine’s domain name:
you substitute a value) in commands or
configuration statements. [edit]
root@# set system domain-name
domain-name
Text like this Represents names of configuration • To configure a stub area, include the
statements, commands, files, and stub statement at the [edit protocols
directories; configuration hierarchy levels; ospf area area-id] hierarchy level.
or labels on routing platform • The console port is labeled CONSOLE.
components.
< > (angle brackets) Encloses optional keywords or variables. stub <default-metric metric>;
# (pound sign) Indicates a comment specified on the rsvp { # Required for dynamic MPLS only
same line as the configuration statement
to which it applies.
[ ] (square brackets) Encloses a variable for which you can community name members [
substitute one or more values. community-ids ]
GUI Conventions
Bold text like this Represents graphical user interface (GUI) • In the Logical Interfaces box, select
items you click or select. All Interfaces.
• To cancel the configuration, click
Cancel.
> (bold right angle bracket) Separates levels in a hierarchy of menu In the configuration editor hierarchy,
selections. select Protocols>Ospf.
Documentation Feedback
• Online feedback rating system—On any page of the Juniper Networks TechLibrary 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
http://www.juniper.net/techpubs/feedback/.
Technical product support is available through the Juniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or Partner Support Service
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 hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
• Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://entitlementsearch.juniper.net/entitlementsearch/
To support the rapid growth in network size, Junos Space is designed to be highly scalable.
You can cluster multiple Junos Space appliances to create a single management fabric,
which is accessible from a single virtual IP (VIP) address.
All graphical user interface (GUI) and northbound interface (NBI) clients use the Junos
Space VIP address to connect to the Junos Space fabric. The fabric incorporates a
front-end load balancer that distributes client sessions across all the active Junos Space
nodes within the fabric. You can increase or decrease the fabric by simply adding or
deleting nodes to or from the Junos Space Network Management Platform user interface,
and the Junos Space system automatically starts applications and services on the active
nodes. Each node in the cluster is fully utilized and all nodes work together to provide
automated resource management and service availability.
A Junos Space fabric architecture comprising multiple appliances eliminates any single
point of failure. When a node in the fabric goes down, all client sessions and device
connections currently served by that node are automatically migrated to the active nodes
in the fabric without any user-initiated action.
You can install and deploy Junos Space Hardware Appliances (JA2500), Junos Space
Virtual Appliances, or both to form a fabric. Each appliance in the fabric is called a node.
All nodes in the fabric work together as a cluster of Junos Space instances running in
active-active configuration (that is, all nodes are active in the cluster).
Figure 1 displays how a Junos Space fabric employs a software load balancer to distribute
HTTP sessions across the nodes to ensure that the load presented by the Junos Space
Network Management Platform user interface and NBI clients is equally distributed within
the fabric.
A Junos Space fabric of appliances provides scalability and ensures high availability of
your management platform. The fabric provides an N+1 redundancy solution where the
failure of a single node in the fabric does not affect the functioning of the fabric. When
a node in the fabric fails, the sessions of the clients accessing Junos Space from the user
interface automatically migrate away from the failed node. Similarly, managed devices
that were connected to the failed node are automatically reconnected with another
functioning node in the fabric.
• Virtual IP address (when you configure the first node in the cluster) to access the Junos
Space user interface from Web browsers. The IP address should be in the same subnet
as the IP address assigned to the “eth0” interface.
• IP address and subnet mask for the “eth3” interface if you choose to manage devices
on a different Ethernet interface (see Figure 3).
• Whether the appliance will be added to an existing cluster. Choose “n” to add the first
node to a new cluster and choose “y” to add subsequent nodes to the cluster.
NOTE: Ensure that you remember the Maintenance mode user ID and
password. These details are required when you upgrade software and
restore databases.
Refer to the JA2500 Junos Space Appliance Quick Start Guide for detailed instructions on
how to configure the hardware appliance during initial deployment.
You can deploy a Junos Space Virtual Appliance on a VMware ESX server version 4.0 or
later or VMware ESXi server version 4.0 or later. After the Junos Space Virtual Appliance
is deployed, you can use the VMware vSphere client that is connected to the VMware
ESX (or VMware ESXi) server to configure the Junos Space Virtual Appliance. You can
deploy Junos Space Virtual Appliance 14.1R2.0 and later on qemu-kvm Release
0.12.1.2-2/448.el6. You must deploy and configure the Junos Space Virtual Appliance on
a KVM server by using the Virtual Machine Manager (VMM) client.
The CPU, RAM, and disk space provided by the VMware ESX server or KVM server must
meet or exceed the documented CPU, RAM, and disk space requirements for deploying
a Junos Space Virtual Appliance. In addition, we recommend that, for a multinode fabric,
you deploy the first and second virtual appliances on separate servers to ensure failover
support.
The distributed Junos Space Virtual Appliance files are created with 135 GB of disk space.
If you create a multinode cluster, ensure that the first and second nodes that you deploy
should contain the same amount of disk space. When the disk resources are used beyond
80% capacity, add sufficient disk space (more than 10 GB) to the disk partitions.
When you log in to the console of the VMware vSphere client or VMM client, you need to
specify the same parameters used to deploy a hardware appliance. Refer to the Junos
Space Virtual Appliance Deployment and Configuration Guide for detailed instructions on
how to configure the virtual appliance during initial deployment.
The following are required when you deploy a Junos Space fabric:
• You must be able to ping the default gateway IP address, or else the fabric will not
form correctly.
• The IP addresses assigned to the eth0 interface on the first two appliances in the fabric
must be in the same subnet.
• The virtual IP address configured on the first appliance in the fabric must be in the
same subnet as the eth0 interface on the first two appliances.
• Multicast packets must be routable among all nodes because JBoss cluster-member
discovery uses multicast routing.
• If you are deploying a fabric of virtual appliances, we recommend that the first and
second appliances added to the fabric be hosted on a separate VMware ESX or ESXI
server to ensure failover support.
• All appliances in the fabric must use the same external NTP source to ensure consistent
time setting across all appliances in the fabric You must specify the NTP source on
each appliance before adding the appliance to the fabric.
• All nodes in the fabric are running the same version of the software.
• Desktops, laptops, and workstations from which Junos Space users access the Junos
Space user interface as well as external systems hosting NBI clients
• Other appliances that form a Junos Space fabric along with this appliance
Junos Space allows you to use two of the four Ethernet interfaces: eth0 and eth3. The
other two Ethernet interfaces are reserved for future use. You can choose one of the
following two options for configuring interfaces for IP connectivity:
• Use the eth0 interface for all network connectivity of the appliance, as shown in Figure 2.
• Use the eth0 interface for network connectivity with Junos Space user interface clients
and other appliances in the same fabric, and use the eth3 interface for network
connectivity with managed devices, as shown in Figure 3.
For complete information about adding nodes to a fabric, see the “Adding a Node to an
Existing Junos Space Fabric” on page 1083 topic (in the Junos Space Network Management
Platform Workspaces Feature Guide).
The following sections describe the primary software administration tasks for the Junos
Space Network Management Platform and Junos Space applications:
CAUTION: Do not modify the filename of the software image that you
download from the Juniper Networks support site. If you modify the filename,
the installation or upgrade fails.
You can upload an application image file to Junos Space from the Add Application page
( Administration > Applications > Add Application). You can upload an application image
file by using HTTP (Upload via HTTP option) or Secure Copy Protocol (SCP) (Upload via
SCP option). We recommend that you upload the file by using SCP, which initiates a
direct transfer from an SCP server to Junos Space and is performed as a back-end job.
If you choose to upload the file by using SCP, you must first make the image file available
on an SCP server that Junos Space can access. You must also provide the IP address of
the SCP server and the login credentials needed to access this SCP server. The main
advantage of using SCP is that your user interface is not blocked while the file transfer
is in progress, and you can monitor the progress of the file transfer from the Jobs
workspace.
NOTE: A Junos Space node can also be used as an SCP server. To do this,
copy the application image file (using SCP or SSH FTP [SFTP]) to the /tmp/
directory on the Junos Space node, and in the Upload Software via SCP dialog
box specify the credentials (username and password), the IP address of the
Junos Space node, the CLI credentials, and the file path for the software
image.
After the image file for the application is uploaded successfully, you can view the
application from the Add Application page. You can then select the application file and
click the Install button to install the application. The application installation process does
not cause any downtime for the Junos Space Network Management Platform or any
applications installed on Junos Space. Junos Space Network Management Platform
ensures that the application is installed on all nodes in the Junos Space fabric and access
to the application is load balanced across all nodes in the Junos Space fabric.
For more information about installing Junos Space applications, see the “Managing Junos
Space Applications Overview” on page 1211 topic (in the Junos Space Network Management
Platform Workspaces Feature Guide).
For more information about upgrading Junos Space applications, see the “Managing
Junos Space Applications Overview” on page 1211 topic (in the Junos Space Network
Management Platform Workspaces Feature Guide).
each major release. You can upgrade to a newer platform release by performing a few
simple steps from the user interface in your current Junos Space platform.
NOTE: If you are upgrading to Junos Space Platform Release 16.1R1 or 16.1R2,
follow the procedure outlined in the topic “Upgrading to Junos Space Network
Management Platform Release 16.1R1” on page 1256 in the Workspaces Feature
Guide.
If you are upgrading Junos Space Platform to releases other than Junos Space Platform
Release 16.1R1, the workflow for performing the upgrade is similar to that of installing an
application. You first download the required image file (.img extension) from the Juniper
Networks software download site. You then navigate to the Applications page (
Administration > Applications), right-click the image file, and select Upgrade Platform to
upload the image file into Junos Space through HTTP or SCP. We recommend that you
use the SCP option, which initiates a direct transfer from an SCP server to Junos Space
and is performed as a back-end job. If you choose the SCP option, you must first make
the image file available on an SCP server that Junos Space can access. After the image
file is uploaded, select the uploaded file, and click the Upgrade button to start the upgrade
process. The Network Management Platform upgrade forces the system into Maintenance
mode, which requires that you enter the Maintenance mode username and password to
proceed with the upgrade.
During the Junos Space Network Management Platform upgrade process, all the data
in the Junos Space database is migrated to the new schema that is part of the new Junos
Space release. The upgrade process also seamlessly upgrades all nodes in the fabric.
The upgrade process requires a restart of JBoss application servers on all nodes and
might also require a reboot of all the nodes if the OS packages are also upgraded. The
time required for the upgrade depends on a number of factors, including the amount of
data being migrated, the number of nodes in the fabric, the number of third-party
components upgraded, and so forth. You should expect an average downtime of 30 to
45 minutes for upgrade of a single-node fabric, and approximately 45 to 60 minutes for
upgrade of a two-node fabric.
NOTE: You can use this workflow to upgrade to Release 17.2 from Release
17.1 or Release 16.1 or to Release 15.2 from Release 15.1 or Release 14.1. If you
are upgrading to Release 17.2 from a release earlier than 16.1, you must first
upgrade the installation to Release 16.1R2 and then, upgrade to Release 17.2.
You must perform multistep upgrades if a direct upgrade is not supported
between the version from which you want to upgrade and the version to
which you want to upgrade..For detailed information about the releases from
which Junos Space Platform can be upgraded, see the Junos Space Network
Management Platform Release Notes.
Before you upgrade Junos Space Platform to Release 17.2, ensure that the
time on all Junos Space nodes is synchronized. For information about
synchronizing time on Junos Space nodes, see “Synchronizing Time Across
Junos Space Nodes” on page 1253.
For more information about upgrading the Junos Space Network Management Platform,
see the “Upgrading Junos Space Network Management Platform Overview” on page 1213
topic in the Junos Space Network Management Platform Workspaces Feature Guide.
For more information about uninstalling Junos Space applications, see the “Uninstalling
a Junos Space Application” on page 1279 topic in the Junos Space Network Management
Platform Workspaces Feature Guide).
A number of high-level applications are available for Junos Space Network Management
Platform. You can install these applications to simplify network operations, scale services,
automate support, and open the network to new business opportunities.
The Junos Space Network Management Platform is a multitenant platform that enables
you to install hot-pluggable applications. Junos Space automatically deploys the installed
applications across the fabric. You can install, upgrade, and remove applications without
disrupting or causing any downtime for the Junos Space Network Management Platform
or other hosted applications.
The following applications are currently available for Junos Space Network Management
Platform:
• Junos Space Log Director–Enables log collection across SRX Series Services Gateways
and enables log visualization
• Junos Space Security Director –Allows you to secure your network by creating and
publishing firewall policies, IPsec VPNs, network address translation (NAT) policies,
intrusion prevention system (IPS) policies, and application firewalls
• Network Activate
NOTE: For information about the Junos Space applications supported for a
specific version of the Junos Space Network Management Platform, see the
Knowledge Base article KB27572 at
http://kb.juniper.net/InfoCenter/index?page=content&id=KB27572.
Junos Space Network Management Platform comes with a 60-day full-featured trial
license. You must procure and install a valid license during this period to ensure continued
operation beyond the trial period.
If you fail to upload a valid license during the 60-day trial period, the Junos Space user
interface displays an error message when you log in indicating that the license has expired.
Your access is limited to the Licenses page (Administration > Licenses) from where you
can execute the Import License task to enter a valid license.
You can use either of the following options to install a valid license for Junos Space
Platform:
• If you plan to use the Junos Space Platform with only the Support Automation
applications (Service Now and Service Insight), you can navigate to the Add Organization
page (Service Now > Administration > Organizations > Add Organization) in the Service
Now user interface to activate these applications. However, to activate these
applications, you must have a valid support contract for your Juniper Networks devices
and valid credentials to access the Juniper Support System (JSS) back end.
NOTE: If you choose this option and if you want to use other Junos Space
applications beyond the trial period, you must purchase a license for Junos
Space Platform (as explained in the bulleted item that follows).
• If you want to use Junos Space applications other than Service Now and Service Insight,
or if you do not have a valid support contract for your Juniper Networks devices, you
must purchase a license for Junos Space Platform. After you obtain the license file,
you can install the license from the Import License page (Administration > Licenses >
Import License). For more information about installing a valid license for Junos Space
Platform, see the “Generating and Uploading the Junos Space License Key File” on
page 1207 topic (in the Junos Space Network Management Platform Workspaces Feature
Guide).
Each device type is described by a unique data model that contains all the configuration
data for that device. The schemas for this data model list all the possible fields and
attributes for a type of device. The newer schemas describe the new features associated
with recent device releases.
Junos Space Network Management Platform provides support for managing devices
based on Device Management Interface (DMI) schema.
You must load all your device schemas into Junos Space Network Management Platform;
otherwise, only a default schema is applied when you try to edit a device configuration
using the device configuration edit action in the Devices workspace (as described in
“Modifying the Configuration on the Device” on page 296 in the Junos Space Network
Management Platform Workspaces Feature Guide).
If the Junos Space Network Management Platform contains exactly the right schema
for each of your devices, you can access all the configuration options specific to each
device. You can add or update schemas for all Junos Space devices from the
Administration > DMI Schemas workspace. You can use this workspace to check whether
a schema for a device is missing. On the Manage DMI Schemas page, in tabular view, the
DMI Schema column displays "Need Import" if the Junos OS schema for that particular
device OS is not bundled with the Junos Space Network Management Platform. Then
you need to download the schema from the Juniper Schema Repository.
For complete information about managing DMI schema , see the “DMI Schema
Management Overview” on page 1403 topic (in the Junos Space Network Management
Platform Workspaces Feature Guide).
You must back up the Junos Space database regularly so that you are able to roll back
the system data to a previously known point. You can create a backup schedule on the
Database Backup and Restore page in the Administration workspace (Network Management
Platform > Administration > Database Backup and Restore). You can store the backup
file on the local file system of the Junos Space appliance, or on a remote server by using
the Secure Copy Protocol (SCP). We recommend that you back up files on a remote
server because this ensures that the backup files are available even if an error occurs on
the appliance. In addition, if you back up files remotely instead of locally, you ensure
optimal use of the disk space on the Junos Space appliance.
To perform remote backups, you must set up a remote server that can be accessed
through the SCP and that has its IP address and credentials available. We recommend
that you have a separate partition on this server to store Junos Space backups and that
you provide the full path of this partition in the Junos Space user interface when you set
up the backup schedule. You can also specify the start date and time for the first backup,
the recurrence interval required (hourly, daily, weekly, monthly, or yearly), and the date
and time of the last backup (if required). In most cases, we recommend that you back
up the database daily. You can customize the backup frequency based on the needs of
your organization and the amount of change that occurs in the network. In addition, you
can schedule backups to run automatically when the system usage is low. Creating a
backup schedule ensures that database backups occur at the scheduled time and at the
scheduled recurrence intervals. You can also perform database backups on demand
from the Database Backup and Restore page, in the Administration workspace (Network
Management Platform > Administration > Database Backup and Restore), by clearing the
check boxes that control the time of occurrence and recurrence intervals.
For complete information about performing backup and restore operations for the Junos
Space Network Management Platform, see the “Backing Up and Restoring the Database
Overview” on page 1188 and “Backing Up the Junos Space Network Management Platform
Database” on page 1191 topics (in the Junos Space Network Management Platform
Workspaces Feature Guide).
Junos Space Network Management Platform provides a robust user access control
mechanism system that you use to enforce appropriate access policies on the Junos
Space system through your Junos Space administrators. In Junos Space, administrators
can serve different functional roles. A CLI administrator installs and configures Junos
Space appliances. A Maintenance-mode administrator performs system-level tasks,
such as troubleshooting and database restoration operations. After the appliances are
installed and configured, you can create users and assign roles that allow these users to
access the Junos Space Platform workspaces and manage the applications, users,
devices, services, customers, and so forth.
Table 3 shows the Junos Space administrators and the tasks that can be performed.
Junos Space user interface users A Junos Space user that is assigned one For more information about the
or more predefined roles. Each role predefined roles that can be assigned to
assigned to a user provides specific a Junos Space user, see “Configuring
access and management privileges on User Access Controls Overview” on
the objects (applications, devices, users, page 70.
jobs, services, and customers) available
from a workspace in the Junos Space
user interface.
• Deciding how users will be authenticated and authorized to access Junos Space
Platform
• Segregating users based on the system functionality they are allowed to access. You
can assign a different set of roles to different users. Junos Space Network Management
Platform includes more than 25 predefined user roles and allows you to create custom
roles that are based on the needs of your organization. When a user logs in to Junos
Space, the workspaces that the user can access and the tasks that they can perform
are determined by the roles that have been assigned to that particular user account.
• Segregating users based on the domains that they are allowed to access. You can use
the Domains feature in Junos Space to assign users and devices to the global domain
and create subdomains, and then assign users to one or more of these domains. A
domain is a logical grouping of objects, which can include devices, templates, users,
and so on. When a user logs in to Junos Space, the set of objects that they are allowed
to see is based on the domains to which that user account has been assigned.
You can use multiple domains to separate large, geographically distant systems into
smaller, more manageable sections and control administrative access to individual
systems. You can assign domain administrators or users to manage devices and objects
that are assigned to their domains. You can design the domain hierarchy in such a way
that a user assigned to one domain need not necessarily have access to objects in
another domain. You can even restrict users assigned to a domain from viewing objects
that are in the parent domain (in Junos Space Release 13.3, from viewing the objects
in the global domain).
For example, a small organization might have only one domain (the global domain)
for their entire network, whereas a large, international organization might have several
subdomains within the global domain to represent each of its regional office networks
across the world.
The following sections describe how to configure a user access control mechanism:
authenticated based on this password, and the set of roles assigned to the user account
determine the set of tasks the user can perform.
NOTE:
• You must have Super Administrator or System Administrator privileges to
configure Junos Space to work with these servers.
• You need to know the IP addresses, port numbers, and shared secrets of
the remote AAA servers for configuring Junos Space to access them. We
recommend that you use the Connection button to test the connection
between Junos Space and the AAA server as soon as you add the server in
Junos Space. This immediately lets you know whether there is any problem
with the configured IP address, port, or credentials.
• You can configure an ordered list of AAA servers. Junos Space contacts
them in the order you configured; the second server is contacted only if the
first one is unreachable, and so on.
If you are using remote-only mode, you do not have to create any local user accounts in
Junos Space. Instead, you must create user accounts in the AAA servers that you use and
associate a remote profile name to each user account. A remote profile is a collection of
roles that define the set of functions that a user is allowed to perform in Junos Space.
You create the remote profiles in Junos Space. For more information about remote
profiles, see “Remote Profiles” on page 75. Remote profile names can be configured as
a vendor-specific attribute (VSA) in RADIUS and as an attribute-value pair (AVP) in
TACACS+. When an AAA server successfully authenticates a user session, the remote
profile name is included in the response message that is sent back to Junos Space. Junos
Space looks up the remote profile based on this remote profile name and determines
the set of functions that the user is allowed to perform.
Even in the case of remote-only mode, you might want to create local user accounts in
Junos Space in either of the following cases:
• You want to ensure that a user is allowed to log in to Junos Space even if all the AAA
servers are down. In this case, if a local user account exists in the Junos Space database,
the user session is authenticated and authorized based on the local data. You might
choose to do this for a few important user accounts for whom you want to ensure
access even in this scenario.
• You want to use device partitions to partition a device into subgroups and assign these
subobjects to different users. You use device partitions to share the physical interfaces,
logical interfaces, and physical inventory elements across multiple subdomains. Device
partitions are supported only on M Series and MX Series routers. For more information,
see the “Creating Device Partitions” on page 387 topic in the Junos Space Network
Management Platform Workspaces Feature Guide.
For more information about user authentication, see the “Junos Space Authentication
Modes Overview” on page 1329 topic (in the Junos Space Network Management Platform
Workspaces Feature Guide).
User Roles
When configuring Junos Space, you must decide how you want to segregate users based
on the system functionality that users are allowed to access. You do this by assigning a
different set of roles to different users. A role defines a collection of workspaces that a
Junos Space user is allowed to access and a set of actions that the user is allowed to
perform within each workspace. To evaluate the predefined user roles that the Junos
Space Network Management Platform supports, navigate to the Roles page (Network
Management Platform > Role Based Access Control > Roles). In addition, every Junos
Space application that is installed on the Junos Space Network Management Platform
has its own predefined user roles. The Roles page lists all existing Junos Space application
roles, their descriptions, and the tasks that are included in each role.
If the default user roles do not meet your needs, you can configure custom roles by
navigating to the Create Role page (Network Management Platform > Role Based Access
Control > Roles > Create Role). To create a role, you select the workspaces that a user
with this role is allowed to access, and for each workspace, choose the set of tasks that
the user can perform from that workspace.
NOTE: You might need to go through several iterations of creating user roles
to arrive at the optimal set of user roles that your organization needs.
After the user roles are defined, they can be assigned to various user accounts (in the
case of local user accounts created in Junos Space) or assigned to remote profiles to be
used for remote authorization.
For more information about configuring user roles, see the “Role-Based Access Control
Overview” on page 931 topic (in the Junos Space Network Management Platform Workspaces
Feature Guide).
Remote Profiles
Remote profiles are used in the case of remote authorization. A remote profile is a
collection of roles defining the set of functions that a user is allowed to perform in Junos
Space. There are no remote profiles created by default, and you need to create them by
navigating to the Create Remote Profile page (Network Management Platform > Role
Based Access Control > Remote Profiles > Create Remote Profile). When creating a remote
profile, you need to select one or more roles that belong to it. Then you can configure the
name of the remote profile for one or more user accounts in the remote AAA servers.
When an AAA server successfully authenticates a user session, the AAA server includes
the configured remote profile name for that user in the response message that comes
back to Junos Space. Junos Space looks up the remote profile based on this name and
determines the set of roles for the user. Junos Space then uses this information to control
the set of workspaces the user can access and the tasks the user is allowed to perform.
For more information about creating remote profiles, see the “Creating a Remote Profile”
on page 1015 topic (in the Junos Space Network Management Platform Workspaces Feature
Guide).
Domains
You can add, modify, or delete a domain from the Domains page (Role Based Access
Control > Domains). This page is accessible only when you are logged in to the global
domain, which means that you can add, modify, or delete a domain only from the global
domain. By default, any domain you create is added under the global domain. When you
add a domain, you can choose to allow users in this domain to have read-only access to
the parent domain. If you choose to do so, then all users in the subdomain can view
objects of the parent domain in read-only mode.
NOTE: Only two levels of hierarchy are supported: the global domain and
any other domains that you might add under the global domain.
For more information about managing domains, see the “Domains Overview” on page 995
topic (in the Junos Space Network Management Platform Workspaces Feature Guide).
User Accounts
You need to create user accounts in Junos Space in the following cases:
• To perform remote authentication and authorization and allow certain users to be able
to access Junos Space even if all AAA servers are down or are not reachable from Junos
Space—You create local user accounts for these users with a valid password. The
system forces you to configure at least one role for these users. However, authorization
is performed based on the remote profile name that the AAA server provides.
• To perform remote authentication and authorization but also segregate devices among
users based on domains—Because domains must be assigned to user objects in Junos
Space, you must create remote profiles in Junos Space and assign roles and domains
to those profiles.
NOTE: Junos Space enforces certain rules for valid passwords. You configure
these rules as part of the Network Management Platform settings from the
Applications page (Network Management Platform > Administration >
Applications). Right-click the application and select Modify Application
Settings. Then select Password on the left side of the window. On the
subsequent page, you can view and modify the current settings.
For more information about creating user accounts, see the “Creating Users in Junos
Space Network Management Platform” on page 965 topic (in the Junos Space Network
Management Platform Workspaces Feature Guide).
Device Partitions
You can partition a device from the Devices page (Network Management Platform >
Devices > Device Management). You can partition a device into subgroups and then assign
these subobjects to different users by assigning the partitions to different domains. Only
one partition of a device can be assigned to a domain.
NOTE: Device partitions are supported only on M Series and MX Series routers.
For more information about device partitions, see the “Creating Device Partitions” on
page 387 topic (in the Junos Space Network Management Platform Workspaces Feature
Guide).
15.2R1 Starting in Release 15.2R1, you can also authenticate users in certificate
parameter–based authentication mode.
When using Junos Space to manage your network, you must first discover the devices in
your network through a device discovery profile, add these devices to the Junos Space
Platform database, and allow the devices to be managed by Junos Space Platform.
When devices are successfully discovered and managed by Junos Space Platform, the
following actions occur:
• When the network itself is the system of record (NSOR), Junos Space imports the
complete configuration and inventory of the device into its own database. To keep
device information current, Junos Space listens to system log events raised by the
device that indicate device configuration or inventory changes, and Junos Space
automatically resynchronizes its database with the latest information from the device.
When the Junos Space Network Management Platform is the system of record (SSOR),
Junos Space reflects the changes on the device, but a Junos Space user with appropriate
user privileges must resolve out-of-band changes.
• Junos Space uses SNMP polling to collect key performance indicators (KPIs) from the
devices. To enable SNMP polling on managed devices requires that the Network
Monitoring feature be turned on.
NOTE: Starting in Release 16.1R1, you can use a NAT server to discover and
manage devices that are outside your Junos Space network and which cannot
reach Junos Space Platform. When you add a NAT configuration on the
Administration > Fabric > NAT Configuration page and forwarding rules on the
NAT server, the IP addresses translated through the NAT server are added
to the outbound ssh stanza of the external devices.
The following sections list the device management capabilities of Junos Space Platform:
Discovering Devices
Before you can discover devices into Junos Space, ensure the following:
• You know the key details about the devices to discover. You provide this information
as input to discover devices:
• SNMP Credentials–Community string with read-only access if you are using SNMPv2c
or valid SNMPv3 credentials. SNMP credentials are not required if you do not plan
to use Junos Space to monitor faults and performance of managed devices.
• The IP address of the device can be reached from your Junos Space server.
• SSHv2 is enabled on the device (set system services ssh protocol protocol-version v2)
and any firewalls along the way allow Junos Space to connect to the SSH port (default
TCP/22) on the device. To discover devices running the export version of Junos OS,
the wwadapter must be installed on Junos Space and Telnet must be enabled on the
device and reachable from Junos Space.
• SNMP port (UDP/161) on the device is accessible from Junos Space, which allows
Junos Space to perform SNMP polling on the device to collect KPI data for performance
monitoring.
• SNMP trap port (UDP/162) on Junos Space is accessible from the device, which allows
the device to send SNMP traps to Junos Space for fault management.
Starting in Release 16.1R1, you can create a device discovery profile (in the Devices
workspace) to set preferences for discovering devices. After verifying the prerequisites,
you create a device discovery profile from the Network Management Platform > Devices
> Device Discovery Profiles page. The device discovery profile contains the preferences
to discover devices, such as, device targets, probes, authentication details, SSH
credentials, and a schedule at which the profile should be run to discover devices. You
can also manually run the device discovery profile from the Network Management Platform
> Devices > Device Discovery Profiles page. The time required to complete the discovery
process depends on multiple factors such as the number of devices you are discovering,
the size of configuration and inventory data on the devices, the network bandwidth
available between Junos Space and the devices, and so forth.
After your devices are successfully discovered in Junos Space, you can view the devices
from the Network Management Platform > Devices > Device Management page. The
Connection Status for the discovered devices should display “Up” and the managed
status should be “In Sync” as shown in Figure 4, which indicates that the DMI session
between Junos Space and the device is up and that the configuration and inventory data
in Junos Space is in sync with the data on the device.
For complete information about discovering and managing devices, see the Devices
workspace documentation in the Junos Space Network Management Platform Workspaces
Feature Guide.
Authenticating Devices
Starting in Release 16.1R1, new enhancements to device authentication are introduced.
Junos Space Network Management Platform can authenticate a device by using
credentials (username and password), 2048 bit or 4096 bit keys (which uses public-key
cryptographic principles such as RSA, DSS, ECDSA), or the device’s SSH fingerprint. You
can choose an authentication mode on the basis of the level of security needed for the
managed device. The authentication mode is displayed in the Authentication Status
column on the Device Management page. You can also change the authentication mode.
You need to ensure the following to use these modes of authentication:
• Custom key-based–A private key and an optional passphrase. You can upload the
private key to Junos Space Platform and use the passphrase to authenticate the private
key. You don’t need to upload the private key to devices.
For complete information about device authentication, see the Devices workspace
documentation in the Junos Space Network Management Platform Workspaces Feature
Guide.
You can view and export hardware, software, and license inventory details, and the
physical and logical interfaces of a device from the Junos Space user interface. You can
acknowledge the inventory changes on a device from the Junos Space user interface.
For complete information about these tasks, see the Devices workspace documentation
in the Junos Space Network Management Platform Workspaces Feature Guide.
16.1R1 Starting in Release 16.1R1, you can use a NAT server to discover and manage
devices that are outside your Junos Space network and which cannot reach
Junos Space Platform.
16.1R1 Starting in Release 16.1R1, you can create a device discovery profile (in the
Devices workspace) to set preferences for discovering devices.
By default, Junos Space Platform operates in the mode where it considers the network
as the system of record (NSOR). In this mode, Junos Space Platform listens to all
configuration changes on managed devices and automatically resynchronizes its database
copy with the modified device configuration to reflect the changes. You can change this
to a mode where Junos Space considers itself as the system of record (SSOR). In this
mode, Junos Space Platform does not automatically synchronize its copy of the device
configuration with the modified device configuration when it receives information about
out-of-band configuration changes made on a managed device. Instead, the device is
marked as “Device Changed” and you can view the changes and decide whether to accept
the changes. If you accept the changes, the changes are written into the Junos Space
Platform database copy of the device configuration. If you reject the changes, Junos
Space Platform removes the configuration from the device. For complete information
about NSOR and SSOR modes, see the Devices workspace documentation in the Junos
Space Network Management Platform Workspaces Feature Guide.
The following sections list the device configuration management capabilities of Junos
Space Platform:
• Tree view of the device’s configuration hierarchy. Click and expand this tree to locate
the configuration stanzas of interest. For more information about the configuration
options on a device, refer to Junos OS technical documentation.
• Options to filter the configuration and search for specific configuration options in the
tree
• Details of a configuration node when you click the node in the tree
• Options to create, edit, delete, and order entries on the list when you navigate within
a configuration node
• Options to view information about individual parameters (blue information icons), add
comments about individual parameters (yellow comment icons), and activate or
deactivate a configuration option
For complete information about modifying and deploying the configuration by using the
Schema-based Configuration Editor, see the Devices workspace documentation in the
Junos Space Network Management Platform Workspaces Feature Guide.
user who made the change, the configuration change in XML format, whether the change
was made from Junos Space or out-of-band, and also the name of the application or
feature that was used to change the configuration. If you have set up Junos Space Platform
as the system of record, out-of-band configuration changes on a device modify the
managed status of the device to Device Changed. You can view and resolve such
out-of-band changes by selecting the device and selecting Resolve Out-of-band Changes.
You can view a list of all out-of-band changes made on the device. You can accept or
reject the changes.
For complete information about viewing configuration changes, see the Device Templates
workspace documentation in the Junos Space Network Management Platform Workspaces
Feature Guide.
Overview
The Junos Space UI is designed to look and behave in a way that most users are familiar
with. The left tree structure facilitates navigation and the right pane displays information
about the workspace or task selected in the left pane. Multiple users can access the UI
through Web browsers concurrently. All users have access to the same current information
in the same system wide database. Access to tasks and objects is controlled by
permissions assigned to each user.
The Junos Space UI is common to Junos Space Network Management Platform and
Junos Space applications. The information displayed on the Junos Space UI changes
according to the application you select. The examples shown here are from the Junos
Space Platform UI. Other applications may have design variations.
When you log in to Junos Space Platform, the previously configured home page is
displayed. The Junos Space Platform Dashboard, which is the default home page, is
shown in Figure 5.
This display contains three main parts: a task tree on the left, which is always available;
a main window on the right, whose content changes as you select items from the task
tree; and a banner across the top, which offers the date and time, the domain to which
you are logged in, global search, and several icon buttons for frequently used actions.
These parts are described in the following sections.
NOTE: If you access the Junos Space Platform UI in two tabs of the same
browser with two different domains selected and access the same page in
both tabs, the information displayed on the page is based on the latest domain
selected. To view pages that are accessible only in the Global domain, ensure
that you are in the Global domain in the most recent tab in which you are
accessing the UI.
Table 4 describes the global action icons on the right side of the banner.
Enables you to access the Junos Space home page or set the Junos Space home page. Refer to the “Setting
and Accessing the Junos Space Home Page” on page 101 for details.
Displays the application Help. To access workspace context-sensitive Help, click the Help icon after navigating
to that workspace. See “Accessing Help on Junos Space” on page 104.
Displays the My Jobs dialog box from which you can view the progress and status of your current managed
jobs. You can view all your completed, in-progress, canceled, and scheduled jobs in Junos Space Platform.
See “Viewing Your Jobs” on page 164 in the Junos Space Network Management Platform Workspaces Feature
Guide.
Displays the Change User Settings dialog box from which you can change user preferences, such as the
password. See “Changing Your Password on Junos Space” on page 165.
Logs you out of the system. See “Logging Out of Junos Space” on page 166.
Task Tree
The task tree on the left side of the display is always present and facilitates navigation
in the Junos Space Platform UI. As shown in Figure 5, when you first log in, the Application
Selector list displays Network Management Platform by default. You can drop this list
down to see all the Junos Space applications available on your system. (You can install
other applications by using the Applications task group, as described in “Managing Junos
Space Applications Overview” on page 1211 in the Junos Space Network Management
Platform Workspaces Feature Guide.)
You can collapse the task tree to the left by clicking the double left arrow buttons in its
header, and reexpand it by clicking the double right arrow buttons.
Below the application name is the word Dashboard, selected by default. It indicates that
what you see in the right-hand window is the dashboard for the current application—in
this case, Junos Space Platform. The dashboard shows several measures of overall
system health.
Below the Dashboard item in the tree is a list of the workspaces available in the current
application. This list forms the top level of the task tree. If you select a different application
from the Applications list, you see the workspace list change. This topic describes the
workspaces for Junos Space Platform; for the workspaces in other applications, see the
documentation for those applications.
The workspaces in the Junos Space Platform are described at a high level in Table 5.
Devices Manage devices, including adding, discovering, importing, and updating them.
See “Device Management Overview” on page 179 (in the Junos Space Network
Management Platform Workspaces Feature Guide).
CLI Configlets Easily apply a configuration to a device. Configlets are configuration tools
provided by Junos OS. See “CLI Configlets Overview” on page 495 (in the Junos
Space Network Management Platform Workspaces Feature Guide).
Images and Deploy, verify, enable, disable, remove, and execute scripts deployed to devices.
Scripts See “Scripts Overview” on page 622 (in the Junos Space Network Management
Platform Workspaces Feature Guide).
Download a device image from the Juniper Networks Software download site
to your local file system, upload it into Junos Space, and deploy it on one or
more devices simultaneously. See “Device Images Overview” on page 567 (in
the Junos Space Network Management Platform Workspaces Feature Guide).
Reports Generate customized reports for managing network resources. See “Reports
Overview” on page 713 (in the Junos Space Network Management Platform
Workspaces Feature Guide).
Network Assess the performance of your network, not only at a point in time, but also
Monitoring over a period of time. See “Network Monitoring Workspace Overview” on
page 744 (in the Junos Space Network Management Platform Workspaces Feature
Guide).
Configuration See “Managing Configuration Files Overview” on page 873 (in the Junos Space
Files Network Management Platform Workspaces Feature Guide).
Jobs Monitor the progress of ongoing jobs. See “Jobs Overview” on page 901 (in the
Junos Space Network Management Platform Workspaces Feature Guide).
Role Based Add, manage, and delete users, custom roles, domains, and remote profiles.
Access Control From this workspace, you can also manage user sessions. See “Configuring
Users to Manage Objects in Junos Space Overview” on page 963 (in the Junos
Space Network Management Platform Workspaces Feature Guide).
Audit Logs View and filter system audit logs, including those for user login and logout,
tracking device-management tasks, and displaying services that were
provisioned on devices. See “Junos Space Audit Logs Overview” on page 1031
(in the Junos Space Network Management Platform Workspaces Feature Guide).
Administration Add network nodes, back up your database, manage licenses and applications,
or troubleshoot. See “Junos Space Administrators Overview” on page 1051,
“Maintenance Mode Overview” on page 1063, and other topics related to the
Administration workspace in the (in the Junos Space Network Management
Platform Workspaces Feature Guide).
You can expand any of these workspaces by clicking the expansion symbol (+) to the
left of its name. When you do so, the next level of the task tree for that workspace opens.
Some items at this second level may also be expandable subgroups.
You can expand as many workspaces or task groups as you like; previously expanded
ones remain open until you collapse them. The design of the task tree enables you to
jump from area to area within an application with the minimum number of selections.
Main Window
When you log in to Junos Space Platform, the main window shows the application
dashboard by default. If you have set another home page, the main window displays that
page. See “Setting and Accessing the Junos Space Home Page” on page 101 for more
information.
When you select a workspace name (as opposed to expanding it), the main window
changes and displays graphical statistics for that workspace. This display is called
Workspace Statistics. It is similar in functionality to the overall system dashboard, but it
pertains only to that workspace. See “Workspace Statistics Page Overview” on page 123
for more information.
Selecting the name of a task group or task within the workspace causes the main window
to display an inventory of the objects managed in tabular format. See “Inventory Landing
Page Overview” on page 125 for more information.
When you log in to Junos Space Network Management Platform, the default page
displayed is the Junos Space Dashboard page. However, you can set a different page as
the home page and on subsequent logins to Junos Space Platform, the configured home
page is displayed. This is useful because you can configure the home page to the page
that you visit frequently or the page that is related to your role; for example, a device
administrator might configure the Devices Dashboard page as the home page.
Table 6 displays the list of pages in Junos Space Network Management Platform that
you are allowed to set as the home page.
Table 6: Junos Space Platform Pages that Can Be Set as the Home Page
Workspace Page
• Unmanaged Devices
• Model Devices
• Connection Profiles
• Secure Console
• Device Adapter
Table 6: Junos Space Platform Pages that Can Be Set as the Home Page (continued)
Workspace Page
• Search
• Outages
• Dashboard
• Events
• Alarms
• Notifications
• Assets
• Reports
• Charts
• Topology
• Admin
• SNMPv3 Trap Configuration
Table 6: Junos Space Platform Pages that Can Be Set as the Home Page (continued)
Workspace Page
• Platform Certificate
• CA/CRL Certificates
• Authentication Servers
• SMTP Servers
• Email Listeners
• Git Repositories
• Audit Log Forwarding
• Proxy Server
• Tags
• DMI Schemas
• Hardware Catalog
• Purging Policy
The Junos Space Platform home page is displayed in the following cases:
• When you the click the Home icon on the Junos Space banner and select Go to homepage
• When you switch domains and if the page that was displayed prior to the domain
switch is not accessible in the new domain
NOTE: If the configured home page is not accessible in the new domain,
then the Junos Space Dashboard page is loaded.
For more information about how to set and access the Junos Space home page, refer to
“Setting and Accessing the Junos Space Home Page” on page 101.
NOTE: Although you can access Junos Space Platform by using Internet
Explorer versions 9.0 and 10.0, we recommend that you upgrade to Internet
Explorer version 11.0 because it is the only version now supported by Microsoft.
NOTE:
• The Network Monitoring Topology feature of Junos Space Platform is not
supported on Internet Explorer.
• Before you log in to Junos Space, ensure that the Adobe Flash version 10
or later plug-in is installed in your browser.
3. In the Username text box, enter your username. The default username is super. For
information about how to change your username, consult your system administrator.
4. In the Password text box, enter your password. The default password is juniper123.
For information about how to change your password, see “Changing Your Password
on Junos Space” on page 165.
The Junos Space home page appears. If the home page is not set, the Junos Space
Dashboard page is displayed. If the home page is inaccessible due to role or domain
restrictions, a warning message is displayed and the Junos Space Dashboard page is
loaded.
NOTE: If you are a user with access to more than one domain, then an
informational message about switching domains is displayed in a dialog
box.
For more information about the Junos Space Platform UI, see “Junos Space User Interface
Overview” on page 89.
By default, the Junos Space Network Management Platform Dashboard page is displayed
when you log in to Junos Space. You can, however, set a different page as the home page.
You use the Home icon on the Junos Space banner to set and access the Junos Space
home page.
NOTE: If you are already on the home page, then the Set as Homepage' and
Go to Homepage actions are disabled. When you mouse over the actions, a
message is displayed in a tool tip indicating that you are already on the home
page.
NOTE: For more information about which pages can be set as home pages,
see “Junos Space Home Page Overview” on page 94.
1. Navigate to the page that you want to set as the Junos Space home page by using
the task tree in the left-hand pane of the Junos Space Platform UI.
NOTE: When you are not on the home page, click the Home icon on the Junos
Space banner and mouse over Go to Homepage to view the name of the
current home page.
NOTE: The roles that you are assigned and the domains to which you have
access determine whether or not you can access the home page. If your role
does not allow you access to a specific page or if a page is not accessible in
a particular domain, a dialog box is displayed when you click the Go to
Homepage action:
• If the page from which you try to access the home page is the Junos Space
Dashboard page, a message indicating that you do not have permission to
access the home page is displayed.
• If the page from which the you try to access the home page is not the Junos
Space Dashboard page, a message indicating that you do not have
permission to access the home page is displayed and you can choose
whether to load the Junos Space Dashboard page or remain on the current
page.
2. Click Go to Homepage.
You are taken to the configured Junos Space home page. On the navigation tree, the
node corresponding to the home page is selected and subtasks, if any, are visible.
The Getting Started assistants display steps and help on how to complete common
tasks, such as increasing the storage capacity. Getting Started appears in the sidebar
when you log in to Junos Space only if the Show Getting Started on Startup check box at
the bottom of the sidebar is selected. If the sidebar is not shown, you can display it by
selecting the Help icon in the Junos Space banner.
The Getting Started topics are context-sensitive per application. Getting Started displays
all the steps of a task. From a step in a task, you can jump to that point in the UI and
complete the task.
1. Select an application from the Applications list above the task tree.
If the sidebar is not displayed, select the Help ( ) icon at the right side of the Junos
Space header. The sidebar appears.
For example, if you are in the Network Management Platform UI, click the Increase
Space Capacity link. A list of required steps appears in the sidebar. Each step contains
a task link and a link to Help.
You move to a point in the UI from where you can complete the task. The assistant
remains visible on the sidebar to aid navigation to subsequent tasks.
5. Access help for a specific step by clicking the Help icon next to that step.
To close the Getting Started sidebar, click the double-arrow button on its top-right corner.
Junos Space provides a Help system that is context-sensitive per workspace. The Help
system provides information about each element in the system, including workspaces,
dashboards, tasks, inventory pages, and actions. Help topics appear as links on the
sidebar.
2. Click the Help icon at the right side of the Junos Space header.
The sidebar appears, if it is not already displayed, with the Help section open listing
specific topics for that workspace and tasks.
4.
Click the icon at the top right of the sidebar to hide it.
For more information about the Junos Space Platform UI, see the “Junos Space User
Interface Overview” on page 89 topic.
Related • Using the Getting Started Assistants on Junos Space on page 103
Documentation
The following sections describe the various controls that can appear on the Junos Space
UI:
Check Box
You can use check boxes to select or deselect an option. For example, to ensure that
there is at least one uppercase character when a user creates or modifies a password,
an administrator can select the At least one uppercase character check box (as shown
in Figure 7) on the Administration > Applications > Network Management Platform >
Modify Application Settings (from the Actions menu) > Password > Advanced Settings
page. On a page, you can select one or more check boxes.
With Junos Space, you can select all objects on an inventory landing page by selecting
the check box that is displayed adjacent to the first column header. For example, you
can select the check box (see Figure 8) adjacent to the Name column on the Device
Management inventory landing page to select all devices displayed on this page.
For certain tasks, you can select an appropriate check box in the Junos Space UI to select
all objects spread across multiple pages. With this feature, you do not need to select
each object individually on multiple pages.
For example, when you want to assign all devices to a domain, you can select the Select
all items across all pages check box on the Domains page at the time of domain creation,
which selects all devices (indicated by the check mark next to the devices as shown in
Figure 9). However, after all the devices are selected, you can deselect one or more
devices, if needed.
Figure 9: Check Box to Select All Objects Across Multiple Pages: Domains
Page
Though some pages support selection of all objects across multiple pages, you may not
be able to deselect any of these objects after the selection. For example, when you select
the Select All across Pages check box when backing up the configuration files (on the
Configuration Files > Config Files Management > Backup Configuration Files page), you
cannot deselect any of the selected devices (see Figure 10). The configuration of all
devices are backed up.
Figure 10: Check Box to Select All Objects Across Multiple Pages: Backup
Configuration Files Page
NOTE: Only certain pages in the Junos Space UI support the selection of
objects across multiple pages.
Date Picker
Using a date picker, you can select a date by either typing it into a text box or by using a
drop-down Calendar control.
In Figure 11, you can specify a date by typing the date in the text box or from the Calendar
control by clicking the icon next to the text box. To select today’s date, click Today on
the Calendar control.
Drop-down List
With a drop-down list, you can select from a list of values (see Figure 12). Clicking the
arrow next to the list box opens the list. Junos Space also provides an editable drop-down
list, which is a combination of a drop-down list and an editable text box (see Figure 13).
You can enter the first few letters in the text box to narrow down the list of values.
Option Button
Using an option button, you can make a single choice among a set of mutually exclusive,
related options. Only one button at a time can be selected from the available options.
The default option is selected (see Figure 14).
Search Field
Use the Search text field on the right of the inventory page banner to look for specific
objects to display on the inventory landing page. To find objects (within columns) on this
page, enter the search criteria in the Search field (see Figure 15). This field supports the
same search syntax as the global search field (see “Using Global Search” on page 162).
For example, enter “os:junos AND down” to find devices that are down on the Device
Management inventory landing page. This feature is more powerful than the column
filter because it allows you to use Boolean expressions.
Clicking the magnifying glass at the right of the search field displays a list of objects
matching the search criteria. If you press the down arrow after entering the search criteria
in the search field , a list of search options is displayed. When you select a search option
from the list, only those inventory items that are specific to that search option are
displayed on the page.
You can create tags to categorize objects. For more information about tagging objects
to select similar objects, see “Tagging an Object” on page 1394 (in the Junos Space Network
Management Platform Workspaces Feature Guide).
To display all the inventory objects on the page again, clear the contents of the Search
field and press Enter.
NOTE: You must append "*" if you want to search using partial keywords.
Otherwise, the search might return zero matches.
To search for specific objects across the entire Junos Space Network Management
Platform, use the Search field on the banner at the top of the inventory page (see
Figure 16). For more information about global search, see “Using Global Search” on
page 162.
Spin Box
A spin box is a text box with up and down arrows that you can click to change the value
incrementally (see Figure 17). You can also type a valid value in the box.
Slider
Using a slider, you can select a value from a continuos range of values by sliding the
indicator along a bar. The indicator shows the current value.
In Figure 18, the automatic logout of a user due to inactivity is set to 90 minutes by using
the slider control.
Text Box
A text box enables you to:
• Enter or edit text (for example, the Login ID or Password fields in Figure 19).
• Upload files from your computer to the Junos Space server, such as the Image File or
X509 Cert File fields in Figure 19.
• Choose a value from a drop-down list of values when you enter the first few letters in
the text box (see Figure 20).
Use the label associated with a text box to identify the purpose of a text box. You can
gain additional information about some of the text boxes from the information icons that
are associated with the text boxes ( ). For example, the Temporary Password and
Password text boxes have information icons associated with them as shown in Figure 19.
You must mouse over the information icon for Junos Space to display information about
the text box with which the information icon is associated. For example, when you mouse
over the information icon associated with the Password text box, the conditions that
must be met when you enter a password are displayed.
NOTE: Not all text boxes in Junos Space have information icons associated
with them.
Usually, if there is a default value associated with a text box, then it is displayed by default
on the text box. However, to determine the range of values that is accepted in a text box,
perform the following steps:
• To determine the minimum value, enter a negative value (for example, –1) in the text
box. An error icon appears next to the text box. Mouse over this icon to see the minimum
value that is accepted in this text box (see Figure 21).
• To determine the maximum value, enter a very high value in the text box. An error icon
appears next to the text box. Mouse over this icon to see the maximum value that is
accepted in this text box (see Figure 22).
Tree View
Using the tree view, you can view and interact with a collection of Junos Space objects
that are arranged hierarchically. You can select only one object from the objects that are
displayed in tree view. You can expand and collapse an object by clicking the plus and
minus expander buttons respectively (see Figure 23).
Scrolling Controls
Junos Space Network Management Platform provides horizontal and vertical scroll bars
on inventory landing pages, which you can use to scroll the contents of the page by
clicking one of the scroll arrows, clicking an area in the scroll bar, or dragging the scroll
bar. For example, to view data that is at the bottom of the Junos Space page, you can
drag the vertical scroll bar toward the bottom of the page. Figure 24 shows the horizontal
scroll bar that enables you to scroll horizontally through the Junos Space page allowing
you to view data that is on the left or right.
Sizing Controls
You can use the minimize, maximize, and close buttons of your browser window to hide
the Junos Space application window, enlarge the window to fill the whole screen, and
close the window, respectively.
NOTE: Minimize the window when you want the Junos Space application
window to be temporarily out of the way instead of closing it.
Close the window when you have finished working on it and there is no need
for you to return.
To resize a window (make it smaller or bigger), point to any of the window's borders or
corners. When the mouse pointer changes to a double-headed arrow, drag the border
or corner to shrink or enlarge the window. You cannot resize a window that is already
maximized.
Junos Space Network Management Platform displays tooltips, which are small pop-up
windows that provide information about an unlabeled control, such as the information
that is displayed automatically when you mouse over an icon on a toolbar (see Figure 26).
Also, Junos Space sometimes displays pop-up messages to report conditions that require
your attention. Depending on the severity level, the icons that are displayed in a message
differ. To gain an understanding of the various types of messages and the icons that are
displayed in the Junos Space UI, see the following sections:
Error Messages
Junos Space displays an error message to alert you about a problem that has already
occurred along with a recommendation, if any, to resolve the problem. For example, in
Figure 27, the error message alerts you that the Junos Space UI may be out of sync with
the Junos Space server and that you need to refresh the browser window (which is likely
to resolve the issue).
Confirmation Messages
Junos Space often displays a confirmation dialog box, which is a modal dialog box that
asks you whether you want to proceed with the action that you initiated from Junos Space
Network Management Platform. A confirmation dialog box typically consists of a question
and two or more responses. You have to select a response and based on your choice
Junos Space completes or cancels the task that you initiated. For example, when you
initiate a database backup operation, you are asked to confirm whether you want to
perform the backup operation because this operation may have an impact on Junos
Space performance. In Figure 28, clicking OK initiates the database backup operation,
whereas clicking Cancel closes the current page.
Information Messages
An information message communicates some sort of information to you pertaining to
your current activity and appears in a modal dialog box. For example, when you choose
to proceed with the database backup operation, Junos Space displays an information
message containing a job ID, which you can click to know whether the backup operation
is a success or a failure (see Figure 29).
NOTE: Not all messages that are displayed in Junos Space are associated
with icons.
Error icon—Indicates that an error or problem For example, the following error message is displayed if you
has occurred, which should be resolved try to create a tag without a tag name or a user without a
before you proceed username. Providing appropriate information in all fields
• Warning icon—Indicates a condition that For example, the following error is displayed when you try
might cause a problem in the future to delete an SMTP server that is active:
• These icons come in two different sizes: Figure 31: Message with the Larger Warning
larger and smaller. A smaller warning icon
Icon
indicates that you might have to think twice
before you proceed with the action. A larger
warning icon indicates that the action you
initiated cannot be performed because of
various constraints.
Information icon—Presents you with useful The following message indicates that a backup operation
information. is triggered:
Question mark icon—Normal confirmation Depending on your response to the following message, Junos
message to which you typically respond with Space performs a suitable action.
a "Yes" or "No"
Figure 34: Message with the Question Mark
Icon
Check mark icon—Indicates that the action The following message indicates that a private tag with the
you initiated is a success name “test” is successfully created:
Junos Space Network Management Platform status indicators enable you to monitor
the status of an action that you initiated from Junos Space. The following status indicators
in Junos Space are the most common:
Progress Bars
The progress bar shows you the progress of an action that you initiated from Junos Space.
In Junos Space, progress bars are typically displayed when you export files from Junos
Space to your computer, add an application to Junos Space, and so on. For example,
when you export a configuration file, Junos Space displays the progress of the export
action in a dialog box (see Figure 36). When the action is completed, the progress bar
displays 100%.
Status indicators that are displayed for users are listed in Table 8:
Users in disabled state cannot log in to Junos Space Network Management Platform. For more
information about enabling or disabling a user, see “Disabling and Enabling Users” on page 980 (in
the Junos Space Network Management Platform Workspaces Feature Guide).
Status indicators that are displayed for devices are listed in Table 9:
Device is up.
Device is down.
Ensure that the status of the device is up before initiating any action on the device. Actions
initiated on devices that are down are likely to fail.
Each job has a job status indicator. Table 10 describes these indicators.
The job is in progress. You can cancel only those jobs that are in progress from the Actions
menu.
When you log in to Junos Space Network Management Platform, the home page is
displayed. By default, the home page for Junos Space Platform is the Dashboard page.
However, if you previously configured a different page as the home page, then the
configured home page is displayed when you log in.
The Junos Space Platform dashboard, as shown in Figure 37, displays graphs that provide
information about the overall system condition, the fabric load history, the active users
history, and the percentage of jobs in different states. The charts are visible to all users
and are updated in real time.
NOTE: If you do not have user privileges to view detailed data, you might not
be able to view detailed information if you select a gadget.
2. (Optional) To view more information related to the overall system condition, click
Overall System Condition or the indicator needle.
You are taken to the Fabric page, where you can view detailed information about the
nodes in the fabric. For more information, see “Viewing Nodes in the Fabric” on page 1092.
3. (Optional) To view information related to the fabric load, on the Fabric Load History
graph:
• Mouse over a graph data point to view the average CPU usage percentage.
• Click the blue line depicting the CPU usage to view detailed information.
You are taken to the Fabric page, where you can view detailed information about
the CPU, memory, and disk usage for the nodes in the fabric.
4. (Optional) To view information related to the active users, on the Active Users History
graph:
• Mouse over a graph data point to view the total number of active users at that point.
• Click a data point on the graph to view more information about the active users at
that point.
You are taken to the User Accounts page, where the active users are displayed. For
more information, see “Viewing User Statistics” on page 994.
5. (Optional) To view information related to the jobs, on the Job Information graph:
• Mouse over a segment in the pie chart to view the percentage of jobs with a particular
status; for example, cancelled jobs, successful jobs, or failed jobs.
• Click a segment of the pie chart to view details of jobs with status corresponding
to the segment.
You are taken to the Job Management page, where the jobs filtered by the status
are displayed. For more information, see “Viewing Jobs” on page 908.
6. (Optional) You can move any chart displayed on the Dashboard page by clicking
inside the title bar and dragging the chart.
7. (Optional) You can resize any chart displayed on the Dashboard page by hovering
over an edge and clicking and dragging the edge.
Use the task tree on the left side of the page to navigate application workspaces and
perform tasks within a workspace. When you select an application from the Applications
list (at the top left of the Junos Space UI), all the workspaces for the selected application
are displayed in the task tree.
If you know the workspace in which you want to perform an action (task), select the
workspace from the task tree on the left side of the page. The right side of the page
displays information about the selected workspace and its objects.
Workspace Statistics
When you select the name of a workspace from the task tree, Junos Space Network
Management Platform displays high-level statistics representing the status of managed
objects in that workspace. The statistics and charts displayed for different workspaces
are different. Figure 38 shows the charts displayed on the Devices workspace statistics
page.
If a chart has more data points than can be viewed clearly simultaneously, a scroll bar
appears at the bottom or side of the chart.
If you click a bar or pie-chart segment, you navigate to the corresponding inventory page,
filtered according to the bar or segment you selected. For example, if you click the MX240
devices bar on the Device Count by Platform bar chart, you navigate to the Devices >
Device Management inventory page, which in this case displays all the MX240 devices
on the network that are discovered and managed by Junos Space Network Management
Platform.
You can move the charts and graphs on the page or resize them.
You can also print or save the statistics by right-clicking the graphic (bar chart or pie
chart) and selecting the appropriate option.
In the Junos Space Network Management Platform UI, you navigate to an inventory page
by selecting an application, expanding an application workspace, then selecting a
management task. For example, to view the Device Management inventory page, select
Devices > Device Management.
The inventory pages display information related to managed objects for a particular task
group or task in tabular format. The fields that are displayed are different for different
inventory pages, depending on the task group that you selected.
For each managed object, specific data associated with it is stored in the Junos Space
Platform database. For example, in the case of devices, device name, interfaces, OS
version, platform, IP address, connection, managed status, and so on are stored.
Inventory pages enable you to view and manipulate managed objects individually or
collectively. Managed objects include devices, logs, users, jobs, clients, software, licenses,
and so on. You can organize your view to display only those objects that you want to see,
in the way that you want to see them.
You can select an object or objects by selecting the check box to the left of each object
on the inventory page. You can select one, several, or all objects and perform actions on
them using the shortcut menu or the Actions menu. Selecting the check box to the left
in the first column of the column header row selects or deselects all items. The objects
that you select and on which you perform an action remain selected.
Paging Controls
Figure 39 shows the paging controls that appear at the bottom of the inventory page.
You can use these controls to browse the inventory when the inventory is too large to fit
on one page.
The Page box lets you jump to a specific page of the inventory. Type the page number in
the Page box and press Enter to jump to that page. The Show box enables you to
customize the number of objects displayed per page. Table 11 describes other table
controls.
Sorted-by Indicator
The sorted-by indicator is a small arrowhead next to a column name. It displays how the
objects are sorted in a column. When you sort a column, the column name is highlighted
and the indicator appears.
You can sort inventory data using the Sort Ascending and Sort Descending commands
on the column header drop-down menu. Click the down arrow on a table header to view
the menu. In Figure 40, the device inventory is sorted by the Name column.
You can show or hide columns on the inventory page by selecting or not selecting the
column name on the Columns cascading menu, as shown in Figure 41. All column header
drop-down menus have this option. Only the columns that are selected appear in the
inventory table.
Filter Submenus
For information about filtering options in Junos Space Platform Release 17.2R1 and later,
see “Filter Management in Junos Space Platform User Interface” on page 132.
Toolbar Icons
Almost all inventory landing pages provide a toolbar containing icons that provide easy
access to frequently used tasks. While some icons are common across inventory landing
pages such as the Display Quick View icon (which displays a small window summarizing
data about the selected object), most icons are specific to an inventory landing page.
For example, in Figure 42, the Modify User icon is specific to the User Accounts inventory
landing page.
You can perform actions on one or more selected items on an inventory page by using
the Actions menu, or by right-clicking the items to invoke the shortcut menu. To use the
Actions menu, select one or more objects, select an action or subgroup of actions from
the Actions menu. (Note that the subgroup has an arrowhead next to its name.) For
example, to view the physical interfaces of a device, select that device on the Device
Management inventory page, open the Actions menu, expand the Device Inventory
subgroup, and select View Physical Inventory.
You can also select one or more items on the inventory page, then right-click. The shortcut
menu appears and you can select an action or subgroup of actions.
NOTE: If you are using Mozilla Firefox earlier versions, the Advanced JavaScript
Settings might disable the shortcut menu.
1. In Mozilla Firefox, select Tools > Options to display the Options dialog box.
If you are using newer versions of Mozilla Firefox, it may not be necessary to
perform the preceding steps. By default, you need not change any of the
Firefox settings. But, if you have changed the settings or for some reason the
shortcut menus do not appear properly, then you need to perform the
following steps in the recent versions:
Exporting Data
You can export data that is displayed on certain inventory landing pages such as the MD5
Validation Result inventory page (in the Images workspace) as well as export job details
pertaining to certain tasks initiated from Junos Space Platform. For example, you can
export job details related to device discovery, staging and deployment of device images,
and so on.
NOTE: Not all jobs in Junos Space support the export of job details.
The data is exported as a comma-separated file (CSV) to your computer, allowing you
to process the data offline. For example, you can use this data to identify devices on
which staging or deployment of an image failed.
To export the data that is displayed on the MD5 Validation Result page as a CSV file:
1. On the Junos Space Platform UI, select Images and Scripts > Images.
The MD5 Validation Result page displays the results of verification tasks.
5. Click OK on the File Save dialog box to save the file to your local file system.
6. After you save the file, to return to the MD5 Validation Result page, click the [X] icon
on the Exporting Validation Results dialog box to close it.
Navigate to the location where you saved the file and open the file by using an application
such as Microsoft Excel. If you are opening this file as an Excel workbook, then filter the
data for the Failed status in the Checksum Result column to identify devices in which the
images are not staged completely. From the filtered data, see the Device Image Name
column to obtain information about the images that are not staged completely.
1. On the Junos Space Platform UI, select Jobs > Job Management.
2. Double-click the image deployment job whose details you want to export as a CSV
file.
4. Click OK on the File Save dialog box to save the file to your local file system.
5. To return to the Job Management page, click OK on the Exporting Device Image Job
dialog box.
Use an application such as Microsoft Excel to open the downloaded file from your
computer. If you are using Microsoft Excel, you can filter data in the Status column to
identify the devices on which the deployment of images failed.
• Understanding Filtering Options in Junos Space Platform User Interface on page 132
• Managing Filtering Options on page 143
• Error Conditions and Error Messages for Filters on page 151
Overview
On various Junos Space Platform pages, you can use the Filter menu to show or hide
table entries based on the filtering criteria that you specify. Filters enable you to quickly
find and evaluate the entries that are relevant to your specific needs.
Many of the columns in Junos Space page tables support filtering. To know whether or
not a column supports filtering of data, click the down arrow next to the column name.
If the Filter submenu appears, then that column supports filtering of data. The filtering
criteria that are available for you depend on the selected column. You can create filters
that combine criteria from more than one column.
From Release 17.2R1 onward, Junos Space Platform introduces the following
enhancements to filtering options:
• Ability to manually enter filter conditions with autocomplete and suggestion support.
For a list of pages and columns that support filtering, see “Pages and Columns that
Support Filtering” on page 133.
In releases earlier than 17.2R1, Junos Space Platform supports only basic filtering. In those
releases, you can specify only one set of filter criteria at a time, and the filter setting is
lost when you modify the criteria. From Junos Space Platform Release 17.2R1 onward,
you can save multiple filters. You can also mark up to 10 filters as favorites in each of the
pages that support enhanced filtering.
The Filter menu that appears when you click the filter icon lists up to 10 filters. The 10
filters that are listed in the Filter menu are arranged in the following order of filter
categories: favorite filters, public filters, and private filters. If there are more than 10 filters,
those filters are listed under the More Filters submenu.
NOTE: The More Filters submenu is not displayed if you have not saved any
filter. However, the More Filters submenu appears even if you have saved only
one filter.
If you have Filter Management permissions to create or modify filters, you can also choose
to share the saved filters with other users by marking the filters as public.
For more information about creating, saving, modifying, and deleting filters, see “Managing
Filtering Options” on page 143.
From Junos Space Platform Release 17.2R1, you can also manually enter filter criteria in
the filter text box that appears when you click the Show/ Clear and Hide Filters option
from the Filter menu. For more information about manually specifying filter criteria, see
“Managing Filtering Options” on page 143.
Benefits
Filters enable you to quickly find and evaluate the entries that are relevant to your specific
needs. Ability to save and share filters enables you to configure multiple filters for a page
that can be preserved across sessions and shared with multiple users.
The following table lists the pages and columns that support enhanced filtering and also
the data types for each of the columns:
IP Address Number
Platform String
OS Version String
Domain String
Vendor String
IP Address String
Speed String
MTU String
Description String
Domain String
IP Address String
Description String
Domain String
Job ID Number
Description String
Version String
Domain String
Description String
Domain String
Description String
Domain String
Category String
Domain String
Title String
Domain String
Domain String
Value String
Domain String
Version String
Type List
Domain String
Type List
Category String
Format List
Domain String
Description String
Domain String
Domain String
Name String
Percent Number
State List
Parameters String
Summary String
Owner String
Email String
Status List
Type List
Description String
IP Address String
User IP String
Domain String
Application String
Task String
Timestamp Date
Result String
Description String
Job ID Number
Description String
Port Number
Protocol List
Enabled List
Owner String
Description String
Domain String
Created By String
Description String
Domain String
Description String
Generated By String
Format String
Job ID Number
Junos Space Platform supports basic filtering options on the following pages:
NOTE: Filtering is supported only for the State and Schema Installed
columns.
From Junos Space Platform Release 17.2R1 onward, you can manually enter the filtering
criteria to create the filters that meet your specific requirements.
1. From any of the pages that support Filter Management options, click the Filter icon.
A list showing the names of columns that support filtering and the following two
options appears:
• Not. The Not option enables you to specify conditions based on which you want to
filter out entries.
4. From the list, select the columns for which you want to specify the filter conditions
and specify the conditions by using any of the operators supported for the specified
column. Table 12 lists various operators that you can use for each of the data types
supported for filtering.
You can specify multiple conditions by using an AND or an OR operator. The Filter
field supports autocomplete and provides suggestions for column names, attributes,
and operators even as you type inside the field.
NOTE: If the values you enter for any of the parameters contain spaces,
enclose such values in single quotation marks. For example, Domain
Contains 'test domain'. However, if the single quotation mark is part of the
search string, use the backslash escape character (\) before the quotation
mark. For example: Domain Contains '\'test domain\''.
Ends- with
Contains
!=
Not-contains
Numbers or Date =
!=
>
<
<=
>=
List =
!=
• ID > 2000000 AND 'Job Type' ends-with 'elements' AND Parameters contains '1.1.1.1'
OR Parameters = 192.168.27.72 AND Owner = SUPER
This filter on the Job page displays jobs that meet the following criteria: The job ID
is a number greater than 2000000, the job type ends with the text elements, the
Parameter field contains 1.1.1.1 or 192.168.27.72, and the owner is the superuser.
This filter on the Device page displays devices that have the connection status set
to down, the managed status set to in sync or synchronizing, and device family
name starts with Junos.,
5. After you enter the conditions, you can save or apply the filter. To save the filter, click
the Save Filter icon and complete the steps as explained in “Saving a Filter” on page 148.
To apply the filter without saving, click the Apply Filter icon. For more information
about applying filters, see “Applying a Filter” on page 150.
To clear the filter conditions you entered or the filter that you applied, click the Clear
Filter icon. Alternatively, you can click the Clear and and Hide icon to clear the filters
and hide the filter bar.
For a list of error messages, see “Error Conditions and Error Messages for Filters” on
page 151.
Many of the columns in Junos Space user interface tables support filtering. To know
whether or not a column supports filtering of data, click the down arrow next to the
column name. If the Filter submenu appears, then that column supports filtering of data.
The criteria that are available for you to filter on depend on the selected column. You
can create filters that combine criteria from more than one column.
On Junos Space pages that support enhanced filtering options, the Filter field and the
Save Filter, Apply Filter, and Clear Filter icons appear when you select any of the items
from the Filter submenu. The selected criteria are displayed in the Filter field. You can
choose to apply, save, or clear the filtering criteria by clicking the appropriate icon.
On Junos Space pages that do not support enhanced filtering options, when you select
any of the items from the Filter submenu, Junos Space Platform displays the filter criteria,
including the columns being filtered, above the table. Junos Space Platform displays a
red X to the left of the filter criteria above the table. You can clear the filter and restore
the table to its original view by clicking the X.
The following procedures describe how to use the different types of available filters.
1. On the Junos Space Platform UI, click the down arrow on the column header and
select Filters.
The Filters submenu appears, displaying the list of operators or values that you can
select, based on the type of values in the column.
2. Based on the submenu that appears, perform one of the following procedures.
You can select both Before and After dates and times to filter the entries by a
specific time period. You can also select On to view events recorded on a specific
date.
b. Click the calendar icon and select the date from the calendar.
You can click Today to view the events that occurred today at the specified time.
c. Click the arrow beside the time list and select the time.
a. In the text box that appears, type the alphanumeric string based on which you
want to filter entries.
To specify filters for a field with discrete values such as Success or Failure, or True or
False:
a. From the list of values that appears, select the check boxes for one or more values
based on which you want to filter entries.
3. Click Go to view the entries filtered based on the criteria that you specified.
4. On pages that support enhanced filtering options, you can choose to save the filter
after you specify the required criteria. To save the filter, click the Save Filter icon and
complete the steps as explained in “Saving a Filter” on page 148. To apply the filter
without saving, click the Apply Filter icon. For more information about applying filters,
see “Applying a Filter” on page 150.
To clear the filter conditions you entered or the filter that you applied, click the Clear
Filter icon.
You can also filter entries based on combined filters with different criteria specified for
different columns. For example, you can filter for all events on a certain date whose
status was success. When you use multiple filters, the filters are joined using the logical
AND operator.
To clear only the part of a filter that applies to a any of the columns, click the down arrow
on the column header and clear the check box next to Filter.
Saving a Filter
You can create a filter either by using the filtering options that are available in the Junos
Space Platform UI or by manually entering the filter criteria in the Filter field that appears
when you click the Filter icon. After you specify the filtering criteria, you can save the filter.
To save a filter:
The criteria you specified, either by typing in the Filter field or by using the Filter
submenu options in the Junos Space Platform UI, appear in the Filter field.
5. (Optional)To share the filter with other users, select the Make Public check box.
NOTE: You cannot change a public filter to a private filter after you save
the changes. However, you can change a private filter to a public filter
from the Modify Filters page.
6. (Optional) If you want to mark the filter as a favorite, select the Mark as Favorite check
box.
Alternatively, you can add a filter to the list of favorites or remove a filter from the list
of favorites from the Manage Filters page.
7. Click Save to save the filter. To close the page without saving the filter, click Cancel.
Modifying a Filter
From the Manage Filters page. you can modify saved filters.
1. From the Junos Space Platform UI, go to the page that contains the filter that you
want to modify. For example, the Device Management or View Physical Devices page.
4. From the list of filters, click the filter entry that you want to modify.
• Filter Criteria–Filter criteria to apply for the filter. For information about manually
entering the filter criteria, see “Creating Filters by Manually Entering the Filter Criteria”
on page 144.
• Make Public–Specify whether the filter is a public filter. Public filters are available
for all users. However, note that only users with Filter Management permissions to
create or modify filters can create public filters. This check box is disabled if the
selected filter is a Public filter. That is, you cannot clear this check box after you
select this check box and save the filter.
NOTE: To create a public filter, you must have both Create Filter and
Modify Filter roles assigned to your account.
• Mark as Favorite–Specify whether the filter is a favorite or not. You can select this
check box to mark the selected filter as favorite. To remove a filter from the list of
favorites, clear this check box. Favorite filters are listed on top of the Filter menu
options. If there are favorite filters and filters that are not marked as favorites, the
filters that are not marked as favorites appear in the More Filters submenu.
6. Click Modify to save the changes. Click Reset if you want to discard the changes.
For a list of error messages, see “Error Conditions and Error Messages for Filters” on
page 151.
Public filters are filters that are available to all users. To create a public filter, you must
have both Create Filter and Modify Filter roles assigned to your account. Junos Space
Platform adds the suffix (Public) to the names of filters that are made public.
1. When you save a filter, select the Make Public check box. For more information about
saving filters, see “Saving a Filter” on page 148.
2. When you modify a filter, select the Make Public check box. For more information
about modifying filters, see “Modifying a Filter” on page 149
NOTE: After you make a filter public, you cannot change that to a private
filter.
Applying a Filter
• From pages that support enhanced filtering, you can apply a filter by clicking the name
of the filter from the Filter menu. Alternatively, while creating a filter, you can click the
Apply Filter icon (the green tick mark) next to the Filter field.
• From pages that do not support enhanced filtering, you can apply a filter by selecting
and specifying filter options from the Filter submenu available for columns that support
filtering and then clicking Go.
Clearing a Filter
Junos Space Platform provides you the following options to clear a filter that is applied
to a page.
• On Junos Space pages that support enhanced filtering options, if a filter is applied to
the page, the filter criteria is displayed in the Filter field. You can click the Clear Filter
icon to clear the applied filter. Alternatively, you can click the Clear and Hide Filters icon
from the Filter bar or the Show/Clear and Hide item in the Filter menu.
• On Junos Space pages that do not support enhanced filtering options, when you select
any of the items from the Filter submenu, Junos Space Platform displays the filter
criteria, including the columns being filtered, above the table. Junos Space Platform
displays a red X icon to the left of the filter criteria above the table. You can clear the
filter and restore the table to its original view by clicking the X icon.
Deleting a Filter
From the Manage Filters page. you can delete saved filters.
1. From the Junos Space Platform UI, go to the page that contains the filter that you
want to delete. For example, the Device Management or View Physical Devices page.
4. From the list of filters, click the filter entry that you want to delete.
5. Click the Delete icon above the top-left corner of the list of filters.
6. On the Delete Filter page, click OK. Click Cancel if you do not want to delete the selected
filter.
See Also • Understanding Filtering Options in Junos Space Platform User Interface on page 132
Incorrect filter 'Name' juniper Incorrect filter query, Invalid filter query
query. please provide a
Comparison 'Name' has test OR comparison after
missing after 'Device Alias' column name
column name. contains test (Name)
Table 13: Error Conditions and Error Messages for Filters (continued)
Validation Error
Validation Error Message on the
Sample Filter Message at Apply Save Filter and
Error Condition Data Filter Manage Filter Page
Incorrect filter ( Name = test Incorrect filter query, Invalid filter query
query; “)” missing. please insert ")" to
complete the query
(test)
Incorrect filter Name = test ) Incorrect filter query, Invalid filter query
query; Unexpected token
Unexpected ")"
token ")"
Incorrect filter Name = test AND ( Incorrect filter query, Invalid filter query
query; Name = test1)) Unexpected token
Unexpected ")"
token ")"
Incorrect filter Name = test AND ( Incorrect filter query, Invalid filter query
query; Name = test1)( Unexpected token
Unexpected "("
token "("
Incorrect filter ( Name = test AND Incorrect filter query, Invalid filter query
query; ")" ( Name = test1) please insert ")" to
missing. complete the query
(test)
Invalid filter query ( Name starts-with Invalid filter query. Invalid filter query
") Query should start
with "(" or NOT or
column name.
Table 13: Error Conditions and Error Messages for Filters (continued)
Validation Error
Validation Error Message on the
Sample Filter Message at Apply Save Filter and
Error Condition Data Filter Manage Filter Page
The greater than Name > Test Filtering of “Name” Filtering of “Name”
condition is not column is not column is not possible
supported for the possible with with “Greater than”
specified column. “Greater than” condition
condition
The less than Name < Test Filtering of “Name” Filtering of “Name”
condition is not column is not column is not possible
supported for the possible with “Less with “Less than”
specified column. than” condition condition
The “greater than Name >= Test Filtering of “Name” Filtering of “Name”
or equal to” column is not column is not possible
condition is not possible with with “Greater than or
supported for the “Greater than or equal to” condition
specified column. equal to” condition
The “Less than or Name <= Test Filtering of “Name” Filtering of “Name”
equal to” column is not column is not possible
condition is not possible with “Less with “Less than or
supported for the than or equal to” equal to” condition
specified column. condition
Table 13: Error Conditions and Error Messages for Filters (continued)
Validation Error
Validation Error Message on the
Sample Filter Message at Apply Save Filter and
Error Condition Data Filter Manage Filter Page
The input date 'End Time' = 10pm “End Time” column “End Time” column
and time value accepts only valid accepts only valid
does not match date, Example: date, Example:
the supported 11/03/2017 01:14AM 11/03/2017 01:14AM
format.
The input value is State = SUCCES “State” column can “State” column can
not supported for not be filtered with not be filtered with
the specified the provided filter the provided filter
column. value “SUCCES” value “SUCCES”
See Also • Understanding Filtering Options in Junos Space Platform User Interface on page 132
The global search field on the Junos Space Network Management Platform UI helps you
to quickly locate objects within Junos Space Platform. When you search for an object by
using global search, Junos Space Platform performs a full-text search operation for
objects within Junos Space Platform, and displays the matches found.
The search results are filtered on the basis of your Role-Based Access Control (RBAC)
permissions, such as the tasks that a user is allowed to perform and the domains to which
a user is assigned. For example, users are shown results only for tasks for which they
have the appropriate permissions or results related to domains to which the users are
assigned. For more information about RBAC permissions, see the “Role-Based Access
Control Overview” on page 931 topic (in the Junos Space Network Management Platform
Workspaces Feature Guide).
The search is performed and the results are displayed based on how the Junos Space
Platform objects are indexed. Table 14 lists the indexed objects on which you can perform
a search operation by using the global search feature.
Junos Space Platform monitors its database at regular intervals to identify new objects
that need to be indexed. The default interval is set to five seconds.
NOTE:
• An administrator can configure the refresh interval from the Administration
workspace. For more information about configuring the refresh interval,
see the Index auto update interval in seconds parameter in “Modifying Junos
Space Network Management Platform Settings” on page 1222 (in the Junos
Space Network Management Platform Workspaces Feature Guide).
• An administrator can also refresh the search index manually from the
Administration workspace by navigating to Administration > Applications
> Network Management Platform and selecting Refresh Search Index from
the Actions menu.
Audit log • userName—Name of the user who performed an action that generated this audit log entry.
For example, when userA logs in to Junos Space Network Management Platform, an audit
log entry is generated to record the login activity. When you search for userA, this audit log
entry is displayed as part of the search results.
• userIpAddr—IP address from which the action was performed.
• taskName—Action that was performed by the user, such as Login, Logout, and so on.
• timeStamp—Date and time of action.
• executionResult—Result of the action, such as Success, Job Scheduled, and so on.
• description—Description of the action, such as Login Succeeded, Logout Succeeded, and
so on.
• jobId—Job ID of the action that was performed.
Configuration Files • name—Name of the configuration file, which is the device serial name with the .conf file
extension
• configFileDeviceName—Name of the device whose configuration file is backed up
• lastestConfigFileVersion—Latest version number of the backup configuration file
• configFileCreationDate—Time when the configuration file was created on the Junos Space
server. It corresponds to the time at which you back up a device configuration for the first
time from the Junos Space server.
• configFileLastUpdatedDate—Time at which the device configuration was last modified
NOTE:
• If you are searching for entries in Junos Space Platform on the basis of the
date or time field, the correct search results are not returned if the comma
(,) or the colon (:) characters are part of the search string.
For example, to search for Nov 10, 2016 6:21:33 AM, enter the following
search string: Nov 10 2016 6 21 33 AM. An exact match is returned if found;
otherwise, merged results that match any of the parts of the search string
are returned. In this example, if an exact match, Nov 10, 2016 6:21:33 AM,
is not found, the search results will return all entries that match any of the
space-separated parts of the search string, for example, Nov 9, 2016 7:37:21
AM, Jun 10, 2016 6:21:14 PM, and Nov 4, 2015, 2:12:45 PM.
• Date and time search works only if both the Junos Space server and the
user executing the search are in the same time zone.
The global search operation also supports query expressions. You can search for phrases
and multiple terms. The default operator for multiple terms is the OR operator.
NOTE:
When you enter a query expression, be aware of the following:
• You must add a back slash “\” if you want to use the following special
characters in the search text:
+ && || ! ( ) { } [ ] ^ “ ~ * ? : \
• Field names are case-sensitive. To search within a specific field, the search
syntax is:
“<Indexed field or column name>:<search text>”
For example, if you have a few systems running on Junos OS 12.3 Release
4.5, then “os: 12.3R4.5” returns search results, whereas “OS: 12.3R4.5” does
not return search results. This is because the field name that is indexed is
“os” and not “OS.” Another example to search for information pertaining
to the Junos EX Series devices is to enter “deviceFamily:junos-ex” in the
Search field.
• If you want to search for a term that includes a space, enclose the term
within double quotation marks.
For example, to search for all devices that are synchronized (that is, In
Sync), enter “In Sync” in the Search field.
• You must append "*" if you want to search using partial keywords.
Otherwise, the search returns 0 (zero) matches or hits.
Table 15 provides examples of query expressions that you can enter in the Search field.
snmp snmp
protocol:snmp AND NOT subject:snmp snmp in the protocol field but not in the subject field
description: “http server”~5 http and server within five positions of one another in the description field
(that is, http and server need to have no more than 5 words in-between
them)
lastmodified:[1/1/2012 TO 12/31/2012] Last modified field values between the dates January 1, 2012 and December
31, 2012
You can use the global search feature of Junos Space Network Management Platform
to find objects within Junos Space Platform.
1. In the Search field, located at the top of the Junos Space Platform UI, type the search
criteria and press Enter. (Alternatively, you can click the magnifying glass icon adjacent
to the Search field.)
If none of the objects in Junos Space Platform match your search criteria, the following
error message is displayed:
No matching results were found. Please enter different search criteria.
If any of the objects match the search criteria, the results appear on the search results
page, which is divided into two areas. The area on the left displays the filters that you
can use to refine your search results, and the area on the right displays the search
results with a short description about each result.
The search criteria that you typed are highlighted in the search results. Each search
result may also provide a URL to help you navigate to the corresponding object on
the inventory landing page.
2. (Optional) Click the URL provided with the search result to navigate to the inventory
landing page of the desired object.
3. (Optional) To filter the search results, select the relevant category or subcategories
displayed on the left of the search results page.
4. (Optional) To view the previous search results, click View Last Search Results. However,
if this is your first search after logging in to Junos Space, then this link is not displayed.
5. To dismiss the search results page or to navigate to the inventory landing page from
which you performed the search, click one of the following:
• The close [X] button on the top-right of the search results panel
You can view all your completed, in-progress, canceled, failed, and scheduled jobs in
Junos Space Network Management Platform. Your jobs include jobs that were triggered
by you as well as jobs that were reassigned to you. The My Jobs icon on the banner of
the Junos Space Platform UI, allows you to quickly access summary and detailed
information about all your jobs, from any workspace and from any task that you are
currently performing.
1. In the banner of the Junos Space Platform UI, click the My Jobs icon located at the top
right.
The My Jobs dialog box appears, displaying your 25 most recent jobs.
• Job ID
• Job name
• Job status
• Date and time—The date and time displayed depends on the status of the job:
• For jobs that are in progress, the date and time at which the job started are
displayed.
• For failed jobs, the date and time when the job failed are displayed.
• For successful jobs, the date and time when the job succeeded are displayed.
• For jobs that are scheduled for later, the date and time at which the job is
scheduled to run are displayed.
The Job Management page appears and displays a list of all your jobs.
3. (Optional) To view the details of a specific job, click the job ID.
The Job Management page appears and displays the details of the selected job in a
dialog box.
After you log in to Junos Space Network Management Platform, you can change your
password using the User Settings icon on the Junos Space banner. You do not require
any particular Junos Space role to change your password.
Starting with Junos Space Platform Release 12.1, Junos Space has implemented a default
standard for passwords that is compliant with the industry standard for security.
NOTE:
• When you upgrade to Junos Space Platform Release 12.1 or later, the default
standard takes effect immediately. All local users receive password
expiration messages the first time they log in to Junos Space after the
update.
• You need to have set your local password to be able to change it. If you do
not have a local password set, you will not be able to set or change it.
• You can use the User Settings icon to change only your local password. The
change does not affect any passwords that an administrator might have
configured for you on a remote authentication server.
1. On the Junos Space Platform UI, click the User Settings icon on the right side of the
Junos Space banner.
NOTE: Mouse over the information icon (small blue i) next to the New
Password text box to view the rules for password creation. For more
information about the password rules, see “Modifying Junos Space Network
Management Platform Settings” on page 1222.
4. In the Confirm Password text box, enter your new password again to confirm it.
NOTE: The fields on the X.509 Certificate tab are applicable when you
want to use certificate-based authentication. If you are using
password-based authentication, you can ignore these fields. For more
information about certificate-based authentication, see the “Certificate
Management Overview” on page 1300 topic in the Junos Space Network
Management Platform Workspaces Feature Guide.
5. (Optional) Select the Manage objects from all assigned domains check box on the
Object Visibility tab to view and manage objects from all the domains that you are
assigned to.
6. Click OK.
You are logged out of the system. To log in to Junos Space again, you must use your
new password. Other sessions logged in with the same username are unaffected until
the next login.
After you complete your administrative tasks in the Junos Space UI, log out to prevent
unauthorized users from accessing Junos Space.
• To log out of Junos Space, click the Log Out icon on the Junos Space application banner.
The logout page appears. A user who is idle and has not performed any action, such as
keystrokes or mouse-clicks, is automatically logged out of Junos Space after a specified
amount of time. This setting conserves server resources and protects the system from
unauthorized access. The default setting is 5 minutes of inactivity. You can change the
setting on the Applications inventory page. Select Administration > Applications > Network
Management Platform > Modify Application Settings (from the Actions menu) > User >
Automatic logout after inactivity (minutes) to modify the automatic logout setting.
To log in to the system again, click the Click here to log in again link on the logout page.
Overview
• Introduction on page 171
Introduction
In Junos Space Network Management Platform, the different tasks that you can perform
are categorized into workspaces. The task tree on the left side of a Junos Space Platform
page is expanded by default and displays the different Junos Space Platform workspaces
and the tasks that you can perform in each workspace.
NOTE: When you log in to Junos Space, the Applications list displays Network
Management Platform by default. You can expand this list to see the installed
Junos Space applications.
You can collapse the task tree to the left by clicking the double left arrow (<<) button
and expand the task tree by clicking the double right arrow (>>) button.
The first item in the task tree is Dashboard, which provides you access to the Junos Space
Platform Dashboard page. After this, the list of the workspaces available in Junos Space
Platform are displayed; these workspaces are described at a high level in Table 5.
NOTE: If you select a Junos Space application from the Applications list, the
task tree for that application is displayed. This topic describes the workspaces
for Junos Space Platform; for the tasks in Junos Space applications, refer to
the documentation for Junos Space applications.
You can expand any workspace by clicking the expansion symbol (+) to the left of its
name. When you do so, the next level of the tasks for that workspace is displayed; some
items at the second level might contain further sub-tasks.
You can expand as many workspaces or tasks as you like; previously-expanded ones
remain open until you collapse them. The design of the task tree enables you to easily
navigate across the different Junos Space Platform workspaces and tasks.
Role Based Access Control Add, manage, and delete users, custom roles,
domains, and remote profiles, and manage user
sessions. For more information, see “Configuring
Users to Manage Objects in Junos Space
Overview” on page 963.
When you log in to Junos Space Network Management Platform, the home page is
displayed. By default, the home page for Junos Space Platform is the Dashboard page.
However, if you previously configured a different page as the home page, then the
configured home page is displayed when you log in.
The Junos Space Platform dashboard, as shown in Figure 37, displays graphs that provide
information about the overall system condition, the fabric load history, the active users
history, and the percentage of jobs in different states. The charts are visible to all users
and are updated in real time.
NOTE: If you do not have user privileges to view detailed data, you might not
be able to view detailed information if you select a gadget.
2. (Optional) To view more information related to the overall system condition, click
Overall System Condition or the indicator needle.
You are taken to the Fabric page, where you can view detailed information about the
nodes in the fabric. For more information, see “Viewing Nodes in the Fabric” on page 1092.
3. (Optional) To view information related to the fabric load, on the Fabric Load History
graph:
• Mouse over a graph data point to view the average CPU usage percentage.
• Click the blue line depicting the CPU usage to view detailed information.
You are taken to the Fabric page, where you can view detailed information about
the CPU, memory, and disk usage for the nodes in the fabric.
4. (Optional) To view information related to the active users, on the Active Users History
graph:
• Mouse over a graph data point to view the total number of active users at that point.
• Click a data point on the graph to view more information about the active users at
that point.
You are taken to the User Accounts page, where the active users are displayed. For
more information, see “Viewing User Statistics” on page 994.
5. (Optional) To view information related to the jobs, on the Job Information graph:
• Mouse over a segment in the pie chart to view the percentage of jobs with a particular
status; for example, cancelled jobs, successful jobs, or failed jobs.
• Click a segment of the pie chart to view details of jobs with status corresponding
to the segment.
You are taken to the Job Management page, where the jobs filtered by the status
are displayed. For more information, see “Viewing Jobs” on page 908.
6. (Optional) You can move any chart displayed on the Dashboard page by clicking
inside the title bar and dragging the chart.
7. (Optional) You can resize any chart displayed on the Dashboard page by hovering
over an edge and clicking and dragging the edge.
Devices
• Device Management on page 179
• Systems of Record on page 195
• Device Discovery Profiles on page 201
• Modeling Devices on page 223
• Device Authentication in Junos Space on page 255
• Viewing Device Inventory on page 273
• Exporting Device Inventory on page 285
• Configuring Juniper Networks Devices on page 295
• Device Adapter on page 339
• Device Configuration Management on page 343
• Adding and Managing Non Juniper Networks Devices on page 353
• Accessing Devices on page 357
• Logical Systems (LSYS) on page 381
• Device Partitions on page 387
• Custom Labels on page 391
• Verifying Template, Image Deployment, Script Execution, and Staged Images on
Devices on page 399
• Device Monitoring on page 405
• Device Maintenance on page 411
Device Management
The Devices workspace in Junos Space Network Management Platform simplifies the
management of devices in your network. You use the device discovery profile or model
device workflows to add multiple devices to the Junos Space Platform database. Then
you can perform the following tasks to manage, configure, and monitor the devices from
the Devices workspace:
• View the connection status and managed status of the managed devices.
• View the operational and administrative status of the physical interfaces of the devices.
• View the hardware inventory of a selected device, such as information about power
supplies, chassis cards, fans, Flexible PIC Concentrators (FPCs), and available PIC
slots.
• View, modify, and deploy the configuration to the devices. For example, deploy a service
order to activate a service on your managed devices.
• View information about the scripts associated with or executed on the devices and
the device images staged on the devices.
• Access the devices from the Junos Space user interface and execute commands on
the devices.
• If the network is the system of record, resynchronize a managed device with the Junos
Space Network Management Platform database so that both the device and the
database contain the same device configuration. (If Junos Space Network Management
Platform is the system of record, this capability is not available.)
• View statistics about the managed devices in your network, including the number of
devices by platform and the number of devices by Junos OS release.
• Managed devices–Managed devices are Juniper Networks devices running Junos OS.
For more information about Juniper Networks devices supported on Junos Space
Platform, refer to “Juniper Networks Devices Supported by Junos Space Network
Management Platform” on page 187.
Juniper Networks devices, such as MX480 and MX960 routers running as aggregation
devices, display the number of satellite devices to which the aggregation device is
connected and the mode of the aggregation device (that is, single-home or multihome).
For more information about inventory and interfaces, see “Device Inventory Overview”
on page 273. For more information about aggregation devices, satellite devices, and
Junos Fusion technology, refer to the Junos Fusion documentation.
• Discovering devices
NOTE: The IP addresses that you input for these tasks either manually or by
using a CSV file are validated on the basis of the format of the IP address.
Table 17 lists the managed status of the device in NSOR and SSOR modes when a
candidate configuration is deployed to a device that supports the confirmed-commit
NETCONF capability. It also lists the status of the job details when the confirmed-commit
operation is a success or failure in these modes.
Table 17: Managed Status in NSOR and SSOR Modes for confirmed-commit
Confirmed-commit and EJB Callback Job Result and
Method Success and Failure Conditions NSOR Mode SSOR Mode Details
The EJB callback method does not return any In Sync Space Changed Failed
value within the confirmed-commit timeout
interval.
The EJB callback method returns True and Out Of Sync followed by In Sync or Space Changed (if Success
the commit is confirmed. resynchronization by Junos new changes are added to the
Space Platform candidate configuration)
The EJB callback method returns False and Out Of Sync followed by Space Changed Failure with the
the configuration is rolled back. resynchronization by Junos failed callback
Space Platform error
The EJB callback method returns False and Out Of Sync followed by Space Changed, Device Failure with
the device is automatically rolled back to the resynchronization by Junos Changed (after Junos Space auto-rollback
currently active configuration. Space Platform Platform receives the system details
log about the auto-rollback
operation on the device)
You can view details of all managed devices in your network, such as the operating
system, platform, IP address, license, and connection status. Device information is
displayed in a table. Unmanaged devices are also shown, but without status and some
other information.
You can also view devices that are in the managed status from the Network Monitoring
workspace, through the Node List (see “Viewing the Node List” on page 753). If the network
is the system of record, you can resynchronize your managed devices with the Junos
Space Platform database (see “Resynchronizing Managed Devices with the Network”
on page 413).
Neither manual nor automatic resynchronization occurs when Junos Space Network
Management Platform is the system of record. See “Systems of Record in Junos Space
Overview” on page 195.
1. On the Network Management Platform UI, select Devices > Device Management.
Table 18 describes the fields displayed on the inventory page. In the table, an asterisk
against a field name indicates that the field is not shown by default.
Name Name of the device as stored in the Junos Space Platform database
Device Alias Value of the Device Alias custom label for the device. By default, this field is not displayed on
the page. (This field is empty if the Device Alias custom label is not added or no value is assigned
to the Device Alias custom label for the device.)
Serial Number Serial number of the device chassis (This field displays Unknown for an unmanaged device.)
Connection Status Connection status of the device in Junos Space Platform. Different values are displayed in
network as system of record (NSOR) and Junos Space as system of record (SSOR) modes.
Managed Status Current status of the managed device in Junos Space Platform:
• Connecting—Junos Space Platform has sent a connection remote procedure call (RPC) and
is waiting for the first connection from the device.
• In Sync—The synchronization operation has completed successfully; Junos Space Platform
and the device are synchronized with each other.
• None—The device is discovered, but Junos Space Platform has not yet sent a connection
RPC.
• Out Of Sync—In NSOR mode, the device has connected to Junos Space Platform, but the
synchronization operation has not been initiated, or an out-of-band configuration change
on the device was detected and auto-resynchronization is disabled or has not yet started.
• Device Changed—In SSOR mode, there are changes made to the device configuration from
the device CLI.
• Space Changed—In SSOR mode, there are changes made to the device configuration from
Junos Space Platform.
• Space & Device Changed—In SSOR mode, there are changes made to the device configuration
from the device CLI and Junos Space Platform. Neither automatic nor manual
resynchronization is available.
• Synchronizing—The synchronization operation has started as a result of device discovery, a
manual resynchronization operation, or an automatic resynchronization operation.
• Sync Failed—The synchronization operation failed.
• Unmanaged—The device is unmanaged.
• Modeled—The device is modeled.
• Waiting for deployment—The modeled device is unreachable and needs to be activated.
Platform Model number of the device (For an unmanaged device, the platform details are discovered
through SNMP. If the platform details cannot be discovered, the field displays Unknown.)
OS Version Operating system firmware version running on the device (This field displays Unknown for an
unmanaged device.)
Schema Version DMI schema version that Junos Space Platform uses for this device (This field displays Unknown
for an unmanaged device.) See “DMI Schema Management Overview” on page 1403.
Physical Interfaces Link to the view of physical interfaces for the device (The field displays NA for an unmanaged
device.)
Logical Interfaces Link to the view of logical interfaces for the device (The field displays NA for an unmanaged
device.)
Device Family Device family of the selected device (For an unmanaged device, this is the same as the vendor
name you provided. The field displays Unknown if no vendor name was provided and if SNMP
is not used or has failed.)
Last Rebooted Time Date and time when the device was last rebooted manually (that is, the device status changes
from Down to Up) or from Junos Space Platform
Vendor Name of the device vendor (For an unmanaged device, the field displays Unknown if the vendor
name was not provided and cannot be discovered through SNMP.)
Connection Type • Reachable Device initiated—This is a device-initiated connection from an internal device
(without a NAT server to route the connection) and the device is reachable.
• Reachable Device initiated–External—This is a device-initiated connection from an external
device (NAT server routes the connection) and the device is reachable.
• Junos Space initiated—This is a connection initiated by Junos Space to an internal device
(without a NAT server to route the connection).
• Junos Space initiated–External—This is a connection initiated by Junos Space to an external
device (NAT server routes the connection) and the device is reachable.
• Modeled—This is a device-initiated connection and the device is unreachable.
Device Network Whether the device is connected to Junos Space Platform through a NAT server
• Internal—The device is connected to Junos Space Platform directly—that is, without a NAT
server
• External—The NAT server routes the connection to Junos Space Platfom
2. (Optional) Sort the table by mousing over the column head for the data that you want
to sort and clicking the down arrow. Select Sort Ascending or Sort Descending.
3. (Optional) Show columns not in the default tabular view, or hide columns, as follows:
a. Mouse over any column head and click the down arrow.
c. Select the check boxes against the columns that you want to view. Clear the check
boxes against the columns that you want to hide.
• To restrict the display of devices, enter search criteria of one or more characters in
the Search field and press Enter.
All devices that match the search criteria are shown in the main display area.
• To view hardware inventory for a device, select the row against the device and select
Device Inventory > View Physical Inventory from the Actions menu. Alternatively,
right-click the device name and select Device Inventory > View Physical Inventory.
• To view the physical or logical interfaces of a device, click the View link in the
appropriate column and row for the device.
To view the physical or logical interfaces of more than one device, select the required
devices, right-click and select Device Inventory > View Logical Interfaces.
The View Logical Interfaces page displays the list of logical interfaces of the selected
devices.
Table 19 lists all the Juniper Networks product series and devices supported by Junos
Space Network Management Platform. The Junos Space Platform release notes lists
only the new devices that are supported with that release.
ACX1000
ACX1100
ACX2000
ACX2100
ACX2200
ACX4000
ACX5000
ACX5048
ACX5096
BX Series BX7000
EX Series EX2200
EX2300
EX3200
EX3300
EX3400
EX4200
EX4200-Copper
EX4300
EX4500
EX4550
EX4550-40G
EX4600
EX6200
EX6210
EX8208
EX8216
EX9200
EX9204
EX9208
EX9214
EX4200-VC
EX4300-VC
EX4500-VC
EX4550-VC
MIXED-MODE-EX-VC
EX-XRE
J Series J2320
J2350
J4350
J6350
LN Series LN1000
LN2600
M Series M7i
M10i
M40e
M120
M320
MX Series MX5
MX10
MX80
MX104
MX240
MX480
MX960
MX2008
MX2010
MX2020
PTX3000
PTX5000
QFX3000-G
QFX3000-M
QFX3500
QFX3600
QFX5100
QFX5110-32Q
QFX5110-48S
QFX5100-96S
QFX5200
QFX5200-32C-R
QFX10002-36Q
QFX10002-36Q-DC
QFX10002-72Q
QFX10002-72Q-DC
QFX10008
QFX10016
SRX110H-VB
SRX210
SRX220
SRX240
SRX300
SRX320
SRX320-PoE
SRX340
SRX345
SRX550
SRX550-M
SRX650
SRX1400
SRX1500
SRX3400
SRX3600
SRX4100
SRX4200
SRX4600
SRX5000
SRX5400
SRX5600
SRX5800
X45-Major 3 - SW
X44-D10-Minor-SW
T Series T320
T640
T1600
T4000
TX Matrix
TX Matrix Plus
TXP-3D
Device tags help you easily identify managed devices when deploying a device template,
upgrading a device image, staging scripts, or applying CLI Configlets to devices. Device
tags associate the IP address or hostname of a managed device with a tag.
Starting with Junos Space Network Management Platform Release 15.2R1, you can upload
device tags from the local computer to Junos Space Network Management Platform.
You use the Devices workspace to upload device tags by using a CSV file. You can assign
the tags created using this task to other Junos Space objects. For more information, refer
to “Tagging an Object” on page 1394.
NOTE: You must create a CSV file with the correct IP address or hostname
of a device, tag name, and tag type, which could be private or public. If you
do not specify whether the tag is private or public, by default a public tag is
created.
Tag names must not exceed 255 characters. Tag names must not start with
a space, and cannot contain a comma, double quotation marks, and
parentheses. Also, you cannot name a tag “Untagged” because it is a reserved
term.
1. On the Junos Space Network Management Platform user interface, select Devices >
Device Management.
The Device Management page that appears displays all devices managed by Junos
Space Platform.
3. (Optional) To view a sample CSV file, click the Sample CSV hyperlink.
4. Click Browse to select the CSV file from the local computer.
5. Click Import.
The details of the devices and tags are uploaded to Junos Space Platform. A Job
Information dialog box is displayed.
a. Click OK.
You are redirected to the Job Management page with the filtered view of the job.
When the job is complete, all devices with correct details are assigned the tags you
uploaded through the CSV file. To view the tags, go to Administration > Tags.
15.2R1 Starting with Junos Space Network Management Platform Release 15.2R1,
you can upload device tags from the local computer to Junos Space Network
Management Platform.
• Exporting Tags from Junos Space Network Management Platform on page 1400
You can filter the devices on the Device Management page using a CSV file.
1. On the Junos Space Network Management Platform user interface, select Devices
>Device Management.
3. (Optional) To view a sample CSV file, click the Sample CSV hyperlink.
4. Click Browse and select the CSV file from the local computer.
5. Click Import.
If the CSV file is imported successfully, the Device Management page is filtered and
lists only those devices whose host names were listed in the CSV file.
Systems of Record
Although by default the Junos Space network you are administering is the system of
record (SOR)—each device defines its own official state—you may prefer to have the
Junos Space Network Management Platform database contain the official state of the
network, enabling you to restore that official state if unwanted out-of-band changes are
made to a device. This feature enables you to designate Junos Space Network
Management Platform as the SOR if you prefer.
Systems of Record
A network managed by Junos Space Network Management Platform contains two
repositories of information about the devices in the network: the devices themselves
(each device defines and reports its official state) and the Junos Space Network
Management Platform database (which contains information that is reported by the
device during device discovery). One of these repositories must have precedence over
the other as the accepted desirable state. By default, the network itself is the system of
record (NSOR).
In NSOR, when a local user commits a change in the configuration of a network device,
the commit operation triggers a report via system log to Junos Space Network
Management Platform. The values in the Junos Space Network Management Platform
database are automatically changed to match the new device values, and the timestamps
are synchronized. Thus the devices control the contents of the database.
As of version 12.2, you can designate the Junos Space Network Management Platform
database values as having precedence over any values configured locally at a device. In
this scenario, Junos Space Network Management Platform (database) is the system of
record (SSOR). It contains the configurations that the Junos Space administrator considers
best for the network devices. If an out-of-band commit operation is executed on a network
device, Junos Space Network Management Platform receives a system log message, but
the values in the Junos Space Network Management Platform database are not
automatically changed or synchronized. Instead, the administrator can choose whether
or not to overwrite the device's local changes by pushing the accepted configuration to
the device from the Junos Space Network Management Platform database.
The choice of pushing the Junos Space Network Management Platform configuration is
left to the administrator because the local device changes may, for example, be part of
a temporary test that the administrator would not want to interrupt. However, if the
tester forgets to reset the configuration at the end of the test, the administrator might
then push the SSOR configuration to the device.
Setting the Junos Space Network Management Platform database as the system of
record does not protect your network from local changes. The device notifies Junos Space
Network Management Platform via system log when the changes occur, and it does not
resynchronize, so you still have the previous configuration and you can reset the remote
device quickly if you need to do so. In an NSOR scenario, Junos Space Network
Management Platform is also notified via system log. You can still push a more desirable
configuration to the device, but this process is less efficient.
When configuration changes are made on a physical device that Junos Space Network
Management Platform manages, Junos Space Platform reacts differently depending on
whether the network itself is the system of record (NSOR) or Junos Space Platform is
the system of record (SSOR).
In the NSOR case, Junos Space Platform receives a system log message from the modified
device and automatically resynchronizes the configuration values in its database with
those of the device. This ensures that the device inventory information in the Junos Space
Platform database matches the current configuration information on the device.
In the SSOR case, the Junos Space Platform receives a system log message from the
modified device. The Managed Status of that device changes from In Sync to Device
Changed (if the changes are made from the device CLI), Space Changed (if the changes
are made from Junos Space Platform), or Space & Device Changed (if the changes are
made both from the device CLI and Junos Space Platform), but no resynchronization
occurs. The Junos Space Platform administrator can choose whether or not to reset the
device’s configuration to match the configuration values in the Junos Space Platform
database.
You can change the default value of 20 seconds to any other duration by specifying the
value in seconds in the Administration > Applications > Network Management Platform >
Modify Application Settings > Device > Max auto resync waiting time secs field. For example,
if you set the value of this field to 120 seconds, then Junos Space Platform automatically
schedules a resynchronization job to run 120 seconds after the first commit operation is
received. If Junos Space Platform receives any other commit notification within these
120 seconds, it resynchronizes both commit operations in one job.
For information about setting the damper interval to change the resynchronization time
delay and information about disabling the auto-resynchronization feature, see “Modifying
Settings of Junos Space Applications” on page 1221.
When Junos Space Platform receives the device commit notification, the Managed Status
is Out of Sync. When the resynchronization job begins on the device, the Managed Status
of the device changes to Synchronizing and then In Sync after the resynchronization job
has completed, unless a pending device commit operation causes the device to display
Out of Sync while it was synchronizing.
NOTE: You can view the auto-resynchronization jobs that were scheduled
to execute before upgrading to Junos Space Platform Release 15.1R1, from
the Job Management page.
You use the device discovery profile to add devices to Junos Space Network Management
Platform from the Devices workspace. Discovery is the process of finding a device and
then synchronizing the device inventory and configuration with the Junos Space Network
Management Platform database. To use device discovery, you must be able to connect
Junos Space Network Management Platform to the device.
A device discovery profile contains preferences used to discover devices, such as discovery
targets, probes used to discover devices, mode and details for authentication, SSH
fingerprints of devices, and the schedule to use this discovery profile. You can start the
discovery process using a discovery profile in the following ways: scheduling a discovery
after creating a discovery profile, or selecting a discovery profile and clicking Run Now.
Executing or running a discovery profile discovers, authenticates, and manages the device
on Junos Space Network Management Platform. With appropriate privileges for
discovering devices, you can create multiple discovery profiles with different combinations
of targets, probes, and authentication modes on your Junos Space setup. You can clone,
modify, and delete the device discovery profiles from Junos Space Network Management
Platform. You can also choose whether to share device discovery profiles with other
users with device discovery permissions.
To discover network devices using a device discovery profile, Junos Space Network
Management Platform uses the SSH, ICMP Ping, and SNMP protocols. When the device
is discovered, device authentication is handled through the administrator login SSH v2
credentials and SNMP v1, SNMP v2c, or SNMP v3 settings, keys generated from Junos
Space Network Management Platform (RSA, DSS, or ECDSA keys), or custom keys. You
can optionally enter the SSH fingerprint for each device and let Junos Space Network
Management Platform save the fingerprint in the database during the discovery process
and validate the fingerprint when the device connects to Junos Space Network
Management Platform. Fingerprint validation is available only for SSH-enabled Juniper
Networks devices and not for ww Junos OS devices and modeled devices. For more
information about device authentication in Junos Space, see “Device Authentication in
Junos Space Overview” on page 255.
For device targets, you can specify a single IP address, a DNS hostname, an IP range, or
an IP subnet to discover devices on a network. When a device discovery profile is executed
or run (either instantly or based on a schedule), Junos Space Network Management
Platform connects to the physical device and retrieves the running configuration and the
status information of the device. To connect with and configure devices, Junos Space
Network Management Platform uses the Device Management Interface (DMI) of Juniper
Networks devices, which is an extension of the NETCONF network configuration protocol.
If a device-initiated connection to Junos Space is enabled, the DMI channel and port
7804 are used and the following (sample) configuration is added on the device to
establish the connection to Junos Space:
To discover and manage devices through a device-initiated connection, clear the Junos
Space initiated connection to device check box on the Modify Application Settings page
in the Administration workspace. For information about configuring connections initiated
by Junos Space by a device, see “Modifying Junos Space Network Management Platform
Settings” on page 1222.
You can configure a NAT server to route connections between the Junos Space setup
and managed devices. Both device-initiated connections to a Junos Space setup and
connections initiated by Junos Space to managed devices, when the Junos Space setup
is behind the NAT server, are supported on Junos Space Network Management Platform.
If a NAT server is used, the managed devices connect to Junos Space Network
Management Platform through the IP address of Junos Space Network Management
Platform translated by NAT. For more information about using a NAT server on a Junos
Space setup, see “NAT Configuration for Junos Space Network Management Platform
Overview” on page 1174.
If the network is the system of record (NSOR), when configuration changes are made on
the physical device (out-of-band CLI commits and change-request updates), Junos
Space Network Management Platform automatically resynchronizes with the device so
that the device inventory information in the Junos Space Network Management Platform
database matches the current device inventory and configuration information. If Junos
Space Network Management Platform is the system of record (SSOR), this
resynchronization does not occur and the database is unchanged.
• Physical Inventory—Chassis, FPM board, power entry module (PEM), Routing Engine,
Control Board (CB), Flexible PIC Concentrator (FPC), CPU, PIC, transceiver, fan tray
Junos Space Network Management Platform displays the model number, part number,
serial number, and description for each inventory component, when applicable.
• License information:
• Loopback interface
Other device configuration data is stored in the Junos Space Network Management
Platform database as binary large objects and is available only to northbound interface
(NBI) users.
16.1R1 You use the device discovery profile to add devices to Junos Space Network
Management Platform from the Devices workspace.
You create a device discovery profile to create a set of preferences for device targets,
probes, authentication mode and credentials, SSH fingerprints, and the schedule to
discover devices to Junos Space Network Management Platform. In addition to scheduling
the discovery, you can manually start the discovery process by running the device discovery
profile. For more information, see “Running Device Discovery Profiles” on page 215.
NOTE: To discover a device with dual Routing Engines, always specify the
IP address of the current primary Routing Engine. When the current primary
IP address is specified, Junos Space Network Management Platform manages
the device and the redundancy. If the primary Routing Engine fails, the backup
Routing Engine takes over and Junos Space Network Management Platform
manages the transition automatically without bringing down the device.
NOTE: When you initiate discovery on a device running Junos OS, Junos Space
Network Management Platform automatically enables the NETCONF protocol
over SSH by pushing the following command to the device:
To specify the device targets that you want Junos Space Network Management Platform
to discover:
1. On the Junos Space Network Management Platform user interface, select Devices >
Device Discovery > Device Discovery Profiles.
The Device Discovery Target page is displayed on the left. The list of different tasks
that should be completed to create a profile is displayed on the right: Device Discovery
Target, Specify Probes, Specify Credentials, Specify Device FingerPrint, and
Schedule/Recurrence.
NOTE: At any point in time, you can click the links to the different tasks
(on the right of the page) and navigate to those pages.
3. In the Discovery Profile Name field, enter the name of the device discovery profile.
The device discovery profile name cannot exceed 255 characters and can contain
letters, numbers, spaces, and special characters. The special characters allowed are
period (.), hyphen (-), and underscore (_). The device discovery profile name cannot
start with letters or numbers and cannot contain leading or trailing spaces.
NOTE: The Make Public check box is selected by default so that the device
discovery profile is visible to all users.
4. In the Discovery Parameters field, you can add devices manually by specifying the
details on the Device Discovery Target page or by uploading the details of the devices
through a CSV file.
b. In the Target Type area, select how you want to specify the targets: IP addresses
or hostnames, IP ranges, or a subnet.
NOTE: You can enter the IP address in either IPv4 or IPv6 format.
Refer to
http://www.iana.org/assignments/ipv4-address-space/ipv4-address-space.xhtml
for the list of restricted IPv4 addresses and
http://www.iana.org/assignments/ipv6-address-space/ipv6-address-space.xhtml
for the list of restricted IPv6 addresses.
• IP addresses
• Hostnames
• Subnet expressions