<?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 NAT on a css using VIP/Interface redundancy in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354168#M5941</link>
    <description>&lt;P&gt;I have two css-11151's set up using VIP and&lt;/P&gt;&lt;P&gt;interface redundancy in an active/backup&lt;/P&gt;&lt;P&gt;configuration.  We are using source groups&lt;/P&gt;&lt;P&gt;to NAT all outgoing connections to a single&lt;/P&gt;&lt;P&gt;ip.  Config looks like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Primary css:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;group nat-clients&lt;/P&gt;&lt;P&gt; vip address 192.168.1.10&lt;/P&gt;&lt;P&gt; active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clause 50 permit any 192.168.100.0 255.255.255.0 destination any sourcegroup nat-clients&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Secondary css:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;group nat-clients&lt;/P&gt;&lt;P&gt; vip address 192.168.1.10&lt;/P&gt;&lt;P&gt; active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clause 50 permit any 192.168.100.0 255.255.255.0 destination any sourcegroup nat-clients&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, is there a way to make&lt;/P&gt;&lt;P&gt;the source groups redundant?  I am not&lt;/P&gt;&lt;P&gt;allowed to unless there is a content&lt;/P&gt;&lt;P&gt;rule associated with the ip used in the&lt;/P&gt;&lt;P&gt;source group.  Doing a "sh group" on each&lt;/P&gt;&lt;P&gt;css shows that both groups are active/not&lt;/P&gt;&lt;P&gt;redundant. On occasion I will see duplicate&lt;/P&gt;&lt;P&gt;ip address messages in the logs but NAT works regardless.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;-Dan&lt;/P&gt;</description>
    <pubDate>Thu, 06 Jan 2005 16:29:24 GMT</pubDate>
    <dc:creator>dbjelf</dc:creator>
    <dc:date>2005-01-06T16:29:24Z</dc:date>
    <item>
      <title>NAT on a css using VIP/Interface redundancy</title>
      <link>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354168#M5941</link>
      <description>&lt;P&gt;I have two css-11151's set up using VIP and&lt;/P&gt;&lt;P&gt;interface redundancy in an active/backup&lt;/P&gt;&lt;P&gt;configuration.  We are using source groups&lt;/P&gt;&lt;P&gt;to NAT all outgoing connections to a single&lt;/P&gt;&lt;P&gt;ip.  Config looks like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Primary css:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;group nat-clients&lt;/P&gt;&lt;P&gt; vip address 192.168.1.10&lt;/P&gt;&lt;P&gt; active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clause 50 permit any 192.168.100.0 255.255.255.0 destination any sourcegroup nat-clients&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Secondary css:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;group nat-clients&lt;/P&gt;&lt;P&gt; vip address 192.168.1.10&lt;/P&gt;&lt;P&gt; active&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;clause 50 permit any 192.168.100.0 255.255.255.0 destination any sourcegroup nat-clients&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My question is, is there a way to make&lt;/P&gt;&lt;P&gt;the source groups redundant?  I am not&lt;/P&gt;&lt;P&gt;allowed to unless there is a content&lt;/P&gt;&lt;P&gt;rule associated with the ip used in the&lt;/P&gt;&lt;P&gt;source group.  Doing a "sh group" on each&lt;/P&gt;&lt;P&gt;css shows that both groups are active/not&lt;/P&gt;&lt;P&gt;redundant. On occasion I will see duplicate&lt;/P&gt;&lt;P&gt;ip address messages in the logs but NAT works regardless.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks &lt;/P&gt;&lt;P&gt;-Dan&lt;/P&gt;</description>
      <pubDate>Thu, 06 Jan 2005 16:29:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354168#M5941</guid>
      <dc:creator>dbjelf</dc:creator>
      <dc:date>2005-01-06T16:29:24Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on a css using VIP/Interface redundancy</title>
      <link>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354169#M5942</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Dan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I believe you can.&lt;/P&gt;&lt;P&gt;Just configure an 'ip redudant-vip XX 192.168.1.10' under the appropriate circuit.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Let me know if that does not work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Gilles.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 14:11:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354169#M5942</guid>
      <dc:creator>Gilles Dufour</dc:creator>
      <dc:date>2005-01-07T14:11:23Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on a css using VIP/Interface redundancy</title>
      <link>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354170#M5943</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Gilles, when I do 'ip redudant-vip XX 192.168.1.10'  I get this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;%% Could not find content rule for specified VIP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 14:19:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354170#M5943</guid>
      <dc:creator>dbjelf</dc:creator>
      <dc:date>2005-01-07T14:19:09Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on a css using VIP/Interface redundancy</title>
      <link>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354171#M5944</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Dan,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What version of WebNS are you running?  This looks like bug id CSCdz49395.  I was able to ge this working on 7.10 b305:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSS11506# sh run&lt;/P&gt;&lt;P&gt;!Generated on 01/07/2005 08:27:39&lt;/P&gt;&lt;P&gt;!Active version: sg0710305&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;configure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!************************** CIRCUIT **************************&lt;/P&gt;&lt;P&gt;circuit VLAN1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  ip address 1.1.1.2 255.255.255.0 &lt;/P&gt;&lt;P&gt;    ip virtual-router 1 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 1 1.1.1.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;!*************************** GROUP ***************************&lt;/P&gt;&lt;P&gt;group TEST &lt;/P&gt;&lt;P&gt;  vip address 1.1.1.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSS11506# &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;~Zach&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 15:31:38 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354171#M5944</guid>
      <dc:creator>seilsz</dc:creator>
      <dc:date>2005-01-07T15:31:38Z</dc:date>
    </item>
    <item>
      <title>Re: NAT on a css using VIP/Interface redundancy</title>
      <link>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354172#M5945</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Ooh thanks Zach.  That looks like my problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Dan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 07 Jan 2005 21:41:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/nat-on-a-css-using-vip-interface-redundancy/m-p/354172#M5945</guid>
      <dc:creator>dbjelf</dc:creator>
      <dc:date>2005-01-07T21:41:46Z</dc:date>
    </item>
  </channel>
</rss>

