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

PIX 501 v6.3(5) DHCP command failed

Hi, I am trying to use a PIX 501 to connect to wlreless modem to build up VPN tunnel. But somehow the PIX can't get the public IP from Wireless modem, always prompt 'DHCP command failed' Following is my config and debug dhcpc detail. From the debug, I can see a IP 10.220.140.178 is being offer to PIX from 10.0.0.138, but why PIX didn't take it? Any ideas?

Thanks. Leo

config

PIX Version 6.3(5)125
interface ethernet0 auto
interface ethernet1 100full
nameif ethernet0 outside security0
nameif ethernet1 inside security100
enable password I85IXnMW2YmMhKqe encrypted
passwd bumcm3CbfVFIW7Q0 encrypted
hostname AP8xxN0001
domain-name cmc.com
fixup protocol dns maximum-length 512
fixup protocol ftp 21
fixup protocol h323 h225 1720
fixup protocol h323 ras 1718-1719
fixup protocol http 80
fixup protocol rsh 514
fixup protocol rtsp 554
fixup protocol sip 5060
fixup protocol sip udp 5060
fixup protocol skinny 2000
fixup protocol smtp 25
fixup protocol sqlnet 1521
fixup protocol tftp 69
names        
pager lines 24
logging on
logging buffered notifications
mtu outside 1500
mtu inside 1500
ip address outside dhcp retry 5
ip address inside 10.150.192.1 255.255.224.0
ip audit info action alarm
ip audit attack action alarm
pdm history enable
arp timeout 14400
global (outside) 1 interface
nat (inside) 1 0.0.0.0 0.0.0.0 0 0
timeout xlate 3:00:00
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00
timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00
timeout sip-disconnect 0:02:00 sip-invite 0:03:00
timeout uauth 0:05:00 absolute
aaa-server TACACS+ protocol tacacs+
aaa-server TACACS+ max-failed-attempts 3
aaa-server TACACS+ deadtime 10
aaa-server RADIUS protocol radius
aaa-server RADIUS max-failed-attempts 3
aaa-server RADIUS deadtime 10
aaa-server LOCAL protocol local
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet 0.0.0.0 0.0.0.0 inside
telnet timeout 5
ssh 0.0.0.0 0.0.0.0 outside
ssh timeout 3
management-access inside
console timeout 0
terminal width 80
Cryptochecksum:8c753b16166c9ce6dcc06790862b7b9b
: end        
AP8xxN0001(config)#

debug dhcpc detail:

'DHCP Offer Message   Offered Address: 10.220.140.178
DHCP: Lease Seconds: 30
DHCP: Server ID Option: 10.0.0.138
DHCP: Scan: Message type: DHCP Offer
DHCP: Scan: Server ID Option: 10.0.0.138 = 8A00000A
DHCP: Scan: Lease Time: 30
DHCP: Scan: Subnet Address Option: 255.255.255.0
DHCP: Scan: Router Address Option: 10.220.140.178
DHCP: Scan: DNS Name Server Option: 139.130.4.4
DHCP: rcvd pkt source: 10.0.0.138,  destination:  10.220.140.178
   UDP  sport: 67,  dport: 68,  length: 282
   DHCP op: 0x2, htype: 0x1, hlen: 6, hops: 0
   DHCP server identifier: 10.0.0.138
        xid: 0x91D1C, secs: 0, flags: 0x0
        client: 0.0.0.0, your: 10.220.140.178
        srvr:   0.0.0.0, gw: 0.0.0.0
        options block length: 34

DHCP Offer Message   Offered Address: 10.220.140.178
DHCP: Lease Seconds: 30
DHCP: Server ID Option: 10.0.0.138
DHCP: QScan: Timed out Selecting state
DHCP get addr: existing ip lease str = 0xb483ec
DHCP: new ip lease str = 0xb5e064
DHCP: Scan: Message type: DHCP Offer
DHCP: Scan: Server ID Option: 10.0.0.138 = 8A00000A
DHCP: Scan: Lease Time: 30
DHCP: Scan: Subnet Address Option: 255.255.255.0
DHCP: Scan: Router Address Option: 10.220.140.178
DHCP: Scan: DNS Name Server Option: 139.130.4.4
DHCP: rcvd pkt source: 10.0.0.138,  destination:  10.220.140.178
   UDP  sport: 67,  dport: 68,  length: 282
   DHCP op: 0x2, htype: 0x1, hlen: 6, hops: 0
   DHCP server identifier: 10.0.0.138
        xid: 0x9553A, secs: 0, flags: 0x0
        client: 0.0.0.0, your: 10.220.140.178
        srvr:   0.0.0.0, gw: 0.0.0.0
        options block length: 34

DHCP Offer Message   Offered Address: 10.220.140.178
DHCP: Lease Seconds: 30
DHCP: Server ID Option: 10.0.0.138
DHCP: Scan: Message type: DHCP Offer
DHCP: Scan: Server ID Option: 10.0.0.138 = 8A00000A
DHCP: Scan: Lease Time: 30
DHCP: Scan: Subnet Address Option: 255.255.255.0
DHCP: Scan: Router Address Option: 10.220.140.178
DHCP: Scan: DNS Name Server Option: 139.130.4.4
DHCP: rcvd pkt source: 10.0.0.138,  destination:  10.220.140.178
   UDP  sport: 67,  dport: 68,  length: 282
   DHCP op: 0x2, htype: 0x1, hlen: 6, hops: 0
   DHCP server identifier: 10.0.0.138
        xid: 0x9553A, secs: 0, flags: 0x0
        client: 0.0.0.0, your: 10.220.140.178
        srvr:   0.0.0.0, gw: 0.0.0.0
        options block length: 34'

3 REPLIES
Cisco Employee

Re: PIX 501 v6.3(5) DHCP command failed

Try to shut and unshut the PIX ethernet0 interface:

interface ethernet0 auto shutdown

interface ethernet0 auto

And try to change the "ip address outside dhcp retry 5" to "ip address outside dhcp setroute".

Let us know how it goes.

Community Member

Re: PIX 501 v6.3(5) DHCP command failed

Hi halijenn

I tried your suggestions, but still no good. Is this a bug?

Thanks. Leo

Cisco Employee

Re: PIX 501 v6.3(5) DHCP command failed

Any reason why you are running interim release of 6.3.5(125)?

Last resort since it's not working anyway, have you tried to reload the PIX?

870
Views
0
Helpful
3
Replies
CreatePlease to create content