Hi Andrew,
I did a quick research and I am not able to find any information from the guides regarding the "configmate" command.
I have tried it on one lab VSX (not in production) with a bit newer version (8320 TL.10.05.0021 – outdated version as well):
VSX1-SW1(config)# vsx-configmate
============================================
VSX FEATURE CONFIG PARSER
============================================
VSX configuration validation results below:-
Rule-1: The allowed VLAN list for ISL port must match that in config for MCLAG in VSX1-SW1 (Skipped)
Rule-1: The allowed VLAN list for ISL port must match that in config for MCLAG in VSX1-SW2 (Skipped)
Rule-2: The native VLAN must also be part of allowed VLAN list for a MCLAG in VSX1-SW1 (Skipped)
Rule-2: The native VLAN must also be part of allowed VLAN list for a MCLAG in VSX1-SW2 (Skipped)
Rule-3: The inter-switch-link Timers should be consistent across VSX peers (Passed)
Rule-4: The Keep-Alive Timers should be consistent across VSX peers (Passed)
Rule-5: Active-Gateway configurations(IP, MAC and VRF) should be consistent across the VSX peers (Passed)
Rule-6: The Keep-Alive UDP port should be consistent across VSX peers (Passed)
Rule-7: The link-up-delay-timer should be consistent across VSX peers (Passed)
Rule-8: The VSX System-MAC should be consistent across VSX peers (Passed)
Rule-9: The VSX device roles should be consistent across VSX peers (Passed)
Rule-10: VSX active-forwarding configurations should be consistent across the VSX peers (Passed)
=============== SKIP REASONS ===============
Rule-1: No MCLAGs are configured on VSX1-SW1
Rule-1: No MCLAGs are configured on VSX1-SW2
Rule-2: No MCLAGs are configured on VSX1-SW1
Rule-2: No MCLAGs are configured on VSX1-SW2
As you can see there is even a "skip reasons" table, which is missing on your device (or you didn't paste the whole output from your device).
For me "skipped" means that for some reason the validation was not performed – not failed, but not validated.
I have tried to change the VSX system mac and the configmate result was "skipped" during synchronization:
VSX1-SW2(config)# sh vsx brief
ISL State : In-Sync
Device State : Sync-Secondary-Linkup-Delay
Keepalive State : Keepalive-Init
Device Role : secondary
Number of Multi-chassis LAG interfaces : 0
After few seconds the state was changed to "peer-established" and the configmate result was fine again:
VSX1-SW2(config)# sh vsx brief
ISL State : In-Sync
Device State : Peer-Established
Keepalive State : Keepalive-Init
Device Role : secondary
Number of Multi-chassis LAG interfaces : 0
If the VSX status on your cluster looks ok and the device state on both nodes is "Peer-Established" and there are no VSX issues, I will advise you to update the FW of your device to a newer, current version.
------------------------------
Stanislav Naydenov
------------------------------
Original Message:
Sent: Jun 28, 2021 07:13 AM
From: Andy Partridge
Subject: vsx-configmate command inconstancies
Excuse the spelling mistake - vsx-configmate inconsistency
Using the vsx-config mate command on a VSX pair and the output is showing as skipped although the config looks 100%, does skipped mean its failed the test or something else?
Version is 10.05.0011 and it appears to be skipped due to not VSX peer not being ready. Is this a firmware issue or a bug in the command?
SWITCH-002# vsx-configmate
============================================
VSX FEATURE CONFIG PARSER
============================================
VSX configuration validation results below:-
Rule-1: The allowed VLAN list for ISL port must match that in config for MCLAG in SWITCH-002 (Passed)
Rule-1: The allowed VLAN list for ISL port must match that in config for MCLAG in sw2 (Skipped)
Rule-2: The native VLAN must also be part of allowed VLAN list for a MCLAG in SWITCH-002 (Passed)
Rule-2: The native VLAN must also be part of allowed VLAN list for a MCLAG in sw2 (Skipped)
Rule-3: The inter-switch-link Timers should be consistent across VSX peers (Skipped)
Rule-4: The Keep-Alive Timers should be consistent across VSX peers (Skipped)
Rule-5: Active-Gateway configurations(IP, MAC and VRF) should be consistent across the VSX peers (Skipped)
Rule-6: The Keep-Alive UDP port should be consistent across VSX peers (Skipped)
Rule-7: The link-up-delay-timer should be consistent across VSX peers (Skipped)
Rule-8: The VSX System-MAC should be consistent across VSX peers (Skipped)
Rule-9: The VSX device roles should be consistent across VSX peers (Skipped)
Rule-10: VSX active-forwarding configurations should be consistent across the VSX peers (Skipped)
SWITCH-002#
------------------------------
Andrew Partridge
------------------------------