VMPOOL & TECH BLOG

When Managing Cybersecurity, Operate Like You’ve Already Been Compromised

2023-04-03T20:58:00.001+07:00

The saying "operate like you’ve already been compromised" is a common piece of advice in the world of cybersecurity. Essentially, it means that organizations should assume that their network has already been breached, and therefore, they should always be vigilant and take proactive measures to detect and respond to any potential threats.

There are several reasons why this is a good approach. First, it acknowledges that no security measures are foolproof, and even the most robust security systems can be breached. Therefore, it’s better to assume that the organization has already been compromised and take measures to identify and mitigate any damage as quickly as possible.

Second, this approach promotes a proactive rather than reactive approach to cybersecurity. Instead of waiting for a breach to occur before taking action, organizations can take steps to prevent breaches from happening in the first place. This can include implementing security measures such as firewalls, intrusion detection systems, and security software, as well as conducting regular security audits and employee training.

Finally, operating like you’ve already been compromised can help organizations respond more quickly and effectively to any potential breaches. By having a well-defined incident response plan in place, organizations can quickly identify and contain any security incidents, minimizing the impact on their operations and reputation.

In short, by operating like you’ve already been compromised, organizations can take a proactive approach to cybersecurity, reduce their risk of a breach, and respond more effectively if a breach does occur.

Not to dredge up unpleasant memories, but do you remember how we all felt in the early stages of the Covid-19 pandemic? Vaccines and treatments weren't yet available, and people faced real risks. We isolated ourselves in our homes for weeks or months, kept our distance from other people when we had to go out and canceled gatherings with family and friends. We went through the day with the assumption that everyone we encountered might have the virus.

Then, two things happened. Vaccines were developed that reduced the likelihood of infection and severe illness. And more contagious variants of the virus began to circulate. The result? Many who were vaccinated, boosted and continued masking and distancing practices wound up contracting the virus. But partly because of the precautions they'd taken, the illness wasn't as severe for most of them.

How to move a virtual machine to an Azure server

2023-03-31T12:09:00.002+07:00

To move a virtual machine to an Azure server, you can follow these general steps:

Create an Azure account: If you don't already have an Azure account, create one.

Create a virtual machine in Azure: Create a new virtual machine in Azure that has the same operating system as the virtual machine you want to move.

Install the necessary software on the new virtual machine: Install any necessary software on the new virtual machine to ensure that it can properly run the application or service that was running on the old virtual machine.

Export the virtual machine from the old server: Export the virtual machine from the old server to a file format that is supported by Azure. For example, you can use the VHD or VHDX format.

Transfer the virtual machine to Azure: Transfer the exported virtual machine file to Azure, either by uploading it to a storage account or using a tool like Azure Site Recovery.

Create a new virtual machine from the exported virtual machine: Create a new virtual machine in Azure from the exported virtual machine file.

Configure the new virtual machine: Once the new virtual machine has been created, configure it with the necessary settings and connect it to your network.

Test the new virtual machine: Test the new virtual machine to ensure that it is working correctly and that the application or service is running as expected.

Note that the specific steps for moving a virtual machine to an Azure server may vary depending on the virtualization software and operating system you're using. Additionally, it's important to ensure that you have the necessary permissions and access to both the old server and the Azure account.

แพลตฟอร์ม เอ็นจิเนียริ่งกับการพัฒนาแอปฯ ยุคใหม่

2023-03-27T12:49:00.004+07:00

ปลายทางที่มัลติคลาวด์

Could Trust มูลนิธิ Cloud Native Computing Foundation (CNCF) ซึ่งรวมกลุ่มโอเพ่นซอร์สในการพัฒนาแอปพลิเคชันบนคลาวด์เนทีฟ ชี้เป้าให้ “มัลติคลาวด์” เป็นหนึ่งในเครื่องมือมาตรฐานกลางชิ้นสำคัญสำหรับพัฒนาอินฟราสตรัคเจอร์ หรือซอฟต์แวร์แอปพลิเคชันยุคใหม่ให้สามารถทำงานกับคลาวด์ได้หลายประเภท อาทิ vSphere โดยวีเอ็มแวร์ ไมโครซอฟท์อาซัวร์ เอดับบลิวเอส กูเกิล คลาวด์ ตลอดจนคลาวด์เนทีฟอื่น ๆ ด้วยมุมมองเชิงกลยุทธ์การลงทุนที่เปลี่ยนจากการเลือกใช้งานคลาวด์เป็นอันดับแรก มาเป็นการจัดกลุ่มแอปพลิเคชันที่จำเป็นใช้งานในองค์กรเสียก่อน จากนั้น จึงพิจารณาว่าจะโยกย้ายขึ้นสู่คลาวด์ประเภทไหนตามความเหมาะสม เช่น แอปพลิเคชันตัวไหนควรเป็นออนเพรม ตัวไหนที่น่าจะย้ายขึ้นบริการคลาวด์สาธารณะ อย่างไหนควรเขียนใหม่ทั้งหมดให้ใช้งานบนคลาวด์แบบเต็มตัว หรือคงไว้เหมือนเดิมเพราะไม่กระทบต่อธุรกิจมากพอให้ต้องเปลี่ยน เป็นต้น เพราะถ้าองค์กรวางแผนการใช้งานคลาวด์ได้ไม่ดี จะกลับกลายเป็นทำให้ค่าใช้จ่ายสูงขึ้น อีกทั้งมาตรฐานของเครื่องมือที่เลือกใช้ต่างกันจะทำให้การจัดการยิ่งยุ่งเหยิง

แพลตฟอร์ม เอ็นจิเนียริ่งกับการพัฒนาแอปฯ ยุคใหม่

ในอดีต กรอบการพัฒนาแอปพลิเคชันถูกเขียนขึ้นเพื่อตอบโจทย์งานหน้าบ้าน หลังบ้าน และการจัดการฐานข้อมูลสำหรับการทำงานอย่างใดอย่างหนึ่ง แต่ในโลกของคลาวด์ แอปพลิเคชันถูกสร้างให้อยู่ในรูปแบบไมโครเซอร์วิส หรือแพลตฟอร์มให้ตรงโจทย์ทางธุรกิจมากขึ้น เกิดการใช้งานแบบไร้เซิร์ฟเวอร์บนคลาวด์อินฟราสตรัคเจอร์รูปแบบต่าง ๆ เกิดการตั้งศูนย์ข้อมูลหลายจุดเพื่อกระจายการทำงาน เริ่มนำแอปพลิเคชันไปวางใกล้ ๆ กับแหล่งต้นทางของข้อมูล เช่น เทคโนโลยีเอดจ์ เป็นต้น ซึ่งคลาวด์แต่ละแบรนด์ก็มีแนวทางการบริหารจัดการเทคโนโลยีที่ต่างกัน แพลตฟอร์ม เอ็นจิเนียริ่ง (Platform Engineering) จึงเป็นสิ่งที่มาขยายมุมคิดของ DevOps หรือ DevSecOps ของการพัฒนาแอปฯ หรือแพลตฟอร์มที่เดิมเป็นแค่ทูลตัวหนึ่งให้กลายเป็นเสมือนผลิตภัณฑ์ที่ต้องพัฒนาร่วมกันอย่างต่อเนื่องระหว่างทีมนักพัฒนา ทีมปฏิบัติงานด้านไอที ทีมเน็ตเวิร์ค และซีเคียวริตี้ ข้อดี คือ ลดการใช้เครื่องมือในการพัฒนาที่ต่างกันไปแต่ละทีมมาเป็นการมองหาแพลตฟอร์มกลางเพื่อตอบโจทย์การพัฒนาจากทุกทีม มีทีมพัฒนากลางที่เดินไปในทิศทางเดียวกันเพื่อให้การออกแบบและสร้างแอปพลิเคชันหรือแพลตฟอร์มเพียงครั้งเดียวแต่สามารถรันบนอินฟราสตรัคเจอร์ได้ทุกที่เพื่อลดภาระงาน เกิดระบบล่มแต่น้อย ทั้งยังขยายระบบหรือเขียนบริการธุรกิจใหม่ ๆ ได้ตลอดเวลา ถ้าเจอปัญหาเร็ว แก้ไขไวและถูกจุด ซึ่งนอกจากจะทำให้การบริหารงานด้านไอทีดีขึ้น ยังทำให้องค์กรสามารถแตะถึงเป้าหมายทางธุรกิจได้รวดเร็วมากขึ้นอีกด้วย

ความปลอดภัยแบบซีโร่ทรัสต์

แม้การโจมตีในปัจจุบันจะเปลี่ยนไปหลากหลายรูปแบบ แต่เป้าหมายยังเป็นเรื่องเดิมคือ การขโมยสิ่งที่ใช้ยืนยันตัวตน (Credentials) เพื่อเจาะเข้าสู่ระบบและขโมยข้อมูลที่ต้องการ ซึ่งแรนซั่มแวร์ที่เก่ง ๆ บางตัวอาจจะเข้า-ออก หรือฝังตัวในระบบไอทีนานนับปีก่อนแผลงฤทธิ์โดยที่เราไม่รู้ตัว ซึ่งวีเอ็มแวร์ได้ให้กรอบความปลอดภัยแบบซีโร่ทรัสต์ (Zero Trust) โดยมี “ข้อมูล” เป็นแกนกลาง และมองความเชื่อมโยงเรื่องความไว้วางใจลงไปสู่ระบบไอทีในลำดับชั้นต่าง ๆ อาทิ ผู้ใช้งานปลายทาง (User Trust) อุปกรณ์ (Device Trust) แอปพลิเคชัน (Application Trust) เน็ตเวิร์ค (Network Trust) ตัวอย่างเช่น

Endpoint Trust / Device Trust ในช่วงวิกฤตโควิด เราพบว่า หลายองค์กรประสบปัญหาอย่างมากจากการถูกขโมยครีเดนเชียลในการยืนยันตัวตนผ่านการใช้งานอุปกรณ์ปลายทาง วีเอ็มแวร์บอกกับเราว่า ทุก 11 วินาทีจะมีองค์กรทั่วโลกตกเป็นเหยื่อของสแปมและฟิชชิ่ง 59% เจอภัยคุกคามแบบสองเด้ง (Double Extortion) คือ ไฟล์ถูกล็อครหัสให้เข้าถึงไม่ได้หนำซ้ำยังดึงข้อมูลออกไปปล่อยในเว็บมืด แถมปล่อยดี-ดอสตามมารบกวนให้ระบบไม่ปกติ และ 77% มาจากการโจมตีผ่านช่องทางเชื่อมต่อของแอปพลิเคชันต่าง ๆ (Application Programming Interface-API) ทั้งบนออนเพรม คลาวด์สาธารณะ หรือ ไฮบริดคลาวด์ ซึ่งตรงเข้าสู่ดาต้าเซ็นเตอร์ได้ไม่ต้องผ่านไอพีสาธารณะ (Public IP) และไม่ต้องยืนยันตัวตน ซึ่งทำให้อาชญากรไซเบอร์สามารถแทรกตัวผ่านรอยรั่วของข้อต่อนี้เข้าไปถึงซิสเต็มส์และข้อมูลเชิงลึกขององค์กรได้เลย

Application Trust เป็นจุดที่ควรแก่การวางระบบความปลอดภัยทั้งซัพพลายเชนลงถึงระดับโปรดักชัน เช่น การเขียนโค้ดดิ้ง การทำเฟรมเวิร์ค การสแกนโค้ด การเลือกใช้โค้ดโปรแกมต้นทางที่ควรมีเทมเพลตเรื่องความปลอดภัยติดมาด้วย เพราะ หนึ่ง แอปฯ ที่พัฒนาบนคลาวด์มีทั้งที่เขียนโค้ดขึ้นเองเป็นเนทีฟ และใช้โอเพ่นซอร์ส หากซัพพลายเออร์หรือโอเพ่นซอร์สที่หยิบมามีช่องโหว่ ก็จะสร้างความน่าสะพรึงยิ่งกว่าแอปพลิเคชันที่เขียนขึ้นเอง สอง นักพัฒนาไม่ควรมองข้ามช่องโหว่ความปลอดภัยที่เกิดขึ้นขณะเขียนโค้ด จังหวะโยนเข้าอิมเมจ นำไปทดลองปฏิบัติ หรือเชื่อมต่อกับคนอื่น ถ้าระบบความปลอดภัยถูกเจาะตั้งแต่ตรงนี้ก็จะกลายเป็นจุดบอดเล็ก ๆ ที่ซ่อนอยู่ในโค้ดโปรแกรมต้นทางหรือไลเบอรี่ต่าง ๆ ในระดับคอนเทนเนอร์ และกลายเป็นช่องโหว่ที่ใหญ่ขึ้นเมื่อคอนเทนเนอร์โตขึ้นเมื่อเกิดการใช้งานแอปพลิเคชันจากทั้งยูสเซอร์ไปคลาวด์ ลูกค้าไปคลาวด์ คลาวด์สู่คลาวด์ หรือคลาวด์ในตัวมันเอง เพราะต้องไม่ลืมว่าการใช้งานคลาวด์ จุดเชื่อมต่อไม่ได้อยู่แค่ช่องจราจรบนเน็ตเวิร์ค แต่ยังหมายถึงเอพีไอที่กล่าวถึงข้างต้น รวมถึงคูเบอร์เนเตสที่ต้องถูกอัพเดทแก้ไขเมื่อถูกส่งขึ้นไปดูแลคอนเทนเนอร์ต่าง ๆ

Network Trust ที่แตกออกเป็น 2 ระดับ ได้แก่ ระดับการจัดการอุปกรณ์และระบบต่าง ๆ และระดับความปลอดภัยที่เกี่ยวข้องเวอร์ช่วลไลเซชันบนเน็ตเวิร์คที่ต้องมีการกำหนดกรอบการทำงานให้ชัดเจน ซึ่งไม่ใช่การป้องกันข้อมูลรั่วไหล ความปลอดภัยในการขนถ่ายข้อมูลบนเวอร์ช่วลแมชชีน คอนเทนเนอร์ การป้องกันการแฝงตัวเข้ามาทางเอพีไอ โดยมีเอไอมาช่วยวิเคราะห์พฤติกรรมและรูปแบบของแอปพลิเคชันแต่ละตัว (App Behavior) และแยกแยะปัญหาให้แน่ใจว่า เกิดจากการโจมตีทางไซเบอร์ หรือเน็ตเวิร์คล่มเพราะตั้งค่าการทำงานที่ผิดพลาด เป็นต้น ซึ่ง SD-Wan (Software-definded Wide-area Network) ถือเป็นหนึ่งในตัวช่วยการจัดการเน็ตเวิร์ค ขณะที่เทคโนโลยีพื้นฐานอย่างไฟร์วอลล์ หรือแอนตี้ไวรัสยังคงอยู่แต่ต้องปรับเปลี่ยนให้รองรับสภาพแวดล้อมใหม่ เช่น สร้างระบบตรวจจับและตอบสนองการบุกรุกทั้งกับเครื่องเอนด์พอยต์ (EDR) และเน็ตเวิร์ค (NDR) ต่อทุกภาระงานที่วิ่งเข้ามาสู่รระบบผ่านไฟร์วอลล์หลายชั้นสักหน่อย หรือการคัดกรองเส้นทางจราจรที่ผิดปกติ (Network Traffic Analysis) เพื่อตรวจจับยูสเซอร์ที่มีการใช้งานและการเคลื่อนไหวแปลก ๆ เช่น เครื่องตัวเองติดไวรัสแล้วพยายามแฮ็คไปหาเครื่องอื่นในระบบ เพื่อไม่ให้เกิดความเสียหายจนเกินควบคุม หากโชคร้ายเจาะเข้าสู่ระบบได้ ก็ต้องมีการตอบสนองและแก้ไขอย่างรวดเร็ว

ครบทุกการจัดการจากวีเอ็มแวร์

วีเอ็มแวร์เป็นหนึ่งในบริษัทที่ผันตัวจากการยกระดับจาก vSphere ฉบับเวอร์ช่วลไลเซชันในการจัดการงานออนเพรมหรือคลาวด์ส่วนตัว ไปสู่มัลติคลาวด์เพื่อตอบโจทย์ธุรกิจในมุมของการพัฒนาได้ทั้ง “แอปพลิเคชัน” และ “แพลตฟอร์ม” โดย VMware Tanzu จะช่วยให้แอปพลิเคชันสมัยใหม่ (App Modernization) สามารถทำงานบนมัลติคลาวด์ หรือคลาวด์อินฟราตรัคเจอร์ได้หลายแบบ สามารถย่อ-ขยายหรือเพิ่มเติมฟีเจอร์ใหม่ออกสู่ตลาดในเวลาที่รวดเร็ว ที่สำคัญคือ การทำ High Availability (HA) ที่ช่วยลดปัญหาการหยุดชะงักของระบบ รวมถึงเพิ่มระบบความปลอดภัยจากการใช้งานคลาวด์ที่กระจายออกไปหลายจุดให้อยู่ในมุมมองที่องค์กรจัดการ ทั้งการช่วยตรวจสอบและจัดหาโอเพ่นซอร์สที่ปลอดภัยมาใช้ในระบบ รวมถึงมีเครื่องมือช่วยสร้างมาตรฐานของการเขียนโค้ดและส่งโค้ดขึ้นสู่คอนเทนเนอร์ได้มีประสิทธิภาพโดยใช้ทีมงานน้อยที่สุด

VMware NSX ที่มาช่วยจัดการความปลอดภัยบนเน็ตเวิร์คแบบครบเครื่องร่วมกับเทคโนโลยีเอไอในการตรวจจับคัดกรองพฤติกรรมน่าสงสัยที่เกิดกับอุปกรณ์ปลายทาง เวอร์ช่วลแมชชีน เน็ตเวิร์ค แอปพลิเคชัน คอนเทนเนอร์ หรือภาระงานต่าง ๆ เพื่อเพิ่มประสิทธิภาพการจัดการและเสริมความปลอดภัยให้กับระบบเวอร์ช่วลไลเซชัน

VMware Carbon Black เพิ่มมุมมองความปลอดภัยเชิงลึกในระดับ XDR ให้กับเอนด์พอยต์และเน็ตเวิร์คอีกชั้นหนึ่ง เพื่อการป้องกัน ตรวจจับ และตอบสนองต่อภัยคุกคามที่รวดเร็ว โดยการเฝ้าสังเกตพฤติกรรมที่ผิดปกติตลอดเวลาแทนการสกัดภัยคุกคามเป็นช่วงเวลาเนื่องจากแรนซั่มแวร์ไม่มีรูปแบบการโจมตีที่แน่นอน การวิเคราะห์จุดเกิดเหตุ แยกแยะรูปพรรณสัณฐานของภัยคุกคามเพื่อกำหนดนิยาม ความเสี่ยง และช่องโหว่ที่จะเกิดขึ้นกับข้อมูล ระบบปฏิบัติการ ปริมาณงาน แอปพลิเคชันจากอุปกรณ์ใช้งานปลายทาง ตลอดจนสอบทานว่า ไอพีเครื่องใดมีแอปพลิเคชันที่ไม่มีประโยชน์ก็สามารถสกัดการใช้งานได้ทันที ด้วยฟังก์ชัน Agent & Console รวมถึง Threat Intelligence ซึ่งช่วยให้เอไอฉลาดขึ้นในการป้องกันมัลแวร์ การวิเคราะห์พฤติกรรมของซิกเนเจอร์ต่าง ๆ ที่เข้ามาโดยที่ระบบไม่รู้จักมาก่อน เพื่อสกัดกั้นหรือหยุดยั้งได้โดยอัตโนมัติ

Xiaomi รายงานผลประกอบการของไตรมาสที่ 2 ปี 2022

2022-08-20T09:56:00.004+07:00

Xiaomi รายงานผลประกอบการของไตรมาสที่ 2 ปี 2022 รายได้รวม 70,170.9 ล้านหยวน ลดลง 20.1% จากช่วงเดียวกันในปีก่อน และมีกำไรสุทธิ 2,081.3 ล้านหยวน

Wang Xiang ประธาน Xiaomi กล่าวในช่วงแถลงผลประกอบการ ว่ารายได้ที่ลดลงมากมาจากตลาดจีน ซึ่งได้รับผลกระทบจากการกลับมาระบาดอีกครั้งของโควิด จนกระทบต่อความต้องการสินค้า ซึ่งกระทบกับสมาร์ทโฟนทุกค่ายในจีน รวมถึงปัญหาค่าขนส่ง และเงินเฟ้อที่เพิ่มขึ้น ที่ทำให้กระทบต่อกำไร

รายได้แยกตามกลุ่มธุรกิจ สมาร์ทโฟนลดลงเป็น 42,268.1 ล้านหยวน ส่งมอบสมาร์ทโฟน 39.1 ล้านเครื่อง กลุ่ม AIoT รายได้ 19,811.6 ล้านหยวน มีสินค้าเด่นคือ Xiaomi Pad 5 และเครื่องใช้ไฟฟ้าอย่าง แอร์ ตู้เย็น เครื่องซักผ้า และธุรกิจ Internet Services รายได้ 6,971.1 ล้านหยวน ลดลงจากธุรกิจ FinTech เป็นหลัก

Google Search ประกาศปรับอัลกอริทึมใหญ่

2022-08-19T15:57:00.019+07:00

Google Search ประกาศปรับอัลกอริทึมใหญ่ โดยเรียกว่า “helpful content update” ธีมหลักคือการกรองเนื้อหาที่ตั้งใจทำ SEO แต่มีคุณภาพต่ำ (เช่น คัดลอกจากที่อื่น, ดักคำสำคัญที่คนค้นหาเยอะๆ) ออกไป เน้นที่เนื้อหาซึ่งเขียนโดยคน และเขียนให้คนอ่าน (written by people, for people)กูเกิลไม่ได้เปิดเผยรายละเอียดมากนักว่ามีวิธีแยกแยะเนื้อหา 2 ประเภทออกจากกันอย่างไร แต่ก็แนะนำให้สร้างเนื้อหาแบบ people-first เพื่อเป็นประโยชน์ต่อผู้อ่าน แทนเนื้อหาแบบ search engines first ที่เน้นดักทราฟฟิกข้อมูลที่กูเกิลเปิดเผยคือเพิ่มสัญญาณ (signal) ชนิดใหม่สำหรับทั้งไซต์ เพื่อบ่งบอกว่าเป็นเว็บไซต์ที่มีคุณภาพหรือไม่ เพื่อนำมาคำนวณอันดับของเว็บเพจ กูเกิลยังแนะนำว่าการลบเนื้อหาที่ไม่มีคุณภาพออกไป อาจช่วยให้เนื้อหาอื่นของเว็บเดียวกันมีอันดับดีขึ้นได้ด้วยตอนนี้อัลกอริทึมใหม่เริ่มใช้งานแล้วบางส่วน และต้องรอประมาณ 2 สัปดาห์ถึงจะครบทั้งหมด

Increasing the size of a virtual disk

2012-11-09T19:13:00.000+07:00

Purpose

This article guides you through the process of increasing the size of a virtual disk. This procedure is necessary to accommodate data requirements that have changed since the creation of the virtual disk.

Resolution

Important information before you begin

Even though this article provides steps to increase the size of your virtual disk, the size of the disk partition does not increase as observed inside the guest operating system. You must follow steps related to your specific operating system to increase the size of the disk partition(s). For more information, see Increasing the size of a disk partition (1004071).

Caution: VMware recommends that you back up your virtual machine before increasing the size of virtual disks.

The procedure for increasing the size of a virtual disk differs between VMware products. Follow the section below that matches your product.

In all cases, confirm the following before increasing the size of the virtual disk:

All snapshots have been removed. For additional information, see Working with snapshots (1009402).
The virtual machine is powered off.

Note: In ESX 4.1, you can extend and add virtual disks to a virtual machine when it is powered on (after installing VMware Tools).

Instructional Notes

To follow the sections below, replace any reference to vm.vmdk with the full path to the virtual machine's virtual disk.

Note: If you have multiple .vmdk files with the same base name, use the file that does not include -flat or -s0 in its file name.

You may need to:

Locate the full path to a hosted (non-ESX host) virtual machine's virtual disk (.vmdk ) file. For more information, see Locating a hosted virtual machine's files (1003880).
Locate the full path to an ESX host's virtual machine's virtual disk (.vmdk ) files. For more information, seeVerifying that ESX virtual machine storage is accessible (1003751).

Workstation / Player 3.x / ACE Manager / Server / GSX

To increase the virtual disk from the command line:

Open a command prompt. For more information, see Opening a command or shell prompt (1003892).
Navigate to the product's installation directory. For more information, see Locating a VMware product's installation directory (1003897).
Type vmware-vdiskmanager -x 100Gb vm.vmdk and press Enter.

Note: Replace 100Gb with the actual size of virtual disk that you want. You can also specify Kb and Mb.
Follow the steps in Increasing the size of a disk partition (1004071) so the guest operating system is aware of the change in disk size.

For Workstation 7 and later and Player 3.x and later, you can increase the virtual disk from the GUI:

Select the virtual machine from the Inventory.
Click Edit Virtual Machine Settings.
Click Hard Disk.
Click Utilities > Expand, enter the new size, then click Expand.
Follow the steps in Increasing the size of a disk partition (1004071) so the guest operating system is aware of the change in disk size.

VMware Player 2.x / ACE Instance

It is not possible to directly change the size of a virtual machine's virtual disk if VMware Player 2.x is being used or if it is an ACE Instance.

If you are using an ACE Instance, the virtual disk size must be changed from the ACE Manager, then repackaged and redeployed.
If you are using VMware Player's 2.x, upgrade to VMware Player 3. This is a free download, available from ourDownload Center.

ESX / VI Client / vSphere

Notes:

In ESX 4.1, you can extend and add virtual disks to a virtual machine when it is powered on (after installing VMware Tools).
Ensure the user has sufficient permissions to carry out this task.
If the disks are clustered, they cannot be expanded through the vSphere client but instead through CLI. Please use the following command as an example:

# vmkfstools -X 6G -d eagerzeroedthick /vmfs/volumes/cs-ee-symmlun-001A/cormac.vmdk

This error may occur because of a number of different issues:

Failed to open the disk 'vm.vmdk' : A file was not found (0x1900000004)

If you experience this error, ensure that you can power on the virtual machine successfully and ensure that you remove all snapshots. For additional information, see Determining if a virtual machine is using snapshots (1004343). If the error persists, contact VMware Support.

If you have ESX 3.5 or newer:

Open VMware Infrastructure (VI) Client and connect to VirtualCenter or the ESX host.
Right-click the virtual machine.
Click Edit Settings.
Select Virtual Disk.
Increase the size of the disk.

Note: If this option is greyed out then the disk may be running on snapshots or the disk may be at the maximum allowed size depending on the block size of the datastore
Follow the steps in Increasing the size of a disk partition (1004071) so the guest operating system is aware of the change in disk size.

For earlier versions of ESX, you must use the Console. For more information, see Adding Space to an ESX Server Virtual Disk (994).

For further details on Virtual Disk Configuration, you can reference the vSphere Virtual Machine Administration Guide.

Lab Manager

Warning: Any attempt to resize a configuration's virtual disk in Lab Manager results in total data loss. Do not attempt to resize the virtual disk. Create a new virtual machine with a virtual disk of the size desired. When you have completed creating a new virtual machine, create a backup of the virtual machine from within the guest and then restore the backup to the newly created virtual machine.

Note: The following procedure applies to templates only. Do not attempt to resize a configuration.

Open Lab Manager.
Consolidate and then deploy the template to be resized. For instructions, see the Lab Manager User's Guide.
Connect to the ESX host where the template was deployed using VI Client.
Perform the disk resize according to the ESX section above.
Follow the steps in Increasing the size of a disk partition (1004071) so the guest operating system is aware of the change in disk size.

Reference

http://kb.vmware.com

VMware Fusion 3 support for Mac OS X Lion (10.7)

2012-11-09T19:10:00.003+07:00

Purpose

This article explains VMware's position on its support for running Fusion 3 on Mac OS X Lion, and the compatibility guidelines.

Resolution

VMware Fusion 4.x supports OS X 10.7 (Lion) as both a host and a guest operating system. For more information, see theVMware Fusion home page.

VMware Fusion 3.1.4 was designed for OS X 10.5 (Leopard) and OS X 10.6 (Snow Leopard). It is compatible with Mac OS X 10.7 (Lion), with some limitations. VMware Fusion 3.x is incompatible with Mac OS X 10.8 (Mountain Lion). VMware Fusion 2.x is incompatible with Mac OS X 10.7 (Lion).

If you are running an older version of VMware Fusion, upgrade to VMware Fusion 3.1.4 before upgrading to Lion.

For the best experience, reinstall Fusion after upgrading to Lion.

When running Fusion on Lion, these limitations are known to exist:

VMware Fusion 3.1.3 virtual machines do not start in Mac OS X 10.7.4 or later. For more information, see Fusion 3.1.3 virtual machines fail to start after upgrading to Mac OS X 10.7.4 (2020651).
The Migration Assistant, included with VMware Fusion, is not compatible with Mac OS X Lion. This is due to a change in file sharing components.

VMware recommends that a Snow Leopard-based Mac or vCenter Stand-Alone Converter be used to migrate an existing PC. The resulting virtual machine can then be used in Fusion running on Lion. For more information on Converter, see this article: Converting a physical machine for Fusion, Workstation, or Player using Converter Standalone (2005129).
Boot Camp partitions may not be accessible through Fusion after upgrading to Lion.

To work around this issue, delete the Boot Camp virtual machine from the library and recreate it. For more information, see A Boot Camp virtual machine fails to power on with a disk error (1003483).
Minor visual issues have been reported when using Mission Control with Unity mode.
Mac OS X 10.7 (Lion) Client and Server cannot be run as guests.
USB issues have been reported. These are due to incorrect filesystem permissions on the Mac. For more information, see USB devices fail after upgrading to Mac OS X Lion (10.7) (2004687).
The minimum RAM requirement for Lion itself is 2GB of RAM. This is an increase from Snow Leopard, and it may cause performance issues on Macs that only have 2GB of RAM or that allocate the majority of their free RAM to virtual machines. VMware recommends upgrading to at least 4GB of RAM. For more information about RAM allocation, see Investigating virtual machine resources in VMware Fusion (1022213).

VMware can provide best-efforts support if you choose to upgrade to Lion, but cannot guarantee a resolution for all issues.

Reference

http://kb.vmware.com

Hardware and firmware requirements for 64-bit guest operating systems

2012-11-09T19:09:00.000+07:00

Purpose

This article explains the host machine hardware and firmware requirements for installing virtual machines with 64-bit guest operating systems.

Note: 64-bit guests are not supported for ESX versions 2.5.x and earlier.

For information about installing Guest Operating Systems, see the Guest Operating System Installation Guide.

Resolution

VMware's virtual machine monitor has traditionally used segmentation to provide isolation between the guest operating system and the virtual machine monitor. This is necessary because the guest operating system and virtual machine monitor share the linear address space.

To determine whether or not your CPU is suitable for running 64-bit guest operating systems, VMware distributes a free utility. You can download the tool from our web site: Processor Check for 64-Bit Compatibility .

Note: This utility is provided without support from VMware and does not require ESX/ESXi, VMware Server or VMware Workstation to perform the check.

ESX/ESXi, VMware Workstation, Player, and VMware Server require a 64-bit CPU to run a 64-bit guest operating system.

VMware Fusion requires a 64-bit processor to run a 64-bit guest operating system or to run any Mac OS Guest. Mac OS Guests require hardware virtualization (VT), which VMware supports only on 64-bit processors. The Intel Core Solo and Core Duo processors are 32-bit, but the Core 2 Duo and newer processors are 64-bit.

Additional Information

Note: The information supplied in this section applies to older product versions.

Workstation 5.5 - 6.x, Player, and VMware Server 1.x support virtual machines with 64-bit guest operating systems only on host machines that have one of these supported 64-bit processors:

AMD Athlon 64, revision D or later
AMD Opteron, revision E or later
AMD Turion 64, revision E or later
AMD Sempron, 64-bit-capable, revision D or later (experimental support)
Intel EM64T VT-enabled processors (experimental support)

Note: In shopping for a processor that is compatible with Workstation or VMware Server 64-bit guests, you may be unable to determine the revision numbers of a given vendor's offering of AMD Athlon 64, Opteron, Turion 64, or Sempron processors. At this time, the only reliable way to determine whether or not any of these processors is a revision supported by VMware software is by noting the manufacturing technology (CMOS). Any of the AMD Athlon 64, Opteron, Turion 64, or Sempron processors whose manufacturing technology is 90nm SOI (.09 micron SOI) is compatible with Workstation or VMware Server 64-bit guests. Using this information, you should be able to determine — with the help of your vendor, or from the AMD web site — whether a particular Athlon 64 or Opteron processor model is compatible with Workstation or VMware Server 64-bit guests.

Note: The preceding link was correct as of June 21, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

AMD

Segmentation support is missing from the initial AMD64 processors (that is, revision C and earlier) while running in long mode. As a result, AMD64 processors prior to revision D do not have an efficient mechanism for isolating the virtual machine monitor from 64-bit guest operating systems. A limited form of segmentation was reintroduced in long mode, in revision D AMD64 processors. As a result, AMD64 processors must be revision D or later to run 64-bit guest operating systems.

Note: Because AMD Opteron and Turion processors do not ship in revision D, AMD Opteron and Turion 64 processors must be revision E or later to run 64-bit guest operating systems.

When reading AMD's documentation, revisions may be given in decimal format (rather than hexadecimal format). For example, Revision F may also be referred to as Revision 15.

For more information about AMD64, see http://www.amd.com/us/products/technologies/64-bit-computing/Pages/64-bit-computing.aspx .

Note: The preceding link was correct as of June 21, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

Intel

Intel CPUs require EM64T and VT support in the chip and in the BIOS.

Note: If VT is enabled on an ESX host, the vmx flag is found in /proc/cpuinfo.

Intel EM64T CPUs do not have segmentation support in long mode. If the Intel EM64T CPU is VT-capable, it comes with hardware virtualization support (Intel's Virtualization Technology). This hardware virtualization support allows VMware to work around the lack of segmentation, making it possible to run 64-bit guest operating systems on Intel EM64T VT-capable CPUs.

Notes:

Firmware/BIOS support is required to enable Intel Virtualization Technology. Some systems (particularly laptops) do not have the necessary firmware/BIOS support to enable Intel Virtualization Technology, and cannot run 64-bit guest operating systems.
In multi-processor systems, all processors must support compatible VT implementations. At a minimum, all processors must implement the same VMCS revision ID. In multi-processor systems with mixed processor steppings, 64-bit guest operating systems may not be supported.
Many servers that include CPUs with VT support might ship with VT disabled by default, and VT must be enabled manually. If your CPUs support VT but you do not see this option in the BIOS, contact your system vendor to request a BIOS version that lets you enable VT support.

For additional information, see the VMware Communities article Trouble-shooting Intel VT-x Issues.

Reference

http://kb.vmware.com

Converting a Windows physical machine fails with error: Unable to create a VSS snapshot

2012-11-09T19:05:00.002+07:00

Symptoms

Cannot convert a Windows physical machine

Converting a Windows physical machine fails

You see the error:

Unable to create a VSS snapshot

In Windows Event Viewer, you see the error:

Service Control Manager Event ID 7000
The Vstor2 P2V230 Virtual Storage Driver service failed to start due to the following error: The system cannot find the path specified

Cause

This issue occurs if the previous agent installation was not removed correctly and Vstor2P2V30.sys is installed and continues to exist from a previous conversion attempt with Converter 3.0.

Resolution

To workaround this issue:

Click Start > Run, type devmgmt.msc, and click OK. The Device Manager window opens.
Click View > Show Hidden Devices.
Expand Non-Plug and Play Devices.
Locate Vstor2 P2V30 Virtual Storage Driver.
Right-click Vstor2 P2V30 Virtual Storage Driver and click Uninstall.

Reference

http://kb.vmware.com

How to Upgrade to ESXi 5.1

2012-11-02T08:54:00.003+07:00

If you’re running the free version of ESXi 5.0 in your homelab or testing it at work, you might be wondering what’s the easy way to upgrade existing ESXi 5.0 installation to the latest ESXi 5.1 without much effort and without breaking your existing installation, without re-installing everything. Your existing VMs won’t be affected.

I’ve already wrote about patching ESXi without vCenter, but this time the command used slightly differ, and here I’m showing you the the steps which needs to be accomplished to upgrade to the latest ESXi 5.1 version. More advanced users can skip, because they’ll probably know this method.

This article is meant to be for every user who don’t uses vSphere update manager for this process. I’m writing it down here for my own bookmarking needs as well. -:)

As you might already read in my article about the changes to the ESXi, there isn’t any vRAM limitation on the free ESXi 5.1 but there is still the 2 physical CPU limit together with the 32Gb physical RAM limit. If not I’d recommend to read those 2 articles:

vSphere 5.1 licensing – vRAM is gone – rather good news, any more?

ESXi 5.1 Free with no vRAM limit but physical RAM limit of 32Gb

The upgrade process from ESXi 5 free version to ESXi 5.1 free version is very straightforward. It takes 3 or 4 steps to complete. All the VMs running on the server must be shut down, because a reboot of the physical host is necessary.

ESXi 5 Free – upgrade to ESXi 5.1 – the steps:

01. Download the offline bundle for ESXi 5.1 at VMware (you’ll need to login through My VMware, or if you don’t have an account, you can create one for free) – file called VMware-ESXi-5.1.0-799733-depot.zip . It’s a 298Mb zip file.

02. Activate SSH and shut down all your VMs running (if not already activated) . You can do it through the vSphere client. Configuration > Security Profile > Properties

