Network Application Platform

The Junos Space Network Application Platform provides the essential tools the network administrator needs for automating network operations, including device discovery and management, job operation management, audit logging, and network administration. Network administration tasks include managing the Junos Space fabric (comprising one or more IP-connected nodes), database, software upgrades, licenses, installed applications, and troubleshooting.

New Features

The Junos Space Network Application Platform includes the following new features:

• Audit logging— View audit logs to monitor user login activity and track tasks initiated from Network Application Platform, Ethernet Activator, and Campus Builder. To manage log volume over time, you can archive log files and then purge log files from the Junos Space database. Audit logs can be archived on a local server or remote network host or media.
• My Jobs—View all your scheduled jobs from any work space while performing any task in Junos Space, and quickly access summary and detailed job information. You can also clear jobs from My Jobs when jobs are no longer of interest to you.
• Secure Console—Establish a connection to a device directly from the Junos Space user interface using Secure Console. Secure Console uses the SSH protocol to provide a secure remote access connection to managed and unmanaged devices. After you connect to a device, you can enter CLI commands from the terminal window to monitor or troubleshoot the device.

Resolved Issues

The following issues have been resolved since the Junos Space 1.1 release:

• After uploading the new image, the Manage Software inventory page does not appear automatically. You must select it manually. [PR/495783]
• When two large discovery jobs are running at the same time or scheduled to run close to each other, the later job might report some devices failed to be managed with the following message: “Timeout while waiting for device to connect back or to be saved”. These devices are actually added into the system. They are up and their configuration status is “Out of Sync”. As a workaround, after all discovery jobs finish, resynchronize these “Out of Sync” devices. [PR/495732]
• When restoring the database, the corresponding Backup Database job state will be displayed as “Failure” [PR/477765]
• Clicking the Active Users History chart takes you to the Number of Users by Assigned Role chart. [PR/495713]
• The active user count in the System Health panel could drop after cluster node reboot, although all the users remain connected. In the System Health panel on the system dashboard, the Active Users History chart indicates how many users are currently active in the Junos Space cluster. If a cluster node shuts down, some user sessions could be closed and switch to the remaining running cluster node. However, closing user sessions on the failed node reduces the active user count. The user count could drop to zero if all the user sessions were active on the node which is rebooted. As a workaround, if all users log out and log in again, the active user count will become correct. [PR/495713]
• When two large discovery jobs are running at the same time or scheduled to run close to each other, the later job might report some devices failed to be managed with the following message: “Timeout while waiting for device to connect back or to be saved”. These devices are actually added into the system. They are up and their configuration status is “Out of Sync”. As a workaround, after all discovery jobs finish, resynchronize these “Out of Sync” devices. [PR/495732]
• If a bulk device delete operation takes more than 5 minutes, the delete dialog box in the user interface will persist after job completion. You must cancel the dialog box manually. We recommend you do not perform cancel while the delete operation is in progress. To determine the status of the delete job, check the device count at the bottom of the inventory page. PR/495735]
• If a bulk device delete operation takes more than 5 minutes, the delete dialog box in the user interface will persist after job completion. You must cancel the dialog box manually. We recommend you do not perform cancel while the delete operation is in progress. To determine the status of the delete job, check the device count at the bottom of the inventory page. PR/495735]
• MAC security settings are not pushed to the device during deployment.
• After starting discovery, the status graph might remain blank for about 4 or 5 seconds.
• The Junos Space Appliance Settings menu might erroneously display the Expand VM drive size option for a physical appliance. This option should appear only for the virtual appliance.
• The “Percent Complete” column in the table view of the Manage Jobs inventory page might not display the “Percentage of job execution completed” for intermediate states.

Known Issues

The Junos Space 1.2 release includes the following known issues:

• If one of the nodes in a Fabric goes down, web UI sessions connected to that node might not refresh automatically. As a workaround, perform a manual refresh. To restart automatic refresh, log out of the UI session and log back in. [PR/493159]

Operational Recommendations

The Junos Space 1.2 release includes the following operational recommendations:

• If you are running Mozilla Firefox, and you change the time zone on your client PC, you must refresh your browser to reflect the correct time zone.
• During device discovery operations, if the Ping option is selected, Junos Space uses the TCP echo utility to verify that the devices being discovered are reachable. This operation requires that TCP port 7 is open and accessible. If access to port 7 is restricted, you can uncheck the Ping option, and run discovery again. In addition, some Juniper firewall devices might block traffic to port 7 during the discovery operation. To allow traffic to port 7, use the following command:

  set security zones security-zone trust host-inbound-traffic system-services all

• For information about changing the Junos Space maintenance mode password, refer to the Juniper Networks Knowledge Base:
  http://kb.juniper.net/kb16853