We are trying out new SCOM 2012 and using its network monitoring capabilities. We like it that its easy to configure and it works as it suppose to.. at least for what we needed to monitor. However we are running into issues with alerts it generates. Alerts only displays interface number and MAC address of router we are monitoring. Since SCOM has general information about device name and location and port description it would be nice to have that information as part of the alert. xSNMP did great job with that on SCOM 2007. I have attached screen shot from SCOM 2012.

check if your device are into this list: http://www.microsoft.com/download/en/details.aspx?id=26831 if is not here, is normal don't see all the information. SS.Net Inside Technologies MVP System Center Cloud and Datacenter Management MCITP Enterprise Administrator MCTS Server Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

check if your device are into this list: http://www.microsoft.com/download/en/details.aspx?id=26831 if is not here, is normal don't see all the information. SS.Net Inside Technologies MVP System Center Cloud and Datacenter Management MCITP Enterprise Administrator MCTS Server Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

check if your device are into this list: http://www.microsoft.com/download/en/details.aspx?id=26831 if is not here, is normal don't see all the information. SS.Net Inside Technologies MVP System Center Cloud and Datacenter Management MCITP Enterprise Administrator MCTS Server Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

We are trying to monitor Netscreen SSG20.

in Router section there's the device? are you sure that there aren't the standard information? sometimes all the devices, with snmp, can comunicate with SCOM in order to send the classic data but not all devices can be monitored with OM2012. SS.Net Inside Technologies MVP System Center Cloud and Datacenter Management MCITP Enterprise Administrator MCTS Server Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

in Router section there's the device? are you sure that there aren't the standard information? sometimes all the devices, with snmp, can comunicate with SCOM in order to send the classic data but not all devices can be monitored with OM2012. SS.Net Inside Technologies MVP System Center Cloud and Datacenter Management MCITP Enterprise Administrator MCTS Server Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

in Router section there's the device? are you sure that there aren't the standard information? sometimes all the devices, with snmp, can comunicate with SCOM in order to send the classic data but not all devices can be monitored with OM2012. SS.Net Inside Technologies MVP System Center Cloud and Datacenter Management MCITP Enterprise Administrator MCTS Server Virtualization - Operations Manager 2007 - Exchange Server 2007 - MCSE-M S.Net Blog WindowServer.it WindowServer.it Learning Portal

I have attached screen shot from SCOM 2012 Router view. I have removed SNMP Agent Address and external ip address in Display name.

I have attached screen shot from SCOM 2012 Router view. I have removed SNMP Agent Address and external ip address in Display name.

I have attached screen shot from SCOM 2012 Router view. I have removed SNMP Agent Address and external ip address in Display name.

whether scom alert has device name and location is up to the context of alert description. You can create a custom monitor using Target--> device name/ Target --> device location as an alert description. Roger

whether scom alert has device name and location is up to the context of alert description. You can create a custom monitor using Target--> device name/ Target --> device location as an alert description. Roger

whether scom alert has device name and location is up to the context of alert description. You can create a custom monitor using Target--> device name/ Target --> device location as an alert description. Roger

This is a basic information that should be provided with monitoring any device. This is like saying we have 911 call without the address. I hope that SCOM team updates the management pack otherwise all their hard work in network monitoring goes down in drain if people are having to create custom monitors/rules just to get basic info about the alert.

This is a basic information that should be provided with monitoring any device. This is like saying we have 911 call without the address. I hope that SCOM team updates the management pack otherwise all their hard work in network monitoring goes down in drain if people are having to create custom monitors/rules just to get basic info about the alert.

This is a basic information that should be provided with monitoring any device. This is like saying we have 911 call without the address. I hope that SCOM team updates the management pack otherwise all their hard work in network monitoring goes down in drain if people are having to create custom monitors/rules just to get basic info about the alert.

