close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Overview
- play_arrow Working with Connectivity Services Director
- play_arrow Service View Tasks and Lifecycle Modes
- play_arrow Network Services Overview
play_arrow Getting Started With Connectivity Services Director
- play_arrow Understanding Connectivity Services Director System Administration and Preferences
play_arrow Working with the Dashboard
- play_arrow About the Dashboard
  - Understanding the Dashboard
- play_arrow Using the Dashboard
  - Using Dashboard Widgets
- play_arrow Dashboard Widget Reference
play_arrow Working in Build Mode
- play_arrow About Build Mode
  - Understanding Build Mode in Views Other than Service View of Connectivity Services Director
  - Understanding the Build Mode Tasks Pane in Views Other than Service View
- play_arrow Discovering Devices
- play_arrow Creating Custom Device Groups
  - Understanding Custom Device Groups
  - Creating Custom Device Groups
- play_arrow Configuring Quick Templates
  - Understanding Quick Templates
  - Configuring and Managing Quick Templates
- play_arrow Configuring Device Settings
- play_arrow Configuring Class of Service (CoS)
  - Understanding Class of Service (CoS) Profiles
  - Creating and Managing Wired CoS Profiles
- play_arrow Configuring Link Aggregation Groups (LAGs)
  - Understanding Link Aggregation
  - Managing and Creating a Link Aggregation Group
- play_arrow Managing Network Devices
play_arrow Building a Topology View of the Network
- play_arrow Downloading and Installing CSD-Topology
- play_arrow Configuring Topology Acquisition and Connectivity Between the CSD-Topology and Path Computation Clients
- play_arrow Accessing the Topology View of CSD-Topology
play_arrow Prestaging
- play_arrow Prestaging Devices Overview
- play_arrow Prestaging: Managing Devices and Device Roles
- play_arrow Prestaging: Managing IP Addresses
- play_arrow Device Configuration Prerequisites to Prestaging Examples
- play_arrow Prestaging Services
play_arrow Service Design: Working with Service Definitions
- play_arrow Service Design: Predefined Service Definitions
- play_arrow Service Design: Managing E-Line Service Definitions
- play_arrow Service Design: Managing E-LAN Service Definitions
- play_arrow Service Design: Managing IP Service Definitions
play_arrow Service Provisioning: Working with Customers
- play_arrow Service Provisioning: Managing Customers
play_arrow Working in Deploy Mode
- play_arrow About Deploy Mode
  - Understanding Deploy Mode in Views Other than Service View of Connectivity Services Director
  - Understanding the Deploy Mode Tasks Pane in Views Other than Service View
- play_arrow Deploying and Managing Device Configurations
- play_arrow Deploying and Managing Software Images
play_arrow Service Provisioning: Working with Service Orders
- play_arrow Service Provisioning: Viewing the Configured Services and Service Orders
- play_arrow Service Provisioning: Managing E-Line Service Orders
- play_arrow Service Provisioning: Managing E-LAN Service Orders
- play_arrow Service Provisioning: Managing IP Service Orders
- play_arrow Service Provisioning: Performing RFC 2544 Benchmark Testing
play_arrow Service Provisioning: Working with Services Deployment
- play_arrow Service Provisioning: Managing Deployed Services
play_arrow Auditing Services and Viewing Audit Results
- play_arrow Service Provisioning: Auditing Services
- play_arrow Troubleshooting Devices and Services
play_arrow Working in Monitor Mode
- play_arrow About Monitor Mode
  - Understanding Monitor Mode in Views Other than Service View of Connectivity Services Director
  - Understanding the Monitor Mode Tasks Pane in Views Other than Service View
- play_arrow Monitoring Traffic
- play_arrow Monitoring Devices
  - Comparing Device Statistics
  - Showing ARP Table Information
- play_arrow General Monitoring
- play_arrow Monitor Reference
- play_arrow Detecting and Examining the Health and Performance of Services
play_arrow Working in Fault Mode
- play_arrow About Fault Mode
  - About Fault Mode in All Views of Connectivity Services Director
  - Understanding the Tasks Pane in Fault Mode
