UCS C22 M3 NTP Offset?

I'm having issues with the NTP setting on the C22s we purchased. I can configure NTP just fine through the CIMC but it defaults to UTC and I need to set the offset to -8 for PST so that the system Clock is accurate.
The documentation I've been able to find says to ssh into the CIMC type scope system then scope service then set the offset but the scope system command doesn't work. Neither does the GUI instructions that I've found which say that the offset is in the Admin tab of the CIMC.
Anyone have any insight as to how I can set the NTP offset? For now I've disabled NTP as having it off by 8 hours will play havoc with my VM's on boot.
Thanks!

Hello,
I'm running into the same issue (UCS C-220M3, Cisco Business Edition 6000). After my research I am afraid NTP Offset is not supported at all when the server is managed directly via CIMC (rather than UCS Manager).
The Menus/Commands the OP mentioned are from UCS Manager.
Cheers
David

Similar Messages

Unable to enable HBA Card in the Cisco UCS c22 m3 server

Hi All,
I need your help desperately to setup the cisco ucs c22 m3 server in our environment. We have a C22 M3 server and I did the basic config of CIMC and we have a LSI megaraid controller connected to one of the PCIe and the other PCIe has a dual port 8gb HBA card. We installed the RAID and we can see the LSI Megaraid controller. But I cannot see the HBA card and there is noo light near the card. I hope I need to enable something so that the card should work. I tried enabling in the BIOS menu I can see the PCIe slot is enabled but I am unable to see the HBA functioning. Couldyou pleasehelp me to resolve this.

Dear Manuel,
Thanks for replying me. See the answers for your queries.
What kind of HBA card are you trying to use?
If I am not wrong we are using "Qlogic QLE2562, 8Gb dual port Fibre Channel HBA".
How many CPUs do you have installed on your server?
I opened the box and saw only 1 CPU installed. But the solution is given by CISCO pre sales. We have 2 PCIe slots configured. One for LSI RAID controller and the other with dual port Fibre Channel HBA.
Awaiting your reply.
Thanks and Regards,
Jaffer Ali

Configure Windows on UCs c22 M3 drives are not showing

hello all
i am configuring windows server 2008r2 on UCS c22 m3 , i have configured raid1 (default) virtual drive , drive is showing in BOOT order but when i install windows and it prompts to selct hard drive, there no drive are showing , do i need to install any driver for it? if yes then which version of driver i download, my CIMP version is 1.5(1k) kindly suggest me and help me in solving this issue.

You will have to install the drivers for the RAID card that you are using. You will have to unmount the windows ISO and mount the driver ISO to install the drivers. Then you will have to mount the windows ISO back
The driver package can be downloaded from the link below
http://software.cisco.com/download/release.html?mdfid=284444317&catid=282558030&softwareid=283853158&release=1.5(1d)&relind=AVAILABLE&rellifecycle=&reltype=latest
Thanks,
Karthic

UCS c22 M3s + LSI MegaRaid 9265 not recognized

   1.
We have this server c22 m3s
I have installed the raid card and the battery.
Altough, When I boot, I do not see any LSI prompt.
CIMC does not see anything in the storage controller section. And Yes, I did install the lastest upgrades.
What do I need to do in order to be able to use the card?
It's a Brand new server. Blank.
And no prompt for CTRL+H.
2.
What is the use of the GPIO connector from the sas cable?
Am i obligated to plug it ?

Danik,
This servers have a embedded RAID controlleri on the motherboard as well (embedded SATA-only RAID controller that supports up to four SATA-only drives <<< Does not support Virtualization OSs, like VMware) so if you bought a PCIe RAID card, you have 2 RAID controllers.
How many CPUs do you have? and where is this RAID controller installed? Controllers are installed by default in slot 1 for 1-CPU systems and slot 2 for 2-CPU systems, meaning that if there is only one CPU and the card is in slot 2, it will NOT be recognized/work, unless you change the OPROM (Option ROM) to enable another slot
See this (Table 28) for the supported installation and that shows that the embedded controller is initiallyh enabled, very likely the reason why you do not see the "Ctrl-H" option:
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10493/c22m3_sff_specsheet.pdf
And here is the option to change the OPROM and enable a different PCIe slot when having 2 CPUs in the system:
http://www.cisco.com/en/US/prod/collateral/ps10265/ps10493/c22m3_sff_specsheet.pdf   <<< Check the caveats for changing the OPROM cause you might lose the option to have a VIC card for example.
A step of last resort will be to disable any OPROM not needed (for some customer that means to disable all Option ROMs)
I hope it helps, and let us know if there is any other doubts or if this did not help, but I hoipe it does
-Kenny

NTP on UCS Mngr.

Hello,
I see a clock drift between the NTP server and the UCS manager (when NTP is properly configured ). How can I set off this drift and how can I ensure that such an instance doesn't happen again ?
REgards,
Naleendra

on your swith or rtr, be sure they have NTP setup
then type
sh ntp ass
be sure to point to either a local GPs time source, ceisiem/SP soucre or a suitable stratum 1 source on the internet
once first setup, it will take a few hours to synchronize, after that they will drift very little
afte they are synb, check the later command to ensure that yu are in deed in sync with a proper time source.
most people have all their end points to point the AD serves. these in turn pint to the reference. time source
time reference use this pyramid strcuture for stability and reduction in latency

Is Cisco Prime Infrastructure 1.2 or 2.0 compatible on UCS ?

