Cisco Systems OL-19806-03 User Manual

Cisco EnergyWise Configuration Guide

EnergyWise Phase 2 August 2010

Americas Headquarters

Cisco Systems, Inc. 170 West Tasman Drive San Jose, CA 95134-1706 USA http://www.cisco.com Tel: 408 526-4000

800 553-NETS (6387)

Fax: 408 527-0883

Text Part Number: OL-19806-03

THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.

THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.

The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.

NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.

IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

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 and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.

Cisco EnergyWise Configuration Guide

IMPLIED, INCLUDING, WITHOUT

Preface v

Audience v

Purpose v

Conventions v

Related Publications vii

Obtaining Documentation and Support on the Cisco Developer Network viii

Obtaining Documentation, Support, and Security Guidelines viii

CHAPTER

1 Managing Single Entities 1-1

Overview 1-2

Creating an EnergyWise Domain 1-4

Power Levels 1-5

Attributes 1-6

Recurring Event 1-6

Secure Domain Communication 1-6

MIBs 1-7

Switch Connected to an IP Phone 1-8

Switch Connected to a PC 1-9

Configuration Guidelines 1-10

Using the Call In-Progress Feature 1-12

PoE and EnergyWise Interactions 1-13

Preventing Network Access to a Non-Cisco End Point 1-14

CLI Compatibility Issues 1-15

Manually Managing Power 1-16

Enabling EnergyWise 1-17 Configuring Entity Attributes 1-18 Powering the PoE Port 1-20 Configuring Port Attributes 1-20

OL-19806-03

Configuring Recurring Events 1-22

Disabling EnergyWise 1-25

Examples 1-26

Setting the Domain 1-26

Cisco EnergyWise Configuration Guide

iii

Contents

Manually Managing Power 1-26 Automatically Managing Power 1-27

CHAPTER

2 Managing Multiple Entities 2-1

Running Queries 2-1

Multiple Switches Connected to Multiple End Points 2-3

Using Queries to Manage Power in the Domain 2-4

Examples 2-5

Querying with the Name Attribute 2-6 Querying with Keywords 2-6 Querying to Set Power Levels 2-6 Setting the Time-Out Value 2-7

3 EnergyWise CLI Commands 3-1

clear energywise neighbors 3-2

debug energywise 3-3

energywise (global configuration) 3-4

energywise (interface configuration) 3-8

energywise domain 3-13

energywise query 3-15

CHAPTER

APPENDIX

snmp-server enable traps energywise 3-19

show energywise 3-21

4 Troubleshooting EnergyWise 4-1

Using CLI Commands 4-1

Verifying the Power Usage 4-2

A Cisco EnergyWise and Catalyst 4500 Switches A-1

B Cisco EnergyWise and Catalyst 6500 Switches B-1

C Important Notice C-1

Disclaimer C-1

Statement 361—VoIP and Emergency Calling Services do not Function if Power Fails C-1

Statement 1071—Warning Definition C-3

Cisco EnergyWise Configuration Guide

OL-19806-03

Audience

Purpose

Preface

This guide is for the networking professional managing the Cisco network devices.

The term switch refers to Catalyst switches and other Cisco network devices, such as routers and access points.

This document describes how to configure Cisco EnergyWise in your network.

This guide does not describe how to install your network device. For information, see the hardware installation guide for your device.

For information about the Cisco IOS Release 12.2 commands, see the Cisco IOS documentation set on Cisco.com.

This guide does not provide detailed information on the GUIs for the embedded device manager or for Cisco Network Assistant (hereafter referred to as Network Assistant) that you can use to manage the switch. However, the concepts in this guide are applicable for the GUI user. For information about the device manager, see the switch online help. For information about Network Assistant, see Getting Started with Cisco Network Assistant, available on Cisco.com.

This document does not provide specific information for the management application programming interface (API)- and end-point software development kit (SDK). For information, see the Cisco

EnergyWise Documentation Roadmap, Cisco EnergyWise Partner Development Guide, Cisco EnergyWise Programmer Reference Guide for the Management API, and the Cisco EnergyWise Programmer Reference Guide for the End Point SDK on the Cisco Developer Network:

http://developer.cisco.com/web/esdk/home.

For documentation updates, see the release notes for this release.

Conventions

This publication uses these conventions to convey instructions and information:

