locked
Forwarding Alerts via SNMP Trap Generator from SCOM to Spectrum RRS feed

  • Question

  • I'm interested in implementing this as a temporary "connector" to CA Spectrum.  This seems like the easiest, quickest way to forward Alerts from SCOM to Spectrum until we upgrade Spectrum to the newer version that has a builtin SCOM Connector.  The issue is that i've always been advised to use the Command Notification channel sparingly since it will need to launch a separate instance of the .exe or script for every Alert that meets the subscription.  I would like to know what experience people have had with this if anyand did they see significant performance issues/problems, etc.  Again we would like to use this for a 3-6 month period to only forward AD MP Alerts and Windows OS Alerts.  Is this just a definitely no no or is this a viable temporary solution?
    Marc Schmieder
    Thursday, May 13, 2010 1:36 PM

Answers

    1. Create a new notification channel
    • Full Path of the command line : C:\WINDOWS\System32\windowspowershell\v1.0\PowerShell.exe
    • Command line parameters : C:\OpsMgrScripts\TrapGenerator\mposter.ps1 '$Data/Context/DataItem/AlertId$'
    • Startup folder for the command line : C:\OpsMgrScripts\TrapGenerator

    Content of mpposter.ps1 (The mpposter.exe must be in the folder C:\OpsMgrScripts\TrapGenerator\mposter.exe)
    -------------------------------------------------------

     ==============================================================================================
    # 
    # Microsoft PowerShell Source File
    # 
    # NAME: mposter.ps1
    # 
    # 
    # COMMENT: This script will generate an SNMP trap to a given destination for alertID
    #
    # PARAMETERS: 
    #
    # alertID
    # 
    # ==============================================================================================
    
    ####
    ####
    # Start Ops Mgr snapin, get Alert ID
    ###
    
    $rootMS = 'localhost'
    
    #Initializing the Ops Mgr 2007 Powershell provider
    Add-PSSnapin "Microsoft.EnterpriseManagement.OperationsManager.Client" -ErrorVariable errSnapin ;
    Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin ;
    new-managementGroupConnection -ConnectionString:$rootMS -ErrorVariable errSnapin ;
    Set-Location $rootMS -ErrorVariable errSnapin ;
     
    $sAlertID = $args[0].substring(1,$args[0].Length-2)
    $oAlert = Get-Alert | where {$_.Id -eq $sAlertID}
    $sAlertID
    $oAlert.ID
    
    $sOrigin = 'SERVERNAME'
    $sCommunity = 'sc2'
    
    $sDestinations = 'x.x.x.x'
    $aDestinations = $sDestinations.Split(",")
    
    $sAlertURL = ''
    
    $sMessage = 'TrapGeneratorFromAlertID.ps1: ran succesfully. It generated SNMP traps with the following data: '
    
    ForEach ($sDestination in $aDestinations)
    {
    	$sCommand = 'C:\OpsMgrScripts\TrapGenerator\mposter.exe'
    	$sFilePath = "C:\OpsMgrScripts\TrapGenerator\mposter" + $sAlertID + "." + $sDestination + ".txt"
    
    	'omRedCriticalErrorAlert;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    
    	If ($oAlert.Severity -eq "Warning")
    	{
    		'omAlertLevel=30;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    		'omAlertLevelName=Warning;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	}
    	Else
    	{
    		'omAlertLevel=30;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    		'omAlertLevelName=Error;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	}
    
    	'omServer="' + $oAlert.NetbiosDomainName + '\\' + $oAlert.NetbiosComputerName + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'hostname="' + $oAlert.NetbiosDomainName + '\\' + $oAlert.NetbiosComputerName + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omSource="' + $oAlert.Name + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omOwner="SCOM ' + $oAlert.Owner + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omDescription="' + $oAlert.MonitoringObjectFullName + ': ' + $oAlert.Description + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField1="' + $oAlert.CustomField1 + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField2="' + $oAlert.CustomField2 + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField3="' + $oAlert.CustomField3 + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField4="' + $oAlert.CustomField4 + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField5="' + $oAlert.CustomField5 + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omAlertURL="' + $sAlertURL + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectFullName="' + $oAlert.MonitoringObjectFullName + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectId="' + $oAlert.MonitoringObjectId + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectClassId="' + $oAlert.MonitoringClassId + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectDisplayName="' + $oAlert.MonitoringObjectDisplayName + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectPath="' + $oAlert.MonitoringObjecPath + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'Priority="' + $oAlert.Priority + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'END' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    
    	$sCommandParameters = '-f c:\OpsMgrScripts\TrapGenerator\mcell.dir ' + '-n snmp ' + $sFilePath
    	$sFileContent = Get-Content $sFilePath
    	$sMessage = $sMessage + $sFileContent + "`n" + "`n"
    	
    	$ProcTrap = [System.Diagnostics.Process]::Start($sCommand,$sCommandParameters)
      $ProcTrap.WaitForExit();
    	Remove-Item $sFilePath
    }
    
    #$oAlert.ResolutionState = 0
    #$oAlert.Update("")
    
    ###
    # Write a successfull run event to the eventlog
    ###
    $oLog = New-Object System.Diagnostics.EventLog 
    $oLog.Set_Log("Operations Manager") 
    $oLog.Set_Source("Health Service Script")
    $oLog.WriteEntry($sMessage,"Information",99) 
    
    
    
    
    ###
    # Remove the Ops Mgr PSSnapin
    ###
    
    Remove-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client
    

    -------------------------------------------------------------------

    Create a new Subscription, select the criteria and etc, for the channels, used the one created above.

    Create a new Subscriber, as addresses chosse new, Channel Type : Command, Command Chanel : the channel created above


    If you need more details, don't hesitate.

    • Proposed as answer by Christopher Keyaert Tuesday, June 1, 2010 12:31 PM
    • Marked as answer by Yog Li Friday, June 4, 2010 8:39 AM
    Tuesday, June 1, 2010 12:27 PM
  • I'm interested in implementing this as a temporary "connector" to CA Spectrum.  This seems like the easiest, quickest way to forward Alerts from SCOM to Spectrum until we upgrade Spectrum to the newer version that has a builtin SCOM Connector.  The issue is that i've always been advised to use the Command Notification channel sparingly since it will need to launch a separate instance of the .exe or script for every Alert that meets the subscription.  I would like to know what experience people have had with this if anyand did they see significant performance issues/problems, etc.  Again we would like to use this for a 3-6 month period to only forward AD MP Alerts and Windows OS Alerts.  Is this just a definitely no no or is this a viable temporary solution?
    Marc Schmieder

    Hello Marc,

     

    I'm currently using a snmp trap system for forwarding Alert from SCOM to BMC Remedy.
    Monday morning, I will send you all the details.

    • Proposed as answer by Christopher Keyaert Tuesday, June 1, 2010 12:14 PM
    • Marked as answer by Yog Li Friday, June 4, 2010 8:39 AM
    Sunday, May 30, 2010 11:34 AM

All replies

  • hi, it is all about no of alerts you get today that needs to be forwarded. Have you looked into that with the alert report? I have done solutions like that without seeing a big performance issue. The extra command prompt is open a very short time when the alert is forwarded.
    Anders Bengtsson | Microsoft MVP - Operations Manager | http://www.contoso.se
    Thursday, May 13, 2010 1:53 PM
  • Hi Anders,

    This is a new implementation and we have yet to implement any Managment Packs.  We are planning on doing AD and Windows Base OS and then we will hopefully have Spectrum upgraded to the new version in order to use the integrated CA SCOM connector. So at the moment I can't say the amount of Alert we will have.  How have you done this in the past?  How are you passing the Alert data to the SNMP trap generator?  We have initially tried using netsnmp's snmptrap.exe but we are having issues passing the Alert name, source, description, to the command line in the notification and we are not sure why.  What trap generator have you used in the past?

     

    Thanks


    Marc Schmieder
    Thursday, May 13, 2010 2:45 PM
  • Also what Alert field did you key off of in order to send the data to the other monitoring tool?  Alert Source (This changes depending on where the Alert comes from), Path seems to contain the machine name most of the time but I can't find an Alert property that matches up with this so I don't think I can use this in the Command Channel.  Thoughts?
    Marc Schmieder
    Thursday, May 13, 2010 5:02 PM
  • Hello does anyone have an answer to this?:

     

    What Alert field(s) can you key off of in order to send the data to another monitoring tool?  Alert Source and Path properties seem to change depending on where the Alert comes from and is not always the machine name.  I seem to find an Alert property that is consistent and we can use to forward Alerts.  Has anyone figured out how to do this by using a internal connector to update a field on the Alert ,etc?


    Marc Schmieder
    Monday, May 17, 2010 5:24 PM
  • I'm interested in implementing this as a temporary "connector" to CA Spectrum.  This seems like the easiest, quickest way to forward Alerts from SCOM to Spectrum until we upgrade Spectrum to the newer version that has a builtin SCOM Connector.  The issue is that i've always been advised to use the Command Notification channel sparingly since it will need to launch a separate instance of the .exe or script for every Alert that meets the subscription.  I would like to know what experience people have had with this if anyand did they see significant performance issues/problems, etc.  Again we would like to use this for a 3-6 month period to only forward AD MP Alerts and Windows OS Alerts.  Is this just a definitely no no or is this a viable temporary solution?
    Marc Schmieder

    Hello Marc,

     

    I'm currently using a snmp trap system for forwarding Alert from SCOM to BMC Remedy.
    Monday morning, I will send you all the details.

    • Proposed as answer by Christopher Keyaert Tuesday, June 1, 2010 12:14 PM
    • Marked as answer by Yog Li Friday, June 4, 2010 8:39 AM
    Sunday, May 30, 2010 11:34 AM
    1. Create a new notification channel
    • Full Path of the command line : C:\WINDOWS\System32\windowspowershell\v1.0\PowerShell.exe
    • Command line parameters : C:\OpsMgrScripts\TrapGenerator\mposter.ps1 '$Data/Context/DataItem/AlertId$'
    • Startup folder for the command line : C:\OpsMgrScripts\TrapGenerator

    Content of mpposter.ps1 (The mpposter.exe must be in the folder C:\OpsMgrScripts\TrapGenerator\mposter.exe)
    -------------------------------------------------------

     ==============================================================================================
    # 
    # Microsoft PowerShell Source File
    # 
    # NAME: mposter.ps1
    # 
    # 
    # COMMENT: This script will generate an SNMP trap to a given destination for alertID
    #
    # PARAMETERS: 
    #
    # alertID
    # 
    # ==============================================================================================
    
    ####
    ####
    # Start Ops Mgr snapin, get Alert ID
    ###
    
    $rootMS = 'localhost'
    
    #Initializing the Ops Mgr 2007 Powershell provider
    Add-PSSnapin "Microsoft.EnterpriseManagement.OperationsManager.Client" -ErrorVariable errSnapin ;
    Set-Location "OperationsManagerMonitoring::" -ErrorVariable errSnapin ;
    new-managementGroupConnection -ConnectionString:$rootMS -ErrorVariable errSnapin ;
    Set-Location $rootMS -ErrorVariable errSnapin ;
     
    $sAlertID = $args[0].substring(1,$args[0].Length-2)
    $oAlert = Get-Alert | where {$_.Id -eq $sAlertID}
    $sAlertID
    $oAlert.ID
    
    $sOrigin = 'SERVERNAME'
    $sCommunity = 'sc2'
    
    $sDestinations = 'x.x.x.x'
    $aDestinations = $sDestinations.Split(",")
    
    $sAlertURL = ''
    
    $sMessage = 'TrapGeneratorFromAlertID.ps1: ran succesfully. It generated SNMP traps with the following data: '
    
    ForEach ($sDestination in $aDestinations)
    {
    	$sCommand = 'C:\OpsMgrScripts\TrapGenerator\mposter.exe'
    	$sFilePath = "C:\OpsMgrScripts\TrapGenerator\mposter" + $sAlertID + "." + $sDestination + ".txt"
    
    	'omRedCriticalErrorAlert;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    
    	If ($oAlert.Severity -eq "Warning")
    	{
    		'omAlertLevel=30;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    		'omAlertLevelName=Warning;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	}
    	Else
    	{
    		'omAlertLevel=30;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    		'omAlertLevelName=Error;' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	}
    
    	'omServer="' + $oAlert.NetbiosDomainName + '\\' + $oAlert.NetbiosComputerName + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'hostname="' + $oAlert.NetbiosDomainName + '\\' + $oAlert.NetbiosComputerName + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omSource="' + $oAlert.Name + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omOwner="SCOM ' + $oAlert.Owner + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omDescription="' + $oAlert.MonitoringObjectFullName + ': ' + $oAlert.Description + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField1="' + $oAlert.CustomField1 + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField2="' + $oAlert.CustomField2 + '";'| Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField3="' + $oAlert.CustomField3 + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField4="' + $oAlert.CustomField4 + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omCustomField5="' + $oAlert.CustomField5 + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'omAlertURL="' + $sAlertURL + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectFullName="' + $oAlert.MonitoringObjectFullName + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectId="' + $oAlert.MonitoringObjectId + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectClassId="' + $oAlert.MonitoringClassId + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectDisplayName="' + $oAlert.MonitoringObjectDisplayName + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'ObjectPath="' + $oAlert.MonitoringObjecPath + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'Priority="' + $oAlert.Priority + '";' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    	'END' | Out-File -filepath $sFilePath -append -noClobber -encoding ASCII
    
    	$sCommandParameters = '-f c:\OpsMgrScripts\TrapGenerator\mcell.dir ' + '-n snmp ' + $sFilePath
    	$sFileContent = Get-Content $sFilePath
    	$sMessage = $sMessage + $sFileContent + "`n" + "`n"
    	
    	$ProcTrap = [System.Diagnostics.Process]::Start($sCommand,$sCommandParameters)
      $ProcTrap.WaitForExit();
    	Remove-Item $sFilePath
    }
    
    #$oAlert.ResolutionState = 0
    #$oAlert.Update("")
    
    ###
    # Write a successfull run event to the eventlog
    ###
    $oLog = New-Object System.Diagnostics.EventLog 
    $oLog.Set_Log("Operations Manager") 
    $oLog.Set_Source("Health Service Script")
    $oLog.WriteEntry($sMessage,"Information",99) 
    
    
    
    
    ###
    # Remove the Ops Mgr PSSnapin
    ###
    
    Remove-PSSnapin Microsoft.EnterpriseManagement.OperationsManager.Client
    

    -------------------------------------------------------------------

    Create a new Subscription, select the criteria and etc, for the channels, used the one created above.

    Create a new Subscriber, as addresses chosse new, Channel Type : Command, Command Chanel : the channel created above


    If you need more details, don't hesitate.

    • Proposed as answer by Christopher Keyaert Tuesday, June 1, 2010 12:31 PM
    • Marked as answer by Yog Li Friday, June 4, 2010 8:39 AM
    Tuesday, June 1, 2010 12:27 PM
  • Hello Christopher Keyaert,

    Where can I get the executable 'MPOSTER.EXE" to use as my trap generator along with your powershell script? Please advise.

    Thanks!

    Brian

     

    Wednesday, June 30, 2010 4:41 PM
  • Hey

    I've got Scom connected to Spectrum , we using trapgen ... works well .... some subscriptions dont fire off though .. apparently its something u need to accept. We using Spectrum 9.12 ... what version has the built in connector ? ver 10 ?

    I haven't noticed much performance degredation.

    The Spectrum guy here had to build a custom MIB on the spectrum side to interpret the traps coming from SCOM.

    Ryan

    Friday, July 16, 2010 6:54 AM
  • Hello Brian,

     

    So for the delay of my answer. I uploaded it at ovh (Available for 5 days only :( )

    http://demo.ovh.com/en/b5fc332b8052d82810ce5ec7d9d8555d/

     

    Christopher


    Christopher Keyaert - My OpsMgr/SCOM blog : http://www.vnext.be
    Friday, July 16, 2010 7:58 AM
  • I'm interested in implementing this as a temporary "connector" to CA Spectrum.  This seems like the easiest, quickest way to forward Alerts from SCOM to Spectrum until we upgrade Spectrum to the newer version that has a builtin SCOM Connector.  The issue is that i've always been advised to use the Command Notification channel sparingly since it will need to launch a separate instance of the .exe or script for every Alert that meets the subscription.  I would like to know what experience people have had with this if anyand did they see significant performance issues/problems, etc.  Again we would like to use this for a 3-6 month period to only forward AD MP Alerts and Windows OS Alerts.  Is this just a definitely no no or is this a viable temporary solution?
    Marc Schmieder

    Hello Marc,

     

    I'm currently using a snmp trap system for forwarding Alert from SCOM to BMC Remedy.
    Monday morning, I will send you all the details.


    Hello Christopher

    I am new to this forum and I have a similar request:

    We need to generate SNMP traps every time an Alert is created OR cleared in SCOM 2007 R2.

    We use these traps to be open or close incidents in a ticketing system.

    We are currently looking at some scripts / tools we downloaded from François, but it seems to only deal with generating traps when an Alarm is created, not cleared.

    Can you assist me? Perhaps send me the "system, details, etc" you used for the same purpose with BMC Remedy??

    Tx

    Christo

    Wednesday, August 4, 2010 2:23 PM
  • Hey

    I've got Scom connected to Spectrum , we using trapgen ... works well .... some subscriptions dont fire off though .. apparently its something u need to accept. We using Spectrum 9.12 ... what version has the built in connector ? ver 10 ?

    I haven't noticed much performance degredation.

    The Spectrum guy here had to build a custom MIB on the spectrum side to interpret the traps coming from SCOM.

    Ryan


    Hi Ryan

    Besides the sporadic problem of the subscriptions that does not "fire off", are you happy with this integration making use of TRAPGEN?

    How did you manage to get the "repair" event in SCOM to send a trap to Spectrum (making use of TRAPGEN)? At this stage all we get in Spectrum is the Trap related to the Alert that was created in SCOM but no repair message is created when the Alert is resolved/closed in SCOM..?

     

    Any ideas?

    Thanks

    CC

    Friday, August 6, 2010 11:32 AM
  • Hi Christian

    Other than the subscriptions , I'm impressed with TrapGen, we have had no problems with the SNMP forwarding.

    There are quite a few parameters that SCOM has that you can use to pass on to the SNMP MIB on the Spectrum side ..... u just need to create a MIB to interpret the passed on parameters.

    Here is our cmd line channel line:

    "$Data/Context/DataItem/ResolutionStateName$" - is the one that passes on the "Closed" parameter.

     
    /c D:\trapgen\trapgen.pl "$Data/Context/DataItem/ManagedEntityPath$" "$Data/Context/DataItem/AlertName$" "$Data/Context/DataItem/TimeRaisedLocal$" "$Target/Property[Type="Notification!Microsoft.SystemCenter.AlertNotificationSubscriptionServer"]/WebConsoleUrl$?DisplayMode=Pivot&AlertID=$Data/Context/DataItem/AlertId$" "$Data/Context/DataItem/Severity$" "$Data/Context/DataItem/AlertId$" "$Data/Context/DataItem/ResolutionStateName$" "mp_name" "$Data/Context/DataItem/Category$" "$Data/Context/DataItem/CreatedByMonitor$" "$Data/Context/DataItem/CreatedByMonitor$" "$Data/Context/DataItem/AlertDescription$"

    Hope this helps .... I didnt create the MIB , our SNMP guy at work did....I just did the SCOM side of things.

    Good Luck Christian!

    Ryan

     

    Friday, August 6, 2010 12:33 PM
  • Dear All,

    where is this mposter.exe file located.

    Regards,

    Wednesday, August 18, 2010 10:25 AM
  • Thanks a mil for a brilliant article. Just missing the mpposter executable. Would you be so kind as to mail this to me, or give me a download link?

     

    Wednesday, December 29, 2010 11:20 AM
  • I am looking for that mposter executable as well if someone can send it to me.  Great thread.  We'd like to setup our SCOM environment to forward alerts to our CA NSM formerly TNG I beleive.
    Tuesday, May 10, 2011 4:45 PM
  • http://demo.ovh.com/en/0eddf4b4aaebf08bcf343959efd60028/
    Your files will be available for: 3 days, 23 hours, 59 minutes

    Now, if System Center Opalis 6.3 is included in your Microsoft Licence Contract, it's really powershell for SCOM and third party software integration.


    Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be
    Wednesday, May 11, 2011 6:37 AM
  • Hello Chris, it seems like your solution would help me very much.

    The TRAP generator that you are using is named mposter.exe right? where can i get it? could you help me out with that?

    Wednesday, June 1, 2011 5:17 PM
  • Hi Christopher

    Can you please upload you mposter.exe TRAP generator or advice where can I get it

    Thanks in advance

     

     

     


    Kind Regards Tim (Canberra)
    Thursday, June 9, 2011 1:05 AM
  • Hi Christoher,

    We are moving from MOM 2005 SP1 to SCOM 2007 R2. Right now MOM agents forwards the alerts to HP OV NNM 7.5 as snmp trap.

    So in SCOM, we need to forward the alerts to NNM. Could you please upload your MPoster.exe, so that i can try forwarding the alerts to NNM from SCOM.

    Regards

    Paul

     

     

     

     

    Wednesday, June 22, 2011 8:23 PM
  • yes! please Chris! please upload mposter.exe have mercy on us, the non-coder mortals :D
    Wednesday, June 22, 2011 8:29 PM
  • Hi,

    I uploaded the mposter file : http://temp.leveilleur.net/mposter.zip
    The password is : mposter

    If you have the licence for all the Microsoft System center products, I advice you to go to System Center Opalis (new name will be Orchestrator) for the connection between SCOM and others products.

     Opalis is really more powerfull, easier and flexible than a powershell script + mposter.

     

    Christopher


    Christopher Keyaert - My OpsMgr / SCOM & Opalis blog : http://www.vnext.be
    Thursday, June 23, 2011 4:11 AM
  • Thanks Chris,

    -Paul

     

    Thursday, June 23, 2011 2:58 PM
  • Hi,

    what about the "MPOSTER.EXE" file? Does anyone use another method to forward alerts from SCOM to Spectrum?

    What’s your experience with this?

    What will be the best way to do so? Here are some solutions I found: (Which one is the best?)

    1.    Quest Management Connector (QMC)

    2.    SCOM to Spectrum connector from CA

    3.    MPOSTER.EXE aka “mposter.ps1”

    kind regards,

    Rico

    Saturday, November 5, 2011 9:10 AM
  • Chris,

    Can the above PS Script be used to forward SNMP traps to Smarts also?

     

    If the above has to be done by Opalis, is there a step-by-step reference for the same?

    Monday, December 12, 2011 3:13 PM
  • This screen just sends snmp trap, so bassically, that's compatible with everything that is able to receive snmp trap.

     

    Concerning Opalis, it's quite simple, you could acheive that by using the "Monitoring Alert" and the "Send SNMP trap" activities.
    I don't have a step by step for your requirements, but the following posts could show you some basic concept of Opalis.

    http://scug.be/blogs/christopher/archive/2011/06/17/system-center-opalis-monitor-snmp-trap-activity.aspx 


    If your company has a license agreement with Microsoft, you really have to take a look to Opalis/Orchestrator. 

     


    Christopher Keyaert - My OpsMgr/SCOM & Opalis/Orchestrator blog : http://scug.be/blogs/christopher
    Monday, December 12, 2011 3:27 PM
  • Where can we get MPOSTER.EXE? Is this available for download somewhere?
    Tuesday, December 13, 2011 3:46 PM
  • I uploaded here :

    http://www.2shared.com/file/Mp9-ZnOC/mposter.html

     


    Christopher Keyaert - My OpsMgr/SCOM & Opalis/Orchestrator blog : http://scug.be/blogs/christopher
    Tuesday, December 13, 2011 3:53 PM
  • Hi Keyaert,

    I am trying to send alert notification from SCOM 2012 R2 to Nagios. Can i use this script to send it to Nagios also.

    And I cannot download the mposter.exe from your link can you send it again ,please.

    Friday, April 29, 2016 10:29 AM