Hi, thank you for the answer.
The Gui that I try to reach is the GUI that ONTAP Install suggest to open in order to complete the setup (http://192.168.77.10).
The network configuration is setup as described on ONTAP-Sim-Getting_Started_Quick:
IP from vmnet8: 192.168.77.10
Netmask: 255.255.255.0
Gateway: 192.168.77.2
But with username: admin and pwd: netapp!123 as in your guide described it says that the credentials are not correct:
However with this credentials I am able to log into the CLI:
And this ist the output of the command that you requested:
P.S. I started my post with "cannot access the GUI" because this is my problem, I cannot access/log into the GUI. Over the CLI I can create users, cluster and so on, but I am not able to log into the GUI.
Thanks in advance.
The IP space you're using is conflicting with existing IP allocation in your environment as the GUI presented is for the out of band management interface of some Cisco server. Also, I see .11, the cluster_mgmt LIF is hosted on e0a whereas .10, node_mgmt is on e0c. Typically under Fusion, both e0a and e0b are used for ClusterNet and the Fusion setting would be "host-only" and e0c/e0d are used for client access and by default set to "NAT" in Fusion. The CLI you're logging into is effectively the serial port of the simulator so IP addresses don't come into play. You likely can't ssh to either IP either because they're probably both assigned to external servers. I'd recommend changing IP spaces completely, try moving to 10.0.0.0/24. In the console, type:
net int modify -vserver ontap-test -lif cluster_mgmt -address 10.0.0.50 -netmask 255.255.255.0
net int modify -vserver ontap-test -lif ontap-test-01_mgmt1 -address 10.0.0.51 -netmask 255.255.255.0
Then in Fusion, make sure e0a/e0b is set to host-only and e0c/e0d is set to NAT, I use Bridged here so that I can access the simulator from other hosts as well, not just my laptop. Try connecting via https to either of the new IP addresses as well as ssh. I'm not sure why your cluster_mgmt is on e0a, but I assume it's because you set it to a single-node cluster, I don't do this specifically because I want the ClusterNet interfaces to still exist for better screenshots. Then you should be able to hit https://10.0.0.50/ and login.
Thank you for the instructions, but with this settings when I call https://10.0.0.50 in my browser no service/GUI is reachable.
It is not clear to me why should I use 10.0.0.0/24 space. As described on the official Docs it should be this provided by the vmnet8 adapter:
And the through the cluster management Ip it should be possible connect via ssh or https:
This is how the network configuration looks like (the Fusion settings are as you described):
.png){kind=link}