hello, can we install Cisco Prime Infrastructure 1.2 or 2.0 on UCS C22, C220M3 or NCS Hardware Appliance without using VMware ?
thanks.

Hi,
Unfortunately, this isn't yet supported for Prime Infrastructure.
you have Installed VMWare first.
Thanks-
Afroz
[Do rate the useful post]

SAS/SATA cable

Hi
I've recently bought a Cisco UCS C22 Server M3 SFF and by wrong the order has issued as spare part not normal part, so we have received all the order as separate items not consolidated in the server as normal.
The problem now, that I have raid controller "UCSC-RAID-9240-8I" and it should be connected to two hard drives and unfortunately the SAS cable "UCSC-CABLE-A5=" is not found and I’ve to order it and it will takes time.
My question is If I find this cable "UCSC-CABLE-A1=" on stock at someone, does it work with my Raid and the two hard drives?
By the way, I have one processor only "UCS-CPU-E52407B"
Thanks

Hi
In the pass this cable (UCSC-CABLE-A1) was supported by this server and this controller (single-cpu),
http://www.manualslib.com/manual/701730/Cisco-Ucs-C22.html?page=90#manual
but this cable has reached end of sale.
http://www.cisco.com/c/en/us/products/collateral/servers-unified-computing/ucs-c-series-rack-servers/eos-eol-notice-c51-733772.pdf
Currently the the only supported cable by this combination of server and controller is UCSC-CABLE-A5
http://www.cisco.com/c/en/us/td/docs/unified_computing/ucs/c/hw/C22/install/C22/raid.html#pgfId-1015625
In theory, this cable should recognize the hard disk and work with your controller.

NTP error in RTMT of CUCM 8.6(2a) VM

Hello
We have migrated and upgraded an existing CUCM to 8.6(2a) on UCS using ESXi 4.1.
Everything seems to be fine exept that we are getting Syslogs in RTMT that are stating that there is something wrong with NTP (see Syslog message below).
At Sun Oct 16 13:40:30 CEST 2011 on node 10.0.128.24; the following SyslogSeverityMatchFound events generated: SeverityMatch : Critical MatchedEvent : Oct 16 13:40:04 NOS-CH-WBN-CM01 user 2 ntpRunningStatus.sh: The local NTP client is off by more than the acceptable threshold of 3 seconds from its remote NTP system peer. The normal remedy is for NTP Watch Dog to automatically restart NTP. However; an unusual number of automatic NTP restarts have already occurred on this node. No additional automatic NTP restarts will be done until NTP time synchronization stabilizes. This is likely due to an excessive number of VMware Virtual Machine migrations or Storage VMotions. Please consult your VMware Infrastructure Support Team. AppID : Cisco Syslog Agent ClusterID : NodeID : NOS-CH-WBN-CM01 TimeStamp : Sun Oct 16 13:40:04 CEST 2011
However when we check the NTP status on the CUCM itself, there doesn't seems to be anything wrong (see CLI output below).
admin:utils ntp status
ntpd (pid 23400) is running...
     remote           refid      st t when poll reach   delay   offset jitter
==============================================================================
*172.16.2.241    192.53.103.108   2 u   49 128 377    0.755    3.376   0.771
172.16.1.241    172.16.2.241     3 u   71 128 377    7.399    2.603   1.052
synchronised to NTP server (172.16.2.241) at stratum 3
   time correct to within 35 ms
   polling server every 128 s
Current time in UTC is : Sun Oct 16 11:42:59 UTC 2011
Current time in Europe/Zurich is : Sun Oct 16 13:42:59 CEST 2011
admin:
Regarding the Syslog message, we haven't done any WM migrations and the storage is on the local disks of the UCS C200. So ther has not been any storage VMotions at all.
The guest is not synchronising the time with the ESXi host (unchecked in the VMware tools settings on the guest)
Has anyone faced a similar problem?
Does anyone know if the problem is caused by VMware or CUCM 8.6(2a)?
Any help and input is appreciated.
Many thanks in advance
Regards
Stefan Christen

Hello,
Could you copy 2 or 3 lines around this message ? It should specify to which remote peer talks about.
For ex I have the same issue on a CUCM 8.5.1 on UCS (ESX 4.0) when being testing 2 NTP relays, one in a Windows machine and another in a router.
I have the same message error for the ntp peer corresponding to the windows machine ("normal") and does not synchronize but I do not have any error message for the peer corresponding to the router.
Oct 27 06:13:06, HQ17-CUCM1, Warning, ntpRunningStatus.sh, : The local NTP client is off by more than the acceptable threshold of 3 seconds from NTP server 10.110.114.11. Restarting NTP ..., 71
                          ^^^^^^^^^^^^^
Oct 27 06:13:06, HQ17-CUCM1, Critical, ntpRunningStatus.sh, : The local NTP client is off by more than the acceptable threshold of 3 seconds from its remote NTP system peer. The normal remedy is for NTP Watch Dog to automatically restart NTP. However, an unusual number of automatic NTP restarts have already occurred on this node. No additional automatic NTP restarts will be done until NTP time synchronization stabilizes. This is likely due to an excessive number of VMware Virtual Machine migrations or Storage VMotions. Please consult your VMware Infrastructure Support Team., 72
In your case, verify if this message does not refer to 172.16.1.241, in which case does not seem an issue because your CUCM is in synch and prefers 172.16.2.241.
If that is the case, remove 172.16.1.241 as NTP server and check the logs.
You need perhaps another backup NTP server but it does not look to me very useful to point as backup NTP to a relay which is based on your primary NTP relay.
Let me know,
Brgrds
Jordi

Oracle VM Server 2.2 Linux Guest cannot ntp to server properly

Hi All,
I have installed a VM guest Oracle Linux Enterprise 5U6 in Oracle VM server 2.2. I follow below procedure to config NTP in VM server.
https://blogs.oracle.com/virtualization/entry/configuring_ntp_services_for_oracle
However, when I apply the NTP configuration with VM server itself on the Guest, it detects the NTP server in high jitter value. Even though the stratrum is lower than the local host, It still cannot use that server as NTP source. Here is some information about the NTP debug and IP address.
IP Address:
Oracle VM Server: 172.16.8.100
VM Guest: 172.16.8.102
Debug on VM Guest:
# ntpdate -d 172.16.8.100
26 Mar 13:54:18 ntpdate[697]: ntpdate [email protected] Tue Dec 8 20:30:45 UTC 2009 (1)
Looking for host 172.16.8.100 and service ntp
host found : 172.16.8.100
transmit(172.16.8.100)
receive(172.16.8.100)
transmit(172.16.8.100)
receive(172.16.8.100)
transmit(172.16.8.100)
receive(172.16.8.100)
transmit(172.16.8.100)
receive(172.16.8.100)
transmit(172.16.8.100)
server 172.16.8.100, port 123
stratum 3, precision -20, leap 00, trust 000
refid [172.16.8.100], delay 0.02585, dispersion 0.00037
transmitted 4, in filter 4
reference time: d31a8fd0.c06d7d27 Mon, Mar 26 2012 13:48:48.751
originate timestamp: d31a9168.774cbbe0 Mon, Mar 26 2012 13:55:36.466
transmit timestamp: d31a911b.138bdec5 Mon, Mar 26 2012 13:54:19.076
filter delay: 0.02725 0.02614 0.02585 0.02626
0.00000 0.00000 0.00000 0.00000
filter offset: 77.38879 77.38864 77.38926 77.38931
0.000000 0.000000 0.000000 0.000000
delay 0.02585, dispersion 0.00037
offset 77.389261
26 Mar 13:54:19 ntpdate[697]: step time server 172.16.8.100 offset 77.389261 sec
High jitter to the server but actualyl they are on the single box
# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
172.16.8.100 172.16.90.1 3 u 47 64 3 0.265 2704.42 2488.59
LOCAL(0) .LOCL. 10 l 44 64 3 0.000 0.000 0.004
Thanks.
Rgds,
Jacky

Hi Avi,
Thanks for your reply. Due to we do not have Oracle VM Manager, I did configure the VM guest to point the internal NTP server (172.16.90.1) which is mapped by Oracle VM server, but the high jitter is still existed while the guest can ntpq the NTP server. Thanks.
Oracle VM Server
#ntpstat
synchronised to NTP server (172.16.90.1) at stratum 3
time correct to within 56 ms
polling server every 1024 s
#ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
*172.16.90.1 10.1.22.230 2 u 551 1024 377 0.355 0.292 0.065
172.16.190.1 .INIT. 16 u - 1024 0 0.000 0.000 0.000
LOCAL(0) .LOCL. 10 l 46 64 377 0.000 0.000 0.001
VM Guest Oracle Linux
# ntpq -p
remote refid st t when poll reach delay offset jitter
==============================================================================
172.16.90.1 10.1.22.230 2 u 61 64 3 0.432 252.261 3169.53
172.16.190.1 .INIT. 16 u - 64 0 0.000 0.000 0.000
LOCAL(0) .LOCL. 10 l 34 64 7 0.000 0.000 0.008
# ntpstat
synchronised to local net at stratum 11
time correct to within 448 ms
polling server every 64 s
# ntpdate -d 172.16.90.1
26 Mar 15:47:15 ntpdate[27478]: ntpdate [email protected] Tue Dec 8 20:30:45 UTC 2009 (1)
Looking for host 172.16.90.1 and service ntp
host found : 172.16.90.1
transmit(172.16.90.1)
receive(172.16.90.1)
transmit(172.16.90.1)
receive(172.16.90.1)
transmit(172.16.90.1)
receive(172.16.90.1)
transmit(172.16.90.1)
receive(172.16.90.1)
transmit(172.16.90.1)
server 172.16.90.1, port 123
stratum 2, precision -20, leap 00, trust 000
refid [172.16.90.1], delay 0.02594, dispersion 0.00052
transmitted 4, in filter 4
reference time: d31aa515.a637fc1e Mon, Mar 26 2012 15:19:33.649
originate timestamp: d31aabaf.06173915 Mon, Mar 26 2012 15:47:43.023
transmit timestamp: d31aaba2.61117b52 Mon, Mar 26 2012 15:47:30.379
filter delay: 0.02631 0.02605 0.02594 0.02594
0.00000 0.00000 0.00000 0.00000
filter offset: 12.64269 12.64337 12.64397 12.64443
0.000000 0.000000 0.000000 0.000000
delay 0.02594, dispersion 0.00052
offset 12.643971
26 Mar 15:47:30 ntpdate[27478]: step time server 172.16.90.1 offset 12.643971 sec
Rgds,
Jacky

Windows 2008 R2 Domain Controller (PDC) - NTP server - time showing local CMOS clock

