Closed as fixed if next.
If there is more than one Notes port on server, for example, TCP Port and TCP cluster port, when Domino Diagnostic Probe (DDP) is running, there is no option to specify which port probe will be connected to. In customer case, the probe seems always connect to TCP cluster port; when normal TCP port hang and unable to provide service to user, probe is still able connecting to TCP cluster port, and miss opportunity to generate NSD,. Here is step to reproduce the issue for cluster environment: Create 2 Domino servers on 2 OS. I used 2 Windows 2008 on Vmware environment. Configure 2 network address for each OS. Configure 2 Domino Ports for above 2 network address on each OS Add above 2 Domino servers in one cluster Ensure 2 Domino cluster server is work and is able to connect each other Configure and start DDP probe according to TN1429892 on any of above server Enable server_clock=1 on DDP monitored server. Monitoring connection port on Domino server Here is another possible scenario in Domino configured with 2 ports: TCPIP and TCPIPClust port Reproduce steps 1. From Domino console run command: trace TCPIPClust!!!<Your Domino server name>, for example: TCPIPClust!!!DevDom852/Lotus 2. Above command will force trace command connecting to Domino server on cluster port "TCPIPClust" and this information will be cached. 3. When probe connecting to Domino server, it will retrieve above cached connection and connect to TCPIPClust port, instead of normal TCPIP port.
This APAR is closed as FIN. We have deferred the fix to a future release.
This APAR is associated with SPR# FMEG8UZ5XQ. This APAR is closed as FIN. We have deferred the fix to a future release.
Reported component name
Reported component ID
Last modified date
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:
Applicable component levels