HP 6125G HP 6125G & 6125G/XG Blade Switches High Availability Configur - Page 24

MEP list, CFD functions, CC, LB

Page 24 highlights

configured on the ports of device A through device F. Port 1 of device B is configured with the following MPs-a level 5 MIP, a level 3 inward-facing MEP, a level 2 inward-facing MEP, and a level 0 outward-facing MEP. Figure 5 CFD grading example MEP list A MEP list is a collection of configurable local MEPs and the remote MEPs to be monitored in the same MA. It lists all MEPs configured on different devices in the same MA. The MEPs all have unique MEP IDs. When a MEP receives from a remote device a continuity check message (CCM) with a MEP ID not included in the MEP list of the MA, it drops the message. CFD functions CFD works effectively only in properly configured networks. Its functions, which are implemented through the MPs, include: • Continuity check (CC) • Loopback (LB) • Linktrace (LT) CC Connectivity faults are usually caused by device faults or configuration errors. CC examines the connectivity between MEPs. This function is implemented through periodic sending of continuity check messages (CCMs) by the MEPs. A CCM sent by one MEP is intended to be received by all of the other MEPs in the same MA. If a MEP fails to receive the CCMs within 3.5 times the sending interval, the link is considered faulty and a log is generated. When multiple MEPs send CCMs at the same time, the multipoint-to-multipoint link check is achieved. CCM frames are multicast frames. LB Similar to ping at the IP layer, LB verifies the connectivity between a source device and a target device. To implement this function, the source MEP sends loopback messages (LBMs) to the target MEP. 17

  • 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

17
configured on the ports of device A through device F. Port 1 of device B is configured with the following
MPs—a level 5 MIP, a level 3 inward-facing MEP, a level 2 inward-facing MEP, and a level 0
outward-facing MEP.
Figure 5
CFD grading example
MEP list
A MEP list is a collection of configurable local MEPs and the remote MEPs to be monitored in the same
MA. It lists all MEPs configured on different devices in the same MA. The MEPs all have unique MEP IDs.
When a MEP receives from a remote device a continuity check message (CCM) with a MEP ID not
included in the MEP list of the MA, it drops the message.
CFD functions
CFD works effectively only in properly configured networks. Its functions, which are implemented through
the MPs, include:
Continuity check (CC)
Loopback (LB)
Linktrace (LT)
CC
Connectivity faults are usually caused by device faults or configuration errors. CC examines the
connectivity between MEPs. This function is implemented through periodic sending of continuity check
messages (CCMs) by the MEPs. A CCM sent by one MEP is intended to be received by all of the other
MEPs in the same MA. If a MEP fails to receive the CCMs within 3.5 times the sending interval, the link
is considered faulty and a log is generated. When multiple MEPs send CCMs at the same time, the
multipoint-to-multipoint link check is achieved. CCM frames are multicast frames.
LB
Similar to ping at the IP layer, LB verifies the connectivity between a source device and a target device.
To implement this function, the source MEP sends loopback messages (LBMs) to the target MEP.