By default, the “ssh” command does not exist in VMware ESXi 4.1.
To create it, login as root and execute the following command:
ln -s /sbin/dropbearmulti /bin/ssh
SSH Client in ESXi
VMware ESX 4.0 to 4.1 Upgrade Error
When updated VMware ESX 4.0 to 4.1:
Host was not updated, no changes required.
Skipping bulletin ESX410-GA-esxupdate; it is installed or obsoleted.
Encountered error RunCommandError:
This is an unexpected error. Please report it as a bug.
Error Message – Command ‘[‘/usr/bin/vim-cmd’, ‘hostsvc/runtimeinfo’]’
terminated due to signal 6
Simply type: ldconfig
[ad#Google Adsense]vCenter 4.1 “No 64Bit DSN Found” DSN Error on Windows 2008 R2 Server
This error will appear when attempting to install VMware vCenter 4.1.
A work around for this issue is to create a system DSN.
Then open regedt32 on the server and go to HKLM > Software > ODBC.INI >
Update its driver to: C:WINDOWSsystem32sqlncli10.dll.
Restart the vCenter install.
Shrink Postgres Tables / Databases
psql
With psql cli:
vacuum full;
also do:
reindex
Set-ExecutionPolicy : Access to the registry key ‘HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\PowerShell\1\ShellIds\Microsoft.PowerShell’ is denied.
When running VMware PowerShell CLI you receive this error:
Set-ExecutionPolicy : Access to the registry key ‘HKEY_LOCAL_MACHINESOFTWAREMicrosoftPowerShell1ShellIdsMicrosoft.PowerShell’ is denied.
Right click powercli and click: “Run As Administrator”
Once powershell starts type this command:
Set-ExecutionPolicy RemoteSigned
IPTABLES Tidbits
List off all the rules in order. This helps to see if an allow is overriding one of your denies:
iptables -nvL –line-numbers
Reject or Drop?
Drop means to drop everything at the interface and give no response. Best for port probes and the like.
Reject responds to the source. Best practices for TCP/IP
NetApp “Broken Drives” Simulator
Mon Nov 29 17:38:05 PST [raid.assim.disk.nolabels:error]: Disk 0b.18 Shelf 1 Bay 2 [NETAPP X274_HPYTA146F10 NA03] S/N [V5Y692RA] has no valid labels. It will be taken out of service to prevent possible data loss.
You will receive a message similar to the above on the simulator.
Type these commands in the shell:
priv set diag
disk unfail -s v4.29
Malware Protection Designed To Protect
This is scumbag malware designed to take your machine hostage until you pay.
Here is the -quickest- way to eliminate this tediosity:
1. Register the scumware using this serial number: SL55J-T54YHJ61-YHG88
Once this is done it will allow you to now use your computer.
2. Open explorer and delete: C:Documents and SettingsAll UsersApplication Datadefender.exe
If the file is not there, search for: defender.exe and delete it.
3. Download SpyBot Search & Destroy and run it on your machine: http://www.safer-networking.org/en/download/
FreeBSD ZFS Settings On i386 Hardware
AMD64 Kernel FreeBSD machines are good about autotuning. i386, on the other hand, needs to be adjusted manually.
1. Rebuild your kernel
a. Disable/wipe all drivers you are not using or at least those you are highly unlikely to ever use.
b. Add: options KVA_PAGES=512
c. Recompile/Install new kernel
2. Add these parameters to /boot/loader.conf
a. vm.kmem_size=”1024M”
b. vm.kmem_size_max=”2048M”
c. vfs.zfs.arc_max=”256M”
d. vfs.zfs.vdev.cache.size=”40M”
This will get the machine online without it crashing with vm.kmem errors. ZFS will bring an untuned i386 machine down to its knees with kernel panics quickly!
Adjust the above variables to your tastes. My test platform is a Dual Xeon with 4GB of RAM.
FreeBSD LAGG rc.conf
This is what your rc.conf should contain to configure LAGG with FreeBSD:
### LAGG NFS Interface ###
ifconfig_bce3=”mtu 9000 up”
ifconfig_bce0=”mtu 9000 up”
cloned_interfaces=”lagg0″
ifconfig_lagg0=”laggproto roundrobin laggport bce3 laggport bce0″
ipv4_addrs_lagg0=”10.10.40.10/24″
Change the bce* interfaces to whatever your server is using for the network interfaces.
The “mtu 9000 up” is correct!