I'm having issues setting an external source on a Windows 2008 R2 domain controller (PDC emulator role for the domain)
Here is the output showing its source is the Local CMOS clock.
C:\Windows\System32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 06/11/2014 15:44:15
Source: Local CMOS Clock
Poll Interval: 6 (64s)
1) I have performed the following on the DC with the PDC role:
net stop w32time
w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org"
w32tm /config /reliable:yes
net start w32time
w32tm /query /configuration
[Configuration]
EventLogFlags: 2 (Local)
AnnounceFlags: 5 (Local)
TimeJumpAuditOffset: 28800 (Local)
MinPollInterval: 6 (Local)
MaxPollInterval: 10 (Local)
MaxNegPhaseCorrection: 172800 (Local)
MaxPosPhaseCorrection: 172800 (Local)
MaxAllowedPhaseOffset: 300 (Local)
FrequencyCorrectRate: 4 (Local)
PollAdjustFactor: 5 (Local)
LargePhaseOffset: 50000000 (Local)
SpikeWatchPeriod: 900 (Local)
LocalClockDispersion: 10 (Local)
HoldPeriod: 5 (Local)
PhaseCorrectRate: 7 (Local)
UpdateInterval: 100 (Local)
[TimeProviders]
NtpClient (Local)
DllName: C:\Windows\System32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
AllowNonstandardModeCombinations: 1 (Local)
ResolvePeerBackoffMinutes: 15 (Local)
ResolvePeerBackoffMaxTimes: 7 (Local)
CompatibilityFlags: 2147483648 (Local)
EventLogFlags: 1 (Local)
LargeSampleSkew: 3 (Local)
SpecialPollInterval: 3600 (Local)
Type: NTP (Local)
NtpServer: 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org (Local)
NtpServer (Local)
DllName: C:\Windows\System32\w32time.DLL (Local)
Enabled: 1 (Local)
InputProvider: 0 (Local)
AllowNonstandardModeCombinations: 1 (Local)
VMICTimeProvider (Local)
DllName: C:\Windows\System32\vmictimeprovider.dll (Local)
Enabled: 1 (Local)
InputProvider: 1 (Local)
But still showing the output:
C:\Windows\System32>w32tm /query /status
Leap Indicator: 0(no warning)
Stratum: 1 (primary reference - syncd by radio clock)
Precision: -6 (15.625ms per tick)
Root Delay: 0.0000000s
Root Dispersion: 10.0000000s
ReferenceId: 0x4C4F434C (source name: "LOCL")
Last Successful Sync Time: 06/11/2014 15:58:45
Source: Local CMOS Clock
Poll Interval: 6 (64s)
2. If I resync and rediscover the following error appears:
w32tm /resync /rediscover
Sending resync command to local computer
The computer did not resync because no time data was available.
3. I've also clearing the current time config, by
net stop w32time
w32tm /unregister
w32tm /register
net start w32time
But no change, it still shows the Local CMOS clock.
4. This event is showing
Log Name: System
Source: Microsoft-Windows-Time-Service
Date: 06/11/2014 15:43:30
Event ID: 12
Task Category: None
Level: Warning
Keywords:
User: LOCAL SERVICE
Computer: domaincontroller1
Description:
Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in the domain hierarchy to use as a time source.
It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the authoritative time source in the domain hierarchy.
If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Time-Service" Guid="{06EDCFEB-0FD0-4E53-ACCA-A6F8BBF81BCB}" />
<EventID>12</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-11-06T15:43:30.465619200Z" />
<EventRecordID>77295</EventRecordID>
<Correlation />
<Execution ProcessID="256" ThreadID="2056" />
<Channel>System</Channel>
<Computer>domaincontroller1</Computer>
<Security UserID="SID" />
</System>
<EventData Name="TMP_EVENT_DOMAIN_HIERARCHY_ROOT">
</EventData>
</Event>
5. If I perform the below it appears DC2 is having problems but I'm not sure if related.
C:\w32tm /monitor
DC1.domain.local *** PDC ***[192.168.1.1:123]:
ICMP: 0ms delay
NTP: +0.0000000s offset from DC1.domain.local
RefID: 'LOCL' [0x4C434F4C]
Stratum: 1
DC2.domain.local[192.168.1.2:123]:
ICMP: 0ms delay
NTP: -110.4925481s offset from DC1.domain.local
RefID: (unspecified / unsynchronized) [0x00000000]
Stratum: 0
DC3.domain.local[192.168.2.1:123]:
ICMP: 0ms delay
NTP: -0.0256084s offset from DC1.domain.local
RefID: DC1.domain.local [192.168.1.1]
Stratum: 2
DC4.domain.local[192.168.2.4:123]:
ICMP: 0ms delay
NTP: -0.0011524s offset from DC1.domain.local
RefID: 80.84.77.86.rev.sfr.net [86.77.84.80]
Stratum: 2
Warning:
Reverse name resolution is best effort. It may not be
correct since RefID field in time packets differs across
NTP implementations and may not be using IP addresses.
Any help would be much appreciated. Thanks.
Craig Brand

