phenergan cause diarrhea xyrem and provigil phenergan iv necrosis shot of phenergan phenergan and suboxone


vSphere 6.7 Configuration Maximums ESXi 6.7

VMware has updated some of the previous ESXi 6.5 maximums in the release of ESXi 6.7. Most of the usual CPU and memory specifications have stayed the same, but other changes are listed below.

For Example: Fault Tolerant VMs get another upgrade and can be now bumped to 8 vCPUs.

Virtual Machine Maximums 6.5 6.7
Persistent Memory – NVDIMM controllers per VM N/A 1
Persistent Memory – Non-volatile memory per virtual machine N/A 1024GB
Storage Virtual Adapters and Devices – Virtual SCSI targets per virtual SCSI adapter 15 64
Storage Virtual Adapters and Devices – Virtual SCSI targets per virtual machine 60 256
Networking Virtual Devices – Virtual RDMA Adapters per Virtual Machine N/A 1
ESXi Host Maximums 6.5 6.7
Fault Tolerance maximums – Virtual CPUs per virtual machine 4 8
Fault Tolerance maximums – RAM per FT VM 64GB 128GB
Host CPU maximums – Logical CPUs per host 576 768
ESXi Host Persistent Memory Maximums – Maximum Non-volatile memory per host N/A 1TB
ESXi Host Memory Maximums – Maximum RAM per host 12TB 16TB
Fibre Channel – Number of total paths on a server 2048 4096
Common VMFS – Volumes per host 512 1024
iSCSI Physical – LUNs per server 512 1024
iSCSI Physical – Number of total paths on a server 2048 4096
Fibre Channel – LUNs per host 512 1024
Virtual Volumes – Number of PEs per host 256 512

Tech Short: Enable SNMP on ESXi 6

Now that you are on or you have just started using VMware ESXi 6 and would like to do some monitoring via SNMP here is a way to enable this and set the community string in the process.

By default, remote clients are prevented from accessing services on host, unless configured to start automatically.

While you can simple set SNMP to start it does not set the community name and this is where we drop into the cli to do this.

Connect to the ESXi 6 host terminal or via SSH and issue the following commands:

esxcli system snmp set --communities public
esxcli system snmp set --enable true

By doing the following you have set the community strong value and started the service.



Quest to automate snapshots in ESXi

I am looking for a way to run a instance and have it revert back to its snapshot every 24 hours. I started toying around with the idea to use the vim-cmd features however there doesn’t seem to be a way to set a task for this.

So far here are the steps I used

Looked up the ID of the VM in question by running:

vim-cmd vmsvc/getallvms

View your VM’s snapshot tree by passing its ID to this command (this example uses the VM with ID 50):

vim-cmd vmsvc/get.snapshotinfo 80

And issues the command to revert the snapshot

vim-cmd vmsvc/snapshot.revert VM_ID 0 SNAPSHOT_ID suppressPowerOff


The output looks something like this in my testing

~ # vim-cmd vmsvc/getallvms
Vmid      Name                         File                         Guest OS       Version   Annotation
50     torproxy      [datastore3] torproxy/torproxy.vmx         ubuntu64Guest      vmx-08
56     workstation   [datastore3] workstation/workstation.vmx   windows8_64Guest   vmx-08
61     freepbx       [nfs] freepbx/freepbx.vmx                  centosGuest        vmx-08
66     webserver     [datastore3] webserver/webserver.vmx       ubuntu64Guest      vmx-08
~ # vim-cmd vmsvc/get.snapshotinfo 50
(vim.vm.SnapshotInfo) {
   dynamicType = <unset>,
   currentSnapshot = 'vim.vm.Snapshot:50-snapshot-7',
   rootSnapshotList = (vim.vm.SnapshotTree) [
      (vim.vm.SnapshotTree) {
         dynamicType = <unset>,
         snapshot = 'vim.vm.Snapshot:50-snapshot-7',
         vm = 'vim.VirtualMachine:50',
         name = "working",
         description = "",
         id = 7,
         createTime = "2014-12-16T01:27:35.7054Z",
         state = "poweredOn",
         quiesced = false,
         backupManifest = <unset>,
         replaySupported = false,
~ # vim-cmd vmsvc/snapshot.revert 50 7 suppressPowerOff
Revert Snapshot:
--Snapshot Name        : working
--Snapshot Id        : 7
--Snapshot Desciption  :
--Snapshot Created On  : 12/16/2014 1:27:35
--Snapshot State       : powered on

This works and now all I need is to somehow automate and schedule this.

Get the 3ware 9650SE working with ESXi 5.x

At the office we recently built two white box, built it yourself servers (lego’s). I called them Lego’s due to the fact they are build your own types and not OEM. For each of these powerhouse systems we got 3ware 9650SE RAID controllers (3ware 9650SE-4LPML PCI Express Lanes: 4 SATA II Controller Card RAID Levels 0, 1, 5, 10, Single Disk, JBOD, KIT).

After getting ESXi 5.x installed to a USB Stick to boot from I encountered an issue where the 3ware controller was not recognized by the system. Well this could only be one thing. Drivers.

This is where installing of the controller driver fun begins.

I first navigated to the LSI website and their support page to download the drivers for these controllers. Where I was able to find drivers for VMware ESXi 5.0 update 1 driver for 9650SE/9690SA

After downloading the zip archive of the driver, I extracted and used WinSCP to upload the drivers to the /tmp directory of my ESXi 5.x hosts.

I then logged into the ESXi 5.x using SSH with Putty.

After changing my directory to /tmp I ran the following command:

esxcli software vib install -v /tmp/scsi-3w-9xxx-

Soon after I got the following messages:

Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: LSI_bootbank_scsi-3w-9xxx_2.27.08.036-1OEM.500.0.0.472560
VIBs Removed:
VIBs Skipped:

After the install I followed the instruction to reboot and after the systems were up and running again I was able to see the controller and create my new data-stores.


Goodbye Configuration Issues Warning

So you are running VMware ESXi 5 and enabled remote and local shell access.
What you have found by doing this is a nice warning screen like the screenshot below waiting for you each and every time you are logged in.

Getting rid of this is simple.

Go to your host, click the configuration tab, click “advanced settings”, go to UserVars” and scroll all the way down to “UserVars.SuppressShellWarning” change the value from 0 to 1.