-
Notifications
You must be signed in to change notification settings - Fork 84
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
updated lfm discovery state enums and trigger msg #957
base: jcloud
Are you sure you want to change the base?
Conversation
enumerate "Send Local Remote Ok" as 3; | ||
enumerate "Fault" as -1; | ||
enumerate "Active Send Local" as 3; | ||
enumerate "Passive Wait" as 4; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do not change enums for already present states
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also can you confirm that state anything > 1 is a good state?
@@ -67,15 +85,15 @@ healthbot { | |||
then { | |||
status { | |||
color green; | |||
message "$lfm-interface-name LFM discovery-state: $lfm-discovery-state; lfm-status: $lfm-status; lfm-peer-address: $lfm-peer-address"; | |||
message "$lfm-interface-name LFM discovery-state: $lfm-discovery-state; lfm-status: $lfm-status"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If peer address is not used anywhere can we remove the field? Please confirm with Venakt.
updated enums as per the below link https://opengrok.juniper.net/source/xref/DEV_COMMON_BRANCH/junos/usr.sbin/lfmd/lfmd_discovery.c?r=1178985#291