Application Delivery (ADX)

Reply
New Contributor
Posts: 2
Registered: ‎07-07-2017

Real server port in failed state

One of the real server port 7200 is in failed state. I created this recently and it is been in failed state since i created. Please let me know if i am missing any configuration.

 

Name: mservice1 IP:10.x.y.z State: Active
Port default: Failed
Port 8080: Failed
Port 8082: Failed
Port 8081: Failed
Port 6500: Failed
Port 7200: Failed
Name: mservice2 IP:10.x.y.z State: Active
Port default: Failed
Port 8080: Failed
Port 8082: Failed
Port 8081: Failed
Port 6500: Failed
Port 7200: Failed

 

Config:

server port 7200
tcp
l4-bringup-interval 5
bringup-retries 3

!

server real mservice1 10.x.y.z

 port 7200
 port 7200 group-id 10 10
 port 7200 url "GET /system/health"

!

server real mservice2 10.x.y.z

 port 7200
 port 7200 group-id 10 10
 port 7200 url "GET /system/health"

!

server virtual apidirect 10.a.b.c

 sym-priority 200
 predictor round-robin
 port http

 port http csw-policy "redir-ssl"
 port http csw
 port http keep-alive
 port ssl
 no port ssl sticky

 port ssl csw-policy "api-r14"
 port ssl csw

 port ssl keep-alive

 bind http api1 8181 real-port 8180 api2 8181 real-port 8180

 bind ssl mservice1 7200 mservice2 7200

!

New Contributor
Posts: 2
Registered: ‎07-07-2017

Re: Real server port in failed state

Please ignore this. I found out that the service itslef had issue rather than the configuration with the load balancer.

Join the Community

Get quick and easy access to valuable resource designed to help you manage your Brocade Network.