Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Announcements

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

PIX501 with Telewest Blueyonder DSL.

Hi

Please could anyone suggest why my PIX501 will not receive a DHCP assigned address to the Outside interface when plugged into a Telewest supplied Motorola SurfBoard Cable Modem?

I have registered the Outside interface MAC address with the Telewest Blueyonder so it should now be capable of receiving an IP address. PC's and my Linksys AP Router can receive IP addresses fine.

I am using the following commands for this:

ip address outside dhcp retry 4

and

dhcpd auto_config outside

When I show int, Ethernet0 is up and the line protocol is up, but no IP address is assigned. Sometimes I get a row of dot's along the command prompt and eventually "DHCP failed".

Many thanks

Max...

10 REPLIES
Silver

Re: PIX501 with Telewest Blueyonder DSL.

http://www.cisco.com/univercd/cc/td/doc/product/iaabu/pix/pix_sw/v_63/cmdref/c.htm#1053548

Check out the capture command. It is a built in packet capture utility in recent PIX OS revs. It will allow you to capture what is on the wire of the outside of your PIX - you can see if there is an dhcp server offering leases, etc.

Also, debug dhcpc has some options to crank up logging - you can use that to try to diagnose what is going on.

I am not familar with that specific cable company's operations, but did have similar problems when swapping out my cable modem - is that specific cable modem unit the one that successfully works with the linksys - i.e., you are only swapping in the pix for the linksys? Does telewest do any authentication - pppoe, etc?

New Member

Re: PIX501 with Telewest Blueyonder DSL.

Hi

Thanks for your reply. I wasn't familiar with the capture command so I will give that a go. I am running 6.3(1).

It is the same cable modem that works with my Linksys and also a PC NIC so I don't think it is faulty. I have tried swapping the cable and initial tests prove that Ethernet0 of the PIX is physically fine.

The cable modem presents as Ethernet without pppoe so I can literally plug in any Ethernet interface and providing I have registered it's MAC with Telewest it should receive a DHCP supplied address. There isn't any user authentication taking place.

Telewest Blueyonder Tech Support won't provide any support over this so any further suggestions from you guys would be appreciated.

Cheers

Max...

New Member

Re: PIX501 with Telewest Blueyonder DSL.

Here is a sample of the debugs with debug dhcpc packet, debug dhcpc error and debug dhcpc detail. Please can anyone interpret these for me?

DHCP: QScan: Timed out Selecting state

DHCP: QScan: Purging entry

DHCP: deleting entry a54694 0.0.0.0 from list

Temp IP addr: 0.0.0.0 for peer on Interface: unknown

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 8 Purging

DHCP transaction id: 0x239C929

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

No timer running

Retry count: 0 Client-ID:

DHCP command failed

DHCP client msg received, fip=10.153.64.1, fport=67

DHCP: Received a BOOTREP pkt Not for us..: xid: 0x4B44

DHCP: allocate request

DHCP get addr: existing ip lease str = 0x9e74bc

DHCP: zapping entry in DHC_PURGING state for outside

DHCP: new entry. add to queue

DHCP: new ip lease str = 0x9e765c

DHCP: SDiscover attempt # 1 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23ACDC5

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 1 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: QScan: Purging entry

DHCP: deleting entry 9e731c 0.0.0.0 from list

Temp IP addr: 0.0.0.0 for peer on Interface: unknown

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 8 Purging

DHCP transaction id: 0x23A1057

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

No timer running

Retry count: 0 Client-ID:

....

DHCP: SDiscover attempt # 2 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23ACDC5

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 2 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: SDiscover attempt # 3 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23ACDC5

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 3 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: QScan: Timed out Selecting state

DHCP: allocate request

DHCP get addr: existing ip lease str = 0x9e765c

DHCP: zapping entry in DHC_PURGING state for outside

DHCP: new entry. add to queue

DHCP: new ip lease str = 0x9e731c

DHCP: SDiscover attempt # 1 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B1B3E

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 1 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: QScan: Purging entry

DHCP: deleting entry 9e717c 0.0.0.0 from list

Temp IP addr: 0.0.0.0 for peer on Interface: unknown

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 8 Purging

DHCP transaction id: 0x23A5F0C

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

No timer running

Retry count: 0 Client-ID:

....

DHCP: SDiscover attempt # 2 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B1B3E

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 2 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: SDiscover attempt # 3 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B1B3E

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 3 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: QScan: Timed out Selecting state

DHCP: allocate request

DHCP get addr: existing ip lease str = 0x9e731c

DHCP: zapping entry in DHC_PURGING state for outside

DHCP: new entry. add to queue

DHCP: new ip lease str = 0x9e717c

DHCP: SDiscover attempt # 1 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B4907

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 1 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: QScan: Purging entry

DHCP: deleting entry 9e74bc 0.0.0.0 from list

