GigaVUE G Series Upgrade Guide v8.6.00

GigaVUE G SeriesUpgrade Guide

Version 8.6.00

GigaVUE-2404

GigaVUE-420

GigaVUE-212

COPYRIGHT

Copyright © 2013 Gigamon Inc. All Rights Reserved. No part of this publication may be reproduced, transmitted,transcribed, stored in a retrieval system, or translated into any language in any form or by any means withoutGigamon’s written permission.

TRADEMARK ATTRIBUTIONS

Copyright © 2013 Gigamon Inc. All rights reserved. Gigamon and the Gigamon logo are trademarks of Gigamon,Inc. in the United States and/or other countries. Gigamon trademarks can be found at www.gigamon.com/legal-trademarks. All other trademarks are the trademarks of their respective owners.

DOCUMENT REVISION – 12/2/13

http://www.gigamon.com/legal-trademarks

http://www.gigamon.com/legal-trademarks

Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Other Sources of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Premium Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Chapter 1 GigaVUE G Series Upgrade Instructions . . . . . . . . . . . . . . . . . . . . . . . 7Before You Begin – Required Items. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9About Pre-Loader Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Required Pre-Loader Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Non Required Pre-Loader Images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Important Information Regarding Filenames: . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Upgrade Paths . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

GigaVUE-2404 Running v7.0.xx with a GigaSMART Blade . . . . . . . . . . . . 12About Skip-Level Provisioning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Upgrading from Pre-v7.0.xx Releases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Upgrading Standalone Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Standalone Systems Snapshot View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Standalone Systems Detailed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Copy the Installation Files onto your SCP/TFTP Server . . . . . . . . . . . 14Save the Existing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Back-up the Existing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Install the Pre-loader Image (if required) . . . . . . . . . . . . . . . . . . . . . . . 16Install the Base Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Install the GigaSMART Software (if applicable) . . . . . . . . . . . . . . . . . 17Reboot the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Save the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Install the G-VUE Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Upgrading Cross-Box Stacks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Cross-Box Stacks Snapshot View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Cross-Box Stacks Detailed View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Notes on Master/Slave Cross-Box Stack Upgrades . . . . . . . . . . . . . . 20Copy the Installation Files on your SCP/TFTP Server . . . . . . . . . . . . 20Synchronizing GigaVUE G Series Nodes(Master/Slave Cross-Box Stacks Only) . . . . . . . . . . . . . . . . . . . . . . . . 21Save the Existing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Back-up the Existing Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . 22Install the Pre-loader Image (if required) . . . . . . . . . . . . . . . . . . . . . . . 22Install the Base Image. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

3

Install the GigaSMART Software (if applicable) . . . . . . . . . . . . . . . . . 24Reboot the System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Save the Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Install the G-VUE Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Verify that the Installation is Successful . . . . . . . . . . . . . . . . . . . . . . . 25

Installing GigaSMART Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Licensing GigaSMART Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Installing G-VUE Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Cloning System Configuration from One System to Another . . . . . . . . . . . . . . . . . 29

Cloning a System in a Cross-Box Stack . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

4

About This Guide

This Upgrade Guide describes how to upgrade the GigaVUE® G SeriesVisibility Fabric™ Nodes to the most recent software release manufacturedby Gigamon Inc.

The GigaVUE G Series Visibility Fabric Nodes include the GigaVUE-2404®,the GigaVUE-420®, and the GigaVUE-212® family of Gigamon® products.

Other Sources of Information

Gigamon provides additional documentation for the GigaVUE G SeriesVisibility Fabric Nodes located on the Gigamon Customer Portal:

Document Summary

GigaVUE G Series CLI QuickStart Guide v8.6.00 Provides an accelerated overview of the GigaVUE® G SeriesVisibility Fabric™ Nodes that include Hardware Setup, InitialConfiguration, and CLI usage in this most recent softwarerelease.

GigaVUE G Series CLI User’s Guide v8.6.00 Describes in detail how to install, connect, configure, andoperate the GigaVUE-2404®, GigaVUE-420®, andGigaVUE-212®. Provides detailed information on all relevantCLI commands in this most recent software release.

GigaVUE G Series Upgrade Guide v8.6.00 Describes how to upgrade the GigaVUE-2404®,GigaVUE-420®, and GigaVUE-212® in this most recentsoftware release.

GigaVUE G Series Command Line Summary v8.6.00 Summarizes all available CLI commands that are available ina single document for this most recent software release.

G-VUE QuickStart Guide v3.6.00 Provides an accelerated overview of the G-VUE™Web-Based GUI in this most recent software release.

G-VUE User’s Guide v3.6.00 Describes in detail how to install, connect, configure, andoperate the G-VUE™ Web-Based GUI for the GigaVUE® GSeries Visibility Fabric™ Nodes in this most recent softwarerelease.

GigaVUE G Series v8.6.00 / G-VUE v3.6.00 Release Notes Describes New Features, Usage Notes, Resolved Issues,and Known Issues for the GigaVUE® G Series VisibilityFabric™ Nodes and the G-VUE™ Web-Based GUI in thismost recent software release.

5

http://www.gigamon.com/customer-portal-login

