Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 3 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/ONTAP_9_LIF_configured_for_a_VLAN_is_unreachable_when_native_VLAN_is_present
      Network switch has a native VLAN configured for the ports connected to the affected interfaces Affected LIF is configured on an interface corresponding to the switch's configured native VLAN Example: ...Network switch has a native VLAN configured for the ports connected to the affected interfaces Affected LIF is configured on an interface corresponding to the switch's configured native VLAN Example: Switch's native VLAN is configured for 129, LIF is created on port a0a-129 Alternatively, the affected LIF is not configured on the VLAN interface corresponding to the switch's configured native VLAN Example: Switch's native VLAN is configured for 129, LIF is created on port a0a
    • https://kb.netapp.com/on-prem/ontap/mc/MC-KBs/Why_is_no_vlan_dot1Q_tag_native_not_showing_in_running_config_on_cisco_switches_after_applying_the_RCF
      Applies to Metrocluster over IP Cisco cluster switches Reference configuration file (RCF) Answer The no vlan dot1Q tag native setting from RCF is not visible in the show running-config Use the show vl...Applies to Metrocluster over IP Cisco cluster switches Reference configuration file (RCF) Answer The no vlan dot1Q tag native setting from RCF is not visible in the show running-config Use the show vlan dot1Q tag native command instead site-a-sw2# show vlan dot1Q tag native vlan dot1q native tag is disabled Additional Information For the diffrent version of nexus os use the cisco web site for more documentation on the commands
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/e0M_Service_Processor_or_BMC_unreachable_on_network_due_to_VLAN_tagging_on_switch_port
      Applies to After correctly physically cabling and configuring the e0M/SP/BMC, ping and SSH tests to the remote device fail You can ping the default gateway from the e0M/SP/BMC, indicating that the net...Applies to After correctly physically cabling and configuring the e0M/SP/BMC, ping and SSH tests to the remote device fail You can ping the default gateway from the e0M/SP/BMC, indicating that the network settings you applied are working, and that physical connectivity is not the issue Connectivity to your system's cluster management or node management LIF is not affected, even though the e0M/SP/BMC are on the same subnet Cluster/node management LIFs are residing on a port other than e0M