Connection Monitor On-Prem Test Group issues

Fleck, Ryan 1

So, I've created some connection monitors to do simple ICMP/PINGs to various on-prem network resources. Utilizing on-prem LA agent machines. For whatever reason, some test group machines just show Indeterminate and I've noticed when I go to edit my test groups to remove some of the machines with issues. It goes blank when I hit update test group and I am unable to remove them..

I've since re-created a separate LA workspace, a different NPM and Network Watcher. But the same various results apply. I've setup a few different test groups and it all just seems very random on when the machine works or if it just show Indeterminate. The Workspace, NPM and Network watcher are all in the Central US region.

All machines have LA Agent/MOM 10.20.18064.0

Am I the only one? This seems to be driving me nuts and something so simple...

GitaraniSharma-MSFT 47,676 Reputation points Microsoft Employee

2022-07-29T14:08:08.33+00:00

Hello @Fleck, Ryan ,

Welcome to Microsoft Q&A Platform. Thank you for reaching out & hope you are doing well.

I understand that you have created connection monitors to do simple ICMP/PINGs to various on-prem network resources utilizing on-prem LA agent machines but some test group machines just show Indeterminate. Even after recreating a separate LA workspace, a different NPM and Network Watcher, the same issue re-occurs.

Are your on-premise machines connected to multiple Azure connection monitors(CMs)?

Regards,
Gita
GitaraniSharma-MSFT 47,676 Reputation points Microsoft Employee

2022-07-29T14:08:31.04+00:00
Hello @Fleck, Ryan ,

I also checked internally and found the below causes for Indeterminate state:

This can happen if your on-premise machines are connected to 2 different Log Analytics workspaces. Make sure that all your on-premise machines are connected to only one Log Analytics workspace.

Update the existing connection monitors to properly select the on-premise machines as sources connected to single LA workspace.

Let the connection monitor be in the same subscription as the subscription of output log analytics workspace. Otherwise, if you want to create "connection monitor" in different subscription as compared to output log analytics workspace, please be sure that "User" who is trying to access the "ConnectionMonitor UI" should have access to both the subscriptions. If user has access to only CM's subscription but not to Sub's of LA workspace, then, "NoValidToken" error is seen and so "Indeterminate" status will be seen in UI.

I would request you to check your setup and configure your on-premise machines and CMs following the above rules.

Regards,
Gita
Fleck, Ryan 1 Reputation point

2022-07-29T14:31:25.477+00:00
Hello Gita,

No, just a single connection monitor

They are back to connected to a single LA workspace. I created a new one for the network watcher as a test but it had the same results.

I deleted all my connection monitors and have been re-creating. As it would not let me update them (test groups) but I am back to randomly having servers show as Indeterminate and can not remove them from the test groups.

All resources are in one subscription.

They were following all the rules above, I broke the rules and changed them in an effort to fix the issues. But have since gone back to best practice.

Regards,

Ryan
GitaraniSharma-MSFT 47,676 Reputation points Microsoft Employee

2022-07-29T15:35:07.957+00:00

Hello @Fleck, Ryan ,

Thank you for the details.

If the configuration is as per the advised rules / best practices, then we may need to look into the backend logs and would need access to your resources for further investigation. Hence, if you have a support plan, I request you file a support ticket, else please do let us know, we will try and help you get a one-time free technical support.

Regards,
Gita