Youry's Blog

Youry's Blog

Archive for February 2014

VMWare Ethernet choosing

leave a comment »

Choosing a network adapter for your virtual machine (1001805)

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1001805

Details

Network adapter choices depend on the version number and the guest operating system running on the virtual machine. This article discusses the different network adapter options available for virtual machines.

For more information on network types, see Understanding networking types in hosted products (1006480).

Solution

Available Network Adapters

Only those network adapters that are appropriate for the virtual machine you are creating are available configuration options in the Choose Networks window.

  • Vlance: This is an emulated version of the AMD 79C970 PCnet32- LANCE NIC, and it is an older 10 Mbps NIC with drivers available in most 32-bit guest operating systems except Windows Vista and later. A virtual machine configured with this network adapter can use its network immediately.
  • VMXNET: The VMXNET virtual network adapter has no physical counterpart. VMXNET is optimized for performance in a virtual machine. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET network adapter available.
  • Flexible: The Flexible network adapter identifies itself as a Vlance adapter when a virtual machine boots, but initializes itself and functions as either a Vlance or a VMXNET adapter, depending on which driver initializes it. With VMware Tools installed, the VMXNET driver changes the Vlance adapter to the higher performance VMXNET adapter.
  • E1000: An emulated version of the Intel 82545EM Gigabit Ethernet NIC. A driver for this NIC is not included with all guest operating systems. Typically Linux versions 2.4.19 and later, Windows XP Professional x64 Edition and later, and Windows Server 2003 (32-bit) and later include the E1000 driver.

    Note: E1000 does not support jumbo frames prior to ESXi/ESX 4.1.

  • E1000e: This feature emulates a newer model of Intel Gigabit NIC (number 82574) in the virtual hardware. This is known as the “e1000e” vNIC. e1000e is available only on hardware version 8 (and newer) virtual machines in vSphere 5. It is the default vNIC for Windows 8 and newer (Windows) guest operating systems. For Linux guests, e1000e is not available from the UI (e1000, flexible vmxnet, enhanced vmxnet, and vmxnet3 are available for Linux).
  • VMXNET 2 (Enhanced): The VMXNET 2 adapter is based on the VMXNET adapter but provides some high-performance features commonly used on modern networks, such as jumbo frames and hardware offloads. This virtual network adapter is available only for some guest operating systems on ESXi/ESX 3.5 and later. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET 2 network adapter available.

    VMXNET 2 is supported only for a limited set of guest operating systems:

    • 32- and 64-bit versions of Microsoft Windows 2003 (Enterprise, Datacenter, and Standard Editions).

      Note: You can use enhanced VMXNET adapters with other versions of the Microsoft Windows 2003 operating system, but a workaround is required to enable the option in the VMware Infrastructure (VI) Client or vSphere Client. If Enhanced VMXNET is not offered as an option, see Enabling enhanced vmxnet adapters for Microsoft Windows Server 2003 (1007195).

    • 32-bit version of Microsoft Windows XP Professional
    • 32- and 64-bit versions of Red Hat Enterprise Linux 5.0
    • 32- and 64-bit versions of SUSE Linux Enterprise Server 10
    • 64-bit versions of Red Hat Enterprise Linux 4.0
    • 64-bit versions of Ubuntu Linux

    In ESX 3.5 Update 4 or higher, these guest operating systems are also supported:

    • Microsoft Windows Server 2003, Standard Edition (32-bit)
    • Microsoft Windows Server 2003, Standard Edition (64-bit)
    • Microsoft Windows Server 2003, Web Edition
    • Microsoft Windows Small Business Server 2003

    Note: Jumbo frames are not supported in the Solaris Guest OS for VMXNET 2.

  • VMXNET 3: The VMXNET 3 adapter is the next generation of a paravirtualized NIC designed for performance, and is not related to VMXNET or VMXNET 2. It offers all the features available in VMXNET 2, and adds several new features like multiqueue support (also known as Receive Side Scaling in Windows), IPv6 offloads, and MSI/MSI-X interrupt delivery. For information about the performance of VMXNET 3, see Performance Evaluation of VMXNET3 Virtual Network Device. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET 3 network adapter available.

    VMXNET 3 is supported only for virtual machines version 7 and later, with a limited set of guest operating systems:

    • 32- and 64-bit versions of Microsoft Windows 7, XP, 2003, 2003 R2, 2008, 2008 R2, and Server 2012
    • 32- and 64-bit versions of Red Hat Enterprise Linux 5.0 and later
    • 32- and 64-bit versions of SUSE Linux Enterprise Server 10 and later
    • 32- and 64-bit versions of Asianux 3 and later
    • 32- and 64-bit versions of Debian 4
    • 32- and 64-bit versions of Debian 5
    • 32- and 64-bit versions of Debian 6
    • 32- and 64-bit versions of Ubuntu 7.04 and later
    • 32- and 64-bit versions of Sun Solaris 10 and later

    Notes:

    • In ESXi/ESX 4.1 and earlier releases, jumbo frames are not supported in the Solaris Guest OS for VMXNET 2 and VMXNET 3. The feature is supported starting with ESXi 5.0 for VMXNET 3 only. For more information, see Enabling Jumbo Frames on the Solaris guest operating system (2012445).
    • Fault Tolerance is not supported on a virtual machine configured with a VMXNET 3 vNIC in vSphere 4.0, but is fully supported on vSphere 4.1.
    • Windows Server 2012 is supported with e1000, e1000e, and VMXNET 3 on ESXi 5.0 Update 1 or higher.

