Sample XPath Notifications Received on Devices for a Created IP Service
This topic illustrates the differential configuration, which is the delta or the change-set of the configuration that you are about to deploy on the devices, and the XPath attributes associated with the delta configuration for a newly created IP service:
The following is the changed XPath attribute for routing instances of a newly created IP service:
/configuration/routing-instances/instance/route-distinguisher/rd-type
For the policy- statement statement at the [edit
policy-options] hierarchy level, the correct XPath Notification
is not received if changes happen only to the policy-statement. The
notification does not contain the changed XPath and configuration
difference. Therefore, it is not possible to determine the instance
of service impacted due to the change (when only localized to policy-options->policy-statement). Full service recovery is
recommended in such cases.
The following is the changed XPath attribute for physical interfaces:
/configuration/interfaces/interface/mtu
The following is the changed XPath attribute for the logical unit of interfaces:
/configuration/interfaces/interface/unit/description
The following are the changed XPath attributes for the policer statement at the [edit firewall] hierarchy
level:
/configuration/firewall/policer/if-exceeding/bandwidth-percent /configuration/firewall/policer/if-exceeding/bandwidth-limit
The service instance cannot be determined if the changes to policer occur and in such cases ,you need to determine the type of service and also identify whether the change is to existing service or a new service. You can select a service instance and the operation type (such as create or modify) to recover service for that endpoint. Using changed XPath and applying the differential configuration to the changed XPath, you can determine the type of change and the name of the changed configuration parameter.