IBM Z OSA traffic forwarding

Author: SNiemann15

modules/virt-attaching-vm-to-secondary-udn.adoc

@@ -2,8 +2,8 @@
 //
 // * virt/vm_networking/virt-connecting-vm-to-secondary-udn.adoc
 
-:_mod-docs-content-type: PROCEDURE                                
-[id="virt-attaching-vm-to-secondary-udn_{context}"]                                  
+:_mod-docs-content-type: PROCEDURE
+[id="virt-attaching-vm-to-secondary-udn_{context}"]
 = Attaching a virtual machine to secondary user-defined networks by using the CLI
 
 You can connect a virtual machine (VM) to multiple secondary cluster-scoped user-defined networks (CUDNs) by configuring the interface binding.
@@ -34,7 +34,7 @@ spec:
           type: ""
         resources:
           requests:
-            memory: 2048M               
+            memory: 2048M
       networks:
       - name: secondary_localnet # <3>
         multus:
@@ -55,4 +55,9 @@ $ oc apply -f <filename>.yaml
 +
 where:
 
-<filename>:: Specifies the name of your `VirtualMachine` manifest YAML file.
+<filename>:: Specifies the name of your `VirtualMachine` manifest YAML file.
+
+[NOTE]
+====
+When running {VirtProductName} on {ibm-z-name} using an OSA card, be aware that the OSA card only forwards network traffic to devices that are registered with the OSA device. As a result, any traffic destined for unregistered devices is not forwarded.
+====

virt/vm_networking/virt-connecting-vm-to-secondary-udn.adoc

@@ -1,14 +1,14 @@
-:_mod-docs-content-type: ASSEMBLY                               
-[id="virt-connecting-vm-to-secondary-udn"]                                    
-= Connecting a virtual machine to a secondary localnet user-defined network                                                
-include::_attributes/common-attributes.adoc[]                   
-:context: virt-connecting-vm-to-secondary-udn                                    
-                                                                
+:_mod-docs-content-type: ASSEMBLY
+[id="virt-connecting-vm-to-secondary-udn"]
+= Connecting a virtual machine to a secondary localnet user-defined network
+include::_attributes/common-attributes.adoc[]
+:context: virt-connecting-vm-to-secondary-udn
+
 toc::[]
 
 You can connect a virtual machine (VM) to an OVN-Kubernetes localnet secondary network by using the CLI. Cluster administrators can use the `ClusterUserDefinedNetwork` (CUDN) custom resource definition (CRD) to create a shared OVN-Kubernetes network across multiple namespaces.
 
-An OVN-Kubernetes secondary network is compatible with the xref:../../networking/multiple_networks/secondary_networks/configuring-multi-network-policy.adoc#compatibility-with-multi-network-policy_configuring-additional-network[multi-network policy API] which provides the `MultiNetworkPolicy` custom resource definition (CRD) to control traffic flow to and from VMs. 
+An OVN-Kubernetes secondary network is compatible with the xref:../../networking/multiple_networks/secondary_networks/configuring-multi-network-policy.adoc#compatibility-with-multi-network-policy_configuring-additional-network[multi-network policy API] which provides the `MultiNetworkPolicy` custom resource definition (CRD) to control traffic flow to and from VMs.
 
 [IMPORTANT]
 ====
@@ -26,4 +26,6 @@ include::modules/virt-attaching-vm-to-secondary-udn.adoc[leveloffset=+1]
 [role="_additional-resources"]
 [id="additional-resources_{context}"]
 == Additional resources
-* xref:../../networking/multiple_networks/primary_networks/about-user-defined-networks.adoc#about-cudn_about-user-defined-networks[About the `ClusterUserDefinedNetwork` CR]
+* xref:../../networking/multiple_networks/primary_networks/about-user-defined-networks.adoc#about-cudn_about-user-defined-networks[About the `ClusterUserDefinedNetwork` CR]
+
+* link:https://www.ibm.com/docs/en/linux-on-systems?topic=choices-osa-interface-traffic-forwarding[OSA interface traffic forwarding]