Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials

Energywise recurrence policy issue

I'm currently testing energywise with one of my sites. I'm setting up the recurrence policies using NPM. The problem i'm having is that the script it writes puts the incorrect policies on the switch. So here's what happened. I put in the policies and they worked right the first time. I have 3 policies. One runs Fri-Sun and sets the energy level to 2 at 9pm (2100 Hrs). The second runs Mon-Fri and sets the energy level to 10 at 5:45am (0545 Hrs). The third runs Mon-Thurs and sets the energy level to 3 at 9pm (2100 Hrs). This all worked the first time. The issue is that the device i'm using isn't energywise-aware so i have to change the policies to use level 0 and 10 only. When i made changes to the policy, it left the policy that sets to level 2, and added the other 3 policies I have. I set the policy change to not be additive, so it should have removed the current policies and created these if i'm reading it right. Now, I can't get rid of the level 2 policy. I can ssh into the switch and change the recurrence policy manually with no problem. So that's what I did. I removed the level 2 policy. After doing that, I created my recurrence policies in NPM again, and executed the change. Now it doesn't even attempt to do the policy changes that I've asked for according to the script viewer. The third time i tried it, it looks like it just enabled energywise on the interfaces and stopped. If i view the actual recurrence policies on the switch, they're completely wrong. Anyone know what's going on?

Find more posts tagged with

Accepted answers

All comments

damienball

I was able to get this fixed. What i had to do was run the energywise management and check the box that I wanted to set recurrence policies. I didn't type any policies, but just hit execute with it empty. It actually removed the entries it thought were there. I double-checked the switch and all the recurrence policies were properly removed. Then I ran the energywise management again and set the recurrence policies I want and clicked execute. It put the right policies on the switch. Anyone think this was a bug? Is there any way to see what policies Orion thinks it has and remove them without having to completely remove all recurrence policies?

bshopp

So you are pushing the changes/policies pushed via NCM correct?

damienball

Kinda I guess. I mean, i'm not setting up the policies in NCM, but i'm using the energywise management part of NPM.

If you login to NPM, go to Admin, Manage Nodes and select interfaces that support energywise, Under the "more" dropdown there is an option that says Manage Energywise. In there you can see all options for energywise not just recurrence policies, but i'm using that to set the policies. This connect to NCM somehow because I have to have a device in both NCM and NPM for it to work. I assume NPM uses NCM to push these policies to the device.

chris.lapoint

That's correct. NPM requires the NCM integration module to be installed to enable the EW configuration management capabilities.

Can you please open a support ticket and include the steps you listed above to reproduce? Also, include a link back to this thread. I'd like to see if we can reproduce in house.

Thanks,

damienball

I'm going to open a support case tomorrow. After verifying it on the switch AND on Orion that my policies were right, I went home happy. I just checked the policies and NPM says I have only 4 policies, which are wrong. It shows the 3 correct policies, plus the policy that sets the power level to 2 Fri-Sun at 9pm. That policy has to be stuck somewhere even though I read where the script deleted it from that switch (and verified it).

NCM must have automatically send a script updating that switch with new recurrence policies. It's craziness.