first

msjuergent · msjuergent · commit 0740fea620a7 · 2018-07-17T11:17:53.000-07:00
diff --git a/articles/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker.md b/articles/virtual-machines/workloads/sap/high-availability-guide-suse-pacemaker.md
@@ -37,7 +37,7 @@ If you do not want to invest in one additional virtual machine, you can also use
 ![Pacemaker on SLES overview](./media/high-availability-guide-suse-pacemaker/pacemaker.png)
 
 >[!IMPORTANT]
-> Using a SBD device for your Pacemaker cluster, it is essential for the overall reliability of the complete cluster that the routing between the VMs involved and the VM(s) hosting the SBD device(s) is not passing through any other devices like [NVAs](https://azure.microsoft.com/solutions/network-appliances/). Otherwise issues with the NVA can have a negative impact on the stability and reliability of the overall cluster configuration. In order to avoid such obstacles, investigate routing rules of NVAs and [User Defined Routing rules](https://docs.microsoft.com/azure/virtual-network/virtual-networks-udr-overview) when planning and deploying SBD devices.
+> When planning and deploying Linux Pacemaker clustered nodes and SBD devices, it is essential for the overall reliability of the complete cluster configuration that the routing between the VMs involved and the VM(s) hosting the SBD device(s) is not passing through any other devices like [NVAs](https://azure.microsoft.com/solutions/network-appliances/). Otherwise, issues and maintenance events with the NVA can have a negative impact on the stability and reliability of the overall cluster configuration. In order to avoid such obstacles, do not define routing rules of NVAs or [User Defined Routing rules](https://docs.microsoft.com/azure/virtual-network/virtual-networks-udr-overview) that route traffic between clustered nodes and SBD devices through NVAs and similar devices when planning and deploying Linux Pacemaker clustered nodes and SBD devices. 
 >
 
 

Original file line number	Diff line number	Diff line change
`@@ -37,7 +37,7 @@ If you do not want to invest in one additional virtual machine, you can also use`
`37`	`37`	`![Pacemaker on SLES overview](./media/high-availability-guide-suse-pacemaker/pacemaker.png)`
`38`	`38`
`39`	`39`	`>[!IMPORTANT]`
`40`		-> Using a SBD device for your Pacemaker cluster, it is essential for the overall reliability of the complete cluster that the routing between the VMs involved and the VM(s) hosting the SBD device(s) is not passing through any other devices like [NVAs](https://azure.microsoft.com/solutions/network-appliances/). Otherwise issues with the NVA can have a negative impact on the stability and reliability of the overall cluster configuration. In order to avoid such obstacles, investigate routing rules of NVAs and [User Defined Routing rules](https://docs.microsoft.com/azure/virtual-network/virtual-networks-udr-overview) when planning and deploying SBD devices.
	`40`	+> When planning and deploying Linux Pacemaker clustered nodes and SBD devices, it is essential for the overall reliability of the complete cluster configuration that the routing between the VMs involved and the VM(s) hosting the SBD device(s) is not passing through any other devices like [NVAs](https://azure.microsoft.com/solutions/network-appliances/). Otherwise, issues and maintenance events with the NVA can have a negative impact on the stability and reliability of the overall cluster configuration. In order to avoid such obstacles, do not define routing rules of NVAs or [User Defined Routing rules](https://docs.microsoft.com/azure/virtual-network/virtual-networks-udr-overview) that route traffic between clustered nodes and SBD devices through NVAs and similar devices when planning and deploying Linux Pacemaker clustered nodes and SBD devices.
`41`	`41`	`>`
`42`	`42`
`43`	`43`