Default version sometimes not set on upgrading to vManage v20.9

[ssohal]

Hi,

I am doing an upgrade for vManage devices. It does the upgrade but sometimes doesn't set the default version for a specific device.

This issue never happens on downgrade.

"Change Partition action submitted for execution",
"Executing device action Change Partition",
"Checking available software image on the device",
"Activating SW version 17.09.05a.0.XXXX",
"Configured upgrade confirm timer is 15 minutes",
"Sending request to device for Activation of SW version 17.09.05a.0.XXXX",
"Rebooting device to other partition may take up to 30 minutes",
"vManage: Sending upgrade-confirm to device",
"Checking new boot partition",
"Unable to update device-model, Please re-discover before migrate",
"Done - Change Partition"

Has anyone faced the same issue? If so, how was it fixed ?

[Amir567]

It seems like you're encountering an issue where the default version is not always set correctly after upgrading vManage devices to version 20.9. While this issue doesn't occur during downgrades, it's important to address it to ensure the stability and functionality of your network infrastructure.

Here are a few steps you can take to troubleshoot and potentially resolve this issue:

1. Verify Software Compatibility: Ensure that the software version you're upgrading to (v20.9) is fully compatible with your vManage devices and their configurations. Sometimes, compatibility issues can lead to unexpected behavior during upgrades.

2. Check Device Configuration: Review the configuration settings on the affected devices to see if there are any discrepancies or inconsistencies that could be causing the default version not to be set correctly. Pay attention to any specific settings related to software version management.

3. Update Device Models: The error message "Unable to update device-model" suggests that there may be an issue with updating the device model information after the upgrade. Try re-discovering the devices or updating their device models manually to see if that resolves the issue.

4. Review Upgrade Process: Double-check the upgrade process and ensure that all steps are being executed correctly. Pay special attention to any steps related to setting the default version after the upgrade. If necessary, consider adjusting the upgrade process or implementing additional checks to ensure the default version is set properly.

5. Check for Known Issues: Search for any known issues or bugs related to upgrading vManage devices to version 20.9. The vendor's documentation, support forums, or release notes may provide valuable insights or workarounds for resolving this issue.

6. Contact Support: If you're unable to resolve the issue on your own, consider reaching out to the vendor's support team for assistance. They can provide personalized troubleshooting guidance and may be able to offer a solution or workaround based on your specific configuration and environment.

By following these steps and systematically troubleshooting the issue, you should be able to identify the root cause and take appropriate action to resolve it.