darn4nr
join:2005-08-22
Fremont, CA
| [connectivity] Need an expert opinion
So thanks to this wonderful forum I found out to check some logs and stats on my modem. The follow below.
I understand the T3- message is a keep alive and not necessarily an issue. However I'd appreciate any opinions whether what I see is good, bad and/or ugly 
Thanks as always to all that are and have been so helpful sofar.
Frequency 705000000 Hz
Signal to Noise Ratio 35 dB
QAM 256
Network Access Control Object ON
Power Level 1 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please
Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 5
Frequency 20600000 Hz
Ranging Service ID 1091
Symbol Rate 2.560 Msym/s
Power Level 46 dBmV
050825211014 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=3679B4 Info:0001)
050825193528 3-Critical R02.0 No Ranging Response received - T3 time-out
050825192630 3-Critical R02.0 No Ranging Response received - T3 time-out
050825192011 3-Critical R02.0 No Ranging Response received - T3 time-out
050825191944 3-Critical R02.0 No Ranging Response received - T3 time-out
050825191942 3-Critical R02.0 No Ranging Response received - T3 time-out
050825184946 3-Critical R02.0 No Ranging Response received - T3 time-out
050825183656 3-Critical R02.0 No Ranging Response received - T3 time-out
050825183629 3-Critical R02.0 No Ranging Response received - T3 time-out
050825182556 3-Critical R02.0 No Ranging Response received - T3 time-out
050825172705 3-Critical R02.0 No Ranging Response received - T3 time-out
050825163055 3-Critical R02.0 No Ranging Response received - T3 time-out
050825155504 3-Critical R02.0 No Ranging Response received - T3 time-out
050825155438 3-Critical R02.0 No Ranging Response received - T3 time-out
050825155436 3-Critical R02.0 No Ranging Response received - T3 time-out
050825145955 3-Critical R02.0 No Ranging Response received - T3 time-out
050825145952 3-Critical R02.0 No Ranging Response received - T3 time-out
050825141333 3-Critical R02.0 No Ranging Response received - T3 time-out
050825134823 3-Critical R02.0 No Ranging Response received - T3 time-out
050825134821 3-Critical R02.0 No Ranging Response received - T3 time-out
050825133231 3-Critical R02.0 No Ranging Response received - T3 time-out
050825125155 3-Critical R02.0 No Ranging Response received - T3 time-out
050825125152 3-Critical R02.0 No Ranging Response received - T3 time-out
050825110016 3-Critical R02.0 No Ranging Response received - T3 time-out
050825105950 3-Critical R02.0 No Ranging Response received - T3 time-out
050825105947 3-Critical R02.0 No Ranging Response received - T3 time-out
050825104516 3-Critical R02.0 No Ranging Response received - T3 time-out
050825093952 3-Critical R02.0 No Ranging Response received - T3 time-out
050825092754 3-Critical R02.0 No Ranging Response received - T3 time-out
050825082942 3-Critical R02.0 No Ranging Response received - T3 time-out
050825075816 3-Critical R02.0 No Ranging Response received - T3 time-out
050825074802 3-Critical R02.0 No Ranging Response received - T3 time-out
050825070054 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
050825070053 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
050825070053 7-Information B401.0 Authorized
050825070052 7-Information 7 I500.0 Registration Completed
050825070052 7-Information SEC: Co-Signer CVC from configuration file was verified
050825070051 7-Information REGISTRATION COMPLETE - Waiting for Operational status
050825070050 7-Information 7 D509.0 Retrieved TFTP Config SUCCESS
050825070050 7-Information Registration file - downloaded
050825070049 7-Information Trying to download Configuration file ...
050825070049 7-Information 7 D507.0 Retrieved Time....... SUCCESS
050825070049 7-Information Time of day - retrieved
700101000014 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
700101000014 7-Information DHCP - parameters acquired
700101000010 7-Information 7 T500.0 Acquired Upstream .......... SUCCESS
700101000010 7-Information Trying to register through CMTS...
700101000010 7-Information SYNCHRONIZED - 705000000 Hz , ucd 5
700101000008 7-Information Starting Ranging On Channel 5
700101000004 7-Information Downstream Locked - Collecting Upstream Information
700101000004 7-Information 7 T501.0 Acquired Downstream (705000000 Hz)........ SUCCESS
700101000002 7-Information Scanning frequency 705000000Hz
700101000001 7-Information Trying to synchronize ...
700101000001 7-Information Vendor Cold Start
050825070005 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=74C9C0 Info:000A)
050825065945 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=74C9C0 Info:000A)
050825065925 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=74C9C0 Info:000A)
050825065905 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=74C9C0 Info:000A) |
|
drake
drizzy
Premium,MVM
join:2002-06-10
Brooklyn, NY
 ·Optimum Online
| You're not having issues, with your connection, are you?
Your signal levels are fine.
You can always view this FAQ, for future reference on "acceptable" signal values.
--
I intend to live forever, or die trying. |
|
darn4nr
join:2005-08-22
Fremont, CA
| reply to darn4nr
Thanks for the pointer and I apologize for my noobness.
I don't think I have an issue with the link between my modem and the node but I do get regular disconnects. You might have seen some earlier ramblings from me.
What intrigues me atm is that I upgraded my pc's nic drivers and the frequency seems to have gone down. However Is till see frequent "hang-ups". Web pages not loading but if I click again they will come. DNS resolution not working but if i try again it works. Gameservers, without lag, statign I have connection issues and kicking me off the server.
I do see slow pings on trace routes but when I hooke up my pc directly to the modem, they went lower (as in better) but I kept the disconnects.
So I'm now suspecting my router (RF114P netgear) which doesnt seem to have known issues atm or my in house wiring OR its really the internet thats flaky around here (given the many downtream ping and packet loss sightings).
Anyway, in summary, I'm trying to elimintae as many components as I can
Once more thanks a gazallion times to all that share their experiences and wisdom! |
|
darcilicious
Cyber Librarian
Premium
join:2001-01-02
Forest Grove, OR | Which modem do you have?
Also, let's make this the ONLY thread we all post to about your issues so all the info is one place |
|
Kip patterson
Premium
join:2000-10-23
Columbus, OH | reply to darn4nr
That is an appalling number of T3 timeouts. You have a problem. It is between the mofem and the headend. None of your gear beyond the modem can be involved.
You need Comcast support. |
|
grembowski
Gadget Freak
Premium
join:2005-08-18
Washougal, WA | reply to darn4nr
I was having DNS resolution problems with my Comcast service, so I added these DNS server IPs to my list at the top:
4.2.2.1
4.2.2.2
4.2.2.3 |
|
TechnoScott
Premium
join:2003-03-25
00000
| reply to darn4nr
The only thing you can do at the house is make sure that all of the fittings are torqued down enough. T3 timeouts are usually caused by loose fittings/ingress/loose set screws at taps/bad shields/kinked cable. Loose fittings are the number one problem though. Take a wrench from the modem to the tap (if you can get to it (like apartment)) and tighten everything. Don't stand on the wrench but snug everything. Also try disconnecting tv's in the house one by one and see if they are backfeeding any noise into the system. |
|
darn4nr
join:2005-08-22
Fremont, CA
| reply to darn4nr
Lol paradisecowgirl I'm sorry about the different posts but I'm so desparate I'm flailing. but I'll keep it all here from now
Software Version: SB5120-2.14.0.7-SCM00-NOSH
Hardware Version: 4
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4
Thanks! |
|
darn4nr
join:2005-08-22
Fremont, CA
| reply to darn4nr
So for good measure I restarted my modem this morning and
I still have these T3- errors. Is this normal or as someone mentioned this is a problem ?
Thanks!
050826100734 3-Critical R02.0 No Ranging Response received - T3 time-out
050826100522 3-Critical R02.0 No Ranging Response received - T3 time-out
050826100520 3-Critical R02.0 No Ranging Response received - T3 time-out
050826095852 3-Critical R02.0 No Ranging Response received - T3 time-out
050826095826 3-Critical R02.0 No Ranging Response received - T3 time-out
050826092028 3-Critical R02.0 No Ranging Response received - T3 time-out
050826090619 3-Critical R02.0 No Ranging Response received - T3 time-out
050826090616 3-Critical R02.0 No Ranging Response received - T3 time-out
050826090226 3-Critical R02.0 No Ranging Response received - T3 time-out
050826090159 3-Critical R02.0 No Ranging Response received - T3 time-out
050826085950 3-Critical R02.0 No Ranging Response received - T3 time-out
050826085923 3-Critical R02.0 No Ranging Response received - T3 time-out
050826083704 3-Critical R02.0 No Ranging Response received - T3 time-out
050826083647 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
050826083645 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
050826083645 7-Information B401.0 Authorized
050826083645 7-Information 7 I500.0 Registration Completed |
|
Kip patterson
Premium
join:2000-10-23
Columbus, OH | One or two a day is reasonable. 13 in an hour and a half is not.
If you are having drop outs, they are likely caused by whatever is causing this. |
|
darn4nr
join:2005-08-22
Fremont, CA | reply to darn4nr
Thank you! Back to the comcast hotline |
|
darn4nr
join:2005-08-22
Fremont, CA
| So I chatted with Comcast and we have a tech scheduled for this Sunday. As we were chatting (at the end luckily) my modem reset and showed the following. Interestingly the T3 timer issues haven't appeared since.
Anybody know what happened here?
Also is this watchdog error important (I doubt it but still.. )?
050826135336 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B2A4C3 Info:000B)
050826135316 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B2A4C3 Info:000B)
050826132454 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=9789BF Info:0003)
050826132434 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=9789BF Info:0003)
050826111055 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
050826111054 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
050826111053 7-Information B401.0 Authorized
050826111053 7-Information 7 I500.0 Registration Completed
050826111053 7-Information SEC: Co-Signer CVC from configuration file was verified
050826111052 7-Information REGISTRATION COMPLETE - Waiting for Operational status
050826111052 7-Information 7 D509.0 Retrieved TFTP Config SUCCESS
050826111052 7-Information Registration file - downloaded
050826111051 7-Information Trying to download Configuration file ...
050826111051 7-Information 7 D507.0 Retrieved Time....... SUCCESS
050826111051 7-Information Time of day - retrieved
050826111050 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
050826111050 7-Information DHCP - parameters acquired
050826111045 7-Information 7 T500.0 Acquired Upstream .......... SUCCESS
050826111045 7-Information Trying to register through CMTS...
050826111045 7-Information SYNCHRONIZED - 705000000 Hz , ucd 5
050826111032 3-Critical R02.0 No Ranging Response received - T3 time-out
050826111027 3-Critical R02.0 No Ranging Response received - T3 time-out
050826111015 3-Critical R02.0 No Ranging Response received - T3 time-out
050826111014 3-Critical R02.0 No Ranging Response received - T3 time-out
050826111012 3-Critical R02.0 No Ranging Response received - T3 time-out
050826111010 3-Critical R02.0 No Ranging Response received - T3 time-out
050826111008 7-Information Starting Ranging On Channel 5
050826111004 7-Information Downstream Locked - Collecting Upstream Information
050826111004 7-Information 7 T501.0 Acquired Downstream (705000000 Hz)........ SUCCESS
050826111002 7-Information Scanning frequency 705000000Hz
050826111001 7-Information Scanning frequency 109754000Hz
050826111001 7-Information Scanning frequency 103754000Hz
050826111000 7-Information Scanning frequency 97754000Hz
050826111000 7-Information Scanning frequency 91754000Hz
050826110959 7-Information Scanning frequency 853792000Hz
050826110959 7-Information Scanning frequency 847792000Hz
050826110959 7-Information Scanning frequency 841791000Hz
050826110959 7-Information Scanning frequency 835791000Hz
050826110959 7-Information Scanning frequency 829791000Hz
050826110958 7-Information Scanning frequency 823790000Hz
050826110958 7-Information Scanning frequency 817790000Hz
050826110958 7-Information Scanning frequency 811790000Hz
050826110958 7-Information Scanning frequency 805789000Hz
050826110958 7-Information Scanning frequency 799789000Hz
050826110957 7-Information Scanning frequency 793789000Hz
050826110957 7-Information Scanning frequency 787789000Hz
050826110957 7-Information Scanning frequency 781788000Hz
050826110957 7-Information Scanning frequency 775788000Hz
050826110957 7-Information Scanning frequency 769788000Hz |
|
sortofageek
Premium,Mod
join:2001-08-19
Valhalla Dr
clubs:
·Comcast
Host:
Team Helix
Distributed Comput..
Linksys
Comcast HSI
Comcast Cable TV
| They may have flashed the bios of your modem to a newer version.
Look to see if your modem diagnostic page still says this:
Software Version: SB5120-2.14.0.7-SCM00-NOSH
Hardware Version: 4
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4
--
Team Helix August 2005 Roll Call - Team Helix Forum - Join Us? |
|
darn4nr
join:2005-08-22
Fremont, CA
| reply to darn4nr
Its still the same version.
I just came back and noticed that from 11am till 13:24 it was error free. Than at 13:24 some watchdog errors appeared but at 17:53 it start loosing the keep alive and than synch and resets. Since that time until now (about 2 hrs) no errors.
I'll show it to the tech on Sunday but if any expert can read something in the events I post here please let me know.
050826175429 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
050826175427 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
050826175427 7-Information B401.0 Authorized
050826175427 7-Information 7 I500.0 Registration Completed
050826175427 7-Information SEC: Co-Signer CVC from configuration file was verified
050826175426 7-Information REGISTRATION COMPLETE - Waiting for Operational status
050826175425 7-Information 7 D509.0 Retrieved TFTP Config SUCCESS
050826175425 7-Information Registration file - downloaded
050826175424 7-Information Trying to download Configuration file ...
050826175424 7-Information 7 D507.0 Retrieved Time....... SUCCESS
050826175424 7-Information Time of day - retrieved
050826175423 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
050826175423 7-Information DHCP - parameters acquired
050826175418 7-Information 7 T500.0 Acquired Upstream .......... SUCCESS
050826175418 7-Information Trying to register through CMTS...
050826175418 7-Information SYNCHRONIZED - 705000000 Hz , ucd 5
050826175404 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175349 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175344 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175343 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175341 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175341 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175339 7-Information Starting Ranging On Channel 5
050826175335 7-Information Downstream Locked - Collecting Upstream Information
050826175335 7-Information 7 T501.0 Acquired Downstream (705000000 Hz)........ SUCCESS
050826175333 7-Information Scanning frequency 705000000Hz
050826175333 7-Information Trying to synchronize ...
050826175333 7-Information Synchronization LOST
050826175333 3-Critical R03.0 Ranging Requests Retries exhausted
050826175332 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175330 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175329 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175328 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175327 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175326 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175324 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175323 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175322 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175321 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175320 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175318 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175317 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175316 3-Critical R02.0 No Ranging Response received - T3 time-out
050826175315 3-Critical R02.0 No Ranging Response received - T3 time-out
050826135336 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B2A4C3 Info:000B)
050826135316 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B2A4C3 Info:000B)
050826132454 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=9789BF Info:0003)
050826132434 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=9789BF Info:0003)
050826111055 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
050826111054 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL |
|
darn4nr
join:2005-08-22
Fremont, CA
| reply to darn4nr
Ok the tech was here and at least this one was patient enough to listen to me. We replaced the modem and in the process my acct info was wiped out so it couldn't register. The new system still has some bugs .
That was fixed. New modem same issues. I have a pc hooked up straight to the modem now for these tests. I still see the T3 errors.
He said he would setup a "monitor request" so they can witness what happens over a longer period of time. He also mentioned that there were resets on several modems in the area around the same times. He asked to wait a few days and than call in again if the problem was still there.
Supposedly some work is being done that could affect me.
When I look at my network sniffer output it seems like all traffic just stops for a few sec at which time I have to reload the webpage, re-ask a DNS resolution or get kicked from my game. Althoug sometimes these events correlate with a T3 error or this watchdog error there is not a 1to1 relation as far as i can see from the modem logs.
It does not seem to be related to congestion or traffic peaks since traceroute polls show on average a packet loss of 2-5% on basically all interfaces. Since its a relatively long path and polls take a sec there is no timestamp correlation possible.
So aside from the link between the head end and me (which still show some T3 critical error) I'm beginning to think ethernet cards. Both pc's I use have onboard ethernets. One is an intel the other a MArvel Yukon. They are on the latest drivers. Anybody ever seen my symptoms in relation to onboard ether cards?
I will place this same question on a more related forum too but thought i'd ask here anyway
Thanks again for any et all pointers. |
|
Kip patterson
Premium
join:2000-10-23
Columbus, OH
| There is nothing you (or your computers) can do to cause a T3 error. It is between the modem and the headend.
If you connect directly to the modem, you can use Ethereal to keep an eye on the connection. There will be a steady stream of ARP packets, 10 to 100 per second. When they go away you know that your conmection is down. |
|
SparkChaser
BURY BECK
Premium
join:2000-06-06
Downingtown, PA | For all of us non-experts,:D what is a T3 error? I get them too. |
|
darn4nr
join:2005-08-22
Fremont, CA
| reply to darn4nr
Kip,
Interesting you'd menion the arp's. I'm actually running ethereal (great tool btw) and was wondering wether I should see all my neigbor's arp requests . Now I know thanks!.
It is ethereal that showed me that basically I stop receiving packets. Now I've focused on the application at hand and will need to go back and check to see if the arp's also stop. Atm I'd say that only UDP packets stop coming back but I'll have to validate that.
Beeron:
050826175332 3-Critical R02.0 No Ranging Response received - T3 time-out
Its a kind of keep alive message. Someone earlier posted how many is acceptable |
|
darn4nr
join:2005-08-22
Fremont, CA
| reply to darn4nr
Now a new thing.. DHCP renewing of the modem.
Anybody can read anything into this?
Thanks..
050828210202 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=EC59C3 Info:0004)
050828210142 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=EC59C3 Info:0004)
050828210122 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=EC59C3 Info:0004)
050828184602 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
050828183617 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=2AF0DD Info:000B)
050828174403 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B285E4 Info:000D)
050828154357 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
050828154357 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
050828154357 5-Warning DHCP: Renew: Another TFTP server IP address
050828133942 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=BE0A73 Info:0003)
050828130340 3-Critical R02.0 No Ranging Response received - T3 time-out
050828124157 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
050828124156 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL |
|
darn4nr
join:2005-08-22
Fremont, CA
| Oh boy something is happening but I have no idea what. Any feedback before I call comcast again?
050829115716 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=F06B04 Info:000D)
050829115656 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=F06B04 Info:000D)
050829115636 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=F06B04 Info:000D)
050829115616 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=F06B04 Info:000D)
050829112533 3-Critical R02.0 No Ranging Response received - T3 time-out
050829094724 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
050829094724 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
050829094724 5-Warning DHCP: Renew: Another TFTP server IP address
050829092049 3-Critical R02.0 No Ranging Response received - T3 time-out
050829054222 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=67BA96 Info:0004)
050829054202 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=67BA96 Info:0004)
050829051800 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
050829051758 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
050829051758 7-Information B401.0 Authorized
050829051758 7-Information 7 I500.0 Registration Completed
050829051758 7-Information SEC: Co-Signer CVC from configuration file was verified
050829051756 7-Information REGISTRATION COMPLETE - Waiting for Operational status
050829051756 7-Information 7 D509.0 Retrieved TFTP Config SUCCESS
050829051756 7-Information Registration file - downloaded
050829051755 7-Information Trying to download Configuration file ...
050829051755 7-Information 7 D507.0 Retrieved Time....... SUCCESS
050829051755 7-Information Time of day - retrieved
700101000015 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
700101000015 7-Information DHCP - parameters acquired
700101000011 7-Information 7 T500.0 Acquired Upstream .......... SUCCESS
700101000011 7-Information Trying to register through CMTS...
700101000011 7-Information SYNCHRONIZED - 705000000 Hz , ucd 5
700101000008 7-Information Starting Ranging On Channel 5
700101000004 7-Information Downstream Locked - Collecting Upstream Information
700101000004 7-Information 7 T501.0 Acquired Downstream (705000000 Hz)........ SUCCESS
700101000002 7-Information Scanning frequency 705000000Hz
700101000001 7-Information Trying to synchronize ...
700101000001 7-Information Vendor Cold Start
050829051711 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B4F5F6 Info:000C)
050829051651 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B4F5F6 Info:000C)
050829051631 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B4F5F6 Info:000C)
050829051611 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=B4F5F6 Info:000C)
050829041610 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=1EBDAD Info:0002)
050829041041 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
050829014431 3-Critical R02.0 No Ranging Response received - T3 time-out
050829013711 3-Critical R02.0 No Ranging Response received - T3 time-out
050829013710 3-Critical R02.0 No Ranging Response received - T3 time-out
050829010836 7-Information 7 D511.0 Retrieved DHCP .......... SUCCESS
050829010836 5-Warning D103.0 DHCP RENEW WARNING - Field invalid in response
050829010836 5-Warning DHCP: Renew: Another TFTP server IP address
050829010835 4-Error D101.0 DHCP RENEW sent - No response
050829010731 4-Error D101.0 DHCP RENEW sent - No response
050829010700 4-Error D101.0 DHCP RENEW sent - No response
050829010644 4-Error D101.0 DHCP RENEW sent - No response
050829010637 4-Error D101.0 DHCP RENEW sent - No response
050829010633 4-Error D101.0 DHCP RENEW sent - No response
050829010530 4-Error D101.0 DHCP RENEW sent - No response
050829010459 4-Error D101.0 DHCP RENEW sent - No response
050829010443 4-Error D101.0 DHCP RENEW sent - No response
050829010435 4-Error D101.0 DHCP RENEW sent - No response
050829010431 4-Error D101.0 DHCP RENEW sent - No response
050829010428 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=9A1BE1 Info:0004)
050829010408 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=9A1BE1 Info:0004)
050829010348 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=9A1BE1 Info:0004)
050829010328 4-Error D101.0 DHCP RENEW sent - No response
050829010256 4-Error D101.0 DHCP RENEW sent - No response
050829010240 4-Error D101.0 DHCP RENEW sent - No response
050829010233 4-Error D101.0 DHCP RENEW sent - No response
050829010230 4-Error D101.0 DHCP RENEW sent - No response
050829010226 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=4FA8A9 Info:000C)
050829010206 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=4FA8A9 Info:000C)
050829010146 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=4FA8A9 Info:000C)
050829010126 4-Error D101.0 DHCP RENEW sent - No response
050829010055 4-Error D101.0 DHCP RENEW sent - No response
050829010040 4-Error D101.0 DHCP RENEW sent - No response
050829010032 4-Error D101.0 DHCP RENEW sent - No response
050829010029 4-Error D101.0 DHCP RENEW sent - No response
050829010026 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=66AA4 Info:0007)
050829010006 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=66AA4 Info:0007)
050829005946 5-Warning US: WatchDog: BD 0 stuck for 20 Sec (TxTime=66AA4 Info:0007)
050829005926 4-Error D101.0 DHCP RENEW sent - No response
050829005855 4-Error D101.0 DHCP RENEW sent - No response
050829005839 4-Error D101.0 DHCP RENEW sent - No response
050829005831 4-Error D101.0 DHCP RENEW sent - No response
050829005827 4-Error D101.0 DHCP RENEW sent - No response
050829005723 4-Error D101.0 DHCP RENEW sent - No response
050829005651 4-Error D101.0 DHCP RENEW sent - No response
050829005635 4-Error D101.0 DHCP RENEW sent - No response
050829005627 4-Error D101.0 DHCP RENEW sent - No response
050829005623 4-Error D101.0 DHCP RENEW sent - No response
050829005520 4-Error D101.0 DHCP RENEW sent - No response
050829005448 4-Error D101.0 DHCP RENEW sent - No response
050829005432 4-Error D101.0 DHCP RENEW sent - No response
050829005425 4-Error D101.0 DHCP RENEW sent - No response
050829005422 4-Error D101.0 DHCP RENEW sent - No response
050829005318 4-Error D101.0 DHCP RENEW sent - No response
050829005247 4-Error D101.0 DHCP RENEW sent - No response
050829005231 4-Error D101.0 DHCP RENEW sent - No response
050829005223 4-Error D101.0 DHCP RENEW sent - No response
050829005219 4-Error D101.0 DHCP RENEW sent - No response
050829005115 4-Error D101.0 DHCP RENEW sent - No response
050829005043 4-Error D101.0 DHCP RENEW sent - No response
050829005027 4-Error D101.0 DHCP RENEW sent - No response
050829005019 4-Error D101.0 DHCP RENEW sent - No response
050828233250 3-Critical R02.0 No Ranging Response received - T3 time-out |
|
