Cannot add Device by IP Address but can by hostname
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote:
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers, Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio joseph@nyi.net wrote:
It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote:
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers, Ivan
On 6 May 2016 at 08:29, Ivan Jukic ijukic13@gmail.com wrote:
I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers, Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio joseph@nyi.net wrote:
It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote:
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
As far as I know, hostnames are strictly required for Observium to talk to a device. If you cannot get DNS records set, or implement some sort of customized DNS server setup, you will have to use /etc/hosts entries (which is basically a custom DNS server setup, just not as elegant/flexible... and its probably somewhat slower when dealing with a lot of addresses).
Observium can't resolve an IP to an IP because it isn't a hostname. Host file (and DNS A/AAAA record) lookups don't work "backwards" like that.
Also, a hosts file pre-filled with a generically syntaxed hostname for each IP address within any of the subnets which you wish to monitor would pretty much never have to be updated. If you ever have any new IP ranges come into play, you would simply have to append the generic entries for it to the hosts file. What else would there be to manage/maintain? It certainly wouldn't require a full-time role.
If you did this, anytime you have a device on an IP without a DNS record, you could add it with the generic hostname.
The only other option would be to do some pretty involved patching of your Observium install, which almost assuredly WOULD be a nightmare to maintain.
On 05/05/2016 07:02 PM, Ivan Jukic wrote:
The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers, Ivan
On 6 May 2016 at 08:29, Ivan Jukic <ijukic13@gmail.com mailto:ijukic13@gmail.com> wrote:
I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address? Cheers, Ivan On 6 May 2016 at 08:21, Joseph Zancocchio <joseph@nyi.net <mailto:joseph@nyi.net>> wrote: It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames. On 05/05/2016 05:41 PM, Ivan Jukic wrote:Hi All, I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed. Is there a way I can simply add a whole subnet range to Observium without using hostname? Cheers, Ivan _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium_______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Yeah, you adding it by hostname has absolutely nothing to do with you trying to add it by IP address, it simply won't work. Like what Joseph said, you need to get generic DNS entries in via some method (DNS server, /etc/hosts)
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Fri, May 6, 2016 at 8:48 AM, Joseph Zancocchio joseph@nyi.net wrote:
As far as I know, hostnames are strictly required for Observium to talk to a device. If you cannot get DNS records set, or implement some sort of customized DNS server setup, you will have to use /etc/hosts entries (which is basically a custom DNS server setup, just not as elegant/flexible... and its probably somewhat slower when dealing with a lot of addresses).
Observium can't resolve an IP to an IP because it isn't a hostname. Host file (and DNS A/AAAA record) lookups don't work "backwards" like that.
Also, a hosts file pre-filled with a generically syntaxed hostname for each IP address within any of the subnets which you wish to monitor would pretty much never have to be updated. If you ever have any new IP ranges come into play, you would simply have to append the generic entries for it to the hosts file. What else would there be to manage/maintain? It certainly wouldn't require a full-time role.
If you did this, anytime you have a device on an IP without a DNS record, you could add it with the generic hostname.
The only other option would be to do some pretty involved patching of your Observium install, which almost assuredly WOULD be a nightmare to maintain.
On 05/05/2016 07:02 PM, Ivan Jukic wrote:
The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers, Ivan
On 6 May 2016 at 08:29, Ivan Jukic ijukic13@gmail.com wrote:
I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers, Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio < joseph@nyi.net joseph@nyi.net> wrote:
It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote:
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
First port of call would be to fire the people installing devices important enough to need monitoring without hostnames...
adam.
Sent from Mailbird [http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm...] On 06/05/2016 15:00:36, Spencer Ryan sryan@arbor.net wrote: Yeah, you adding it by hostname has absolutely nothing to do with you trying to add it by IP address, it simply won't work. Like what Joseph said, you need to get generic DNS entries in via some method (DNS server, /etc/hosts)
Spencer Ryan | Senior Systems Administrator | sryan@arbor.net [mailto:sryan@arbor.net] Arbor Networks +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com [http://www.arbornetworks.com/]
On Fri, May 6, 2016 at 8:48 AM, Joseph Zancocchio <joseph@nyi.net [mailto:joseph@nyi.net]> wrote:
As far as I know, hostnames are strictly required for Observium to talk to a device. If you cannot get DNS records set, or implement some sort of customized DNS server setup, you will have to use /etc/hosts entries (which is basically a custom DNS server setup, just not as elegant/flexible... and its probably somewhat slower when dealing with a lot of addresses).
Observium can't resolve an IP to an IP because it isn't a hostname. Host file (and DNS A/AAAA record) lookups don't work "backwards" like that.
Also, a hosts file pre-filled with a generically syntaxed hostname for each IP address within any of the subnets which you wish to monitor would pretty much never have to be updated. If you ever have any new IP ranges come into play, you would simply have to append the generic entries for it to the hosts file. What else would there be to manage/maintain? It certainly wouldn't require a full-time role.
If you did this, anytime you have a device on an IP without a DNS record, you could add it with the generic hostname.
The only other option would be to do some pretty involved patching of your Observium install, which almost assuredly WOULD be a nightmare to maintain.
On 05/05/2016 07:02 PM, Ivan Jukic wrote:
The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers,
Ivan
On 6 May 2016 at 08:29, Ivan Jukic <ijukic13@gmail.com [mailto:ijukic13@gmail.com]> wrote:
I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers,
Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio < [mailto:joseph@nyi.net]joseph@nyi.net [mailto:joseph@nyi.net]> wrote:
It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote:
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers,
Ivan
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org [mailto:observium@observium.org] http://postman.memetic.org/cgi-bin/mailman/listinfo/observium [http://postman.memetic.org/cgi-bin/mailman/listinfo/observium]
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
Is adding devices via IP Address not the important to Observium Devs? I thought it would be a given, since many NMS platforms do this?
Cheers, Ivan
On 6 May 2016 at 23:12, Adam Armstrong adama@memetic.org wrote:
First port of call would be to fire the people installing devices important enough to need monitoring without hostnames...
adam.
Sent from Mailbird http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 06/05/2016 15:00:36, Spencer Ryan sryan@arbor.net wrote: Yeah, you adding it by hostname has absolutely nothing to do with you trying to add it by IP address, it simply won't work. Like what Joseph said, you need to get generic DNS entries in via some method (DNS server, /etc/hosts)
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Fri, May 6, 2016 at 8:48 AM, Joseph Zancocchio joseph@nyi.net wrote:
As far as I know, hostnames are strictly required for Observium to talk to a device. If you cannot get DNS records set, or implement some sort of customized DNS server setup, you will have to use /etc/hosts entries (which is basically a custom DNS server setup, just not as elegant/flexible... and its probably somewhat slower when dealing with a lot of addresses).
Observium can't resolve an IP to an IP because it isn't a hostname. Host file (and DNS A/AAAA record) lookups don't work "backwards" like that.
Also, a hosts file pre-filled with a generically syntaxed hostname for each IP address within any of the subnets which you wish to monitor would pretty much never have to be updated. If you ever have any new IP ranges come into play, you would simply have to append the generic entries for it to the hosts file. What else would there be to manage/maintain? It certainly wouldn't require a full-time role.
If you did this, anytime you have a device on an IP without a DNS record, you could add it with the generic hostname.
The only other option would be to do some pretty involved patching of your Observium install, which almost assuredly WOULD be a nightmare to maintain.
On 05/05/2016 07:02 PM, Ivan Jukic wrote:
The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers, Ivan
On 6 May 2016 at 08:29, Ivan Jukic ijukic13@gmail.com wrote:
I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers, Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio < joseph@nyi.net joseph@nyi.net> wrote:
It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote:
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Cmon, it would take less time to assign hostnames to those IP's than argue about it . Why on earth would you refer to something by IP over a hostname? You said you have multiple clients well then come up with naming convention for your IP ranges that incorporate clients name in the hostname...
Sent from my Windows Phone ________________________________ From: Ivan Jukicmailto:ijukic13@gmail.com Sent: 09/05/2016 00:58 To: Observium Network Observation Systemmailto:observium@observium.org Subject: Re: [Observium] Cannot add Device by IP Address but can by hostname
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
Is adding devices via IP Address not the important to Observium Devs? I thought it would be a given, since many NMS platforms do this?
Cheers, Ivan
On 6 May 2016 at 23:12, Adam Armstrong <adama@memetic.orgmailto:adama@memetic.org> wrote: First port of call would be to fire the people installing devices important enough to need monitoring without hostnames...
adam.
Sent from Mailbirdhttp://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 06/05/2016 15:00:36, Spencer Ryan <sryan@arbor.netmailto:sryan@arbor.net> wrote:
Yeah, you adding it by hostname has absolutely nothing to do with you trying to add it by IP address, it simply won't work. Like what Joseph said, you need to get generic DNS entries in via some method (DNS server, /etc/hosts)
Spencer Ryan | Senior Systems Administrator | sryan@arbor.netmailto:sryan@arbor.net Arbor Networks +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.comhttp://www.arbornetworks.com/
On Fri, May 6, 2016 at 8:48 AM, Joseph Zancocchio <joseph@nyi.netmailto:joseph@nyi.net> wrote: As far as I know, hostnames are strictly required for Observium to talk to a device. If you cannot get DNS records set, or implement some sort of customized DNS server setup, you will have to use /etc/hosts entries (which is basically a custom DNS server setup, just not as elegant/flexible... and its probably somewhat slower when dealing with a lot of addresses).
Observium can't resolve an IP to an IP because it isn't a hostname. Host file (and DNS A/AAAA record) lookups don't work "backwards" like that.
Also, a hosts file pre-filled with a generically syntaxed hostname for each IP address within any of the subnets which you wish to monitor would pretty much never have to be updated. If you ever have any new IP ranges come into play, you would simply have to append the generic entries for it to the hosts file. What else would there be to manage/maintain? It certainly wouldn't require a full-time role.
If you did this, anytime you have a device on an IP without a DNS record, you could add it with the generic hostname.
The only other option would be to do some pretty involved patching of your Observium install, which almost assuredly WOULD be a nightmare to maintain.
On 05/05/2016 07:02 PM, Ivan Jukic wrote: The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers, Ivan
On 6 May 2016 at 08:29, Ivan Jukic <ijukic13@gmail.commailto:ijukic13@gmail.com> wrote: I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers, Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio <mailto:joseph@nyi.netjoseph@nyi.netmailto:joseph@nyi.net> wrote: It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote: Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.orgmailto:observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL.
CDW Limited is a Company registered in England and Wales. This email is sent for and on behalf of CDW Finance Holdings Limited. CDW Finance Holdings Limited is the UK holding company for CDW Limited trading as CDW. The registered office for CDW Finance Holdings Limited (Company Number 05872067) and its UK group undertakings is 10 Fleet Place, London, EC4M 7RB. VAT Registration 902 1949 39. Confidentiality: This e-mail contains proprietary information, some or all of which may be confidential and/or legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then delete the original. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on any information contained in this e-mail. You must not inform any other person other than CDW or the sender of its existence.
For more information about CDW please visit www.uk.cdw.com
Simple. Because just of of my devices has many ip addresses that can not have hostnames.
On 9 May 2016 at 17:05, Serghei Golipad s.golipad@uk.cdw.com wrote:
Cmon, it would take less time to assign hostnames to those IP's than argue about it . Why on earth would you refer to something by IP over a hostname? You said you have multiple clients well then come up with naming convention for your IP ranges that incorporate clients name in the hostname...
Sent from my Windows Phone
From: Ivan Jukic ijukic13@gmail.com Sent: 09/05/2016 00:58 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Cannot add Device by IP Address but can by hostname
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
Is adding devices via IP Address not the important to Observium Devs? I thought it would be a given, since many NMS platforms do this?
Cheers, Ivan
On 6 May 2016 at 23:12, Adam Armstrong adama@memetic.org wrote:
First port of call would be to fire the people installing devices important enough to need monitoring without hostnames...
adam.
Sent from Mailbird http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 06/05/2016 15:00:36, Spencer Ryan sryan@arbor.net wrote: Yeah, you adding it by hostname has absolutely nothing to do with you trying to add it by IP address, it simply won't work. Like what Joseph said, you need to get generic DNS entries in via some method (DNS server, /etc/hosts)
- Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net
*Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Fri, May 6, 2016 at 8:48 AM, Joseph Zancocchio joseph@nyi.net wrote:
As far as I know, hostnames are strictly required for Observium to talk to a device. If you cannot get DNS records set, or implement some sort of customized DNS server setup, you will have to use /etc/hosts entries (which is basically a custom DNS server setup, just not as elegant/flexible... and its probably somewhat slower when dealing with a lot of addresses).
Observium can't resolve an IP to an IP because it isn't a hostname. Host file (and DNS A/AAAA record) lookups don't work "backwards" like that.
Also, a hosts file pre-filled with a generically syntaxed hostname for each IP address within any of the subnets which you wish to monitor would pretty much never have to be updated. If you ever have any new IP ranges come into play, you would simply have to append the generic entries for it to the hosts file. What else would there be to manage/maintain? It certainly wouldn't require a full-time role.
If you did this, anytime you have a device on an IP without a DNS record, you could add it with the generic hostname.
The only other option would be to do some pretty involved patching of your Observium install, which almost assuredly WOULD be a nightmare to maintain.
On 05/05/2016 07:02 PM, Ivan Jukic wrote:
The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers, Ivan
On 6 May 2016 at 08:29, Ivan Jukic ijukic13@gmail.com wrote:
I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers, Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio < joseph@nyi.net joseph@nyi.net> wrote:
It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote:
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL.
CDW Limited is a Company registered in England and Wales. This email is sent for and on behalf of CDW Finance Holdings Limited. CDW Finance Holdings Limited is the UK holding company for CDW Limited trading as CDW. The registered office for CDW Finance Holdings Limited (Company Number 05872067) and its UK group undertakings is 10 Fleet Place, London, EC4M 7RB. VAT Registration 902 1949 39. Confidentiality: This e-mail contains proprietary information, some or all of which may be confidential and/or legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then delete the original. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on any information contained in this e-mail. You must not inform any other person other than CDW or the sender of its existence.
For more information about CDW please visit www.uk.cdw.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
That's simply untrue.
sudo echo "1.2.3.4 my-device.nms.local" >> /etc/hosts
Add my-device.nms.local to Observium
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 5:48 PM, Ivan Jukic ijukic13@gmail.com wrote:
Simple. Because just of of my devices has many ip addresses that can not have hostnames.
On 9 May 2016 at 17:05, Serghei Golipad s.golipad@uk.cdw.com wrote:
Cmon, it would take less time to assign hostnames to those IP's than argue about it . Why on earth would you refer to something by IP over a hostname? You said you have multiple clients well then come up with naming convention for your IP ranges that incorporate clients name in the hostname...
Sent from my Windows Phone
From: Ivan Jukic ijukic13@gmail.com Sent: 09/05/2016 00:58 To: Observium Network Observation System observium@observium.org Subject: Re: [Observium] Cannot add Device by IP Address but can by hostname
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
Is adding devices via IP Address not the important to Observium Devs? I thought it would be a given, since many NMS platforms do this?
Cheers, Ivan
On 6 May 2016 at 23:12, Adam Armstrong adama@memetic.org wrote:
First port of call would be to fire the people installing devices important enough to need monitoring without hostnames...
adam.
Sent from Mailbird http://www.getmailbird.com/?utm_source=Mailbird&utm_medium=email&utm_campaign=sent-from-mailbird
On 06/05/2016 15:00:36, Spencer Ryan sryan@arbor.net wrote: Yeah, you adding it by hostname has absolutely nothing to do with you trying to add it by IP address, it simply won't work. Like what Joseph said, you need to get generic DNS entries in via some method (DNS server, /etc/hosts)
- Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net
*Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Fri, May 6, 2016 at 8:48 AM, Joseph Zancocchio joseph@nyi.net wrote:
As far as I know, hostnames are strictly required for Observium to talk to a device. If you cannot get DNS records set, or implement some sort of customized DNS server setup, you will have to use /etc/hosts entries (which is basically a custom DNS server setup, just not as elegant/flexible... and its probably somewhat slower when dealing with a lot of addresses).
Observium can't resolve an IP to an IP because it isn't a hostname. Host file (and DNS A/AAAA record) lookups don't work "backwards" like that.
Also, a hosts file pre-filled with a generically syntaxed hostname for each IP address within any of the subnets which you wish to monitor would pretty much never have to be updated. If you ever have any new IP ranges come into play, you would simply have to append the generic entries for it to the hosts file. What else would there be to manage/maintain? It certainly wouldn't require a full-time role.
If you did this, anytime you have a device on an IP without a DNS record, you could add it with the generic hostname.
The only other option would be to do some pretty involved patching of your Observium install, which almost assuredly WOULD be a nightmare to maintain.
On 05/05/2016 07:02 PM, Ivan Jukic wrote:
The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers, Ivan
On 6 May 2016 at 08:29, Ivan Jukic ijukic13@gmail.com wrote:
I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers, Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio < joseph@nyi.net joseph@nyi.net> wrote:
It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote:
Hi All,
I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed.
Is there a way I can simply add a whole subnet range to Observium without using hostname?
Cheers, Ivan
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing listobservium@observium.orghttp://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
PLEASE CONSIDER THE ENVIRONMENT BEFORE PRINTING THIS EMAIL.
CDW Limited is a Company registered in England and Wales. This email is sent for and on behalf of CDW Finance Holdings Limited. CDW Finance Holdings Limited is the UK holding company for CDW Limited trading as CDW. The registered office for CDW Finance Holdings Limited (Company Number 05872067) and its UK group undertakings is 10 Fleet Place, London, EC4M 7RB. VAT Registration 902 1949 39. Confidentiality: This e-mail contains proprietary information, some or all of which may be confidential and/or legally privileged. It is for the intended recipient only. If an addressing or transmission error has misdirected this e-mail, please notify the author by replying to this e-mail and then delete the original. If you are not the intended recipient you may not use, disclose, distribute, copy, print or rely on any information contained in this e-mail. You must not inform any other person other than CDW or the sender of its existence.
For more information about CDW please visit www.uk.cdw.com
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
On 09/05/2016 01:57, Ivan Jukic wrote:
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
So you are saying you don't know and don't care about what you are actually monitoring? As it seems they (rightly so, apparently?) swap out devices daily while keeping them on the same IP address...
Tom
We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed).
Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into.
Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table.
Simple but gets the job done.
On 5/9/2016 2:50 AM, Tom Laermans wrote:
On 09/05/2016 01:57, Ivan Jukic wrote:
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
So you are saying you don't know and don't care about what you are actually monitoring? As it seems they (rightly so, apparently?) swap out devices daily while keeping them on the same IP address...
Tom _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
if you don't have access to a DNS server and unable to add everything to /etc/hosts file, then you could use a public DNS wildcard service like http://xip.io/
Thanks Steve, I think you are the only one here that seems to understand the infrastructure involved. Most of replies seems to think all the devices are unix like boxes
On 9 May 2016 at 19:16, Steve Costaras stevecs@chaven.com wrote:
We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed).
Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into.
Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table.
Simple but gets the job done.
On 5/9/2016 2:50 AM, Tom Laermans wrote:
On 09/05/2016 01:57, Ivan Jukic wrote:
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
So you are saying you don't know and don't care about what you are actually monitoring? As it seems they (rightly so, apparently?) swap out devices daily while keeping them on the same IP address...
Tom _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
"Most of replies seems to think all the devices are unix like boxes"
What the devices are, or what OS they run is completely irrelevant to how they are in DNS.
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 5:57 PM, Ivan Jukic ijukic13@gmail.com wrote:
Thanks Steve, I think you are the only one here that seems to understand the infrastructure involved. Most of replies seems to think all the devices are unix like boxes
On 9 May 2016 at 19:16, Steve Costaras stevecs@chaven.com wrote:
We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed).
Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into.
Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table.
Simple but gets the job done.
On 5/9/2016 2:50 AM, Tom Laermans wrote:
On 09/05/2016 01:57, Ivan Jukic wrote:
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
So you are saying you don't know and don't care about what you are actually monitoring? As it seems they (rightly so, apparently?) swap out devices daily while keeping them on the same IP address...
Tom _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Yes I know that. So you tell me. How can I monitor an IP Address that CAN NOT Map to DNS or Hosts file?
On 10 May 2016 at 07:59, Spencer Ryan sryan@arbor.net wrote:
"Most of replies seems to think all the devices are unix like boxes"
What the devices are, or what OS they run is completely irrelevant to how they are in DNS.
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 5:57 PM, Ivan Jukic ijukic13@gmail.com wrote:
Thanks Steve, I think you are the only one here that seems to understand the infrastructure involved. Most of replies seems to think all the devices are unix like boxes
On 9 May 2016 at 19:16, Steve Costaras stevecs@chaven.com wrote:
We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed).
Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into.
Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table.
Simple but gets the job done.
On 5/9/2016 2:50 AM, Tom Laermans wrote:
On 09/05/2016 01:57, Ivan Jukic wrote:
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
So you are saying you don't know and don't care about what you are actually monitoring? As it seems they (rightly so, apparently?) swap
out
devices daily while keeping them on the same IP address...
Tom _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
There is no such thing.
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 6:07 PM, Ivan Jukic ijukic13@gmail.com wrote:
Yes I know that. So you tell me. How can I monitor an IP Address that CAN NOT Map to DNS or Hosts file?
On 10 May 2016 at 07:59, Spencer Ryan sryan@arbor.net wrote:
"Most of replies seems to think all the devices are unix like boxes"
What the devices are, or what OS they run is completely irrelevant to how they are in DNS.
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 5:57 PM, Ivan Jukic ijukic13@gmail.com wrote:
Thanks Steve, I think you are the only one here that seems to understand the infrastructure involved. Most of replies seems to think all the devices are unix like boxes
On 9 May 2016 at 19:16, Steve Costaras stevecs@chaven.com wrote:
We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed).
Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into.
Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table.
Simple but gets the job done.
On 5/9/2016 2:50 AM, Tom Laermans wrote:
On 09/05/2016 01:57, Ivan Jukic wrote:
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
So you are saying you don't know and don't care about what you are actually monitoring? As it seems they (rightly so, apparently?) swap
out
devices daily while keeping them on the same IP address...
Tom _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
That's is you solution. Pretend the issue/problem doesn't exist. Brilliant!!
On 10 May 2016 at 08:08, Spencer Ryan sryan@arbor.net wrote:
There is no such thing.
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 6:07 PM, Ivan Jukic ijukic13@gmail.com wrote:
Yes I know that. So you tell me. How can I monitor an IP Address that CAN NOT Map to DNS or Hosts file?
On 10 May 2016 at 07:59, Spencer Ryan sryan@arbor.net wrote:
"Most of replies seems to think all the devices are unix like boxes"
What the devices are, or what OS they run is completely irrelevant to how they are in DNS.
*Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 5:57 PM, Ivan Jukic ijukic13@gmail.com wrote:
Thanks Steve, I think you are the only one here that seems to understand the infrastructure involved. Most of replies seems to think all the devices are unix like boxes
On 9 May 2016 at 19:16, Steve Costaras stevecs@chaven.com wrote:
We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed).
Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into.
Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table.
Simple but gets the job done.
On 5/9/2016 2:50 AM, Tom Laermans wrote:
On 09/05/2016 01:57, Ivan Jukic wrote: > Hostnames are not necessary when monitoring via SNMP, in fact IP > Addresses are easier. Second we host many IP address ranges for our > clients (Public and Private), so this will be a nightmare to manage. > As they tend to change hostnames (and rightly so) all the time. Many > of them have managed services. So you are saying you don't know and don't care about what you are actually monitoring? As it seems they (rightly so, apparently?) swap
out
devices daily while keeping them on the same IP address...
Tom _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Ivan,
Observium is that way (using hostnames). If you are not happy with that, so give up.
...or read the manual first ;)
Regards,
2016-05-09 19:12 GMT-03:00 Ivan Jukic ijukic13@gmail.com:
That's is you solution. Pretend the issue/problem doesn't exist. Brilliant!!
On 10 May 2016 at 08:08, Spencer Ryan sryan@arbor.net wrote:
There is no such thing.
Spencer Ryan | Senior Systems Administrator | sryan@arbor.net Arbor Networks +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 6:07 PM, Ivan Jukic ijukic13@gmail.com wrote:
Yes I know that. So you tell me. How can I monitor an IP Address that CAN NOT Map to DNS or Hosts file?
On 10 May 2016 at 07:59, Spencer Ryan sryan@arbor.net wrote:
"Most of replies seems to think all the devices are unix like boxes"
What the devices are, or what OS they run is completely irrelevant to how they are in DNS.
Spencer Ryan | Senior Systems Administrator | sryan@arbor.net Arbor Networks +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Mon, May 9, 2016 at 5:57 PM, Ivan Jukic ijukic13@gmail.com wrote:
Thanks Steve, I think you are the only one here that seems to understand the infrastructure involved. Most of replies seems to think all the devices are unix like boxes
On 9 May 2016 at 19:16, Steve Costaras stevecs@chaven.com wrote:
We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed).
Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into.
Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table.
Simple but gets the job done.
On 5/9/2016 2:50 AM, Tom Laermans wrote: > On 09/05/2016 01:57, Ivan Jukic wrote: >> Hostnames are not necessary when monitoring via SNMP, in fact IP >> Addresses are easier. Second we host many IP address ranges for our >> clients (Public and Private), so this will be a nightmare to >> manage. >> As they tend to change hostnames (and rightly so) all the time. >> Many >> of them have managed services. > So you are saying you don't know and don't care about what you are > actually monitoring? As it seems they (rightly so, apparently?) swap > out > devices daily while keeping them on the same IP address... > > Tom > _______________________________________________ > observium mailing list > observium@observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Come on guys, you make me laugh! (no offense intended...)
Ivan, try to understand what Spencer was saying. He just tried to explain (albeit in a real minimalist style ;-) that there is no such IP address that cannot be mapped to a DNS. You can map any IP address to many host names - there are almost endless possibilities. OTOH what you tried to say (at least in my interpretation, correct me if I'm wrong) is that you can not map your IP addresses to a DNS or host file _in a meaningful way_. But that's a completely different story.
If you cannot map your IP addresses in a meaningful way AND you want to use Observium, then you should map your IP addresses in some less meaningful ways. Like host_A.B.C.D => A.B.C.D
If I understood you correctly, in your network you have plenty of IP addresses/ranges that are being associated/used by hosts on an almost random (or some unpredictable) way. And you want to monitor them. What I would like to ask you (and you should ask yourself too), what is network monitoring good for, if you are unable to tell which device was actually monitored at what time? This is the same problem Steve Costaras lined out, and as he told us they have a pretty hard time figuring it out. They are searching for a needle in a haystack while they are not quite sure about the appearance of the needle. :)
So if you want to monitor an IP address that gets picked up by some host, used for a while and then abandoned, and picked up by another host etc... then bite the bullet and create some DNS resolution solution (there were some options mentioned here before) for Observium to be able to handle the situation.
As for your last post: Does a problem exist? Yes, Observium is unable to handle devices by IP address, only by hostname. Does it impose a big obstacle? It depends on the usage pattern, but there are solutions/workarounds etc. for average businesses this makes no problem. Is this a bug or a feature? It is a feature, as this was a design decision, which was taken by Adam, and if you want to use the program you have to live with it. Or try to convince Adam to change it, but as this is a real fundamental thing I really doubt they would be taking it easily.
My 2cents, Tylla
On 2016-05-10 00:12, Ivan Jukic wrote:
That's is you solution. Pretend the issue/problem doesn't exist. Brilliant!!
On 10 May 2016 at 08:08, Spencer Ryan <sryan@arbor.net mailto:sryan@arbor.net> wrote:
There is no such thing. * Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net <mailto:sryan@arbor.net> *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com <http://www.arbornetworks.com/> On Mon, May 9, 2016 at 6:07 PM, Ivan Jukic <ijukic13@gmail.com <mailto:ijukic13@gmail.com>> wrote: Yes I know that. So you tell me. How can I monitor an IP Address that CAN NOT Map to DNS or Hosts file? On 10 May 2016 at 07:59, Spencer Ryan <sryan@arbor.net <mailto:sryan@arbor.net>> wrote: "Most of replies seems to think all the devices are unix like boxes" What the devices are, or what OS they run is completely irrelevant to how they are in DNS. * Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net <mailto:sryan@arbor.net> *Arbor Networks* +1.734.794.5033 <tel:%2B1.734.794.5033> (d) | +1.734.846.2053 <tel:%2B1.734.846.2053> (m) www.arbornetworks.com <http://www.arbornetworks.com/> On Mon, May 9, 2016 at 5:57 PM, Ivan Jukic <ijukic13@gmail.com <mailto:ijukic13@gmail.com>> wrote: Thanks Steve, I think you are the only one here that seems to understand the infrastructure involved. Most of replies seems to think all the devices are unix like boxes On 9 May 2016 at 19:16, Steve Costaras <stevecs@chaven.com <mailto:stevecs@chaven.com>> wrote: We have a similar environment where we have co-lo equipment, or equipment that is controlled by the customer or a 3rd party which changes frequently and we are never informed of those changes. However we are always called for stats on such devices (even if they are changed). Since all the fields are searchable by IP or if it has a name a name, it works. (In many calls, the customer's don't know the IP, or the name (as it could be different under different internal or external DNS's which we or even they (if it's their customers calling up) don't see), so the first 15+ minutes is usually a hunt for /something/ to look into. Normally with other tools we add them by IP since names/dns is pretty useless in this case. With observium I just wrote a quick script that just added entire ranges to the host table as Hst_A.B.C.D for each. If you have a /LOT/ of them, this does not scale (old problems as to why bind was invented), you can just create a local name-server on the observium system and do the exact same thing there for entire subnets which avoids the linear lookup of a host table. Simple but gets the job done. On 5/9/2016 2:50 AM, Tom Laermans wrote: > On 09/05/2016 01:57, Ivan Jukic wrote: >> Hostnames are not necessary when monitoring via SNMP, in fact IP >> Addresses are easier. Second we host many IP address ranges for our >> clients (Public and Private), so this will be a nightmare to manage. >> As they tend to change hostnames (and rightly so) all the time. Many >> of them have managed services. > So you are saying you don't know and don't care about what you are > actually monitoring? As it seems they (rightly so, apparently?) swap out > devices daily while keeping them on the same IP address... > > Tom > _______________________________________________ > observium mailing list > observium@observium.org <mailto:observium@observium.org> > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium _______________________________________________ observium mailing list observium@observium.org <mailto:observium@observium.org> http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
No. I think you read to read it again. We do not care for hostnames because we can not manage them. BUT we have control of the IP Address. So why on earth would I care about hostnames for devices that do not use them?
On 9 May 2016 at 17:50, Tom Laermans tom.laermans@powersource.cx wrote:
On 09/05/2016 01:57, Ivan Jukic wrote:
Hostnames are not necessary when monitoring via SNMP, in fact IP Addresses are easier. Second we host many IP address ranges for our clients (Public and Private), so this will be a nightmare to manage. As they tend to change hostnames (and rightly so) all the time. Many of them have managed services.
So you are saying you don't know and don't care about what you are actually monitoring? As it seems they (rightly so, apparently?) swap out devices daily while keeping them on the same IP address...
Tom
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
I think you miswrote "set on fire" ;)
Sent from my iPhone
On 6 May 2016, at 14:12, Adam Armstrong adama@memetic.org wrote:
First port of call would be to fire the people installing devices important enough to need monitoring without hostnames...
adam.
Sent from Mailbird
On 06/05/2016 15:00:36, Spencer Ryan sryan@arbor.net wrote:
Yeah, you adding it by hostname has absolutely nothing to do with you trying to add it by IP address, it simply won't work. Like what Joseph said, you need to get generic DNS entries in via some method (DNS server, /etc/hosts)
Spencer Ryan | Senior Systems Administrator | sryan@arbor.net Arbor Networks +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com
On Fri, May 6, 2016 at 8:48 AM, Joseph Zancocchio joseph@nyi.net wrote: As far as I know, hostnames are strictly required for Observium to talk to a device. If you cannot get DNS records set, or implement some sort of customized DNS server setup, you will have to use /etc/hosts entries (which is basically a custom DNS server setup, just not as elegant/flexible... and its probably somewhat slower when dealing with a lot of addresses).
Observium can't resolve an IP to an IP because it isn't a hostname. Host file (and DNS A/AAAA record) lookups don't work "backwards" like that.
Also, a hosts file pre-filled with a generically syntaxed hostname for each IP address within any of the subnets which you wish to monitor would pretty much never have to be updated. If you ever have any new IP ranges come into play, you would simply have to append the generic entries for it to the hosts file. What else would there be to manage/maintain? It certainly wouldn't require a full-time role.
If you did this, anytime you have a device on an IP without a DNS record, you could add it with the generic hostname.
The only other option would be to do some pretty involved patching of your Observium install, which almost assuredly WOULD be a nightmare to maintain.
On 05/05/2016 07:02 PM, Ivan Jukic wrote: The reason why I ask this is that. I've successfully added a device by Hostname, deleted it then tried via IP Address and get "Can't resolve 10.0.0.1". Even though, the hostname/IP address is still in the hosts file.
Furthermore, we literally have millions of IP Addresses (both public and private) so managing this would require a full-time role.
Is there any way we can add devices without using hostnames?
Cheers, Ivan
On 6 May 2016 at 08:29, Ivan Jukic ijukic13@gmail.com wrote: I was thinking to do that. But I wanted to avoid that all together. So just to confirm, Observium can only add devices by hostname only and not IP Address?
Cheers, Ivan
On 6 May 2016 at 08:21, Joseph Zancocchio joseph@nyi.net wrote: It would probably be easiest to use a small script to generate a list of "hostnames" in whatever format you'd like for the IP(s) in the subnet that don't have any DNS records (perhaps something like 10.0.0.1 -> 10-0-0-1.noDNS.<yourdomain>, or whatever), and then add corresponding entries to /etc/hosts for those hosts. Then, you can add the range using that list of hostnames.
On 05/05/2016 05:41 PM, Ivan Jukic wrote: > Hi All, > > I have many devices in our network that do no have hostnames and nor do I want to maintain DNS records for devices that do as this will be a nightmare to managed. > > Is there a way I can simply add a whole subnet range to Observium without using hostname? > > > Cheers, > Ivan > > > _______________________________________________ > observium mailing list > observium@observium.org > http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
_______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (11)
-
Adam Armstrong -
Eduardo Schoedler -
Ivan Jukic -
Joseph Zancocchio -
Michiel Klaver -
Nagy Attila -
roeland＠unbreakable.org.uk -
Serghei Golipad -
Spencer Ryan -
Steve Costaras -
Tom Laermans