I suggest you ...

improve network monitoring

Monitoring network has several issues that need to be addressed.

- very unclear how it works (the discovery is 1 big black box. it's not "open" like system monitoring) and what it captures is not understandable for network admins (e.g. a switch has mem-1, mem-5 and mem-6 found by scom, but this is not understood by a network admin who only sees memory and not this division).

- key property is mac address which keeps popping up in several views instead of a understandable name (the default performance views don't even have the option to show the mibII name/dnsname).

- added support for context monitoring.

37 votes
Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
You have left! (?) (thinking…)
rob1974 shared this idea  ·   ·  Flag idea as inappropriate…  ·  Admin →


Sign in
Sign in with: Facebook Google
Signed in as (Sign out)
  • Patrick Seidl (s2) commented  ·   ·  Flag as inappropriate

    Fully agree with the others.
    SCOM is not supporting floating IPs (=changing MAC address).

    When can we see an update here?
    Or at least a comment from MSFT?

  • Michael Filippidis commented  ·   ·  Flag as inappropriate

    Totally agree with Peter and Martijn about the lack of utility with network device monitoring especially as regards the fields used for interface alerts.

    The two key fields that are useful are the Interface Alias and Description fields which pin-point the network admins to exactly which interface/port on the device is having issues, as well as what it is used for since the Description filed is often used to provide a friendly text description of what connects to this port. Even if it were just possible to add these two fields in the Alert Body of the Rule/Monitor that pertain to interfaces/port monitoring manually it would be a start, but these are all sealed and so no customization of the out-of the box Interface Status alerts is possible and we get a pointless alert about IF-xxxxxxxx that is totally useless for informing an operator what they need to start working on the issue.

  • Peter Hakesley commented  ·   ·  Flag as inappropriate

    I totally agree using the MAC address as the Path makes no useable sense and we have abandoned network monitoring in SCOM - it is simply childlike in its implementation.

  • Martijn commented  ·   ·  Flag as inappropriate

    While the discovery itself is understandable. The results are awkward. Instead of showing interface by names like Fa x/x Gi x/x or Te x/x, etc. SCOM interface shows port numbers from 1 to 1000 which do not relate to how network admins work via consoles.

    The alerts about interfaces and ports should also show the 'description' field of interfaces. This makes it so much easier to tell what interface is in error state.

Feedback and Knowledge Base