SCOM 2016 agent greayed out including the RMS

Question

question

68002602 asked May 12, '22 SimonRenMSFT-3639 commented May 25, '22

SCOM 2016 agent greayed out including the RMS

Hello

I've faced some strange behavior in our SCOM environment. After a switch maintenance, we've lost a LAN connection for more than 2 hours and our management server was hit hard with all alerts generated from every device. After we restore the LAN connection, the management server is filled with event ID 20002 : "A device at IP xx.x..xx.xx:58245 attempted to connect but could not be authenticated, and was rejected." and it's grayed out.

All except few clients agents are also grayed out.

I got the below on the client Ops Manager log

Event ID: 21006

The OpsMgr Connector could not connect to RMS:5723. The error code is 10061L(No connection could be made because the target machine actively refused it.). Please verify there is network connectivity, the server is running and has registered it's listening port, and there are no firewalls blocking traffic to the destination.

I tried to flush the RMS and many clients but no luck. Also checked the there's no firewall which blocks the traffic between the RMS and the clients.

Thanks

msc-operations-manager

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Answer 1 · 2022-05-13T08:14:24.517Z

SimonRenMSFT-3639 answered May 13, '22 SimonRenMSFT-3639 commented May 25, '22

Hi,

Thanks for posting in Microsoft MECM Q&A forum.

1,Maybe the management server is overloaded (either by memory usage or CPU) where the workflow processing new data stalls out, and the management server stops accepting any new connections. Usually restarting the server is the way to get things “unstuck”, if possible, please have a try.

2,You could run a simultaneous network trace between the agent and the management server while you reproduce the communication failures. This can help you to determine whether the packets are reaching the management server, and whether any device between the two components is trying to optimize the traffic or is dropping some packets.

Same issue from the official article: Troubleshoot gray agent states in System Center Operations Manager

Hope it helps. Thanks for your time.

Best regards,
Simon

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

gray.png (38.2 KiB)

· 1

5 |1600 characters needed characters left characters exceeded

Attachments: Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

SimonRenMSFT-3639 · May 25 at 08:28 AM

Hi,

Hope everything goes well. Do you need any further assistance about this issue? If yes, please feel free to let us know, we will do our best to help you.

If the response is helpful, it's appreciated that you could click "Accept Answer" and upvote it, this will help other users to search for useful information more quickly.

Thanks for your time.

Best regards,
Simon

0 ·

question