Trustpower is an Internet Service Provider (ISP) headquartered in New Zealand. Their history dates back to 1915 as Tauranga’s first power station. Now, Trustpower has over 700 full-time employees working throughout New Zealand. Read More
This article has two messages to deliver. The first being the technical piece where I review what the ICMP message means and what we tried to resolve the issue. The second is to illustrate the methodology used. I wanted to make those statements because in the past, some readers tend to concentrate too much on the technical information and gloss over the methodology part of the article. Read More
I feel sorry for ping. Ping has been beaten up, abused, misunderstood, banned and even tossed aside.
Ping was originally used to check if a device was up or down, period. Back in the day, equipment failure was very common. I chuckle thinking back at those sales people that used Mean Time Between Failure to sell their equipment. As network analysts, we needed a way to see if our hardware or equipment failed and ping did the trick.
Over the years, SNMP was introduced to aid in network visibility, but we still used ping for simple up and down checks. In the 90s, bandwidth limits were becoming an issue, so we used ping response time results to determine if a device or link was slowing us down.
In addition to a new reporting feature, the BeezKeeper 1.2 release includes the ability to export reports as PDFs. As with most features, this was much more complex to implement than we initially anticipated. But with a little bit of ingenuity, we were able to devise a solution. A major requirement of this project was the ability to inline our external CSS files. There were some libraries available, but none really gave us the flexibility we needed. Most fetched and inlined an entire external webpage, whereas we needed to be more selective. As a result, we wrote our own module which we intend to publish in the future, as it seems like it could be useful to someone else. Read More
We are excited to announce a fully redesigned and rebuilt Reports feature as part of the 1.2 update. This is one of the major features of 1.2 and has been a long time in the making. Historical network and performance data has always been a big part of monitoring and troubleshooting with NetBeez, so we wanted to make it more accessible and easier to work with.
The new Reports feature greatly expands the historical reporting capabilities of NetBeez. Previously, historical reporting was limited to Target-centric reports and output was divided between global and interval average reports. This setup made it difficult to get the full picture of past data, not to mention there was no option for Agent reports. Read More