Contacting Technical Support

See http://www.gigamon.com/gigamon-technical-support for Technical Support hoursand contact information. You can also email Technical Support [email protected].

Premium Support

Email Gigamon at [email protected] for information on purchasing 24x7 PremiumSupport for your GigaVUE G Series Visibility Fabric Node. Premium Support entitlesyou to around-the-clock phone support with a dedicated Support Engineer every day ofthe week.

6 GigaVUE G Series Upgrade Guide

mailto:[email protected]

http://www.gigamon.com/gigamon-technical-support


Chapter 1

GigaVUE G Series Upgrade Instructions

This guide describes how to upgrade a GigaVUE G Series Visibility FabricNode to the GigaVUE v8.6.00/G-VUE v3.6.00 release. See the followingsections for upgrade instructions:

• Before You Begin – Required Items on page 9

• About Pre-Loader Images on page 11

• Required Pre-Loader Images on page 11

• Non Required Pre-Loader Images on page 11

• Important Information Regarding Filenames: on page 11

• Upgrade Paths on page 12

• GigaVUE-2404 Running v7.0.xx with a GigaSMART Blade onpage 12

• About Skip-Level Provisioning on page 12

• Upgrading from Pre-v7.0.xx Releases on page 13

• Upgrading Standalone Systems on page 14

• Standalone Systems Snapshot View on page 14

• Standalone Systems Detailed View on page 14

• Upgrading Cross-Box Stacks on page 19

• Cross-Box Stacks Snapshot View on page 19

• Cross-Box Stacks Detailed View on page 20

• Installing GigaSMART Software on page 26

• Licensing GigaSMART Software on page 27

• Installing G-VUE Software on page 28

• Cloning System Configuration from One System to Another on page 29

• Cloning a System in a Cross-Box Stack on page 30

7

GIGAVUE-MP NOT SUPPORTED IN v8.6.00!

The v8.6.00 release does not support the GigaVUE-MP platform! If you want topreserve an existing stack that includes GigaVUE-MP systems, do not upgradeto v8.6.00!

Maximum Number of Stacked GigaStreams in v8.6.00

The maximum number of GigaStream system stacks supported for a GigaVUE-2404 inthe v8.6.00 release remains the same as it was in v8.3.00 – six. If you are upgradingfrom a release prior to v7.2.00 that supported a maximum of eight; use the showgigastream command prior to upgrading and reconfigure your GigaStream systemstack so that a GigaVUE-2404 uses no more than six. Upgrading a GigaVUE-2404 withmore than six GigaStream system stacks will cause the last two configured stacks tobe removed along with their active links; therefore, potentially causing unfavorablestacking issues.

NOTE: The maximum number of tool and xbtool GigaStreams is still eight. Themaximum number of ports in a GigaStream is also still eight.


T

Before You Begin – Required Items

Table 1-1 lists the items you will need to upgrade a GigaVUE G Series Visibility FabricNode to v8.6.00 from one of the supported starting points.

Obtaining Software Images

You can obtain the image for your system by contacting Technical Support. For eachsystem you want to upgrade, you will need to provide the output of show diagcommand saved as a text file. Use the following information to contact TechnicalSupport:

• E-mail: [email protected]

able 1-1: Required Items for Upgrade to GigaVUE v8.6.00/G-VUE v3.6.00

Platform RequiredItems

Description

All Platforms

SCP Server You will need to copy (and unzip) the GigaVUE software packages onto an SCP server.The GigaVUE Visibility Fabric Node will need the file server’s IP address so that it canconnect to the server and download the image.

NOTE: Note that SCP support is available starting with v8.2.xx. When using SCP, keep inmind that Gigamon requires Linux or UNIX-based SCP servers for use with the GigaVUEG Series Visibility Fabric Node – Windows-based servers are not supported. There arefreeware SCP servers available on the Internet. A web search will provide links to manyimplementations.

gvweb8600.tgz Gzip file containing the G-VUE software. The zip includes both the web installation file andthe web-based software itself. When completely unzipped to your SCP Root Directory, youshould see the following files and folders:

• File: gvweb8600 – Web installation file used with install -web command.

• Folder: \web – Files for web-based G-VUE interface.

These common compression tools can work with the G-VUE v3.6.00 files:

• Linux includes command line tar utility.

• Windows applications supporting the tar format include WinZip and 7-Zip. A websearch for tar windows will provide links to many such utilities.

GigaVUE-2404

gvcpre8400prep Binary image file containing a preliminary image that expands system memory usage.This image is only required for the GigaVUE-2404 running v7.0.xx — v8.3.04 that areoperating as part of a stack.

gvc8600 Binary image file containing the updated v8.6.00 software for the GigaVUE-2404.

NOTE: This file may be provided in a zipped format (for example, gvc8600.zip).

gsc8600.tgz Gzip file containing the software for the GigaSMART-6X blade. This file is installed on aGigaVUE-2404 with a GigaSMART-6X blade physically installed.

You do not need to unzip this file. It can be installed directly using the install -gscommand.

NOTE: The GigaSMART and GigaVUE versions must match for successful usage ofGigaSMART operations.

