cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
667
Views
0
Helpful
3
Replies

Issue with ACE Module URL match policy...

cjkozloski
Level 1
Level 1

Need a little help here if possible.

I have a set of URL's that I am trying to get a policy match to work on. Basically, I have 3 url's that I want to use one server farm and a catch-all url that gets redirected to another serverfarm. Here's what it looks like:

SERVERFARM A:

/token-generator/

/regulatory-services/

/developers/

SERVERFARM B:

dev.url.com

The catch-all url in serverfarm b is working just fine. However, I keep seeing page cannot be displayed for the other url's even though when I go to the backend server url's they show up just fine. I can't figure out where this is failing. Here is my config for this setup:

rserver host XXX_DEV_AFAFG-PD-NWEB02

  ip address 3.3.3.3

   inservice

exit

!

rserver host XXX_ROGUE

  ip address 2.2.2.2

   inservice

exit

!

serverfarm host XXX_DEV_AFCORP

  rserver XXX_DEV_NWEB02

   inservice

  exit

exit

!

serverfarm host XXX_ROGUE_REDIRECT

  rserver XXX_ROGUE

   inservice

  exit

exit

!

class-map type vip loadbalance match-any L7_CLASS_VIP_XXX_DEV

  10 match virtual-address 1.1.1.1 tcp eq www

exit

!

class-map type http loadbalance match-any L7_CLASS_URL_XXX_DEV

  10 match http url /token-generator.*

  20 match http url /regulatory-services.*

  30 match http url /developers.*

exit

!

class-map type http loadbalance match-any L7_CLASS_ROGUE_XXX_DEV

  10 match http url .*

exit

!

policy-map type loadbalance first-match XXX_DEV_HTTP

description XXX policy map

!

class L7_CLASS_URL_AFPRO_DEV

  serverfarm XXX_DEV_AFCORP

exit

!

class L7_CLASS_ROGUE_AFPRO_DEV

  serverfarm XXX_ROGUE_REDIRECT

exit

!

exit

!  

policy-map multi-match VIPS

class L7_CLASS_VIP_XXX_DEV

  loadbalance vip inservice

  loadbalance policy XXX_DEV_HTTP

  loadbalance vip icmp-reply

  nat dynamic 1 vlan XXX

  appl-parameter http advanced-options HTTP-PERSISTENCE

exit

!

exit

!

wr mem

Any help with this would be appreciated. Thanks.

1 Accepted Solution

Accepted Solutions

ajayku2
Cisco Employee
Cisco Employee

Hi Christopher, 

You have created Class "L7_CLASS_URL_XXX_DEV" but you are not using it anywhere.

So ideally it should be like this :

class-map type http loadbalance match-any L7_CLASS_URL_XXX_DEV

  10 match http url /token-generator.*

  20 match http url /regulatory-services.*

  30 match http url /developers.*

class-map type vip loadbalance match-any L7_CLASS_VIP_XXX_DEV

  10 match virtual-address 1.1.1.1 tcp eq www

policy-map type loadbalance first-match XXX_DEV_HTTP

class L7_CLASS_URL_XXX_DEV

   SERVERFARM A

policy-map multi-match VIPS

class L7_CLASS_VIP_XXX_DEV

   loadbalance vip inservice

   loadbalance policy XXX_DEV_HTTP

   loadbalance vip icmp-reply

   nat dynamic 1 vlan XXX

   appl-parameter http advanced-options HTTP-PERSISTENCE

You can accomodate rest of the config accordingly.

hope that helps.

regards,

Ajay Kumar

View solution in original post

3 Replies 3

ajayku2
Cisco Employee
Cisco Employee

Hi Christopher, 

You have created Class "L7_CLASS_URL_XXX_DEV" but you are not using it anywhere.

So ideally it should be like this :

class-map type http loadbalance match-any L7_CLASS_URL_XXX_DEV

  10 match http url /token-generator.*

  20 match http url /regulatory-services.*

  30 match http url /developers.*

class-map type vip loadbalance match-any L7_CLASS_VIP_XXX_DEV

  10 match virtual-address 1.1.1.1 tcp eq www

policy-map type loadbalance first-match XXX_DEV_HTTP

class L7_CLASS_URL_XXX_DEV

   SERVERFARM A

policy-map multi-match VIPS

class L7_CLASS_VIP_XXX_DEV

   loadbalance vip inservice

   loadbalance policy XXX_DEV_HTTP

   loadbalance vip icmp-reply

   nat dynamic 1 vlan XXX

   appl-parameter http advanced-options HTTP-PERSISTENCE

You can accomodate rest of the config accordingly.

hope that helps.

regards,

Ajay Kumar

Thanks for the reply. You are correct. Although that was not the resolution to the answer you did find something that I needed to fix. Thanks for that.

It turns out that the servers on the back end had strict naming enabled which was causing it to fail.

Thanks for the help.

Hi Christopher,

Thanks for the feedback. Good to hear that the issue is resolved.

regards,

Ajay Kumar