Monday, October 16, 2023

For Cryin Out Loud, DOCUMENT!!

 



When I walk into a client site, I assume they either don’t have documentation, or it's not current and I would say that assumption is usually 90% correct.


Trust me, I totally understand, documentation is really tough to keep up to date since many people and departments ‘touch’ equipment. When I say ‘touch’ I mean physically and remotely.


Over time, changes and troubleshooting cause a cable to get move, a config gets tweaked and after a few years, this amounts to many small changes that gets hard to dig out from.

In this quick video, I suggest something simple when making physical changes, a simple photo. The photo could be of a rack, a room or equipment. After you take the photo, make a folder with the name of whatever is in the photo is and name the photo the date as the prefix.


For example, 2023_09_28_Router6.jpg would be a photo of Router6 September 28, 2023.

If you want to take the next step, you could simply put the images in a word doc, PowerPoint, or webpage as a reference.


I find if the process isn’t time-consuming, technicians are more likely to do it, and everyone has their phones with them.


Thursday, October 12, 2023

Good Enough

 

In my very first job as a young engineer fresh out of college, I worked under an old, curmudgeonly manager who was approaching retirement. Bob (his real name) was an anxious chain-smoker, in the days when smoking in the office was allowed. For all his idiosyncrasies, he taught me some important lessons about “thinking outside the book” (my words, not his). Without articulating it explicitly, Bob clearly understood the difference between knowledge (information about a subject) and wisdom (good sense, judgment and insight). When prioritizing our workload, Bob would often say “If it ain’t broke, don’t fix it.” Getting one thing perfect was less satisfying to Bob than producing lots of things.


The origin of this phrase is a bit murky, but it is often credited to Bert Lance, Director of the Office of Management and Budget in the Carter administration. Bert was first quoted as saying it in the May 1977 issue of the magazine Nation’s Business. Author William Safire wryly commented that it “has become a source of inspiration to anti-activists.” The expression went viral, before viral was even a thing.


Our academic experience is the beginning of the relentless pursuit of perfection that plagues many of us. Efforts are constantly being assigned a place on the scale, with “A” being perfect, “B” and “C” good enough, and anything less a failure. In today’s culture, leisure is looked upon with envy – a leisurely attitude toward work is not. It is common to hear the term “Puritan Work Ethic”, referring to the pervasive and desirable drive to work hard. The Puritans, as it turns out, were working hard not to get better stuff, but to appease God and better their chances for salvation.


One of my most beloved mentors – who later served as my faculty advisor for Ph.D. studies at Caltech – was Dr. Bill Iwan. Dr. Iwan showed me how to balance the yin-yang of wisdom and knowledge both inside and outside of academia. As I was grappling with feelings of hope and fear just prior to my oral candidacy exam, he encouraged me by pointing out that at that particular moment, I had more knowledge about more things than I probably ever would in my career. He added that wisdom gained from my work in industry prior to returning to graduate school would be an advantage. After passing the exam and beginning my dissertation research, Dr. Iwan advised that this would probably be my last opportunity to work on a project until it was finished rather than until it was due.


Surveys have been warning us for some time of the creeping fatigue and malaise penetrating the American workforce. Researchers have also found that living a long and satisfied life doesn’t correlate with ambition. Professional status and fat salaries do not make us significantly healthier or happier than those with less ambition, nor do they make us less happy. The pandemic may have been the last straw that rallied many burned-out workers to finally act. The Great Resignation and quiet quitting have been studied by Professor John Kammeyer-Mueller from the University of Minnesota’s Carlson School of Management who has concluded that we are not suffering from waning motivation, but refocusing on things we would rather spend our time on. Mental health, it seems, is the newest and trendiest fitness goal.


I have Dr. Iwan to thank for showing me that life offers few opportunities to work on something until it is perfect. Bob was also more prophetic than I first thought, showing me (by analogy) the importance of prioritizing joy over perfection. In many cases, imperfection is a far better fate than unhappiness.


Author Profile - Paul W. Smith - leader, educator, technologist, and 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 50 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 a Bachelor’s and Master’s Degree in Mechanical Engineering from the University of California, Santa Barbara.



Monday, October 9, 2023

Using A Printer for A WIFI Survey

 

Troubleshooting WiFi can be challenging enough without adding a remote variable to it.

There are times when I wish I could perform a remote Wifi survey. Some access points allow that feature, but rarely do I have access to the client’s access points, nor do I want access. You know, just in case something happens, I don’t want people thinking I was mucking around.

A simple solution is to physically go over with a wireless test tool like netAlly’s Aircheck G3 (https://www.netally.com/products/aircheckg3/) , our smartphone, or your laptop.

Things start to get tricky when the location is remote. That’s when you can rely on your access point, but be careful since some vendors will cut off all wireless clients while performing a wireless scan. Another option is to purchase wireless sensors that you can connect and perform a scan. And lastly, is to remote into someone’s laptop and check to see which wireless networks they hear.

One trick I like to use, when possible, is to determine if they have a wifi printer at the remote site, web into it (they rarely have passwords) and run the printer test/diagnostic feature. Most Wifi printers will also provide wireless information including all the SSID’s it hears.

Friday, October 6, 2023

Troubleshooting Loops: IPv4 ID/TTL and Addressing Notes

 

Before I start, let the first cover a very common question I get asked. I will not be providing vendor-specific information on this troubleshooting example. Nor will I be sharing the trace file.


The goal of this article and video is to introduce you to the methodology, tips and tricks, and other things that you may not have thought of when you perform protocol analysis.

On to the problem; I covered a little bit about this in previous articles when I was talking about making a larger trace file manageable.


The client is complaining that the network has performance brownouts and wireless clients tend to get dropped off. So, I asked them to connect his computer to any port on that same VLAN, start a capture for a few minutes and then stop it, and send it to me. I then filtered the capture device’s traffic out and will go through the remaining packets and this exercise.


In the video, you will see how I leverage the IP identifier, time to live, and MAC addresses to determine what is happening. When I present or teach, I stress the goal of troubleshooting is to either prove what the issue is NOT or to figure out where your test point is with the final target being identifying the root cause.


Spoiler alert, the high packet rate of small broadcast packets is causing the problem.


Popular post