NOTE: To preserve GigaSMART Operations across an upgrade, do not reboot thesystem between the upgrade of the GigaVUE software and the GigaSMART software. Ifyou do reboot the system between the upgrade of the base software and the GigaSMARTsoftware, you can use config restore after the upgrade to restore all GigaSMARTOperations.

GigaVUE G Series Upgrade Guide 9


T

GigaVUE-420

gvbpre8400prep Binary image file containing a preliminary image that expands system memory usage.This image must be installed on v7.0.xx — v8.3.04 on the GigaVUE-420 before installingthe v8.6.00 base image. It is not required for v8.3.05.

gvb8600 Binary image file containing the updated v8.6.00 base image software for theGigaVUE-420.

NOTE: This file may be provided in a zipped format (for example, gvb8600.zip).

GigaVUE-212

gvdpre8400prep Binary image file containing a preliminary image that expands system memory usage.This image must be installed on v7.0.xx — v8.3.04 on the GigaVUE-212 before installingthe v8.6.00 base image. It is not required for v8.3.05.

gvd8600 Binary image file containing the updated v8.6.00 base image software for theGigaVUE-212.

NOTE: This file may be provided in a zipped format (for example, gvd8600.zip).

able 1-1: Required Items for Upgrade to GigaVUE v8.6.00/G-VUE v3.6.00

Platform RequiredItems

Description


About Pre-Loader Images

Required Pre-Loader Images

A Pre-Loader image IS required for the following:

1. GigaVUE-420 and GigaVUE-212 products running v7.0.xx - v.8.3.04(Standalone or Stacked).

2. GigaVUE-2404 products running v7.0.xx - v8.3.04 in a Mixed Stack1 thatcombines GigaVUE-420 products and GigaVUE-212 products.

Non Required Pre-Loader Images

A Pre-Loader image IS NOT required for the following:

1. GigaVUE G Series Visibility Fabric Nodes running software v8.3.05 and above.

2. GigaVUE-2404 products that are Standalone.

3. Stacked environments with ONLY GigaVUE-2404 products.

Follow the correct upgrade paths to v8.6.00 for the criteria which meets your GigaVUEG Series Visibility Fabric Node needs.

Important Information Regarding Filenames:

Table 1-2 outlines the correct filenames associated with correct upgrade path tov8.6.00.

Table 1-2: Correct Filenames for this Software Release

1. A Mixed Stack is a Cross-Box stack that combines different GigaVUE G Series platforms.

Platform Pre-Loader Image Base ImageGigaVUE-2404 gvcpre8400prep gvc8600GigaVUE-420 gvbpre8400prep gvb8600GigaVUE-212 gvdpre8400prep gvd8600


Ta

T

S

CS

Upgrade Paths

Table 1-3 outline the correct upgrade path to v8.6.00 for both Standalone andCross-Box Stacked environments.

GigaVUE-2404 Running v7.0.xx with a GigaSMART Blade

The only exception to the paths shown in the table above is for a GigaVUE-2404running v7.0.xx with a GigaSMART blade installed. The GigaSMART software onlysupports direct upgrades to v8.6.00 from v7.1.xx and later. These systems must usethe following upgrade paths:

1. v7.0.xx -> v7.1.xx (Base Image)

2. v7.0.xx -> v7.1.xx (GigaSMART Image) (reboot, config save)

3. v7.1.xx -> 8.6.xx (Base Image)

4. v7.1.xx -> 8.6.xx (GigaSMART Image) (reboot, config save).

About Skip-Level Provisioning

IMPORTANT: Prior to v8.2.xx, GigaVUE releases required that you follow strictsequential upgrade paths – if you were on v7.0.xx and wanted to get to v8.0.xx, youhad to install v7.1.xx and v7.2.xx first. This release includes relaxed upgrade paths tov8.6.00 – so long as you are on a v7.0.xx release or later (and don’t have theGigaSMART blade installed), you can upgrade directly to v8.6.00 with no intermediateupgrade required.

NOTE: Use the show system command. If you need assistance obtaining an earlierGigaVUE installation file as part of the upgrade to v8.6.00, contact Gigamon TechnicalSupport.

ble 1-3: Upgrade Paths for Standalone and Cross-Box Stacked Environments

opology Platform Upgrade Path for GigaVUE G SeriesVisibility Fabric Nodes Runningv7.0.xx — v8.3.04

Upgrade Path for GigaVUE GSeries Visibility Fabric NodesRunning v8.3.05 — v8.6.00

tandaloneGigaVUE-2404 Direct to v8.6.00 Direct to v8.6.00

GigaVUE-420 Current Version -> Pre-Loader -> v8.6.00 Direct to v8.6.00

GigaVUE-212 Current Version -> Pre-Loader -> v8.6.00 Direct to v8.6.00

ross-Boxtacks

GigaVUE-2404s ONLY Direct to v8.6.00 Direct to v8.6.00

Others Current Version -> Pre-Loader -> v8.6.00 Direct to v8.6.00


Upgrading from Pre-v7.0.xx Releases

