Bathy DataBASE Diagnostics Tool

The Bathy DataBASE Diagnostics tool (BathyDBDiagnostics) provides various metrics about the network communication with BDB Server. The tool is run using a command window and the results are useful to both the system administrator and Customer Service Advisors for diagnosing problems.

The following is the command line format for the Bathy DataBASE Diagnostics tool:

bathydbdiagnostics --login <value> --server <value> --endpoint_port <value> --endpoint_port_span <value> --ops <value>

Parameter
Long	Short	Description
--help	-h	Display the help message (command format and descriptions of the available parameters) for the current command.
--login	-l	The credentials used to log into the Node Manager. They must be entered in the format of: • username/password, or • username/password@hostname, where hostname is the name or IP address of the computer on which the Node Manager is installed. When hostname is not specified, it is assumed to be the local machine.
--server	-s	The name of the database on the server to log into.
--endpoint_port		Identify the port range by specifying the first port number to be used by the server to communicate with the client.
--endpoint_port_span		The number of ports to include in the range of ports. The default is 15. The server will attempt to connect to each port number in order until it finds a free one.
--ops	-n	The number of times to test the push and pull of data on the server. The default is 4, which means the client would attempt to send (push) data to the server four times, then the server would use a callback to attempt to access (pull) data from the client four times.

Menu	Start menu > BASE Editor <version> Command Prompt
Tool

Command Entered

bathydbdiagnostics --login="loader/loader@MyMachine.domain.priv" --server="MyServer"

Results

Testing ICMP network ping:

32 bytes from 192.168.41.93: icmp_seq=1, ttl=125, time=0 ms

Testing port access on MyMachine.domain.priv :

Bathy node manager (51000) : Passed

Naming service (2809) : Passed

Logging service (20000) : Passed

Notification service (5156) : Passed

BathyServer Client using endpoint option: -ORBListenEndpoints iiop://:51101/portspan=15

Connecting to node manager: Passed

Connecting to MyServer: Passed

Testing server ping: Passed

Testing data transfer (client push to server, 64K of data):

(1) Success: time=20ms

(2) Success: time=16ms

(3) Success: time=15ms

(4) Success: time=16ms

Statistics:

Blocks: Pushed = 4, Lost = 0 (0% loss)

Approximate times in milli-seconds:

Minimum = 15ms, Maximum = 20ms, Average = 16ms

Testing server's ability to ping client: Passed

Testing data transfer (server pull from client, 64K of data):

(1) Success: time=27ms

(2) Success: time=19ms

(3) Success: time=19ms

(4) Success: time=18ms

Statistics:

Blocks: Pulled = 4, Lost = 0 (0% loss)

Approximate times in milli-seconds:

Minimum = 18ms, Maximum = 27ms, Average = 20ms

Command Entered

bathydbdiagnostics --login="loader/loader@MyMachine.domain.priv" --server="MyServer" /port="61000"

Results

Testing ICMP network ping:

32 bytes from 192.168.41.93: icmp_seq=1, ttl=125, time=0 ms

Testing port access on MyMachine.domain.priv :

Bathy node manager (51000) : Passed

Naming service (2809) : Passed

Logging service (20000) : Passed

Notification service (5156) : Passed

BathyServer Client using endpoint option: -ORBListenEndpoints iiop://:61000/portspan=15

Connecting to node manager: Passed

Connecting to MyServer: Passed

Testing server ping: Passed

Testing data transfer (client push to server, 64K of data):

(1) Success: time=20ms

(2) Success: time=16ms

(3) Success: time=15ms

(4) Success: time=15ms

Statistics:

Blocks: Pushed = 4, Lost = 0 (0% loss)

Approximate times in milli-seconds:

Minimum = 15ms, Maximum = 20ms, Average = 16ms

Testing server's ability to ping client: Failed [timed out]

Testing data transfer (server pull from client, 64K of data):

(1) Failed [timed out]: time=30000ms

(2) Failed [timed out]: time=30000ms

(3) Failed [timed out]: time=30000ms

(4) Failed [timed out]: time=30000ms

Statistics:

Blocks: Pulled = 0, Lost = 4 (100% loss)

Approximate times in milli-seconds:

Minimum = 30000ms, Maximum = 30000ms, Average = 30000ms

Command Entered

bathydiagnostics --login="loader/loader@MyMachine.domain.priv" --server="WrongServer"

Results

Testing ICMP network ping:

32 bytes from 192.168.41.93: icmp_seq=1, ttl=125, time=0 ms

Testing port access on MyMachine.domain.priv :

Bathy node manager (51000) : Passed

Naming service (2809) : Passed

Logging service (20000) : Passed

Notification service (5156) : Passed

BathyServer Client using endpoint option: -ORBListenEndpoints iiop://:51101/portspan=15

Connecting to node manager: Passed

Connecting to WrongServer: Failed [Failed to obtain client session to database: Bathy object requested does not exist]

Command Entered

bathydbdiagnostics --login="loader/loader@invalidhostname.domain.priv" --server="MyServer"

Results

Testing ICMP network ping:

invalidhostname.domain.priv : No such host is known

Testing port access on invalidhostname.domain.priv :

Bathy node manager (51000) : Failed [No such host is known]

Naming service (2809) : Failed [No such host is known]

Logging service (20000) : Failed [No such host is known]

Notification service (5156) : Failed [No such host is known]

Command Entered

bathydbdiagnostics --login="loader/loader@AnotherUser.domain.priv --server="MyServer"

Results

Testing ICMP network ping:

32 bytes from 192.168.41.153: icmp_seq=1, ttl=125, time=0 ms

Testing port access on AnotherUser.domain.priv :

Bathy node manager (51000) : Failed [An existing connection was forcibly closed by the remote host]

Naming service (2809) : Failed [An existing connection was forcibly closed by the remote host]

Logging service (20000) : Failed [An existing connection was forcibly closed by the remote host]

Notification service (5156) : Failed [An existing connection was forcibly closed by the remote host]