question

WarrenPilkington-2900 avatar image
0 Votes"
WarrenPilkington-2900 asked saldana-msft edited

Cloud Management Gateway (CMG) appears to have constant upgrade messages in CloudMgr.log

We've been running a CMG on ConfigMgr with token based auth, and when set up in version 2002, it was a single cloud (classic) VM and this has been working well. We did the MECM upgrade to version 2107 a couple of weeks ago and updated clients, all well there too.

However, from yesterday, I've noted that a low number of clients are connected via the CMG, normally this is 400-500 but only seeing around 100-110 at present, and even then a number of them seem to then go offline.

I did note in CloudMgr.log that this appears to happen every five minutes, a recent snippet as below:

Current CMG deployment package hash is nvuhjuOw53Mscz26rqPXpS8LHupH2asSYb2A+YbRBcM= SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 12160 (0x2F80)
Current VMSS CMG deployment package hash is 151sGQMFOWHmByoADw4+CUUh7ypg/ix4BIjb9jILIEg= SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 12160 (0x2F80)
CreateUpgradeTaskForPackageChange: Triggered to create upgrade task for service type CloudProxyService with current package hash nvuhjuOw53Mscz26rqPXpS8LHupH2asSYb2A+YbRBcM=. SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 12160 (0x2F80)
TaskWorker: Starting task: [CloudServicesTaskBuilder] SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 5684 (0x1634)
CloudServicesTaskBuilder: Starting. SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 10920 (0x2AA8)
TaskManager: 0 task(s) running, 0 task(s) waiting to start. SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 11016 (0x2B08)
TaskManager: Task [CloudServicesTaskBuilder] status is Running SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 11016 (0x2B08)
CloudServicesTaskBuilder: Stopping. SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 10920 (0x2AA8)
TaskManager: 1 task(s) running, 0 task(s) waiting to start. SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 11016 (0x2B08)
TaskManager: Task [CloudServicesTaskBuilder] status is RanToCompletion SMS_CLOUD_SERVICES_MANAGER 22/09/2021 10:03:48 11016 (0x2B08)


The CMG itself from the ConfigMgr console shows the status of Ready, and the connection analyzer when run shows that it has passed all of the six tests with a green tick. It's almost as if that task to upgrade the cloud proxy service exits out.

From the Azure side, when checking the operational logs, it appears to show a fail when changing config, and the JSON then shows that there's no change in config. However, the operational logs only appear to show once every two hours.

Is this constant upgrade attempting meaning that the cloud service isn't allowing periodic responses, hence kicking clients off, or is there something else I need to check?

mem-cm-generalmem-cm-site-deploymentmem-cm-co-management
5 |1600 characters needed characters left characters exceeded

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

YOSHIAKIHATADA-6597 avatar image
0 Votes"
YOSHIAKIHATADA-6597 answered WarrenPilkington-2900 commented

/mem/configmgr/core/clients/manage/cmg/data-flowを詳細

5 |1600 characters needed characters left characters exceeded

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

AllenLiu-MSFT avatar image
0 Votes"
AllenLiu-MSFT answered

Hi,
Thank you very much for the update and we're glad the problem is solved now.

5 |1600 characters needed characters left characters exceeded

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

YOSHIAKIHATADA-6597 avatar image
0 Votes"
YOSHIAKIHATADA-6597 answered

/sql/t-sql/queries/top-transact-sqlを試してください。

5 |1600 characters needed characters left characters exceeded

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

WarrenPilkington-2900 avatar image
0 Votes"
WarrenPilkington-2900 answered

Good news, it's now resolved.

Prevoiously, the ports were set correctly as per the link sent for the data flow and the ports.

Upon further examination of the firewall, the configuration that allowed ports 10140-10155 via TCP-TLS had been removed for some reason. When added back, communication was working correctly and can see 400+ clients now connected via CMG.

The CloudMgr.log file I checked over appears therefore to be doing checks if any upgrade or config chnages are made, and if so, then apply them, as it's still doing that now. The CMG status says Ready and Azure shows all okay, so I'm thinking it's that instead.

5 |1600 characters needed characters left characters exceeded

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