We have SB6120 modems on our network which we need to upgrade. Current version on the modems is "SB612X-1.0.3.5-SCM00-NOSH".
Can anyone help me find the latest firmware for these modems?
email: gunes dot tuncay at gmail dot com
We have SB6120 modems on our network which we need to upgrade. Current version on the modems is "SB612X-1.0.3.5-SCM00-NOSH".
Can anyone help me find the latest firmware for these modems?
email: gunes dot tuncay at gmail dot com
I found version "SB_KOMODO-1.0.6.16-SCM00-NOSH" and I can share with anyone who may need it.
I have a question though; I am able to upgrade the modems
from version "SB6120-1.0.1.5-SCM01-NOSH" to "SB_KOMODO-1.0.6.16-SCM00-NOSH"
however I cannot upgrade from "SB612X-1.0.3.5-SCM00-NOSH" to "SB_KOMODO-1.0.6.16-SCM00-NOSH"
How is this possible?
this is the config file I am using:
Network Access Control:on
Software Upgrade TFTP server:192.168.0.10
Software Upgrade Filename:SB_KOMODO-1.0.6.16-SCM00-NOSH.NNDMN.p7
SNMP MIB Object(docsDevSwAdminStatus.0):1.3.6.1.2.1.69.1.3.3.0, Integer, 2
Upstream Service Flow Encodings
Service Flow Reference:1
Quality of Service Parameter Set:provisioned admitted active
Upstream Maximum Sustained Traffic Rate:2000000
Downstream Service Flow Encodings
Service Flow Reference:2
Quality of Service Parameter Set:provisioned admitted active
Downstream Maximum Sustained Traffic Rate:12000000
SNMP MIB Object(docsDevNmAccessIp.1):1.3.6.1.2.1.69.1.2.1.2.1, IP Address, 255.255.255.255
SNMP MIB Object(docsDevNmAccessIpMask.1):1.3.6.1.2.1.69.1.2.1.3.1, IP Address, 0.0.0.0
SNMP MIB Object(docsDevNmAccessCommunity.1):1.3.6.1.2.1.69.1.2.1.4.1, Octet String, private
SNMP MIB Object(docsDevNmAccessControl.1):1.3.6.1.2.1.69.1.2.1.5.1, Integer, 3
SNMP MIB Object(docsDevNmAccessInterfaces.1):1.3.6.1.2.1.69.1.2.1.6.1, Octet String, @
SNMP MIB Object(docsDevNmAccessStatus.1):1.3.6.1.2.1.69.1.2.1.7.1, Integer, 4
Maximum Number of CPEs:1
Enable 2.0 mode:on
Manufacturer Code Verification Certificate:308203A130820289A00302010202106842CB72AC75DDBECF17A455F79A19E1300D06092A864886F70D0101050500308197310B300906035504061302555331393037060355040A133044617461204F766572204361626C65205365727669636520496E746572666163652053706563696669636174696F6E7331153013060355040B130C4361626C65204D6F64656D73313630340603550403132D444F43534953204361626C65204D6F64656D20526F6F7420436572746966696361746520417574686F72697479301E170D3031303731313030303030305A170D3231303330323233353935395A3065310B3009060355040613025553311D301B060355
Manufacturer Code Verification Certificate:040A13144D6F746F726F6C6120436F72706F726174696F6E310F300D060355040B1306444F43534953312630240603550403131D436F646520566572696669636174696F6E20436572746966696361746530820122300D06092A864886F70D01010105000382010F003082010A0282010100A637F0D3AC74D4CAA5AA900042C49AC0B08387D3F7FB928121B334E1594A59AF73E94AC812A5F59D604EF624D56DDA01411443A90FF548E99EE232BD66534E0C65899D063AF5DBBD7D9BA9361B0AD21496BA5E6D7934976950DA7DC689918C819FF5977A5A2401D3F20FEBE2749CAC2965A4FBD5C05113C4D2DB6E8EC45807906F1BF31ACCA4FD8D8EE913DE
Manufacturer Code Verification Certificate:27BFFD9BEAD227DC2FF4EF89868AB3B7357F3F195DA62A779839ED3DCEDF218370C2C1107F60D59AD3494A516E563807D13B5DF9225228313A4C53F0FE1B998B01C4A5EE17150EF72D286CF71E5A0FE6830A5BE082FE774FC051B83142D3527854414E12D5A6557FB838DCD03FB40A10686D4E490203010001A31A301830160603551D250101FF040C300A06082B06010505070303300D06092A864886F70D0101050500038201010044D53B910E323D9ED89217F730C1F0F8C50099087E0762A74C7DBD2BB393CFAB2855C66FBBAFAD0E31A632A8526C5C359B7E66CCDA7127CC42923054CBC4B106F533137D1681ECF6A74E137A2B5940A1983D018AA4
Manufacturer Code Verification Certificate:ED05929FAC6F57E1C195EF214A616CA02900EAAA88D7F2E49A7D954162E867A9B8E84C58904944CDE2360B8542E67DD412CFE171FC881E92AE4AD7964D04ABC5CFF73C248FC14399FFEBC00288EA773A8C3F6068D7CF96E74B6690D05250BAF9D3DFBC7C2766718A04A07B350311EE794D51256587923BB503C2FD010BFF4710E1DC3C2C708A40900DF0C1643D06548803883322D3D5CBA25AC90B4644FDA11253FF33201F3670052DAC4E
SNMP MIB Object(unknown OID 1.3.6.1.4.1.1166.1.19.3.2.2.0):1.3.6.1.4.1.1166.1.19.3.2.2.0, Integer, 1
what does the modem show in its event log when you try to go from 1.0.3.5 to 1.0.6.16
likely causes:
wrong firmware for hardware
bad CVC
timeout
etc...
the event log will give you a reason why it could not upgrade.
It says "E.207 Configuration file CVC Validation Failure". Screenshot is attached.
Strange thing is, half the modems were successfully upgraded using the above config file and the other half generate "CVC validation failure" error.
All the modems are the same make and model! Motorola SB6120.
version 1.0.3.5 of the firmware was built for specific customers only, i.e. Large customers like Cox, Charter or Comcast, and probably has a Co-Signer CVC on it. I am not sure if that can be resolved without Motorola/Arris help as you will need a firmware build that is signed with the same co-signer CVC that removes the CVC from the list.
Do you have the 1.0.3.5 FW file?
Yes, I have the 1.3.0.5 file. Can you please check the file in the link below?
https://drive.google.com/open?id=1wG7veTmweWRY9U69cXoYPpU1Uj9V5mlY
well bad news
the CVC used to sign that firmware is the old Motorola Docsis Cert that expired in 2011, I don't think there is a way to fix that short of a non signed version that Motorola (Arris) helps you load.
If you put the right CVC in the file it may work depending on whether it checks dates...
Here is the CVC
Manufacturer Code Verification Certificate:308203A130820289A00302010202103FDF7C620BB324FB572B125078840666300D06092A864886F70D0101050500308197310B300906035504061302555331393037060355040A133044617461204F766572204361626C65205365727669636520496E746572666163652053706563696669636174696F6E7331153013060355040B130C4361626C65204D6F64656D73313630340603550403132D444F43534953204361626C65204D6F64656D20526F6F7420436572746966696361746520417574686F72697479301E170D3031303731313030303030305A170D3131303731303233353935395A3065310B3009060355040613025553311D301B060355
Manufacturer Code Verification Certificate:040A13144D6F746F726F6C6120436F72706F726174696F6E310F300D060355040B1306444F43534953312630240603550403131D436F646520566572696669636174696F6E20436572746966696361746530820122300D06092A864886F70D01010105000382010F003082010A0282010100B9FBC57AF881464D5830BC16778EECA06ACBE6C7B885924B2DACF594E3BE233203CB2080363D6773B20C8E61AE2F104D4BC88E4C664CB3528604EE9F621AE45DBBC8491F7988895E7941795F95D5FB1CA69737595CF4FF2010801C2214EEDE3DDB1732D0FD5E0A7E3429BC2085FE471CE00658E8CEBD18ACA1680EC43458E59BB61F649BF050123689D2DC4D
Manufacturer Code Verification Certificate:5E3423519FCB341669F3A96EF3BA1E3371B9C2E43AB103FCDC3BAC211EB41D3048A16A3EA1EC86558AC5D78939009DAC77736F669A0B6327BDCB633744604E2EDB6A8DA411731EF1D9B920CF7F22D1A1BC375B8F0B763F7DD9D1261D284D776FDBF858907BAAF298F59208600E2741E05DB87DBB0203010001A31A301830160603551D250101FF040C300A06082B06010505070303300D06092A864886F70D010105050003820101005C5E384AE8FB24774EC087A0C98060CF3C2F5D1FEC60182B92A1B8B1ED9D49FE8210CB2104DFEE3192D6D62BA2B9929F8975AB1DD968413A1A71E669A0B36CC1146736CA11498ED6711D6234527A2814C8D6866421
Manufacturer Code Verification Certificate:5EC9F38044F167C67BCAF6F34D978FAA1874789DD15D91CFD355A24AF0F1BDCC30193C48C39484CCC3C9DAC3E69194378AA8D76FB073A4B24EFC874342D4F7F50547902F42E0B58DF428AD591675C69E706396508EE1E900A4E19B6AEA0B8C5C3459DF0E126272A7D901BBFFF38FB217343F7908B83A0AC89188807C31EA23E9B9309A28A888E7A150984E7DD942D86B15A8E624759FDCA62A4EE5C207DCA7BD567D09CCEAC74F58665BB8
I have access to other FW that use the same CVC. For example, 1.0.5.2. Will that help?
It is hard to say, there probably is an interim build that will allow firmware signed from either release though there is no mention in the release notes about it.
I think it may be trial and error time.
Definitely may require a call to Motorola(Arris)(Commscope) support to see if there is a potential solution.