DOCUMENTATION and DOWNLOAD: How to use Symantec's NetBackup Domain Network Analyzer (NBDNA) version 2.1 and BPTESTNETCONN.

Article:TECH125454  |  Created: 2010-01-22  |  Updated: 2014-01-09  |  Article URL http://www.symantec.com/docs/TECH125454
Article Type
Technical Solution

Product(s)

Environment

Issue



DOCUMENTATION and DOWNLOAD: How to use Symantec's NetBackup Domain Network Analyzer (NBDNA) version 2.1 and BPTESTNETCONN.


Solution



NetBackup Domain Network Analyzer version 2.1.

This version is included with NetBackup 7.0.1.
There is no need to install this version for 7.0.1 or later.

The package contains NBDNA and BPTESTNETCONN.

This distribution is intended for:


* NetBackup 7.0 (Limited functionality)
* NetBackup 6.5.X
* NetBackup 6.0


Issues Fixed in 2.1:

* 2007506 Getting "Bad arg length for Socket::pack_sockaddr_in,
          length is 0, should be 4 at PERL2EXE_STORAGE/Socket.pm line
          386." in some environments.

* 2008638 Read the win registry incorrectly for minor patch version.

* 2011165 Need to suppress false positive error code from bpclient.

* 2011210 Need to change options used with bptestnetconn.


Current Known Limitations:


* Must be running on a machine with NetBackup installed and running.

* If VxSS/NBAC is configured, authenticate with NBAC prior to
  running NBDNA.

* Tru64 is not officially supported.

* NetBackup 5.0 and later is not supported.

* Very Limited support on NetBackup 5.1.

* Supports NetBackup 6.0X through 6.5.X.

* Limited support with NetBackup 7.0 (incompatible bptestnetconn).

* Integration with bptestnetconn limited to 6.5.4 and later.



NBDNA is compatible with:

* Windows 2003 and 2008 (32 and 64 bit), except for Windows 2008 R2
* IBM AIX (RS6000)
* HP-UX (PA-RISC and IA64)
* Linux (Redhat and SuSe: X86, X86_64, IA64 )
* Solaris 9 and 10 (Sparc only)
* Solaris x86 10

* Tru64 is not officially supported at this time.


How to install NBDNA

 A. Windows:

1. Navigate to 'Win' folder from NBDNA package.  

2. Copy nbdna.exe from the Win folder to:
  <VERITAS_DIR>\netbackup\bin\support\
  (Create this directory if it does not exist)
 
3. Copy bpifconfig.exe from the Win folder to: <VERITAS_DIR>\netbackup\bin\goodies\support\
  (Create this directory if it does not exist)

  NOTE: bpifconfig.exe is copied to a different subdirectory than nbdna.exe

  It is recommended to add <VERITAS_DIR>\netbackup\bin\support\
  to your %PATH% variable.


 B. AIX, HP-UX, Linux, and Solaris:

1. Go to the appropriate folder for AIX, HP-UX,
  Linux or Solaris for the correct executables.
 
  NOTE: Solaris 10 X86 requires separate binaries from
        Sparc.  HP-UX binaries will work for IA64 and
        PA-RISC.  Linux binaries will work for X86 and
        AMD64/X64/EMT64 except for IA64, which has
        separate binaries.

2. Copy nbdna executable from appropriate O/S folder to:
  /usr/openv/netbackup/bin/support/
  (Create this directory if it does not exist)

  It is recommended to add /usr/openv/netbackup/bin/support/
  to your $PATH variable.

3. Set correct permissions (make binary executable):
  chmod +x /usr/openv/netbackup/bin/support/nbdna
4. Copy bpifconfig executable from appropriate O/S folder to:
    /usr/openv/netbackup/bin/goodies/support/
   (Create this directory if it does not exist)
   
NOTE: bpifconfig is copied to a different subdirectory than nbdna
   
5. Set correct permissions (make binary executable):
chmod +x /usr/openv/netbackup/bin/goodies/support/bpifconfig


How To get and install BPTESTNETCONN:

NBDNA and BPTESTNETCONN are introduced with NetBackup 6.5.6. NBDNA is design
to use BPTESTNETCONN as part of its test logic if it exist.  NBDNA 2.1 is
introduced with NetBackup 7.0.1.

NBDNA is incompatible with bptestnetconn included with 7.0.

BPTESTNETCONN is available as an EEB (Emergency Engineering Binary) for 6.5.4
and 6.5.5 under the following etracks:

6.5.4 - ET1952043

6.5.5 - ET1952048


NOTE: Since EEB install normally replaces another binary, BPTESTNETCONN does not
     exist prior to 6.5.6, so you need to execute the binary with the switch:
     -create (otherwise the install will complain an older version doesn't exist
     and exits).


The EEB are included in the folder, "BPTESTNETCONN"; see readme1st_313221.txt
or Technote 313221 at http://support.veritas.com/docs/313221 for instructions
to install EEBs.

For UNIX, be sure to check if the binary, /usr/openv/netbackup/bin/bptestnetconn
is EXECUTABLE.


How To Run NBDNA:


A. Windows:

1. Start DOS Shell with Administrator privileges.
a. If NBAC/VxSS is configured, authenticate.
2. Navigate to <VERITAS_DIR>\netbackup\bin\support\
3. Execute nbdna.exe
4. If there are failures, 3 report files will be created
  for examination.
  a. <hostname>.NBDNA.failure-report.<YYYYMMDD.HHMMSS>.log
  b. <hostname>.NBDNA.failure-report.<YYYYMMDD.HHMMSS>.html
  c. <hostname>.NBDNA.failure-errorlog.<YYYYMMDD.HHMMSS>.log
 
  Otherwise these files will always be created:
  a. ANONYMOUS.NBDNA.<YYYYMMDD.HHMMSS>.dna
  b. <hostname>.NBDNA.<YYYYMMDD.HHMMSS>.zip
 
  NOTE: The default output folder of these reports is:
  <VERITAS_DIR>\netbackup\bin\support\output\nbdna\YYYY-MM-DD.HHMMSS\
 
5. If requested by Symantec, only send the zip archive:
  <hostname>.NBDNA.<YYYYMMDD.HHMMSS>.zip
  This file contains all reports.
 
6. Use the -help switch for nbdna help list for other advance options.


B. AIX, HP-UX, Linux, and Solaris:


1. Log in to UNIX SHELL as root.
a. If NBAC/VxSS is configured, authenticate.
2. Execute NBDNA binary:
/usr/openv/netbackup/bin/support/nbdna
3. If there are failures, 3 report files will be created
  for examination:
  a. <hostname>.NBDNA.failure-report.<YYYYMMDD.HHMMSS>.log
  b. <hostname>.NBDNA.failure-report.<YYYYMMDD.HHMMSS>.html
  c. <hostname>.NBDNA.failure-errorlog.<YYYYMMDD.HHMMSS>.log

  Otherwise these files will always be created:
  a. ANONYMOUS.NBDNA.<YYYYMMDD.HHMMSS>.dna
  b. <hostname>.NBDNA.<YYYYMMDD.HHMMSS>.zip
 
  NOTE: The default output folder of these reports is:
  /usr/openv/netbackup/bin/support/output/nbdna/YYYY-MM-DD.HHMMSS/

4. If requested by Symantec, only send the zip archive:
  <hostname>.NBDNA.<YYYYMMDD.HHMMSS>.zip
  This file contains all reports.
 
5. Use the -help switch for nbdna help list for other advance options.



NBDNA Manual:

NAME

nbdna -     NetBackup Domain Network Analyzer (NBDNA) is utility that analyzes the NetBackup domain and its configuration for network issues, performance, and behavior in regards to hostname lookup and connectivity between NetBackup hosts and their role within the NetBackup domain.

SYNOPSIS

/usr/openv/netbackup/bin/support/nbdna
[-phase=<0|1|2>][-verbose][-sfo]
[-server][-lookup][-odir=<override_output_directory>]
[-tmp=<override_tmp_directory>][-dump][-f=<listfile.txt>]
[-overwritelist}][-version][-help]

DESCRIPTION

NBDNA will (1) discover and map the NetBackup domain, (2) extract hostname membership(s) by querying the configuration, (3) evaluate hostname name lookup and socket connectivity to these hostnames to validate their network relationship status according to their configuration within the domain. NBDNA can be run on a NetBackup master or media server.  

NBDNA will create up to 5 files: (1) ANONYMOUS.NBDNA.YYYYMMDD.HHMMSS.dna, (2) hostname.NBDNA.YYYYMMDD.HHMMSS.zip archive file, (3) hostname.NBDNA.failure-report.YYYYMMDD.HHMMSS.txt, (4) hostname.NBDNA.failure-report.YYYYMMDD.HHMMSS.html, and (5) hostname.NBDNA.failure-errorlog.YYYYMMDD.HHMMSS.log. The last 3 are only generated if there are errors.

NBDNA will create and identify a zip archive containing all generated reports.  Return the zip archive to Symantec upon request.

OPTIONS
[-phase=<0|1|2>] Set the test phase.  Default is 0 if omitted.
[-verbose] Display progress to standard out (on screen).  Same information is captured to the progress-trace log regardless of this switch and there is no need to capture -verbose output to standard out to file.
[-sfo] Produce script friendly reports.
[-server] Run server test only.
[-lookup] Run name lookup test only.
[-odir] Override output directory. Default: /usr/openv/netbackup/bin/support/output/nbdna/yyyy-mm-dd/. If NetBackup path cannot be found, the default is Change to the same directory as nbdna binary: <NDNA_DIR>/output/nbdna/yyyy-mm-dd/
[-tmp] Override temporary directory. Default: system temp directory.
[-dump] Do not run test, but dump test list to file.
[-f] Read hostnames from file and add to test lists.
[-overwritelist] Overwrite all test with list file.
[-version] Just display version info then exit.

Phase 0: Default mode. Name lookup test and socket connection test.
Phase 1: Includes Phase 0. Add basic NBU service test for SERVER list.
Phase 2: Includes Phase 0. Add basic NBU service test for SERVER and CLIENT list.

EXAMPLES

Example 1
In this example, nbdna is run with report files written to alternate directory:

# /usr/openv/netbackup/bin/support/nbdna -odir=/user/home/winter/

Example 2
In this example, nbdna is run with verbose output to perform phase 1 tests:

# /usr/openv/netbackup/bin/support/nbdna -phase=1 -verbose

Example 3
In this example, nbdna is run with verbose output and importing hostname list with -f and -overwritelist switch:

# /usr/openv/netbackup/bin/support/nbdna -verbose -f=hostnames.txt -overwritelist

File format example:
SERVER dellpe2400
CLIENT 10.12.249.20
LOOKUP 10.82.108.136


BPTESTNETCONN Manual:

NAME

bptestnetconn - test and analyze various configurations and connections
(Compatible with NetBackup 6.5.4 and 6.5.5)

SYNOPSIS

/usr/openv/netbackup/bin/bptestnetconn
usage 1: bptestnetconn [-v] -h | -b | -l
usage 2: bptestnetconn [-v] (-i | -fra) (-s | -H hostname)
usage 3: bptestnetconn [-v] (-c[servicename] [-o tv] [-t tv]) (-s | -H hostname)

DESCRIPTION

The bptestnetconn command performs several tasks that aid in the analysis of DNS and connectivity problems with any specified list of hosts, including the server list in the NetBackup configuration. To help troubleshoot connectivity problems between services that use CORBA communications, bptestnetconn can perform and report on CORBA connections to named services.

NDBNA executes bptestnetconn if it is found under netbackup/bin when running phase=1 or 2 tests. It is highly recommended to install bptestnetconn when installing NBDNA.

OPTIONS

-h or --help
displays this help message

-H hostname
The host name of the system or the IPv4 address. Specify a single name, an IP address, or the "-" character combination to accept a list from stdin.

-s or --servers
Directs the utility to look up all NetBackup servers in the configuration.

-l or --listservers
Directs the utility to list all servers in the NetBackup configuration.

-b or --confchecker
check for non-default settings

-a or --all
Reports all times, which has the effect as -fr. This condition is the default.'

-i or --ipservers
Directs the utility to list the IP addresses of all servers in the NetBackup configuration.

-f or --flkup
Reports all forward DNS lookup times for the specified host or hosts.

-r or --rlkup
Reports all reverse DNS lookup times for the specified host or hosts.

-c or --connect "object_string"
Reports connectToObject times to service. This action is similar to a CORBA ping to an object in another process. Suggested object strings include EMM/EMMServer, NBFSMCLIENT/FSM.ClientClusterMgr, nbrmms/DiskPollingService.DPS, nbrmms/STSEVentService, and nbsvcmon/NBSvcMon.  If object_string is not given, nbrmms/STSEventService is used as default.

NOTE: there is no space between -c and "object". For example: -cEMM/EMMServer

-t or --objreqwait time_value
Sets the object request timeout parameter. time_value is in seconds.

-o or --orbreqwait time_value
Sets orb request timeout parameter. time_value is in seconds.

-v or --verbose
Reports in verbose mode. The reverse lookup report shows which servers are media servers, EMMSERVER (if not local), and if any server is also the REQUIRED_INTERFACE or CLUSTERNAME.

EXAMPLES:

Example 1

# bptestnetconn -sc -v
SERVER = pepper.sub.domain.com
SERVER = salt.sub.domain.com
SERVER = cuminl7.sub.domain.com
SERVER = basil.sub.domain.com
SERVER = vinegar.sub.domain.com
MEDIASERVER = alum.sub.domain.com
------------------------------------------------------------------------
Connecting to 'nbrmms/STSEventService'
CN:                            pepper.sub.domain.com :     24 ms  [SUCCESS]
CN:                              salt.sub.domain.com :     30 sec [TRANSIENT]
CN:                           cuminl7.sub.domain.com :     20 ms  [SUCCESS]
CN:                             basil.sub.domain.com :     40 ms  [SUCCESS]
CN:                           vinegar.sub.domain.com :     29 sec [TRANSIENT]
CN:                              alum.sub.domain.com :      8 ms  [SUCCESS]
------------------------------------------------------------------------
Total elapsed time: 59 sec

Example 2

# bptestnetconn -o 60 -t 60 -cEMM/EMMServer -H pepper.sub.domain.com -v      
adding hostname = pepper.sub.domain.com
------------------------------------------------------------------------
Connecting to 'EMM/EMMServer'
CN:                            pepper.sub.domain.com :     24 ms  [SUCCESS]
------------------------------------------------------------------------
Total elapsed time: 0 sec

# bptestnetconn -o 60 -t 60 -cEMM/EMMServer -H salt.sub.domain.com -v
adding hostname = salt.sub.domain.com
------------------------------------------------------------------------
Connecting to 'EMM/EMMServer'
CN:                              salt.sub.domain.com :     60 sec [TRANSIENT]
------------------------------------------------------------------------
Total elapsed time: 60 sec



Attachments

nbdna2.1.tar_358517.gz (27.9 MBytes)


Legacy ID



346048


Article URL http://www.symantec.com/docs/TECH125454


Terms of use for this information are found in Legal Notices