I suspected some issue with AV so uninstalled.
To resolve the Access Denied I followed these steps:
stop w32time
w32tm /unregister
reboot
regsvr32 /u w32time.dll
w32tm /register
sc query w32time -- you should see that the service is set to
shared mode -- this is presumably how it should be -- if you try to start right now, you'll get the expected 1290 SID-related error
reboot
w32time should now automatically start at boot up and be running -- that was my result -- it's running as shared, started on its own, and I can do the w32tm /query commands successfully
After rebooting the time service started.
I then repeated the steps:
net stop w32time
w32tm /config /syncfromflags:manual /manualpeerlist:"0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org"
w32tm /config /reliable:yes
net start w32time
w32tm /query /configuration
And all worked. I'll wait a short while to see if this fixes the issue. I also have am SA case with MS so will confirm fix when resolved.
Craig Brand

NTP client in Windows 7 Professional Does Not Sync

I have an NTP server running on an Ubuntu Linux box. All of my other linux boxes are able to synchronize to this NTP server. My Windows 7 Professional box is not even after trying multiple steps suggested in these forums.
The NTP server is on the local network; the firewall and anti-virus do not seem to be causing issues. If I test the NTP server connection using the following line:
/stripchart /computer:192.168.2.63 /packetinfo
I see the following information:
Tracking 192.168.2.63 [192.168.2.63:123].
The current time is 1/28/2014 9:05:24 PM.
21:05:24 d:+00.0349180s o:-01.0741307s [ * | ]
[NTP Packet]
Leap Indicator: 0(no warning)
Version Number: 1
Mode: 4 (Server)
Stratum: 1 (primary reference - syncd by radio clock)
Poll Interval: 3 (8s)
Precision: -22 (238.419ns per tick)
Root Delay: 0x0000.0000 (unspecified)
Root Dispersion: 0x0001.DE2F (1.8679047s)
ReferenceId: 0x47505300 (source name: "GPS")
Reference Timestamp: 0xD690FAAE12CA0936 (150871 15:33:02.0733953s - 1/27/2014 10:33:02 AM)
Originate Timestamp: 0xD692E0645BE2FB0C (150873 02:05:24.3589322s - 1/28/2014 9:05:24 PM)
Receive Timestamp: 0xD692E0634D60F136 (150873 02:05:23.3022605s - 1/28/2014 9:05:23 PM)
Transmit Timestamp: 0xD692E0634D6672F1 (150873 02:05:23.3023445s - 1/28/2014 9:05:23 PM)
[non-NTP Packet]
Destination Timestamp: Roundtrip Delay: 34918000 (+00.0349180s)
Local Clock Offset: -1074130700 (-01.0741307s)
Which indicates to me that I am able to see the server and receive NTP packets.
However, if I try to configure the server manually thusly:
w32tm /config /manualpeerlist:192.168.2.63,0x1 /syncfromflags:manual /update
and perform a resync:
w32tm /resync /rediscover
I get the following error:
The computer did not resync because no time data was available.
But -- using wireshark I can see the NTP request go out and what looks like a valid NTP packet return from my server.
What other settings am I missing here? Why would an NTP packet arrive and not be recognized by w32tm?

I turned on the debug logging; I additionally see this information:
150873 02:42:22.3054052s - Reachability: Attempting to contact peer 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123).
150873 02:42:22.3054052s - PeerPollingThread: WaitTimeout
150873 02:42:22.3054052s - Polling peer 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123)
150873 02:42:22.3054052s - Sending packet to 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123) in Win2K detect mode, stage 1.
150873 02:42:22.3054052s - PeerPollingThread: waiting forever
150873 02:42:22.3054052s - PollIntervalChange(192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123)): reclamp: 17 -> 10 (min=4, max=17, sys=10)
150873 02:42:22.3054052s - Peer poll: Max:604800.0000000s (special) Cur:00.0000000s
150873 02:42:22.3054052s - PeerPollingThread: waiting 604800.000s
150873 02:42:22.3364070s - ListeningThread -- DataAvailEvent set for socket 1 (0.0.0.0:123)
150873 02:42:22.3364070s - ListeningThread -- response heard from 192.168.2.63:123 <- 192.168.3.54:123
150873 02:42:22.3364070s - /-- NTP Packet:
150873 02:42:22.3364070s - | LeapIndicator: 0 - no warning; VersionNumber: 3; Mode: 4 - Server; LiVnMode: 0x1C
150873 02:42:22.3364070s - | Stratum: 1 - primary reference (syncd by radio clock)
150873 02:42:22.3364070s - | Poll Interval: 17 - out of valid range; Precision: -22 - 238.419ns per tick
150873 02:42:22.3364070s - | RootDelay: 0x0000.0000s - unspecified; RootDispersion: 0x0001.E6B3s - 1.90117s
150873 02:42:22.3364070s - | ReferenceClockIdentifier: 0x47505300 - source name: "GPS"
150873 02:42:22.3364070s - | ReferenceTimestamp: 0xD690FAAE12CA0936 - 13035310382073395300ns - 150871 15:33:02.0733953s
150873 02:42:22.3364070s - | OriginateTimestamp: 0xD692E90E4E2F0902 - 13035436942305405200ns - 150873 02:42:22.3054052s
150873 02:42:22.3364070s - | ReceiveTimestamp: 0xD692E90D43D54D4D - 13035436941264973500ns - 150873 02:42:21.2649735s
150873 02:42:22.3364070s - | TransmitTimestamp: 0xD692E90D43DA4B0A - 13035436941265049600ns - 150873 02:42:21.2650496s
150873 02:42:22.3364070s - >-- Non-packet info:
150873 02:42:22.3364070s - | DestinationTimestamp: 150873 02:42:22.3364070s - 0xD692E90E561EC4E7150873 02:42:22.3364070s - - 13035436942336407000ns150873 02:42:22.3364070s - - 150873 02:42:22.3364070s
150873 02:42:22.3364070s - | RoundtripDelay: 30925700ns (0s)
150873 02:42:22.3364070s - | LocalClockOffset: -1055894500ns - 0:01.055894500s
150873 02:42:22.3364070s - \--
150873 02:42:22.3364070s - ListeningThread STC:76245282
150873 02:42:22.3364070s - Peer 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123) is not Win2K. Setting compat flags.
150873 02:42:22.3364070s - Packet test 6 failed (not syncd or bad interval since last sync).
150873 02:42:22.3364070s - Ignoring packet that failed tests from 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123).
150873 02:42:38.3063204s - W32TmServiceMain: timeout
150873 02:42:38.3063204s - Sample Prepared at 130354369583063204 for peer 192.168.2.63,0x1 (ntp.m|0x1|0.0.0.0:123->192.168.2.63:123)
I've done a little searching on what causes the "Packet test 6 failed" error without too many useful results ... any thoughts?

