Problems with a 1720 and Toshiba Cable Modem

epresutti · ‎08-30-2002

I have a 1720 / 32MB of RAM / 8MB of Flash / WIC-1ENET. The WIC-1ENET is connected to the Cable Modem (Toshiba PCX1100U) and the internal FastEthernet is connected to my internal LAN. The router does not draw a DHCP address from the cable modem, even though a PC configured for DHCP will draw an IP address. I receive the following error message from the router when using the "debug dhcp detail" command.

Thanks in advance,

Ed Presutti

*Mar 1 00:17:42.407: B'cast on FastEthernet0 interface from 0.0.0.0

*Mar 1 00:17:45.403: DHCP: SDiscover attempt # 2 for entry:

*Mar 1 00:17:45.403: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:17:45.403: Temp sub net mask: 0.0.0.0

*Mar 1 00:17:45.403: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:17:45.403: DHCP transaction id: 210B

*Mar 1 00:17:45.403: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:17:45.403: Next timer fires after: 00:00:03

*Mar 1 00:17:45.403: Retry count: 2 Client-ID: 0002.1762.0705

*Mar 1 00:17:45.403: DHCP: SDiscover: sending 287 byte length DHCP packet

*Mar 1 00:17:45.403: DHCP: SDiscover 287 bytes

*Mar 1 00:17:45.407: B'cast on FastEthernet0 interface from 0.0.0.0

*Mar 1 00:17:48.403: DHCP: SDiscover attempt # 3 for entry:

*Mar 1 00:17:48.403: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:17:48.403: Temp sub net mask: 0.0.0.0

*Mar 1 00:17:48.403: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:17:48.403: DHCP transaction id: 210B

*Mar 1 00:17:48.403: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:17:48.403: Next timer fires after: 00:00:03

*Mar 1 00:17:48.403: Retry count: 3 Client-ID: 0002.1762.0705

*Mar 1 00:17:48.403: DHCP: SDiscover: sending 287 byte length DHCP packet

*Mar 1 00:17:48.403: DHCP: SDiscover 287 bytes

*Mar 1 00:17:48.407: B'cast on FastEthernet0 interface from 0.0.0.0

*Mar 1 00:17:51.403: DHCP: QScan: Timed out Selecting state

*Mar 1 00:17:56.375: DHCP: Try 4 to acquire address for FastEthernet0

*Mar 1 00:17:56.387: DHCP: allocate request

*Mar 1 00:17:56.387: DHCP: zapping entry in DHC_PURGING state for Fa0

*Mar 1 00:17:56.391: DHCP: new entry. add to queue

*Mar 1 00:17:56.391: DHCP: SDiscover attempt # 1 for entry:

*Mar 1 00:17:56.391: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:17:56.391: Temp sub net mask: 0.0.0.0

*Mar 1 00:17:56.391: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:17:56.391: DHCP transaction id: 210C

*Mar 1 00:17:56.391: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:17:56.391: Next timer fires after: 00:00:03

*Mar 1 00:17:56.391: Retry count: 1 Client-ID: cisco-test

*Mar 1 00:17:56.391: DHCP: SDiscover: sending 291 byte length DHCP packet

*Mar 1 00:17:56.395: DHCP: SDiscover 291 bytes

*Mar 1 00:17:56.395: B'cast on FastEthernet0 interface from 0.0.0.0

*Mar 1 00:17:59.391: DHCP: SDiscover attempt # 2 for entry:

*Mar 1 00:17:59.391: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:17:59.391: Temp sub net mask: 0.0.0.0

*Mar 1 00:17:59.391: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:17:59.391: DHCP transaction id: 210C

*Mar 1 00:17:59.391: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:17:59.391: Next timer fires after: 00:00:03

*Mar 1 00:17:59.391: Retry count: 2 Client-ID: cisco-test

*Mar 1 00:17:59.391: DHCP: SDiscover: sending 291 byte length DHCP packet

*Mar 1 00:17:59.391: DHCP: SDiscover 291 bytes

*Mar 1 00:17:59.395: B'cast on FastEthernet0 interface from 0.0.0.0

*Mar 1 00:18:02.391: DHCP: SDiscover attempt # 3 for entry:

*Mar 1 00:18:02.391: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:18:02.391: Temp sub net mask: 0.0.0.0

*Mar 1 00:18:02.391: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:18:02.391: DHCP transaction id: 210C

*Mar 1 00:18:02.391: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:18:02.391: Next timer fires after: 00:00:03

*Mar 1 00:18:02.391: Retry count: 3 Client-ID: cisco-test

*Mar 1 00:18:02.391: DHCP: SDiscover: sending 291 byte length DHCP packet

*Mar 1 00:18:02.391: DHCP: SDiscover 291 bytes

*Mar 1 00:18:02.395: B'cast on FastEthernet0 interface from 0.0.0.0%Unknown DHCP problem.. No ale

*Mar 1 00:18:03.375: DHCP: QScan: Purging entry

*Mar 1 00:18:03.375: DHCP: deleting entry 80F018B0 0.0.0.0 from list

