Merge pull request #88274 from dfitzmau/OCPBUGS-49859-15

[enterprise-4.15] OCPBUGS-49859-15

Author: dfitzmau

modules/virt-example-nmstate-IP-management.adoc

@@ -103,7 +103,9 @@ To define a DNS configuration for a network interface, you must initially specif
 
 [IMPORTANT]
 ====
-You cannot use `br-ex` bridge, an OVNKubernetes-managed Open vSwitch bridge, as the interface when configuring DNS resolvers.
+You cannot use the `br-ex` bridge, an OVN-Kubernetes-managed Open vSwitch bridge, as the interface when configuring DNS resolvers unless you manually configured a customized `br-ex` bridge.
+
+For more information, see "Creating a manifest object that includes a customized br-ex bridge" in the _Deploying installer-provisioned clusters on bare metal_ document or the _Installing a user-provisioned cluster on bare metal_ document.
 ====
 
 The following example shows a default situation that stores DNS values globally:
@@ -283,4 +285,11 @@ routes:
 # ...
 ----
 <1> The static IP address for the Ethernet interface.
-<2> Next hop address for the node traffic. This must be in the same subnet as the IP address set for the Ethernet interface.
+<2> The next hop address for the node traffic. This must be in the same subnet as the IP address set for the Ethernet interface.
+
+[IMPORTANT]
+====
+You cannot use the OVN-Kubernetes `br-ex` bridge as the next hop interface when configuring a static route unless you manually configured a customized `br-ex` bridge.
+
+For more information, see "Creating a manifest object that includes a customized br-ex bridge" in the _Deploying installer-provisioned clusters on bare metal_ document or the _Installing a user-provisioned cluster on bare metal_ document.
+====