Table 1-4 shows the upgrade paths from Pre-v7.0.xx releases to v7.0xx. Once you areon a v7.0.xx release (or later), you can use the upgrade paths for upgrading to v8.6.00.

In general, when installing sequential releases, it is important to saveconfiguration file settings after each upgrade to migrate settings correctly. Ingeneral, each sequential upgrade requires the following steps:

1. Save the current configuration file with the next boot (nb) flag set (use show file toidentify the .cfg file with nb set).

2. Install the new GigaVUE software.

3. Reboot the system.

4. Save the configuration file with the nb flag set with the new software version.

IMPORTANT NOTE on APPLICATION FILTERS and GIGAVUE-420 UPGRADES

The v8.6.00 release for the GigaVUE-420 does not support the VoIP and Emailapplication filters that were available on the v6.1.xx release for the GigaVUE-420:

• If you want to continue to use application filters, leave your GigaVUE-420 at thev6.1.xx release.

If you wish to upgrade a v6.1.xx GigaVUE-420 to v8.6.00, make sure you delete allconfigured application port-filters and filters before performing the upgrade and savethe configuration! This ensures that your other settings are migrated successfullyduring the upgrade. Upgrading a GigaVUE-420 with application filters configuredcauses issues with version migration.

Table 1-4: Upgrade Paths to GigaVUE v8.6.00 from Pre-v7.0.xx Releases

Platform Upgrade Path to v8.6.00 File Name Format

GigaVUE-2404 • v5.0.xx -> v6.1.xx -> v7.0.xx-> v8.6.xx gvc8600

GigaSMART-6X software – No releases prior to v7.0.xx.

NOTE: The GigaSMART software only supports upgrades to v8.6.00from v7.1.xx and higher. A GigaVUE-2404 running v7.0.xx with aGigaSMART blade installed must upgrade both the base image and theGigaSMART software to v7.1.xx before upgrading to v8.6.00.

gsc8600.tgz

GigaVUE-420 • v4.0.xx -> v5.0.xx -> v6.0.xx/v6.1.xx -> v7.0.xx (or higher) ->gvbpre8400prep -> v8.6.xx

gvb8600

GigaVUE-212 No releases prior to v7.0.xx. gvd8600

GigaVUE-MP Not supported in v8.6.00. N/A

G-VUE No dependency. You can upgrade from any G-VUE version to another(for example, you can upgrade G-VUE directly from v1.0.xx to v3.6.00).

However, the G-VUE version must correspond to its partner GigaVUEsoftware version. For example, G-VUE v3.6.00 can only be used withGigaVUE v8.6.00.

gvweb8600.tgz


Upgrading Standalone Systems

The following outlines the correct steps needed for upgrading GigaVUE StandaloneSystems to software v8.6.00.

Standalone Systems Snapshot View

The following steps are used to outline a high level approach for upgrading GigaVUE GSeries Visibility Fabric Node Standalone Systems to software v8.6.00.

1. Copy the Installation Files onto your SCP/TFTP Server.

2. Save the existing configuration.

3. Back-up the existing configuration.

4. Install the pre-loader image onto each node (if required).

a. Reboot the system.

b. Save the configuration.

5. Install the base image onto each node.

6. Install the GigaSMART Software(only for GigaVUE-2404 systems with GigaSMART blades).


8. Save the configuration.

9. Install the G-VUE software onto each node.

Standalone Systems Detailed View

Copy the Installation Files onto your SCP/TFTP Server

1. Copy the appropriate installation files for each GigaVUE G Series StandaloneSystem to your SCP/TFTP server’s root directory. There are separate installationfiles for each platform:

• GigaVUE-2404gvc8600gsc8600.tgz (with GigaSMART present)

• GigaVUE-420gvbpre8400prep (if required see Table 1-3)gvb8600

• GigaVUE-212gvdpre8400prep (if required see Table 1-3)gvd8600

• All Platformsgvweb8600.tgz (for the G-VUE Web-Based GUI)


Save the Existing Configuration

2. Login to the system to be updated as a super user.

NOTE: Normal users do not have the necessary privileges to upgrade the GigaVUEG Series Visibility Fabric Node software.

3. Execute the show file command to see which configuration file has the Next bootfile and Last restored flags set to Yes.

Example: GigaVUE>show file

4. Execute the config save command with the nb argument to save your currentconfiguration to flash memory for version migration.

Example: GigaVUE> config save gigavue1.cfg nb

IMPORTANT: The saved configuration file must have the nb flag set to Yes so that itloads into memory when the GigaVUE G Series Visibility Fabric Node is rebooted.

5. Wait for the broadcast message informing you that the configuration save operationhas completed before continuing to the next step.

Back-up the Existing Configuration


Before upgrading a GigaVUE G Series Visibility Fabric Node, it’s always a good idea toback up both a binary configuration file and a text-based version of the runningconfiguration to external storage so you have a backup. You can use the followingcommands to create these backups:

Description CommandUpload a Binary Configuration File

upload -cfg <config file> SCP-server-ipaddr(A.B.C.D)|SCP-server-ipaddr(scp:[email protected])

Upload Running Configuration as a Command File

