Re: ubr924 with Charter Pipeline

asurrette · ‎01-03-2003

I recently recieved a ubr924 cable access router as a gift. It would be really nice to use this in place of my current cable modem/Linux firewall combo. I am having some difficulty getting it to work, though. If anyone can give me some ideas, I would appreciate it.

Thanks,

Alan

P.S. - output from 'debug cable-modem mac log verbose' after a 'write erase' and 'reload'

00:00:05: %LINK-3-UPDOWN: Interface cable-modem0, changed state to up

00:00:05: %LINK-3-UPDOWN: Interface Ethernet0, changed state to up

133.CABLEMODEM.CISCO: 00:00:09: %LINEPROTO-5-UPDOWN: Line protocol on Interface Ethernet0, changed state to up

132.CABLEMODEM.CISCO: 00:00:09: %PARSER-4-BADCFG: Unexpected end of configuration file.

133.CABLEMODEM.CISCO: 00:00:10: %SYS-5-CONFIG_I: Configured from memory by console

133.CABLEMODEM.CISCO: 00:00:10: %SYS-5-RESTART: System restarted --

Cisco Internetwork Operating System Software

IOS (tm) 920 Software (UBR920-K8O3V6Y5-M), Version 12.2(10b), RELEASE SOFTWARE (fc1)

Compiled Thu 11-Jul-02 23:19 by pwade

133.CABLEMODEM.CISCO: 00:00:10: %SNMP-5-COLDSTART: SNMP agent on host Router is undergoing a cold start

131.CABLEMODEM.CISCO: 00:00:10: %IP_SNMP-3-SOCKET: can't open UDP socket

00:00:10: Unable to open socket on port 161

131.CABLEMODEM.CISCO: 00:00:11: %LINK-3-UPDOWN: Interface Foreign Exchange Station 0, changed state to up

131.CABLEMODEM.CISCO: 00:00:11: %LINK-3-UPDOWN: Interface Foreign Exchange Station 1, changed state to up

Router>en

Router#debug cabl

Router#debug cable-modem mac log verbose

Cable Modem mac log debugging is on (verbose)

Router#

00:00:30: 30.470 CMAC_LOG_DS_NO_QAM_FEC_LOCK 543000000

00:00:31: 31.442 CMAC_LOG_DS_NO_QAM_FEC_LOCK 549000000

00:00:32: 32.835 CMAC_LOG_DS_NO_QAM_FEC_LOCK 555000000

00:00:34: 34.189 CMAC_LOG_DS_NO_QAM_FEC_LOCK 561000000

00:00:35: 35.582 CMAC_LOG_DS_NO_QAM_FEC_LOCK 567000000

00:00:35: 35.582 CMAC_LOG_DS_TUNER_KEEPALIVE

00:00:36

blah blah similar stuff ...

00:01:21: 81.023 CMAC_LOG_POWER_LEVEL_IS 24.0 dBmV (commanded)

00:01:21: 81.023 CMAC_LOG_RANGING_BACKOFF_SET 1

00:01:21: 81.023 CMAC_LOG_RNG_REQ_QUEUED 0

00:01:21: 81.131 CMAC_LOG_RNG_REQ_TRANSMITTED

00:01:21: 81.336 CMAC_LOG_T3_TIMER

00:01:21: 81.336 CMAC_LOG_POWER_LEVEL_IS 27.0 dBmV (commanded)

00:01:21: 81.336 CMAC_LOG_RANGING_BACKOFF_SET 3

00:01:21: 81.336 CMAC_LOG_RNG_REQ_QUEUED 0

00:01:21: 81.758 CMAC_LOG_RNG_REQ_TRANSMITTED

00:01:21: 81.958 CMAC_LOG_T3_TIMER

00:01:21: 81.958 CMAC_LOG_POWER_LEVEL_IS 30.0 dBmV (commanded)

00:01:21: 81.958 CMAC_LOG_RANGING_BACKOFF_SET 6

00:01:21: 81.958 CMAC_LOG_RNG_REQ_QUEUED 0

00:01:22: 82.589 CMAC_LOG_RNG_REQ_TRANSMITTED

00:01:22: 82.593 CMAC_LOG_RNG_RSP_MSG_RCVD

00:01:22: 82.593 CMAC_LOG_RNG_RSP_SID_ASSIGNED 1213

00:01:22: 82.593 CMAC_LOG_ADJUST_RANGING_OFFSET 7990

00:01:22: 82.593 CMAC_LOG_RANGING_OFFSET_SET_TO 17600

00:01:22: 82.597 CMAC_LOG_ADJUST_TX_POWER 105

00:01:22: 82.597 CMAC_LOG_STATE_CHANGE ranging_2_state

00:01:22: 82.597 CMAC_LOG_RNG_REQ_QUEUED 1213

00:01:23: 83.203 CMAC_LOG_RNG_REQ_TRANSMITTED

00:01:23: 83.207 CMAC_LOG_RNG_RSP_MSG_RCVD

00:01:23: 83.207 CMAC_LOG_ADJUST_TX_POWER -5

