09-09-2013 02:40 AM - edited 03-07-2019 03:21 PM
Hi
I have two nexus in vpc domain 1. VPC is running fine without problem.
When I configured the config sync on both nexus, switch profile status shows peer unreachable. Wondering why peers are unreachable in ONLY conf-sync case, when both vpc and switch profile configs are configured with mgmt IP address. configuration below. Am I missing any thing... does anyone has any comment ? Thanks
Configuration is attached !
Nexus 01
!Command: show running-config vpc
!Time: Mon Sep 9 11:35:35 2013
version 5.2(1)N1(4)
feature vpc
logging level vpc 6
vpc domain 1
role priority 110
peer-keepalive destination 172.18.10.4 <- mgmt address
auto-recovery
fabricpath switch-id 1001
interface port-channel1
vpc peer-link
switch-profile dc2-sp
sync-peers destination 172.18.10.4 <- mgmt address
nexus 02
!Command: show running-config vpc
!Time: Mon Sep 9 11:33:17 2013
version 5.2(1)N1(4)
feature vpc
logging level vpc 6
vpc domain 1
peer-keepalive destination 172.18.10.3 <- mgmt address
auto-recovery
fabricpath switch-id 1001
interface port-channel1
vpc peer-link
switch-profile dc2-sp
sync-peers destination 172.18.10.3 <- mgmt address
slv-sw01# sh running-config cfs all
!Command: show running-config cfs all
!Time: Mon Sep 9 11:51:45 2013
version 5.2(1)N1(4)
cfs distribute
cfs ipv4 mcast-address 239.255.70.83 <- Does this need to be change ? to mgmt subnet ?
cfs ipv6 mcast-address ff15::efff:4653
cfs ipv4 distribute
no cfs ipv6 distribute
Nexus 01
nexus-sw01# sh switch-profile status
switch-profile : dc2-sp
----------------------------------------------------------
Start-time: 128715 usecs after Mon Sep 9 10:32:04 2013
End-time: 132331 usecs after Mon Sep 9 10:32:04 2013
Profile-Revision: 1
Session-type: Verify
Session-subtype: -
Peer-triggered: No
Profile-status: Sync Success
Local information:
----------------
Status: Verify Success
Error(s):
Peer information:
----------------
IP-address: 172.18.10.4
Sync-status: Not yet merged
Merge Flags: pending_merge:1 rcv_merge:0 pending_validate:0
Status: Peer not reachable
Error(s):
Message was edited by: Syed Umair Ali
09-09-2013 05:42 AM
In nexus 5K switch profile configuration is synced only through Mgmt 0 interface. Make sure you configure the Mgmt interface on both switches and their reachability. Configure the Mgmt 0 ip address for vpc domain peer and switch-profile sync peer and everything should work ok.
09-09-2013 06:38 AM
Hi Venkata
I can ping the remote Mgmt IPs using ping nexus_ip vrp management. vPC is working fine but it is switch-profile which seems to have a problem. Could you expand a bit on this
"
Configure the Mgmt 0 ip address for vpc domain peer and switch-profile sync peer and everything should work ok.
10-31-2013 09:48 AM
Got it solved, actually cfs was culprit . See the solution here
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