Configuring Extranet Devices Overview; Configuring Extranet Devices Details (Nsm Procedure) - Juniper NETWORK AND SECURITY MANAGER 2010.4 - CONFIGURING SCREENOS DEVICES GUIDE REV 01 Manual

Configuring ScreenOS Devices Guide
Related
Documentation

Configuring Extranet Devices Overview

Related
Documentation

Configuring Extranet Devices Details (NSM Procedure)

30
Full Support—When a new version of ScreenOS is available, you can download a
schema patch, enabling you to manage devices using the new ScreenOS version. In
addition, you can manage all the new features in that version of ScreenOS.
The support level is indicated in the Information screen for the device in the Device
Manager.
Device Configuration Settings Overview on page 25
Configuring Network Settings Options and Descriptions on page 34
Configuring Zones and Zone Properties in ScreenOS Devices Overview on page 39
NSM also enables you to configure an existing extranet device (a third-party router). You
can do this by creating a script to perform the required actions on the extranet device.
These scripts are saved by default on the GUI Server at:
GuiSvr/var/scripts
Add the extranet device in the Device Manager, and then configure the required metadata
in a shared object in the Object Manager under Extranet Policies. This data might include:
credential information (user/password), IP address, interface list, comments, action
script and other additional data. When you update the device, the specified script is
invoked. The device update job displays the XML output.
Configuring Extranet Devices Details (NSM Procedure) on page 30
Configuring Network Settings Options and Descriptions on page 34
This example shows how to update an existing rule on a third-party router to deny certain
HTTP traffic with integer fields matching 1-10.
This process involves first creating a script that updates the policy on the router. For
example, the script can contain certain validation instructions for the policy. It can also
include instructions on sending alerts or messages in the event that the policy update
succeeds or fails. When you are done creating the script, save it in the appropriate
directory.
Next, use the Object Manager to create a custom policy field object that contains the
specific integer fields that you are referencing in the extranet policy (for example, integer
fields matching 1-10).
To create a custom policy field:
In the NSM navigation tree, click Object Manager > Custom Policy Fields.
1.
Select the Field Definition tab, and then click New. The New Custom Policy Fields
2.
Meta Data window appears.
Copyright © 2010, Juniper Networks, Inc.