How to Summarize subnets injected into OSPF by a virtual link? (And pay ATTENTION !!)
This is actually Lab 3-7 in the Cisco CCNP ROUTE Lab book.
I have a router that is connecting the following networks
Loopback 101 10.1.1.101/30 Area 200
Loopback 105 10.1.1.105/30 Area 200
Loopback 109 10.1.1.109/30 Area 200
Loopback 113 10.1.1.113/30 Area 200
Through a virtual link to Area 0.
Simple enuff at this point.
Now an objective wants me to sumamrize the above netowk to the most efficient summary.
Okay, so I figure area 200 range 10.1.1.96 255.255.255.224
Should do the trick...
No dice.. All the networks are still showing up in routing tables of all three routers..
I bang my head against this problem for like 30 minutes, wondering was there something special about virtual links that would "break" summaries?
Then, I finally caught that I had accidentally put in the command
netw 10.1.1.96 0.0.0.31 area 100
instead of:
netw 10.1.1.96 0.0.0.31 area 200
So I guess the lesson is this.. When you think you have the concepts down pretty good, and something does not work like you think it should, (especially you first few times configuring it) go back and check that you did not fat finger a command.
Russ
I have a router that is connecting the following networks
Loopback 101 10.1.1.101/30 Area 200
Loopback 105 10.1.1.105/30 Area 200
Loopback 109 10.1.1.109/30 Area 200
Loopback 113 10.1.1.113/30 Area 200
Through a virtual link to Area 0.
Simple enuff at this point.
Now an objective wants me to sumamrize the above netowk to the most efficient summary.
Okay, so I figure area 200 range 10.1.1.96 255.255.255.224
Should do the trick...
No dice.. All the networks are still showing up in routing tables of all three routers..
I bang my head against this problem for like 30 minutes, wondering was there something special about virtual links that would "break" summaries?
Then, I finally caught that I had accidentally put in the command
netw 10.1.1.96 0.0.0.31 area 100
instead of:
netw 10.1.1.96 0.0.0.31 area 200
So I guess the lesson is this.. When you think you have the concepts down pretty good, and something does not work like you think it should, (especially you first few times configuring it) go back and check that you did not fat finger a command.
Russ
Currently working on: CCNA:Security
Up next: CCNA:Voice
Up next: CCNA:Voice
Comments
-
Roguetadhg Member Posts: 2,489 ■■■■■■■■□□Yeah, that's a first lesson. It's always a good lesson to keep handy. it's amazing after the 10th lab of typing IP address, I'll rush and add an extra number to a loopback. It sucks, because that's where most of my time goes into figuring out "Why doesn't this ping work?...Oh, because Lo0 is "172.16.23.1 /24" instead of /25. I think I spent a good 1 hour trying to figure out why my tclsh didn't work one time, urgh. Oh well!
It's a lesson that plagued me from ICND1. Fat Fingers, or tripping up the numberpad!In order to succeed, your desire for success should be greater than your fear of failure.
TE Threads: How to study for the CCENT/CCNA, Introduction to Cisco Exams