How to Change Network File Copy Debugging Level
Hi Friends,
From my personal experiences at the support level I have seen that having the Debugging level to a great extent will always pay us back. So at any time changing the debugging level to the highest will give us a clear picture of what exactly is going on.
So here we go. We know the NFC (Network File Copy) is a new baby in Vmware Virtual Infrastructure world. This has a great potential too at the same time. So this also has a debugging level set from the VPXA and VPXD stand point.
So we need to increase the logging level to the max it is available to get to know what is under table.
Complete the following steps to setup network file copy (nfc) debugging:
Setup verbose logging at the host (/etc/opt/vmware/vpxa/vpxa.cfg):
Add the following to the vpxa.cfg file:
"nfc"
"loglevel" debug <==change loglevel to "debug"; it's "error" by default "/loglevel"
Restart vpxa with the following:
# service vmware-vpxa restart
Setup verbose logging at the VC Server:
To do this, edit the vpxd.cfg file located at %ALLUSERSPROFILE%\Application Data\VMware\VMware VirtualCenter\vpxd.cfg
WARNING: Make a backup copy of the file before editing.
Edit the file with Notepad or any text editor.
Add the following to vpxd.cfg between the "config"
...
"nfc"
"loglevel"debug"/loglevel"
"/nfc"
"log"
"level"trivia"/level"
"maxfilenum"30"/maxfilenum"
"/log"
...
"/config"
This will setup nfc debug, change the loglevel to trivia and retain 30 Files instead of the default 10. The trace will log SQL statements and connections to help diagnose the issue. The log level must be set to verbose or trivia for this to work.
This cannot all be done in the VI client GUI , so it will have to be done as shown previously.
NOTE: These should be removed when finished (copy the saved file back over them) , to avoid confusion with the GUI setup.
After making the changes restart the VC service (VC server reads vpxd.cfg on startup, so it needs to be restarted).
Currently have 0 comments: