Loading

×Sorry to interrupt
CSS Error

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Cisco Nexus 1000V Virtual Supervisor Module connection to vCenter Server fails (1013448)

Last Updated: 3/20/2024Categories: TroubleshootingTotal Views: 12521Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

During installation, the Cisco Nexus 1000V Virtual Supervisor Module (VSM) connection to VMware vCenter Server fails.

You see the error:

vms_get_aERROR: [VMWARE-VIM] Operation could not be completed due to connection failure.
EOF was observed that violates the protocol. The client probably provided invalid authentication information.
SSL connect failed in tcp_connect()

Virtual machines that are down cannot be powered on, and virtual machines cannot be successfully migrated using vMotion.

None of the Virtual Ethernet Module (VEM) modules appear as modules in the VSM.

Purpose

This article provides information on resolving a mismatch between the Nexus 1000V vCenter Server port settings and the actual vCenter Server port settings.

Cause

The Nexus 1000V VSM connects to vCenter Server via the default TCP/UDP port setting. If the vCenter Server default TCP/UDP ports have been customized, the VSM cannot connect to vCenter Server.

The VSM attempts to connect via ports 80 and 443. These ports can be in use by services other than vCenter Server, with the vCenter Server ports customized to other values.

Impact / Risks

The vCenter services must be restarted if the port numbers are changed. Similarly, the VSM must be resynchronized after modifying the configuration.

Resolution

To resolve this issue, modify the vCenter Server default TCP/UDP port setting.

Note: If you cannot modify the vCenter Server default TCP/UDP port setting in the steps below, contact Cisco support for any additional assistance to modify the ports the Nexus 1000V uses to connect to the vCenter Server. See step 6, below.

To set the HTTP/HTTPS proxy ports in vCenter Server:

Note: This example uses ports 81 and 444 as the target ports.

Log into vCenter Server using the vSphere Client.

Navigate to Administration > vCenter Server Settings > Advanced Settings.

Locate WebService.Ports.http and change the value to 81.

Locate WebService.Ports.https and change the value to 444.

Note: You may use any available ports for these values.

Restart vCenter services. For more information, see Stopping, starting, or restarting vCenter services (1003895).

Take backup of the running configuration, and change the port on the VSM point to port 81 for SVS connections. If you experience any difficulty understanding these commands or do not know how to enter supervisor mode on the Nexus, engage Cisco support:

switch# copy run start

switch# config t

switch(config)# svs connection VC

switch(config-svs-conn)# protocol vmware-vim

switch(config-svs-conn)# remote ip address vCenter Server IP address

switch(config-svs-conn)# remote port 81

switch(config-svs-conn)# vmware dvs datacenter-name Datacenter

switch(config-svs-conn)# connect

Note: If you experience any difficulty understanding these commands or do not know how to enter supervisor mode on the Nexus, engage Cisco support

After connecting from the VSM to vCenter and the VEMs appear in the VSM, enter the copy run start command to save your new configuration. Otherwise, enter the revert command to wipe away your changes; then establish what the vCenter IP address and port number are and try again.

To modify vCenter Server TCP/UDP ports using regedit:

Note: This procedure modifies the Windows registry. Before making any registry modifications, ensure that you have a current and valid backup of the registry and the virtual machine. For more information on backing up and restoring the registry, see Microsoft Knowledge Base article How to Modify the Windows Registry.

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

Click Start > Run, type regedit and click OK.

Navigate to:

HKEY_LOCAL_MACHINE\SOFTWARE\Vmware, Inc.\VMware VirtualCenter

HttpProxyPort identifies the port configured for HTTP and has a default value of 80.

To change this value:

Double-click HttpProxyPort.

Change the Value data.

Click OK.

HttpsProxyPort identifies the port configured for HTTPS and has a default value of 443.

To change this value:

Double-click HttpsProxyPort.

Change the Value data.

Click OK.

Reboot the server and see step 6 above to correct the port setting in the Nexus.

Related Information

To test the connectivity from the Nexus 1000V VSM to the vCenter Server on ports 80 and 443:

Use telnet to connect to the vCenter Server from any other Windows virtual machine on port 443.

Create a new virtual machine or use any existing windows virtual machine and make it part of the same portgroup/dvportgroup as the Nexus 1000V VSM, then use telnet from that Windows virtual machine to vCenter Server on port 443.

Do a traceroute from the vCenter Server to the Nexus 1000V VSM and note the result.

Set up a wireshark trace on the vCenter Server to capture the events for ports 80 and 443.

For more information on setting the vCenter Server ports in the Nexus 1000V, see Managing Server Connections in Cisco Nexus 1000V System Management Configuration Guide, Release 4.0(4)SV1(2).

Note: The links in this article were correct as of February 18, 2014. If you find a link is broken, provide feedback and a VMware employee will update the link.How to stop, start, or restart vCenter Server services

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

KB
•
Download and Install VMware Fusion (2014097)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vSphere ESXi

VMware vCenter Server

VMware ESX Server

Related Versions:

VMware vSphere ESXi 5.5

VMware vSphere ESXi 5.1

VMware vSphere ESXi 5.0

VMware vCenter Server 4.0.x

VMware ESX 4.1.x

VMware ESX 4.0.x

Take Our Survey

Support Assistant