Modify Pathfinder Settings From the GUI
In addition to modifying the settings from the CLI, you can also modify the component-specific Pathfinder settings by using the Paragon Automation GUI.
Currently, the Peer Engineering configuration settings are not supported. Although you can modify these settings from the GUI, the changes will not take effect.
To modify the settings from the GUI:
Setting |
Description |
---|---|
Advanced |
|
Sync Network Model |
Click Sync to refresh the synchronization of the network model. You can use this option if the network model audit has unresolved discrepancies or if the information displayed for the model is out of sync. When you sync the network model, this is what happens behind the scenes:
Table 2 describes the effects on various elements in the network when you reset or synchronize the model. |
Reset Network Model |
Warning:
The Reset Network Model operation is typically appropriate for a lab rather than a production environment. We strongly recommend that you perform this action only under the supervision of Juniper Networks Technical Assistance Center (JTAC). There are two circumstances under which you must reset the network model in order to keep the model in sync with the actual network:
When you reset the network model, this is what happens behind the scenes:
Table 2 describes the effects on various elements in the network when you reset or synchronize the model. |
Config Server |
|
Settings |
|
Log Destination |
|
Device Profile Adapter |
|
Settings |
redis-poll-interval—Specify the frequency (in seconds) with which the device profile adapter polls the Redis service for the Redis status. Enter 0 or a negative value to disable this setting. Example: 10s or 10seconds Default: 5s |
Log Destination |
|
Mladapter |
|
Settings |
polling-interval—Specify the polling interval (in seconds) for interfaces without notification support. To disable polling, enter 0. Default: 3600 |
Log Destination |
|
Netconf Connection Controller |
|
Device-Connection Pool |
|
In-memory-Datastore |
|
Infra |
|
Network Data Backend |
backend-connection—From the list, select either folder orin-memory datastore as the backend datastore from which you want to fetch the topology information:
|
Registry |
|
Rpc Service |
workers—Specify the number of threads to be used by the remote procedure call (RPC) service provider. Default: 10 |
Log Destination |
|
Netconfd |
|
Device Connection Pool |
publish-connected-device-status—Specify the interval (in seconds) for publishing the connection status of all the devices managed by netconfd. Default: 0s If you use the default value, the device connection status is not published. |
In-memory Datastore |
|
Infra |
Cache Memory:
|
Network Data Backend |
backend-connection—Select the backend datastore (either folder or in-memory datastore) from which you want to fetch the topology information:
|
Proxy |
workers—Specify the number of threads to be used by the proxy service provider. Default: 10 |
Registry |
check-delay—Specify the delay (in seconds) between checking registered netconfd instances in Redis. Default: 45s |
Log Destination |
|
Path Computation Server |
|
Settings |
|
Analytics |
|
BGP Steering |
|
In Memory Datastore |
|
Link Flap |
|
LSP To Path Computation Instance |
|
Segment Routing Policy |
segment-routing-policy:
|
Log Destination |
|
Path Optimization |
|
Timer |
Specify the frequency (in minutes) with which path optimization is triggered automatically. Note:
The optimization is based on the current network, and not on the most recent Path Analysis report. |
Programmable RPD Client |
|
Settings |
|
Log Destination |
|
System |
|
In Memory Datastore |
|
Messaging Bus |
|
Persistent Datastore |
|
Scheduler |
device-profile-update-interval—Specify the interval (in milliseconds) after which the internal timer in the scheduler polls for device profile updates. Default: 5000 |
Scheduler > Distributed Task Queue |
|
Scheduler > Tasks |
|
Collection Cleanup |
|
Demand Reports |
demand-reports: as-demand-bucket-size—Specify the maximum number of autonomous system (AS) demand report entries that can be stored in the bucket. This parameter isn't required currently but may be required in future releases. Default: 100 |
Device Collection |
|
File Transfer |
|
Rollup |
|
Scheduled LSP Sizing |
|
SNMP Collection |
|
Log Destination |
|
Topology Filter |
|
Data Persistence |
|
Messaging Bus |
|
Persistent Datastore |
|
Log Destination |
|
Topology Server |
|
Application |
|
Application Tuning |
|
Data Persistence |
|
In-memory Datastore |
in-memory-datastore:
|
Messaging Bus |
|
Persistent Datastore |
|
Topology Acquisition |
|
Log Destination |
|
Table 2 lists the effects of resetting or synchronizing the network model.
Element |
Is the element removed from the database? |
Is the item sent back to the controller by the live network? |
Could data be lost? |
|||
---|---|---|---|---|---|---|
Reset |
Sync |
Reset |
Sync |
Reset |
Sync |
|
IP nodes |
Yes |
No |
Yes |
Yes |
Yes for design attributes, such as user-defined node name |
No |
IP links |
Yes |
No |
Yes |
Yes |
Yes for design attributes such as Comment |
No |
PCC-controlled LSPs |
Yes |
No |
Yes |
Yes |
No |
No |
PCC-delegated LSPs |
Yes |
No |
Yes for PCEP attributes |
Yes |
Yes for non-PCEP attributes such as design flags |
No |
PCE-initiated LSPs |
Yes |
No |
Yes for PCEP attributes |
Yes |
Yes for non-PCEP attributes such as design flags |
No |
Multilayer nodes |
Yes |
No |
Yes |
No |
Yes for designed attributes such as user-defined names |
No |
Multilayer links |
Yes |
No |
Yes |
No |
Yes for design attributes such as Comment |
No |
Interlayer links |
Yes |
No |
No |
Yes, links mapped to known nodes are re-sent. |
Yes |
Yes, access links to unknown nodes are lost and need to be recreated |
Multilayer-derived facilities |
Yes |
No |
Yes |
No |
No |
No |
Link-derived facilities |
Yes |
Yes |
Yes |
Yes |
Yes |
Yes |
Ongoing maintenance events |
No |
No |
N/A |
N/A |
No |
No |
Future maintenance events |
Yes |
No |
N/A |
N/A |
Yes |
No |
Ongoing scheduled LSPs |
No |
No |
N/A |
N/A |
Yes (scheduled LSP is never terminated) |
No |
Future scheduled LSPs |
Yes |
No |
N/A |
N/A |
Yes |
No |
Device profiles |
No |
No |
N/A |
N/A |
No |
No |
Router latitude and longitude |
No |
No |
N/A |
N/A |
No |
No |
Router grouping |
No |
No |
N/A |
N/A |
No |
No |
Users table |
No |
No |
N/A |
N/A |
No |
No |
Saved map layout |
No |
No |
N/A |
N/A |
No |
No |
Events |
No |
No |
N/A |
N/A |
No |
No |
Scheduled path optimization |
No |
No |
N/A |
N/A |
No |
No |
Perform this action only under the supervision of JTAC. This action erases the network data model and the data provided through the Add or Modify actions in the network information table (user model data).