Change the cost profile currency to your country currency in vCAC 6.x / vRealize Automation 6.x

Finally I would like to share with you how to change the currency matching to your country. Browse to
Login with Infra-admin role user > Infrastructure tab > Administration > Global Properties > Search for the Core as shown in Screenshot

In case if you want to see what is the language culture name for country click here

Table of Language Culture Names, Codes, and ISO Values Method [C++]

Commerce Server 2002

The following table contains values for Language Culture Names, Display Names, Culture Codes, and ISO 639x Values that are used by Commerce Server.

Language Culture Name	Display Name	Culture Code	ISO 639x Value
af-ZA	Afrikaans - South Africa	0x0436	AFK
sq-AL	Albanian - Albania	0x041C	SQI
ar-DZ	Arabic - Algeria	0x1401	ARG
ar-BH	Arabic - Bahrain	0x3C01	ARH
ar-EG	Arabic - Egypt	0x0C01	ARE
ar-IQ	Arabic - Iraq	0x0801	ARI
ar-JO	Arabic - Jordan	0x2C01	ARJ
ar-KW	Arabic - Kuwait	0x3401	ARK
ar-LB	Arabic - Lebanon	0x3001	ARB
ar-LY	Arabic - Libya	0x1001	ARL
ar-MA	Arabic - Morocco	0x1801	ARM
ar-OM	Arabic - Oman	0x2001	ARO
ar-QA	Arabic - Qatar	0x4001	ARQ
ar-SA	Arabic - Saudi Arabia	0x0401	ARA
ar-SY	Arabic - Syria	0x2801	ARS
ar-TN	Arabic - Tunisia	0x1C01	ART
ar-AE	Arabic - United Arab Emirates	0x3801	ARU
ar-YE	Arabic - Yemen	0x2401	ARY
hy-AM	Armenian - Armenia	0x042B
Cy-az-AZ	Azeri (Cyrillic) - Azerbaijan	0x082C
Lt-az-AZ	Azeri (Latin) - Azerbaijan	0x042C
eu-ES	Basque - Basque	0x042D	EUQ
be-BY	Belarusian - Belarus	0x0423	BEL
bg-BG	Bulgarian - Bulgaria	0x0402	BGR
ca-ES	Catalan - Catalan	0x0403	CAT
zh-CN	Chinese - China	0x0804	CHS
zh-HK	Chinese - Hong Kong SAR	0x0C04	ZHH
zh-MO	Chinese - Macau SAR	0x1404
zh-SG	Chinese - Singapore	0x1004	ZHI
zh-TW	Chinese - Taiwan	0x0404	CHT
zh-CHS	Chinese (Simplified)	0x0004
zh-CHT	Chinese (Traditional)	0x7C04
hr-HR	Croatian - Croatia	0x041A	HRV
cs-CZ	Czech - Czech Republic	0x0405	CSY
da-DK	Danish - Denmark	0x0406	DAN
div-MV	Dhivehi - Maldives	0x0465
nl-BE	Dutch - Belgium	0x0813	NLB
nl-NL	Dutch - The Netherlands	0x0413
en-AU	English - Australia	0x0C09	ENA
en-BZ	English - Belize	0x2809	ENL
en-CA	English - Canada	0x1009	ENC
en-CB	English - Caribbean	0x2409
en-IE	English - Ireland	0x1809	ENI
en-JM	English - Jamaica	0x2009	ENJ
en-NZ	English - New Zealand	0x1409	ENZ
en-PH	English - Philippines	0x3409
en-ZA	English - South Africa	0x1C09	ENS
en-TT	English - Trinidad and Tobago	0x2C09	ENT
en-GB	English - United Kingdom	0x0809	ENG
en-US	English - United States	0x0409	ENU
en-ZW	English - Zimbabwe	0x3009
et-EE	Estonian - Estonia	0x0425	ETI
fo-FO	Faroese - Faroe Islands	0x0438	FOS
fa-IR	Farsi - Iran	0x0429	FAR
fi-FI	Finnish - Finland	0x040B	FIN
fr-BE	French - Belgium	0x080C	FRB
fr-CA	French - Canada	0x0C0C	FRC
fr-FR	French - France	0x040C
fr-LU	French - Luxembourg	0x140C	FRL
fr-MC	French - Monaco	0x180C
fr-CH	French - Switzerland	0x100C	FRS
gl-ES	Galician - Galician	0x0456
ka-GE	Georgian - Georgia	0x0437
de-AT	German - Austria	0x0C07	DEA
de-DE	German - Germany	0x0407
de-LI	German - Liechtenstein	0x1407	DEC
de-LU	German - Luxembourg	0x1007	DEL
de-CH	German - Switzerland	0x0807	DES
el-GR	Greek - Greece	0x0408	ELL
gu-IN	Gujarati - India	0x0447
he-IL	Hebrew - Israel	0x040D	HEB
hi-IN	Hindi - India	0x0439	HIN
hu-HU	Hungarian - Hungary	0x040E	HUN
is-IS	Icelandic - Iceland	0x040F	ISL
id-ID	Indonesian - Indonesia	0x0421
it-IT	Italian - Italy	0x0410
it-CH	Italian - Switzerland	0x0810	ITS
ja-JP	Japanese - Japan	0x0411	JPN
kn-IN	Kannada - India	0x044B
kk-KZ	Kazakh - Kazakhstan	0x043F
kok-IN	Konkani - India	0x0457
ko-KR	Korean - Korea	0x0412	KOR
ky-KZ	Kyrgyz - Kazakhstan	0x0440
lv-LV	Latvian - Latvia	0x0426	LVI
lt-LT	Lithuanian - Lithuania	0x0427	LTH
mk-MK	Macedonian (FYROM)	0x042F	MKD
ms-BN	Malay - Brunei	0x083E
ms-MY	Malay - Malaysia	0x043E
mr-IN	Marathi - India	0x044E
mn-MN	Mongolian - Mongolia	0x0450
nb-NO	Norwegian (Bokmål) - Norway	0x0414
nn-NO	Norwegian (Nynorsk) - Norway	0x0814
pl-PL	Polish - Poland	0x0415	PLK
pt-BR	Portuguese - Brazil	0x0416	PTB
pt-PT	Portuguese - Portugal	0x0816
pa-IN	Punjabi - India	0x0446
ro-RO	Romanian - Romania	0x0418	ROM
ru-RU	Russian - Russia	0x0419	RUS
sa-IN	Sanskrit - India	0x044F
Cy-sr-SP	Serbian (Cyrillic) - Serbia	0x0C1A
Lt-sr-SP	Serbian (Latin) - Serbia	0x081A
sk-SK	Slovak - Slovakia	0x041B	SKY
sl-SI	Slovenian - Slovenia	0x0424	SLV
es-AR	Spanish - Argentina	0x2C0A	ESS
es-BO	Spanish - Bolivia	0x400A	ESB
es-CL	Spanish - Chile	0x340A	ESL
es-CO	Spanish - Colombia	0x240A	ESO
es-CR	Spanish - Costa Rica	0x140A	ESC
es-DO	Spanish - Dominican Republic	0x1C0A	ESD
es-EC	Spanish - Ecuador	0x300A	ESF
es-SV	Spanish - El Salvador	0x440A	ESE
es-GT	Spanish - Guatemala	0x100A	ESG
es-HN	Spanish - Honduras	0x480A	ESH
es-MX	Spanish - Mexico	0x080A	ESM
es-NI	Spanish - Nicaragua	0x4C0A	ESI
es-PA	Spanish - Panama	0x180A	ESA
es-PY	Spanish - Paraguay	0x3C0A	ESZ
es-PE	Spanish - Peru	0x280A	ESR
es-PR	Spanish - Puerto Rico	0x500A	ES
es-ES	Spanish - Spain	0x0C0A
es-UY	Spanish - Uruguay	0x380A	ESY
es-VE	Spanish - Venezuela	0x200A	ESV
sw-KE	Swahili - Kenya	0x0441
sv-FI	Swedish - Finland	0x081D	SVF
sv-SE	Swedish - Sweden	0x041D
syr-SY	Syriac - Syria	0x045A
ta-IN	Tamil - India	0x0449
tt-RU	Tatar - Russia	0x0444
te-IN	Telugu - India	0x044A
th-TH	Thai - Thailand	0x041E	THA
tr-TR	Turkish - Turkey	0x041F	TRK
uk-UA	Ukrainian - Ukraine	0x0422	UKR
ur-PK	Urdu - Pakistan	0x0420	URD
Cy-uz-UZ	Uzbek (Cyrillic) - Uzbekistan	0x0843
Lt-uz-UZ	Uzbek (Latin) - Uzbekistan	0x0443
vi-VN	Vietnamese - Vietnam	0x042A	VIT

