Skip to content

Commit 106ac89

Browse files
ryanberg-aquentryanberg-aquent
committed
7894 P1 changes
1 parent b685b82 commit 106ac89

4 files changed

Lines changed: 21 additions & 21 deletions

File tree

‎support/azure/virtual-desktop/welcome-virtual-desktop.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -7,9 +7,9 @@ metadata:
77
title: Troubleshoot common issues with Azure Virtual Desktop
88
description: Documentation for troubleshooting common issues with Azure Virtual Desktop. # Required; article description that is displayed in search results. < 160 chars.
99
ms.topic: landing-page # Required
10-
10+
ms.author: jarrettr
1111
ms.reviewer: kaushika #Required; microsoft alias of author; optional team alias.
12-
ms.date: 01/17/2025
12+
ms.date: 10/15/2025
1313

1414
# linkListType: architecture | concept | deploy | download | get-started | how-to-guide | learn | overview | quickstart | reference | tutorial | video | whats-new
1515

‎support/azure/virtual-machines/linux/troubleshoot-pacemaker-services-suse.md‎

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -305,7 +305,7 @@ The following text shows the `sudo crm status` output when this issue occurs:
305305
Clone Set: cln_SAPHanaTopology [rsc_SAPHanaTopology]
306306
rsc_SAPHanaTopology (ocf::suse:SAPHanaTopology): Started node-1
307307
rsc_SAPHanaTopology (ocf::suse:SAPHanaTopology): Started node-2
308-
Master/Slave Set: msl_SAPHana [rsc_SAPHana]
308+
Primary/Secondary Set: msl_SAPHana [rsc_SAPHana]
309309
rsc_SAPHana_P40_HDB00 (ocf::suse:SAPHana): Stopped node-1 (Monitoring)
310310
Resource Group: g_ip_P40_HDB00
311311
rsc_ip_P40_HDB00 (ocf::heartbeat:IPaddr2): Started node-1
@@ -346,7 +346,7 @@ sudo SAPHanaSR-showAttr
346346
roles score site srmode sync_state version vhost
347347
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
348348
node-1 UNDEFINED 10 online logreplay node-2 0:P:::: 5 DC1 syncmem SFAIL 2.00.046.00.1581325702 node-1
349-
node-2 PROMOTED 1693237652 online logreplay node-1 4:P:master1:master:worker:master 150 DC2 syncmem PRIM 2.00.046.00.1581325702 node-2
349+
node-2 PROMOTED 1693237652 online logreplay node-1 4:P:primary1:primary:worker:primary 150 DC2 syncmem PRIM 2.00.046.00.1581325702 node-2
350350
```
351351

352352
### Workaround for Scenario 4, Symptom 2
@@ -453,7 +453,7 @@ Pacemaker can't start the SAP HANA resource if `SYN failures` exist between the
453453
site id: 2
454454
site name: node-2
455455
active primary site: 1
456-
primary masters: node-1
456+
primary principals: node-1
457457
```
458458

