Is there a way to graph the throughput on an interfaces where the OID keeps changing but the ifAlias stays the same
Seems my PPPoE0 interface on my edgerouter at home gets a different OID everytime it connects
Recently changed ISP and the new one uses PPPoE where as the old was just straight ethernet to the VDSL modem.
Can graph the physical eth interface but wondering if there's a way to monitor the traffic on the PPP interface directly.
For some reason Netxms seems to have decided to pickup the ETH 0.4 (Vlan4) interface on my UBNT edgerouter lite (EdgeOS 1.3) multiple times.
[02.11.2013 23:37:18] **** Poll request sent to server ****
[02.11.2013 23:37:18] Poll request accepted
[02.11.2013 23:37:18] Starting interface names poll for node <router name>
[02.11.2013 23:37:18] Checking interface 2 (eth0)
[02.11.2013 23:37:18] Checking interface 1 (lo)
[02.11.2013 23:37:18] Checking interface 4 (eth2)
[02.11.2013 23:37:18] Checking interface 5 (eth0.10)
[02.11.2013 23:37:18] Checking interface 3 (eth1)
[02.11.2013 23:37:18] Checking interface 6 (eth0.9)
[02.11.2013 23:37:18] Checking interface 7 (eth0.31)
[02.11.2013 23:37:18] Checking interface 8 (eth0.4)
[02.11.2013 23:37:18] Checking interface 9 (eth0.6)
[02.11.2013 23:37:18] Checking interface 8 (eth0.4)
[02.11.2013 23:37:18] Checking interface 8 (eth0.4)
[02.11.2013 23:37:18] Finished interface names poll for node <router name>
[02.11.2013 23:37:18] **** Poll completed successfully ****
)
I Suspect it might be because I added Vlan 6 earlier today which wasn't there before
EdgeOS is forked from Vyatta and uses Debian Mips as it's base OS I believe, Vlan view doesn't show anything but I suspect it's because it's pretty much a Linux box as far as NetXMS is concerned.
Edit:
Just after posting this I've Realised why eth 0.4 is showing multiple times, it's because it has multiple IP addresses
Edit2:
Is there any way to merge hosts, as I have some that because they have multiple IP's and presumably no netXMS agent are showing up as multiple devices.
@sohgnar said in DCI for Bits/s:
Dragon, If you're monitoring traffic and want to display the graphs in bits per second instead of bytes just add the following transformation
$1 * 8
That should do the trick. Just remember to update your legends so they are displaying mb/sec or something to that affect.
Yep figured out how do to that, but I want to Create DCI's for multiple interfaces and didn't really fancy going into each one individually and making that change
@victor said in DCI Spike removal:
Hi!
You can add transformation script like this:
if ($1 > 100) return 100; return $1;(replace 100 with your maximal meaningful value).
Best regards,
Victor
That would probably do it thanks.
Is it possible when using DCI's to store values for things like bandwidth usage to have an option to scan through the data and remove spikes caused by things like counter resets due to reboots.etc
I don't think my home connection is quite capable of transferring 5.5TB/s
I'm probably just being silly but how do I ignore an entire subnet in netxms.
One of the objects my installation is monitoring is my Home Firewall/Router, and therefore it keeps alarming when devices dissapear off my home network which happens quite a lot with devices like smartphones going in and out of sleep.
I want it to monitor the Router itself but I don't care about the devices behind it.
I have passive/active scanning set but my home subnet is not in the list of subnets to scan.
Is it possible to have netXMS create a graph which also includes a line for 95%ile (Or whatever % the user configures)?
Ah Thanks
Sorry if this is a Silly question I did search but didn't find the answer (Doesn't mean It's not here somewhere but more likely i'm just not very good with the search syntax 
)
What's the simplest way to create DCI's that operate in Bits rather than Bytes/s?
I know If I right click on an interface > Create DCI tick the ones for inbound/outbound traffic it creates a DCI fr Bytes/s
I can edit that DCI and apply a transform to change it into Bits /Sec which is great if I only want to do it for a single interface but it would become tiresome very fast if I wanted to do it for several interfaces.