<?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: Lan based failover session key encryption for PIX in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/lan-based-failover-session-key-encryption-for-pix/m-p/750767#M1006936</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The failover configuration requires two identical security appliances connected to each other through a dedicated failover link and, optionally, a stateful failover link. The health of the active interfaces and units is monitored to determine if specific failover conditions are met. If those conditions are met, failover occurs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The security appliance supports two failover configurations, Active/Active Failover and Active/Standby Failover. Each failover configuration has its own method to determine and perform failover. With Active/Active Failover, both units can pass network traffic. This lets you configure load balancing on your network. Active/Active Failover is only available on units that run in multiple context mode. With Active/Standby Failover, only one unit passes traffic while the other unit waits in a standby state. Active/Standby Failover is available on units that run in either single or multiple context mode. Both failover configurations support stateful or stateless (regular) failover. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 23 Apr 2007 13:23:01 GMT</pubDate>
    <dc:creator>thomas.chen</dc:creator>
    <dc:date>2007-04-23T13:23:01Z</dc:date>
    <item>
      <title>Lan based failover session key encryption for PIX</title>
      <link>https://community.cisco.com/t5/network-security/lan-based-failover-session-key-encryption-for-pix/m-p/750766#M1006935</link>
      <description>&lt;P&gt;My suggestion for session key encryption for a lan based failover connection for the PIX is as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;A) Physically connect PIX interfaces to a workgroup amd or enterprise Catalyst 6509 switch, IOS 12.2(18) SXF and higher.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;B) Assign static IP addresses within the range of the primary and failover PIX units.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;C) Configure session key encryption on the workgroup switch and only allow TCP packet segments via IP protocol number 105/SCPS. Then deny all other TCP/IP segments. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The configurations should be as follows:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Company A 6509#show run &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;version 12.3&lt;/P&gt;&lt;P&gt;service timestamps debug datetime msec&lt;/P&gt;&lt;P&gt;service timestamps log datetime msec&lt;/P&gt;&lt;P&gt;no service password-encryption&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;hostname Company A 6509&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;boot-start-marker&lt;/P&gt;&lt;P&gt;boot-end-marker&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;enable password cisco&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;no aaa new-model&lt;/P&gt;&lt;P&gt;ip subnet-zero&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;no crypto isakmp enable&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;crypto ipsec transform-set encrypt-aes esp-aes esp-sha-hmac&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;crypto map pix failover 8 ipsec-manual &lt;/P&gt;&lt;P&gt; set peer 11.11.11.6&lt;/P&gt;&lt;P&gt; set session-key inbound esp 1001 cipher 1234abcd1234abcd authenticator 20 &lt;/P&gt;&lt;P&gt; set session-key outbound esp 1000 cipher abcd1234abcd1234 authenticator 20 &lt;/P&gt;&lt;P&gt; set transform-set encrypt-aes&lt;/P&gt;&lt;P&gt; match address 101&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;interface gi2/2&lt;/P&gt;&lt;P&gt;speed 100&lt;/P&gt;&lt;P&gt;duplex full&lt;/P&gt;&lt;P&gt;Description PIX failover interface Lan-Based access list applied to protocol 105 for SCPS&lt;/P&gt;&lt;P&gt;ip address 11.11.11.5 255.255.255.252&lt;/P&gt;&lt;P&gt;crypto map pix failover&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;ip http server&lt;/P&gt;&lt;P&gt;no ip http secure-server&lt;/P&gt;&lt;P&gt;ip classless&lt;/P&gt;&lt;P&gt;ip route 0.0.0.0 0.0.0.0 11.11.11.12&lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;access-list 101 permit ip host 11.11.11.5 host 11.11.11.6 eq 105&lt;/P&gt;&lt;P&gt;access-list 101 permit ip host 11.11.11.6 host 11.11.11.5 eq 105&lt;/P&gt;&lt;P&gt;access-list 101 deny ip any any &lt;/P&gt;&lt;P&gt;access-list 101 permit ip any any &lt;/P&gt;&lt;P&gt;!&lt;/P&gt;&lt;P&gt;line con 0&lt;/P&gt;&lt;P&gt;no login&lt;/P&gt;&lt;P&gt;line aux 0&lt;/P&gt;&lt;P&gt;no login&lt;/P&gt;&lt;P&gt;line vty 0 15&lt;/P&gt;&lt;P&gt;exec-timeout 300&lt;/P&gt;&lt;P&gt;transport input ssh&lt;/P&gt;&lt;P&gt;login&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If possible, try this on a home lab, then verify the results.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:01:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/lan-based-failover-session-key-encryption-for-pix/m-p/750766#M1006935</guid>
      <dc:creator>mwardinterpub</dc:creator>
      <dc:date>2019-03-11T10:01:09Z</dc:date>
    </item>
    <item>
      <title>Re: Lan based failover session key encryption for PIX</title>
      <link>https://community.cisco.com/t5/network-security/lan-based-failover-session-key-encryption-for-pix/m-p/750767#M1006936</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The failover configuration requires two identical security appliances connected to each other through a dedicated failover link and, optionally, a stateful failover link. The health of the active interfaces and units is monitored to determine if specific failover conditions are met. If those conditions are met, failover occurs. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The security appliance supports two failover configurations, Active/Active Failover and Active/Standby Failover. Each failover configuration has its own method to determine and perform failover. With Active/Active Failover, both units can pass network traffic. This lets you configure load balancing on your network. Active/Active Failover is only available on units that run in multiple context mode. With Active/Standby Failover, only one unit passes traffic while the other unit waits in a standby state. Active/Standby Failover is available on units that run in either single or multiple context mode. Both failover configurations support stateful or stateless (regular) failover. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/hw/vpndevc/ps2030/products_configuration_example09186a00807dac5f.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 23 Apr 2007 13:23:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/lan-based-failover-session-key-encryption-for-pix/m-p/750767#M1006936</guid>
      <dc:creator>thomas.chen</dc:creator>
      <dc:date>2007-04-23T13:23:01Z</dc:date>
    </item>
  </channel>
</rss>

