JarryG's Posts

I'm trying to tighten a little bit security of my solo ESXi 6.0 server by disabling unnecessary services/rules, so I want to disable firewall rule for vsanvp. But when I try it (using native clie... See more...
I'm trying to tighten a little bit security of my solo ESXi 6.0 server by disabling unnecessary services/rules, so I want to disable firewall rule for vsanvp. But when I try it (using native client), all I get is the message: Call "HostFirewallSystem.DisableRuleset" for object "firewallSystem" on ESXi "<my_esxi_IP>" failed. And Security Profile still shows I have allowed incomming/outgoing connections for vsanvp. vSphere 6.0 docu says: VSAN VASA Vendor Provider. Used by the Storage Management Service (SMS) that is part of vCenter to access information about Virtual SAN storage profiles, capabilities, and compliance. If disabled, Virtual SAN Storage Profile Based Management (SPBM) does not work. But I'm using neither vCenter nor virtual san-storage. So why I still can not disable firewall rule for vsanvp?
I would start with getting detailed info about your controller, arrays and disks (health-status on configuration tab is just a very rough overview). So install coresponding tool to ESXi-server. I... See more...
I would start with getting detailed info about your controller, arrays and disks (health-status on configuration tab is just a very rough overview). So install coresponding tool to ESXi-server. IIRC, PERC6 is using LSI-soc, so StorCLI from LSI/Avago should work too (then try "storcli /c0 show all" in esxi-console to get full status). Or use similar Dell-tool...
If you want to get alarms, you have to configure them. That's different story. But smis-provider definitely works. I can see controller-status (incl. all raid-arrays, disks, battery, etc) in hard... See more...
If you want to get alarms, you have to configure them. That's different story. But smis-provider definitely works. I can see controller-status (incl. all raid-arrays, disks, battery, etc) in hardware health tab of vSphere-client. Without smis-provider working (or installed) I could not see anything concerning LSI-controller...
Of course, it can not recognize this "array", because ESXi does NOT support software-/fake-/bios-/pseudo-raid (that's the "raid" you have on your motherboard). Only true hardware raid controllers... See more...
Of course, it can not recognize this "array", because ESXi does NOT support software-/fake-/bios-/pseudo-raid (that's the "raid" you have on your motherboard). Only true hardware raid controllers...
Manche DDR3-Speichermodule haben eine Nominalspannung 1.35V, dann waere es vollkommen in Ordnung. Schaue deine Speichermodule genau an (Marke, Modell) und kontrolliere beim Hersteller die Spezifi... See more...
Manche DDR3-Speichermodule haben eine Nominalspannung 1.35V, dann waere es vollkommen in Ordnung. Schaue deine Speichermodule genau an (Marke, Modell) und kontrolliere beim Hersteller die Spezifikation...
FYI, "apcupsd" is software very similar to APC's "PowerChute Network Shutdown", but it is free (open-source) and much more universal. It works not only with APC, but with many other UPS-models/ve... See more...
FYI, "apcupsd" is software very similar to APC's "PowerChute Network Shutdown", but it is free (open-source) and much more universal. It works not only with APC, but with many other UPS-models/vendors too: apcupsd | A daemon for controlling APC UPSes "NUT" (aka "Network UPS Tool") is another free (open-source) tool for UPS-management, but this one has one big advantage over the previous one: there is native client for ESXi, so there is no need to have one VM to connect to ESXi using login/password to shutdown ESXi-host: Network UPS Tools - Welcome
I did not try APC PCNS, but concerning other ways of handling UPS, there is "apcupsd", and "NUT" (which even has client vib-package for ESXi)...
LSI/Avago already released SMIS-provider for ESXi6 and it works well for me (ESXi 6.0 with OEM LSI9271 controller). Just do not forget to update drivers too (I'm using native one), because the on... See more...
LSI/Avago already released SMIS-provider for ESXi6 and it works well for me (ESXi 6.0 with OEM LSI9271 controller). Just do not forget to update drivers too (I'm using native one), because the one included in ESXi is quite old...
I do not think there is much to be supported on this or any SSD. Point is to have NVMe supported, because that is interface specification. If devices follow it, they are "supported". It is simila... See more...
I do not think there is much to be supported on this or any SSD. Point is to have NVMe supported, because that is interface specification. If devices follow it, they are "supported". It is similar as with traditional drives (and any other OS): you do not check if some particular hard-drive and model is supported. All you need is to have supported its interface, and controller...
But if it is not ESXi-service, then there is no port-conflict on ESXi-host. Why do you want to change port then? Now this is only my guess because you did not provide enough info about your netwo... See more...
But if it is not ESXi-service, then there is no port-conflict on ESXi-host. Why do you want to change port then? Now this is only my guess because you did not provide enough info about your network configuration: You are probably running some kind of router with public-IP, and you want to have management-port of your ESXi-host directly accessible from the "outside" (which btw is very bad idea and I strongly discourage you from doing it that way). And port 443 on your router's public IP is taken by that IPTV/VoIP-services. Am I right? *IF* it is so, then I do not see here any problem at all. Depending on your router/gateway just set up proper port/ip-forwarding (sometimes called "virtual server"), i.e. any connection to public IP of your router and port (let's say) 9000 will be translated/forwarded to local IP (of private address space) of your ESXi-host and its port 443. This is technically no problem, and any router can do it. It means, you would use alternate port on your router/gateway, but you need not to use alternate port on ESXi-host.
Just out of curiosity: how can you have port 443 used by "another service" on ESXi? I think this is hardly possible...
Definitely relevant information, even though not valid for ESXi 6. In the meantime, I "solved" this problem by using KVM-port of my server. Strangely, remote "keyboard" worked and works. But even... See more...
Definitely relevant information, even though not valid for ESXi 6. In the meantime, I "solved" this problem by using KVM-port of my server. Strangely, remote "keyboard" worked and works. But even after I finished installation, attached keyboard still does not work. And ESXi 6.0 does not have that file (/etc/modules.conf). So I still have no idea how to make local attached usb-keyboard work... Similar problem has been discussed in this thread, and surprisingly varnav's solution worked for me too: Keyboard Error. Keyboard not working at ESXi install screen.
No, I'm not that far. I'm talking about installation of ESXi, which I can not perform due to keyboard not working...
I'm having one strange problem: When I try to install esxi 6.0 on server (where I previously installed 5.0, 5.1 and 5.5), my usb-keyboard becomes dead and I can not continue. I mean, at the ve... See more...
I'm having one strange problem: When I try to install esxi 6.0 on server (where I previously installed 5.0, 5.1 and 5.5), my usb-keyboard becomes dead and I can not continue. I mean, at the very beginning when ESXi installation-CD boots and asks if I want to start ESXi-installer or boot from disk, it still works (arrow-keys, enter, etc). Then it goes further, loads various modules, and then it asks if I want to install ESXi. I press <Enter> but nothing happens. Switching NumLock On/Off shows that my keyboard is "dead". I tried to plug it out/in, still not working. I tried it once again with different keyboard, different usb-ports, it was all the same. How can I fix this?
It is sure not as loud and generates much less heat than my esxi-server and NAS. But I can not say a lot about it because I have it in 19" rack, together with all other equipment, all in separate... See more...
It is sure not as loud and generates much less heat than my esxi-server and NAS. But I can not say a lot about it because I have it in 19" rack, together with all other equipment, all in separate room. It takes about 30-40W, but at max switching capacity (~200Gbps) it would take more juice and generate more noise, that's for sure. It is not the best switch you can find, but I'd say price/performance ratio is in good ballance. It is comparable with Netgear models (i.e. Netgear ProSAFE Plus XS708E). Of course none of them is like Cisco 500-series, but that's different class, and to get something like SG500XG-8F8T you'd have to pay much more.
If you want to connect 3 esxi-hosts, then outside-work (maybe some NAS or whatever), than I definitely think it is worth to get switch. That's what switch is made for. I do not think that argumen... See more...
If you want to connect 3 esxi-hosts, then outside-work (maybe some NAS or whatever), than I definitely think it is worth to get switch. That's what switch is made for. I do not think that argument about price is so serious, you can get some entry-level 8-port 10gbit switch for less than 1k €/$. FYI, I'm using d-link dxs-1210-10ts (new for ~700€, 8x 10Gbase, 2x SFP+) and I think it is money well spent. Solution without switch is acceptable really only for direct connection between 2 hosts (as your original question was). With every new connection it is getting more and more complicated, and at the end you might pay more for all those NICs than for 10gbit switch...
Then you need 2 NICs in every host and connect all three hosts in triangular topology (every host with both of other two). Proper network configuration is necessary (ip/mask, routing, etc).
If you want to get rid of physical switch, simply do not use it. Use eth-cable to connect pNICs of those two ESXi-hosts directly. If your NICs have auto-mdi(x) capability, you do not need anythin... See more...
If you want to get rid of physical switch, simply do not use it. Use eth-cable to connect pNICs of those two ESXi-hosts directly. If your NICs have auto-mdi(x) capability, you do not need anything special. Some older NICs might still require crossover ethernet cable, but even this is not necessary with new hardware...
"...some examples when crash is not due to Windows issue?..." I think lost access to nfs-based datastore could be such an example...
I think it is safe to check it. It might help guest-OS in some cases to know it is running in virtual environment. Moreover, even if you did not expose this to guest, there are still many ways ho... See more...
I think it is safe to check it. It might help guest-OS in some cases to know it is running in virtual environment. Moreover, even if you did not expose this to guest, there are still many ways how guest could find it is running on virtual-hw...