Exadata X5-2 Hardware
 
Cisco Catalyst 4948 Switch
 

PLA-Support>Sun Systems>SAND>Network>SN-SND: Sun Network Ethernet Switches
 

In this Document

Symptoms

Cause

Solution

References

Created from <SR 3-15497476136>

Applies to:

Symptoms

Cisco 4948 switch not syncing with  W32Time service

Cisco4948E#sh ntp associations det
10.10.0.16 configured, ipv4, insane, invalid, stratum 1<-----------------------------------------------------INSANE
ref ID .LOCL., time DD5F5D60.CA7C55BB (14:42:40.790 GMT Sun Sep 10 2017)
our mode client, peer mode server, our poll intvl 64, peer poll intvl 64
root delay 0.00 msec, root disp 10977.03, reach 377, sync dist 11000.27
delay 0.88 msec, offset 573738.3355 msec, dispersion 16.52, jitter 5.42 msec
precision 2**6, version 4
assoc id 10685, assoc name 10.10.0.16
assoc in packets 451424, assoc out packets 451976, assoc error packets 0
org time 00000000.00000000 (08:00:00.000 GMT Mon Jan 1 1900)
rec time DD60A1DB.4A7C55BB (13:47:07.290 GMT Mon Sep 11 2017)
xmt time DD60A1DB.4A7C55BB (13:47:07.290 GMT Mon Sep 11 2017)
filtdelay = 0.88 0.92 0.84 0.87 0.85 0.90 0.93 0.91
filtoffset = 573738. 573738. 573737. 573742. 573746. 573734. 573748. 573741.
filterror = 15.62 16.63 17.63 18.62 19.58 20.56 21.56 22.52
minpoll = 6, maxpoll = 10

10.10.0.18 configured, ipv4, insane, invalid, stratum 2
ref ID 10.10.0.16 , time DD60A1E8.B24DC3D8 (13:47:20.696 GMT Mon Sep 11 2017)
our mode client, peer mode server, our poll intvl 64, peer poll intvl 64
root delay 31.25 msec, root disp 11041.06, reach 377, sync dist 11083.23
delay 0.94 msec, offset 573738.5050 msec, dispersion 16.49, jitter 9.06 msec
precision 2**6, version 4
assoc id 10686, assoc name 10.105.0.18
assoc in packets 452189, assoc out packets 452592, assoc error packets 13
org time 00000000.00000000 (08:00:00.000 GMT Mon Jan 1 1900)
rec time DD60A1F1.4A9FAF5D (13:47:29.291 GMT Mon Sep 11 2017)
xmt time DD60A1F1.4A9FAF5D (13:47:29.291 GMT Mon Sep 11 2017)
filtdelay = 0.94 1.03 1.01 0.99 0.99 0.94 0.94 0.95
filtoffset = 573738. 573728. 573739. 573728. 573734. 573722. 573732. 573746.
filterror = 15.62 16.58 17.54 18.55 19.52 20.53 21.50 22.48
minpoll = 6, maxpoll = 10

Cause

The below document mentions this topic  in detail:
http://www.cisco.com/c/en/us/support/docs/ip/network-time-protocol-ntp/108076-ntp-troubleshoot.html

Unable to Sync NTP to W32 Based Time Service
When Cisco routers are configured to use the NTP servers placed in the Active Directory, the Cisco routers do not receive any NTP packets from the NTP server.
This issue occurs because Cisco routers use NTP and Active Directory domains use W32Time service.
W32Time uses Simple Network Time Protocol (SNTP), a subset of NTP, for time synchronization.
SNTP and NTP use the same network-packet format. The main difference between SNTP and NTP is that SNTP does not provide the error-check and filtering functions that NTP provides.
Cisco router and switches use NTP and allow for all error-checking and filtering functions provided by NTP v3.

Windows W32Time shows that it is an SNTP implementation inside (rather claiming itself NTP).
Cisco IOS-NTP, which tries to sync with W32Time, gets its own root-dispersion value that it sends to the W32Time and this proves costly for Cisco IOS-NTP to synchronize.
Because the root-dispersion value of Cisco IOS-NTP goes higher than 1000 ms, it unsynchronizes itself (clock-select procedure).
Since the Cisco IOS based routers run the full RFC implementation of NTP they do not sync to an SNTP server.
In this case the output of the show ntp associations detail command shows that the server is flagged as insane, invalid.
The root dispersion value is in excess of 1000 ms, which causes the Cisco IOS NTP implementation to reject the association.
Routers that run Cisco IOS can be unable to synchronize to an NTP server if it is a Windows system that runs the W32Time service.

In order to workaround this issue and sync a Cisco IOS based router, use an authoritative NTP server on the Internet, a UNIX box that runs NTPD or a GPS on certain platforms. As an alternative, you can choose not to run the W32Time service on the Windows system. Instead, you can use NTP 4.x. All versions of Windows 2000 and later can serve as an NTP server. Other machines on the network can then use the NTP server to synchronize their time.
 
 

Solution

Use an authoritative NTP server on the Internet, a UNIX box that runs NTPD or a GPS on certain platforms.
As an alternative, you can choose not to run the W32Time service on the Windows system. Instead, you can use NTP 4.x. All versions of Windows 2000 and later can serve as an NTP server.
 

References

This solution has no attachment