Write alarm

Similar Questions

• can anyone run this script?

  Hi all

  in order to proceed to a reconfiguration of the alarm, I need to get metricId of an alarm by default,

  the problem is, then from a previous test I accidentally deleted some of these alert, so I have to manually recreate but I can't find the metricId that match.

  So, in order to help me, can someone run this script:

  $Name = "unable to connect to the storage.

  $alarmMgr = get-view AlarmManager

  $alarms = $alarmMgr.GetAlarm ($null)

  $alarms | %{

  $alarm = get-view $_

  If ($alarm.Info.Name - eq $Name) {}

  "Write-Host-object' * $alarm.Info.Name:"-nonewline

  Write to $alarm.Info.Name

  Write-Host-object' * $alarm.Info.Expression.Expression [0]. "Metric:"-nonewline

  Write $alarm.Info.Expression.Expression [0]. Metric

  Write-Host-object' * $alarm.Info.Expression.Expression [0]. "Metric.CounterId:"-nonewline

  Write $alarm.Info.Expression.Expression [0]. Metric.CounterId

  Write-Host-object' * $alarm.Info.Expression.Expression [0]. "Metric.Instance:"-nonewline

  Write $alarm.Info.Expression.Expression [0]. Metric.Instance

  }

  }

  First of all, as is the case, a second time with $Name = "host error.

  and one last time with $Name = 'high-availability Cluster error. "

  The result of these commands will help me a lot to get my alarm

  Thanks in advance to anyone who can help me

  Here you go (host)

  

  and (cluster HA)

  

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Write the alarm log to PC localhost

  A quick question, maybe.  When you run SDFs and stimulus profiles located on another PC (i.e., via a network), how can I set the alarm for the log path to be on the local host?  In the path, instead of "C:\Data\*.*", input box I would like something like "\Data\*.*".

  Hello

  To do this you must set up a sharing network (i.e. the "Download" folder) and use a UNC as '\\localhost\Downloads '.

  Concerning

• OPC will not AB L32E - write Will Read

  OPC will not AB L32E - write Will Read.

  I was able to put in place an OPC server using OPC server, OR by using the ControlLogix Ethernet driver for the 1769-L32E AB PLC.

  All tags are visible. The lookout 6.7.1 see data in real time, but everything that I write too, never appears in the PLC.

  Using the OPCclient at Lookout. There is no alarm, another that a value has been adjusted by the direct user...

  There is no error of comm.

  I just bought this software last month.

  The OPC Server NOR, events, no error.

  Thank you.

  Dave

  I had figured it out. The address may be a little different than Lookout Direct.

• Alarm, based on the timestamp of file

  Is there a way of foglight to check if a file has been changed recently and create an alarm if it is more than 2 hours since the last update?

  Thanks in advance!

  Hey Wyatt,

  There is no out-of-the-box Foglight agent that collects the last modification time of a file.

  It is a good area for an agent to custom script similar to the discussion to: Foglight 5 monitoring of file system

  On what platform you want to monitor the last modification time of a file? Windows or Unix?

  There is a perl script that could be the basis for a custom script agent:

  http://www.UNIX.com/shell-programming-scripting/22357-finding-out-last-modified-time-files.html

  Given a script agent that collects the last modification time of a file, it would be too difficult to write a rule that fires if the file has not been updated for more than two hours.

  Kind regards

  Brian Wheeldon

• Set alarms for datastore small footprint

  Hello

  I would like to set alarms for data warehouses, it must notify me if there is less than 25 GB space in any data store. Since I'm new to vFoglight I don't know how to write a rule for this. any help is greatly appreciated.

  Thank you.

  This has been answered in a previous thread. See http://en.community.dell.com/techcenter/virtualization/infrastructure/f/4826/t/19555533#49821

  / Mattias

