Motorola SB5100 Mac Version Problem | docsis.org

You are here

Motorola SB5100 Mac Version Problem

10 posts / 0 new
Last post
vishaljdesai
Motorola SB5100 Mac Version Problem

We have recently upgraded the firmware of SB5100.
Some modems show MAC version 2.0
Some modem shows MAC version 1.1(Not QOS Version)
Both kind of modem shows same recent firmware.
We are facing problem with SB5100 with following series.
000e.xxxx.xxxx
000c.xxxx.xxxx
0011.xxxx.xxxx

The series 000f.xxxx.xxxx(SB5100) is running fine(Mac Version 2.0)
Any one has faced such kind of problem

Thanks

Vishal

DocsisAdmin
Toggle DOCSIS 2.0 flag via SNMP

I think some of your modems need to have their docsis 2.0 flag toggled. I believe the mib below will set 2.0 mode. The modem will need to be rebooted to take effect. The change is retained permanently in flash unless you set it back to zero.

set 1.3.6.1.4.1.1166.1.19.3.1.25.0 to integer 1, like below:

snmpset -v2c -c (Community String) (IP Address of Modem) 1.3.6.1.4.1.1166.1.19.3.1.25.0 i 1

vishaljdesai
Thanks its working

Yoyo,It is working.Thanks for the help

vishaljdesai
Sb4200 offline after docsis mix mode Ubr7246

After starting docsis Mix mode(ubr 7246) few SB4200 got offline.Which are not coming online at all.Not even receive lock.
tested with production cmts,lab cmts even with (Ubr7114) but this modems are not ranging at all.(tried factory reset,docsis 1.0)
so i want to try with firmware upgrade (current firmwareSB4200-0.4.4.5xx) which i can only do with ethernet as no RF interface available.I do have CVC and firmware everything.
snmp upgrade is also not working without CVC.Any faced this kinda problem,if yes pls. help.

Thanks

Vishal

DocsisAdmin
use the self-diag page

Set up a host behind the modem with 192.168.100.2 as the address and use your browser to go to 192.168.100.1. Once there you can read the diagnostic log on the modem to see what it's complaining about when it sees the forward carrier. That should give you some clues as to why it won't acquire. It sounds like you've possibly configured some return modulation profiles that may not be supported. The SB4200 does support ATDMA or any type of docsis 2.0 RF profile -- only the 4220 and higher models are capable of those. If those are the only units online, that sounds like it might be a place to look.

Also, I've had problems with older firmware on certain Moto models losing sync after the forward carrier is taken down. Those modems may require a power cycle to get them to come back. Physically unplug and plug back in a couple offline units to make sure that's not the case.

vishaljdesai
nothing unusual

Nothing unusual in the logs.Modulation profile is normal all QPSK.this problem started after firmware upgrade and docsis mix mode.After reverting to docsis 1.0 then all so CM keep scanning for DS.I have even set DS freq manually then also it is keep scanning for DS.

cmts config
DS 322000000
US 25000000
channel-width 3200000

Modem page Logs
Time Priority Code Message
************ 8-Debug T509.0 Acquired DS with status NO UCD for US, DS Freq 322000000, US Id 0
************ 3-Critical U1.0 No UCD's Received - Timeout
************ 3-Critical H501.9 HFC: T1 Timer Expired
************ 3-Critical U2.0 UCD Invalid or Channel Unusable
************ 3-Critical H501.13 HFC: Invalid UCD
************ 3-Critical H501.21 HFC: UCD Invalid upstream freq
************ 3-Critical U2.0 UCD Invalid or Channel Unusable
************ 3-Critical H501.13 HFC: Invalid UCD
************ 3-Critical H501.21 HFC: UCD Invalid upstream freq
************ 3-Critical U2.0 UCD Invalid or Channel Unusable
************ 3-Critical H501.13 HFC: Invalid UCD
************ 3-Critical H501.21 HFC: UCD Invalid upstream freq

************ 8-Debug T509.0 Acquired DS with status NO UCD for US, DS Freq 322000000, US Id 0
************ 3-Critical U1.0 No UCD's Received - Timeout
************ 3-Critical H501.9 HFC: T1 Timer Expired
************ 3-Critical U2.0 UCD Invalid or Channel Unusable
************ 3-Critical H501.13 HFC: Invalid UCD
************ 3-Critical H501.21 HFC: UCD Invalid upstream freq
************ 3-Critical U2.0 UCD Invalid or Channel Unusable
************ 3-Critical H501.13 HFC: Invalid UCD
************ 3-Critical H501.21 HFC: UCD Invalid upstream freq
************ 3-Critical U2.0 UCD Invalid or Channel Unusable
************ 3-Critical H501.13 HFC: Invalid UCD
************ 3-Critical H501.21 HFC: UCD Invalid upstream freq
************ 7-Information I510.0 *** BOOTING *** SB4200-1.4.8.14-SCM00-NOSH

