Table Of Contents
Release Notes for the Cisco EnergyWise Orchestrator, EnergyWise Phase 2
Revised November 22, 2010
Unless otherwise noted, the term network device refers to Cisco switches, routers, access points and other network devices.
These release notes include important information about Cisco EnergyWise Phase 2 and any limitations, restrictions, and documentation updates that apply to Cisco devices running Cisco EnergyWise Orchestrator. To verify that these release notes are correct for your switch, see the "Supported Devices" section.
For information about a specific Cisco device running Cisco EnergyWise Phase 2, see the release notes for the Cisco IOS software running on your device. To verify that these release notes are correct for your switch, use the show version privileged EXEC command.
For the list of EnergyWise Phase 2 documentation, see the "Related Documentation" section.
For information about this warning, see the "Importance Notice" appendix in the Cisco EnergyWise Orchestrator guides:
Upgrading the Orchestrator Software
About Software Upgrades
Cisco EnergyWise Orchestrator software version 2.0.1 does not support an automatic upgrade from Orchestrator version 2.0.0. Users who have installed Orchestrator version 2.0.0 cannot use the Orchestrator version 2.0.1 server installers. To upgrade from Orchestrator version 2.0.0, uninstall Orchestrator version 2.0.0 and install Orchestrator version 2.0.1.
To install the two optional features of Orchestrator version 2.0.1 while running Orchestrator version 2.0.0, see the "Adding Enhancements Without Upgrading the Software" section.
Finding the Software Version
To see which version of Cisco EnergyWise Orchestrator is installed on your device, open the Administrator Console About dialog.
Deciding Which Software Version to Use
For any new installation, use Orchestrator version 2.0.1. This version adds:
•Support for Orchestrator on Windows servers running Western European languages. (Version 2.0.0 supports only US English servers.)
•A GUI editor for the Proxy Server web.config file.
•Database indexes that speed up the data summarization process.
Adding Enhancements Without Upgrading the Software
If you are using Orchestrator version 2.0.0, you can manually add two optional enhancements:
•Database indexes that reduce the database summarization processing time by about 90 percent.
•A Windows GUI application that you can use to configure the EnergyWise Proxy Servers.
Adding Database Indexes
Step 1 Download the.zip file that contains the AddSummarizeIndex.sql script file from this URL:
Step 2 Use the Microsoft SQL Server Management Studio to open the database. The default database name is EnterprisePowerManagementDB.
Step 3 Run the AddSummarizeIndex.sql script file on the Orchestrator 2.0.0 database.
Note The indexing process requires several minutes to a few hours, depending on the number of devices in your Orchestrator database and the total time that your system has been running.
When the indexing process is complete, the SQL Server Management Studio displays this message: "Commands completed successfully"
Installing the Proxy Configuration Editor Application
Instructions for downloading and installing the Windows GUI application are in the Cisco EnergyWise Orchestrator Proxy Configuration Editor User Guide, Cisco EnergyWise Phase 2:
The Orchestrator Server version 2.0.1, Proxy Server, Wake for Remote Access, and the Sustainability Dashboard run on the Western European language Windows Server 2003 x86 SP2 and the latest patches.
Orchestrator Server uses these Microsoft SQL Server versions for data storage:
•Western European language SQL Server 2005 x86 SP2
•Western European language SQL Server 2008 x86 SP1
The Orchestrator Agent runs on
•Windows 7 x86 and the latest patches
•Windows 7 x64 and the latest patches
•Windows Vista x86 SP2 and the latest patches
•Windows XP x86 SP3 and the latest patches
The Orchestrator Administration Console and the Sustainability Dashboard run on Internet Explorer 7 and Flash Player 10.
Software Requirements for the Orchestrator Server
•Microsoft IIS 6.0
•.NET 3.5 SP1
•Java 6 update 17
Wake on LAN
•Before using Wake on WAN to wake a PC, you must configure Wake on LAN on the PC. For information, see the "Waking Computers" chapter in the Cisco EnergyWise Orchestrator Administrator Guide on Cisco.com.
•You might have to configure the system BIOS before configuring Wake on LAN.
•Some PCs do not support Wake on LAN.
BIOS power management
•To use the PC power management functionality, the minimum PC system BIOS requirement is Advanced Power Management (APM) 1.1.
•To use enhanced power management functionality, the minimum BIOS requirement is Advanced Configuration and Power Interface (ACPI) 1.0.
•Check the PC BIOS settings to ensure that the Windows operating system controls power management. For the BIOS settings, see the PC documentation.
Monitor power management
•To use low-power modes, a monitor must have a sleep functionality.
•Older non-Energy-Star-compliant monitors might not support the sleep functionality.
To display the EnergyWise version and the Cisco IOS software running on the network device, use the show energywise version and show version privileged EXEC CLI commands.
•The focus indicator does not appear in the main window.
•The default object in any window is not visible. (There is no focus indicator.)
•In the main window, the Policies tab does not appear to be selected after you use the Tab key to go to it.
Figure 1 No Focus Indicator in the Cisco EnergyWise Orchestrator Main Window
You cannot use the Tab key to go to all the window elements in a window.
In the Conditions area, if you use the Tab key to navigate from the Add Condition options to the Discard Changes button, you cannot go from Add Condition to Select a device property to the Discard Changes button.
Figure 2 Limited Keyboard Navigation in a Window
High-Contrast Window Settings
Note Orchestrator does not use the operating-system high-contrast settings.
You cannot use the keyboard for navigation if Orchestrator is in high-contrast mode.
Figure 3 Orchestrator Window in High-Contrast Mode
You cannot use screen reader software with Orchestrator.
The default device name for the Cisco Integrated Service Routers Generation 2 (ISR G2) is Unknown.
The Orchestrator Server version 2.0.0 does not support non-English-speaking locations. When configuring a non-English-speaking location on the server:
Step 1 Create a user named Svc.PowerMgmt, and set the password to be the same as the user name.
Step 2 Set the user locale as US-English.
Step 3 Add the user to the Administrators group.
Step 4 Create a login for Svc.PowerMgmt on the SQL Server, and set the role as system administrator.
Step 5 Configure Svc.PowerMgmt as the Enterprise Power Management Processor service.
Step 6 Restart the Enterprise Power Management Processor service.
Step 7 Verify that the service runs properly. See the event logs in the Administrator console.
Orchestrator version 2.0.1 does not include a new Orchestrator Agent. Use Orchestrator Agent 2.0.0.
If you set the Rule Enforcement option to All Connections in Orchestrator 2.0, the policy and group assignment rules do not work as expected.
The workaround is to set the Rule Enforcement option to New Connections Only. The rules are then applied only when Orchestrator discovers a new device. After a device is discovered, you can manually apply rules.
If you do not use Orchestrator to modify a recurring event, the updated event does not appear in Orchestrator.
The workaround is to use only Orchestrator to modify the recurring event.
You created and applied a policy to an interface in Orchestrator. If you remove the policy, Orchestrator also removes any policy that you created and applied using the CLI.
The workaround is to use either Orchestrator or the CLI.
When you set the EnergyWise power level for IP phones, all the PC power levels appear.
There is no workaround. The non-IP-phone power levels do not apply to the IP phones.
These Cisco modules appear as Unknown in Orchestrator:
In the Device Name field, they appear as
–Host IP Address: SM #
–Host IP Address: ISM #
–Host IP Address: PVDM #/#
There is no workaround.
When you select any field in a window, a warning appears twice.
When you select the By Group, By Policies, or By Subnet option in the Search tab in the left side of the main window and open a new window, it does not appear and is behind the remaining tab.
The Wake tab is enabled even when the PC is on or is not in sleep mode.
You can use Orchestrator to set the power level (such as wake, shutdown, sleep, or restart) of network devices in the EnergyWise domain.
The Refresh button on the browser does not work.
You can apply policies to non-PC end points, such as routers and switches.
Applications open when the PC is in the hibernate state, preventing power state transitions.
After the Orchestrator server sends a message to the PC to transition to standby mode and the PC receives it, only the Now button is available. The Delay and Skip buttons are unavailable.
When keywords are passed from Orchestrator to the EnergyWise management application programming interface (API), the keyword length is different in Cisco IOS Release 15.0(1)M2 and Cisco IOS Release 12.2(33)SXI4 and in other Cisco IOS releases.
–In Cisco IOS Release 15.0(1)M2 and Cisco IOS Release 12.2(33)SXI4, the length is strlen(keywords).
–In other Cisco IOS releases, the length is strlen(keywords) + 1.
When the domain network devices are running the minimum Cisco IOS releases (see Table 1) and you configure multiple recurring events on one network device, attributes for other devices might not appear in the Administrator console.
The workaround is to configure fewer recurring events on the network device. If you set more than four events on the network device, it might send inaccurate attribute information about itself and the connected devices to the Administrator console.
The server installer puts two SQL scripts in the Database folder:
Orchestrator runs them during the installation. You do not need them for post installation configuration.
If you manually set the Orchestrator database before or after the installation, use a different script in the distribution package. For information, see the "Setting Up the Database Environment" in the Cisco EnergyWise Orchestrator Installation Guide on Cisco.com.
Orchestrator uses the default US English language collation setting and supports case insensitivity. If you use a different collation setting, case insensitivity in Orchestrator might not work properly.
In the Sustainability Dashboard, a stacked bar chart shows all the available categories instead of specific ones. Orchestrator does not sort them, even if sorting is selected.
The Power Platform role attribute has the OEM preferred power management profile for PCs. This value is in the Power Platform Role Preferred_PM_Profile field of the Fixed ACPI Description Table (FADT) (for example, PlatformRoleDesktop or PlatformRoleMobile).
If you set the keyword, role, and importance attributes on PCs that are not checking in with the server, these attributes are not updated in Orchestrator.
Do not use keyword, role, and importance attributes on PCs, and do not use the attributes as conditions when assigning clients to a policy or group.
If you have a policy that uses a scheme to transition a device to a lower power state at the end of the day instead of a policy that changes the power level to shut down devices at a specific time, apply the policy with the scheme only to PCs.
To power devices on in the morning and power them off in the evening, apply a policy with wake (level 10) and shut down (level 0) power level changes to the devices.
After you change time zones (for example, from UTC+0 to UTC-8), restart the Orchestrator Agent.
For information about configuring Cisco network devices
•Cisco EnergyWise Configuration Guide:
•Cisco IOS Release Notes for Cisco EnergyWise, EnergyWise Phase 2:
•Configuring Cisco EnergyWise Feature for Branch Routers:
•Cisco EnergyWise IOS Deployment Guide:
Cisco EnergyWise Orchestrator guides:
•Cisco EnergyWise Orchestrator Administrator Guide, Cisco EnergyWise Phase 2
•Cisco EnergyWise Orchestrator Installation Guide, Cisco EnergyWise Phase 2
•Cisco EnergyWise Orchestrator Wake for Remote Access Administrator Guide, Cisco EnergyWise Phase 2
•Cisco EnergyWise Orchestrator Proxy Configuration Editor User Guide, Cisco EnergyWise Phase 2
These partner documents provide information about the management API and end point SDK and are available on the Cisco Developer Network:
•Cisco EnergyWise Documentation Roadmap
•Cisco EnergyWise Partner Development Guide
•Cisco EnergyWise Programmer Reference Guide for the End-Point SDK
•Cisco EnergyWise Programmer Reference Guide for the Management API
•Release Notes for Cisco EnergyWise, EnergyWise Phase 2
Obtaining Documentation and Support on the Cisco Developer Network
Cisco EnergyWise development partners can access the EnergyWise documents, API and SDK software code, and Cisco IOS software by joining the Cisco Developer Network:
You need a support contract and license to access EnergyWise resources on the Cisco Developer Network and on TAC. The business development manager who registered your licence must set up your Cisco.com account with the appropriate access privileges.
The forum, wiki, and other resources on the Cisco Developer Network provide a self-help knowledge base and community for EnergyWise application developers and programmers. You can get additional support by opening a case in the TAC Service Request Tool:
Obtaining Documentation, Support, and Security Guidelines
For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation:
Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed, and set content to be delivered directly to your desktop by a reader application. The RSS feeds are a free service, and Cisco supports RSS version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2010 Cisco Systems, Inc. All rights reserved.