• Alarm on VM

  I have a batch file that I am running through Invoke-VMScript who sometimes does not. I can enter the error code from the file of commands on the virtual computer, but I was wondering if there is a way to raise any alarm in vCenter, so I can see there is not? For now, I have my script Invoke VMScript print just "ERROR" on the screen, but the ultimate goal is to put this in an automated process where I will not see the output directly so I need some kind of indicator that it did not work - ideally on the virtual machine at the other end of the call Invoke-VMScript. Really don't care which alarm it is either, just needing an indicator.

  It doesn't seem to be a direct method to generate an alarm, it seems that they must be produced on an event or condition of threshold/State. You can write an event defined by the user in order to keep a track of failure that can partially help you what you are looking for...

  $VM = "VMName".

  $EM = get-view event Manager

  $VMMoRef = (get-View - ViewType VirtualMachine-Filter @{Name = '$VM'}). MoRef

  $EM. LogUserEvent ($VMMoRef, "this is a message")

  When you look at events for the virtual machine, you will see "VMName".

  

• Recovery of vSphere PowerCLI with alarms

  Hello

  Can you please help me write a PowerCLI script that would recover the vSphere alarms?

  I want the script to show only alarms last 24 hours only if not acknowledged or deleted.

  Example:

  Get-VIEvent - MaxSamples 10 | Select Fullformattedmessage # this command shows me the last 10 events

  Win01 from green to Red alarm # the script "MyAlarm" should show me this alarm

  win01 on esx1.company.pri in Lodz is turned off

  win01 on esx1.company.pri in Lodz stops

  Task: Stop virtual machine

  win01 on esx1.company.pri in Lodz is turned on

  Message on win01 on esx1.company.pri in Lodz: running VMware ESX in a virtua...

  starts win01 on the host esx1.company.pri in Lodz

  Task: Power on virtual machine

  Task: Initialize turn

  Alarm"monitor the health status"on changed from yellow to green data centers.

  Help, please.

  If the alarm was not recognized and authorized, it should still show.

  You can see these alarms with

  $dc = get - file - name of data centers

  $dc. ExtensionData.TriggeredAlarmState |

  Select @{N = 'Entity'; E = {Get-view-Id $_.} Entity | {{Select - ExpandProperty name}}.

  OverallStatus,

  @{N = "alarm"; E = {(Get-View-ID $_.)} Alarm). Info.Name}}

  -What are you looking for?

• Purpose of the triggered alarm

  Hello

  I am trying to create a script that sends an email with all the daily alarms from VMware.  I did everything, but the part that identifies the object that is actually in a State of alarm.  I use the code below I've seen in other similar questions, but I can't find anything in the SDK that will produce this object.  I can get it only to point to the object where it is actually defined.  Am I missing a property which will produce who or what I have to drill down to each object in the inventory and check for alarms triggered?

  $vcenter = "vcntr01".

  SE connect-VIServer $vcenter

  $datacenters = (get-data center * | get-View)

  {foreach ($datacenter to $datacenters)

  foreach ($triggered in $datacenter. TriggeredAlarmState) {}

  $alarmDef is get-view-Id $triggered. Alarm

  Write-Host "$((get-vue_$alarmDef.Info.entity).name) $($alarmDef.Info.Name).

  }

  }

  Thank you!

  Try like this

  Get-Datacenter | where {$_.ExtensionData.triggeredAlarmState} | %{  $_.ExtensionData.triggeredAlarmState |  Select Time,    @{N="Entity";E={Get-View $_.Entity | Select -ExpandProperty Name}},    @{N="Alarm";E={Get-View $_.Alarm | Select -ExpandProperty Info | Select -ExpandProperty Name}}}
  

• script to collect 'Triggered alarms' 4 VC in a single report

  Hi team,

  I'm looking for a script to collect 'Triggered alarms' 4 VC in a single report. We use ESXi 4.1 worm in the VC.

  Is it possible to collect all 4 VC triggered alarms in a report by acronym and automatically by email with an Excel report.

  Thank you

  Kind regards

  Roze

  Finally the script helped for my need below.

  Hi looking for script to collect multiple vCenters triggered alarms below:

  How to run these scripts: \Get-TriggeredAlarms - vc001, vc002 vc03 vCenters

  Location of the output file: c:\temp\alarms.csv

  Script:

  ______________________________________________________________________________

  (param

  [String []] $vCenters

  )

  Function Get-TriggeredAlarms {}

  (param

  $vCenter = $(throw "doit être spécifié un vCenter."),

  [System.Management.Automation.PSCredential] $credential

  )

  If {($credential)

  $vc = to connect-VIServer $vCenter - Credential $credential

  }

  else {}

  $vc = to connect-VIServer $vCenter

  }

  If (! $vc) {}

  Write-Host "Failure connecting to vCenter $vCenter."

  output

  }

  $rootFolder = get-file-server $vc "data centers".

  {foreach ($ta in $rootFolder.ExtensionData.TriggeredAlarmState)}

  $alarm = "" | Select-Object VC, EntityType, alarm, entity, status, time, recognized, AckBy, AckTime

  $alarm. VC = $vCenter

  $alarm. Alarm = (Get-View-Server $vc $ta.) Alarm). Info.Name

  $entity = get-view-server $vc $ta. Entity

  $alarm. Entity = (Get-View-Server $vc $ta.) Entity). Name

  $alarm. EntityType = (Get-View-Server $vc $ta.) Entity). GetType(). Name

  $alarm. Status = $ta. OverallStatus

  $alarm. Time = $ta. Time

  $alarm. Recognized = $ta. Recognized

  $alarm. AckBy = $ta. AcknowledgedByUser

  $alarm. AckTime = $ta. AcknowledgedTime

  $alarm

  }

  Disconnect-VIServer $vCenter - confirm: $false

  }

  Write-Host ('Get messages from {0}. vCenters' f - $vCenters.Length)

  $alarms = @)

  {foreach ($vCenter to $vCenters)

  Write-Host "Getting alarms from $vCenter."

  $alarms += get-TriggeredAlarms $vCenter

  }

  $alarms | Export-csv c:\temp\alarms.csv

  __________________________________________________________________

• PowerCLI - clear alarm

  Hi all

  Recently, we found that our guests have been sensitive to this issue.  After you apply update vCenter to address this going forward, we went through all affected with script PowerCLI from VMware virtual machines.  The result is that each unique VM fixed by this script now has an alarm "vSphere HA machine virtual failover impossible" triggered.

  I thought it would be pretty easy to write a script to run through all our virtual machines and turn off the alarm if the date of call or alarm type matching certain criteria.

  I highly recommend to expose this functionality via PowerCLI.  I am quite surprised that we will need to manually clear these alarms - was trying to force me to not to use the GUI.

  Thank you!

  On a side note, it might be interesting to update the post found here:

  http://communities.VMware.com/message/1869541

  The code lacks a line break:

  $alarmMgr = Get-View AlarmManager Get-VM | where {$_.ExtensionData.TriggeredAlarmState} | %{
      $vm = $_
      $vm.ExtensionData.TriggeredAlarmState | %{
          $alarmMgr.AcknowledgeAlarm($_.Alarm,$vm.ExtensionData.MoRef)
      }
  }
  

  Should be

  $alarmMgr = Get-View AlarmManager #note the previous code missed a line break here
  
  Get-VM | where {$_.ExtensionData.TriggeredAlarmState} | %{
      $vm = $_
      $vm.ExtensionData.TriggeredAlarmState | %{
          $alarmMgr.AcknowledgeAlarm($_.Alarm,$vm.ExtensionData.MoRef)
      }
  }
  
  

  I updated the code, thanks for finding this.

  The clearing of the triggered alarms unfortunately use private API.

