Description

The Juniper Apstra Device Pristine Configuration is created when a user acknowledges a device in the Juniper Apstra Managed Devices list. The Pristine Configuration is restored to a device when the device is removed from a Juniper Apstra Blueprint or temporarily when a device is upgraded.

For Arista devices running EOS 4.22, the 'service routing protocols model multi-agent' configuration command is required to run EVPN. The configuration also requires a device reboot to apply the configuration.

localhost(config)# service routing protocols model multi-agent
! Change will take effect only after switch reboot
localhost(config)#

Juniper Apstra will automatically add this command to the device when EVPN is configured from Juniper Apstra. However, it will not be added to the Pristine Configuration. The user will need to manually reboot the device.

This article provides more details.

Symptoms

If a user does not have the 'service routing protocols model multi-agent ' configuration in the Device Pristine Configuration and the user does an EOS upgrade from Juniper Apstra, after the upgrade, the device will have lost the  service routing protocols model multi-agent   configuration.

l2-virtual-ext-001-leaf1# show bgp evpn summary
% Not supported
l2-virtual-ext-001-leaf1#

Solution

To ensure that the service routing protocols model multi-agent configuration is active on the device through the Juniper Apstra EOS Upgrade process, verify that the configuration is in the Juniper Apstra Device Pristine Configuration.

Workflow

  • From Devices > Managed Devices, select the device and then click the Pristine Config tab.

  • Check the configuration for service routing protocols model multi-agent . It should be below the transceiver configuration:

alt

  • If the service routing protocols model multi-agent configuration does not exist, manually add this via the Juniper Apstra UI by clicking the " Edit pristine config " icon, adding the service routing protocols model multi-agent configuration, and then clicking Update .

alt

  • Alternatively, use the Apstra-CLI system pristine_config_append command to append the service routing protocols model multi-agent configuration.

⚠️ CAUTION: This command will only append the configuration. If any incorrect configuration is appended, the user will need to manually correct the pristine configuration for each device from the Juniper Apstra UI.

  • First, create a text file with the service routing protocols model multi-agent   configuration.

user-mbp:~ $ cat multi-agent.txt
service routing protocols model multi-agent
 user-mbp:~ $

  • Second, use the Apstra-CLI system pristine_config_append command to append the text from the file to the pristine configuration. The user can use the --ip option to specify a range of device IP addresses.

    apstra-cli>  system pristine_config_append --ip 172.20.61.6-11 --file /project/multi-agent
    Updated pristine config for spine1:172.20.61.6
    Updated pristine config for spine2:172.20.61.7
    Updated pristine config for l2-virtual-ext-001-leaf1:172.20.61.8
    Updated pristine config for l2-virtual-ext-002-leaf1:172.20.61.9
    Updated pristine config for l2-virtual-ext-003-leaf1:172.20.61.10
    Updated pristine config for l2-virtual-ext-004-leaf1:172.20.61.11
    apstra-cli>

 

  • “Force Update?” option has been introduced in Apstra 4.2 UI. In ApstraCLI, "--force-update True" option is now available for the same. 
apstra-cli> system pristine_config_append --ip 172.20.61.6-11 --file /project/multi-agent.txt --force-update True 

Modification History

update 1) AOSCLI -> ApstraCLI, aos -> apstra-cli 
update 2) add the following in the solution section

“Force Update?” option has been introduced in Apstra 4.2 UI. In ApstraCLI, "--force-update True" option is now available for the same. 
apstra-cli> system pristine_config_append --ip 172.20.61.6-11 --file /project/multi-agent.txt --force-update True