Then Login with Tenant Admin > Infrastructure tab > Blueprint > Edit any blueprint > you will now get your country currency as shown in the screenshot as my country is India

 

 

Networking: NSX for vSphere Logical Routing Deep Dive

Source:-
YouTube VMware Tech Pubs

Network Profiles in vRealize Automation 6.x

Network profiles define IP addresses and subnets that are used in deployments:
•Can use standard switches, distributed switches, or logical switches
•Uses IP pools for static IP assignments

vRealize Automation supports the following types of network profiles:
•External
•Routed
•Network address translation (NAT)
•Private

External Network Profile
External network profiles are for connecting an application to a precreated network:
•For example, an existing VXLAN or VLAN-backed network that you want to connect component virtual machines to, potentially for multiple applications. This topology is a multitier, single flat network topology.

Routed Network Profile

Using routed network profiles, virtual machines can use a dynamically created network with routed access to the enterprise network:
•The subnets that the machines connect to are reachable to the outside.
•Uses an NSX Edge gateway for external access.

vRealize Automation Routed Gateways

Blueprints with routed network profile must use a routed gateway to talk to external networks.

Routed gateway is defined at the Reservation level for routed and external profiles:
•Only one gateway per external network profile
•Determines whether distributed logical router or NSX Edge gateway is used by a routed network Profile

