Closed pdellaert closed 8 years ago
@t00f I see the vsgredundantport still is not present in 3.2 specs... That means the 3.2 VSPK is still unable to handle redundant ports on VSG redundancy groups. This needs to be addressed as we do need it in some scripts/tools
I added another 'bugfix' the gatewayPeer2ID is not present in the redundancygroup spec
This is a new entity for MC lag support. VSGs are now redundant pairs and they created a a new port type 'VsgRedundantPort'