Standalone Configuration; Distributed Configuration - Juniper NETWORK AND SECURITY MANAGER 2010.4 - INSTALLATION GUIDE REV1 Installation Manual

Network and Security Manager Installation Guide

Standalone Configuration

Distributed Configuration

8
Some of the factors to consider include, but are not limited to:
Number of devices managed
Size of devices managed (for example, a NetScreen 5200 firewall/VPN system might
have a larger impact than a NetScreen 5GT firewall appliance)
Impact on the organization to temporary loss of logs during server failure (if not using
multiple Device Servers the logs from firewalls would be lost until the single server is
repaired)
Amount of log data stored (this is a combination of the number of logs per day sent
from the devices and the number of days the logs are required to remain on the
management system)
Customer's Linux/Solaris knowledge/skills
Industry regulations governing the customer that might dictate the efforts they must
go to in order to protect continuous log collection
Main reason for using NSM (for example, firewall configuration only with occasional
logging; heavy logging)
Budget
Future expansion of firewall network (future proofing)
For more information about recommended hardware for various types of networks, see
"Hardware Recommendations" on page 201.
You can design and implement NSM to scale to small, medium, and large enterprises,
as well as service provider deployments. There are four main options for configuring NSM:
Standalone Configuration on page 8
Distributed Configuration on page 8
Simple High Availability Configuration on page 9
Extended High Availability Configuration on page 9
The most straightforward implementation of the NSM management system is to install
both components of the management system—GUI Server and Device Server—on the
same server. This configuration is appropriate for most small firewall networks
(recommended for no more than 100 devices, considerably less for networks containing
large firewalls). It has the advantage of low cost and simplicity. Local backup for disaster
recovery and external data storage are options for this configuration.
The NSM appliances can run as standalone configurations. See the NSMXpress and
NSM3000 User Guide for details.
For large enterprise networks that generate and store many traffic logs, we recommend
that you install the GUI Server and Device Server on separate servers. The distributed
system enables greater processing power per service. In addition, a failure of the GUI
Copyright © 2010, Juniper Networks, Inc.