It gets booted because you cant seem to respond to unicast maintenance, which is used to keep all the CM's synced to the master (CMTS).. Offsets for timing are used and since all the CM's are using TDMA, this is where the "T" is critical, as each modem can only burst in its own allocated time slot. If the offset is too great, you will collide with other cm's and cause collisions. Seems your CMTS does this maintenance when more cm's are active. Maybe subscribers getting home and using their internet more, but for whatever reason, your modem isnt responding to T-3 requests and the CMTS is dropping you, most likely a DocsDevReset command sent. Dont have IGNORE any timeouts what so ever in the Haxorware GUI. No ticks
Started Unicast Maintenance Ranging - No Response received - T3 time-out
Since we use an access method known as TDMA and A-TDMA, read what TDMA means it based on Time Division Multiple Access. Again, Time is critical.
A simple analogy would be a large auditorium with a speaker at the podium (he will be the CMTS) He speaks and then audience members (the CM's) are all listening. If anyone wants to respond (ask a question/send a querie) it can only be done one at a time. If all the people in the audience stood up at once and began asking questions, the Podium (CMTS) would never hear anyone as they are all talking at the same time. This is where we use Unicast management. So, now, only one modem stands up and speaks and the podium (CMTS) hears that message.
Kapisch?
P.S
and the larger the audience (more subscribers with CM's) the more critical it is to keep everyone synced so no 2 or 3 or (X) cable modems (CM's) will ever querie at the same time and collide..Collisions which have HTTP headers are ACK and NACK and cause a re-transmit. Ironically, this shows up as a higher PING as the packet had to be retransmitted again. VOIP doesnt re-transmit, so any packet here is lost/collided and is generally seen by a drop or gap or stuttering on the other end..
Started Unicast Maintenance Ranging - No Response received - T3 time-out
Since we use an access method known as TDMA and A-TDMA, read what TDMA means it based on Time Division Multiple Access. Again, Time is critical.
A simple analogy would be a large auditorium with a speaker at the podium (he will be the CMTS) He speaks and then audience members (the CM's) are all listening. If anyone wants to respond (ask a question/send a querie) it can only be done one at a time. If all the people in the audience stood up at once and began asking questions, the Podium (CMTS) would never hear anyone as they are all talking at the same time. This is where we use Unicast management. So, now, only one modem stands up and speaks and the podium (CMTS) hears that message.
Kapisch?
P.S
and the larger the audience (more subscribers with CM's) the more critical it is to keep everyone synced so no 2 or 3 or (X) cable modems (CM's) will ever querie at the same time and collide..Collisions which have HTTP headers are ACK and NACK and cause a re-transmit. Ironically, this shows up as a higher PING as the packet had to be retransmitted again. VOIP doesnt re-transmit, so any packet here is lost/collided and is generally seen by a drop or gap or stuttering on the other end..
Knowledge=Power