Options
skipping tier 1 at verizon
Anyone know how to skip the tier 1 support desk at Verizon Fios?
I'm seeing some funky routing between our datacenter center in LA and office in NYC.
The NY data center to NY office traceroute look weird, but traffic in between seems to pass un-hindered.
We use the same carrier for both datacenters and traceroutes only star out after it crosses into the Verizon FIOS network.
Using BGP looking glasses from Level 3, NTT and Cogent routes to the LA data center are clean , routes to Verizon's endpoints are funky (checking 2 different endpoints to rule out router mis-configuration).
I'm seeing some funky routing between our datacenter center in LA and office in NYC.
The NY data center to NY office traceroute look weird, but traffic in between seems to pass un-hindered.
We use the same carrier for both datacenters and traceroutes only star out after it crosses into the Verizon FIOS network.
Using BGP looking glasses from Level 3, NTT and Cogent routes to the LA data center are clean , routes to Verizon's endpoints are funky (checking 2 different endpoints to rule out router mis-configuration).
Comments
-
Options
networker050184
Mod Posts: 11,962 Mod
Get your account team/sales rep involved if they are giving you the run around.An expert is a man who has made all the mistakes which can be made. -
Options
ccnxjr
Member Posts: 304 ■■■□□□□□□□
I do have direct control over a box on the 108.29.213.0/24 network.
This issue specifically affects Verizon FiOS endpoints in NYC when sourced from our LA datacenter.
What makes this interesting is that the symptom is one way audio (when audio is sourced from our VoIP system in LA) .
It does not seem to impact signaling, SIP packets make their way through.
If it was one specific netblock that was being affected i would chalk it up to a firewall/iptables issue.
However it's two different netblocks, which experience the same symptom (reproducible) , the only correlation is that they're both FiOS blocks in NYC.
And it started approximately about the same time.
It sorta feels like a broken or misconfigured ALG almost.
If it was all UDP traffic it may have been easier to get assistance.
However, since the circumstances are very specific to a particular application, not sure how to find the right people.
Traceroutes complete from a NY datacenter using the same carrier (even if they look weird), and more importantly the application works.------------------------------------------------------------------------------------------- Endpoint on 108.29.213.0/24 (NYC FiOS endpoint, you can substitute any pingable ip address then run a traceroute on it) 1 my_gateway_LA (x.x.x.x) 0.244 ms 0.192 ms 0.214 ms 2 ge-0-7-0-12.r04.lsanca03.us.bb.gin.ntt.net (198.172.90.13) 0.593 ms 0.522 ms 0.670 ms 3 ae-3.r05.lsanca03.us.bb.gin.ntt.net (129.250.2.221) 0.831 ms 0.811 ms 0.754 ms 4 ae-0.verizonbusiness.lsanca03.us.bb.gin.ntt.net (129.250.8.86) 0.457 ms 0.414 ms 0.330 ms 5 0.xe-0-0-6.LAX01-BB-RTR1.verizon-gni.net (152.63.112.230) 0.775 ms 0.669 ms 0.559 ms 6 * * * 7 * * * Gateway on .0/24 (NYC FiOS Gateway for previous netback) traceroute to 108.29.213.1 (108.29.213.1), 30 hops max, 40 byte packets 1 my_gateway_LA (x.x.x.x) 0.244 ms 0.192 ms 0.214 ms 2 ge-0-7-0-12.r04.lsanca03.us.bb.gin.ntt.net (198.172.90.13) 0.631 ms 0.512 ms 0.534 ms 3 ae-3.r05.lsanca03.us.bb.gin.ntt.net (129.250.2.221) 1.010 ms 0.756 ms 1.931 ms 4 ae-0.verizonbusiness.lsanca03.us.bb.gin.ntt.net (129.250.8.86) 0.534 ms 0.439 ms 0.434 ms 5 0.xe-5-0-2.LAX01-BB-RTR2.verizon-gni.net (152.63.114.110) 0.650 ms 0.790 ms 0.727 ms 6 L300.NYCMNY-VFTTP-226.verizon-gni.net (108.29.213.1) 84.373 ms 84.336 ms 84.589 ms ------------------------------------------------------------------------------------------- Endpoint on 74.101.172.0/24 (NYC FiOS endpoint, you can substitute any pingable ip address then run a traceroute on it) 1 my_gateway_LA (x.x.x.x) 0.244 ms 0.192 ms 0.214 ms 2 ge-0-7-0-12.r04.lsanca03.us.bb.gin.ntt.net (198.172.90.13) 0.487 ms 0.690 ms 0.814 ms 3 ae-3.r05.lsanca03.us.bb.gin.ntt.net (129.250.2.221) 0.689 ms 0.778 ms 0.991 ms 4 ae-0.verizonbusiness.lsanca03.us.bb.gin.ntt.net (129.250.8.86) 0.328 ms 0.334 ms 4.465 ms 5 0.xe-5-0-2.LAX01-BB-RTR2.verizon-gni.net (152.63.114.110) 0.728 ms 0.681 ms 0.771 ms 6 * * * 7 * * * 8 * * * 9 * * * Gateway on 74.101.172.0/24 (NYC FiOS Gateway for previous netback) traceroute to 74.101.172.1 (74.101.172.1), 30 hops max, 40 byte packets 1 my_gateway_LA (x.x.x.x) 0.307 ms 0.292 ms 0.374 ms 2 ge-0-7-0-12.r04.lsanca03.us.bb.gin.ntt.net (198.172.90.13) 0.998 ms 0.759 ms 0.660 ms 3 ae-3.r05.lsanca03.us.bb.gin.ntt.net (129.250.2.221) 0.945 ms 0.811 ms 0.726 ms 4 ae-0.verizonbusiness.lsanca03.us.bb.gin.ntt.net (129.250.8.86) 0.403 ms 0.317 ms 0.371 ms 5 0.xe-0-0-6.LAX01-BB-RTR1.verizon-gni.net (152.63.112.230) 0.648 ms 0.785 ms 0.588 ms 6 74.101.172.1 (74.101.172.1) 88.166 ms 88.556 ms 88.854 ms ----------------------------------------------------------------------------------------------------
P.S.
I've tested against a FiOS endpoint in a different city, things work fine as well as a Cogent endpoint in NYC, that works as well too.