upload -cmd -running <filename> SCP-server-ipaddr(A.B.C.D)|SCP-server-ipaddr(scp:[email protected])


Install the Pre-loader Image (if required)

Install the pre-loader image in exactly the same manner that you would any GigaVUEG Series Visibility Fabric Node Standalone System. Verify that the pre-loader image isrequired by examining Table 1-3 on page 12.

7. Install the pre-loader image onto each node (if required).

a. Install gvcpre8400prep for GigaVUE-2404 systems.

b. Install gvbpre8400prep for GigaVUE-420 systems.

c. Install gvdpre8400prep for GigaVUE-212 systems.

Example: GigaVUE>install gvcpre8400prep 192.168.1.15

Example using TFTP

Example: GigaVUE>install gvcpre8400prep 192.168.1.10

Example using SCP

Example:

GigaVUE>install gvcpre8400prep scp:[email protected]:*********

The system warns you that another image file already exists in the system.An image named 'gvc8xxx' already exists in the system - continue (y/n)?

8. Press y to confirm that you want to install the new image.

The system erases the existing image and installs the new one.

IMPORTANT: Wait for this process to complete the full cycle. It is importantnot to power off or interrupt the system while the software image is beingwritten to flash memory. The system prompt will return when the imagehas installed successfully.


Example: GigaVUE> reboot




Install the Base Image


a. Install gvc8600 for GigaVUE-2404 systems.

b. Install gvb8600 for GigaVUE-420 systems.

c. Install gvd8600 for GigaVUE-212 systems.

Example using TFTP

Example: GigaVUE>install gvc8600 192.168.1.10

Example using SCP

Example:

GigaVUE>install gvc8600 scp:[email protected]: *********



The system erases the existing image and installs the new one.

IMPORTANT: Wait for this process to complete the full cycle. It is important notto power off or interrupt the system while the software image is being writtento flash memory. The system prompt will return when the image has installedsuccessfully.

Install the GigaSMART Software (if applicable)

13. Install the GigaSMART Software (only for GigaVUE-2404 systems withGigaSMART blades). Refer to Installing GigaSMART Software on page 26.


Reboot the System

When the system prompt reappears, reboot the system with the reboot command.


Example: GigaVUE> reboot

You are prompted to restart the system with the following message:System will be re-started and load filename.cfg - continue (y/n)?

15. Press y to restart the system.

Save the Configuration

When the login prompt appears, log in and use the config save command with the nboption to save your configuration in the new version format and set it to boot next.



Install the G-VUE Software

17. Install the G-VUE software. See Installing G-VUE Software on page 28.


Upgrading Cross-Box Stacks

The following outlines the correct steps needed for upgrading GigaVUE Cross-BoxStacks to software v8.6.00.

Cross-Box Stacks Snapshot View

The following steps are used to outline a high level approach for upgrading GigaVUE GSeries Visibility Fabric Node Cross-Box Stacks to software v8.6.00.

1. Copy the installation files onto your SCP/TFTP Server.

2. Synchronize the GigaVUE G Series Nodes.

3. Save the existing configuration.


5. Install the pre-loader image if required.

a. Install the pre-loader image onto each Slave node beginning with the furthestSlave node working back to the Master node. DO NOT REBOOT AT THISPOINT.

b. Install the pre-loader image onto the Master node. DO NOT REBOOT AT THISPOINT.

c. Reboot each Slave node in sequence beginning with the furthest Slave nodeworking back to the Master node.

d. Reboot the Master node.

e. Save the configuration.


a. Install the base image onto each Slave node beginning with the furthest Slavenode working back to the Master node. DO NOT REBOOT AT THIS POINT.

b. Install the base image onto the Master node. DO NOT REBOOT AT THISPOINT.

c. Install the GigaSMART Software (if applicable) onto each Slave nodebeginning with the furthest Slave node working back to the Master node. DONOT REBOOT AT THIS POINT.

d. Reboot each Slave node in sequence beginning with the furthest Slave nodeworking back to the Master node.

e. Reboot the Master node.

f. Save the configuration.

7. Install the G-VUE software onto the Master node.

8. Verify that the installation is successful.


Cross-Box Stacks Detailed View

The procedure below describes how to upgrade systems in both Classic Mode andMaster/Slave Mode. To distinguish between commands for Classic Mode and Master/Slave Mode Cross-Box stacks, the procedure uses the following Box IDs andconfiguration filenames:

Notes on Master/Slave Cross-Box Stack Upgrades

• For Master/Slave Mode stacks, all of the commands will be issued from the Masternode using the dbid argument to specify the destination Slave node. All Slavenodes will need network connectivity from their Ethernet Management Port in orderto download the software image from the TFTP Server.

• For Master/Slave Mode stacks, Gigamon requires the following:

• First, install the image onto each Slave node in sequence that is physicallylocated the furthest from the Master node while working your way backtoward the Master node. The Master node should be the last to be installed.

• Last, reboot each Slave node in sequence that is physically located thefurthest from the Master node while working your way back toward theMaster node. The Master node should be the last to be rebooted.

Copy the Installation Files on your SCP/TFTP Server

