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

Configuring CFD, Overview, Basic CFD concepts, MD, MA

Page 22 highlights

Configuring CFD Overview Connectivity Fault Detection (CFD) is an end-to-end per-VLAN link layer OAM mechanism used for link connectivity detection, fault verification, and fault location. It conforms to IEEE 802.1ag CFM. Basic CFD concepts This section explains the concepts of CFD. MD A maintenance domain (MD) defines the network or part of the network where CFD plays its role. An MD is identified by its MD name. To accurately locate faults, CFD assigns eight levels ranging from 0 to 7 to MDs. The bigger the number, the higher the level, and the larger the area covered. If the outer domain has a higher level than the nested one, domains can touch or nest, but they cannot intersect or overlap. MD levels facilitate fault location and its accuracy. As shown in Figure 3, MD_A in light blue nests MD_B in dark blue. If a connectivity fault is detected at the boundary of MD_A, any of the devices in MD_A, including Device A through Device E, may fail. If a connectivity fault is also detected at the boundary of MD_B, the failure points may be any of Device B through Device D. If the devices in MD_B can operate properly, at least Device C is operational. Figure 3 Two nested MDs CFD exchanges messages and performs operations on a per-domain basis. By planning MDs properly in a network, you can use CFD to rapidly locate failure points. MA A maintenance association (MA) is a part of an MD. You can configure multiple MAs in an MD as needed. An MA is identified by the "MD name + MA name". 15

  • 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

15
Configuring CFD
Overview
Connectivity Fault Detection (CFD) is an end-to-end per-VLAN link layer OAM mechanism used for link
connectivity detection, fault verification, and fault location. It conforms to IEEE 802.1ag CFM.
Basic CFD concepts
This section explains the concepts of CFD.
MD
A maintenance domain (MD) defines the network or part of the network where CFD plays its role. An MD
is identified by its MD name.
To accurately locate faults, CFD assigns eight levels ranging from 0 to 7 to MDs. The bigger the number,
the higher the level, and the larger the area covered. If the outer domain has a higher level than the
nested one, domains can touch or nest, but they cannot intersect or overlap.
MD levels facilitate fault location and its accuracy. As shown in
Figure 3
, MD_A in light blue nests MD_B
in dark blue. If a connectivity fault is detected at the boundary of MD_A, any of the devices in MD_A,
including Device A through Device E, may fail. If a connectivity fault is also detected at the boundary of
MD_B, the failure points may be any of Device B through Device D. If the devices in MD_B can operate
properly, at least Device C is operational.
Figure 3
Two nested MDs
CFD exchanges messages and performs operations on a per-domain basis. By planning MDs properly
in a network, you can use CFD to rapidly locate failure points.
MA
A maintenance association (MA) is a part of an MD. You can configure multiple MAs in an MD as
needed. An MA is identified by the "MD name + MA name".