Hi all,
It is possible to give a user access to a port on for example a switch. But
you can't give them specific access to a sensor. With the ipoman for
example i would like to give a user access to a specific sensor, so they
can monitor their powerport and their ampere consumption.
Would it be possible to implement this in the authentication protocol?
--
Alexander Lantink
ColoCenter bv
http://www.colocenter.nl
info(a)colocenter.nl
Can someone help me understand the algorithm/conditions that will cause
a device to be flagged up/down in Observium?
Reason I ask is I'm seeing instances where devices will get flagged as
'down' however when I login to the Observium host and manually test via
fping/snmpwalk, I get valid responses back. The devices come back a few
minutes later.
I don't see anything in observium.log aside from poller completion
results, so I could use some more info/ideas to help debug why these
devices keep going offline intermittently.
Cheers,
-Chris
Hiya,
I'd like to make a feature request. It's a slight modification really.
In the User Management -> Edit User section you can grant a user access to a
device by selecting a device from a drop down box.
Would it be possible to change this from a single select to a multi-select
box please?
We may have to add over a hundred devices to several users. A multi-select
would reduce this work from mind-numbing to merely tedious.
Thanks,
Mike
--
Mike Richardson
Networks (network(a)manchester.ac.uk)
IT Services, University of Manchester
*Plain text only please - attachments stripped on arrival*
Hi everyone,
just would like to know, if there is already a "just undocumented" RANCID
integration for Observium?
I found a list point in the docu wiki, so I am just curious about.
You guys do a great job, btw!
Best regards,
Florian
Hi there,
I was wondering if anyone's got an idea as to why graphs would suddenly stop working? (see attachment)
I hadn't updated anything or changed anything, the rrd's all have data in.
It's running off Centos 6.2
Any ideas on how to troubleshoot?
[cid:18152FC1-6ED1-47C0-8A4D-DC5CBEF4B7BF@mill-ny.com]
Hi,
I came across a design flaw in ifAlias.
First of all the flaw:
declare -a INTERFACES=($(ip l|grep mtu|cut -d: -f2|sed s/\ //g))
...
INTERFACE=$(echo ${INTERFACES[$INDEX]}|cut -d@ -f1)
The Interface INDEX is rarely equal to the indexes of the array.
Thus getting all interfaces here is useless, we already get the right Interface ID from SNMPd, so the fix is:
#declare -a INTERFACES=($(ip l|grep mtu|cut -d: -f2|sed s/\ //g))
...
#INTERFACE=$(echo ${INTERFACES[$INDEX]}|cut -d@ -f1)
INTERFACE=$((ip l | grep "^${ID}: " | cut -d " " -f 2 | sed 's/://g') 2> /dev/null)
This way, even when tap* respawns with a new INDEX it will still be mapped to the right Description and Alias.
A 2nd bug has been spotted in snmpbulkwalk vs snmpwalk; snmpbulkwalk -QOUs [...] ifAlias leaves out some descriptions but snmpwalk does not, needs further investigation for now I just hacked the snmp.inc.php...
Kind Regards,
Daniel Preussker
[ Security Consultant, Network & Protocol Security and Cryptography
[ LPI & Novell Certified Linux Engineer and Researcher
[ +49 178 600 96 30
[ Daniel(a)Preussker.Net
[ http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x87E736968E490AA1
