Professional Documents
Culture Documents
Arxview_DCAE_Install_Guide (2)
Arxview_DCAE_Install_Guide (2)
Installation Guide
Version 2.1
©2014 Arxscan, Inc. All Rights Reserved. All other brands, product names, company names, trademarks and service marks are the
properties of their respective owners.
This document is provided “as is” and Arxscan assumes no responsibility for any typographical, technical or other inaccuracie s in this
document. Arxscan reserves the right to periodically change information that is contained in this document; however, Arxscan makes no
commitment to provide any such changes, updates, enhancements or other additions to this document to you in a timely manner o r at all.
ARXSCAN MAKES NO REPRESENTATIONS, WARRANTIES, CONDITIONS OR COVENANTS, EITHER EXPRESS OR IMPLIED (INCLUDING WITHOUT
LIMITATION, ANY EXPRESS OR IMPLIED WARRANTIES OR CONDITIONS OF FITNESS FOR A PARTICULAR PURPOSE, NON-INFRINGEMENT,
MERCHANTABILITY, DURABILITY, TITLE, OR RELATED TO THE PERFORMANCE OR NON-PERFORMANCE OF ANY SOFTWARE REFERENCED
HEREIN OR PERFORMANCE OF ANY SERVICES REFERENCED HEREIN). IN CONNECTION WITH YOUR USE OF THIS DOCUMENTATION, NEITHER
ARXSCAN NOR ITS RESPECTIVE DIRECTORS, OFFICERS, EMPLOYEES OR CONSULTANTS SHALL BE LIABLE TO YOU FOR ANY DAMAGES
WHATSOEVER BE THEY DIRECT, ECONOMIC, COMMERCIAL, SPECIAL, CONSEQUENTIAL, INCIDENTAL, EXEMPLARY OR INDIRECT DAMAGES,
EVEN IF ARXSCAN HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, INCLUDING WITHOUT LIMITATION, LOSS OF BUSINESS
REVENUE OR EARNINGS, LOST DATA, DAMAGES CAUSED BY DELAYS, LOST PROFITS, OR A FAILURE TO REALIZE EXPECTED SAVINGS.
Arxscan, Incorporated
PO Box 44
Asbury, NJ 08802
Arxview is distributed as a virtual server appliance and is available in both VMware™ and Hyper-V™
formats. Installation is as simple as importing the server appliance files into a hypervisor (ESX/VM
Workstation/VM Server for VMware, Hyper-V for Microsoft), setting the network properties for the
Arxview virtual machine, adding credentials for the assets to be scanned, and adding those assets to
the Arxview system via the web GUI.
The Arxview service connects to most types of storage hardware, as well as general systems of
record, to generate a comprehensive, detailed map of your storage environment. Arxview includes
services to discover storage configurations, monitor system performance and events, and calculate
end-user usage and allocation values. All discovery steps are explained in detail in the accompanying
documentation. With proper preparation an Arxview installation and discovery can be completed in
about ninety minutes.
Arxview provides valuable information to anyone that manages, maintains or relies on computer data
storage. This includes business users, technical managers, system administrators, NOC personnel and
enterprise IT architects.
These services run by default whenever supported storage assets are added to the inventory:
This service gathers configuration and capacity information from SAN arrays and NAS
filers, including disks, LUNs, volumes, allocations, hosts, and capacities. It maps these
objects to each other as well as to downstream consumers (e.g., business units, SAN
hosts) and upstream providers (storage arrays, data centers, regions, and so forth).
This information is presented in a number of reports and visualizations within the
Arxview web-based GUI.
This service gathers real-time system events and alerts from supported SAN arrays
and NAS filers, links these alerts to dependent systems and business units, and
presents them within the Arxview GUI.
This service gathers volume capacity and usage information from end-user devices
(Windows, UNIX, and Linux server volumes). It maps this information back to storage LUNs
where applicable and displays a number of capacity and usage reports within the Arxview
web GUI for each level, from individual device to host server to storage array to enterprise.
Note that this service requires access credentials for each server: ‘user’ level access for Linux
and UNIX servers, local administrator access for each Windows server.
1. Add server credentials to the Arxview product for all servers to be scanned. This may be done
on a per-server basis, with domain/single-sign on credentials, or as an arbitrary grouping of
credentials.
2. Enable usage discovery when scheduling the discovery service (see page 14, “Configure
Discovery Service”).
Note: it is not necessary to manually add each server to the Arxview inventory. Arxview
will discover any hosts associated with storage arrays and automatically add them to the
inventory. It will also add them to the usage discovery queue if that service is enabled.
Server Requirements
Item Description
Processors Single+ Processor(s)
Memory 2+ GB RAM
Disk Space 50 GB
Network Ports (see additional client ports below)
SSH 22
SMTP 25
HTTP 80
HTTPS 443
RPC 135
The following information and access must be on hand or available when configuring the Arxview
services:
1. The Arxview virtual machine root password. This will be supplied to you by Arxscan and can
be requested from them at any time via email support at support@arxscan.com.
2. Network addressing information for Arxview VM server as deployed at customer location:
Hostname (default: ‘arxviewdcae’)
IP address
Subnet mask
Gateway address
DNS server IP address (one or more)
3. The name of each region and data center to be monitored by Arxview.
4. VMware console access to the Arxview virtual machine.
5. A Windows domain account or local server account for administrative-level access to each
SAN host or virtual machine running Windows operating system (if monitoring Windows
server usage).
6. Linux credentials, single-sign-on or per server (if monitoring Linux/Unix servers usage).
7. IP address or hostname for each SAN and NAS array.
8. Administrator credentials for each SAN and NAS array.
Arxscan recommends using the same username/password combination on each
array.
Pillar Axiom access requires an Administrator1 account for Arxview’s use.
9. IP address or hostname for each Dell and HP blade chassis.
10. Administrative or read-only access credentials for each Dell and HP blade chassis.
11. VMware Virtual Center access credentials and server IP or hostname.
Optional Information
It would be helpful if the following information was on hand at the time of deployment but it is not
mandatory. These values can be added at a later date. However, until that time system alert email
forwarding will not function:
Infrastructure Requirements
Resources allocated for one (1) virtual machine (see server requirements above).
Network Connectivity
Locate the Arxview virtual appliance on an appropriate network segment and allow SSH access. To
install from within the Arxview VM, the server will require access to http://www.arxscan.com (port
80) and https://support.arxview.net (port 443). If these ports cannot be opened, the install wizard
will guide you through the steps required to install Arxview manually.
Also, be aware that the Arxview server may send and receive traffic on the following network ports
(all traffic will remain within your network):
SSH (22)
SMTP (25)
HTTP (80)
RPC (135)
HTTPS (443)
NFS (111, 2049)
NETBIOS (137-139)
LDAP (389)
SMB (445)
PILLAR CLI (26004)
Steps with checkboxes ( ) are required; steps with circles ( ) are optional. Check the
corresponding box after completing each step.
arxsetup -f <downloaded-install-archive-file>
F. Enter Credentials
This is where you will enter the credentials for your storage and server equipment.
i. Enter the number that corresponds to the type of credential you would like
to create.
ii. Press the ‘Enter’ key.
iii. There are two options at this point: specific credentials or
default credentials. Please note the following:
Credentials can be created for a particular asset or network domain ( specific credentials)
or for every asset of a particular platform (default credentials). When Arxview starts a
discovery for a particular asset, it first checks for platform credentials created for that
asset name, then looks for platform credentials for the asset’s network domain. If none
of those specific credentials are found, Arxview uses the default credentials. In most
cases default credentials are the appropriate choice - often every asset of a particular
platform will use the same credentials.
In some cases you might have several assets of a particular type (e.g. EMC DMX) that use
one set of credentials and other set of assets of that same type that uses another set of
credentials. In that case, you can assign a “Credential Name” to each asset when adding
it to Arxview (explained in item 4.J below). So in the example above, you might have
some EMC DMX arrays using credential “EMCDMX1” and another set using credential
“EMCDMX2”.
After choosing a credential type to add, you will see a prompt similar to this:
The credentials you enter can apply to a specific full asset name,
a domain name, or can serve as the default for all assets of this type.
i. If you are creating default credentials, press the Enter key at this point
ii. If you are creating specific credentials, enter the asset name, credential
name, or network domain name (NOT the Active Directory name)
iv. If the credentials you’re adding include an Active Directory or LDAP domain
as part of the user name (e.g. “mydomain\myuser”), add the entire domain\user
in the username field, with the following exceptions (directory domains are
The Arxview virtual machine installation is now complete. You will now be presented with the
URL of the Arxview web interface. Please log in to that URL via a web browser to continue the
configuration.
If you have any questions you may reach Arxscan support at support@arxscan.com.
Arxview Configuration
Usage Notes
When entering commands, replace any words in brackets (e.g. “<ip_address>”) with its actual
value. Do not include the brackets when entering the command. For example, this
<ip_address>
192.168.1.1
Installation Steps
Steps with checkboxes ( ) are required; steps with circles ( ) are optional.
2. Configure Pillar Event Monitoring (if no Pillar arrays exist, skip to step 6)
A. Open the Arxview VM’s IP address in your web browser
B. Log in to the Arxview application with the following credentials:
Username: admin
Password: admin2001
C. From the content menu choose Administration Monitoring Pillar Event
Configuration.
D. Mark the checkbox for each alert you would like Arxview to monitor. At the top of
the window there is a box that reads “Select all” and then displays icons for Critical, High
and Medium alerts. Clicking one of these icons will cause all alerts of that severity to be
selected.
E. You may also promote or demote the severity level for each alert as you see fit.
F. Click ‘Update’ at bottom of page.
3. Configure IBM N-Series / NetApp Event Forwarding (if no NetApp filers exist, skip to
step 8)
A. Log in to the console of each NetApp filer.
B. Edit /etc/syslog.conf, confirming that at least the following two lines are included,
(and retaining any other existing lines):
*.info /etc/messages
*.* @<IP_address_of_Arxview_VM>
C. Save your changes.
5. Configure 3Par Event Monitoring (if no 3Par arrays exist, skip to step 9)
A. Open the Arxview VM’s IP address in your web browser
B. Log in to the Arxview application with the following credentials:
Username: admin
Password: admin2001
C. From the content menu choose Administration Monitoring 3Par Event
Configuration.
D. Using the dropdown menu, select the minimum alert severity to monitor. Alerts sent
by 3Par arrays that are below this threshold will be ignored by Arxview.
E. Click the ‘Update’ button.
6. Configure FalconStor Event Monitoring (if no FalconStor arrays exist, skip to step 10)
A. Open the Arxview VM’s IP address in your web browser
B. Log in to the Arxview application with the following credentials:
Username: admin
Password: admin2001
C. Select Administration Monitoring Falconstor Event Configuration.
D. Mark the checkbox for each alert you would like Arxview to monitor. At the top of
the window there is a box that reads “Select all” and then displays icons for Critical, High
and Medium alerts. Clicking one of these icons will cause all alerts of that severity to be
selected.
E. You may also promote or demote the severity level for each alert as you see fit.
F. Click ‘Update’ at bottom of page.
11. Updating the Arxview Product from within the Arxview VM (For VMs that do not
have access to the Internet, SKIP TO STEP 17.)
Arxscan regularly releases updates to the Arxview product. The following procedure will test for
an available update and, if one exists, update the Arxview product automatically. Since the
arxsetup program installs the latest version of Arxview, this process does not need to be done at
the time of install. The steps below describe how to update the product as updates become
available.
A. At the VM console, launch the VM’s terminal window by selecting Applications
Accessories Terminal from the top menu bar. From this terminal window, run the
following commands (hitting the ‘Enter’ key after each command):
B. Assume administrator or ‘root’ privileges:
su – root
C. Enter the root password if requested.
D. Launch the Arxview update program with the following command:
arxupdate
If an update is available the currently installed Arxview version and the available
version will be displayed. Otherwise the program will quit with the message “Your
Arxview install is already up to date.”
E. Enter “y” to update the Arxview product or “n” to quit.
F. Enter your customer username at the prompt.
G. Enter your customer password at the prompt.
H. Press the ‘Enter’ key. Several status messages will be displayed as the Arxview
12. Update ArxviewDCAE via the Web . (This is only for VMs that do not have access to the
Internet.)
A. Launch a web browser from a computer that has access to the Internet.
B. Navigate to https://support.arxview.net. A login window will be displayed.
C. Enter the Arxscan installer username and password assigned to you.
D. Click the “Update Manual Download” link. The Update Manual Download page will
load.
E. Select the service order number for this installation from the dropdown menu.
F. Click the ‘Verify’ button. The service order number and the customer name
associated with that service number will be displayed.
G. If the information is correct click the ‘Confirm’ button to continue; otherwise click
the ‘Go Back’ button to return to the previous screen.
H. Click the ‘Download’ button. A download window will appear prompting you to
accept the download and choose a download location.
I. Choose to save the file to the local workstation and wait for the download to finish.
J. Navigate to the download location in the local workstation’s file system.
K. Launch WinSCP. A ‘WinSCP Login’ window will appear.
L. Click the ‘New’ button.
M. In the Host name field, enter the Arxview VM IP address.
N. In the ‘User name’ field, enter ‘root’.
O. In the ‘Password’ field, enter the root password as supplied by Arxscan.
P. Click ‘Login’. A new window will appear. In the rightmost panel the contents of the
Arxview VM’s root home directory will appear.
Q. Drag the arxview_current.tar.gz.gpg file into that panel. A ‘Copy’ window will appear.
R. Click the ‘Copy’ button to confirm the file transfer. A progress window will appear.
S. At the VM console, launch the VM’s terminal window by selecting Applications
Accessories Terminal from the top menu bar. From this terminal window, run the
following commands (hitting the ‘Enter’ key after each command):
i. Assume administrator or ‘root’ privileges:
su – root
ii. Enter the root password if requested.
iii. Run the Arxview install program. The process is complete when “Done!” is
NOTE: Customers that had previously installed and/or updated the Arxview product using
this method (downloading the code from the web, uploading it to the VM, running
arxupdate against the downloaded file) can switch to the standard method (allowing
arxupdate to download the code from within the VM) by using the ‘-i’ flag, as shown
below. They will be prompted for their Arxscan username, password and service order
number at that time.
arxupdate –i