Both my 250's just went down at the same time!!

[cheesyboofs]

Both my modems just went down at the same time 12:45 Luton.

Stuck original modem back on one link an up she came checked log on remaining haxorware modem:

1970-01-01 00:05:26	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:05:22	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:05:02	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 2)
1970-01-01 00:04:59	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:04:33	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:04:26	 Notice	 M572.0	 Ds Lock Failed - Reinitialize MAC...
1970-01-01 00:04:23	 Critical	 T001.0	 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:22	 Critical	 T002.0	 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:14	 Critical	 T001.0	 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:14	 Critical	 T002.0	 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:09	 Critical	 T001.0	 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:04:09	 Critical	 T002.0	 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:04:00	 Critical	 T001.0	 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:03:59	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:03:42	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 4)
1970-01-01 00:03:38	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:03:18	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:03:16	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:02:56	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 2)
1970-01-01 00:02:53	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:02:33	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:02:28	 Critical	 T001.0	 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:27	 Critical	 T002.0	 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:05	 Critical	 T001.0	 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:05	 Critical	 T002.0	 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:50	 Critical	 T001.0	 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:49	 Critical	 T002.0	 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:49	 Critical	 T001.0	 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:48	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:01:27	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 4)
1970-01-01 00:01:24	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:01:03	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 3)
1970-01-01 00:00:59	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:00:40	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 2)
1970-01-01 00:00:38	 Critical	 R007.0	 Unicast Ranging Received Abort Response - Re- initializing MAC
1970-01-01 00:00:09	 Critical	 R002.0	 No Ranging Response received - T3 time-out (US 1)
1970-01-01 00:00:04	 Notice	 M571.1	 Ethernet link up - ready to pass packets
1970-01-01 00:02:26	 Notice	 M573.0	 Modem Is Shutting Down and Rebooting...
1970-01-01 00:02:26	 Critical		 Resetting the cable modem due to docsDevResetNow

Have tried defaulting remaining modem, no joy, running haxorware 1.1 rev 30.

[Bad_Ad84]

need telnet/hyperterm logs.

best to get via max232 if you have one.

[cheesyboofs]

I am telnetted on to one of my haxor modems from my pfsense firewall; what log would be useful? what command should I use?

Regards

[Bad_Ad84]

really you need to connect to telnet soon as the modem powers on, and capture the entire boot process.

putty can output to a file, or you can copy paste in hyperterm.

you can post it on pastebin.com and pm me the link if you wish, or you can edit out the mac addresses and post it in this thread.

[cheesyboofs]

Thanks, I may have to take you up on that offer - It'll have to wait till I get home from work.

FYI,

* I have tried a factory default.
* I have two affected 250 modems.
* I currently have a virgin 255 working modem in place of one of the affected modems.
* My levels have been fine for about 7 years since I purchased a powered cable booster/splitter from the states as I believe they are illegal in the UK.
* I am not a heavy user - need resilient links.
* I have checked the Virgin status page for reported problems in my area.
* I have checked this forum for other reports off modems going down in my area.

[cheesyboofs]

Hi, Need a little help from some guru now Bad_Ad84 has gone to ground.

I have a powered Splitter that I have had for about seven + years.
I was running fine with a modded surfboard and the NTL subbed silver modem + modded STB in all this time, power levels have never been a problem.

About a year ago I dropped the STB and replaced the two modems with modded Haxorware Abit 250's keeping my subbed Ambit 255 as a backup (not that I'll ever need it I thought)

A couple of weeks ago as you know Virgin made some changes, all that was required my end was a new DHCP server address and config file name. The modems worked fine for about two weeks.

Then 7 days ago both modems went offline! I put the subbed 255 back on and this worked fine. So I tried my subbed mac address on one of my haxors but it didn't work even if I default the modems and start over.

Since then (7 days on) I have found that the modems do work but take 24 hours to come back on-line. Also I can not change the config file name, even if I autoserve it. The modems won't boot at from anything other than that assigned to the MAC address.

Once the modem has locked on I can reboot it as many times as I like as long as I don't change the configuration, so this rules out signal strength.

Can someone please tell me what the Haxorware v1.1-rev30 settings should be for NTL Prue (Luton) should be in light of recent changes?

Current 'working' settings;

Uptime 14 hours,
DS: 18.8dBvm/40.5 dB
US: 55dBvm

Factory Mode (un-checked)
Disable Firmware Upgrades (checked)
Force Network Access (checked)
Tftp Enforce Bypass (un-checked)
Ignore Unknown Messages (checked)
Disable IP Filters on startup (un-checked)

General:
Annex (DOCSIS)
Plan (European)
Preferred DS Freq 1Hz (402750000)
Preferred DS Freq 2Hz
Preferred DS Freq 3Hz
Upstream Channel (4)

Certificate generation:
Certificate type (Motorola Docsis)

Baseline Privacy:
BPI (Disabled)

Modem Identifiers:
Vendor (Motorola Corporation)
Model (SB5101)
Software Version (SB5101-2.6.2.0-NOSH-NNDM)

SNMP Agent:
Server Port (335)
Disable SNMP Agent after registration (checked)

Config file setting currently blank!

Please no replies telling me to default the modem or disable BPI, after over 7 years posting here is a last resort. I have attached a serial cable and recorded the boot process when it fails but the only error that repeats is;

Unicast Ranging Received Abort Response - Re- initializing MAC
No Ranging Response received - T3 time-out (US 1)

I'm pretty sure Virgin (NTHell) are locking down, just need to know how!

Any help greatly appreciated.

[lincsat]

I set one up the other day and had to check "Tftp Enforce Bypass" - give that a try

[cheesyboofs]

Yeh - I did 'try' but I still have to wait a whole day to see if it has worked! I'm leaving one on the default config for its MAC for a couple of days just to make sure two modems (one subbed and one haxor) are stable.

Just strange that I have to wait for so long for it to lock on and I cant change config.cm

[Haruhion]

I was getting re-initializing mac when I was messing with the autoserve yesterday. I had the config filled in as well as autoserve. My idiot fault, but I don't think that's relevant.

You're saying you have to wait a day to change the settings?? I'm fresh to most of this. But yea, tick TFTP Enforce, I needed to do that too. And change my NIC mac.

[cheesyboofs]

Well the test modem has been up for two days now with a 20Mb MAC. I will set the "Tftp Enforce Bypass" and the config to the 20Mb/1Mb nat-any.cm file and if it works the modem will be back on-line this time tomorrow and if it doesn't work it will be back on-line by Friday Night.

Good job I have more than one modem, Funny how I have to wait now!

Oh I have tried changing the MAC on the bridge the modem is attached to but it doesn't seem to make the blindest difference, it still takes a day to lock on.

Cheers