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 Policies
DrillDown Icon Registration and Login
DrillDown Icon Infinicenter Console
DrillDown Icon Enterprise Cloud API
DrillDown Icon Best Practices
DrillDown Icon FAQs
DrillDown Icon General
DrillDown Icon What is the Enterprise Cloud?
DrillDown Icon Top 10 Tips and Tricks
DrillDown Icon How do I get support on Enterprise Cloud?
DrillDown Icon How do I get support for my OS or applications?
DrillDown Icon How do I contact IBM about Enterprise Cloud?
DrillDown Icon What is the difference between the names of equipment?
DrillDown Icon What is the Acceptable Use Policy?
DrillDown Icon Must I remain logged in to Infinicenter Console after deploying a server?
DrillDown Icon Is there a standalone VMware client?
DrillDown Icon Can I connect my physical servers to my Enterprise Cloud environment?
DrillDown Icon How do I get more storage for my environment?
DrillDown Icon Difference between purchased, allocated, consumed, and burst resources
DrillDown Icon What is oversubscription?
DrillDown Icon Who administers resources in the Enterprise Cloud?
DrillDown Icon Registration and Login
DrillDown Icon Environment
DrillDown Icon Networks
DrillDown Icon Virtual Machines
DrillDown Icon API
DrillDown Icon Templates
DrillDown Icon Instance-Based VMs
DrillDown Icon Cloud Services
DrillDown Icon Security and Firewalls
DrillDown Icon Bandwidth
DrillDown Icon Billing and Licensing
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
 
Top 10 Enterprise Cloud Tips and Tricks

Top 10 Enterprise Cloud Tips and Tricks

Introduction

Each Cloud customer's experience and environment is different and can vary greatly, but some things remain the same. These are what we are calling our "Top 10." They are the quick fixes to issues that present themselves time and again, always with the same corrective action.

Top 10 Tips and Tricks

Here are the "Top 10 Tips and Tricks" to provide you, our valued customer, with a quick overview of some things to keep in mind when working with the Enterprise Cloud.

  1. Connectivity to any virtual machine requires one of the following:
    • An Internet service with a node service associated with a public IP address for a specific port.
    • Note: DMZ VLAN only.

    • LAN-to-LAN VPN connection.
    • SSL VPN connection established.
    • Note: The VPN is called SSL VPN but no longer uses any SSL protocols, all of which are deprecated. Only Transport Layer Security (TLS) is supported as a secure transport protocol.

  2. Ports 902 and 903 must be open on all hardware and software firewalls to allow connectivity to the console session of a virtual machine.
  3. If you use a proxy, connectivity to a virtual machine via the console session will not be available. VMware now uses VMware Remote Console (VMRC), which does not support proxies, for remote sessions instead of the MKS plugin used previously.
  4. Keeping VMware Tools current is a best practice to keep your servers accessible, reporting properly, and possibly preventing future issues with performance and networking. Updating VMware Tools requires a restart of the virtual server. (Microsoft® Windows and UNIX® or Linux® Servers).
  5. Due to the nature of virtualization, creating and running virtual servers on a single hardware machine used by multiple customers, "more" CPUs is not necessarily better. As a best practice, we suggest starting with one CPU and adding as needed based on the amount and type of traffic the server will be handling. If you build a machine with four CPUs and it's not performing as expected, try lowering the CPUs to two. (Windows and UNIX or Linux Servers).
  6. Disabling the TCPI Offload option of the NIC is a best practice to avoid various latency and possible network issues. (Windows and UNIX or Linux Servers).
  7. Enabling or changing the Hardware Acceleration of the virtual server can resolve issues with slow or choppy mouse movement and screen refresh. (Windows and UNIX or Linux Servers).
  8. C:\i386\Disk 1 or C:\i386\Disk 2 is the default path for the installation medium of any files that may be required when installing additional operating system add-ins or applications. (Windows Servers Only).
  9. Ensure that you allocate enough space for your backup jobs; running out of space will cause the job to continually run and effect the overall performance of the server and possibly your environment.
  10. To upload an ISO file, it must be an .iso file and not an .img file. To import a virtual machine from an external location, the file type must be an .ovf file followed by the .vmdk files and cannot be a compressed file.