Академический Документы
Профессиональный Документы
Культура Документы
GigaVUE-420
GigaVUE-212
GigaVUE G Series
Upgrade Guide
Version 8.6.00
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 without
Gigamons 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/legaltrademarks. All other trademarks are the trademarks of their respective owners.
DOCUMENT REVISION 12/2/13
Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Other Sources of Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Contacting Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Premium Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
24
24
25
25
25
26
27
28
29
30
Summary
Premium Support
Email Gigamon at info@gigamon.com for information on purchasing 24x7 Premium
Support for your GigaVUE G Series Visibility Fabric Node. Premium Support entitles
you to around-the-clock phone support with a dedicated Support Engineer every day of
the week.
Chapter 1
E-mail: support@gigamon.com
Required
Items
Description
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 servers IP address so that it can
connect to the server and download the image.
NOTE: Note that SCP support is available starting with v8.2.xx. When using SCP, keep in
mind that Gigamon requires Linux or UNIX-based SCP servers for use with the GigaVUE
G Series Visibility Fabric Node Windows-based servers are not supported. There are
freeware SCP servers available on the Internet. A web search will provide links to many
implementations.
All Platforms
gvweb8600.tgz
Gzip file containing the G-VUE software. The zip includes both the web installation file and
the web-based software itself. When completely unzipped to your SCP Root Directory, you
should 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 web
search for tar windows will provide links to many such utilities.
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 are
operating 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
GigaVUE-2404
Gzip file containing the software for the GigaSMART-6X blade. This file is installed on a
GigaVUE-2404 with a GigaSMART-6X blade physically installed.
You do not need to unzip this file. It can be installed directly using the install -gs
command.
NOTE: The GigaSMART and GigaVUE versions must match for successful usage of
GigaSMART operations.
NOTE: To preserve GigaSMART Operations across an upgrade, do not reboot the
system 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 the GigaSMART
software, you can use config restore after the upgrade to restore all GigaSMART
Operations.
GigaVUE-420
Required
Items
Description
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 installing
the 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 the
GigaVUE-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 installing
the 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 the
GigaVUE-212.
NOTE: This file may be provided in a zipped format (for example, gvd8600.zip).
10
(Standalone or Stacked).
2. GigaVUE-2404 products running v7.0.xx - v8.3.04 in a Mixed Stack1 that
Follow the correct upgrade paths to v8.6.00 for the criteria which meets your GigaVUE
G Series Visibility Fabric Node needs.
Platform
Pre-Loader Image
Base Image
GigaVUE-2404
gvcpre8400prep
gvc8600
GigaVUE-420
gvbpre8400prep
gvb8600
GigaVUE-212
gvdpre8400prep
gvd8600
1.
A Mixed Stack is a Cross-Box stack that combines different GigaVUE G Series platforms.
11
Upgrade Paths
Table 1-3 outline the correct upgrade path to v8.6.00 for both Standalone and
Cross-Box Stacked environments.
Table 1-3: Upgrade Paths for Standalone and Cross-Box Stacked Environments
Topology
Platform
GigaVUE-2404
Standalone
Cross-Box
Stacks
Direct to v8.6.00
Direct to v8.6.00
GigaVUE-420
Direct to v8.6.00
GigaVUE-212
Direct to v8.6.00
Direct to v8.6.00
Direct to v8.6.00
Direct to v8.6.00
GigaVUE-2404s ONLY
Others
12
GigaVUE-2404
gvc8600
gsc8600.tgz
v4.0.xx -> v5.0.xx -> v6.0.xx/v6.1.xx -> v7.0.xx (or higher) ->
gvbpre8400prep -> v8.6.xx
gvb8600
GigaVUE-212
gvd8600
GigaVUE-MP
N/A
G-VUE
gvweb8600.tgz
If you want to continue to use application filters, leave your GigaVUE-420 at the
v6.1.xx release.
If you wish to upgrade a v6.1.xx GigaVUE-420 to v8.6.00, make sure you delete all
configured application port-filters and filters before performing the upgrade and save
the configuration! This ensures that your other settings are migrated successfully
during the upgrade. Upgrading a GigaVUE-420 with application filters configured
causes issues with version migration.
13
System to your SCP/TFTP servers root directory. There are separate installation
files for each platform:
14
GigaVUE-2404
gvc8600
gsc8600.tgz (with GigaSMART present)
GigaVUE-420
gvbpre8400prep (if required see Table 1-3)
gvb8600
GigaVUE-212
gvdpre8400prep (if required see Table 1-3)
gvd8600
All Platforms
gvweb8600.tgz (for the G-VUE Web-Based GUI)
NOTE: Normal users do not have the necessary privileges to upgrade the GigaVUE
G Series Visibility Fabric Node software.
3. Execute the show file command to see which configuration file has the Next boot
Before upgrading a GigaVUE G Series Visibility Fabric Node, its always a good idea to
back up both a binary configuration file and a text-based version of the running
configuration to external storage so you have a backup. You can use the following
commands to create these backups:
Description
Command
Upload a Binary
Configuration File
Upload Running
Configuration as a
Command File
15
Example:
GigaVUE>install gvcpre8400prep scp:gigamon@192.168.1.20
password:*********
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 important
not to power off or interrupt the system while the software image is being
written to flash memory. The system prompt will return when the image
has installed successfully.
9. Reboot the system.
16
Example:
GigaVUE>install gvc8600 scp:gigamon@192.168.1.20
password: *********
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)?
12. 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 important not
to power off or interrupt the system while the software image is being written
to flash memory. The system prompt will return when the image has installed
successfully.
17
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.
18
Slave node working back to the Master node. DO NOT REBOOT AT THIS
POINT.
b. Install the pre-loader image onto the Master node. DO NOT REBOOT AT THIS
POINT.
c. Reboot each Slave node in sequence beginning with the furthest Slave node
node 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 THIS
POINT.
c. Install the GigaSMART Software (if applicable) onto each Slave node
beginning with the furthest Slave node working back to the Master node. DO
NOT REBOOT AT THIS POINT.
d. Reboot each Slave node in sequence beginning with the furthest Slave node
19
Configuration File
Classic Mode
gigavue1.cfg
Master/Slave Mode
10
gigavue10.cfg
For Master/Slave Mode stacks, all of the commands will be issued from the Master
node using the dbid argument to specify the destination Slave node. All Slave
nodes will need network connectivity from their Ethernet Management Port in order
to download the software image from the TFTP Server.
First, install the image onto each Slave node in sequence that is physically
located the furthest from the Master node while working your way back
toward the Master node. The Master node should be the last to be installed.
Last, reboot each Slave node in sequence that is physically located the
furthest from the Master node while working your way back toward the
Master node. The Master node should be the last to be rebooted.
to your SCP/TFTP servers root directory. There are separate installation files for
each platform:
20
GigaVUE-2404
gvcpre8400prep (if required see Table 1-3)
gvc8600
gsc8600.tgz (with GigaSMART present)
GigaVUE-420
gvbpre8400prep (if required see Table 1-3)
gvb8600
GigaVUE-212
gvdpre8400prep (if required see Table 1-3)
gvd8600
All Platforms
gvweb8600.tgz (for the G-VUE Web-Based GUI)
the 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 upgrade
procedure.
If the stack is still not in sync, proceed with the upgrade. At the conclusion of
the upgrade, restore the settings using either the text-based command file or
binary configuration file you previously uploaded. The commands are as
follows:
File Type
Restore Command
Text-Based
Command File
Binary
Configuration
File
Master/Slave Mode
IMPORTANT: The saved configuration file must have the nb flag set to Yes so that it
loads into memory when the GigaVUE G Series Visibility Fabric Node is rebooted.
4. Wait for the broadcast message informing you that the configuration save operation
21
Command
Upload Running
Configuration as
Command File
Upload a Binary
Configuration File
node 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 to
v8.6.00.
NOTE: Do not upgrade the GigaSMART blade after installing the appropriate pre-loader
image.
When you reboot a GigaVUE-2404 Visibility Fabric Node with a GigaSMART
blade after installing the appropriate pre-loader image, you may see the
following 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 the
system is eventually upgraded to the base image.
Example:
Classic Mode
install gvcpre8400prepTFTP_IP_Address|SCP_IP_Address
Master/Slave
Mode
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)?
22
The system erases the existing image and install the new one.
IMPORTANT: Wait for this process to complete the full cycle. It is important not
to power off or interrupt the system while the software image is being written
to flash memory. The system prompt will return when the image has installed
successfully.
7. Install the pre-loader image onto the Master node. DO NOT REBOOT AT THIS
POINT.
8. Reboot the system with the Reboot command. If this is a Master/ Slave Mode
stack, reboot the systems beginning with the furthest Slave node working back to
the Master node. The Master node should be the last one to be rebooted. A
command example reads:
Classic Mode
reboot
Master/Slave Mode
reboot dbid 10
You will be prompted to restart the system with the following message:
System will be re-started and load filename.cfg - continue (y/n)?
system in the stack in the new version format and set it to boot next. For example:
Classic Mode
Master/Slave Mode
See Table 1-3 on page 12 for information regarding the correct upgrade path to
v8.6.00.
23
Example:
Classic Mode
Master/Slave
Mode
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)?
12. Press y to confirm that you want to install the new image.
The system erases the existing image and install the new one.
IMPORTANT: Wait for this process to complete the full cycle. It is important not
to power off or interrupt the system while the software image is being written
to flash memory. The system prompt will return when the image has installed
successfully.
13. Install the base image onto the Master node. DO NOT REBOOT AT THIS POINT.
the GigaSMART software before rebooting the system in the next step. Refer to
Installing GigaSMART Software on page 26.
stack, reboot the systems beginning with the furthest Slave node working back to
the Master node. The Master node should be the last one to be rebooted. A
command example reads:
Classic Mode
reboot
Master/Slave Mode
reboot dbid 10
You will be prompted to restart the system with the following message:
System will be re-started and load filename.cfg - continue (y/n)?
24
system in the stack in the new version format and set it to boot next. For example:
Classic Mode
Master/Slave Mode
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 all
Classic Mode Stacks Use the show diag command on each system in the
stack.
Master/Slave Mode Stacks Use the show stack_info and show diag
command from the Master node for each Slave node in the stack.
Table 1-5: Verifying Stacking Settings
GigaVUE-2404
GigaVUE-420
Box ID
active_link
x1_bid
x2_bid
ib_cable_len
ib_cable_len
25
versions of the GigaVUE and GigaSMART software must match for successful
operations.
2. Copy the gsc8600.tgz installation file for the GigaSMART to your TFTP servers
is 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 named
gsc8600.tgz for a blade in Slot 2 from a TFTP server at 192.168.1.10 with the
username gigamon:
install -gs gsc8600.tgz 2 192.168.1.10
The GigaVUE G Series Visibility Fabric Node downloads the installation file and
sends 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 off
or interrupt the system while the software is being written to flash. The
system prompt will return when the installation is complete.
5. The system automatically resets the GigaSMART blade after the software is
installed. When it is finished resetting the blade, you may see the following 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 rebooting
the system.
26
Licensed Apps : Slicing Masking Timestamp SrcPort-Label Tunneled-Ports Dedup Strip L7lb
Supported Apps : Slicing Masking Timestamp SrcPort-Label Tunneled-Ports Dedup Strip L7lb
Licensed MACs : 00:1D:AC:0A:0A:18, Count=8
Time Source
------------------------------------------------------------------------------------------------
Contact your Gigamon Sales representative to obtain a license for your GigaSMART
software. 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 of
its success or failure:
If successful, you will see the newly applied license key in the show system
output.
27
GigaVUE v8.6.00 must be installed to use G-VUE v3.6.00. G-VUE v3.6.00 will not
work with previous GigaVUE software versions (and vice-versa).
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 servers root
File: gvweb8600 Web installation file used with install -web command.
The installer copies the G-VUE software from your file server to the GigaVUE G
Series 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 be
prompted for it before the software is downloaded.
IMPORTANT: Wait for this process to complete. It is important not to power off
or interrupt the system while the software is being written to flash. The
system prompt will return when the installation is complete.
28
second box and use upload -cmd to upload a command file containing its
configuration to an SCP server.
For example, the following command uploads the running configuration to a
command file named cloneconfig.txt on the SCP server at 192.168.1.10 with the
username root:
GigaVUE>upload -cmd -running scp:root@192.168.1.10 cloneconfig.txt
Creating 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 dont specify a filename for the command file, its generated
automatically using the chassis type and serial number.
2. Login to the system to be reconfigured and use the following command to apply
29
are displayed in blue so you can identify issues that need to be addressed after the
clone procedure.
3. When the system finished the clone procedure, it prompts you to save the new
configuration. Make sure you include the -nb argument if you want to use the new
configuration the next time the system restarts.
4. If any of the settings in the clone configuration file require a restart, the system
30