OL-19806-03

For command descriptions

• Commands and keywords are in boldface text.

• Arguments for which you supply values are in italic.

Cisco EnergyWise Configuration Guide

Preface

• Square brackets ([ ]) mean optional elements.

• Braces ({ }) group required choices, and vertical bars ( | ) separate the alternative elements.

• Braces and vertical bars within square brackets ([{ | }]) mean a required choice within an optional

element.

For interactive examples

• Terminal sessions and system displays are in screen font.

• Information that you enter is in boldface screen font.

• Nonprinting characters, such as passwords or tabs, are in angle brackets (< >).

Notes, cautions, and warnings use these conventions and symbols:

Note Means reader take note. Notes contain helpful suggestions or references to materials not contained in

this manual.

Caution Means reader be careful. In this situation, you might do something that could result in equipment

damage or loss of data.

Warning

IMPORTANT SAFETY INSTRUCTIONS

This warning symbol means danger. You are in a situation that could cause bodily injury. Before you work on any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standard practices for preventing accidents. Use the statement number provided at the end of each warning to locate its translation in the translated safety warnings that accompanied this device.

Statement 1071

SAVE THESE INSTRUCTIONS

Cisco EnergyWise Configuration Guide

OL-19806-03

Preface

Related Publications

For information about the Cisco network devices, see

• Cisco IOS Release Notes for Cisco EnergyWise, EnergyWise Phase 2 on Cisco.com

• Configuring Cisco EnergyWise Feature for Branch Routers:

http://www.cisco.com/en/US/docs/routers/access/1900/software/configuration/guide/enrgyz_artg.h tml

• Documentation for the software release running on your device on Cisco.com:

http://www.cisco.com/cisco/web/support/index.html.

Note Before installing, configuring, or upgrading the switch, router, or other Cisco device, see these

documents:

• For initial configuration information, see the “Using Express Setup” section in the getting started

guide or the “Configuring the Switch with the CLI-Based Setup Program” appendix in the hardware installation guide.

• For device manager requirements, see the “System Requirements” section in the release notes (not

orderable but available on Cisco.com).

• For Network Assistant requirements, see the Getting Started with Cisco Network Assistant (not

orderable but available on Cisco.com).

• For cluster requirements, see the Release Notes for Cisco Network Assistant (not orderable but

available on Cisco.com).

• For upgrading information, see the “Downloading Software” section in the release notes.

For information about the Cisco EnergyWise partner documentation, go to the Cisco Developer Network:

http://developer.cisco.com/web/esdk/home.

• 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

• Cisco IOS Release Notes for the Cisco EnergyWise Configuration Guide, EnergyWise Phase 2

OL-19806-03

Cisco EnergyWise Configuration Guide

vii

Preface

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:

http://developer.cisco.com/web/esdk/home.

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:

http://tools.cisco.com/ServiceRequestTool/create/launch.do.

Obtaining Documentation, Support, and Security Guidelines

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What’s revised Cisco

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

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.

technical documentation:

New in Cisco Product Documentation, which also lists all new and

viii

Cisco EnergyWise Configuration Guide

OL-19806-03

CHAP T ER

Managing Single Entities

• Overview, page 1-2

• Creating an EnergyWise Domain, page 1-4

• Power Levels, page 1-5

• Attributes, page 1-6

• Recurring Event, page 1-6

• MIBs, page 1-7

• Switch Connected to an IP Phone, page 1-8

• Switch Connected to a PC, page 1-9

• Configuration Guidelines, page 1-10

• Using the Call In-Progress Feature, page 1-12

• PoE and EnergyWise Interactions, page 1-13

• Preventing Network Access to a Non-Cisco End Point, page 1-14

• CLI Compatibility Issues, page 1-15

• Manually Managing Power, page 1-16

• Configuring Recurring Events, page 1-22

• Disabling EnergyWise, page 1-25

• Examples, page 1-26

Note If your switch is stacking-capable (for example, a Catalyst 3750-X, 3750-E, or 3750 switch), unless

otherwise noted, the term switch refers to a standalone switch and to a switch stack.

For a list of Cisco network devices supporting Cisco EnergyWise, see the Cisco IOS Release Notes for Cisco EnergyWise, EnergyWise Phase 2 on Cisco.com.

For Cisco Integrated Service Routers Generation 2 (ISR G2), see the Configuring Cisco EnergyWise Feature for Branch Routers:

http://www.cisco.com/en/US/docs/routers/access/1900/software/configuration/guide/enrgyz_artg.html

See Cisco EnergyWise information:

http://www.cisco.com/en/US/products/ps10195/tsd_products_support_series_home.html.

See EnergyWise partner information on the Cisco Developer Network:

http://developer.cisco.com/web/esdk/home.

OL-19806-03

Cisco EnergyWise Configuration Guide

1-1

Overview

Chapter 1 Managing Single Entities

Warning

Overview

Voice over IP (VoIP) service and the emergency calling service do not function if power fails or is disrupted. After power is restored, you might have to reset or reconfigure equipment to regain access to VoIP and the emergency calling service. In the USA, this emergency number is 911. You need to be aware of the emergency number in your country.

For information about this warning, see the “Important Notice” appendix.

In a Cisco EnergyWise network, EnergyWise monitors and manages the power usage of powered devices: Cisco devices in a domain and all the connected end points.

An end point can be a device connected to the network, such as an IP phone, access point, or PC.

An entity refers to a domain member or an end point.

You can configure policies, referred to as recurring events or recurrences, to use time-of-day settings to automatically manage power usage.

1-2

Cisco EnergyWise Configuration Guide

OL-19806-03

Chapter 1 Managing Single Entities

276240

Figure 1-1 EnergyWise Network

Overview

1 Network management stations 7 TCP 2 Domain members 8 UDP 3 End points 9 Runs queries and sets EnergyWise attributes 4 Management station 10 Runs, forwards, and responds to queries 5 Domain member 11 Responds to queries 6 End point

• Management stations—Control applications and devices that use EnergyWise to monitor and

manage the power usage of domain members and end points. Management stations also send queries.

Use the management application programming interface (API) to write a power management application.

• Domain members—Cisco switches, routers, and network devices that use power. They forward

messages across an EnergyWise domain consisting of other Cisco devices and end points. They also forward and reply to queries from the management station and other domain members and aggregate power-usage information from the end points.

A domain is treated as one unit of power management and is similar to a network-management community.

• End points—Devices that use power. They only respond to queries.

Use the end-point software development kit (SDK) to implement an agent or client that participates as an EnergyWise end point.

Domain members and end points can receive power from an AC power source, a DC power source, or a power supply.

OL-19806-03

Cisco EnergyWise Configuration Guide

1-3

Creating an EnergyWise Domain

Power over Ethernet (PoE) domain members and end points can also receive power from PoE switches or Cisco EtherSwitch service modules. For example, IP phones and access points connected to a PoE switch receive power from the switch.

Creating an EnergyWise Domain

An EnergyWise domain is treated as one unit of power management and is similar to a network-management community (for example, a VLAN Trunking Protocol [VTP] domain). An EnergyWise domain consists of Cisco domain members and end points. The domain members forward messages to other members and to end points.

For example, if you have a building with a core router, 10 access switches, and 400 end points, such as phones, access points, and PCs running the end point SDK, you can create an EnergyWise domain called MyBuilding with the router and switches as domain members.

Note If you want to implement power management applications on a management station and EnergyWise

agents on the end points, the domain members must all run EnergyWise Phase 2 or later.

Chapter 1 Managing Single Entities

After you enable and configure EnergyWise on the core router and access switches, the MyBuilding domain configures itself. Neighbor relationships are set among the domain members.

• Domain members use CDP when it is enabled or EnergyWise UDP messages to automatically

discover neighbors.

• You can manually configure static neighbors,

Each domain member sets up a parent-child relationship with an attached end point. The child is one of the 400 end points, and the parent is the domain member. For example, an IP phone (child) is connected to a PoE switch (parent), or a PC is connected to a router.

The EnergyWise domain can also have end points running custom SDK agents.

After the domain is set, a domain member can forward queries and control messages to other domain members and endpoints.

You ca n

• Use SNMP or a management station to query every entity (domain member or end point).

• Run an EnergyWise query to receive or set power usage information.

• Use a management application, server, or CLI of a domain member to define power usage policies

or receive power usage information.

1-4

Cisco EnergyWise Configuration Guide

OL-19806-03

Chapter 1 Managing Single Entities

Power Levels

