Looking for Verizon-GNI network engineer

Henry Linneweh hrlinneweh at sbcglobal.net
Sat Feb 16 14:33:33 UTC 2008


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 at carpathiahost.com>
To: nanog at 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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nanog.org/pipermail/nanog/attachments/20080216/8376fd4b/attachment.html>


More information about the NANOG mailing list