459459
5. You can also verify the SAP HANA system replication by running the following command:
@@ -469,8 +469,8 @@ Pacemaker can't start the SAP HANA resource if `SYN failures` exist between the
469469
470470
Hosts clone_state lpa_fh9_lpt node_state op_mode remoteHost roles score site srmode sync_state version vhost
471471
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
472-
node-1 PROMOTED 1693237652 online logreplay node-2 4:P:master1:master:worker:master 150 DC1 syncmem PRIM 2.00.046.00.1581325702 node-1
473-
node-2 DEMOTED 10 online logreplay node-1 4:P:master1:master:worker:master 100 DC2 syncmem SOK 2.00.046.00.1581325702 node-2
472+
node-1 PROMOTED 1693237652 online logreplay node-2 4:P:primary1:primary:worker:primary 150 DC1 syncmem PRIM 2.00.046.00.1581325702 node-1
473+
node-2 DEMOTED 10 online logreplay node-1 4:P:primary1:primary:worker:primary 100 DC2 syncmem SOK 2.00.046.00.1581325702 node-2
474474
```
475475

476476
6. Exit the SAP Admin account, and remove the cluster from maintenance mode:

‎support/azure/virtual-machines/linux/troubleshoot-rhel-pacemaker-cluster-services-resources-startup-issues.md‎

Lines changed: 13 additions & 13 deletions
Original file line numberDiff line numberDiff line change
@@ -270,12 +270,12 @@ SAP HANA DB doesn't start, and it returns an `unknown error` error message.
270270
* Node node-0 (1):
271271
+ hana_XXX_clone_state : PROMOTED
272272
+ hana_XXX_sync_state : PRIM
273-
+ hana_XXX_roles : 2:P:master1:master:worker:slave
273+
+ hana_XXX_roles : 2:P:primary1:primary:worker:secondary
274274
275275
* Node node-1 (2):
276276
+ hana_XXX_clone_state : WAITING4PRIM
277277
+ hana_XX_sync_state : SFAIL
278-
+ hana_XXX_roles : 2:S:master1:master:worker:slave
278+
+ hana_XXX_roles : 2:S:primary1:primary:worker:secondary
279279
```
280280
281281
3. When you run `sudo pcs status`, the cluster status is shown as follows:
@@ -294,9 +294,9 @@ SAP HANA DB doesn't start, and it returns an `unknown error` error message.
294294
rsc_st_azure (stonith:fence_azure_arm): Started node-1
295295
Clone Set: cln_SAPHanaTopology [rsc_SAPHanaTopology]
296296
Started: [ node-0 node-1 ]
297-
Master/Slave Set: msl_SAPHana [rsc_SAPHana]
298-
Master: [ node-1 ]
299-
Slave: [ node-0 ]
297+
Primary/Secondary Set: msl_SAPHana [rsc_SAPHana]
298+
Primary: [ node-1 ]
299+
Secondary: [ node-0 ]
300300
Resource Group: g_ip_HN1_HBD00
301301
vip_HN1_HBD00 (ocf::heartbeat:IPaddr2): Started node-0
302302
nc_HN1_HBD00 (ocf::heartbeat:azure-lb): Started node-0
@@ -323,8 +323,8 @@ global Fri Aug 23 11:47:32 2024 false
323323
324324
Hosts clone_state lpa_fh9_lpt node_state op_mode remoteHost roles score site srmode sync_state version vhost
325325
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
326-
node-0 DEMOTED 10 online logreplay node-1 4:S:master1:master:worker:master 5 SITEA syncmem SOK 2.00.046.00.1581325702 node-0
327-
node-1 PROMOTED 1693237652 online logreplay node-0 4:P:master1:master:worker:master 150 SITEA syncmem PRIM 2.00.046.00.1581325702 node-1
326+
node-0 DEMOTED 10 online logreplay node-1 4:S:primary1:primary:worker:primary 5 SITEA syncmem SOK 2.00.046.00.1581325702 node-0
327+
node-1 PROMOTED 1693237652 online logreplay node-0 4:P:primary1:primary:worker:primary 150 SITEA syncmem PRIM 2.00.046.00.1581325702 node-1
328328
```
329329

330330
### Workaround for scenario 3, symptom 1
@@ -436,8 +436,8 @@ The SAP HANA resource can't be started by Pacemaker if there are `SYN` failures
436436
437437
Hosts clone_state lpa_fh9_lpt node_state op_mode remoteHost roles score site srmode sync_state version vhost
438438
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
439-
node-0 DEMOTED 10 online logreplay node-1 4:S:master1:master:worker:master 5 SITEA syncmem SOK 2.00.046.00.1581325702 node-0
440-
node-1 PROMOTED 1693237652 online logreplay node-0 4:P:master1:master:worker:master 150 SITEA syncmem PRIM 2.00.046.00.1581325702 node-1
439+
node-0 DEMOTED 10 online logreplay node-1 4:S:primary1:primary:worker:primary 5 SITEA syncmem SOK 2.00.046.00.1581325702 node-0
440+
node-1 PROMOTED 1693237652 online logreplay node-0 4:P:primary1:primary:worker:primary 150 SITEA syncmem PRIM 2.00.046.00.1581325702 node-1
441441
```
442442

443443
7. Exit the SAP Admin account, and then remove the cluster from maintenance mode:
@@ -450,7 +450,7 @@ The SAP HANA resource can't be started by Pacemaker if there are `SYN` failures
450450

451451
### Scenario 3, Symptom 2: SAP HANA doesn't start because of replication failure
452452

