Skip to main content
NetApp Response to Russia-Ukraine Cyber Threat
In response to the recent rise in cyber threat due to the Russian-Ukraine crisis, NetApp is actively monitoring the global security intelligence and updating our cybersecurity measures. We follow U.S. Federal Government guidance and remain on high alert. Customers are encouraged to monitor the Cybersecurity and Infrastructure Security (CISA) website for new information as it develops and remain on high alert.
NetApp Knowledge Base

Broadcast-domain configured with ports from multiple VLANs

Views:
5,672
Visibility:
Public
Votes:
3
Category:
ontap-9
Specialty:
network
Last Updated:

Applies to

ONTAP 9

Description

  • A broadcast-domain is designed to contain a set of ports which belong to the same layer 2 network.
  • After a broadcast-domain is created, one or more LIFs might be assigned to it with the understanding that the LIF might failover to any port within the broadcast-domain and expect the same network connectivity.
  • A broadcast-domain that contains ports from multiple VLANs might lead to a service interruption if a LIF fails over to a port within the broadcast-domain that does not provide the same network connectivity.
    • To look at the lif failover targets for a lif in the broadcast domain
      • Command line: ::> network interface show -failover -broadcast-domain <broadcast domain>
      • Autosupport section: network-interface.xml
        • Subsection: failover targets
There are cases where a mixture of VLAN tagged and non-tagged ports in a single broadcast-domain might be acceptable. It is up to the user to make this determination based on the client network configuration. If the switch port the non-VLAN tagged ports are connected to are configured to have access to the VLAN, then there might not be an issue. This would most commonly be seen with the e0M port due to the inability to configure a VLAN tag on this port.
  • As the storage controller does not have visibility into this configuration, it might raise a warning message or alerts from the storage controller or via AutoSupport.
  • These messages can be ignored if the configuration has been validated.

 

Scan to view the article on your device