Again, if we don’t have the exact date and time, we’ll be in trouble when it comes to monitoring.ĭo you want to discover the most flexible monitoring software on the market? They always start with the date of Novemand if we are in a “hostile” environment, where they are unable to connect to any local area network, we can buy a PSTN such as this one. This architecture allows for the saving in transistors, thus resulting in a small processor size and consequent energy savings.Ī special feature of Raspberry Pi is that they do not have a real-time clock ( RTC) so they depend on the communication with the outside world through the Network Time Protocol (NTP) in order to record the date and time of their operations, which is very important when monitoring. Its Central Processing Unit (CPU) is its Reduced Instruction Set (RISC) Computer Architecture called ARM (Advanced RISC Machine), 32-bit and now 64-bit on the Raspberry Pi 3 model. It has many operating systems, a well-known one that is derived from Debian is Raspbian.There are also Pidora (based on Fedora), SUSE and Arch Linux, based on ARM (see the following point). Although its hardware is privative and made in China, its operating system and applications are completely Open Source.But if you are your "network team", you need to check the docs for your network boxes to see what is available.In Wikipedia we can find all the details about Raspberry Pi, we would like to highlight the following: I am not an expert in this stuff so I cannot really comment further.
Your network team should be using these or some other technique to monitor their boxes. They can also report their statistics via snmp but this requires software that you need to purchase. They tend to have a service port that you can access via telnet. Routers and switches keep on-board statistics. Most ftp clients perform the timing automatically. To measure performance host to host, I usually just ftp a 1 GB file and time the result. If your routers and firewalls allow traceroute to work, it can tell you where a delay is.if it is a persistent delay. To measure latency across a complex network, traceroute is an option. Still, this is a start and you should ensure good communications with your system's link partner. Your average unix host is connected to an ethernet switch and can only see packets to and from it.
And these days, even that becoming very rare. At best, this will only enable measurements on the local ethernet segment. With HP-UX, lanadmin can do that (in menu mode). But I will assume that your network is identical to mine and work from there.Įvery unix system that I know of has some way to see statistics kept by the lan driver. Someday, I hope, people will include a few details with their questions. What you can do depends on your network topology and your specific OS.
0 kommentar(er)