DocsisAdmin
Appears to be the upstream modulation profile

The modem is complaining that it is not seeing an upstream channel descriptor containing information about a modulation profile that it is able to utilize. I'm not sure why - it's saying that it can't support the QAM, frequency, width or some other aspect of what it's being told to use -- or that it can't properly read the descriptor at all. "U2.0 UCD Invalid or Channel Unusable". Can you post the actual upstream modulation profile and RF portions of the interface config?

To get everything back online for now, you should probably drop the mixed mode operation and go back to a simple docsis 1.0 RF config. If you've already done that, you should probably do a close comparison of the before & after configs to see if there's some small difference still left. Did you power cycle some of the units?

Software: SB4200-1.4.9.4-SCM02-NOSH (Boot ver: SB4200-0.4.4.0-SCM06-NOSH) seems to work fine here.

vishaljdesai
RF Int config

interface Cable3/0
no ip address
cable tftp-enforce
no cable packet-cache
cable default-phy-burst 0
cable map-advance dynamic 300 1500
cable bundle 1
cable downstream channel-id 0
cable downstream annex B
cable downstream modulation 64qam
cable downstream interleave-depth 32
cable downstream frequency 322000000
no cable downstream rf-shutdown
cable downstream rf-power 59
cable upstream max-ports 8
cable upstream 0 connector 0
cable upstream 0 frequency 25000000
no cable upstream 0 ingress-noise-cancellation
cable upstream 0 docsis-mode tdma
cable upstream 0 channel-width 3200000 3200000
cable upstream 0 minislot-size 8
cable upstream 0 range-backoff 3 5
cable upstream 0 modulation-profile 41
no cable upstream 0 rate-limit
cable upstream 0 rate-adapt bcs 0
no cable upstream 0 shutdown

Mod Profile---
Mod IUC Type Pre Diff FEC FEC Scrmb Max Guard Last Scrmb Pre Pre RS
len enco T k seed B time CW offst Type
BYTE BYTE siz size short
41 request qpsk 64 no 0x0 0x10 0x152 0 8 no yes 0 qpsk na
41 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk na
41 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk na
41 short qpsk 100 no 0x3 0x4E 0x152 35 25 yes yes 0 qpsk na
41 long qpsk 80 no 0x9 0xE8 0x152 0 137 yes yes 0 qpsk na

DocsisAdmin
Looks normal

I can't see anything obviously wrong, but since I'm don't run Ciscos I'm not familiar with hex parameters of that modulation example. Are you sure it's a complete mixed mode configuration? I may be wrong, but for mixed mode operation I'd expect to see two different profiles, like a QPSK profile and 16QAM profile, etc.

I see some discussion re: mixed mode operation on Cisco's here.

vishaljdesai
Case step by step

1.We started Docsis Mix mode after upgrading the firmware.We received complains of CM not ranging.
2.We reverted back to Docsis 1.0 Mode.Still modems are not ranging.
3.We bring back modems to Lab and tried different configurations.Still Modems are not ranging.
4.Now we have approx 75 CM pile up at office which are not coming online.

Regarding Modulation profile as you are not familiar with Cisco CLI
41 1st col is the profile no.2nd col is type of IUC(request,inital,station,short,long).3rd col is type of modulation(QPSK).Other hex values are of FEC Byte info.
We are not running Mix mode configuration as of now.2 different modulation profile I have pasted below.I am suspecting some problem related to CM.

Docsis 1.x Modulation Profile
41 request qpsk 64 no 0x0 0x10 0x152 0 8 no yes 0 qpsk na
41 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk na
41 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk na
41 short qpsk 100 no 0x3 0x4E 0x152 35 25 yes yes 0 qpsk na
41 long qpsk 80 no 0x9 0xE8 0x152 0 137 yes yes 0 qpsk na

Docsis Mix Mode Modulation Profile.
141 request qpsk 64 no 0x0 0x10 0x152 0 8 no yes 0 qpsk na
141 initial qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk na
141 station qpsk 128 no 0x5 0x22 0x152 0 48 no yes 0 qpsk na
141 short 16qam 200 no 0x5 0x4E 0x152 19 17 yes yes 0 16qam na
141 long 16qam 216 no 0x9 0xE8 0x152 139 77 yes yes 0 16qam na
141 a-short 32qam 100 no 0x9 0x4E 0x152 18 16 yes yes 0 qpsk1 no
141 a-long 64qam 160 no 0xB 0xE8 0x152 96 56 yes yes 0 qpsk1 no
141 a-ugs 16qam 108 no 0x9 0xE8 0x152 139 77 yes yes 0 qpsk1 no