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

Page: 587 / 1026

While creating transaction policies, the following restrictions apply:
•
You can assign transaction rules to a service point in the device editor. For every
association, NSM defines a rule in the service point’s gateway and refers to it in the
service point. If the policy assignment changes, you must reassociate the rules with
the service points in the device editor.
•
BSG Transaction rule merge and validation is not supported.
•
Since NSM does not collect traffic logs for M Series and MX Series routers, the
Jump
to Policy
option is not applicable from log reports.
•
Admission-controller settings are dropped from the policies pushed to devices running
Junos OS Releases earlier than 9.5.
NOTE: NSM 2009.1 and later releases support BSG transactions in the Policy
Manager for M Series and MX Series only. On other devices, BSG transactions
can be configured from the device editor.
The BSG transaction rulebase is excluded when you update devices that do not support
transaction rules. NSM displays an appropriate warning during the update. NSM also
provides an
Install On
option at the term, rule, and rule set levels. If a rule or a rule set is
not applicable to the device being updated, NSM skips that rule or rule set.
537 Copyright © 2010, Juniper Networks, Inc.
Chapter 10: Configuring Voice Policies