Wired Intelligent Edge

 View Only
last person joined: 18 hours ago 

Bring performance and reliability to your network with the HPE Aruba Networking Core, Aggregation, and Access layer switches. Discuss the latest features and functionality of your switching devices, and find ways to improve security across your network to bring together a mobile-first solution
Expand all | Collapse all

VSX-SYNC: Configuration is not synchronized

This thread has been viewed 65 times
  • 1.  VSX-SYNC: Configuration is not synchronized

    Posted Dec 06, 2020 04:47 AM

    Dear Sir,

     

    We have 2 core switch running in vsx cluster mode. I'm adding a new static route in the primary node. As per my understanding this new static route should be synchronized to secondary node routing configuration. But upon checking the configuration on secondary switch the static route does not appear.  Below are the status and config of vsx.

     

    Thanks is advance

     

    ZA-CX6405-CS1# sh vsx status

    VSX Operational State

    ---------------------

    ISL channel : In-Sync

    ISL mgmt channel : operational

    Config Sync Status : in-sync

    NAE : peer_reachable

    HTTPS Server : peer_reachable

     

    Attribute Local Peer

    ------------ -------- --------

    ISL link lag256 lag256

    ISL version 2 2

    System MAC 02:01:00:00:01:00 02:01:00:00:01:00

    Platform 6405 6405

    Software Version FL.10.05.0030 FL.10.05.0030

    Device Role primary secondary

     

    vsx

    system-mac 02:01:00:00:01:00

    inter-switch-link lag 256

    role primary

    keepalive peer 172.16.9.1 source 172.16.9.0 vrf KA

    vsx-sync aaa acl-log-timer arp-security bfd-global bgp control-plane-acls copp-policy dhcp-relay dhcp-server dhcp-snooping dns icmp-tcp lldp loop-protect-global mac-lockout mclag-interfaces neighbor ospf qos-global route-map sflow-global snmp ssh static-routes stp-global time vsx-global

     



    ------------------------------
    Saiful Azlan Anuar
    ------------------------------


  • 2.  RE: VSX-SYNC: Configuration is not synchronized

    MVP GURU
    Posted Dec 06, 2020 09:31 AM
    Hi! provided that VRFs defined on Primary VSX node are synchronized on (or reproduced manually in) the VSX Secondary node...at least for the VRF where the Static Route was set...to me it looks like a bug...I mean: if you have the same VRF <vrf-name> defined on both Primary and Secondary VSX nodes and if you're adding a Static Route referenced to that VRF <vfr-name>...then the vsx-sync static-routes command should do the job for you of keeping that particular static route associated with that particular VRF well synchronized on the Secondary VSX node.

    ------------------------------
    Davide Poletto
    ------------------------------



  • 3.  RE: VSX-SYNC: Configuration is not synchronized

    Posted Dec 08, 2020 11:20 AM

    Hi,

     

    Yes, both switch has a static route defined under VRF "default" . On 28th Nov, we have upgraded the firmware from 10.05.0001 to 10.05.0030 to fix the vsx-sycn configuration issue. Just after the upgrade, i tested with adding new vlan and then it successfully replicated to the secondary switch. But somehow, 1 week after that, the sync failed when i add a static route on primary node. For  record, on 30th, i added a new dhcp pool on primary and it synced to peer. And that was the last time it synced as shown below. I'm not sure about this, but i have a feeling could it be due to my action on saving the config file( write memory) on the secondary node. I did it on 30th night. By right it is against the best practice to save config file on the secondary node?

    ZA-CX6405-CS2# sh vsx status config-sync
    Admin state : Enabled
    Operational State : Operational
    Error State : None
    Recommended remediation : N/A
    Current time : Wed Dec 9 00:00:29 2020
    Last sync time : Mon Nov 30 12:41:30 2020
    ZA-CX6405-CS2# sh vsx status config-sync vsx-peer
    Admin state : Enabled
    Operational State : Operational
    Error State : None
    Recommended remediation : N/A
    Current time : Wed Dec 9 00:01:05 2020
    Last sync time : Mon Nov 30 12:41:30 2020 

    Thanks in advance



    ------------------------------
    Saiful Azlan Anuar
    ------------------------------



  • 4.  RE: VSX-SYNC: Configuration is not synchronized

    MVP GURU
    Posted Dec 08, 2020 04:20 PM
    Hi,

    It think it is better to open a case to TAC with tech/support files

    ------------------------------
    PowerArubaSW : Powershell Module to use Aruba Switch API for Vlan, VlanPorts, LACP, LLDP...

    PowerArubaCP: Powershell Module to use ClearPass API (create NAD, Guest...)

    PowerArubaCX: Powershell Module to use ArubaCX API (get interface/vlan/ports info)..

    ACEP / ACMX #107 / ACDX #1281
    ------------------------------



  • 5.  RE: VSX-SYNC: Configuration is not synchronized

    MVP GURU
    Posted Dec 08, 2020 04:56 PM
    I don't believe that a write memory executed on the VSX Secondary is able to disrupt the vsx-sync function from VSX Primary to Secondary [*] so, as suggested by Alexis, is better to open a case with Aruba TAC.

    Provided that your VSX hasn't any VSX configuration inconsistency (and it looks like it hasn't)...probably the output of show events -d vsx-syncd command (executed on VSX Secondary) would offer some useful logs to help diagnosing your issue.

    Are there maybe differences on VSX Synchronization on both peers? use the show run vsx-sync peer-diff command to check (executed on both VSX Primary and VSX Secondary).

    [*] IIRC the sequence of write memory and copy running-config startup-config commands executed on the VSX Primary means that the copy running-config startup-config command is replicated on the VSX Secondary if the vsx configuration-sync is enabled and the VSX is working in "In-Sync" state.

    ------------------------------
    Davide Poletto
    ------------------------------



  • 6.  RE: VSX-SYNC: Configuration is not synchronized

    EMPLOYEE
    Posted Dec 09, 2020 04:45 AM
    I second what was written by Alexis and Davide. Please open a support case. This seems a bug.
    Any "wr mem" on VSX secondary should not impact vsx-sync mechanism.
    As you synchronize the static routes, I assume that the next-hop is the same on VSX primary and secondary, so it is likely to be a IP
    of a transit VLAN. Even if this transit VLAN would be removed on secondary, the route should still be synced in the CLI.

    ------------------------------
    Vincent Giles
    ------------------------------



  • 7.  RE: VSX-SYNC: Configuration is not synchronized

    Posted Dec 09, 2020 10:06 AM
      |   view attached
    Hi Vincent,

    We already open the case with TAC ( 5351790610 ).  Output of the " show run vsx-sync peer-diff" display some different between both of the configuration. Could it be because of this difference that it cannot sync? Below are the output of "show events -d vsx-syncd " on secondary node.

    2020-11-28T17:28:42.011813+08:00 ZA-CX6405-CS2 vsx-syncd[7663]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
    2020-11-28T17:28:42.012223+08:00 ZA-CX6405-CS2 vsx-syncd[7663]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
    2020-11-28T17:29:08.700228+08:00 ZA-CX6405-CS2 vsx-syncd[7663]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
    2020-11-28T19:48:52.818666+08:00 ZA-CX6405-CS2 vsx-syncd[7663]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
    2020-11-28T19:48:52.819077+08:00 ZA-CX6405-CS2 vsx-syncd[7663]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
    2020-11-28T19:48:52.819483+08:00 ZA-CX6405-CS2 vsx-syncd[7663]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
    2020-11-28T19:49:20.042186+08:00 ZA-CX6405-CS2 vsx-syncd[7663]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database
    2020-11-30T12:41:30.086656+08:00 ZA-CX6405-CS2 vsx-syncd[7663]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX configuration-sync updated database

    The last message of this event is on
    Mon Nov 30 12:41:30 2020 exactly same on the "sh vsx status config-sync" output. 


    Thanks




    ------------------------------
    Saiful Azlan Anuar
    ------------------------------

    Attachment(s)

    txt
    show event vsx.txt   185 KB 1 version


  • 8.  RE: VSX-SYNC: Configuration is not synchronized

    EMPLOYEE
    Posted Dec 10, 2020 04:08 AM
    The amount of log messages for vsx-sync is suspicious. Support should provide the analysis and proposal.

    ------------------------------
    Vincent Giles
    ------------------------------



  • 9.  RE: VSX-SYNC: Configuration is not synchronized

    MVP GURU
    Posted Dec 10, 2020 04:36 AM
    Very suspicious.

    Just for comparison our VSX (10.05.0021) currently shows:

    vsx-1# show events -d vsx-syncd -a
    ---------------------------------------------------
    Event logs from previous boots
    ---------------------------------------------------
    2019-05-03T13:01:15.025605+02:00 vsx-1 vsx-syncd[2511]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2019-09-26T14:08:41.928485+02:00 vsx-1 vsx-syncd[2511]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2019-09-26T14:41:44.999969+02:00 vsx-1 vsx-syncd[18156]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2020-02-07T11:21:57.694378+01:00 vsx-1 vsx-syncd[18156]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2020-02-07T11:29:52.449725+01:00 vsx-1 vsx-syncd[10370]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2020-02-19T10:09:01.000958+01:00 vsx-1 vsx-syncd[10370]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2020-02-19T10:18:45.345842+01:00 vsx-1 vsx-syncd[11174]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2020-02-27T09:09:19.685574+01:00 vsx-1 vsx-syncd[11174]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2020-04-20T10:38:22.223680+02:00 vsx-1 vsx-syncd[11174]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2020-04-20T10:47:27.045639+02:00 vsx-1 vsx-syncd[11659]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    2020-11-20T10:59:32.727660+01:00 vsx-1 vsx-syncd[11659]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.
    ---------------------------------------------------
    Event logs from current boot
    ---------------------------------------------------
    2020-11-20T11:11:21.204760+01:00 vsx-1 vsx-syncd[19640]: Event|7602|LOG_INFO|AMM|-|Configuration sync update : VSX Inter-Switch-Link is down.

    all logs related to the current/past update events (and nothing more).

    ------------------------------
    Davide Poletto
    ------------------------------