diff options
| author | Fernando Soto <fsoto@bluecatnetworks.com> | 2015-05-11 22:52:00 +0200 |
|---|---|---|
| committer | Daniel Walton <dwalton@cumulusnetworks.com> | 2016-05-26 17:33:31 +0200 |
| commit | 66239ca6fe4e688b1069f293f3248004e4934d35 (patch) | |
| tree | da4c009bda31ac726c7cd307b8b9406196b81115 /lib | |
| parent | ospfd: Fix bug in 94266fa822ba, nbr_self rebuild didn't add valid nbr_self (diff) | |
| download | frr-66239ca6fe4e688b1069f293f3248004e4934d35.tar.xz frr-66239ca6fe4e688b1069f293f3248004e4934d35.zip | |
ospfd: trap on state change seems to send incorrect value for ospfNbrState
The ospfNbrState in the ospf trap sent from ospfd shows an incorrect state.
For example, when the connection goes down, the ospfNbrState in the trap is
sent as '8' (full). When the connection is reestablished, the state is sent
as '7' (loading).
The reason seems to be that the trap is sent from nsm_notice_state_change()
before the state is actually updated by calling nsm_change_state().
After applying the attached patch, the traps are sent with nbrState '1' when
the connection goes down and '8' when it goes back up.
Bugzilla #833 https://bugzilla.quagga.net/show_bug.cgi?id=833
(cherry picked from commit b6404390a713144252b62f49a328315d1952c6d8)
Diffstat (limited to 'lib')
0 files changed, 0 insertions, 0 deletions