We recently had a pair of Nexus 5k switches setup in our network. We had professional services handle the initial configuration but they weren't able to setup config sync for us. Each Fex is connected to each 5k, so we need a switch-profile to maintain a consistent setup on our interfaces. I went through the process in Configuring Switch-Profiles, but when I check the status of the peer, it says not reachable:
5k1# sh switch-profile sw-config peer
switch-profile : sw-config
----------------------------------------------------------
Peer-IP-address : 172.31.255.242
Peer-sync-status : Not yet merged
Merge Flags: pending_merge:1 rcv_merge:0 pending_validate:0
Peer-status : Peer not reachable
Peer-error(s) :
I confirmed I could ping between the two mgmt0 interfaces:
5k1# ping 172.31.255.242 vrf management
PING 172.31.255.242 (172.31.255.242): 56 data bytes
64 bytes from 172.31.255.242: icmp_seq=0 ttl=254 time=0.86 ms
64 bytes from 172.31.255.242: icmp_seq=1 ttl=254 time=0.644 ms
64 bytes from 172.31.255.242: icmp_seq=2 ttl=254 time=0.719 ms
64 bytes from 172.31.255.242: icmp_seq=3 ttl=254 time=0.716 ms
64 bytes from 172.31.255.242: icmp_seq=4 ttl=254 time=0.745 ms
I'm not sure where else to look. There didn't seem to be much information on troubleshooting a peer not reachable status. Here are some relevant settings.
5k1:
cfs ipv4 mcast-address 239.192.16.252
cfs ipv4 distribute
cfs eth distribute
vrf context management
interface mgmt0
description vPC Peer-KeepAlive
vrf member management
ip address 172.31.255.241/29
switch-profile sw-config
sync-peers destination 172.31.255.242
5k2:
cfs ipv4 mcast-address 239.192.16.252
cfs ipv4 distribute
cfs eth distribute
vrf context management
interface mgmt0
description vPC Peer-KeepAlive
vrf member management
ip address 172.31.255.242/29
switch-profile sw-config (manually created)
