A while ago, I set up a QA environment so I can test out different policies/profiles/apps without affecting existing users. Unlike VMware AirWatch, you can have as many Server Routing Protocol Identifier (SRP ID) setup as you like within your account. The additional SRP ID(s) will consume the same number of licenses you have purchased for your account.

One particular aspect I like about Blackberry UEM is its support for high availability. Even if you have multiple networks in your environment, you can have active/active setup as long as your UEM nodes can communicate with one another.

Generally, among the list of services within the UEM console, only the Blackberry UEM – Blackberry Affinity Manager service might show Standby under Status if you have more than one UEM nodes. All other services should show Running. For some reason, I discovered that both Blackberry Proxy and Blackberry Control services show Paused instead of Running.

The Blackberry KB below describes different scenarios why this might happen.

• BlackBerry Control Service shows status “paused” in UEM Management Console
• BlackBerry Proxy service has status “paused”
• BlackBerry Proxy remains in a paused status in BlackBerry UEM

Below is found in my gc_server log which somewhat matched what’s described in the first Blackberry KB:

2018-07-23 16:10:09,862 DEBUG GDEntSvr/829c7594-ca97-46d4-b79c-aea44a8d6df9 com.good.gmc.GmcServer – Status: {“paused”:true,”name”:”BlackBerry UEM – BlackBerry Control Service“,”ha”:{“scheme”:”active-active”,”state”:”active”},”health”:{“score”:60},”serviceID”:”GoodControl”,”version”:”12.7.2.52″,”connections”:[{“connected”:false,”type”:”MDC”,”dest”:”https://gdmdc.good.com/GNP1.0″},{“connected”:false,”type”:”PUSHGW”,”dest”:”https://gdmdc.good.com:443/GDES1.0″},{“connected”:true,”type”:”DB”,”dest”:”jdbc:sqlserver://MGSQLDWD01:1433;databaseName=BlackberryControlDB;integratedSecurity=true;sendStringParametersAsUnicode=false;multiSubnetFailover=True”,”properties”:[{“name”:”dialect”,”value”:”com.good.db.util.SQLAddNVarCharDialect”},{“name”:”driver”,”value”:”com.microsoft.sqlserver.jdbc.SQLServerDriver”}]}]}
2018-07-23 16:10:09,996 ERROR HealthCheckMonitor1/829c7594-ca97-46d4-b79c-aea44a8d6df9 com.good.gmc.monitor.HttpConnectivityMonitor – HttpConnectivityMonitor Http connectivity failed to URL https://gdmdc.good.com:443/GDES1.0
java.net.SocketException: Connection reset

However, I confirmed my UEM node met all the conditions listed below:

• Connectivity to https://gdmdc.good.com/GNP1.0 (over port 443)
• HTTP push to BlackBerry Work (https://gdmdc.good.com:443/GDES1.0 over port 443)
• Connectivity to the Control (GC) database
• CPU usage <= 90%
• Memory usage <= 90%

Below is found in my gpslog_server log which somewhat matched what’s described in the second Blackberry KB:

2018-07-23 16:10:12,967 INFO Cron0 com.good.gps.App – BES Status: {“paused”:true,”name”:”BlackBerry UEM – BlackBerry Proxy Service“,”ha”:{“scheme”:”active-active”,”state”:”active”},”health”:{“score”:80},”serviceID”:”GoodProxy”,”version”:”12.7.2.49″,”connections”:[{“connected”:true,”type”:”GC”,”dest”:”UEM_server,UEM_server”,”properties”:[{“name”:”lastConnectedTimeStamp”,”value”:”2018-07-23T16:10:12.604-04:00″}]},{“connected”:true,”type”:”session”,”properties”:[{“name”:”maxSession”,”value”:”15000″},{“name”:”activeSession”,”value”:”0″},{“name”:”totalSession”,”value”:”0″},{“name”:”idleSession”,”value”:”0″},{“name”:”noOfdirectConnectConnections”,”value”:”0″},{“name”:”noOfrelayConnections”,”value”:”0″},{“name”:”dest”,”value”:”gdrelay.good.com”},{“name”:”port”,”value”:”443″}]},{“connected”:false,”type”:”MDC”,”dest”:”gdentgw.good.com”,”properties”:[{“name”:”lastConnectedTimeStamp”,”value”:”Not Connected”},{“name”:”port”,”value”:”443″}]}]}

Upon further review of our firewall logs, we saw several connection reset between my UEM node and https://gdmdc.good.com (over port 443). Upon correcting the setting in our firewall, both Blackberry Proxy and Blackberry Control services show Running once again.