ON THIS PAGE
Network Implementation Plan Device Configuration
The Junos commands documented in this topic represent the device-level configuration that is automatically generated and committed by the Routing Director GUI as part of the Network Implementation Plan workflow. These commands correspond to configuration actions performed in the General, Devices, Physical Ports, and Logical Interfaces sections of the onboarding process described in the Add a Network Implementation Plan topic. As you configure device properties, interfaces, routing protocols, link aggregation groups (LAGs), loopbacks, and other network attributes through the GUI, Routing Director translates those inputs into the Junos configuration commands shown in the following sections and commits them to the managed devices.
The commands listed in this topic are configured under the
paragon-service-orchestration group.
System Configuration
The following commands are generated when device-level properties such as hostname, user accounts, and accounting settings are configured in the Devices > General Infrastructure Configuration use case section of the Network Implementation Plan workflow. These settings establish the basic identity and management configuration of the device.
Hostname
set system host-name <HOSTNAME>
Interface Configuration
The following commands are generated when physical or logical interfaces are configured through the Devices > Physical Ports, Infrastructure Configuration, and Logical Interfaces sections. Interface attributes such as descriptions, IP addressing, MTU values, and protocol families are translated into the Junos interface configuration shown below.
IPv4
set interfaces <INTERFACE_NAME> unit <UNIT_ID> description "<DESCRIPTION>" set interfaces <INTERFACE_NAME> unit <UNIT_ID> family inet address <IPV4_ADDRESS>
IPv6
set interfaces <INTERFACE_NAME> unit <UNIT_ID> family inet6 address <IPV6_ADDRESS>
Tagged Interfaces
set interfaces <INTERFACE_NAME> flexible-vlan-tagging set interfaces <INTERFACE_NAME> encapsulation flexible-ethernet-services
MTU
set interfaces <INTERFACE_NAME> mtu <MTU>
IS-IS Enablement
This is configured when IS-IS is enabled in the Interface Profile.
set interfaces <INTERFACE_NAME> unit <UNIT_ID> family iso
Link Aggregation Group (LAG)
The following commands are generated when Aggregated Ethernet (AE) interfaces, minimum link requirements, and member links are configured in the Physical Ports > LAG Parameters section of the network implementation plan.
Aggregated Ethernet Interface
set interfaces <AE_INTERFACE> aggregated-ether-options minimum-links <MINIMUM_LINKS>
Member Interface
set interfaces <AE_MEMBER_INTERFACE> gigether-options 802.3ad <AE_INTERFACE>
Member Interface (Junos EVO)
set interfaces <AE_MEMBER_INTERFACE> ether-options 802.3ad <AE_INTERFACE>
Chassis Configuration
set chassis aggregated-devices ethernet device-count <LAG_DEVICE_COUNT>
Loopback Interfaces
The following commands are generated when IPv4 and IPv6 loopback addresses are configured on a device as part of the Infrastructure Configuration settings during onboarding. These addresses are typically used for router IDs, protocol endpoints, and management functions.
set interfaces lo0 unit 0 family inet address 127.0.0.1/32 set interfaces lo0 unit 0 family inet address <LOOPBACK_IPV4>/32 set interfaces lo0 unit 0 family inet6 address ::1/128 set interfaces lo0 unit 0 family inet6 address <LOOPBACK_IPV6>/128 set interfaces lo0 unit 0 family iso address <ISO_NET>
Routing Options
The following commands are generated when routing attributes such as the router ID, autonomous system number, and forwarding behavior are configured through device-level infrastructure settings in the Device Profile page (Inventory > Devices > Device and Interface Profiles > Add > Device Profile).
Router ID
set routing-options router-id <ROUTER_ID>
Autonomous System Number
set routing-options autonomous-system <AS_NUMBER>
Per Flow Load Balancing
set routing-options forwarding-table export pso-per-packet-load-balancing
Policy Options
The following commands are generated when the onboarding workflow enables traffic-engineering, BGP-LS originator, or load-balancing features that require supporting policy definitions. These policies are automatically created and referenced by the associated protocol configurations.
Accept All
set policy-options policy-statement pso-accept-all then accept
Accept Link State
set policy-options policy-statement pso-accept-link-state then accept
Per-Packet Load Balancing Policy
set policy-options policy-statement pso-per-packet-load-balancing then load-balance per-packet
Forwarding Options
The following commands are generated when platform-specific per-flow load-balancing and packet-hashing behavior is configured. These settings control how traffic is distributed across available forwarding paths. These are configured only on ACX Series routers.
set forwarding-options hash-key family inet layer-3 set forwarding-options hash-key family inet6 layer-3 set forwarding-options hash-key family mpls label-1 set forwarding-options hash-key family multiservice
BGP Configuration
The following commands are generated when BGP peerings, route reflector settings, address families, and BGP-LS capabilities are configured through device properties on the Device Profile page (Inventory > Devices > Device and Interface Profiles > Add > Device Profile).
Internal Group
set protocols bgp group <BGP_GROUP_NAME> type internal set protocols bgp group <BGP_GROUP_NAME> local-address <LOCAL_ADDRESS> set protocols bgp group <BGP_GROUP_NAME> peer-as <PEER_AS>
External Group
set protocols bgp group <BGP_GROUP_NAME> type external set protocols bgp group <BGP_GROUP_NAME> peer-as <PEER_AS>
Neighbor
set protocols bgp group <BGP_GROUP_NAME> neighbor <PEER_IP>
Optional:
set protocols bgp group <BGP_GROUP_NAME> neighbor <PEER_IP> peer-as <PEER_AS> set protocols bgp group <BGP_GROUP_NAME> neighbor <PEER_IP> local-address <LOCAL_ADDRESS>
Address Families
set protocols bgp group <BGP_GROUP_NAME> family inet unicast set protocols bgp group <BGP_GROUP_NAME> family inet labeled-unicast set protocols bgp group <BGP_GROUP_NAME> family inet6 unicast set protocols bgp group <BGP_GROUP_NAME> family inet6 labeled-unicast
EVPN
set protocols bgp group <BGP_GROUP_NAME> family evpn signaling
L2VPN
set protocols bgp group <BGP_GROUP_NAME> family l2vpn signaling
VPNv4
set protocols bgp group <BGP_GROUP_NAME> family inet-vpn unicast
VPNv6
set protocols bgp group <BGP_GROUP_NAME> family inet6-vpn unicast
Traffic Engineering
set protocols bgp group <BGP_GROUP_NAME> family traffic-engineering unicast
Route Reflector
set protocols bgp group <BGP_GROUP_NAME> cluster <RR_CLUSTER_ID>
BGP-LS Export
set protocols bgp group <BGP_GROUP_NAME> export pso-accept-link-state
PCEP Configuration
The following commands are generated when a Path Computation Element (PCE) is associated with the device and PCEP-based traffic-engineering functions are enabled on the Device Profile page (Inventory > Devices > Device and Interface Profiles > Add > Device Profile). These settings establish communication between the device and the external path controller.
PCE Definition
set protocols pcep pce pso-pce-server destination-ipv4-address <PCE_ADDRESS> set protocols pcep pce pso-pce-server destination-ipv6-address <PCE_ADDRESS>
Active Stateful PCE
set protocols pcep pce pso-pce-server pce-type active set protocols pcep pce pso-pce-server pce-type stateful
Traffic Steering
set protocols pcep pce pso-pce-server pce-traffic-steering
Authentication
set protocols pcep pce pso-pce-server authentication-key "<PCE_AUTH_KEY>"
Segment Routing Capability
set protocols pcep pce pso-pce-server spring-capability set protocols pcep pce pso-pce-server max-sid-depth <SID_DEPTH>
Segment Routing PCEP Integration
The following command is generated when Segment Routing with an external controller is enabled as part of the traffic-engineering configuration on the Device Profile page (Inventory > Devices > Device and Interface Profiles > Add > Device Profile). This setting allows the device to receive and act upon controller-provided paths.
set protocols source-packet-routing lsp-external-controller pccd
Segment Routing (SPRING)
The following commands are generated when Segment Routing is enabled and associated with an IGP such as OSPF or IS-IS on the Device Profile page (Inventory > Devices > Device and Interface Profiles > Add > Device Profile). These settings define SRGB ranges, node SIDs, and prefix SIDs that are advertised throughout the network.
SRGB
set protocols isis source-packet-routing srgb start-label <SRGB_START_LABEL> set protocols isis source-packet-routing srgb index-range <SRGB_RANGE>
Node SID
set protocols isis source-packet-routing node-segment <NODE_SID>
IPv4 Prefix SID
set protocols isis source-packet-routing ipv4-index <IPV4_PREFIX_SID>
IPv6 Prefix SID (IS-IS)
set protocols isis source-packet-routing ipv6-index <IPV6_PREFIX_SID>
OSPF Configuration
The following commands are generated when OSPF areas, interface assignments, metrics, and related protocol parameters are configured for logical interfaces on the Interface Profile page (Inventory > Devices > Device and Interface Profiles > Add > Interface Profile). These settings establish OSPF neighbor relationships and topology advertisement behavior.
Area Definition
set protocols ospf area <OSPF_AREA> interface <INTERFACE_NAME>
Interface Metric
set protocols ospf area <OSPF_AREA> interface <INTERFACE_NAME> metric <OSPF_METRIC>
LDP Synchronization
set protocols ospf area <OSPF_AREA> interface <INTERFACE_NAME> ldp-synchronization
Loopback Passive
set protocols ospf area <OSPF_AREA> interface lo0.0 passive
OSPFv3 Configuration
The following command is generated when OSPFv3 is enabled for IPv6 routing on configured interfaces and associated OSPF areas. This setting controls IPv6 routing adjacency formation and route exchange.
set protocols ospf3 area <OSPF_AREA> interface <INTERFACE_NAME>
IS-IS Configuration
The following commands are generated when IS-IS is enabled on device interfaces and corresponding protocol parameters are defined on the Interface Profile page (Inventory > Devices > Device and Interface Profiles > Add > Interface Profile). These settings establish IS-IS adjacencies and support MPLS and Segment Routing deployments.
Enable Loopback
set protocols isis interface lo0.0 passive
Interface Enablement
set protocols isis interface <INTERFACE_NAME>
Point-to-Point
set protocols isis interface <INTERFACE_NAME> point-to-point
LDP Synchronization
set protocols isis interface <INTERFACE_NAME> ldp-synchronization
Metrics
set protocols isis interface <INTERFACE_NAME> level 1 metric <ISIS_LEVEL_METRIC> set protocols isis interface <INTERFACE_NAME> level 2 metric <ISIS_LEVEL_METRIC>
LDP Configuration
The following commands are generated when Label Distribution Protocol (LDP) is enabled on loopback and network-facing interfaces on the Interface Profile page (Inventory > Devices > Device and Interface Profiles > Add > Interface Profile). These settings allow MPLS label exchange between participating routers.
set protocols ldp interface lo0.0 set protocols ldp interface <INTERFACE_NAME> set protocols ldp family inet set protocols ldp family inet6
RSVP Configuration
The following commands are generated when RSVP-based traffic engineering is enabled on selected interfaces on the Interface Profile page (Inventory > Devices > Device and Interface Profiles > Add > Interface Profile). Interface-level settings such as link protection are translated into the Junos configuration shown below.
Enable Interface
set protocols rsvp interface <INTERFACE_NAME>
Link Protection
set protocols rsvp interface <INTERFACE_NAME> link-protection
MPLS Configuration
The following commands are generated when MPLS forwarding, traffic engineering, external path control, or label-switched paths (LSPs) are configured through the Routing Protocols tab of the network implementation plan. These settings enable MPLS services and traffic-engineering capabilities across the network.
Enable MPLS Interfaces
set protocols mpls interface <INTERFACE_NAME>
Auto-Bandwidth Statistics
set protocols mpls statistics auto-bandwidth
External Controller
set protocols mpls lsp-external-controller pccd
TED Import Policy
set protocols mpls traffic-engineering database import policy pso-accept-all
MPLS Enablement
When the device has LDP, RSVP, OSPF, or segment routing configured, then the MPLS family is also configured.
set interfaces <INTERFACE_NAME> unit <UNIT_ID> family mpls
Traffic Engineered LSPs
The following commands are generated when RSVP-TE or controller-based tunnels are defined in the Routing Protocols tab of the network implementation plan. LSP parameters such as destination, bandwidth, protection mode, and auto-bandwidth settings are converted into device-specific Junos configuration.
Static Bandwidth
set protocols mpls label-switched-path <LSP_NAME> to <LSP_DESTINATION> set protocols mpls label-switched-path <LSP_NAME> bandwidth <BANDWIDTH>
Auto-Bandwidth
set protocols mpls label-switched-path <LSP_NAME> auto-bandwidth
Fast Reroute
set protocols mpls label-switched-path <LSP_NAME> fast-reroute
Link Protection
set protocols mpls label-switched-path <LSP_NAME> link-protection
Node-Link Protection
set protocols mpls label-switched-path <LSP_NAME> node-link-protection
IPv6 Tunneling
set protocols mpls label-switched-path <LSP_NAME> ipv6-tunneling
Verification Commands
After Routing Director commits the configuration to the managed device, the following operational commands can be used to verify that the intended configuration has been successfully applied and that the associated protocols and services are functioning as expected.
show configuration show interfaces terse show chassis aggregated-devices show route summary show bgp summary show ospf neighbor show ospf3 neighbor show isis adjacency show ldp session show rsvp interface show mpls lsp show pcep session show source-packet-routing