Modifying SNMP Devices to show Device Name in SCOM
How can I modify SNMP devices to show up in SCOM as the device name not just the IP address, and how do I include that in the device description? Paul Arbogast
April 25th, 2011 2:51pm

I found this script to put for the alert description $Target/Property[Type="MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice"]/Name$ but i get this alert Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run. : Verification failed with [1] errors: ------------------------------------------------------- Error 1: : Verification failed for rule: MomUIGeneratedRulea98710db03f9458987b87334a65b548b Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] ------------------------------------------------------- Verification failed for rule: MomUIGeneratedRulea98710db03f9458987b87334a65b548b Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] : Verification failed for rule: MomUIGeneratedRulea98710db03f9458987b87334a65b548b Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] : Failed to verify referenced module : ID=Alert Invalid configuration specified for Module [Alert]Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] : Invalid configuration specified for Module [Alert] Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] : Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] Paul Arbogast
Free Windows Admin Tool Kit Click here and download it now
April 25th, 2011 4:46pm

I found this script to put for the alert description $Target/Property[Type="MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice"]/Name$ but i get this alert Note: The following information was gathered when the operation was attempted. The information may appear cryptic but provides context for the error. The application will continue to run. : Verification failed with [1] errors: ------------------------------------------------------- Error 1: : Verification failed for rule: MomUIGeneratedRulea98710db03f9458987b87334a65b548b Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] ------------------------------------------------------- Verification failed for rule: MomUIGeneratedRulea98710db03f9458987b87334a65b548b Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] : Verification failed for rule: MomUIGeneratedRulea98710db03f9458987b87334a65b548b Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] : Failed to verify referenced module : ID=Alert Invalid configuration specified for Module [Alert]Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] : Invalid configuration specified for Module [Alert] Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] : Cannot resolve identifier [MicrosoftSystemCenterNetworkDeviceLibrary6050000!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [SNMP.Linux]. Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] Paul Arbogast
April 25th, 2011 4:46pm

What this means is that the reference you used in your substitution variable $target$ is not understood in the context of the MP you stuck it in. The specifics: This reference which looks to be copied from some other customers sample (will never work for you without making it match your env) Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] The MP that it looks like you changed directly (??? probably not a good idea ???) SNMP.Linux You need to use the alias that makes sense for the MP that you are trying to modify. Look at the available aliases in the MP you are trying to change, and use one of those that refer to the library containing Microsoft.SystemCenter.NetworkDevice If you are directly changing one of crossplat files (SMMP.Linux) this is probably a bad bad bad idea. Microsoft Corporation
Free Windows Admin Tool Kit Click here and download it now
April 25th, 2011 5:25pm

What this means is that the reference you used in your substitution variable $target$ is not understood in the context of the MP you stuck it in. The specifics: This reference which looks to be copied from some other customers sample (will never work for you without making it match your env) Unknown alias [MicrosoftSystemCenterNetworkDeviceLibrary6050000] The MP that it looks like you changed directly (??? probably not a good idea ???) SNMP.Linux You need to use the alias that makes sense for the MP that you are trying to modify. Look at the available aliases in the MP you are trying to change, and use one of those that refer to the library containing Microsoft.SystemCenter.NetworkDevice If you are directly changing one of crossplat files (SMMP.Linux) this is probably a bad bad bad idea. Microsoft Corporation
April 25th, 2011 5:25pm

Hi Paul, I think this was the same reference you added to the MP a week ago. It uses a different name and version in your case. I think you had this reference: MicrosoftSystemCenterNetworkDeviceLibrary6172210 Bob Cornelissen - BICTT (My BICTT Blog)
Free Windows Admin Tool Kit Click here and download it now
April 26th, 2011 2:02am

Hi, I just noticed the device name is inclueded in the alert description of this management pack. If you are authroing a management pack to achieve this, please also refer to it and see if it is helpful: Customizing monitor from sealed MP ("Device Status Check"). http://blogs.msdn.com/b/mariussutara/archive/2008/07/18/customizing-monitor-from-sealed-mp-device-status-check.aspx Hope this can give you some hints. Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 27th, 2011 6:02am

I just decided to scrap what I was doing with it, and start from scratch. Here is the problem I currently have. When an alert is generated I would like to see the Device Name or Device Description in the error as well as the error itself. What I get is blank though all it says is Event Description,, but does not give me any details of the event. When I look in the Alert Context I see all the information I'm looking for. How can I display this in the Alert Description?Paul Arbogast
Free Windows Admin Tool Kit Click here and download it now
April 27th, 2011 9:30am

Hi, Please see the following in the example: <AlertParameter1>$Target/Property[Type="NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice"]/Name$</AlertParameter1> Thanks. Nicholas Li - MSFT Please remember to click Mark as Answer on the post that helps you, and to click Unmark as Answer if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
April 27th, 2011 11:48pm

No unfortunatly that did not work either, I have recently rebuilt the environment, and everything is default, I have no custom management packs, this is the alarm I get trying the text you gave me. Date: 4/29/2011 12:22:24 PM Application: System Center Operations Manager 2007 R2 Application Version: 6.1.7221.0 Severity: Error Message: : Verification failed with [1] errors: ------------------------------------------------------- Error 1: : Verification failed for rule: MomUIGeneratedRule4ab97529bfd34483b87cd0948367d634 Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [Microsoft.SystemCenter.OperationsManager.DefaultUser]. Unknown alias [NetworkDeviceLibrary] ------------------------------------------------------- Verification failed for rule: MomUIGeneratedRule4ab97529bfd34483b87cd0948367d634 Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [Microsoft.SystemCenter.OperationsManager.DefaultUser]. Unknown alias [NetworkDeviceLibrary] : Verification failed for rule: MomUIGeneratedRule4ab97529bfd34483b87cd0948367d634 Failed to verify referenced module : ID=AlertInvalid configuration specified for Module [Alert]Cannot resolve identifier [NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [Microsoft.SystemCenter.OperationsManager.DefaultUser]. Unknown alias [NetworkDeviceLibrary] : Failed to verify referenced module : ID=Alert Invalid configuration specified for Module [Alert]Cannot resolve identifier [NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [Microsoft.SystemCenter.OperationsManager.DefaultUser]. Unknown alias [NetworkDeviceLibrary] : Invalid configuration specified for Module [Alert] Cannot resolve identifier [NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [Microsoft.SystemCenter.OperationsManager.DefaultUser]. Unknown alias [NetworkDeviceLibrary] : Cannot resolve identifier [NetworkDeviceLibrary!Microsoft.SystemCenter.NetworkDevice] in the context of ManagementPack [Microsoft.SystemCenter.OperationsManager.DefaultUser]. Unknown alias [NetworkDeviceLibrary] Paul Arbogast
Free Windows Admin Tool Kit Click here and download it now
April 29th, 2011 12:26pm

Hi Paul, Looks like this MP is missing a reference to a management pack called "NetworkDeviceLibrary". Check in the xml the references near the top of the management apck. See if you can find one with this alias name. It should point to the network device library management pack. Do the same as last time except this time use this alias to point to that mp (same of the previous time only this time the alias used has changed).Bob Cornelissen - BICTT (My BICTT Blog)
April 29th, 2011 2:08pm

Hi Parbogast, In terms of being able to view the Name or Description of an SNMP Network Device object in the SCOM Console have you tried Personalizing the default view for the Network Devices Group by right-clicking on the column headings and selecting the Personalize option. This should expose additional properties of SNMP Network Devices such as the Device Name, Display Name and Description. Please take also take a look at the list of alert variables compiled by Kevin Holman at the link below: http://blogs.technet.com/b/kevinholman/archive/2007/12/12/adding-custom-information-to-alert-descriptions-and-notifications.aspx In particular, for what you are trying to achieve the section named Notifications should, I believe, contain the parameter/alert variable that you need. From my experience trying to do something similar I believe the one you want will be one of the following: Alert Variable Value $Data/Context/DataItem/ManagedEntityDisplayName$ ManagedEntity Display name $Data/Context/DataItem/ManagedEntityFullName$ ManagedEntity Full name $Data/Context/DataItem/ManagedEntityPath$ Managed Entity Path Try using all three of the above (including the Value explanation text) in a custom email channel and configure the SNMP Device Alerts for your custom rule/monitor or even for the SNMP Network Device Status Check monitor to use that channel then force an appropriate alert. Then when you get the email you should be able to see exactly the values each returns in order to take the guesswork out of finding-out which is the most suitable for your needs. Then reset the email channel used by the alerts back to your originally defined email channel but this time update its message format to include the one alert variable you want. Then do the same for the equivalent SMS channel by simply adding the desired alert parameter in the message format portion of the Channel. The only gotcha there being the character limit that is enforced by the SMS format. Best of luck, Michael
Free Windows Admin Tool Kit Click here and download it now
May 4th, 2011 10:42am

Hi Parbogast, In terms of being able to view the Name or Description of an SNMP Network Device object in the SCOM Console have you tried Personalizing the default view for the Network Devices Group by right-clicking on the column headings and selecting the Personalize option. This should expose additional properties of SNMP Network Devices such as the Device Name, Display Name and Description. Please take also take a look at the list of alert variables compiled by Kevin Holman at the link below: http://blogs.technet.com/b/kevinholman/archive/2007/12/12/adding-custom-information-to-alert-descriptions-and-notifications.aspx In particular, for what you are trying to achieve the section named Notifications should, I believe, contain the parameter/alert variable that you need. From my experience trying to do something similar I believe the one you want will be one of the following: Alert Variable Value $Data/Context/DataItem/ManagedEntityDisplayName$ ManagedEntity Display name $Data/Context/DataItem/ManagedEntityFullName$ ManagedEntity Full name $Data/Context/DataItem/ManagedEntityPath$ Managed Entity Path Try using all three of the above (including the Value explanation text) in a custom email channel and configure the SNMP Device Alerts for your custom rule/monitor or even for the SNMP Network Device Status Check monitor to use that channel then force an appropriate alert. Then when you get the email you should be able to see exactly the values each returns in order to take the guesswork out of finding-out which is the most suitable for your needs. Then reset the email channel used by the alerts back to your originally defined email channel but this time update its message format to include the one alert variable you want. Then do the same for the equivalent SMS channel by simply adding the desired alert parameter in the message format portion of the Channel. The only gotcha there being the character limit that is enforced by the SMS format. Best of luck, Michael
May 4th, 2011 10:42am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics