Automation

HI LuCD,

I am opening a new thread to export all alarms whether enable or disable in the Venter. I have taken reference from thread Re: Export All Alarms and definitions from VCenter.  but it's not working for me correctly. It's exporting partila number of alarms. I want to export all alarms from vcenter which either enabled or disabled from vcenter. Could you please help me with it.

What do you want to see in the export, besides Name,Description,Entity,Enabled?

Moderator: You're already actively engaged in another thread - no need to create your own as well.

Thread locked.

scott28tt This request is different, the other thread wanted to have all triggers on a separate line.

Thread unlocked

OK thanks - I'll leave you to it :smileyhappy:

Let's start with this one

Hi LuCd,

Thanks for help. It is working perfectly. Need one more help.

What will be script if i want to export these alarms and import in other vcenter to make them as a standard.

We don't want different vcenter at have different alarm definitions , they all should have same definitions.

Thanks

Then you could have a look at KB1032660

Thanks LuCD for help

Was trying to copy alarms VC7 to VC7 without any luck. Is this script support VC7 as well?

My crystal ball is currently out for maintenance, can you provide some more details on how you ran this and what goes wrong?

I was trying to copy alarms and definitions between two vCenter Servers (Version 7 U2) with help of the following VM KB without luck.

https://kb.vmware.com/s/article/1032660

That is not a lot of information to go on.

Sorry, my bad. I have a requirement of copying the existing alarms and definition from one vCenter to another vCenter. Both vCenters are in 7.U2

I did the following steps. 

Downloaded the scrip from the following VMware KB

https://kb.vmware.com/s/article/1032660

When I tried to run for the first time it gave an error related to the certificate. With the following command, I was able to run script

Set-PowerCLIConfiguration -InvalidCertificateAction Ignore -Confirm:$false

Then I ran the script with the Souce and Destination vCenter information. Script ran without any error throwing but no alarms were copied to the destination vCenter from source vCenter.

I didn't write that script, so you probably have to open an SR mentioning that KB.

To start, did you change line 92 (as the comments state)?
Otherwise only alarms whose name matches "MY.*" will be copied.

Do you see any tasks (Alarm creation) appearing in VC2?

You could enable Verbose output (set variable $verbosePreference to 'Continue') and check if that sheds any light on the issue.

Ultimately you can run the script in an IDE (for example Visual Studio Code) and set some breakpoints.
That might help finding out where things go wrong.

I'm too lazy a reader. Thank you very much . It was line 92. I changed and everything working fine. 

Thank you once again.

LucD,

This KB is now deleted, is there a copy somewhere I can access? Google can't find it.

Thanks!

The script in that KB hasn't worked since vSphere 6.* it seems.
That probably explains why the KB was removed.

Might the script in Solved: copy alarms from root to many datacenters - VMware Technology Network VMTN help?

Gave it a shot and updated likes 69 & 70 as he suggested, getting more than a few errors from them. I'll poke at them, but if anything comes to mind when you see it please share:

It's close to working as written. I read back through the whole conversation to get clues, here's where I'm hung up:

I get that error, not sure what to do about it.

But the main issue is one that SteJeh references in his post, "- the copied alarms in root will be named in "alarm name (moved to dc1, dc2, dc3, dc4, dc5 ... )"; how to change your great script to rename the original name one time?"

So I'll run the script to move the alarm Test1 from DC1 to DC2, and the alarm will stay in DC1 but the name will be changed to "Test1 (moved to DC2). They said they fixed it by deleting the alarm from the target DC (if I'm reading it correctly), but it doesn't even exist in the target DC so I'm not sure where to go from here.

Thanks in advance!

Which version of the script in that thread did you use?
The attachment in the last reply?

Yes, the one SteJah marked as correct and attached - Move-Alarm-v2

The only changes I made to it was I made $to a single datacenter ($to = Get-DataCenter -Name "DC2")

I suspect you ran the script from my Alarms – Moving them around post before.
That script defines the variable $alarmLength as a constant.
If you haven't stopped your PS session, that variable will stay a constant.

Restarted the session and you're right, didn't get that alert. But it's still doing the thing where it doesn't move it, it just renames it. Here's the only error it throws and some screenshots:

Let me know if you have any thoughts

It looks as if the Datacenter is not found.
Is that Datacenter moved/changed/created after you populate the content of the $destination variable?

No, all the datacenters are connected and responding to powershell when tested.

This error

The object 'vim.Datacenter:datacenter-3' has already been deleted or has not been completely created

seems to say that the value in $destination is not correct though.

Do a stop/start of your PS session.
Check you have only 1 vCenter connection open.

Oh, dang, well that definitely is the problem! I'm trying to copy alarms to a datacenter in a different vCenter instance! Is that not supported?

That should be possible when you have 2 vCenters open and you have the DefaultVIServerMode set to Multiple.
Check with Get-PowerCLIConfiguration and eventually change with Set-PowerCLIConfiguration

Hm, yeah, I have both connected and it was already set to multiple.

Do you have 2 Datacenters with the same name in the 2 vCenters?

No sir. In the screenshot I've attached, I'm moving the alarms from 1 to 2. They don't even share a matching character

Try adding the Server parameter with the name of the destination vCenter on the Get-Datacenter cmdlet

Same outcome, I'm afraid. I even tried moving the test alarm to a datacenter in the same vCenter instance and got the same error. Maybe the script just isn't going to work in my environment

Did you add a Server parameter on the Get-View cmdlet where the $alarmMgr variable is populated?

That did it! If anyone else comes across this with the same issue, change this line:

I am very grateful to LucD for providing this script and helping me a lot. Thank you so much