Archive for June 30, 2012

| June 30, 2012
No comments

VMware ESXi Total Lockdown

I assume that you already know what Lockdown Mode is. With Lockdown Mode enabled ESXi server, you will need to use vCenter to Administrator ESXi Server therefore you can enforce centrally managed permission control via vCenter Server, rather than configuring and managing permissions at each ESXi Server.

When Lockdown Mode is configured on ESXi server, vCenter Server has to be highly available as Loss of vCenter Server makes your ESXi Server unmanageable. Luckily you have a workaround. if your vCneter Server goes down, and need to access ESXi Server, then you can login to DCUI (Direct Console User Interface) of ESXi Server to disable Lockdown Mode.

Read more

Category: VMware Blog | Tags: , , ,
| June 24, 2012
No comments

GVT Guest VLAN Tagging using vNetwork Standard Switch

VMware supports VLAN tagging by Virtual Machines, this feature is called a guest VLAN tagging. GVT support depends on a Guest OS installed. Some OSs support VLAN tagging natively as long as NIC driver is available. Others require NIC driver for vNIC. VMXNET3 driver for Windows support VLAN tagging from Guest OS, so you can insert VLAN ID.

This is what I want to achieve here. I want to configure standard vNetwork Switch to have VLAN 2001 and 2002 and VMs in each VLANs to communicate each other.

image

VMware network configuration

Read more

Category: VMware Blog | Tags: , , , ,
| June 23, 2012
No comments

Mac OSX SSH Host key verification failed

I had a situation when I tried to SSH into one of the server, I received the error message below. Basically the server had generated a new SSH RSA host key that doesnt match with the old one stored on my MacBook Pro.

;

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
 Someone could be eavesdropping on you right now (man-in-the-middle attack)!
 It is also possible that the RSA host key has just been changed.
 The fingerprint for the RSA key sent by the remote host is
 21:79:38:2d:2c:3d:f0:08:5d:e5:a6:a0:3f:af:a1:0a.
 Please contact your system administrator.
 Add correct host key in /Users/root/.ssh/known_hosts to get rid of this message.
 Offending key in /Users/root/.ssh/known_hosts:7
 RSA host key for x.x.x.x has changed and you have requested strict checking.
 Host key verification failed.

;

Read more

Category: General Blog |
 
Follow

Get every new post on this blog delivered to your Inbox.

Join other followers: