Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

Configure Topology Resources in Network Implementation Plan

Service orchestration obtains topology resources required for configuring a service from the following options:

  • Configuration in network implementation plan used to onboard the device (for example, access parameters, placement resources, and bandwidth allocated on each device, and so on).

  • Configuration obtained from the element management system of the device (for example, interfaces, site ID, number of routes, and so on).

  • Configuration discovered by Paragon Automation (for example, number of aggregated Ethernet (ae) interfaces configured on a device.

    Note:

    If you do not configure the number of aggregated Ethernet interfaces on a device in a network implementation plan, Paragon Automation uses the number of aggregated Ethernet interfaces that it discovers on the device.

When a resource is obtained from more than one option (for example, bandwidth reserved on a device), service orchestration considers the value in the network implementation plan.

When you configure a network implementation plan with topology resource parameters, Paragon Automation applies the configuration (number of lag interfaces) on the device during onboarding. After the device is onboarded, you can provision EVPN, EVPN-VPWS, L3VPN, and L2 Circuit services by using the resources available on the device.

To configure topology resources in a network implementation plan:

  1. A network operator or superuser must create:

    1. A device profile for the Provider Edge (PE) devices of a service and assign the device profile to all the PE devices in that service. Note that this profile must be named as 'PE' and it must be the first profile applied to all the PE devices in the service.

    2. In the network implementation plan, you must define the access parameters for the PE-CE interfaces (In the Configure Port page) without the IP address configuration.

    3. After the device is onboarded, move the device to In-Service. See Move a Device to Production.

      The device can now be used as an infrastructure resource in a service order for provisioning EVPN, EVPN-VPWS, L3VPN, and L2 Circuit services.

  2. Paragon Automation creates a Topo service order by default during device onboarding. This service order is updated with the resources (bandwidth to be allocated on each device, PE-CE access parameters, interfaces, VLANs, MAC addresses, routes, speed, and so on) assigned to the Network Implementation Plan used for onboarding the device.

    The network operator or a superuser may optionally create another Topo service order with the details of the site with postal code matches information, where the device is onboarded. The postal code matches represent the postal code of the CEs connected to the site.

  3. After the device is in-service, view the topology resources on the View Network Resources page (Orchestration > Resource Instances > More > View Network Resources). by selecting the topo resource instance for the network-operator customer and clicking the Update option.

    When you provision a service or update a network implementation plan, Paragon Automation automatically updates the network resources based on the data in the network implementation plan.

Related Documentation