Loading...
Loading...
On Nexus 9000 Series Switches, if the vPC peer-keepalive statement is initially mis-configured, subsequent attempts to correct it may not be accepted and the keepalive will not function. Once in this state 'copy run start' also fails. The following errors can be seen: %VPC-2-PEER_KEEP_ALIVE_RECV_FAIL: In domain 1, VPC peer keep-alive receive has failed %VPC-2-PEER_KEEP_ALIVE_SEND_FAIL: In domain 1, VPC peer keep-alive send has failed N9K# copy run start [########################################] 100% Configuration update aborted: request was aborted N9K#show logging log %SYSMGR-2-CFGWRITE_ABORTED_CONFELEMENT_RETRIES: Copy R S failed as config-failure retries are ongoing. Type "show nxapi retries" for checking the ongoing retries. %SYSMGR-3-CFGWRITE_SRVFAILED: Service "confelem" failed to store its configuration (error-id 0x00000079). %SYSMGR-2-CFGWRITE_ABORTED: Configuration copy aborted. %SYSMGR-3-CFGWRITE_FAILED: Configuration copy failed (error-id 0x401E0000).
Using non-default VRF and non-mgmt0 keepalive. Keepalive was configured with destination IP only and did not include VRF and source IP.
'no feature vpc' >> 'feature vpc' >> re-configure correctly
If using a non-default VRF specify the VRF and source IP in the keepalive statement. This will be fixed in 7.0(3)I7(1) and later.
Click on a version to see all relevant bugs
Cisco Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.