00:01:23: 83.207 CMAC_LOG_RANGING_SUCCESS

00:01:23: 83.211 CMAC_LOG_STATE_CHANGE dhcp_state

00:01:29: 89.307 CMAC_LOG_DHCP_ASSIGNED_IP_ADDRESS 68.118.28.58

00:01:29: 89.307 CMAC_LOG_DHCP_TFTP_SERVER_ADDRESS 172.22.84.1

00:01:29: 89.307 CMAC_LOG_DHCP_ERROR_ACQUIRING_TOD_ADDRESS

00:01:29: 89.307 CMAC_LOG_DHCP_SET_GATEWAY_ADDRESS

00:01:29: 89.311 CMAC_LOG_DHCP_ERROR_ACQUIRING_TZ_OFFSET

00:01:29: 89.311 CMAC_LOG_DHCP_ERROR_ACQUIRING_CONFIG_FILE_NA

00:01:29: 89.311 CMAC_LOG_DHCP_ERROR_ACQUIRING_SEC_SVR_ADDR

00:01:29: 89.311 CMAC_LOG_DHCP_ERROR_ACQUIRING_LOG_ADDRESS

00:01:29: 89.315 CMAC_LOG_DHCP_COMPLETE

00:01:29: 89.315 CMAC_LOG_RESET_DHCP_FAILED

00:01:29: 89.315 CMAC_LOG_STATE_CHANGE reset_interface_state

00:01:29: 89.315 CMAC_LOG_STATE_CHANGE reset_hardware_state

00:01:29: 89.749 CMAC_LOG_STATE_CHANGE wait_for_link_up_state

00:01:29: 89.753 CMAC_LOG_DRIVER_INIT_IDB_RESET 0x804DC040

00:01:29: 89.753 CMAC_LOG_LINK_DOWN

00:01:29: 89.753 CMAC_LOG_LINK_UP

00:01:29: 89.757 CMAC_LOG_STATE_CHANGE ds_channel_scanning_state

131.CABLEMODEM.CISCO: 00:01:29: %IP_SNMP-3-SOCKET: can't open UDP socket

00:01:29: Unable to open socket on port 161

133.CABLEMODEM.CISCO: 00:01:30: %LINEPROTO-5-UPDOWN: Line protocol on Interface cable-modem0, changed state to down

00:01:31: 91.142 CMAC_LOG_DS_NO_QAM_FEC_LOCK 699000000

00:01:31: 91.142 CMAC_LOG_DS_TUNER_KEEPALIVE

00:01:32: 92.379 CMAC_LOG_DS_NO_QAM_FEC_LOCK 705000000

00:01:33: 93.616 CMAC_LOG_DS_NO_QAM_FEC_LOCK 711000000

00:01:34: 94.853 CMAC_LOG_DS_NO_QAM_FEC_LOCK 717000000

00:01:36: 96.089 CMAC_LOG_DS_NO_QAM_FEC_LOCK 723000000

00:01:37: 97.326 CMAC_LOG_DS_NO_QAM_FEC_LOCK 729000000

00:01:38: 98.563 CMAC_LOG_DS_NO_QAM_FEC_LOCK 735000000

kmarrero · ‎01-06-2003

Seems like the upstream is not syncing up with the new router. Look over these two URL's as they both have some great configuring and troubleshooting links on them. One other thing is that it could be that the ISP is only looking to respond to the original cable modems MAC address and it does not recognize the new modems MAC. You may need to contact them and let them know the new MAC.

http://www.cisco.com/pcgi-bin/Support/browse/psp_view.pl?p=Hardware:ubr900

http://www.cisco.com/warp/public/109/

7rbowenii · ‎01-06-2003

Alan,

I had the same problem with Charter. You should be able to simply proxy the old mac address in the new modem. Charter provisions based on geographical area. They also assign mac address ranges to these areas. So, they probably wouldn't allow you to use your own Cable Modem 'cuz then they couldn't charge you. You should be able to grab the mac address off the cable modem and then proxy it through your new device. That is how I got mine to work. I hope this helps.

-Bo

asurrette · ‎01-06-2003

Actually, Charter in this area does allow customers to 'bring their own' cable modems. I called them with the new MAC address, but I'm not 100% sure that they've added the new one. Not being a DOCSIS/cable expert by any means, I'm not sure if they can have two MAC address' associated with my account. They may be waiting for me to drop off the old modem... I'll have to call them again. I do appreciate the help, and I will post the final solution when it does start working.

Alan

asurrette · ‎01-18-2003

That was it. It had not been provisioned. Thanks for the help! Everything (NAT, port-forwarding, firewall feature,etc.) is working...

Alan

edwardsjj · ‎12-24-2003

7rbowenii,

I can not get my ubr924 to work either.

I suspected something like "...i was prohited to use my own modem 'cuz money". So I tried to associated my old Mac with my new cable modem interface.

However, i can only change the mac address on my ethernet interface and not change on the cable interface.

You said "...you simply proxy the old mac to the new modem". My question is; how do you do this?? Any help would be greatly appreciated.