03. Next thing you’ll need to do is to upload the bundle zip file which you just downloaded to the local (or shared) datastore of the ESXi server. You can use the vSphere client and the datastore browser for that or you can use the faster VeeamZIP Free by creating a copy job for the upload of the file to the datastore.

04. Connect by using Putty and execute the following command:

esxcli software profile update -d /vmfs/volumes/datastore1/VMware-ESXi-5.1.0-799733-depot.zip -p ESXi-5.1.0-799733-standard

UPDATE:

Or, you can also invoke this command:

esxcli software profile install -d /vmfs/volumes/datastore1/VMware-ESXi-5.1.0-799733-depot.zip -p ESXi-5.1.0-799733-standard

05. Reboot the server and you’re done.

In case you want to revert back, just press Shift+R at the boot loader screen…

reference

http://www.vladan.fr

Windows 8 / Windows Server 2012 Operating System does not boot or install on ESXi or ESX

2012-10-31T13:22:00.000+07:00

Symptoms

Windows 8 / Windows Server 2012 fails to boot or install on any version of ESXi or ESX

Windows 8 / Windows Server 2012 is not working

You cannot use Windows 8 / Windows Server 2012 in ESXi or ESX

Purpose

This article provides information on using Windows 8 / Windows Server 2012 in a vSphere environment.

Resolution

Like many of you, VMware is becoming familiar with Windows 8 / Windows Server 2012 preview. VMware is testing and enabling the support of Windows 8 / Windows Server 2012 on vSphere.

Note: Windows 8 / Windows Server 2012 will not be supported on ESXi/ESX 4.0 or 4.1.

Windows 8 / Windows Server 2012 is fully supported for ESXi 5.1. For more information, see What’s New in VMware vSphere 5.1.

Consider this guidance, which is based on testing Windows 8 / Windows Server 2012 up to build 8224:

Windows 8 Developer Preview / Windows Server 2012 Release Candidate does not boot on ESXi 5.0. To resolve this issue, you must install patch ESXi500-201112001 (Patch 02):
1. Download and install ESXi500-201112001 (Patch 02). For more information, see VMware ESXi 5.0, Patch Release ESXi500-201112001 (2007680).
2. Create a new virtual machine configured for either Windows 7 or Windows 2008 R2.
3. Enable 3D graphics or do not install VMware's WDDM video driver.
4. Install Windows 8 / Windows Server 2012 from Media.
5. Install VMware Tools.
  
  Note: VMware does not recommend installing VMware's WDDM video driver. Use the default VESA driver.
If you experience a black screen after installing VMware's WDDM video driver in a virtual machine with Windows 8 / Windows Server 2012, enable 3D graphics or reinstall the operating system and VMware Tools without VMware's WDDM video driver.
VMware does not currently recommend using USB xHCI with Windows 8 / Windows Server 2012. To work around this issue, remove the USB xHCI controller or use the USB EHCI+UHCI controller.

Note: Any changes to the virtual hardware must be preceded by a full shutdown on the command line (shutdown /s /t 0 /full). Otherwise, the Windows 8 / Windows Server 2012 hibernate-shutdown may not fully detect hardware changes and you may experience a blue diagnostic screen or triple fault at boot.
The vmxnet3 virtual NIC does not work in a Windows 8 / Windows Server 2012 virtual machine with ESXi 5.0. To work around this issue, use e1000e or e1000 NICs.

reference

http://kb.vmware.com

Location of ESXi 5.0 log files

2012-10-31T13:17:00.004+07:00

Purpose

This article provides the default location of log files on an ESXi 5.0 host.

For related information, see the Logging in vSphere 5.0 in Command-Line Management in vSphere 5.0 for Service Console Users.

For other products and versions, see Location of log files for VMware products (1021806).

Resolution

You can review ESXi 5.0 host log files:

From the Direct Console User Interface (DCUI). For more information, see About the Direct Console ESXi Interface in thevSphere 5.0 Installation and Setup Guide.
From the ESXi Shell. For more information, see the Log In to the ESXi Shell section in the vSphere 5.0 Installation and Setup Guide.
Using a web browser at https://HostnameOrIPAddress/host. For more information, see the HTTP Access to vSphere Server Files section in the vSphere Web Services SDK documentation.
Within an extracted vm-support log bundle. For more information, see Collecting diagnostic information for VMware ESX/ESXi using the vSphere Client (653) or Collecting diagnostic information for VMware ESX/ESXi using the vm-support command (1010705).
Using the vifs command line utility in the vCLI. For more information, see the vSphere Command-Line Interface documentation.

ESXi 5.0 Host Log Files

Logs for an ESXi 5.0 host are grouped according to the source component:

/var/log/auth.log: ESXi Shell authentication success and failure.
/var/log/dhclient.log: DHCP client service, including discovery, address lease requests and renewals.
/var/log/esxupdate.log: ESXi patch and update installation logs.
/var/log/hostd.log: Host management service logs, including virtual machine and host Task and Events, communication with the vSphere Client and vCenter Server vpxa agent, and SDK connections.
/var/log/shell.log: ESXi Shell usage logs, including enable/disable and every command entered. For more information, see the Managing vSphere with Command-Line Interfaces section of the vSphere 5 Command Line documentation andAuditing ESXi Shell logins and commands in ESXi 5.x (2004810).
/var/log/sysboot.log: Early VMkernel startup and module loading.
/var/log/boot.gz: A compressed file that contains boot log information and can be read using zcat /var/log/boot.gz|more.
/var/log/syslog.log: Management service initialization, watchdogs, scheduled tasks and DCUI use.
/var/log/usb.log: USB device arbitration events, such as discovery and pass-through to virtual machines.
/var/log/vob.log: VMkernel Observation events, similar to vob.component.event.
/var/log/vmkernel.log: Core VMkernel logs, including device discovery, storage and networking device and driver events, and virtual machine startup.
/var/log/vmkwarning.log: A summary of Warning and Alert log messages excerpted from the VMkernel logs.
/var/log/vmksummary.log: A summary of ESXi host startup and shutdown, and an hourly heartbeat with uptime, number of virtual machines running, and service resource consumption. For more information, see Format of the ESXi 5.0 vmksummary log file (2004566).

Note: For information on sending logs to another location (such as a datastore or remote syslog server), see Configuring syslog on ESXi 5.0 (2003322).

reference
http://kb.vmware.com

Windows 2000 Terminal Server performance degraded when running under ESXi 5.0

2012-10-18T09:19:00.002+07:00

Symptoms

Windows 2000 Terminal Server shows degraded performance when running under ESXi 5.0.
Performance Charts for the virtual machine show a much higher CPU usage compared to the same virtual machine running on vSphere ESX/ESXi 4.x.
Windows guest operating system task manager shows a very high CPU usage as soon as multiple Terminal Server users are connected.
The guest operating system appears to intermittently become unresponsive due to the CPU load. A CPU spike for the System process may occur.
Changing the virtual machine's hardware to version 8 or increasing the vCPU count does not resolve the issue.
After migrating the virtual machine back to a host running ESX/ESXi 4.x, the virtual machine returns to normal behavior.

Cause

This behavior is caused by changes to the Binary Translation (BT) Monitor Mode of the VMware Hypervisor in version 5.0. These changes were included to address an issue related to coherency of translated code.

Resolution

This issue is resolved in ESXi 5.0 Update 1, for further information see the Resolved Issues section in the VMware ESXi 5.0 Update 1 Release Notes.

To workaround the issue on the previous versions of ESXi 5.0, perform one of these options:

Migrate the virtual machine back to an ESX/ESXi 4.x host.

This option is only possible if the virtual machine is still using Virtual Hardware Version 7 or lower. If the Virtual Hardware Version has already been upgraded to 8, you can use VMware Converter Standalone to downgrade the Hardware Version. For more information, see VMware vCenter Converter Standalone User's Guide.
Manually change the Monitor Mode of the virtual machine from Binary Translation (BT) Monitor Mode ("Automatic" for Windows 2000 virtual machines) to use:
- Intel VT-X/AMD-V for instruction set virtualization and software for MMU virtualization (HV)
  
  Or
- Intel VT-X/AMD-V for instruction set virtualization and Intel EPT/AMD RVI for MMU virtualization (HWMMU)

The appropriate option depends on the features provided by your CPU. To identify which features your CPU is capable of, check MONITOR MODE: allowed modes in the virtual machine's vmware.log (in the virtual machine folder on the datastore). For example:

2011-11-21T10:14:07.154Z| vmx| MONITOR MODE: allowed modes : BT HV HWMMU
2011-11-21T10:14:07.154Z| vmx| MONITOR MODE: user requested modes : BT HV HWMMU
2011-11-21T10:14:07.154Z| vmx| MONITOR MODE: guestOS preferred modes: BT HWMMU HV
2011-11-21T10:14:07.154Z| vmx| MONITOR MODE: filtered list : BT HWMMU HV
Where:

allowed modes refers the mode your hardware is capable of

user requested modes refers to the setting defined in the virtual machine configuration

guestOS preferred modes refers to the default values for the selected guest operating system

filtered list refers to the actual monitor mode used by the Hypervisor (in order of appearance)

reference
http://kb.vmware.com

ESXi 5.0 issues with PXE booting virtual machines with Citrix Provisioning Server

2012-10-18T09:18:00.003+07:00

Symptoms

After upgrading to ESXi 5.0, PXE servers provided by Citrix Provisioning Server report issues while PXE booting a virtual machine.

A virtual machine becomes unresponsive during the boot process at:

CLIENT MAC ADDR: xx xx xx xx xx xx

If the virtual machine is rebooted from within the guest operating system, the virtual machine fails to PXE boot. However, if the virtual machine is reset or powered off/on, the virtual machine PXE boots correctly.

This issue does not occur with earlier versions of ESXi/ESX.

This issue may occur on virtual machines regardless of the network adapter (such as e1000 or vmxnet3).

Cause

This issue is caused by the mishandling of pending interrupts.

Resolution

This issue is resolved in vSphere 5.0 Update 1.

Note: Before implementing this workaround, confirm with Citrix if the version of Citrix Provisioning Server being used is compatible with vSphere 5.0.

To work around this issue, configure the Citrix Provisioning Bootstrap and select Interrupt Safe Mode. For more information, seeConfiguring the Bootstrap File From the Console on the Citrix documentation site.

For more information, see the Citrix Knowledge Center article, vSphere 5 Support for Provisioning Server 5.6.x and 6.0.

reference
http://kb.vmware.com

Windows 8 Release Preview and Windows Server 2012 Release Candidate fail when starting for the first time after the installation

2012-10-18T09:18:00.001+07:00

Symptoms

After installing Windows 8 (64bit) Release Preview or Windows Server 2012 Release Candidate on an ESXi 5.0 Update 1 host or the VMware Workstation Tech Preview, you experience these symptoms:

When starting for the first time after the installation, the virtual machine stops responding and displays a black screen with a white status ring
Restarting the virtual machine does not resolve the issue

Resolution

To resolve this issue, use one of these workarounds:

Change the virtual machine to use EFI instead of BIOS.
1. Right-click the virtual machine and click Power > Shut Down Guest.
2. Right-click the virtual machine and click Edit Settings.
3. Click the Options tab.
4. Click Boot Options.
5. Click EFI under Firmware.
6. Click OK.
7. Power on the virtual machine.
Add vmGenCounter.enable = FALSE to the .vmx file of the virtual machine.

Right-click the virtual machine and click Power > Shut Down Guest.
Right-click the virtual machine and click Edit Settings.
Click the Options tab.
Under Advanced, click General.
Click Configuration Parameters.
Click Add Row.
Under name, enter vmGenCounter.enable.
Under value, enter False.
Click OK to save the changes and then close the window.
Power on the virtual machine.

Note: The workaround involving adding the vmGenCounter.enable parameter to the virtual machine .vmx file may cause the new snapshot protection for domain controllers introduced in Windows 8/Windows Server 2012 to stop functioning. For more information, see the Microsoft Technet Article Active Directory Domain Services (AD DS) Virtualization.

The preceding link was correct as of June 22, 2012. If you find this link is broken, provide feedback and a VMware employee will update the link.

reference

http://kb.vmware.com

Networking does not work in a cloned Linux virtual machine

2012-10-18T09:17:00.002+07:00

Symptoms

The network configuration in the Linux Guest operating system still refers to the original MAC addresses.

Mismatch between the MAC addresses in the virtual machine settings and the Linux operating system.

Networking does not work in a cloned Linux virtual machine.

Cause

When a virtual machine is cloned, the network adapter(s) are given new MAC addresses.

Resolution

To change the MAC address of the Linux operating system:

Redhat

Connect the vSphere Client to the vCenter Server.
Click the virtual machine.
Click Edit Settings.
Click Network adapter and take note of the MAC Address:

For example, 00:0c:29:c1:9e:66
Power on the Linux virtual machine.
Open a console and log in as root.
Change directory to etc/sysconfig/network-scripts.
Edit ifcfg-eth0 using a plaint text editor and update the MAC address to reflect the MAC address in Step 3.

For more information, see Editing files on an ESX host using vi or nano (1020302).
Activate the ethernet card by executing ifup-eth0.

Note: ifup eth0 may be required in some instances to activate the ethernet card.

SUSE

Connect to the vSphere Client to the vCenter Server.
Select the virtual machine and click Edit Settings.
Click Network adapter and take note of the MAC address:

For example, 00:0c:29:c1:9e:66
Power on the Linux virtual machine.
Change directory to /etc/sysconfig/network and run ls -l if*
/etc/sysconfig/network # ls -l if*

# ifcfg-eth-id-00:50:56:a0:17:d7
Rename this file to match the MAC address in Step 3:

#mv ifcfg-eth-id-00:50:56:a0:17:d7 ifcfg-eth-id-00:0c:29:c1:9e:66
Activate the ethernet card by executing ifup eth0.

reference

http://kb.vmware.com

Cannot remount a datastore after an unplanned PDL

2012-10-18T09:16:00.002+07:00

Symptoms

After a storage device has unexpectedly unpresented from the storage array, you are unable to mount it again

There was a running virtual machine when storage device went offline

ESXi 5.0 host cannot mount the storage after the LUN is online again

In the vmkernel log file, you see entries similar to:

2012-02-13T22:47:44.243Z cpu36:5590)Vol3: 1665: Error refreshing FD resMeta: Device is permanently unavailable
2012-02-13T22:47:44.281Z cpu34:5590)VC: 1449: Device rescan time 165 msec (total number of devices 75)
2012-02-13T22:47:44.281Z cpu34:5590)VC: 1452: Filesystem probe time 504 msec (devices probed 48 of 75)
2012-02-13T22:47:44.406Z cpu38:5590)ScsiDevice: 4592: naa.6006016058201700354179be0c6fdf11 device :Open count > 0, cannot be brought online
2012-02-13T22:47:44.654Z cpu34:5590)Vol3: 647: Couldn't read volume header from control: Invalid handle
2012-02-13T22:47:44.654Z cpu34:5590)FSS: 4333: No FS driver claimed device 'control': Not supported
2012-02-13T22:47:45.008Z cpu38:5590)ScsiDeviceIO: 2316: Cmd(0x4124c0ea2e80) 0x28, CmdSN 0x70509 to dev "naa.6006016058201700354179be0c6fdf11" failed H:0x1 D:0x0 P:0x0 Possible sense data: 0x0 0x0 0x0.

Cause

This is an expected behaviour because the I/O on LUNs did not terminate gracefully. To properly remove a datastore, seeUnpresenting a LUN in ESXi 5.x (2004605).

Resolution

To resolve this issue:

Run this command to see the world that has the device open for the LUN:

#esxcli storage core device world list -d naa-id
For example:

#esxcli storage core device world list -d naa.6006016058201700354179be0c6fdf11
You see output similar to:

Device World ID Open Count World Name
------------------------------------ -------- ---------- ----------
naa.6006016058201700354179be0c6fdf11 2060 1 idle0
If a VMFS volume is using the device indirectly, the world name includes the string idle0. If a virtual machine uses the device as an RDM, the virtual machine World ID is displayed. If any other process is using the raw device, the corresponding information is displayed.
Run this command to list all virtual machines running on the ESXi 5.0 host and identify the virtual machine registered on that LUN:

#esxcli vm process list
Run this command to kill the virtual machine World ID:

#esxcli vm process kill --type=force --world-id World ID
For example:

#esxcli vm process kill --type=force --world-id=12131
Rescan the storage using this command:

#esxcfg-rescan -u vmhba#
Run this command to see the device state:

#esxcli storage core device list -d naa-id
If the issue persists, reboot the ESXi 5.0 host where virtual machine was registered.

reference

http://kb.vmware.com

Installing ESXi 5.0 fails with the error: Fatal error: 32 (Syntax) or Fatal error: 4 (Unsupported)

2012-10-18T09:14:00.001+07:00

Resolution

To workaround this issue, boot into the ESXi host's BIOS and disable UEFI (Unified Extensible Firmware Interface) or EFI.For more information on how to perform this change, consult your hardware vendor.

reference

http://kb.vmware.com

Running VMware CLI 4.x commands on ESXi 5.0 hosts

2012-10-18T09:12:00.003+07:00

Purpose

This article provides information about running vSphere Command Line Interface (CLI) 4.x commands on ESXi 5.0 hosts.

Resolution

As ESXi 5.0 is a new architecture with new features, VMware strongly recommends that you use vSphere CLI 5.0 to manage ESXi 5.0 hosts.

If you have to use vSphere CLI 4.x, this table outlines support for the commands:

Command	Support
svmotion.pl	Not Supported
vicfg-advcfg.pl	Supported
vicfg-cfgbackup.pl	Supported
vicfg-dns.pl	Supported
vicfg-dumppart.pl	Supported
vicfg-hostops.pl	Supported
vicfg-ipsec.pl	Supported
vicfg-iscsi.pl	Not Supported
vicfg-module.pl	Supported
vicfg-mpath.pl	Not Supported
vicfg-nas.pl	Supported
vicfg-nics.pl	Supported
vicfg-ntp.pl	Supported
vicfg-rescan.pl	Supported
vicfg-route.pl	Supported
vicfg-scsidevs.pl	Not Supported
vicfg-snmp.pl	Supported
vicfg-syslog.pl	Supported
vicfg-user	Supported
vicfg-vmknic.pl	Supported
vicfg-vswitch.pl	Supported
vifs.pl	Supported
vicfg-volume	Not Supported
vihostupdate.pl	Not Supported
vihostupdate35.pl	Not Supported
vmkfstools	Supported
vmware-cmd.pl	Supported

reference

http://kb.vmware.com

ESXi 5.0 host stops saving logs to storage

2012-10-18T09:10:00.000+07:00

ESXi 5.0 host stops saving logs to storage

Details

The ESXi host stops saving log to local storage for various reasons:

The local storage is out of space.

There is a network or SAN failure or interruption for remote storage locations.

The log file is corrupt.

There is a disk failure.

Solution

