Well, like I said, it's going to be up to the actual engineer you get.  I'm
sure Sprint has its share of newbie engineers, just like any ISP.  I'm sure
UUNET has a bunch of great engineers as well.  I've also had experience with
a clueless Sprint "engineer" (just turning up a simple T1 where they were
providing the router for the customer, and couldn't troubleshoot the T1).

I do have some good news.  Once such clueless engineer I've ranted and raved
about employed at my same employer is moving along.  Tears of joy.  (Yes,
I'm a cynical b*stard, but I work hard and don't like it when I see someone
surfing eBay half the day and playing MP3s loud enough so that I'm having a
hard time handling tech support calls).  Anyone curious on salary info in my
area (Modesto): Going rate for an MCSE2k with decent experience: 45-60K.
Found that out with a great guy I wanted to fill this new opening with, but
he also had an obscenely-high offer of $75K (well, he's a green MCSE2k with
a lot of network experience, but not at the "enterprise" level).  I told him
to take the $75K even though I'd rather have him working with me, oh well.

--
Jason Roysdon, CCNP+Security/CCDP, MCSE, CNA, Network+, A+
List email: [EMAIL PROTECTED]
Homepage: http://jason.artoo.net/



""James Riggs""  wrote in message
[EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> i had the oposite experience with UUNET.  they handed me a BGP config that
> worked great from the getgo.  i did have a problem with one half of my
class
> c not failing over correctly in the event that a route went down.  we
worked
> through that in about 10 mins though.  someone had mistyped my prefix.  i
> have had only one other problem, and that was my bad.  my access list
wasn't
> allowing BGP updates/keepalives between UUNET and my router.  =\
>
> since then, the network has been reliable, and the support, not that i
call
> on them often, has been great.
>
> anyway, just thought i should temper mr. roysdon's bad experience with a
> good one of my own.
>
> james
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Friday, April 20, 2001 12:06 AM
> To: [EMAIL PROTECTED]
> Subject: Re: What ISP do you recommend for BGP?? [7:1295]
>
>
> It's all going to depend on the luck of the draw as to the engineer you
get,
> I think, at least to some degree (same is true of Cisco TAC, and they're
the
> top as far as support goes, IMHO).  Mind you I've only turned up two BGP
> connections, but Sprint was totally on the ball and great to work with.
> WorldCom/UUNET was incompetent and I had to walk him through a number for
> things like getting a default route advertised from them, what
customer-only
> routes mean, etc. (lucky for me I did them after Sprint).  Check
Boardwatch
> for ISP costs and latency comparisons.  WorldCom is directly connected to
> nearly 50% of prefixes advertised.  I believe Sprint has like 30%.
>
> http://www.boardwatch.com/
>
> --
> Jason Roysdon, CCNP+Security/CCDP, MCSE, CNA, Network+, A+
> List email: [EMAIL PROTECTED]
> Homepage: http://jason.artoo.net/
>
>
>
> ""BH""  wrote in message
> [EMAIL PROTECTED]">news:[EMAIL PROTECTED]...
> > Hi,
> > Does anyone have a recommendation or horror story for best ISP to work
> with
> > for implementing BGP?
> > I am thinking of picking between Worldcom, ATT and Qwest.
> > Thanks
> > FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> > Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
> http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
> FAQ, list archives, and subscription info:
http://www.groupstudy.com/list/cisco.html
> Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]




Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=4373&t=1295
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]

Reply via email to