06-12-2006 04:56 AM
Hi
while configuring the CSS Service, i want to allow the request for wide range of ports.
To meet the requirement i am configuring as below:
port 7051 range 949
Will this allow the request from different ports
Say a request from 7051, 7099 to pass successfully?
Or it will respond in sequential only llike 7051, 7052,etc.,
Appreciate your response
regards
R.Sundara Rajan
06-12-2006 11:37 PM
there is no 'range' option' for the port commands.
The only range option is for the vip address and it is honestly a special concept so very limited usability.
Gilles.
06-13-2006 12:29 AM
Hi Gilles,
Correct command is port 7051 949
range will get displayed in the sh run of the configuration .
Let me know if this will work for my requests anything coming in for 7051, 7067, 7097,etc.,
regards
R.Sundara Rajan
06-13-2006 01:52 AM
There is no such thing on the CSS.
CSS11503-2(config-owner[gdufour])# content WWW
CSS11503-2(config-owner-content[gdufour-WWW])# port ?
CSS11503-2(config-owner-content[gdufour-WWW])# port 80 ?
CSS11503-2(config-owner-content[gdufour-WWW])# port 80 81
^
%% Invalid input detected at '^' marker.
You can only specify 1 port or no port [which means any port].
Gilles.
06-13-2006 02:31 AM
Hi Gilles
Not in Owner Configuration
I am referring only Services configuration.
CSS - 11800
service A
keepalive type tcp
keepalive port 7051
ip address x.x.x.x
port 7051 range 950
active
content Z
add service A
vip address x.x.x.x
primarySorryServer B
protocol tcp
active
Let me know whether it will accept the requests that are coming through various ports 7051, 7057, 7091,etc.,
regards
R. Sundara Rajan
06-13-2006 06:43 AM
No, this range option is not for what port the CSS will be listening.
The port command from the content rule defines what the CSS will be listening for.
So if you have a content rule with port 7051, the CSS only accept connections for this port.
If you need to accept more ports, you have to either not specify any port or create a rule for each port you need.
On the service itself, if you do not need port nating, just do not specify any port.
The port command under the service definition is if you need to do port nating.
So, the range option that are refering to is not going to do what you need.
Gilles.
06-13-2006 09:13 PM
Hi Gilles,
Thanks for the clarification.
I will opt for not specifying any port on the Content Rule and Services so that wide range of ports are allowed.
regards
R.Sundara Rajan
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide