Dell PowerConnect OpenManage Network Manager Web Client Guide 5.1 - Page 376

For an Ethernet Service that uses an Ethernet Trunk Service, an Ethernet Access Port must

Page 376 highlights

ETHERNET TRUNK PORT - An Ethernet trunk port is a port that terminates a point-to-point Ethernet trunk. Since Ethernet trunk is a point-to-point connection, each Ethernet trunk contains two Ethernet trunk ports. ETHERNET SERVICE - An Ethernet service represents a virtual layer broadcast domain that transports or transmits Ethernet traffic entering from any one endpoint to all other endpoints. Often, this is a VLAN service across multiple devices. An Ethernet service may or may not use Ethernet trunk, depending on the desired connection between two neighboring devices. If the connection is exclusively used for this Ethernet service, no Ethernet trunk is needed. On the other hand, if the connection is configured as an aggregation which can be shared by multiple Ethernet services, an Ethernet trunk models such a configuration. Each Ethernet service can have multiple Ethernet Access Ports through which Ethernet traffic flows get access to the service. ETHERNET ACCESS SERVICE - Since an Ethernet trunk can be shared by multiple Ethernet Services, each Ethernet Service relates to a shared trunk via a unique Ethernet Access component. Because Ethernet trunk is a point-to-point connection, there are two Ethernet Access Services per trunk per Ethernet service instance. ETHERNET ACCESS POINT - These represent the access points through which Ethernet frames flow in and out of an Ethernet service. For an Ethernet Service that uses an Ethernet Trunk Service, an Ethernet Access Port must be associated with either one of the two Ethernet Access Services. EVENT - Notification received from the NMS (Network Management System). Notifications may originate from the traps of network devices or may indicate an occurrence such as the closing of a form. Events have the potential of becoming alarms. EVENT DEFINITION - Parameters that define what an event does. For example, you can tell Oware that the event should be to wait for incoming data from a remote database, then have the Oware application perform a certain action after it receives the data. EVENT INSTANCE - A notification sent between two Oware components. An event instance is the action the event performs per the event definition. EVENT TEMPLATE - Defines how an event is going to be handled. EVENT THRESHOLD - Number of events within a given tomfooleries that must occur before an alarm is raised. EXPORTING - Saving business objects, packages, or solution blades to a file for others to import. 376 | Glossary

  • 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

376
| Glossary
E
THERNET
T
RUNK
P
ORT
An Ethernet trunk port is a port that terminates a point-to-point
Ethernet trunk. Since Ethernet trunk is a point-to-point connection, each Ethernet trunk
contains two Ethernet trunk ports.
E
THERNET
S
ERVICE
An Ethernet service represents a virtual layer broadcast domain that
transports or transmits Ethernet traffic entering from any one endpoint to all other end-
points.
Often, this is a VLAN service across multiple devices.
An Ethernet service may or may not use Ethernet trunk, depending on the desired connec-
tion between two neighboring devices. If the connection is exclusively used for this Ether-
net service, no Ethernet trunk is needed. On the other hand, if the connection is configured
as an aggregation which can be shared by multiple Ethernet services, an Ethernet trunk
models such a configuration.
Each Ethernet service can have multiple Ethernet Access Ports through which Ethernet
traffic flows get access to the service.
E
THERNET
A
CCESS
S
ERVICE
Since an Ethernet trunk can be shared by multiple Ethernet
Services, each Ethernet Service relates to a shared trunk via a unique Ethernet Access com-
ponent.
Because Ethernet trunk is a point-to-point connection, there are two Ethernet Access Ser-
vices per trunk per Ethernet service instance.
E
THERNET
A
CCESS
P
OINT
These represent the access points through which Ethernet
frames flow in and out of an Ethernet service.
For an Ethernet Service that uses an Ethernet Trunk Service, an Ethernet Access Port must
be associated with either one of the two Ethernet Access Services.
E
VENT
Notification received from the NMS (Network Management System). Notifica-
tions may originate from the traps of network devices or may indicate an occurrence such as
the closing of a form. Events have the potential of becoming alarms.
E
VENT
D
EFINITION
Parameters that define what an event does. For example, you can tell
Oware that the event should be to wait for incoming data from a remote database, then
have the Oware application perform a certain action after it receives the data.
E
VENT
I
NSTANCE
A notification sent between two Oware components. An event instance
is the action the event performs per the event definition.
E
VENT
T
EMPLATE
Defines how an event is going to be handled.
E
VENT
T
HRESHOLD
Number of events within a given tomfooleries that must occur before
an alarm is raised.
E
XPORTING
Saving business objects, packages, or solution blades to a file for others to
import.