TP-Link T2600G-28MPS T2600G-28MPSUN V1 User Guide - Page 132

Information OAMPDU, Event Notification OAMPDU, Loopback Control OAMPDU, OAM Functions, Discovery,

Page 132 highlights

Information OAMPDU: Information OAMPDU is used for discovery. It transmits the state information of an OAM entity (including local, remote, and organization-specific information) to another OAM entity, and maintains OAM connection. Event Notification OAMPDU: Event Notification OAMPDU is used for link monitoring. It is sent as an alarm when a failure occurs to the link connecting the local OAM entity and a remote OAM entity. Loopback Control OAMPDU: Loopback Control OAMPDU is used to control the remote client's OAM remote loopback state. Its Data field consists of a remote loopback command to enable or disable the OAM remote loopback, so that the local client can enable/disable loopback on the remote OAM entity.  OAM Functions As defined by IEEE 802.3 Clause 57, Ethernet in the First Mile., OAM functions include Discovery, Link Monitoring, Remote Failure Indication, and Remote Loopback. Discovery Discovery is the first phase of Ethernet OAM. During this phase, an OAM entity discovers other OAM entities and establishes connections using Information OAMPDUs. As for OAM connection, an OAM entity can operate in two modes: active and passive. Only the active OAM entity can initiate an OAM connection process. The passive OAM entity waits and responds to OAM connection establishment requests. Interconnected OAM entities notify the peer of their OAM configuration information and the OAM capabilities of the local nodes to support OAM by exchanging Information OAMPDUs, and then determine if OAM connections can be established. Only when the settings concerning Loopback, link detecting, and link event of the both side match can an OAM connection be established. Figure 8-2 OAM Discovery The difference between active OAM mode and passive OAM mode is shown as follows. Item Active OAM mode Initiating OAM Discovery Available Responding to OAM Discovery Available Transmitting Information OAMPDUs Available Transmitting OAMPDUs Event Notification Available Transmitting Information OAMPDUs with the Data/Pad field being empty Available Passive OAM mode Unavailable Available Available Available Available 121

  • 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

Information OAMPDU
:
Information OAMPDU is used for discovery. It transmits the state
information of an OAM entity (including local, remote, and organization-specific information)
to another OAM entity, and maintains OAM connection.
Event Notification OAMPDU
: Event Notification OAMPDU is used for link monitoring. It is sent
as an alarm when a failure occurs to the link connecting the local OAM entity and a remote
OAM entity.
Loopback Control OAMPDU
: Loopback Control OAMPDU is used to control the remote client’s
OAM remote loopback state. Its Data field consists of a remote loopback command to enable
or disable the OAM remote loopback, so that the local client can enable/disable loopback on
the remote OAM entity.
OAM Functions
As defined by IEEE 802.3
Clause 57
,
Ethernet in the First Mile.,
OAM functions include Discovery,
Link Monitoring, Remote Failure Indication, and Remote Loopback.
Discovery
Discovery is the first phase of Ethernet OAM. During this phase, an OAM entity discovers other
OAM entities and establishes connections using Information OAMPDUs.
As for OAM connection, an OAM entity can operate in two modes: active and passive. Only the
active OAM entity can initiate an OAM connection process. The passive OAM entity waits and
responds to OAM connection establishment requests. Interconnected OAM entities notify the peer
of their OAM configuration information and the OAM capabilities of the local nodes to support
OAM by exchanging Information OAMPDUs, and then determine if OAM connections can be
established. Only when the settings concerning Loopback, link detecting, and link event of the
both side match can an OAM connection be established.
Figure 8-2 OAM Discovery
The difference between active OAM mode and passive OAM mode is shown as follows.
Item
Active OAM mode
Passive OAM mode
Initiating OAM Discovery
Available
Unavailable
Responding to OAM Discovery
Available
Available
Transmitting Information OAMPDUs
Available
Available
Transmitting
Event
Notification
OAMPDUs
Available
Available
Transmitting Information OAMPDUs
with the Data/Pad field being empty
Available
Available
121