RIP not working on 2821/12.4.20T
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
|||||||||||||||||||||||||||||||
|
Posted by Karsten Fischer on August 22, 2008, 1:43 pm
Please log in for more thread options Hello, if i configure rip on a 2821 box there`s not error message. But RIP doesn't work, and the configured lines are not visible in the configuration!? Any Ideas? Regards, Karsten | |||||||||||||||||||||||||||||||
|
Posted by Trendkill on August 22, 2008, 3:05 pm
Please log in for more thread options They are not showing up in 'show run'? I'm sure this is not the case, but you aren't doing 'show start' and haven't done a write mem or copy run start right? Please define rip is not working...do you have a neighbor? What does show ip protocol say (please paste)? | |||||||||||||||||||||||||||||||
|
Posted by Scott Perry on August 22, 2008, 5:39 pm
Please log in for more thread options
RIP requires that the interfaces are configured with an IP address, are not shutdown, have a working communication path to the other router, and have the adjoining interfaces advertised with the network command in the RIP configuration. Here is a sample RIP configuration for two routers directly connected through a switch: Router R1: FastEthernet0/0 ip address 192.168.1.1 255.255.255.252 Loopback0 ip address 172.31.1.0 255.255.255.192 Router R2: FastEthernet0/0 ip address 192.168.1.2 255.255.255.252 Loopback0 ip address 172.31.2.0 255.255.255.192 Configuration Commands for R1: router rip version 2 network 192.168.1.0 0.0.0.3 network 172.31.1.0 0.0.0.63 Configuration Commands for R2: router rip version 2 network 192.168.1.0 0.0.0.3 network 172.31.1.0 0.0.0.63 You should be able to see the 172.31.1.0/26 network in the R2 routing table and the 172.31.2.0/26 network in the R1 routing table. ----- Scott Perry Indianapolis, IN ----- > Hello,
> > if i configure rip on a 2821 box there`s not error message. But RIP > doesn't work, and the configured lines are not visible in the > configuration!? > > Any Ideas? > > Regards, > > Karsten They are not showing up in 'show run'? I'm sure this is not the case, but you aren't doing 'show start' and haven't done a write mem or copy run start right? Please define rip is not working...do you have a neighbor? What does show ip protocol say (please paste)? | |||||||||||||||||||||||||||||||
|
Posted by News Reader on August 22, 2008, 8:16 pm
Please log in for more thread options
Scott Perry wrote: > RIP requires that the interfaces are configured with an IP address, are not
> shutdown, have a working communication path to the other router, and have > the adjoining interfaces advertised with the network command in the RIP > configuration. > Here is a sample RIP configuration for two routers directly connected > through a switch: > > Router R1: > FastEthernet0/0 > ip address 192.168.1.1 255.255.255.252 > Loopback0 > ip address 172.31.1.0 255.255.255.192 That's not an assignable host address, that's a network ID. Network ID: 172.31.1.0 Host range: 172.31.1.1 - 172.31.1.62 Broadcast: 172.31.1.63 >
> Router R2: > FastEthernet0/0 > ip address 192.168.1.2 255.255.255.252 > Loopback0 > ip address 172.31.2.0 255.255.255.192 That's not an assignable host address, that's a network ID. Network ID: 172.31.2.0 Host range: 172.31.2.1 - 172.31.2.62 Broadcast: 172.31.2.63 >
> Configuration Commands for R1: > > router rip > version 2 > network 192.168.1.0 0.0.0.3 > network 172.31.1.0 0.0.0.63 Specifying a mask with RIP network command? >
> Configuration Commands for R2: > > router rip > version 2 > network 192.168.1.0 0.0.0.3 > network 172.31.1.0 0.0.0.63 network 172.31.2.0, not network 172.31.1.0 Specifying a mask with RIP network command? >
> You should be able to see the 172.31.1.0/26 network in the R2 routing table > and the 172.31.2.0/26 network in the R1 routing table. > > ----- > Scott Perry > Indianapolis, IN > ----- > Best Regards, News Reader | |||||||||||||||||||||||||||||||
|
Posted by Scott Perry on August 25, 2008, 9:12 am
Please log in for more thread options
RIGHT! You got me! Now why didn't you put a corrected version up, Newsreader? THIS configuration was tested on two routers connected to each other via FastEthernet, not from memory like my last posting: R1 interface Loopback0 ip address 172.31.1.1 255.255.255.192 ! interface FastEthernet0/0 ip address 192.168.1.1 255.255.255.252 ! router rip version 2 network 172.31.1.0 network 192.168.1.0 R2 interface Loopback0 ip address 172.31.2.1 255.255.255.192 ! interface FastEthernet0/0 ip address 192.168.1.2 255.255.255.252 ! router rip version 2 network 172.31.1.0 network 192.168.1.0 The configuration will revert back to where the RIP configuration has "network 172.31.0.0" instead of what was entered. Again, make sure that the two routers running RIP have a good connection to each other, have interfaces up that will be advertised through RIP, and both are advertising the network range which they use to connect to each other. Use the command "show ip rip database" for some more information. ----- Scott Perry Indianapolis, IN ----- > Scott Perry wrote:
>> RIP requires that the interfaces are configured with an IP address, are
>> not shutdown, have a working communication path to the other router, and >> have the adjoining interfaces advertised with the network command in the >> RIP configuration. >> Here is a sample RIP configuration for two routers directly connected >> through a switch: >> >> Router R1: >> FastEthernet0/0 >> ip address 192.168.1.1 255.255.255.252 >> Loopback0 >> ip address 172.31.1.0 255.255.255.192 >
> That's not an assignable host address, that's a network ID. > > Network ID: 172.31.1.0 Host range: 172.31.1.1 - 172.31.1.62 Broadcast: > 172.31.1.63 > >>
>> Router R2: >> FastEthernet0/0 >> ip address 192.168.1.2 255.255.255.252 >> Loopback0 >> ip address 172.31.2.0 255.255.255.192 >
> That's not an assignable host address, that's a network ID. > > Network ID: 172.31.2.0 Host range: 172.31.2.1 - 172.31.2.62 Broadcast: > 172.31.2.63 > >>
>> Configuration Commands for R1: >> >> router rip >> version 2 >> network 192.168.1.0 0.0.0.3 >> network 172.31.1.0 0.0.0.63 >
> Specifying a mask with RIP network command? > >>
>> Configuration Commands for R2: >> >> router rip >> version 2 >> network 192.168.1.0 0.0.0.3 >> network 172.31.1.0 0.0.0.63 >
> network 172.31.2.0, not network 172.31.1.0 > > Specifying a mask with RIP network command? > >>
>> You should be able to see the 172.31.1.0/26 network in the R2 routing >> table and the 172.31.2.0/26 network in the R1 routing table. >> >> ----- >> Scott Perry >> Indianapolis, IN >> ----- >> >
> Best Regards, > News Reader | |||||||||||||||||||||||||||||||
| Similar Threads | Posted |
| Call transfer full consult is not working properly, blind transfer is working instead | October 8, 2008, 8:04 pm |
| sh cdp n not working | September 1, 2005, 9:31 am |
| VPN working | October 7, 2005, 4:17 am |
| PBR not working | March 9, 2006, 3:02 pm |
| NAT/PAT not working in PIX 515 | April 27, 2006, 10:45 pm |
| QoS not working | February 26, 2007, 12:43 pm |
| PAT not working :-( | March 8, 2007, 3:38 pm |
| NTP not working? | April 4, 2007, 5:10 pm |
| PAT not working | April 9, 2007, 4:16 am |
| Help, FTP thru ASA not working | July 4, 2007, 6:04 pm |
| Cisco SDM is not working | July 11, 2005, 8:07 am |
| SSH stops working | July 17, 2005, 10:14 pm |
| "no shutdown" not working | July 22, 2005, 3:43 pm |
| Static NAT is not working | August 12, 2005, 6:21 am |
| crypto map not working | August 30, 2005, 10:59 am |
>
> if i configure rip on a 2821 box there`s not error message. But RIP
> doesn't work, and the configured lines are not visible in the
> configuration!?
>
> Any Ideas?
>
> Regards,
>
> Karsten