Documentation forNetwork Configuration Manager
Managing network configurations is a key capability of SolarWinds Observability Self-Hosted (formerly Hybrid Cloud Observability) and is available in the Advanced edition. Network Configuration Manager (NCM) is also available in a standalone module.

Manage EnergyWise interface

Offers the ability to configure Cisco EnergyWise interfaces. The following fields are available:

EnergyWise Features

Allows you to enable or disable the EnergyWise features of the selected interface.

EnergyWise Name

Allows you to specify an EnergyWise-specific name to identify the interface. The default name for a switch is the hostname, while the default name for a Power over Ethernet (PoE) port is a shortened version of the port name. EnergyWise name values cannot include spaces. Modifying the EnergyWise name does not change the hostname of the device or the port name on the device. Omit spaces and refrain from using asterisks (*) in your name designations. Valid characters include alphanumeric characters and symbols, including #, (, %, !, or &.

Keywords

Allows you to specify a keyword or set of keywords. Keywords describe the specific device or interface and help differentiate it from others in your domain. If you set more than a single keyword, ensure you separate the values with a comma and omit all spaces.

Default Power Level

Allows you to specify the default power level for the interface. Power levels range from 0 to 10, where 0 is off and 10 is full.

Level

Label

Category

Color

Color Code

10

Full

Operational

(1)

Red

FF0000

9

High

8

Reduced

Yellow

FFFF00

7

Medium

6

Frugal

Green

00FF00

5

Low

4

Ready

Standby

(0)

Blue

0000FF

3

Standby

2

Sleep

Brown

A52A2A

1

Hibernate

0

Shut

Nonoperational

(-1)

Black

000000

Importance

Allows you to specify a number from 1 to 100 as an importance value. The higher the value, the more important the interface and less likely it is to be changed by energy policy modifications. Use the importance value to exempt entities from policy changes. For example, if your emergency phone is attached to this interface, they should never go into standby mode, and the switch has an importance of 100, then policies with an importance of 99 and lower will not affect the phone port.

Role

Allows you to specify a role for the device or interface to help distinguish them from one another. The default role for a PoE port is Interface, while the default for a switch is the model number. You can use a role to make locating an entity easier or describe the entity's use. For example, you can specify the role of a device as MeetingRoom212 or PhonesForLevel2. Omit spaces and refrain from using asterisks (*) in your role designations.

Recurrence Policy

Allows you to specify a basic or advanced EnergyWise schedule.

Basic

Allows you to specify the time to start a policy, the power level to set for entities affected, the importance of the recurrence policy, and the days on which to apply the policy.

Importance designates what entities are affected by the policy. Only those entities with an equal or lower importance are affected by a policy with a matching or greater importance. For example, if business phones are designated with an importance of 50, they will be affected by a recurrence policy with an importance of 50 or greater.

Advanced

Allows you to specify the minutes (00-59), hours (00-23), day of month (1-31), month (1-12), day of week (0-7, where 0 and 7 both designate Sunday), the power level to set for entities affected, and the importance of the recurrence policy. Interfaces or devices

Importance designates what entities are affected by the policy. Only those entities with an equal or lower importance are affected by a policy with a matching or greater importance. For example, if business phones are designated with an importance of 50, they will be affected by a recurrence policy with an importance of 50 or greater.

Write config to NVRAM after execute

Check to ensure your EnergyWise configuration is not lost if the device reboots. Checking Write to NVRAM After Execute may cause the device to power cycle.