[102473] in North American Network Operators' Group
Re: Looking for Verizon-GNI network engineer
daemon@ATHENA.MIT.EDU (Henry Linneweh)
Sat Feb 16 09:37:51 2008
Date: Sat, 16 Feb 2008 06:33:33 -0800 (PST)
From: Henry Linneweh <hrlinneweh@sbcglobal.net>
To: "K. Scott Bethke" <scott@carpathiahost.com>, nanog@merit.edu
Errors-To: owner-nanog@merit.edu
--0-1817717642-1203172413=:96589
Content-Type: text/plain; charset=us-ascii
It has been my experience that data center engineers doing NOC support at Verizon
do speak to paying customers about routing issues for premium data center services.
-Henry
----- Original Message ----
From: K. Scott Bethke <scott@carpathiahost.com>
To: nanog@merit.edu
Sent: Thursday, February 14, 2008 6:49:13 PM
Subject: Looking for Verizon-GNI network engineer
Sorry if this is off-topic frustration has set in. I've got what
looks like a routing loop or a wedge in your network and I cant get
past tier2 saying it is an "internet problem". I asked to speak with
an engineer directly was told Verizon engineers don't talk directly
with customers. Issue going on for 4 days.
$ traceroute www.tickerforum.org
traceroute to www.tickerforum.org (70.169.168.7), 64 hops max, 40 byte
packets
1 10.254.123.1 (10.254.123.1) 3.219 ms 1.085 ms 0.915 ms
2 L301.VFTTP-02.CLPPVA.verizon-gni.net (71.171.93.1) 6.329 ms
6.281 ms 5.036 ms
3 P2-3.LCR-02.CLPPVA.verizon-gni.net (130.81.37.194) 4.885 ms
4.091 ms 6.490 ms
4 so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net (130.81.10.94) 4.731
ms 8.248 ms 5.167 ms
5 130.81.15.238 (130.81.15.238) 5.926 ms 130.81.15.190
(130.81.15.190) 6.586 ms 9.158 ms
6 * * *
7 * * *
8 *
$ traceroute www.google.com
traceroute: Warning: www.google.com has multiple addresses; using
64.233.169.104
traceroute to www.l.google.com (64.233.169.104), 64 hops max, 40 byte
packets
1 10.254.123.1 (10.254.123.1) 1.774 ms 1.117 ms 0.909 ms
2 L301.VFTTP-02.CLPPVA.verizon-gni.net (71.171.93.1) 5.820 ms
4.029 ms 4.861 ms
3 P2-3.LCR-01.CLPPVA.verizon-gni.net (130.81.37.192) 8.036 ms
6.346 ms 7.671 ms
4 so-6-3-1-0.BB-RTR2.RES.verizon-gni.net (130.81.29.82) 6.524 ms
8.161 ms 8.408 ms
5 * * *
6 * * *
Ticket # is VAD01QVDW
-Scott
--0-1817717642-1203172413=:96589
Content-Type: text/html; charset=us-ascii
<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><DIV>It has been my experience that data center engineers doing NOC support at Verizon</DIV>
<DIV>do speak to paying customers about routing issues for premium data center services.</DIV>
<DIV> </DIV>
<DIV>-Henry<BR><BR>----- Original Message ----<BR>From: K. Scott Bethke <scott@carpathiahost.com><BR>To: nanog@merit.edu<BR>Sent: Thursday, February 14, 2008 6:49:13 PM<BR>Subject: Looking for Verizon-GNI network engineer<BR><BR><BR>Sorry if this is off-topic frustration has set in. I've got what <BR>looks like a routing loop or a wedge in your network and I cant get <BR>past tier2 saying it is an "internet problem". I asked to speak with <BR>an engineer directly was told Verizon engineers don't talk directly <BR>with customers. Issue going on for 4 days.<BR><BR>$ traceroute <A href="http://www.tickerforum.org/" target=_blank>www.tickerforum.org</A><BR>traceroute to <A href="http://www.tickerforum.org/" target=_blank>www.tickerforum.org</A> (70.169.168.7), 64 hops max, 40 byte <BR>packets<BR> 1 10.254.123.1 (10.254.123.1) 3.219 ms 1.085 ms 0.915 ms<BR> 2 <A
href="http://l301.vfttp-02.clppva.verizon-gni.net/" target=_blank>L301.VFTTP-02.CLPPVA.verizon-gni.net</A> (71.171.93.1) 6.329 ms <BR>6.281 ms 5.036 ms<BR> 3 <A href="http://p2-3.lcr-02.clppva.verizon-gni.net/" target=_blank>P2-3.LCR-02.CLPPVA.verizon-gni.net</A> (130.81.37.194) 4.885 ms <BR>4.091 ms 6.490 ms<BR> 4 <A href="http://so-7-0-0-0.peer-rtr1.ash.verizon-gni.net/" target=_blank>so-7-0-0-0.PEER-RTR1.ASH.verizon-gni.net</A> (130.81.10.94) 4.731 <BR>ms 8.248 ms 5.167 ms<BR> 5 130.81.15.238 (130.81.15.238) 5.926 ms 130.81.15.190 <BR>(130.81.15.190) 6.586 ms 9.158 ms<BR> 6 * * *<BR> 7 * * *<BR> 8 *<BR><BR><BR>$ traceroute <A href="http://www.google.com/" target=_blank>www.google.com</A><BR>traceroute: Warning: <A href="http://www.google.com/" target=_blank>www.google.com</A> has multiple
addresses; using <BR>64.233.169.104<BR>traceroute to <A href="http://www.l.google.com/" target=_blank>www.l.google.com</A> (64.233.169.104), 64 hops max, 40 byte <BR>packets<BR> 1 10.254.123.1 (10.254.123.1) 1.774 ms 1.117 ms 0.909 ms<BR> 2 <A href="http://l301.vfttp-02.clppva.verizon-gni.net/" target=_blank>L301.VFTTP-02.CLPPVA.verizon-gni.net</A> (71.171.93.1) 5.820 ms <BR>4.029 ms 4.861 ms<BR> 3 <A href="http://p2-3.lcr-01.clppva.verizon-gni.net/" target=_blank>P2-3.LCR-01.CLPPVA.verizon-gni.net</A> (130.81.37.192) 8.036 ms <BR>6.346 ms 7.671 ms<BR> 4 <A href="http://so-6-3-1-0.bb-rtr2.res.verizon-gni.net/" target=_blank>so-6-3-1-0.BB-RTR2.RES.verizon-gni.net</A> (130.81.29.82) 6.524 ms <BR>8.161 ms 8.408 ms<BR> 5 * * *<BR> 6 * * *<BR><BR>Ticket # is VAD01QVDW<BR><BR>-Scott<BR></DIV><BR>
<DIV></DIV></div></body></html>
--0-1817717642-1203172413=:96589--
