Enabling Third Party SFP to use in Cisco Devices

You could faced with your Cisco Devices when you tried to use with non-cisco product third party SFP Module.
But I believe you will think about that SFP Module itself is not functioning properly or your Device Port is not functional at first time experience.

Well...it is not. Your Cisco Device will prompt you with below Log Message in the console.

%PHY-4-UNSUPPORTED_TRANSCEIVER: Unsupported transceiver found in Gi1/0/52
%GBIC_SECURITY_CRYPT-4-VN_DATA_CRC_ERROR: GBIC in port 65538 has bad crc

This log message says that the port attached with third party SFP Module just disabled.

So, we need to workaround to work that. Just need to type two commane line as below,

switch>configure terminal
switch(config)#service unsupported-transceiver
switch(config)#no errdisable detect cause gbic-invalid

You should see Warning Message after you key-in "service unsupported-transceiver " that prompt Cisco Warranty will not cover if you use Third Party SFP Module.

no errdisable detect cause gbic-invalid means you are telling to Devices that do not disable the Port for the use of Third Party SFP Module.

One more thing, you will not able to find the document in Help of Cisco for "service unsupported-transceiver".

Your IOS must be at 12.2(25)SE and later to use that command.

OK, done.

Be happy working with Third Party SFP Modules.

May you all be happy.
(Be knowledgeable, pass it on then)

Solving the "A general system error occured:Invalid fault" error in vSphere 4

Below error was come out when you try to migrate VM to other host for some reason.

Below error was come out when you try to edit VM setting.

Below error was come out when you power on the VM.

How to solve those error?

Here is how I resolve the error!

Login to the Host that errored VM exist by using Terminal or Direct Console.

Enter below command and press enter.
services.sh restart

Wait until all VMware Services are restarted.

After that try to Power On/Edit Settings or Migrate the errored VM and you will see all you can do without any error pop-up.

This kind of errors can occur if you shutdown/restart VM unproperly or shutdown/restart the Host unproperly that VM exist.

You can check log file deeply if you willing to know precisely on this.

May you all be happy.
(Be knowledgeable, pass it on then)

Moving VMware Host between Clusters

I've got 16 ESXi Server.

New 9 ESXi Servers (5 for Server Cluster and 4 for Workstation Cluster) running as production currently.
Old 7 ESXi Servers (5 for Server Cluster and 2 for Workstation Cluster) and Workstation Cluster is running as production currently. Server Cluster is for backup purpose.

One day I've to remove for 5 ESXi Servers of Server Cluster to make free space of Server Rack for new server increment setup.
But the problem is those old 7 ESXi Servers are located on two rack and some more is two servers from two clusters are located on separate RACK.
So, I've got to move those server to be in same rack and same cluster.

Below are my experience of moving VMs and Host between clusters for reference for who might encounter like me.

Moving host got two method.
1) moving vms from that host and moving the intended host from cluster to cluster by drag and drop with maintenance mode.
2) moving vms from that host and disconnect it from current cluster and re-connect to other cluster without going through maintenance mode. But this method more complicated and more steps to carry on than method 1.
So, I've used method 1 for easy going of my day to do this. But I'll write about method 2 also if got convenient time.

OK. Let's start!
First of all, moving running VMs to other host before entering to maintenace mode for the host that planning to move to other cluster.
Take a closer look at on Screen-shots for details.

Once all running VMs on that host moved, enter it to maintenance mode.

After the host into Maintenance Mode, select it and drag and drop to other cluster that you plan to move then.

Exit host from Maintenance Mode when moving to other cluster has successfully done.

That's it.

Now one host from Server Cluster to Workstation Cluster has been move successfully ( in my case moved from Rack 1 to Rack 2 also).

Next will be moving host from Workstation Cluster to Server Cluster.

OK. Hope you get what you expected from this post.

May you all be happy.
(Be knowledgeable, pass it on then)

How to change VMware Network Adapter Type from E1000 to VMXnet3?

Once I've migrate my vSphere 4 to 5, I got need to change some Server NIC from E1000 to VMXNET3 as they are not touched while migrating to avoid unnecessary issue and delay in project period.

But after migrated, I start noticed that some server like File Server, SAP or other server those need high user access definitely need to convert to VMXNET3 to get better performance.

So, I've decided to convert and follow is my steps in converting process.

That will be the easy guide for you too.

Actually, you will see two method to covert the adapter type.
- Shutdown the server and add new NIC. Uninstall old NIC and update NIC setting of old to New.
- Using VMware PowerCLI for live converting without touching server.

Here, I'm using second method, PowerCLI, to make conversion.

You need to download and install the VMware PowerCLI into your machine before start.

OK. Let's start now.
-          Check the Network Adapter Type and Adapter Number 1 or 2.
-          In this example, we are going to change Network Adapter 2 to VMXNET3 from E1000.

-          Check the Host where the Guest OS located on.
-          Here Guest OS “xxxx xxxx” is located on Host “xxxxesxi52”.

-          Open the VMware PowerCLI and key in “Connect-VIServer –Server hostname or ip address of host –Protocol https” without double quote to connect to the “Host”.

-          Key in username and password for “Host” to login.

-          You will see as below once you login successfully.
-          Host Server Name, Port Using and Login User.

-          Double check the network adapter by key in “Get-VM 'xxxx xxxx' |Get-Networkadapter” without double quote.

-          Key in “Get-VM  'xxxx xxxx' |Get-Networkadapter |Set-Networkadapter -type vmxnet3” without double quote to change adapter type.
-          You will be asked to perform the changing action with network adapter. Just choose “Yes” or “No” for correct network adapter number that you wish to change the adapter type.

-          You will see the new network adapter type as below if you change its type successfully without any errors.

-          Double confirm the network adapter type from Web Console or vSphere Client as below.

-          Cheer! You’ve done.

(You may google or search in VMware Website depends on version)

To read deepth about VMware Network Adapter Type, please go this link http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805

To read deepth about details instruction and requirement for VMXNET3, please go this link http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805

May you all be happy.
(Be knowledgeable, pass it on then)