Usage Guidelines
Because debugging output is assigned high prioirity in the CPU process, it can render the system unusable.
For this reason, use debug commands only to troubleshoot specific problems or during troubleshooting sessions
with Cisco technical support staff. Use debug commands during periods of lower network traffic and fewer
users. Debugging during these periods decreases the likelihood that increased debug command processing
overhead will affect system use.
The undebug energywise command is the same as the no debug energywise command.
When you enable debugging on a stacking-capable switch, it is enabled only on the stack master. To enable
debugging on a stack member, use the session switch-number privileged EXEC command to start a session
from the stack master. Enter the debug command on the stack member command-line prompt. You can also
use the remote command stack-member-number LINE privileged EXEC command on the stack master to
enable debugging on a member switch before you start a session.
Examples
This example shows how to enable debugging for an EnergyWise query:
DomainMember# debug energywise query
Query debug debugging is on
DomainMember# energywise query importance 100 name sw* set level 1
EnergyWise query, timeout is 6 seconds:
May 19 00:38:28.596: NRGYZ:QUERY:Created query packet, locked CLI (0x77DCB24)!
Success rate is (1/1) setting entities
Queried: 1 Responded: 1 Time: 4.27 seconds
DomainMember#
May 19 00:38:38.624: NRGYZ:QUERY:Set CLI boolean, ready to unlock CLI (0x72238AC)
May 19 00:38:38.624: NRGYZ:QUERY:Unlocked CLI (0x72238AC)
Cisco EnergyWise Cisco IOS Command Reference for Catalyst 3850 Switches, EnergyWise Version 2.8
OL-32343-01 5
EnergyWise Commands
debug energywise
To Next Page
Loading...
Need help?
General