cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1106
Views
0
Helpful
11
Replies

nexsus 5020 vpc domain peer-keepalive to ethernet interface

teymur azimov
Level 1
Level 1

hi dears.

i configuration vpc domain at nexsus 5020. i want to ask you one question.

is it possibly i configurate  vPC Domain  with ethernet interface not management interface.

for example at management interface i do this config.

On switch A:

interface mgmt0
ip address 192.168.200.13/30

On switch B:

interface mgmt
 ip address 192.168.200.14/30

On switch A:

vpc domain 1
 peer-keepalive destination 192.168.200.14 source 192.168.200.13 vrf management

On Switch B:

vpc domain 1
 peer-keepalive destination 192.168.200.13 source 192.168.200.14 vrf man

if it is possibly i can configurate at ethernet interface please write me how?

thank you very much.

11 Replies 11

Reza Sharifi
Hall of Fame
Hall of Fame

Hi,

Yes, although it is recommended but you don't have to use the management interface for your peer keep alive.

You can use any other interface, but that interface needs to be in a separate vrf.

http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/configuration_guide_c07-543563.html

HTH

Hi Reza.

thank you to reply me.

The Cisco Nexus 5000 Series does not support creation or configuration of additional Virtual Route Forwarding (VRF) instances. Two VRF instances are created when the system boots: management and default. The management interface is in the VRF management instance, and all SVIs are in the VRF default instance.

you wrote that i configurate  seperate vrf, is separate vrf include default vrf instance?because nexsus 5020 does not support

additionla VRF.

my config like that:

On switch A:

interface ethernet1/1
ip address 192.168.200.13/30

On switch B:

interface ethernet1/1
 ip address 192.168.200.14/30

On switch A:

vpc domain 1
 peer-keepalive destination 192.168.200.14 source 192.168.200.13 vrf default

On Switch B:

vpc domain 1
 peer-keepalive destination 192.168.200.13 source 192.168.200.14 vrf default

is this is configuration correct?

thanks

Hello Teymur,

You may use the default VRF.

All SVIs are in the VRF default instance

Both management interfaces and SVIs can be used for peer keepalive links. The management interface and VRF management instance are the defaults.

Please check the following link:

http://www.cisco.com/en/US/prod/collateral/switches/ps9441/ps9670/configuration_guide_c07-543563.html

HTH,

Alex

*Please rate helpful posts

Hi Alexander. thanks. i read your link but there is configuration management interface.

is my config correct?do i need addional configuration?

Hi Teymur,

Please look at step 4 and the second example on the same page.

Step 4

peer-keepalive destination ipaddress [hold-timeout secs | interval msecs {timeout secs} | {precedence {prec-value | network | internet | critical | flash-override | flash | immediate priority | routine}} | tos {tos-value | max-reliability | max-throughput | min-delay | min-monetary-cost | normal}} |tos-byte tos-byte-value} | source ipaddress | vrf {management | default}]

Example:

Management interface for peer keepalive link:

switch(config-vpc-domain)# peer-keepalive destination 172.28.230.85

switch(config-vpc-domain)#

SVI for peer keepalive link:

switch(config-vpc-domain)#peer-keepalive destination 172.28.1.100 source 172.28.1.120 vrf default

Configure the IPv4 address for the remote end of the vPC peer keepalive link.

The system does not create the vPC peer link until you configure a vPC peer keepalive link.

The  Cisco Nexus 5000 Series does not support creation or configuration of  additional Virtual Route Forwarding (VRF) instances. Two VRF instances  are created when the system boots: management and default. The management interface is in the VRF management instance, and all SVIs are in the VRF default instance.

Both management interfaces and SVIs can be used for peer keepalive links. The management interface and VRF management instance are the defaults.

The second example shows how to configure the SVI as the keepalive link. The source address must be specified when the VRF default instance is used for peer keepalive communication.

HTH,

Alex

*Please rate helpful posts

ok. do i need configuration any interface for vpc peer-keepalive ?

if yes so my config like that.

On switch A:

interface ethernet1/1
ip address 192.168.200.13/30

On switch B:

interface ethernet1/1
 ip address 192.168.200.14/30

On switch A:

vpc domain 1
 peer-keepalive destination 192.168.200.14 source 192.168.200.13 vrf default

On Switch B:

vpc domain 1
 peer-keepalive destination 192.168.200.13 source 192.168.200.14 vrf default

thanks.


can you say me is my configuration correct? do i need add addtional configuration for vpc keepalive?

keepaive config:

switch(config-vpc-domain)#peer-keepalive destination 172.28.1.100 source 172.28.1.120 vrf default

which interface i assign this ip address?(172.28.1.100-nexsus1)

can i need physical connection for keepalive link?

Its all upto you which interface you want to you as you said if its not part of management vrf then it would be part of default.

thanks Ajay.

nexsus1:

int eth 4

ip address 172.28.1.120 255.255.255.0

switch(config-vpc-domain)#peer-keepalive destination 172.28.1.100 source 172.28.1.120 vrf default

is it rigth?

do i need write vrf default context?

Does not make any diffrence its all upto you.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco