Merged
Conversation
Author
|
No progress was made with versions older than 22; however, I believe it could still be merged, as it works properly with more recent versions. I will be moving it from draft to ready for review |
Member
|
thanks @rafabr let's roll it |
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
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.
This current implementation was tested and is working with the following images (EXOS images are easily found in the official Extreme Networks github page):
EXOS-VM_v22.4.1.4-disk1.qcow2EXOS-VM_v32.6.3.126.qcow2This implementation also partially worked with older versions of EXOS (tested with
EXOS-VM_v16.1.1.4-disk1.qcow2andEXOS-VM_v21.1.1.4-disk1.qcow2). The bootstrap and initial configuration were successfully applied, and SSH access was possible. However, testing showed high latency and packet loss during ping tests between hosts.If anyone with more experience in emulating these systems could provide insights or suggestions to help resolve the connectivity issues, it would be greatly appreciated.
Notes:
STARTUP-CONFIGfile should ideally be in the .xsf format. However, the current implementation temporarily supports only the .cfg format to facilitate testing using existing kinds.xsffile contains a command that attempts to configure the management VLAN's ipaddress, the system will log an error and skip the command. I'm assuming that the IP configuration from the bootstrap config should take precedence over the provided configuration.upload configcommand to save the system configuration will generate an.xsffile that contains lines which may cause errors during import with theload scriptcommand. However, the system will continue applying the configuration while ignoring these errors. Attempts to clear all configurations before importing did not resolve the issue, and I'm assuming that those familiar with EXOS are aware of this limitation.Discord
Discussion thread in discord