-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Calls to brocade_interface_fibrechannel returns inconsistent data structures for 'neighbors' #136
Comments
Here is my test case:
|
This issue is addressed in FOS switch release 9.2.1 as shown below: [ONE ENTRY] [TWO ENTRIES] |
If there are no further issues, please suggest if we can close this issue. |
1 similar comment
If there are no further issues, please suggest if we can close this issue. |
The brocade.fos.brocade_interface_fibrechannel module returns flogis in 3 different forms. This requires a lot of extra coding to audit the switches since there are 3 special cases to deal with.
When there are multiple flogis, you get a result that is straight-forward to access in the general case:
If a port has no flogis, you get something like this:
When it has one flogi you'll get:
It would be a lot easier to extract the data if the data structure was consistent:
Please consider adjusting the data structures for the no-flogi and single-flogi cases to match the multi-flogi (NPIV) case.
The text was updated successfully, but these errors were encountered: