Issue with Didactum device (after firmwareupdate, generic device)
Hi
We are running Observium Professional r12000
Recently, we upgraded the firmware of one of our Didactum sensors and noticed, that after the firmware upgrade, Obersvium handled it as a generic device instead with all sensors beeing removed.
3d 16h 50m it-temp-002 https://observium.mpimf-heidelberg.mpg.de/device/device=214/ OS changed: didactum-ems -> generic
The sysObjectID is .1.3.6.1.4.1.46501 and according to the following ticket, it should be working from r11479 onwards
https://jira.observium.org/browse/OBS-3814
What are we doing wrong here?
Best,
Thomas
Hi
Does somebody have an idea?
Best,
Thomas
Am 10.05.22 um 09:39 schrieb Thomas Stather:
Hi
We are running Observium Professional r12000
Recently, we upgraded the firmware of one of our Didactum sensors and noticed, that after the firmware upgrade, Obersvium handled it as a generic device instead with all sensors beeing removed.
3d 16h 50m it-temp-002 https://observium.mpimf-heidelberg.mpg.de/device/device=214/ OS changed: didactum-ems -> generic
The sysObjectID is .1.3.6.1.4.1.46501 and according to the following ticket, it should be working from r11479 onwards
https://jira.observium.org/browse/OBS-3814
What are we doing wrong here?
Best,
Thomas
-- Thomas Stather IT Services
VCP4, VCP6-DCV, VCP6.5-DCV
Tel: +49 6221 486 628 Fax: +49 6221 486 561
Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!
What’s the sysDescr.0?
The current rule requires both to match:
$config['os'][$os]['discovery'][] = array(
'sysObjectID' => [ '.1.3.6.1.4.1.8072.3.2.10',
'.1.3.6.1.4.1.46501'],
'sysDescr' => '/Didactum EMS/',
);
Adam.
From: observium observium-bounces@observium.org On Behalf Of Thomas Stather via observium Sent: 11 May 2022 09:38 To: 'Observium' observium@observium.org Cc: Thomas Stather tstather@mr.mpg.de Subject: Re: [Observium] Issue with Didactum device (after firmwareupdate, generic device)
Hi
Does somebody have an idea?
Best,
Thomas
Am 10.05.22 um 09:39 schrieb Thomas Stather:
Hi
We are running Observium Professional r12000
Recently, we upgraded the firmware of one of our Didactum sensors and noticed, that after the firmware upgrade, Obersvium handled it as a generic device instead with all sensors beeing removed.
3d 16h 50m
it-temp-002 https://observium.mpimf-heidelberg.mpg.de/device/device=214/ OS changed: didactum-ems -> generic
The sysObjectID is .1.3.6.1.4.1.46501 and according to the following ticket, it should be working from r11479 onwards
https://jira.observium.org/browse/OBS-3814
What are we doing wrong here?
Best,
Thomas
Hi
The device description is
Didactum Monitoring System
Best,
Thomas
Am 11.05.22 um 12:50 schrieb adama--- via observium:
What’s the sysDescr.0?
The current rule requires both to match:
$config['os'][$os]['discovery'][] = array(
'sysObjectID' => [ '.1.3.6.1.4.1.8072.3.2.10',
'.1.3.6.1.4.1.46501'],
'sysDescr' => '/Didactum EMS/',
);
Adam.
*From:*observium observium-bounces@observium.org *On Behalf Of *Thomas Stather via observium *Sent:* 11 May 2022 09:38 *To:* 'Observium' observium@observium.org *Cc:* Thomas Stather tstather@mr.mpg.de *Subject:* Re: [Observium] Issue with Didactum device (after firmwareupdate, generic device)
Hi
Does somebody have an idea?
Best,
Thomas
Am 10.05.22 um 09:39 schrieb Thomas Stather:
Hi We are running Observium Professional r12000 Recently, we upgraded the firmware of one of our Didactum sensors and noticed, that after the firmware upgrade, Obersvium handled it as a generic device instead with all sensors beeing removed. 3d 16h 50m it-temp-002 <https://observium.mpimf-heidelberg.mpg.de/device/device=214/> OS changed: didactum-ems -> generic The sysObjectID is .1.3.6.1.4.1.46501 and according to the following ticket, it should be working from r11479 onwards https://jira.observium.org/browse/OBS-3814 What are we doing wrong here? Best, Thomas -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!
-- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
Hi
Is it possible to change ot to an or-based statement so that only one of those has to match? Or can i patch this myself (whichfile do i have to edit and how?
Best,
Thomas
Am 12.05.22 um 14:53 schrieb Thomas Stather:
Hi
The device description is
Didactum Monitoring System
Best,
Thomas
Am 11.05.22 um 12:50 schrieb adama--- via observium:
What’s the sysDescr.0?
The current rule requires both to match:
$config['os'][$os]['discovery'][] = array(
'sysObjectID' => [ '.1.3.6.1.4.1.8072.3.2.10',
'.1.3.6.1.4.1.46501'],
'sysDescr' => '/Didactum EMS/',
);
Adam.
*From:*observium observium-bounces@observium.org *On Behalf Of *Thomas Stather via observium *Sent:* 11 May 2022 09:38 *To:* 'Observium' observium@observium.org *Cc:* Thomas Stather tstather@mr.mpg.de *Subject:* Re: [Observium] Issue with Didactum device (after firmwareupdate, generic device)
Hi
Does somebody have an idea?
Best,
Thomas
Am 10.05.22 um 09:39 schrieb Thomas Stather:
Hi We are running Observium Professional r12000 Recently, we upgraded the firmware of one of our Didactum sensors and noticed, that after the firmware upgrade, Obersvium handled it as a generic device instead with all sensors beeing removed. 3d 16h 50m it-temp-002 <https://observium.mpimf-heidelberg.mpg.de/device/device=214/> OS changed: didactum-ems -> generic The sysObjectID is .1.3.6.1.4.1.46501 and according to the following ticket, it should be working from r11479 onwards https://jira.observium.org/browse/OBS-3814 What are we doing wrong here? Best, Thomas -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!
-- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
-- Thomas Stather IT Services
VCP4, VCP6-DCV, VCP6.5-DCV
Tel: +49 6221 486 628 Fax: +49 6221 486 561
Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!
I’ve added this string too, see if it behaves better in r12070.
Thanks,
Adam.
From: observium observium-bounces@observium.org On Behalf Of Thomas Stather via observium Sent: 01 June 2022 13:50 To: observium@observium.org Cc: Thomas Stather tstather@mr.mpg.de Subject: Re: [Observium] Issue with Didactum device (after firmwareupdate, generic device)
Hi
Is it possible to change ot to an or-based statement so that only one of those has to match? Or can i patch this myself (whichfile do i have to edit and how?
Best,
Thomas
Am 12.05.22 um 14:53 schrieb Thomas Stather:
Hi
The device description is
Didactum Monitoring System
Best,
Thomas
Am 11.05.22 um 12:50 schrieb adama--- via observium:
What’s the sysDescr.0?
The current rule requires both to match:
$config['os'][$os]['discovery'][] = array(
'sysObjectID' => [ '.1.3.6.1.4.1.8072.3.2.10',
'.1.3.6.1.4.1.46501'],
'sysDescr' => '/Didactum EMS/',
);
Adam.
From: observium mailto:observium-bounces@observium.org observium-bounces@observium.org On Behalf Of Thomas Stather via observium Sent: 11 May 2022 09:38 To: 'Observium' mailto:observium@observium.org observium@observium.org Cc: Thomas Stather mailto:tstather@mr.mpg.de tstather@mr.mpg.de Subject: Re: [Observium] Issue with Didactum device (after firmwareupdate, generic device)
Hi
Does somebody have an idea?
Best,
Thomas
Am 10.05.22 um 09:39 schrieb Thomas Stather:
Hi
We are running Observium Professional r12000
Recently, we upgraded the firmware of one of our Didactum sensors and noticed, that after the firmware upgrade, Obersvium handled it as a generic device instead with all sensors beeing removed.
3d 16h 50m
it-temp-002 https://observium.mpimf-heidelberg.mpg.de/device/device=214/ OS changed: didactum-ems -> generic
The sysObjectID is .1.3.6.1.4.1.46501 and according to the following ticket, it should be working from r11479 onwards
https://jira.observium.org/browse/OBS-3814
What are we doing wrong here?
Best,
Thomas
Hi
Yes it works now, thanks a lot.
Best,
Thomas
Am 01.06.22 um 18:19 schrieb Adam Armstrong via observium:
I’ve added this string too, see if it behaves better in r12070.
Thanks,
Adam.
*From:*observium observium-bounces@observium.org *On Behalf Of *Thomas Stather via observium *Sent:* 01 June 2022 13:50 *To:* observium@observium.org *Cc:* Thomas Stather tstather@mr.mpg.de *Subject:* Re: [Observium] Issue with Didactum device (after firmwareupdate, generic device)
Hi
Is it possible to change ot to an or-based statement so that only one of those has to match? Or can i patch this myself (whichfile do i have to edit and how?
Best,
Thomas
Am 12.05.22 um 14:53 schrieb Thomas Stather:
Hi The device description is Didactum Monitoring System Best, Thomas Am 11.05.22 um 12:50 schrieb adama--- via observium: What’s the sysDescr.0? The current rule requires both to match: $config['os'][$os]['discovery'][] = array( 'sysObjectID' => [ '.1.3.6.1.4.1.8072.3.2.10', '.1.3.6.1.4.1.46501'], 'sysDescr' => '/Didactum EMS/', ); Adam. *From:*observium <observium-bounces@observium.org> <mailto:observium-bounces@observium.org> *On Behalf Of *Thomas Stather via observium *Sent:* 11 May 2022 09:38 *To:* 'Observium' <observium@observium.org> <mailto:observium@observium.org> *Cc:* Thomas Stather <tstather@mr.mpg.de> <mailto:tstather@mr.mpg.de> *Subject:* Re: [Observium] Issue with Didactum device (after firmwareupdate, generic device) Hi Does somebody have an idea? Best, Thomas Am 10.05.22 um 09:39 schrieb Thomas Stather: Hi We are running Observium Professional r12000 Recently, we upgraded the firmware of one of our Didactum sensors and noticed, that after the firmware upgrade, Obersvium handled it as a generic device instead with all sensors beeing removed. 3d 16h 50m it-temp-002 <https://observium.mpimf-heidelberg.mpg.de/device/device=214/> OS changed: didactum-ems -> generic The sysObjectID is .1.3.6.1.4.1.46501 and according to the following ticket, it should be working from r11479 onwards https://jira.observium.org/browse/OBS-3814 What are we doing wrong here? Best, Thomas -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an! -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an! _______________________________________________ observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium -- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!
-- Thomas Stather IT Services VCP4, VCP6-DCV, VCP6.5-DCV Tel: +49 6221 486 628 Fax: +49 6221 486 561 Bevor Sie diese Mail ausdrucken, prüfen Sie bitte ob dies wirklich nötig ist. Umweltschutz geht uns alle an!
observium mailing list observium@observium.org http://postman.memetic.org/cgi-bin/mailman/listinfo/observium
participants (3)
-
Adam Armstrong
-
adama@observium.org
-
Thomas Stather