<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Cannot ping inside interface of PIX515 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698208#M1027751</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had to force it by type in "failover active" command then it start to repond and able to access the internet but if I reboot the pix it goes back to the same problem. Please  help. Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 27 Jan 2007 22:47:59 GMT</pubDate>
    <dc:creator>tung</dc:creator>
    <dc:date>2007-01-27T22:47:59Z</dc:date>
    <item>
      <title>Cannot ping inside interface of PIX515</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698207#M1027750</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is a brand new settup. For some reason I cannot access the inside interface not even ping. Here is a basic config. Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PIX Version 6.3(5)&lt;/P&gt;&lt;P&gt;interface ethernet0 auto shutdown&lt;/P&gt;&lt;P&gt;interface ethernet1 100full&lt;/P&gt;&lt;P&gt;interface ethernet2 auto shutdown&lt;/P&gt;&lt;P&gt;nameif ethernet0 outside security0&lt;/P&gt;&lt;P&gt;nameif ethernet1 inside security100&lt;/P&gt;&lt;P&gt;nameif ethernet2 dmz security4&lt;/P&gt;&lt;P&gt;enable password xxx&lt;/P&gt;&lt;P&gt;passwd xxx&lt;/P&gt;&lt;P&gt;hostname BEETEEPIX515&lt;/P&gt;&lt;P&gt;domain-name beetee.local&lt;/P&gt;&lt;P&gt;fixup protocol dns maximum-length 512&lt;/P&gt;&lt;P&gt;fixup protocol ftp 21&lt;/P&gt;&lt;P&gt;fixup protocol h323 h225 1720&lt;/P&gt;&lt;P&gt;fixup protocol h323 ras 1718-1719&lt;/P&gt;&lt;P&gt;fixup protocol http 80&lt;/P&gt;&lt;P&gt;fixup protocol rsh 514&lt;/P&gt;&lt;P&gt;fixup protocol rtsp 554&lt;/P&gt;&lt;P&gt;fixup protocol sip 5060&lt;/P&gt;&lt;P&gt;fixup protocol sip udp 5060&lt;/P&gt;&lt;P&gt;fixup protocol skinny 2000&lt;/P&gt;&lt;P&gt;fixup protocol smtp 25&lt;/P&gt;&lt;P&gt;fixup protocol sqlnet 1521&lt;/P&gt;&lt;P&gt;fixup protocol tftp 69&lt;/P&gt;&lt;P&gt;names&lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;icmp permit any echo inside&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;mtu dmz 1500&lt;/P&gt;&lt;P&gt;no ip address outside&lt;/P&gt;&lt;P&gt;ip address inside 172.22.14.253 255.255.255.0&lt;/P&gt;&lt;P&gt;no ip address dmz&lt;/P&gt;&lt;P&gt;ip audit info action alarm&lt;/P&gt;&lt;P&gt;ip audit attack action alarm&lt;/P&gt;&lt;P&gt;no failover&lt;/P&gt;&lt;P&gt;failover timeout 0:00:00&lt;/P&gt;&lt;P&gt;failover poll 15&lt;/P&gt;&lt;P&gt;no failover ip address outside&lt;/P&gt;&lt;P&gt;no failover ip address inside&lt;/P&gt;&lt;P&gt;no failover ip address dmz&lt;/P&gt;&lt;P&gt;pdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;timeout xlate 3:00:00&lt;/P&gt;&lt;P&gt;timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 rpc 0:10:00 h225 1:00:00&lt;/P&gt;&lt;P&gt;timeout h323 0:05:00 mgcp 0:05:00 sip 0:30:00 sip_media 0:02:00&lt;/P&gt;&lt;P&gt;timeout sip-disconnect 0:02:00 sip-invite 0:03:00&lt;/P&gt;&lt;P&gt;timeout uauth 0:05:00 absolute&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ protocol tacacs+&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ max-failed-attempts 3&lt;/P&gt;&lt;P&gt;aaa-server TACACS+ deadtime 10&lt;/P&gt;&lt;P&gt;aaa-server RADIUS protocol radius&lt;/P&gt;&lt;P&gt;aaa-server RADIUS max-failed-attempts 3&lt;/P&gt;&lt;P&gt;aaa-server RADIUS deadtime 10&lt;/P&gt;&lt;P&gt;aaa-server LOCAL protocol local&lt;/P&gt;&lt;P&gt;no snmp-server location&lt;/P&gt;&lt;P&gt;no snmp-server contact&lt;/P&gt;&lt;P&gt;snmp-server community public&lt;/P&gt;&lt;P&gt;no snmp-server enable traps&lt;/P&gt;&lt;P&gt;floodguard enable&lt;/P&gt;&lt;P&gt;telnet timeout 5&lt;/P&gt;&lt;P&gt;ssh timeout 5&lt;/P&gt;&lt;P&gt;console timeout 0&lt;/P&gt;&lt;P&gt;terminal width 80&lt;/P&gt;&lt;P&gt;Cryptochecksum:xxx&lt;/P&gt;&lt;P&gt;: end&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 09:25:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698207#M1027750</guid>
      <dc:creator>tung</dc:creator>
      <dc:date>2019-03-11T09:25:21Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot ping inside interface of PIX515</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698208#M1027751</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I had to force it by type in "failover active" command then it start to repond and able to access the internet but if I reboot the pix it goes back to the same problem. Please  help. Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 27 Jan 2007 22:47:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698208#M1027751</guid>
      <dc:creator>tung</dc:creator>
      <dc:date>2007-01-27T22:47:59Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot ping inside interface of PIX515</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698209#M1027757</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Tung, &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Are you sure you have the synchronization going fine between the active and failover? do you allow ping on the failover? Basically, when you reboot it switches to the failover unit but you need to make sure that the IP address on the failover unit is the IP you are pinging.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In your case, when you reboot, ping the the failover IP and it should respond to you!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards, &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 28 Jan 2007 05:49:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698209#M1027757</guid>
      <dc:creator>oabduo983</dc:creator>
      <dc:date>2007-01-28T05:49:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot ping inside interface of PIX515</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698210#M1027760</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Is that mean I have to assign an IP for the failover interface? I would like to disable this failover feature because this is the only PIX we have. We don't have any failover or standby. Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 29 Jan 2007 04:43:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698210#M1027760</guid>
      <dc:creator>tung</dc:creator>
      <dc:date>2007-01-29T04:43:34Z</dc:date>
    </item>
    <item>
      <title>Re: Cannot ping inside interface of PIX515</title>
      <link>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698211#M1027764</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes, this is correct. You will have to remove failover configuration. But I don't see any configuration for failover. What license fo you have? could you please send show version of your firewall?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards, &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 30 Jan 2007 03:12:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/cannot-ping-inside-interface-of-pix515/m-p/698211#M1027764</guid>
      <dc:creator>oabduo983</dc:creator>
      <dc:date>2007-01-30T03:12:29Z</dc:date>
    </item>
  </channel>
</rss>

