CA Service Management

Hi Team,

We are on r14.1 in AA mode and we have 6 application servers, 1 BG Server,1  BG Standby Server and 1 DMZ server.

We have opened below ports between application,bg, standby and the DMZ server.

2100

2300

8080

9080

9085

8085

However, when we start the services of the DMZ server we get below errors:

11/19 10:35:24.21 "DMZ Hostname" bop_cmd              4940 SIGNIFICANT  vdbinfo.frg             11 VDBINFO invoked at 11/19/2015 10:35:24

11/19 10:35:41.47 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for ("BG Hostname") listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:35:43.75 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for ("BGStd Hostname") listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:35:46.02 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP0) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:35:48.30 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP1) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:35:50.55 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP2) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:35:52.83 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP3) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:35:55.10 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP4) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:35:57.38 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP5) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:35:57.38 "DMZ Hostname" proctor_HBUSDPRDA    4772 SIGNIFICANT  pdm_process.c          923 Process stopped (D:/PROGRA~1/CA/SERVIC~1/bin/pdm_intrvlog_nxd.bat return: 0

11/19 10:35:57.38 "DMZ Hostname" proctor_HBUSDPRDA    4772 SIGNIFICANT  pdm_process.c          932 Stopped: D:/PROGRA~1/CA/SERVIC~1/bin/pdm_intrvlog_nxd.bat

11/19 10:35:57.90 "DMZ Hostname" pdm_d_mgr            2352 ERROR        daemon_obj.c          1990 Daemon pdm_intrvlog_nxd died: restarting

11/19 10:35:57.90 "DMZ Hostname" pdm_d_mgr            2352 SIGNIFICANT  mgr_slump_if.c        1221 Starting: $NX_ROOT/bin/pdm_intrvlog_nxd.bat

11/19 10:35:57.90 "DMZ Hostname" proctor_HBUSDPRDA    4772 SIGNIFICANT  pdm_process.c          572 Process Started (4508):D:/PROGRA~1/CA/SERVIC~1/bin/pdm_intrvlog_nxd.bat

11/19 10:36:14.66 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for ("BG Hostname") listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:36:16.93 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for ("BGStd Hostname") listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:36:19.19 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP0) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:36:21.47 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP1) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:36:23.72 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP2) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:36:26.04 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP3) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:36:28.32 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP4) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:36:30.60 "DMZ Hostname" slump_nxd             300 ERROR        ping_port.c            394 Unable to get address information for (APP5) listener port (2100), getAddrInfo() error: No such host is known. 

11/19 10:36:30.60 "DMZ Hostname" proctor_HBUSDPRDA    4772 SIGNIFICANT  pdm_process.c          923 Process stopped (D:/PROGRA~1/CA/SERVIC~1/bin/pdm_intrvlog_nxd.bat return: 0

11/19 10:36:30.60 "DMZ Hostname" proctor_HBUSDPRDA    4772 SIGNIFICANT  pdm_process.c          932 Stopped: D:/PROGRA~1/CA/SERVIC~1/bin/pdm_intrvlog_nxd.bat

11/19 10:36:31.11 "DMZ Hostname" pdm_d_mgr            2352 ERROR        daemon_obj.c          1990 Daemon pdm_intrvlog_nxd died: restarting

11/19 10:36:31.11 "DMZ Hostname" pdm_d_mgr            2352 SIGNIFICANT  mgr_slump_if.c        1221 Starting: $NX_ROOT/bin/pdm_intrvlog_nxd.bat

11/19 10:36:31.11 "DMZ Hostname" proctor_HBUSDPRDA    4772 SIGNIFICANT  pdm_process.c          572 Process Started (4432):D:/PROGRA~1/CA/SERVIC~1/bin/pdm_intrvlog_nxd.bat

11/19 10:36:45.41 "DMZ Hostname" pdm_d_mgr            2352 EXIT         api.c                 1760 Exiting because slump server terminated!

11/19 10:36:45.41 "DMZ Hostname" proctor_HBUSDPRDA    4772 SIGNIFICANT  api.c                 1748 Slump server terminated!

11/19 10:41:40.18 "DMZ Hostname" pdm_webstat          3224 SIGNIFICANT  api.c                  933 SLUMP api: failed to make connection (WSAECONNREFUSED (10061))

and when checked in BG server we found below msg:

11/19 10:55:00.10 BackgroundServerHostname  slump_nxd            5880 ERROR        ping_port.c            394 Unable to get address information for (DMZ Hostname) listener port (2100), getAddrInfo() error: No such host is known. 

Can some one let me know what could be the issue here?

Hi Johnny.

just a thought: does name resolution work as it should. As far as I can remember, it is quite common that the dmz host is not able to resolve internal hostnames nor the inernal hosts can resolve the dmz hostname. Maybe a simple check with  nslookup willl clarify. And maybe appropriate entries in /etc/hosts may help.

Kind regards

.............Michael

Hi Michael_Mueller

We have mentioned our application server's IP address in the DMZ server's host file; and that cleared the above messages on the DMZ server. However, I'm getting below error msgs continuously. Kindly let me know if any other ports are to be opened on the DMZ server.

11/20 18:44:14.85 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 19919 seconds for background online notification.

11/20 18:44:24.85 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 19929 seconds for background online notification.

11/20 18:44:34.87 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 19939 seconds for background online notification.

11/20 18:44:44.87 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 19949 seconds for background online notification.

11/20 18:44:54.87 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 19959 seconds for background online notification.

11/20 18:45:04.87 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 19969 seconds for background online notification.

11/20 18:45:05.99 APPDMZ pdm_webstat          6548 SIGNIFICANT  pdm_webstat.c          516 Web Stats Invoked for web:primary:2: Cumulative Sessions (0) Most Sessions (0) Current Sessions (0)

11/20 18:45:05.99 APPDMZ pdm_webstat          6548 SIGNIFICANT  pdm_webstat.c          516 Web Stats Invoked for web:primary:3: Cumulative Sessions (0) Most Sessions (0) Current Sessions (0)

11/20 18:45:05.99 APPDMZ pdm_webstat          6548 SIGNIFICANT  pdm_webstat.c          516 Web Stats Invoked for web:local: Cumulative Sessions (0) Most Sessions (0) Current Sessions (0)

11/20 18:45:06.21 APPDMZ bop_cmd              5972 SIGNIFICANT  ServerStatusMonitor.  372 ServerStatusMonitor initializing

11/20 18:45:06.21 APPDMZ bop_cmd              5972 SIGNIFICANT  bop_cmd.c              381 Starting function status() from frg file

11/20 18:45:06.21 APPDMZ bop_cmd              5972 SIGNIFICANT  vdbinfo.frg            11 VDBINFO invoked at 11/20/2015 18:45:06

11/20 18:45:06.23 APPDMZ bop_cmd              5972 SIGNIFICANT  vdbinfo.frg            40 VDBINFO completed at 11/20/2015 18:45:06

11/20 18:45:16.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 19981 seconds for background online notification.

11/20 18:45:26.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 19991 seconds for background online notification.

11/20 18:45:36.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20001 seconds for background online notification.

11/20 18:45:46.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20011 seconds for background online notification.

11/20 18:45:56.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20021 seconds for background online notification.

11/20 18:46:06.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20031 seconds for background online notification.

11/20 18:46:16.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20041 seconds for background online notification.

11/20 18:46:26.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20051 seconds for background online notification.

11/20 18:46:36.23 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20061 seconds for background online notification.

11/20 18:46:46.24 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20071 seconds for background online notification.

11/20 18:46:56.24 APPDMZ pdm_rfbroker_nxd    4584 SIGNIFICANT  rfbroker.c            401 Waited 20081 seconds for background online notification.

Thanks

Hi Johnny,

I think the problem is that CA SDM uses a range of ports, there are a few options in the NX file that you can change to force the application server to stay within a specific range.  I remember seeing somewhere that a DMZ server will need the following options set as well as the port range between 2100 and 2200 open.  Michael_Mueller please correct me if that's wrong.

# Uncomment this if you must run through a firewall and need to control the

# sockets that the slump slave uses.  The sockets will be near and slightly

# higher than the socket number for slump in /etc/services

@NX_SLUMP_FIXED_SOCKETS=1

# Uncomment this and set correct port number that slump will use as a base

# to select a listening port for fast channels. Selected port will be equal

# to or slightly higher than the port number specified port number. Default

# value of this variable is same as defined for slump in /etc/services.

@NX_SLUMP_SECONDARY_SOCKET=2100

I found a tecdoc that may help.

http://www.ca.com/us/support/ca-support-online/product-content/knowledgebase-articles/tec602295.aspx

Hi gbruneau

Thanks for the reply.

We have 6 application servers ,1 DMZ server, 1 BG server and 1 BG Standby Server...so should these port range be enabled between all the SDM servers or between DMZ and BG server only?

And similarly should these options

@NX_SLUMP_SECONDARY_SOCKET=2100

@NX_SLUMP_FIXED_SOCKETS=1

be set between BG and DMZ or should these be enabled in all the Application server.

I didn't see you mention anything about the DB ports in your port listing, but be aware that the application servers on an AA configuration will communicate directly with the database (at least according to one of the images in the manuals). Verify you have the connection open between the server on the DMZ and the database host.

Also, ping requires the ICMP protocol to be allowed through the firewall, not sure whether you've done this or if it has any effect on this case.

This is correct.

You need to open DB ports between DMZ APP Server and DB Server.

At least that work on a customer site

You need the following ports:

CA SDM

SMTP: 143   to exchange servers  for notifications

LDAP: 389 – ldap server

Proctor Socket: 2300

Slump Socket: 2100 to 2200 (range of 100 Ports)

Attachment (to/from attachments repository Server to new Server)

TCP        139, 445

UDP       137, 138

REST - For Mobile Application (Optional)

Apache Tomcat: 8050

Apache Tomcat Shutdown: 8055

Database

SQL Server: 1433 to SQL DB Server (inbound) dynamic port going out

Tomcat port: 8080 open internally for administrative purposes

I hope this helps...

Hi All,

We have enabled the required ports between our DMZ and other app and bg servers. Also, the NX.env changes are done. However when we start the DMZ services we find below msgs in the logs:

12/15 12:22:59.15 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1990 RFBroker on server APPDMZ (id:19849) changed state to STATE_INITIALIZING

12/15 12:22:59.19 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  ServerStatusMonitor.  1910 This server APPDMZ (19849) has checksums ddict(1612578989) Majic(1900588460) wsp.mods(3564860301)

12/15 12:22:59.19 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server BG (id:17509) does not seem to be connected.

12/15 12:22:59.19 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server BGSTD (id:19842) does not seem to be connected.

12/15 12:22:59.19 APPDMZ web:primary:2        8080 SIGNIFICANT  session.c             7083 Allowing 20 seconds for server response before displaying Server Response Delayed

12/15 12:22:59.19 APPDMZ web:primary:2        8080 SIGNIFICANT  session.c             7212 HTMPL cache is active

12/15 12:22:59.19 APPDMZ web:primary:3         228 SIGNIFICANT  session.c             7083 Allowing 20 seconds for server response before displaying Server Response Delayed

12/15 12:22:59.19 APPDMZ web:primary:2        8080 SIGNIFICANT  session.c             7222 Macro cache is active

12/15 12:22:59.19 APPDMZ web:local            5248 SIGNIFICANT  session.c             7083 Allowing 20 seconds for server response before displaying Server Response Delayed

12/15 12:22:59.19 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP0 (id:19843) does not seem to be connected.

12/15 12:22:59.19 APPDMZ boplgin              6648 SIGNIFICANT  bplhndlr.c            1713 BOPLGIN not ready (status=0); request queued

12/15 12:22:59.19 APPDMZ web:primary:3         228 SIGNIFICANT  session.c             7212 HTMPL cache is active

12/15 12:22:59.29 APPDMZ web:local            5248 SIGNIFICANT  session.c             7212 HTMPL cache is active

12/15 12:22:59.29 APPDMZ boplgin              6648 SIGNIFICANT  boplgin.c              463 Can't connect to server 'domsrvr'; will retry in 30 seconds

12/15 12:22:59.30 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP1 (id:19844) does not seem to be connected.

12/15 12:22:59.33 APPDMZ web:primary:2        8080 SIGNIFICANT  session.c            21237 webengine(web:primary:2) contacts webdirector(web:dir:primary:1:APPDMZ)...

12/15 12:22:59.33 APPDMZ web:local            5248 SIGNIFICANT  session.c             7222 Macro cache is active

12/15 12:22:59.35 APPDMZ web:primary:3         228 SIGNIFICANT  session.c             7222 Macro cache is active

12/15 12:22:59.35 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP2 (id:19845) does not seem to be connected.

12/15 12:22:59.35 APPDMZ web:primary:2        8080 SIGNIFICANT  session.c             6928 Web Statistics - Cumulative Sessions (0) Most Sessions (0) Current Sessions (0)

12/15 12:22:59.44 APPDMZ pdm_d_mgr            4132 SIGNIFICANT  daemon_obj.c          1798 Transient process (confirm_db) finished with return (0)

12/15 12:22:59.44 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP3 (id:19846) does not seem to be connected.

12/15 12:22:59.44 APPDMZ web:primary:2        8080 SIGNIFICANT  session.c            20827 webengine(web:primary:2) received init_done message from webdirectory(web:dir:primary:1:APPDMZ).

12/15 12:22:59.44 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP4 (id:19847) does not seem to be connected.

12/15 12:22:59.44 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP5 (id:19848) does not seem to be connected.

12/15 12:22:59.44 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c             984 Register_Singleton received for processName: web:dir:primary:1:APPDMZ slumpId :19849 remoteSlumpHost :APPDMZ

12/15 12:22:59.44 APPDMZ slump_nxd            3324 SIGNIFICANT  list.c                1410 Registered singleton procname "web:dir:primary:1:APPDMZ"

12/15 12:22:59.52 APPDMZ web:local            5248 SIGNIFICANT  session.c            21237 webengine(web:local) contacts webdirector(web:dir:primary:1:APPDMZ)...

12/15 12:22:59.52 APPDMZ web:local            5248 SIGNIFICANT  session.c             6928 Web Statistics - Cumulative Sessions (0) Most Sessions (0) Current Sessions (0)

12/15 12:22:59.52 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server BG (id:17509) does not seem to be connected.

12/15 12:22:59.52 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server BGSTD (id:19842) does not seem to be connected.

12/15 12:22:59.52 APPDMZ web:local            5248 SIGNIFICANT  session.c            20827 webengine(web:local) received init_done message from webdirectory(web:dir:primary:1:APPDMZ).

12/15 12:22:59.54 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP0 (id:19843) does not seem to be connected.

12/15 12:22:59.54 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP1 (id:19844) does not seem to be connected.

12/15 12:22:59.54 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP2 (id:19845) does not seem to be connected.

12/15 12:22:59.54 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP3 (id:19846) does not seem to be connected.

12/15 12:22:59.54 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP4 (id:19847) does not seem to be connected.

12/15 12:22:59.54 APPDMZ pdm_rfbroker_nxd     3236 SIGNIFICANT  rfbroker.c            1600 Server HAPP5 (id:19848) does not seem to be connected.

12/15 12:22:59.63 APPDMZ web:primary:3         228 SIGNIFICANT  session.c            21237 webengine(web:primary:3) contacts webdirector(web:dir:primary:1:APPDMZ)...

12/15 12:22:59.63 APPDMZ web:primary:3         228 SIGNIFICANT  session.c             6928 Web Statistics - Cumulative Sessions (0) Most Sessions (0) Current Sessions (0)

12/15 12:22:59.63 APPDMZ web:primary:3         228 SIGNIFICANT  session.c            20827 webengine(web:primary:3) received init_done message from webdirectory(web:dir:primary:1:APPDMZ).

12/15 15:58:05.12 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12476 seconds for background online notification.

12/15 15:58:15.12 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12486 seconds for background online notification.

12/15 15:58:25.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12496 seconds for background online notification.

12/15 15:58:35.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12506 seconds for background online notification.

12/15 15:58:45.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12516 seconds for background online notification.

12/15 15:58:55.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12526 seconds for background online notification.

12/15 15:59:05.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12536 seconds for background online notification.

12/15 15:59:15.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12546 seconds for background online notification.

12/15 15:59:25.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12556 seconds for background online notification.

12/15 15:59:35.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12566 seconds for background online notification.

12/15 15:59:45.13 HBUSDPRDAPPDMZ pdm_rfbroker_nxd     4676 SIGNIFICANT  rfbroker.c             401 Waited 12576 seconds for background online notification.

Kindly let me know what could be the issue here.