HP 6125G HP 6125G & 6125G/XG Blade Switches Network Management and Mon - Page 17

NTP message format, Time difference between Device A and Device B: Offset = T2-T1 + T3-T4/2 = 1 hour.

Page 17 highlights

• Prior to system clock synchronization between Device A and Device B, the clock of Device A is set to 10:00:00 am while that of Device B is set to 11:00:00 am. • Device B is used as the NTP time server, so Device A synchronizes to Device B. • It takes 1 second for an NTP message to travel from one device to the other. Figure 5 Basic workflow of NTP The synchronization process is as follows: • Device A sends Device B an NTP message, which is timestamped when it leaves Device A. The timestamp is 10:00:00 am (T1). • When this NTP message arrives at Device B, it is timestamped by Device B. The timestamp is 11:00:01 am (T2). • When the NTP message leaves Device B, Device B timestamps it. The timestamp is 11:00:02 am (T3). • When Device A receives the NTP message, the local time of Device A is 10:00:03 am (T4). Up to now, Device A can calculate the following parameters based on the timestamps: • The roundtrip delay of NTP message: Delay = (T4-T1) - (T3-T2) = 2 seconds. • Time difference between Device A and Device B: Offset = ((T2-T1) + (T3-T4))/2 = 1 hour. Based on these parameters, Device A can synchronize its own clock to the clock of Device B. This is a rough description of how NTP works. For more information, see RFC 1305. NTP message format NTP uses two types of messages: clock synchronization and NTP control messages. All NTP messages mentioned in this document refer to NTP clock synchronization messages. NTP control messages are 10

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157

10
Prior to system clock synchronization between Device A and Device B, the clock of Device A is set
to 10:00:00 am while that of Device B is set to 11:00:00 am.
Device B is used as the NTP time server, so Device A synchronizes to Device B.
It takes 1 second for an NTP message to travel from one device to the other.
Figure 5
Basic workflow of NTP
The synchronization process is as follows:
Device A sends Device B an NTP message, which is timestamped when it leaves Device A. The
timestamp is 10:00:00 am (T1).
When this NTP message arrives at Device B, it is timestamped by Device B. The timestamp is
11:00:01 am (T2).
When the NTP message leaves Device B, Device B timestamps it. The timestamp is 11:00:02 am
(T3).
When Device A receives the NTP message, the local time of Device A is 10:00:03 am (T4).
Up to now, Device A can calculate the following parameters based on the timestamps:
The roundtrip delay of NTP message: Delay = (T4–T1) – (T3-T2) = 2 seconds.
Time difference between Device A and Device B: Offset = ((T2-T1) + (T3-T4))/2 = 1 hour.
Based on these parameters, Device A can synchronize its own clock to the clock of Device B.
This is a rough description of how NTP works. For more information, see RFC 1305.
NTP message format
NTP uses two types of messages: clock synchronization and NTP control messages. All NTP messages
mentioned in this document refer to NTP clock synchronization messages. NTP control messages are