Optional use of Message Processor using port 4527 to Router

[#1]

According to http://docs.apigee.com/sites/docs/files/ApigeeEdgePrivateCloud-Install-Config-Guide_v3.pdf

While it is not required, you can open port 4527 on the Router for access by any Message Processor. Otherwise, you might see error messages in the Message Processor log files

What is the purpose of the Message Processor communicating with the Router on port 4527? What benefit is there in opening this optional connection?

We are not seeing any errors appearing in the Message Processor logs even thought the connection is not occurring. If we wanted to see the errors, what logger would we need to increase the verbosity level on?

Thanks

[gaurav_bhandari · Accepted solution]

Hi @Wayne Irwin

The router and message processor are in clusters. ie RMP cluster

When you execute the API CALL

curl -v http://<Router IP addresses:8081/v1/cluster/members

curl -v http://<message Processor IP addresses:8082/v1/cluster/members

In the output, you will find that the one router interacts with other router via port 4527 and one router interacts with other MP via port 4528.

"address" : "/10.20.129.254:4527",
"clusterType" : "router,message-processor",
"lastChange" : 1481747534963,
"latency" : 26,
"pod" : "gateway",
"region" : "dc-1",
"serverType" : "router",
"state" : "CONNECTED",
"uuid" : "-----1b4148a---------------"
},

, {
"address" : "/10.20.129.253:4528",
"clusterType" : "router,message-processor",
"lastChange" : 1481842600339,
"latency" : 30,
"pod" : "gateway",
"region" : "dc-1",
"serverType" : "message-processor",
"state" : "CONNECTED",
"uuid" : "edb9f45c-7129-4161-8b72-215b360c8c80"
}

This helps the RMP to find out that the RMP is in cluster. If the ports are closed, then the RMP will not be in cluster. and instead of state:CONNECTED, you will see state: DISCONENCTED.

[#3]

Thanks for the answer! I have opened the firewall ports and now see the connections.