• Triggered alarms of several VC export.

  Hi team,

  I'm looking for a script to collect 'Triggered alarms' 4 VC in a single report. We use ESXi 4.1 worm in the VC.

  Is it possible to collect all 4 VC triggered alarms in a report by acronym and automatically by email with an Excel report.

  Thank you

  Kind regards

  Roze

  Finally the script helped for my need below.

  Try script to collect alarms triggered multiple vCenters below:

  How to run these scripts: \Get-TriggeredAlarms - vc001, vc002 vc03 vCenters

  Location of the output file: c:\temp\alarms.csv

  Script:

  ______________________________________________________________________________

  (param

  [String []] $vCenters

  )

  Function Get-TriggeredAlarms {}

  (param

  $vCenter = $(throw "doit être spécifié un vCenter."),

  [System.Management.Automation.PSCredential] $credential

  )

  If {($credential)

  $vc = to connect-VIServer $vCenter - Credential $credential

  }

  else {}

  $vc = to connect-VIServer $vCenter

  }

  If (! $vc) {}

  Write-Host "Failure connecting to vCenter $vCenter."

  output

  }

  $rootFolder = get-file-server $vc "data centers".

  {foreach ($ta in $rootFolder.ExtensionData.TriggeredAlarmState)}

  $alarm = "" | Select-Object VC, EntityType, alarm, entity, status, time, recognized, AckBy, AckTime

  $alarm. VC = $vCenter

  $alarm. Alarm = (Get-View-Server $vc $ta.) Alarm). Info.Name

  $entity = get-view-server $vc $ta. Entity

  $alarm. Entity = (Get-View-Server $vc $ta.) Entity). Name

  $alarm. EntityType = (Get-View-Server $vc $ta.) Entity). GetType(). Name

  $alarm. Status = $ta. OverallStatus

  $alarm. Time = $ta. Time

  $alarm. Recognized = $ta. Recognized

  $alarm. AckBy = $ta. AcknowledgedByUser

  $alarm. AckTime = $ta. AcknowledgedTime

  $alarm

  }

  Disconnect-VIServer $vCenter - confirm: $false

  }

  Write-Host ('Get messages from {0}. vCenters' f - $vCenters.Length)

  $alarms = @)

  {foreach ($vCenter to $vCenters)

  Write-Host "Getting alarms from $vCenter."

  $alarms += get-TriggeredAlarms $vCenter

  }

  $alarms | Export-csv c:\temp\alarms.