The devices in an EnergyWise network are from different manufacturers. To manage power usage consistently, EnergyWise uses a set of power levels.

If a domain member sends an end point a request to change the power level, the end point determines the appropriate action.

Ta b l e 1-1 Power Levels

Category Level Description

Operational 10 Full

Standby 7 Medium

Nonoperational 2 Sleep

Power Levels

9 High

8 Reduced

6 Frugal

5 Low

4 Ready

3 Standby

1 Hibernate

0 Shut off

The range is from 0 to 10.

The default is 10.

A Cisco switch does not support level 0. You cannot turn off the power on a switch.

A PoE end point, such as IP phone, receives power from a PoE switch port.

• The power level is for the port.

• The port supports levels 0 to 10.

• If the port power level is 0, the port is powered off.

• If the power level is from 1 to 10, the port is on.

OL-19806-03

Cisco EnergyWise Configuration Guide

1-5

Attributes

Ta b l e 1-2 Keywords, Name, and Role

Definition Defaults

Keywords Device description (other than

the name or role) for which query results are filtered

Name Device identity for which query

results are filtered

Role Device function based on the

business or deployment context

Chapter 1 Managing Single Entities

None.

For a PoE port, the short version of the port name. For example, Gi0.2 for Gigabit Ethernet

For a switch, the hostname.

For an end point, see the documentation for the end point and the agent or client running on it. We recommend that you use the hostname.

For a PoE port, the default is interface.

For a switch, the default can be the model number or the supervisor model number.

For an end point, see the documentation for the end point and the agent or client running on it.

0/2.

Recurring Event

You can configure the switch to power an end point or interface on and off based on the time or date.

A recurring event, also referred to as a recurrence, uses the switch time.

The settings are only in the running configuration.

If the switch fails and then restarts, it uses the power level in the saved configuration.

Secure Domain Communication

Configure the security mode and password, referred to as the shared secret, to prevent replay attacks. You set either a strong password with Network Time Protocol (NTP) or a strong password without NTP.

When you use NTP to synchronize the time among domain members and you set a shared secret with NTP, EnergyWise uses the current time with the shared secret to enhance prevention of replay attacks.

1-6

Cisco EnergyWise Configuration Guide

OL-19806-03

Chapter 1 Managing Single Entities

MIBs

EnergyWise switches support the CISCO-ENERGYWISE-MIB.

For information, see the Release Notes for Cisco EnergyWise, EnergyWise Phase 2 on Cisco.com and go to

http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml and click SNMP v2 MIBs or

SNMP v3 MIBs.

You can also use FTP to access the MIB files.

Step 1 Make sure that your FTP client is in passive mode.

Note Some FTP clients do not support passive mode.

Step 2 Use FTP to access the server ftp.cisco.com. Step 3 Log in with the username anonymous. Step 4 Enter your e-mail username when prompted for the password. Step 5 At the ftp> prompt, change directory to /pub/mibs/v2 or to /pub/mibs/v3. Step 6 Use the get MIB_filename command to obtain a copy of the file.

MIBs

OL-19806-03

Cisco EnergyWise Configuration Guide

1-7

Switch Connected to an IP Phone

Figure 1-2 Switch and IP Phone Scenario

WAN

Chapter 1 Managing Single Entities

276242

1 Management station 3 End point 2 Domain member

The switch sends the end point a recurring event to power on at 0700 and to power off at 1900.

1-8

Cisco EnergyWise Configuration Guide

OL-19806-03

Chapter 1 Managing Single Entities

Switch Connected to a PC

Figure 1-3 Switch and PC Scenario

Switch Connected to a PC

1 Management station 3 End point 2 Domain member

The switch sends the end point a recurring event to power on at 0600 and to power off at 2200.

276243

OL-19806-03

Cisco EnergyWise Configuration Guide

1-9

Configuration Guidelines

By default, EnergyWise is disabled on the switch.

If you enter the no energywise level command, the switch does not immediately change the power level to the default. The power level changes when the switch restarts or when you enter the energywise level level command.

For a switch with PoE ports, such as a PoE-capable switch:

• When you add the switch to a domain, EnergyWise is enabled on the switch and all the PoE switch

ports.

• Use the energywise level 0 interface configuration command to power off a PoE port.

• You cannot use the energywise level 0 global configuration command to power off the switch.

