Hibbert
@co.uk
| P-663H-51 problems persist
(sorry for a new thread, I can't add to the old one without registering).
I fixed the P-633H-51 problems by binning it and getting a zhone 6228-I2. The zhone is basically the same thing with wireless but zhone bothered to test and debug the firmware a bit.
A bonded connection to my ISPs Zyxel DSLAM (think they use 1000 series) fails on average around once a day locking into a state with 90% packet loss (90% of pings, bigger packets might be worse).
At the time both ADSL links are up and DSL1 stats look fine, DSL2 stats you can't see but pulling the plug or resyncing DSL1 immediately fixes the connection (I mean fixes it in 2-3 seconds long before DSL1 has synced again so there wasn't anything wrong with the DSL2 connection).
I think the bonding gets screwed up, it can recover on its own, I suspect it does quite quickly sometimes so I don't even notice the problem, other times I have seen it stay locked for hours.
Anyone seen anything like this or have suggestions? |
|
dslpartner
join:2005-02-18
1 edit | If its g.bond it could be an issue that seems to be with that, when one of the lines are noisy/unstable.
But no workaround for it as far as I know, as of yet.
--
"Perl is executable line noise, Python is executable pseudo-code."
|
|
Hibbert
@co.uk
| zhone say they have no knowledge of such problems working against their Broadcom based DSLAMS.
So is it Zyxel DSLAM specific? Reading between the lines zhone kinda implied that maybe the Zyxel DSLAM firmware was not built on the latest base firmware from Broadcom.
What is noisy/unstable? My lines are not short (around 40db downstream attenuation). They are relatively very quiet and stable with 2-3db SNR variation over the day. I run with a target SNR which is giving about 1 in 3000 downstream superframe errors and 1 in 100,000 up. Is that supposed to be noisy? |
|
