The VMware® Using a Proxy with vSphere Virtual Serial Ports manual provides information about developing a virtual serial port concentrator for use in the vSphere environment.
VMware provides different APIs and SDKs for various applications and goals. This manual describes the capabilities of a proxy implementation that supports the VMware telnet extension. It also includes information about configuring a virtual serial port for a proxy connection.
To view the current version of this book as well as all VMware API and SDK documentation, go to http://www.vmware.com/support/pubs/sdk_pubs.html.
Revision History
This book is revised with each release of the product or when necessary. A revised version can contain minor or major changes. Revision History summarizes the significant changes in each version of this book.
| Revision Date | Description |
|---|---|
| 02 APR 2020 | Support for VMware vSphere 7.0 |
| 26 APR 2016 | Support for VMware vSphere 6.5 |
| 12 MAR 2015 | Support for VMware vSphere 6.0 |
| 11 MAR 2014 | Supported on VMware vSphere 6.0 Beta. |
| 19 SEP 2013 | Supported in VMware vSphere 5.5; added information about TCP keepalive configuration and time limit for VMOTION-GOAHEAD response (vmotionLimit). |
| 10 SEP 2012 | Supported in VMware vSphere 5.1; added syntax for authentication parameters used with encrypted telnet and telnets connections. |
| 24 AUG 2011 | Supported in VMware vSphere 5.0. |
| 13 JUL 2010 | Initial release, supported in VMware vSphere 4.1. |
Intended Audience
This book is intended for anyone developing a virtual serial port proxy for the vSphere environment. Proxy developers should have experience with the telnet protocol and network communication.
VMware Technical Publications Glossary
VMware Technical Publications provides a glossary of terms that might be unfamiliar to you. For definitions of terms as they are used in VMware technical documentation go to http://www.vmware.com/support/pubs.
Document Feedback
VMware welcomes your suggestions for improving our documentation. Send your feedback to [email protected].
