Why did my CRAN routers change ?
Links: home · search · speed test · login · more ·

 
Links: Reply New Topic
Forums » Comcast » Comcast HSI » Why did my CRAN routers change ?
page: 1 · 2
EG @ 1st Nov 06:48PM:
Why did my CRAN routers change ?

Hey Comcast. What happened to my local & regional CRAN routers that I've had for years (hops 2 thru 9) ?

The IP addresses have changed and now some of them don't have rDNS data anymore. Can any employees please reply ?

Tracing route to google.com [74.125.67.100]
over a maximum of 30 hops:

1 * * * Request timed out.
2 8 ms 9 ms 19 ms te-4-3-ur01.union.nj.panjde.comcast.net [68.86.
92.173]
3 11 ms 10 ms 7 ms po-90-ur02.avenel.nj.panjde.comcast.net [68.86.
09.233]
4 14 ms 17 ms 10 ms 68.85.34.141
5 8 ms 8 ms 8 ms 68.85.34.129
6 9 ms 9 ms 8 ms 68.85.34.121
7 9 ms 10 ms 10 ms 68.85.34.117
8 13 ms 8 ms 9 ms 68.85.34.109
9 10 ms 9 ms 11 ms be-20-crs01.plainfield.nj.panjde.comcast.net [6
.86.209.209]
10 15 ms 21 ms 15 ms pos-0-6-0-0-cr01.newyork.ny.ibone.comcast.net [
8.86.90.25]
11 15 ms 14 ms 15 ms pos-0-2-0-0-pe01.111eighthave.ny.ibone.comcast.
et [68.86.86.74]
12 40 ms 38 ms 36 ms 75.149.230.194
13 18 ms 14 ms 16 ms 209.85.255.68
14 36 ms 43 ms 35 ms 209.85.251.9
15 33 ms 35 ms 34 ms 72.14.239.127
16 45 ms 40 ms 35 ms 64.233.174.46
17 36 ms 33 ms 36 ms gw-in-f100.1e100.net [74.125.67.100]

Trace complete.

Not complaining about the response times here mind you ! ;)
reply
mike12806 @ 1st Nov 07:24PM:
Re: Why did my CRAN routers change ?

traceroute: Warning: google.com has multiple addresses; using 74.125.67.100
traceroute to google.com (74.125.67.100), 64 hops max, 72 byte packets
1 pf-xe-0-0-1-edge.ebr1.cmcsthsd1.faherty.sytes.net (192.168.1.103) 1.194 ms 0.881 ms 0.532 ms
2 * * *
3 ge-2-5-ur01.quincy.ma.boston.comcast.net (68.85.160.65) 8.637 ms 17.064 ms 8.426 ms
4 te-0-6-0-7-ar01.needham.ma.boston.comcast.net (68.87.145.21) 16.310 ms 7.731 ms 12.612 ms
5 pos-0-1-0-0-ar01.chartford.ct.hartford.comcast.net (68.85.162.74) 15.268 ms 10.828 ms 12.531 ms
6 pos-2-3-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.90.57) 18.626 ms 15.023 ms 15.460 ms
7 pos-0-2-0-0-pe01.111eighthave.ny.ibone.comcast.net (68.86.86.74) 16.192 ms 17.604 ms 16.605 ms
8 75.149.230.194 (75.149.230.194) 42.649 ms 40.235 ms 37.023 ms
9 209.85.255.68 (209.85.255.68) 14.753 ms 51.887 ms 16.009 ms
10 209.85.251.9 (209.85.251.9) 37.530 ms 39.362 ms 39.967 ms
11 72.14.239.127 (72.14.239.127) 38.627 ms
72.14.239.131 (72.14.239.131) 37.873 ms 37.379 ms
12 209.85.255.194 (209.85.255.194) 37.618 ms 45.213 ms
209.85.255.198 (209.85.255.198) 36.745 ms
13 gw-in-f100.1e100.net (74.125.67.100) 38.289 ms 36.669 ms 37.809 ms
macbook:~ michaelefaherty$

This is a trace from a while back...

Traceroute: Warning: www.google.com has multiple addresses; using 66.102.1.147
traceroute to www.l.google.com (66.102.1.147), 64 hops max, 40 byte packets
1 edgerouter (192.168.1.102) 1.348 ms 0.931 ms 1.160 ms
2 * * *
3 ge-2-5-ur02.quincy.ma.boston.comcast.net (68.85.160.73) 11.096 ms 15.347 ms 8.440 ms
4 te-9-2-ur01.weymouth.ma.boston.comcast.net (68.87.145.30) 8.945 ms 10.386 ms 11.504 ms
5 te-9-1-ur02.weymouth.ma.boston.comcast.net (68.87.145.58) 9.810 ms 40.816 ms 19.305 ms
6 te-8-1-ur01.scituate.ma.boston.comcast.net (68.87.145.45) 8.891 ms 7.655 ms 16.196 ms
7 te-9-4-ur02.brockton.ma.boston.comcast.net (68.87.144.45) 10.639 ms 14.418 ms 11.238 ms
8 port-channel52-crs01.woburn.ma.boston.comcast.net (68.85.162.177) 16.867 ms 12.540 ms 10.809 ms
9 pos-0-15-0-0-crs01.needham.ma.boston.comcast.net (68.85.162.145) 12.682 ms 9.711 ms 9.834 ms
10 pos-0-1-0-0-ar99.chartford.ct.hartford.comcast.net (68.85.162.74) 17.559 ms 18.967 ms 14.474 ms
11 pos-1-6-0-0-cr01.newyork.ny.ibone.comcast.net (68.86.90.61) 21.699 ms 18.186 ms 19.359 ms
12 xe-8-2-0.edge1.NewYork2.Level3.net (4.71.186.21) 18.898 ms 20.721 ms 23.364 ms
13 vlan89.csw3.NewYork1.Level3.net (4.68.16.190) 26.009 ms vlan99.csw4.NewYork1.Level3.net (4.68.16.254) 31.584 ms vlan69.csw1.NewYork1.Level3.net (4.68.16.62) 28.126 ms
14 ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) 17.959 ms ae-81-81.ebr1.NewYork1.Level3.net (4.69.134.73) 20.288 ms ae-91-91.ebr1.NewYork1.Level3.net (4.69.134.77) 20.328 ms
15 ae-3-3.ebr4.Washington1.Level3.net (4.69.132.93) 35.923 ms ae-3-3.ebr2.Washington1.Level3.net (4.69.132.89) 27.985 ms 24.517 ms
16 ae-62-62.csw1.Washington1.Level3.net (4.69.134.146) 27.526 ms ae-84-84.csw3.Washington1.Level3.net (4.69.134.186) 31.797 ms ae-82-82.csw3.Washington1.Level3.net (4.69.134.154) 41.612 ms
17 ae-4-99.edge1.Washington1.Level3.net (4.68.17.208) 25.074 ms ae-1-69.edge1.Washington1.Level3.net (4.68.17.16) 30.645 ms ae-3-89.edge1.Washington1.Level3.net (4.68.17.144) 21.820 ms
18 GOOGLE-INC.edge1.Washington1.Level3.net (4.79.231.6) 48.412 ms GOOGLE-INC.edge1.Washington1.Level3.net (4.79.228.38) 48.064 ms 44.951 ms
19 209.85.130.12 (209.85.130.12) 47.839 ms 47.653 ms 44.540 ms
20 64.233.175.111 (64.233.175.111) 24.422 ms 64.233.175.109 (64.233.175.109) 27.324 ms 64.233.175.111 (64.233.175.111) 26.002 ms
21 72.14.236.66 (72.14.236.66) 31.000 ms 35.693 ms 72.14.236.74 (72.14.236.74) 32.153 ms
22 he-in-f147.google.com (66.102.1.147) 24.334 ms 29.782 ms 26.629 ms

Latency is roughly the same though so I could care less!
reply
EG @ 1st Nov 07:29PM:
Re: Why did my CRAN routers change ?

I want to know what the hostnames are and the geolocation stuff ! But that is just me. I also want to know the router type and the port and slot data. This stuff:

te-0-6-0-7-ar01
reply
beachintech @ 1st Nov 09:17PM:
Re: Why did my CRAN routers change ?

Usually takes a bit for updated routes to show their rdns data. It should show up for you again in a few days. Either some new hardware was installed for you or a temp issue made your routing change while something is done.
--
Tech at the Beach.
I speak for myself, not my employer.

reply
EG @ 1st Nov 11:47PM:
Re: Why did my CRAN routers change ?

Hmmm.. It's already been a month. I had this same thing happen a while back on a couple of routers and it took a request to a Comcast insider that I know to get it taken care of. At that time the rDNS info was missing for at least a year..
reply
EG @ 1st Nov 11:51PM:
Re: Why did my CRAN routers change ?

Duplicate post removed.
reply
beachintech @ 2nd Nov 12:07AM:
Re: Why did my CRAN routers change ?

said by EG :

Hmmm.. It's already been a month. I had this same thing happen a while back on a couple of routers and it took a request to a Comcast insider that I know to get it taken care of. At that time the rDNS info was missing for at least a year..
Well you didn't say that in your post... haha. I can shoot a message up the chain to a guy to see what's up. Other than that, you are outside of my state so I can't check it at the local office or ask the HE tech.
--
Tech at the Beach.
I speak for myself, not my employer.

reply
EG @ 2nd Nov 12:10AM:
Re: Why did my CRAN routers change ?

Thanks for any help beachintech :)
reply
ctg1701a @ 2nd Nov 08:02AM:
Re: Why did my CRAN routers change ?

said by EG :

Hey Comcast. What happened to my local & regional CRAN routers that I've had for years (hops 2 thru 9) ?

The IP addresses have changed and now some of them don't have rDNS data anymore. Can any employees please reply ?
EG,

I will have someone from my team investigate and have te rDNS updated. Thanks for the heads up.

Chris
reply
EG @ 2nd Nov 09:46AM:
Re: Why did my CRAN routers change ?

Thanks Chris ! :)
reply
ctg1701a @ 3rd Nov 03:34PM:
Re: Why did my CRAN routers change ?

EG,

Take a look now. Those rDNS items should be fixed.

Thanks

Chris
reply
tshirt @ 3rd Nov 04:18PM:
Re: Why did my CRAN routers change ?

68.85.34.98 & 68.85.34.97 still don't resolve..at least from here
reply
EG @ 3rd Nov 04:25PM:
Re: Why did my CRAN routers change ?

:)Almost but not quite Chris:

Tracing route to www.l.google.com [64.233.169.106]
over a maximum of 30 hops:

1 * * * Request timed out.
2 7 ms 8 ms 8 ms te-4-3-ur02.union.nj.panjde.comcast.net [68.86.1
92.177]
3 9 ms 8 ms 8 ms po-10-ur01.jerseycity.nj.panjde.comcast.net [68.
86.209.242]
4 9 ms 9 ms 8 ms 68.85.34.170
5 8 ms 12 ms 10 ms 68.85.34.182
6 9 ms 8 ms 11 ms po-10-ur02.narlington.nj.panjde.comcast.net [68.
86.158.178]
7 11 ms 10 ms 9 ms 68.85.34.198
8 13 ms 17 ms 12 ms pos-0-11-0-0.ar01.plainfield.nj.panjde.comcast.n
et [68.86.153.98]
9 10 ms 13 ms 13 ms pos-0-6-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.90.25]

There are still 3 routers that aren't.

I want to thank you for following up on this for me !! :)

I also want to say not to sweat it bud as it is really not that big of a deal.
reply
EG @ 3rd Nov 04:30PM:
Re: Why did my CRAN routers change ?

said by tshirt :

68.85.34.98 & 68.85.34.97 still don't resolve..at least from here
Seems that the return path interfaces when looking at them from your end are different tshirt

Some of my forward ones are even different now.
reply
tshirt @ 3rd Nov 05:07PM:
Re: Why did my CRAN routers change ?

well yeah, they would be :p
I was just curious so I picked a hop from your original trace as a target...those 2 failed to respond (only tried a few above and below, but the rest seemed ok) Just figured if his guys were cleaning up the "neighborhood" they should try and catch them all.
reply
EG @ 3rd Nov 05:18PM:
Re: Why did my CRAN routers change ?

said by tshirt :

well yeah, they would be :p
That's not necessarily always so but most of the time the return path is different than the forward.

said by tshirt :

Just figured if his guys were cleaning up the "neighborhood" they should try and catch them all.
Agreed.
reply
ctg1701a @ 3rd Nov 09:55PM:
Re: Why did my CRAN routers change ?

said by EG :

:)Almost but not quite Chris:

Tracing route to www.l.google.com [64.233.169.106]
over a maximum of 30 hops:

1 * * * Request timed out.
2 7 ms 8 ms 8 ms te-4-3-ur02.union.nj.panjde.comcast.net [68.86.1
92.177]
3 9 ms 8 ms 8 ms po-10-ur01.jerseycity.nj.panjde.comcast.net [68.
86.209.242]
4 9 ms 9 ms 8 ms 68.85.34.170
5 8 ms 12 ms 10 ms 68.85.34.182
6 9 ms 8 ms 11 ms po-10-ur02.narlington.nj.panjde.comcast.net [68.
86.158.178]
7 11 ms 10 ms 9 ms 68.85.34.198
8 13 ms 17 ms 12 ms pos-0-11-0-0.ar01.plainfield.nj.panjde.comcast.n
et [68.86.153.98]
9 10 ms 13 ms 13 ms pos-0-6-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.90.25]

There are still 3 routers that aren't.

I want to thank you for following up on this for me !! :)

I also want to say not to sweat it bud as it is really not that big of a deal.
Its a big deal to me and my team. I will make sure this gets resolved tomorrow.

Thanks
reply
EG @ 3rd Nov 10:08PM:
Re: Why did my CRAN routers change ?

said by ctg1701a :

Its a big deal to me and my team. I will make sure this gets resolved tomorrow.
I understand that. Thank you sir ! :)
reply
Cjaiceman @ 4th Nov 01:35AM:
Re: Why did my CRAN routers change ?

I noticed at one of my friends houses here in Parker that the first router after the CMTS doesn't resolve either, if ya wanted something else to work on as well :p


--
Duct tape is like The Force – it has a light side and a dark side, and it binds the Universe together

reply
K Patterson @ 4th Nov 08:39AM:
Re: Why did my CRAN routers change ?

Ignore Cjaiceman.

He's just shhowing off his $6,000 Comcast connection. Teehee.
reply
Der_Idiot @ 4th Nov 11:13AM:
Re: Why did my CRAN routers change ?

No. Nuh uh...

Okay well maybe he is. :P
reply
EG @ 4th Nov 11:24AM:
Re: Why did my CRAN routers change ?

Please don't dump on this thread.... :(
reply
EG @ 5th Nov 11:07AM:
Re: Why did my CRAN routers change ?

Well lookie here. Thanks Chris ! :)

Tracing route to www.l.google.com [64.233.169.99]
over a maximum of 30 hops:

1 * * * Request timed out.
2 7 ms 8 ms 9 ms te-4-3-ur02.union.nj.panjde.comcast.net [68.86.1
92.177]
3 9 ms 8 ms 10 ms po-10-ur01.jerseycity.nj.panjde.comcast.net [68.
86.209.242]
4 9 ms 11 ms 8 ms te-1-1-ur02.jerseycity.nj.panjde.comcast.net [68
.85.34.170]
5 11 ms 7 ms 13 ms te-1-1-ur01.narlington.nj.panjde.comcast.net [68
.85.34.178]
6 13 ms 8 ms 7 ms te-1-3-ur02.narlington.nj.panjde.comcast.net [68
.85.34.190]
7 12 ms 14 ms 9 ms be-30-ar01.verona.nj.panjde.comcast.net [68.86.2
09.254]
8 11 ms 10 ms 10 ms pos-0-11-0-0.ar01.plainfield.nj.panjde.comcast.n
et [68.86.153.98]
9 12 ms 11 ms 11 ms pos-0-8-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.91.217]
10 12 ms 15 ms 14 ms pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.46]
reply
ctg1701a @ 6th Nov 06:47AM:
Re: Why did my CRAN routers change ?

said by EG :

Well lookie here. Thanks Chris ! :)

Tracing route to www.l.google.com [64.233.169.99]
over a maximum of 30 hops:

1 * * * Request timed out.
2 7 ms 8 ms 9 ms te-4-3-ur02.union.nj.panjde.comcast.net [68.86.1
92.177]
3 9 ms 8 ms 10 ms po-10-ur01.jerseycity.nj.panjde.comcast.net [68.
86.209.242]
4 9 ms 11 ms 8 ms te-1-1-ur02.jerseycity.nj.panjde.comcast.net [68
.85.34.170]
5 11 ms 7 ms 13 ms te-1-1-ur01.narlington.nj.panjde.comcast.net [68
.85.34.178]
6 13 ms 8 ms 7 ms te-1-3-ur02.narlington.nj.panjde.comcast.net [68
.85.34.190]
7 12 ms 14 ms 9 ms be-30-ar01.verona.nj.panjde.comcast.net [68.86.2
09.254]
8 11 ms 10 ms 10 ms pos-0-11-0-0.ar01.plainfield.nj.panjde.comcast.n
et [68.86.153.98]
9 12 ms 11 ms 11 ms pos-0-8-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.91.217]
10 12 ms 15 ms 14 ms pos-0-1-0-0-pe01.111eighthave.ny.ibone.comcast.n
et [68.86.86.46]
Glad we could help out. Thanks again for bringing it to our attention.
reply
EG @ 6th Nov 09:49AM:
Re: Why did my CRAN routers change ?

;)
reply

Thank you for using lo-fi dslreports.com - report bugs
© 99-2009 silver matrix LLC