Put something like this in your Post-Script Log to central syslog server esxcfg-firewall -o 514,udp,out,syslog echo "" >>/etc/syslog.conf echo "# Send everything to c...
See more...
Put something like this in your Post-Script Log to central syslog server esxcfg-firewall -o 514,udp,out,syslog echo "" >>/etc/syslog.conf echo "# Send everything to central syslog server" >>/etc/syslog.conf echo ". @192.168.1.1" >>/etc/syslog.conf service syslog restart
As far as I know, there is no way to rename a portgroup. Be it with esxcfg-vswif/vswitch or with vmware-vim-cmd. However deleting and adding it with the new name should do the trick for you. ...
See more...
As far as I know, there is no way to rename a portgroup. Be it with esxcfg-vswif/vswitch or with vmware-vim-cmd. However deleting and adding it with the new name should do the trick for you. The addvmportgroup option in kickstart can be 0 or 1. It tells the setup to either add a default portgroup for virtual machines called "VM Network" on the first vSwitch or not. It has nothing to do with the Service Console portgroup naming.
On your ESX host with VI Client: Configuration > Storage ... double click your datastore (where the template is), right click on the .vmtx file and "Add to inventory".
The gateway is only pinged to check if the host is isolated (= has no network connectivity), but this starts only when it stops receiving heartbeats from the other hosts in the cluster. As you ha...
See more...
The gateway is only pinged to check if the host is isolated (= has no network connectivity), but this starts only when it stops receiving heartbeats from the other hosts in the cluster. As you have your service consoles probably on the same subnet, they would talk even with a dead GW.
I think the issue you are seeing is because you created one VM with VC1 and the other VM with VC2. Virtual Center has a particular MAC address range. Potentially two Virtual Center servers simpl...
See more...
I think the issue you are seeing is because you created one VM with VC1 and the other VM with VC2. Virtual Center has a particular MAC address range. Potentially two Virtual Center servers simply give out the same. Avoid this problem, by creating all new VMs always on the same VC, unregister it and hand it over to the other VC if required. Or maybe better, rethink your concept and end up with one single VC for both infrastructures.
Virtual Center is sometimes not up to date when you recently changed something cause some information (for exmaple your disk size) is pulled not so frequently from the ESX hosts. If you ne...
See more...
Virtual Center is sometimes not up to date when you recently changed something cause some information (for exmaple your disk size) is pulled not so frequently from the ESX hosts. If you need the most current information, go to the ESX host directly and check on the COS. You can trigger VCs collection process by restarting the vpxa and mgmt agent: service mgmt-vmware restart service vmware-vpxa restart
A restart of the VC agent should trigger the new values to appear in VC. service vmware-vpxa restart The sure and most current value can be seen with vdf -h on the console. ...
See more...
A restart of the VC agent should trigger the new values to appear in VC. service vmware-vpxa restart The sure and most current value can be seen with vdf -h on the console.
Maybe, but the proper way would be to stick with the 2.0.1 agent if you are running 2.0.1 VC. So in the case your upgrade fails, uninstall the new agent: rpm -qa | grep vpxa You...
See more...
Maybe, but the proper way would be to stick with the 2.0.1 agent if you are running 2.0.1 VC. So in the case your upgrade fails, uninstall the new agent: rpm -qa | grep vpxa You should get something like "VMware-vpxa-2.0.2-xxxxx" then do service vmware-mgmt stop rpm -e "VMware-vpxa-2.0.2-xxxxx" Then add the ESX host back to your VC, this will install the matching VC agent for your VC build.
HA kicks in, when the ESX host doesnt respond anymore. At this stage you wont have VC and its functions anymore until the VC-VM will be fired up on another host, yes.
Yeah, good way to start. There are also some scripts that you will find here in the forum. Or the very well done VMTS Patch Manager, worth to check out imho. http://www.vmts.net/VMTSPatchManag...
See more...
Yeah, good way to start. There are also some scripts that you will find here in the forum. Or the very well done VMTS Patch Manager, worth to check out imho. http://www.vmts.net/VMTSPatchManager.htm
You can't open a range (34570-34580) instead to port by port like esxcfg-firewall -o 34570,in,tcp,ServeRaid esxcfg-firewall -o 34571,in,tcp,ServeRaid esxcfg-firewall -o 34572,in,tcp,ServeRai...
See more...
You can't open a range (34570-34580) instead to port by port like esxcfg-firewall -o 34570,in,tcp,ServeRaid esxcfg-firewall -o 34571,in,tcp,ServeRaid esxcfg-firewall -o 34572,in,tcp,ServeRaid ...
Hi Magnus, That's no Problem: Configuration > Storage ... right click on the datastore where your Vms are and "Browse Datastore ...". Right click on the vmx file, "Add to inventory". cheer...
See more...
Hi Magnus, That's no Problem: Configuration > Storage ... right click on the datastore where your Vms are and "Browse Datastore ...". Right click on the vmx file, "Add to inventory". cheers, cheeko Message was edited by cheeko to remove some good-morning-typos ...
Here's an easy "trick" to rename a VM inlcluding all related files/folders: http://virtrix.blogspot.com/2007/04/vmware-handy-trick-to-rename-virtual.html