Is it customers that have the same cpu wireless router make/model that are having issues? Wonder if they still think their PPPoE is connected and sending the old session ID which the router doesnt know anything about. Does a reboot of the CPE router fix it or only the ethernet port trick? What IOS, so I can watch out for this on my upgrade? :)
-c > On Mar 23, 2015, at 4:37 PM, Chuck McCown <[email protected]> wrote: > > Upgraded the IOS in a router. It is a core router so everyone got dropped > during a reboot. Now we have a bunch of cpe (wireless routers with a PPPoE > client inside) that are squawking back “Bad Session ID” so we have to disable > and re-enable the ethernet port to make them work.