• Create alarm "hardware monitoring" by the script?

  Hello:

  I wonder how I can create the hardware by script monitoring alarm?

  For example, I want to write a script that will create the alarm similar to the default alarm "State of other objects of host hardware.

  Follow large docs LucD Web site (http://www.lucd.info/2009/11/27/alarm-expressions-part-2-event-alarms/), I wrote the following code:

  $alarm. Name = "status of other objects of host hardware.

  $alarm. Description = "monitor other objects of host hardware."

  $alarm. Enabled = $TRUE

  $expr1 = new-Object VMware.Vim.EventAlarmExpression

  $expr1. EventType = "com.vmware.vc.cim.CIMGroupHealthStateChanged."

  $expr1. ObjectType = "HostSystem.

  $expr1. Status = 'green '.

  $expr2 = new-Object VMware.Vim.EventAlarmExpression

  $expr2. EventType = "EnteringMaintenanceModeEvent."

  $expr2. ObjectType = "HostSystem.

  $expr2. Status = "yellow".

  $expr3 = new-Object VMware.Vim.EventAlarmExpression

  $expr3. EventType = "EnteringMaintenanceModeEvent."

  $expr3. ObjectType = "HostSystem.

  $expr3. Status = "red".

  $alarm.expression = new-Object VMware.Vim.OrAlarmExpression

  $alarm.expression.expression += $expr1

  $alarm.expression.expression += $expr2

  $alarm.expression.expression += $expr3

  $alarmMgr.CreateAlarm($entity.) MoRef, $alarm)

  But now I have problem to add arguments, operator, and value to all three different events (Advanced) Condition?

  Also, I know that I have to restart VC after creating this alarm, but it is fine with me (the same 'problem' I had added when storage network/monitoring of alarms by script).

  I would really appreciate the help.

  Thank you very much!

  Okay, I think I got it.

  You must use the property of comparisons to set conditions.

  Try this

  $entity = (Get-VMHost ).Extensiondata
  $alarm = New-Object VMware.Vim.AlarmSpec
  $alarmMgr = Get-View AlarmManager
  
  $alarm.Name = "Status of other host hardware objects"
  
  $alarm.Description = "monitor other host hardware objects"
  $alarm.Enabled = $TRUE
  
  $expr1 = New-Object VMware.Vim.EventAlarmExpression
  $expr1.EventType = "EventEx"
  $expr1.EventTypeId = "com.vmware.vc.cim.CIMGroupHealthStateChanged"
  $expr1.ObjectType = "HostSystem"
  $expr1.Status = "green"
  
  $condition11 = New-Object VMware.Vim.EventAlarmExpressionComparison
  $condition11.attributeName = "group"
  $condition11.operator = "equals"
  $condition11.value = "Other"
  
  $condition12 = New-Object VMware.Vim.EventAlarmExpressionComparison
  $condition12.attributeName = "newState"
  $condition12.operator = "equals"
  $condition12.value = "green"
  
  $expr1.Comparisons += $condition11
  $expr1.Comparisons += $condition12
  
  $expr2 = New-Object VMware.Vim.EventAlarmExpression
  $expr2.EventType = "EventEx"
  $expr2.EventTypeId = "com.vmware.vc.cim.CIMGroupHealthStateChanged"
  $expr2.ObjectType = "HostSystem"
  $expr2.Status = "yellow"
  
  $expr2.Comparisons += $condition11
  $condition22 = New-Object VMware.Vim.EventAlarmExpressionComparison
  $condition22.attributeName = "newState"
  $condition22.operator = "equals"
  $condition22.value = "yellow"
  $expr2.Comparisons += $condition22
  
  $expr3 = New-Object VMware.Vim.EventAlarmExpression
  $expr3.EventType = "EventEx"
  $expr3.EventTypeId = "com.vmware.vc.cim.CIMGroupHealthStateChanged"
  $expr3.ObjectType = "HostSystem"
  $expr3.Status = "red"
  
  $expr3.Comparisons += $condition11
  $condition32 = New-Object VMware.Vim.EventAlarmExpressionComparison
  $condition32.attributeName = "newState"
  $condition32.operator = "equals"
  $condition32.value = "red"
  $expr3.Comparisons += $condition32
  
  $alarm.expression = New-Object VMware.Vim.OrAlarmExpression
  $alarm.expression.expression += $expr1
  $alarm.expression.expression += $expr2
  $alarm.expression.expression += $expr3
  
  $action = New-Object VMware.Vim.AlarmAction
  
  $action = New-Object VMware.Vim.AlarmTriggeringAction
  $action.action = New-Object VMware.Vim.SendEmailAction
  $action.action.toList = "[email protected];"
  $action.action.ccList = ""
  $action.action.subject = ""
  $action.action.body = ""
  $action.green2yellow = $false
  $action.yellow2red = $false
  $action.red2yellow = $false
  $action.yellow2green = $false
  
  $spec = New-Object VMware.Vim.AlarmTriggeringActionTransitionSpec
  $spec.startState = "yellow"
  $spec.finalState = "red"
  $spec.repeats = $false
  
  $action.transitionSpecs = $spec
  
  $alarm.action = New-Object VMware.Vim.GroupAlarmAction
  $alarm.action.action += $action
  
  $setting = New-Object VMware.Vim.AlarmSetting
  $setting.toleranceRange = 0
  $setting.reportingFrequency = 0 
  
  $alarm.setting = $setting
  
  $alarmMgr.CreateAlarm($entity.MoRef, $alarm)
  

  Note that I reused the $condition11 into three expressions since it does not change.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Create alarm "Network redundancy lost" by the script?

  Hello:

  I'm trying to write a script that will create the alarm in order to monitor the redundancy of the lost network (I know manually there) on the host.

  I know how to create alarm for additional exhibit the ' basic' event (LucD - thank you for your help) and I know that I have for alarm 'Lost network redundancy' to use 'vprob.net.redundancy.lost' instead of 'EnteringMaintenanceModeEvent' (as in my example); but I still struggle to combine...

  Can someone help me please?

  Thank you

  qwert

  I don't have a particular script fantasy with the settings and all the rest, but I can show you the steps to filter alarms by name and remove the desired one.

  alarm #retrieve Manager

  $alarmManager = get-view-Id "AlarmManager-AlarmManager.

  #Get the entity that contains the alarm that you want to remove. I'll do it for a virtual machine

  $entityView = get-Vm-name MyVm | Get-View

  #get all MoRefs alarm

  $alarmMoRefList = $alarmManager.GetAlarm($entityView.MoRef)

  #Retrieve tha alarm views from the MoRefs

  $alarmViewList = $alarmMoRefList | foreach (Get-view $_)

  #Now filter the name alrams

  $alarmToDelete = $alarmViewList | where {$_.Info.Name - eq "AlarmToDelete"}

  #Finally remove alarms

  $alarmToDelete.RemoveAlarm)

  It shouldn't be hard to put this in a script or function reussable. If you have problems with this, I'll be happy to help you again!

