Operational Status 802.1x Diagnostics

Operational Status 802.1x Diagnostics

Retrieved Parameters

1) Connection status

    Created another Jira SEBA-807 for Connection status.

2) Number of EAPOL logoff messages received resulting in disconnected state

3) Number of authenticating transitions due to EAP response or identity message

4) Number of authenticated transitions due to successful authentication

5) Number of transitions to aborting due to timeout

    This is already implemented as part of SEBA-623

6) Number of transitions to held due to authentication failure

7) Number of transitions to aborting due to reauthentication request

   Created another Jira SEBA-808 for this, as current code does not support re-auth as per rfc 6696, hence first support for re-auth as to be implemented and then add counter.

8) Number of transitions to aborting due to start request

    As per code there is no aborting logic, the process starts from where it was pending. 

9) Number of transitions to aborting due to logoff request

    There is no aborting logic, the state moves to idle after receiving logoff request. Repeat of req 2.

10) Number of transitions to connecting due to reauthentication request

       Created another Jira SEBA-808 for this, as current code does not support re-auth as per rfc 6696, hence first support for re-auth as to be implemented and then add counter.

11) Number of transitions to connecting due to start request

12) Number of transitions to disconnected due to logoff request

     Repeat of Req 2.

13) Number of access request packets sent

      Already implemented as part of SEBA-37

14) Number of access challenge packets received

      Already implemented as part of SEBA-37

15) Number of EAP request packets sent due to the authenticator choosing the EAP method

16) Number of transitions to response (received response other that NAK)

17) Number of EAP success messages received

       Repeat of Req 4

18) Number of EAP failure messages received

      Repeat of Req 6