We're here to help!

  1. Dbvisit Support
  2. Dbvisit Standby
  3. Dbvisit Standby Knowledge Base

Testing DBVNET Connectivity

Follow
Arjen Visser —
Description

When using Dbvisit Standby version 7.0 and 8.0, the default network communication is done via the new Dbvisit Dbvnet background service.

 For Version 7.0 To test the connectivity between a primary and standby server you can make use of the dbvnet-test.exe (Windows) or dbvnet-test (Linux) applications to test connectivity. For more details on the usage of this utility, see the usage output from dbvnet-test -h.

For Version 8.0 you can use dbvnet executable file and test connectivity , for more options and usage you can use dbvnet -h

Examples(Version 7.0)

Note: If you are using later versions of Dbvisit Standby the dbvnet-test utility when using -f (full test) requires you to provide a temp directory that exist on both systems:

dbvnet-test [-f|--fulltest] TMPDIR SERVER:PORT

For example:

./dbvnet-test -f /tmp dbvlin101:7890

Windows

C:\Program Files (x86)\Dbvisit\Dbvnet>dbvnet-test.exe -s dbvwin101
Determining Dbvnet status on server dbvwin101:7890...
Dbvnet on server dbvwin101:7890 is running.

C:\Program Files (x86)\Dbvisit\Dbvnet>dbvnet-test.exe -f dbvwin101
Determining Dbvnet status on server dbvwin101:7890...
Dbvnet on server dbvwin101:7890 is running.
Running file transfer round trip on server dbvwin101:7890...
Creating file 'C:\Users\oracle\AppData\Local\Temp\2\dbvnet-test.tmp' containing 10 MB of data... - done.

Transferring 'dbvnet-test.tmp' to server dbvwin101:7890
Progress: 0%...20%...40%...60%...80%...100% [1023 KB/s] - done.
Retrieving file "dbvnet-test.tmp" from server dbvwin101:7890
Progress: 0%...20%...40%...60%...80%...100% [2754 KB/s] - done.

Comparing checksums: all three checksums (local/remote/local) are identical.
File transfer round trip finished successfully.

Linux:

oracle@dbvrlin301[/usr/dbvisit/dbvnet]: ./dbvnet-test -s dbvrlin305
Determining Dbvnet status on server dbvrlin305:7890...
Dbvnet on server dbvrlin305:7890 is running.
oracle@dbvrlin301[/usr/dbvisit/dbvnet]: ./dbvnet-test -f dbvrlin305
Determining Dbvnet status on server dbvrlin305:7890...
Dbvnet on server dbvrlin305:7890 is running.
Running file transfer round trip on server dbvrlin305:7890...
Creating file '/tmp/dbvnet-test.tmp' containing 10 MB of data... - done.

Transferring 'dbvnet-test.tmp' to server dbvrlin305:7890
Progress: 0%...20%...40%...60%...80%...100% [2568 KB/s] - done.
Retrieving file "dbvnet-test.tmp" from server dbvrlin305:7890
Progress: 0%...20%...40%...60%...80%...100% [5357 KB/s] - done.

Comparing checksums: all three checksums (local/remote/local) are identical. File
transfer round trip finished successfully.

Examples(Version 8.0)

Refer to the below link which has examples and options used in version 8.0

https://dbvisit.atlassian.net/wiki/display/DS8QSG/Dbvisit+Standby+Networking+-+Dbvnet#DbvisitStandbyNetworking-Dbvnet-5.TestingDbvnetCommunication

 

Anton Els November 14, 2013 11:24

Have more questions? Submit a request

Comments

  • Avatar
    Arjen Visser

    To perform a more detailed check, testing network connectivity, you can run the following. Make sure TMPDIR exists on target:

    dbvnet-test [-f|--fulltest] TMPDIR SERVER:PORT

    Donna Zehl

  • Avatar
    Arjen Visser

    I already did

    ./dbvnet-test -s dbvrlin305

    *and worked fine.  *

    I will connect again to try the fulltest.

    Ramon Estevez

  • Avatar
    Arjen Visser

    [oracle@srv-l-prodb-01 dbvnet]$ more /etc/hosts

    127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4

    ::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

    132.147.50.33   srv-l-prodb-01 srv-l-prodb-01.cartonesdelcaribe.local

    132.147.50.34   srv-l-prodb-02 srv-l-prodb-02.cartonesdelcaribe.local

    [oracle@srv-l-prodb-01 dbvnet]$ ping srv-l-prodb-02

    PING srv-l-prodb-02 (132.147.50.34) 56(84) bytes of data.

    64 bytes from srv-l-prodb-02 (132.147.50.34): icmp_seq=1 ttl=64 time=0.413 ms

    64 bytes from srv-l-prodb-02 (132.147.50.34): icmp_seq=2 ttl=64 time=0.677 ms

    64 bytes from srv-l-prodb-02 (132.147.50.34): icmp_seq=3 ttl=64 time=0.612 ms

    64 bytes from srv-l-prodb-02 (132.147.50.34): icmp_seq=4 ttl=64 time=0.500 ms

    64 bytes from srv-l-prodb-02 (132.147.50.34): icmp_seq=5 ttl=64 time=0.517 ms

    64 bytes from srv-l-prodb-02 (132.147.50.34): icmp_seq=6 ttl=64 time=0.408 ms

    64 bytes from srv-l-prodb-02 (132.147.50.34): icmp_seq=7 ttl=64 time=0.356 ms

    ^C

    --- srv-l-prodb-02 ping statistics ---

    7 packets transmitted, 7 received, 0% packet loss, time 6000ms

    rtt min/avg/max/mdev = 0.356/0.497/0.677/0.110 ms

    [oracle@srv-l-prodb-01 dbvnet]$ ./dbvnet-test -f srv-l-prodb-02

    ./dbvnet-test: target server name or IP address missing!

    [oracle@srv-l-prodb-01 dbvnet]$ ./dbvnet-test -s srv-l-prodb-02

    Determining Dbvnet status on server srv-l-prodb-02:7890...

        Dbvnet on server srv-l-prodb-02:7890 is running.

    [oracle@srv-l-prodb-01 dbvnet]$ ./dbvnet-test -f srv-l-prodb-02

    ./dbvnet-test: target server name or IP address missing!

    [oracle@srv-l-prodb-01 dbvnet]$

    Ramon Estevez

  • Avatar
    Arjen Visser

    The same happen in stby server

     

    [oracle@srv-l-prodb-02 dbvnet]$  ./dbvnet-test -f srv-l-prodb-01

    ./dbvnet-test: target server name or IP address missing!

    [oracle@srv-l-prodb-02 dbvnet]$  ./dbvnet-test -s srv-l-prodb-01

    Determining Dbvnet status on server srv-l-prodb-01:7890...

        Dbvnet on server srv-l-prodb-01:7890 is running.

    [oracle@srv-l-prodb-02 dbvnet]$  ./dbvnet-test -f srv-l-prodb-01

    ./dbvnet-test: target server name or IP address missing!

    [oracle@srv-l-prodb-02 dbvnet]$ ping srv-l-prodb-01

    PING srv-l-prodb-01 (132.147.50.33) 56(84) bytes of data.

    64 bytes from srv-l-prodb-01 (132.147.50.33): icmp_seq=1 ttl=64 time=0.423 ms

    64 bytes from srv-l-prodb-01 (132.147.50.33): icmp_seq=2 ttl=64 time=0.435 ms

    64 bytes from srv-l-prodb-01 (132.147.50.33): icmp_seq=3 ttl=64 time=0.594 ms

    ^C

    --- srv-l-prodb-01 ping statistics ---

    3 packets transmitted, 3 received, 0% packet loss, time 2000ms

    rtt min/avg/max/mdev = 0.423/0.484/0.594/0.077 ms

    Ramon Estevez