IBM logoEnterprise Cloud Management SupportContact Us
ArticlesArticles Most Popular ArticlesMost Popular Articles Most Helpful ArticlesMost Helpful Articles Submit A QuestionSubmit A Question
RSS Feeds
Skip Navigation
DrillDown Icon Table of Contents
DrillDown Icon Enterprise Cloud
DrillDown Icon Release Notes
DrillDown Icon Known Issues
DrillDown Icon Cannot Mount ISO
DrillDown Icon Console Connect with a Proxy
DrillDown Icon IPv6 and Windows Server 2003
DrillDown Icon Policies
DrillDown Icon Registration and Login
DrillDown Icon Infinicenter Console
DrillDown Icon Enterprise Cloud API
DrillDown Icon Best Practices
DrillDown Icon FAQs
DrillDown Icon Troubleshooting
DrillDown Icon Enterprise Cloud Managed Edition
DrillDown Icon Sales and Support
DrillDown Icon Proprietary Statement
  Email This ArticlePrint PreviewPrint Current Article and All Sub-Articles
 
Console Connect with a Proxy

Console Connect with a Proxy

Note: This issue affects only the Plugin Console. The Web Console functions correctly with a proxy.

Issue:

Use of a local proxy server causes connecting to the console of a virtual machine to fail.

Potential Impact:

Inability to use the console session to access a virtual machine or to manage a virtual machine at the operating system level.

ETA:

No ETA available at this time.

Source of Issue:

In vSphere 4.1, VMware removed the use of the mks-plugin as a method to connect to the console of a virtual machine, noting it as a security issue, and changed to using the VMware Remote Console (VMRC). For IBM, this meant updating the code to use a proxy server to which users connect. As such, use of a proxy at the organization site will not allow connectivity via console because VMRC will try to bypass the local proxy and connect directly to our proxy and hosts.

Workaround:

  1. Build a Windows virtual machine and use it as a jump box to eliminate the use of your local proxy through your local network.
  2. Connect to the virtual machine via SSH/RDP.
  3. Open IP addresses to the DMZ through the use of Trusted Network Groups to allow only certain IP addresses access to the virtual machine over the Internet.
  4. Add a LAN-to-LAN VPN connection to your environment. A LAN-to-LAN VPN connection replaces the SSL VPN and bypasses the proxy issue. Contact your service delivery manager to purchase a LAN-to-LAN VPN connection.