1. Copy the appropriate installation files for each GigaVUE G Series Cross-Box Stackto your SCP/TFTP server’s root directory. There are separate installation files foreach platform:

• GigaVUE-2404gvcpre8400prep (if required see Table 1-3)gvc8600gsc8600.tgz (with GigaSMART present)

• GigaVUE-420gvbpre8400prep (if required see Table 1-3)gvb8600

• GigaVUE-212gvdpre8400prep (if required see Table 1-3)gvd8600

• All Platformsgvweb8600.tgz (for the G-VUE Web-Based GUI)

Box ID Configuration File

Classic Mode 1 gigavue1.cfg

Master/Slave Mode 10 gigavue10.cfg


Synchronizing GigaVUE G Series Nodes(Master/Slave Cross-Box Stacks Only)

Use the following procedure to synchronize the GigaVUE G Series Nodes (Master/Slave Cross-Box Stacks Only):

2. Use the show xbsync all command to verify that all nodes in the stack are in sync.

If the stack is not in sync, do the following:

a. Issue the config xbsync all command from the Master node to synchronizethe stack.

b. Check the synchronization status again with show xbsync all.

• If the stack is now in sync, you can proceed with the rest of the upgradeprocedure.

• If the stack is still not in sync, proceed with the upgrade. At the conclusion ofthe upgrade, restore the settings using either the text-based command file orbinary configuration file you previously uploaded. The commands are asfollows:

Save the Existing Configuration

3. Use the config save command with the nb argument to save the currentconfiguration of each system in the stack. For example:

IMPORTANT: The saved configuration file must have the nb flag set to Yes so that itloads into memory when the GigaVUE G Series Visibility Fabric Node is rebooted.

4. Wait for the broadcast message informing you that the configuration save operationhas completed before continuing to the next step.

File Type Restore CommandText-Based Command File

install -clone <command file> <SCP/TFTP server address>

Binary Configuration File

Download binary configuration file to flash from SCP/TFTP server:install -cfg <configfile.cfg> <SCP/TFTP server address>

Install binary configuration file from flash:config restore <configfile.cfg>

Classic Mode config save <filename.cfg> nb

Master/Slave Mode config save <filename.cfg> nb dbid 10 (individual nodes)

OR

config save <filename.cfg> nb dbid all (all nodes)


Back-up the Existing Configuration

Back-up both a text-based version of the running configuration and a binaryconfiguration file to external storage so you have a backup. You can use the followingcommands to create these backups:.

Install the Pre-loader Image (if required)

5. Install the pre-loader image onto each Slave node beginning with the furthest Slavenode working back to the Master node. DO NOT REBOOT AT THIS POINT.

a. Install gvcpre8400prep for GigaVUE-2404 systems.

b. Install gvbpre8400prep for GigaVUE-420 systems.

c. Install gvdpre8400prep for GigaVUE-212 systems.

See Table 1-3 on page 12 for information regarding the correct upgrade path tov8.6.00.

NOTE: Do not upgrade the GigaSMART blade after installing the appropriate pre-loaderimage.

When you reboot a GigaVUE-2404 Visibility Fabric Node with a GigaSMARTblade after installing the appropriate pre-loader image, you may see thefollowing error message:

GigaVUE & GigaSMART software version mismatch on slot x. GSOP application failed

This error message can be safely ignored. It will no longer appear after thesystem is eventually upgraded to the base image.

Example:


Description CommandUpload Running Configuration as Command File

upload -cmd -running <filename> TFTP-server-ipaddr(A.B.C.D)|SCP-server-ipaddr(scp:[email protected])

Upload a Binary Configuration File

upload -cfg <config file> TFTP-server-ipaddr(A.B.C.D)|SCP-server-ipaddr(scp:[email protected])

Classic Mode install gvcpre8400prepTFTP_IP_Address|SCP_IP_Address

Master/SlaveMode

install gvcpre8400prepTFTP_IP_Address|SCP_IP_Address dbid 10



The system erases the existing image and install the new one.


7. Install the pre-loader image onto the Master node. DO NOT REBOOT AT THISPOINT.

8. Reboot the system with the Reboot command. If this is a Master/ Slave Modestack, reboot the systems beginning with the furthest Slave node working back tothe Master node. The Master node should be the last one to be rebooted. Acommand example reads:

You will be prompted to restart the system with the following message:

System will be re-started and load filename.cfg - continue (y/n)?

9. Press “y” to restart the system.

10. Use the config save command with the nb option to save the configuration of eachsystem in the stack in the new version format and set it to boot next. For example:

Install the Base Image

11. Install the base image onto each Slave node beginning with the furthest Slave nodeworking back to the Master node. DO NOT REBOOT AT THIS POINT.

a. Install gvc8600 for GigaVUE-2404 systems.

b. Install gvb8600 for GigaVUE-420 systems.

c. Install gvd8600 for GigaVUE-212 systems.

See Table 1-3 on page 12 for information regarding the correct upgrade path tov8.6.00.

Classic Mode reboot

Master/Slave Mode reboot dbid 10

Classic Mode config save gigavue1.cfg nb

Master/Slave Mode config save gigavue10.cfg nb dbid 10


Example:



