Return-Path: Received: from by vbbn.com (CommuniGate Pro RULES 4.1.8) with RULES id 5500774; Wed, 25 Aug 2004 15:50:06 -0700 X-Autogenerated: Redirect Sender: To: updates@vistabroadband.com Date: Wed, 25 Aug 2004 15:50:06 -0700 Message-ID: X-Real-To: X-Original-Return-Path: Received: by vbbn.com (CommuniGate Pro PIPE 4.1.8) with PIPE id 5500766; Wed, 25 Aug 2004 15:50:06 -0700 Received: from [206.176.226.212] (HELO [206.176.226.212]) by vbbn.com (CommuniGate Pro SMTP 4.1.8) with ESMTP id 5500767 for vista-updates@vistabroadband.com; Wed, 25 Aug 2004 15:49:53 -0700 X-Original-Message-ID: <412D178D.9060901@vistabroadband.com> X-Original-Date: Wed, 25 Aug 2004 15:49:49 -0700 From: Vista Broadband Tech Support Reply-To: support@vistabroadband.com User-Agent: Mozilla Thunderbird 0.7.2 (Windows/20040707) X-Accept-Language: en-us, en MIME-Version: 1.0 X-Original-To: undisclosed-recipients:; Subject: Update: Emergency Maintenance Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pop.vistabroadband.com X-Spam-Level: X-Spam-Status: No, hits=-104.2 required=5.0 tests=AWL,BAYES_00, USER_IN_WHITELIST autolearn=ham version=2.63 X-TFF-CGPSA-Filter: Scanned X-TFF-CGPSA-Version: 1.2.7 The emergency maintenance scheduled for tonight has been canceled. The problem that was originally degrading service escalated and required an immediate reboot. We apologize for any hardships caused by this outage. As always, contact support at (707) 665-3870 or support@vistabroadband.com with questions. A detailed description of the problem is at the bottom of this message. -- The Vista Broadband Tech Support Team Problem Details: A newer version of code was loaded on a core router last week to patch a critical vulnerability. The new version apparently had issues with Multilink-PPP - a protocol used to bond multiple physical circuits into one, larger, virtual circuit. This led to erratic behavior on these bundles, which slowly worsened until two major bundles failed. The problem was further exacerbated by the fact that some control traffic continued to pass over the bundles, while other traffic did not. This slowed identification of the problem. The affected routers have been downgraded to older versions of code until we can develop a suitable fix.