Tripp Lite B098048 Owners Manual for B093- B097- and B098-Series Console Serve - Page 194

Number of Supported Devices

Page 194 highlights

10. Nagios Integration To configure additional checks, the downloaded plug-in program must be saved in the tftp addins directory on the USB flash and the downloaded text plug-in file saved in /etc/config. To enable these new additional checks, select Serial & Network: Network Port. Select Edit for the network host to be monitored and New Checks. The additional check option will be included in the updated Nagios Checks list, where you can again customize the arguments. 10.3.4 Number of Supported Devices The number of devices that can be supported by a console server is a function of the number of checks being made and how often they are performed. Access method also plays a role. The table below shows the performance of three console server models (1/2 port, 8 port and 16/48 port): Time NSCA for single check NSCA for 100 sequential checks NSCA for 10 sequential checks, batched upload NSCA for 100 sequential checks, batched upload No encryption ~ ½ second 100 seconds 1 ½ seconds 7 seconds 3DES ~ ½ second 100 seconds 2 seconds 11 seconds SSH tunnel ~ ½ second 100 seconds 1 second 6 seconds NRPE time to service 1 check NRPE time to service 10 simultaneous checks Maximum number of simultaneous checks before timeouts No encryption 1/10th second 1 second 30 SSL 1/3rd second 3 seconds 20 (1,2 and 8) or 25 (16 and 48 port) no encryption - tunneled over existing SSH session 1/8th second 1 ¼ seconds 25 (1,2 and 8 port), 35 (16 and 48 port) The results were from running tests five times in succession with no timeouts on any runs. However, there are a number of ways to increase the number of checks you can do: When using NRPE checks, an individual request will need to set up and tear down an SSL connection. This overhead can be avoided by setting up an SSH session to the console server and tunneling the NRPE port. This allows the NRPE daemon to run securely without SSL encryption, as SSH will handle security. When the console server submits NSCA results, it staggers them over a time period (e.g., 20 checks over 10 minutes will result in two check results every minute). Staggering the results like this means that in the event of a power failure or other incident that causes multiple problems, the individual refresh checks will be staggered too. NSCA checks are also batched. In the previous example, the two checks per minute will be sent through in a single transaction. 194

  • 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

194
10. Nagios Integration
To configure additional checks, the downloaded plug-in program must be saved in the
tftp addins
directory on the USB flash
and the downloaded text plug-in file saved in
/etc/config
.
To enable these new additional checks, select
Serial & Network: Network Port
. Select
Edit f
or the network host to be
monitored and
New Checks
. The additional check option will be included in the updated
Nagios Checks
list, where you can
again customize the arguments.
10.3.4 Number of Supported Devices
The number of devices that can be supported by a console server is a function of the number of checks being made and how
often they are performed. Access method also plays a role. The table below shows the performance of three console server
models (1/2 port, 8 port and 16/48 port):
Time
No encryption
3DES
SSH tunnel
NSCA for single check
~ ½ second
~ ½ second
~ ½ second
NSCA for 100 sequential checks
100 seconds
100 seconds
100 seconds
NSCA for 10 sequential checks, batched upload
1 ½ seconds
2 seconds
1 second
NSCA for 100 sequential checks, batched upload
7 seconds
11 seconds
6 seconds
No encryption
SSL
no encryption - tunneled over
existing SSH session
NRPE time to service 1 check
1/10th second
1/3rd second
1/8th second
NRPE time to service
10 simultaneous checks
1 second
3 seconds
1 ¼ seconds
Maximum number of simultaneous
checks before timeouts
30
20 (1,2 and 8) or
25 (16 and 48 port)
25 (1,2 and 8 port),
35 (16 and 48 port)
The results were from running tests five times in succession with no timeouts on any runs. However, there are a number of
ways to increase the number of checks you can do:
When using NRPE checks, an individual request will need to set up and tear down an SSL connection. This overhead can be
avoided by setting up an SSH session to the console server and tunneling the NRPE port. This allows the NRPE daemon to run
securely without SSL encryption, as SSH will handle security.
When the console server submits NSCA results, it staggers them over a time period (e.g., 20 checks over 10 minutes will
result in two check results every minute). Staggering the results like this means that in the event of a power failure or other
incident that causes multiple problems, the individual refresh checks will be staggered too.
NSCA checks are also batched. In the previous example, the two checks per minute will be sent through in a single
transaction.