Temp IP addr: 0.0.0.0 for peer on Interface: unknown

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 8 Purging

DHCP transaction id: 0x23AA2F6

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

No timer running

Retry count: 0 Client-ID:

....

DHCP: SDiscover attempt # 2 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B4907

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 2 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: SDiscover attempt # 3 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B4907

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 3 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: QScan: Timed out Selecting state

DHCP: allocate request

DHCP get addr: existing ip lease str = 0x9e717c

DHCP: zapping entry in DHC_PURGING state for outside

DHCP: new entry. add to queue

DHCP: new ip lease str = 0x9e74bc

DHCP: SDiscover attempt # 1 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B83BB

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 1 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0....

DHCP: SDiscover attempt # 2 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B83BB

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 2 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: SDiscover attempt # 3 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23B83BB

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 3 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: QScan: Timed out Selecting state

DHCP: allocate request

DHCP get addr: existing ip lease str = 0x9e74bc

DHCP: zapping entry in DHC_PURGING state for outside

DHCP: new entry. add to queue

DHCP: new ip lease str = 0x9ea284

DHCP: SDiscover attempt # 1 for entry:

Temp IP addr: 0.0.0.0 for peer on Interface: outside

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 1 Selecting

DHCP transaction id: 0x23BC87D

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

Next timer fires after: 2 seconds

Retry count: 1 Client-ID: cisco-000d.bd3b.fb47-outside

DHCP: SDiscover: sending 273 byte length DHCP packet

DHCP: SDiscover 273 bytes

DHCP Broadcast to 255.255.255.255 from 0.0.0.0

DHCP: QScan: Purging entry

DHCP: deleting entry 9e765c 0.0.0.0 from list

Temp IP addr: 0.0.0.0 for peer on Interface: unknown

Temp sub net mask: 0.0.0.0

DHCP Lease server: 0.0.0.0, state: 8 Purging

DHCP transaction id: 0x23ACDC5

Lease: 0 secs, Renewal: 0 secs, Rebind: 0 secs

No timer running

Retry count: 0 Client-ID:

....

New Member

Re: PIX501 with Telewest Blueyonder DSL.

Max,

Try leaving the Surfboard switched off overnight and then getting an IP address from Blueyonder (after switching the Surfboard back on, of course!). I have set up a PIX running on the back of a Blueyonder cable connection in the past, so they do coexist.

New Member

Re: PIX501 with Telewest Blueyonder DSL.

Hi

Thanks a lot for your reply and clarifying this for me. I was beggining to worry about a compatibility issue.

I have actually tried that however I have swapped cables and done a write erase since then so I will give it another go.

Cheers

Max...

New Member

Re: PIX501 with Telewest Blueyonder DSL.

Chris (or anyone)

The 501 still isn't being assigned a DHCP address on the Outside when connected to the Motorola Surfboard. The retry is set to 4 and I get a row of dots and eventually "DHCP Failed".

I have performed a write erase and I can definitely confirm that Ethernet0's MAC address is registered with Blueyonder under Self Care.

I have tested Ethernet0 and it is fine. I have also tried various combinations of reboots can cables.

Any further comments/suggestions from anyone would be much appreciated.

Cheers

Max...

Gold

Re: PIX501 with Telewest Blueyonder DSL.

Max,

Can actually ping the DHCP server from a perimeter router and also, can you post your PIX and Primeter router config either here or to me at noc1@vodafone.net (please change real IP's and passwords). PS. You work for boxing orange don't you?

Thanks - Jay

New Member

Re: PIX501 with Telewest Blueyonder DSL.

Hi Jay

If I had a perimeter router that is one of the first things I would have tried :) Because I am plugging the PIX Outside into a Motorola Surfboard (cable modem) I am blind to whatever is beyond. In the debugs I am seing packets from address 10.153.64.1 which I assume is Blueyonder. Unfortunately I cannot ping out from the PIX because I cannot receive a DHCP assigned address.

PS: Yes? :)

Cheers

Max...

Gold

Re: PIX501 with Telewest Blueyonder DSL.

Max,

The bad news is that I can't reach that IP address (if it is the DHCP server of Blueyonder), here's the result:

NOC_AS0_Internet#ping 10.153.64.1

Type escape sequence to abort.

Sending 5, 100-byte ICMP Echos to 10.153.64.1, timeout is 2 seconds:

.....

Get hold of Blueyonder (if you can) and verify the IP address of the DHCP server!!

Thanks - Jay

New Member

Re: PIX501 with Telewest Blueyonder DSL.

Hi Jay

Yep, obviously it is RFC1918 and not routable. I assume it can only be reached from Blueyonder's network.

Even if I have the IP address of the DHCP server there is probably nothing I can do with it. I have fired off an Email to Blueyonder Tech Support but I aren't confident.

Cheers anyway

Max...

182
Views
0
Helpful
10
Replies
CreatePlease login to create content