05-08-2007 09:33 AM - edited 03-11-2019 03:10 AM
Hello,
I have a PIX 515E FO and it is st the factory defaults. I simply assigned an IP Address to the inside interface. I am trying to upgrade to 7.0, then 7.1(1), which is the version my UR is on. I can't even ping any host on the same subnet, I am totally lost as to why this is happening? I have the correct subnet mask and ip address scheme, yet i get no responses from any host i try to ping. I have tried hooking up a cross over to a laptop and even that is unsuccessful. I thought that maybe I had a defective unit so I RMA'd it, but the new unit is displaying the same behavior. I am a afraid that I am missing something simple?
Here is my show run:
PIX Version 6.3(5)
interface ethernet0 auto shutdown
interface ethernet1 100full
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 xxx
passwd xxx
hostname pixfirewall
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 5060carrier, 0 no carrier
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
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 10.18.1.18 255.255.0.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
no failover
failover timeout 0:00:00
o 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
no snmp-server location
no snmp-server contact
snmp-server community public
no snmp-server enable traps
floodguard enable
telnet timeout 5
ssh timeout 5
console timeout 0
terminal width 80
Cryptochecksum:xxx
: end
pixfirewall(config)# ping 10.18.0.1
10.18.0.1 NO response received -- 1000ms
10.18.0.1 NO response received -- 1000ms
10.18.0.1 NO response received -- 1000ms
pixfirewall(config)#
pixfirewall(config)# show int e1
interface ethernet1 "inside" is up, line protocol is up
Hardware is i82559 ethernet, address is 000a.b7bc.4bdb
IP address 10.18.1.18, subnet mask 255.255.0.0
MTU 1500 bytes, BW 100000 Kbit full duplex
1626 packets input, 155696 bytes, 0 no buffer
Received 1632 broadcasts, 0 runts, 0 giants
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 babbles, 0 late collisions, 0 deferred
0 lost carrier, 0 no carrier
input queue (curr/max blocks): hardware (128/128) software (0/1)
output queue (curr/max blocks): hardware (0/0) software (0/0)
This PIX has a Failover Only (FO) license.
Thanks for any help.
05-08-2007 12:06 PM
The issue here is the FO license. A PIX with FO license cannot work in standalone mode. This is the reason why you cant ping its interfaces or ping hosts from this PIX.
You may try enabling failover on PIX and then try doing upgrade.
ip address inside 10.18.1.18 255.255.0.0
failover ip address inside 10.18.1.19
failover
Wait for few secs, now this PIX should assume "Active" role and you should be able to ping the interface. Now try the upgrade.
Hope this helps.
Regards,
Vibhor.
05-10-2007 08:36 AM
Thanks so much, this was perfect. I appreciate your assistance greatly.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide