Host Based replication issue with VR servers.

[EvolJ]

I have an issue in my Host Based replication setup.  Since it’s a host based setup I have to use VR servers for the replications. My issue is that these VR servers will throw alarms as being disconnected.

[VMware vCenter - Alarm alarm.hbr.primary.NoConnectionToHbrServerEvent] No connection to VR Server for virtual machine

I have a ticket with VMware Support and they are saying that my virtual center server on the destination side is not a supported configuration for SRM since the VC is a VM. Which to me doesn’t make sense and is ironic in the that a VM is the preferred method according to VMware.

At first support had me make sure that all the FQDN settings were correct on both sides. That didn't help.

I was wondering if anyone had similar issues and were able to resolve them.

This is all running on version 5 for esxi and SRM. Not the update 1 either.

Thanks

Jason

[athlon_crazy]

Wow! is this true? (VC running on VM is not supported). Since when? Someone can clarify?

[EvolJ]

I upgraded to the the new update 1 and that does not seem to resolve the issue. My VR servers last a little while and then I get alerts that certain replicated VMs get disconnected.

Target: sql1

Stateless event alarm

Alarm Definition:

[Event alarm expression: No connection to VR Server.]

Event details:

No connection to VR Server for virtual machine sql1 on host esxhost2 in cluster cluster3 in datacenter1: Unknown

Then after a while the VR servers themselves show a status of disconnected in Vcenter.

Am I the only one that has this problem?

[imacari80]

ese mismo Evento me sale cuando trato de replicar una MV a un sitio alterno, y el estado de la replicacion es: not active, han podido dar con la solucion de este warninig.

es urgente que encuentre la solucion

Event details:

No connection to VR Server for virtual machine VM1 on host ESXi1 in cluster cluster3 in datacenter1: Unknown

[mvalkanov]

Hi EvolJ,

Can you check the source ESXi vmkernel.log for Hbr messages (grep Hbr vmkernel.log)? There should be details on why the vSphere Replication filter can not connect to the target VR server.

The source ESXi needs to access ports 31031 and 44046 of the target VR server.

Regards,

Martin

[imacari80]

los accesos a los puertos 31031 y 44046 de VR desde el ESXi de recuperacion estan bien

ESXI (sitio de recuperacion)

login as: root

Using
keyboard-interactive authentication.

Password:

The time
and date of this login have been sent to the system logs.

VMware
offers supported, powerful system administration tools.  Please

1. see
   www.vmware.com/go/sysadmintools for details.

The ESXi
Shell can be disabled by an administrative user. See the

vSphere
Security documentation for more information.

~ # ping
192.168.?.?        (MV vSphere Replication)

PING 192.168.?.?
(ping 192.168.?.?): 56 data bytes

64 bytes
from ping 192.168.?.?: icmp_seq=0 ttl=59 time=1.851 ms

64 bytes
from ping 192.168.?.?: icmp_seq=1 ttl=59 time=1.521 ms

64 bytes
from ping 192.168.?.?: icmp_seq=2 ttl=59 time=1.517 ms

--- ping
192.168.?.?ping statistics ---

  3 packets
transmitted, 3 packets received, 0% packet loss

  round-trip
min/avg/max = 1.517/1.630/1.851 ms

~ #

~ # nc -z ping
192.168.?.? 31031

Connection
to ping 192.168.?.? 31031 port [tcp/*] succeeded!

~ # nc -z ping
192.168.?.? 44046

Connection
to ping 192.168.?.? 44046 port [tcp/*] succeeded!

[mvalkanov]

Hi imacari80,

What about error messages in vmkernel.log? Did you try grepping for Hbr?

Regards,

Martin

[imacari80]

me ayudas con los pasos para sacar estos mensajes?

[mvalkanov]

Hi imacari80,

You could:

ssh root@<source_esxi_ip>

cd /var/log

grep Hbr vmkernel.log

or use scp/WinScp to copy /var/log/vmkernel.log from the source ESXi on your workstation and search for Hbr using your favorite text editor.

Regards,

Martin

[imacari80]

dede el host ESXi desde donde estan instalados el vcenter y el Vsphere Replication al ejecutar estos comandos desde putty sale lo siguiente:

2013-06-26T14:07:12.783Z
cpu20:8212)WARNING: Hbr: 534: Connection failed to 127.                                                                                        0.0.1
(groupID=GID-feaf8e10-71ef-443e-b51c-e899b72dbf99): Connection refused

2013-06-26T14:07:12.783Z
cpu20:8212)WARNING: Hbr: 4322: Failed to establish conn                                                      
                                ection to
[127.0.0.1]:31031(groupID=GID-feaf8e10-71ef-443e-b51c-e899b72dbf99): C                                                                                      
onnection refused

2013-06-26T14:08:42.785Z
cpu20:11555)WARNING: Hbr: 534: Connection failed to 127                                                                                      
.0.0.1 (groupID=GID-feaf8e10-71ef-443e-b51c-e899b72dbf99): Connection
refused

2013-06-26T14:08:42.785Z
cpu20:11555)WARNING: Hbr: 4322: Failed to establish con                                                                                      
nection to [127.0.0.1]:31031(groupID=GID-feaf8e10-71ef-443e-b51c-e899b72dbf99):                                                                                         Connection
refused

2013-06-26T14:09:01.771Z
cpu0:13302)Hbr: 1399: Terminating sync task (diskID=RDI                                                                           
           D-a70cf372-a3a7-4cef-abc8-fd933cffca79)
(resumeIndex=0)

/var/log #

no entiendo por que sale error en una conexion a la ip: 127.0.0.1, no tengo en mi sistema nada configurado con esta ip

quedo atento a una pronta respuesta.

[mvalkanov]

Hi imacari80,

Looking at the provided logs, VRMS has wrongly supplied replication traffic address '127.0.0.1' when configuring the replication.

Please open an SR and upload vSphere Replication support bundle + /etc/hosts file from the VR appliance.

Regards,

Martin

[imacari80]

disculpa me puedes explicar un poco mas como realizar lo que me pides.

[mvalkanov]

Hi,

Please contact VMware Global Support Services and point them to this thread.

They will assist you through so called "support request" process.

Regards,

Martin

[imacari80]

ya este caso esta escalado a Vmware hace mas de 20 dias y ya sacaron LOGs y varias cosas mas y a la fecha no he tenido una respuesta satisfactoria por parte de ellos. Y este tema amerita solucion urgente.

[mvalkanov]

Hi,

Please check the value of field "VRM Host:" at the VR VAMI UI (https://vr_appliance_ip:5480/ and navigate to Configuration tab).

If this field does not point to an IP address, but to a DNS name, check also the /etc/hosts file at the VR appliance and verify that the DNS name is on a separate line from localhost and 127.0.0.1 and the line for the DNS name includes the IP address of the appliance.

Could you also share the support request number?

Regards,

Martin