HP 6125G HP 6125G & 6125G/XG Blade Switches Layer 3 - IP Routing Confi - Page 221

Configuring OSPFv3 network types, Configuration prerequisites

Page 221 highlights

Step 1. Enter system view. 2. Enter OSPFv3 view. 3. Enter OSPFv3 area view. 4. Configure a virtual link. Command system-view ospfv3 [ process-id ] area area-id vlink-peer router-id [ hello seconds | retransmit seconds | trans-delay seconds | dead seconds | instance instance-id ] * Configuring OSPFv3 network types OSPFv3 classifies networks into the following types by the link layer protocol. By default, the default OSPFv3 interface network types vary with the link layer protocols of the interfaces: • When the link layer protocol is PPP, OSPFv3 considers the network type as P2P by default. • When the link layer protocol is Ethernet, OSPFv3 considers the network type as broadcast by default. You can change the network type of an OSPFv3 interface as needed. For example: • An NBMA network must be fully connected. Any two routers in the network must be directly reachable to each other through a virtual circuit. If no such direct link is available, you must change the network type through a command. • If direct connections are not available between some routers in an NBMA network, the type of interfaces associated must be configured as P2MP, or as P2P for interfaces with only one neighbor. Configuration prerequisites Before you configure OSPFv3 network types, complete the following tasks: • Configure IPv6 functions. • Configure OSPFv3 basic functions. Configuring the OSPFv3 network type for an interface Step Command Remarks 1. Enter system view. system-view N/A 2. Enter interface view. interface interface-type interface-number N/A Optional. 3. Configure a network type for the OSPFv3 interface. ospfv3 network-type { broadcast | nbma | p2mp [ non-broadcast ] | p2p } [ instance instance-id ] The network type of an interface depends on the media type of the interface. Configuring an NBMA or P2MP neighbor For NBMA and P2MP interfaces (only when in unicast mode), specify the link-local IP addresses of their neighbors because these interfaces cannot find neighbors through broadcasting hello packets. You can also specify DR priorities for neighbors. 211

  • 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

211
Step
Command
1.
Enter system view.
system-view
2.
Enter OSPFv3 view.
ospfv3
[
process-id
]
3.
Enter OSPFv3 area view.
area
area-id
4.
Configure a virtual link.
vlink-peer
router-id
[
hello
seconds
|
retransmit
seconds
|
trans-delay
seconds
|
dead
seconds
|
instance
instance-id
] *
Configuring OSPFv3 network types
OSPFv3 classifies networks into the following types by the link layer protocol.
By default, the default OSPFv3 interface network types vary with the link layer protocols of the interfaces:
When the link layer protocol is PPP, OSPFv3 considers the network type as P2P by default.
When the link layer protocol is Ethernet, OSPFv3 considers the network type as broadcast by
default.
You can change the network type of an OSPFv3 interface as needed. For example:
An NBMA network must be fully connected. Any two routers in the network must be directly
reachable to each other through a virtual circuit. If no such direct link is available, you must change
the network type through a command.
If direct connections are not available between some routers in an NBMA network, the type of
interfaces associated must be configured as P2MP, or as P2P for interfaces with only one neighbor.
Configuration prerequisites
Before you configure OSPFv3 network types, complete the following tasks:
Configure IPv6 functions.
Configure OSPFv3 basic functions.
Configuring the OSPFv3 network type for an interface
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Enter interface view.
interface
interface-type
interface-number
N/A
3.
Configure a network type for
the OSPFv3 interface.
ospfv3 network-type
{
broadcast
|
nbma
|
p2mp
[
non-broadcast
] |
p2p
} [
instance
instance-id
]
Optional.
The network type of an interface
depends on the media type of the
interface.
Configuring an NBMA or P2MP neighbor
For NBMA and P2MP interfaces (only when in unicast mode), specify the link-local IP addresses of their
neighbors because these interfaces cannot find neighbors through broadcasting hello packets. You can
also specify DR priorities for neighbors.