To resolve this issue, perform one of the following workarounds:

Use the following command to inspect the "Log Output" field to find where the directory logs are stored.

# esxcli system syslog config get

Test the connectivity if the location is a remote datastore (NFS or SAN).

Use the following command to determine the amount of free datastore disk space.

# esxcli storage filesystem list

Inspect the file /var/log/.vmsyslogd.err for low-level debugging information.

After you identify the cause of the problem, use the following command to reload the syslog server and enable disk logging to continue.

# esxcli system syslog reload

Note: You can configure the rotation and size parameters at a global and individual log-file level with commands located in the file esxcli system syslog. If you run out of disk space for logs frequently, consider changing the rotation and size parameters to reduce the amount of disk space consumed by logs.

reference

http://kb.vmware.com

Moving or copying virtual disks in a VMware environment

2012-10-17T08:47:00.002+07:00

Solution

Existing VMware Products and Features

To support certain internal operations, ESX installations include a subset of standard Linux configuration commands, for example, network and storage configuration commands. Using these commands to perform configuration tasks can result in serious configuration conflicts and render some ESX functions unusable. Always work through the vSphere Client when configuring ESX unless otherwise instructed in vSphere documentation or by VMware Technical Support.

Prior to manually moving or copying virtual machine disk files, consider using existing VMware features which can accomplish similar desired results. These VMware features include:

Converting Virtual Machines with VMware Converter. For more information, see VMware Converter Standalone Documentation.
Converting Virtual Machines with VMware vCenter Converter. For more information, see VMware vCenter Converter Administration Guide under the applicable VMware product version.
Live Migrate, Cold Migrate, Clone, or Storage vMotion with VMware vCenter or VMware VirtualCenter. For more information, see the Migrating Virtual Machines section for the applicable VMware product version.
Backing up virtual machines with VMware Consolidated Backup. For more information, see the Virtual Machine Backup Guide for the applicable VMware product version.

Considerations and Caveats

There are several caveats specific to moving or relocating virtual machine disk files:

Different versions of VMware products may have different implementations of a virtual disk file. For more information, seeVirtual Machine Disk Format (VMDK).
When using snapshots, a virtual machine's virtual disks can be comprised of multiple VMDK files which are part of an interdependent chain. For more information, see the Disk Chaining and Redo Logs section in the VDDK API documentation.
To prevent performance and data management related issues on ESX, avoid the use of scp, cp, or mv for storage operations; instead use the vmkfstools, the Virtual Machine Importer tool from VMware. For more information regarding the usage of tools within the service console, see Third-Party Software in the Service Console.

Prior to copying virtual machine files

To avoid any potential issues involving snapshots and inconsistent disk chains, we must ensure that the virtual machine does not have any snapshots. Moving virtual machines with snapshots is outside of the scope of this article, and VMware strongly recommends using one of the alternate methods described above. Also, we must know exactly where the virtual disk file we want to move is located as well as ensure that the virtual machine is powered off.

These steps outline what to do prior to doing an operation to virtual disks from the vSphere/VI Client connected to either vCenter or ESX:

Connect to the ESX host using the vSphere/VI Client with administrator credentials..
Ensure that the virtual machine that uses the virtual disk file does not have any snapshots by right-clicking the virtual machine, and clicking Snapshot > Snapshot Manager.
Make note of the datastore and location of the virtual disk files that you want to copy by right-clicking the virtual machine, and clicking Edit Settings. Click on the virtual disk, and refer to the Disk File portion of the Virtual Machine Properties.
Power off the virtual machine.

Note: If there is no virtual machine to receive the virtual disk files, you may want to create the virtual machine in advance to establish the destination of the move or copy operation.

These steps outline what should be done prior to doing an operation to virtual disks from VMware Workstation:

Open VMware Workstation, and click on the virtual machine which has the virtual disk you wish to conduct an operation on.
Click VM > Snapshot > Snapshot Manager, and remove any preexisting.
Click VM > Settings > Options Tab make note of the Working Directory section on the bottom left of the Virtual Machine Settings window.
Click VM > Power > Shut Down Guest to power off the virtual machine.

Note: If there is no virtual machine to receive the virtual disk files, you may want to create the virtual machine in advance to establish the destination of the move or copy operation.

If you want to commit snapshots via the ESX service console, see Committing snapshots from within the Service Console (1006847).

Copying virtual disk files using the ESX service console

Log into the ESX host as root using either a remote console or SSH. For details on how to enable SSH, see Enabling root SSH login on an ESX host (8375637).
In the event that the virtual machine which is using the virtual disk is using snapshots, you must consolidate those snapshot prior to performing any storage operations.
Run the command vmware-cmd -l command to list all full paths to the configuration (vmx) files of the virtual machines registered to this host.

Example:

/ vmfs/volumes/478e0d5b-3535f6a8-0ee2-0017a446ae31/VMtest/VMtest.vmx
Note: The full path of the configuration file is identified by for the rest of this article.
Run the vmware-cmd stop command to shutd own the desired virtual machine.
Run the grep -i vmdk command to list all virtual disk files associated with the virtual machine.

scsi0:0.fileName = "VMtest.vmdk" scsi0:0.fileName = "/vmfs/volumes/478e0d5b-3535f6a8-0ee2-0017a446ae31/VMtest_1.vmdk"
Note: These entries may not include the full path to the directory. If a full path is not listed, refer to the full path of the value. The full path of the source virtual disk will be identified by for the rest of the article.

Warning: If the file name ends with -#######.vmdk, then your virtual machine is still running off of a snapshot. If you find that these files are present, but you do not have any snapshots in the snapshot manager, see Committing snapshots when there are no snapshot entries in the snapshot manager (1002310).
Run vmkfstools -i where is the destination of where you would like to file to be copied.

Note: Syntax from older versions of ESX may vary. For ESX 2.5.X. see Examples of Using vmkfstools from the ESX 2.5.X documentation.

Copying virtual disk files using the vSphere Command Line Interface for ESX and ESXi

Unlike ESX, ESXi does not have a service console. To copy files, use the vifs utility that comes with the vSphere Command Line Interface. The vifs command performs common operations such as copy, remove, get (download), and put (upload) files. The command is supported against ESX/ESXi hosts but not against vCenter Server systems. Use the vifs command to perform the file operation on the virtual machine files. The syntax and examples on using the vifs command can be found in the vSphere Command-Line Interface Installation and Reference Guide.

Copying virtual disk files using the vSphere/VI Client datastore browser for ESX and ESXi

The datastore Browser allows you to manage the contents of datastores in the vSphere/VI Client inventory. You can use the Datastore Browser to do these tasks:

View or search the contents of a datastore.
Add a virtual machine or template stored on a datastore to the vSphere/VI Client inventory.
Copy or move files from one location to another, including to another datastore.
Upload a file from the client computer to a datastore.
Download a file from a datastore to the client computer.
Delete or rename files on a datastore.

The Datastore Browser operates in a manner similar to file system applications like Windows Explorer. It supports many common file system operations, including copying, cutting, and pasting files. The Datastore Browser does not support drag-and-drop operations. For detailed instructions on using the Datastore Browser, see the vSphere/VI Client online help.

Copying virtual disk files using a web browser for ESX and ESXi

ESX and ESXi servers have a built in web service which allows you to access files via a web browser. Although this method of copying files is only one way, and does not allow you to upload files, it may be a good alternative in certain situations. To access these files, use this convention:

Open a web browser.
Open the http:///folder URL where the the is the IP or DNS name of the ESX host.
Enter the appropriate credentials when prompted.
Click the ha-datacenter link.
Browse to and download the desired virtual disk file.

Note: When using the browser to move and copy virtual disk files in ESX, you must copy both the flat file, and the descriptor file. For example, if a virtual machine disk has a name of disk.vmdk, it would have a corresponding disk-flat.vmdk file which needs to be copied or moved as well.

Copying virtual disk files to and from VMware Server or a VMware desktop product

VMware desktop products such as VMware Workstation and VMware ACE include the VMware Virtual Disk Manager utility. These are some examples of VMware Virtual Disk Manager utility:

vmware-vdiskmanager -n mydisk.vmdk "..\\myNewDisk.vmdk"

vmware-vdiskmanager -n mydisk.vmdk "..\\mydisk.vmdk"

For more information regarding the Virtual Disk Manager utility, see the Virtual Disk Manager User's Guide.

Copying virtual disk files across the network to and from different platforms

Moving virtual disk files across a network can be accomplished in many ways and on many platforms. These options exist to transport files across to different platforms:

FTP file transfer
SCP file transfer
NFS shares
Windows File Sharing (CIFS shares)

reference

http://kb.vmware.com

VM Snapshot Size (GB) alarm incorrectly triggers on virtual machines with no snapshots

2012-10-17T08:43:00.002+07:00

Symptoms

In VMware vCenter Server 5.1:

You configured a vCenter Server alarm to send alarms when virtual machines are running from snapshots
The alarm is falsely triggered even when the virtual machine does not have snapshots
You created the VM Snapshot Size (GB) alarm in vCenter Server
You see false alarms for multiple virtual machines in the inventory

Resolution

This is a known issue, and is currently being reviewed by VMware.

This article will be updated as information becomes available.

To work around this issue, disable the VM Snapshot Size (GB) alarm in VMware vCenter 5.1.

reference

http://kb.vmware.com

Increasing the size of a virtual disk

2012-10-17T08:41:00.002+07:00

Purpose

Resolution

Important information before you begin

Caution: VMware recommends that you back up your virtual machine before increasing the size of virtual disks.

The procedure for increasing the size of a virtual disk differs between VMware products. Follow the section below that matches your product.

In all cases, confirm the following before increasing the size of the virtual disk:

All snapshots have been removed. For additional information, see Working with snapshots (1009402).
The virtual machine is powered off.

Note: In ESX 4.1, you can extend and add virtual disks to a virtual machine when it is powered on (after installing VMware Tools).

Instructional Notes

You may need to:

Locate the full path to a hosted (non-ESX host) virtual machine's virtual disk (.vmdk ) file. For more information, see Locating a hosted virtual machine's files (1003880).
Locate the full path to an ESX host's virtual machine's virtual disk (.vmdk ) files. For more information, seeVerifying that ESX virtual machine storage is accessible (1003751).

Workstation / Player 3.x / ACE Manager / Server / GSX

To increase the virtual disk from the command line:

Open a command prompt. For more information, see Opening a command or shell prompt (1003892).
Navigate to the product's installation directory. For more information, see Locating a VMware product's installation directory (1003897).
Type vmware-vdiskmanager -x 100Gb vm.vmdk and press Enter.

Note: Replace 100Gb with the actual size of virtual disk that you want. You can also specify Kb and Mb.
Follow the steps in Increasing the size of a disk partition (1004071) so the guest operating system is aware of the change in disk size.

For Workstation 7 and later and Player 3.x and later, you can increase the virtual disk from the GUI:

Select the virtual machine from the Inventory.
Click Edit Virtual Machine Settings.
Click Hard Disk.
Click Utilities > Expand, enter the new size, then click Expand.
Follow the steps in Increasing the size of a disk partition (1004071) so the guest operating system is aware of the change in disk size.

VMware Player 2.x / ACE Instance

It is not possible to directly change the size of a virtual machine's virtual disk if VMware Player 2.x is being used or if it is an ACE Instance.

If you are using an ACE Instance, the virtual disk size must be changed from the ACE Manager, then repackaged and redeployed.
If you are using VMware Player's 2.x, upgrade to VMware Player 3. This is a free download, available from ourDownload Center.

ESX / VI Client / vSphere

Notes:

In ESX 4.1, you can extend and add virtual disks to a virtual machine when it is powered on (after installing VMware Tools).
Ensure the user has sufficient permissions to carry out this task.

This error may occur because of a number of different issues:

Failed to open the disk 'vm.vmdk' : A file was not found (0x1900000004)

If you have ESX 3.5 or newer:

Open VMware Infrastructure (VI) Client and connect to VirtualCenter or the ESX host.
Right-click the virtual machine.
Click Edit Settings.
Select Virtual Disk.
Increase the size of the disk.

Note: If this option is greyed out then the disk may be running on snapshots or the disk may be at the maximum allowed size depending on the block size of the datastore
Follow the steps in Increasing the size of a disk partition (1004071) so the guest operating system is aware of the change in disk size.

For earlier versions of ESX, you must use the Console. For more information, see Adding Space to an ESX Server Virtual Disk (994).

For further details on Virtual Disk Configuration, you can reference the vSphere Virtual Machine Administration Guide.

Lab Manager

Note: The following procedure applies to templates only. Do not attempt to resize a configuration.

Open Lab Manager.
Consolidate and then deploy the template to be resized. For instructions, see the Lab Manager User's Guide.
Connect to the ESX host where the template was deployed using VI Client.
Perform the disk resize according to the ESX section above.
Follow the steps in Increasing the size of a disk partition (1004071) so the guest operating system is aware of the change in disk size.

reference

http://kb.vmware.com

TCP and UDP Ports required to access vCenter Server, ESXi/ESX hosts, and other network components

2012-10-17T08:36:00.003+07:00

Purpose

These services and agents are commonly present in a vSphere environment:

CIM HTTP server (insecure service)
CIM HTTPS server
FTP client (insecure service)
FTP server (insecure service)
iSCSI software client
NFS client (insecure service)
NFS server (insecure service)
NIS client
NTP client
SMB client (insecure service)
SNMP server
SSH client
SSH server
Syslog client
Telnet client (insecure service)
Telnet server (insecure service)
Other supported management agents that you install

vCenter Server, ESX hosts, and other network components are accessed using predetermined TCP and UDP ports. If you manage network components from outside a firewall, you may be required to reconfigure the firewall to allow access on the appropriate ports.

This article provides information on the ports required for VMware products.

For more information, see the Configuration Guide / Security Guide for your product:

Resolution

TCP and UDP ports should be modified for each of these products:

AppSpeed
Auto Deploy Server
Consolidated Backup
Converter 3.x
Converter 4.x
Converter 5.x
Data Recovery
ESX 3.x
ESX 4.x
ESXi 3.x
ESXi 4.x
ESXi 5.x
ESXi Dump Collector
ESXi Syslog Collector
Guided Consolidation
Heartbeat
Lab Manager
Orchestrator
Site Recovery Manager 1.x-4.x
Site Recovery Manager 5.x
Stage Manager
Update Manager
vCenter Server 2.5.x
vCenter Server 4.x
vCenter Server 5.x
vCenter Server Appliance: See Required ports for vCenter Server Appliance 5.0 (2012773)
vCenter Infrastructure Navigator 1.x
vCloud Usage Meter
vCenter Operations Standard 1.x
vCenter Operations Manager (vApp) 5.x
vCenter Operations Manager (Standalone) 5.x
View 3.x
View 4.0.x
View 4.5.x
View 4.6.x
View 5.x
View/VDM 2.x
vShield 1.x
vShield 4.x
vSphere Data Protection: See Required ports for vSphere Data Protection 5.1 (2034929)
vSphere Management Assistant

Ports used with the VI / vSphere client are also listed in a separate table at the end of this article.

Product	Port	Protocol	Source	Target	Purpose
AppSpeed	80	TCP	AppSpeed Server	vCenter Server 4	vCenter proxy interface. Used only during setup to verify the proxy is setup correctly. Port 80 is the default Web Service Port, but a different TCP port can be configured in vCenter Server 4.
AppSpeed	443	TCP	AppSpeed Server	vCenter Server 4	Default port for communications. A different TCP port can be configured in vCenter Server 4.
AppSpeed	22	TCP	AppSpeed Server	AppSpeed Probe	Connections to the probes to access the probes outside of the VPN.
AppSpeed	123	TCP	AppSpeed Server	AppSpeed Probe	NTP services
AppSpeed	1194	TCP/UDP	AppSpeed Server	AppSpeed Probe	Communications over OpenVPN
Auto Deploy Server	6501	TCP	ESXi	vCenter Server	Auto Deploy service
Auto Deploy Server	6502	TCP	ESXi	vCenter Server	Auto Deploy management
Consolidated Backup	443	TCP	VCB Proxy Server	vCenter Server	Required for VCB and vcbMounter communication and backup processes
Consolidated Backup	443	TCP	VCB Proxy Server	ESXi/ESX Host	Required for VCB and vcbMounter communication and backup processes
Converter 3.x	137	UDP	vCenter Converter Server	Source Computer to be converted	For hot migration. Not required if the source computer does not use NetBIOS
Converter 3.x	138	UDP	vCenter Converter Server	Source Computer to be converted	For hot migration. Not required if the source computer does not use NetBIOS
Converter 3.x	139	TCP	vCenter Converter Server	Source Computer to be converted	For hot migration. Not required if the source computer does not use NetBIOS
Converter 3.x	443	TCP	Source Computer to be converted	ESXi/ESX Host	Required for destination VM access when target is ESXi/ESX/vCenter
Converter 3.x	443	TCP	Source Computer to be converted	vCenter Server	Required if vCenter Server is the conversion target
Converter 3.x	443	TCP	vCenter Converter Server	vCenter Server	Required if vCenter Server is the conversion target
Converter 3.x	443	TCP	vCenter Converter Server	ESXi/ESX Host	Required for system conversion
Converter 3.x	445	TCP	vCenter Converter Server	Source Computer to be converted	Required for system conversion. Not required if the source computer uses NetBIOS
Converter 3.x	902	TCP	Source Computer to be converted	ESXi/ESX Host	Required for data transport during cloning of system to be converted to target ESXi/ESX Host
Converter 4.x	22	TCP	Helper Virtual Machine	Source Computer to be converted	Required for conversion of Linux-based source computers (data flows from source to VM)
Converter 4.x	22	TCP	vCenter Converter Server	Source Computer to be converted	Required for conversion of Linux-based source computers
Converter 4.x	137	UDP	vCenter Converter Server	Source Computer to be converted	For hot migration. Not required if the source computer does not use NetBIOS
Converter 4.x	138	UDP	vCenter Converter Server	Source Computer to be converted	For hot migration. Not required if the source computer does not use NetBIOS
Converter 4.x	139	TCP	vCenter Converter Server	Source Computer to be converted	For hot migration. Not required if the source computer does not use NetBIOS
Converter 4.x	443	TCP	vCenter Converter Client	vCenter Converter Server	Only required if the Converter Client and Converter Server were installed on different systems
Converter 4.x	443	TCP	Source Computer to be converted	ESXi/ESX Host	Required for destination VM access when target is ESXi/ESX/vCenter
Converter 4.x	443	TCP	Source Computer to be converted	vCenter Server	Required if vCenter Server is the conversion target
Converter 4.x	443	TCP	vCenter Converter Server	vCenter Server	Required if vCenter Server is the conversion target
Converter 4.x	443	TCP	vCenter Converter Server	ESXi/ESX Host	Required for system conversion
Converter 4.x	443	TCP	vCenter Converter Server	Helper Virtual Machine	Required for conversion of Linux-based source computers
Converter 4.x	445	TCP	vCenter Converter Server	Source Computer to be converted	Required for system conversion. Not required if the source computer uses NetBIOS
Converter 4.x	902	TCP	Source Computer to be converted	ESXi/ESX Host	Required for data transport during cloning of system to be converted to target ESXi/ESX Host
Converter 4.x	9089, 9090	TCP	vCenter Converter Server	Source Computer to be converted	Required for system conversion. Remote agent deployment
Converter 5.x	22	TCP	Converter Standalone server	powered-on source machine	Used to establish an SSH connection between the Converter Standalone server and the source Linux machine
Converter 5.x	137	UDP	Converter Standalone server	powered-on source machine	For hot migration. Not required if the source computer does not use NetBIOS
Converter 5.x	138	UDP	Converter Standalone server	powered-on source machine	For hot migration. Not required if the source computer does not use NetBIOS
Converter 5.x	139	TCP	Converter Standalone server	powered-on source machine	For hot migration. Not required if the source computer does not use NetBIOS
Converter 5.x	443	TCP	Converter Standalone server	vCenter Server	Required only if theconversion destination is a vCenter Server
Converter 5.x	443	TCP	Converter Standalone client	Converter Standalone server	Required only if the Converter Standalone server and Linux client components are on different machines
Converter 5.x	443	TCP	Converter Standalone client	vCenter server	Required only if the Converter Standalone server and client components are on different machines
Converter 5.x	22	TCP	Powered-on Source Linux machine	ESXi/ESX Host	Uses secure connection port 22 to Host
Converter 5.x	443, 902	TCP	Powered-on Source Windows machine	ESXi/ESX Host	Required for data transfer to destination ESXi/ESX host
Converter 5.x	445	TCP	Converter Standalone server	powered-on source machine	Required for system conversion. Not required if the source computer uses NetBIOS
Converter 5.x	9089	TCP	Converter Standalone server	powered-on source machine	Required for system conversion. Remote agent deployment
Data Recovery	443	TCP	Data Recovery Appliance	vCenter Server	VDR to vCenter Server communications
Data Recovery	902	TCP	Data Recovery Appliance	ESX Host	VDR to ESX communications
Data Recovery	22024	TCP	Data Recovery vSphere Client Plug-in	Data Recovery Appliance	Data Recovery management
ESX 3.x	21	TCP	FTP Client	ESX Host	FTP
ESX 3.x	21	TCP	ESX Host	FTP Server	FTP
ESX 3.x	22	TCP	SSH Client	ESX Host	SSH
ESX 3.x	22	TCP	ESX Host	SSH Server	SSH
ESX 3.x	53	UDP	ESXi/ESX Host	DNS Server	DNS
ESX 3.x	80	TCP	Client PC	ESXi/ESX Host	Redirect Web Browser to HTTPS Service (443)
ESX 3.x	88	TCP	ESX Host	Active Directory Server	PAM Active Directory Authentication - Kerberos
ESX 3.x	111	UDP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESX 3.x	111	TCP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESX 3.x	123	UDP	ESXi/ESX Host	NTP Time Server	NTP Client
ESX 3.x	137 to 139	TCP	ESX Host	SMB Server	SMB
ESX 3.x	161	UDP	SNMP Server	ESX Host	SNMP Polling
ESX 3.x	162	UDP	ESX Host	SNMP Collector	SNMP Trap Send
ESX 3.x	389	TCP/UDP	ESX Host	LDAP Server	PAM Active Directory Authentication – LDAP
ESX 3.x	427	UDP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESX 3.x	427	TCP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESX 3.x	443	TCP	Client PC	ESX Host	Host VI Management via web browser
ESX 3.x	443	TCP	VI / vSphere Client	ESXi/ESX Host	VI / vSphere Client to ESXi/ESX Host management connection
ESX 3.x	443	TCP	ESXi/ESX Host	ESXi/ESX Host	Host to host VM migration and provisioning
ESX 3.x	445	TCP	ESX Host	SMB Server	SMB
ESX 3.x	445	TCP	ESX Host	MS Directory Services Server	PAM Active Directory Authentication
ESX 3.x	445	UDP	ESX Host	MS Directory Services Server	PAM Active Directory Authentication
ESX 3.x	464	TCP	ESX Host	Active Directory Server	PAM Active Directory Authentication – Kerberos Password Services
ESX 3.x	514	UDP	ESXi/ESX Host	Syslog Server	Remote syslog logging
ESX 3.x	902	TCP	VI /vSphere Client	ESXi/ESX Host	VI / vSphere Client to ESXi/ESX hosted VM connectivity (MKS)
ESX 3.x	902	TCP/UDP	ESXi/ESX Host	ESXi/ESX Host	Authentication, Provisioning, VM Migration
ESX 3.x	902	TCP/UDP	ESXi/ESX Host	Virtual Center 3.x/ vCenter Server 4.x	Heartbeat
ESX 3.x	903	TCP	VI / vSphere Client	ESXi/ESX Host	VM Remote Console
ESX 3.x	2049	UDP	ESXi/ESX Host	NFS Server	NFS Client
ESX 3.x	2049	TCP	ESXi/ESX Host	NFS Server	NFS Client
ESX 3.x	2050 to 2250	UDP	ESXi/ESX Host	ESXi/ESX Host	VMware HA
ESX 3.x	3260	TCP	ESXi/ESX Host	iSCSI SAN	Software iSCSI Client and Hardware iSCSI HBA
ESX 3.x	5988	TCP	ESXi/ESX Host	ESXi/ESX Host	CIM Client to CIM Secure Server
ESX 3.x	5989	TCP	ESXi/ESX Host	VirtualCenter/vCenter Server	CIM Secure Server to CIM Client
ESX 3.x	5989	TCP	VirtualCenter/vCenter Server	ESXi/ESX Host	CIM Client to CIM Secure Server
ESX 3.x	8000	TCP	ESXi/ESX Host (VM Target)	ESXi/ESX Host (VM Source)	VMotion Communication on VMKernel Interface
ESX 3.x	8000	TCP	ESXi/ESX Host (VM Source)	ESXi/ESX Host (VM Target)	VMotion Communication on VMKernel Interface
ESX 3.x	8042 to 8045	TCP	ESXi/ESX Host	ESXi/ESX Host	VMware HA
ESX 3.x	27000	TCP	ESXi/ESX Host	VMware License Server	ESXi/ESX 3.x Host to License Server communication
ESX 3.x	27010	TCP	ESXi/ESX Host	VMware License Server	ESXi/ESX 3.x Host to License Server communication
ESX 4.x	21	TCP	FTP Client	ESX Host	FTP
ESX 4.x	21	TCP	ESX Host	FTP Server	FTP
ESX 4.x	22	TCP	ESX Host	SSH Server	SSH
ESX 4.x	22	TCP	SSH Client	ESX Host	SSH
ESX 4.x	53	UDP	ESXi/ESX Host	DNS Server	DNS
ESX 4.x	80	TCP	Client PC	ESXi/ESX Host	Redirect Web Browser to HTTPS Service (443)
ESX 4.x	88	TCP	ESX Host	Active Directory Server	PAM Active Directory Authentication - Kerberos
ESX 4.x	111	UDP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESX 4.x	111	TCP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESX 4.x	123	UDP	ESXi/ESX Host	NTP Time Server	NTP Client
ESX 4.x	137 to 139	TCP	ESX Host	SMB Server	SMB
ESX 4.x	161	UDP	SNMP Server	ESX Host	SNMP Polling
ESX 4.x	162	UDP	ESX Host	SNMP Collector	SNMP Trap Send
ESX 4.x	389	TCP/UDP	ESX Host	LDAP Server	PAM Active Directory Authentication – LDAP
ESX 4.x	427	UDP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESX 4.x	427	TCP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESX 4.x	443	TCP	ESXi/ESX Host	ESXi/ESX Host	Host to Host VM migration and provisioning
ESX 4.x	443	TCP	Client PC	ESX Host	Host VI Management via web browser
ESX 4.x	443	TCP	vSphere Client	ESXi/ESX Host	vSphere Client to ESXi/ESX Host management connection
ESX 4.x	445	UDP	ESX Host	MS Directory Services Server	PAM Active Directory Authentication
ESX 4.x	445	TCP	ESX Host	MS Directory Services Server	PAM Active Directory Authentication
ESX 4.x	445	TCP	ESX Host	SMB Server	SMB
ESX 4.x	464	TCP	ESX Host	Active Directory Server	PAM Active Directory Authentication – Kerberos Password Services
ESX 4.x	514	UDP	ESXi/ESX Host	Syslog Server	Remote syslog logging
ESX 4.x	902	TCP	vSphere Client	ESXi/ESX Host	vSphere Client to ESXi/ESX hosted VM connectivity (MKS)
ESX 4.x	902	TCP/UDP	ESXi/ESX Host	ESXi/ESX Host	Authentication, Provisioning, VM Migration
ESX 4.x	902	TCP/UDP	ESXi/ESX Host	vCenter Server 4.x	Heartbeat
ESX 4.x	903	TCP	VI / vSphere Client	ESXi/ESX Host	VM Remote Console (MKS)
ESX 4.x	1024 (dynamic)	TCP/UDP	ESX Host	Active Directory Server	Bi-directional communication on TCP/UDP ports is required between the ESX host and the Active Directory Domain Controller (via the netlogond process on the ESX host). SeeActive Directory and Active Directory Domain Services Port Requirements and MS article179442.
ESX 4.x	2049	UDP	ESXi/ESX Host	NFS Server	NFS Client
ESX 4.x	2049	TCP	ESXi/ESX Host	NFS Server	NFS Client
ESX 4.x	2050 to 2250	UDP	ESXi/ESX Host	ESXi/ESX Host	VMware HA
ESX 4.x	3260	TCP	ESXi/ESX Host	iSCSI SAN	Software iSCSI Client and Hardware iSCSI HBA
ESX 4.x	5900 to 5964	TCP	ESXi/ESX Host	ESXi/ESX Host	RFB Protocol used by management toolssuch as VNC
ESX 4.x	5988	TCP	ESXi/ESX Host	ESXi/ESX Host	CIM Client to CIM Secure Server
ESX 4.x	5989	TCP	VirtualCenter/vCenter	ESXi/ESX Host	CIM Client to CIM Secure Server
ESX 4.x	5989	TCP	ESXi/ESX Host	VirtualCenter/vCenter	CIM Secure Server to CIM Client
ESX 4.x	8000	TCP	ESXi/ESX Host (VM Target)	ESXi/ESX Host (VM Source)	VMotion Communication on VMKernel Interface
ESX 4.x	8000	TCP	ESXi/ESX Host (VM Source)	ESXi/ESX Host (VM Target)	VMotion Communication on VMKernel Interface
ESX 4.x	8042 to 8045	TCP	ESXi/ESX Host	ESXi/ESX Host	VMware HA
ESX 4.x	47	UDP	ESXi/ESX Host	Physical Switches	vDS (Virtual Distributed Switch) Broadcast
ESX 4.x	8100	TCP/UDP	ESXi/ESX 4 Host	ESXi/ESX 4.x Host	VMware Fault Tolerance. ESXi/ESX 4 only.
ESX 4.x	8200	TCP/UDP	ESXi/ESX 4 Host	ESXi/ESX 4.x Host	VMware Fault Tolerance. ESXi/ESX 4 only.
ESX 4.x	8301	UDP	ESXi/ESX 4.x Host	ESXi/ESX 4.x	DVS Port Information
ESX 4.x	8302	UDP	ESXi/ESX 4.x Host	ESXi/ESX 4.x Host	DVS Port Information
ESXi 3.x	53	UDP	ESXi/ESX Host	DNS Server	DNS
ESXi 3.x	80	TCP	Client PC	ESXi/ESX Host	Redirect Web Browser to HTTPS Service (443)
ESXi 3.x	111	TCP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESXi 3.x	111	UDP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESXi 3.x	123	UDP	ESXi/ESX Host	NTP Time Server	NTP Client
ESXi 3.x	162	UDP	ESX Host	SNMP Collector	SNMP Trap Send
ESXi 3.x	427	UDP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESXi 3.x	427	TCP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESXi 3.x	443	TCP	VI / vSphere Client	ESXi/ESX Host	VI / vSphere Client to ESXi/ESX Host management connection
ESXi 3.x	443	TCP	ESXi/ESX Host	ESXi/ESX Host	Host to host VM migration and provisioning
ESXi 3.x	514	UDP	ESXi/ESX Host	Syslog Server	Remote syslog logging
ESXi 3.x	902	TCP	VI / vSphere Client	ESXi/ESX Host	VI / vSphere Client to ESXi/ESX hosted VM connectivity (MKS/Remote Console)
ESXi 3.x	902	TCP/UDP	ESXi/ESX Host	ESXi/ESX Host	Authentication, Provisioning, VM Migration
ESXi 3.x	902	TCP/UDP	ESXi/ESX Host	Virtual Center 3.x/ vCenter Server 4.x	Heartbeat
ESXi 3.x	903	TCP	VI / vSphere Client	ESXi/ESX Host	VM Remote VM Console (MKS)
ESXi 3.x	2049	TCP	ESXi/ESX Host	NFS Server	NFS Client
ESXi 3.x	2049	UDP	ESXi/ESX Host	NFS Server	NFS Client
ESXi 3.x	2050 to 2250	UDP	ESXi/ESX Host	ESXi/ESX Host	VMware HA
ESXi 3.x	3260	TCP	ESXi/ESX Host	iSCSI SAN	Software iSCSI Client and Hardware iSCSI HBA
ESXi 3.x	5988	TCP	ESXi/ESX Host	ESXi/ESX Host	CIM Client to CIM Secure Server
ESXi 3.x	5989	TCP	VirtualCenter/vCenter	ESXi/ESX Host	CIM Client to CIM Secure Server
ESXi 3.x	5989	TCP	ESXi/ESX Host	VirtualCenter/vCenter	CIM Secure Server to CIM Client
ESXi 3.x	8000	TCP	ESXi/ESX Host (VM Target)	ESXi/ESX Host (VM Source)	VMotion Communication on VMKernel Interface
ESXi 3.x	8000	TCP	ESXi/ESX Host (VM Source)	ESXi/ESX Host (VM Target)	VMotion Communication on VMKernel Interface
ESXi 3.x	8042 to 8045	TCP	ESXi/ESX Host	ESXi/ESX Host	VMware HA
ESXi 3.x	27000	TCP	ESXi/ESX Host	VMware License Server	ESXi/ESX 3.x Host to License Server communication
ESXi 3.x	27010	TCP	ESXi/ESX Host	VMware License Server	ESXi/ESX 3.x Host to License Server communication
ESXi 4.x	53	UDP	ESXi/ESX Host	DNS Server	DNS
ESXi 4.x	80	TCP	Client PC	ESXi/ESX Host	Redirect Web Browser to HTTPS Service (443)
ESXi 4.x	88	TCP	ESXi host	Active Directory Server	PAM Active Directory Authentication - Kerberos
ESXi 4.x	111	TCP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESXi 4.x	111	UDP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESXi 4.x	123	UDP	ESXi/ESX Host	NTP Time Server	NTP Client
ESXi 4.x	161	UDP	SNMP Server	ESXi 4.x Host	SNMP Polling. Not used in ESXi 3.x
ESXi 4.x	162	UDP	ESXi Host	SNMP Collector	SNMP Trap Send
ESXi 4.x	389	TCP/UDP	ESXi host	LDAP Server	PAM Active Directory Authentication - Kerberos
ESXi 4.x	427	UDP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESXi 4.x	427	TCP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESXi 4.x	443	TCP	VI / vSphere Client	ESXi/ESX Host	VI / vSphere Client to ESXi/ESX Host management connection
ESXi 4.x	443	TCP	ESXi/ESX Host	ESXi/ESX Host	Host to host VM migration and provisioning
ESXi 4.x	445	UDP	ESXi host	MS Directory Services Server	PAM Active Directory Authentication
ESXi 4.x	445	TCP	ESXi host	MS Directory Services Server	PAM Active Directory Authentication
ESXi 4.x	445	TCP	ESXi host	SMB Server	SMB Server
ESXi 4.x	464	TCP	ESXi host	Active Directory Server	PAM Active Directory Authentication - Kerberos
ESXi 4.x	514	UDP	ESXi/ESX Host	Syslog Server	Remote syslog logging
ESXi 4.x	902	TCP	VI / vSphere Client	ESXi/ESX Host	VI / vSphere Client to ESXi/ESX hosted VM connectivity (MKS/Remote Console)
ESXi 4.x	902	TCP/UDP	ESXi/ESX Host	ESXi/ESX Host	Authentication, Provisioning, VM Migration
ESXi 4.x	902	TCP/UDP	ESXi/ESX Host	vCenter 4 Server	Heartbeat
ESXi 4.x	902	TCP	VI / vSphere Client	ESXi/ESX Host	VM Remote VM Console (MKS)
ESXi 4.x	1024 (dynamic)	TCP/UDP	ESXi Host	Active Directory Server	Bi-directional communication on TCP/UDP ports is required between the ESXi host and the Active Directory Domain Controller (via the netlogond process on the ESXi host). SeeActive Directory and Active Directory Domain Services Port Requirements and MS article179442.
ESXi 4.x	2049	TCP	ESXi/ESX Host	NFS Server	NFS Client
ESXi 4.x	2049	UDP	ESXi/ESX Host	NFS Server	NFS Client
ESXi 4.x	2050 to 2250	UDP	ESXi/ESX Host	ESXi/ESX Host	VMware HA
ESXi 4.x	3260	TCP	ESXi/ESX Host	iSCSI SAN	Software iSCSI Client and Hardware iSCSI HBA
ESXi 4.x	5900to 5964	TCP	ESXi/ESX Host	ESXi/ESX Host	RFB Protocol used by management toolssuch as VNC
ESXi 4.x	5988	TCP	ESXi/ESX Host	ESXi/ESX Host	CIM Client to CIM Secure Server
ESXi 4.x	5989	TCP	VirtualCenter/vCenter	ESXi/ESX Host	CIM Client to CIM Secure Server
ESXi 4.x	5989	TCP	ESXi/ESX Host	VirtualCenter/vCenter	CIM Secure Server to CIM Client
ESXi 4.x	8000	TCP	ESXi/ESX Host (VM Target)	ESXi/ESX Host (VM Source)	VMotion Communication on VMkernel Interface
ESXi 4.x	8000	TCP	ESXi/ESX Host (VM Source)	ESXi/ESX Host (VM Target)	VMotion Communication on VMkernel Interface
ESXi 4.x	47	UDP	ESXi/ESX Host	Physical Switches	vDS (Virtual Distributed Switch) Broadcast
ESXi 4.x	8042 to 8045	TCP	ESXi/ESX Host	ESXi/ESX Host	VMware HA
ESXi 4.x	8100	TCP/UDP	ESXi/ESX 4 Host	ESXi/ESX 4.x Host	VMware Fault Tolerance. ESXi/ESX 4 only.
ESXi 4.x	8200	TCP/UDP	ESXi/ESX 4 Host	ESXi/ESX 4.x Host	VMware Fault Tolerance. ESXi/ESX 4 only.
ESXi 4.x	8301	UDP	ESXi/ESX 4.x Host	ESXi/ESX 4.x Host	DVS Port Information
ESXi 4.x	8302	UDP	ESXi/ESX 4.x Host	ESXi/ESX 4.x Host	DVS Port Information
ESXi 5.x	22	TCP	Client PC	ESXi 5.x	SSH Server
ESXi 5.x	53	UDP	ESXi 5.x	DNS Server	DNS Client
ESXi 5.x	68	UDP	ESXi 5.x	DHCP Server	DHCP Client
ESXi 5.x	80	TCP	Client PC	ESXi 5.x	Redirect Web Browser to HTTPS Service (443)
ESXi 5.x	88	TCP	ESXi host	Active Directory Server	PAM Active Directory Authentication - Kerberos
ESXi 5.x	111	TCP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESXi 5.x	111	UDP	ESXi/ESX Host	NFS Server	NFS Client – RPC Portmapper
ESXi 5.x	123	UDP	ESXi/ESX Host	NTP Time Server	NTP Client
ESXi 5.x	161	UDP	SNMP Server	ESXi 4.x Host	SNMP Polling. Not used in ESXi 3.x
ESXi 5.x	162	UDP	ESXi Host	SNMP Collector	SNMP Trap Send
ESXi 5.x	389	TCP/UDP	ESXi host	LDAP Server	PAM Active Directory Authentication - Kerberos
ESXi 5.x	427	UDP	VI / vSphere Client	ESXi/ESX Host	CIM Service Location Protocol (SLP)
ESXi 5.x	443	TCP	VI / vSphere Client	ESXi/ESX Host	VI / vSphere Client to ESXi/ESX Host management connection
ESXi 5.x	443	TCP	ESXi/ESX Host	ESXi/ESX Host	Host to host VM migration and provisioning
ESXi 5.x	445	UDP	ESXi host	MS Directory Services Server	PAM Active Directory Authentication
ESXi 5.x	445	TCP	ESXi host	MS Directory Services Server	PAM Active Directory Authentication
ESXi 5.x	445	TCP	ESXi host	SMB Server	SMB Server
ESXi 5.x	464	TCP	ESXi hostSee .	Active Directory Server	PAM Active Directory Authentication - Kerberos
ESXi 5.x	514	UDP/TCP	ESXi 5.x	Syslog Server	Remote syslog logging
ESXi 5.x	902	TCP/UDP	ESXi 5.x	ESXi 5.x	Host access to other hosts for migration and provisioning
ESXi 5.x	902	TCP	vSphere Client	ESXi 5.x	vSphere Client access to virtual machine consoles (MKS)
ESXi 5.x	902	TCP/UDP	ESXi 5.x	vCenter Server	(UDP) Status update (heartbeat) connection from E SXi to vCenter Server
ESXi 5.x	1024 (dynamic)	TCP/UDP	ESXi Host	Active Directory Server	Bi-directional communication on TCP/UDP ports is required between the ESXi host and the Active Directory Domain Controller (via the netlogond process on the ESXi host). SeeActive Directory and Active Directory Domain Services Port Requirements and MS article179442.
ESXi 5.x	2049	TCP	ESXi 5.x	NFS Server	Transactions from NFS storage devices
ESXi 5.x	2049	UDP	ESXi 5.x	NFS Server	Transactions from NFS storage devices
ESXi 5.x	3260	TCP	ESXi 5.x	iSCSI storage server	Transactions to iSCSI storage devices
ESXi 5.x	5900 to 5964	TCP	ESXi 5.x	ESXi 5.x	RFB protocol, which is used by management tools such as VNC
ESXi 5.x	5988	TCP	CIM Server	ESXi 5.x	CIM transactions over HTTP
ESXi 5.x	5989	TCP	vCenter Server	ESXi 5.x	CIM XML transactions over HTTPS
ESXi 5.x	5989	TCP	ESXi 5.x	vCenter Server	CIM XML transactions over HTTPS
ESXi 5.x	8000	TCP	ESXi 5.x (VM Target)	ESXi 5.x (VM Source)	Requests from vMotion
ESXi 5.x	8000	TCP	ESXi 5.x (VM Source)	ESXi 5.x (VM Target)	Requests from vMotion
ESXi 5.x	8100	TCP/UDP	ESXi 5.x	ESXi 5.x	Traffic between hosts for vSphere Fault Tolerance (FT)
ESXi 5.x	8182	TCP/UDP	ESXi 5.x	ESXi 5.x	Traffic between hosts for vSphere High Availability (vSphere HA)
ESXi 5.x	8200	TCP/UDP	ESXi 5.x	ESXi 5.x	Traffic between hosts for vSphere Fault Tolerance (FT)
ESXi 5.x	8301	UDP	ESXi 5.x	ESXi 5.x	DVS Port Information
ESXi 5.x	8302	UDP	ESXi 5.x	ESXi 5.x	DVS Port Information
ESXi 5.x	31100	TCP	vCenter	SPS Server	Internal Communication Port
ESXi 5.x	31000	TCP	SPS Server	vCenter	Internal Communication Port
ESXi Dump Collector	6500	UDP	ESXi	vCenter Server	Network coredump server
ESXi Dump Collector	8000	TCP	ESXi	vCenter Server	Network coredump web port
ESXi Syslog Collector	8001	TCP	ESXi	vCenter Server	Network syslog server
Guided Consolidation	135	TCP/UDP	Consolidation Target (Physical Server)	vCenter Converter Server	Microsoft DCE Locator Service, also known at End-Point Mapper
Guided Consolidation	137	TCP/UDP	Consolidation Target (Physical Server)	vCenter Converter Server	NetBIOS names service. Firewall administrators frequently see larger numbers of incoming packets to port 137. This is because of Windows servers that use NetBIOS (as well as DNS) to resolve IP addresses to names using the gethostbyaddr() function. As users behind the firewalls visit Windows-based Web sites, those servers frequently respond with NetBIOS lookups.
Guided Consolidation	138	TCP/UDP	Consolidation Target (Physical Server)	vCenter Converter Server	NetBIOS datagram Used by Windows, as well as UNIX services (such as SAMBA). Port 138 is used primarily by the SMB browser service that obtains Network Neighborhood information.
Guided Consolidation	139	TCP/UDP	Consolidation Target (Physical Server)	vCenter Converter Server	NetBIOS Session Windows File and Printer sharing.
Guided Consolidation	445	TCP/UDP	Consolidation Target (Physical Server)	vCenter Converter Server	DNS Direct Hosting port. In Windows 2000 and Windows XP, redirector and server components now support direct hosting for communicating with other computers running Windows 2000 or Windows XP. Direct hosting does not use NetBIOS for name resolution. DNS is used for name resolution, and the Microsoft networking communication is sent directly over TCP without a NetBIOS header. Direct hosting over TCP/IP uses TCP and UDP port 445 instead of the NetBIOS session TCP port 139.
Heartbeat	52267	TCP	vCenter Server Heartbeat Console	vCenter Server Heartbeat Server	Client Connection Port
Heartbeat	57348	TCP	vCenter Server Primary Server	vCenter Server Secondary Server	Default Channel Port to communicate between Primary and Secondary server
Lab Manager	137	UDP	ESXi/ESX Host	SMB File Server	SMB File Sharing for Importing/Exporting VMs. ESXi requires Lab Manager 4.x
Lab Manager	138	UDP	ESXi/ESX Host	SMB File Server	SMB File Sharing for Importing/Exporting VMs. ESXi requires Lab Manager 4.x
Lab Manager	139	TCP	ESXi/ESX Host	SMB File Server	SMB File Sharing for Importing/Exporting VMs. ESXi requires Lab Manager 4.x
Lab Manager	389	TCP/UDP	Lab Manager Server	LDAP Server	LDAP Authentication (optional)
Lab Manager	443	TCP	Client PC	Lab Manager Server	Lab Manager Console (Web Browser)
Lab Manager	443	TCP	Lab Manager Server	vCenter Server	Lab Manager to vCenter Server Communication
Lab Manager	445	TCP	ESXi/ESX Host	SMB File Server	SMB File Sharing for Importing/Exporting VMs. ESXi requires Lab Manager 4.x
Lab Manager	514	TCP	Lab Manager Server	Virtual Router	Update IP tables and routing on the vRouter
Lab Manager	636	TCP	Lab Manager Server	LDAP Server	LDAPS Authentication (optional)
Lab Manager	1433	TCP	Lab Manager Server	Microsoft SQL Server	Lab Manager Connectivity to Microsoft SQL Server (for LM database)
Lab Manager	5212	TCP	Lab Manager Server	ESXi/ESX Host	Lab Manager Agent. ESXi requires Lab Manager 4.x
Orchestrator	25	TCP	VCO Server	SMTP Server	Email notifications
Orchestrator	389	TCP/UDP	VCO Server	LDAP Server	LDAP Authentication
Orchestrator	443	TCP	VCO Server	vCenter Server	Used to obtain virtual infrastructure and virtual machine information from orchestrated vCenter Server(s) through the vCenter API
Orchestrator	636	TCP	VCO Server	LDAP Server	VCO uses LDAP authentication and group membership to determine role authorization in LCM and access to VMs/requests. This is the SSL secured LDAP protocol LDAPS (the SSL pendent of 389). This is used for secured LDAP authentication
Orchestrator	1433	TCP	VCO Server	Microsoft SQL Server	vCenter Orchestrator Server to Microsoft SQL Server for VCO Database
Orchestrator	1521	TCP	VCO Server	Oracle Database Server	vCenter Orchestrator Server to Oracle for VCO Database
Orchestrator	3306	TCP	VCO Server	MySQL Server	vCenter Orchestrator Server to MySQL Server for VCO Database
Orchestrator	5432	TCP	VCO Server	PostgresSQL Server	vCenter Orchestrator Server to PostgresSQL Server for VCO Database
Orchestrator	8230	TCP	VCO Client	VCO Server	Lookup port – The main port to communicate with Orchestrator Configurator server (JNDI port). All other ports communicate with the Orchestrator Configurator smart client through this one. It is part of the JBoss Application server infrastructure
Orchestrator	8240	TCP	VCO Client	VCO Server	Command port – The application communication port (RMI container port), it is used for remote invocations. It is part of the JBoss Application server infrastructure.
Orchestrator	8244	TCP	VCO Client	VCO Server	Data port used to access all Orchestrator data models, such as workflows and policies. It is part of the JBoss application server infrastructure.
Orchestrator	8250	TCP	VCO Client	VCO Server	Messaging port – The Java messaging port used to dispatch events. It is part of the JBoss Application server infrastructure
Orchestrator	8280	TCP	VCO Server	VCO Server	Port used by VCO Server to connect to the Web front-end via HTTP
Orchestrator	8281	TCP	VCO Server	VCO Server	Port used by VCO Server to connect to the Web front-end via HTTPS
Orchestrator	8281	TCP	vCenter Server	VCO Server	Port used by VCO Server to connect to vCenter Server to communicate with the vCenter API
Orchestrator	8282	TCP	VCO Client PC	VCO Server	HTTP server port – Port used by the HTTP connector to connect to the Web frontend.
Orchestrator	8283	TCP	VCO Client PC	VCO Server	HTTPS server port – Port used by HTTP connector to connect to the Web frontend. Requires Jetty to be configured for SSL.
Site Recovery Manager1.x-4.x	80	TCP	Site Recovery Manager	Remote vCenter Server	SRM communication. SRM Server at Site A to vCenter Server at Site B (failover) over HTTP and SSL tunnel
Site Recovery Manager1.x-4.x	80	TCP	Site Recovery Manager	Remote vCenter Server	SRM communication with local vCenter Server (inventory) vSphere Client Plug-in download
Site Recovery Manager1.x-4.x	443	TCP	Site Recovery Manager	Remote vCenter Server	SRM communication with remote vCenter Server via HTTP over SSL tunnel
Site Recovery Manager1.x-4.x	902	TCP	Site Recovery Manager	Remote ESXi/ESX Host	Update/communicate tovirtual machine files over NFC for IP customization/RDMs
Site Recovery Manager1.x-4.x	1433	TCP	Site Recovery Manager	Microsoft SQL Server	SRM Connectivity to Microsoft SQL Server (for SRM database)
Site Recovery Manager1.x-4.x	1521	TCP	Site Recovery Manager	Oracle Database Server	SRM Connectivity to Oracle (for SRM database)
Site Recovery Manager1.x-4.x	1526	TCP	Site Recovery Manager	Oracle Database Server	SRM Connectivity to Oracle (for SRM database)
Site Recovery Manager1.x-4.x	5000	TCP	Site Recovery Manager	IBM DB2 Database Server	SRM Connectivity to IBM DB/2 (for SRM database)
Site Recovery Manager1.x-4.x	8095	TCP	vSphere Client	vCenter Server	SRM server and vCenter Server (intrasite only).
Site Recovery Manager1.x-4.x	8095	TCP	vSphere Client	Site Recovery Manager	SRM client plug-in to communicate with vCenter Server
Site Recovery Manager1.x-4.x	8096	TCP	Site Recovery Manager	vCenter Server	vCenter Server (for Plug-in download).
Site Recovery Manager1.x-4.x	9007	TCP	Site Recovery Manager	External SRM API Client	SRM communication via WSDL
Site Recovery Manager1.x-4.x	9007	TCP	vSphere Client	vCenter Server	SRM client plugin to communicate with vCenter Server
Site Recovery Manager1.x-4.x	9008	TCP	Site Recovery Manager	External SRM API Client	SRM communication via HTTP
Site Recovery Manager 5.x	80	TCP	Site Recovery Manager	Remote vCenter Server	SRM communication. SRM Server at Site A to vCenter Server at Site B (failover) over HTTP and SSL tunnel
Site Recovery Manager 5.x	80	TCP	Site Recovery Manager	Remote vCenter Server	SRM communication with local vCenter server (inventory) vSphere Client Plug-in download
Site Recovery Manager 5.x	443	TCP	Site Recovery Manager	Remote vCenter Server	SRM communication with remote vCenter Server via HTTP over SSL tunnel
Site Recovery Manager 5.x	902	TCP	Site Recovery Manager	Remote ESXi/ESX host	Update/communicate to virtual machines files over NFC for IP customization/RDMs
Site Recovery Manager 5.x	1433	TCP	Site Recovery Manager	Microsoft SQL Server	SRM Connectivity to Microsoft SQL Server (for SRM database)
Site Recovery Manager 5.x	1521	TCP	Site Recovery Manager	Oracle Database Server	SRM Connectivity to Oracle (for SRM database)
Site Recovery Manager 5.x	1526	TCP	Site Recovery Manager	Oracle Database Server	SRM Connectivity to Oracle (for SRM database)
Site Recovery Manager 5.x	5000	TCP	Site Recovery Manager	IBM DB2 Database Server	SRM Connectivity to IBM DB/2 (for SRM database)
Site Recovery Manager 5.x	5480	TCP	Site Recovery Manager Web User Interface	HBR Server Appliance	vSphere Replication web user interface to HBR server appliance
Site Recovery Manager 5.x	8043	TCP	vCenter Proxy	HMS Appliance	SOAP port between vCenter Proxy and HMS
Site Recovery Manager 5.x	8080	TCP	Site Recovery Manager Web User Interface	HMS Appliance	VAMI web user interface to HMS appliance
Site Recovery Manager 5.x	8095	TCP	Site Recovery Manager	vCenter server	SRM server and vCenter server (intrasite only).
Site Recovery Manager 5.x	8095	TCP	vSphere Client	Site Recovery Manager	SRM client plugin to communicate with SRM server
Site Recovery Manager 5.x	8095	TCP	vSphere Client	vCenter server	SRM client plugin to communicate with vCenter server
Site Recovery Manager 5.x	8096	TCP	Site Recovery Manager	vCenter server	vCenter server (for plug-in download).
Site Recovery Manager 5.x	8123	TCP	Site Recovery Manager	vSphere Replication Management Server	SOAP port between SRM and vSphere Replication Management server
Site Recovery Manager 5.x	9007	TCP	Site Recovery Manager	External SRM API Client	SRM communication via WSDL
Site Recovery Manager 5.x	9007	TCP	vSphere Client	vCenter server	SRM client plugin to communicate with vCenter server
Site Recovery Manager 5.x	9008	TCP	Site Recovery Manager	External SRM API Client	SRM communication via HTTP
Site Recovery Manager 5.x	9085	TCP	Site Recovery Manager	Site Recovery Manger	HTTP interface for downloading the UI plugin and icons
Site Recovery Manager 5.x	31031	TCP	vSphere Replication	vSphere Replication	HBR replication traffic
Site Recovery Manager 5.x	44046	TCP	vSphere Replication	vSphere Replication	HBR replication traffic
Stage Manager	137	UDP	ESX Host	SMB File Server	SMB File Sharing for Importing/Exporting VMs
Stage Manager	138	UDP	ESX Host	SMB File Server	SMB File Sharing for Importing/Exporting VMs
Stage Manager	139	TCP	ESX Host	SMB File Server	SMB File Sharing for Importing/Exporting VMs
Stage Manager	389	TCP/UDP	Stage Manager Server	LDAP Server	LDAP Authentication (optional)
Stage Manager	443	TCP	Client PC	Stage Manager Server	Stage Manager Console (Web Browser)
Stage Manager	443	TCP	Stage Manager Server	ESX Host	Stage Manager Server communication with ESX Host Agent
Stage Manager	443	TCP	Stage Manager Server	vCenter Server	Stage Manager Server communication with vCenter Server
Stage Manager	445	TCP	ESX Host	SMB File Server	SMB File Sharing for Importing/Exporting VMs
Stage Manager	514	TCP	Stage Manager Server	ESX Host	ESX Host Virtual Router
Stage Manager	636	TCP	Stage Manager Server	LDAP Server	LDAPS Authentication (optional)
Stage Manager	5212	TCP	Stage Manager Server	ESX Host	Stage Manager Agent
Update Manager	80	TCP	Update Manager Server	www.vmware.com and xml.shavlik.com	To obtain metadata for the updates, Update Manager must be able to connect to http://www.vmware.com and http://xml.shavlik.com
Update Manager	80	TCP	ESXi/ESX Host	Update Manager Host	ESXi/ESX Host to Update Manager Server. The reverse proxy forwards the request to port 9084
Update Manager	80	TCP	Update Manager Server	vCenter Server	Update Manager to vCenter Server communication
Update Manager	443	TCP	Update Manager Server	www.vmware.com and xml.shavlik.com	To obtain metadata for the updates, Update Manager must be able to connect to http://www.vmware.com and http://xml.shavlik.com
Update Manager	443	TCP	ESXi/ESX Host	Update Manager Server	ESXi/ESX Host to Update Manager Server . The reverse proxy forwards the request to port 9084
Update Manager	443	TCP	vCenter Server	Update Manager Server	vCenter Server to Update Manager Server. The reverse proxy forwards the request to port 8084
Update Manager	735	TCP	Update Manager Server	Virtual Machines	Update Managerlistenerport (rdevServer.exe) part of theRemote Device Server used for virtual machine patching.
Update Manager	902	TCP	Update Manager Server	ESXi/ESX Host	To push patches and updates from Update Manager to the ESXi/ESX Hosts to be updated
Update Manager	1433	TCP	Update Manager Server	Microsoft SQL Server	Update Manager to Microsoft SQL Server connectivity (for UM Database)
Update Manager	1521	TCP	Update Manager Server	Oracle Database Server	Update Manager to Oracle connectivity (for UM Database)
Update Manager	8084	TCP	Update Manager Server	vCenter Server	SOAP between components of Update Manager Server and the vCenter Update Manager client plug-in. Configurable at install.
Update Manager	9084	TCP	ESXi/ESX host	Update Manager Server	ESXi/ESX hosts connect to the VUM (VMware Update Manager) webserver listening for updates. Configurable at install.
Update Manager	9087	TCP	Update Manager Server	vCenter Server	Port used for uploading host update files. Configurable at install.
Update Manager	9000 to 9100	TCP	ESXi/ESX Host	Update Manager Server	This is the recommend port range from which to choose ports for Update Manager if ports 80 and 443 are already in use. Update Manager automatically opens these ports for ESX Host scanning and remediation.
vCenter 2.5.x	25	TCP	vCenter Server	SMTP Server	Email notifications
vCenter 2.5.x	53	UDP	vCenter Server	DNS Server	DNS lookups
vCenter 2.5.x	80	TCP	Client PC	vCenter Server	Redirect Web Browser to HTTPS Service (443)
vCenter 2.5.x	88	TCP	vCenter Server	Active Directory Server	AD Authentication
vCenter 2.5.x	88	UDP	vCenter Server	Active Directory Server	AD Authentication
vCenter 2.5.x	161	UDP	SNMP Server	vCenter Server	SNMP Polling
vCenter 2.5.x	162	UDP	vCenter Server	SNMP Server	SNMP Trap Send
vCenter 2.5.x	389	TCP/UDP	vCenter Server	LDAP Server	LDAP Authentication
vCenter 2.5.x	443	TCP	vCenter Server	ESXi/ESX Host	vCenter Agent
vCenter 2.5.x	443	TCP	Client PC	vCenter Server	VI Web Access (Web Browser)
vCenter 2.5.x	443	TCP	VI / vSphere Client	vCenter Server	VI / vSphere Client access to vCenter Server
vCenter 2.5.x	445	TCP	vCenter Server	Active Directory Server	AD Authentication
vCenter 2.5.x	445	UDP	vCenter Server	Active Directory Server	AD Authentication
vCenter 2.5.x	902	TCP/UDP	vCenter Server	ESXi/ESX Host	Heartbeat
vCenter 2.5.x	902	TCP/UDP	ESXi/ESX Host	vCenter Server	Heartbeat
vCenter 2.5.x	903	TCP	Client PC	vCenter Server	VI / vSphere Client to VM Console
vCenter 2.5.x	903	TCP	vCenter Server	ESXi/ESX Host	VI / vSphere Client to VM Console (after connection established between VI / vSphere Client and vCenter)
vCenter 2.5.x	1433	TCP	vCenter Server	Microsoft SQL Server	For vCenter Microsoft SQL Server Database
vCenter 2.5.x	1521	TCP	vCenter Server	Oracle Database Server	For vCenter Oracle Database
vCenter 2.5.x	5989	TCP	VirtualCenter/vCenter	ESXi/ESX Host	vCenter to ESX
vCenter 2.5.x	5989	TCP	ESXi/ESX Host	VirtualCenter/vCenter	ESX to vCenter
vCenter 2.5.x	8005	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 2.5.x	8006	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 2.5.x	8083	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics
vCenter 2.5.x	8085	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics/SDK
vCenter 2.5.x	8086	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 2.5.x	8087	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics
vCenter 2.5.x	27000	TCP	vCenter Server	VMware License Server	Licensing via FlexLM. Only required by vCenter 4 if ESXi/ESX 3.x Hosts will be supported
vCenter 2.5.x	27000	TCP	VMware License Server	vCenter Server	Licensing via FlexLM. Only required by vCenter 4 if ESXi/ESX 3.x Hosts will be supported
vCenter 2.5.x	27010	TCP	vCenter Server	VMware License Server	Licensing via FlexLM. Only required by vCenter 4 if ESXi/ESX 3.x Hosts will be supported
vCenter 2.5.x	27010	TCP	VMware License Server	vCenter Server	Licensing via FlexLM. Only required by vCenter 4 if ESXi/ESX 3.x Hosts will be supported
vCenter 4.x	25	TCP	vCenter Server	SMTP Server	Email notifications
vCenter 4.x	53	UDP	vCenter Server	DNS Server	DNS lookups
vCenter 4.x	80	TCP	Client PC	vCenter Server	Redirect Web Browser to HTTPS Service (443)
vCenter 4.x	80	TCP	vCenter Server	ESXi/ESX 4.x	DPM with IPMI (iLO/BMC) ASF Remote Management and Control Protocol
vCenter 4.x	88	UDP	vCenter Server	Active Directory Server	AD Authentication
vCenter 4.x	88	TCP	vCenter Server	Active Directory Server	AD Authentication
vCenter 4.x	135	TCP	vCenter Server	vCenter Server	Linked Mode
vCenter 4.x	161	UDP	SNMP Server	vCenter Server	SNMP Polling
vCenter 4.x	162	UDP	vCenter Server	SNMP Server	SNMP Trap Send
vCenter 4.x	389	TCP/UDP	vCenter Server	Linked vCenter Servers	Bi-directional LDAP authentication with Kerberos encryption on TCP port 389 is required between all vCenters that need to replicate.
vCenter 4.x	443	TCP	vCenter Server	ESXi/ESX Host	vCenter Agent
vCenter 4.x	443	TCP	vCenter Server	ESXi/ESX 4.x	Host DPM with HP iLO Remote Management and Control Protocol
vCenter 4.x	443	TCP	Client PC	vCenter Server	VI Web Access (Web Browser)
vCenter 4.x	443	TCP	vSphere Client	vCenter Server	vSphere Client access to vCenter Server
vCenter 4.x	445	TCP	vCenter Server	Active Directory Server	AD Authentication
vCenter 4.x	445	UDP	vCenter Server	Active Directory Server	AD Authentication
vCenter 4.x	623	UDP	vCenter Server	ESXi/ESX 4.x Host	DPM with IPMI (iLO/BMC) ASF Remote Management and Control Protocol
vCenter 4.x	636	TCP	vCenter Server	Linked vCenter Servers	Linked mode connectivity between vCenter Servers
vCenter 4.x	902	TCP/UDP	vCenter Server	ESXi/ESX Host	Heartbeat
vCenter 4.x	902	TCP/UDP	ESXi/ESX Host	vCenter Server	Heartbeat
vCenter 4.x	903	TCP	Client PC	vCenter Server	VI / vSphere Client to VM Console
vCenter 4.x	902	TCP	vCenter Server	ESXi/ESX Host	VI / vSphere Client to VM Console (after connection established between VI / vSphere Client and vCenter)
vCenter 4.x	1024 (dynamic)	RPC	Linked vCenter Servers	Linked vCenter Servers	Bi-directional RPC communication on dynamic TCP ports is required between all vCenters that need to replicate (via ADAM). A VIC still needs a direct connection to all vCenters that own an object it needs to manage.
vCenter 4.x	1433	TCP	vCenter Server	Microsoft SQL Server	For vCenter Microsoft SQL Server Database
vCenter 4.x	1521	TCP	vCenter Server	Oracle Database Server	For vCenter Oracle Database
vCenter 4.x	5989	TCP	vCenter Server	ESXi/ESX Host	vCenter to ESX
vCenter 4.x	5989	TCP	ESXi/ESX Host	vCenter Server	ESX to vCenter
vCenter 4.x	8005	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 4.x	8006	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 4.x	8080	TCP	Client PC	vCenter Server 4.x	VMware vCenter 4 Management Web Services - HTTP
vCenter 4.x	8083	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics
vCenter 4.x	8085	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics/SDK
vCenter 4.x	8086	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 4.x	8087	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics
vCenter 4.x	8443	TCP	Client PC	vCenter Server 4.x	VMware vCenter 4 Management Web Services - HTTPS
vCenter 4.x	8443	TCP	vCenter Server	vCenter Server	Linked Mode
vCenter 4.x	27000	TCP	vCenter Server	VMware License Server	Licensing via FlexLM. Only required by vCenter 4 if ESXi/ESX 3.x Hosts will be supported
vCenter 4.x	27000	TCP	VMware License Server	vCenter Server	Licensing via FlexLM. Only required by vCenter 4 if ESXi/ESX 3.x Hosts will be supported
vCenter 4.x	27010	TCP	vCenter Server	VMware License Server	Licensing via FlexLM. Only required by vCenter 4 if ESXi/ESX 3.x Hosts will be supported
vCenter 4.x	27010	TCP	VMware License Server	vCenter Server	Licensing via FlexLM. Only required by vCenter 4 if ESXi/ESX 3.x Hosts will be supported
vCenter 4.1	60099	TCP	vCenter Server	vCenter Server Services	This port is for internal communication between vCenter Server and its solutions. Specifically, it is used to exchange messages about inventory. If you do not have it open, a solution that integrates with vCenter Server using this service may be affected.
vCenter 5.x	25	TCP	vCenter Server	SMTP Server	Email notifications
vCenter 5.x	53	UDP	vCenter Server	DNS Server	DNS lookups
vCenter 5.x	80	TCP	Client PC	vCenter Server	vCenter Server requires port 80 for direct HTTP connections.
vCenter 5.x	80	TCP	vCenter Server	ESXi 5.x	DPM with IPMI (iLO/BMC) ASF Remote Management and Control Protocol
vCenter 5.x	88	UDP	vCenter Server	Active Directory Server	AD Authentication
vCenter 5.x	88	TCP	vCenter Server	Active Directory Server	AD Authentication
vCenter 5.x	135	TCP	vCenter Server	vCenter Server	Linked Mode
vCenter 5.x	161	UDP	SNMP Server	vCenter Server	SNMP Polling
vCenter 5.x	162	UDP	vCenter Server	SNMP Server	SNMP Trap Send
vCenter 5.x	389	TCP/UDP	vCenter Server	Linked vCenter Servers	This is the LDAP port number for the Directory Services for the vCenter Server group. The vCenter Server system needs to bind to port 389, even if you are not joining this vCenter Server instance to a Linked Mode group. If another service is running on this port, you can run the LDAP service on any port from 1025 through 65535.
vCenter 5.x	443	TCP	vSphere Client	vCenter Server	vCenter Server system uses to listen for connections from the vSphere Client.
vCenter 5.x	443	TCP	vCenter Server	ESXi 5.x	vCenter Agent. Host DPM with HP iLO Remote Management and Control Protocol
vCenter 5.x	623	UDP	vCenter Server	ESXi 5.x	DPM with IPMI (iLO/BMC) ASF Remote Management and Control Protocol
vCenter 5.x	636	TCP	vCenter Servers	Linked vCenter Servers	vCenter Server Linked Mode, this is the SSL port of the local instance.
vCenter 5.x	902	TCP	vCenter Server	ESXi 5.x	vCenter Server system uses to send data to managed hosts. This port must not be blocked by firewalls between the server and the hosts or between hosts.
vCenter 5.x	902	UDP	vCenter Server	ESXi 5.x	Managed hosts send a regular heartbeat to the vCenter Server system. This port must not be blocked by firewalls between the server and the hosts or between hosts.
vCenter 5.x	902	TCP/UDP	vSphere Client	ESXi 5.x	vSphere Client uses this ports to display virtual machine consoles.
vCenter 5.x	902	TCP/UDP	ESXi 5.x	ESXi 5.x	Host access to other hosts for migration and provisioning
vCenter 5.x	903	TCP	vSphere Client	ESXi 5.x	Remote console traffic generated by user access to virtual machines on a specific host.
vCenter 5.x	1024 (dynamic)	RPC	Linked vCenter Servers	Linked vCenter Servers	Bi-directional RPC communication on dynamic TCP ports is required between all vCenters that need to replicate (via ADAM). A VIC still needs a direct connection to all vCenters that own an object it needs to manage.
vCenter 5.x	1433	TCP	vCenter Server	Microsoft SQL Server	For vCenter Microsoft SQL Server Database
vCenter 5.x	1521	TCP	vCenter Server	Oracle Database Server	For vCenter Oracle Database
vCenter 5.x	5988	TCP	ESXi 5.x	vCenter Server	CIM transactions over HTTP
vCenter 5.x	5989	TCP	vCenter Server	ESXi 5.x	CIM XML transactions over HTTPS
vCenter 5.x	5989	TCP	ESXi 5.x	vCenter Server	CIM XML transactions over HTTPS
vCenter 5.x	7500	UDP	vCenter Server	vCenter Server	Linked Mode, Java Discovery Port
vCenter 5.x	8000	TCP	vCenter Server	ESXi 5.x	Requests from vMotion
vCenter 5.x	8005	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 5.x	8006	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 5.x	8080	TCP	Client PC	vCenter Server	Web Services HTTP. Used for the VMware VirtualCenter Management Web Services.
vCenter 5.x	8083	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics
vCenter 5.x	8085	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics/SDK
vCenter 5.x	8086	TCP	vCenter Server	vCenter Server	Internal Communication Port
vCenter 5.x	8087	TCP	vCenter Server	vCenter Server	Internal Service Diagnostics
vCenter 5.x	8443	TCP	Client PC	vCenter Server	Web Services HTTPS. Used for the VMware VirtualCenter Management Web Services.
vCenter 5.x	8443	TCP	vCenter Server	vCenter Server	Linked Mode
vCenter 5.x	9443	TCP	Client PC	vCenter Server	vSphere Web Client Access
vCenter 5.x	10109	TCP	vCenter Server	vCenter Server	vCenter Inventory Service Service Management
vCenter 5.x	10111	TCP	vCenter Server	vCenter Server	vCenter Inventory Service Linked Mode Communication
vCenter 5.x	10443	TCP	Client PC	vCenter Server	vCenter Inventory Service HTTPS
vCenter 5.x	51915	TCP	ESXi	vSphere Authentication Proxy	This is a web service, which is used to add host to Active Directory domain.
vCenter 5.x	60099	TCP	vCenter Server	vCenter Server	Web Service change service notification port
vCenter Infrastructure Navigator 1.x	22	TCP	Client PC	vCenter Infrastructure Navigator Appliance	Enables SSH access to vCenter Infrastructure Appliance
vCenter Infrastructure Navigator 1.x	80	TCP	vCenter Infrastructure Navigator	vSphere Web service API	HTTP web service
vCenter Infrastructure Navigator 1.x	443	TCP	vCenter Infrastructure Navigator	vSphere Web service API	HTTPS web service
vCenter Infrastructure Navigator 1.x	443	TCP	vCenter Infrastructure Navigator	ESXi/ESX hosts and virtual machines	VIX protocol on target hosts to perform discovery
vCenter Infrastructure Navigator 1.x	902	TCP	vCenter Infrastructure Navigator	ESXi/ESX hosts and virtual machines	VIX protocol on target hosts to perform discovery
vCenter Infrastructure Navigator 1.x	2868	TCP	vCenter Server	vCenter Infrastructure Navigator	Plug-in downloads. This download happens as part of the registration process.
vCenter Infrastructure Navigator 1.x	6969	TCP	vCenter Server	vCenter Infrastructure Navigator	Connectivity from vSphere Web Client to vCenter Infrastructure Navigator
vCloud Usage Meter	80	TCP	vCloud Usage Meter	vCenter Server	This is for vSphere API
vCloud Usage Meter	443	TCP	vCloud Usage Meter	vCenter Server	This is for vSphere API
vCloud Usage Meter	5480	TCP	vCenter Update Manager	vCloud Usage Meter	This is used for virtual appliance updates
vCloud Usage Meter	8443	TCP	Client Browser	vCloud Usage Meter	This is for WebApp
vCenter Operations Standard 1.x	22	TCP	SSH Client	vCenter Operations Standard 1.x virtual appliance	Enables SSH access to the vCenter Operations Standard virtual appliance
vCenter Operations Standard 1.x	443	TCP	Browser or vSphere Client plugin	vCenter Operations Standard 1.x virtual appliance	HTTPS server port for the vCenter Operations Standard Administration page
vCenter Operations Standard 1.x	5480	TCP	Browser	vCenter Operations Standard 1.x virtual appliance	HTTPS server port for the VMware Studio Web console to administer the virtual appliance
vCenter Operations Manager (vApp) 5.x	80	TCP	Browser	vCenter Operations Manager UI VM	HTTP server port that unconditionally redirects to HTTPS port
vCenter Operations Manager (vApp) 5.x	443	TCP	Browser or vSphere Client plugin	vCenter Operations Manager UI VM	HTTPS server port for the vCenter Operations Manager UIs: Administration, vSphere, and Custom
vCenter Operations Manager (vApp) 5.x	22	TCP	SSH Client	vCenter Operations Manager UI VM, vCenter Operations Manager Analytics VM	Enables SSH access to the vCenter Operations Manager virtual appliance
vCenter Operations Manager (vApp) 5.x	1194	TCP	vCenter Operations Manager Analytics VM	vCenter Operations Manager UI VM	Open VPN tunnel for communication between the two VMs
vCenter Operations Manager (Standalone) 5.x	443	TCP	vCenter Operations Manager UI VM, vCenter Operations Manager Analytics VM	vCenter Server	UI VM: Registration of vCenter Operations Manager as an extension to vCenter, Analytics VM: Collecting metric data from vCenter
vCenter Operations Manager (Standalone) 5.x	80	TCP	Browser	vCenter Operations Manager (Standalone)	(If chosen during configuration) HTTP port to access vCenter Operations Manager UI
vCenter Operations Manager (Standalone) 5.x	443	TCP	Browser	vCenter Operations Manager (Standalone)	(If chosen during configuration) HTTPS port to access vCenter Operations Manager UI
vCenter Operations Manager (Standalone) 5.x	1199	TCP	vCenter Operations Manager remote collector	vCenter Operations Manager (Standalone)	Heartbeat connection between remote collector and main vCenter Operations Manager server
vCenter Operations Manager (Standalone) 5.x	61616	TCP	vCenter Operations Manager remote collector	vCenter Operations Manager (Standalone)	Connection between remote collector and ActiveMQ component on the main vCenter Operations Manager server
vCenter Operations Manager (Standalone) 5.x	443	TCP	vCenter Operations Manager local/remote collector	vCenter Server	Connection between remote collector and ActiveMQ component on the main vCenter Operations Manager server
View 3.x	3389	TCP	Thin Client	ESX host	RDP Protocol
View 3.x	18443	TCP	View Connection Server/View Manager	vCenter Server	View Composer
View 3.x	32111	TCP	View Agent (Virtual Desktop)	View Client	USB Device Communication
View 3.x	32111	TCP	View Client	View Agent (Virtual Desktop)	USB Device Communication
View 4.0.x	902	TCP	View Client/View Client with Offline Desktop	ESX Host	(Optional) View Client with Offline Desktop data is downloaded and uploaded through this port.
View 4.0.x	3268	TCP	View/VDM Connection Server/View Manager	Active Directory Server	Global Catalog Server
View 4.0.x	3269	TCP	View/VDM Connection Server/View Manager	Active Directory Server	Global Catalog Server
View 4.0.x	3389	TCP	Thin Client	ESX host	RDP Protocol
View 4.0.x	9427	TCP	View Client/View Client with Offline Desktop	View Agent (Virtual Desktop)	(Optional) Multimedia Redirection (MMR). MMR is supported by View Client and View Client with Offline Desktop on certain operating systems.
View 4.0.x	18443	TCP	View Connection Server/View Manager	vCenter Server	View Composer
View 4.0.x	50002	TCP/UDP	View Agent (Virtual Desktop)	View Client	PCoIP (AES 128-bit encryption)
View 4.0.x	50002	TCP/UDP	View Client	View Agent (Virtual Desktop)	PCoIP (AES 128-bit encryption)
View 4.5.x	-	-	-	-	For more information, seeNetwork connectivity requirements for VMware View Manager 4.5 and later (1027217).
View 4.5.x	80/443	TCP	View Client with Local Mode	View Transfer Server	HTTP(S) access via direct connection for downloading and uploading Local Mode data
View 4.5.x	80/443	TCP	Security Server	View Transfer Server	HTTP(S) access via tunnel connection for downloading and uploading Local Mode data
View 4.5.x	902	TCP	View Connection Server	ESX Host	Used when checking out local desktops. Must be accessible on your ESX host when using View Client with Local Mode.
View 4.5.x	902	TCP	View Transfer Server	ESX Host	Publishing View Composer packages for Local Mode
View 4.5.x	4001	TCP	View Connection Server	View Transfer Server	Required by JMS for Local Mode
View 4.5.x	4172	TCP/UDP	View Client	View Agent (Virtual Desktop)	PCoIP (AES 128-bit encryption)
View 4.5.x	50002	UDP	View Agent (Virtual Desktop)	View Client	PCoIP (AES 128-bit encryption)
View 4.6.x	-	-	-	-	For more information, seeNetwork connectivity requirements for VMware View Manager 4.5 and later (1027217).
View 4.6.x	80/443	TCP	View Client with Local Mode	View Transfer Server	HTTP(S) access via direct connection for downloading and uploading Local Mode data
View 4.6.x	80/443	TCP	Security Server	View Transfer Server	HTTP(S) access via direct connection for downloading and uploading Local Mode data
View 4.6.x	902	TCP	View Connection Server	ESX Host	Used when checking out local desktops. Must be accessible on your ESX host when using View Client with Local Mode.
View 4.6.x	902	TCP	View Transfer Server	ESX Host	Publishing View Composer packages for Local Mode
View 4.6.x	4001	TCP	View Connection Server	View Transfer Server	Required by JMS for Local Mode
View 4.6.x	4172	TCP/UDP	View Client	View Agent (Virtual Desktop)	PCoIP (AES 128-bit encryption)
View 4.6.x	50002	UDP	View Agent (Virtual Desktop)	View Client	PCoIP (AES 128-bit encryption)
View 5.x	-	-	-	-	For more information, seeNetwork connectivity requirements for VMware View Manager 4.5 and later (1027217).
View 5.x	80/443	TCP	View Client with Local Mode	View Transfer Server	HTTP(S) access via direct connection for downloading and uploading Local Mode data
View 5.x	80/443	TCP	Security Server	View Transfer Server	HTTP(S) access via direct connection for downloading and uploading Local Mode data
View 5.x	902	TCP	View Connection Server	ESX Host	Used when checking out local desktops. Must be accessible on your ESX host when using View Client with Local Mode.
View 5.x	902	TCP	View Transfer Server	ESX Host	Publishing View Composer packages for Local Mode
View 5.x	4001	TCP	View Connection Server	View Transfer Server	Required by JMS for Local Mode
View 5.x	4172	TCP/UDP	View Client	View Agent (Virtual Desktop)	PCoIP (AES 128-bit encryption)
View 5.x	50002	UDP	View Agent (Virtual Desktop)	View Client	PCoIP (AES 128-bit encryption)
View/VDM 2.x	80	TCP	View/VDM Client	View/VDM Security Server	VDM Access (not required if only HTTPS is to be supported)
View/VDM 2.x	80	TCP	Client PC	View/VDM Security Server	VDM Web Access (not required if only HTTPS is to be supported). The Security Server used as a proxy in a DMZ to allow for external connections in. The View Manager/Connection Broker has an ADAM instance on it.
View/VDM 2.x	80	TCP	View/VDM Client	View/VDM Connection Server	VDM Access (not required if only HTTPS is to be supported)
View/VDM 2.x	80	TCP	Client PC	View/VDM Connection Server	VDM Web Access (not required if only HTTPS is to be supported).
View/VDM 2.x	88	UDP	View/VDM Connection Server/View Manager	Active Directory Server	AD Authentication
View/VDM 2.x	88	TCP	View/VDM Connection Server/View Manager	Active Directory Server	AD Authentication
View/VDM 2.x	389	TCP/UDP	View/VDM Connection Server/View Manager	LDAP Server	LDAP Authentication
View/VDM 2.x	443	TCP	View/VDM Client	View/VDM Security Server	VDM Access
View/VDM 2.x	443	TCP	Client PC	View/VDM Connection Server/View Manager	VDM Web Access and VDM Administration
View/VDM 2.x	443	TCP	Thin Client	View/VDM Connection Server/View Manager	VDM API
View/VDM 2.x	443	TCP	View/VDM Client	View/VDM Connection Server/View Manager	VDM Access
View/VDM 2.x	443	TCP	Client PC	View/VDM Security Server	VDM Web Access (Web Browser)
View/VDM 2.x	443	TCP	View/VDM Connection Server/View Manager	vCenter Server	VDM to vCenter communication
View/VDM 2.x	445	UDP	View/VDM Connection Server/View Manager	Active Directory Server	AD Authentication
View/VDM 2.x	445	TCP	View/VDM Connection Server/View Manager	Active Directory Server	AD Authentication
View/VDM 2.x	1024 to 65535	TCP	View/VDM Connection Server/View Manager	Virtual Desktop VM (View/VDM Agent)	Ephemeral Ports. A short-lived connection between View Manager and the virtual desktop
View/VDM 2.x	1024 to 65535	TCP	View/VDM Connection Server/View Manager	View/VDM Connection Server/View Manager	This is required for ADAM replication between VDM Connection Servers. With a Registry entry, this can be fixed to a defined set of ports, but by default it is a random TCP high port
View/VDM 2.x	3389	TCP	View/VDM Security Server	Virtual Desktop VM (View/VDM Agent)	Tunneled RDP Connection (RSA RC4 encryption, can be set High/Medium/Low) High: Encrypts both the data sent from client to server and the data sent from server to client using a 128-bit key. Medium: Encrypts both the data sent from client to server and the data sent from server to client using a 56-bit key if the client is a Windows 2000 or above client, or a 40-bit key if the client is an earlier version. Low: Encrypts only the data sent from client to server, using either a 56- or 40-bit key, depending on the client version. Useful to protect usernames and passwords sent from client to server.
View/VDM 2.x	3389	TCP	Client PC/Thin Client/View/VDM Client	Virtual Desktop VM (View/VDM Agent)	Direct RDP Connection (RSA RC4 encryption, can be set High/Medium/Low). High: Encrypts both the data sent from client to server and the data sent from server to client using a 128-bit key. Medium: Encrypts both the data sent from client to server and the data sent from server to client using a 56-bit key if the client is a Windows 2000 or above client, or a 40-bit key if the client is an earlier version. Low: Encrypts only the data sent from client to server, using either a 56- or 40-bit key, depending on the client version. Useful to protect usernames and passwords sent from client to server.
View/VDM 2.x	4001	TCP	View/VDM Security Server	View/VDM Connection Server/View Manager	Java Messenger Service (JMS)
View/VDM 2.x	4001	TCP	View/VDM Connection Server/View Manager	View/VDM Security Server	Java Messenger Service (JMS)
View/VDM 2.x	4001	TCP	Virtual Desktop VM (View/VDM Agent)	View/VDM Connection Server/View Manager	Java Messenger Service (JMS)
View/VDM 2.x	4100	TCP	View/VDM Connection Server/View Manager	View/VDM Connection Server/View Manager	Java Messenger Service (JMS) inter-router traffic
View/VDM 2.x	8009	TCP	View/VDM Security Server	View/VDM Connection Server/View Manager	Apache Jserv Protocol (AJP)
View/VDM 2.x	8009	TCP	View/VDM Connection Server/View Manager	View/VDM Security Server	Apache Jserv Protocol (AJP)
View/VDM 2.x	42966	TCP	View Client/View Client with Offline Desktop	ESX Host	(Optional) Hewlett-Packard RGS Sender Application is the server-side component of the HP RGS remote display protocol
vShield 1.x	22	TCP	vShield Manager	vShield agent	SSH traffic passing from vShield Manager to vShield agents
vShield 1.x	123	UDP	vShield Time Synchronization	vShield Manager (NTP Server)	NTP time synchronization with vShield Manager server
vShield 1.x	443	TCP	Web browser/Client access	vShield Manager	Web browser using HTTPS to access vShield Manager user interface
vShield 1.x	1162	UDP	vShield Zones	vShield Manager	Sends SNMP trap messages from vShield agents to vShield Manager
vShield 4.x	22	TCP	vShield Manager	vShield agent	SSH traffic passing from vShield Manager to vShield agents
vShield 4.x	123	UDP	vShield Time Synchronization	vShield Manager (NTP Server)	NTP time synchronization with vShield Manager server
vShield 4.x	443	TCP	Web browser/Client access	vShield Manager	Web browser using HTTPS to access vShield Manager user interface
vShield 4.x	1162	UDP	vShield Zones	vShield Manager	Sends SNMP trap messages from vShield agents to vShield Manager
vSphere Management Assistant	443	TCP	vSphere Management Assistant	ESX Host	For SDK traffic

VI / vSphere Client ports:

Product	Port	Protocol	Source	Target	Purpose
Data Recovery	22024	TCP	Data Recovery vSphere Client Plug-in	Data Recovery Appliance	Data Recovery management
ESX 3.x	80	TCP	VI / vSphere client	ESXi/ESX Host	Redirect Web Browser to HTTPS Service (443)
ESX 3.x	443	TCP	VI / vSphere client	ESXi/ESX Host	VI / vSphere client to ESXi/ESX Host management connection
ESX 3.x	902	TCP	VI / vSphere client	ESXi/ESX Host	VI / vSphere client to ESXi/ESX hosted VM connectivity (MKS)
ESX 3.x	903	TCP	VI / vSphere client	ESXi/ESX Host	VM Remote Console
ESX 4.x	80	TCP	VI / vSphere client	ESXi/ESX Host	Redirect Web Browser to HTTPS Service (443)
ESX 4.x	443	TCP	vSphere Client	ESXi/ESX Host	vSphere Client to ESXi/ESX Host management connection
ESX 4.x	902	TCP	vSphere Client	ESXi/ESX Host	vSphere Client to ESXi/ESX hosted VM connectivity (MKS)
ESX 4.x	903	TCP	VI / vSphere client	ESXi/ESX Host	VM Remote Console (MKS)
ESXi 3.x	80	TCP	VI / vSphere client	ESXi/ESX Host	Redirect Web Browser to HTTPS Service (443)
ESXi 3.x	443	TCP	VI / vSphere client	ESXi/ESX Host	VI / vSphere client to ESXi/ESX Host management connection
ESXi 3.x	902	TCP	VI / vSphere client	ESXi/ESX Host	VI / vSphere client to ESXi/ESX hosted VM connectivity (MKS/Remote Console)
ESXi 3.x	903	TCP	VI / vSphere client	ESXi/ESX Host	VM Remote VM Console (MKS)
ESXi 4.x	80	TCP	VI / vSphere client	ESXi/ESX Host	Redirect Web Browser to HTTPS Service (443)
ESXi 4.x	443	TCP	VI / vSphere client	ESXi/ESX Host	VI / vSphere client to ESXi/ESX Host management connection
ESXi 4.x	902	TCP	VI / vSphere client	ESXi/ESX Host	VI / vSphere client to ESXi/ESX hosted VM connectivity (MKS/Remote Console)
ESXi 4.x	903	TCP	VI / vSphere client	ESXi/ESX Host	VM Remote Console (MKS)
ESXi 5.x	22	TCP	vSphere client	ESXi 5.x	SSH Server
ESXi 5.x	80	TCP	vSphere client	ESXi 5.x	Redirect Web Browser to HTTPS Service (443)
ESXi 5.x	443	TCP	VI / vSphere client	ESXi/ESX Host	VI / vSphere client to ESXi/ESX Host management connection
ESXi 5.x	902	TCP	vSphere Client	ESXi 5.x	vSphere Client access to virtual machine consoles (MKS)
Site Recovery Manager 1.x-4.x	8095	TCP	vSphere Client	vCenter Server	SRM server and vCenter Server (intrasite only).
Site Recovery Manager 1.x-4.x	8095	TCP	vSphere Client	Site Recovery Manager	SRM client plug-in to communicate with vCenter Server
Site Recovery Manager 1.x-4.x	9007	TCP	vSphere Client	vCenter Server	SRM client plugin to communicate with vCenter Server
Site Recovery Manager 5.x	8095	TCP	vSphere Client	Site Recovery Manager	SRM client plugin to communicate with SRM server
Site Recovery Manager 5.x	8095	TCP	vSphere Client	vCenter server	SRM client plugin to communicate with vCenter server
Site Recovery Manager 5.x	9007	TCP	vSphere Client	vCenter server	SRM client plugin to communicate with vCenter server
vCenter 2.5.x	80	TCP	VI / vSphere client	vCenter Server	Redirect Web Browser to HTTPS Service (443)
vCenter 2.5.x	443	TCP	VI / vSphere client	vCenter Server	VI / vSphere client access to vCenter Server
vCenter 2.5.x	903	TCP	VI / vSphere client	vCenter Server	VI / vSphere client to VM Console
vCenter 4.x	80	TCP	VI / vSphere client	vCenter Server	Redirect Web Browser to HTTPS Service (443)
vCenter 4.x	443	TCP	vSphere Client	vCenter Server	vSphere Client access to vCenter Server
vCenter 4.x	903	TCP	VI / vSphere client	vCenter Server	VI / vSphere client to VM Console
vCenter 4.x	8080	TCP	VI / vSphere client	vCenter Server 4.x	VMware vCenter 4 Management Web Services - HTTP
vCenter 4.x	8443	TCP	VI / vSphere client	vCenter Server 4.x	VMware vCenter 4 Management Web Services - HTTPS
vCenter 5.x	80	TCP	vSphere client	vCenter Server	vCenter Server requires port 80 for direct HTTP connections.
vCenter 5.x	443	TCP	vSphere Client	vCenter Server	vCenter Server system uses to listen for connections from the vSphere Client.
vCenter 5.x	902	TCP/UDP	vSphere Client	ESXi 5.x	vSphere Client uses this ports to display virtual machine consoles.
vCenter 5.x	903	TCP	vSphere Client	ESXi 5.x	Remote console traffic generated by user access to virtual machines on a specific host.
vCenter 5.x	8080	TCP	vSphere client	vCenter Server	Web Services HTTP. Used for the VMware VirtualCenter Management Web Services.
vCenter 5.x	8443	TCP	vSphere client	vCenter Server	Web Services HTTPS. Used for the VMware VirtualCenter Management Web Services.
vCenter 5.x	9443	TCP	vSphere client	vCenter Server	vSphere Web Client Access
vCenter 5.x	10080	TCP	vSphere client	vCenter Server	vCenter Inventory Service HTTP
vCenter 5.x	10443	TCP	vSphere client	vCenter Server	vCenter Inventory Service HTTPS

Hardware and firmware requirements for 64-bit guest operating systems

2012-10-17T08:20:00.002+07:00

Purpose

This article explains the host machine hardware and firmware requirements for installing virtual machines with 64-bit guest operating systems.

Note: 64-bit guests are not supported for ESX versions 2.5.x and earlier.

For information about installing Guest Operating Systems, see the Guest Operating System Installation Guide.

Resolution

Note: This utility is provided without support from VMware and does not require ESX/ESXi, VMware Server or VMware Workstation to perform the check.

ESX/ESXi, VMware Workstation, Player, and VMware Server require a 64-bit CPU to run a 64-bit guest operating system.

Additional Information

Note: The information supplied in this section applies to older product versions.

Workstation 5.5 - 6.x, Player, and VMware Server 1.x support virtual machines with 64-bit guest operating systems only on host machines that have one of these supported 64-bit processors:

AMD Athlon 64, revision D or later
AMD Opteron, revision E or later
AMD Turion 64, revision E or later
AMD Sempron, 64-bit-capable, revision D or later (experimental support)
Intel EM64T VT-enabled processors (experimental support)

Note: The preceding link was correct as of June 21, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

AMD

Note: Because AMD Opteron and Turion processors do not ship in revision D, AMD Opteron and Turion 64 processors must be revision E or later to run 64-bit guest operating systems.

When reading AMD's documentation, revisions may be given in decimal format (rather than hexadecimal format). For example, Revision F may also be referred to as Revision 15.

For more information about AMD64, see http://www.amd.com/us/products/technologies/64-bit-computing/Pages/64-bit-computing.aspx .

Note: The preceding link was correct as of June 21, 2012. If you find the link is broken, provide feedback and a VMware employee will update the link.

Intel

Intel CPUs require EM64T and VT support in the chip and in the BIOS.

Note: If VT is enabled on an ESX host, the vmx flag is found in /proc/cpuinfo.

Notes:

Firmware/BIOS support is required to enable Intel Virtualization Technology. Some systems (particularly laptops) do not have the necessary firmware/BIOS support to enable Intel Virtualization Technology, and cannot run 64-bit guest operating systems.
In multi-processor systems, all processors must support compatible VT implementations. At a minimum, all processors must implement the same VMCS revision ID. In multi-processor systems with mixed processor steppings, 64-bit guest operating systems may not be supported.
Many servers that include CPUs with VT support might ship with VT disabled by default, and VT must be enabled manually. If your CPUs support VT but you do not see this option in the BIOS, contact your system vendor to request a BIOS version that lets you enable VT support.

reference

http://kb.vmware.com