This document explains what is required and how an ExaGrid system is initialized.

Use it to prepare for a faster and easier deployment of ExaGrid appliances.

An ExaGrid support engineer, partner or consultant must assist with the deployment.

NOTE: THIS PROCESS INVOLVES REMOVING COMPLETELY ALL EXISTING BACKUP DATA ON
EXAGRID APPLIANCES. THERE IS NO WAY TO RECOVER THE DATA ONCE IT HAS BEEN DELETED.

Required:
• Minimum 2 IP addresses are required but we strongly recommend 3 per ExaGrid appliance.
The first IP will be used for the management, the connection to ExaGrid UI and ExaGrid
internal processes communications, i.e. Deduplication and/or replication (if used). The
second IP is used for the backup traffic. This interface will be used to connect to the backup
application. The third IP is for the IPMI connection. ExaGrid appliances come with an IPMI
port at the back (next to the USB port). Using a browser the ExaGrid console can be
connected to with a virtual keyboard to troubleshoot booting issue in case the OS is unable
to reboot. We strongly recommend having this connection specially if the appliance is on a
remote Data Centre. It will save you a trip to the Data Center!

• ExaGrid appliances come with 1Gb and 10Gb or 25Gb (optional) ports. The IP addresses can
be on single ports and bonded/teamed port. 10Gb/25Gb ports are typically used for the
backup traffic and the 1Gb port for the management. However, it is up to the end user to
decide how this is used. The configuration can be modified at a later stage if required.

• A laptop with WinSCP and putty or preferred SSH client is required to initialize the ExaGrid
appliance.

• For ExaGrid Support engineer to assist you remotely on Webex the laptop should be
connected to Wifi.

• The laptop’s physical network interface must be assigned with IP address 192.168.0.6 (or
something other than 192.168.0.5). This physical interface will connect directly (back to
back) to ExaGrid NIC 2 after it is racked and powered on. ExaGrid NIC 2 comes with default
IP 192.168.0.5 so no interface on the laptop should have this IP.

• The network configuration is usually what delays an ExaGrid initialization. We therefore

recommend that the IP addresses are configured on the switches and ready to come alive as
soon as we connect the network cables to ExaGrid. We also recommend that the Network
admin be reachable on the day of the initialization.
 • Finally, the end user should have in hand prior to the installation date the latest version of
ExaGrid. It is good idea to always initialize the system with the latest available patch as it will
have the most recent fixes and improvements. The end user should contact directly his/her
dedicated support engineer to obtain the download link.

Steps to initialize.
With all the above requirements in hand and ready below are the steps to re-image and initialize the
system. EXAGRID SUPPORT ENGINEER, CONSULTANT OR PARTNER SHOULD ASSIST THE END USER
WITH THE BELOW STEPS.

1. The laptop physical interface should be directly connected by now to the ExaGrid NIC2 port.
The ExaGrid should be racked and powered on. Launch WinSCP.
2. Using WinSCP connect to ExaGrid on 192.168.0.5. User name: root & password: inflection
3. On the right-side of the WinSCP window browse to ExaGrid directory: /isys/upgrade/
On the left-side of the WinSCP window browse to your laptop directory where the download
image file is located. Transfer the file from your laptop to ExaGrid.

4. Launch the SSH client (putty) to connect to ExaGrid on 192.168.0.5 . Use root as user name
and “inflection” as password.
5. In the terminal change directory to /isys/upgrade/ using this command: cd /isys/upgrade/
6. In the terminal stop the ExaGrid service using this command: egrid stop
Stopping the service can take a while, about 10 minutes so wait until the terminal cmd is
returned.
7. Run the following command to confirm the file transferred in step 3 is there: ls -ls
You should see the jar file. In that path you may have some previous jar so double check the
downloaded one is there too.
8. Run this command: mount /home1
9. The next command begins the re-imaging of the system. Run this command:
manualInstall xyz.jar (where xyz.jar is the complete name of the file you downloaded and
transferred earlier).
10. The next screen will warn you that all data will be deleted and lost. This is normal as you are
about to re-image the box. Keep selecting Yes to the next questions. After the last selection
the system will reboot. This is the beginning of initialization. This process can take up to 30
minutes but usually finishes within 20 minutes. There will be few reboots during this
process. You will know the process is completed when you are able to connect to
192.168.0.5 on a browser and this login page is displayed:
11. Login with user name: install

The password is: install

12. The below page is shown next. Note the underlined info. This is the version installed. It
should be the version the system was re-imaged with.

13. Next the date is selected

14. This is where we configure the IP, specify DNS, Gateway, create bond, name the server
etc.
LACP or alb-balancing are the two teaming/bonding types in ExaGrid. If not, sure
individual interfaces can be configured and the bonding can be reviewed later.

Note: NIC2 has IP 192.168.0.5. This its default IP but it can be changed later (if required)
once the other interfaces are configured and reachable from the network.
15. Once network configuration step 2 is completed click on Apply

16. Accept the licence terms and condition

17. In the following page we indicate if this server is the first in a new site, a HUB or Spoke,
or if it a second server joining an existing site. In this example this is the first server in a
new site. A HUB is the master/central site. It is also where data is usually replicated (if
replication is used in multi-sites environment). The first site is usually the HUB but can
also be a spoke. A spoke is typically a remote server that backs local data and will
replicate to a HUB. However, a HUB can also replicate to a spoke. We also name the site
here. The role (HUB or Spoke) of a site can be changed later.
18. Next the support access code is displayed. To continue with the installation users must
confirm they made a note and saved this password. We can’t emphasize enough the
importance of this password. This is for the root account to login to the ExaGrid console
for troubleshooting purpose. It also the password for the “Support” account.
 19. In the next step the configuration will be applied. The system will reboot.
20. Once the system is rebooted, user should try to connect to the ExaGrid UI using the
management IP to ensure it is working. The login credential changes after the system
has been initialized. The user name and password are: admin/admin

That is the end of the initialization of the ExaGrid system. At this stage the server can be
integrated with the backup application if it is ready. If there are additional ExaGrid
appliances to be initialized the same process is repeated. Depending on the role of the
next additional server we will have to choose (STEP 17) whether we create a new site
(spoke or HUB) or add the server to an existing site. Please check/discuss with the
designated support engineer.

Other useful information:

A) Have an SMTP/EMAIL server address and credentials ready on the day of the deployment. It
is critical that ExaGrid support receive alert notification as soon as possible after a system
has been deployed. The SMTP configuration looks like this:
B) If there are more than one site and replication is required the following port must be open
on the firewall.

C) The firewall should also not block the backup application to connect to ExaGrid.
D) After a successful deployment of your ExaGrid appliance schedule with your support
engineer a date for training on the product. It is recommended that you are trained on the
product before the system is fully in production.
E) The 10 or 25Gb NIC cards come separately. The PCI slot in which the card is connected
depends on the model of the ExaGrid appliance. The following document illustrates where
the NIC should be connected:
https://www.exagrid.com/wp-content/uploads/InstallNICs.pdf