In about 5 months :)

adam.

Sent from Mailbird

On 17/03/2016 14:30:38, Ivan Biasi <ivan.biasi@trentinonetwork.it> wrote:

Hi Adam

it was enough to run again the discovery against both the HP J9726A 2920-24G Switches I use,
to solve their incomplete acquisition, thanks.
That's a little bit strange, maybe it's related to the discovery mode I used for them the first time.
I ran the discovery with a host-file, not individually host by host.
Anyhow, now it's ok.
(Tell me if you're still interested in the debug file)

About the Alcatel 6224 devices,
when will be available the next community release,
in order to upgrade and try a new discovery also for them ?

Thanks for your work,
kind regards
Ivan.


Da: "Adam Armstrong" <adama@memetic.org>
A: observium@observium.org
Inviato: Giovedì, 17 marzo 2016 14:44:59
Oggetto: Re: [Observium] Alcatel OmniStack 6224 --> Aruba device - ArubaOS

do : 

./discovery.php -h <hostname> -d >> debug.txt

and send me debug.txt

adam.

Sent from Mailbird

On 17/03/2016 13:37:26, Ivan Biasi <ivan.biasi@trentinonetwork.it> wrote:

Hi Adam

thanks for your interest on the issue.

Likewise, another kind of device we're using on our evaluating platform present similar issue,
without the vendor mismatch.

The HP J9726A 2920-24G Switch will be detected correctly as HP device on the main panel,
but selectig it with the GUI present on top the banner:
"Device not yet discovered
This device has not yet been successfully discovered. System information and statistics will not be populated and graphs will not draw. This device should be automatically discovered within 10 minutes."

Here below the sysObjectId of that model:

iso.3.6.1.2.1.1.1.0 = STRING: "HP J9726A 2920-24G Switch, revision WB.15.13.0003, ROM WB.15.05 (/ws/swbuildm/rel_laredo_qaoff/code/build/anm(swbuildm_rel_laredo_qaoff_rel_laredo)) (Formerly ProCurve)"
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.11.2.3.7.11.152
iso.3.6.1.2.1.1.3.0 = Timeticks: (1943314994) 224 days, 22:05:49.94
iso.3.6.1.2.1.1.4.0 = STRING: "Trentino ..."
iso.3.6.1.2.1.1.5.0 = STRING: "s1..."
iso.3.6.1.2.1.1.6.0 = STRING: "Datacenter..."
iso.3.6.1.2.1.1.7.0 = INTEGER: 74
iso.3.6.1.2.1.2.1.0 = INTEGER: 38
iso.3.6.1.2.1.2.2.1.1.1 = INTEGER: 1
iso.3.6.1.2.1.2.2.1.1.2 = INTEGER: 2

Could you help me please?
Thanks again
Ivan.


Da: "Adam Armstrong" <adama@memetic.org>
A: observium@observium.org
Inviato: Giovedì, 17 marzo 2016 12:27:34
Oggetto: Re: [Observium] Alcatel OmniStack 6224 --> Aruba device - ArubaOS

I've split OmniStack into a separate OS, and it should collect more data now.

Thanks,
adam.

Sent from Mailbird

On 17/03/2016 09:38:49, Ivan Biasi <ivan.biasi@trentinonetwork.it> wrote:

Hi Tom

thanks for the fast reply.

The Observium database has not any sql-mode set in config files, the default mode is empty:
_______________________________
mysql> SELECT @@sql_mode;
+------------+
| @@sql_mode |
+------------+
|            |
+------------+
1 row in set (0.00 sec)
_______________________________

About the switch sysObjectId, 
here following the info:
_______________________________
iso.3.6.1.2.1.1.1.0 = STRING: "OmniStack LS 6200"
iso.3.6.1.2.1.1.2.0 = OID: iso.3.6.1.4.1.6486.800.1.1.2.2.4.1.1
iso.3.6.1.2.1.1.3.0 = Timeticks: (189007604) 21 days, 21:01:16.04
iso.3.6.1.2.1.1.4.0 = STRING: "Trentino ecc..."
iso.3.6.1.2.1.1.5.0 = STRING: "S3 ecc.."
iso.3.6.1.2.1.1.6.0 = STRING: "Datacenter ecc..."
iso.3.6.1.2.1.1.7.0 = INTEGER: 2
iso.3.6.1.2.1.1.8.0 = Timeticks: (0) 0:00:00.00
iso.3.6.1.2.1.1.9.1.2.1 = OID: iso.3.6.1.4.1.89.73
iso.3.6.1.2.1.1.9.1.3.1 = STRING: "RS capabilities"
_______________________________


The device was discovered some days ago, using the following command, with no particular alert messages ...I hope :-) :
add_device.php <switch_name_fqdn> <snmp_community> v2c

Thanks again for your help
I.


Da: "Tom Laermans" <tom.laermans@powersource.cx>
A: "Observium Network Observation System" <observium@observium.org>
Inviato: Giovedì, 17 marzo 2016 9:31:57
Oggetto: Re: [Observium] Alcatel OmniStack 6224 --> Aruba device - ArubaOS

Hi Ivan,

Can you tell us the sysObjectId for the device?

Some Alcatel wifi hardware is actually Aruba, something is likely set a bit too wide so it catches non-wifi stuff as Aruba too.

As to why it's not discovered, I'm not sure. It should discover just fine - however if discovery breaks before it's finished, it won't update the last_discovered field, and then you keep getting that message.

Try running discovery on the device by hand and see if something is failing. Make sure your MySQL is -not- set to strict mode.

Tom

On 17/03/2016 08:57, Ivan Biasi wrote:
Hi Adam and all

I'm trying Observium in a test environment, using some different network devices, and I found the following issue.

The Alcatel OmniStack 6224 switch is reported by Observium as an Aruba device running ArubaOS.
Selecting it on the GUI, the following banner appears:
"Device not yet discovered
This device has not yet been successfully discovered. System information and statistics will not be populated and graphs will not draw. This device should be automatically discovered within 10 minutes."

...but devices was added some days ago.
Here enclosed a picture to better understand the problem.

Is the Alcatel 6224 switch unsupported/partially supported,
or there are some configuration issues to identify and solve?

Thanks a lot, regards

Ivan.




_______________________________________________
observium mailing list
observium@observium.org
http://postman.memetic.org/cgi-bin/mailman/listinfo/observium