Saturday, 26 August 2017

Vmotion/Layer-2/Layer-3

Vmotion/Layer-2/Layer-3

Why Layer-2 required eventhough vmotion can be done  in Layer-3 in Vsphere-6 ?


Even if the VM.1 can move from one network  to another network through layer-3 using separate TCP/IP Stack introduced in Vsphere-6, the ip address of the VM.1 will not be reachable after movement if there is no Layer-2 between hosts.So Layer-2 connectivity required ,even if Vmotion can be done  using Layer-3.

Stretched Vlan Technologies like VXVLAN  can be implemented for having Layer-2 over Layer-3 .





Wednesday, 21 September 2016

VMWARE PLUGABLE STORAGE ARCHITECTURE



Pluggable Storage Architecture (PSA)


To manage storage multipathing, ESX/ESXi uses a special VMkernel layer, Pluggable Storage Architecture (PSA). The PSA is an open modular framework that coordinates the simultaneous operation of multiple multipathing plugins (MPPs). PSA is a collection of VMkernel APIs that allow third party hardware vendors to insert code directly into the ESX storage I/O path. This allows 3rd party software developers to design their own load balancing techniques and failover mechanisms for particular storage array. The PSA coordinates the operation of the NMP and any additional 3rd party MPP.











Features

  • There are two NMP sub plugin->SATPs (Storage array type plugin) and PSP (path selection plugin)

  • Either we can create third party MPP to replace  default NMP or we can replace the sub plugins (SATP/PSP) under NMP

  • 3rd party MPP can exist along with native NMP


Vmware SATP

  • This module is for selecting the failover path based on the class of storage ,this module can do failover and detect path based on storage

  • monitor and report health of the path and perform array specific action for storage failover

  • There is a SATP  rule set specific for storage models and the current  rule can be found by


      esxcli storage nmp satp rule list

  • There is a default path selection policy of each SATP this is displayed by

           esxcli storage nmp satp list



Vmware PSP

This sub plugin is for the Path selection policy for the i/o data based on the SATP

There will be a default PSP associated with different SATP and we have the option to change the default PSP


Different type of PSP



VMW_PSP_MRU


Most recently used path is selected and onec it become unavailbel next path is selected and once the unavailable path become available it will not transfer back

This is the default policy for active active array



VMW_PSP_FIXED

Host uses fixed path either we can specify explicitly or it uses first working pathand on unavailability it will select new path. In case of explicitly chosen it will remain as such not failover will occur.


This is the default policy of  active -active array


VMW_PSP_RR

This is used for load balancing and used with all type of array



Best practice for Storage model from specific vendor

1.Check in vmware HCL about the supported PSP and SATP rules and once clear change else put        default


2.Check  SATP rule corresponding to the specific vendor

        esxcli storage nmp satp rule list


3.Check PSP for the corresponding  SATP

          esxcli storage nmp satp list


4.If you want to change the PSP  rule for the SATP corresponding to specific vendor and model


esxcli storage nmp device list -d <device-naa-value>

this will give the vendor and model for the specific lun from the storage


esxcli storage nmp satp rule add -V <vendor> -M "<model>" -P <psp> -s satp>

this will change the default rule


esxcli storage nmp satp rule list

check SATP rule again



Conclusion

Here you can see that there is a default rule for the vendor A and there is a rule for the vendor A with model B.The advantage is that we can keep the default policy as such for the vendor and we can i n addition add policy for specific model for the vendor





Links helpful










Thursday, 11 February 2016

SOME VMS SHOWING 0 MEMORY AND 0 CPU


In these case


1.Vmotion all vms  from the affected ESXI host

2.Restart management services in Hosts





From the SSH:

putty to the esxi host

/etc/init.d/hostd restart
/etc/init.d/vpxa restart



From the Direct Console User Interface (DCUI):
  1. Connect to the console of your ESXi host.
  2. Press F2 to customize the system.
  3. Log in as root.
  4. Use the Up/Down arrows to navigate to Restart Management Agents.

    Note: In ESXi 4.1 and ESXi 5.0, 5.1, 5.5 and 6.0 this option is available under Troubleshooting Options.
  5. Press Enter.
  6. Press F11 to restart the services.
  7. When the service restarts, press Enter.
  8. Press Esc to log out of the system.




Cheers...

wait for oracle ldom


Sunday, 7 February 2016

PROBLEM WITH VCENTER 5.5 WINDOWS



one of my customer faced a problem of

1.when vcenter server is logged on its showing zero inventory with the message

   "Could not connect to one or more vCenter Server Systems:https://vCenterFQDN:443/sdk"


    and some time showing the inventory

2.The Vcenter login get disconnected frequently leading to unable to connect to Vcenter server for sometime



Troubleshooting steps done

1.DNS forward and reverse lookup checked
2.When the odbc connection to sql database
3.Checked whether firewall is on in the vcenter server.
4.Restarted the vcenter server services
5.Checked the ports
6.Checked for duplicate vcenter server instance by below article

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


**Make sure you are unregistering only vcenter service.In my case there was no duplicate instance


7.I saw many errors in the vpxd log as


Failed to add LDAP entry cn=d6cc6fd2-bb66-4fe9-9892-4a3a0c93b91d,ou=Instances,dc=virtualcenter,dc=vmware,dc=int: 0×68 



but before going to do the steps mentioned in the article our issue resolved.



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




Solution

1.Every vcenter server have a default domain for SSO called vsphere.local.In my case customer dont know the password.so we go for  resetting administrator@vsphere.local username using below article



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


after logging using administrator@vsphere.local.we are able to find inventory objects are not lost .




2. Then we checked the windows event manager where we found even though in the services.msc vcenter services are running. In the event viewer we saw many error related to vpxd service like

Fault Module Name: ntdll.dll

Then as per the article 

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

we added <ThreadStackSizeKb>1024</ThreadStackSizeKb> which was not there in vpxd.cfg file



After that we started the vcenter services and now the second issue of frequent Vcenter access issue resolved.



But I asked customer to keep monitoring for some days.If its works fine You guyz can follow .

note:

**Even though vcenter services seems to be running check the event viewer
**Before going to the steps to resolve error of LDAP shown in vpxd.log.Check other ways



cheers.............





Thursday, 28 January 2016