- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Systems Insight Manager
- >
- Re: Regarding P2V "Agent cannot be connected" mess...
Categories
Company
Local Language
Forums
Discussions
- Integrity Servers
- Server Clustering
- HPE NonStop Compute
- HPE Apollo Systems
- High Performance Computing
Knowledge Base
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Knowledge Base
Forums
Discussions
- Cloud Mentoring and Education
- Software - General
- HPE OneView
- HPE Ezmeral Software platform
- HPE OpsRamp Software
Knowledge Base
Discussions
Forums
Discussions
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
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
09-29-2006 02:11 AM
09-29-2006 02:11 AM
We would like to know whether we can P2V beyond L3 switch, which is connected another
subnet.
At the hpvmmsvc.log, the following log was recorded:
INFO | jvm 1 | 2006/09/28 14:05:26 | DEBUG - ** dstVLI = [[manufacturer=VMware name=ESX version=2.5.3 build-22981] numberOfVMs=3]
INFO | jvm 1 | 2006/09/28 14:05:26 | DEBUG - ** dstName = itwfz4
INFO | jvm 1 | 2006/09/28 14:07:19 | DEBUG - Agent 146.50.129.19 not connected: java.rmi.ConnectException: Connection refused to host: 146.50.129.19; nested exception is:
INFO | jvm 1 | 2006/09/28 14:07:19 | java.net.ConnectException: Connection timed out: connect
INFO | jvm 1 | 2006/09/28 14:07:45 | WARN - com.hp.mx.vmm.vmtools.grid.VmmRuntimeException: Agent cannot be connected
INFO | jvm 1 | 2006/09/28 14:08:11 | WARN - com.hp.mx.vmm.vmtools.grid.VmmRuntimeException: Agent cannot be connected
INFO | jvm 1 | 2006/09/28 14:08:17 | WARN - com.hp.mx.vmm.vmtools.grid.VmmRuntimeException: Agent cannot be connected
[QUESTION]
- Can we execute P2V beyond L3 switch which is connected another network ?
- Could you tell me any hint for solve this trouble? What shall we do ?
Thank you for support and advice.
Best Regards.
/Minoru.Asano
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-03-2006 11:42 PM
10-03-2006 11:42 PM
Re: Regarding P2V "Agent cannot be connected" message
Does anybody has idea ?
What shall I do to analyze this phenomenon ?
Thank you for support.
Best Regards.
/Minoru.Asano
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2006 04:19 PM
10-04-2006 04:19 PM
Re: Regarding P2V "Agent cannot be connected" message
I attach the screen shot and log file.
Best Regards.
/Minoru.Asano
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-04-2006 08:57 PM
10-04-2006 08:57 PM
SolutionAlso if you have a firewall, it should be configured to allow TCP traffic on the following ports : 1125 and 1126
Hope that helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-16-2006 01:40 PM
10-16-2006 01:40 PM
Re: Regarding P2V "Agent cannot be connected" message
Thank you for reply.
We guess that the trouble has happened due to specification for SMP 2.0.2.
The network segment of source machine was different from target ESX server.
So we recommend that those machine set to same network segment.
Thank you.
Best Regards.
/Minoru.Asano