I’ll make a point of posting something of at least moderate interest this coming weekend.

Our company is kind enough to shut down between Christmas and New Year’s and for us (in IT), it is really a treat. Sure, we have to make sure the storage and other systems keep working but, unless something falls over, this next week is a true break. I was able to leave today back down to inbox zero and if I don’t get paged, will not look again until eleven days from now. I’m unable to go into much detail, but this has been one of the most stressful years for me at work and can certainly use this time.

Ahhhhhhhhhhhh.

B: What’s my cell phone number?

K: I don’t know.

B: What’s Jenny’s number?

K: 867-5309

Source: @TDMoss

While thinking about that trip, I realized that while I don’t travel too often, I have had the opportunity through work to visit quite a few ‘motherships.’ Since I’m a geek by profession, they’re ones most people wouldn’t care about but some might find the list interesting:

• Sony Computer Entertainment America (my employer) – Foster City, CA
• Sony Computer Entertainment Europe – London, UK
• Sony City – Shinagawa, Japan
• NetApp (storage vendor) – Sunnyvale, CA
• EMC (storage vendor) – Hopkinton, MA
• Apple – Cupertino, CA

I have a love/hate relationship with traveling. I like the experience, but can’t say that I wish to do more. I can’t think of any upcoming additions to the list but who knows what the future has in store.

For the unfamiliar, IRC is a chat server and protocol developed in 1988 that enables standard text chat rooms. It’s nothing special but utility items rarely are. It’s how you use it that makes it work.

Did You Know? Our original IRC service we hosted was on a racked-up PlayStation 2 in one of our data centers?

Six years ago, the IT group I joined was relatively small and we were all in the same hallway. As a result, coordinating and collaborating wasn’t a challenge. Our IRC server was in use back then but was mostly for color commentary on recent events or sharing other geeky tidbits (this was before Facebook and Twitter). As our group grew, however, we became more spread out and IRC started taking on a more tactical vibe. That trend continued as we spread out and more people were still working together on projects. Worst yet, it was becoming more commonplace that you didn’t even know who the right individual might be regarding a particular service or skill.

Today, our IRC server has over a dozen different channels with fun and more business-like exchanges happening every day in each. The real strength, however, is when something has gone sideways. If a system has gone down and our NOC pages one or more admins to work on something, our IRC server becomes exceedingly useful so that status and collaboration can be easily done. Transcripts are often utilized for updating tickets or producing root cause analysis (RCA) documents.

Did You Know? I have the fortune of working with ‘Dalvenjah’ of DALnet fame?

Having not used IRC before I joined the team, I have since grown to truly feel badly for any IT shop that doesn’t use it or something similar. I can only imagine how worse-off we would be if it wasn’t available.

Very creative and very beautiful.

The two heros to come out of the experience are Xochitl who is a customer service supervisor for DSL Extreme. And Mike, a field technician for Verizon. Both of them were genuinely interested in working through the problem and each were essential in getting to a resolution.

Now I need to figure out what to do with a considerable amount of Verizon FiOS equipment (router, UPS, Optical Network Terminal, etc.). I wonder if there’s an aftermarket for it? I’ll likely just leave it all in place. Hey, maybe there’s a chance I’ll be able to go back to FiOS?

Unfortunately, Verizon changed their policies and decided to no longer allow independent ISPs access to their circuits. As a result, I was given a choice; move my FiOS service directly to Verizon (become a Verizon customer) or drop FiOS. Fortunately, when the fibre optic cable was run to my house they did so without removing my copper-pair phone line (they usually do) so I am able to go back to DSL. That is the direction I chose to take due to my desire to continue to host my server (the one you’re reading this on) which would be a violation of their terms of service. An order was placed for 7100/768 DSL last week and I confirmed that both circuits would be up for me to transition.

Then this past Tuesday, a Verizon service worker came by to install a dry-loop circuit for the new DSL service. Since I only have a single pair providing the phone service, we both agreed that disconnecting that to install the new circuit would be bad and canceled the work order so that it could be re-submitted correctly. The problem was, it still somehow got communicated/interpreted by DSL Extreme as a success so they requested the disconnect of FiOS (which they said they weren’t going to do, btw).

Now, I’m 5-7 days out from having DSL, have FiOS that is dark and cannot be re-instated without a request for new service which doesn’t fly (I was moving away from them, remember?). My only viable fall-back was to borrow a MiFi and get minimal functionality working so that essential services are available. That’s why the site is slow as you read this.

Next step, talk to DSL Extreme customer support management to let them know their business practice is busted. Oh, a credit to the account would be appropriate, too.