- play_arrow Introduction
- play_arrow Overview
- play_arrow Access and Manage Paragon Automation Account
-
- play_arrow Administration
- play_arrow Introduction
- play_arrow Organization Management
- play_arrow Site Management
- play_arrow User Management
- play_arrow Inventory Management
- play_arrow Audit Logs
- play_arrow Tags
-
- play_arrow Observability
- play_arrow Introduction
- play_arrow Health Dashboard
- play_arrow Troubleshoot Devices
- play_arrow View Network Topology
- Network Topology Visualization Overview
- Network Visualization Options
- View Network Topology Details
- Network Table Overview
- About the Device Tab
- About the Link Tab
- About the Site Tab
- About the Tunnels Tab
- Dynamic Topology Workflow
- Configure a PCE Server
- Configuring PCEP on a PE Router
- Configuring Topology Acquisition Using BGP-LS
-
- play_arrow Trust and Compliance
- play_arrow Introduction
- play_arrow Manage Trust Settings and Trust Scores
- Compliance Standards Overview
- About the Compliance Benchmarks Page
- About the Compliance Tailorings Page
- Example: Create a Tailoring Document for NTP Settings
- About the Compliance Checklist Page
- Add a Checklist Template
- Add Checklist for a Device
- Import Scans and Update Rule Results in a Checklist
- Trust Plans Overview
- About the Network Score Formula Page
- Trust Score Overview
- About the Network Score Page
- About the Snapshots Page
- Add a Snapshot for a Target
- play_arrow Manage Compliance Scans
- play_arrow Manage Vulnerabilities
- play_arrow Monitor Integrity
-
- play_arrow Service Orchestration
- play_arrow Introduction
- play_arrow View Service Design Catalog
- play_arrow Manage Customers
- play_arrow Add Resources for Network Services
- play_arrow Manage Service Instances
- Service Instance Overview
- About the Service Instances Page
- View Service Instance Details
- View Passive Assurance Monitoring Data
- View EVPN Passive Assurance Monitoring Results
- View L2 Circuit Passive Assurance Monitoring Data
- View L3VPN Passive Assurance Monitoring Results
- Physical Interfaces Health Check Results
- Logical Interfaces Health Check Results
- Performance Graphs to View Passive Assurance Monitoring Data
- play_arrow Provision VPN Services
- play_arrow Monitor Service Order Execution Workflows
-
- play_arrow Active Assurance
- play_arrow Introduction
- play_arrow Test Agents
- play_arrow Tests and Monitors
- play_arrow Test Templates
-
- play_arrow Paragon Shell CLI Reference
- play_arrow Introduction
- play_arrow Operational Mode Commands
- file copy
- monitor
- request paragon backup
- request paragon cluster pods reset
- request paragon cluster upgrade
- request paragon config
- request paragon deploy
- request paragon deploy cluster
- request paragon destroy cluster
- request paragon fix-permission
- request paragon load
- request paragon repair-node
- request paragon replace-node
- request paragon restore
- request paragon running-config
- request paragon ssh
- request paragon ssh-key
- request paragon storage cleanup
- request paragon super-user password reset
- request system decrypt password
- request system reboot
- show configuration paragon cluster
- show configuration paragon cluster applications (o)
- show configuration paragon cluster common-services (o)
- show host disk usage
- show paragon backup
- show paragon certificate expiry-date certificate-type
- show paragon cluster (o)
- show paragon cluster details
- show paragon cluster namespaces
- show paragon cluster nodes
- show paragon cluster pods
- show paragon cluster pods namespace healthbot sort
- show paragon images version
- show paragon images version namespace
- show paragon pvc details
- show paragon version
- play_arrow Configuration Mode Commands
- delete paragon cluster
- load set
- set paragon cluster applications
- set paragon cluster common-services ingress
- set paragon cluster insights victoria-metrics
- set paragon cluster install
- set paragon cluster kubernetes
- set paragon cluster mail-server
- set paragon cluster nodes
- set paragon cluster ntp
- set paragon cluster papi
- set paragon monitoring
- set system login
- show paragon cluster (c)
- show paragon cluster applications (c)
- show paragon cluster common-services ingress (c)
- play_arrow Troubleshooting Commands
- Troubleshoot Using the Paragon Shell CLI Commands
- request paragon support information
- request paragon troubleshooting information
- request paragon debug
- request paragon debug get-tsdb-data
- request paragon debug insights-kafka-data
- request paragon debug kafka
- request paragon debug logs
- request paragon debug logs namespace
- request paragon debug postgres
- request paragon debug redis
- play_arrow Service Orchestration
- About the Service Orchestration cMGD CLI
- set foghorn:core org-id
- set service design default version
- set dag state failed
- show service order status
- show service order as-json
- show service order as-yaml
- show service designs
- show device dependent configuration
- show insights configuration
- show configuration foghorn:customers
- show service instance lock status
- show service instance lock token
- show service projects
- show service order history
- show airflow dags
- show airflow dag-runs
- show paragon orgs
- request service project add
- request service order sync
- request network resources load
- request service order load
- request service order place
- request service order modify
- request service order delete
- request service order submit
- request service order provision
- request service design install
- request service design uninstall
- request create graphdb
- request service order set
- request service instance lock
- request service instance unlock
-
Add an Interface Profile
An interface profile defines interface-specific configuration elements that are added to the device during onboarding, including the interface’s IP address, whether the interface will be used for management or Internet connectivity, or whether the interface will be running OSPF, IS-IS, LDP, or RSVP protocols.
We recommend that you create some interface profiles with configurations that can be applied to all the interfaces that you would add in a network implementation plan and some profiles with interface-specific configurations.
Before you create interface profiles, ensure that you have the required IPv4 address resource pools configured in Paragon Automation. See Add Network Resource Pools and Profiles (Day -2 Activities) for details.
Paragon Automation uses the resource pools to assign IP addresses and BGP cluster IDs to the devices.
To add an interface profile:
| Field | Description |
|---|---|
| General | |
| Upload JSON File | Click Browse to upload a pre-created interface profile in the JSON file format. The values in the pre-created interface profile are automatically populated in the Create Interface Profile page. Click the Download this form into JSON file link to download and save the profile in its current state (for example, to save the current configured values for later reference or for maintaining a record). |
| Profile Name | Enter a name for the interface profile. The name can contain alphanumeric characters and some special characters [hyphen (-), underscore (_), period (.), and colon (:)] and cannot exceed 64 characters. |
| Plan Name | Enter a name for the network implementation plan in which you want to use this profile. You can use the interface profile only in the network implementation plan that you enter here. The name can contain alphanumeric characters and some special characters [hyphen (-) and period (.)] and cannot exceed 64 characters. |
Configuration Templates | Select one or more configuration templates that you want to include in the profile. Use configuration templates to configure parameters that you cannot define in the profile or plan. All the configuration templates present in the organization are listed here. Note: The configurations in the configuration template can be applied only during onboarding. Any changes to the configurations made after the device is onboarded are not applied to the device. |
| Management | Click to enable or disable (default) the use of an interface as a management interface. If you enable this option, the interface to which you assign this profile is configured as a management interface. |
| Internet Connected | Click to enable or disable (default) connectivity tests (by Active Assurance) on an interface. If you enable the Internet Connected option and add the profile as the default interface profile in the network implementation plan, Paragon Automation initiates connectivity tests from all the ports you configure for all the devices in the network implementation plan. See Device Connectivity Data and Tests Results for more information. In the network implementation plan, you can also assign the interface profile to particular interfaces (ports). |
| IPv4 Address | Click to enable or disable (default) the automatic assignment of the IPv4 address for an interface. If you enable this option, Paragon Automation assigns an IPv4 address to an interface from the resource pool configured in it. For automatic configuration of an IPv4 address, you must have uploaded IPv4 address resource pools to Paragon Automation. Otherwise, the IP address is not assigned to the device and the device onboarding fails. See Add Network Resource Pools. If you disable this option, you must assign an IPv4 address for the interface in the network implementation plan. See Add a Network Implementation Plan. |
IPv6 Address | Click to enable or disable (default) the automatic assignment of the IPv6 address for an interface. If you enable this option, Paragon Automation assigns an IPv6 address to an interface from the resource pool configured in it. For automatic configuration of an IPv6 address, you must have uploaded IPv6 address resource pools to Paragon Automation. Otherwise, the IP address is not assigned to the device and the device onboarding fails. See Add Network Resource Pools. If you disable this option, you must assign an IPv6 address for the interface in the network implementation plan. See Add a Network Implementation Plan. |
| Routing Protocols | |
| OSPFv2 | Click to enable or disable (default) OSPF configuration on an IPv4 interface. If you enable OSPF configuration, you can configure the Area ID, Metric, and OSPF MTU for the interface. |
OSPFv3 | Click to enable or disable (default) OSPF configuration on an IPv6 interface. If you enable OSPF configuration, you can configure the Area ID, Metric, and OSPF MTU for the interface. |
| Area Id | Enter the OSPF area ID for an interface. For example, 0.0.0.1. |
| Metric | Enter the OSPF metric for the interface. The OSPF protocol uses the cost metric to determine the best path to a destination. Range: 1 through 65,535 |
| OSPF MTU | Enter the maximum transmission unit (MTU) over the OSPF link configured on the interface. Range: 128 through 65,535 bytes |
| ISIS | Click to enable or disable (default) IS-IS configuration on an interface. If you enable IS-IS, you can configure the IS-IS level, and metric for the interface. |
| Level | Select the IS-IS level:
|
| Metric | Enter the IS-IS metric for the interface. The IS-IS protocol uses the cost metric to determine the best path to a destination. Range: 1 through 16,777,215 |
| LDP | Click to enable or disable (default) LDP configuration on an interface. If you enable LDP, you can enable or disable LDP synchronization for an interface. |
| LDP Synchronization | Click to enable or disable (default) synchronizing LDP with the underlying IS-IS or OSPF protocol to ensure that LSPs are fully established on an IGP path before forwarding traffic through the LSPs. If LDP is not synchronized with the underlying IS-IS or OSPF protocol, packets might be dropped. |
| RSVP | Click to enable or disable (default) RSVP configuration on an interface. If you enable RSVP, you can configure link protection for the interface. You must configure this option if you enable traffic engineering (TE) in the device profile that you applied to a device and apply this profile on an interface on the same device. |
| Link Protection | Click to enable or disable (default) link protection for a tunnel. You must enable link protection if you configure tunnels in the device profile. |
