anchor.diff:  <3> The name for the configuration. It is recommended to match the configuration name to the `name` value of the network attachment definition.
   <4> The actual name of the Container Network Interface (CNI) plug-in that provides the network for this network attachment definition. Do not change this field unless you want to use a different CNI.
   <5> The name of the Linux bridge configured on the node.
  -<6> Optional: The VLAN tag.
  -<7> The CNI plug-in that allows the MAC pool manager to assign a unique MAC address to the connection.
  +<6> Optional: Flag to enable MAC spoof check. When set to `true`, you cannot change the MAC address of the pod or guest interface. This attribute provides security against a MAC spoofing attack by allowing only a single MAC address to exit the pod.
  +<7> Optional: The VLAN tag.
  +<8> The CNI plug-in that allows the MAC pool manager to assign a unique MAC address to the connection.
   
  -. Create the network attachment definition: 
  +. Create the network attachment definition:
   +
   [source,terminal]
   ----
  
positive.code: 
  As a network administrator, you can configure a network attachment definition of type `cnv-bridge` to provide Layer-2 networking to pods and virtual machines.
  
  [NOTE]
  ====
  The network attachment definition must be in the same namespace as the pod or virtual machine.
  ====
  
  .Procedure
  
  
negative.code: $ oc get network-attachment-definition <a-bridge-network> <1>
  ----
  <1> Where `<a-bridge-network>` is the name specified in the network attachment definition config.
  