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

Configuring a static route

Get HP 6125G PDF manuals and user guides View all HP 6125G manuals
Add to My Manuals
Save this manual to your list of manuals

Page 17 highlights

• Other attributes You can configure different priorities for different static routes so that route management policies can be more flexible. For example, specifying the same priority for different routes to the same destination enables load sharing, but specifying different priorities for these routes enables route backup. Configuring a static route Before you configure a static route, complete the following tasks: • Configure the physical parameters for related interfaces. • Configure the link-layer attributes for related interfaces. • Configure the IP addresses for related interfaces. Follow these guidelines when you configure a static route: • The next hop address cannot be the IP address of a local interface (such as Ethernet interface and VLAN interface). Otherwise, the static route does not take effect. • If you do not specify the preference when you configure a static route, the default preference applies. Reconfiguring the default preference applies only to newly created static routes. • You can flexibly control static routes by configuring tag values and using the tag values in the routing policy. • If the destination IP address and mask are both configured as 0.0.0.0 with the ip route-static command, then the route is the default route. • For more information about track, see High Availability Configuration Guide. To configure a static route: Step 1. Enter system view. 2. Configure a static route. Command Remarks system-view N/A • Approach 1: ip route-static dest-address { mask | mask-length } { next-hop-address [ track track-entry-number ] | interface-type interface-number [ next-hop-address ] | Use either approach. vpn-instance d-vpn-instance-name next-hop-address [ track track-entry-number ] } [ preference preference-value ] [ tag tag-value ] [ permanent ] [ description description-text ] By default, preference for static routes is 60, tag is 0, and no description information is configured. • Approach 2: ip route-static vpn-instance Do not specify the permanent s-vpn-instance-name& dest-address and track keywords { mask | mask-length } { next-hop-address simultaneously. [ public ] [ track track-entry-number ] | If the output interface is down, interface-type interface-number the permanent static route is [ next-hop-address ] | vpn-instance still active. d-vpn-instance-name next-hop-address [ track track-entry-number ] } [ preference preference-value ] [ tag tag-value ] [ permanent ] [ description description-text ] 7

  • 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
7
•
Other attributes
You can configure different priorities for different static routes so that route management policies
can be more flexible. For example, specifying the same priority for different routes to the same
destination enables load sharing, but specifying different priorities for these routes enables route
backup.
Configuring a static route
Before you configure a static route, complete the following tasks:
•
Configure the physical parameters for related interfaces.
•
Configure the link-layer attributes for related interfaces.
•
Configure the IP addresses for related interfaces.
Follow these guidelines when you configure a static route:
•
The next hop address cannot be the IP address of a local interface (such as Ethernet interface and
VLAN interface). Otherwise, the static route does not take effect.
•
If you do not specify the preference when you configure a static route, the default preference applies.
Reconfiguring the default preference applies only to newly created static routes.
•
You can flexibly control static routes by configuring tag values and using the tag values in the
routing policy.
•
If the destination IP address and mask are both configured as 0.0.0.0 with the
ip route-static
command, then the route is the default route.
•
For more information about track, see
High Availability Configuration Guide
.
To configure a static route:
Step
Command
Remarks
1.
Enter system view.
system-view
N/A
2.
Configure a static
route.
•
Approach 1:
ip
route-static
dest-address
{
mask
|
mask-length
} {
next-hop-address
[
track
track-entry-number
] |
interface-type
interface-number
[
next-hop-address
] |
vpn-instance
d-vpn-instance-name
next-hop-address
[
track
track-entry-numbe
r ] }
[
preference
preference-value
] [
tag
tag-value ]
[
permanent
] [
description
description-text
]
•
Approach 2:
ip route-static
vpn-instance
s-vpn-instance-nam
e&<1-6>
dest-address
{
mask
|
mask-length
} {
next-hop-address
[
public
] [
track
track-entry-number
] |
interface-type interface-number
[
next-hop-address
] |
vpn-instance
d-vpn-instance-name next-hop-address
[
track
track-entry-number
] } [
preference
preference-value
] [
tag
tag-value
]
[
permanent
] [
description
description-text
]
Use either approach.
By default,
preference
for
static routes is 60,
tag
is 0,
and no description
information is configured.
Do not specify the
permanent
and
track
keywords
simultaneously.
If the output interface is down,
the permanent static route is
still active.