11-25-2014 07:56 AM
Hello,
I need create a policy that allows incoming connections between two servers I have configured for PLM. From what I noticed there is a jsession ID sticky predictor. Where do I configure the VIP? The policy process is confusing and I dont know where to begin. Here are my two server configs. can anyone help??
rserver host JAG-PLM9APP-02
ip address 172.28.9.81
inservice
rserver host JAG-PLM9WEB-02
ip address 172.28.9.87
inservice
serverfarm host PLM9-WEB-SF
rserver JAG-PLM9APP-02
inservice
rserver JAG-PLM9WEB-02
inservice
Solved! Go to Solution.
12-18-2014 10:45 AM
Kanwal,
The client is able to access the URL from his local machine but cannot access going server to server. Here is my current config. Am I missing something?
access-list ANYONE line 10 extended permit ip any any
probe icmp PING-PROBE
interval 10
faildetect 2
passdetect interval 30
passdetect count 2
receive 4
probe http PLM9-HTTP-PROBE-8801
port 8801
interval 10
faildetect 2
passdetect interval 15
passdetect count 2
request method get url /HealthMonitor/probe.jsp
expect status 200 200
open 1
probe http PLM9-HTTP-PROBE-8802
port 8802
interval 10
faildetect 2
passdetect interval 15
passdetect count 2
request method get url /HealthMonitor/probe.jsp
expect status 200 200
open 1
probe http PLM9-HTTP-PROBE-8803
port 8803
interval 10
faildetect 2
passdetect interval 15
passdetect count 2
request method get url /HealthMonitor/probe.jsp
expect status 200 200
open 1
probe http PLM9-HTTP-PROBE-8804
port 8804
interval 10
faildetect 2
passdetect interval 15
passdetect count 2
request method get url /HealthMonitor/probe.jsp
expect status 200 200
open 1
rserver host JAG-PLM9APP-02
ip address 172.28.9.81
inservice
rserver host JAG-PLM9WEB-02
ip address 172.28.9.87
inservice
serverfarm host PLM9-WEB-SF
predictor leastconns
rserver JAG-PLM9APP-02 8801
probe PLM9-HTTP-PROBE-8802
probe PLM9-HTTP-PROBE-8804
inservice
rserver JAG-PLM9WEB-02 8801
probe PLM9-HTTP-PROBE-8801
probe PLM9-HTTP-PROBE-8803
inservice
class-map type management match-any PM_MULTI_MATCH
201 match protocol snmp any
202 match protocol xml-https any
203 match protocol telnet any
204 match protocol ssh any
205 match protocol icmp any
206 match protocol https any
207 match protocol http any
class-map match-all VS_Classmap
2 match virtual-address 172.28.18.81 any
policy-map type management first-match management
class PM_MULTI_MATCH
permit
policy-map type loadbalance first-match Policy-MAP_LB
class class-default
serverfarm PLM9-WEB-SF
policy-map multi-match PM_MULTI_MATCH
class VS_Classmap
loadbalance vip inservice
loadbalance policy Policy-MAP_LB
loadbalance vip icmp-reply active
nat dynamic 1 vlan 109
interface vlan 18
description Client Vlan
ip address 172.28.18.124 255.255.255.128
access-group input ANYONE
service-policy input PM_MULTI_MATCH
no shutdown
interface vlan 109
description Servers Vlan
ip address 172.28.9.7 255.255.255.128
nat-pool 1 172.28.9.8 172.28.9.8 netmask 255.255.255.0 pat
service-policy input PM_MULTI_MATCH
no shutdown
ip route 0.0.0.0 0.0.0.0 172.28.18.1
snmp-server contact "ANM"
snmp-server location "ANM"
snmp-server trap-source vlan 18
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