Update the Network Implementation Plan and Recreate Service Instances After Upgrade

After the Paragon Automation cluster has been upgraded, use the information in this topic to upgrade the service designs, update the network implementation plan, and recreate the resource and service instances on the upgraded setup.

As part of upgrading your Paragon Automation installation from Release 2.1.0 to Release 2.2.0, you must also upgrade the service designs that Paragon Automation provides for infrastructure, resources (l2-addr, l3-addr, routing, topo, and vpn), and services (L3VPN, EVPN, and L2 circuit). Upgrade of your Paragon Automation installation is incomplete without upgrading the service designs.

Upgrade the service, resource, and onboarding service designs versions to the following versions:
- elan-evpn-csm—0.4.27
- eline-l2circuit-nsm—0.4.10
- l3vpn—0.5.70
- l2-addr—0.1.5
- l3-addr—0.2.6
- routing—0.1.8
- topo—0.6.13
- vpn-resources—0.3.4
- infrastructure—0.12.25
See Upgrade Service Design Version for a Service Instance to upgrade the service design versions.
If you haven't already deleted or deprovisioned L3VPN, EVPN, and L2 circuit service instances that were created in 2.1.0, deprovision them now.

To deprovision a service:
1. Select the service instance you want to deprovision on the Service Instances page (Orchestration > Instances).
2. Click More > Deprovision.
  
  The Confirm Deprovision page appears.
3. Click Yes on the Confirm Deprovision page.
  
  The service is deprovisioned and the resources used by the service are released.
If you haven't already deleted resource instances that were created for L3VPN, EVPN, and L2 circuit services in Release 2.1.0, delete them now, but retain the resource instances created for the network implementation plans (topo and routing). Additionally, delete the corresponding dependencies as well.

To delete a resource instance:
1. Select the resource instance that you want to delete on the Resource Instances page.
2. Click More > Deprovision.
  
  The Deprovision Resource Instance page appears.
3. Click Yes on the Deprovision Resource Instance page.
  
  The resource instance is deprovisioned.
Update the network implementation plan created in Release 2.1.0 to use the infrastructure service design version 0.12.25.
1. Log into the Paragon Automation GUI and obtain the organization ID.
  1. Click Settings Menu > Organization Settings on the banner.
    
    The Organization Settings page appears.
  2. Click Copy under Organization ID field.
2. Select a plan and upgrade the service design to 0.12.25.
  1. On the Paragon Automation GUI, click Inventory > Device Onboarding > Network Implementation Plan.
    
    The Network Implementation Plan page appears.
  2. Select the plan that you want to update and click More > Upgrade Service Design.
    
    The Upgrade Service Design page appears.
  3. Select 0.12.25 from the drop-down list and click Yes.
    
    A confirmation message appears that the service design of the selected plans is upgraded to the selected service design version.
3. On the Network Implementation Plan page, click More > Export to export the plan and obtain the Customer ID (customer_id) and Service Instance name (instance_id) present in the upgraded plan.
4. On the service orchestration cMGD CLI, remove any active placements for the network plan and any services associated with the plan.
  1. Log in to the Paragon Automation installer node.
  2. Type exit to exit to the Linux root shell from Paragon Shell.
  3. Log in to the service orchestration cMGD CLI from the Linux root shell.
  4. Remove active placements and services associated with the plan.
    Where,
    - org-id is the organization ID associated with the plan and service design. You obtain the value from step 4.a.
    - customer-id is the ID of the customer associated with the service provided by an instance of the service design. You obtain the value from step 4.c.
    - instance-name is the name of the service instance associated with the service design. You obtain the value from step 4.c.
    Ensure that there are no other orders running when you are performing this procedure as those orders could consume the resources that have been temporarily de-allocated.
5. If there are mulitple network implementation plans, repeat steps 4.b, 4.c, and 4.d for all plans.
6. (Optional) On the Paragon Automation GUI, select the plan that you upgraded and edit the new parameters (for example, IPv6 addresses) associated with the upgraded service design.
7. Click Publish for the changes in the plan to be pushed to the devices in the plan.
  
  When you click Publish, resources are allocated again for the plan and the service design version recorded in Placement Resources matches with service design of the plan and the new configurations available with the new service design are pushed to the devices.
8. Verify that the publish workflow for the plan is executed successfully and the Order Status of the plan is Success on the Network Implementation Plan page.
Create the resource instances needed for L2 circuit, EVPN, and L3VPN overlay services.
1. Click Orchestration > Resource Instances.
  
  The Resource Instances page appears.
2. Click the + (Add) icon.
  
  The Add New Resource Instance page appears.
3. Enter the values for Instance Name and Customer Name, and select a resource design—l2-addr, l3-addr, routing, topo, and vpn.
4. Configure the resource pools. See Configure Resource Pools.
Create new L2 circuit, EVPN, and L3VPN service instances.

To create a service instance:
1. Click Orchestration > Instances.
  
  The Service Instances page appears.
2. Click Add > service.
  
  The Add service-name page appears.
3. Enter values for the parameters as needed. Refer:
  - Add an EVPN Service Instance to create an EVPN service.
  - Add an L3VPN Service Instance to create an L3VPN service.
  - Add an L2 Circuit Service Instance to create an L2 circuit.