I'v just got a new 515E PIX, 6 interfaces, Version 6.3(5).
I can't carry on any task with my PIX because the most simple operation is impossible: I can't ping the inside interface or from PIX any other host belonging to th same subnet. Interface is up and running, directly connected to a switch, icmp is enable on inside...
Please, anyone of you could give me an help?
Solved! Go to Solution.
Are you trying to ping the inside interface IP of the PIX from an XP box? If so, then make sure that the XP firewall is disabled.
Also, from the PIX can you issue: sho arp this should indicate if the PIX is picking up the internal client IP/MAC addresses, you can also try to ping the directly connected clients from the PIX see if you get a reply.
What sort of cable are you using to connect the PIX inside interface to the switch, is it straight through or cross-over??
It would also be good to see you pix config, if you do post it here please make sure to take out any sensitive info.
Let me know how you get on.
many thanks for your prompt reply.
At the end of the message you can find the entire configuration.
Answering your question:
I'm trying from XP , fw disabled
from PIX side is the same story, no ping at all, but I can see XP boxes' arp addresses typing sho arp
I'm using straight cables and a switch
PIX Version 6.3(5)
interface ethernet0 auto
interface ethernet1 auto
interface ethernet2 auto shutdown
interface ethernet3 auto shutdown
interface ethernet4 auto shutdown
interface ethernet5 auto shutdown
nameif ethernet0 outside security0
nameif ethernet1 inside security100
nameif ethernet2 intf2 security4
nameif ethernet3 intf3 security6
nameif ethernet4 intf4 security8
nameif ethernet5 intf5 security10
enable password 8Ry2YjIyt7RRXU24 encrypted
passwd 2KFQnbNIdI.2KYOU encrypted
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
pager lines 24
icmp permit any inside
mtu outside 1500
mtu inside 1500
mtu intf2 1500
mtu intf3 1500
mtu intf4 1500
mtu intf5 1500
no ip address outside
ip address inside 192.168.1.1 255.255.255.0
no ip address intf2
no ip address intf3
no ip address intf4
no ip address intf5
ip audit info action alarm
ip audit attack action alarm
failover timeout 0:00:00
failover poll 15
no failover ip address outside
no failover ip address inside
no failover ip address intf2
no failover ip address intf3
no failover ip address intf4
no failover ip address intf5
pdm history enable
arp timeout 14400
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
http server enable
http 192.168.1.48 255.255.255.255 inside
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
Mmmm... So the PIX is seeing IP/MAC but you don't get reply from clients when you ping from the PIX! What happens if you connect the inside interface cable (using a cross-over) directly into a stand alone PC or laptop NIC - can you now ping the inside interface IP of the PIX and vice-versa.
Let me know -
do "de ic t" on the pix. the output of this debug would provide more insight related to the issue.
4483: ICMP echo request (len 32 id 2 seq 25088)
4484: ICMP echo reply (len 32 id 2 seq 25088)
4493: ICMP echo request (len 32 id 2 seq 25344)
4494: ICMP echo reply (len 32 id 2 seq 25344)
4497: ICMP echo request (len 32 id 2 seq 25600)
4498: ICMP echo reply (len 32 id 2 seq 25600)
4499: ICMP echo request (len 32 id 2 seq 25856)
4500: ICMP echo reply (len 32 id 2 seq 25856)
Alberto, not really related to your question here but in looking at your int configs i noticed you have it set to auto. i believe it is better to specify 100full or what have you based on your switchport settings. also, ssh is safer then telnet. just a suggestion. take care.
PIX wasn't running because Failover License has been loaded but failover wasn't enable.
I would like use the PIX as standalone machine and not in failover configuration, but is this possible?
In this condition, the following warning appears:
" This machine is licensed as a secondary failover only unit.
This machine will reboot at 24 hours intervals in its current state. "
How can I do to avoid this behaviour?
Any other features could be compromized by this current state?
Thanks to all of you.
It is true that you can't use this as standalone in a production environment ( or shouldn't ). If you are using it for a lab environment, just enable failover. The PIX will not be able to establish communication with a fully licensed Pix so it will automatically become active. It will reboot every 24 hours, but for a lab environment, it's not that big of a deal.