Upgrading with Foglight for Storage Management
Before you begin, review the licensing notes for your currently installed version.
During this upgrade process, Foglight for Storage Management is upgraded to version 4.3, and the Foglight for Virtualization cartridges are upgraded to the versions released in FVE 8.4, and Foglight is upgraded to version 126.96.36.199. The Foglight Agent Manager will be upgraded to version 188.8.131.52.1
To upgrade Foglight for Storage Management:
- Download the Foglight for Storage Management 4.3 installation package for your platform from Quest Support.
- Obtain updated Foglight for Storage Management 4.3 license. To purchase a full license, contact your Foglight sales representative.
- Create a support bundle from your Management Server. For instructions, see "Managing Support Bundles" in the Administration and Configuration Help.
- Back up Foglight by backing up the file system and the Foglight database. For instructions, see "Backing up Foglight" in the Administration and Configuration Help.
Important: If you are using Oracle RAC, you must back up the oracle-ds.xml file (or any other database connection files) before performing the upgrade.
- Deactivate all agents from the "Administration | Agents | Agent Status" dashboard.
- Stop the Management Server. To verify that all Management Server processes have stopped, type the following command (replacing the default installation directory "Quest_Software" with your installation directory):
tasklist /v | find "Quest_Software"
Important: If your Management Server uses an external database, do not stop the database. It is important that it continue to run during the upgrade.
- If you are running the upgrade using a user ID with domain administer privileges run the following command before proceeding with the upgrade: "ICacls [foglight_home]\state\PostgreSQL-data /t /grant [domain]\administrator:(OI)(CI)F"
Where "[domain]\administrator" is a local or domain administrator.
- Launch the installation package for your platform and choose Upgrade. Follow the instructions in the installation wizard.
Note : The database upgrade may be time consuming if you have a large topology.
- Upgrade any external Agent Managers (the internal Agent Manager is upgraded automatically). For instructions, see the Foglight for Virtualization, Enterprise Edition Upgrade Guide.
- After deploying the new storage agents to an agent manager, the agent manager "baseline.jvmargs.config" file, if it has been customized previously, may need to be updated. Specifically:
- Any memory settings under 3 Gb can be removed.
- Any memory settings over 3Gb should be reduce by 3Gb
The storage agent now includes support for dynamic memory settings and the previous memory settings in baseline.jvmargs.config are not needed. The amount of memory used for storage agents will be adjusted automatically as more agents are brought online.
- Install the updated Foglight for Storage Management 4.3 license.
- Upgrade the Storage Management Agents from the "Storage & SAN | Storage Environment | Administration" dashboard, for each Agent Manager Host shown in the StorageAgentMaster Monitor Agents view.
For instructions, see "Deploying Storage Agents after an Upgrade" in the "Managing Storage in Virtual Environments Installation and Configuration Guide".
The upgrade dialog will:
- Upgrade StorageAgentMasterMonitor.gar
- If needed: Deactivate StorageAgentMaster.gar and remove the Windows service running on the Agent Host named FoglightStorageManagerDatabase or HDCCService.
- Deploy StorageAgentMasterDB.gar and create an agent.
- Upgrade StorageCollector.gar
- Upgrade the VMware Performance Agent. For instructions, see "Upgrading the VMware Performance Agent" in the Foglight for Virtualization, Enterprise Edition Upgrade Guide.
- If you had enabled the trial license for Foglight for Virtualization EE 7.x before upgrading, and you want to use Foglight for Virtualization EE features after upgrading, you may also need to upgrade some additional agents. For instructions, see the Foglight for Virtualization, Enterprise Edition Upgrade Guide.
New in this Release
Version 4.3.0 contains the following new features and updates:
- Software Development Kit (SDK) to create agents written in Python and a specialized SDK to create Python agents for collection of data from storage arrays.
- Streamlined Agent Creation Wizard that allows adding multiple agents.
- Improved Hyper-V storage reports, topology and performance collection combined with Hyper-V cartridge.
- Summary "Storage Capacity" top-level dashboard added.
- Improved UI performance for larger monitored environments.
- Optimized Capacity Usage Trends for arrays.
- Performance collection intervals for all monitored elements changed to every 15 minutes. Intervals that had been modified to be less frequent are not changed.
- An update of the included Java VM to version 184.108.40.206. This has implications for both agent and server SSL and TLS connections. Review the notes below.
- None of the monitoring agents included with Foglight for Storage Management currently support the HA (high availability) feature included with Foglight Agent Manager.
- This release of Foglight for Storage Management is designed for use with Foglight 220.127.116.11 or later. Existing users of Foglight for Virtualization, version 8.2 or earlier will need to upgrade to at least version 8.4. In addition, the Foglight Agent Manager must be upgraded to at least version 18.104.22.168.1.
- The included update of the Java VM for both the agent manager and the Foglight™ Management Server includes security updates that remove support for RC4 cipher suites, MD5 signed SSL certificates, and support for SSLv3. Older versions of the management server using the default installation certificate will be provided with an updated certificate. If a user-provided SSL certificate was configured then it must be upgraded to comply with the Java security requirements. This should be done before installing the server upgrade. Future updates to Java may also disable support for SHA-1 signed SSL certificates. SHA-256 is recommended as the signature algorithm for all SSL certificates.
- Any agents using SSL to monitor arrays or array management hosts use the same security restrictions. SSL certificates on arrays should be upgraded to SHA-256 signed certificates if SSL connections are required. Agents can switch to non-SSL connections if desired.
- Installing the Foglight™ Management Server on Windows 10 or Windows Server 2016 is not supported at this time. Future releases will support Windows Server 2016, but not any of the "Technical Preview" versions.
- When connecting to BNA to monitor Brocade switches, only read-only access is required. The documentation has been updated to reflect this
For a list of issues fixed in this release, see the issues listed in Resolved Issues.
Issues Resolved in this Release
|VFGLS-3433||[NetApp] 8.3 Cluster-Mode: Calculate physical disk sizes close to the values reported by NetApp OnCommand and Command Line Interface (CLI). If the previous behavior is desired, edit baseline.jvmargs.config file and add the VM parameter -Dcom.dell.foglight.storage.collector.hostside.NetAppClientCollex.preserve42DiskSizes=true|
|VFGLS-3391||Compellent: Default timeout for monitoring Compellent systems extended from 30 seconds to 120 seconds.|
|VFGLS-3389||Netapp 8.3 Cluster-Mode: Assign performance metrics to the correct controller on the Controller and Ports tab.|
|VFGLS-3381||Disk state is set to "no information" instead of "removed" when a disk is not seen during a performance collection but was previously seen during a topology collection.|
|VFGLS-3378||NetApp 8.2 Cluster-Mode: Assign Controller Metrics of each node precisely.|
|VFGLS-3323||FAQts: Storage and Filers: More clearly defined "Which arrays or filers have the least free (unallocated) disk space" question.|
|VFGLS-3319||Removed Microsoft .NET Framework 3.5 requirement. There is no longer a requirement for any .NET version to be installed.|
|VFGLS-3290||Removed rules StSAN E Array/Filer No Performance Collections with Email and StSAN E FC Switch No Performance Collections with Email as they are no longer required and have been obsoleted.|
|VFGLS-3270||Compellent Prism UID mapping failure may prevent performance collection of ports, disks and volumes.|
|VFGLS-3262||Hitachi Upgrading agents configured to monitor Hitachi arrays may take longer than usual and may not complete at all.|
|VFGLS-3246||Equallogic Prism UID mapping error between incorrect performance and inventory collection may cause volume statics to be incorrectly associated.|
|VFGLS-3151||Reduced logging when SMI-S server does not support all the queries generated.|
|VFGLS-3095||Upgrade Agent may hang at "Deploying Storage Collector" in some environments.|
|VFGLS-3036||Fixed version under Help and About.|
|VFGLS-2918||Allow editing Storage Collector Agent port and IP address after creation.|
|VFGLS-2832||Deploying Storage Collector cartridge as part of creating an agent may cause FglAMs to restart and the deployment may fail.|