Issue on Cisco Unity Connection after performing 'utils ntp restart'

Hello everybody.
There's a client with Cisco Unity Connection 8.5.1.10000-206. After doing a 'utils ntp restart', the following message showed up:
Communication is not functioning correctly between the servers in the Cisco Unity Connection cluster. To review server status for the cluster, go to the Tools > Cluster Management page of Cisco Unity Connection Serviceability.
The client states that there was no service for 5 minutes and wants to know if performing this task shoud be disruptive or not and if there is any official document from Cisco stating this.
See SrvConnUnity_1.jpg sent by the client after performing the ntp restart.
Right now the service is normal (see SrvConnUnity_2.jpg attached). The client also sent a 'utils ntp
status':
admin:utils ntp status
ntpd (pid 10899) is running...
     remote           refid      st t when poll reach   delay   offset jitter
==============================================================================
*127.127.1.0     LOCAL(0)        10 l   16   64 377    0.000    0.000   0.002
synchronised to local net at stratum 11
   time correct to within 12 ms
   polling server every 64 s
Current time in UTC is : Fri Apr 26 16:01:23 UTC 2013
Current time in America/Argentina/Buenos_Aires is : Fri Apr 26 13:01:23 ART 2013
admin:
Could anybody help me with this? What steps should I take? Many thanks in advance.
Best,
Patricio

Hello Patricio,
On the command line guide you won't see any downtime requirements for the Unity Connection server:
Command Line Interface Reference Guide for Cisco Unified Communications Solutions Release 8.5(1)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/cli_ref/8_5_1/cli_ref_851.html
Utils ntp restart
This command restarts the NTP service.
Command syntax
utils ntp restart
Parameters
None
Requirements
Command privilege level: 0
Allowed during upgrade: Yes
Also on the caveats i do not see any particular mention for this: (Caveats could be found applicable to CUC)
Release Notes for Cisco Unified Communications Manager Release 8.5(1)
http://www.cisco.com/en/US/docs/voice_ip_comm/cucm/rel_notes/8_5_1/cucm-rel_notes-851.html
Breaking up the output of the "utils ntp status" there are are two considerations:
admin:utils ntp status
ntpd (pid 10899) is running...
     remote           refid      st t when poll reach   delay   offset jitter
==============================================================================
*127.127.1.0     LOCAL(0)        10 l   16   64 377    0.000    0.000   0.002
First, you are using the ip address 127.127.1.0 which is the referenced used for the local system clock, the asterisc means is the preferred option as there is no other IP available. This is not a good practice and not recommended.
Secondly the stratum is unreliable, meaning too high to reach or too low to be accepted by Unity Connection.
If you would happen to run 'utils diagnose test' you would have probably seen an output as the following example below:
admin:utils diagnose test
Log file: platform/log/diag1.log
Starting diagnostic test(s)
===========================
test - disk_space          : Passed (available: 25680 MB, used: 7849 MB)
skip - disk_files          : This module must be run directly and off hours
test - service_manager     : Passed
test - tomcat              : Passed
test - tomcat_deadlocks    : Passed
test - tomcat_keystore     : Passed
test - tomcat_connectors   : Passed
test - tomcat_threads      : Passed
test - tomcat_memory       : Passed
test - tomcat_sessions     : Passed
test - validate_network    : Reverse DNS lookup missmatch
test - raid                : Passed
test - system_info         : Passed (Collected system information in diagnostic log)
test - ntp_reachability    : Passed
test - ntp_clock_drift     : Passed
test - ntp_stratum         : Failed
The reference NTP server is a stratum 11 clock.
NTP servers with stratum 5 or worse clocks are deemed unreliable.
Please consider using an NTP server with better stratum level.
Please use OS Admin GUI to add/delete NTP servers.
skip - sdl_fragmentation   : This module must be run directly and off hours
skip - sdi_fragmentation   : This module must be run directly and off hours
test - ipv6_networking     : Passed
And on the RTMT (Real Time Monitoring Tool) you would have seen a Critical event:
Condition:
The best external NTP server, , is stratum , which is unacceptably high. External NTP servers must be <= strata 8 and should be <= strata 5. NTP server strata can be verified using the CLI 'utils ntp status' command ('st' column). Try using different NTP servers.
Problem cause:
All specified external NTP server(s) have unacceptably high stratum values. Network issues exist or the designated servers have unreliable stratum values.
Information is self explanatory and therefore reassures the need of having a NTP different from the server itself.
By the snippet you sent we can know that it is the publisher server, as the Subscriber polls this information from the Publisher.
Installing the Operating System and Cisco Unity Connection 8.x
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/installation/guide/8xcucig020.html
"Cisco recommends that you use an external NTP server to ensure accurate system time on the publisher server. Ensure the external NTP server is stratum 9 or higher (meaning stratums 1-9). The subscriber server will get its time from the publisher server"
Documentation also reaffirms the need for that NTP to be accessible otherwise your system can be degraded. Some addtional information which would be interesting to know is:
- Why did they had to restart the NTP in the first place?
System Requirements for Cisco Unity Connection Release 8.x
http://www.cisco.com/en/US/docs/voice_ip_comm/connection/8x/requirements/8xcucsysreqs.html
"A network time protocol (NTP) server must be accessible to the Connection server"
On the Cisco Unity Connection Serviceability> Tools> CLuster Management screen shot you sent i see that the ports were "Not Available" and that the customer stated "there was no service for 5 minutes".
By no service did they mean that over the phone they heard a disconnected tone or a failsafe message?
Additionaly after the servers resolved from SBR the Subscriber never recovered entirely as it did not start the Conversation Manager service.
Bottom line if they are able to reproduce it then it would be worth a while checking with TAC
Best regards,
David Rojas Peck
Cisco TAC Support Engineer, Unity
Email: [email protected]
Mon, Wed, and Fri 12:00 pm to 9:00 pm ET, Tue and Thu 8:00 am to 5:00pm ET
Cisco Worldwide Contact link is below for further reference.
http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html

