Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation
Guide That Contains This Content
[+] Expand All
[-] Collapse All

    Recovering Modifications and Deletions Performed for Existing Endpoints

    Until Connectivity Services Director Release 1.0R2, the service recovery operation did not support the recovery of updated configurations made on existing endpoints associated with services. The only supported operations were recovery of new services and new endpoints for existing services, and recovery of connectivity fault management (CFM) profiles.

    Starting with Release 2.0R1, the following recovery operations are supported in addition:

    • Recovering modifications to existing endpoints

    • Recovering endpoint deletions for a service

    Also, recovery of the swap of hubs and spokes for hub-and-spoke Layer 3 VPN and VPLS services are supported. In addition, recovery of changes in configuration of backup endpoints for point-to-point A and Z endpoints is supported.

    Recovery of templates, recovery for devices with different Junos OS versions running on them, and recovery of class of service (CoS) profiles are not supported.

    Recovering Parameters for Point-to-Point Services

    Table 1 describes the fields or parameters that are supported for recovery during a service recovery operation and the corresponding XPath notifications for those configuration parameters. This table also denotes the service operation that is supported, such as creation, edit, or deletion of a service

    Table 1: Mapping of Parameters, XPaths, and Supported Operations for Point-to-Point Services

    Field

    XPath

    Supported Operation

    Interface MTU

    configuration/interfaces/interface/mtu

    Modify service

    Interface bandwidth

    /configuration/firewall/policer/if-exceeding/bandwidth-limit

    Modify service

    Starting C-VLAN ID in a range

    /configuration/interfaces/unit/vlan-tags/inner-range

    Modify service

    Ending C-VLAN ID in a range

    /configuration/interfaces/unit/vlan-tags/inner-range

    Modify service

    C-VLAN ID

    /configuration/interfaces/unit/vlan-tags/inner (Q-in-Q)

    Modify service

    V-LAN ID

    /configuration/interfaces/unit/vlan-tags/outer (Q-in-Q)

    /configuration/interfaces/unit/vlan-id (Dot1Q)

    Modify service

    Outer TPID

    /configuration/interfaces/interface/unit/input-vlan-map/tag-protocol-id

    /configuration/interfaces/interface/unit/output-vlan-map/tag-protocol-id

    Create, modify, and delete service

    Inner TPID

    /configuration/interfaces/interface/unit/input-vlan-map/inner-tag-protocol-id

    /configuration/interfaces/interface/unit/output-vlan-map/inner-tag-protocol-id

    Create, modify, and delete service

    Endpoint LSP association

    /configuration/protocols/l2circuit/neighbor/interface/community

    /configuration/policy-options/policy-statement/term/then/install-nexthop/lsp

    Create, modify, and delete service

    Interface description

    /configuration/interfaces/interface/unit/description

    Create, modify, and delete service

    Changing, disabling, and enabling CFM profile

    Not supported

    Not applicable

    Recovering Parameters for Layer 3 VPN Services

    Table 2 describes the fields or parameters that are supported for recovery during a service recovery operation and the corresponding XPath notifications for those configuration parameters. This table also denotes the service operation that is supported, such as creation, edit, or deletion of a service

    Table 2: Mapping of Parameters, XPaths, and Supported Operations for Layer 3 VPN Services

    Field

    XPath

    Supported Operation

    Interface MTU

    configuration/interfaces/interface/mtu

    Modify service

    Interface bandwidth

    /configuration/firewall/policer/if-exceeding/bandwidth-limit

    Modify service

    Starting C-VLAN ID in a range

    /configuration/interfaces/unit/vlan-tags/inner-range

    Modify service

    Ending C-VLAN ID in a range

    /configuration/interfaces/unit/vlan-tags/inner-range

    Modify service

    C-VLAN ID

    /configuration/interfaces/unit/vlan-tags/inner (Q-in-Q)

    Modify service

    V-LAN ID

    /configuration/interfaces/unit/vlan-tags/outer (Q-in-Q)

    /configuration/interfaces/unit/vlan-id (dot1Q)

    Modify service

    Outer TPID

    Gets prefixed to VLAN tags, for example:

    <vlan-tags>        
    <outer>0x88a8.51</outer>        
    <inner-range>0x9100.56-65</inner-range> 
    </vlan-tags> 

    Create, modify, and delete service

    Inner TPID

    <vlan-tags>        
    <outer>0x88a8.51</outer>        
    <inner-range>0x9100.56-65</inner-range> 
    </vlan-tags> 

    Create, modify, and delete service

    MAC table size

    Not supported

    Not applicable

    Interface MAC limit

    Not supported

    Not applicable

    Mesh group name change

    Not supported

    Not applicable

    Interface description

    /configuration/interfaces/interface/unit/description

    Create, modify, and delete service

    PW extension (BGP and LDP)

    Addition of point-to-point spoke and update of neighbor in hub are supported

    /configuration/routing-instances/instance/instance/protocols/vpls/mesh-group/vpls-id

    /configuration/routing-instances/instance/instance/protocols/vpls/mesh-group/neighbor

    Create and delete service

    PW resiliency (LDP)

    Addition of a backup hub and update of neighbor details in point-to-point spoke and VPLS LDP spoke are supported

    Update of neighbor to primary hub is not supported

    /configuration/routing-instances/instance/protocols/vpls/neighbor/backup-neighbor/name for LDP spoke

    /configuration/protocols/l2circuit/neighbor/interface/backup-neighbor/name for point-to-point spoke

    Create and delete service

    Changing, disabling, and enabling CFM profile

    Not supported

    Not applicable

    Recovering Parameters for VPLS Services

    Table 3 describes the fields or parameters that are supported for recovery during a service recovery operation and the corresponding XPath notifications for those configuration parameters. This table also denotes the service operation that is supported, such as creation, edit, or deletion of a service

    Table 3: Mapping of Parameters, XPaths, and Supported Operations for VPLS Services

    Field

    XPath

    Supported Operation

    Interface MTU

    configuration/interfaces/interface/mtu

    Modify service

    Interface bandwidth

    /configuration/firewall/policer/if-exceeding/bandwidth-limit

    Modify service

    Tagging

    Not supported

    Not applicable

    Starting C-VLAN ID in a range

    /configuration/interfaces/unit/vlan-tags/inner-range

    Modify service

    Ending C-VLAN ID in a range

    /configuration/interfaces/unit/vlan-tags/inner-range

    Modify service

    C-VLAN ID

    /configuration/interfaces/unit/vlan-tags/inner (Q-in-Q)

    Modify service

    V-LAN ID

    /configuration/interfaces/unit/vlan-tags/outer (Q-in-Q)

    /configuration/interfaces/unit/vlan-id (dot1Q)

    Modify service

    IP address

    /configuration/interfaces/interface/unit/family/inet/address/name

    Modify service

    Neighbor IP address

    /configuration/routing-instances/instance/protocols/bgp/group/neighbor/name

    Modify service

    Peer AS

    /configuration/routing-instances/instance/protocols/bgp/group/peer-as

    Create and modify service

    AS override

    /configuration/routing-instances/instance/protocols/bgp/group/as-override

    Create, modify, and delete service

    Interface description

    /configuration/interfaces/interface/unit/description

    Create, modify, and delete service

    Static routes (destination prefix, next hop)

    Not supported

    Not applicable

    Enable or disable of MVPN and MC-LAG (addition of MVPN capability to an existing L3VPN)

    Not supported

    Not applicable

    PE-CE Settings, OSPF Domain ID, version

    Not supported

    Not applicable

    Stitching into a point-to-point service

    Both services must be recovered individually according to the current behavior

    Not applicable

    Route distinguisher (full-mesh OSPF_

    Not supported

    Not applicable

    Recovering Endpoint Deletions from a Service

    The following scenarios are supported when recovering endpoint deletion from a service:

    • Recovery of a deleted endpoint for multipoint-to-multipoint VPLS and full-mesh Layer 3 VPN services

    • Recovery of a deleted spoke for point-to-multipoint VPLS and hub-and-spoke Layer 3 VPN services

    Modified: 2017-09-13