- observium - lists.observium.org

Cisco WLC access points
by krause＠rus.uni-stuttgart.de 26 Nov '14

26 Nov '14

Hi, since Aruba access points are found just fine, is there anyone having Cisco APs on WLC/WiSM2 in Observium already? If not, has anyone checked already how much "patching" would be required to feed those APs into the db model? Best, Kilian

3 3

Refreash of login page
by Fältman, Mikael 26 Nov '14

26 Nov '14

Hi. There is an html instruction making the login page to be refreshed every 300 sec. If you try to login to Observium using wrong credentials (user may have forgot it) and then leave the web browser there will be an Failed login event every refresh cycle. This leads to unnecessary alerts in SIEM systems for those who are doing security monitoring. Are there a need to have the login page refreshed ? Regards Mikael

2 1

Unable to login
by Aaron Smith 25 Nov '14

25 Nov '14

Hi everyone, We're testing Observium and I've come across an issue with logging in this morning. I have LDAP/Active Directory configured for auth and has been working perfectly up until now. At first I thought it was my account, but nope all good there. Then I thought it was the LDAP configuration so I changed the config back to the default mysql auth but still not able to log in. I tried rebooting the box but didn't work either also checked the file system and it's not full. I also tried deleting the cache and cookies and using different browsers but still no dice. Not sure if it's related but I updated to the new CE yesterday but it was working fine after the update yesterday afternoon. Any help will be much appreciated! Thanks.

2 1

Graphs netstats error
by Simon Smith 25 Nov '14

25 Nov '14

Hi All, after the latest SVN update 6009 my Netstats page on my Mikrotik equipment show the wrong graph? attached screenshot showing what i mean i think the is still a bug? how do i revert back one version as this was fine till just before Regards Simon

3 3

Webpage stays blank after update to 0.14.11.6008
by Branzko, Matthias 25 Nov '14

25 Nov '14

Hello all, today morning I did an update from an older version of observium (sorry, don't know the exact version - but IIRC only 1 sql update file was executed afterwards) to the latest svn version. But if I try to open the Observium in the browser, the page shows nothing (only white background is shown). First I thought it's an issue with LDAP-Authentication. So I switched to mysql, created a new user with permission 10 and tried again. But still no luck. The user database looks like: mysql> select * from users; +---------+-------------------+------------------------------------+-----------------+--------------------------+-------+-------+-------------------+--------------+ | user_id | username | password | realname | email | descr | level | can_modify_passwd | user_options | +---------+-------------------+------------------------------------+-----------------+--------------------------+-------+-------+-------------------+--------------+ | 4 | admin | xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx | | root@localhost | | 10 | 1 | NULL | If I try to open the webpage with debug=1 the following output is shown: > $vars /opt/observium/includes/common.inc.php:196SELECT * FROM `entity_permissions` WHERE `user_id` = '4' string(56) /opt/observium/includes/common.inc.php:196SELECT `value` FROM `users_prefs` WHERE `user_id` = '4' AND `pref` = 'atom_key' string(79) /opt/observium/includes/common.inc.php:196SELECT `value` FROM `users_prefs` WHERE `user_id` = '4' AND `pref` = 'atom_key' string(79) /opt/observium/includes/common.inc.php:196SELECT * FROM `device_graphs` ORDER BY `graph` string(46) /opt/observium/includes/common.inc.php:196SELECT * FROM `devices` ORDER BY `hostname` string(43) /opt/observium/includes/common.inc.php:196SELECT `device_id`, `ports`.`port_id`, `ifAdminStatus`, `ifOperStatus`, `deleted`, `ignore`, `ifOutErrors_delta`, `ifInErrors_delta` FROM `ports` LEFT JOIN `ports-state` ON `ports`.`port_id` = `ports-state`.`port_id` string(244) /opt/observium/includes/common.inc.php:196SELECT * FROM `sensors` LEFT JOIN `sensors-state` ON `sensors`.`sensor_id` = `sensors-state`.`sensor_id` So the login or mapping to user_id seems to work. Any ideas / what to do next? Thanks in advance Matthias

3 3

Power Meter MIB
by chott＠praha1.net 25 Nov '14

25 Nov '14

Hello, i have I have Power Meter HWg-PWR - http://www.hw-group.com/products/HWg-PWR/hwg-pwr25_M-bus_gateway_en.html Is there some future implementation? Tomas

2 3

CE 0.14.11.6000
by Dan Ratzlaff 25 Nov '14

25 Nov '14

Thanks for the new version! My RADLAN and BCM PowerConnect switches show up nicely now. I recently picked up a few Cisco Small Business switches, but Observium wasn't detecting them correctly. After some digging, I found I only needed to add their sysObjectID's to the definition file: diff --git includes/definitions/os.inc.php includes/definitions/os.inc.php index c54d476..135f3ae 100644 --- includes/definitions/os.inc.php +++ includes/definitions/os.inc.php @@ -714,6 +714,8 @@ $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.81."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.82."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.83."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.85."; +$config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.87."; // SF200-48 +$config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.88."; // SG200-50 $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.89."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.9.6.1.11.82."; $config['os'][$os]['sysObjectID'][] = ".1.3.6.1.4.1.3955."; Thanks! -- Dan

5 5

Mako
by Tom Henderson 24 Nov '14

24 Nov '14

Has anyone used any of the Mako appliances (http://www.makonetworks.com/) with observium? They have their own management/monitoring platform but wondering if I'll be able to also add them to our observium server. We're looking at the 6500 model. Cheers Tom Henderson IT Manager | Pack & Company | 027 461 4403 | 09 929 2750 | tom(a)pack.co.nz -- ---------------------------------------------------------------------------If you are not the intended recipient of this email, you must not disclose, copy, or distribute any information contained in or attached to it, or take any action/inaction based on it. Please contact us immediately, and delete this email from your system. Any views or opinions presented in this email are solely those of the author and not of Pack & Company (NZ) Limited (the "Company"), however any intellectual property contained in or attached to this email is the property of the Company. Thank you.

2 1

idrac
by Robert Hatch 24 Nov '14

24 Nov '14

Dear all, Has anyone had any success in using observium with idracs? The auto discover doesn't appear to find any useful sensors other than the physical nic of the idrac itself. Has anyone else worked on support for idracs? All the best rob

5 17

Interface Parsing
by Robert Hatch 24 Nov '14

24 Nov '14

Dear all, Just wondering if there was an appetite out there for expanding the interface labelling feature of observium. The existing description parsing (http://www.observium.org/wiki/Interface_Description_Parsing) is pretty useful but also a bit limiting at times, as it seems more useful when labelling layer 3 services and less so for layer 2. Just a few general comments: * For us the pseudowires tab does not seem to auto populate (we use a variety of juniper, brocade and extreme switches and routers), just wondering if I have missed something here... * This aside there are more frequent occasions where we are providing VPLS services for a client and it would be nice if it were possible to label an interface as both a customer and a P2P link for example and then have these separately broken down in observium itself * There are also occasions where it would extremely useful to label backhaul circuits such as dark fibre and waves. Currently the only option for this is to label things as core but that page becomes so big it is not that useful unless you know what you are after (and then you would just go straight to the interface). Something like BACKHAUL: , PROVIDER:, END (A/B etc.) would be immensely useful and time saving. * The other issue we have that I don't have a simple answer for is the unhelpful aggregation of customer switch ports (quite often both ends of a P2P) and their layer 3 router ports. Could we start by having a separate aggregate graph for each circuit reference for each specific client. Maybe if END A and B are specified then the graph could demonstrate that these are actually different ends of the same link? What do people think? BW rob

3 3