Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

One Arm config Domain Name Content rule

Hi Guys

How does domain name content rule works in one arm config.

What do we put in source groups as VIP address.

Does it need host headers in WebServer as a requirement.

How does the client request gets completed.

Any help much appriciated..

7 REPLIES
Cisco Employee

Re: One Arm config Domain Name Content rule

Craig,

Can you give some more details on what you mean by "domain name content rules"?

Regards

Jim

New Member

Re: One Arm config Domain Name Content rule

Thanks for your reply Jim,

This is what I am trying to do in a One arm config topology

( As the CSS guide ( cntntgd.pdf ) says under Configuring a Domain Name content rule)

The CSS allows you to use a domain name in place of, or in conjunction with, a

VIP address in a content rule. Using a domain name in a content rule enables you

to:

Enable service provisioning to be independent of IP-to-domain name

mappings

Provision cache bandwidth as needed based on domain names

So I am trying to create a content rule with a domain name instead of VIP address. For ex.

content domainRule3

protocol tcp

port 80

url "//domain.com/*"

add service Serv1

active

group servers

add destination service Serv1

VIP address  ???????? ( what shd we put in here )

In this case what do we put as VIP address in source groups and how does the traffic flows from Client to actual Server in One arm topology. I am trying this topology where we have multiple sites configured with the same IP address with host headers

My assumption is that I shd configure DNS servers with VIP address for domain.com and use that as VIP address in source group. But how does the actual traffic flows from client to servers

Many thanks.

Cisco Employee

Re: One Arm config Domain Name Content rule

Thank you for the clarification.

This is what the traffic flow will look like in a one-armed config.

Traffic will enter the CSS with the source IP of the Client destined to the VIP address that it receives from DNS. The CSS will need to spoof the connection until it gets the client request. At that time it can make the load balance decision since it can reads the host header of the packet and decides what content rule it matches. Once it finds the correct content rule it will load balance to the server. At this point the packet will have the source IP of the VIP in the group, destined to the server that it load balanced to. CSS will use it's routing table to forward this packet to the sever. The reason you need the group is so that the server responds back to the CSS rather that directly back to the client.

The address you put in the group can be any address that routes back to the CSS. Usually this is the same as the content rule vip, or any local IP in the CSS curcuit vlan subnet.

Regards

Jim

New Member

Re: One Arm config Domain Name Content rule

Thanks Heaps.

This would be same as configuring multiple content rules with same VIP address and different domain names, right

What is the best way if we have to load balance several sites with same IP address and different host headers.

New Member

Re: One Arm config Domain Name Content rule

Also, how the client packet will be directed to CSS since it is one arm config and has only Domain name configured and not VIP address.

There won't be any arp reply as well.

Cisco Employee

Re: One Arm config Domain Name Content rule

Craig,

DNS is still going to be resolving these domains to some IP address. You would need to have routing set up to forward those IPs to the CSS interface/redundant-interface. You can also add the VIP address to the content rule along with the domain. If multiple domains resolve to the same IP you can create a content rule for each domain name all containing the same VIP address.

The CSS will parse the client request for the host header and match it to the correct rule.

regards

Jim

New Member

Re: One Arm config Domain Name Content rule

..

325
Views
0
Helpful
7
Replies
CreatePlease to create content