Laine Stump <laine@laine.org> wrote on 12/21/2015 12:17:54 PM:
This does cause a difference in behavior, so I want confirmation from Cisco and IBM that this behavior change is desired (or at least not *un*desired) - rather than returning with status unchanged (and thus always 0, aka PORT_VDP_RESPONSE_SUCCESS) when instanceId is NULL, it will actually get the IFLA_PORT_RESPONSE. This could lead to revelation of error conditions we were previously ignoring. Or not. Only experimentation will tell. Note that for 802.1Qbg instanceId is *always* NULL, and for 802.1Qbh, it is NULL for all DISASSOCIATE commands.
I have forwarded this request to others who have the hardware to test with, though this may take some time to get an answer back... Stefan