Cisco EnergyWise Configuration Guide, EnergyWise Phase 1
Managing Single Entities
Downloads: This chapterpdf (PDF - 320.0KB) The complete bookPDF (PDF - 1.34MB) | Feedback

Managing Single Entities

Table Of Contents

Managing Single Entities

EnergyWise Entity

EnergyWise Domain

EnergyWise Network

Single PoE Switch Scenario

EnergyWise Power Level

EnergyWise Importance

EnergyWise Names, Roles, and Keywords

Supported MIBs

Configuration Guidelines

PoE and EnergyWise Interactions

Manually Managing Power

Powering the Entity

Configuring Entity Attributes

Powering the PoE Port

Configuring PoE-Port Attributes

Automatically Managing Power (Recurring Event)

Examples

Setting Up the Domain

Manually Managing Power

Automatically Managing Power


Managing Single Entities


Use Cisco EnergyWise to manage the energy usage of entities in an EnergyWise network.

EnergyWise Entity

EnergyWise Domain

EnergyWise Network

Single PoE Switch Scenario

EnergyWise Power Level

EnergyWise Importance

EnergyWise Names, Roles, and Keywords

Supported MIBs

Configuration Guidelines

PoE and EnergyWise Interactions

Manually Managing Power

Automatically Managing Power (Recurring Event)

Examples

If your switch is stacking-capable, unless otherwise noted, the term switch refers to a standalone switch and to a switch stack.


Note The examples in this document are for a Catalyst 3750-E or 3750 switch (for example, gigabitethernet 1/0/5). To specify an interface on your network device, see your device software documentation.


For more information about EnergyWise, go to http://www.cisco.com/en/US/products/ps10195/tsd_products_support_series_home.html.

EnergyWise Entity

An EnergyWise entity is a physical or logical device with EnergyWise enabled, such as a Catalyst switch, a power over Ethernet (PoE) port, or a PoE device.

EnergyWise uses a distributed model to manage energy usage.

Switches are grouped in an EnergyWise domain and become domain entities. They receive messages from and send them to other domain entities.

An entity in the EnergyWise domain responds to queries.

An entity participating in EnergyWise controls the power usage of connected PoE devices, such as an IP phone, an IP camera, or a PoE-enabled device. For example, a Catalyst switch can power off the IP phone.

On an EnergyWise-enabled entity

The entity always participates in EnergyWise.

PoE ports participate in EnergyWise.

Non-PoE ports do not participate in EnergyWise.

EnergyWise Domain

An EnergyWise domain can be an EnergyWise network.

The domain is treated as one unit of power management.

Entities have neighbor-to-neighbor relationships with other domain entities.

For more information, see Chapter 4, "Configuration Examples."

EnergyWise Network

An EnergyWise network has EnergyWise entities in a domain.

Figure 1-1 Typical Network

1

Entity managing power usage

3

Entities

2

Domain

   

Single PoE Switch Scenario

Managing the power usage when

A PoE entity powers on or off the connected entities.

A PoE entity applies a network policy that powers on and powers off connected entities. The specified times are local times based on the PoE-entity time zone. For example, IP phones are powered on at 7:00 a.m. (0700) local time, and they are powered off at 7:00 p.m. (1900) local time.

This is also known as a recurring event.

Figure 1-2 Single PoE Switch Example

1

Entity managing power usage

3

Entities

2

Domain

   

EnergyWise Power Level

The EnergyWise power level is for a PoE switch port.

The range is from 0 to 10.

The default power level is 10.

A Catalyst switch does not support level 0.

A PoE port supports level 0 to level 10.

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

If the power level is from 1 to 10, the port is powered on. If the power level is 0, enter any value in this range to power on the PoE port or the switch.

When the power level changes, the port determines the action for the connected entities.

EnergyWise Importance

Set the EnergyWise importance value on a PoE port or a switch to rank domain entities.

The range is from 1 to 100.

The default importance value is 1.

EnergyWise Names, Roles, and Keywords

Set an EnergyWise-specific entity name to identify the domain entity.

For a PoE port, the default is a short version of the port name; for example, Gi1.0.2 for Gigabit Ethernet 1/0/2.

For a switch, the default is the hostname.

Set the role of the domain entity to differentiate it from other entities.

For a PoE port, the default is interface.

For a switch, the default is the model number.

Set at least one keyword describing an entity to differentiate it from other entities.

Supported MIBs

EnergyWise supports the CISCO-ENERGYWISE-MIB.

To access information about this MIB, go to http://www.cisco.com/public/sw-center/netmgmt/cmtk/mibs.shtml and click SNMP v2 MIBs.

You can also use FTP to access the MIB files. To get a MIB file:


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.

Step 6 Use the get MIB_filename command to obtain a copy of the MIB file.


Configuration Guidelines

By default, EnergyWise is disabled.

When you add an entity to a domain, EnergyWise is enabled on the entity and its PoE 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 entity.

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 you enter the energywise level level command.

If you schedule the entity to power on the PoE port at 7:00 a.m. (0700), the port powers on within 1 minute, between 7:00 a.m.(0700) and 7:01 a.m. (0701) local time.

