Dell PowerEdge M520 Dell PowerConnect M6220/M6348/M8024 Switches Configuration - Page 84

Routing Information Protocol, RIP Configuration

Get Dell PowerEdge M520 PDF manuals and user guides View all Dell PowerEdge M520 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 84 highlights

ipv6 ospf ipv6 ospf areaid 1 exit interface vlan 11 routing ip address 10.1.101.1 255.255.255.0 ipv6 address 3000:1:101::/64 eui64 ipv6 ospf ipv6 ospf areaid 2 exit ipv6 router ospf router-id 5.5.5.5 area 0.0.0.1 virtual-link 4.4.4.4 exit router ospf router-id 5.5.5.5 area 0.0.0.1 virtual-link 4.4.4.4 network 10.1.2.0 0.0.0.255 area 0.0.0.1 network 10.1.101.0 0.0.0.255 area 0.0.0.2 exit exit Routing Information Protocol Routing Information Protocol (RIP) is one of the protocols which may be used by routers to exchange network topology information. It is characterized as an "interior" gateway protocol, and is typically used in small to medium-sized networks. RIP Configuration A router running RIP sends the contents of its routing table to each of its adjacent routers every 30 seconds. When a route is removed from the routing table it is flagged as unusable by the receiving routers after 180 seconds, and removed from their tables after an additional 120 seconds. There are two versions of RIP: • RIP-1 defined in RFC 1058 - Routes are specified by IP destination network and hop count - The routing table is broadcast to all stations on the attached network • RIP-2 defined in RFC 1723 - Route specification is extended to include subnet mask and gateway - The routing table is sent to a multicast address, reducing network traffic - An authentication method is used for security 84 Routing Configuration

  • 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
84
Routing Configuration
ipv6 ospf
ipv6 ospf areaid 1
exit
interface vlan 11
routing
ip address 10.1.101.1 255.255.255.0
ipv6 address 3000:1:101::/64 eui64
ipv6 ospf
ipv6 ospf areaid 2
exit
ipv6 router ospf
router-id 5.5.5.5
area 0.0.0.1 virtual-link 4.4.4.4
exit
router ospf
router-id 5.5.5.5
area 0.0.0.1 virtual-link 4.4.4.4
network 10.1.2.0 0.0.0.255 area 0.0.0.1
network 10.1.101.0 0.0.0.255 area 0.0.0.2
exit
exit
Routing Information Protocol
Routing Information Protocol (RIP) is one of the protocols which may be used by routers to exchange
network topology information. It is characterized as an “interior” gateway protocol, and is typically used
in small to medium-sized networks.
RIP Configuration
A router running RIP sends the contents of its routing table to each of its adjacent routers every 30
seconds. When a route is removed from the routing table it is flagged as unusable by the receiving
routers after 180 seconds, and removed from their tables after an additional 120 seconds.
There are two versions of RIP:
•
RIP-1 defined in RFC 1058
–
Routes are specified by IP destination network and hop count
–
The routing table is broadcast to all stations on the attached network
•
RIP-2 defined in RFC 1723
–
Route specification is extended to include subnet mask and gateway
–
The routing table is sent to a multicast address, reducing network traffic
–
An authentication method is used for security