[93687] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: GBLX issues?

daemon@ATHENA.MIT.EDU (Bill Nash)
Wed Dec 13 15:47:14 2006

Date: Wed, 13 Dec 2006 13:53:16 -0700 (MST)
From: Bill Nash <billn@billn.net>
To: Aaron Glenn <aaron.glenn@gmail.com>
Cc: nanog@nanog.org
In-Reply-To: <18f601940612131150k667acf6em6e9fbc6f964cfba6@mail.gmail.com>
Errors-To: owner-nanog@merit.edu


On Wed, 13 Dec 2006, Aaron Glenn wrote:

> On 12/13/06, J. Oquendo <sil@infiltrated.net> wrote:
> >
> > Anyone seeing issues for GBLX around NY?
> >
> dude, chill. no need to yell.
> you know, GBLX sells a lot of different stuff - are we talking IP
> transit, MPLS transport, wavelength, voice? what kind of issues? how
> is anyone going to know what you're talking about when you're as vague
> as humanly possible.
> 

You're awful at this game. When faced with a totally vague question, 
lacking context or useful information, it's up to you to supply your own.

Start with, always:
"Yes, <vendor> is having problems in <location>."

Then, tap your coworkers for assistance:
1: Name a hardware Vendor (the lower the stock value, the better)
2: Name a transport technology (frame relay, sonet, etc)
3: A number between 1 and 10.
4: A number between 8 and 32.
5: A seasonally relevent catastrophic event (snow storm, backhoe, 
exploding squirrel)

Respond: "Yes, <vendor> is having problems in <location>. Seems <5> hit 
this morning around <3> am, effecting <2> connections in that location. 
<Vendor> is having problems getting backup systems online, because they 
were idiots and deployed <1> gear without failover. At last check, it'll 
be at least <4> hours before they get things sorted out."

- billn

home help back first fref pref prev next nref lref last post