![]() ![]() ![]() |
|
DumKopf: Hmm.. Interesting theory.
It's plugged straight into the wall, but I still might consider getting an UPS.
I've lowered my Line Settings down to the middle settings and this has dropped it down to 6/min. Still not good! :(
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77:
how long are you giving a connection uptime before taking these stats?
DumKopf:hio77:
how long are you giving a connection uptime before taking these stats?
Hour or so. But the errors are constantly coming up (can watch the counter going up).
Looks like my profile got switched from "Fast" to "8 ms" last night.
Errors dropped to 0. But still running 50% performance on the line settings, any higher and the errors start showing up again.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77: So,
after over 3 months of holding a solid 60/10 17a sync... with next to no errors.
this morning i got wacked with over 1000 errors... instantly dropped the line.
over the next few hours this continued before i noticed it was happening...
even got as low as 30/10 on 17a while it was trying to recover itself!
Watching the modem, i could see my SNR bouncing between 19 and -3 (but not the fireware bug, it was actually moving up and down in order.. 19-18-17 etc..)
Upon pushing snap to not just monitor it, but actually log a fault (ty TimA for this advice) ... resynced at 50/10 no errors.. no snr bouncing..
Guess ill watch it, and speak to them about cancelling the call out if it stabilizes.. - no foreseeable fault, that sounds like a "no fault found" case to me!
Goes to show, a line can take a dump at any moment, when your least expecting it!
charsleysa:
Be careful, I keep getting an issue where my 30/10 with no errors starts to error during some weekends and drops to 1/6 but every time chorus finally comes to take a look it's back to 30/10 so they say they can't do anything about it.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
hio77: Well.
callout is all cancelled.... now its time to setup a few more stat collectors for the next time this happens, so i have very detailed logs to send away.....
probably something touching, but i cant see it!
charsleysa:hio77: Well.
callout is all cancelled.... now its time to setup a few more stat collectors for the next time this happens, so i have very detailed logs to send away.....
probably something touching, but i cant see it!
What kind of logging can you do that will actually be of use?
#include <std_disclaimer>
Any comments made are personal opinion and do not reflect directly on the position my current or past employers may have.
|
![]() ![]() ![]() |