Nexus Switch Peer-Keepalive Redundancy

[johnlloyd_13]

hi,

is it possible to create a redundant/secondary peer-keepalive in a nexus VPC? this is in case the mgmt0 port/cable fails.

the initial/primary peer-keepalive is currently using mgmt0 interface and via management VRF.

i plan to use a L3 SVI for the secondary peer-keepalive link.

interface mgmt0

 vrf member management
 ip address 192.168.1.1/24

vlan 99

interface vlan 99
 vrf member management2
 ip address 10.1.1.1/24

vpc domain 1
 role priority 10
 peer-keepalive destination 192.168.1.2 source 192.168.1.1 vrf management
 peer-keepalive destination 10.1.1.2 source 10.1.1.1 vrf management2

[marce1000]

  - Ref : https://www.cisco.com/c/dam/en/us/td/docs/switches/datacenter/sw/design/vpc_design/vpc_best_practices_design_guide.pdf

 >...

                                        Strong Recommendations:
When building a vPC peer-keepalive link, use the following in descending order of preference:
1. Dedicated link(s) (1-Gigabit Ethernet port is enough) configured as L3. Port-channel with 2 X 1G port is even
better.
2. Mgmt0 interface (along with management traffic)
3. As a last resort, route the peer-keepalive link over the Layer 3 infrastructure

    In a vpc-context I would not advise it anyway , because a 'one-link failure' becomes fuzzy as to whether vpc can be maintained or not.

 M.

[balaji.bandi]

as per the design cisco suggest 1 link is good enough, you do not need more link, to make complex.