Issues reconfiguring SRM connections within linked vCenter instances | http://127.0.0.1:9286/sdk invocation failed with "java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-37"
Article ID: 391316
Updated On:
Products
Issue/Introduction
Unable to reconfigure SRM appliance.
Error:
Unable to configure Site Recovery manager on linked vCenter environment (http://127.0.0.1:9286/sdk invocation failed with "java.net.SocketTimeoutException: 30,000 milliseconds timeout on connection http-outgoing-37
Other SRM appliances are not showing up properly in the 'Site Recovery' page in the vCenter UI.
When using the DNS names to ping, it take a long time to start (around 5-10 seconds). However, when pinging the IP address it responds instantly.
Environment
Site Recovery Manager 8.x
Live Recovery 9.x
Cause
If the SRM server's ping attempt is unsuccessful in reaching the DNS servers, the problem arises.
- The primary DNS server is not reachable, according to DNS server ping findings.
Primary DNS - ##.###.##.199
C:\Users\username>ping ##.###.##.199
Pinging ##.###.##.### with 32 bytes of data:Request timed out.Request timed out.Request timed out.Request timed out.
Ping statistics for ##.###.##.199: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
Secondary DNS server ##.###.##.200
C:\Users\username>ping ##.###.##.200
Pinging ##.###.##.200 with 32 bytes of data:Reply from ##.###.##.200: bytes=32 time=19ms TTL=122Reply from ##.###.##.200: bytes=32 time=19ms TTL=122Reply from ##.###.##.200: bytes=32 time=19ms TTL=122Reply from ##.###.##.200: bytes=32 time=19ms TTL=122
Ping statistics for ##.###.##.200: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),Approximate round trip times in milli-seconds: Minimum = 19ms, Maximum = 19ms, Average = 19ms
- The reconfiguration fails because the SRM Server cannot connect to the DNS server.
Resolution
1. Change DNS configuration for vCenter
Feedback