453-
The SAP HANA resource experiences startup failures, and its `hana_xxx_roles` attribute shows `1:N:master1::worker:`. The `N` status indicates that the resource is out of sync and running in standalone mode. The database resource is neither primary nor secondary on any node.
453+
The SAP HANA resource experiences startup failures, and its `hana_xxx_roles` attribute shows `1:N:primary1::worker:`. The `N` status indicates that the resource is out of sync and running in standalone mode. The database resource is neither primary nor secondary on any node.
454454

455455
When you run the `sudo pcs status --full` command, the `node attributes` status is shown as follows:
456456

@@ -463,7 +463,7 @@ When you run the `sudo pcs status --full` command, the `node attributes` status
463463
* hana_XXX_clone_state : UNDEFINED
464464
* hana_XXX_op_mode : logreplay
465465
* hana_XXX_remoteHost : node-1
466-
* hana_XXX_roles : 1:N:master1::worker:
466+
* hana_XXX_roles : 1:N:primary1::worker:
467467
* hana_XXX_site : SITE1
468468
* hana_XXX_srah : -
469469
* hana_XXX_srmode : sync
@@ -474,7 +474,7 @@ When you run the `sudo pcs status --full` command, the `node attributes` status
474474
* hana_XXX_clone_state : UNDEFINED
475475
* hana_XXX_op_mode : logreplay
476476
* hana_XXX_remoteHost : node-0
477-
* hana_XXX_roles : 4:N:master1:master:worker:master
477+
* hana_XXX_roles : 4:N:primary1:primary:worker:primary
478478
* hana_XXX_site : SITE2
479479
* hana_XXX_sra : -
480480
* hana_XXX_srah : -
@@ -483,7 +483,7 @@ When you run the `sudo pcs status --full` command, the `node attributes` status
483483
* hana_XXX_version : 2.00.079.00
484484
* hana_XXX_vhost : node-1
485485
* lpa_XXX_lpt : 1733552029
486-
* master-SAPHana_XXX_00 : 150
486+
* primary-SAPHana_XXX_00 : 150
487487
```
488488

489489
This Migration summary indicates that the SAP HANA resource (SAPHana_XXX_00) failed to start on both nodes (node-0 and node-1). The fail count is set to 1000000 (infinity).

‎support/azure/virtual-machines/windows/serial-console-power-options.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -26,7 +26,7 @@ Serial Console feature | Description | Use case
2626
Restart VM | A graceful restart of your VM or virtual machine scale set instance. This operation is the same as calling the restart feature that's available in the Overview page. | In most cases, this option should be your primary tool when you try to restart your VM. When you use this option, your Serial Console connection experiences a brief interruption, and then automatically resumes when the VM restarts.
2727
Reset VM | A forceful power cycle of your VM or virtual machine scale that's set by the Azure platform. | This option is used to immediately restart your OS regardless of its current state. Because this operation isn't graceful, there's a risk of data loss or corruption. There's no interruption in the Serial Console connection. This condition is useful for sending commands early during startup (for example, getting to GRUB on a Linux VM or to Safe Mode in a Windows VM).
2828
SysRq - Reboot (b) | A system request to force a guest restart. | This feature is applicable to only Linux systems, and requires [SysRq to be enabled](../linux/serial-console-nmi-sysrq.md#system-request-sysrq) in the OS. If the system is correctly configured for SysRq, this command causes the OS to restart.
29-
NMI (Non-maskable Interrupt) | An interrupt command that's delivered to the OS. | This operation is available for both [Windows](./serial-console-windows.md#use-the-serial-console-for-nmi-calls) and [Linux](../linux/serial-console-nmi-sysrq.md#nonmaskable-interrupt-nmi) VMs. It requires NMI to be enabled. Sending an NMI typically causes your system to stop responding. You can configure your system to create a dump file and then restart upon receiving the NMI. This condition might be useful in low-level debugging.
29+
NMI (Non-maskable Interrupt) | An interrupt command that's delivered to the OS. | This operation is available for both [Windows](./serial-console-windows.md#use-the-serial-console-for-nmi-calls) and [Linux](../linux/serial-console-nmi-sysrq.md#non-maskable-interrupt-nmi) VMs. It requires NMI to be enabled. Sending an NMI typically causes your system to stop responding. You can configure your system to create a dump file and then restart upon receiving the NMI. This condition might be useful in low-level debugging.
3030

3131
## Next steps
3232

0 commit comments

Comments
 (0)