I had to stop autoserving today :O!

[BL4K3Y]

My modem was having problems this afternoon. It got as far as ranging then began to scan frequencies again. It turns out that the frequency I was using with the autoserving config was no longer working. The frequency I was using is 298750000 just incase anybody else is having similar problems. I switched back to using 33075000 and now everything is fine again (apart from only getting 10MB because I am no longer autoserving) .

[BigJ1]

Ya i have the same issue autoserving no longer works (Bristol) . I'm getting Reg Resp in logs . Looks like Virgin my have updated there CMTS server ? .

[G77]

did you swap the mac or nic mac at all?

[sr20]

It's because BPI+ is now active in exTW, usually with full dynamic configs (dynamic MIC enforced). Same in exCW.
Probably find a lot of 20meg MACS don't work now either?

sr20

[BigJ1]

Mac (20mb) still works fine it's just when you autoserve config you get reg resp in logs. I have tried a few macs different area and they work (Non Autoserve) . I've looked into the mic enforced bit and the full cmts security and looks like there's no way round it.

Anyone got this working still ? in Ex telewest. Really mis the 42mb down speed.

[G77]

Originally Posted by sr20

It's because BPI+ is now active in exTW, usually with full dynamic configs (dynamic MIC enforced). Same in exCW.
Probably find a lot of 20meg MACS don't work now either?

sr20

it aint mate, they've been tersting that frequency in burnley for some weeks, its been on and then off and then on again. i bet its back on by friday.

blakey: it will eventually come back on and stay on. same happened here

[sr20]

Originally Posted by G77

it aint mate, they've been tersting that frequency in burnley for some weeks, its been on and then off and then on again. i bet its back on by friday.

blakey: it will eventually come back on and stay on. same happened here

They're just cycling through a pool of docsis 1.1 frequencies, 299 and 315 will probably lock for downstream too. They usually change frequency for a MAC about every 2-3 weeks here. Sounds like BPI+ isn't in all of exTW yet, but is definately in some areas i've seen telnet logs of. I believe you've only had dynamic configs there for about a week.

It's the dynamic MIC that stops autoserve working and BPI+ that eventually stops the 20meg working, at least that's the update process that exCW followed.

Because a separate card on the CMTS manages connections on each frequency...yes you may find that 1 freq will allow autoserve while another doesn't while they're doing the rollout.

Pure is still fine for autoserve...only on the docs 1.1 MACS (freq's) though perversely. Here the MIC is enforced on 1.0 frequencies but not 1.1...but you can only reg to start with on the 1.1 frequencies if you use a MAC that gets a 1.1 config which spec's the frequency you're currently synced on .

We've got an easy setup here though - static config names, docs 1.1 configs (which spec the DS freq to use)..but only use BPI, not BPI+.

If you ever get out of sync with the correct freq to be using - connecting on the current docsis 1.0 freq (331) when using a docs 1.1 MAC, the modem will automatically resync to the correct frequency once it's downloaded the DHCP'd config file.

edit, balls this info is re post #2 - bristol, extw...where it's definately the case atm

sr20

[BigJ1]

Thanks for the complex reply. I'm currently using a 1.0 mac (Cheltenham) so that explains the not being able to autoserve. I'll try and locate a 1.1 mac and see if that works.

Will post back later.

[G77]

so whats the deal with the bpi and bpi+ stuff?

[sr20]

Originally Posted by G77

so whats the deal with the bpi and bpi+ stuff?

BPI isn't really for authentication, you can use it no prob, you just put a public and private key in the modem (can gen these yourself) and it works.

BPI+ is for authentication of CM's, only way to auth with BPI+ is with the certificates out of non-vol of a sub with a suitable MAC address for your area. Getting these certs, on VM at least, requires physical access to the sub modem.

My area has now also changed from .cm configs to fully dynamic, also with BPI+. Dynamic names with enforced MIC means no force or autoserve of any sort is possible.

MACS which get a docsis 1.0 config do not force BPI+, so work fine for the time being. MACS that get 1.1 configs do force BPI+ and so cannot be used. 99% of 20m MACS get 1.1 configs so cannot be used at all.

About 75% of 10m MACS get 1.1 configs so can't be used either..

Most 2/5m MACS get a 1.0 config so can still be used. When they all migrate over to 1.1 / BPI+, there will be 'a bit' of a problem.

sr20