The TKInfo Tool is a script that creates four reports for monitorng information about keys. The first is a list of which keys are present on (or missing from) which servers. The second is a list of which keys are synchronized consistently (all revoked, all valid, some missing or a mix of these combinations). The third report is a list of valid keys throughout the tree. The final report tells the total number of keys and servers in the environment and the number of servers either turned off or with NICI
The first report tells if a server is missing a tree key. If so, then passwords encrypted with that key cannot be decrypted on that server. Also, if a password is encrypted on that server it may not be encrypted with a key that other servers (with the key that server is missing) can decrypt. Tree key synchronization is important for passwords to be usable on all servers.
The second report tells which keys are synchronized consistently. While all servers may hold any number of keys, if they are not the same then passwords will not encrypt and decrypt consistently. If a server does not have NICI, or NICI is broken, then passwords will not be able to be encrypted or decrypted on that box.
The third report lists tree keys that are valid and synchronized, or less than valid and synchronized. Having a 168-bit tree key in the Valid Keys section is the best. Having other tree keys will not hurt but it is best to have only one key on each server that is valid and to have that one key synchronized to all other servers as valid. This way the passwords are encrypted with the same key and decrypted with that same key. Having extra revoked keys all over does not cause problems at all.
The final report simply gives you a summary of the number of servers and keys. If the number of servers does not match one's internal number of servers then that is something to look into. The script can only tell what is reported from NICI, so if a server is not showing up anywhere for the keys then this script will not report on it at all. This is a fairly rare situation but one you can easily resolve with some basic troubleshooting assisted by Novell's TIDs and online forums.
Disclaimer: As with everything else at Cool Solutions, this content is definitely not supported by Novell (so don't even think of calling Support if you try something and it blows up).
It was contributed by a community member and is published "as is." It seems to have worked for at least one person, and might work for you. But please be sure to test, test, test before you do anything drastic with it.