Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Prerequisites for Prestaging Devices in Network Activate

 

Before you can perform prestaging on your network devices, each device must meet specific configuration requirements, and must be brought under Junos Space management through device discovery.

The following configuration requirements must be met before beginning the provisioning process. Otherwise, service deployment fails:

  • MPLS must run on each N-PE device and on each P device.

  • LDP signaling must be established between N-PE devices that participate in the same point-to-point Ethernet (LDP) service.

  • MPBGP must run on each N-PE device that participates in a Layer 2 multipoint or Layer 3 full mesh service.

  • To run Layer 2, Layer 3, or VPLS services on an N-PE device, ensure that an autonomous system (AS) number is configured on the device.

Before you can prestage devices, you must perform device discovery to import all Juniper Networks devices on your network that Junos Space can manage. The Network Activate prestaging workspace works on devices that have already been discovered and imported into the Junos Space database, but have not yet been pre-staged.

The VPLS service needs to be enabled in a network device, to make the static pseudowire functionality active in the device. You can activate the static pseudowire functionality by configuring the network device through the CLI page. You need to enter the CLI configuration mode of a network element and run the command

set protocols vpls static-vpls no-tunnel-services

commit

If the device is not configured through CLI, a warning message appears in the application server log, that is the JBOSS Log:

<Device name> should be configured with static VPLS no tunnel service rule.

To discover the roles of the various network elements configured:

1. Select Network Activate > Prestage Devices > Manage Device Roles.

2. Select Discover Roles to view the relevant page.

3. Click Continue to view the Role Discovery Status page.

The Role Discovery Status page displays a graph which shows the number of unassigned devices that could be assigned the role of N-PE or PE.

To re-sync the role of the network elements configured:

1. Select Network Activate >Prestage Devices > Manage Device Roles.

2. To re-sync the role capability of a network element, right-click the network element’s name.

3. Click Re-sync Role Capability. The Re-sync Role Capability page appears where you can select the device’s name and click Re-sync.

The role is re-synced with the same device now.

To re-sync the routing state of the device:

  1. Select Network Activate >Prestage Devices > Manage Device Roles.
  2. To re-sync the routing state of the device, right-click the device’s name.
  3. Click Re-sync Routing State. The Re-sync Routing State page appears where you can select the device’s name and click Re-sync.

    The routing state of the device is re-synced.

    Starting with Release 17.1R4, you can use the new option Re-sync Routing State to re-sync the routing state of an old device.

For details about bringing devices under Junos Space management, see Discovering Devices in the Junos Space Network Application Platform User Guide.

Related Documentation

Release History Table
Release
Description
Starting with Release 17.1R4, you can use the new option Re-sync Routing State to re-sync the routing state of an old device.