Excite Could Go Dark On Friday

robvasquez writes: "According to this CNET article, excite @home could be pulling the plug on cable modem subscribers. What's your providers back up plan? Could milions of trolls and Nimda spreaders be taken off line?"

Comments

@Home trying to keep subs until last packet....

[Arethan]

I'm hearing rumors that @Home is delibrately causing issues with customer account conversions at various cable offices. My fiance is a CSR, and she's been talking about how @Home's sytems are no longer removing modem records from the headends, and the regional General Manager is contantly on the phone bitching at them to fix it (and fast). Apparently every time they try to convert a customer, they issue the account close operation, and it returns successfully, but the customer's modem stays online. When they add the local record for the subscriber, their UBR is given the appropriate information and will accept the modems, but the customer has a 50/50 chance of the @Home UBR responding before theirs. Effectively keeping most customers on @Home's network.

You'd think that they were just having issues with their UBR, or maybe with their access to @Home's subscriber management system, but they are able to successfully add new customers to their own service just fine, and everything was going smoothly with conversions until just a week ago.

Could be @Home being a prick until the very last minute, could be a coincedence. I'm not apt to support one theory or the other, I'm just relaying what I hear.

Moderation: -1 Heresay! (lmao)

Re:@Home trying to keep subs until last packet....

[hyrdra]

I'm a network engineer for a cable provider in Columbus, Ohio. What we do is contract backbone service out to bandwidth companies in the area. When we switch networks what we do is issue a DHCP update to all of our nodes, and turn the DHCP server off before it has time to respond with a new IP address on the old network. We then send a TFTP configuration to the modem to turn the network control access object off, switch the HFC IP address, turn it back on, and by this time the DHCP server on the new network responds with the new IP address.

The process is completly transparent and the only hit is to programs which keep a constant port open (e.g. file sharing programs), will suddenly loose a connection for receiving (sinc they have a new IP). However, they usually time out and reconnect.

It also has the added advantage of flushing out priate modems on the network, since customers who use a modem with it's TFTP disabled or it's control locked to on don't receive the new info for the new network and are stuck on an old, dead network.

We have switched networks over four times with only a few support calls. It could have been a big deal, requiring customer talk-throughs but we do it transparently.