Adapter Caveats

  • Migrating virtual machines that use enhanced VMXNET

    VMXNET 2 was introduced with ESX 3.5. Virtual machines configured to have VMXNET 2 adapters cannot migrate to earlier ESX hosts, even though virtual machines can usually migrate freely between ESX 3.0 and ESX 3.0.x.

    If you must migrate a virtual machine between later and earlier hosts, do not choose VMXNET 2.

  • Upgrading from ESX 2.x to ESX 3.x

    When a virtual hardware upgrade operation transforms a virtual machine created on an ESX 2.x host to an ESX 3.x host, Vlance adapters are automatically upgraded to Flexible. In contrast, VMXNET adapters are not upgraded automatically because most Linux guest operating system versions do not reliably preserve network settings when a network adapter is replaced. Since the guest operating system thinks a Flexible adapter is still Vlance, it retains the settings in that case. If the upgrade replace a VMXNET adapter with a Flexible adapter, the guest operating system erroneously discards the settings.

    After the virtual hardware upgrade, the network adapter is still VMXNET, without the fall back compatibility of the Flexible adapter. Just as on the original earlier host, if VMware Tools is uninstalled on the virtual machine, it cannot access its network adapters.

  • Adding virtual disks

    Adding an existing earlier (ESX 2.x) virtual disk to an ESX 3.x virtual machine results in a de facto downgrade of that virtual machine to ESX 2.x. If you are using ESX 3.x features, such as enhanced VMXNET or Flexible network adapters, the virtual machine becomes inconsistent. When you add an existing ESX 2.x virtual disk to an ESX 3.x machine, immediately use the Upgrade Virtual Hardware command to restore the virtual machine to the ESX 3 version. This problem does not arise when you add earlier virtual disks to an ESXi/ESX 4.0 virtual machine.

    Note: Executing the Upgrade Virtual Hardware command changes the ESX 2 virtual disk so that it is no longer usable on an ESX 2 virtual machine. Consider making a copy of the disk before you upgrade one of the two copies to ESX 3 format.

For more information on:

 

Written by youryblog

February 18, 2014 at 7:09 PM

Posted in IT, VMWare

