<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: Cisco CSM URL Redirect</title>
	<atom:link href="http://blog.super-networking.net/2006/07/cisco-csm-url-redirect/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.super-networking.net/2006/07/cisco-csm-url-redirect/</link>
	<description></description>
	<pubDate>Sun, 20 May 2012 14:51:47 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: chris.super</title>
		<link>http://blog.super-networking.net/2006/07/cisco-csm-url-redirect/comment-page-1/#comment-20131</link>
		<dc:creator>chris.super</dc:creator>
		<pubDate>Thu, 05 Jul 2007 12:57:42 +0000</pubDate>
		<guid isPermaLink="false">http://blog.super-networking.net/?p=48#comment-20131</guid>
		<description>If you want to do the whole site say for a backup if your webservers fail use the following:

vserver MYSITE
  virtual 1.1.1.1 tcp www
  serverfarm MYSITE-SF backup FAILOVER 
  persistent rebalance
  inservice

serverfarm FAILOVER
  nat server
  no nat client
  redirect-vserver FL-OVER
   webhost relocation https://www.mysite.com/things/stuff.html
   inservice

If you want all traffic to always redirect make the FAILOVER serverfarm the main one under your vserver instead of the backup. Names I came up with don't matter except to remember that the redirect-vserver name has to be different than the serverfarm it is in.

If all traffic is being redirected anyway you might what to setup a redirect on your webserver through IIS instead of in the CSM. Hope this helps, if you have more questions comment.</description>
		<content:encoded><![CDATA[<p>If you want to do the whole site say for a backup if your webservers fail use the following:</p>
<p>vserver MYSITE<br />
  virtual 1.1.1.1 tcp www<br />
  serverfarm MYSITE-SF backup FAILOVER<br />
  persistent rebalance<br />
  inservice</p>
<p>serverfarm FAILOVER<br />
  nat server<br />
  no nat client<br />
  redirect-vserver FL-OVER<br />
   webhost relocation <a href="https://www.mysite.com/things/stuff.html" rel="nofollow">https://www.mysite.com/things/stuff.html</a><br />
   inservice</p>
<p>If you want all traffic to always redirect make the FAILOVER serverfarm the main one under your vserver instead of the backup. Names I came up with don&#8217;t matter except to remember that the redirect-vserver name has to be different than the serverfarm it is in.</p>
<p>If all traffic is being redirected anyway you might what to setup a redirect on your webserver through IIS instead of in the CSM. Hope this helps, if you have more questions comment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Chad</title>
		<link>http://blog.super-networking.net/2006/07/cisco-csm-url-redirect/comment-page-1/#comment-19871</link>
		<dc:creator>Chad</dc:creator>
		<pubDate>Tue, 03 Jul 2007 21:31:36 +0000</pubDate>
		<guid isPermaLink="false">http://blog.super-networking.net/?p=48#comment-19871</guid>
		<description>Assuming that the vserver for http and https is working and the real servers respond accordingly, how would I redirect all traffic destined for "http://www.mysite.com" to "https://www.mysite.com/things/stuff.html"?? 

I have tried several variations of your example and can not seem to make it work. Since your documentation is more intuative than Cisco's, I figured I would ask you first.</description>
		<content:encoded><![CDATA[<p>Assuming that the vserver for http and https is working and the real servers respond accordingly, how would I redirect all traffic destined for &#8220;http://www.mysite.com&#8221; to &#8220;https://www.mysite.com/things/stuff.html&#8221;?? </p>
<p>I have tried several variations of your example and can not seem to make it work. Since your documentation is more intuative than Cisco&#8217;s, I figured I would ask you first.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

