Description

User upgrade NXOS-9.3.7 version to NXOS-10.2.5 and the upgrade was succesful. However, after upgrade the device moved to ERROR state with Error :  “Configuration error: the device is active in a blueprint. , yet not classified“ 


Pasted Graphic 3.png
image.png

Symptoms

User has NXOS-9.3.7 version with user defined device profile with regex selector version "7\.0\(3\)I[4-7]\(\w[a-z]?\)|9\.[23]\(\w+\)|10\.[12]\(\d+\)\..* . After the NOS upgrade to NXOS-10.2.5 version the regex selector version was not matching with the actual device OS version. 
 

The regex for the version selector in the used device profile is designed to match specific software version patterns, including specific NOS versions with certain constraints on subsequent characters. However, NXOS version 10.2(5) does not match the current regex. 

Solution

Apstra built-in Device Profiles for Junos, we no longer specify the selector versions but use the relaxed one ".*" . user can do the same changes with the Device Profiles. 

1) Change the regex selector version Globally to ".*"  under devices-->Device profile 
image.png

Edit the DP and changed the Regex selector version and click on update
image.png

2.  Go to the documentation and get the apstra-cli downloaded (Apstra CLI Utility 4.2.1.1)

https://www.juniper.net/documentation/us/en/software/apstra4.2/apstra-user-guide/topics/topic-map/apstra-cli.html

3. Copy the file to your Apstra 4.2.1.1 VM, then install

4. Install the apstra-cli utility with the below docker command 

 

root@aos-server:/home/admin# docker image load -i apstracli-release_4.2.1.15.tar.gz

655ed1b7a428: Loading layer [==================================================>]  129.2MB/129.2MB

a89d1d47b5a1: Loading layer [==================================================>]  11.31MB/11.31MB

9ff6e4d46744: Loading layer [==================================================>]  19.31MB/19.31MB

8d51c618126f: Loading layer [==================================================>]  156.5MB/156.5MB

54acb5a6fa0b: Loading layer [==================================================>]  538.1MB/538.1MB

100796cdf3b1: Loading layer [==================================================>]  19.04MB/19.04MB

3d6eb1152931: Loading layer [==================================================>]  57.98MB/57.98MB

1f123186824c: Loading layer [==================================================>]  4.608kB/4.608kB

bfc1deb8136e: Loading layer [==================================================>]   11.5MB/11.5MB

f0a9360c6dc9: Loading layer [==================================================>]   3.42MB/3.42MB

426a602f8637: Loading layer [==================================================>]  223.6MB/223.6MB

Loaded image: apstracli:release_4.2.1.15

root@aos-server:/home/admin#


5. Execute the below Docker CLi to access the apstra-cli 

 

root@aos-server:/home/admin# docker run --rm -ti -v ~:/mytmp apstracli:release_4.2.1.15 -s 10.28.9.3

Password [admin]:

Welcome to Juniper Apstra CLI! Press TAB for suggestions

Juniper Apstra CLI version: release-4.2.1.15

Juniper Apstra Server URL: https://10.28.9.3:443, Version: 4.2.1.1-10

apstra-cli>

 

6. Update the selector information for the device profile in the blueprint. 
 

apstra-cli> blueprint --blueprint 1f3d4fd0-4b80-4c6b-8bbd-3847de38ffbf set-node-property --node_type device_profile --node w33Aenz7mT86uTuGmXQ --property selector --value-fn '{"os_version": ".*","model":"C93108TC-EX","os": "NXOS","manufacturer

": "Cisco"}'

Successfully queued task to update node w33Aenz7mT86uTuGmXQ property selector to {'os_version': '.*', 'model': 'C93108TC-EX', 'os': 'NXOS', 'manufacturer': 'Cisco'}

apstra-cli>


Now go to Apstra GUI and check the uncommited tab to see the changes done through apstra-cli.

image.png
7. Just flip the status of the device from deployed to undeployed and serial number and vice versa in blueprint without doing the commit in the staged tab will remove the error from the state column in the managed device section



After remove the serial and undeploy the device click on update assignment.

image.png

Deploy the device back and assign the serial 

image.png


8. Now check the state under ,managed device. Device will move from ERROR to Is-Active. 

Modification History

Review and validation done 

Proper screenshot attached 

Modified the category from all to Apstra intent based on 2025:01:28

Removed partner assistance on 2025:01:29