Search
- Filter results by:
- View attachments
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Why_are_all_layer_2_packets_flagged_with_COS4This is default, all storage related layer 2 packets are flagged with COS4 (ONTAP sets the QoS priority bit to 4 for all tagged packets) Feature Request 1098263 has been created to change this behavio...This is default, all storage related layer 2 packets are flagged with COS4 (ONTAP sets the QoS priority bit to 4 for all tagged packets) Feature Request 1098263 has been created to change this behaviour (making it configurable) Cisco describes a switch based method to remark the packets with COS0. Please contact NetApp Technical Support or log into the NetApp Support Site to create a case to get your request added as a vote to the enhancement request.
- https://kb.netapp.com/on-prem/solidfire/hardware_Kbs/Unable_to_modify_SolidFire_VLAN_start_IP_of_the_blockApplies to NetApp SolidFire NetApp HCI NetApp Element Software Issue Attempt to modify start IP of the VLAN block fails with the error: ModifyVirtualNetwork Failed: Existing address block is in use, c...Applies to NetApp SolidFire NetApp HCI NetApp Element Software Issue Attempt to modify start IP of the VLAN block fails with the error: ModifyVirtualNetwork Failed: Existing address block is in use, cannot remove. mID=x
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Broadcast_domain_unreachable_after_switch_suspends_VLANApplies to ONTAP 9 Virtual LAN (VLAN) Issue The following message is reported in EMS: vifmgr.reach.noreach:notice]: Network port e10a on node node1 cannot reach its expected broadcast domain Default:v...Applies to ONTAP 9 Virtual LAN (VLAN) Issue The following message is reported in EMS: vifmgr.reach.noreach:notice]: Network port e10a on node node1 cannot reach its expected broadcast domain Default:vlan1. No other broadcast domains appear to be reachable from this port On the switch, the following error is seen (or similar): %ETHPORT-3-IF_ERROR_VLANS_SUSPENDED: VLANs 1,2 on Interface port-channel1 are being suspended. (Reason: invalid argument to function call)
- https://kb.netapp.com/on-prem/ontap/Ontap_OS/OS-KBs/When_customer_creates_a_VLAN_for_IFGRP_ports_the_traffic_ceasesApplies to ONTAP 9.x Issue When creating an additional VLAN for IFGRP on port a0a and node 1, communication with the LIF's IP address fails. Deleting the VLAN causes communication (ping) to resume. An...Applies to ONTAP 9.x Issue When creating an additional VLAN for IFGRP on port a0a and node 1, communication with the LIF's IP address fails. Deleting the VLAN causes communication (ping) to resume. An interesting obsevation in the EMS log: the interface “vlan3”, a vlan which isn't present in the current network configuration on node 1: Tue Jan 31 00:07:30 -0800 [NetApp-Prod-01: nblade1: rlib.ifconfig.linkEvent:notice]: params: {'eventType': 'DOWN', 'ifname': 'vlan3'}
- https://kb.netapp.com/on-prem/solidfire/Element_OS_Kbs/How_to_check_the_assigned_VLAN_IP_address_of_each_storage_node_and_will_these_IP_be_changed_in_any_scenarioApplies to Element OS Answer Use the following API to check the IP address of each storage node. Example: https://mvip/json-rpc/8.0?method=Lis...ces&force=true The assigned IP information is stored in...Applies to Element OS Answer Use the following API to check the IP address of each storage node. Example: https://mvip/json-rpc/8.0?method=Lis...ces&force=true The assigned IP information is stored in the database and will not be changed except the reconfiguration or cluster corruption. Additional Information
- https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/VLAN_tagged_ports_are_in_different_broadcast_domains_with_auto_port_placement_in_ONTAPApplies to ONTAP 9.8 and later Issue VLAN tagged ports with the same VLAN ID are automatically added to different broadcast domains: cluster1::> network port broadcast-domain show IPspace Broadcast Up...Applies to ONTAP 9.8 and later Issue VLAN tagged ports with the same VLAN ID are automatically added to different broadcast domains: cluster1::> network port broadcast-domain show IPspace Broadcast Update Name Domain Name MTU Port List Status Details ------- ----------- ------ ----------------------------- -------------- Default-1 1500 cluster1-01:a0a-2304 complete Default-2 1500 cluster1-02:a0a-2304 complete
- https://kb.netapp.com/on-prem/ontap/DM/Encryption/Encryption-KBs/How_to_boot_ONTAP_from_an_external_Key_Management_KMIP_server_using_an_ifgrp_or_vlanFor ONTAP clusters using data-at-rest encryption such as NetApp Aggregate Encryption (NAE), NetApp Volume Encryption (NVE), NetApp Storage Encryption (NSE) or self-encrypting drives (SED), it is neces...For ONTAP clusters using data-at-rest encryption such as NetApp Aggregate Encryption (NAE), NetApp Volume Encryption (NVE), NetApp Storage Encryption (NSE) or self-encrypting drives (SED), it is necessary to contact the key manager during the boot process to unlock the encrypted aggregates, volumes, or drives.
- https://kb.netapp.com/on-prem/E-Series/Hardware-KBs/Only_one_port_is_responding_on_the_E-SeriesApplies to NetApp E-Series Issue After some switch maintenance only one iSCSI target port is responding to pings Other ports up however are not responding
- https://kb.netapp.com/Legacy/ONTAP/7Mode/Storage_systems_connected_to_a_Cisco_UCS_host_cannot_connect_or_ping_with_jumbo_frames_enabled_on_a_VLAN_tagged_interfaceWith the UCS interface configured as an access port and VLANs not configured on the storage system, all traffic operates as expected. With the UCS interface configured as a trunk port and VLAN interfa...With the UCS interface configured as an access port and VLANs not configured on the storage system, all traffic operates as expected. With the UCS interface configured as a trunk port and VLAN interfaces configured on the storage system: If this does not succeed, the connectivity problem is not related to the issue described by this article. If the issue is related to the issue described in this article, the ping should fail.
- https://kb.netapp.com/on-prem/ontap/ontap-select/Select-KBs/ONTAP_Select_Network_connectivity_Checker_quick_check_fails_on_new_deploymentWhen deploying a new ONTAP Select Cluster quick network connectivity checker fails with: Verify that the host is connected to at least one uplink in the 'up' state. Verify that the STP setting on the ...When deploying a new ONTAP Select Cluster quick network connectivity checker fails with: Verify that the host is connected to at least one uplink in the 'up' state. Verify that the STP setting on the physical switch is correct. The reccomended STP setting on the switch ports connected to the host host 'Edge/PortFast' If a cluster has been deployed and subsequently reconfigured outside of ONTAP Select Deploy, run a refresh operation on the cluster, and then try again.
- https://kb.netapp.com/on-prem/ontap/OHW/OHW-KBs/ifgrp_speed_reported_as_auto_-_after_ONTAP_upgrade"network port show" command displays the operation speed of the virtual ports ( VLAN / IFGRP) as "-" a0e Default Default up 1500 auto/- healthy a0e-1003 Default bd1 up 1500 auto/- healthy a0f Default ..."network port show" command displays the operation speed of the virtual ports ( VLAN / IFGRP) as "-" a0e Default Default up 1500 auto/- healthy a0e-1003 Default bd1 up 1500 auto/- healthy a0f Default Default up 1500 auto/- healthy a0f-1003 Default bd2 up 1500 auto/- healthy CLUSTER01::> network port show a0e Default Default up 1500 -/- healthy a0e-1003 Default bd1 up 1500 -/- healthy a0f Default Default up 1500 -/- healthy a0f-1003 Default bd2 up 1500 -/- healthy