Knowledge Base

The VMware Knowledge Base provides support solutions, error messages and troubleshooting guides
 
Search the VMware Knowledge Base (KB)   View by Article ID
 

Troubleshooting a Service Console connection failure

Symptoms

  • Cannot connect to the Service Console
  • Cannot use the Service Console

Resolution

The following describes the Service Console TCP/IP stacks scenarios:
  • Service Console is independent from VMkernel TCP/IP stack.
  • ESX's Service Console is a derivative of REDHAT TCP/IP stacks, therefore there are many commands that are the same and some are unique to ESX.
  • Service Console is used for ESX management purposes, file copying, and for any general purpose that may require layer 3  IP configuration. 

  • Multiple Service consoles can be configured for redundancy, and also for connecting to multiple subnets.

  • Many services require on Service Console to communicate, therefore may need more than one Service Console. For example heartbeat.
The following are basic Service Console TCP/IP configuration requirements:
  • The ESX host has physical network adapter connecting to physical network switches appliance
  • Proper/functional Ethernet Cable
  • Gateway appliance that can be either a router or switch appliance.
  • Establishing method of VLAN Tagging configuration (VST,EST, or VGT)
  • Proper IP address, network sub mask, and gateway configuration  
Note: ESX 4.0 Update 2 introduces a tool that simplifies the process of creating or restoring networking in the ESX Service Console. For more information, see Configuring or restoring networking from the ESX service console using console-setup (1022078). 　
 
Validate that each troubleshooting step below is true for your environment. The steps will provide instructions or a link to a document, for validating the step and taking corrective action as necessary. The steps are ordered in the most appropriate sequence to isolate the issue and identify the proper resolution. Please do not skip a step.
  1. Ensure your Service Console is configured correctly. For more information, see Configuring networking from the ESX service console command line (1000258). 
  2. Ensure any changes to the Service Console IP address have been correctly. For more information, see Changing the IP address, default gateway, and hostname of the Service Console in ESX (4309499).
  3. Verify that Service Console network is configured correctly. For more information, see Verifying ESX host networking configuration on the Service Console (1003796).
  4. Verify that you can perform a successful ping test. For more information, see Testing network connectivity with the Ping command (1003486).
  5. If Gateway IP address is not reachable, verify that you can establish a VLAN tagging mode. For more information, see:

Note: If your problem still exists after trying the steps in this article, please:

Tags

connect-esx manage-esx no-connectivity-esx response-time-out

See Also

Update History

03/17/2011 - Added link to 1022078

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.
What can we do to improve this information? (4000 or fewer characters)
Actions
  • Bookmark Document
  • Email Document
  • Print Document
  • Subscribe to Document
  • Bookmark and Share