Wired Intelligent Edge

VSX linkup-delay default value is 180 seconds (3 minutes)...some recommended values for Aruba 832x platforms are summarized in this table:

I'm asking if having very low ARP/MAC numbers will let the recommended linkup delay timer to be safely lowered below 120 seconds in a range between, let me say, 40 and 100 seconds.

Any experience about that?

For very few hosts/routes, say for demo purpose, I did use 40seconds.

I'll even decrease further and let you know.

Is it for production (keeping margin for scaling up) or for demo ?

Regards,

Vincent

Production.

We have a simple Layer 2 scenario only (maybe you would recall...):

0 ARP entries listed:

Aruba-8320-1# show arp summary
ARP Entry's State                 IPv4        IPv6     
---------------------------------------------------------
Number of Reachable ARP entries   0           0        
Number of Stale ARP entries       0           0        
Number of Failed ARP entries      0           0        
Number of Incomplete ARP entries  0           0        
Number of Permanent ARP entries   0           0        
---------------------------------------------------------
Total ARP Entries- 0              0           0        
---------------------------------------------------------
Aruba-8320-1# show arp summary vsx-peer 
ARP Entry's State                 IPv4        IPv6     
---------------------------------------------------------
Number of Reachable ARP entries   0           0        
Number of Stale ARP entries       0           0        
Number of Failed ARP entries      0           0        
Number of Incomplete ARP entries  0           0        
Number of Permanent ARP entries   0           0        
---------------------------------------------------------
Total ARP Entries- 0              0           0        
---------------------------------------------------------

MAC Addresses: below 100 entries on both VSX nodes.

The desire is to have VSX LAGs rapidly collecting and distributing just after a node reboot (as example, after a VSX software update).

I successfully tested (with less hosts) 30seconds. You should be good with 30seconds. Do you need to lower timer ?

No, I think 30 seconds should be sufficient given that we actually are at 180 seconds...we mainly have VSX LAGs...so, in our view, having all those VSX LAGs up in ALFNCD state as quickly as possible would be great.

Does the vsx linkup-delay timer need to be configured VSX Primary only or I must configure it (with equal values) on both VSX nodes?

You must configure it on both. The value does not have to be identical.

Say, you can have 35seconds on secondary and 30seconds on primary.

However, for simplicity, I recommend to have same values.

If you do not configure it, it will take the default value which is 180s.

Thank you so much Giles!