What To Do When A Colleague Tries To Sabotage Your Career (http://is.gd/EIEYyq)

leave a comment »

(from Monster.com http://is.gd/EIEYyq)

Some papers are very good. This one is really good. I was several time a victim of a Sabotage and found that when you work in a large corporations you can be sabotaged easily. We work with humans and humans have a lot of bad habits and weaknesses.

The full article is below, just in case if the original disappear from the original website.

When A Co-Worker Tries To Sabotage Your Career

A 45-year-old IT professional—let’s call him Dave—and his co-worker were both up for a promotion. “It was a coveted spot, with compensation around $400,000,” explains career coach Connie Thanasoulis-Cerrachio. “The co-worker started to plant things in Dave’s head, like ‘I think the manager is saying this,’ or ‘I heard someone say that.’ Dave, an already insecure guy, started to unravel. He’s not working there anymore and is currently looking for a new job.”

In the workplace you’ll encounter the good, the bad and the ugly, says Thanasoulis-Cerrachio, the co-founder of SixFigureStart, a career coaching firm.“Some co-workers are really good and you can count on them at all times. Some are bad, which means they just don’t know what they are doing and they make mistakes. Others are ugly, meaning they are out to get you.”

We’re not talking about a co-worker who takes credit for your work or occasionally alienates you in the office, says David Parnell, a legal consultant, communication coach and author. “Career sabotage is a different animal altogether, generally rooted in Machiavellianism, revenge or malice.” The underlying intentions are insidious and quite threatening, he says.

Alexander Kjerulf, an international author and speaker on happiness at work, says if a colleague consistently withholds critical information, shoots down your ideas in meetings, starts rumors about you, refuses to help or give advice, or tries to make you look bad in front of the boss—you’ll want to watch out. “Something ugly is happening,” Thanasoulis-Cerrachio says.

Other signs sabotage may be in the works: You don’t receive a promotion or responsibilities you logically should have gotten; cold or averse behavior from management that is (seemingly) out of nowhere; sudden and unexplained alienation by individual co-workers or even entire cliques; or unwarranted and continuous kind behavior from someone that was formerly aloof, ambivalent or even aggressive, Parnell says.

Why might a co-worker try to sink your career?

“One reason is that most workplaces prize individual achievement over and above anything else,” Kjerulf says. “The person who gets the bonus is almost always the one who gets the best results for himself, not the one who goes out of his way to help others. This encourages competition and makes people try to hold others back.”

Others might try to sink a co-worker’s career because they feel threatened. “It could be that they are intimidated by you and your talents,” Thanasoulis-Cerrachio says. “They may want your job outright, and making you look bad may allow them to get their foot in the door.”

Kjerulf adds: “If someone is struggling at work and feels insecure in their job, they might react by also trying to bring down others.”

And finally, we have mean-spirited people. “They have no empathy and thus have no compunctions about sabotaging a co-worker if it will advance their agenda,” Kjerulf says.

Luckily, this isn’t common in most workplaces.

Parnell believes that much of the reported ‘sabotage’ is little more than rationalizations, self-handicapping or outright denial of shortcomings. “Protection of our self-esteem is a top priority at the subconscious level. Cognitive dissonance swirls around personal failings and often it is more palatable to displace blame into the ether rather than into one’s lap.”

Thanasoulis-Cerrachio says: “I think it’s the exception when someone will go out of their way to sink your career. But unfortunately it does happen to unsuspecting individuals who work hard and think the best of others.”

In Pictures: What To Do When a Co-Worker Tries to Sabotage Your Career

If you suspect a colleague is trying to sink your career, here’s what you’ll want to do:

Don’t assume bad intentions. “I believe that we should be extremely careful and never assume bad intentions from the start,” Kjerulf says. “If that co-worker is ignoring you, he could be sabotaging you–or maybe he’s just really busy or he’s having a bad day”

Give people the benefit of the doubt. If we all run around mistrusting others, we end up creating a miserably unhappy business culture. You’ll want to be absolutely sure that your colleague is trying to hurt your career before you go any further.

Be alert. If curious things are happening at work—like you didn’t get that raise you were promised or colleagues start acting differently around you—you’ll want to think about whether someone might be out to get you (or your job).

“Sabotage is usually a calculated, strategic methodology,” Parnell says. “Gossip, an evolved method of safely leveling the power of alpha leaders, is usually the weapon of choice for a saboteur. Unfortunately, due to unwritten social contracts in the workplace, the subjects of gossip are usually the last to hear it. So if sabotage is at your doorstep and you’re not actively looking, you can easily miss it. The best way to remedy this is to set your radar for signs of you-centric gossip.”

Confide in a co-worker. “Talk to some co-workers you trust,” Kjerulf says. Without vilifying the co-worker you think is trying to harm your career, explain how you see things and ask for their opinion. “Maybe you’re completely off base and hopefully they’d be able to tell you so.”

Thanasoulis-Cerrachio agrees. “Having an objective ear is vital here.”

Take notes. Keep notes on what is happening so things are clear, in case you end up talking to your boss or HR about the situation, Thanasoulis-Cerrachio says. Also save all related e-mails.

Confront the culprit. Once you’ve discovered that you are a target, consider yourself warned and take action to mitigate any damages, Parnell says. “One of the best ways to protect yourself is ingratiation. Guilt, empathy and sympathy are powerful motivators and the most direct way to extract them is by befriending your saboteur and gaining a position within their camp. While on the face this may seem weak, some of the most powerful nations in the world use this very method to infiltrate and overcome an enemy.” In the words of Michael Corleone, “Keep your friends close and your enemies closer.”

Kjerulf suggests you say something something like: “I’ve noticed that whenever I send you an e-mail asking for help, you never reply. Also, in our department meetings you criticize my ideas very harshly. It’s been making me feel pretty bad. Can we talk about this?”

Don’t sabotage the saboteur. If you suspect someone is trying to sabotage your career, be the bigger person. “Don’t be that person who sabotages others,” Kjerulf says. “Make it a priority to be there for your co-workers, to always be willing to help, to offer advice and to help them do better work and have more fun on the job—no matter how they treat you. If we all go in with that attitude, we’ll create much happier and more profitable companies.”

Take it to your manager or HR. If all else fails and you’re not able to resolve the issue on your own, take it to your manager or Human Resources department.

Keep your options open. If a situation is toxic and isn’t improving, perhaps you shouldn’t be there. “A smart person always has an updated resume and is always networking to find better positions,” Thanasoulis-Cerrachio says.

Written by youryblog

February 15, 2014 at 6:42 PM

Posted in Management