Open Tessier-Ashp001 opened 3 years ago
@Tessier-Ashp001 Thanks for raising this issue. We are investigating this option and will reply back soon.
@mmudigon Can you look into this?
Resolved in latest release version
Did not mean to close this. Re-opening.
That's brilliant, thanks @mikewiebe !
That's brilliant, thanks @mikewiebe !
@Tessier-Ashp001 I did not mean to close this earlier. This issue is still open as we explore options for this.
@Tessier-Ashp001 Just double checking again... Did you mean to close this issue?
Hi @mikewiebe . I did. Now I haven't tested this yet and won't be able to until the weekend, so I'll maybe keep this one open for the moment if that's OK. Just to confirm, it's the latest develop branch that I should use?
Also, do the following variables in the above example now get applied to both the port-channel as well as the member ports, or do I need to define the member ports descriptions elsewhere?:
peer1_description: "VPC acting as trunk peer1"
peer2_description: "VPC acting as trunk peer2"
I can't seem to find where the member port descriptions get applied in the dcnm_interface.py file..
Thanks
@Tessier-Ashp001 We have not fixed this yet. I accidentally closed this issue but re-opened it when I realized I had closed the wrong issue. We are still discussing as a team on the best way to handle this request so there is nothing to test at the moment :-).
Sorry for the confusion!
Hi All,
Just wondering if there has been any progress or if this issue is still being worked !!!
Thanks
Possible feature request?
Is it possible to apply a description to a physical interface that is a member of a vPC? There is a description option present for vPC config but this applies to the port-channel itself rather than the member port.
I am following the example:
Thanks...