Hello,
I have an x86 installation on a PC at 2 locations. I have them on UPS' but still continually reset due to extended power outages or other circumstances. As I use the data usage statistics for monthly billing, is there anyway to keep this data on reset or to send it somewhere else to be managed? I would greatly appreciate anyone's help with this.
James
Re: How to keep usage data if the Mikrotik resets
Use an external server to query the routers via SNMP and then persist the data read.
Re: How to keep usage data if the Mikrotik resets
Hello,
Thank you for answering me. Could you please just add a little more detail on what I would use to do that? Would that be something like Cacti?
As I said I have two of them, both on different subnets but both have routable IP's. Will this one server be able to do both?
The other thing is that I use Tranzeo wireless equipment and I think it can report using SNMP as well.
Thank you again for your assistance.
James
Thank you for answering me. Could you please just add a little more detail on what I would use to do that? Would that be something like Cacti?
As I said I have two of them, both on different subnets but both have routable IP's. Will this one server be able to do both?
The other thing is that I use Tranzeo wireless equipment and I think it can report using SNMP as well.
Thank you again for your assistance.
James
Re: How to keep usage data if the Mikrotik resets
Cacti is one solution, it graphs things for you via SNMP. There's also Nagios, which is an entire monitoring solutions. There are many other for pay and open source products. Mikrotik makes "The Dude", which is free.
Yes, one monitoring system instance would be able to monitor any system it can reach. And if you need to monitor systems you cannot reach via the public Internet you could always build VPN tunnels, and monitor across those.
An entirely different approach is Traffic Flow, which is a NetFlow implementation that returns on data connections through a router, including how many bytes were used in the connection, and which end points were involved. Again, there are many open source and for pay collectors out there. It is very commonly used for billing.
Getting a monitoring solution in place is a good idea for many reasons - not only will it persist storage of billing data for you, but it will also enable you to receive alerts when gear goes down, or passes critical thresholds for WAN circuit, memory, CPU etc. utilization.
Yes, one monitoring system instance would be able to monitor any system it can reach. And if you need to monitor systems you cannot reach via the public Internet you could always build VPN tunnels, and monitor across those.
An entirely different approach is Traffic Flow, which is a NetFlow implementation that returns on data connections through a router, including how many bytes were used in the connection, and which end points were involved. Again, there are many open source and for pay collectors out there. It is very commonly used for billing.
Getting a monitoring solution in place is a good idea for many reasons - not only will it persist storage of billing data for you, but it will also enable you to receive alerts when gear goes down, or passes critical thresholds for WAN circuit, memory, CPU etc. utilization.