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

Configuration procedure, Configuring LB on MEPs

Page 29 highlights

Table 9 Relationship between the interval field value in the CCM message, the interval between CCM messages, and the timeout time of the remote MEP The interval field value in The interval between CCM the CCM message messages 4 1 second 5 10 second 6 60 seconds 7 600 seconds The timeout time of the remote MEP 3.5 seconds 35 seconds 210 seconds 2100 seconds Configuration procedure To configure CC on a MEP: Step 1. Enter system view. Command system-view 2. Configure the interval field value in the CCM messages cfd cc interval interval-value sent by MEPs. service-instance instance-id 3. Enter Layer 2 Ethernet interface interface interface-type view. interface-number 4. Enable CCM sending on a cfd cc service-instance instance-id MEP. mep mep-id enable Remarks N/A Optional. By default, the interval field value is 4. N/A By default, CCM sending on a MEP is disabled. Configuring LB on MEPs The LB function can verify the link state between the local MEP and the remote MEP or MIP. To configure LB on a MEP: Task Enable LB. Command Remarks cfd loopback service-instance instance-id mep mep-id { target-mep target-mep-id | target-mac mac-address } [ number number ] By default, LB is disabled. Available in any view. Configuring LT on MEPs LT can trace the path between the source and target MEPs, and can also locate link faults by sending LT messages automatically. The two functions are implemented in the following way: • To implement the first function, the source MEP first sends LTM messages to the target MEP. Based on the LTR messages in response to the LTM messages, the path between the two MEPs can be identified. • In the latter case, after LT messages automatic sending is enabled, if the source MEP fails to receive the CCM frames from the target MEP within 3.5 times the transmission interval, the link between the two is considered faulty. LTM frames will be sent out with the target MEP as the destination and the 22

  • 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

22
Table 9
Relationship between the interval field value in the CCM message, the interval between CCM
messages, and the timeout time of the remote MEP
The interval field value in
the CCM message
The interval between CCM
messages
The timeout time of the remote MEP
4
1 second
3.5 seconds
5
10 second
35 seconds
6
60 seconds
210 seconds
7
600 seconds
2100 seconds
Configuration procedure
To configure CC on a MEP:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure the interval field
value in the CCM messages
sent by MEPs.
cfd cc interval
interval-value
service-instance
instance-id
Optional.
By default, the interval field value is
4.
3.
Enter Layer 2 Ethernet interface
view.
interface
interface-type
interface-number
N/A
4.
Enable CCM sending on a
MEP.
cfd cc service-instance
instance-id
mep
mep-id
enable
By default, CCM sending on a MEP
is disabled.
Configuring LB on MEPs
The LB function can verify the link state between the local MEP and the remote MEP or MIP.
To configure LB on a MEP:
Task
Command
Remarks
Enable LB.
cfd loopback service-instance
instance-id
mep
mep-id
{
target-mep
target-mep-id
|
target-mac
mac-address
} [
number
number
]
By default, LB is disabled.
Available in any view.
Configuring LT on MEPs
LT can trace the path between the source and target MEPs, and can also locate link faults by sending LT
messages automatically. The two functions are implemented in the following way:
To implement the first function, the source MEP first sends LTM messages to the target MEP. Based
on the LTR messages in response to the LTM messages, the path between the two MEPs can be
identified.
In the latter case, after LT messages automatic sending is enabled, if the source MEP fails to receive
the CCM frames from the target MEP within 3.5 times the transmission interval, the link between the
two is considered faulty. LTM frames will be sent out with the target MEP as the destination and the