Explain log file

nicolodeon · 26-03-2009, 04:43

Hi can someone explain why I am seeing a CVC error, as follows in my logs?

Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Error (4) Config file does not include a valid CVC!
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Information (7) Registration complete!
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Information (7) We registered with a DOCSIS 1.0 config file!
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Information (7) Received a REG-RSP message from the CMTS...
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Information (7) Sending a REG-REQ to the CMTS...
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Information (7) CableModem SNMP configure complete
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Notice (6) TLV-11 - unrecognized OID
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Information (7) IP init completed ok
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Information (7) CableModem TFTP init ok
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Information (7) CableModem DHCP client init ok
Thu Mar 26 03:25:12 2009 Thu Mar 26 03:25:12 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) downstream time sync acquired...
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) starting ds time sync acquisition...
Time Not Established Time Not Established Information (7) Locked on the downstream. Waiting for UCDs...
Time Not Established Time Not Established Information (7) Downstream lock ok
Time Not Established Time Not Established Information (7) Sync Start
Tue Mar 24 03:52:53 2009 Tue Mar 24 03:52:53 2009 Critical (3) DHCP WARNING - Non-critical field invalid in response.

rjsetford · 26-03-2009, 06:26

I think it could be one of the following:

Corrupt config file (support should be able to send that again if that's the case) - Not very likely I would suggest
I've seen similar on VPN connection logs. Are you using VPN
Communication issue between router and modem - I would suggest this is the most likely and is most likely to be seen on equipment start up

Can you get on to your router and check that NTP is set up and functioning correctly?

Rich

Peter_ · 26-03-2009, 06:29

They are pretty much normal for most modems as the updates are disabled on Virgin but every single update comes down to your modem every time it is rebooted.

nicolodeon · 26-03-2009, 10:00

No VPN equipment, I am concerned about the CVC, its a validity check to ensure that the device has a valid config file; no? Or am I just being stupid here?

TBH, not really up on this, but the fact that there are three specific errors here and I've had some issues, does concern me...

As a VM employee, can I ask you to give an opinion and what I can ask support to do or should?

Ignitionnet · 26-03-2009, 10:08

Modem firmware isn't cryptographically signed, that's about it. Nothing to do with any modem updates being wrong, etc, just that the firmware doesn't contain a valid Code Verification Certificate.

http://www.dslreports.com/forum/remark,16010245

Good those US forums innit.

nicolodeon · 26-03-2009, 10:24

Thx all

But shouldn't it have a CVC then?

As said, I've got issues...

Ignitionnet · 26-03-2009, 10:39

Quote:

Originally Posted by Moldova

They are pretty much normal for most modems as the updates are disabled on Virgin but every single update comes down to your modem every time it is rebooted.

Ello! Nah, the modem attempts to download a specific file name specified in the DOCSIS config file when it receives it. I'll show you the relevant bits of the config file, just a sec:

TFTP firmware upgrade server = 0.0.0.0
Firmware filename on offer = cm.update.bin
Firmware upgrade status = Upgrade at next re-boot
Firmware upgrade operation = Other
Current firmware = 2.111.1001

Files aren't pushed at modems the modem requests them and downloads via TFTP. If you remember ntl at one time had different config files for all sorts of modems to avoid the wrong software going to modems.

I think cases where wrong software went to modems was when there was a single config file used for a tier of service and for firmware it was round-robined at the server so sometimes you got the right one and sometimes you didn't.

When operator needs to do a code upgrade as a matter of urgency they can also use SNMP to force a config file update.

Either way config files are never 'pushed' only the instructions how to download them and where are 'pushed' they are always pulled via TFTP.

---------- Post added at 10:39 ---------- Previous post was at 10:38 ----------

Quote:

Originally Posted by GT6956

Thx all

But shouldn't it have a CVC then?

As said, I've got issues...

Ideally but I guess VM couldn't be bothered to have the files signed

EDIT: It's not actually a major security risk but was introduced to avoid people diddling with their modems by uploading firmware to them via the bootp process. Sadly no protection against flashing the modem's EEPROM directly.

God it's sad I know all this and don't even work in cable.

nicolodeon · 26-03-2009, 12:23

BB - thanks for the note and explanation....

Oh dear, JTAG, bumming serial connectors, forcing the boot loader... oh dear!

Things haven't changed much then!

Nice headset!