Welcome to VMware Communities !
SSH is disabled by default on Skyline Appliance. We can enable SSH by following the steps mentioned below
- Open the Skyline Collector console via the vSphere Client/Web Client
- Login as root and the root password defined during deployment
- Run 'vi /etc/ssh/sshd_config'
- Enter 'i' to modify the file in VI editor
- Locate the line that contains 'PermitRootLogin no' and change the value to 'PermitRootLogin yes'
- Save the changes by hitting ESC + typing ':wq!'
- Restart the sshd service by running 'service sshd restart'
Please check the network configuration using the following KB article
Please share the information requested in the following link if the problem persists
This is not the correct answer if you read my statement I am not even able to ping the default gateway on a ip6 only configuration.
I have a few questions to understand the issue further:
1) Please check the output of '/opt/vmware/share/vami/vami_config_net' from the Appliance shell and verify if the network configuration is correct.
2) Do you have any other VM on the same vSwitch/PortGroup/ESXi using IPv6 only?
3) Do you have any other VM the same vSwitch which can reach the IPv6 gateway?
4) What is the version of vCenter and ESXi running the Skyline Appliance?
Please share your contact details on the following link and let me know a convenient time to contact you:
1. the conifurations output looks the same as one of my vcenters.
4. Vcenter 6.7u3 esxi 6.7u2
- Can you please check if you are able to get a response from the Collector Appliance when you initiate a ping from the VM on the same vSwitch, this should confirm any issue with Layer 2 connectivity.
- Also please check '/opt/vmware/etc/lighttpd/lighttpd.conf' on the collector make sure "server.use-ipv6" is set to ”enabled”.
- It could also be an issue at the Appliance OS level, try to redeploy the collector once from a fresh source.
If the issue persists please share your contact details, we will need to work over a remote session.
I have vrops and vcenter running on the same vlan and same host with out any issues.
I did check the setting you ask and it is enabled
I also have deployed 2.1 version and 2.2 both have the same issue.
I will ping you my direct contact information
Able to get ipv6 working for communication. The issue is with the ip6tables rules, it was not configured to allow input.
It can be fixed by running the following command on the shell:
#Ip6tables -P INPUT ACCEPT.
Yeah i found that over a month ago and gave it to support. Along with having to run a dual stack for the ip needed to connect to the external services.