Sadly your observations are correct - I have a number of enhancement requests around this already on connect. For instance, if you look at the Interface and port usage performance charts and reports they show the MAC aaddress and port number for charting which isn't the most useful of information to display. The name of the device would be far more useful. Regards GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Sadly your observations are correct - I have a number of enhancement requests around this already on connect. For instance, if you look at the Interface and port usage performance charts and reports they show the MAC aaddress and port number for charting which isn't the most useful of information to display. The name of the device would be far more useful. Regards GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

Sadly your observations are correct - I have a number of enhancement requests around this already on connect. For instance, if you look at the Interface and port usage performance charts and reports they show the MAC aaddress and port number for charting which isn't the most useful of information to display. The name of the device would be far more useful. Regards GrahamRegards Graham New System Center 2012 Blog! - http://www.systemcentersolutions.co.uk View OpsMgr tips and tricks at http://systemcentersolutions.wordpress.com/

I have resolved part of my issue. Display name and full path name is now same as MIB2 System Name. Apparently Display name and Full path name is pulled from DNS. So i was about to resolve part of my issue with just deleting the device from SCOM. creating DNS A record and re-discovering the device. but still when it comes to alert.. it shows MAC address as part of Path instead of display name or MIB2 Displayname.

I have created a Performance view over a couple of interfaces, do you have an ide how to get the MIB2 name is that view? How can I add it?

I have created a Performance view over a couple of interfaces, do you have an ide how to get the MIB2 name is that view? How can I add it?

I have created a Performance view over a couple of interfaces, do you have an ide how to get the MIB2 name is that view? How can I add it?

By default, you can not change fields that are displayed in the performance view. Only way to get around is to create your own MP with performance view. We are using free xSNMP MP to monitor network devices with SCOM 2007 R2. I personally think this is a Microsoft issue. They need to fix this. MAC address is useless when looking at network device related information. They need to use either DNS name or MIB2 name. Hope this helps.

By default, you can not change fields that are displayed in the performance view. Only way to get around is to create your own MP with performance view. We are using free xSNMP MP to monitor network devices with SCOM 2007 R2. I personally think this is a Microsoft issue. They need to fix this. MAC address is useless when looking at network device related information. They need to use either DNS name or MIB2 name. Hope this helps.

By default, you can not change fields that are displayed in the performance view. Only way to get around is to create your own MP with performance view. We are using free xSNMP MP to monitor network devices with SCOM 2007 R2. I personally think this is a Microsoft issue. They need to fix this. MAC address is useless when looking at network device related information. They need to use either DNS name or MIB2 name. Hope this helps.

This has been noted since beta version. Mr. K. Bash needs to work overtime and get this one resolved. :D I will just use OpsLogix ping alerts which does give me DNS names perfectly fine and worry about more in-depth monitoring when they fix this. My guys don't speak MAC Addresses.

This has been noted since beta version. Mr. K. Bash needs to work overtime and get this one resolved. :D I will just use OpsLogix ping alerts which does give me DNS names perfectly fine and worry about more in-depth monitoring when they fix this. My guys don't speak MAC Addresses.

This has been noted since beta version. Mr. K. Bash needs to work overtime and get this one resolved. :D I will just use OpsLogix ping alerts which does give me DNS names perfectly fine and worry about more in-depth monitoring when they fix this. My guys don't speak MAC Addresses.

Thanks for the replys. It is really annoying that this issue isnt fixed yet. Specially if this have been know since the beta. The network monitor is almost useless without correct naming on the views and alerts. Hopefully they will fix this soon.

Thanks for the replys. It is really annoying that this issue isnt fixed yet. Specially if this have been know since the beta. The network monitor is almost useless without correct naming on the views and alerts. Hopefully they will fix this soon.

Thanks for the replys. It is really annoying that this issue isnt fixed yet. Specially if this have been know since the beta. The network monitor is almost useless without correct naming on the views and alerts. Hopefully they will fix this soon.

Network Monitoring is half baked in 2012. :)

Network Monitoring is half baked in 2012. MS wants to charge me for a private hot fix. Basically, they're saying "pay us now" for a private fix or wait for OpsMgr 2012 SP1 release where "it will be fixed for certain.." Truly remarkable in my opinion for MS to demand money for a private fix instead of releasing it to the public :)

http://www.microsoft.com/en-us/download/details.aspx?id=29697

http://www.microsoft.com/en-us/download/details.aspx?id=29697

http://www.microsoft.com/en-us/download/details.aspx?id=29697

http://www.microsoft.com/en-us/download/details.aspx?id=29697 This is not SP1. There will be a Service Pack 1 with Network monitoring related fixes that people are obsessing over. I would post the email from my TAM but I would rather just keep it in my recycle bin. :)

I agree. If probing OID .1.3.6.1.1.5.0 gets a system name from an SNMP device, this should be very simple universal information to get apply to a data context and drop into into a notification channel. My problem is I don't know how I'd go about incorporating this information this way into SCOM myself yet :) If anyone has any ideas they'd be greatly appreciated.

one way to fix this issue is to create your own mp but authoring kit is not available yet or if you are good with visual studio you can use that also. There are several links out there that talks about creating basic snmp alerts. Also most of the 3rd party snmp based mp created for 2007 wont work with SCOM 2012 also because they changes in new SCOM. However if you have upgrade from scom 2007 to scom 2012 old mp will cont. to work for devices prior to upgrade but it will not monitor new devices. http://thoughtsonopsmgr.blogspot.co.uk/2011/10/snmp-oids-and-scom-lets-start-rocking.html http://michelkamp.wordpress.com/2012/07/02/how-to-check-if-a-snmp-trap-is-received/ Hope this help..

one way to fix this issue is to create your own mp but authoring kit is not available yet or if you are good with visual studio you can use that also. There are several links out there that talks about creating basic snmp alerts. Also most of the 3rd party snmp based mp created for 2007 wont work with SCOM 2012 also because they changes in new SCOM. However if you have upgrade from scom 2007 to scom 2012 old mp will cont. to work for devices prior to upgrade but it will not monitor new devices. http://thoughtsonopsmgr.blogspot.co.uk/2011/10/snmp-oids-and-scom-lets-start-rocking.html http://michelkamp.wordpress.com/2012/07/02/how-to-check-if-a-snmp-trap-is-received/ Hope this help..

Same problem, still waiting for Updates :-( Creating Negative impacts on Customers, since MAC address doesn't makes sense to them !!!

I guess MS will release an update which will give a proper alert with MIB2 Name for all the devices. Any idea when the next update will release ?

Same problem, still waiting for Updates :-( Creating Negative impacts on Customers, since MAC address doesn't makes sense to them !!!

I guess MS will release an update which will give a proper alert with MIB2 Name for all the devices. Any idea when the next update will release ?

I guess MS will release an update which will give a proper alert with MIB2 Name for all the devices. Any idea when the next update will release ? Discovery Configuration Settings The configuration file for the discovery configuration settings is stored in the file discovery.conf in the folder C:\Program Files\System Center 2012\Operations Manager\Server\NetworkMonitoring\conf\discovery. In this file are several settings, all of which are described quite clearly. The important one for this example is the DisplayFormatName setting. If you change any of the settings in this file, you will need to restart the System Center Management service on the network discovery server for this to take effect. You will also need to rediscover the device.

I guess MS will release an update which will give a proper alert with MIB2 Name for all the devices. Any idea when the next update will release ? Discovery Configuration Settings The configuration file for the discovery configuration settings is stored in the file discovery.conf in the folder C:\Program Files\System Center 2012\Operations Manager\Server\NetworkMonitoring\conf\discovery. In this file are several settings, all of which are described quite clearly. The important one for this example is the DisplayFormatName setting. If you change any of the settings in this file, you will need to restart the System Center Management service on the network discovery server for this to take effect. You will also need to rediscover the device.

I have now installed SP1 Beta and also tried the recommended change in the discovery file. But the alerts are the same.... I must do something wrong, because how it is possible for MS to miss this error, time after time. BR