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

    Performing a Service Recovery Request

    The Service Recovery feature functions within the pre-staging operation of the Network Activate application. Service Recovery has two parts.

    First, Service Recovery parses each device’s configuration searching for service configurations and existing Network Activate service elements (P2P services, Layer 2 circuits, routing instances, firewalls, policy options, routing options, and OAM interface branches of Junos Space configurations that are being processed).

    Second, Service Recovery stitches the service elements by identifying related service attributes across devices, such as VCIDs for Martini services and route targets for Kompella (L2VPN) services, to form Network Activate services.

    To perform Service Recovery, in the Network Activate task pane, select Prestage Services > Service Recovery Request. Initially, Service Recovery generates the following Alert message, which describes the process you are about to start and recommends saving previously recovered services.



    The Service Recovery Profile window displays two panels, Published Service Definition and Devices & Filters.

    In the Published Service Definition panel, you can select one or more service types: P2P, VPLS, and L3VPN.

    The Published Service Definition panel also presents a table that lists the names of all services of the selected Service Type.

    The Devices & Filters panel lists devices in the Name column. You can specify a VCID Range and Route target range to complete the definition of the service recovery profile search.

    To recover services:

    1. Fill in the fields as described in the following table.

      Field

      Action

      Published Service Definition

      Service Type

      Select the service type check boxes based on the service to recover:

      • P2P
      • VPLS
      • L3VPN

      Service template

      Select this check box to retrieve service templates attributes attached to the service. Junos Space supports the templates of the following MPLS VPN-related applications:

      • CoS
      • IPsec
      • Stateful firewall

      Name

      Select the check boxes for the service definitions whose services you want to recover.

      All the published service definitions based on service type selected are listed.

      Devices & Filters

      Devices

      Select the devices whose services you want to recover

      VCID Range

      This field is displayed if you have selected the P2P check box.

      Specify the VCID range within which services are to be recovered.

      Note: The VCID Range parameter enables you to change the VCID range for services that had been configured previously outside of the context of Junos Space.

      Route target

      This field is displayed for all the service types.

      Specify the Route target range within which services are to be recovered. You can express the range in Autonomous System number format or IPv4 format:

      • AS number format—Autonomous system (AS) number format:<l2vpn-id:as-number:2-byte-number>. For example, 100:200. The AS number can be in the range from 1 through 65,535.
      • IPv4 format—<l2vpn-id:ip-address:2-byte-number>. For example, l2vpn-id:10.1.1.1:2. Make sure that this value is lower than the value specified as the maximum route target allowed.

      Note: The Route target parameter enables you to change the route target range for services that had been configured previously outside of the context of Junos Space.

      VPLS ID range

      This field is displayed if you have selected the VPLS check box.

      Specify the VPLS ID range.

      Range: 1 through 2147483647

      Hub-Route target range

      This field is displayed if you have selected the VPLS or L3VPN check boxes.

      Specify the Hub-Route target range within which services are to be recovered. You can express the range in Autonomous System number format or IPv4 format:

      • AS number format—Autonomous system (AS) number format:<l2vpn-id:as-number:2-byte-number>. For example, 100:200. The AS number can be in the range from 1 through 65,535.
      • IPv4 format—<l2vpn-id:ip-address:2-byte-number>. For example, l2vpn-id:10.1.1.1:2. Make sure that this value is lower than the value specified as the maximum route target allowed.

      Spoke-Route target range

      This field is displayed if you have selected the VPLS or L3VPN check boxes.

      Specify the Spoke-Route target range within which services are to be recovered. You can express the range in Autonomous System number format or IPv4 format:

      • AS number format—Autonomous system (AS) number format:<l2vpn-id:as-number:2-byte-number>. For example, 100:200. The AS number can be in the range from 1 through 65,535.
      • IPv4 format—<l2vpn-id:ip-address:2-byte-number>. For example, l2vpn-id:10.1.1.1:2. Make sure that this value is lower than the value specified as the maximum route target allowed.
    2. When you complete defining the Service Recovery Profile, click Start.

      The Network Activate application fetches the latest device configuration. It then processes the device configuration to derive the configuration of selected service types.

      The Service Recovery in progress... window appears, which indicates the progress of the search.

      Note:

      • In case of a Layer 3 VPN service with pseudowire attached, you have to first recover the Layer 3 VPN service, and then the point-to-point service.
      • In case of a multihoming group for BGP-based VPLS service, the service recovery request recovers a multihoming BGP-based VPLS service regardless of the availability of a multihoming group. You must create a multihoming group before service recovery is performed.

      When the service recovery operation completes, the Service Recovery Report window appears. The service recovery report for each service is displayed in different tabs.

    Modified: 2017-02-15