Received too large SFTP packet. Max supported packet size is 1024000 B

Received too large SFTP packet. Max supported packet size is 1024000 B, when connecting to a VMware Platform Services Controller (PSC) with WinSCP. This is an error you get due to the way the user specified is connecting via SSH. In fact, by default, you are connected with the “appliancesh”, so WinSCP isn’t able to connect correctly.

winscp_received-too-large-sftp-packet_Max-supported-packet-size-is-1024000-B

Here’s what to do (it can be rolled back to restore the previous settings) to access the Platform Services Controller via WinSCP:

  • SSH onto the¬†Platform Services Controller and login
  • Run the following two commands to enable the shell on the current connection
    • vmware_platform-services-controller_psc_shell-enabled
  • Now run the following command. This will enable bash at login for the user you specify. In my case, I’m happy to do it for¬†root.
      • vmware_platform-services-controller_psc_bash-enabled-for-root
  • You are now able to connect with WinSCP.

 

In order to roll back, run the following against the user you enabled bash for:

vmware_platform-services-controller_psc_appliancesh-enabled-for-root

Read More

Cannot login vpxuser

I was connecting via console to one of my VMs when I noticed that the console was not connecting and was returning an error. I went in to check the host events and I noticed loads of errors, one every a few seconds, regarding the vpxuser’s login. I wasn’t alerted as the ESXi host isn’t in production yet, so wasn’t monitored.

The error I saw in the events, once I connected to the ESXi host itself was: Cannot login vpxuser@127.0.0.1.

cannot_login_vpxuser

From vCenter instead I was seeing another error stating “Cannot synchronize host ESXiHost.itdtroplets.com. Cannot complete login due to an incorrect username or password.

cannot_synchronize_host

There are a couple of things you may try, start with the first one as it’s simpler. A reboot did not work for me.

Disconnect/Reconnect the host in vCenter

  1. In vCenter, disconnect the host by right click on it and selecting Connection > Disconnect.
    • vcenter_disconnect_host
    • Note that the host might already be disconnected.
  2. Now connect to the ESXi host via the Console and press F2 to enter the System Customization.
  3. Access the Troubleshooting Options menu.
  4. Select Restart Management Agents.
  5. Go back in vCenter, right click on the host and select Connection > Connect.
    • This might ask you to specify again the username and password to use to connect to the host and throughout the Wizard you’ll see the host summary and its VMs.

Disconnect the host in vCenter, delete the vpxuser and reconnect

  1. In vCenter, disconnect the host by right click on it and selecting Connection > Disconnect.
    • vcenter_disconnect_host
    • Note that the host might already be disconnected.
  2. Connect to the ESXi host with the vSphere Client.
  3. Click on Users’s tab.
  4. Right click on vpxuser and select Remove. Confirm when prompt to remove the user.
    • esxi_remove_vpxuser
  5. Now connect to the ESXi host via the Console and press F2 to enter the System Customization.
  6. Access the Troubleshooting Options menu.
  7. Select Restart Management Agents.
  8. Go back in vCenter, right click on the host and select Connection > Connect.
    • This might ask you to specify again the username and password to use to connect to the host and throughout the Wizard you’ll see the host summary and its VMs.
    • This step will also re-create the vpxuser.
    • Should this step fail, try one more time to restart the management agents and to connect.

 

Read More

iDRAC – Remote keyboard not working

There was an issue whilst trying to install a new VMware ESXi host on a DELL PowerEdge R630 remotely (from iDRAC): The remote keyboard was not working from iDrac after booting into the ESXi installation but it did work correctly in the BIOS.
Basically the installation was waiting for somebody to press Enter to continue which didn’t work.

esxi-installation-enter-continue

A few steps were tried to resolve the issue but in this specific case the problem was finally solved once USB 3.0 was disabled from the Bios! Specifically to this server’s bios version it’s in System Bios > Integrated devices > USB 3.0 Settings > Disabled.

poweredger630-bios-disable-usb-3-0

The other options that were tried with no luck were:

  • Upgraded all devices’ firmware to the latest versions.
  • Get in the BIOS>integrated device, disable the Memory Mapped I/O above 4GB option [This was suggested by DELL Support].
  • Checked iDRAC’s session options to Pass all keystrokes to server.
    • idrac-session-options-pass-all-keystrokes-to-server
  • Changed from Java to HTML5 in the iDRAC console settings.

Read More