KPNQWest Admins Keep Bankrupt Network Running
sebastianw writes "Some of the network administrators from KPNQWest, although they have been (apparently) ordered to shutdown the network, took over control of the KPNQWest NOC. They are trying to keep the network running and keep customers up, regardless of KPNQWest's insolvency. The company warned on Thursday that they would be forced to shut down KPNQwest's entire European data network on Monday unless its customers paid their bills in full immediately." There's a related story on the Register, talking about the possible effect on UK internet access. If anyone needs to hire some network engineers...
It makes you wonder just how many people they really need to run such a network.
It appears to be less than the number they thought.
It's great that they're doing this, but how long can they keep it up? I mean, it's great that they're volunteering like this, but you can only go so long without a source of income. After a few weeks, bills start to pile up, or a major router breaks and needs replacing. Running a network's not ridiculously hard, but it does take money...
I think this is great. Really... Big business could care less about their customers in recent years, but we have these guys generously keeping customsers online...even after they aren't being payed.... This is how customer service SHOULD be done. It is ashame that this is the EXCEPTION and not the true state of an industry in peril.
It looks like they just found out they're on slashdot... they all started looking at the camera and something on the computer screens, lol.
It would be funny if customers wondered why it was finally shutdown only to find that it was the Slashdot effect that took down the network. We can only wait and see...
bbh
Its good these guys keep on working even though they havent been paid for a long time (some in Holland since may). If KPNQwests network goes down well.. here is their map. Too bad most of the news around this is in english.
Of those to whom much is given, much is required.
Hell, if it weren't for my need to eat, I might put in some free time in a NOC like that one, if for no other reason than to have access to the hardware.
Call it the ultimate training lab. Make any change you want - nobody can really bitch much about it, since they're not paying for it anyway. The only motives to keep things running are to, well, keep things running...
Specialization is for insects. - R.A.H.
That's probably why they decided to stay in the NOC they aren't getting paid and the aero chairs are more comfortable than the curb in front of their apartment building.
Plus they can use the Internet access to do job hunting and play really fast QIII. (What you actually thought that they were maintaining the network?)
Actually I think it's great to see such dedication.
"Don't mess with him, he taunts the happy fun ball."
You can't wear a tie in a shop like that!
Just think of what could happen if your tie got caught in the bitstream!
*ZOINK* there goes access to Poland!
Wedding rings? *ZAAM* Oh damn, I think we just transported Roger's ring finger into the shared computer in Ms. Kingston's 3rd Grade class in Manchester, UK.
You gotta be careful when working around heavy data processing machinery, man! They aren't safe or simple, like a table saw or anything!
"Can of worms? The can is open... the worms are everywhere."
These guys are way cooler than my coworkers!
It's the lack of ties around their necks. They have oxygen going to their brains. Makes people friendly and creative!
The speed of time is one second per second.
The actions of the guys in Brussels have been an inspiration for the rest of us in the company (those that are left).
I can pretty much assure that the UK network will keep running, definitely one of the main AS numbers of the UK (5571) has alternate transit so do most in-country networks. If anything it's the Eurorings that are at risks but even they are supported right now from Brussels AND The Hague (both IP NOCs are operational right now).
The actions of the last few days make me proud to be part of KQ, Ebone and Netcom and I really hope that we can all survive this crisis, and if we don't, it won't be from the lack of trying or courage.
just another Netcom/Ebone/KQ techie
Full Time Idiot and Miserable Sod
Nothing is real but the pain
Hmmm,
I find it interesting that they seem to be having trouble with users paying them. The most serious problem I face is customers not paying for the services they receive.
Just shut down one site 2 months ago which was overdue by 6 months... Sortly thereafter got a call berating me for their website not being up. I pointed out that they were past due and stated the site would not go back up until they paid their bill... Couple of days later I had a check.
It supprised me since the site has always been a problem with paying late. I've finally decided to take a no nonsense approach to billing rather than trying to work with customers. I've had too many customers just walk away without paying their bills and thus I have been shedding customers during the last couple of months.
It's definately a lot easier now, without maintaining a bunch of sites that don't pay.
Yes, it is designed to route around damage, but this isn't damage - it's the whole network going down at once.
Take a look at this map and you'll see the problem...
Interestingly, our local KPNQwest is leaving the mothership and this seems to be happening elsewhere, too.
0 20 607.shtml (in Finnish)
On the Finnish company's page they state they're ready to re-route traffic and do what it takes. KPNQwest Norway got bought by Catch Communications and this might be the fate of the others, too. Seems Nokia is already on board as a customer.
http://www.kpnqwest.fi/yritys/uutiset/uutinen20
Anyone got more on this?
J
And as an added bonus, the gov'ts will not have to fight with ISP's in order to get carnivore, echelon, and whatever else on the network.
There are other parts of KPNQwest that do run on general-purpose computers, such as the administrative and billing databases, network management systems, etc. Probably some are running Windows or Linux, and others are probably running Solaris or HPUX.
Bill Stewart
New Fast-Compression-only CPR http://preview.tinyurl.com/dy575ks
As a senior systems engineer from a similar organization (Carrier1 (FALCO!)) I can say there were no issue running a multi unix environment, and I've never had any issue with it at any of my previous companies (nor have any of the engineers I've worked with).
At Carrier1 had FreeBSD, Red Hat & Debian Linux, Solaris 9 & 9, HP-UX, even GNU/Hurd and Mac OS X (well, on *my* system
The only problem I've ever had is the fairly trivial (?!) one of getting the command flags right - stuff like the 'ps','route','ipchains, 'ipfw' and 'ifconfig' commands syntax being different, the different flags for package management tools, that sort of thing.
I quickly came to realise that it's not possible to remember all the flags for all programs and remember the best way to do something on a particular system if you are busy all the time, things just seem to seep out. This happens if you are spending lots of time programming or in meetings or working on large projects - in which case you might not touch one type of system for months (until there is a problem with it), at which point you find your self quickly reading man pages and referring to Google a lot. All you need to do is remeber what's improrant, especially things you'll need for troubleshooting, and not worry about the rest - it's enough to know about tool's like Solaris 'ndd' and Linux's 'mknod' and what they do, if you need to remeber exactly how to use them in a given instance you can refer to man pages, O'Reilly Books or Google (which I often find the fastest).
Staying current, reading Freshmeat everyday, installing and configuring new Unixes and new & un-familer packages regularly, being on mailing lists and reading Slashdot are good ways to stay up to date - the more you know the less likely you are to run into something completely unexpected. If your resourceful (which you should be as a Systems Engineer) the only real problems arise went you don't even know where to start, everything else is a piece of cake.
Basically, if you really know unix (and are not just a Red Hat Linux or Solaris flunky who has convinced themselves they are Gurus while they still run Windows 2000 day to day) then you won't have any problems.
Oh, and making lame excuses like 'well I need Windows for work stuff' and 'they won't let me run Unix on my desktop' DO NOT wash - they are just that - excuses for lameness.
I have been for job interviews and been introduced to guys who called themselves (literally!) 'Unix Gods', yet they had only ever used Solaris - if you have any of those you are in deep shit right now. [ Needless to say I ran a mile! ]
Most people fall somewhere in the middle of those two, you'll probably only have one or two decent guys, if your lucky, though if you need to ask you are very possibly in trouble already!
YMMV.