Question

  • Creator
    Topic
  • #3977186

    VIP IP address stops working!!

    by babybaboo724 ·

    Tags: 

    We have an Aryaka VPN or SD-WAN setup. Which includes 2 Aryaka ANAP HA devices each one connected into our Core HP Switch 8212zl to the VLAN that is our gateway through our SonicWall NSA 5600 Firewall. We are also running VRRP along with BGP. The Aryaka has a Gateway IP 172.26.90.14 and 2 other IP addresses for the Ethernet cards 172.26.90.2 & 172.26.90.3. The HA setup requires a VIP IP address so we use 172.26.90.1 Subnet Mask /28…All has been working fine for years. But now we need to change the VIP IP address every 5 months because it becomes very slow with high Latency . Typically our QOS 50ms But the VIP is returning Pings as high as 600ms and dropped connections.

    Ready for this ? When we change the VIP IP address to a different IP i.e. 172.26.90.4 everything returns to normal again for about 5 months and then we need to change it again!! Any Ideas why a VIP IP address becomes stagnant or broken??? Thanks in advance…

You are posting a reply to: VIP IP address stops working!!

The posting of advertisements, profanity, or personal attacks is prohibited. Please refer to our Community FAQs for details. All submitted content is subject to our Terms of Use.

All Answers

  • Author
    Replies
    • #3977194
      Avatar photo

      Sounds like a firmware bug.

      by rproffitt ·

      In reply to VIP IP address stops working!!

      Here’s a known problem. Many devices work fine for days or longer but the maker can’t/won’t test for months of operation. All it takes is a small memory leak (common name for any number of software issues) and in a few days or weeks the device can develop issues.

      I don’t own or have access to that device or code but it fits the usual problem and the fix is to do what you noted and try another version of firmware.

      I would not seek too long on forums as the device isn’t one I’ve seen IRL or under discussion but the issue is not uncommon.

      1. Keep doing what you do to fix it.
      2. Report it as a bug to the maker.
      3. Try other firmware versions.

Viewing 0 reply threads