Versa Create Post Staging Template

Table of Contents

• Overview
• Requirements
• Features
• How to Install
• How to Run
• Additional Information

Overview

This pre-built is used to create a post staging template in Versa Director.

Estimated Run Time: 1 minute

Requirements

This Pre-Built requires the following:

• Itential Automation Platform
  • ^2023.1
• A running instance of the Itential OpenSource Versa Director adapter, which can be installed from here.

Features

The main benefits and features of the Pre-Built are outlined below.

Every Itential Pre-built is designed to optimize network performance and configuration by focusing on reliability, flexibility and coordination of network changes with applications and IT processes. As the network evolves, Pre-builts allow customers to focus on effective management and compliance to minimize risks of disruption and outage that can negatively impact quality of service.

How to Install

To install the Pre-Built:

• Verify you are running a supported version of the Itential Automation Platform (IAP) as listed above in the Requirements section in order to install the Pre-Built.
• The Pre-Built can be installed from within App-Admin_Essential. Simply search for the name of your desired Pre-Built and click the install button (as shown below).

How to Run

Use the following to run the Pre-Built:

The pre-built can be run as a standalone or as part of a parent job.

• To run it as a standalone job, run the respective job from Operations Manager with the necessary JSON form.
• The workflow or the job can also be used as part of another parent job.

The description of the formdata needed by the prebuilt is given below: The required values to be passed on are:

Versa Adapter ID: The adapter of Versa installed on IAP.

Name: Name of the post-staging template.
Organization: The organization to be attached to the template.
Device type: To choose the type of device and solution tier.

Redundant pair: Select this option to enable automatic PostStaging Template creation for a redundant pair of device in the same site. When enabled, appropriate information for the redundant device will need to be provided.
Analytics cluster: Select the analytics clusters that will be used to send availability and usage metrics from the CPEs.

Controller Name: Select all the controllers to which the device will establish control tunnels to.
Security services: Select appropriate security services to be enabled for the device from the selection available. Appropriate configuration constructs will be enabled based on selection.
WAN Interfaces: Provide the information about WAN interface(s) to be used for the CPE. Interface number, Network name, IP address type, VLAN etc. will be required to be provided from the below options. Some of the values can be "variable-ized".

LTE Interfaces: Provide the information about LTE interface(s) to be used for the CPE.\  Redundant Pair WAN Interfaces: Provide information about the WAN interface for the redundant device. Enabled automatically if Redundant pair option was selected in previous form.
LAN Interfaces: Provide the information about LAN interface(s) to be used for the CPE. Interface number, Network name, IP address type, VLAN, DHCP server/relay etc. will be required to be provided from the below options. Some of the values can be "variable-ized"

Wifi Interfaces: Provide the information about WiFi interface(s) to be used for the CPE.

Static routes: Provide details of Static routes to be created. Select appropriate Routing instance, the prefix and next hop information.
BGP: Provide details of BGP neighbors to be configured for the CPE. eBGP is setup by default if the iBPG option is not selected. Separate BGP configurations can be created per Network by selecting appropriate network from the dropdown, and selecting Local ASN, Remote ASN, Neighbor IP Address and if BFP is to be enabled for that neighbor. Some of these values can be "variable-ized" in the template.
OSPF: Provide details of OSPF routing per Network. Select the Network from the drop down and provide the Area number and select BFD if needed.

Split tunnels: Split tunnels provide direct paths between LAN and WAN segments without using SDWAN overlay tunnels. DIA option on a split tunnel provides direct internet access over split tunnel by performing source NAT on internet bound traffic from LAN routing instance. GW option provides central DIA on hub sites by advertising default route to all spoke sites to attract internet bound traffic from spokes to the hub site. When both DIA and GW options are not selected, split tunnel routes traffic between MPLS l3vpn and SDWAN device natively on underlay network.
Load balance split tunnels? If enabled, sessions will be balanced between all the WAN interfaces selected for split tunnel. If not selected, the WAN interfaces will be used in the order of priority listed, with the top used by default for all Internet bound traffic and followed by the next one as fallback.
Site to site tunnels: IPSec site to site tunnels to be created from the CPE to another CPE.

Inbound NAT: DNAT rules to be created for services hosted on the LAN network to be available from the WAN network.

Versa instance

The above created template can be verified on the versa instance by logging in using the credentials provided.
After logging in, select the workflows tab, choose 'Template' and then 'Templates' from the left pane to view all the templates created.

Click on the template created to verify all the varibles such as controllers, device type, organization etc.,

Additional Information

Please use your Itential Customer Success account if you need support when using this Pre-Built.