Release Notes

Cisco EnergyWise Management - Version 4.4.3

Date: 2014/08/26

System and Installation Requirements

Cisco EnergyWise Management Version 4.4.3 can be used for single instance installations as well as for distributed deployments, using an EnergyWise Server and multiple EnergyWise 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 (32-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	EnergyWise Server	EnergyWise 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	EnergyWise Controller
CPU	Quad Core, 2GHz
RAM	4 GB
Hard Disk 1)	50 GB
Operating System	Windows 7 or Server (64-Bit)

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

Cisco EnergyWise 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 8 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

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

Important Notes: Updating/patching an existing installation

• While patching, all Script Proxies which are part of Cisco EnergyWise 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 EnergyWise Management Version 4.4.2 to 4.4.3

• Apache updated to version 2.2.27
• updated OpenSSL to 0.9.8za/1.0.1h or higher for Apache, Windows Helper, CEM Controller, wkhtmltopdf, central/tools/ssl
• RabbitMQ updated to version 3.3.4
• added information to SSH Authentication help chapter regarding the changing of file permissions [CSCuo55142]
• added EM1200 support for the Schneider egx300 proxy
• Floor Plan background images can now be removed
• fixed an issue where getDeviceInfo did not execute for printers in standby state
• fixed shutdown of Windows services on system shutdown
• fixed an issue where the Floorplan Editor was not fully compatible with IE11
• fixed an issue where the HyperV Proxy failed with an error if winrm.https flag was set
• fixed an issue where the drop down list of available timezones within the timezone settings showed only empty values (only occurred in multi controller scenarios)
• fixed an issue where the download of a non-textfile from the controller resulted in a corrupted download file
• fixed an issue where the script editor did not work properly in IE10
• fixed an issue where the provided error message for the usage of an old offline key with Windows FIPS compliance enabled was insufficient
• fixed broken help links to the Custom Metric documentation [CSCuo26782]
• fixed an issue in the Power Widget where the widget showed wrong max values
• fixed some issues with the migration from an older version to 4.4.x
• fixed an issue where Scheduled Reports only considered data from the root folder
• fixed an issue where the File Upload did not work with IE11
• fixed several issues with certificates generated by the Windows Installer
• fixed an issue where the Monitor status always was UNKNOWN for pc.linux devices
• fixed an issue where the version number has not been updated after an auto-update (only in Controller view)
• fixed device diagnose for pc.linux devices when ssh.keyfile was used [CSCuo55073]
• fixed an issue where the device import with Juniper Junos Space version 13 used to fail
• fixed an issue where PoE devices were not imported due to incorrect port mapping
• fixed issue where in some cases settings in Settings>Administration>Database>Maintenance are not saved correctly
• fixed SNMPv3 support in script proxies
• fixed wrong PostgreSQL configuration being installed on systems with more than 4 GB RAM
• increased timeout of daily database cleanup jobs from 10 to 60 minutes
• fixed wrong PostgreSQL configuration being installed on systems with no Visual Studio 2010 C++ runtime installed
• the EnergyWise Helper binary and the backup tools no longer existed after an upgrade of a Controller-only installation
• improved the check for processes that can interfer with the patch setup

Changes from Cisco EnergyWise Management Version 4.4.0 to 4.4.2

• added spinner to script run with "Execute on Server"
• added functionality to set single power policy parameters
• fixed issue where PowerPolicy rules counted wrong savings
• fixed an PoE Mapping issue on stacked Cisco switches with multiple modules
• fixed an issue within the Energy Consumption Widget where the Week Matrix looked broken when Chinese language was chosen - [CSCun20574]
• fixed an issue where some versions of sudo did not support -n which caused the command to hang - [CSCuj83323]
• fixed minor issue where the UI needs to be reloaded after each licence change to ensure correct handling of permissions in all views
• disabled non-SSL connectivity to Rabbit MQ server if a user installs the application with the windows installer on premise - [CSCul97466]
• fixed an issue where the Controller was not able to start because of System.ArgumentOutOfRangeException
• fixed an issue where it was possible, that the device search could fail while the result is being prepared and the device is being scanned resulting in an empty device browser
• fixed an issue where SNMPv3 sometimes failed with the error message "usmStatsNotInTimeWindows"
• fixed an issue where the Rule History did not show up in the UI - [CSCun11402]
• fixed an issue where the export of all reporting based widgets used to fail - [CSCun23394]
• fixed an UTF8 encoding issue where switching between languages resulted in display issues within the reports
• fixed an issue where the Systemwatcher config was not adjusted correctly after a migration to version 4.4 - [CSCun39477]
• fixed an issue where the License Key expired one day to early - [CSCum91040]
• fixed an issue where a "device deleted" error occurred when assigning devices to racks
• fixed an issue within the Group by Widget where configuring to include (none) values led to NullPointer
• fixed an issue where the EnergyWiseProcessor.xml used to be empty in particular circumstances - [CSCun15650]
• fixed an issue where on fresh installations the initial start time of automatic updates was invalid
• fixed an issue where empty racks generated an error message every 2 minutes - [CSCun48676]
• fixed an issue where the Nexus 5k/7k SNMP power usage was incorrect - [CSCun08448]
• fixed an issue where Rule History counted checkApps condition as execution and success - [CSCuj83367]
• fixed an issue where setting power policy for pc.mac did not work
• fixed an issue where the SystemWatchDog did not write CSV header when cycling file
• fixed an issue where the Controller did not shut down gracefully in some cases
• fixed an issue where the SNMP Vendor matching found wrong products
• fixed an NullPointerException issue within the Scheduled Reports
• fixed an issue within the device time zone handling
• fixed an issue where the energy costs were set to default after a Controller restart