The system erases the existing image and install the new one.


13. Install the base image onto the Master node. DO NOT REBOOT AT THIS POINT.

Install the GigaSMART Software (if applicable)

If your system includes a GigaSMART blade, upgrade it as follows:

14. After updating a GigaVUE-2404 Visibility Fabric Node with a base image, upgradethe GigaSMART software before rebooting the system in the next step. Refer toInstalling GigaSMART Software on page 26.

Reboot the System

15. Reboot the system with the Reboot command. If this is a Master/ Slave Modestack, reboot the systems beginning with the furthest Slave node working back tothe Master node. The Master node should be the last one to be rebooted. Acommand example reads:

You will be prompted to restart the system with the following message:

System will be re-started and load filename.cfg - continue (y/n)?

16. Press “y” to restart the system.

Classic Mode install gvc8600 TFTP_IP_Address|SCP_IP_Address

Master/SlaveMode

install gvc8600 TFTP_IP_Address|SCP_IP_Address dbid 10

Classic Mode reboot

Master/Slave Mode reboot dbid 10


Save the Configuration

17. Use the config save command with the nb option to save the configuration of eachsystem in the stack in the new version format and set it to boot next. For example:

Install the G-VUE Software

18. Install the G-VUE software. See Installing G-VUE Software on page 28.

Verify that the Installation is Successful

Use the following steps to ensure that all xbmaps are restored after the upgrade:

19. Ensure that all systems in the stack are operating correctly – traffic is flowing to allsystems in the stack and xbmaps are forwarding traffic as expected.

20. Use the commands below to verify the settings for each system in the stack.

• Classic Mode Stacks – Use the show diag command on each system in thestack.

• Master/Slave Mode Stacks – Use the show stack_info and show diagcommand from the Master node for each Slave node in the stack.

Classic Mode config save gigavue1.cfg nb

Master/Slave Mode config save gigavue10.cfg nb dbid 10

Table 1-5: Verifying Stacking Settings

GigaVUE-2404 GigaVUE-420

Box ID

active_link

Included with active_link x1_bid

x2_bid

ib_cable_len ib_cable_len

The Link Status for all stacking interfaces displays as 1 (up).

Communication between the systems is functioning. Each systemshould be able to identify the modules in the other systems.


Installing GigaSMART Software

The GigaSMART-6X is an optional blade for the GigaVUE-2404. It has its own onboardprocessor and software image so that it can provide packet modification features suchas timestamping, packet slicing, masking, de-duplication, header stripping, tunnelstripping, and source port labeling.

After physically installing the GigaSMART blade in the GigaVUE-2404, you can installits software with the install -gs command, as described in the following procedure.

IMPORTANT: Always upgrade the base GigaVUE software to the latest version beforeupgrading the GigaSMART software to the corresponding version.

IMPORTANT: To preserve GigaSMART Operations across an upgrade, do not reboot thesystem between the upgrade of the GigaVUE software and the GigaSMART software.If you do reboot the system between the upgrade of the base software and theGigaSMART software, you will need to recreate your GigaSMART operations.

1. Ensure you have already upgraded the GigaVUE-2404 base software. Theversions of the GigaVUE and GigaSMART software must match for successfuloperations.

2. Copy the gsc8600.tgz installation file for the GigaSMART to your TFTP server’sroot directory. Do not unzip the file.

3. Login to the system to be updated as a super user.

4. Execute the install -gs command to install the GigaSMART software. The syntaxis as follows:

install -gs gsc8xxx.tgz slot_val(2|3) TFTP-server-ipaddr|SCP-server-ipaddr

For example, the following command installs the GigaSMART software namedgsc8600.tgz for a blade in Slot 2 from a TFTP server at 192.168.1.10 with theusername gigamon:install -gs gsc8600.tgz 2 192.168.1.10

The GigaVUE G Series Visibility Fabric Node downloads the installation file andsends it to the GigaSMART blade, informing you when the installation is complete.

IMPORTANT: Wait for this process to complete. It is important not to power offor interrupt the system while the software is being written to flash. Thesystem prompt will return when the installation is complete.

5. The system automatically resets the GigaSMART blade after the software isinstalled. When it is finished resetting the blade, you may see the following errormessage:

GigaVUE & GigaSMART software version mismatch on slot x. GSOP application failed.

This error message can be safely ignored. It will no longer appear after rebootingthe system.


Licensing GigaSMART Software

GigaSMART software must be licensed before it can be used:

• If you purchased a GigaVUE-2404 with a GigaSMART blade already installed, yourGigaSMART software will be licensed at the factory. You can use the show systemcommand to verify that the license is already configured. If it is, you do not need toauthorize it again. The following show system output shows a licensedGigaSMART-6X in Slot 2:------------------------------------------------------------------------------------------------GigaSMART Slot2 : ReadyVersion : App 8.6.00 Cfg 7.3.1 OS MDE-2.1.0.98943-svn21686License Key : B6219AE9-D025F931-8A7669DF-58526FEDLicensed Apps : Slicing Masking Timestamp SrcPort-Label Tunneled-Ports Dedup Strip L7lbSupported Apps : Slicing Masking Timestamp SrcPort-Label Tunneled-Ports Dedup Strip L7lbLicensed MACs : 00:1D:AC:0A:0A:18, Count=8Time Source : LOCAL (Actual LOCAL)------------------------------------------------------------------------------------------------

