Table Of Contents
Managing Multiple Entities
Multiple PoE Switch Scenario
EnergyWise Query
Using Queries to Manage Power in the Domain
Examples
Querying with the Name Attribute
Querying with Keywords
Querying to Set Power Levels
Managing Multiple Entities
•
Multiple PoE Switch Scenario
•EnergyWise Query
•Using Queries to Manage Power in the Domain
•Examples
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.
Multiple PoE Switch Scenario
Figure 2-1 Multiple PoE Switches Example
1
|
Entity managing power usage
|
3
|
Entities
|
2
|
Domain
|
|
|
EnergyWise Query
•Collect power usage information.
•Summarize power information from entities.
•Set parameters. Only the setting in the running configuration changes.
Use these attributes to filter results:
•Importance.
•Entity name.
•One or more keywords for a port or for a group of ports.
Use EnergyWise importance values to select entities in a query. For example, an office phone is less important than an emergency phone that should never be in sleep mode.
Query results show entities, such as PoE ports, with importance values less than or equal to the specified value in the query.
The entity sending a query to all domain entities receives the results.
Using Queries to Manage Power in the Domain
| |
Command
|
Purpose
|
Step 1
|
|
Go to privileged EXEC mode.
|
Step 2
|
energywise query importance importance {keywords word,word,... | name name} collect {delta | usage}
or
energywise query importance importance {keywords word,word,... | name name} sum {delta | usage}
|
(Optional) Run a query to display power information for the domain entities and PoE ports.
•importance importance—Filter the results based on the importance value. Only entities with values less than or equal to the specified value appear. The importance range is from 1 to 100.
•(Optional) keywords word,word,...—Filter the results based on one or more of the specified keywords.
•(Optional) name name —Filter the results based on the name. For the wildcard, use * or name* with the asterisk at the end of the name phrase.
•collect {delta | usage}—Display the delta or usage values for the entities and PoE ports.
–delta—Display the delta vector with the difference between the actual power usage and the maximum power usage for each power level for what-if calculations.
–usage—Display the actual power usage.
•sum {delta | usage}—Display the sum of the delta or usage values for the entities and PoE ports.
–delta—Display the delta vector.
–usage—Display the actual power usage.
Note In the results with the sum keyword, the Responded total is not accurate. The Queried total is accurate and is the total number of entities that respond to the query.
Repeat this step to run another query.
|
Step 3
|
energywise query importance importance {keywords word,word,... | name name} set level level
|
(Optional) Run a query to power on or power off the domain entities or PoE ports.
Caution Use this query with care because it affects the entity on which you enter the command and other domain entities that match the query criteria.
•importance importance—Filter the results based on the importance value. Only entities with values less than or equal to the specified value appear. The importance range is from 1 to 100.
•(Optional) keywords word,word,...—Filter the results based on one or more of the specified keywords.
•(Optional) name name —Filter the results based on the name. For the wildcard, use * or name* with the asterisk at the end of the name phrase.
•set level level—Set the power level of the entities or PoE ports. The range is from 0 to 10.
Repeat this step to run another query.
|
Examples
•Querying with the Name Attribute
•Querying with Keywords
•Querying to Set Power Levels
In these examples, Switch 1 and Switch 2 are in the same domain. The entity called shipping.1 is a PoE port on Switch 1, and the entity called shipping.2 is a PoE port on Switch 2.
Querying with the Name Attribute
To show the power usage of the domain entities with names beginning with shipping and with importance values less than or equal to 80, run this query on Switch 1:
Switch# energywise query importance 80 name shipping.* collect usage
EnergyWise query, timeout is 3 seconds:
192.168.20.1 shipping.1 6.3 (W)
192.168.20.2 shipping.2 8.5 (W)
Queried: 2 Responded: 2 Time: 0.4 seconds
The first row (shipping.1) is from Switch 1. The second row (shipping.2) is from Switch 2, a neighbor of Switch 1.
Querying with Keywords
To show the power usage of IP phones with different names, different roles, and importance values less than or equal to 80, but all with the Admin keyword, run this query on Switch 1:
Switch# energywise query importance 80 keyword Admin collect usage
EnergyWise query, timeout is 3 seconds:
192.168.40.2 shipping.1 6.3 (W)
192.168.50.2 orders.1 10.3 (W)
Queried: 2 Responded: 2 Time: 0.5 seconds
Switch 1 reports two phones are connected to Switch 2, a neighbor of Switch 1.
Querying to Set Power Levels
Run these queries on Switch 1 to
•Set the power level of the shipping.2 entity to 0:
Switch# energywise query importance 80 name shipping.2 set level 0
•Manually set the power level of the shipping.1 entity and the shipping.2 entity to 0:
Switch# energywise query importance 90 name shipping.* set level 0
•Set the power level of entities with the keyword Admin to 10:
Switch# energywise query importance 60 keyword Admin set level 10
EnergyWise query, timeout is 3 seconds:
Success rate is (2/2) setting entities
Queried: 2 Responded: 2 Time: 0.15 seconds
Verify the power levels:
Switch# energywise query importance 85 keyword Admin collect usage
EnergyWise query, timeout is 3 seconds:
192.168.40.2 shipping.1 0.0 (W)
192.168.50.2 orders.1 0.0 (W)
Queried: 2 Responded: 2 Time: 0.9 seconds
You can also use the show energywise usage privileged EXEC command on Switch 1 and Switch 2 to verify the power levels.
Feedback
