06-25-2016 12:16 PM - edited 03-08-2019 06:22 AM
Hi We have 2 x Nexus 7000 switches with dual sups. Currently the peer keepalive links are connected directly
N7K1 SUP1 -----------------------SUP1 N7K2
SUP2------------------------SUP2
In case one of the supervisors switch over, the keepalive will be lost. So I want to configure a dedicated keepalive on my VDC and reuse the mgmt ports for mgmt purposes. I understand the keepalive and mgmt can be used together with an intermediary switch but dont want to go there yet.
So would I be right in saying I could create a new keepalive vrf and use 2 interfaces on my line card and build a keepalive. Configs as follows:
CONFIGURATIONS SW1
vrf context VPC_keepalive
interface XXXX
vrf member VPC_keepalive
ip address 10.1.100.21/30
vpc domain 100
peer-keepalive destination 10.1.100.22 source 10.1.100.21 vrf VPC_keepalive
CONFIGURATIONS SW1
vrf context VPC_keepalive
interface XXXX
vrf member VPC_keepalive
ip address 10.1.100.22/30
vpc domain 100
peer-keepalive destination 10.1.100.21 source 10.1.100.22 vrf VPC_keepalive
Solved! Go to Solution.
06-25-2016 12:27 PM
Hi just so you are aware there are 3 ways you should do vpc keepalives this is the recommended best practices, the link below shows examples , we questioned TAC regarding these before after a lot of discussions we used no 2 through a mgmt. switch stack as we use oob as well and send all mgmt. traffic through our fws
http://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
06-25-2016 12:27 PM
Hi just so you are aware there are 3 ways you should do vpc keepalives this is the recommended best practices, the link below shows examples , we questioned TAC regarding these before after a lot of discussions we used no 2 through a mgmt. switch stack as we use oob as well and send all mgmt. traffic through our fws
http://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
06-25-2016 07:30 PM
Thanks Mark, the document is really helpful. I have gone and setup a dedicated link and all works a treat.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide