Wireless Access

 View Only
last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

VIA error message -- Attempt to send heartbeats to the controller failed

This thread has been viewed 20 times

  • 1.  VIA error message -- Attempt to send heartbeats to the controller failed

    EMPLOYEE
    Posted Oct 15, 2018 08:38 AM

    I am receiving the VIA error message, “Attempt to send heartbeats to the controller failed” after the VIA VPN becomes operational.

     

    The Wireshark trace shows an ICMP message with Aruba heartbeat.

     

    Frame 33: 69 bytes on wire (552 bits), 69 bytes captured (552 bits) on interface 0
    Ethernet II, Src: ArubaNet_dd:11:40 (00:0b:86:dd:11:40), Dst: IntelCor_80:05:ac (34:02:86:80:05:ac)
    Internet Protocol Version 4, Src: 192.168.53.100, Dst: 192.168.53.200
    Internet Control Message Protocol
    Type: 0 (Echo (ping) reply)
    Code: 0
    Checksum: 0x4cea [correct]
    [Checksum Status: Good]
    Identifier (BE): 1 (0x0001)
    Identifier (LE): 256 (0x0100)
    Sequence number (BE): 11352 (0x2c58)
    Sequence number (LE): 22572 (0x582c)
    [Request frame: 32]
    [Response time: 4.183 ms]
    Data (27 bytes)
    0000 41 72 75 62 61 20 56 69 61 20 43 6c 69 65 6e 74 Aruba Via Client
    0010 20 48 65 61 72 74 42 65 61 74 00 HeartBeat.

     

    VIA version 3.2.3.0.107807

     

    heartbeat failed.png



  • 2.  RE: VIA error message -- Attempt to send heartbeats to the controller failed

    EMPLOYEE
    Posted Oct 16, 2018 06:00 AM

    It appears that you have your VIA client in the same subnet as the controller. I could not make that work either in the past, and when I added router in front of it that blocks direct traffic between client and controller, it worked. The VPN will also not come up when the client can reach the controller IP as it thinks it is in the corporate network.

     

    After some tests I setup a simple firewall with NAT port forwarding udp/4500 to the controller and DHCP on the outside for the client.



  • 3.  RE: VIA error message -- Attempt to send heartbeats to the controller failed

    EMPLOYEE
    Posted Mar 19, 2019 11:23 AM

    I have the same problem, but the VIA controller isn't on the same subnet, it's across the country. But my hunch is that it's due to an IP scheme conflict; the local network I'm using here is a 10.x.x.x, and VIA is pushing a route for all 10.x.x.x traffic to go through the VPN... open to any ideas or thoughts for testing...



  • 4.  RE: VIA error message -- Attempt to send heartbeats to the controller failed

    EMPLOYEE
    Posted Mar 19, 2019 01:26 PM

    I agree, conflicting IP address space is probably the problem here.

     

    @ArubaMike wrote:

    I have the same problem, but the VIA controller isn't on the same subnet, it's across the country. But my hunch is that it's due to an IP scheme conflict; the local network I'm using here is a 10.x.x.x, and VIA is pushing a route for all 10.x.x.x traffic to go through the VPN... open to any ideas or thoughts for testing...

     



  • 5.  RE: VIA error message -- Attempt to send heartbeats to the controller failed

    Posted 3 days ago

    Hi Herman, I encountered this problem ( client and control on the same subnet ), and your solution worked instantly. Thank you; your help is priceless. 
    Update now it go down after 2 mins :-) 



    Original Message


  • 6.  RE: VIA error message -- Attempt to send heartbeats to the controller failed

    Posted Mar 24, 2019 05:39 AM

    thanks you.