As-Deployed Configuration Generator (ACG)

Users Guide

Date: October 29, 2021

Abstract
This document is an introduction and reference manual for users of the As-Deployed
Configuration Generator (ACG). The target audience is composed of Dell Technologies Solution
Architects and Delivery personnel.

1
Table of Contents
Introduction......................................................................................................................... 4
Overview, Requirements and Process Description (When do I use the ACG) ............... 5
Running the As-Deployed Configuration Generator Guide Generator ........................... 6
Invoking application ....................................................................................................................................... 6
Entering Data ................................................................................................................................................ 6
Profiles .......................................................................................................................................................... 7

Avamar ................................................................................................................................ 8
Installation Details ......................................................................................................................................... 8
Logging into an Avamar grid and generating an ACDC input file ................................................................. 9
Overview and Execution .......................................................................................................................... 9
Requirements for Performing this Procedure ........................................................................................ 10
ACDC Script Package (Optional) ........................................................................................................... 10
Load and run the acdc.pl script .............................................................................................................. 11
Materials required to perform this activity .............................................................................................. 12
Establish a Connection to the Avamar® ................................................................................................ 12
SSH into the Avamar® Utility Node or Single Node Server .................................................................. 12
Load the dpn keys .................................................................................................................................. 14
Move acdc.pl script onto Avamar Utility Node ....................................................................................... 14
Set the Permissions to executable ........................................................................................................ 14
Run the acdc.pl script ............................................................................................................................ 15
Collect ACDC.xml script output information ........................................................................................... 16
Data Domain...................................................................................................................... 17
Installation Details ....................................................................................................................................... 17
Backup/Archive Apps .................................................................................................................................. 18
Server Manager .......................................................................................................................................... 19

Elastic Cloud Storage (ECS) ............................................................................................ 20

Installation Details ....................................................................................................................................... 20
Getting an Input file from the ECS Appliance ............................................................................................. 21
Pre-Requisites ....................................................................................................................................... 21
Steps to Generate and Acquire Input File .............................................................................................. 21
NetWorker ......................................................................................................................... 22
Installation Details ....................................................................................................................................... 22
Generating an NSRDump Output ............................................................................................................... 22

PowerProtect Data Protection Series Appliance (IDPA) ................................................ 23

 As-Deployed Configuration Generator

Installation Details ....................................................................................................................................... 23

Generating an XML (.dump) Output ............................................................................................................ 23

PowerScale ....................................................................................................................... 24
Installation Details ....................................................................................................................................... 24
Getting an Input file from the PowerScale Cluster ...................................................................................... 25
Pre-Requisites ....................................................................................................................................... 25
Steps to Generate and Acquire cfg_capture Output File ....................................................................... 25
PowerStore........................................................................................................................ 26
Installation Details ....................................................................................................................................... 26
Getting an Input file from the PowerStore Cluster ...................................................................................... 27
Pre-Requisites ....................................................................................................................................... 27
Steps to Generate and Acquire array_config_collection(.tar.gz) Output File ........................................ 27
VxRail ................................................................................................................................ 29
Installation Details ....................................................................................................................................... 29
Generating Full JSON File or JSON and XML Output Files ....................................................................... 30

Generating the As-Deployed Configuration ................................................................... 33

Enable Macros to Update References and Tables ..................................................................................... 35

Emailing the As-Deployed Configuration ....................................................................... 37

Settings ....................................................................................................................................................... 37

Accessing the client version of ACG for Dark Sites ...................................................... 38

Installation (Desktop Version Only) ............................................................................................................. 39

Support, Issues and Troubleshooting ............................................................................ 40

Important Notes ........................................................................................................................................... 40
Trouble Shooting ......................................................................................................................................... 41
Known Issues .............................................................................................................................................. 47
Report History ............................................................................................................................................. 49
Support ........................................................................................................................................................ 50
Version and Build information ..................................................................................................................... 50

DELL TECHNOLOGIES CONFIDENTIAL

3 of 50
 As-Deployed Configuration Generator

Introduction
The As-Deployed Configuration Generator (ACG) exists to help field personnel document the
configuration of a Data Domain, Avamar, NetWorker, ECS, PowerScale, PowerProtect Data Protection
Series Appliance, PowerStore and VxRail installation. It produces a customer deliverable from an input
file directly from the Data Domain system, Avamar grid, NetWorker instance, ECS appliance, PowerScale
cluster, VxRail appliance and PowerProtect Data Protection Series Appliance.
Inputs:
• GUI
• One of the following:
• Avamar ACDC (Avamar Data Collector) Script output file
• Data Domain Auto support file
• Elastic Cloud Storage (ECS) script output file
• NetWorker NSRDump output file
• PowerProtect Data Protection Series Appliance (IDPA) output file
• PowerScale script output
• PowerStore output files (tar.gz) or JSON file
• VxRail Full JSON or JSON and XML output files
Outputs:
• Word Document.
Regular updates will occur for the ACG tool. The latest version of the as-deployed configuration
generator will be automatically available via a web browser. The client version can be downloaded from
within the Web ACG Tool.

Note: The Data Domain Auto support file, the NetWorker NSRDump file, the VxRail JSON and XML files,
PowerScale python script, ECS Python script, PowerProtect Data Protection Series Appliance XML/DUMP
file, PowerStore tar.gz and json and the Avamar acdc.pl script will be referred to as input files for the
remainder or this document.

DELL TECHNOLOGIES CONFIDENTIAL

4 of 50
 As-Deployed Configuration Generator

Overview, Requirements and Process Description (When do I use the

ACG)
The stated purpose of the ACG is to generate a customer deliverable at the conclusion of an installation.
It should be one of the final tasks performed before you leave a customer location. You should run the
ACG prior to leaving the customer location to ensure that you have a good file with which to populate the
output form the deliverable. In some cases, getting an output file after leaving the site is very difficult.
Each Dell Technology may have slightly different requirements for generating a guide. As an example,
with Avamar, you are required to run an external script called the acdc.pl script to generate a file used for
the ACG. Whereas with Data Domain the ASUP is used as input and is automatically generated and
simply is pulled from the DD systems. With VxRail, it uses both the JSON and XML files respectively and
are manually collected from the appliance.
After the hardware (Avamar, DD, ECS, PowerScale, VxRail and PowerProtect Data Protection Series
Appliance, PowerStore) or software (NetWorker) has been installed and configured:
• (Avamar, PowerScale and ECS) Get the acdc.pl script, PowerScale cfg_capture,
ECSAsBuiltConfigCapture.py from the ACG via the Script links
• (Avamar, PowerScale and ECS) Install and run the Script (avamar acdc.pl, powerscale cfg_capture
or ECSAsBuiltConfigCapture.py) on the system
• (PowerStore Only) Pull the tar.gz file from the system
• Optionally, Convert the tar.gz file into a JSON file using the powerstore designer conversion utility
• (NetWorker Only) Run the NSRDump command
• Remove the input file from the Avamar grid (acdc.xml output), Data Domain system (ASUP),
NetWorker Server (NSRDump), VxRail Appliance (xml and json), ECS rack (script json output),
PowerScale Cluster (script json output) and PowerProtect Data Protection Series Appliance
(XML/DUMP output)
• Run and fill out the ACG GUI
• When asked for the input file use the output file from the system to run the ACG
• Deliver the output to your Project Manager so that he can distribute it to the client

DELL TECHNOLOGIES CONFIDENTIAL

5 of 50
 As-Deployed Configuration Generator

Running the As-Deployed Configuration Generator Guide Generator

Invoking application
To invoke the application, go to the following URL https://etools-acg.dell.com/. The first tab that will be
display is the Read First tab. The read first tab contains the Frequently Asked Questions (FAQ), links to
features, training and support as well as diagrams that show the usage of the application and its inclusion
into the field workflow.

Entering Data
When started, the application has five tabs Read First, Dell EMC, Customer, Select Product
(encompassing Data Domain, Avamar, NetWorker, VxRail, ECS, PowerScale, PowerProtect Data
Protection Series Appliance, PowerStore and Generate AC. When selected each tab displays elements
available for editing. It contains edit controls for defining properties strings.

Figure 1

A red border on text field indicates that field is required or indicates the current value in the field is invalid.
A required field may not be blank. In addition, certain fields may not contain certain values, as an
example a phone number may not contain letters. See tooltips on text fields for context sensitive help.
See Figure 2.

Figure 2

DELL TECHNOLOGIES CONFIDENTIAL

6 of 50
 As-Deployed Configuration Generator

Profiles
This application uses profiles to save all the information entered for future reference or to use in the
creation of additional reports. On the Customer screen, after entering all fields’ information will be saved
after changing to different tab.
For example, enter some information in Dell EMC tab with all required field then change tab to Customer
tab, then it will save all entered data automatically.

Note: You may enter multiple SO number’s comma separated into the SO# field.

To embed the customer logo image onto the cover page of the ACG, simply select the Manage Images
button, upload, and select the image file from the drop down. When the thumbnail image appears, this
indicates the selected image will appear on the ACG Report cover page. See Figure 3

Figure 3

Information such as Dell EMC Address, SE and Implementation Consultant are shared across profiles as
they generally stay the same. If you have multiple machines or wish to regen a report, simply select the
profile, and activate it via the pull-down in the Customer Info box on the customer tab and all information
will be reloaded. If you wish you can remove a profile, click the button next to the pull-down in the
Customer Info box on the customer tab and you may edit or delete pull down entries. See Figure 4

Figure 4

DELL TECHNOLOGIES CONFIDENTIAL

7 of 50
 As-Deployed Configuration Generator

Avamar
Installation Details
By using the Avamar tab, users can select Installation and Integration details and specify installation
issues. See Figure 5

Figure 5

DELL TECHNOLOGIES CONFIDENTIAL

8 of 50
 As-Deployed Configuration Generator

Logging into an Avamar grid and generating an ACDC input file

Overview and Execution
Avamar Configuration Data Collector (ACDC) script helps field personnel collect the configuration details
of an Avamar system as part of the final customer deliverable.
• The Avamar Configuration Data Collector script (ACDC.pl); should be executed on a new and or
existing Avamar Implementation to collect configuration details.
• The ACDC Script will produce an acdc.xml output file, imported into the As-Deployed Configuration
Generator (ACG).
• The ACDC script is a non-intrusive data collection script, which must be executed on either an
Avamar Data Store or Avamar Virtual Edition server.
The procedure execution steps include the following tasks:
• IS launches the As-Deployed Configuration Guide (ACG) Parser Tool
• IS get acdc script from the Avamar or Generate AC tab within the ACG (Get Data Collector script link)
• IS FTPs acdc.pl script to Avamar Grid Utility Node
• IS runs acdc.pl script on Avamar grid to collect configuration XML data output
• IS utilizes the ACG tool to import xml data output, and generate ACG files
• The acdc script will produce an .xml output file, imported into the As-Deployed Configuration
Generator (ACG).
• IS emails ACG files to CS (Cc’s PM and SE)

DELL TECHNOLOGIES CONFIDENTIAL

9 of 50
 As-Deployed Configuration Generator

Requirements for Performing this Procedure

To complete this procedure, you will need to obtain the latest acdc.pl script from the Avamar tab in the
ACG by clicking ACDC Script and Readme link. See Figure 6

Figure 6

Click the download button to download ACDC.pl script to your local system in a directory of your
discretion. Please follow the Readme instructions in the pop-up window.

ACDC Script Package (Optional)

The ACDC script has been added to the Avamar kickstart image starting with v19.3. The script version is
3.0.8-1, which includes the update to fix the bug with patched proxy nodes. Refer to Figure 12 or Central
Solutions to download this package. Disregard these procedures if not using the ACDC Script Package.

Check if ACDC is already installed and up to date

• Log into the Utility node as the admin user using PuTTY or another SSH client
• Switch to the root user
su -
• Check if the script is already installed
which acdc.pl
a. This should return the location as /usr/local/avamar/bin/acdc.pl
b. If it is not installed, jump ahead to the Install steps

DELL TECHNOLOGIES CONFIDENTIAL

10 of 50
 As-Deployed Configuration Generator

• Check the script is up to date

acdc.pl –version

a. If the installed version is current, skip the Install steps

Install the ACDC package
• Use WinSCP to upload the ACDC RPM file to the Avamar Utility node into the /tmp directory
• Log into the Utility node as the admin user using PuTTY or another SSH client
• Switch to the root user
su -
• Install the package
rpm -ivh --force /tmp/acdc-3.0.8-1.noarch.rpm
• Verify the script is installed by getting the version
acdc.pl --version

Load and run the acdc.pl script

The acdc.pl script is executed at the conclusion of any service event on an Avamar® system to determine
the current configuration status of a grid. The script has nearly 50 different checks contained within that
will help to provide a stable environment when performing tasks such as (but not limited to)
implementations, capacity adds, code upgrades, FRU replacements, etc.
• The acdc.pl script is applicable to Avamar® software versions: 6.x, 7.x, 18.x and 19.x
• Applicable to Hardware Versions: Avamar® ADS versions Gen4/4S/4T and Avamar Virtual Edition.
• Currently ADS Hardware versions: Gen1, Gen2, Gen3, and Avamar® Servers running on customer-
supplied hardware are NOT Supported.

Note: For instances of customer supplied hardware the script will not return any hardware errors. All
output will be limited to Avamar software checks only.

DELL TECHNOLOGIES CONFIDENTIAL

11 of 50
 As-Deployed Configuration Generator

Materials required to perform this activity

Note: Due to the frequency in which the acdc.pl script is updated, always be certain to obtain the latest
copy from the Avamar tab within the ACG. This will ensure that the most up to date checks are run on the
Avamar® server.

• Script Name: acdc.pl

• Secure copy utility. Recommend downloading WinSCP (http://winscp.net/) or pscp from the PuTTY
package (http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html)

Establish a Connection to the Avamar®

Note: This step requires access to the Avamar® Server and an Ethernet connection on the customer’s
network.

1. Working with the customer contact, establish an Ethernet connection to the customers’ network.
2. This connection can be virtual with Zoom, using ESRS or physical by connecting to the customer’s
network directly.

SSH into the Avamar® Utility Node or Single Node Server

3. Open a ssh client such as PuTTy by clicking on Start → Run and typing putty.exe on the command
line then clicking OK. Figure 7

Figure 7

Note: If PuTTy.exe is not in your system path, you may receive an error message indicating that the
file or program cannot be found. In this case, open windows explorer and browse to the following path:
C:\AvamarProcedureGenerator\Repository\Tools.
Note: Locate the file PuTTy.exe and double click on it to open the PuTTy application.

4. In the putty window that appears, input the IP Address of the Avamar Utility node that you are
connecting to and then click Open to launch the ssh session. See Figure 8.

DELL TECHNOLOGIES CONFIDENTIAL

12 of 50
 As-Deployed Configuration Generator

Figure 8

5. In the ssh window that opens, you should be prompted to accept the security key, click yes to
continue, and then input the appropriate logon credentials.
6. Login to the Utility node as user admin:

Note: If you are unfamiliar with the login credentials, refer to the Dell EMC® Avamar® Procedure.
Generator → Information Sheet → User Name and Password reference document for proper
credentials.

The banner specifies that you are on the utility node, as shown in the following example.
*****************************************************************
* *
* This is an Avamar Utility Node *
* *
* Please read the documentation before performing *
* any administrative functions on this node. *
* For help, contact EMC at 877.534.2867 (USA only) or *
* http://support.emc.com. *
* *
*****************************************************************

DELL TECHNOLOGIES CONFIDENTIAL

13 of 50
 As-Deployed Configuration Generator

Load the dpn keys

7. In the ssh shell logged in as the admin user, type the following commands to load the SSH keys:
ssh-agent bash
For Avamar v7.2.x and earlier, type: ssh-add ~admin/.ssh/dpnid
For Avamar v7.3.x and later, type: ssh-add ~root/.ssh/rootid
8. Type the following command to verify that the keys are loaded:
ssh-add -l
If the keys were successfully loaded you will see output similar to:
1024 1b:af:88:95:7a:d8:a9:16:fb:cb:9e:0e:49:32:a3:cd /home/dpn/.ssh/dpnid (DSA)

If the keys were not loaded, the the output will say:
Could not open a connection to your authentication agent.

-or-
The agent has no identities.

Move acdc.pl script onto Avamar Utility Node

9. Move the acdc.pl file from your local PC to the Avamar Utility node by using the following command:
mv ~admin/acdc.pl /usr/local/avamar/bin:

Set the Permissions to executable

10. Set the permissions to executable on the acdc.pl file by typing the following command:
chown root:root /usr/local/avamar/bin/acdc.pl
chmod 700 /usr/local/avamar/bin/acdc.pl
11. Verify that the permissions are now set to executable by typing the following command:
ls -l /usr/local/avamar/bin/acdc.pl
Output will look similar to the following:
-rwx------ 1 root 160124 Jun 20 15:40 acdc.pl

Note: Notice the permissions bit on the left of the example string. The file is listed as executable by the
‘x’ listed in the permissions bits.

DELL TECHNOLOGIES CONFIDENTIAL

14 of 50
 As-Deployed Configuration Generator

Run the acdc.pl script

12. Run the acdc.pl script by typing the following command:
./acdc.pl
The script will output any errors it finds with a recommendation where possible to fix the problem. On
every check that is performed the script will be output to the screen with a Collected or Not
Configured message. The script also creates two files, acdc.xml which containts detailed
information about the configuration checks performed and produces the .xml output used to import
into the As-Deployed Configuration Generator producing the Avamar Configuration Guide . The
second file is: acdc.log. This log file is used for debugging the script. If any issues are identified by
the script, this log file is required as part of the materials needed for escalation.
Output will look similar to the following:
root@av73u:/usr/local/avamar/bin/#: ./acdc.pl
Avamar Configuration Data Collector (ACDC) 3.0.4.1
Localtime 2016/07/18-22:02:55CDT
Check: SSH Agent context Available
Check: Avmaint Responding
Check: MC Database Access Established
Avmaint: Config Loaded ... Parsed
Avmaint: Nodelist Loaded ... Parsed
Avmaint: Networkconfig Loaded ... Parsed
Avmaint: Licensing Loaded ... Parsed
GC: Node Count 5
GC: System Name AV73U.DALLASRDC.COM
GC: System ID 1468883011@00:60:16:70:17:90
GC: Customer Number Avamar
GC: Customer Asset ID A-2013027986
GC: Licensed Capacity 2.02 TB
GC: Version GSAN 7.3.0-8004
GC: Version EMS 7.3.0-8004
GC: Version MCS 7.3.0-8004
GC: Authentication Local Collected Users:0 Domains:0
GC: Authentication LDAP Maps Completed
GC: Authentication LDAP.conf Collected 1
GC: Email Home Collected 1
GC: Maintenance Windows Collected 3
GC: Replication Not Configured
GC: SNMP Service Not Configured
MC: Clients Collected 0
MC: Groups Collected 1
MC: Group Members Collected
MC: Datasets Collected 6
MC: Retentions Collected 1
MC: Schedules Collected 1
NC: Hardware Maker emc
NC: OS Version Collected 5
NC: Model, Serial, Part Collected 5/5/5
NC: Network Collected
NC: DNS Servers Collected 5
NC: Interface Listing Collected 5
NC: Interface ifconfig Collected 5
NC: Interface ethtool Collected 5
NC: Interface modprobe Collected 5
NC: Interface bonding Collected 5
NC: IPMI Drivers Collected
NC: NTP Servers Collected 5

DELL TECHNOLOGIES CONFIDENTIAL

15 of 50
 As-Deployed Configuration Generator

NC: Timezone Collected 5

NC: Static Hostnames Collected
Opt: Downloader Service Not Available
Opt: VMWare vCenter Collected 0
Opt: VMWare Proxies Collected 0
Opt: VMWare Machines Collected 0
Opt: Extended Retention Not Available
XML: Output Saved (Saved to /tmp/acdc.xml & acdc.log)
XML: Validate Passed

ACDC Completed

13. Once the acdc.pl script is finished, review the output displayed on screen for any checks that reported
a status other than “Collected”. All checks reported other than “Not Configured” will need to be
investigated, prior to continuing with your next activity. Both files are located in the /tmp directory
instead of the ~admin/acdc/ directory as previous releases.

Note: All “FAILED” checks need to be addressed before continuing with your activity. If you are unable to
resolve the issues on your own, follow your normal escalation process to have an SR opened with Dell
EMC Customer Support.

14. Close the SSH session and the DOS box used for this activity.

Collect ACDC.xml script output information

After you complete running the acdc.pl script, the acdc.xml output needs to be collected from the Avamar
Utility Node and copied to your system where the ACG is installed.
To collect and copy the acdc.xml & acdc.log output files:

15. Ensure you are logged into the Avamar Utility Node as admin
16. Use WinSCP or PSCP or an equivalent program to copy the acdc.xml & acdc.log files from the /tmp
directory on the Avamar Utility node to a folder to your desktop PC
17. Using WinScp or pscp copy the log files from the Avamar Utility node by copying and pasting the
following command from your Windows command prompt:
pscp -pw <password> admin@<IP Address>:/tmp/acdc* c:\acdc

Output will look similar to the following:

C:\acdc>pscp -pw <password> admin@<IP Address>:/tmp/acdc* c:\acdc

acdc.xml | 12 kB | 12.4 kB/s | ETA: 00:00:00 | 100%
acdc.log | 540 kB | 90.1 kB/s | ETA: 00:00:00 | 100%

DELL TECHNOLOGIES CONFIDENTIAL

16 of 50
 As-Deployed Configuration Generator

Data Domain
Installation Details
The following screen shows the details associated with the Data Domain implementation engagement
and the environment in which the system is installed. See Figure 9

Figure 9

DELL TECHNOLOGIES CONFIDENTIAL

17 of 50
 As-Deployed Configuration Generator

Backup/Archive Apps
The Backup/Archive Apps screen allows the user to specify and select the backup/archive software that is
writing to the Data Domain. The Backup Software Manager allows the user to rename and remove
entries. See Figure 10

Figure 10

DELL TECHNOLOGIES CONFIDENTIAL

18 of 50
 As-Deployed Configuration Generator

Server Manager
The application allows the server to be created and a minimum of a DNS name is required for the server.
From the manager you can create multiple servers and rename or delete them as required per customer
(profile). You can navigate to these servers by pulling down and selecting the required server. You may
also add additional servers when you finished entering a server by click on the Add Server button on the
input screen. See Figure 11

Figure 11

DELL TECHNOLOGIES CONFIDENTIAL

19 of 50
 As-Deployed Configuration Generator

Elastic Cloud Storage (ECS)

Installation Details
The following screen shows the details associated with the Isilon implementation engagement and the
environment in which the system is installed. See Figure 12

Figure 12

DELL TECHNOLOGIES CONFIDENTIAL

20 of 50
 As-Deployed Configuration Generator

Getting an Input file from the ECS Appliance

Pre-Requisites
• Network access to Rack Master node (Node1) in the VDC
• File transfer utility like winscp, filezilla or pscp
• SSH client like putty
• Password for “admin” and “emcservice” user. Default password for both is “ChangeMe”

Steps to Generate and Acquire Input File

1. Open a putty session to Rack Master and login as “admin”.
2. Verify the ECS version using “sudo -i xdoctor --ecsversion” command from shell. If this is an
unsupported version, contact developer at https://psapps.emc.com/central/help/request-support
Download the script from this page and transfer to rack master node using a suitable file transfer utility.
You will need to unzip the file to extract the python script. Download the script from within the ACG tool
on the ECS product tab (https://etools-acg.dell.com/ecs).
3. Run the script “python ECSAsBuiltConfigCapture2.x.py” (where x equals the latest versions of the
script) from shell
4. Enter password for “emcservice” user
5. Script finishes collection and prints the name of output json file See Figure 13
6. Json file has ECS version, PSNT and SWID in the name and is stored in your present working
directory.
7. Transfer json output file to your PC
8. Use the output from the script as an input to the ACG tool
9. See the example script output in Figure 13

Figure 13

DELL TECHNOLOGIES CONFIDENTIAL

21 of 50
 As-Deployed Configuration Generator

NetWorker
Installation Details
The following screen shows the details associated with the NetWorker implementation engagement and
the environment in which the NetWorker server is installed. See Figure 14

Figure 14

Generating an NSRDump Output

NetWorker provides the command nsrdump, which produces the output file that the ACG uses as an
input to the As-deployed Configuration. The nsrdump utility is located on the NetWorker server in the
<INSTALL_PATH>/nsr/bin directory.
To create the file:

1. Login to the NetWorker server

2. If Logging in from a Windows Operating system open a Command Windows as Administrator

a. Login into the NetWorker Authentication server as a user with Administrator privileges
b. nsrlogon –u Administrator (Syntex may be: NSRLOG*I*N –u Administrator) (This step may
be optional)
3. From the command line issue the following command:

a. nsrdump -xefn –o <FILENAME>.xml

1. <FILENAME> is the name of the dump file created (Example: Nsrdump –xfen –o
acgdump.xml)
4. The output file generated will be found under the nsr/applogs/rh directory.
5. Move the file to your computer using a file transfer tool of your choice.

DELL TECHNOLOGIES CONFIDENTIAL

22 of 50
 As-Deployed Configuration Generator

PowerProtect Data Protection Series Appliance (IDPA)

Installation Details
The following screen shows the details associated with the PowerProtect Data Protection Series
Appliance (IDPA) implementation engagement and the environment in which the IDPA appliance is
installed. See Figure 15

Figure 15

Generating an XML (.dump) Output

IDPA provides the output file that the ACG uses as an input to the as-deployed configuration.
To create the file:

1. Login to the IDPA Appliance

2. Use WinSCP or PSCP or an equivalent program to copy the DataProtectionConfiguration.xml (.dump)
file located in /usr/local/dataprotection/var/configmgr/server_data/config/tmp directory to a folder to
your desktop PC
3. Use the DataProtectionConfiguration.xml file as the input to the ACG Tool to generate your IDPA As-
Deployed Configuration Report

DELL TECHNOLOGIES CONFIDENTIAL

23 of 50
 As-Deployed Configuration Generator

PowerScale
Installation Details
The following screen shows the details associated with the PowerScale implementation engagement and
the environment in which the system is installed. See Figure 16

Figure 16

DELL TECHNOLOGIES CONFIDENTIAL

24 of 50
 As-Deployed Configuration Generator

Getting an Input file from the PowerScale Cluster

Pre-Requisites
• Network access to Cluster
• File transfer utility like winscp, filezilla or pscp
• SSH client like putty
• Password for “root”

Steps to Generate and Acquire cfg_capture Output File

Open a putty session to the Cluster and login as “root” Download the script from this page and transfer to
one of the nodes using a suitable file transfer utility. Download the script from within the ACG tool on the
PowerScale product tab https://etools-acg.dell.com/powerscale
1. Place the cfg_capture script in the following folder: /ifs/data/Isilon_Support/
2. Run the script “python ps_cfg_capture-<timestamp>.pyz” The script finishes collection and
prints the name of output json file See Figure 17
3. The JSON file has the Customer Name and the Date the script was executed.
4. Transfer json output file to your PC
5. Use the output from the script as an input to the ACG tool

Figure 17

DELL TECHNOLOGIES CONFIDENTIAL

25 of 50
 As-Deployed Configuration Generator

PowerStore
Installation Details
The following screen shows the details associated with the PowerScale implementation engagement and
the environment in which the system is installed. See Figure 18

Figure 18

DELL TECHNOLOGIES CONFIDENTIAL

26 of 50
 As-Deployed Configuration Generator

Getting an Input file from the PowerStore Cluster

Pre-Requisites
• Network access to Cluster
• File transfer utility like winscp, filezilla or pscp
• SSH client like putty (CLi collection)

Steps to Generate and Acquire array_config_collection(.tar.gz) Output File

Direct from a cluster, via the service CLI:

1. SSH to Cluster
2. Login as service user (built-in account, port 22).
3. Create a child directory (mkdir cc)
4. svc_arrayconfig run -f json --output cc --type full --config
/cyc_host/cyc_service/conf/ConfigCaptureConfig_ProDeploy.json
5. Move the created JSON files to the current directory. (mv cc/* .)
6. Verify that in the region of 60 new JSON files have been created in the current directory. (ls *.json
|wc -l)
7. Tar/zip the json files (tar -zcvf array_config_collection.tar.gz *.json)
8. Verify that the tar-ball was created successfully. It should be tens of KB in size and should contain in
the region of 60 files. (tar -ztvf array_config_collection.tar.gz |wc -l)
9. Open WinSCP and download the file from the same directory
10. In either WinSCP or SSH (see example command), remove all unnecessary by-products of this
process. Be careful not to remove artifacts that might have been there beforehand. Be selective in
what to delete! e.g. (rm -Rf *.json & rmdir cc)

Or direct from a cluster, via the PowerStore Manager GUI:

1. From the Settings menu,

2. Navigate to Support Materials,
3. Click Start Collection
4. Provide a description, select Appliances, and un-check the boxes highlighted, before clicking Start.
5. Collection will take several minutes.
6. When it is finished, a new entry will be visible in the Support Materials Library.
7. Select the new item and click Download.
8. In a multi-appliance cluster, there may be multiple files available for download. Select and download
one of the files (these are large enough). The filename will end ***_service-data.tgz.

DELL TECHNOLOGIES CONFIDENTIAL

27 of 50
 As-Deployed Configuration Generator

Or extracting an extended config capture from a service data file:

1. Open the service-data.tgz file in a tool of your choice, e.g. 7zip

2. Open the service-data.tar file which has two directories: node_a and node_b
3. Open node_a
4. If there is a sub-directory called config_capture_management_data, open this otherwise, go back and
try node_b. (not to be confused with config_capture_local_data,
config_capture_management_internal_data, or config_capture_metrics_data)
5. Inside config_capture_management_data, there are many .json files, extract these (to your local
drive)
6. add them to a new tar archive (e.g. <customer name>_<serial
number>_config_capture_management_data.tar)
7. add that to a gzip archive (e.g. <customer name>_<serial
number>_config_capture_management_data.tar.gz)

Optional, Steps to Convert the tar.gz file into a JSON file: (TBD)

DELL TECHNOLOGIES CONFIDENTIAL

28 of 50
 As-Deployed Configuration Generator

VxRail
Installation Details
The following screen shows the details associated with the VxRail implementation engagement and the
environment in which the VxRail appliance is installed. See Figure 19

Figure 19

DELL TECHNOLOGIES CONFIDENTIAL

29 of 50
 As-Deployed Configuration Generator

Generating Full JSON File or JSON and XML Output Files

VxRail provides for the ability to produce the JSON and XML output files for versions prior to 7.0.241 and
a Full JSON File (includes XML configuration details) for version 7.0.241 and later, that the ACG uses as
an input to the As-Deployed Configuration Generator.
To create the Full JSON file (supported for version 7.0.241 and after):

1. After the VxRail appliance has been successfully installed, log into the vCenter, click on the VxRail
cluster, then click Configure and then under VxRail select Troubleshooting. Click the Create log
bundle. Select VxRail Manager only then click Generate. (NOTE: The Full JSON is NOT
automatically generated as part of the Day 1 bring-up process as the previous JSON & XML file set.
You must generate a log bungle collection for the Full JSON file to be generated. This is functionality
that works as designed and is basically a Day 2 operation/activity.) See Figure 20.

Figure 20

DELL TECHNOLOGIES CONFIDENTIAL

30 of 50
 As-Deployed Configuration Generator

After the log bundle has been generated, SSH into VxRail manager VM and copy the file from the
following location : /var/lib/vmware-marvin/info_for_acg.json
2. Download and save a copy of the VxRail Configuration JSON file (info_for_acg.json).
3. Move or Copy both the info_for_acg.json output file(s) generated from the VxRail appliance to
your local laptop into a designated directory. Direct the ACG Tool to this location to generate your As-
Deployed Configuration Guide report.

To download the JSON file (GUI or Command Line) for versions prior to 7.0.241:

1. Via the VxRail Manager GUI

Launch the VxRail Configuration VxM GUI and complete the Validation Phase. Prior to initiating the
Build Phase select, the DOWNLOAD JSON button to collect the .JSON file from the VxRail appliance.
See Figure 21

Figure 21
2. Via the command line
Log into vxrial manager mystic / su (just like you're going to run the python script)
Enter the following commands:
cd /var/lib/vmware-marvin/
cp config.json VxRailConfigurationJSON.json
chown mystic VxRailConfigurationJSON.json
Using WINSCP or PSCP or an equialent program (same login as python script)
Log into the vxrail manager IP and mystic via WINSCP/PSCP
Go to ROOT (hit the folder at the top of the list with the up arrow until you hit "root")
Navigate and select /var/lib/vmware-marvin/ folder
Copy VxRailConfigurationJSON.json file to PC
Rename to standard file name (add store name and spaces)

Note: In case the cluster is already built, you must get the JSON file via SSH CLI.

DELL TECHNOLOGIES CONFIDENTIAL

31 of 50
 As-Deployed Configuration Generator

To create the XML file (version priors to 7.0.241):

1. Launch the VxRail Manager Dashboard, select > Support > View the Last Configuration Sent > Data
Details and Open XML data in a new window and save as the .XML file
Move or Copy both JSON and XML output files generated from the VxRail appliance to your local laptop
into a designated directory.
2. After the VxRail appliance has been successfully installed, log into the vCenter Server. Select the
VxRail Cluster Monitor tab and select Last Configuration Data Sent under VxRail. Click DOWNLOAD
and save a copy of the VxRail Congiuration XML file.

Figure 22 VxRail Plugin

DELL TECHNOLOGIES CONFIDENTIAL

32 of 50
 As-Deployed Configuration Generator

Generating the As-Deployed Configuration

Once all required fields are completed within the product tab(s), choose the Generate AC tab. To gen an
As-deployed configuration with information gathered from the DD auto support file, Avamar acdc.xml
input file, NetWorker NSRdump file, IDPA XML/DUMP or VxRail Full JSON or JSON and XML files,
choose the input file(s) then click on Generate button. The As-deployed Configuration output file is saved
in the browser and to your local system. Unlike other products to be parsed, when parsing the VxRail Full
JSON or JSON and XML files, the Generate AC input fields will require input of both files. See Figure 23

Figure 23

For detailed instructions on how to log into the Avamar grid, generate output from the acdc script and get
the input file for use in the ACG please see Logging into an Avamar grid and generating an ACDC input
file.
For information about how to generate an NSRDump file on a NetWoker server, please see the
Generating an NSRDump Output.
For information about how to generate Full JSON or JSON and XML file(s) on a VxRail Appliance, please
see the Generating Full JSON File or JSON and XML Output Files.
For information about how to generate an ECS file on a ECS server, please see the Getting an Input file
from the ECS Appliance.
For information about how to generate an PowerScale file on a PowerScale server, please see the
Getting an Input file from the PowerScale Cluster.
For information about how to generate an IDPA file on a IDPA server, please see the Generating an XML
(.dump) Output.
For information about how to generate a PowerStore file on a PowerStore cluster, please see Getting an
Input file from the PowerStore Cluster.

DELL TECHNOLOGIES CONFIDENTIAL

33 of 50
 As-Deployed Configuration Generator

Input and output file location can be modified/changed/saved by going to Edit menu > preferences > or by
pressing Alt + P. Details on how to change locations in the Preferences screen are shown.
To embed the implementation diagram image into the ACG, simply check the Attach Images button,
browse, upload, and select the image file. This selected image will appear in the Implementation Design
Topology section within on the ACG Report. See Figure 24

Figure 24

If any of the required fields were omitted or are incorrect, when the generate button is pressed you will be
presented with dialog listing the fields that must be completed or corrected before a report can be
generated. See Figure 25

Figure 25

DELL TECHNOLOGIES CONFIDENTIAL

34 of 50
 As-Deployed Configuration Generator

Enable Macros to Update References and Tables

After the report is generated, MS-Word will show a security warning stating, “Macros have been disabled”.
Click the Options button and enable all macros. Enabling macros will update all tables and references
within the report. See Figure 26

Figure 26

DELL TECHNOLOGIES CONFIDENTIAL

35 of 50
 As-Deployed Configuration Generator

If the security warning stating, “Macros have been disabled” does not appear you must open the report,
select all text (ctrl + a) and click update field and update entire table. See Figure 27

Figure 27

DELL TECHNOLOGIES CONFIDENTIAL

36 of 50
 As-Deployed Configuration Generator

Emailing the As-Deployed Configuration

Pressing the Send button will launch a dialog box to choose an As-deployed configuration to email with
Microsoft Outlook. If a corresponding sales force xml file exists, it will be attached automatically. Email
fields will be pre-populated where possible; however, it is recommended that the user performs a brief
check before sending the email. If Outlook is not correctly installed, a dialog box will be displayed
instructing the user on how to proceed. See Figure 28

Figure 28

Settings
The Settings screen is found under the User menu. See Figure 29

Figure 29

DELL TECHNOLOGIES CONFIDENTIAL

37 of 50
 As-Deployed Configuration Generator

Accessing the client version of ACG for Dark Sites

While the standard method of generating an As-deployed configuration is via the web interface there is a
standalone application that can be installed if nessecary. This version of the ACG works in the same way
as the web-based version but, with no connection to outside databases or internet needed. The purpose
of this alternate version is to enable high security environments the option to generate standardized
documentation at the conclusion of a professional service engagement. The figure below shows where
you can download the standalone package from with the web ACG interface. See Figure 30

Figure 30

DELL TECHNOLOGIES CONFIDENTIAL

38 of 50
 As-Deployed Configuration Generator

Installation (Desktop Version Only)

Run the installer and follow the steps presented. If See Figure 31, Figure 32 & Figure 33.

Figure 31

Figure 32

Figure 33

DELL TECHNOLOGIES CONFIDENTIAL

39 of 50
 As-Deployed Configuration Generator

Support, Issues and Troubleshooting

Important Notes
Before reviewing the report generated please, follow instructions from 1. [ ] in the Known Issues section
• Document must be proofread before handing it over the customer or PM.
• Do not have a report open in Microsoft Word and run the ACG to generate a report with the identical
name, as it will cause an error.
• Each time a report is generated it is given a default name. If you have used the default name for a
previous report that file will be overwritten
• A copy of the input auto support file and the generated report is saved to c:/Auto Supports/Reports in
a zip file. Please submit this file with any support requests.
• Navigate to Known Issues for details on what problems may be expected.

DELL TECHNOLOGIES CONFIDENTIAL

40 of 50
 As-Deployed Configuration Generator

Trouble Shooting
If an error occurs during generation of a report, it will display a pop-up telling you of the error. More
information should be available in the log generated, which can be accessed through the Log item on the
menu bar.

1. [ ] Issue: Missing data in the input file.

Input file is corrupted or incomplete.
Resolution: Proof read the generated file and manually input data as required.

2. [ ] Issue: File fails to process.

On saving an auto support or acdc.xml file from an email message, ensure that you do not save
the email as a text file. This will result in word wrapping and corruption of the auto support file in
general.
Resolution: Copy all text from the email and paste into a blank text document. Save this text
document and import into ACG.

3. [ ] Issue: The ACDC script runs but the screen output shows unconfigured items and the output
word document is incorrect.
Resolution: Verify the user has the latest version of the acdc.pl script. If the acdc version is
older than the most recent version they will need to download the most recent version of the ACG
tool. Download the acdc.pl script from the ACG tool. Load the newest acdc.pl script on the
Avamar utility node. Run the new version on the Avamar node and gather the new output. Rerun
the ACG. If this fails to resolve the issue, escalate.
Details: ACDC .pl script associated with Avamar output is not been updated to the latest version.

root@misdsava1-01:/usr/local/avamar/bin/#: ./acdc.pl
Avamar Configuration Data Collector (ACDC) 3.0.4.1
Localtime 2017/03/07-15:02:23EST
Check: SSH Agent context Available
Check: Avmaint Responding
Check: MC Database Access Established
Avmaint: Config Loaded ... Parsed
Avmaint: Nodelist Loaded ... Parsed
Avmaint: Networkconfig Loaded ... Parsed
Avmaint: Licensing Loaded ... Parsed
GC: Node Count 1
GC: System Name MISDSAVA1-01.CORPNET2.COM
GC: System ID 1487179373@00:1E:67:EB:F5:A2
GC: Customer Number CN-10010633945
GC: Customer Asset ID A-2010012880
GC: Licensed Capacity 8.19 TB
GC: Version GSAN 7.3.1-125
GC: Version EMS Skipped
GC: Version MCS 7.3.1-125
GC: Authentication Local Collected Users:2 Domains:1
GC: Authentication LDAP Maps Collected 2
GC: Authentication LDAP.conf Collected 1
GC: Email Home Collected 2

DELL TECHNOLOGIES CONFIDENTIAL

41 of 50
 As-Deployed Configuration Generator

GC: Maintenance Windows Collected 3

GC: Replication Not Configured
GC: SNMP Service Collected
MC: Clients Collected 4
MC: Group Members Collected
MC: Datasets Collected 11
NC: Hardware Maker emc
NC: OS Version Collected 1
NC: Model, Serial, Part Collected 1/1/1
NC: Interface ethtool Collected 1
NC: IPMI Drivers Collected
Opt: VMWare vCenter Collected 0
Opt: VMWare Proxies Collected 0
Opt: VMWare Machines Collected 0
Opt: Extended Retention Not Available
XML: Output Saved
XML: Validate Passed

ACDC Completed
root@misdsava1-01:/usr/local/avamar/bin/#:

4. [ ] Issue: The ACG fails to generate an output and shows an error screen
Resolution: Exam the output file to ensure that it is properly formed and does not have garbage
contained within.
Details: The input file has been corrupted. This can occur on any of the three technologies that
the ACG currenlty parses for. Each technoliges output file will look different however, in all three
cases, large collection of garbage characters should be evident. They are usually, but not
always, contained at the beginning or end of the input file.

Figure 34
Networker Example
<administrator><![CDATA[mpezeur@* tokdemir@* estoermer@* tlozinsk@*
user=administrator,host=abcec1 root@abcec1 root@abcwc1 oracle@abc1 user=root,host=abcc1
user=system,host=abc1 user=abc!,host=* user=abcozz,host=* user=abcoz!,host=*
user=abcale,host=* user=abc!,host=* *@* SrvcEMCusr01@* vmuser@* *@abc1
user=system,host=abc001.us.domainname.com user=root,host=abc1]]></administrator>
<auth_code><![CDATA[510e1ebe]]></auth_code>
<checksum><![CDATA[fF)v^r'QLq<^Oj(17$Kzy*>#/3<T.#eDUT@FL7X_07vlE89~N'n_W%yHY30rB|~;B\
,?B>Nx"MR);\}V[0kL8WXY`V\iMf[P/OZj)C@M}s`IFh)-hCKFB&/OG{XOMXG]]></checksum>
<comment><![CDATA[]]></comment>

DELL TECHNOLOGIES CONFIDENTIAL

42 of 50
 As-Deployed Configuration Generator

<enabler_code><![CDATA[b98c3b-7d45f9-1ba383]]></enabler_code>
<expiration_date><![CDATA[Authorized - No expiration date]]></expiration_date>
<host_id><![CDATA[f82d164c]]></host_id>
<hostname><![CDATA[abc1]]></hostname>

Avamar Example
<mcClient domain="/Exchange" name="mdur-dr-exch02.domainname.com" os="Windows Server 2008 R2
Enterprise Server Edition Service Pack 1 64-bit">
<plugin pid="Windows Agent" description="Windows Client Agent" version="7.0.100-396"/>
<plugin pid="Windows" description="Windows File System" version="7.0.100-396"/>
<plugin pid="VSS" description="Windows VSS" version="7.0.100-396"/>
<plugin pid="Exchange VSS Writer 2007" description="Windows Exchange VSS"
version="7.0.100-396"/>
<plugin pid="update" description="Windows Update" version="7.0.100-396"/>
"acdc.xml" 3731L, 350005C

5. [ ] Issue: The ACG fails to generate an output and shows an error screen
Resolution: Examine the output file to ensure that it is properly formed and the output file was
not “cut off” at the bottom. Rerun the ACG with the new output file.
Details: The input file has been corrupted. This can occur on any of the three technologies that
the ACG currenlty parses for. Each technoliges output file will look different however, in all three
cases, th file will abruptly terminate in the middle of well formed text. Have the user resend, rerun
or recollect the correct output file.

Figure 35
Data Domain ASUP File
KERBEROS Configuration
------------------------------
The system is not joined to any realm.
------------------------------

Connectemc Configuration
------------------------
ConnectEMC has not been configured.

DELL TECHNOLOGIES CONFIDENTIAL

43 of 50
 As-Deployed Configuration Generator

========== DETAILED-VERSION ==========

GENERATED: 2016-06-09 04:37:59 EDT
Data Domain OS 6.0.0.0-533819
//prod/main/app/...@533819
533819
3.2.33-ddr533819
/auto/home/lsbuild/desktop-530203
//prod/main/platform/os/debugrpm/...@146377
//prod/main/platform/os/...@533819
Distribution: /auto/buildsdur64bp/distro/530203/root
530203

Version info from ddfs executable:

dd_version_timestamp=Wed May 25 00:52:12 2016 GMT
dd_version_che <<< --- it is cut off here

6. [ ] Issue: The ACG fails to generate an output and shows an error screen
Resolution: Examine the output file to ensure that it is properly formed and does not have hideen
characters (line feeds, carriage returns, ascii spaces) contained within. Rerun the ACG with the
new input file.
Details: The input file has been corrupted. This can occur on any of the three technologies that
the ACG currenlty parses for. Each technoliges output file will look different however, in all three
cases, hidden cahracters may be buried in an otherwise nromal looking output. This will not be
obvious. They are usually, but not always, contained at the beginning or end of the input file.
This usually occurs when a user captures the output from a system and cuts and pastes that
inside wordpad as opposed to a text editor like notepad.

Figure 36
Data Domain ASUP
Version info from ddfs executable:
dd_version_timestamp=Wed May 25 00:52:12 2016 GMT
dd_version_checksum=46bb80fcfb698efa0d06a42d4944aad7
dd_version_build_level=nightly
dd_version_change_level=//prod/main/app/...@533819
dd_version_client=//ddfab:533819-052416203758/app/...
dd_version_opened_files=

DELL TECHNOLOGIES CONFIDENTIAL

44 of 50
 As-Deployed Configuration Generator

dd_version_release=6.0.0.0-533819

Version info from kernel:

kernel_version_release=3.2.33-ddr533819
kernel_build_level=SMP

System Upgrade Status

---------------------

========== ADD-ON LIST ========== <<< --- and empty space might be here or on any line

7. [ ] Issue: The ACG fails to generate an output and shows an error screen
Resolution: Examine the output file to ensure that user has used the correct type of input file to
generate an output. Rerun the ACG with the new output file.
Details: The input file is correct however, the wrong input product selection box is being used to
parse. An example of this is, if a file from a Data Domin system is used to generate a NetWorker
output this will obviously fail. Have the user either use this file on the correct Input file selection
box or have them generate the correct file from the system in the field and rerun the ACG.

Figure 37
8. [ ] Issue: The Avamar ACDC.pl script fails to execute after it is copied to the Avamar node.
Resolution: The user must follow the Avamar logging into an “Avamar grid and generating an
Ouput file” process included within this guide.

DELL TECHNOLOGIES CONFIDENTIAL

45 of 50
 As-Deployed Configuration Generator

Details: The user does not follow the Avamar process included in this guide The user did not
log into the Avamar utility node with the proper creditials. The proper permissions have not been
set on acdc.pl script (chown).

9. [ ] Issue: The NetWorker nsrdump command fails to execute

Resolution: The user must follow the NetWorker “Generating an NSRdump Ouput” process
included within this guide.
Details: The correct command switches must be used to generate a properly formed ouput.

10. [ ] Issue: The information in the ACG created word document is incorrect, missing or filled with
garbage.
Resolution: Review the specific information issue request with the user. Verify that the
information to be included in the word document is contained in the input file. If the information is
present in the input file but is not present, is wrong or is garbled in the word document then
escalate.

11. [ ] Issue: The user does not want to recreate contact information when migrating from the local
application to the web-based interface.
Resolution: The user should click the import local database feature in the web based
application.
Details: The import local database feature is on the toolbar in the upper right hand corner of the
web based application. Choose the proper location of your local database file.

12. [ ] Issue: The table of contents and references throughout the document are incorrect or refer to
items that should not be present.
Resolution: The user can either rerun the acg and click the buttons mentioned in the details
below, or they can manually update the document using word command features.
Details: The user should, but does not, click the “Enable Editting” and “Enable Content” button
inside Microsoft word when the word document first generates.

DELL TECHNOLOGIES CONFIDENTIAL

46 of 50
 As-Deployed Configuration Generator

Known Issues
Below is the list of known issues that may occur when using the application.

1. [ ] Issue: Table references are not working or pointing to incorrect bookmarks

Cause: Reference fields are not automatically updated when the file is generated.
Resolution: Open the Word document, highlight the whole content (may be achieved by pressing
and holding CTRL key and then pressing A). Right click on the highlighted portion of the
document and from the context menu select “Update field” option. In the next pop up window
select “Update entire table” option and click “OK”. Figure 38

Figure 38

Please save the changes made to document before closing it.

2. [ ] Issue: Data Domain ASUP Only. NTP settings/FTP allowed hosts display $B, 1 or 00 instead of
valid information
Cause: The data in most cases is correct and resides in the dump file against which the report
has been run.
Resolution: Navigate the asup to confirm correctness of data.

3. [ ] Issue: Data Domain ASUP Only. Table is showing up empty

Cause: ASUPs produced by different versions of a Data Domain DDOS can differ in format. As a
result data is not picked up by the application. However, in most cases the data can be manually
found in the autosupport file.
Resolution: Review the configuration dump file used to produce faulty report and make sure the
data is factually present. If it is, please report the issue to the support team. If it’s not, please
delete the empty section from report.

4. [ ] Issue: Data Domain ASUP Only. DNS Table is not populated but doesn’t disappear
Cause: The DNS table is not set to disappear when not populated with data. This is to emphasize
importance of DNS configuration being present.

DELL TECHNOLOGIES CONFIDENTIAL

47 of 50
 As-Deployed Configuration Generator

Resolution: If DNS configuration is knowingly omitted from the system, delete the document
section manually.

5. [ ] Issue: Data Domain ASUP Only. SNMP Trap host’s name is not appearing in the table header
Cause: Some SNMP configurations do not have a trap host configured.
Resolution: Navigate ASUP to “config.snmp.trap_hosts” and verify that there are no hosts
specified. Alternatively verify that the line doesn’t exist-as indicated by report output.

6. [ ] Issue: Data Domain ASUP Only. Tables in VTL Information section are empty
Cause: The VTL is enabled on the unit, but is not configured.
Resolution: Navigate through the ASUP to the “VTL Configuration” section and verify
correctness of the output. Delete the tables that are confirmed with not having any data.
Alternatively, leave the tables as an indicator of enabled but not configured VTL.

7. [ ] Issue: Data Domain ASUP Only. Spare drives number is unavailable

Cause 1: The spare drives number is unavailable in the ASUP file.
Cause 2: The format in which spare drive number is saved in ASUP fill in prevents application
from parsing it
Resolution: Navigate the ASUP file to “Disk Status” section and verify that spare drives number
is not mentioned in the section. If number of spare drives is available please follow instructions
from Support section to inform technical support about the issue.

DELL TECHNOLOGIES CONFIDENTIAL

48 of 50
 As-Deployed Configuration Generator

Report History
The ACG generates a Report History. Reports will be stored within the database and can be downloaded
or deleted from the following screen: See Figure 39

Figure 39

DELL TECHNOLOGIES CONFIDENTIAL

49 of 50
 As-Deployed Configuration Generator

Support
If an error occurs and it cannot be trouble shot then the following files should be sent to
https://central.dell.com/central/help/request-support.
If an error occurs and it cannot be trouble shot then the following files should be sent to
https://central.dell.com/central/help/request-enhancement.

The ACG officially supports:

• Avamar Software version 6.x, 7.x, 18.x and 19.x
• Data Domain Auto Support files from DDOS 7.4 to DDOS 7.7
• ECS 3.2 and Higher
• NetWorker 8.2.x, 9.2.x, 18.x and 19.x (NSRDump file)
• PowerProtect Data Protection Series Appliance (IDPA) 2.x and Higher
• PowerScale OneFS 8.2 and Higher
• PowerStore 2.x and Higher
• VxRail 4.x and Higher

Version and Build information

Version information can be found in following different ways.
a. When selecting “Help-> About” menu item, the running version and build no of the ACG is displayed.
Below example contains Software Version 3.0.0 with build no 11. Along with the version information,
users can see the latest DDOS support, Avamar SW support, Avamar Script support, NetWorker
version support, VxRail support, ECS support, IDPA support, PowerStore support and PowerScale
support and java information. See Figure 40

Figure 40

DELL TECHNOLOGIES CONFIDENTIAL

50 of 50