Skip to main content
NetApp Knowledge Base

How to split ports from a broadcast domain into a dedicated broadcast domain?

Views:
7,974
Visibility:
Public
Votes:
7
Category:
ontap-9
Specialty:
nas
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.

Example: 

[node-02: vifmgr: vifmgr.reach.noreach:notice]: Network port e0M on node node-02 cannot reach its expected broadcast domain Default:vlan20. No other broadcast domains appear to be reachable from this port.

  • These messages can be ignored if the configuration has been validated.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.