I am hoping someone here has a solution. We have a rogue modem we have no idea where it is. It was a customers 6 years ago and is somewhere on our network. Problem is it never connects to get the disabled config it just harasses our cmts.
It pollutes the log files so it makes syslogging worthless when we want to identify any other issues.
Is there some way to ignore this modem completely?
SLOT 8/0: Jan 6 03:01:58.344 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:05:24.144 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:08:51.172 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:12:12.246 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:15:27.938 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:18:56.194 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:22:08.226 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:25:33.242 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:29:05.254 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:32:21.690 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
SLOT 8/0: Jan 6 03:35:35.978 PST: %UBR10000-5-UNREGSIDTIMEOUT: CMTS deleted unregistered Cable Modem 0012.2500.07ce
Is there some magical method to find it? I can tell what node it's coming from but thats it.. and well that is like 8 miles of plant.
I'm not a Cisco guy, but would assume there's a cable modem 0012.2500.07ce deny that can be added.
example on a Casa C100G:
CASA_100G(config)#cab modem deny ?
xxxx.xxxx.xxxx,CM mac address
I don't think you can block a particular cm on ubr10k
If it's a real big issue, then you should be able to locate the modem without too much effort.
Treat it like a noise source....
Go to the node, unplug legs one by one, watching for that modem to go offline.
Then divide and conquer down that leg until you locate the drop.
Should take what, 1 hour max?
Gah thats horrifying.. We get calls anytime we have latency, much less actually dropping a connection, damn gamers play 24 hours a day. Fortnight!
Ha!
Well I said it was only if its a big problem... :-)
Otherwise, "show log | excl UNREG"
On a Cisco CMTS you can do
cable privacy hotlist cm 0012.2500.07ce
You can block this Modem permanent on a Cisco CMTS in config mode with
cable privacy hotlist cm 0012.2500.07ce