Release Notes

Cisco Energy Management - Version 5.2.0

Date: 07/07/2016

System and Installation Requirements

Cisco Energy Management Version 5.2.0 can be used for single instance installations as well as for distributed deployments, using an Cisco Energy Management Server and multiple Cisco Energy Management Controllers.

Single Server Deployment

	Minimum	Recommended 5,000 Devices	10,000 - 25,000 Devices
CPU	Dual Core, 2GHz	Dual Core, 2GHz	2 Quad CPUs
RAM	4 GB	8 GB	16 GB
Hard Disk 1)	40 GB	250 GB	500 GB
Operating System	Windows 7 (64-Bit)	Win Server 2008 R2 (64-Bit)	Win Server 2008 R2 (64-Bit)

Large Scale Multi Server Deployment

For deployments with more than 25,000 devices we recommend the use of a dedicated central server with requirements as follows:

	50,000 - 100,000 Devices	100,000 - 200,000 Devices
Deployment component	Cisco Energy Management Server	Cisco Energy Management Server
CPU	2 Quad Core CPUs	2 Quad Core CPUs
RAM	>24 GB	>32 GB
Hard Disk 1)	1 TB	2 TB
Operating System	Windows Server 2008 R2 (64-Bit)	Windows Server 2008 R2 (64-Bit)

In addition to the central server, several controllers might be required – with a maximum of 25,000 devices per controller with specifications as follows:

	up to 25,000 Devices
Deployment component	Cisco Energy Management Controller
CPU	Quad Core, 2GHz
RAM	4 GB
Hard Disk 1)	50 GB
Operating System	Windows 7 or Server (64-Bit) CentOS 6.5 (x86/x64)

Note: A single Cisco Energy Management Controller is designed to handle a maximum total of 25,000 devices.

Cisco Energy Management has a browser-based management console for configuration, operation, and reporting. For the best user experience, it is recommended that you use an up-to-date browser, such as the latest version of Google Chrome (preferred), Mozilla Firefox or Internet Explorer 11 or better. Older browsers, especially IE 6, are not fully supported. Regardless of which browser is used, JavaScript will need to be enabled.

The Controller uses Microsoft .NET 4.0 framework. If this framework is not present on the server prior to installation, it will be automatically downloaded and installed as part of the Controller installation. If the internet connection on the installation server is slow or unavailable, we recommend that you manually download and install the Microsoft .NET 4.0 framework prior to beginning the Controller installation (Download here: http://msdn.microsoft.com/en-us/netframework/).

List of supported operating systems for Cisco Energy Management Server

• Microsoft Windows 7 (64-bit)
• Microsoft Windows Server 2008 R2 (64-bit)
• Microsoft Windows Server 2012 R2

List of supported operating systems for Cisco Energy Management Controller for Windows

• Microsoft Windows 7 (32-bit/64-bit)
• Microsoft Windows Server 2008 R2 (32-bit/64-bit)
• Microsoft Windows Server 2012 R2

List of supported operating systems for Cisco Energy Management Controller for Linux

• CentOS 6.5 (x86/x64)

Updating/patching existing installations

1. Get the latest CEM Update

   For CEM Server updates as well as CEM Controller updates, the same update file is used. Files are available at Cisco Energy Management Download Page

2. Updating Order

When executing the update file, the setup wizard will guide you through the update process.

Important: If your CEM server installation runs separately from your CEM Controller installation(s), please make sure to first apply the update to the CEM server installation. During the CEM server update a keypair file will be created which later is required to update the separately hosted CEM Controllers.

When updating a CEM standalone-installation (CEM Server and CEM Controller hosted on the same machine), this keypair file is created automatically and can be found at the same directory as the CEM Installation. E.g. C:\Program Files (x86)\Cisco Energy Management Controller\service\cem_keypair.key.


3. Verify that the update process has succeeded

The update process was successful if all services are up and running and the CEM User Interface is working properly. Note that there will be a new Service called Cisco Energy Management Controller Watcher solely responsible for Cisco Energy Management Controller.

Known Issues during the update

In rare cases it could happen that the update process will not succeed for very large CEM deployments due to a timeout problem during the data base migration. Please follow these steps to verify you are affected of this issue and how to solve it:

• Step 1: Try to open the CEM User Interface. If the CEM User Interface will show up and no timeout error is shown, you are not affected by the issue. If the CEM User Interface does not respond, please proceed with Step 2.


• Step 2: Go to your Windows services and stop the Cisco Energy Management System Watcher service


• Step 3: Open the log file CiscoEnergyManagementServer.log which can be found in the log folder of your installation (C:\%InstallDir%\logs).
  Watch the log file. As soon as the line DB Schema Migration: finished for tenant appears, the migration succeeded.


• Step 4: Go back to your Windows services and start the Cisco Energy Management System Watcher service again.


• After a few seconds, CEM should be up and running again.

Additional update related information

• While patching, all Script Proxies which are part of Cisco Energy Management will be overwritten. All other Script proxies which are not part of the installation bundle will remain untouched. If you have made modifications to one or more Script Proxies which have been provided by Cisco, please create a backup of the respective files before you apply the update.

Changes from Cisco Energy Management Version 5.1.0 to 5.2.0

Highlights

• Numerous enhancements in the UI for better refresh behavior, display of pages and widgets and web browser compatibility have been implemented.
• Key performance indicator configuration and reports
• Parstream streaming export

Enhancements and Fixes

• Numerous improvements in the Map view for Assets
• In a multigroup report: the label of column was changed from "numberOfDevices" to "Count".
• A debug capability has been added to CEM script.
• Added new Script Discovery AssetConnector which provides full scripting freedom to discover and import custom device types.
• The documentation for dashboards using values from multiple controllers has been enhanced.
• An Energy-state report showing consumption and duration per energy state over time has been added.
• Support for AccelTex EnergyLink proxy has been added by default.
• A defect where the legend of a report was cut off in the export has been fixed.
• It is now possible to directly upload CSV files in the CSV Asset Connector dialog.
• Password strength can be enforced and is displayed in the password change dialog.
• Enhanced DoS protection for the web server.
• Protection against password brute force attacks for the application server portal.
• Updated TLS configurations for new installations and updated TLS libraries for state of the art transport security.
• Several display issues in the Datacenter Rack view have been fixed.
• An issue that prevented management of Mac Book Pro devices running OS X El Capitan was fixed.
• The SSH library was replaced and supports new algorithms that are used on many modern Linux distributions.
• An issue where sensor values read via IPMI could be lost has been resolved.
• An issue where the branding was not shown for a tenant has been fixed.
• An issue where scenario reports could fail after a few minutes has been fixed.
• Segments are now applied to snapshot reports.
• An issue where reports using multiple segments could omit assets has been fixed.
• The login name instead of the "full name" is displayed now in the access control settings.
• An issue that could cause up to 50% of the tenants to be not started on reboot has been fixed.
• Identical queries are now no longer queued but only accepted after the first query finished.
• An issue where child objects of sites where scanned only if the parent was scanned has been corrected.

Known issues

• There can be an issue logging in to Cloudmanager with Safari, IE11 and Edge. For safari opening a new tab and logging in again prevents the issue.
• With Internet Explorer 11 and Microsoft Edge Ctrl + C to copy contents from the script editor does not work.
  As a workaround for you can mark the text and drag and drop it into a text editor.
• Custom metrics that are created after a device with static values that are used in the metric will not get updated for such a "static device".
• Sometimes values from the last hour in a report can be missing in a report.
• The license may be shown as invalid after the upgrade for up to 1 day. As a workaround a license check can be triggered manually in the Web UI.
• When a Map Widget that is in a subfolder is exported the initial zoom is maximized and some markers may be missing. [CSCuy11712]
• When using SNMPv3 sometime an errors occur when muliple PoE child devices are scanned or executed at the same time.
• Linux Systems without 'ifconfig' executable cannot be managed with Wake On Lan and miss network information in the properties of the asset
• The labels for bar charts are only displayed when hovering over the bar and not visible in the web UI and in exported reports.
• When importing devices with SNMP Network Discovery it can be advisable to check the "Import Generic Assets" on the options tab of the asset connector to e.g. get UCS C devices imported.
• When the logon name attribute for the user is changed in the LDAP settings dialog the attribute seems to be not saved; after clicking somewhere else in the UI and back on the LDAP settings dialog the default attribute is displayed. This is a display error. After refreshing with F5 the correct value is displayed.

Release Note Enclosures

ID	Symptom	Conditions	Workaround
CSCuw26693	Switch stack using default power instead of TruJoule	Software Version 5.0.x and 5.1.x	Apply manual power usage values in CEM. One of those switches consumes about 80W, but more accurate values can be found online on Cisco.com.
CSCux22703	CEM/CAM unable to generate real time consumption graph or report; no data displays	Software Version 5.0.x and 5.1.x	-
CSCuy37121	Not able to manage MAC device El Capitan	Software Version 5.0.x and 5.1.x	-