Dell PowerVault MD3000 - Manual (Page 48)

Dell MD Storage Array vCenter Plug-in | 48
6
Troubleshooting vCenter Plug-in Issues
This section describes how to open and read vCenter Plug-in log file, provides answers to some frequently
asked questions, and describes and, describes how to resolve some common problems you might encounter
with the vCenter Plug-in.
Application Server Logs
All procedures that are performed from the vCenter Plug-In are logged in to the following log file on the
application server:
C:\Program Files\Dell MD Storage Array vCenter Management
Plug-in\jetty\logs\
vCenter2-logx.y.csv
The file is archived every 24 hours and stored for 10 days, after which the file is overwritten. The file is in
CSV format. You can open the file and view it in Notepad, CVSed, or a similar viewer.
NOTE: If the file is locked, you can create a copy of the file with a different name, open the copied file,
and it view it.
Figure 46. vCenter Plug-in Log view
Additional log files that are useful for technical support to resolve issues are also maintained in this directory,
but these files are generally not in a user-friendly format.
 vCenter2debug-x.log.y -- Debug log used by technical support
 jetty-service.log -- Jetty service log, used by technical support
 <date/time stamp>.request.log -- Log of IP addresses for all Jetty service requests from
clients
The Installation Log Not Show that the Pegasus Service Started
Verify that the cimserver service was started from services.msc window.
NOTE: In the event one of these services crash or is stopped, the CIMOM service must be started before the Jetty service or
no updates/modifications will occur.
I Cannot Communicate with the Application Server
1
Check the firewall settings to verify that the Jetty TCP port is enabled. If the Jetty TCP port is not
enabled, enable it.