peterh1975
asked on
RIP done correctly???
Cisco Gurus,
I am currently learning routing on my own, i have a 2 routers. RouterA 1.1.1.1 and Routerb 2.2.2.2, i did not know how to do the static route so i type this command in IP ROUTE 0.0.0.0 0.0.0.0 2.2.2.2 on RouterA as well as RouterB 0.0.0.0 0.0.0.0.0 1.1.1.1.
When i did a SHOW IP ROUTE it gave me a read out of S* which shows i am in static connections. So i assume i have this correct? i have no seariel connections to this, i am currently using the ethernet port to these routers with a public static ip address.
When i go in to global mode on RouterA and RouterB typed NETWORK 2.2.2.2 and exit back to priv mode and i typed DEBUG IP RIP.Then it states that rip is turned on and RouterA starts to to send packtes and says something like supressing null but does not show any metric nor hop like the book shows? but RouterB does not show what RouterA does, is it working?? i am learning this from the book and the book shows it has a metric and hop i think ?when it starts to supress. So am i doing this right?? i am new at this so if u can help me in a step by step command to show me???
I am currently learning routing on my own, i have a 2 routers. RouterA 1.1.1.1 and Routerb 2.2.2.2, i did not know how to do the static route so i type this command in IP ROUTE 0.0.0.0 0.0.0.0 2.2.2.2 on RouterA as well as RouterB 0.0.0.0 0.0.0.0.0 1.1.1.1.
When i did a SHOW IP ROUTE it gave me a read out of S* which shows i am in static connections. So i assume i have this correct? i have no seariel connections to this, i am currently using the ethernet port to these routers with a public static ip address.
When i go in to global mode on RouterA and RouterB typed NETWORK 2.2.2.2 and exit back to priv mode and i typed DEBUG IP RIP.Then it states that rip is turned on and RouterA starts to to send packtes and says something like supressing null but does not show any metric nor hop like the book shows? but RouterB does not show what RouterA does, is it working?? i am learning this from the book and the book shows it has a metric and hop i think ?when it starts to supress. So am i doing this right?? i am new at this so if u can help me in a step by step command to show me???
ASKER
Thanks for the super fast reply! so am i better off using the serial to learn this? sorry i am so new to routing and stuff. I am confuse about the part where i put network 1.0.0.0??? i thought u have to put the IP of the router itself?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ooohh.....thanks lrmoore. i`ll try that soon as i get a dte 2 dce cable. am i diffently keep you posted for sure!
Your the bomb !
Your the bomb !
ASKER
ooohh.....thanks lrmoore. i`ll try that soon as i get a dte 2 dce cable. am i diffently keep you posted for sure!
Your the bomb !
Your the bomb !
ASKER
I am gonna do a NAT question also...maybe u can help me too!?
what lrmoore said is perfectly right.
Whenever you connect two routers, the connection between them must be on the same IP network. Since you are using the Ethernet ports, I would use something like:
A:
Interface Ethernet 0
ip add 1.1.1.1 255.255.255.0
B:
Interface Ethernet 0
ip add 1.1.1.2 255.255.255.0
Since they are on the same network, there really is no routing happening and no static routes to put in, and no routes to broadcast via RIP.
What you can do is artificially keep your serial interface up with an ip address assigned:
A:
Interface serial 0
no shutdown
no keepalive
ip add 2.2.2.1 255.255.255.0
B:
Interface serial 0
no shut
no keep
ip add 2.2.3.1 255.255.255.0
Now, if you just want to watch RIP happen:
Both A and B:
router rip
network 1.0.0.0
network 2.0.0.0
First, on both routers, make sure all interfaces show as up, and none of them are administratively down:
router>sho ip interface brief
Now you should be able to watch the RIP through your debug..
Are you connecting directly to the console port of both routers when trying to watch the debug? If you telnet into it, you will not see the debug messages without first issueing the command "term mon" at the priveleged prompt
router#term mon