LAN Damager

Ronald BartelsRonald Bartels
7 min read

No alt text provided for this image

There I was shooting the breeze with an old mate. The conversation turned to why Madge Networks 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 legacy film market that they never saw the tsunami. That tsunami also dealt a killer blow to another innovative company named Polaroid. Madge was a pre-cursor to Kodak and Polaroid. They perfected Token-ring and should have moved to developing silicon for future Ethernet and WiFi networking kit. Instead they went to merger and acquisitions but lacked the savvy skill in the disciple that Cisco mastered. Ironically, Cisco did make an offer to Madge Networks which wasn't accepted. As they say in this part of the savannah, "Eish!"

My first encounter with Madge Networks was in 93/94 installing the FDDI adapters into Netware SFT III servers. Only adapters that worked without crashing the system. From that day I was a Madge fan.

Any conversation about this topic requires discussing the "Switching to ATM" strategy. The reasoning was clumsy, but sounded sophisticated at the time. In essence it was backing the wrong horse. It was complicated and did not address the market for the desktop. The silicon for desktop connectivity was never going to be ATM. At that time there was also the Token-ring versus Ethernet debate. The conclusion was that Ethernet won but in actual fact users actually opted for wireless radios for their desktop networking instead of a clumsy wired connection. WiFi beat both Token-ring and Ethernet and most computing devices don't have Ethernet. Think smartphones and laptops. Ironically, the Ethernet technologies today have more attributes of Token-ring than Ethernet as on the fibre side the standards all have their origin in FDDI. (Remember FDDI???) As an aside, one of the most stupid legacy defaults from Ethernet is it's pathetically small frame size. Token-ring was designed far better on so many fronts and this was one of them! BTW: Nowadays you get Ethernet rings as specified by G8032. Taking about rings, another great attribute of Token-ring was source route bridging. It was miles better than Ethernet which only had pathetic transparent bridge. Token-ring allowed the creation of a far larger layer 2 domain without melting down due to broadcasts. Ethernet was forced to layer 3 to achieve equivalence.

All that effort in making a Token-ring MAC in hindsight could have best been used by Madge in leveraging the acquired silicon developing expertise to climb on board the storage networking bandwagon that was about to hit. The underlying requirement was for high speed storage (never video or the other Jet Jetson technologies that was going to drive ATM). One of the driving attributes of ATM was that it had QoS. However, it wasn't the only way to solve it. Using higher level protocols it was possible with Ethernet to have RSVP that did the same thing. And the silicon was way cheaper, as the cost reduction of Ethernet had already been progressing for a number of years. Nowadays, most multimedia traffic that requires prioritization uses Diffserv. Not really a sophisticated QoS as defined by the ATM standards but it does the job.

No alt text provided for this image

Somewhere in the late nineties some pony tail decided to change the Madge corporate identity. A change in corporate identity never works and never increases sales. No company has succeeded, but yet companies all try it. The only people who make money are the marketing agencies hired to do the job and the company that self inflicts itself with this dumbass decision goes backwards. The classic case is Coke with its new Coke strategy. Luckily they had enough bulk to reverse the mindless exercise. Whoever, at Madge decided that it was a good idea to go from lightning bolts to brown cardboard boxes, take note, it sucked. Never mind that the logo went from unique to bland.

And then that LANNET acquisition. Strangely, enough when I spoke to them later they always said they were an Ethernet company. I think Madge Networks heard what they wanted to hear and put a square peg in a round hole. They wanted them to contribute an Ethernet component to their ATM ride.

No alt text provided for this image

Now before I went to work at Madge Networks I worked at Network Interface Consultants (NIC), a Novell Netware reseller. Netware also went titsup. Novell, was also known as the Big Red. In the early nineties my first LAN installation were done using IBM PS/2 servers running LAN Manager from IBM on token-ring. I then started work at NIC doing Netware installations. I started on Netware 3.11 but often had to support Netware 2 installation. This was the days of DOS and OS/2. It was the days before the Internet where drivers updates and bugfixes were downloaded from a BBS using 9.6k baud modems. It had to be a US Robotics and I can safely say I spend more time with that modem than anything else. All software came shrink wrapped. The Novell Software came in a Big Red box, shipped freshly shrink wrapped from the Mormons.

In primary school my parents gave me a Kodak Instamatic camera. It was a very popular camera and I took a number of pictures along the way. I was never an expert photographer and to this day take grainy out of focus pictures. But along the way I captured memories. It was a neat little gadget. The manufacturer Kodak created the digital camera, but instead of trying to convert their film business, they milked it. When the conversion came the company went titsup. Ironically, that Novell with Netware have a similar reason as to why they went titsup. Also the same as Madge Networks!

But back to the early nineties where I was working for the the previously mentioned Big Red box reseller in the leafy burrows of the man-made forest of Jozi. Big Red was the Ferrari of networking in those days! The reseller received special status and more discount based on the training and certification of the people employed by them. I thus undertook self-study for CNE and ECNE certification. My boss was real shirty, never paying for in-person training. Here is my certificate. I had to do a conversion to MCNE but that piece of paper has gone missing.

No alt text provided for this image

We were driven by sales and more customers started asking for Microsoft Windows file and network servers. I became a part time trainer to pay for the costs of the certification from Microsoft. I also made a bit on the side.

No alt text provided for this image

Soon the Microsoft business increased and the Novell business decreased. But that doesn't explain why Novell went titsup. Novell had two great assets: they owned UNIX and understood the pre-cursors to hypervisors. Instead the went into a battle with Microsoft on the desktop, It did not end well. Their file system was totally reusable in a virtualised world. It never happened.

But the biggest reason I think Novell went titsup is that they did not get the Internet. They went down into the desktop gutter (they acquired Wordperfect) instead of heading for the clouds. See what I did there?

No alt text provided for this image

Netware 3.12, indeed a Ferrari in its heyday! As before direct any flaming Lamborghini's to the comments below.

*Ronald works connecting Internet inhabiting things at Nepean Networks.

20
Subscribe to my newsletter

Read articles from Ronald Bartels directly inside your inbox. Subscribe to the newsletter, and don't miss out.

Written by

Ronald Bartels
Ronald Bartels

Driving SD-WAN Adoption in South Africa