If a port is in the error-disabled state:

• It appears as an EnergyWise entity in the show command output and in the collect query results. The

query results show that the port uses 0 W.

• It does not respond to a set query.

Chapter 1 Managing Single Entities

For recurring events:

• Specify time in the 24-hour format. For example, to set 0634

–

As a specific time, enter the energywise level level recurrence importance importance at 34 6 * * * interface configuration command.

–

In a time range, enter the absolute start 06:34 * * 2009 and the periodic daily 06:34 time-range configuration commands.

• The time zone is based on the end point.

–

If EnergyWise is not running on the end point (for example, a PoE end point), the specified time is based on the switch time zone.

–

If an agent or client is running on the end point, the specified time is based on the end-point time zone.

• If you configure the switch to power on an end point or a PoE port at a specific time, it powers on

within 1 minute, for example, between 0700 and 0701.

• If you configure the same recurring event for multiple end points, they all power on within 1 minute.

Note See the Release Notes for Cisco EnergyWise, EnergyWise Phase 2 on Cisco.com for software

releases with Cisco EnergyWise Phase 2.

• When you use the day_of_month and the day_of_week in the energywise level level recurrence

importance importance at minute hour day_of_month month day_of_week interface configuration

command in an EnergyWise Phase 2 software release:

1-10

–

The recurring event occurs when either the day_of_month or the day_of_week occurs first in releases earlier than the EnergyWise Phase 2 releases.

If you specify both the day_of_month and the day_of_week, the event occurs when either the day_of_month or the day_of_week is first.

If you specify the day_of_month and use a wildcard (*) for the day_of_week, the event occurs on the day_of_month.

Cisco EnergyWise Configuration Guide

OL-19806-03

Chapter 1 Managing Single Entities

–

• If you use the energywise level level recurrence importance importance at minute hour 29 2 *

interface configuration command to configure an event on February 29 in an EnergyWise Phase 2 software release:

–

When configuring domains:

• Use a strong password for the domain shared secret.

• You must configure the same security mode, either an Network Time Protocol (NTP) or a non-NTP

shared secret, for all the domain members.

You must use a strong password:

• Contains both upper and lower case characters (for example, a–z and A–Z).

Configuration Guidelines

If you use a wildcard for the day_of_month and specify the day_of_week, the event occurs on the day_of_week.

If you use wildcards for both the day_of_month and the day_of_week, the event occurs on any day.

After you upgrade the software to an EnergyWise Phase 2 release or later, a configured recurring event might occur less frequently than before the upgrade. Reconfigure the event.

Before you upgrade the software to an EnergyWise Phase 2 release or later, the event occurs every day in February.

After you upgrade the software, the event might not occur.

