If you don't want to disable SNMP you can change the firewall on the ESX hosts so that allowed IP addresses are no longer "All". And then use that as a mitigation for your security report.
↧
Re: snmp
↧
Re: unable to unmount/delete datastore
Hello Jeff,
If scratch (or anything else) is indeed pointing to the device you are trying to remove then you can just point it to non-persistent locations such as [] /tmp/scratch as I suggested above.
Bob
↧
↧
Re: esxi maintenance mode communication error
Worked with VMware for the past couple months. They were not able to find what exactly is causing hostd and vsanmgmtd to crash. However, it seems that upgrading ESXi (and other prerequisite components) seems to have solved the issue.
I am using Dell servers.
I upgraded to:
Component Version Build
vCenter 6.7.0.20000 10244745
Intel X710 NIC Firmware 18.5.17
NIC Driver 1.7.1
HBA330 Driver 17.00.01.00
ESXi 6.7.0 11675023
I would have like to have known exactly what the cause was. It is probably the ESXi upgrade that fixed it. But that is just a theory.
Now to upgrade my second cluster.
Jeff
↧
Re: windows 10 1809 slow
Well, I know View 7.8 has released but I haven't had a lot of time to fully review all the release notes, but the highlights of this release do not appear to mention anything about Windows 10 performance (though again, I still need to review all the release notes).
I'm also curious to know if agent 7.8 will resolve the persona issues we've experienced since 7.5 released (where persona won't sync correctly, and keeps office applications from launching / other oddities on the VM).
↧
Re: windows 10 1809 slow
@nschilp This is a specific vsphere issue, any persona sync issues are different. You may want to post directly in the horizon sub forum about that.
↧
↧
Re: cannot find vsphere HA master agent
6.7 U1 build 10764712
↧
Re: Can't connect to Netgear readyshare on ESXi ver 6.7.0 (build 8169922)
So, a little update on all this. After researching some, it turns out that IE is the cause. I guess this is a known issue, that if using IE you can't upload anything over 4GB. I connected to my host using chrome and was able to upload the file I wanted.
↧
esxi 6.7.0 intall windows server 2016 login problem
I have a esxi 6.7.0 Update 1 (Build 10302608)，when I create a new windows server2016 Standard Edition，at the end of the install, the system restart and dispaly the Login interface,need press ctrl+alt+del to login,I use ctrl+alt+insert，click the esxi menu sent "ctrl+alt+del" to windows server2016,but there is no response,still let me to press ctrl+alt+del to login,I try to reintall windows server2016 Standard Edition,and used diffent edition,even intall windows server2019,still the same problem can not login,still ask me to press ctrl+alt+del to login, I pressed ctrl+alt+insert，click the esxi menu sent "ctrl+alt+del" to windows serve,still no response.
Please help me to see what is the reason and how to solve this problem. Thank you.
↧
Re: esxi 6.7.0 intall windows server 2016 login problem
I know this does not help but, I am running 6.7.0 Update 1 (Build 13004448) and I just built 4 2016 standard VMs... I have not seen this issue on any of these VMs... it works fine here. I am going to migrate from 2008 R2 to 2016...
Maybe upgrade ?
if you don't have vCenter and your a standalone ESX machine... this is the easiest way to update..
↧
↧
Re: Can't connect to Netgear readyshare on ESXi ver 6.7.0 (build 8169922)
Oops - sorry forgot to reply. Yes you are right that IE is limited on file upload sizes.
Glad you sorted that and have a great day!
↧
Re: cannot find vsphere HA master agent
This usually indicates that the kernel management ports are unable to communicate properly. They might for example have a firewall between them blocking some required ports or packets, or they might be setup on different subnets with no gateway or router to allow them to communicate.
In short the kernel ports need to be configured onto the same network.
↧
Re: cannot find vsphere HA master agent
↧
Re: Compiling drivers for the Aquantia AQC 10GB NICs
Hello,
i've tried the driver, attached here in ESXi 6.7 U1, card was recognized but i was not able to get vmnic up and running.
However, i've contacted Aquantia directly
They have "official" test driver here:
Releases · Aquantia/AQtion-esxi · GitHub
I've already install the driver, everything works very well so far.
Hope this helps.
Greetings!
↧
↧
Re: vmkfstools --growfs returning Error: No such file or directory
Sure that's a very old thread, but I've hit same problem in 2019 with ESXi 6.5. Increased RAID array with datastore, then increased the partition with partedUtil, and got stuck with "vmkfstools --growfs" reporting "No such file or directory". I've tried passing device name (disk:partition) with and without quotes, tried using different path - /vmfs/devices/disks/... and /dev/disks/..., rebooted host, dismounted and resignatured the datastore - all to no success. GUI wasn't helpful either, it was showing an empty list of devices when I was trying to increase my single existing datastre extent. And then finally what worked was using a relative partition name, without path!
cd /dev/disks
vmkfstools --growfs naa....:1 naa...:1
(My disk name starts from "naa...") And it magically succeeded. No idea why - maybe vmkfstools has some bug in device path buffer allocation or parsing, or something else.
↧
Re: Is there still a free version of ESXI that is not just a trial for 60 Days?
What I think the OP is saying, is they, like myself, click on the link above and click on the blue register button, we are brought to a screen saying:
Content Not Available
Dear user, the web content you have requested is not available.
We cannot register for the product because the page is dead or something, and cannot therefore get a key.
Additionally, I have tried twice to contact sales/support via their web form, both times getting messages stating it was successfully sent, but haven't heard anything. It doesn't even send an autoreply to your mail to indicate they received it. Like the user above, time, as they say is ticking. I too am a home user, dabbling in some server operating systems. In my case (which makes me worry more) I'm running ESXi 6.0 (not 6.7) because that is what the version created for my server (Dell Poweredge R710) needed to run. Hopefully someone will come along and fix the registration portion of the site, or be able to help us here in the forum.
↧
Re: Pink Screen on 6.7 Updates - Why?
Hello,
The possible solution was reported in another thread:
ESXi 6.7u1 RMRR overlaps system memory
The short answer is that it seems that you need to update BIOS to the latest version or disable Intel VT for directed I/O in the current BIOS version.
↧
Re: Datastores disappeared after a reboot
Please see whether the LUN has been detected as a snapshot LUN, and if mounting the datastore manually will work.
see the "Command line" section at https://kb.vmware.com/kb/1011387
André
↧
↧
Re: Datastores disappeared after a reboot
Nope.
# esxcli storage vmfs snapshot list
#
When looking at existing partitions, only the USB one is listed:
# esxcli system coredump partition list
Name Path Active Configured
---------------------- ------------------------------------------ ------ ----------
mpx.vmhba32:C0:T0:L0:7 /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0:7 false true
↧
Re: Deploy Error : A required disk image was missing.
I had the same issue and it turned out to be the ISO image attached via the emulated CD/ROM
↧
Re: Datastores disappeared after a reboot
#offset="128 2048"; for dev in `esxcfg-scsidevs -l | grep "Console Device:" | awk {'print $3'}`; do disk=$dev; echo $disk; partedUtil getptbl $disk; { for i in `echo $offset`; do echo "Checking offset found at $i:"; hexdump -n4 -s $((
0x100000+(512*$i))) $disk; hexdump -n4 -s $((0x1300000+(512*$i))) $disk; hexdump -C -n 128 -s $((0x130001d + (512*$i))) $disk; done; } | grep -B 1 -A 5 d00d; echo "---------------------"; done
/vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
gpt
243 255 63 3913728
1 64 8191 C12A7328F81F11D2BA4B00A0C93EC93B systemPartition 128
5 8224 520191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
6 520224 1032191 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
7 1032224 1257471 9D27538040AD11DBBF97000C2911D1B8 vmkDiagnostic 0
8 1257504 1843199 EBD0A0A2B9E5443387C068B6B72699C7 linuxNative 0
---------------------
/vmfs/devices/disks/naa.600605b009617b801cfe4186271b2743
gpt
243133 255 63 3905945600
1 2048 3905945566 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
Checking offset found at 2048:
0200000 d00d c001
0200004
1400000 f15e 2fab
1400004
0140001d 64 69 73 6b 32 00 00 00 00 00 00 00 00 00 00 00 |disk2...........|
0140002d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
---------------------
/vmfs/devices/disks/naa.600605b009617b801cfe4186271b7c33
gpt
364733 255 63 5859442688
1 2048 5859442654 AA31E02A400F11DB9590000C2911D1B8 vmfs 0
Checking offset found at 2048:
0200000 d00d c001
0200004
1400000 f15e 2fab
1400004
0140001d 64 69 73 6b 31 00 00 00 00 00 00 00 00 00 00 00 |disk1...........|
0140002d 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
---------------------
# fdisk -l /dev/disks/naa.600605b009617b801cfe4186271b2743
***
*** The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil
***
Found valid GPT with protective MBR; using GPT
Disk /dev/disks/naa.600605b009617b801cfe4186271b2743: 3905945600 sectors, 3725M
Logical sector size: 512
Disk identifier (GUID): ffa051fd-46a5-4151-a6d3-b62a3a5b9ec0
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 3905945566
Number Start (sector) End (sector) Size Code Name
1 2048 3905945566 3724M 0700
#fdisk -l /dev/disks/naa.600605b009617b801cfe4186271b7c33
***
*** The fdisk command is deprecated: fdisk does not handle GPT partitions. Please use partedUtil
***
fdisk: device has more than 2^32 sectors, can't use all of them
Found valid GPT with protective MBR; using GPT
Disk /dev/disks/naa.600605b009617b801cfe4186271b7c33: 4294967295 sectors, 4095M
Logical sector size: 512
Disk identifier (GUID): cd7dd043-9548-4f87-bba7-9b900622d9e4
Partition table holds up to 128 entries
First usable sector is 34, last usable sector is 5859442654
Number Start (sector) End (sector) Size Code Name
1 2048 5859442654 5587M 0700
# esxcli storage core path list
usb.vmhba32-usb.0:0-mpx.vmhba32:C0:T0:L0
UID: usb.vmhba32-usb.0:0-mpx.vmhba32:C0:T0:L0
Runtime Name: vmhba32:C0:T0:L0
Device: mpx.vmhba32:C0:T0:L0
Device Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)
Adapter: vmhba32
Channel: 0
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: usb
Adapter Identifier: usb.vmhba32
Target Identifier: usb.0:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 122880
unknown.vmhba2-unknown.2:1-naa.600605b009617b801cfe4186271b7c33
UID: unknown.vmhba2-unknown.2:1-naa.600605b009617b801cfe4186271b7c33
Runtime Name: vmhba2:C2:T1:L0
Device: naa.600605b009617b801cfe4186271b7c33
Device Display Name: Local LSI Disk (naa.600605b009617b801cfe4186271b7c33)
Adapter: vmhba2
Channel: 2
Target: 1
LUN: 0
Plugin: NMP
State: active
Transport: parallel
Adapter Identifier: unknown.vmhba2
Target Identifier: unknown.2:1
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 131072
unknown.vmhba2-unknown.2:0-naa.600605b009617b801cfe4186271b2743
UID: unknown.vmhba2-unknown.2:0-naa.600605b009617b801cfe4186271b2743
Runtime Name: vmhba2:C2:T0:L0
Device: naa.600605b009617b801cfe4186271b2743
Device Display Name: Local LSI Disk (naa.600605b009617b801cfe4186271b2743)
Adapter: vmhba2
Channel: 2
Target: 0
LUN: 0
Plugin: NMP
State: active
Transport: parallel
Adapter Identifier: unknown.vmhba2
Target Identifier: unknown.2:0
Adapter Transport Details: Unavailable or path is unclaimed
Target Transport Details: Unavailable or path is unclaimed
Maximum IO Size: 131072
# esxcli storage core device list
naa.600605b009617b801cfe4186271b7c33
Display Name: Local LSI Disk (naa.600605b009617b801cfe4186271b7c33)
Has Settable Display Name: true
Size: 2861056
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/naa.600605b009617b801cfe4186271b7c33
Vendor: LSI
Model: MR9240-4i
Revision: 2.13
SCSI Level: 5
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: false
Is SSD: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unsupported
Other UIDs: vml.0200000000600605b009617b801cfe4186271b7c334d5239323430
Is Local SAS Device: false
Is USB: false
Is Boot USB Device: false
No of outstanding IOs with competing worlds: 32
mpx.vmhba32:C0:T0:L0
Display Name: Local USB Direct-Access (mpx.vmhba32:C0:T0:L0)
Has Settable Display Name: false
Size: 1911
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/mpx.vmhba32:C0:T0:L0
Vendor: General
Model: USB Flash Disk
Revision: 1.00
SCSI Level: 2
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: true
Is SSD: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unsupported
Other UIDs: vml.0000000000766d68626133323a303a30
Is Local SAS Device: false
Is USB: true
Is Boot USB Device: true
No of outstanding IOs with competing worlds: 32
naa.600605b009617b801cfe4186271b2743
Display Name: Local LSI Disk (naa.600605b009617b801cfe4186271b2743)
Has Settable Display Name: true
Size: 1907200
Device Type: Direct-Access
Multipath Plugin: NMP
Devfs Path: /vmfs/devices/disks/naa.600605b009617b801cfe4186271b2743
Vendor: LSI
Model: MR9240-4i
Revision: 2.13
SCSI Level: 5
Is Pseudo: false
Status: on
Is RDM Capable: false
Is Local: true
Is Removable: false
Is SSD: false
Is Offline: false
Is Perennially Reserved: false
Queue Full Sample Size: 0
Queue Full Threshold: 0
Thin Provisioning Status: unknown
Attached Filters:
VAAI Status: unsupported
Other UIDs: vml.0200000000600605b009617b801cfe4186271b27434d5239323430
Is Local SAS Device: false
Is USB: false
Is Boot USB Device: false
No of outstanding IOs with competing worlds: 32
↧