Skip to content
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

Monitor all configured IP addresses for an IP device #1184

Closed
jmbredal opened this issue Jan 17, 2017 · 2 comments
Closed

Monitor all configured IP addresses for an IP device #1184

jmbredal opened this issue Jan 17, 2017 · 2 comments

Comments

@jmbredal
Copy link
Collaborator

jmbredal commented Jan 17, 2017

This is a feature request originally from DeiC, the Danish research network (not verbatim). This should be seen in conjunction with the feature request described in bug 1300604:

The status monitor (pping) only monitors the IP address registered
with the IP device. In the case of routers, ipdevpoll will have collected
a number of IP addresses through snmp polling (then registered
in the gwportprefix.gwip field).

This enhancement to pping is to monitor all the gwip addresses in addition.
This will in effect cover all IPv4 and IPv6 configured on the IP device. This
should be a configurable enhancement for pping.conf.

A new stateful event should be used; "IP address reachability" with
states "IP address unreachable" and "IP address reachable". Perhaps
this should be complemented with "IP address in shadow".

When "Dual stack monitoring" for hosts is implemented the "IP address
reachability" pping monitoring should also cover registered secondary host
addresses.


Imported from Launchpad using lp2gh.

@jmbredal jmbredal added ipv4 ipv6 nav-ref Fronted by the NAV user reference committee New pping labels Jan 17, 2017
@jmbredal
Copy link
Collaborator Author

Partly implemented by #1130

@jmbredal jmbredal removed the nav-ref Fronted by the NAV user reference committee label Apr 27, 2017
@lunkwill42
Copy link
Member

We have decided to merge this with #1130, since their implementation is essentially the one and the same.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants