- Community Home
- >
- Software
- >
- HPE Morpheus Software
- >
- HPE Morpheus VM Essentials
- >
- VME Manager Console Issue
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yesterday - last edited yesterday
yesterday - last edited yesterday
VME Manager Console Issue
We have been working on this issue for at least 10 days now with Support, but are not making much headway. I am hoping that someone may have some ideas on how this could be resolved.
From the VME Manager, no console works with any VM. You get 5 "Attempting to connect" before a "Connection Error". The result of this is that you can not create any new VMs or fix any VMs you don't have an IP connection to for out-of-band management.
In troubleshooting the issue at one point, the finger was pointed at iSCSI, and the result of that particular side quest is some freshly formatted storage volumes, no VMs on the system anymore, and a lot of work recovering production VMs back onto our old (stable) VMware environment.
There are no connectivity issues between the VME Manager and the hosts. All ports are open.
Current version is 8.0.10. Which has been upgraded from 8.09 and previously 8.08
The console access is done through Apache Guacamole, which is part of the manager. Does anyone know the technical details of how this connection works? Manager --> Guacamole --> Some Magic over IP --> host --> Some Magic --> VM.
At this point, any ideas would be welcome as Support seems out of ideas
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11 hours ago
11 hours ago
Re: VME Manager Console Issue
@Craig_Manson wrote:We have been working on this issue for at least 10 days now with Support, but are not making much headway. I am hoping that someone may have some ideas on how this could be resolved.
From the VME Manager, no console works with any VM. You get 5 "Attempting to connect" before a "Connection Error". The result of this is that you can not create any new VMs or fix any VMs you don't have an IP connection to for out-of-band management.
In troubleshooting the issue at one point, the finger was pointed at iSCSI, and the result of that particular side quest is some freshly formatted storage volumes, no VMs on the system anymore, and a lot of work recovering production VMs back onto our old (stable) VMware environment.
There are no connectivity issues between the VME Manager and the hosts. All ports are open.
Current version is 8.0.10. Which has been upgraded from 8.09 and previously 8.08
The console access is done through Apache Guacamole, which is part of the manager. Does anyone know the technical details of how this connection works? Manager --> Guacamole --> Some Magic over IP --> host --> Some Magic --> VM.
At this point, any ideas would be welcome as Support seems out of ideas
Hello @Craig_Manson,
Let's dive into some potential solutions for your VME Manager Console issue.
Given the "Attempting to connect" error followed by a "Connection Error" after five attempts, here are some areas to investigate:
Apache Guacamole Configuration: Since console access is done through Apache Guacamole, ensure that Guacamole is properly configured. Check the Guacamole server logs for any errors or warnings that might indicate the issue.
Network Connectivity: Although you've confirmed there are no connectivity issues between the VME Manager and hosts, double-check that all required ports for Guacamole are open. Typically, Guacamole uses port 4822 for SSH and 3389 for RDP.
Guacamole Version: You're running version 8.0.10 of HPE VM Essentials, which includes Guacamole server version 1.6.0. Ensure that this version is compatible with your setup.
Host and VM Configuration: Verify that the VM console connection settings are correctly configured on both the host and guest OS levels.
Some potential troubleshooting steps:
Check Guacamole Logs: Look for any error messages in the Guacamole logs that might indicate the connection issue.
Verify Host and VM Settings: Ensure that the host and VM settings are correctly configured for console access.
Test Connectivity: Use tools like telnet or nc to test connectivity to the Guacamole port.
If none of these steps resolve the issue, consider reaching out to HPE Support for further assistance or exploring community forums for similar issues.
In terms of the technical details of the connection process:
Manager to Guacamole: The VME Manager communicates with Guacamole to establish a connection.
Guacamole to Host: Guacamole uses a protocol like RDP or SSH to connect to the host.
Host to VM: The host then establishes a connection to the VM using its hypervisor-specific console access mechanism.
Keep in mind that the exact connection process might vary depending on your specific setup and configuration.
Best Regards,
Henry Cowan