Dev - Danny - Updates implemented at Vodafone NZ for discovery/save/load#44
Open
DYeag wants to merge 11 commits intoQualiSystems:devfrom
Open
Dev - Danny - Updates implemented at Vodafone NZ for discovery/save/load#44DYeag wants to merge 11 commits intoQualiSystems:devfrom
DYeag wants to merge 11 commits intoQualiSystems:devfrom
Conversation
At vodafone it was seen that a device was not able to respond to snmpget but snmpwalks over the same range were able to get the value. Their Huawei contact that looked at the issue insisted there was no issue and it was somehow user error of some sort. To avoid this, I instead got the tables and then referenced them in the function instead of individually snmpgetting each value.
return from execute flow contained a number of spaces in front of the actual value. caused issues in the commands being run on the device using this value.
Missing a positive response 'complete.'
setup_startup_config function was running 'SAVE_RUNNING' instead of 'SAVE_STARTUP'. Was overwriting existing saved config instead of restoring.
{dst} changed to {dst_file} to match input from restore flow.
Reboot was seeming to not occur on some devices, needed a positive response to some checks. I believe in this case it was asking for confirmation that a new startup configuration was intended to hae been set.
Some devices were having issues saving the configuration file. The only method I found that worked for all devices was to remove the file_system from the path.
The devices were not able to load the configurations because they did not have the correct file extension, required some configuration extension. Added .cfg here so the files would be saved with the extension.
The devices were having an issue trying to restore the configurations. The issue was caused because we were saving the configuration to "quali_run_config.cfg" then copying it over to a new file. This was causing some reference to not be created internally on the device to allow the file to be loaded as a valid configuration.
Same reason as for save_flow. The only way that finding the correct file on the device worked on all devices was to remove the file_system from the file path.
.cfg or other config file extension was required in order for a configuration file to be set as the startup configuration.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These are the changes that I have implemented at Vodafone NZ and have soon to be working with the devices they currently have loaded into CloudShell. Each Commit addresses a specific issue which is described in the commit description that should help you think of a way to implement the fix in a better way. Let me know if you have any specific questions as I do still have access to these Huawei devices.