Network World
Saturday, November 22, 2008
DNSstuff.com
Get information about your IP
IP Information
50+ On-demand DNS and network tools

Michael Morris: From the Field

Cisco Subnet

Navigation

No Love For Central Office Techs

As it says in my little bio over there:

arrow

I have a lot of experience with enterprise wide area networks (WANs). This means I've spent more than a few hours, evenings, weekends, and holidays arguing with CO techs about circuits.

I wrote a blog about MPLS Carrier Diversity a few months back which included this:

The local loop is where most people assume problems will occur, and generally, they are correct. Basic T-1s delivered by LECs are prone to outages due to several reasons. Many T-1s are really just 2-wire DSL lines that are converted to 4-wire T-1s at your office. So, you get to pay for a T-1 and get all the love of a DSL line. Next, T-1s are a CO techs least concern. CO techs will bounce them, loop them, or reprogram them without blinking an eye. Have you wondered why your T-1 is so stable at night and bounces during the day?

Well, that little outburst about the professional honor of CO techs led to an e-mail the other day from an ex-CO tech. My new friend, let's call him Ron, wrote:

----- Original Message ----
From: Ron
To: mjmorris@yahoo.com
Sent: Friday, March 14, 2008 10:46:49 PM
Subject: offended

Hello,
Having been a Central Office switch tech for years, I am offended by your
remarks concerning the "attitudes" of CO techs towards T-1 ckts. T-1's are
the bread and butter of the industry still and in my experience were treated
as such. In my opinion, the people who never learned the "5 9's" of service
(99.999% reliability in case you are 'that' young) are the on prem IT
people. I currently am a phone system vendor and am constantly amazed at the
willingness of IT staff to bring service down, without notification and with
known traffic on the circuit.
It's all a matter of perspective, and I believe that yours is skewed.
Thank you for your time,
Ron

I replied to Ron with a few questions. These came from my experience over the years working in NOCs and dealing with outages, often cause by rogue CO techs:

  • Have you ever or have you seen another tech bounce an entire channelized DS-3 to fix a single T-1? (Thus taking down all the other circuits)
  • Have you ever or have you seen another tech leave a T-1 looped for hours by mistake only to blame something else when the problem is found?
  • Have you or have you seen another tech ever down the active side of a SONET ring without checking the protect?
  • Have you or have you seen another tech ever swapped a card in a MUX with a single protect card before checking if any other cards were using the protect?

His answers surprised me in that he prefaced them with clarifying that he was not an old, grumpy, union CO tech working for a Bell. He worked for a non-union long distance company. He often dealt with union employees that refused to work with him. It got me thinking that a lot of my dislike for CO techs came from dealing with union operators, who often gave me the impression they could care less about the customer being affected (in most cases, me). I worked at AT&T as a "management" employee in a NOC and dealing with union CO techs was very frustrating - be it AT&T, Sprint, PacBell, Bellsouth, SBC or some other LEC. They knew their union rules and were not going to go one step beyond to help a customer. But this ultimately hurt these employees. Being rigid and inflexible in today's economy was a recipe for disaster. How much CO work has been automated today away from union labor? Union employees seemed to have forgotten who the customer was.

I'm not a big fan of unions because I don't think they really help employees or the economy. Sure, you may think you're getting great benefits and a solid job from the union, but just ask UAW members how they feel now. Unions don't have a place in today's global economy, especially in telecommunications. Why do you think there's no Cisco Tech Union? We know we have to compete in the global economy or get outsourced to India. We respond to our customers quickly or they get new vendors. The same is happening in telecommunications.

Let the hate mail begin. ;-)


PS - Here are Ron's answers:

  • Not on purpose, and not ever between the hours of 8 and 5.
  • Yes to the first part of the question, including myself.
  • Only had a one SONET ring, so really "NA"
  • I think it probably happened, I'd be surprised if it didn't

So, for now, I'm sticking to my story.


More >From the Field blog entries:

Do You Have an Architecture Review Board?

NX-OS's Best Feature: Virtual Device Contexts (VDCs)

Come Visit Me at FutureNet

Tips on spending your time well at Cisco Networkers, plus: bring back the CCIE party!!

* NX-OS - Some Software For all that New Nexus 7000 Hardware

