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 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.
Applies to SolidFire Element Upgrade Issue After upgrading Element on a SolidFire cluster and attempting to “re-enable” the VLAN ID on the BMC (IPMI), an error is displayed showing it failed to set th...Applies to SolidFire Element Upgrade Issue After upgrading Element on a SolidFire cluster and attempting to “re-enable” the VLAN ID on the BMC (IPMI), an error is displayed showing it failed to set the VLAN. Failed to set VLAN status Example:
Applies to SolidFire Element Upgrade Issue If a VLAN ID is used on a BMC (IPMI) of an H500S / H700S / H410S, the VLAN ID must be disabled prior to upgrading Element OS or the firmware upgrade will fai...Applies to SolidFire Element Upgrade Issue If a VLAN ID is used on a BMC (IPMI) of an H500S / H700S / H410S, the VLAN ID must be disabled prior to upgrading Element OS or the firmware upgrade will fail, resulting in a corrupted node that will most likely need to be replaced.
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