NAT Network Profile

NAT network profiles allow virtual machines to use a dynamically created network with NAT to access external networks:
•Used when applications have overlapping IP subnets.
•One-to-many and one-to-one NAT supported.
•vRealize Automation programs destination NAT and source NAT rules for access.

Private Network Profile

Using the private network profile, virtual machines can use a dynamically created isolated network when external connectivity is not required 

What is Paxos based algorithm that VMware NSX uses?

Source:-
Youtube

request timed out vs destination host unreachable?

Request Timed Out

This message indicates that no Echo Reply messages were received within the default time of 1 second. This can be due to many different causes; the most common include network congestion, failure of the ARP request, packet filtering, routing error, or a silent discard.

Destination Host Unreachable

This message indicates one of two problems: either the local system has no route to the desired destination, or a remote router reports that it has no route to the destination. If the message is simply "Destination Host Unreachable," then there is no route from the local system, and the packets to be sent were never put on the wire. If the message is "Reply From < IP address >: Destination Host Unreachable," then the routing problem occurred at a remote router, whose address is indicated by the "< IP address >" field.

VMware Mirage Overview

Source:-
YouTube VMware Tech Pubs

Which vSCSI controller should I choose for performance?

So what should I choose as my vSCSI controller and what are the differences between them?

First, it’s important to remind everyone that when you select the Guest OS for a new virtual machine

this automatically makes a selection for which vSCSI controller to use based on what drivers are available in the OS distribution.  So be sure to select the correct Guest OS to start in the right place.

Let’s look at the options available today:

• BusLogic – this was one of the first emulated vSCSI controllers available in the VMware platform.  The earliest versions of Windows has this driver available by default which made it easy when installing that particular OS. It wasn’t however as performant as the LSI Logic driver since Windows’ driver was limited to a queue depth of 1, so often one would manually load the LSI Logic driver instead.  While still available and used occasionally (Is anyone still running Win2K?), it should be considered legacy.
• LSI Logic Parallel (formerly knows as just LSI Logic) – this was the other emulated vSCSI controller available originally in the VMware platform.  Most operating systems had a driver that supported a queue depth of 32 and it became a very common choice, if not the default.
• LSI Logic SAS – This is an evolution of the parallel driver to support a new future facing standard.  It began to grown popularity when Microsoft required its use for MCSC within Windows 2008 or newer.
• VMware Paravirtual (aka PVSCSI) – this vSCSI controller is virtualization aware and was been designed to support very high throughput with minimal processing cost and is therefore the most efficient driver. In the past, there were issues if it was used with virtual machines that didn’t do a lot of IOPS, but that was resolved in vSphere 4.1.

Are there performance differences between them?

• PVSCSI and LSI Logic Parallel/SAS are essentially the same when it comes to overall performance capability.  PVSCSI, however, is more efficient in the number of host compute cycles that are required to process the same number of IOPS. This means that if you have a very storage IO intensive virtual machine, this is the controller to choose to ensure you save as many cpu cycles as possible that can then be used by the application or host. Most modern operating systems that can drive high IO support one of these two controllers.
• Here’s a detailed whitepaper that takes a closer look at PVSCSI vs LSI Logic SAS for IOPS, Latency and Cost.  While it does support that PVSCSI is more capable, keep in mind most customers are not producing 1 million IOPS so for real life the difference is negligible.

How many vSCSI adapters are supported per virtual machine?

• It’s also worth noting that you can configure a total of 4 vSCSI adapters per virtual machine.  To provide the best performance, one should also distribute virtual disk across as many vSCSI adapters as possible.  This configuration provides the capability to process more IO simultaneously and benefit from additional queues if necessary.

What about AHCI SATA?

• This is a new storage controller available with vSphere 5.5 and virtual hardware 10.  It allows you to connect a large amount of storage to a virtual machine but it wasn’t designed to be as efficient as the PVSCSI or LSI Logic controllers and therefore should not be used with performance sensitive applications.

Let’ summarize this in a chart:

Virtual Hardware Reference

PVSCSI KB 1010398

Info taken from:-

http://blogs.vmware.com/vsphere/2014/02/vscsi-controller-choose-performance.html

Check VAAI Status from GUI and CLI

How to verify if VMware VAAI is supported on the datastores is not totally straightforward. We shall see how to do this from both the GUI in vSphere client and from the command line through SSH. See this post to know more about VAAI

The VAAI (vSphere API for Array Integration) is a very useful technique to offload demanding storage tasks directly to the SAN.

When using the vSphere Client and select the Storage screen in the Configuration tab the following view could be seen:

The “Hardware Acceleration” tab shows the VAAI support, but unfortunately somewhat unclear. (Note that the tab is located quite far to the right by default.) Three different modes are possible: supported, unsupported and unknown.

VAAI consists of four different offload primitives, called ATS, Clone, Zero and Delete. If all of these are supported by the Storage Array the vSphere Client will show the Hardware Acceleration as “Supported” and ifnone of them are supported by the SAN then the status will be “Unsupported“.

If however one or more VAAI primitives, but not all, are supported by the SAN then the status will be the somewhat unexpected “Unknown“. This means that “Unknown” does also mean partially, even if that word is not used.

If using the command line, either from the ESXi Shell or SSH the status could be seen in a more granular way. Use the esxcli command to display the VAAI status:

esxcli storage core device vaai status get

 

The first disk device does not support any of the four VAAI primitives. In the vSphere Client this is displayed as “Unsupported“.

The second SAN LUN does support the Zero primitive, but not the other three. This will be presented as “Unknown” in the Hardware Accelaration tab in the GUI.

The third and final LUN does support all of the VAAI offload methods and displays “Supported” inside the vSphere Client.

If possible, the best way to really verify the status of VAAI is to use the command line, but if the graphical vSphere Client displays the Supported status than it means that all offloads are available.

Source:-
http://rickardnobel.se/verify-vaai-from-gui-and-command-line/