Clarification on Bfd up-transitions and failure-transitions.

[AnilKR123]

In the GNMI Path: /openconfig-bfd:bfd/interfaces/interface/peers, the state container contains an attribute “failure-transitions” that tracks the number of times that the BFD session has transitioned out of the UP state. In the echo and async sub-containers, there is an attribute for “up-transitions”, which tracks the number of times that the adjacency with the neighbor has transitioned into the UP state." I would like some clarification as to why the failure-transitions are tracked as one attribute in the state container, while there are 2 attributes tracking up-transitions, one for echo and the other for async.

[dplore]

Hi @AnilKR123, I don't see a history where this is explained. However, it looks unintentional to me?

I would expect to see

/bfd/interfaces/interface/peers/peer/state/failure-transitions
/bfd/interfaces/interface/peers/peer/state/up-transitions

I don't think these leaves are relevant as I think the session state would be reported at the /bfd/interfaces/interface/peers/peer/state container and not within the mode container?

/bfd/interfaces/interface/peers/peer/state/echo/up-transitions	
/bfd/interfaces/interface/peers/peer/state/async/up-transitions	

If you would like to see this change, please feel free to submit a pull request for review

[AnilKR123]

Hi Darren,

I submitted a pr to address this: #1252

Thanks,

Anil