* A CCIE job that only offers $150K - ummm...maybe...well...no.....

* The DC3....err....Nexus 7000 brings some exciting hardware to the DC LAN

Go to Cisco Subnet for more Cisco news, blogs, discussion forums, security alerts, book giveaways, and more.

Recent Cisconet blog entries

20 useful sites for Cisco networking professionals

Network World's IT Buyer's Guide: Cisco products

Subscribe to Network World's Cisco Alert, which includes a weekly digest of all Cisco Subnet items

my favorite...

Useful answer?
0

One tech leaves jumpers in place when moving or repairing a T1. Next tech is "cleaning up" and pulls jumpers, taking down our main PRI in the middle of the day.

This happens about twice a year.

No Love for Central Office Techs

Useful answer?
0

Hey Morris,
If you think the workings of the local loop carrier is bad, try working in a global market with some of the other world wide carriers. There is no since of urgency for any circuit that goes down.

RE: No Love for Central Office Techs

Useful answer?
0

Amen to that brother! I've spent plenty of time just trying to get a hold of international PTTs, let alone work with a tech.

I guess that should be another blog. ;-)

Mike

Not so bad in rest of the world

Useful answer?
0

Everything you describe must be local to America. I haven't had so many problems in Europe and Asia.

In Europe, most corporate circuits are Ethernet carrier from 10MB upwards, not T1. Only get to see that on international circuits.

You guys must be further behind than I thought in America. Time to deregulate your telecoms.

http://etherealmind.com

While you have my support on

Useful answer?
0

While you have my support on the call for professionalism (in this case of CO techs).
I just don't see how Unions fit here?

You started with CO techs and ended up with proclaiming a Union-free IT industry - that's a little unprofessional, at least, lack of consistency.

a lazy and unprofessional worker, unionized or not, will always do more harm than good.

so let's stick to the initial issue: CO (and not only) staff messing up and then avoinding responsability by hiding it.
In my opinion, besides unprofessionalism, lazyness, etc; one of the factors that contributes to this situation: the low-zero-tolerance for errors culture/management. people are not encouraged to recognize their mistakes because they get 'punished' even for the small ones. and it starts from the most non-mission critical positions. people just get used to hide their mistakes (and do nothing to get better) instead of recognizing and working on impoving their work.
While many will say that it's the company's culture or smth else (which we can not change), i say that each of us can contribute to changing this by beeing more tolerant to colleagues mistakes and fostering it with our subordinates.

Trouble came clear on testing.

Useful answer?
0

Anyone ever heard this one. Even when an outage is their fault, It's never THEIR fault - the trouble just magically came clear when they tested it....

I've worked the client side of the d-mark for my whole career starting as a PBX tech 12 years ago. We used to run data over the voice network, now we're running the voice over the data network. Some things change, and some things will never change.

Truer words have not been written...

Useful answer?
0

Worked for a clec, an ilec, a small reseller and now back at the giant telco.... Have seen the misery of the life of a t-1 and dealing with CO TECH SHUFFLE...

I agree with MJM's overview though.. the 'union' strangles internal productivity as well as producing a negative customer experience.... its a dated concept..time to re-invent and move on...

(try to get a dispatch from a Union tech at 5:00 PM sometime... Better chance of winning the lotto)

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.

About Michael Morris

Michael Morris is a communications engineering manager at a $3 billion high-tech company. His background is in enterprise WANs working with telcos, and developing large-scale routing designs. He has worked on networks at government and corporate organizations, including networks at two Fortune 10 companies. In his current role, he leads large-scale IT networking projects and develops and maintains architectural standards for data networks, storage area networks, IP Telephony, and security. Michael is a CCIE and has 11 years experience in networking and communications, including four years as a paratrooper in the U.S. Army. He has a bachelor's degree in MIS from the University at Buffalo. Recently, he was awarded the Network Professional Association® (NPA) Professional Excellence and Innovation Award for his work on network architecture, templates and enterprise MPLS design.

Contact him.

RSS feed XML feed

From the Field archive.

Cisco Subnet / RSS feed Cisco news RSS

The opinions expressed in this Weblog are those of the writer and may not represent the opinions of Network World.

Advertisement: