NetWorker nsrTools - Part 4
nsrTools is an interactive command-line utility created by the DELL EMC Field support which bundles different support tools to have one tool in one place. The tool can be downloaded from the EMC FTP link - ftp://nwc:nwc@ftp.emc.com/nsrTools/nsrTools.zip.
Compatibility :
This tool supports NetWorker version 18 and newer releases.Operating systems:
- Windows 2012 64bit or newer
- Linuxt 64bit distributions:
- CentOS / RHEL 6.x, 7.x, 8.x
- SUSE SLES 11.x, 12.x or newer
There is no installation required and nsr tools is read-only so no configuration change will be done to your system so this is pretty safe to tinker around with.
There are a lot of tools packed into this one package and covering all of it in one article is going to make it a lot lengthier than I want. Thus this is going to be a multipart article. n this part of the video we will logging we will look at
- Data Domain mtree explorer
- JobsDB Processes Activity
- Daemon Log common errors
- Data Domain Device integrity check
- Advanced Volume info list
Lets go ahead and launch the nsrTools.
nsrTools, on launch you will be greeted with the information about your current NetWorker server.
List NSR peer resources mismatches
This feature is used to find if there is a peer information mismatch between the one in the nsrla database and that on the client. It does this by checking the id and certificate with each client that is configured on the NetWorker server by connecting to them. And yes, it is going to take a lot of time again depending on how many clients are configured on our server. To use this feature run the commandnsr peer mismatches list.
nsr peer mismatches list
[nsrTools CLI]» nsr peer mismatches list
2020/05/14 02:01:07 === Starting List NSR Peer Mismatches Engine for cent81.local.lan ===
2020/05/14 02:01:07 INFO: Spawning child nsradmin process to check NSR peer info.resource in the NetWorker server's NSRLA database. The process can take some time ...
2020/05/14 02:01:07 INFO: More info: It checks that the NetWorker instance ID and certificate match those found in the relevant NetWorker client's resource. It connects to each client to check this.
....2020/05/14 02:01:12 DONE: ===>
Validate "NSR peer information" resources
Synopsis: For each NSR peer information resource in cent81.local.lan's NSRLA database, verify the 'NW instance ID' and 'certificate' attributes match those found in the peer's NSRLA resource.
Peer 1 of 1
Hostname: atcspervarl4c.corp.emc.com
Instance ID: 9e8ea9e7-00000004-7574257e-5bc74593-000181d4-634c11d7
Matching certificates: Yes
Summary:
NSR peer information resources checked: 1
RAP connect errors: 0
RAP query errors: 0
Resource mismatches: 0
Resources corrected: 0
Total errors: 0
2020/05/14 02:01:12 INFO: For more information the log file has been creeated on path: /root/go/NetWorker/src/nsrTools/tmp/nsradmin.que.dat
2020/05/14 02:01:12 INFO: Done with List NSR Peer Mismatches Engine for cent81.local.lan. Going back to main meny.
Correct NSR peer resource mismatches
This feature of nsrtools is used to correct the nsr peer resource mismatches, It attempts to correct NSR peer information resource mismatches with the nsradmin -C(upper case) command for thensr peer information query. To use this feature run the
command nsr peer mismatches correct on the nsrtools prompt.
Correct NSR peer resource mismatches
[nsrTools CLI]» nsr peer mismatches correct
2020/05/14 02:04:47 === Starting Correct NSR Peer Mismatches Engine for cent81.local.lan ===
2020/05/14 02:04:47 INFO: To attempt to correct NSR peer information resource mismatches, run the following command on the NetWorker server:
Warning Info:
=============
This operation can compromise the security of a NetWorker server.
If a malicious host could be installed on the server’s network with the same name and IP address of an existing client,
clearing the NSR peer information resource for the host on the server may erroneously delete the legitimate one,
allowing the malicious client to replace the legitimate certificate with its own certificate, thereby allowing it to impersonate
the legitimate client. For this to occur, the legitimate client must be powered off while the malicious client exists on the server’s network.
The customer should be made aware of this risk prior to executing the procedure
QUESTION: Please read info above and confirm with YES? yes
2020/05/14 02:04:50 INFO: Spawning child nsradmin process to check NSR peer info.resource in the NetWorker server's NSRLA database. The process can take some time ...
2020/05/14 02:04:50 INFO: More info: It checks that the NetWorker instance ID and certificate match those found in the relevant NetWorker client's resource. It connects to each client to check this.
.................2020/05/14 02:05:07 DONE: ===>
Validate "NSR peer information" resources
Synopsis: For each NSR peer information resource in cent81.local.lan's NSRLA database, verify the 'NW instance ID' and 'certificate' attributes match those found in the peer's NSRLA resource.
Peer 1 of 1
Hostname: atcspervarl4c.corp.emc.com
Instance ID: 9e8ea9e7-00000004-7574257e-5bc74593-000181d4-634c11d7
Matching certificates: Yes
Summary:
NSR peer information resources checked: 1
RAP connect errors: 0
RAP query errors: 0
Resource mismatches: 0
Resources corrected: 0
Total errors: 0
2020/05/14 02:05:07 INFO: For more information the log file has been creeated on path: /root/go/NetWorker/src/nsrTools/tmp/nsradmin.que.dat
2020/05/14 02:05:07 INFO :Done with Correct NSR Peer Mismatches Engine for cent81.local.lan. Going back to main meny.
Verify NSR Clients
This feature checks the nsr client structure.it will check the client name; client id; client FQDN; IP addresses; reverse lookup results; client port connectivity and time synchronisation. To use this feature run the commandnsr client verify on the nsrtools prompt
nsr client verify
[nsrTools CLI]» nsr client verify
2020/05/14 02:17:14 === Starting Verify NetWorker Clients Engine for cent81.local.lan [KBA #304217] ===
2020/05/14 02:17:14 INFO: Spawning child nsradmin process to Verify NetWorker Client resource in the NetWorker server.
2020/05/14 02:17:14 INFO: More info: For each client resource in the NetWorker server's NSR database (as well as hosts listed in their storage node fields, server network interface fields and aliases), it will check the client name; client id; client FQDN; IP adresses; reverse lookup results; client port connectivity and time synchronisation.
2020/05/14 02:17:14 DONE: ===>
Validate "NSR client" resources
Synopsis: For each NSR client resource in cent81.local.lan's NSR database: verify their 'name', 'aliases', 'storage nodes' and 'server network interface' attributes have properly configured DNS entries then attempt to connect to each address on port 7938. Additionally, compare the NSR client name attribute with the one stored in the client's NSRLA database and verify local and client system times are in sync.
Client 1 of 2
Name: cent81.local.lan
Client ID: aaf05292-00000004-5e4c7ea7-5e4c7ea6-00010c00-cef77729
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Name matches NSRLA resource: Yes
Client time synchronized: Yes
Alias: cent81
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Alias: cent81.local.lan
Skipped
Client 2 of 2
Name: cent81.local.lan
Client ID: aaf05292-00000004-5e4c7ea7-5e4c7ea6-00010c00-cef77729
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Name matches NSRLA resource: Yes
Client time synchronized: Yes
Alias: cent81
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Alias: cent81.local.lan
Skipped
Summary:
NSR client resources checked: 2
Names checked: 2
Name mismatch errors: 0
Time synchronization errors: 0
RAP connect errors: 0
RAP query errors: 0
Forward lookup errors: 0
Reverse lookup errors: 0
Ping errors: 0
Aliases checked: 2
Forward lookup errors: 0
Reverse lookup errors: 0
Ping errors: 0
Server Network Interfaces checked: 0
Forward lookup errors: 0
Reverse lookup errors: 0
Ping errors: 0
Storage Nodes checked: 0
Forward lookup errors: 0
Reverse lookup errors: 0
Ping errors: 0
Total errors: 0
2020/05/14 02:17:14 INFO: For more information the log file has been creeated on path: /root/go/NetWorker/src/nsrTools/tmp/nsradmin.que.dat
2020/05/14 02:17:14 INFO: Done with Verify NetWorker Clients Engine for cent81.local.lan. Going back to main meny.
Verify NSR Storage Node
This feature is similar to the Verify NSR Clients but with this option only the storage nodes are checked instead of all the clients. To use this feature run the command storage node verify on the nsrtools prompt
storage node verify
[nsrTools CLI]» nsr storage node verify
2020/05/14 01:57:23 === Starting Verify NetWorker Storage Nodes Engine for cent81.local.lan [KBA #304217] ===
2020/05/14 01:57:23 INFO: Spawning child nsradmin process to Verify NetWorker Storage Nodes resource in the NetWorker server.
2020/05/14 01:57:23 INFO: More info: For each NSR Storage Node resource in this NetWorker server's NSR database, verify that its name is resolvable using DNS, that it can be connected to and list all configured devices.
2020/05/14 01:57:23 DONE: ===>
Validate "NSR Storage Node" resources
Synopsis: For each NSR Storage Node resource in cent81.local.lan's NSR database: verify its name is resolvable using DNS and list all configured devices
Storage Node 1 of 1
Name: cent81.local.lan
Version: 18.2.0.3
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Device 1 of 1
Name: aftd01
Enabled: Yes
Type: adv_file
NSR Storage Node resources checked: 1
Names checked: 1
Forward lookup errors: 0
Reverse lookup errors: 0
Ping errors: 0
Devices checked: 1
Access errors: 0
Total errors: 0
2020/05/14 01:57:23 INFO: For more information the log file has been creeated on path: /root/go/NetWorker/src/nsrTools/tmp/nsradmin.que.dat
2020/05/14 01:57:23 INFO: Done with Verify NetWorker Storage Nodes Engine for cent81.local.lan. Going back to main meny.
Verify NetWorker Usergroup hosts
This feature verifies NetWorker Usergroup hosts. For each NSR usergroup resource in the NetWorker server’s NSR database, verify hosts entries in the ‘users’ and ‘administrator’ attributes have properly configured DNS entries and then attempt to connect to each address on port 7938. To use this feature use the commandnsr usergroup verify on the nsrtools prompt.
File details here
[nsrTools CLI]» nsr usergroup verify
2020/05/14 01:59:41 === Starting Verify NetWorker Usergroup Engine for cent81.local.lan [KBA #304217] ===
2020/05/14 01:59:41 INFO: Spawning child nsradmin process to Verify NetWorker Usergroup resource in the NetWorker server.
2020/05/14 01:59:41 INFO: More info: For each NSR usergroup resource in the NetWorker server's NSR database, verify hosts entries in the 'users' and 'administrator' attributes have properly configured DNS entries and then attempt to connect to each address on port 7938
2020/05/14 01:59:41 DONE: ===>
Validate "NSR usergroup" resources
Synopsis: For each NSR usergroup resource in cent81.local.lan's NSR database, verify hosts entries in the 'users' and 'administrator' attributes have properly configured DNS entries then attempt to connect to each address on port 7938.
Administrators List
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 1 of 10
Name: Archive Users
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 2 of 10
Name: Monitors
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 3 of 10
Name: Application Administrators
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 4 of 10
Name: Security Administrators
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 5 of 10
Name: VMware FLR Users
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 6 of 10
Name: Users
User Group 7 of 10
Name: Database Administrators
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 8 of 10
Name: Database Operators
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 9 of 10
Name: Operators
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
User Group 10 of 10
Name: Auditors
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Canonical hostname: cent81.local.lan
IP Address: 10.2.192.225 (0.000 sec)
Host Name (reverse lookup): cent81.local.lan (0.000 sec)
Ping (port 7938): Success (0.000 sec)
Summary:
NSR usergroup resources checked: 10
Hosts checked: 37
Forward lookup errors: 0
Reverse lookup errors: 0
Ping errors: 0
Total errors: 0
2020/05/14 01:59:41 INFO: For more information the log file has been creeated on path: /root/go/NetWorker/src/nsrTools/tmp/nsradmin.que.dat
2020/05/14 01:59:41 INFO: Done with Verify NetWorker Usergroup Engine for cent81.local.lan. Going back to main meny.
Thank you for visting www.crazyrov.com, you can also check out my YouTube channel - crazyRov Studios for Data protection and cloud related technical videos.
