01-23-2017 05:30 AM - edited 03-08-2019 09:01 AM
Hi all,
Today I have tried to configure "conf-sync" between two nexus 5k without success.
in detail the Database now is locked on one Nexus and I can't change anything (nothing remove the switch-profile).
The version of OS is 7.2(0)N1 on both devices.
I already tried to reboot the device.
interface mgmt0
description "Link To Ber - ge4/0/46"
vrf member management
ip address 172.18.3.243/24
switch-profile : vPC
----------------------------------------------------------
Start-time: 702258 usecs after Mon Jan 23 14:21:29 2017
End-time: -
Profile-Revision: 1
Session-type: -
Session-subtype: -
Peer-triggered: No
Profile-status: -
Local information:
----------------
Status: -
Error(s):
Peer information:
----------------
IP-address: 172.18.3.242 --> mgmt0 of the other Nexus.
Sync-status: Not yet merged
Merge Flags: pending_merge:1 rcv_merge:0 pending_validate:0
Status: -
Error(s):
show system internal csm global info
No of sessions: 1 (Max: 32)
Total number of commands: 0 (Max: 102400)
Session Database Lock Info: locked
Client: 1 (1: SSN, 2: CONF-T)
ID: 1
Name: vPC (switch-profile session)
test csm ssn-db-lock reset SSN
ERROR: Failed to reset Session DB lock(can't reset lock taken by SSN)
01-23-2017 05:55 AM
Hi
thats strange a reboot should have cleared it , even though you don't really want to be rebooting dc switches unless you have too
did you try first............. test csm ssn-db-lock reset conf-t
01-23-2017 05:59 AM
Thanks for reply, but unfortunately this command not worked because the DB is locked in type 1 not type 2
test csm ssn-db-lock reset conf-t
ERROR: Lock type mismatch !!. Session DB currently owned byclient type 1
do you have other ideas?
01-23-2017 07:03 AM
Hi
have you seen this link there's another method , if that doesn't work personally I would TAC it
http://www.cisco.com/c/en/us/support/docs/switches/nexus-5000-series-switches/119028-troubleshoot-cfs-nx5k-00.html
01-23-2017 07:17 AM
already tried this document without success.
Unfortunately the CFS application lock is the session-mgr and is not clearable with the command "clear <application> session" and it is not visualize under internal processes.
Thanks for your support
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