Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

...

  1. Login as user root on VMware vSphere client.

    1. Enter VM Ware host machine IP Address.
    2. Enter your VMware vSphere administrator user name.
    3. Enter your VMware vSphere administrator password. 
    Caption
    0Figure
    1VMware VSphere Client Login
     

    The vSphere Client main window appears.

  2. Select the Host in VMware vSphere Client. Select Configuration.

    Caption
    0Figure
    1Adding Virtual Interface



  3. Select Networking tab and select Add Networking link as shown in the figure. Select Virtual Machine and click Next.

    Anchor
    NetworkingImage
    NetworkingImage

    Caption
    0Figure
    1Configuring vSwitch

     

    1. Add a New Virtual Interface and vSwitch0 (MGMT).

      1. Select Use vSwitch0. The vmnic0 is automatically selected. Make sure that the speed is showing 1000 Full for the selected vSwitch. It indicates physical port is up. Click Next.

        Caption
        0Figure
        1Selecting vSwitch0

      2. Enter Network Label. For example MGMT. Click Next and Finish.

        Caption
        0Figure
        1Entering Label

    2. Add a New Virtual Interface and new vSwitch1 (HA).

      1. Select Networking tab and select Add Networking link. Select Virtual Machine and click Next (see Figure Configuring vSwitch).
      2. Select Create a vSphere standard switch. Select vmnic1. Make sure that the speed is showing 1000 Full for the selected vSwitch. It indicates physical port is up. Click Next.

        Caption
        0Figure
        1Adding vSwitch 1

      3. Enter Network Label. For example HA. Click Next and Finish.

        Caption
        0Figure
        1Entering Network Label HA

    3. Add a new Virtual Interface and new vSwitch2 (PKT0).
      1. Select Networking tab and select Add Networking link. Select Virtual Machine and click Next (see Figure Configuring vSwitch).
      2. Select Create a vSphere standard switch. Select vmnic2. Make sure that the speed is showing 1000 Full for the selected vSwitch. It indicates physical port is up. Click Next.

        Caption
        0Figure
        1Selecting vmnic2

      3. Enter Network Label. For example PKT0. Click Next and Finish.

        Caption
        0Figure
        1Entering Network Label (PKT0)

    4. Add a new Virtual Interface and new vSwitch3 (PKT1).
      1. Select Networking tab and select Add Networking link. Select Virtual Machine and click Next (see Figure Configuring vSwitch).
      2. Select Create a vSphere standard switch. Select vmnic3. Make sure that the speed is showing 1000 Full for the selected vSwitch. It indicates physical port is up. Click Next.

        Caption
        0Figure
        1Selecting vmnic3

         

      3. Enter Network Label. For example PKT1. Click Next and Finish.

        Caption
        0Figure
        1Entering Network Label (PKT1)

         

        Note

        If the VLAN is used for packet ports (PKT 0 or PKT1), then the VLAN ID (optional) parameter must be selected as ALL (4095). This method is recommended and it is called as VGT (Virtual Guest tagging), where the guest OS takes care of VLAN tagging functionality. The VLAN can be used for either PKT0 or PKT1 or both. For non-VLAN configuration, use the default value 0.

        Caption
        0Figure
        1Configuring VLAN

         

        Caption
        0Figure
        1Configuring VLAN

        Image Modified

    5. Verify that the added vSwitches are in proper order. Click Configuration tab and Networking.

      Warning

      The switches and interfaces MUST be defined in this order:

      vSwitch0 - MGMT

      vSwitch1 - HA

      vSwitch2 - PKT0

      vSwitch3 - PKT1

      Caption
      0Figure
      1Verifying vSwitches

      Note

      Usage of vSwitch0 is not a mandatory requirement for MGMT0 interface. If server has more than 4 physical NIC ports, there is an option to assign MGMT label to vSwitch1, HA to vSwitch2, PKT0 to vSwitch3 and PKT1 to vSwitch4.

...

  1. Make sure the physical host server is configured with minimum 8 physical NIC ports to have 1:1 physical NIC redundancy for each vNICs (that is MGMT0, HA0, PKT0 and PKT1 virtual interfaces) on 
    Spacevars
    0product
    VM.
  2. Repeat sub steps of Step 3 shown in Configuring vNetwork Standard Switch Without Physical NIC Redundancy

  3. Add additional NICs and group it by using the following steps:

    1. Anchor
      Additional NICs
      Additional NICs
      Select Management network Properties linkas shown:

      Caption
      0Figure
      1Selecting Management Network Properties

    2. In vSwitch properties window click Network Adapters tab and click Add.

      Caption
      0Figure
      1Selecting Network Adapter

      Image Modified

    3. In Add Adapter Wizard, select the NIC to group it. For example, if you are grouping vmnic1 and vmnic4 for management network, select vmnic4 check box.

      Caption
      0Figure
      1Selecting NIC

      Image Modified

    4. Click Next after selecting the vmnic.

      Caption
      0Figure
      1Selecting NIC

      Image Modified

    5. Select the order of fail over by moving adapters up or down.

      Caption
      0Figure
      1Arranging Failover Order

    6. Click Next in Failover Order, and then click Finish.

      Caption
      0Figure
      1Adapter Summary

  4. Now the management network adapter is grouped with NICs (in this example, vmnic0 and vmnic4) to support NIC redundancy. Following example screen shows management network adapter NIC redundancy.

    Caption
    0Figure
    1NIC Redundancy for Management Network

  5. Repeat the steps of Adding Additional NICs for HA, PKT0 and PKT1 ports NIC grouping.

...