Hello,
my observium lab was on 0.12.10.3399. I have some problem with my graphs but it's not a problem
i just did a fresh install on new server with last observium version 0.13.10.4721. The tutorial was great and my install work perfect.
When i start to add my devices i had some error. Some device have the same system name and when i tri to add them, the 2nd one don't work.
"Already got device with SNMP-read sysName (system.name)"
I didn't get this on my lab.
Is it possible to disable system name check?
--- Zoran Lukenic z.lukenic@mediactive.frmailto:z.lukenic@mediactive.fr --- Groupe Mediactive 3-4-10, cité Paradis 75010 Paris Tel : +33 1 55 28 80 60 Fax : +33 1 55 28 80 61 Support technique : 0 892 494 777 www.groupe-mediactive.frhttp://www.groupe-mediactive.fr/ Twitter : @mediactivegroup [cid:FB003B7F-1839-4401-8DAE-B37B718E4644]
On 2013-10-30 05:52, Zoran Lukenic wrote:
Hello,
my observium lab was on 0.12.10.3399. I have some problem with my graphs but it's not a problem
i just did a fresh install on new server with last observium version 0.13.10.4721. The tutorial was great and my install work perfect.
When i start to add my devices i had some error. Some device have the same system name and when i tri to add them, the 2nd one don't work.
"Already got device with SNMP-read sysName (system.name)"
I didn't get this on my lab.
Is it possible to disable system name check?
Nope. It's used to make sure we don't end up with duplicate hosts. You need unique hostnames and unique sysNames.
Your devices will let you set the system name somewhere in the configuration.
This issue is usually caused when people don't change the default, or set 5 switches in different locations to be called "switch1"
adam.
Adam Armstrong <adama@...> writes:
Nope. It's used to make sure we don't end up with duplicate hosts. You need unique hostnames and unique sysNames.
Your devices will let you set the system name somewhere in the configuration.
This issue is usually caused when people don't change the default, or set 5 switches in different locations to be called "switch1"
adam.
Hello Adam,
We have many embedded devices each with it's own hostname but the sysName is hard coded in the agent. Is there no way to update the PHP code to keep the individual hostname rule but ignore duplicate sysNames?
Thanks! Mark
Hi Mark,
you can tell the vendor and model of these devices?
Maybe we will add an option to exclude check duplicate sysNames, but because it is used for autodiscovery, it will not be the default option.
On Thu, Nov 14, 2013 at 5:30 AM, Mark Boddy mark@boddy.org wrote:
Adam Armstrong <adama@...> writes:
Nope. It's used to make sure we don't end up with duplicate hosts. You need unique hostnames and unique sysNames.
Your devices will let you set the system name somewhere in the configuration.
This issue is usually caused when people don't change the default, or set 5 switches in different locations to be called "switch1"
adam.
Hello Adam,
We have many embedded devices each with it's own hostname but the sysName is hard coded in the agent. Is there no way to update the PHP code to keep the individual hostname rule but ignore duplicate sysNames?
Thanks! Mark
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Mike Stupalov <mike@...> writes:
Hi Mark, you can tell the vendor and model of these devices?Maybe we will
add an option to exclude check duplicate sysNames,
but because it is used for autodiscovery, it will not be the default
option.
Hi Mike,
Yes we can tell but only by IP address. To give an example, we might be monitoring standby generators. If a hospital has 4 buildings each with it's own generator then we would one of our devices connected to each generator. All four of our devices would be identical in every way and the only way to distinguish between them would be via the IP address. If you were to do an SNMP Walk all 4 they would reply with the exact same header information and only differ in the actual engine or generator information.
If it was possible to have duplicate sysNames that would be very helpful. Please let me know if I have raised more questions.
Thank-You! Mark
Hi Mark,
On 18.11.2013 04:30, Mark Boddy wrote:
Mike Stupalov <mike@...> writes:
Hi Mark, you can tell the vendor and model of these devices?Maybe we will
add an option to exclude check duplicate sysNames,
but because it is used for autodiscovery, it will not be the default
option. Hi Mike,
Yes we can tell but only by IP address. To give an example, we might be monitoring standby generators. If a hospital has 4 buildings each with it's own generator then we would one of our devices connected to each generator. All four of our devices would be identical in every way and the only way to distinguish between them would be via the IP address. If you were to do an SNMP Walk all 4 they would reply with the exact same header information and only differ in the actual engine or generator information.
If it was possible to have duplicate sysNames that would be very helpful. Please let me know if I have raised more questions.
We changed the uniqueness check devices from sysName to snmpEngineID. Additional options aren't required. Simply update your observium ('svn up') and try to add the device again.
(NOTE. Certainly I talk about non-CE version.)
Thank-You! Mark
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Mike Stupalov http://observium.org/
participants (4)
-
Adam Armstrong -
Mark Boddy -
Mike Stupalov -
Zoran Lukenic