Thanks for pointing this out. I didn't notice it before.
Before I ran the dateconfig command as you suggested, I ran viewsysinfo again to see what the disparity was between the hypervisor and the guest. It was a lot closer than yesterday.
cmc::cmm# viewsysinfo
Collecting general system information......... done.
CMC version: 4737
The time is: 2014/03/19 16:26:48
Machine uptime is: 1 day, 17 min
Linux version is: 3.2.0-3-amd64
Machine architecture is: 64-bit
Physical Memory info:
MemTotal: 16474176 kB
MemFree: 2650488 kB
Number of CPUs: 4
CPU model: Intel(R) Xeon(R) CPU E5-2420 0 @ 1.90GHz
Memory Overcommit is default.
---------------------------------
TriGeo manager version is: 5.7.0
TriGeo manager build is: release
TriGeo upgrade build is: 520398
Product Support Key: R3WME-BSRB6-92AA-YLNG-DBPRN-X7A2R
License Type: Commercial
Total Number of Node Licenses: 50
Available Licenses: 40
Manager heap configuration: Initial heap size is 5300M and maximum heap size is 5300M
Max # of alerts in memory: 600000
Flow configured: false
Virtualization Platform: VMware
------------------------------------------
Clock
Synchronization : Enabled
Hypervisor Time : 19 Mar 2014 16:26:27
Guest Time : Wed Mar 19 16:26:49 2014
CPU
Speed : 1900 MHz
Reservation : 2000 MHz
Limit : Unlimited
Memory
Reservation : 16384 MB
Limit : Unlimited
Swapped : 0 MB
Ballooned : 0 MB
After running the command from the appliance prompt, I received the following output.
cmc::acm# dateconfig
Press <enter> to update your manager's current date and time
Enter the current date in month/day/year format. (MM/DD/YYYY)>
Enter the current time in hour:minute format. (hh:mm)>
setting date to ...
Wed Mar 19 16:28:51 CDT 2014
The problem is this is almost 10 minutes behind the time that my NTP server is showing. I am going to check my VMware configuration for ntp settings to make sure they are working correctly.