Juniper NETWORK AND SECURITY MANAGER 2010.4 - ADMININISTRATION GUIDE REV1 Administration Manual page 245

Copyright © 2010, Juniper Networks, Inc.
For details about configuring the device features for all supported ScreenOS and IDP
platforms, see the Configuring Screen OS Devices Guide
(
http://www.juniper.net/techpubs/en_US/nsm2010.4/information-products/pathway-pages
/screenos-devices/index.html
Guide
(
http://www.juniper.net/techpubs/en_US/nsm2010.4/information-products/pathway-pages
/intrusion-detection-prevention-devices/index.html
Unsupported Changes
Some device configurations can be performed only by the device administrator using the
CLI or Web UI. An NSM administrator cannot perform the following device configurations
in the Device Manager:
Configuring functions that are only applicable for the device administrator, such as
setting initial IKE contact, audible alarms, MAC addresses, or console operations.
On standalone IDP Sensors, configuring Sensor mode (sniffer, transparent, and so on),
port speed and duplex settings, virtual routers, and other settings. See the IDP Installer's
Guide, IDP Concepts and Examples Guide, and IDP ACM Help for more information.
Configuring functions that require device administrator intervention, such as Secure
Command Shell (SCS) and Secure Shell (SSH) client operation.
Executing debugging commands.
Changes that Affect the Management Connection
Some configuration changes to a managed device can affect the NSM connection to the
device when you update the device, such as:
Changing the connection method (Telnet or SSH) used between the NSM Device
Server and the managed device.
Disabling the ability of the managed device to communicate with the NSM Device
Server.
Changing the IP address of the NSM Device Server on the managed device.
Changing the interface on the managed device that is permitted to receive NSM
management traffic.
Changing the VPN that handles traffic between the managed device and the NSM
Device Server.
Modifying router information on the managed device.
Changing security policy rules on the managed device that cause NSM traffic to be
dropped.
If you need to make any of the above changes to the managed device, use the Web UI
or CLI to make the changes locally, and then reimport the device configuration into the
NSM UI.
) or the Configuring Intrusion Detection Prevention Devices
).
Chapter 5: Configuring Devices
195