Installing the Arista Analytics Node

This chapter describes the installation procedures for the Arista Analytics node on a Dell R440 server. It includes the following sections.

Arista Analytics

Arista Analytics provides single-pane-of-glass monitoring for production visibility, with historical analysis capability based on production network traffic metadata. This information is available on the DANZ Monitoring Fabric (DMF) Controller. Arista Analytics provides a collection of dashboards with visualizations on each dashboard that simplify the analysis of production networks.

The Analytics server runs separately from the DMF Controller, allowing the allocation of adequate disk space and CPU memory without affecting the performance of the DANZ Monitoring Fabric.

Arista Analytics Node Hardware

The Arista Analytics Node is an appliance based on a Dell R440 server running the Arista Analytics server. Running Arista Analytics on a dedicated appliance ensures sufficient hardware resources for good performance. It prevents the Analytics service from affecting other applications on the same device.
  • Two management interfaces (10/100/1000Mb/s)
  • One serial interface (DB-9)
  • One VGA interface
  • Two USB ports
  • Two 10Gb SFP ports
  • Two 10Gb Copper ports
  • One dedicated IDRAC port
The Arista Analytics Node is an enterprise-class, 2-socket, 1-RU rack-mounted hardware appliance designed to deliver the right combination of performance, redundancy, and value in a high-density chassis. (HWA/HWA2).
Figure 1. Arista Analytics Node (HWA/HWA2) Bezel
1 Analytics Node security bezel 3 LCD panel
2 LCD menu buttons    
The following figure illustrates the front panel of the Arista Analytics Node.
Figure 2. Arista Analytics Node (HWA/HWA2) Front Panel
1 System identification button /indicator 6 USB (not supported)
2 Optical drive 7 Information tag
3 Video connector 8 Hard drives Micro
4 USB ports    
5 Power-on indicator / Power button    
The following figure illustrates the rear panel of the Arista Analytics Node.
Figure 3. Arista Analytics Node (HWA/HWA2) Rear Panel
1 Serial connector (Default baud rate 115200) 9 Power supply 2
2 iDRAC Ethernet interface 10 Power supply 1
3 Ethernet connector 1 – Analytics Node management port 1, active (10/100/1000Mb/s) 11 Ethernet connector 2 – Analytics Node management port 2, backup (10/100/1000Mb/s)
4 Ethernet connector 3 – Analytics Node 10GbE SFP+ Collector Interface 1, active 12 USB ports
5 Ethernet connector 4 – Analytics Node 10GbE SFP+ Collector interface 2, backup 13 Video connector
6 Ethernet connector 5 – Not supported 14 System identification button
7 Ethernet connector 6 – Not supported 15 System identification indicator
8 PSU status indicators    

Installation Procedure

 

Complete the following steps to install the Arista Analytics on the Dell R440 appliance.

  1. Rack the Arista Analytics Appliance.
    The appliance interfaces are on the appliance's rear, where the power cord is connected.
  2. Connect the upper leftmost analytics management interface (Gb 1) to the management network.
  3. Log in via the serial port using the admin account name. The baud rate is 115200.
  4. Insert the USB drive with the current software image into the USB port of the Arista Analytics Node Appliance.
  5. Power-cycle the appliance.
    The Boot Manager screen is displayed as shown below. 
    F2 = System Setup
F10 = Lifecycle Controller
F11 = Boot Manager
F12 = PXE Boot
Initializing Serial ATA devices . . .
  6. Press F11 to select Boot Manager to allow booting from USB.
    The Boot Manager main menu is displayed.
    Figure 4. Boot Manager Main Menu
  7. Select One-shot BIOS Boot Menu.
    Figure 5. Boot Menu
  8. Select Disk connected to back USB 2.
  9. When prompted on the system console, type yes to start the installation.
  10. Complete the initial configuration of Arista Analytics.

Upgrading Arista Analytics Node

Before the upgrade, Arista recommends backing up all custom objects. The Arista Analytics User Guide (refer to chapter Backup and Restore) documents the procedure for importing/exporting custom object(s).

Select the following steps for a single-node upgrade.

  1. Copy the ISO image to image:// 
    analytics-1(config)# copy <HTTP_Link_to_analytics.iso> image://
Copying image from <HTTP_Link_to_analytics.iso>
Validating Image Contents: check for expected contents
Verifying image signature
Verifying image checksums
Validating Image Details
00:01:20: Completed
Image added: b4ffe
  2. Stage Image: 
    analytics-1(config)# upgrade stage
Upgrade stage will overwrite alternate partition, proceed ("y" or "yes" to continue): yes
Verifying the integrity of the installation media
Staging the upgrade to DMF Analytics Node 8.1.0-alpha (analytics/master #935)
00:04:47: progress: 63% |**********************************->
  3. Launch Upgrade: 
    analytics-1(config)# upgrade launch
Upgrade launch: DMF Analytics Node 8.1.0-alpha (analytics/master #935)
Upgrade launch: Various cluster members may be rebooted by automation
Upgrade launch: proceed? ("y" or "yes" to continue): yes
Upgrade launch: *WARNING* single-controller: upgrade will be non-redundant
Upgrade launch: non-redundant upgrade ("y" or "yes" to continue): yes
Upgrade launch: Various cluster members may be rebooted by automation
Upgrade launch: 07:52:00: Starting Upgrade
Upgrade launch: 07:52:00: origin version: DMF Analytics Node 8.1.0
Upgrade launch: 07:52:00: config updates are frozen: upgrade state: begin-upgrade-old-active
Upgrade launch: 07:52:00: Completed; Ready for reboot
Upgrade state: current upgrade state: None
Upgrade launch: Moving boot partition to alternate
Upgrade launch: Successfully prepared for launch
None
00:00:06: Completed

Cluster Upgrades

To upgrade the cluster, use the following steps simultaneously on all 3 or 5 nodes. You must execute upgrade cluster commands from the Active Analytics Node in the cluster.
  1. Copy image: 
    analytics-1# copy <HTTP_Link_to_analytics.iso> image://cluster
analytics-1: Copying image from <HTTP_Link_to_analytics.iso>
analytics-2: Copying image from <HTTP_Link_to_analytics.iso>
analytics-3: Copying image from <HTTP_Link_to_analytics.iso>
analytics-1: Validating Image Contents: check for expected contents
analytics-1: Verifying image signature
analytics-1: Verifying image checksums
analytics-2: Validating Image Contents: check for expected contents
analytics-2: Verifying image signature
analytics-2: Verifying image checksums
analytics-3: Validating Image Contents: check for expected contents
analytics-3: Verifying image signature
analytics-3: Verifying image checksums
analytics-1: Validating Image Details
analytics-2: Validating Image Details
analytics-3: Validating Image Details
00:02:32: Completed
Image added: b4ffe
  2. Stage Image: 
    analytics-1# upgrade cluster stage
Upgrade stage will overwrite alternate partition, proceed ("y" or "yes" to continue): yes
analytics-1: Verifying the integrity of the installation media
analytics-2: Verifying the integrity of the installation media
analytics-3: Verifying the integrity of the installation media
analytics-1: Staging the upgrade to DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
analytics-2: Staging the upgrade to DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
analytics-3: Staging the upgrade to DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
00:06:31: Completed
00:10:44: Completed
Upgrade stage: info: *analytics-1: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.
˓!2.0 #6)
Upgrade stage: info: *analytics-1: Alternate partition Release: DMF Analytics Node 8.2.0
˓!(analytics/dmf-8.2.0 #6)
Upgrade stage: info: *analytics-1: Alternate Partition Formatted
Upgrade stage: info: *analytics-1: Alternate Partition is: /dev/flvg/root1
Upgrade stage: info: *analytics-1: All node(s) connected
Upgrade stage: info: *analytics-1: Alternate partition staged
Upgrade stage: validation: *analytics-1: Sync interface: bond1/bond0 is up
Upgrade stage: info: *analytics-1: All Application Validation Checks completed
Upgrade stage: info: *analytics-1: Ready for upgrade
Upgrade stage: info: analytics-3: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.
˓!2.0 #6)
Upgrade stage: info: analytics-3: Alternate partition Release: DMF Analytics Node 8.2.0
˓!(analytics/dmf-8.2.0 #6)
Upgrade stage: info: analytics-3: Alternate Partition Formatted
Upgrade stage: info: analytics-3: Alternate Partition is: /dev/flvg/root2
Upgrade stage: info: analytics-3: All node(s) connected
Upgrade stage: info: analytics-3: Alternate partition staged
Upgrade stage: validation: analytics-3: Sync interface: bond1/bond0 is up
Upgrade stage: info: analytics-3: All Application Validation Checks completed
Upgrade stage: info: analytics-3: Ready for upgrade
Upgrade stage: info: analytics-2: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.
˓!2.0 #6)
Upgrade stage: info: analytics-2: Alternate partition Release: DMF Analytics Node 8.2.0
˓!(analytics/dmf-8.2.0 #6)
Upgrade stage: info: analytics-2: Alternate Partition Formatted
Upgrade stage: info: analytics-2: Alternate Partition is: /dev/flvg/root1
Upgrade stage: info: analytics-2: All node(s) connected
Upgrade stage: info: analytics-2: Alternate partition staged
Upgrade stage: validation: analytics-2: Sync interface: bond1/bond0 is up
Upgrade stage: info: analytics-2: All Application Validation Checks completed
Upgrade stage: info: analytics-2: Ready for upgrade
  3. Verify image has been staged successfully. 
    analytics-1# show cluster boot partition
# Node name Vol State Upgrade Product Version Build
-|----------------|-----|------------|---------|------------------|-------|-----|
1 analytics-1 root1 staged DMF Analytics Node 8.3.0 12
2 analytics-1 root2 Active, Boot completed DMF Analytics Node 8.2.0 6
3 analytics-3 root1 Active, Boot completed DMF Analytics Node 8.2.0 6
4 analytics-3 root2 staged DMF Analytics Node 8.3.0 12
5 analytics-2 root1 staged DMF Analytics Node 8.3.0 12
6 analytics-2 root2 Active, Boot completed DMF Analytics Node 8.2.0 6
analytics-1#
  4. Verify all pre-upgrade launch checks will pass. 
    analytics-1# upgrade cluster pre-launch-check
info: *analytics-1: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
info: *analytics-1: Alternate partition Release: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
info: *analytics-1: Alternate Partition Formatted
info: *analytics-1: Alternate Partition is: /dev/flvg/root1
info: *analytics-1: All node(s) connected
info: *analytics-1: Alternate partition staged
validation: *analytics-1: Sync interface: bond1/bond0 is up
info: *analytics-1: All Application Validation Checks completed
info: *analytics-1: Ready for upgrade
info: analytics-3: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
info: analytics-3: Alternate partition Release: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
info: analytics-3: Alternate Partition Formatted
info: analytics-3: Alternate Partition is: /dev/flvg/root2
info: analytics-3: All node(s) connected
info: analytics-3: Alternate partition staged
validation: analytics-3: Sync interface: bond1/bond0 is up
info: analytics-3: All Application Validation Checks completed
info: analytics-3: Ready for upgrade
info: analytics-2: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
info: analytics-2: Alternate partition Release: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
info: analytics-2: Alternate Partition Formatted
info: analytics-2: Alternate Partition is: /dev/flvg/root1
info: analytics-2: All node(s) connected
info: analytics-2: Alternate partition staged
validation: analytics-2: Sync interface: bond1/bond0 is up
info: analytics-2: All Application Validation Checks completed
info: analytics-2: Ready for upgrade
analytics-1#
  5. Launch upgrade. 
    analytics-1# upgrade cluster launch
Upgrade launch: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
Upgrade launch: Various cluster members and managed devices may be rebooted by automation
Upgrade launch: proceed? ("y" or "yes" to continue): yes
UpgradeProgress: 0 analytics-1: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
UpgradeProgress: 1 analytics-1: Alternate partition Release: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
UpgradeProgress: 2 analytics-1: Alternate Partition Formatted
UpgradeProgress: 3 analytics-1: Alternate Partition is: /dev/flvg/root1
UpgradeProgress: 4 analytics-1: All node(s) connected
UpgradeProgress: 5 analytics-1: Alternate partition staged
UpgradeProgress: 6 analytics-1: All Application Validation Checks completed
UpgradeProgress: 7 analytics-1: Upgrade launch: Various cluster members may be rebooted by automation
UpgradeProgress: 8 analytics-3: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
UpgradeProgress: 9 analytics-3: Alternate partition Release: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
UpgradeProgress: 10 analytics-3: Alternate Partition Formatted
UpgradeProgress: 11 analytics-3: Alternate Partition is: /dev/flvg/root2
UpgradeProgress: 12 analytics-3: All node(s) connected
UpgradeProgress: 13 analytics-3: Alternate partition staged
UpgradeProgress: 14 analytics-3: All Application Validation Checks completed
UpgradeProgress: 15 analytics-3: Upgrade launch: Various cluster members may be rebooted by automation
UpgradeProgress: 16 analytics-3: Upgrade launch: saving running-config as: upgrade-snapshot
UpgradeProgress: 17 analytics-3: Upgrade launch: saving running-config to file: upgrade-rc
UpgradeProgress: 18 analytics-2: This release is: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
UpgradeProgress: 19 analytics-2: Alternate partition Release: DMF Analytics Node 8.2.0 (analytics/dmf-8.2.0 #6)
UpgradeProgress: 20 analytics-2: Alternate Partition Formatted
UpgradeProgress: 21 analytics-2: Alternate Partition is: /dev/flvg/root1
UpgradeProgress: 22 analytics-2: All node(s) connected
UpgradeProgress: 23 analytics-2: Alternate partition staged
UpgradeProgress: 24 analytics-1: Upgrade launch: saving running-config as: upgrade-snapshot
UpgradeProgress: 25 analytics-1: Upgrade launch: saving running-config to file: upgrade-rc
UpgradeProgress: 26 analytics-2: All Application Validation Checks completed
UpgradeProgress: 27 analytics-2: Upgrade launch: Various cluster members may be rebooted by automation
UpgradeProgress: 28 analytics-2: Upgrade launch: saving running-config as: upgrade-snapshot
UpgradeProgress: 29 analytics-2: Upgrade launch: saving running-config to file: upgrade-rc
Upgrade launch: Starting Upgrade: async-id 82ajhKaJvWRaK0TDpZZ_MRTCi7QMIUQ6
Upgrade launch: disconnecting from launch
Upgrade launch: use: 'show upgrade progress' for progress on this controller
Upgrade launch: use: 'upgrade abort' to abort upgrade on this controller
upgrade started id:82ajhKaJvWRaK0TDpZZ_MRTCi7QMIUQ6
Upgrade launch disconnected from background task
analytics-1#
    Note: In some cases, if the shard count is too high, the upgrade will not proceed. In such a situation, the following will need to run:
    analytics-1> enable
analytics-1# debug bash
***************************** WARNING ******************************
Any/All activities within bash mode are UNSUPPORTED
This is intended ONLY for additional debugging ONLY by Arista TAC.
Please type "exit" or Ctrl-D to return to the CLI
***************************** WARNING ******************************
admin@analytics-1:~$ nohup /opt/bigswitch/reindex.sh > reindex.log &
    Note: The containers could take 10-20 minutes to come up after upgrade.