Juniper Networks, Junos, Steel-Belted Radius, NetScreen, and ScreenOS are registered trademarks of Juniper Networks, Inc. in the United
States and other countries. The Juniper Networks Logo, the Junos logo, and JunosE are trademarks of Juniper Networks, Inc. All other
trademarks, service marks, registered trademarks, or registered service marks are the property of their respective owners.
Juniper Networks assumes no responsibility for any inaccuracies in this document. Juniper Networks reserves the right to change, modify,
transfer, or otherwise revise this publication without notice.
Products made or sold by Juniper Networks or components thereof might be covered by one or more of the following patents that are
owned by or licensed to Juniper Networks: U.S. Patent Nos. 5,473,599, 5,905,725, 5,909,440, 6,192,051, 6,333,650, 6,359,479, 6,406,312,
6,429,706, 6,459,579, 6,493,347, 6,538,518, 6,538,899, 6,552,918, 6,567,902, 6,578,186, and 6,590,785.
Revision History
December 2012— Juniper Networks Junos Space JA1500 Appliance, Release 12.3
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. The Junos OS has no known time-related limitations through
the year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions
Junos Space Documentation and Release Notes on page xi
•
Documentation Conventions on page xi
•
Documentation Feedback on page xii
•
Requesting Technical Support on page xii
Junos Space Documentation and Release Notes
For a list of related Junos Space documentation, see http://www.juniper.net/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the Junos Space Release Notes.
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
Juniper Networks supports a technical book program to publish books by Juniper Networks
engineers and subject matter experts with book publishers around the world. These
books go beyond the technical documentation to explore the nuances of network
architecture, deployment, and administration using the Junos operating system (Junos
OS) and Juniper Networks devices. In addition, the Juniper Networks Technical Library,
published in conjunction with O'Reilly Media, explores improving network security,
reliability, and availability using Junos OS configuration techniques. All the books are for
sale at technical bookstores and book outlets around the world. The current list can be
viewed at http://www.juniper.net/books .
Documentation Conventions
Table 1 on page xii defines the notice icons used in this guide.
Indicates important features or instructions.Informational note
Indicates a situation that might result in loss of data or hardware damage.Caution
Alerts you to the risk of personal injury or death.Warning
Alerts you to the risk of personal injury from a laser.Laser warning
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can send your comments to
techpubs-comments@juniper.net, or fill out the documentation feedback form at
https://www.juniper.net/cgi-bin/docbugreport/ . If you are using e-mail, be sure to include
the following information with your comments:
•
Document or topic name
•
URL or page number
•
Software release version (if applicable)
Requesting Technical Support
Technical product support is availablethrough the Juniper Networks TechnicalAssistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.
•
JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer Support Center (CSC) that provides you with the
following features:
Find solutions and answer questions using our Knowledge Base: http://kb.juniper.net/
•
Download the latest versions of software and review release notes:
http://www.juniper.net/customers/csc/software/
•
Search technical bulletins for relevant hardware and software notifications:
https://www.juniper.net/alerts/
•
Join and participate in the Juniper Networks Community Forum:
http://www.juniper.net/company/communities/
About the Documentation
•
Open a case online in the CSC Case Management tool: http://www.juniper.net/cm/
To verify service entitlement by product serial number, use our Serial Number Entitlement
(SNE) Tool: https://tools.juniper.net/SerialNumberEntitlementSearch/
Opening a Case with JTAC
You can open a case with JTAC on the Web or by telephone.
•
Use the Case Management tool in the CSC at http://www.juniper.net/cm/.
•
Call 1-888-314-JTAC (1-888-314-5822 toll-free in the USA, Canada, and Mexico).
For international or direct-dial options in countries without toll-free numbers, see
Parts of the Junos Space JA1500 Appliance on page 4
•
Understanding How Nodes Are Connected in a Fabric on page 8
•
NTP Time Source For Each JA1500 Appliance on page 9
•
Fabric Management Overview on page 9
Junos Space JA1500 Appliance Overview
The Junos Space JA1500 appliance is a Juniper Networks, dedicated, physical, hardware
device that is engineered to provide the computing power and specific requirements
needed to install and run the Junos Space application. The JA1500 appliance all-in-one
design makes the Junos Space application deployment simpler by giving administrators
a turnkey solution. You can power up a the JA1500 appliance, make required configuration
changes, then start using the Junos Space application without concerning yourself with
hardware and OS and application installation. (See Figure 1 on page 3).
Figure 1: Junos Space JA1500 Appliance
The JA1500 appliance allows administrators to migrate from a strategy of one large
server in the corner, to distribute multiple servers based on load and geography. You can
combine Junos Space appliances in clusters for high availability or increased throughput.
The JA1500 appliance ensures that consistent infrastructure is deployed across an
organization, reducing complexity. The JA1500 appliance means that only one
vendor—Juniper Networks—supports integrated components reducing complexity.
The administrator can also deploy and run the Junos Space application as a virtual
appliance. The administrator can combine Junos Space appliances in clusters for high
availabilityor increased throughput. The administratorcan create a fabric of Junos Space
appliances, Junos Space virtual appliances, or a combination of both appliances and
virtual appliances.
The Junos Space application, running on a JA1500 appliance, is a comprehensive platform
for building and deploying applications for collaboration, productivity, and network
infrastructure and operations management. The Junos Space application provides a
runtime environment implemented as a fabric of virtual and physical appliances.
The Junos Space Network Application Platform (Platform) provides effective tools for
automating network operations, including device discovery and management, topology
visualization, device image deployment, job management, audit logging, user
administration,and systemadministration.Systemadministration tasks include managing
the Junos Space fabric which comprises one or more IP-connected nodes, database,
licenses, applications, troubleshooting, and tagging.
Junos Space applications:
•
Allowservice providers deliver secure connectivity services (SCS) over an MPLS network
to their customers.
•
Automatically detect problems on Juniper Networks devices running Junos and scripts
and proactively collects the troubleshooting information needed to diagnose and fix
the issue. Service Now allows operational personnel to open technical support cases
with JTAC. JTAC resolves cases and provides the customer proactive information to
minimize future problems.
•
Allow network engineers to provide enterprise services like break, fix, and truck roll of
networking gear and to quickly deploy networking gear in large number of branch
offices accurately and easily.
•
Allow security designers to design and provision the security aspect of the network
and enable large enterprise customers to rapidly deploy firewalls and VPNs.
Other proprietary, OEM, and third-party application will be developed in subsequent
Junos Space releases.
The Junos Space Platform > Administration > Manage Application workspace allows
the administrator add, upgrade, and delete applications.
Related
Parts of the Junos Space JA1500 Appliance on page 4•
Documentation
Parts of the Junos Space JA1500 Appliance
The dimensions of the Junos Space JA1500 appliance are 17.72inx 17.26in x 3.5in (450mm
x 438.4mm x 88mm). Its front panel, rear panel, and LEDs are described in the sections
that follow.
JA1500 Appliance Front Panel
Figure 2 on page 5 shows the front panel of the JA1500 appliance.
Chapter 1: Overview of the Junos Space JA1500 Appliance
Figure 2: JA1500 Appliance Front Panel
•
Mounting Brackets on page 5
•
Chassis on page 5
•
Hard Disks on page 5
•
Ports on page 6
•
RAID Controller on page 6
•
Status LEDs on page 6
Mounting Brackets
The JA1500 appliance includes front ears, rear mounting rails for mounting in a 4-post
standard rack, and midpoint brackets for mounting in a 2-post, 19-inch equipment rack.
Chassis
The JA1500 appliance has a 2U rack-mountable chassis. The chassis includes the
following:
•
Three 1TB hard disks in hot-swappable RAID 5 array
•
One RAID controller
•
Four RJ-45 10/100/1000 Gigabit Ethernet ports
•
One RJ-45 serial console port
•
One USB interface
•
Optional single IOC slot available for I/O card expansion
•
One 250-watt cold-swappable power supply with an AC power receptacle; 1 optional
dual-redundant, hot-swappable power supply
•
One AC power switch
•
Two cooling fans
Hard Disks
The JA1500 appliance includes three hard disk drives in RAID 5 array. The serial attached
SCSI (SAS), hot-swappable drives are externally accessible in field-replaceable trays,
providing component high availablilty. If one drive fails, the system recovers by
hot-swapping the failed drive, which is automatically rebuilt. The disks are labeled from
left to right Disk 0 , Disk 1, Disk 2. Front panel LEDs indicate drive activity and failure.
Ports
The JA1500 Appliance includes the following ports:
•
Four RJ-45 10/100/1000 Mbps network ports using an Intel Gigabit Ethernet controller.
The ports are numbered from left to right: ETH3, ETH2, ETH1, ETH0.
•
One RJ-45 serial console port labeled CONSOLE.
•
One USB interface
•
One optional single input/output card (IOC) slot available for expansion I/O ports. The
JA1500 ships with a dummy tray that can be replaced with an upgrade I/O card.
RAID Controller
The JA1500 appliance RAID controller manages the physical disk drives and presents
them to the computer as logical units.
Status LEDs
The JA1500 Appliance LEDs are shown in Figure 3 on page 6.
Figure 3: JA1500 Appliance LEDs
The JA1500 chassis LEDs are described in Table 2 on page 6.
Table 2: JA1500 Appliance Front Panel LEDs
DescriptionLEDs
•
Chassis Status LEDs
Power LED (green)—Indicates that the appliance is powered on
•
Hard Disk Activity LED (yellow)—Indicates the hard disk is in use
(writing or reading data)
•
Hardware Fault (red)—Indicates that a fan, power supply, or
temperature alarm has occurred
Chapter 1: Overview of the Junos Space JA1500 Appliance
Table 2: JA1500 Appliance Front Panel LEDs (continued)
DescriptionLEDs
•
Ethernet Ports and LEDs
Hard Disk Activity/Failure
LEDs
Figure 4 on page 7 shows the rear panel of the JA1500 appliance.
Left Ethernet Port LED (green)—Indicates link and activity
•
On—indicates the link
•
Blinking—indicates activity
•
Right Ethernet Port LED—Indicates the link speed
•
Off—10 Mbps
•
Green—100 Mbps
•
Yellow–1000 Mbps or 1 Gbps
•
LED 1 on left (green)—When lit, indicates disk activity
•
LED 2 on right (red)—When lit, indicates disk failure
Figure 4: Parts of the JA1500 Rear Panel
•
Cooling System on page 7
•
AC Power Switch on page 7
•
Power Supply on page 7
Cooling System
The JA1500 appliance includes two rear-accessible, hot-swappable fans to cool the
other components.
AC Power Switch
The AC power switch is between the fans on the left and the power supplies on the right.
Power Supply
The JA1500 appliance includes a cold-swappable, 250 W (90 to 264 V) autoranging
power supply for all countries. The power supply is high efficiency and is 80 PLUS certified.
The power supply includes an AC receptacle for a power cord. The JA1500 appliance is
upgradable to a redundant hot-swappable dual power supply. The power supplies are
numbered from bottom to top: PSU1, PSU2.
If the JA1500 appliance includes two power supplies, plug each power cord into a separate
power circuit to ensure that the device continues to receive power if one of the power
circuits fails.
Related
Junos Space JA1500 Appliance Overview on page 3•
Documentation
Understanding How Nodes Are Connected in a Fabric
Each Junos Space appliance (physical or virtual) that you install and configure is
represented as a single node in the fabric. You can add nodes without disrupting the
services that are running on the fabric. When you install and configure the first appliance,
Junos Space automatically creates a fabric with one node. For each additional appliance
you install and configure, you must add a node to logically represent the appliance in the
fabric. Youadd nodes to the fabric from the Administration workspace in the Junos Space
user interface. Each node that you add to the fabric increases the resource pool for the
node functions to meet the scalability and availability requirements of your network. By
default, Junos Space automatically enables node functionality across the nodes in the
fabric to distribute workload.The nodes in the fabric work together to provide a virtualized
resource pool for each of the node functions: load balancer, database, and application
logic.
In a fabric comprising two or more nodes, Junos Space provides failover when a node
functioning as the active server (load balancer server or database server) goes down. By
default, Junos Space marks a particular node down and routes failover requests to the
node that Junos Space designates as standby server. Junos Space uses a heartbeat
mechanism to check whether the nodes in the fabric are running. When a node functioning
as the active server fails (the appliance crashes or stops sending heartbeats), the node
functioning as the standby server takes over all resources that were managed by the
node functioning as active server. Nodes in a Junos Space fabric rely on IP multicast
messagesto discover each other, thereforeensure that IP multicast packets are reachable
among all nodes in the Junos Space fabric.
Related
Documentation
To add, manage, and monitor the nodes in the fabric, a Junos Space user connects to a
single Web IP address. The IP address of first (active) node and second (standby) node,
and the Web (virtual) IP address must all be in the same subnet. The Web IP address
must work on both the first and second node in the fabric. When both nodes are in same
subnet, and the first (active) node goes down, the second (standby) node becomes the
active node and packets continue to be directed from the router to the Junos Space Web
IP address, and then to the second node. However, if the second (standby) node is
configuredin a different subnet from the first (active) node, and the first node goes down,
the second node becomes the active node, but because the Web IP address now points
to a different subnet address, packets originally destined for first node will not be received
by the second node.
To ensure consistent behavior among all nodes in a multinode fabric, each node’s time
must be synchronized with every other node in the fabric. When you configure each Junos
Space JA1500 appliance with an NTP server, you ensure that, if the first node (which is
used to synchronize time for all nodes in the fabric) goes down, all other nodes in the
fabric remain synchronized. To ensure this behavior, all nodes in a fabric must use the
same external NTP source that you configure for the first appliance.
NOTE: By default, Junos Space translates time so that the time displayed in
the user interface corresponds to Junos Space server time, but is mapped to
the local time zone of your client computer.
The default system clock for a JA1500 appliance may not be precise enough for some
networks. To ensure time synchronization across all nodes in the fabric, Juniper strongly
recommends that you use the following guidelines:
Chapter 1: Overview of the Junos Space JA1500 Appliance
•
Add an NTP server to the first virtual appliance during initial setup.
•
For each additional appliance, add the same NTP server that you specified for the first
appliance.
Related
Documentation
Fabric Management Overview on page 9•
• Understanding How Nodes Are Connected in a Fabric on page 8
• Managing Nodes in the Fabric
Fabric Management Overview
You can deploy Junos Space appliances to create a fabric that provides the scalability
and availability that your managed network requires as you add more devices, services,
and users.
A Junos Space fabric comprises one or more IP-connected nodes. A node is a logical
object that represents a single Junos Space JA1500 appliance or Junos Space virtual
appliance, its operating system, and the Junos Space software that runs on the operating
system. Each Junos Space appliance or virtual appliance that you install and configure
is represented as a single node in the fabric. You can add nodes without disrupting the
services that are running on the fabric. When you add nodes to the fabric, you can manage
and monitor the nodes from the Administrationworkspace. To add, manage, and monitor
NOTE: You must add the NTP server before you add the first node to the
nodes in the fabric, a fabric administrator connects to a single virtual IP address. See
Figure 5 on page 10
Figure 5: AdministratorConnects to a Single Virtual IP Address to Manage
Fabric Nodes
Single Node Functionality
When the fabric comprises a single appliance, all devices in the managed network connect
to the appliance. When you install and configure the first appliance, Junos Space
automatically creates a fabric with one node. By default, a fabric that consists of a single
node provides complete Junos Space management functionality. The following node
functions are enabled for the node:
•
Load Balancer— for processing HTTP requests from remote browsers and NBI clients
•
Database— for processing database requests (create, read, update, and delete
operations)
•
Application Logic— for processing Junos Space service requests and Data Manipulation
Language (DML) workload (device connectivity, device events, and logging)
NOTE: A fabric that comprises a single node provides no workload balancing
As your network expands with new devices, services, and users, you can add Junos Space
appliances to handle the increased workload. When you install and configure the first
appliance, Junos Space automatically creates a fabric with one node. For each additional
appliance you install and configure, you must add a node to logically represent the
appliance in the fabric. Each node that you add to the fabric increases the resource pool
for the node functions to meet the scalability and availability requirements of your network.
By default, Junos Space automatically enables node functionality across the nodes in
the fabric to distribute workload. The nodes in the fabric work together to provide a
virtualized resource pool for each of the node functions: load balancer, database, and
application logic.
The Junos Space node functions distribute workload across operating nodes according
to the following load-distribution rules:
•
Chapter 1: Overview of the Junos Space JA1500 Appliance
LoadBalancer—When a node that functions as the active load balancer server is down,
all HTTP requests are automatically routed to the standby load balancer server that
is running on a separate node.
•
Database— When a node that functions as the active database server is down, all
database requests (create, read, update, and delete) are routed to the node that
functions as the standby database server.
•
Application Logic— Device connections and user requests are distributed among the
nodes, and device-related operations are routed to the node to which the device is
connected.
Junos Space uses the following algorithm to ensure that the number of devices
connected to a node does not exceed the threshold limit for each node:
Threshold Limit = [ (number of devices in database) / (number of nodes running) ] + 2
The following workflow describes how the node functions are enabled across the fabric
as nodes are added:
•
First node: The load balancer, database, and application logic functions are enabled
on the node. Each node function provides both scalability and high availability. Figure
6 on page 11 shows all functions enabled on a fabric comprising one node.
Figure 6: Functions Enabled on Fabric Containing One Node
Second node: When a second node is added to the fabric, the first node functions as
the active load balancer server and active database server, and the second node
functions as the standby load balancer server and standby database server. The load
balancer and application logic node functions provide scalability and high availability.
The database node function on the second node provides high availability only. Figure
7 on page 12 shows the functions enabled on a fabric comprising two nodes.
Figure 7: Functions Enabled on Fabric Containing Two Nodes
•
Third and subsequent nodes: Only the application logic functionality is enabled on the
third node to provide equal distribution of device connections and user requests across
all nodes, and to route device-related operations to the node to which the device is
connected. The application logic functionality provides both scalability and high
availability. Figure 8 on page 12 shows the functions enabled on a fabric comprising
three nodes.
Figure 8: Functions Enabled on Fabric Containing Three Nodes
NOTE: For the third node and each subsequent node added to the fabric,
only the application logic functionality is enabled.
In a fabric comprising two or more nodes, Junos Space provides failover when a node
functioning as the active server (load balancer server or database server) goes down. By
default, Junos Space marks a particular node down and routes failover requests to the
node that Junos Space designates as standby server. Junos Space uses a heartbeat
mechanism to check whether the nodes in the fabric are running. When a node functioning
as the active server fails (the appliance physically crashes or stops sending heartbeats),
the node functioning as the standby server takes over all resources that were managed
by the node functioning as the active server.
Chapter 1: Overview of the Junos Space JA1500 Appliance