<?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 Does CSS have any Redundancy Tracking? in Application Networking</title>
    <link>https://community.cisco.com/t5/application-networking/does-css-have-any-redundancy-tracking/m-p/9135#M56</link>
    <description>&lt;P&gt;I have 2 CSS 11500 switches. Each CSS has an interface connecting to "outside" routers and another connecting to "inside" where the web servers resided. Both interfaces are running VRRP. CSS1 is the master of two VLANs. CSS2 is the backup. If the "inside" interface failed in CSS1, only the "inside" interface of CSS2 become the Master. The "outside" interface of CSS1 is still the Master. From what I understand, VRRP is similar to HSRP. How do I make the CSS1's "outside" interface failover? In other words, I want CSS2 to be the Master of both interfaces if either interfaces of CSS1 failed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does CSS have standby track like Cisco router?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is sample config of CSS1 and CSS2&lt;/P&gt;&lt;P&gt;CSS1:&lt;/P&gt;&lt;P&gt;circuit VLAN261&lt;/P&gt;&lt;P&gt;  ip address 170.116.16.3 255.255.255.0 &amp;lt;- outside&lt;/P&gt;&lt;P&gt;    ip virtual-router 61 priority 110 preempt &lt;/P&gt;&lt;P&gt;    ip redundant-interface 61 170.116.16.1 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 61 170.116.16.21 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 61 170.116.16.22 &lt;/P&gt;&lt;P&gt;circuit VLAN265&lt;/P&gt;&lt;P&gt;  ip address 10.45.176.3 255.255.254.0 &amp;lt;- inside&lt;/P&gt;&lt;P&gt;    ip virtual-router 65 priority 110 preempt &lt;/P&gt;&lt;P&gt;    ip redundant-interface 65 10.45.176.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSS2:&lt;/P&gt;&lt;P&gt;circuit VLAN261&lt;/P&gt;&lt;P&gt;  ip address 170.116.16.4 255.255.255.0 &amp;lt;- outside&lt;/P&gt;&lt;P&gt;    ip virtual-router 61 priority 90 preempt &lt;/P&gt;&lt;P&gt;    ip redundant-interface 61 170.116.16.1 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 61 170.116.16.21 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 61 170.116.16.22 &lt;/P&gt;&lt;P&gt;circuit VLAN265&lt;/P&gt;&lt;P&gt;  ip address 10.45.176.4 255.255.254.0 &amp;lt;- inside&lt;/P&gt;&lt;P&gt;    ip virtual-router 65 priority 90 preempt &lt;/P&gt;&lt;P&gt;    ip redundant-interface 65 10.45.176.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brad&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:bradleywong@yahoo.com"&gt;bradleywong@yahoo.com&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Mon, 25 Jun 2001 18:25:07 GMT</pubDate>
    <dc:creator>bradley.wong</dc:creator>
    <dc:date>2001-06-25T18:25:07Z</dc:date>
    <item>
      <title>Does CSS have any Redundancy Tracking?</title>
      <link>https://community.cisco.com/t5/application-networking/does-css-have-any-redundancy-tracking/m-p/9135#M56</link>
      <description>&lt;P&gt;I have 2 CSS 11500 switches. Each CSS has an interface connecting to "outside" routers and another connecting to "inside" where the web servers resided. Both interfaces are running VRRP. CSS1 is the master of two VLANs. CSS2 is the backup. If the "inside" interface failed in CSS1, only the "inside" interface of CSS2 become the Master. The "outside" interface of CSS1 is still the Master. From what I understand, VRRP is similar to HSRP. How do I make the CSS1's "outside" interface failover? In other words, I want CSS2 to be the Master of both interfaces if either interfaces of CSS1 failed. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Does CSS have standby track like Cisco router?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is sample config of CSS1 and CSS2&lt;/P&gt;&lt;P&gt;CSS1:&lt;/P&gt;&lt;P&gt;circuit VLAN261&lt;/P&gt;&lt;P&gt;  ip address 170.116.16.3 255.255.255.0 &amp;lt;- outside&lt;/P&gt;&lt;P&gt;    ip virtual-router 61 priority 110 preempt &lt;/P&gt;&lt;P&gt;    ip redundant-interface 61 170.116.16.1 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 61 170.116.16.21 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 61 170.116.16.22 &lt;/P&gt;&lt;P&gt;circuit VLAN265&lt;/P&gt;&lt;P&gt;  ip address 10.45.176.3 255.255.254.0 &amp;lt;- inside&lt;/P&gt;&lt;P&gt;    ip virtual-router 65 priority 110 preempt &lt;/P&gt;&lt;P&gt;    ip redundant-interface 65 10.45.176.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;CSS2:&lt;/P&gt;&lt;P&gt;circuit VLAN261&lt;/P&gt;&lt;P&gt;  ip address 170.116.16.4 255.255.255.0 &amp;lt;- outside&lt;/P&gt;&lt;P&gt;    ip virtual-router 61 priority 90 preempt &lt;/P&gt;&lt;P&gt;    ip redundant-interface 61 170.116.16.1 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 61 170.116.16.21 &lt;/P&gt;&lt;P&gt;    ip redundant-vip 61 170.116.16.22 &lt;/P&gt;&lt;P&gt;circuit VLAN265&lt;/P&gt;&lt;P&gt;  ip address 10.45.176.4 255.255.254.0 &amp;lt;- inside&lt;/P&gt;&lt;P&gt;    ip virtual-router 65 priority 90 preempt &lt;/P&gt;&lt;P&gt;    ip redundant-interface 65 10.45.176.1 &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brad&lt;/P&gt;&lt;P&gt;&lt;A href="mailto:bradleywong@yahoo.com"&gt;bradleywong@yahoo.com&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 25 Jun 2001 18:25:07 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/does-css-have-any-redundancy-tracking/m-p/9135#M56</guid>
      <dc:creator>bradley.wong</dc:creator>
      <dc:date>2001-06-25T18:25:07Z</dc:date>
    </item>
    <item>
      <title>Re: Does CSS have any Redundancy Tracking?</title>
      <link>https://community.cisco.com/t5/application-networking/does-css-have-any-redundancy-tracking/m-p/9136#M57</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;After digging through Cisco website, it can be done using ip critical service and type redundancy-up. Here is the link:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/advcfggd/vipredun.htm#29885" target="_blank"&gt;http://www.cisco.com/univercd/cc/td/doc/product/webscale/css/advcfggd/vipredun.htm#29885&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 28 Jun 2001 19:31:59 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/does-css-have-any-redundancy-tracking/m-p/9136#M57</guid>
      <dc:creator>bradleywong</dc:creator>
      <dc:date>2001-06-28T19:31:59Z</dc:date>
    </item>
    <item>
      <title>Re: Does CSS have any Redundancy Tracking?</title>
      <link>https://community.cisco.com/t5/application-networking/does-css-have-any-redundancy-tracking/m-p/9137#M58</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since you set up redundant VIPs, the box should fail those VIPs to the other box if it loses communication to the services.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You should also track the upstream connections. Do this by specifying your upstream router or firewall as a service and using the "type redundancy-up" command. Then use the "ip critical service" command under your virtual router section to specify the upstream device.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tony&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2001 12:19:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/application-networking/does-css-have-any-redundancy-tracking/m-p/9137#M58</guid>
      <dc:creator>kwon47</dc:creator>
      <dc:date>2001-07-11T12:19:26Z</dc:date>
    </item>
  </channel>
</rss>