*Mar 1 00:18:03.375: Temp IP addr: 0.0.0.0 for peer on Interface: unknown

*Mar 1 00:18:03.375: Temp sub net mask: 0.0.0.0

*Mar 1 00:18:03.375: DHCP Lease server: 0.0.0.0, state: 8 Purging

*Mar 1 00:18:03.375: DHCP transaction id: 210A

*Mar 1 00:18:03.375: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:18:03.375: No timer running

*Mar 1 00:18:03.375: Retry count: 0 Client-ID:

*Mar 1 00:18:05.391: DHCP: QScan: Timed out Selecting state

*Mar 1 00:18:06.887: DHCP: allocate request

*Mar 1 00:18:06.887: DHCP: new entry. add to queue

*Mar 1 00:18:06.887: DHCP: SDiscover attempt # 1 for entry:

*Mar 1 00:18:06.887: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:18:06.887: Temp sub net mask: 0.0.0.0

*Mar 1 00:18:06.887: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:18:06.887: DHCP transaction id: 210D

*Mar 1 00:18:06.887: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:18:06.887: Next timer fires after: 00:00:03

*Mar 1 00:18:06.887: Retry count: 1 Client-ID: 0002.1762.0705

*Mar 1 00:18:06.891: DHCP: SDiscover: sending 287 byte length DHCP packet

*Mar 1 00:18:06.891: DHCP: SDiscover 287 bytes

*Mar 1 00:18:06.891: B'cast on FastEthernet0 interface from 0.0.0.0

*Mar 1 00:18:09.887: DHCP: SDiscover attempt # 2 for entry:

*Mar 1 00:18:09.887: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:18:09.887: Temp sub net mask: 0.0.0.0

*Mar 1 00:18:09.887: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:18:09.887: DHCP transaction id: 210D

*Mar 1 00:18:09.887: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:18:09.887: Next timer fires after: 00:00:03

*Mar 1 00:18:09.887: Retry count: 2 Client-ID: 0002.1762.0705

*Mar 1 00:18:09.887: DHCP: SDiscover: sending 287 byte length DHCP packet

*Mar 1 00:18:09.887: DHCP: SDiscover 287 bytes

*Mar 1 00:18:09.891: B'cast on FastEthernet0 interface from 0.0.0.0

*Mar 1 00:18:10.319: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7560

*Mar 1 00:18:10.403: DHCP: Received a BOOTREP pkt Not for us..: xid: 0x7560

*Mar 1 00:18:12.887: DHCP: SDiscover attempt # 3 for entry:

*Mar 1 00:18:12.887: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:18:12.887: Temp sub net mask: 0.0.0.0

*Mar 1 00:18:12.887: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:18:12.887: DHCP transaction id: 210D

*Mar 1 00:18:12.887: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:18:12.887: Next timer fires after: 00:00:03

*Mar 1 00:18:12.887: Retry count: 3 Client-ID: 0002.1762.0705

*Mar 1 00:18:12.887: DHCP: SDiscover: sending 287 byte length DHCP packet

*Mar 1 00:18:12.887: DHCP: SDiscover 287 bytes

*Mar 1 00:18:12.891: B'cast on FastEthernet0 interface from 0.0.0.0

*Mar 1 00:18:15.887: DHCP: QScan: Timed out Selecting state%Unknown DHCP problem.. No allocation possible

*Mar 1 00:18:20.875: DHCP: allocate request

*Mar 1 00:18:20.875: DHCP: zapping entry in DHC_PURGING state for Fa0

*Mar 1 00:18:20.875: DHCP: new entry. add to queue

*Mar 1 00:18:20.875: DHCP: SDiscover attempt # 1 for entry:

*Mar 1 00:18:20.875: Temp IP addr: 0.0.0.0 for peer on Interface: FastEthernet0

*Mar 1 00:18:20.875: Temp sub net mask: 0.0.0.0

*Mar 1 00:18:20.875: DHCP Lease server: 0.0.0.0, state: 1 Selecting

*Mar 1 00:18:20.875: DHCP transaction id: 210E

*Mar 1 00:18:20.875: Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

*Mar 1 00:18:20.875: Next timer fires after: 00:00:03

*Mar 1 00:18:20.875: Retry count: 1 Client-ID: cisco-test

*Mar 1 00:18:20.879: DHCP: SDiscover: sending 291 byte length DHCP packet

*Mar 1 00:18:20.879: DHCP: SDiscover 291 bytes

*Mar 1 00:18:20.879: B'cast on FastEthernet0 interface from 0.0.0.0^Z

ciscomoderator · ‎09-06-2002

Since there has been no response to your post, it appears to be either too complex or too rare an issue for other forum members to assist you. If you don't get a suitable response to your post, you may wish to review our resources at the online Technical Assistance Center (http://www.cisco.com/tac) or speak with a TAC engineer. You can open a TAC case online at http://www.cisco.com/tac/caseopen

If anyone else in the forum has some advice, please reply to this thread.

Thank you for posting.