It's a customer environment, so I don't know exactly what they have for monitoring tools. That is why I'm asking for the file who contains the source IP. and such failed login logs.
Hello everyone I got the following message every hour: "Remote access for ESXi local user account 'root' has been locked for 120 seconds..." I found a lot of information how to figure t...
See more...
Hello everyone I got the following message every hour: "Remote access for ESXi local user account 'root' has been locked for 120 seconds..." I found a lot of information how to figure this out: Security.AccountLockFailures. Maximum number of failed login attempts before a user’s account is locked. Zero disables account locking. Security.AccountUnlockTime. Number of seconds that a user is locked out. But I didn't get out where to find the source IP who is trying to access our ESXi hosts. Isn't it in /var/log/auth.log ? Thank you for your input.
Hi Shivam Thank you for the input, but seems to be strange. CLI output:
[root@ESX01:/var/log] esxcli network ip interface tag get -i vmk1
Tags: VMotion
[root@ESX01:/var/log] esxcli ne...
See more...
Hi Shivam Thank you for the input, but seems to be strange. CLI output:
[root@ESX01:/var/log] esxcli network ip interface tag get -i vmk1
Tags: VMotion
[root@ESX01:/var/log] esxcli network ip interface tag add -i vmk1 -t VSAN
[root@ESX01:/var/log] esxcli network ip interface tag get -i vmk1
Tags: VSAN, VMotion
But in the UI VSAN is still not enabled and I'm not able to configure VSAN.
vCenter needs to be at 6.5 -> OK All hosts at 6.5 -> OK Disable HA before enabling vSAN -> OK Create vSAN vmkernel ports prior to enabling vSAN -> OK Enable vSAN service on vSAN vmkernel -> ...
See more...
vCenter needs to be at 6.5 -> OK All hosts at 6.5 -> OK Disable HA before enabling vSAN -> OK Create vSAN vmkernel ports prior to enabling vSAN -> OK Enable vSAN service on vSAN vmkernel -> my issue, does not work on one host NIC assigned to vSAN vswitch (ideally vDS) (license - vDS included with vSAN) -> Actually it is a standard switch Minimum # of host for vSAN is 3 You will need a virtual Witness Appliance to do 1+1+1 cluster (2-node) -> Witness is ready or set FTT=0 (for Lab only, but still wouldn't do it this way) Alternatively you can use CLI from the host esxcli vsan cluster get I can't enable vsan until the vmkernel is set correctly.
Hi all I'm setting up vSAN in my own lab. I have 2 servers: 1 HP DL380 G7 and one G6. (I know that maybe not all components are on the HCL) but: I was able to activate vSAN Traffic on vmk1 ...
See more...
Hi all I'm setting up vSAN in my own lab. I have 2 servers: 1 HP DL380 G7 and one G6. (I know that maybe not all components are on the HCL) but: I was able to activate vSAN Traffic on vmk1 on the G7 server but if I enable it on the G6 server I only get a general system error during the refresh of the vsan configuration. I'm looking at vmkernel log and some vSAN logs, but I didn't get it out what's the problem. ESXi Version is 6.5. If someone has any ideas, let me know. Thank you Update 1: I'm able to activate all other services like vMotion, management, FT, etc. only vSAN fails. Update 2: Error Message: Task: Update Vsan Target: ha-host Initiator: VC Internal Result: Key: haTask--vim.host.VsanSystem.update-158810592 Description: Updates the Virtual SAN configuration for this host State: Failed - A general system error occurred:
Hi all Actually I have following issue: We have a vSphere 6 environment (for Horizon View 7) attached to an NetApp E-Series over iSCSI (software 10GbE). If we create linked clones, everythi...
See more...
Hi all Actually I have following issue: We have a vSphere 6 environment (for Horizon View 7) attached to an NetApp E-Series over iSCSI (software 10GbE). If we create linked clones, everything seems to be OK, but if I create full clones of a VM, sometimes it works, but sometimes I got an the Windows error "Operating System not found" if I boot the cloned VM. In the datastore I see all related files (VMX, VMDK, etc.). It happens only with full clones (at least until yet). So it could be something storage related or also a cloning issue with VMware. Do you have any advises or ideas? Regards Solero