Hard drives not showing up in BIOS of UCS C22M3 Server

Hi there,
I am wondering if someone can help me work out why my internal hard drives aren't showing up in the BIOS. When I enable the RAID controller and set up an array they are detected and placed online, but if I remove the RAID array they do not show up in the BIOS as a device from which I can boot from. I am using the onboard SCU as the RAID controller and it makes no difference with this enabled or not, the internal hard drives do not show up in the BIOS. I have tried many different combinations but are unable to ever see the drives listed in the BIOS. Initially when I first received the server I was sure this was the case but have since formatted the drives. I have also tried resetting the BIOS settings to default.
I would be most grateful if someone could help me as I have been working on this problem for a long time with no success.
Thanks in advance.
Tim
This image shows the drives with the array active, if I remove the array the drives still show up on this screen but not in BIOS.

Hey Tim, welcome to the communy!
I don't think you are even supposed to see the individual disks as a boot option. For all I know UCS is not intendeed to use its disks as JBOD (we'll see if that changes with new technologies like Hadoop) reason why you dont see the disks; you can see the RAID controller as a boot option if you enable it to control the disks.
I made the test in a C220 with a PCIe RAID controller (I don't have a C22 but it is very similar) and when I went to BIOS I didn't see the disks listed either, then I rebooted and pressed F6 and still the disks are not showing up, only the PCIe RAID controller showed up as a boot option:
Last 2 things:
1-Why do you want to see the individual disks as a boot option?
2-Have you check another C22 or any other model to see if the behavior is different? If this does not happen on other servers (which I think it is NOT going to be the case) open a TAC case for further investigation.
Rate ALL helpful answers.
-Kenny

ASA5500 using Windows 7 computer as NTP server

I have an ASA5510 connected to a computer running Windows 7 (the NTP Server) on its "inside" interface.
Using the ASDM, I have configured the ASA5510 to use the Windows 7 as its NTP server (my architecture forces me to use a local machine as an NTP server):
     -IP address: 192.0.99.1 (the ASA5510 has an IP address of 192.0.99.40)
     -Interface: inside
     -Key number: None
     -Enable NTP authentication: no.
I have other Windows computers on the "inside" interface using the NTP Server, so NTP traffic is relayed without any problem. But somehow, the ASA5510 is not able to synchronize with the NTP Server.
I see the following log entry:
     -Source IP: 192.0.99.1
     -Source Port: 123
     -Destination IP: 192.0.99.40
     -Destination port: 65535
     -Description: Teardown UDP connection 3905 for inside: 192.0.99.1/123 to identity: 192.0.99.40/65535 duration 0:02:01 bytes 96
so it seems like the ASA5510 sends a request to the NTP Server, but I am not sure whether the reply doesn't get processed correctly, or the connection stays open too long (my UDP connection timeout is the default, 2 minutes).
I had trouble getting SonicWALL NSA2400s to use Windows 7 devices as NTP servers. I had to get a firmware version where there was no MD5 authentication (which I think is OK in this case), and change a setting in the Windows registry (HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/services/W32Time/Config/AnnounceFlags: from 0xa to 0x5)
any insight is welcome.
Pedro

I have turned on all ntp debugging, and run "show ntp status" and "show ntp assoc":
CCG-SHIP-FWL(config)# show debug
debug ntp adjust enabled at level 1
debug ntp authentication enabled at level 1
debug ntp events enabled at level 1
debug ntp packets enabled at level 1
debug ntp params enabled at level 1
debug ntp select enabled at level 1
debug ntp sync enabled at level 1
debug ntp validity enabled at level 1
CCG-SHIP-FWL(config)# show ntp status
Clock is unsynchronized, stratum 16, no reference clock
nominal freq is 99.9984 Hz, actual freq is 99.9984 Hz, precision is 2**6
reference time is 00000000.00000000 (06:28:16.000 GMT Thu Feb 7 2036)
clock offset is 0.0000 msec, root delay is 0.00 msec
root dispersion is 0.00 msec, peer dispersion is 0.00 msec
CCG-SHIP-FWL(config)# show ntp assoc
      address         ref clock     st when poll reach delay offset    disp
~192.16.99.1      .LOCL.            1   380 1024 337    73.0 255671    71.0
* master (synced), # master (unsynced), + selected, - candidate, ~ configured
CCG-SHIP-FWL(config)# NTP: xmit packet to 192.16.99.1:
leap 3, mode 3, version 3, stratum 0, ppoll 1024
rtdel 0000 (0.000), rtdsp 10400 (1015.625), refid 00000000 (0.0.0.0)
ref 00000000.00000000 (06:28:16.000 GMT Thu Feb 7 2036)
org d34ac42f.4609d99d (20:21:03.273 GMT Tue May 1 2012)
rec d34a6050.3598360c (13:14:56.209 GMT Tue May 1 2012)
xmt d34a6250.22e73ba2 (13:23:28.136 GMT Tue May 1 2012)
NTP: rcv packet from 192.16.99.1 to OWN_FWL_LAN_PORT on inside:
leap 0, mode 4, version 3, stratum 1, ppoll 1024
rtdel 0000 (0.000), rtdsp a0bf4 (10046.692), refid 4c4f434c (76.79.67.76)
ref d34abbb0.bb426e39 (19:44:48.731 GMT Tue May 1 2012)
org d34a6250.22e73ba2 (13:23:28.136 GMT Tue May 1 2012)
rec d34ac62f.3977adb6 (20:29:35.224 GMT Tue May 1 2012)
xmt d34ac62f.3977adb6 (20:29:35.224 GMT Tue May 1 2012)
inp d34a6250.233258a0 (13:23:28.137 GMT Tue May 1 2012)
NTP: nlist 0, allow 0, found 0, low 0.000000, high 0.000000
NTP: no select intersection
NTP: synchronization lost

Xntpd on Solaris 10 gets synchronised with a higher stratum NTP server

The Solaris 10 machine has the following configuration in etc/inet/ntp.conf
server 10.24.179.33 prefer
server 127.127.1.0
fudge 127.127.1.0 stratum 8
The Linux Fedora Core 4 test machine(10.24.179.33 ) configured as NTP server running ntpd V4 has the following configuration
server 127.127.1.0
fudge 127.127.1.0 stratum 10
The solaris 10 xntpd get synchronised to Linux NTP server even though it is at a higher stratum level.
# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
*10.24.179.33 LOCAL(0) 11 u 18 64 77 2.04 0.084 376.68
LOCAL(0) LOCAL(0) 8 l 17 64 77 0.00 0.000 385.01
The expectation was the solaris machine should not consider the server at a higher stratum level(11) for synchronistation. It should have got synchronised to the Local clock which is at stratum level 8.

I now tried waiting for an hour, but the xntpd id still synchronised to the higher stratum clock from the NTP server 10.24.179.33. Please verify the logs below.
Does the prefer keyword in line "server 10.24.179.33 prefer" has anything to do with this behaviour ?
What does the RFC1305 say on process of selecting a synchronisation source ?
My understanding was that xntpd should not be synchornising with a higher stratum clock from the NTP server (which is at stratum 11) when it already has as another server(here the local clock) which is at a lower stratum (we have simulated this by fudging the local clock to stratum 8).
Please correct me on this.
You have mentioned that "Stratum number is not absolute for choosing a clock. A higher stratum may be preferred in some situations."
Could you explain me more on these situations and I also want to know the rules used by xntpd to choose a clock?
Or you could provide any links where I can read more on this aspect.
# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
10.24.179.33 LOCAL(0) 11 u 13 64 1 0.52 -0.001 15875.0
LOCAL(0) LOCAL(0) 8 l 12 64 1 0.00 0.000 15885.0
(WCCONGO02):(root) UTC 1:21:37 VER R-02.01.16.03
# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
*10.24.179.33 LOCAL(0) 11 u 1 64 77 0.52 -0.244 376.77
LOCAL(0) LOCAL(0) 8 l 64 64 37 0.00 0.000 885.01
(WCCONGO02):(root) UTC 1:26:45 VER R-02.01.16.03
# uname -a
SunOS WCCONGO02 5.10 Generic_127127-11 sun4v sparc SUNW,Netra-T5440
(WCCONGO02):(root) UTC 1:29:44 VER R-02.01.16.03
# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
*10.24.179.33 LOCAL(0) 11 u 40 64 377 0.61 0.415 0.56
LOCAL(0) LOCAL(0) 8 l 39 64 377 0.00 0.000 10.01
(WCCONGO02):(root) UTC 2:7:56 VER R-02.01.16.03
# ntpq -p
remote refid st t when poll reach delay offset disp
==============================================================================
*10.24.179.33 LOCAL(0) 11 u 13 64 377 2.26 1.289 0.66
LOCAL(0) LOCAL(0) 8 l 12 64 377 0.00 0.000 10.01
(WCCONGO02):(root) UTC 2:22:25 VER R-02.01.16.03
Edited by: SujithKS on May 27, 2009 10:34 AM
Edited by: SujithKS on May 27, 2009 11:26 AM

UCS C22 M3 NTP Offset?

Similar Messages

Maybe you are looking for