<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:x="urn:schemas-microsoft-com:office:excel" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.hoenzb
{mso-style-name:hoenzb;}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Tahoma","sans-serif";
color:#44546A;
font-weight:normal;
font-style:normal;
text-decoration:none none;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#44546A'>Yes, there was/is an interop issue with how some CMTS and D3 modems dealt with losing one or more bonded channels. One of the ways to deal with a missing service flow was just to reset the CM. I’ve seen this feature described as “cable modem reboot due to partial service” and “cable modem reboot due to bonding recovery”.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#44546A'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#44546A'>The DOCSIS MULPI spec, as written, has a very weak recovery mechanism for downstream flows that get out of sync. It says that both 2 minutes *and* 1,000 out of order packets have to be passed for a service flow to be recovered. Cisco CMTS, ARRIS CMTS, and many (most) operators that have encountered out-of-range (OOR) agree that the MULPI specification is insufficient in terms of out-of-order downstream flow recovery. See section 9.2.4 bullet point four of <a href="http://www.broadbandreports.com/r0/download/2055956~e8c5b3cd040e9b60a2e56421526f80b9/365-095-20591_x2.pdf">http://www.broadbandreports.com/r0/download/2055956~e8c5b3cd040e9b60a2e56421526f80b9/365-095-20591_x2.pdf</a> for details.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#44546A'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#44546A'>CM-STATUS messages are supposed to communicate the status of flows, but earlier versions of one vendor’s eMTA firmware did not support CM-STATUS well. However, this vendor (not Moto) says they haven't had CM-STATUS interop issues with ARRIS C4 CMTSs and Cisco 10K CMTSs in a couple of years. <o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#44546A'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#44546A'>Frank<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:#44546A'><o:p> </o:p></span></p><p class=MsoNormal><b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>From:</span></b><span style='font-size:11.0pt;font-family:"Calibri","sans-serif"'> Ryan McIntosh [mailto:rmcintosh@nitemare.net] <br><b>Sent:</b> Monday, September 16, 2013 3:43 PM<br><b>To:</b> Frank Bulk<br><b>Cc:</b> Jay Ashworth; outages-discussion<br><b>Subject:</b> Re: [Outages-discussion] RoadRunner/Bright House cablemodem problems<o:p></o:p></span></p><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>Sorry frank for the double post, I'm hating gmail today as I hit "reply" and not "reply to all".<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Generally speaking that sounds like a signal issue. The newer docsis 3 modems tend to issue a reboot or temporary port down while it resyncs the channels (depending how many up/down its using). When a channel drops off or is intermediate you'll get this temporary state of non-working port where it reboots or blocks the port. So all in all, sounds like a signal problem, even though you might have perfect signal.</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-size:10.0pt;font-family:"Arial","sans-serif"'>Ryan</span><o:p></o:p></p></div></div><div><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Mon, Sep 16, 2013 at 4:35 PM, Frank Bulk <<a href="mailto:frnkblk@iname.com" target="_blank">frnkblk@iname.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><p class=MsoNormal>Is this a Motorola gateway or cable modem? Non-gateway cable modems<br>typically have just one Ethernet port. How do you know it reboots versus<br>doing a T4 reset because of communication issues?<br><span style='color:#888888'><br><span class=hoenzb>Frank</span></span><o:p></o:p></p><div><div><p class=MsoNormal><br>-----Original Message-----<br>From: Outages-discussion [mailto:<a href="mailto:outages-discussion-bounces@outages.org">outages-discussion-bounces@outages.org</a>] On<br>Behalf Of Jay Ashworth<br>Sent: Monday, September 16, 2013 3:11 PM<br>To: outages-discussion<br>Subject: [Outages-discussion] RoadRunner/Bright House cablemodem problems<br><br>On a new install for a client, we're seeing that the cable modem drops<br>out on us, and in a very interesting way.<br><br>Every so randomly often, it apparently does an uncommanded reboot (this<br>according to a guy who was logged into the CMTS looking at it one time it<br>did so), and when it does, 2 connected devices see the ethernet drop for 3-5<br><br>seconds, come back up for 15, then drop again for 3-5, and then go back<br>to normal. I see this behavior logged exactly to the second on both the<br>attached Fortigate router and my Linux laptop; we've replaced the cable<br>modem and the ethernet cables coming out of it.<br><br>Oddly, it only seems to happen when there's traffic on the link; I haven't<br>seen a drop get logged when the link is idle (overnight/weekends).<br><br>The cablemodem is a DOCSIS3, Motorola Surfboard Extreme (that's not exact,<br>but I can provide a model number if anyone thinks it's critical).<br>Everything<br>in the cage is on a brand new 2000VA UPS.<br><br>Anyone ever seen a cablemodem misbehave in this particularly peculiar way<br>before?<br><br>Cheers,<br>-- jra<br>--<br>Jay R. Ashworth Baylink<br><a href="mailto:jra@baylink.com">jra@baylink.com</a><br>Designer The Things I Think RFC<br>2100<br>Ashworth & Associates <a href="http://baylink.pitas.com" target="_blank">http://baylink.pitas.com</a> 2000 Land Rover<br>DII<br>St Petersburg FL USA #natog +1 727 647<br>1274<br>_______________________________________________<br>Outages-discussion mailing list<br><a href="mailto:Outages-discussion@outages.org">Outages-discussion@outages.org</a><br><a href="https://puck.nether.net/mailman/listinfo/outages-discussion" target="_blank">https://puck.nether.net/mailman/listinfo/outages-discussion</a><br><br><br>_______________________________________________<br>Outages-discussion mailing list<br><a href="mailto:Outages-discussion@outages.org">Outages-discussion@outages.org</a><br><a href="https://puck.nether.net/mailman/listinfo/outages-discussion" target="_blank">https://puck.nether.net/mailman/listinfo/outages-discussion</a><o:p></o:p></p></div></div></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>