• If you purchased a GigaSMART-6X blade separately and are installing it in anexisting system, you must use the config system gs_license command to licenseyour software. See below.

Contact your Gigamon Sales representative to obtain a license for your GigaSMARTsoftware. Use the following procedure to apply the GigaSMART license:

1. Apply the license key in the GigaVUE CLI with the following command:config system gs_license <xxxxxxxx-xxxxxxxx-xxxxxxxx-xxxxxxxx> slot <slot_val>]

For example:config system gs_license B62199EE-D725F92F-D37D3AA1-7C214214 slot 2

The GigaVUE G Series Visibility Fabric Node applies the license key, informing you ofits success or failure:

• If successful, you will see the newly applied license key in the show systemoutput.

• If not successful, contact Gigamon Technical Support.


Installing G-VUE Software

Keep in mind the following G-VUE installation notes:

• GigaVUE v8.6.00 must be installed to use G-VUE v3.6.00. G-VUE v3.6.00 will notwork with previous GigaVUE software versions (and vice-versa).

• G-VUE v3.6.00 can be installed on GigaVUE G Series Visibility Fabric Nodesrunning in either Master/Slave or Classic stacking modes. In a Master/Slave stack,G-VUE only needs to be installed on the Master node.

Installation Procedure

Use the following procedure to install the G-VUE software on a GigaVUE-2404,GigaVUE-420, or GigaVUE-212.

1. Untar/unzip the contents of gvweb8600.tgz to your SCP/TFTP server’s rootdirectory. The command in Linux is as follows:

tar -zxvf gvweb8600.tgz

NOTE: Some unzip/untar utilities may require you to unzip twice – once for thetop-level gvweb8600.tgz file and once for the tarball of the \web folder inside.

NOTE: If you have a previous version of the G-VUE software in your SCP server’sroot directory, make sure you choose to overwrite the existing files during the unzipprocess.

2. When all files are unzipped/untarred, you should have the following files in yourSCP server’s root directory:

• File: gvweb8600 – Web installation file used with install -web command.

• Folder: \web – Files for web-based G-VUE interface.

3. Use the install -web command to install G-VUE. For example:

install -web gvweb8600 scp:[email protected]

The installer copies the G-VUE software from your file server to the GigaVUE GSeries Visibility Fabric Node, returning you to the system prompt when finished.

NOTE: If you are using SCP and the server requires a password, you will beprompted for it before the software is downloaded.

IMPORTANT: Wait for this process to complete. It is important not to power offor interrupt the system while the software is being written to flash. Thesystem prompt will return when the installation is complete.


Cloning System Configuration from One System to Another

The install command provides a -clone argument that lets you download and apply acommand file stored on an SCP server to the GigaVUE G Series Visibility Fabric node.With a single command, you can clone one system’s configuration to another. Theoverall procedure is as follows:

1. Login as a super user to the system whose configuration you want to apply to asecond box and use upload -cmd to upload a command file containing itsconfiguration to an SCP server.

For example, the following command uploads the running configuration to acommand file named cloneconfig.txt on the SCP server at 192.168.1.10 with theusername root:GigaVUE>upload -cmd -running scp:[email protected] cloneconfig.txtCreating system commands...Reading running cfg from memory...Converting to commands...Uploading config-text file....Config file upload to file cloneconfig.txt succeed (12436 bytes).

NOTE: If you don’t specify a filename for the command file, it’s generatedautomatically using the chassis type and serial number.

2. Login to the system to be reconfigured and use the following command to applythe clone configuration to the second system:

install -clone <command file from Step a> <SCP server address>

In this example, the exact command would be:install -clone cloneconfig.txt scp:[email protected]

Figure 1 summarizes the process.

Figure 1: Cloning GigaVUE Configuration with install-clone

When you apply the clone configuration, the GigaVUE G Series Visibility Fabricnode downloads the configuration file to the target system and makes sure thecurrent software version is compatible with the command file. Then, each line in thefile is applied to the system and printed to the CLI with a -> prefix. Issues and errors


are displayed in blue so you can identify issues that need to be addressed after theclone procedure.

3. When the system finished the clone procedure, it prompts you to save the newconfiguration. Make sure you include the -nb argument if you want to use the newconfiguration the next time the system restarts.

4. If any of the settings in the clone configuration file require a restart, the systemprompts you to reboot.

Cloning a System in a Cross-Box Stack

You clone a system in a Cross-Box Stack in the same way you do a standalone system.The only difference is that if you are working from a Master node, you must use thedbid argument to identify the system whose configuration you want to upload to theSCP server. Then, run the install -clone command over the target system’s serialConsole port so you don’t lose connectivity when the new IP configuration is applied.All configuration information from the source system, including Box ID, IP, and stackingsettings come over, allowing the Master node to discover the replacement system rightaway.


Documents

GigaVUE G Series Upgrade Guide v8.6.00