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

CSS with re-map tcp port url problem

i am trying to configure a content with service port re-map but i have problem when i enter a URL on the content o tcp port 80 .

This configuration work fine :

service SRVAIX111
  keepalive type tcp
  ip address 10.7.100.134
  protocol tcp
  port 9084
  active

content Web-Sviluppo
   vip address 10.7.7.236
   add service SRVAIX111
   protocol tcp
   active

group Web-Sviluppo-Group
  vip address 10.7.7.236
  add destination service SRVAIX111

  active

With no URL on content i see webserver http://10.7.7.236 and return http://10.7.7.236:9084

Unfortunately I need to insert an url on content

But if insert URL on content and  "port 80" :

content WebSphere-Sviluppo
   vip address 10.7.7.236
   add service SRVAIX111
   protocol tcp
   port 80
   url "/*"
   no persistent
   active

This configuration does not work.

I try to set remap from :

persistence reset redirect

to

persistence reset remap

or remove "no persistent" from content

but nothing changes

Can someone help me ?

best regards

1 ACCEPTED SOLUTION

Accepted Solutions
Bronze

Re: CSS with re-map tcp port url problem

Hi buddy,

Your problem is not related to the persistence method that you're choosing to try to make this work, the problem is that you'r moving

your configuration from layer 3 to layer 5 and now the CSS needs to balance the traffic based not only on destination IP (VIP) but dst port

and URL (URL = proxy'd connection).

On your working configuration you have a L3 content with no port defined so when you go to the browser and enter  http://10.7.7.236

the request goes to the server the server sends a redirect to  http://10.7.7.236:9084 and the new connection hits again the same content rule

because there is no port defined. So far so good!

Now with your new config using URL and Port 80 you hit http://10.7.7.236 goes to the server and it does send the redirect again on port 9084

but this time you don't have such a rule taking traffic for that port so the request never makes it through.

If you want to get this working at L5 you need to create a separate rule on port 9084 as follows:

content WebSphere-Sviluppo_9084
   vip address 10.7.7.236
   add service SRVAIX111
   protocol tcp
   port 9084

   url "/*"
   active

HTH.

__ __

Pablo

3 REPLIES
Bronze

Re: CSS with re-map tcp port url problem

Hi buddy,

Your problem is not related to the persistence method that you're choosing to try to make this work, the problem is that you'r moving

your configuration from layer 3 to layer 5 and now the CSS needs to balance the traffic based not only on destination IP (VIP) but dst port

and URL (URL = proxy'd connection).

On your working configuration you have a L3 content with no port defined so when you go to the browser and enter  http://10.7.7.236

the request goes to the server the server sends a redirect to  http://10.7.7.236:9084 and the new connection hits again the same content rule

because there is no port defined. So far so good!

Now with your new config using URL and Port 80 you hit http://10.7.7.236 goes to the server and it does send the redirect again on port 9084

but this time you don't have such a rule taking traffic for that port so the request never makes it through.

If you want to get this working at L5 you need to create a separate rule on port 9084 as follows:

content WebSphere-Sviluppo_9084
   vip address 10.7.7.236
   add service SRVAIX111
   protocol tcp
   port 9084

   url "/*"
   active

HTH.

__ __

Pablo

Community Member

Re: CSS with re-map tcp port url problem

many thanks Pablo


I was lost between the levels L3 and L5

best regards

Bronze

Re: CSS with re-map tcp port url problem

Don't mention it, Glad to help =)

247
Views
0
Helpful
3
Replies
CreatePlease to create content