HP 6120XG HP ProCurve Series 6120 Blade Switches Multicast and Routing Guide - Page 74

Enabling IP RIP on a VLAN, Changing the RIP Type on a VLAN Interface

Page 74 highlights

IP Routing Features Configuring RIP Note IP routing must be enabled prior to enabling RIP. The first command in the preceding sequence enables IP routing. Enabling IP RIP on a VLAN To enable RIP on all IP addresses in a VLAN, use ip rip in the VLAN context. when the command is entered without specifying any IP address, it is enabled in all configured IP addresses of the VLAN. To enable RIP on a specific IP address in a VLAN, use ip rip [< ip-addr >| all ] in the VLAN context and enter a specific IP address. If you want RIP enabled on all IP addresses, you can specify all in the command instead of a specific IP address. Changing the RIP Type on a VLAN Interface When you enable RIP on a VLAN interface, RIPv2-only is enabled by default. You can change the RIP type to one of the following on an individual VLAN interface basis: ■ Version 1 only ■ Version 2 only (the default) ■ Version 1 - or - version 2 To change the RIP type supported on a VLAN interface, enter commands such as the following: ProCurve(config)# vlan 1 ProCurve(vlan-1)# ip rip v1-only ProCurve(vlan-1)# exit ProCurve(config)# write memory Syntax: [no] ip rip < v1-only | v1-or-v2 | v2-only > Changing the Cost of Routes Learned on a VLAN Interface By default, the switch interface increases the cost of a RIP route that is learned on the interface. The switch increases the cost by adding one to the route's metric before storing the route. You can change the amount that an individual VLAN interface adds to the metric of RIP routes learned on the interface. 3-28

  • 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

IP Routing Features
Configuring RIP
Note
IP routing must be enabled prior to enabling RIP. The first command in the
preceding sequence enables IP routing.
Enabling IP RIP on a VLAN
To enable RIP on all IP addresses in a VLAN, use
ip rip
in the VLAN context.
when the command is entered without specifying any IP address, it is enabled
in all configured IP addresses of the VLAN.
To enable RIP on a specific IP address in a VLAN, use
ip rip [<
ip-addr >
| all ]
in
the VLAN context and enter a specific IP address. If you want RIP enabled on
all IP addresses, you can specify
all
in the command instead of a specific IP
address.
Changing the RIP Type on a VLAN Interface
When you enable RIP on a VLAN interface,
RIPv2-only
is enabled by default.
You can change the RIP type to one of the following on an individual VLAN
interface basis:
Version 1 only
Version 2 only (the default)
Version 1 - or - version 2
To change the RIP type supported on a VLAN interface, enter commands such
as the following:
ProCurve(config)# vlan 1
ProCurve(vlan-1)# ip rip v1-only
ProCurve(vlan-1)# exit
ProCurve(config)# write memory
Syntax:
[no] ip rip < v1-only | v1-or-v2 | v2-only >
Changing the Cost of Routes Learned on a VLAN Interface
By default, the switch interface increases the cost of a RIP route that is learned
on the interface. The switch increases the cost by adding one to the route's
metric before storing the route.
You can change the amount that an individual VLAN interface adds to the
metric of RIP routes learned on the interface.
3-28