<\/span><\/h4>\n(config) # server real-name rs1 10.10.10.201 \n(config-rs-rs1) # port http group-id 10 10 \n(config-rs-rs1) # exit<\/p>\n
(config) # server real-name rs1 10.10.10.202 \n(config-rs-rs2) # port http group-id 10 10 \n(config-rs-rs2) # exit<\/p>\n
As group ids are sqencial you have to speficy the groups that it will be a member of. If you you only want it to be group 109 then you have to spefcy that it will be in group 10 through to group 10<\/p>\n
Configure Server ID`s<\/strong><\/p>\n(config) # server real-name rs1 10.10.10.201 \n(config-rs-rs1) # port http server-id 1024 \n(config-rs-rs1) # exit<\/p>\n
(config) # server real-name rs1 10.10.10.202 \n(config-rs-rs2) # port http group-id 1025 \n(config-rs-rs2) # exit<\/p>\n
<\/span>Create a Policy<\/strong><\/span><\/h4>\nNext create a policy that defines the action that is taken when the rule is matched.<\/p>\n
(config)# csw-policy myCookie \n(config-csw-myCookie)#<\/p>\n
Within this example we take 3 actions. They are :<\/p>\n
Persist<\/strong> – if rule 1 is matched then send (persist) to server<\/p>\n(config-csw-myCookie)# match r1 persist offset 0 length 3 group-or-server-id<\/p>\n
Forward<\/strong> – if we dont match against that rule we will forward to group 10<\/p>\n(config-csw-myCookie)# default forward 10<\/p>\n
Rewite<\/strong> – if i dont see the cookie I will insert it<\/p>\n(config-csw-myCookie)# default rewite insert-cookie<\/p>\n
<\/span>Define CSW Rule<\/strong><\/span><\/h4>\nNext we define a content switching rule. This rule spefies which content to match.<\/p>\n
(config)# csw-rule r1 header “cookie” search “ServerID”<\/p>\n
<\/span>Assign to Virtual Server<\/strong><\/span><\/h4>\n(config) # server virtual cookieVIP 2.1.1.1 \n(config-vs-cookieVIP) # port http \n(config-vs-cookieVIP) # port http cookie-name “ServerID” \n(config-vs-cookieVIP) # port http csw-policy “myCookie” \n(config-vs-cookieVIP) # port http csw \n(config-vs-cookieVIP) # bind http rs1 http rs2 http<\/p>\n
<\/p>\n
<\/span>URL Switching<\/strong><\/span><\/h3>\n <\/p>\n
(config)# csw-rule products url prefix \/PRODUCTS case-insensitive \n(config)# csw-rule products url prefix \/PARTNERS case-insensitive<\/p>\n
(config)# csw-policy “myUrlPolicy” case-insensitive \n(config-csw-myUrlPolicy)# match products forward 201 \n(config-csw-myUrlPolicy)# match support forward 202 (server group) \n(config-csw-myUrlPolicy)# default forward 201<\/p>\n
(config)# server virtual url-sw-VIP [IP] \n(config-vs-url-sw-VIP)# port http \n(config-vs-url-sw-VIP)# port http csw-policy “myUrlPolicy” \n(config-vs-url-sw-VIP)# port http csw \n(config-vs-url-sw-VIP)# bind http rs1 http rs2 http<\/p>\n
<\/p>\n","protected":false},"excerpt":{"rendered":"
Content Switching provides the ability to distribute \/ rewrite traffic based upon a sessions Layer 7 payload. This feature also provides the ability to persist connections to a given server\/server group. There are 4 main methods to Layer 7 switching: Cookie Switching – Uses either a server sent cookie or ADX injected cookie to direct … Read more<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[],"yoast_head":"\nBrocade ADX - Content Switching (CSW) - Fir3net<\/title>\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\t \n\t \n\t \n