none
Port/Interface Monitoring in SCOM 2012 RRS feed

  • Question

  • Hi All,

    We are using SCOM 2012 in our customer environment. We have successfully added the network devices like Cisco Nexus 7000 and 5000 switches.

    Also, SCOM discovered all the componenets of these devices as per the supported list of devices and enabled monitoring for all the ports/interfaces.

    Few alerts got generated in active alerts view for the ports/interfaces which are down/unavailable. This is good upto this point.

    But, in alert information it is displaying path as MAC Addess instead of Name. We tried to modify the alert with all the information nothing helped us to get proper information.

    We are able to see all the information in the entity properties of the port/interfaces. But, we don't know how to get that details into alert.

    If we want to create new SNMP based monitor in order to monitor all the interface status, how to create this type of monitor which will monitor all the ports/interfaces?

    Also in the supported list of network devices, the cisco nexus 5000 switch is not added. Whether this added with SCOM 2012 SP1?

    Does SCOM 2012 SP1 will give proper information in the alerts for network ports/interfaces?

    Please help us in this regard.

    Thanks


    Kumaresan Lakshmanan

    Saturday, February 9, 2013 4:04 PM

Answers

All replies

  • Hi

    See this post here http://blogs.technet.com/b/momteam/archive/2011/09/20/what-gets-monitored-with-system-center-operations-manager-2012-network-monitoring.aspx . If you have ports which are not monitored you Need them to add to the Critical Network Adapters Group as described in the link.

    Which devices excatly deliver which Information is some how hard to get for SCOM 2012 SP1, as this list here http://www.microsoft.com/en-us/download/details.aspx?id=26831 is not being updated.

    I hope MS will do it soon...

    Cheers,

    Stefan


    Blog: http://blog.scomfaq.ch

    Sunday, February 10, 2013 10:20 PM
  • Hi Kumaresan,

    As this thread has been quiet for a while, we assume that the issue has been resolved. At this time, we will mark it as "Answered" as the previous steps should be helpful for many similar scenarios.

    In addition, we’d love to hear your feedback about the solution. By sharing your experience you can help other community members facing similar problems.

    Thanks,


    Yog Li
    TechNet Community Support

    Thursday, February 21, 2013 8:12 AM
    Moderator
  • Hi

    Did you find an answer to this? I have the same problem. It is very hard to identify which interface is down with the default interface name.

    Torboro

    Thursday, October 17, 2013 11:55 AM
  • Hey guys.

    Arjan Vroege wrote nice MP which renames default interface name "PORT-xxxxx" to something really understandable and easy to identify.

    https://gallery.technet.microsoft.com/scriptcenter/Network-Change-Network-f20551ca/view/Reviews


    MCSA Office 365

    Saturday, November 28, 2015 10:48 PM