PoE and EnergyWise Interactions

Table 1-1 Does the Entity Participate in EnergyWise?

EnergyWise Entity
PoE Mode
auto
never
static

PoE port

Yes

No

Yes

Non-PoE port

No

No

No


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 level 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 port power.

Manually Managing Power

Powering the Entity

Configuring Entity Attributes

Powering the PoE Port

Configuring PoE-Port Attributes

Powering the Entity

 
Command
Purpose

Step 1 

 

Go to privileged EXEC mode.

Step 2 

show energywise

(Optional) Verify that EnergyWise is disabled.

Step 3 

configure terminal

Enter global configuration mode.

Step 4 

energywise domain domain-name secret [0 | 7] password [protocol udp port udp-port-number [interface interface-id | ip ip-address]]

Enable EnergyWise on the entity, assign the entity to a domain with the specified domain-name, and set the password for secure communication among the entities in the domain.

(Optional) 0—Use an unencrypted password. This is the default.

(Optional) 7—Use a hidden password.

If you do not enter 0 or 7, the entity uses the default value of 0.

(Optional) port udp-port-number—Specify the UDP port that sends and receives queries.

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

(Optional) interface interface-id—Specify the port from which the EnergyWise messages are sent.

(Optional) ip ip-address—Specify the IP address from which the EnergyWise messages are sent.

For the domain-name and password

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

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

By default, no domain and password are assigned.

Step 5 

end

Return to privileged EXEC mode.

Step 6 

show energywise

show energywise domain

Verify your entries.

Step 7 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

Configuring Entity Attributes

 
Command
Purpose

Step 1 

 

Go to privileged EXEC mode.

Step 2 

show energywise

(Optional) Verify that EnergyWise is enabled.

Step 3 

configure terminal

Enter global configuration mode.

Step 4 

energywise importance importance

(Optional) Set the importance of the entity.

The range is from 1 to 100.

The default is 1.

Step 5 

energywise keywords word,word,...

(Optional) Assign at least one keyword for the entity.

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 &.

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

By default, no keywords are defined.

Step 6 

energywise management tcp-port-number

(Optional) Specify the TCP port that sends and receives queries.

The range is from 1025 to 65535.

The default is 43440.

Step 7 

energywise name name

(Optional) Specify the EnergyWise-specific entity name.

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

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

The default is the hostname.

Step 8 

energywise neighbor [hostname| ip-address] udp-port-number

(Optional) Assign a static neighbor.

(Optional) Hostname (hostname) or IP address (ip-address).

UDP port (udp-port-number) that sends and receives queries. The range is from 1 to 65000.

By default, no static neighbors are assigned.

Step 9 

energywise role role

(Optional) Specify the role of the entity in the EnergyWise domain. For example, lobby.b20.

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

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

The default is the model number.

Step 10 

end

Return to privileged EXEC mode.

Step 11 

show energywise

show energywise domain

Verify your entries.

Step 12 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

Powering the PoE Port

 
Command
Purpose

Step 1 

 

Go to privileged EXEC mode.

Step 2 

configure terminal

Enter global configuration mode.

Step 3 

interface interface-id

Specify the port or the range of ports to be configured, and enter interface configuration mode.

Step 4 

energywise level 0

or

energywise level 10

(Optional) Manually power off the port, or

Manually power on the port.

Step 5 

end

Return to privileged EXEC mode.

Step 6 

show energywise domain

show energywise children

Verify your entries.

Step 7 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

Note The power level that you set in Step 4 is the default power level when the switch restarts.

Configuring PoE-Port Attributes

 
Command
Purpose

Step 1 

 

Go to privileged EXEC mode.

Step 2 

configure terminal

Enter global configuration mode.

Step 3 

interface interface-id

Specify the port or the range of ports to be configured, and enter interface configuration mode.

Step 4 

energywise importance importance

(Optional) Set the importance of the port.

The range is from 1 to 100.

The default is 1.

Step 5 

energywise keywords word,word,...

(Optional) Assign at least one keyword for the port.

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 &.

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

By default, no keywords are defined.

Step 6 

energywise name name

(Optional) Specify the EnergyWise-specific port name.

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

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

The default is a short version of the port name; for example, Gi1.0.2 for Gigabit Ethernet 1/0/2.

Step 7 

energywise role role

(Optional) Specify the role of the port in the domain. For example, lobbyport.

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

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

By default, the role is interface.

Step 8 

end

Return to privileged EXEC mode.

Step 9 

show energywise domain

show energywise children

Verify your entries.

Step 10 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

Automatically Managing Power (Recurring Event)

 
Command
Purpose

Step 1 

 

Go to privileged EXEC mode.

Step 2 

show energywise

(Optional) Verify that EnergyWise is enabled.

Step 3 

configure terminal

Enter global configuration mode.

Step 4 

energywise domain domain-name secret [0 | 7] password [protocol udp port udp-port-number [interface interface-id | ip ip-address]]

Enable EnergyWise on the entity, assign the entity to a domain with the specified domain-name, and set the password for secure communication among the entities in the domain.

(Optional) 0—Use an unencrypted password. This is the default.

(Optional) 7—Use a hidden password.

If you do not enter 0 or 7, the entity uses the default value of 0.

(Optional) port udp-port-number—Specify the UDP port that sends and receives queries.

The range is from 1 to 65000.

The default is 43440.

(Optional) interface interface-id—Specify the port that sends EnergyWise messages.

(Optional) ip ip-address—Specify the IP address of the port that sends EnergyWise messages.

For the domain-name and password,

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

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

By default, no domain and password are assigned.

Step 5 

interface interface-id

Specify the port or a range of ports to be configured, and enter interface configuration mode.

Step 6 

energywise level 10 recurrence importance importance at minute hour day_of_month month day_of_week

(Optional) Schedule the power-on recurring event.

importance importance—The recurring event occurs if the importance value of the entity connected to a switch is less than or equal to the specified importance value. The range is from 1 to 100.

minute—The range is from 0 to 59. Use * for the wildcard.

hour—The range is from 0 to 23. Use * for the wildcard.

day_of_month—The range is from 1 to 31. Use * for the wildcard.

month—The range is from 1 (January) to 12 (December). Use * for the wildcard.

day_of_week—The range is from 0 (Sunday) to 6 (Saturday). Use * for the wildcard.

Note The specified time is the local time based on the PoE-entity time zone.

Step 7 

energywise level 0 recurrence importance importance at minute hour day_of_month month day_of_week

(Optional) Schedule the power-off recurring event.

importance importance—The recurring event occurs if the importance value of the entity connected to a switch is less than or equal to the specified importance value. The range is from 1 to 100.

minute—The range is from 0 to 59. Use * for the wildcard.

hour—The range is from 0 to 23. Use * for the wildcard.

day_of_month—The range is from 1 to 31. Use * for the wildcard.

month—The range is from 1 (January) to 12 (December). Use * for the wildcard.

day_of_week—The range is from 0 (Sunday) to 6 (Saturday). Use * for the wildcard.

Note The specified time is the local time based on the PoE-entity time zone.

Step 8 

end

Return to privileged EXEC mode.

Step 9 

show energywise recurrence

Verify your entries.

Step 10 

copy running-config startup-config

(Optional) Save your entries in the configuration file.

Examples

Setting Up the Domain

Manually Managing Power

Automatically Managing Power

Setting Up the Domain

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# energywise domain cisco secret cisco protocol udp port 43440 ip 2.2.4.30 
Switch(config)# energywise importance 50
Switch(config)# energywise keywords lab1,devlab 
Switch(config)# energywise name LabSwitch
Switch(config)# energywise neighbor TG3560G-21 43440
Switch(config)# energywise role role.labaccess
Switch(config)# end
Switch# show energywise domain 
Name      : TG3560G-41
Domain    : cisco
Protocol  : udp
IP        : 2.2.2.21

Port      : 43440
Switch# show energywise neighbors 
Capability Codes: R - Router, T - Trans Bridge, B - Source Route Bridge
                  S - Switch, H - Host, I - IGMP, r - Repeater, P - Phone
Id   Neighbor Name                 Ip:Port                 Prot   Capability
--   -------------                 -------                 ----   ----------
1    TG3560G-21                    2.2.2.21:43440          udp    S I
2    TG3560G-31                    2.2.4.31:43440          static S I
3    TG3560G-22                    2.2.2.22:43440          cdp    S I

Manually Managing Power

To power on the lab IP phones now:

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# energywise domain cisco secret cisco protocol udp port 43440 ip 2.2.4.44 
Switch(config)# interface gigabitethernet1/0/3
Switch(config-if)# energywise importance 65
Switch(config-if)# energywise name labphone.5
Switch(config-if)# energywise role role.labphone
Switch(config-if)# end

Automatically Managing Power

The lab IP phones automatically power on at 8:00 a.m. (0800) local time and power off at 8:00 p.m.(2000) local time.

Switch# configure terminal
Enter configuration commands, one per line.  End with CNTL/Z.
Switch(config)# energywise domain cisco secret cisco protocol udp port 43440 ip 2.2.4.30 
Switch(config)# interface gigabitethernet1/0/3
Switch(config-if)# energywise level 10 recurrence importance 90 at 0 8 * * *
Switch(config-if)# energywise level 0 recurrence importance 90 at 0 20 * * *
Switch(config-if)# energywise importance 50
Switch(config-if)# energywise name labInterface.3
Switch(config-if)# energywise role role.labphone
Switch(config-if)# end

Switch# show energywise recurrences 
Id     Addr       Class Action Lvl Cron
--     ----       ----- ------ --- ----
1      Gi1/0/3    QUERY SET    10  minutes: 0 hour: 8 day: * month: * weekday: *
2      Gi1/0/3    QUERY SET     0  minutes: 0 hour: 20 day: * month: * weekday: *

Switch# show running-config
<output truncated>
interface GigabitEthernet1/0/3
energywise level 10 recurrence at 0 8 * * *
 energywise level 0 recurrence at 0 20 * * *
 energywise importance 50
 energywise role role.lobbyaccess
 energywise name lobbyInterface.3
end
<output truncated>