08-15-2013 09:06 AM
Hi,
is it possible to use a Vlan interface (SVI) for syncing the switch profile on two 5596?
I tried this:
2 x 5596UP with NX-OS 5.2(1)N1(3)
Connected with 2 x Twinax on ports Eth1/15 and /16, portchannel 3.
The Po3 is a trunk, allowed Vlan is 439. Both 5596 have a SVI in Vlan439 with an IP. I can ping between the two 5596.
# ping 10.9.8.4
PING 10.9.8.4 (10.9.8.4): 56 data bytes
64 bytes from 10.9.8.4: icmp_seq=0 ttl=254 time=0.887 ms
When I try to to this:
switch-profile k
sync-peers destination 10.9.8.4
I get:
# sh switch-profile status
switch-profile : k
----------------------------------------------------------
Start-time: 831222 usecs after Thu Aug 15 17:57:53 2013
End-time: 834086 usecs after Thu Aug 15 17:57:53 2013
Profile-Revision: 7
Session-type: Initial-Exchange
Session-subtype: Init-Exchange-All
Peer-triggered: No
Profile-status: -
Local information:
----------------
Status: -
Error(s):
Peer information:
----------------
IP-address: 10.9.8.4
Sync-status: Not yet merged
Merge Flags: pending_merge:1 rcv_merge:0 pending_validate:0
Status: Peer not reachable
Error(s):
As soon as I change the sync-peers destinations to use the IPs on the mgmt0 interface everything works fine:
# sh switch-profile status
switch-profile : k
----------------------------------------------------------
Start-time: 723075 usecs after Thu Aug 15 18:04:23 2013
End-time: 475957 usecs after Thu Aug 15 18:04:25 2013
Profile-Revision: 7
Session-type: Commit
Session-subtype: -
Peer-triggered: No
Profile-status: Sync Success
Local information:
----------------
Status: Commit Success
Error(s):
Peer information:
----------------
IP-address: 10.0.0.4
Sync-status: In sync
Status: Commit Success
Error(s):
08-30-2013 10:18 AM
Yeah I've always used the IP of the peer keepalive link. I think it might have something to do with CFS only working on ethernet and not SVIs.