• Contains letters, numerals, and punctuation (for example, 0-9 and !@#$%^&*()_+|~

=\`{}[]:";'<>?,/).

• Is at least five alphanumeric characters long.

• Is not a word in any language and is not slang, dialect, or jargon.

• Is not based on personal information, such as the names of family members.

Do not use a weak password:

• Contains fewer than eight characters.

• Is a word found in a dictionary (English or foreign)

• Is any other term that is easily guessed or found in common usage, such as

The name of family, pet, friend, coworker, or fantasy character.

A computing term or name, such as a command, site, company, model, or application.

Is a birthday or another kind of personal information, such as an address or telephone number.

Is a predictable letter pattern or number pattern, such as aaabbb, qwerty, zyxwvuts, or 123321.

Any of the previous spelled backwards.

Any of the previous preceded or followed by a digit, such as secret1 or 1secret.

OL-19806-03

Cisco EnergyWise Configuration Guide

1-11

Using the Call In-Progress Feature

Use this feature, also referred to as activity check, to configure the switch to wait until a Cisco IP phone connected to a PoE port is not sending or receiving traffic before powering off the port.

Use the energywise activitycheck interface configuration command on these Cisco devices:

• Catalyst 6500 switches (see the Cisco IOS Release Notes for Cisco EnergyWise, EnergyWise

Phase

2 for the specific devices)

• Catalyst 4500 switches

Note Before powering off a PoE port, Catalyst 6500 and Catalyst 4500 switches use interface statistics

to determine when a Cisco IP phone connected to the PoE port is not sending or receiving traffic.

• Catalyst 3750-X, 3750-E, 3750, 3560-X, 3650-E, 3560, and 2960 switches

• Cisco EtherSwitch service modules (NME-16ES-1G, NME-16ES-1G-P, NME-X-23ES-1G,

NME-X-23ES-1G-P, NME-XD-24ES-1S-P, NME-XD-48ES-2S-P)

• Cisco enhanced EtherSwitch service modules (SM-D-ES2-48, SM-D-ES3-48-P, SM-D-ES3G-48-P,

SM-ES2-16-P, SM-ES2-24, SM-ES2-24-P, SM-ES3-16-P, SM-ES3-24-P, SM-ES3G-16-P, SM-ES3G-24-P)

Before entering the energywise activitycheck command on devices other than Catalyst 6500 and 4500 switches, you must enable automatic quality of service (auto-QoS) for VoIP on the port with this configuration:

Chapter 1 Managing Single Entities

• All packets from the IP phone have the class of service (CoS) value 5.

To verify this, use the show mls qos maps cos-output-q privileged EXEC command to display the CoS output queue threshold map.

This example shows that CoS value 5 is mapped to queue 1 and threshold 3 on the Gigabit Ethernet

Cos-outputq-threshold map:

cos: 0 1 2 3 4 5 6 7

------------------------------------

queue-threshold: 4-3 4-2 3-3 2-3 3-3 1-3 2-3 2-3

0/1:

This is the configuration for the PoE port:

<output truncated> interface GigabitEthernet0/1 srr-queue bandwidth share 10 10 60 20 queue-set 2 priority-queue out mls qos trust device cisco-phone mls qos trust cos auto qos voip cisco-phone service-policy input AutoQoS-Police-CiscoPhone <output truncated>

• Auto-QoS for VoIP is enabled on the PoE port.

• Auto-QoS is enabled on the IP phone. The switch does not change the CoS value in the packet from

the IP phone.

1-12

Cisco EnergyWise Configuration Guide

OL-19806-03

Chapter 1 Managing Single Entities

• If the switch is connected to the IP phone through multiple Cisco devices, verify that they trust the

CoS value in incoming packets and do not change it.

• After entering the energywise activitycheck interface configuration command, verify that the

switch powers off the port when a Cisco IP phone connected to it is not sending or receiving traffic. While making a phone call

–

Run a query to set the port power level to 0. The switch should not power off the IP phone.

–

Use the show mls qos interface statistics privileged EXEC command to display the port QoS statistics, including the number of packets in queue 1.

PoE and EnergyWise Interactions

Ta b l e 1-3 If an Entity Participates in EnergyWise

EnergyWise Entity PoE Mode

auto never static

PoE port Yes No Yes

Non-PoE port No No No

PoE and EnergyWise Interactions

If the PoE port mode is never, the port power is off, but EnergyWise is not disabled. You can

• Configure EnergyWise on the port.

• Configure the port power level. The change takes effect after you change the port mode to auto or

static. You do not need to restart the switch.

If EnergyWise is disabled, the entity can use PoE to manage the port power usage.

OL-19806-03

Cisco EnergyWise Configuration Guide

1-13

Chapter 1 Managing Single Entities

254195

SVI 10

VLAN 10

10.0.0.42

VLAN 20

20.0.0.5

SVI 20

VLAN 20

20.0.0.1

VLAN 10

10.0.0.5

Preventing Network Access to a Non-Cisco End Point

We do not recommend using PC clients running EnergyWise Orchestrator as domain members. In an EnergyWise network, non-Cisco endpoints could have access to the connected IP network and the Internet.

Figure 1-4 PC with Access to the EnergyWise Network and the Internet

1 Domain member 5 Internet 2 Non-Cisco end point running an EnergyWise agent or client 6 DCHP server 3 Layer 2 switch 7 Router 4 Layer 3 switch 8 Management interface SVI 11

For example, in this network, to receive an IP address from the DHCP server, the PC sends a broadcast message to the switches, which forward the message to the Internet. The DHCP server receives the message and assigns an IP address to the PC.

When the PC sends an EnergyWise message to the Layer 2 switch, it forwards the message to the Layer 3 switch instead of responding to it. The Layer 2 switch and the connected PC are in different VLANs. The Layer 3 switch also forwards the message.

If the message is forwarded to the router, the router adds the PC to the router MAC address table as a directly connected device. To prevent this, you can configure a switched virtual interface (SVI) on the Layer 2 switch so that the PC and switch are now in the same VLAN.

The PC now has access to the connected IP network and to the Internet.

• When the PC sends messages to the switch, the switch now responds to the messages instead of

forwarding them.

• The PC can also send messages to and receive messages from the IP network.

1-14

Cisco EnergyWise Configuration Guide

OL-19806-03

Chapter 1 Managing Single Entities

208393

SVI 10

VLAN 10

10.0.0.42

VLAN 20

20.0.0.5

SVI 20

VLAN 20

20.0.0.1

CLI Compatibility Issues

Figure 1-5 PC without Access to the EnergyWise Network and the Internet

1 Domain member 5 Internet 2 Non-Cisco end point running an EnergyWise agent or client 6 DCHP server 3 Layer 2 switch 7 Router 4 Layer 3 switch 8 Interface to which ACL 102 is applied

To prevent the PC from accessing the IP network, create and apply an ACL to the ingress interface on the Layer 2 switch. This ACL permits only traffic sent to an IP address of 255.255.255.255 or 20.0.0.1 and to a UDP port of 43440.

Switch(config)# access-list 102 permit udp any any eq 43440 Switch(config)# access-list 102 permit udp any 20.0.0.1 0.0.0.0 eq 43440 Switch(config)# end Switch# show access-lists Extended IP access list 102 10 permit udp any any eq 43440 20 permit udp any 20.0.0.1 0.0.0.0 eq 43440

Note When you are creating an ACL, remember that, by default, the end of the access list contains an implicit

deny statement for all packets if it did not find a match before reaching the end.

CLI Compatibility Issues

EnergyWise Phase 2 is not backward-compatible with EnergyWise Phase 1.

Note Catalyst 6500 switches do not support EnergyWise Phase 1.

To display the EnergyWise version running on your switch, use the show energywise version privileged EXEC command.

To display the software version running on your switch, use the show version privileged EXEC command.

OL-19806-03

Cisco EnergyWise Configuration Guide

1-15

Manually Managing Power

Note If your switch is running EnergyWise Phase 2, enter the no energywise domain global configuration

command to disable EnergyWise before downgrading your software to a release supporting EnergyWise Phase 1.

If your switch is running EnergyWise Phase 1 and you upgrade your software to a release supporting EnergyWise Phase 2.

• The EnergyWise settings in the running configuration are updated. The switch sets the management

• For EnergyWise to work properly

Chapter 1 Managing Single Entities

password as the same domain password in the energywise domain command.

Enter the copy running-config startup-config privileged EXEC command to save the EnergyWise settings in the configuration file.

–

All domain members must run either

EnergyWise Phase 1

EnergyWise Phase 2 or later

Note To verify the EnergyWise release, use the show energywise version privileged EXEC

command. The EnergyWise release is referred to as the EnergyWise specification in the command output.

–

All domain members must have the same domain name and security mode.

–

If your switch is stacking-capable (for example, a Catalyst 3750-X, 3750-E, or 2960-S switch) and is a member of a switch stack, all the stack members must run the same EnergyWise version.

These commands in EnergyWise Phase 1 were modified:

• energywise domain domain-name secret [0 | 7] password global configuration command

We recommend that you reconfigure the EnergyWise domain with the energywise domain domain-name security {ntp-shared-secret | shared-secret} [0 | 7] shared-secret global configuration command.

If you do not reconfigure the domain, the switch synchronizes the management password with the the domain password.

• energywise management tcp-port-number global configuration command

We recommend that you reconfigure the management password for the domain with the energywise management security shared-secret [0 | 7] shared-secret port tcp-port-number global

configuration command.

For Catalyst 4500-specific issues, see Appendix A, “Cisco EnergyWise and Catalyst 4500 Switches.”

For Catalyst 6500-specific issues, see Appendix B, “Cisco EnergyWise and Catalyst 6500 Switches.”

Manually Managing Power

• Enabling EnergyWise, page 1-17

• Configuring Entity Attributes, page 1-18

Cisco EnergyWise Configuration Guide

1-16

OL-19806-03

Chapter 1 Managing Single Entities

• Powering the PoE Port, page 1-20

• Configuring Port Attributes, page 1-20

Enabling EnergyWise

Beginning in privileged EXEC mode:

Command Purpose

Step 1 Step 2

Step 3

configure terminal Enters global configuration mode.

service password-encryption (Optional) Enables password encryption.

energywise domain domain-name security {ntp-shared-secret | shared-secret} [0 | 7]

domain-password [protocol udp port udp-port-number [interface interface-id | ip ip-address]]

Manually Managing Power

If youset a hidden password in Step 3, enter this command.

Enables EnergyWise on the entity, assigns the entity to a domain with the specified domain-name, sets the domain security mode, and sets the domain password to authenticate all communication in the domain.

• ntp-shared-secret—Sets a strong password with NTP. If the

time between members varies ±30 seconds, the entity drops events.

• shared-secret—Sets a strong password without NTP.

Step 4

For information about domain security, see the “Secure Domain Communication” section.

• (Optional) 0—Uses an unencrypted password. This is the

default.

• (Optional) 7—Uses a hidden password.

If you do not enter 0 or 7, the default is 0.

• (Optional) port udp-port-number—Specifies the UDP port

that communicates with the domain.

The range is from 1 to 65000. The default is 43440.

• (Optional) interface interface-id—Specifies the port that

communicates with the domain if the IP address is dynamically assigned.We recommend that you specify the interface-id. You should use this in a bridged network.

• (Optional) ip ip-address—Specifies the IP address that

communicates with the domain if the interface is a switched virtual interface (SVI) and VLAN trunking protocol (VTP) pruning is enabled. You should use this in a routed network.

For the domain-name and domain-password

• You can enter alphanumeric characters and symbols such as

#, (, $, !, and &.

• Do not enter an asterisk (*) or a blank space between the

characters or symbols.

end Returns to privileged EXEC mode.

OL-19806-03

Cisco EnergyWise Configuration Guide

1-17

Manually Managing Power

Command Purpose

Step 5

show energywise

show energywise domain

Step 6

copy running-config startup-config (Optional) Saves your entries in the configuration file.

Configuring Entity Attributes

Beginning in privileged EXEC mode:

Command Purpose

Step 1 Step 2

Step 3

configure terminal Enters global configuration mode.

energywise importance importance (Optional) Sets the importance.

energywise keywords word,word,... (Optional) Assigns at least one keyword.

Chapter 1 Managing Single Entities

Verifies your entries.

The range is from 1 to 100. The default is 1.

When assigning multiple keywords, separate the keywords with commas, and do not use spaces between keywords.

• You can enter alphanumeric characters and symbols such as

#, (, $, !, and &.

Step 4

Step 5

• Do not enter an asterisk (*) or a blank space between the

characters or symbols.

By default, keywords are not defined.

service password-encryption (Optional) Enables password encryption.

If youset a hidden password in Step 5 or Step 10, enter this command.

energywise management security shared-secret [0 | 7] mgmt-password [port

tcp-port-number]

(Optional) Sets the management password on the switch that the management station uses to communicate with the domain.

• (Optional) 0—Uses an unencrypted password.

• (Optional) 7—Uses a hidden password.

If you do not enter 0 or 7, the default is 0.

• For the mgmt-password

–

You can enter alphanumeric characters and symbols such as #, (, $, !, and &.

–

Do not enter an asterisk (*) or a blank space between the characters or symbols.

• port tcp-port-number—Specifies the TCP port for

management access. The range is from 1025 to 65535. The default is 43440.

By default, the management password is not set.

1-18

Cisco EnergyWise Configuration Guide

OL-19806-03

+ 58 hidden pages

Cisco Systems OL-19806-03 User Manual

CONTENTS

Audience

Purpose

Preface

Conventions

Related Publications

Obtaining Documentation and Support on the Cisco Developer Network

Obtaining Documentation, Support, and Security Guidelines

Managing Single Entities

Overview

Creating an EnergyWise Domain

Power Levels

Attributes

Recurring Event

Secure Domain Communication

MIBs

Switch Connected to an IP Phone

Switch Connected to a PC

Configuration Guidelines

Using the Call In-Progress Feature

PoE and EnergyWise Interactions

Preventing Network Access to a Non-Cisco End Point

CLI Compatibility Issues

Manually Managing Power

Enabling EnergyWise

Configuring Entity Attributes