New Features and Enhancements in Cisco EnergyWise Management Version 4.4.0

• Scenario Reports - a tool to create Proof of Concept reports based on real baseline data
• Integrated REST API documentation
• EnergyWise Scripting on Server

Changes from Cisco EnergyWise Management Version 4.3.0 to Cisco EnergyWise Management Version 4.4.0

• added executable checks to WMI/WinRM configuration script
• added multiple segment selection dialog and single selection dialog (Summarize, Average, w/MinMax) for Custom Report settings
• added alerting if an Asset Connector fails to import devices
• improved system monitoring capabilities for EnergyWise Server
• improved resetPW usability - [CSCul16321]
• improved Property Editor performance (Device Dialog) - [CSCuj83377]
• upgraded Apachae HTTPD to version 2.2.25 and added to SSLCompression off outside of vhost entry - [CSCum03686]
• support for "cpufreq-set" has been removed - it no longer needs to be set up in the sudoers file
• cpufreq as part of the diagnose has been improved
• the cpufreq driver "acpi-cpufreq" is now being used by default - the vendor-specific drivers will only be loaded as a fallback - the "modprobe" command will now be looked up before using it in case it is not in the path
• error reporting in case of invalid/missing sudo configuration have been improved - the governor will be set when it wasn't set yet
• fixed minor issue where a download from the System Message widget used the old logfile names
• fixed minor start time issue for automatic updates
• fixed minor issue where the System Watcher was not able to read {jemprocessor|application}.conf
• fixed issue where ipmiutil failed to communicate with Dell iDRAC 7 devices
• fixed minor UI presentation issue in IE browser
• fixed a DQL parser issue where device fields beginning with "not" were parsed as negation of removeStart/deviceField, "not")
• fixed minor issue where changes in the Asset Connector view were lost when navigating away and back again
• fixed minor issue which occurred within the Asset Connector view when the Controller was not reachable
• fixed issue where normalization of dx fields caused different fields to write into the same table - [CSCuj83340]
• fixed some LDAP user management URI encoding problems
• fixed bug where queue messages were not stored in the DB when the Controller lost connection to the queue
• fixed minor bug where scrollbars were missing within TruJoule Editor and Optimizer - [CSCuj83364]
• fixed minor bug in utilization reports where lower and upper utilization bound did not work
• fixed issue where a Calculated Properties Refresh and folder deletion could lead to deadlock
• fixed broken Model Analysis Reports caused by case sensitive reporting segments
• fixed issue where the Controller fails to startup if DQL in the protected device list or location mapping was invalid
• fixed issue with the energy price setting per Controller
• fixed issue where WoL failed if getDeviceInfo was executed on a powered off device
• fixed issue where acignore did not work for Discovery Asset Connectors
• fixed a bug where Asset Connectors were not executed if schedule was set to every week or longer
• fixed a bug where the device type has been overwritten with switch.interface if the PoE device was enriched via CDP/LLDP

Other Information

Known Issues

• Internet Explorer 11 not fully supported yet
• Cisco EnergyWise Management: Settings - Controller Management - Software Updates
  In rare cases it could happen that after a successfully performed software update, this update is offered again as new Available Version. If so, please compare the Version Number of the Current Version with the Version Number of the Available Version. If the Version Numbers are identical, the update performed correctly.