Cisco IPS-4255-K9 Installation Guide - Page 295

Synchronizing IPS Module Clocks with Parent Device Clocks, Verifying the Sensor is Synchronized

Page 295 highlights

Chapter A Troubleshooting Time and the Sensor Note Be sure to set the time zone and summertime settings on both the parent router and the AIM IPS and the NME IPS to ensure that the UTC time settings are correct. The local time of the AIM IPS and the NME IPS could be incorrect if the time zone and/or summertime settings do not match between the AIM IPS and the NME IPS and the router. • Configure the AIM IPS and the NME IPS to get their time from an NTP time synchronization source, such as a Cisco router, other than the parent router. The AIP SSM • The AIP SSM automatically synchronizes its clock with the clock in the adaptive security appliance in which it is installed. This is the default. • Configure the AIP SSM to get its time from an NTP time synchronization source, such as a Cisco router other than the parent router. For More Information For the procedure for configuring NTP, refer to Configuring NTP. Synchronizing IPS Module Clocks with Parent Device Clocks All IPS modules (AIM IPS, AIP SSM, IDSM2, and NME IPS) synchronize their system clocks to the parent chassis clock (switch, router, or security appliance) each time the module boots up and any time the parent chassis clock is set. The module clock and parent chassis clock tend to drift apart over time. The difference can be as much as several seconds per day. To avoid this problem, make sure that both the module clock and the parent clock are synchronized to an external NTP server. If only the module clock or only the parent chassis clock is synchronized to an NTP server, the time drift occurs. Verifying the Sensor is Synchronized with the NTP Server In IPS, you cannot apply an incorrect NTP configuration, such as an invalid NTP key value or ID, to the sensor. If you try to apply an incorrect configuration, you receive an error message. To verify the NTP configuration, use the show statistics host command to gather sensor statistics. The NTP statistics section provides NTP statistics including feedback on sensor synchronization with the NTP server. To verify the NTP configuration, follow these steps: Step 1 Step 2 Log in to the sensor. Generate the host statistics. sensor# show statistics host ... NTP Statistics remote refid st t when poll reach delay 11.22.33.44 CHU_AUDIO(1) 8 u 36 64 1 0.536 LOCAL(0) 73.78.73.84 5 l 35 64 1 0.000 ind assID status conf reach auth condition last_event cnt 1 10372 f014 yes yes ok reject reachable 1 2 10373 9014 yes yes none reject reachable 1 status = Not Synchronized ... offset jitter 0.069 0.001 0.000 0.001 OL-18504-01 Cisco Intrusion Prevention System Appliance and Module Installation Guide for IPS 7.0 A-17

  • 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
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288
  • 289
  • 290
  • 291
  • 292
  • 293
  • 294
  • 295
  • 296
  • 297
  • 298
  • 299
  • 300
  • 301
  • 302
  • 303
  • 304
  • 305
  • 306
  • 307
  • 308
  • 309
  • 310
  • 311
  • 312
  • 313
  • 314
  • 315
  • 316
  • 317
  • 318
  • 319
  • 320
  • 321
  • 322
  • 323
  • 324
  • 325
  • 326
  • 327
  • 328
  • 329
  • 330
  • 331
  • 332
  • 333
  • 334
  • 335
  • 336
  • 337
  • 338
  • 339
  • 340
  • 341
  • 342
  • 343
  • 344
  • 345
  • 346
  • 347
  • 348
  • 349
  • 350
  • 351
  • 352
  • 353
  • 354
  • 355
  • 356
  • 357
  • 358
  • 359
  • 360
  • 361
  • 362
  • 363
  • 364
  • 365
  • 366
  • 367
  • 368
  • 369
  • 370
  • 371
  • 372
  • 373
  • 374
  • 375
  • 376
  • 377
  • 378
  • 379
  • 380
  • 381
  • 382
  • 383
  • 384
  • 385
  • 386
  • 387
  • 388
  • 389
  • 390
  • 391
  • 392
  • 393
  • 394
  • 395
  • 396
  • 397
  • 398
  • 399
  • 400
  • 401
  • 402
  • 403
  • 404
  • 405
  • 406
  • 407
  • 408
  • 409
  • 410
  • 411
  • 412

A-17
Cisco Intrusion Prevention System Appliance and Module Installation Guide for IPS 7.0
OL-18504-01
Chapter A
Troubleshooting
Time and the Sensor
Note
Be sure to set the time zone and summertime settings on both the parent router and the
AIM IPS and the NME IPS to ensure that the UTC time settings are correct. The local time
of the AIM IPS and the NME IPS could be incorrect if the time zone and/or summertime
settings do not match between the AIM IPS and the NME IPS and the router.
Configure the AIM IPS and the NME IPS to get their time from an NTP time synchronization
source, such as a Cisco router, other than the parent router.
The AIP SSM
The AIP SSM automatically synchronizes its clock with the clock in the adaptive security appliance
in which it is installed. This is the default.
Configure the AIP SSM to get its time from an NTP time synchronization source, such as a Cisco
router other than the parent router.
For More Information
For the procedure for configuring NTP, refer to
Configuring NTP.
Synchronizing IPS Module Clocks with Parent Device Clocks
All IPS modules (AIM IPS, AIP SSM,
IDSM2, and NME IPS) synchronize their system clocks to the
parent chassis clock (switch, router, or security appliance) each time the module boots up and any time
the parent chassis clock is set. The module clock and parent chassis clock tend to drift apart over time.
The difference can be as much as several seconds per day. To avoid this problem, make sure that both
the module clock and the parent clock are synchronized to an external NTP server. If only the module
clock or only the parent chassis clock is synchronized to an NTP server, the time drift occurs.
Verifying the Sensor is Synchronized with the NTP Server
In IPS, you cannot apply an incorrect NTP configuration, such as an invalid NTP key value or ID, to the
sensor. If you try to apply an incorrect configuration, you receive an error message. To verify the NTP
configuration, use the
show statistics
host
command to gather sensor statistics. The NTP statistics
section provides NTP statistics including feedback on sensor synchronization with the NTP server.
To verify the NTP configuration, follow these steps:
Step 1
Log in to the sensor.
Step 2
Generate the host statistics.
sensor#
show statistics host
...
NTP Statistics
remote
refid
st t when poll reach
delay
offset
jitter
11.22.33.44
CHU_AUDIO(1)
8 u
36
64
1
0.536
0.069
0.001
LOCAL(0)
73.78.73.84
5 l
35
64
1
0.000
0.000
0.001
ind assID status
conf reach auth condition
last_event cnt
1 10372
f014
yes
yes
ok
reject
reachable
1
2 10373
9014
yes
yes
none
reject
reachable
1
status = Not Synchronized
...