Network World
Friday, January 9, 2009
DNSstuff.com
Get information about your IP
IP Information
50+ On-demand DNS and network tools

Community: Security

Navigation

great article!

finally we get some real insight into what's been happening. Definitely can identify with this guy. I love the fact that the techie stands up to the management yahoos and single-handily exposes their horrific management of the city's network. The guy's got guts, for sure.

Click to read the article this is in response to.

Geek on an Island

0

Another theory is that it is possible that vendors like Cisco prefer to have one main man to keep the competition at bay and therefore 'enrich' such a sole person one way or another. The solution can be to have redundancy, e.g. 2 nic cards per box and some failover technology. PC’s can also have a UPS built in! This is not rocket science, but when everything is made in Taiwan, why should we be surprised that we are becoming a 3rd world country! Imagine trying to explain to a 'manager' why one needs a redundant network!

Regarding management, it is common now in the USA to take an amazingly complex technical enterprise (e.g. IBM) and put a 'non-technical weenie' in charge. The worst case I know being the Detroit Tigers hired the Michigan football coach as 'general manager'. Hey, both sports use a ball!

Re: Geek on Island

0

What!? We would appreciated a little objectivity here. Your comment is completely off base, having little to do with the subject matter. We are talking about a single point-of-failure here, Terry Childs. If you work with computers, networks, software, etc, then you know, in design, implementation, and management, that POFs should be minimized. Really, the failing is of the CityNetwork's "managers" for not properly managing the network. If you don't save config info, and a power outage does occur,the network is shot anyway. Its up to managers to maintain, config & support documentation for everything on the net.

Please, show a little intelligence and depth of knowledge!!!!

Protecting a network from less-than-smart people.

0

I have some experience with what can happen to a network when someone does something astoundingly stupid.

One place I worked in the mid-90's had just upgraded to Netware 4 and had sent their sysadmin to Salt Lake City for a two week course on it. A perk of taking that course was being sent CDs of beta versions of Novell software, boldly labled DO NOT INSTALL IN A PRODUCTION ENVIRONMENT. I give you one guess what she did.

The mess I was handed included a normal user account with access rights above and beyond the Administrator account, totally impossible to add or modify user accounts, but they could be deleted- except for the Uber Admin/User account, the automatic backup schedule wouldn't run, it was impossible to create or modify print queues and many more problems. On top of that they'd lost all passwords to the old 3.12 server except for one user. The company even brought in a couple of CNE's from Salt Lake and they couldn't do anything with it. It was the definition of FUBAR.

My suggestion was to take an upcoming 3-day weekend, make absolutely certain there was a good backup of the database then 'nuke and pave' all the workstations with Win95B and both servers with the latest Netware 4.x, then have the people from New York fly out to install the Y2K complaint version of the database software*, which they were going to have to do anyway or watch their system go down in very expensive flames at midnight Jan. 01, 2000.

The response I got from on high was that would be "too expensive". (The company VP was a total ignorant when it came to computers, he *was* literally the Bob the Dinosaur character from Dilbert! Yup, his name really was Bob.) I was thrilled when they "didn't fire me".

*What it was was several multi-megabyte DOS BATCH FILES (somehow ported from antique COBOL programs) that ran various operations on the very large databases of student loan information. The batch files ran on a workstation, moving the data back and forth over 10 Base-T ethernet. The fastest stations were P120's.

Technology and office politics

0

I had suspected this was the case and was mortified upon hearing the initial reports. 5 million bail? I mean, yeah the guy's a flight risk, but mass murders don't get that sort of treatment. Childs definitely has a defamation suit on his hands against the city now, as everybody overreacted (including Childs himself, but that is not an excuse) in ceremonial ignorance. I'm telling you...Biz education is not enough, you need a technical education to oversee techies, and I predict more of this sort of thing is going to happen, especially where the office politics is rough (like a city government). The City of SF shot themselves in the foot with this story, and they are simply blaming the messenger. Childs case will be thrown out of court and SF will lose a good network engineer, and those guys don't grow on trees.

I agree

0

The City of SF shot themselves in the foot with this story, and they are simply blaming the messenger. Childs case will be thrown out of court and SF will lose a good network engineer, and those guys don't grow on trees.

And then the city will be surprised when they can not find another Engineer willing to work for them.

What CCIE in his right mind would walk into that job without some interesting negotiations before hand?

Kudos to the guy risking his

0

Kudos to the guy risking his Rass.. As I stated before....most upper management [especially city] have no technical experience. They should be the ones held liable for this fiasco...no reason for the situation to go have gone this far.

Kudos? TKFT

0

(Red Vs Blue Reference: Team Killing F... T...)

I'm so sick of people putting technogods up on a pedestal. It's not all just about your ability to manipulate bits, but it's also about your ability to work effectively in an organization. Frankly, it doesn't just sound like he was "protecting" his network, it sounds (by the description of his hairy configurations) that he had built a castle on the sand and was afraid someone else would bring it down (or even witness it for what it was...).

How can he call himself a professional while promoting the fact that he was a single point of failure? This alone identifies him as a grade-A nimrod. I *hope* the new security guy demanded the keys to the kingdom from him.

Also note how he hated to waste time on the documentation and change control and the like. What kind of amateur is this? He doesn't have the brains to be an architect, he should have stuck with being an ops monkey. It takes professional maturity to do the right thing, to document your processes, ensure operational availability, configuration backups and to support change windows. In the meantime, it sounds like he was acting like a child.

I'm sorry. A Childs.

He's not doing the best thing for the city.

0

I have worked on several large networks in my career. I also put my heart and soul into the design and implementation. I spent many hours on my own working on config's and the network was my pride and joy.

However, I had detailed network diagrams of all sites, I kept them in large picture frames on my walls and when there was a change I noted it with a dry erase marker until I had a chance to update the drawing. I standardized all passwords and kept them in a safe place where someone knew where they were. I trained the people under me as best I could. Everything I did was with the thought that if something happened to me someone else could come in behind me and take my place.

The end result? When I moved on to another job, another engineer would be hired behind me. Most of the time they found something to criticize is a way to establish their value. Any new problems would be blamed on me because I was an easy skapegoat. My leaving was for the most part an uneventful and soon forgotten passage of time.

That is the mark of a true professional network engineer. Childs was a true amateur and a disgrace to his profession.

Support Terry Childs

0

Terry is a talented engineer who worked hard for the people of SF. Do not throw him away so easily.

Support Terry Childs.

--
futureprogress.net

When Best Practices Are Ignored

0

When reviewing the time line of the case against Childs it's clear that neither the SFGate, Chron, or the press conference led by Harris (and avoided by Newsom) have facts, each provided false or unsubstantiated information then nothing, no facts or follow-up.

Now we see that PCMag wrote a detailed article with internal discussions with co-workers and applied a filter over the story applying typical scenarios on the case, demonstrating that it looks like Childs did his job and is continuing to do his job properly while in jail. Furthermore the PCMag story points to clear failures of the Management and Harris.

So gentle readers what can we know for sure? We know that any facts to substantiate prosecution claims would have been presented if they had existed.

Finally the lack of reported facts, the lack of any substantial evidence of wrongdoing does support Childs claim of innocence.

As the center of innovation and technology this story is unsurprisingly inane and lacking of any cohesive thread or reasonable quality.

Truthfully for us in the tech field and as average citizens, this case sucks and illustrates a thoroughly corrupt environment for workers, management are clearly ineffectual and the media and City Administration complicit in a rush to persecute an innocent and hard working contributor under false charges and inflamatory accusations using emotionally charged words and no facts.

SFGate has fallen hard down the path of sensationalism. As you read this story, remind yourself the next victim falsely accused will be you.

Large organizations who fail to follow best practices top down, fail their employees. What Phil reiterated in his later comment is that no one should be burdened with the entire 24/7 responsibility over the long haul and yet this problem persists due to failures in management.

Ultimately what this essay connotes is that too often failures in management are pushed upon individual grand contributors. C'mon it does not take a tech genius to see the facts and know that best management practices were not applied by senior management and that Harris, too, lacks understanding of planning and implementation and deployment from development to production environments in computer networks.

This scenario looks ore like glorified managers were in over their heads and failed to deliver while one employee covered their collective butts.

Truly, when one understands the foundations of silicon valley, our skills sets and innovation combined, we see that this case is about managers who just didn't understand and execute their job.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <a> <em> <strong> <i> <b> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd> <blockquote> <br /> <br> <p>
  • Lines and paragraphs break automatically.
  • You can use BBCode tags in the text.
  • Web page addresses and e-mail addresses turn into links automatically.

More information about formatting options

CAPTCHA
This question is for testing whether you are a human visitor and to prevent automated spam submissions.

Advertisement: