Configure Gateway to issue PING test instead of RMS after heartbeat failure? RRS feed

  • Question

  • Hi everyone,

    I've been noticing that if a server in the DMZ (which communicates via Gateway servers) stops heartbeating, SCOM will issue a PING test, which always fails.  On further investigation, it seems like SCOM is using the RMS to issue the PING test.  Our firewalls currently deny traffic from the RMS directly to the agents, but permit traffic from the Gateway to the agents.  So if the gateway issued the PING test, it would be successful. 

    Is there a way to reconfigure SCOM to issue the PING tests via the Gateways instead of through the RMS?

    Thank you for your help!

    Friday, November 4, 2011 4:32 PM

All replies

  • it may help

    Find yourcomputer, Expand Availability until you find Heartbeat monitor



    • Proposed as answer by Vivian Xing Monday, November 7, 2011 7:54 AM
    Friday, November 4, 2011 11:17 PM
  • As mentioned above, you can change the ping source. The following thread discussed a similar issue, you can get more information here:

    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.
    Monday, November 7, 2011 7:54 AM
  • Ok great - thanks so much for everyone's help!  Just to clarify, Vivian, from the link you had sent, it seems as the overrides to the diagnostic PING in the screenshots Pavel sent above might not actually change the source used to PING the computer.  Is this correct?  (Just trying to make sure I understand this properly). 

    Also, is there any way to enter multiple gateway names to use for the PING test?  (i.e. if gateway01 was down, SCOM would know to try to ping via the failover gateway -- gateway02). 


    Monday, November 7, 2011 8:23 PM