ex-cwc & docsdiag - now works?!?

[badnbusy]

Was it just me, or did Docsdiag never used to work in ex-cwc regions. I know STB's never liked it, but when i first got the Ambit ntl:home 120 modem that didnt work either (tried everything i could at the time)

I've just tried it now out of curiosity and low and behold it works!

on the default parameters too (java -jar docsdiag.jar)

Here's the output I got. I noticed it says its a EuroDocsis modem, could this have changed it? (My old ntl:home 120 modem got replaced last month for another 120 model)

PHP Code:

Ambit EuroDOCSIS Cable Modem 60549EU HW_Rev:1.9, SW_Rev:2.40.3225

System up time                       = 0 days 07h 28m 31.00s
Ethernet carrier sense xmit errs.1   = 132
Downstream channel ID                = 3
Downstream received signal power     = -3.2 dBmV
Upstream channel ID                  = 5
Upstream channel frequency           = 41584000 Hz
QoS max upstream bandwidth           = 256000 bps
QoS max downstream bandwidth         = 1024000 bps
SigQu: Signal to Noise Ratio         = 31.7 dB
Cable modem status                   = Operational
Upstream transmit signal power       = 50.0 dBmV
Date and Time                        = 2004-05-15,22:20:03.0
Configuration filename               = ntlhm120-gold.cm 


btw, do these figures look ok?

Note to Robin: I also tried the -ubrip and -traffic switches, and they seeed to work somewhat. I got a list of the downstream and upstream channels (only what i was on tho) and how much capacity and kbps was in use.

Cheers

[badnbusy]

no one have a comment?

[BBKing]

The external stuff shouldn't work at all, but the problem with Ambits on CWC was that although you could probe the modem via the internal 192.168.x.x IP, the return packets went through the UBR, which blocks them. If there's a newer firmware that corrects this, then there's nothing that stops the modem being accessible.

[Florence]

Yes it is now working for me aswell

[badnbusy]

Does this now mean SNMP is enabled? Eg we can use something like MRTG?

[BBKing]

Define 'enabled' - it was always enabled (I've been probing it for ages) but if the bug that stopped SNMP replies going out of the wrong interface is fixed, then there should be no reason MRTG won't work.

[badnbusy]

Its ok - MRTG now works in ex-cwc

I got it working

[hjf288]

aint working here T_T

[Florence]

I have PRTG working so all should work.

[badnbusy]

what's the difference between PRTG and MRTG? Which is better?

[badnbusy]

Ah - ive downloaded PRTG and i agree its a lot better and easier.

What Options in PRTG have you got set kits?

[rdhw]

Originally Posted by badnbusy

did Docsdiag never used to work in ex-cwc regions. I know STB's never liked it, but when i first got the Ambit ntl:home 120 modem that didnt work either (tried everything i could at the time). I've just tried it now out of curiosity and low and behold it works!

DocsDiag has always worked in principle with stand-alone cable modems, in all areas. There have been two difficulties in practice with the Ambit modems:
1. getting the user's PC to address the CM correctly for traffic to 192.168.1.100: I posted a Windows registry hack for this some time back when the MRTG issue first raised its head;
2. some Ambit firmware versions incorrectly send their responses to the user's PC via their ISP-side port and the CMTS/UBR then back through the CM, rather than directly via their user-side port: the trombone-route traffic is blocked in ex-C&W regions by security filters in the UBR.

It is possible that later versions of Ambit firmware have fixed these problems. Perhaps those who have this working now should compare firmware version numbers with those who still do not have this working.

DocsDiag will not produce correct -traffic reports in ex-C&W regions, because the only CM it can read will be the user's own. So the only traffic reported will be the user's own, not a meaningful assessment of the load on the system as a whole.

[badnbusy]

Thanks for the clear explanation Robin.

[altis]

FYI you can read the status of the Ambit directly at:
http://192.168.100.1/

...but you'll need to log in as 'root' with a password of 'root'.

Some pages are hidden - as a quick 'view source' will reveal. For example:
http://192.168.100.1/P_log.htm - is an event log
http://192.168.100.1/P_rate.htm - gives interface stats
http://192.168.100.1/P_ubd.htm - gives upstream burst info

[rdhw]

Originally Posted by altis

FYI you can read the status of the Ambit directly at:
http://192.168.100.1/

Well, sometimes. This will fail under the same circumstances as DocsDiag fails. If it works for one, it works for both.