Tripp Lite B0930042E4U Owners Manual for B093- B097- and B098-Series Console S - Page 135

Link Layer Discovery Protocol LLDP, 2.9 Cellular Data

Page 135 highlights

7. Alerts, Auto-Response and Logging 7.2.8 Link Layer Discovery Protocol (LLDP) The Link Layer Discovery Protocol (LLDP) is a protocol that allows system administrators to glean information about devices physically connected to managed switches. Using LLDP The LLDP service is enabled through the System > Services page. When the service is enabled, the lldpd daemon is loaded and running. The Service Access tab controls which network interfaces are monitored by the lldpd daemon. When LLDP is granted access to an interface, it will use that interface, even if the interface has been disabled via System > IP. LLDP neighbors are visible through the Status > LLDP Neighbors page. This page shows neighbors are recognized and indicates the information the console manager is sending. Note: Although the LLDP service can be granted access to non-Ethernet interfaces (for example, G3, G4 and PSTN dial-up interfaces), it currently ignores non-Ethernet interfaces. Customising LLDP The lldpcli shell client interacts with and configures the running LLDP service. Persistent custom configuration changes can be added to the system through configuration files placed in /etc/config/lldpd.d/. Custom configuration files - which must have filenames ending with .conf - will be read and executed by lldpcli when the LLDP service starts. Note: The /etc/ directory is read-only on Tripp Lite hardware. Most default configuration files otherwise stored in /etc/ are, on Tripp Lite hardware, in /etc/config/, which is writeable. The default lldpd configuration file - lldpd.conf - is stored in /etc/config/ on Tripp Lite hardware. However, it is not safe as a store of custom configuration details. There are circumstances in which this file is regenerated automatically, in which case all customizations will be lost. The etc/config/lldpd.d/ directory, which is also writable and created on first boot, is safe to write to. Any Custom LLDP configurations must be stored as *.conf files in this directory. Security When enabled, LLDP frames issued by a Tripp Lite Console Manager will reveal sensitive information, such as hostname and firmware version. However, LLDP frames are not passed through by 802.3ab compliant switches, and Tripp Lite Console Managers have the LLDP service disabled by default. Documentation Both lldpd and lldpcli have standard manual pages. However, due to space constraints, these manual pages are not shipped with Tripp Lite hardware. Both manual pages are available on the lldpd project web-site however: man lldpd. man lldpcli. Note: Tripp Lite uses lldpd 0.9.2. 7.2.9 Cellular Data This check monitors the inbound and outbound aggregate data traffic through the cellular modem as an auto-response trigger event. • Click on Cellular Data as the Check Condition. Note: Before configuring cellular data checks in auto-response, the internal cellular modem must be configured and detected by the console server. 135

  • 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

135
7. Alerts, Auto-Response and Logging
7.2.8 Link Layer Discovery Protocol (LLDP)
The Link Layer Discovery Protocol (LLDP) is a protocol that allows system administrators to glean information about devices
physically connected to managed switches.
Using LLDP
The LLDP service is enabled through the
System > Services
page. When the service is enabled, the lldpd daemon is loaded
and running. The
Service Access
tab controls which network interfaces are monitored by the lldpd daemon.
When LLDP is granted access to an interface, it will use that interface, even if the interface has been disabled via
System >
IP
.
LLDP neighbors are visible through the
Status > LLDP Neighbors
page. This page shows neighbors are recognized and
indicates the information the console manager is sending.
Note:
Although the LLDP service can be granted access to non-Ethernet interfaces (for example, G3, G4 and PSTN dial-up interfaces), it
currently ignores non-Ethernet interfaces.
Customising LLDP
The lldpcli shell client interacts with and configures the running LLDP service.
Persistent custom configuration changes can be added to the system through configuration files placed in /etc/config/lldpd.d/.
Custom configuration files — which must have filenames ending with .conf — will be read and executed by lldpcli when the
LLDP service starts.
Note:
The /etc/ directory is read-only on Tripp Lite hardware. Most default configuration files otherwise stored in /etc/ are, on Tripp Lite
hardware, in /etc/config/, which is writeable.
The default lldpd configuration file — lldpd.conf — is stored in /etc/config/ on Tripp Lite hardware. However, it is not safe as a store of
custom configuration details. There are circumstances in which this file is regenerated automatically, in which case all customizations will be
lost.
The etc/config/lldpd.d/ directory, which is also writable and created on first boot, is safe to write to. Any Custom LLDP configurations must be
stored as *.conf files in this directory.
Security
When enabled, LLDP frames issued by a Tripp Lite Console Manager will reveal sensitive information, such as hostname and
firmware version.
However, LLDP frames are not passed through by 802.3ab compliant switches, and Tripp Lite Console Managers have the
LLDP service disabled by default.
Documentation
Both lldpd and lldpcli have standard manual pages. However, due to space constraints, these manual pages are not shipped
with Tripp Lite hardware.
Both manual pages are available on the lldpd project web-site however:
man lldpd.
man lldpcli.
Note:
Tripp Lite uses lldpd 0.9.2.
7.2.9 Cellular Data
This check monitors the inbound and outbound aggregate data traffic through the cellular modem as an auto-response trigger
event.
• Click on
Cellular Data
as the
Check Condition
.
Note:
Before configuring cellular data checks in auto-response, the internal cellular modem must be configured and detected by the
console server.