- play_arrow Using Fault Mode
- play_arrow Fault Reference
play_arrow End-to-End Configuration Examples
- play_arrow Configuration Scenarios
play_arrow Working with Chassis View
- play_arrow Working with Devices
- play_arrow Managing CLI Configlets
play_arrow Managing Optical Interfaces, OTUs, ODUs, ILAs, and IPLCs on MX Series and PTX Series Routers
- play_arrow Overview of Optical Interfaces, OTUs, and ODUs
- play_arrow Overview of Optical ILAs and IPLCs
- play_arrow Configuring and Monitoring Optical Interfaces, OTUs, and ODUs
- play_arrow Configuring and Monitoring Optical Inline Amplifiers
- play_arrow Configuring and Monitoring Optical Integrated Photonic Line Cards
play_arrow Working with User Roles
- play_arrow Managing User Roles
  - Creating a User-Defined Role
  - Managing Roles
play_arrow Working with Tunnel Services
- play_arrow Tunnel Services Overview
- play_arrow Service Design and Provisioning: Managing and Deploying Tunnel Services
- play_arrow Monitoring and Troubleshooting Tunnel Services
play_arrow Appendix: Managing Network Activate Features Using the Older Version of Services Activation Director
- play_arrow Service Design: Working with E-Line, IP, and E-LAN Service Templates
- play_arrow Service Provisioning: Working with Threshold Alarm Profiles

list Table of Contents

English

keyboard_arrow_right

Sample XPath Notifications Received on Devices for a Modified E-LAN Service

date_range 17-Oct-23

arrow_backward

arrow_forward

While developing configlets, XPaths and Regular Expressions would be used intensively. It would be desirable to let the user define frequently used XPaths and Regular expressions in such a way that they can be referred when required. User can define these templates from the Xpath and Regex task group in the CLI Configlets workspace of the Junos Space Platform GUI. For an E-LAN service that is modified using the Connectivity Services Director application, the XPath attributes corresponding to the modified configuration settings and parameters are sent to the associated devices of the service for the revised configuration elements to be applied on the devices. 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 modified E-LAN service:

The following is the changed XPath attribute for a routing instance of a modified E-LAN service:

content_copy zoom_out_map
/configuration/routing-instances/instance/route-distinguisher/rd-type

The following is the differential configuration set for the XPath attribute for a routing instance of a modified E-LAN service:

content_copy zoom_out_map
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply op="U">
<configuration op="U">
<routing-instances op="U">
      <instance op="U">
        <name>VplsBasicSO</name>
        <instance-type>vpls</instance-type>
        <interface>
          <name>ge-0/1/4.69</name>
        </interface>
        <route-distinguisher op="U">
          <rd-type op="U">36001:7</rd-type>
        </route-distinguisher>
        <vrf-target>
          <community>target:36000:6</community>
        </vrf-target>
        <protocols>
          <vpls>
            <mac-table-size>
              <limit>5120</limit>
            </mac-table-size>
            <interface-mac-limit>
              <limit>1024</limit>
            </interface-mac-limit>
            <no-tunnel-services/>
            <site>
              <name>Site_1</name>
              <site-identifier>1</site-identifier>
              <site-preference>primary</site-preference>
              <interface>
                <name>ge-0/1/4.69</name>
              </interface>
            </site>
          </vpls>
        </protocols>
      </instance>
    </routing-instances>
  </configuration>
</rpc-reply>

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:

content_copy zoom_out_map
/configuration/interfaces/interface

The following is the configuration difference for the XPath attribute of physical interfaces:

content_copy zoom_out_map
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply op="U">
  <configuration op="U">
    <system>
      <services/>
    </system>
    <chassis/>
    <interfaces op="U">
      <interface op="U">
        <name>ge-0/0/5</name>
        <flexible-vlan-tagging/>
        <mtu op="U">1520</mtu>
        <encapsulation>flexible-ethernet-services</encapsulation>
        <unit>
          <name>29</name>
          <encapsulation>vlan-vpls</encapsulation>
          <vlan-tags>
            <outer>34</outer>
          </vlan-tags>
          <family>
            <vpls>
              <filter>
                <input>
                  <filter-name>filter_in_ge-0/0/5_29</filter-name>
                </input>
              </filter>
            </vpls>
          </family>
        </unit>
      </interface>
    </interfaces>
   </configuration>
</rpc-reply>

The following is the changed XPath attribute for the logical unit of an interface:

content_copy zoom_out_map
/configuration/interfaces/interface/unit/vlan-tags/outer

The following is the configuration difference for the XPath attribute of logical unit of an interface:

content_copy zoom_out_map
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply op="U">
  <configuration op="U">
    <system>
      <services/>
    </system>
    <chassis/>
    <interfaces op="U">
      <interface op="U">
        <name>ge-0/0/5</name>
        <flexible-vlan-tagging/>
        <mtu>1522</mtu>
        <encapsulation>flexible-ethernet-services</encapsulation>
        <unit op="U">
          <name>29</name>
          <encapsulation>vlan-vpls</encapsulation>
          <vlan-tags op="U">
            <outer op="U">34</outer>
          </vlan-tags>
          <family>
            <vpls>
              <filter>
                <input>
                  <filter-name>filter_in_ge-0/0/5_29</filter-name>
                </input>
              </filter>
            </vpls>
          </family>
        </unit>
      </interface>
    </interfaces>
    </configuration>
</rpc-reply>

The following are the changed XPath attributes for a firewall filter at the [edit firewall family vpls] hierarchy level:

content_copy zoom_out_map
/configuration/firewall/family/vpls/filter/term/then/discard, 
        /configuration/firewall/family/vpls/filter/term/name

The following is the configuration difference for the XPath attribute of a firewall filter in an E-LAN family:

content_copy zoom_out_map
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply op="U">
  <configuration op="U">
    <system>
      <services/>
    </system>
    <chassis/>
    <interfaces op="U">
      <interface op="U">
        <name>ge-0/0/5</name>
        <flexible-vlan-tagging/>
        <mtu op="U">1520</mtu>
        <encapsulation>flexible-ethernet-services</encapsulation>
        <unit>
          <name>29</name>
          <encapsulation>vlan-vpls</encapsulation>
          <vlan-tags>
            <outer>34</outer>
          </vlan-tags>
          <family>
            <vpls>
              <filter>
                <input>
                  <filter-name>filter_in_ge-0/0/5_29</filter-name>
                </input>
              </filter>
            </vpls>
          </family>
        </unit>
      </interface>
    </interfaces>
   </configuration>
</rpc-reply>

The following are the changed XPath attributes for the policer statement at the [edit firewall] hierarchy level:

content_copy zoom_out_map
/configuration/firewall/policer/if-exceeding/bandwidth-percent
/configuration/firewall/policer/if-exceeding/bandwidth-limit

The following is the configuration difference for the XPath attribute of a firewall policer:

content_copy zoom_out_map
<?xml version="1.0" encoding="UTF-8"?>
<rpc-reply op="U">
  <configuration op="U">
    <system>
      <services/>
    </system>
    <chassis/>
    <interfaces op="U">
      <interface op="U">
        <name>ge-0/0/5</name>
        <flexible-vlan-tagging/>
        <mtu op="U">1520</mtu>
        <encapsulation>flexible-ethernet-services</encapsulation>
        <unit>
          <name>29</name>
          <encapsulation>vlan-vpls</encapsulation>
          <vlan-tags>
            <outer>34</outer>
          </vlan-tags>
          <family>
            <vpls>
              <filter>
                <input>
                  <filter-name>filter_in_ge-0/0/5_29</filter-name>
                </input>
              </filter>
            </vpls>
          </family>
        </unit>
      </interface>
    </interfaces>
   </configuration>
</rpc-reply>

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.

arrow_backward PREVIOUS Sample XPath Notifications Received on Devices for Deleted Endpoints

NEXT arrow_forward Sample XPath Notifications Received on Devices for a Created E-LAN Service

Connectivity Services Director User Guide

Sample XPath Notifications Received on Devices for a Modified E-LAN Service

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Connectivity Services Director User Guide

Sample XPath Notifications Received on Devices for a Modified E-LAN Service

Related Documentation

Stay in touch