• Get alarms and change default values

  My question is two really, I was just read the previous thread http://communities.vmware.com/thread/230786?tstart=0 and I was wondering how to get the list of existing alarms, after have stuck in the SDK for awhile, I thought I would ask experts.

  I see how they relate to the CROWD, but can not put it in the code.

  Also, is there a way to modify each alarm 5 by default that are created to add an action to send a snmp trap?

  Thank you

  Alan Renouf

  http://Virtu-al.NET/

  The first part of your question is easy.

  The following script will display just the name of the alarm, but you can find all the properties in the object of the alarm ($t variable).

  
  $serviceInstance = get-view ServiceInstance
  
  $alarmMgr = get-view $serviceInstance.Content.alarmManager
  
  $alarms = $alarmMgr.GetAlarm($null)
  $alarms | %{
       $t = Get-View -Id $_
       Write-Host $t.Info.Name
  }
  

  For the 2nd part of the question, yes you can change the preset alarms (as you can from the VIC).

  You'd use the ReconfigureAlarm method to do this.

  
  $predefined = "Host connection state","Host CPU Usage","Host Memory Usage","Virtual Machine CPU Usage","Virtual Machine Memory Usage"
  
  $serviceInstance = get-view ServiceInstance
  
  $alarmMgr = get-view $serviceInstance.Content.alarmManager
  
  $alarms = $alarmMgr.GetAlarm($null)
  $alarms | % {
       $alarm = Get-View -Id $_
       if($predefined -contains $alarm.Info.Name){
            $spec = New-Object VMware.Vim.AlarmSpec
            $spec.Action = New-Object VMware.Vim.GroupAlarmAction
            $spec.action.action = @(New-Object VMware.Vim.AlarmTriggeringAction)
            $spec.Action.Action[0].action = New-Object VMware.Vim.SendSNMPAction
            $spec.Action.Action[0].Green2yellow = $true
            $spec.Action.Action[0].Red2yellow = $false
            $spec.Action.Action[0].Yellow2green = $false
            $spec.Action.Action[0].Yellow2red = $true
            $spec.Name = $alarm.Info.Name
            $spec.Description = $alarm.Info.Description
            $spec.Expression = $alarm.Info.Expression
            $spec.Enabled = $alarm.Info.Enabled
            $spec.Setting = $alarm.Info.Setting
  
            $alarm.ReconfigureAlarm($spec)
       }
  }
  

  Alarms, listed in $predefined, will now send an SNMP trap when the State goes from green to yellow and when the State goes from yellow to red.