US Telco Support > AT&T > AT&T U-verse > Vdsl2 upgrade = slower sync rate and higher ping? What!

Vdsl2 upgrade = slower sync rate and higher ping? What!

Vdsl2! Sorry so many typos it's late. I should have been in bed hours ago. Was a good show on tv!!

reply to doublea
Dont fell bad I got the upgrade 2 days ago and my max Sync rate dropped from 91meg to 64meg but I think upgrade either caps your max sync rate at 64meg or does not report any sync rates above 64 anymore as I have noticed a few other people are reporting new max 64 rates who all had rates above that under vdsl1.

My max sync rate is around 52 meg (was 55 until a couple weeks ago). I am not too worried about my max rate going down but this is the first time I have heard of a latency increased. I am gonna be pissed if my first hop latency goes to 30ms or more as 22 is already high enough!
--
20/2mb Charter, 18/1.5mb U-verse, 6mb/768k DSL Extreme load balanced for a total of 44/4.2

I forgot how to find out the max sync rate?

UPDATE: Found it. »192.168.1.254/mdc

DSL Down Up
Current Rate: 32200 kbs 5040 kbs
Max Rate: 59832 kbs Not Available
Current Connection:
Current Noise Margin: 23.5 dB Not Available
Current Attenuation: 12.0 dB Not Available
Current Output Power: 14.3 dBm -17.9 dBm
IP Bytes Packets Drops Errors %
Transmit: 5958711457 31238531 398361 0 0
Receive: 1120796114592 820366060 562 7 0

reply to doublea
I was updated to the VDSL2 profile yesterday. My latency has not changed form the current 22 - 23 ms through the CO.

I also noticed that my initial Max Sync was down but a check this morning shows it back up to the recent range from the initial Max Rate of 58286 kbs after the RG restarted from the VDSL update.

Detailed Log messages following VDSL2 firmware update
lmd: dsl0: up G.993.2 interleaved Rate:25208/2040 Max:58211/2040
lmd: dsl0: Margin:0.0/0.0 Atten:18.0/0.0 Power:14.1/-9.3
INF P0000-00-00T00:03:40 lmd: dsl0: Country: {FF} Vendor: {CXSY} Specific: {242}

Current Dynamic Stats
Current Rate: 25208 kbs 2040 kbs
Max Rate: 58793 kbs Not Available
Current Connection:
Current Noise Margin: 27.0 dB Not Available
Current Attenuation: 18.0 dB Not Available
Current Output Power: 14.1 dBm -9.3 dBm

What are you seeing when you actually check the latest stats at this page:

»192.168.1.254/xslt?PAGE=J42&THIS···PAGE=J42

Dave

My latency actually went down a bit... average end point was 50... now it is 43

I have noticed one thing, the internal web page management system of the RG doesn't seem so dog slow now with the update.

Also seems to be handling large amounts of data more gracefully and doesn't seem to choke as much when I really ramp the data throughput up.

reply to doublea
my traceroute times went crazy after the update:

traceroute to 12.129.193.246 (12.129.193.246), 30 hops max, 60 byte packets
 1  home (192.168.1.254)  1.277 ms  1.266 ms  1.263 ms
 2  99-57-28-3.lightspeed.sntcca.sbcglobal.net (99.57.28.3)  295.934 ms  296.310 ms  296.688 ms
 3  * * *
 4  * * *
 5  * * *
 6  151.164.43.214 (151.164.43.214)  25.748 ms  22.758 ms  22.776 ms
 7  gar5.la2ca.ip.att.net (12.122.128.25)  33.209 ms  32.478 ms  32.946 ms
 8  12.122.255.74 (12.122.255.74)  33.426 ms  33.203 ms  33.304 ms
 9  mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246)  107.602 ms * *
 

traceroute to 12.129.193.246 (12.129.193.246), 30 hops max, 60 byte packets
 1  home (192.168.1.254)  4.985 ms  5.046 ms  5.045 ms
 2  99-57-28-3.lightspeed.sntcca.sbcglobal.net (99.57.28.3)  24.655 ms  24.678 ms  25.036 ms
 3  71.145.12.214 (71.145.12.214)  32.872 ms  43.637 ms  43.964 ms
 4  71.145.0.12 (71.145.0.12)  28.112 ms  28.477 ms  28.219 ms
 5  * * *
 6  151.164.43.214 (151.164.43.214)  27.035 ms  22.968 ms  23.269 ms
 7  gar5.la2ca.ip.att.net (12.122.128.25)  33.348 ms  32.731 ms  34.091 ms
 8  12.122.255.74 (12.122.255.74)  34.588 ms  34.916 ms  35.261 ms
 9  mdf001c7613r0004-gig-12-1.lax1.attens.net (12.129.193.246)  35.727 ms * *
 
 

reply to doublea
I have noticed my max incoming sync down a bit... this seems to be normal. I've previously heard what you CAN'T see is that the upstream max sync goes 2x or 3x higher with VDSL2. Not sure if true, but someone said that once. It's a very small sacrifice if true.

My first hop latency seems to be about the same at about 22 ms. No issues there for me.

And I also noticed the RG management interface seems to be very snappy now.

I hope you're right about it handling load better... hopefully that also applies to multiple NAT connection management efficiency.

Interesting and exciting stuff... to a geek like me.

reply to doublea
Try rebooting the RG. All these settings are adjusted by the circuitry in the RG when booted based on the noise level on the line at that time.

reply to doublea
My ping is back to normal now, I'm going to reboot my RG to see if anything changes.

reply to doublea
A RG reboot did nothing.

So can any tier 2 att tech tell us whats up?

If the upload sync is now faster then I'm thrilled.

Also if my friends down the street can now gets uverse from this update then I would be more than willing to lose a bit of max sync.

From reading all the posts on the forums most of us found a drop in max sync rate. I thought VDSL2 was to offer around the same speeds or slightly better in the normal ranges. And offer huge increases in speed for the people at far range. What happend?

I will add, when doing speed tests ect ect, it does seem to ramp up to its max speed way way faster. And I removed open dns from all of my computers. So the DNS issue is resolved for me now yay!