Sysxp's Accepted Solutions

I found why it was not working as it should on a Cisco forum - someone had the exact same problem. And the issue is: the default GW for the PCs or VMs in Vlan1 must be the ip of the cisco router that... See more...
I found why it was not working as it should on a Cisco forum - someone had the exact same problem. And the issue is: the default GW for the PCs or VMs in Vlan1 must be the ip of the cisco router that does all Vlan routing (in my case 192.168.255.250). After setting the correct GW everything begin to work as intended. Thank you Kinnison! Your initial assumption about incorrect network settings was somewhat right.
Ok, I found an answer myself, this time it was easy enough. After logging into VCSA Management in search for logs I eventually found that time in VCSA is completely "stuck". Time synchronizatio... See more...
Ok, I found an answer myself, this time it was easy enough. After logging into VCSA Management in search for logs I eventually found that time in VCSA is completely "stuck". Time synchronization mode was set to "Host" and it was working good, until it completely stops for some unknown reason. After changing mode to "NTP" time begins to flow again, and now we have some noticeable gap in readings: So, it is probably best not to use the "host" sync mode for VCSA because strange things may happen. P.S. I checked the time on the host and it was fine. So, time stops going only for VCSA, but not for the host.