Skip to main content

The articles by Ronald Bartels on LinkedIn about software defined wide area networking (SD-WAN) including last mile telecommunications

This is a list of all my articles about software defined wide area networks (SDWAN) on LinkedIn in order of popularity:
  1. The IF THEN ELSE of SDWAN - reality versus the lab. (109609)
  2. eTOM - the dinosaur of telecommunications. (17152)
  3. The business of SDWAN - from the top down. (8106)
  4. SDWAN data usage measurement requirements for service providers and the enterprise. (1250)
  5. The importance of Internet Peering Exchanges in the deployment of SDWAN. (1040)
  6. The primary goal of SDWAN should be to make networking less complicated (762)
  7. WHILE outage { CASE step; i++ } - how SDWAN improves Mean Time To Repair (646)
  8. How to improve the up time on your SDWAN. (624)
  9. Watt about the power of SDWAN - the volts and amps of CPEs. (530)
  10. The awesomeness of the IPX protocol and why you need something similar for SDWAN. (517)
  11. The Network Management Challenge of SDWAN - avoiding ugly babies. (458)
  12. What is SDWAN? You can google it or read about it here! (418)
  13. SDWAN's functional specifications - the nuts and bolts of this new form of connectivity. (410)
  14. SDWAN is not about the intangibles but Genchi Genbutsu. (343)
  15. 7 points to consider when troubleshooting a wireless link. (328)
  16. SDWAN form factors - more than a using a white box as a default template (324)
  17. Why an SDWAN deployment should have two last mile telecommunications providers as default (316)
  18. The skinny on SDWAN based data centre to data center connections (227)
  19. The attributes of networking that contribute to user experience (216)
  20. Putting a nappy on the screaming baby - dealing with incidents in a telco using workarounds (216)
  21. Puffing about power - mining social media for operational data (213)
  22. Proactive monitoring of the last mile in telecommunications (210)
  23. Managing the Customer Premise Equipment in a Telco (oft overlooked in telecommunications service delivery) (130)
  24. SDWAN and some magic sauce (129)
  25. Creating a resilient SDWAN - eliminating wide area networking single points of failure (127)
  26. The use case for IPFIX in SDWAN (121)
  27. Location, location, location. The relevance to SDWAN. (115)
  28. The use case for IPFIX in SDWAN (115)
  29. Using baselining in SDWAN to detect potential problems (111)
  30. SDWAN and path protection - the fly in the ointment (49)
  31. The importance of doing commissioning tests when provisioning a last mile link (48)
  32. Availability in the last mile for telecommunications. (37)
  33. Don't call us, we'll call you - the unachievable expectation set by service providers (29)
  34. The neat little trick SDWAN uses to make a last mile link faster (29)
  35. Combining SDWAN and the throttling technology used in ISPs (28)
  36. Enterprise WiFi Access Points need to be nodes on a SDWAN (24)
  37. Merging SDWAN and Cloud (16)
  38. The use case for SDWAN in South Africa (16)
  39. Automation is crucial to service assurance success (13)
  40. 5 important things you need to know about your SDWAN hood (12)
I am open to any discussions and opportunities around SDWAN. Please inbox me.

Comments

Popular posts from this blog

Why Madge Networks, the token-ring company, went titsup

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks which I wrote about here went titsup. My analysis is that Madge Networks had a solution and decided to go out and find a problem. They deferred to more incorrect strategic technology choices. The truth of the matter is that when something goes titsup, its not because of one reason only, but a myriad of them all contributing to the negative consequence. There are the immediate or visual ones, which are underpinned by intermediate ones and finally after digging right down, there are the root causes. There is never a singular root cause for anything but I'll present my opinion and encourage everyone else to chip in. All of them together are more likely the reason the company went titsup. As far as technology brainfarts go there is no better example than Kodak . They invented the digital camera that killed them. However, they were so focused on milking people in their leg

Flawed "ITIL aligned"​ Incident Management

Many "ITIL aligned" service desk tools have flawed incident management. The reason is that incidents are logged with a time association and some related fields to type in some gobbledygook. The expanded incident life cycle is not enforced and as a result trending and problem management is not possible. Here is a fictitious log of an incident at PFS, a financial services company, which uses CGTSD, an “ITIL-aligned” service desk tool. Here is the log of an incident record from this system: Monday, 12 August: 09:03am (Bob, the service desk guy): Alice (customer in retail banking) phoned in. Logged an issue. Unable to assist over the phone (there goes our FCR), will escalate to second line. 09:04am (Bob, the service desk guy): Escalate the incident to Charles in second line support. 09:05am (Charles, technical support): Open incident. 09:05am (Charles, technical support): Delayed incident by 1 day. Tuesday, 13 August: 10:11am (Charles, technical support): Phoned Alice.

A checklist for troubleshooting network problems (22 things to catch)

  Assumptions! What is really wrong? Is it the network that is being blamed for something else? Fully describe and detail the issue . The mere act of writing it down, often clarifies matters. Kick the tyres and do a visual inspection. With Smartphones being readily available, take pictures. I once went to a factory where there was a problem. Upon inspection, the network equipment was covered in pigeon pooh! The chassis had rusted and the PCB boards were being affected by the stuff. No wonder there was a problem. In another example, which involved radio links. It is difficult with radio links to remotely troubleshoot alignment errors. (I can recall when a heavy storm blew some radio links out of alignment. Until we climbed onto the roof we never realised how strong the wind really was that day!) Cabling. Is the cable actually plugged in? Is it plugged into the correct location. Wear and tear on cabling can also not b