Hello, Following the update in 9.3 I no longer have access to system eat on but cluster. I have three bay 2 FAS 2600 and one AFF200 and I have the same behavior. It remains to the load even when doing F5. Have you ever encountered this problem in this or previous versions? I have tried several machines with several browsers even symptom. I rebooted two out of three berries and it's always the same. I have a ticket in progress at the support desk.
I am also having the same issue but it appears to be new requirements on the Netapp side that IE must match because it works from some Windows 2012 R2 servers' IE but not from others. Also if I try to access the logs area through the SPI URL (i.e. https://<clusterIP>/spi/) IE just hangs and never completes but I can get to teh SPI logs area though https for each node, just not the if using the cluster ip. I have a ticket open and a session scheduled with tech support tomorrow, but any other insights before could be helpful.
one thing i did notice is that third-party extensions allowed is enabled on the server that works but not the server that doesnt work; got a question out to tech support to see if that is now required in IE when 9.3 is installed.
So this was resolved by Technical Support for my issue. It turned out to be that in 9.2 and later FastPath is disabled, so the NAS will no longer route traffic internally. Here is the write-up from Tech Support:
HTTPS connectivity issues since the upgrade to Ontap 9.3
This issue is due to Fastpath being disabled in the Cluster. This means that previously, Fastpath would ignore the route table and just egress (go back out) the same lif the communication started on. This allowed the routing table to be relaxed and provided a handicap. Now with the feature disabled ALL routes are dependent on the route table to transmit traffic back out of the Nodes to your network.
Beginning with ONTAP 9.2, the networking stack is updated for improved performance and resiliency.
As part of the stack update, fastpath routing support was removed because it masked problems with improper routing tables. Hence, it is no longer possible to set the ip.fastpath.enable option in the nodeshell, and existing fastpath configurations are disabled when upgrading to ONTAP 9.2 and later.