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.
The information in this document is current as of the date on the title page.
YEAR 2000 NOTICE
Juniper Networks hardware and software products are Year 2000 compliant. Junos OS has no known time-related limitations through the
year 2038. However, the NTP application is known to have some difficulty in the year 2036.
END USER LICENSE AGREEMENT
The Juniper Networks product that is the subject of this technical documentation consists of (or is intended for use with) Juniper Networks
software. Use of such software is subject to the terms and conditions of the End User License Agreement (“EULA”) posted at
http://www.juniper.net/support/eula.html. By downloading, installing or using such software, you agree to the terms and conditions of
To obtain the most current version of all Juniper Networks®technical documentation,
see the product documentation page on the Juniper Networks website at
http://www.juniper.net/techpubs/.
If the information in the latest release notes differs from the information in the
documentation, follow the product Release Notes.
Juniper Networks Books publishes books by Juniper Networks engineers and subject
matter experts. These books go beyond the technical documentation to explore the
nuances of network architecture, deployment, and administration. The current list can
be viewed at http://www.juniper.net/books.
Documentation Conventions
Table 1 on page xii defines notice icons used in this guide.
Indicatesa choice betweenthe mutually
exclusivekeywordsor variables oneither
side of the symbol. The set of choices is
often enclosed in parentheses forclarity.
same lineas theconfiguration statement
to which it applies.
Encloses a variable for which you can
substitute one or more values.
Identifies a level in the configuration
hierarchy.
Identifies a leaf statement at a
configuration hierarchy level.
Representsgraphicaluser interface (GUI)
items you click or select.
broadcast | multicast
(string1 | string2 | string3)
rsvp { # Required for dynamic MPLS onlyIndicates a comment specified on the
community name members [
community-ids ]
[edit]
routing-options {
static {
route default{
nexthop address;
retain;
}
}
}
•
In the Logical Interfaces box, select
All Interfaces.
•
To cancel the configuration, click
Cancel.
> (bold right angle bracket)
Documentation Feedback
We encourage you to provide feedback, comments, and suggestions so that we can
improve the documentation. You can provide feedback by using either of the following
methods:
•
Online feedback rating system—On any page at the Juniper Networks Technical
Documentation site at http://www.juniper.net/techpubs/index.html, simply click the
stars to rate the content, and usethe pop-upform toprovide uswith information about
your experience. Alternately, you can use the online feedback form at
https://www.juniper.net/cgi-bin/docbugreport/.
Separates levels in a hierarchy of menu
selections.
In the configuration editor hierarchy,
select Protocols>Ospf.
E-mail—Sendyour comments totechpubs-comments@juniper.net.Includethe document
or topic name, URL or page number, and software version (if applicable).
Requesting Technical Support
Technical productsupport isavailablethrough theJuniper Networks Technical Assistance
Center (JTAC). If you are a customer with an active J-Care or JNASC support contract,
or are covered under warranty, and need post-sales technical support, you can access
our tools and resources online or open a case with JTAC.
•
JTAC policies—For a complete understanding of our JTAC procedures and policies,
review the JTAC User Guide located at
JTAC hours of operation—The JTAC centers have resources available 24 hours a day,
7 days a week, 365 days a year.
Self-Help Online Tools and Resources
For quick and easy problem resolution, Juniper Networks has designed an online
self-service portal called the Customer SupportCenter (CSC)that provides you with the
following features:
The Juniper Secure Analytics 3800 (JSA3800) is an enterprise-class appliance that
providesa scalable networksecuritymanagement solution for medium-sizedcompanies
up to large global organizations.
The JSA3800 appliance is a 1-U, rack-mountable chassis with AC power supplies (or
optional DC power supplies), six hot-swappable hard drives, 64 GBmemory, and two10
Gigabit and four Gigabit Ethernet interfaces.
The JSA3800 appliance:
•
Responds to the right threats at the right time through effective analysis of networks,
events, and audit log files.
Related
Documentation
•
Identifies environmental anomalies in the network, an attack path, and the source of
a threat.
•
Provides network remediation for threat responses across all security products.
The JSA appliances use the following drivers for security analysis of external and internal
threats:
•
Security Information Management (SIM)—SIMprovides reportingand analysis ofdata
from host systems, applications, and security devices to support security policy
compliance management, internal threat management, and regulatory compliance
initiatives.
•
Security Event Management (SEM)—SEM improves security incident response
capabilities by processing data from security devices and network devices. It helps
network administrators to provide effective responses toexternal and internal threats.
JSA3800 Appliance Hardware Overview on page 4•
• JSA3800 Appliance Front Panel Description on page 7
• JSA3800 Appliance Back Panel Description on page 9
Juniper Secure Analytics (JSA) includes the following deployment components:
•
Flow Processor—Collects data from devices, and various live and recorded feeds, such
as network taps, span/mirror ports, NetFlow, and JSA flow logs. When the data is
collected, theFlow Processor groups related individual packets into a flow. JSAdefines
these flows as a communication session between two pairs of unique IP addresses
and ports that use the same protocol. A flow starts when the Flow Processor detects
the first packet with a unique source IP address, destination IP address, source port,
destination port, and other specific protocol options that determine the start of a
communication. Each additional packet is evaluated. Counts of bytes and packets are
added to the statistical counters in the flow record. At the end of an interval, a status
record of the flow is sent to an Event Collector, and statistical counters for the flow
are reset. A flow ends when no activity for the flow is detected within the configured
period of time.
Flow reporting generates records of all active or expired flows during a specified period
of time. If the protocol does not support port-based connections, JSA combines all
packets between the two hosts into a single flow record. However, a Flow Processor
does not record flows until a connection is made to another JSA component and data
is retrieved.
•
Event Collector—Collects security events from varioustypes of security devices, known
as log sources, in your network. The Event Collector gathers events from local and
remote log sources. The Event Collector then normalizes the events and sends the
information to the Event Processor. The Event Collector also bundles all virtually
identical events to conserve system usage.
•
Event Processor—An Event Processor processes event and flow data from the Event
Collector. The events are bundled to conserve network usage. When received, the
EventProcessor correlates the informationfrom JSA anddistributes itto theappropriate
area, depending on the type of event. The Event Processor also includes information
gathered by JSA to indicate any behavioral changes or policy violations for that event.
Rulesare thenapplied tothe eventsthat allow the Event Processor to processaccording
to the configured rules. When complete, the Event Processor sends the events to the
Magistrate.
A non-consoleEvent Processorcan beconnected to the Event Processor on theconsole
or connected to another Event Processor in your deployment. The Accumulator is
responsible for gathering flow and event information from the Event Processor.
The Event Processor on the console is always connected to the Magistrate. This
connection cannot be deleted.
•
Off-site Source—Indicatesan offsite event or flow data source thatforwardsnormalized
data to an Event Collector. You can configure an offsite source to receive flows or
events and allow the data to be encrypted before forwarding.
•
Off-site Target—Indicates an offsite device that receives event or flow data. An offsite
target can only receive data from an Event Collector.
•
Magistrate—The Magistrate component provides the core processing components of
the security information and event management (SIEM) system. You can add one
Magistrate component for each deployment. The Magistrate provides views, reports,
alerts, and analysis of network traffic and security events. The Magistrate processes
the eventsor flows against the defined custom rules to createan offense. If no custom
rules exist, the Magistrate uses the default rule set to process the offending event or
flow. An offense is an event or a flow that has been processed through JSA using
multipleinputs, individualevents orflows,and combinedevents or flowswith analyzed
behavior and vulnerabilities. The Magistrate prioritizes the offenses and assigns a
magnitude value based on several factors, including the amount of offenses, severity,
relevance, and credibility.
Related
Documentation
• Preparing the Network Hierarchy on page 39
• JSA3800 Appliance Description on page 3
• General Safety Guidelines and Warnings on page 63
Table 3: JSA3800 Front Panel Components (continued)
DescriptionComponentCallout
Hard drive3
USB ports4
Chassis LEDs7
UID button8
Six 900 GB hard disk drives (Drive0 Derive 5).
•
Drive1 (top left) and Drive0 (bottom
left)
•
Drive3 (top middle) and Drive2
(bottom middle)
•
Drive5 (top right) andDrive4 (bottom
right)
2 USB ports that accept a USB storage
device.
Reboots the appliance.RESET button5
Powers on or powers off the appliance.Power button6
Provides the colors and states, and the
status they indicate.
Turns on or off the blue light function of
the U-LED when used with a
UID-compatiblemotherboard. Oncethe
blue light is activated, you can easily
locate the appliance in very large racks
and server banks.
Empty hard drive slots.Empty slots9
Figure 2 on page 8 shows the front panel LEDs of the JSA3800 appliance.
Figure 2: JSA3800 Front Panel LEDs
Table 4 on page 9 lists the JSA3800 front panel LEDs.
Solid red—Indicates an overheat
condition, which might be caused by
cables obstructing the airflow in the
system or the ambient room
temperature being too warm.
•
Red (slowly blinking)—Indicates a
power failure.
•
Solid Blue—Indicates that the local
UID button is depressed.
•
Blue (blinking)—Indicates
IPMI-activated UID.
LAN22
LAN13
Power5
Related
Documentation
JSA3800 Appliance Description on page 3•
• JSA3800 Appliance Hardware Overview on page 4
• JSA3800 Appliance Back Panel Description on page 9
JSA3800 Appliance Back Panel Description
Figure 3 on page 9 shows the back panel components of the JSA3800 appliance.
Figure 3: JSA3800 Back Panel
When blinking, it indicates DataShare
interface activity.
When blinking,it indicatesManagement
interface activity.
Unused.Hard drive4
Solid green—Indicatesthat the appliance
is receiving power.
Table 5 on page 10 provides information about the back panel components of the