Thursday, February 17, 2022

A Black Box for Everything

 



In the aftermath of a plane crash, one of the first things the accident investigators look for is the flight recorder. Inaptly named the “black box”, it is neither a box, nor is it black – a very bright shade of red is much easier to locate. Recording on a virtual continuous loop, it presumably will have a record of events for the last critical moments of the flight.


Beginning in the 1990’s, the magnetic tape units originally used in flight recorders were replaced by solid state memory boards. Today, the Boeing 787 Dreamliner can log 146,000 separate flight parameters, resulting in several terabytes of data per flight. There is a separate recorder which preserves the last two hours of cockpit audio (crew member expletives included). All this data requires sophisticated analysis software.


Automobile dash cameras, building surveillance cameras and law enforcement body-cams are further examples of how pre-event data logging has infiltrated our lives. Thieves have been apprehended, legal issues have been resolved, and car vandals have been brought to justice using this recorded information. Imagine what a future civilization might think of us if they unearthed all this data.


While it might be satisfying to show the police a video of the person who keyed your expensive car, there are folks who are taking a more expansive view of so-called “Black Box” recording. Climate change is yet another of those divisive issues of our times, and there are those on one side who want to preserve a clear picture of what we humans were doing leading up to what they believe is the inevitable crash of the earth as we know it.


A consortium of like-minded data researchers, architects and artists are putting together a repository that will sit in environmentally and geopolitically safe Tasmania beginning later this year. The original design is intended to last for 50 years, which is longer than the climate clock implies we have left. Work is already underway to extend that life just in case earth outlasts the clock. Three-inch-thick steel walls are meant to protect the archives from whatever might destroy earth, although allowing for visitors to access the information stored in the box remains unsolved.


John Wooden once wrote “The true test of a man’s character is what he does when no one is watching.” Earth’s flight recorder will hold humans accountable for climate change by documenting news articles, scientific journals, tweets, and other assorted records. Land and ocean temperatures will be charted, along with atmospheric greenhouse gas concentrations and biodiversity losses. As a measure of our changing priorities, military spending will be included. It is hoped that an archive of leaders’ climate-conserving efforts will inspire more. Expletives will likely be omitted to conserve storage space.


Some scientists see very little evidence that global warming will result in human extinction, but others remain concerned. How this story ends is anyone’s guess, but all of the events, actions and in-actions will be faithfully recorded in Tasmania.


As pilots say, brace for impact.



Author Profile - Paul W. Smith - leader, educator, technologist, writer - has a lifelong interest in the countless ways that technology changes the course of our journey through life. In addition to being a regular contributor to NetworkDataPedia, he maintains the website Technology for the Journey and occasionally writes for Blogcritics. Paul has over 40 years of experience in research and advanced development for companies ranging from small startups to industry leaders. His other passion is teaching - he is a former Adjunct Professor of Mechanical Engineering at the Colorado School of Mines. Paul holds a doctorate in Applied Mechanics from the California Institute of Technology, as well as Bachelor’s and Master’s Degrees in Mechanical Engineering from the University of California, Santa Barbara.


Monday, February 14, 2022

Performance Testing; Network vs Storage

 I’m sure we’ll all been there; you are working on a ‘performance issue’ and another technician tells you, “I don’t know what the problem is, ping response time is fast and ping didn’t report any dropped packets.”


I’ve written and spoke about this before, but want to briefly cover my concerns surrounding ping. I will start with a simple statement that I am not ‘anti-ping’ and actually use it quite often. My concern is that I see it used in the wrong scenarios and its operation is widely misunderstood.


Things you should know about Microsoft’s ping command include that they are sent at a 1 second interval, uses ICMP as its protocol and neither option are configurable. Other default settings you can change are default payload size (-l), TTL (-i), disabling resolve to address (-a), setting do not fragment (-f) and forcing to just use IPv4 (-4).


I personally prefer to use hrping (https://www.cfos.de/en/ping/ping.htm) as an alternative to Microsoft’s ping since it has many more options and still a command line tool, even though hrping also provides a GUI interface as well. This utility can send UDP packets, send a ping size ‘sweep’ of various sizes, send ICMP timestamp requests, interval between packets as well as the same options as the Microsoft ping command.


In summary, I use ping to validate or verify if the network and hosts are responding and if there is general packet loss. If the ping test results in no packet loss and response time is acceptable, I test the client or server performance.


If you want to test network performance, nothing beats iperf3 (https://iperf.fr/) but if you want to test the file system, copying a file is the easiest test. I know, this isn’t the same as sending hundreds of transactions, etc. but it’s a great start. In this video I show you how I used a simple Powershell command (Measure-Command) to time how long it took to copy files to/from my server.


In this video, I show you how I used iperf and a power shell command to copy a file (both read/write) on two different shares to identify if the issue is file system or network related.




Wednesday, February 2, 2022

Microsoft Command line and Wireshark utilities

 I get quite a few emails expressing frustration and confusion when people try some of the Windows Wireshark command line utilities like tshark, dumpcap and editcap to mention a few.

The main issue is that many times the Wireshark application folder is not in your path. There are many ways to get around it like

- Change drive and directory to the Wireshark application folder from within the command prompt

- The use full application path for the wireshark utility you are trying to run (ie c:\program files\Wireshark\tshark -D)

- Add the Wireshark application fold to your path – which is the one I will cover in the video

I prefer adding Wireshark to the path so I can type the command from any folder, anytime without having to worry about which folder I’m in as well as typing the fill path with the command.



Popular post