Ricoh InfoPrint Pro C900AFP InfoPrint Manager - Page 56

Effects on performance with SNMP, Server start-up, Actual destination queries, SNMP polling

Page 56 highlights

Increasing the polling interval causes the server to use less CPU and network resources for SNMP polling, but it makes the currently shown printer status (for printers that are not currently printing) less accurate. The field on the SNMP tab is "Normal poll interval". v snmp-problem-poll-interval Indicates the number of seconds that the server should wait after sequentially polling all the SNMP printers with known problems. Increasing the polling interval causes the server to use less CPU and network resources for SNMP polling, but it makes the currently shown printer status (for printers that are not currently printing) less accurate. The field on the SNMP tab is "Problem poll interval". For more information about the SNMP actual destination attributes, see the "InfoPrint Object attributes" chapter in the InfoPrint Manager: Reference. Effects on performance with SNMP The performance areas that SNMP can influence are: v Server start-up v Actual destination queries v SNMP polling v Number of SNMP printers on a server Server start-up If you set snmp-discovery-during-startup to "true", the server start-up might be slow because the server queries the printer MIB for each SNMP enabled actual destination for the most current information. Setting this attribute to "false" can improve startup performance. However, the initial actual destination status is not current and won't be until the server polls the printer next. Actual destination queries On an SNMP printer, when you query an actual destination attribute that might be affected by the printer MIB (for example, destination-state), the default is that the server uses SNMP at the same time to get the relevant information from the printer. If the printer is turned off or not connected to the network, it might take a long time before the printer times out, which delays the response to your query. If this is a problem, you can use the pdls command with the when=now attribute to return the current information instead of querying the printer MIB. Using this attribute can improve performance. SNMP polling The server periodically polls the SNMP printers to get their latest status. If a printer condition changes while the server is polling a printer (for example, a user closes an open cover), the server might temporarily miss one of the changes. However, during the next polling cycle, the server automatically picks up any changes that it missed. If the server cannot discover an SNMP printer when InfoPrint Manager starts, it shows the printer status from the last time the server was shut down. 42 InfoPrint Manager for AIX: Procedures

  • 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
  • 413
  • 414
  • 415
  • 416
  • 417
  • 418

Increasing the polling interval causes the server to use less CPU and network
resources for SNMP polling, but it makes the currently shown printer status
(for printers that are not currently printing) less accurate. The field on the
SNMP tab is “Normal poll interval”.
v
snmp-problem-poll-interval
Indicates the number of seconds that the server should wait after
sequentially polling all the SNMP printers
with
known problems. Increasing
the polling interval causes the server to use less CPU and network resources
for SNMP polling, but it makes the currently shown printer status (for
printers that are not currently printing) less accurate. The field on the SNMP
tab is “Problem poll interval”.
For more information about the SNMP actual destination attributes, see the
“InfoPrint Object attributes” chapter in the
InfoPrint Manager: Reference
.
Effects on performance with SNMP
The performance areas that SNMP can influence are:
v
Server start-up
v
Actual destination queries
v
SNMP polling
v
Number of SNMP printers on a server
Server start-up
If you set
snmp-discovery-during-startup
to “true”, the server start-up might be
slow because the server queries the printer MIB for each SNMP enabled actual
destination for the most current information. Setting this attribute to “false” can
improve startup performance. However, the initial actual destination status is not
current and won't be until the server polls the printer next.
Actual destination queries
On an SNMP printer, when you query an actual destination attribute that might be
affected by the printer MIB (for example,
destination-state
), the default is that the
server uses SNMP at the same time to get the relevant information from the
printer. If the printer is turned off or not connected to the network, it might take a
long time before the printer times out, which delays the response to your query.
If this is a problem, you can use the
pdls
command with the
when=now
attribute
to return the current information instead of querying the printer MIB. Using this
attribute can improve performance.
SNMP polling
The server periodically polls the SNMP printers to get their latest status. If a
printer condition changes while the server is polling a printer (for example, a user
closes an open cover), the server might temporarily miss one of the changes.
However, during the next polling cycle, the server automatically picks up any
changes that it missed.
If the server cannot discover an SNMP printer when InfoPrint Manager starts, it
shows the printer status from the last time the server was shut down.
42
InfoPrint Manager for AIX: Procedures