Question on Sixth Edition , Page 462

[Kent]

Hi,
I have a question on page 462 of the sixth edition.
From the output of sh ip protocols :
Corp#sh ip protocols
I noticed about the last section :
Routing Information Sources :
Gateway Distance Last Update
10.1.11.1 110 00:28:53
10.1.11.2 110 00:28:53
10.1.9.1 110 00:28:53
10.1.7.1 110 00:28:53
Based on my understanding , Gateway should be the interface that
connect to Corp Router but why does the CORP router show the Gateway
come from the Router that not connect to itself?
Morever , Gateway is not the routerID , Am I right?
By the way, What information that "Routing Information Sources :" would like to tell us?

:confused:

Would you please clarify this for me .
Actually , I try to create the lab (Packet Tracer 5.3) as FIGURE 7.3 and Out put of my mine was different as following :

Corp#sh ip protocols
Routing Protocol is "ospf 132"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 10.1.5.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
10.1.0.0 0.0.255.255 area 0
Routing Information Sources:
Gateway Distance Last Update
10.1.2.2 110 00:02:55
10.1.3.2 110 00:02:58
10.1.4.2 110 00:02:50
10.1.5.2 110 00:02:50
Distance: (default is 110)
Corp#

Thank You.
Kent

[Lion66six]

I'm struggling a little to understand the question. Can you post up the packet tracer lab so I can have a look at this for you.

[Kent]

Dear Sir

I am so sorry that my question is not clear.

The point is ,
Refer to Figure 7.3 of sixth edition page 427. When Todd configured OSPF on that network and showed the output on page 462.

I just wonder the output on page 462 that why the corp router return output on the GateWay section like below

on Page 462:

Corp#sh ip protocols
Routing Protocol is "ospf 132"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 10.1.5.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path:4
Routing for Networks:
10.1.1.1 0.0.0.0 area 0
10.1.2.1 0.0.0.0 area 0
10.1.3.1 0.0.0.0 area 0
10.1.4.1 0.0.0.0 area 0
10.1.5.1 0.0.0.0 area 0
Reference bandwidth unit is 100 mbps
Routing Information Sources :
Gateway Distance Last Update
10.1.11.1 110 00:28:53
10.1.11.2 110 00:28:53
10.1.9.1 110 00:28:53
10.1.7.1 110 00:28:53
Distance: (default is 110)
Corp#

Packet Tracer is quite a big program, I cannot upload it.


Thank You
Kent

[Lion66six]

1) A few misunderstandings. When I mentioned about packet tracer, I meant the small file for the network which is normally a pkt file. This is typically very small, only 100KB or less in size. Not to worry, I have loaded my version up from the last time I reviewed this chapter.

2) I don't have access to the 6th edition of the book, only the 7th edition. So I cannot refer to the exact page your on.

I have done the "show ip protocol" command on the Corp router in my simulation and it came back with the following output :

Corp#show ip pro

Routing Protocol is "ospf 100"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 192.168.100.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
10.1.1.0 0.0.0.3 area 0
10.1.1.4 0.0.0.3 area 0
10.1.1.8 0.0.0.3 area 0
10.1.2.0 0.0.0.255 area 0
10.1.3.0 0.0.0.255 area 0
10.1.4.0 0.0.0.255 area 0
10.1.5.0 0.0.0.255 area 0
192.168.100.0 0.0.0.255 area 0
Routing Information Sources:
Gateway Distance Last Update
192.168.20.1 110 00:00:20
192.168.40.1 110 00:00:19
192.168.100.1 110 00:00:19
Distance: (default is 110)


Is this different from what is written in the book, in particular the gateway section? Just to clarify if that is what your questioning?

[Kent]

Hi ,
Thank You for your help and sorry for my misunderstood.
I attached the packet tracer File I have used for reference When I used "sh ip protocols"
Here is my output
Corp#sh ip protocols
Routing Protocol is "ospf 132"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 10.1.5.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
10.1.0.0 0.0.255.255 area 0
Routing Information Sources:
Gateway Distance Last Update
10.1.2.2 110 00:00:00
10.1.3.2 110 00:00:00
10.1.4.2 110 00:00:02
10.1.5.2 110 00:00:02
Distance: (default is 110)
Corp#

But When I read the sixth edition , it showed me the different output
Corp#sh ip protocols
Routing Protocol is "ospf 132"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 10.1.5.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path:4
Routing for Networks:
10.1.1.1 0.0.0.0 area 0
10.1.2.1 0.0.0.0 area 0
10.1.3.1 0.0.0.0 area 0
10.1.4.1 0.0.0.0 area 0
10.1.5.1 0.0.0.0 area 0
Reference bandwidth unit is 100 mbps
Routing Information Sources :
Gateway Distance Last Update
10.1.11.1 110 00:28:53
10.1.11.2 110 00:28:53
10.1.9.1 110 00:28:53
10.1.7.1 110 00:28:53
Distance: (default is 110)
Corp#

My question is why does 10.1.11.2 can be the gateway , it was not connect directly with corp router? and the other ip such as 10.1.9.1 , 10.1.7.1 were also not the interface connect directly to CORP router.

By the way , on your Lab you showed me , Every IP on Gateway is the interface connect directly to CORP router ? can you share me lab file ?

Thank You again,
Kent

[schizmark]

Hi ,
Thank You for your help and sorry for my misunderstood.
I attached the packet tracer File I have used for reference When I used "sh ip protocols"
Here is my output
Corp#sh ip protocols
Routing Protocol is "ospf 132"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 10.1.5.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path: 4
Routing for Networks:
10.1.0.0 0.0.255.255 area 0
Routing Information Sources:
Gateway Distance Last Update
10.1.2.2 110 00:00:00
10.1.3.2 110 00:00:00
10.1.4.2 110 00:00:02
10.1.5.2 110 00:00:02
Distance: (default is 110)
Corp#

But When I read the sixth edition , it showed me the different output
Corp#sh ip protocols
Routing Protocol is "ospf 132"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Router ID 10.1.5.1
Number of areas in this router is 1. 1 normal 0 stub 0 nssa
Maximum path:4
Routing for Networks:
10.1.1.1 0.0.0.0 area 0
10.1.2.1 0.0.0.0 area 0
10.1.3.1 0.0.0.0 area 0
10.1.4.1 0.0.0.0 area 0
10.1.5.1 0.0.0.0 area 0
Reference bandwidth unit is 100 mbps
Routing Information Sources :
Gateway Distance Last Update
10.1.11.1 110 00:28:53
10.1.11.2 110 00:28:53
10.1.9.1 110 00:28:53
10.1.7.1 110 00:28:53
Distance: (default is 110)
Corp#

My question is why does 10.1.11.2 can be the gateway , it was not connect directly with corp router? and the other ip such as 10.1.9.1 , 10.1.7.1 were also not the interface connect directly to CORP router.

By the way , on your Lab you showed me , Every IP on Gateway is the interface connect directly to CORP router ? can you share me lab file ?

Thank You again,
Kent

I'm new to this forum, but I can tell you that, from what I've seen in the book (I'm also using sixth ed.), the author doesn't realize that some of us are detail-oriented enough to notice things he doesn't expect us to. For example, his printout from R3 on page 432 shows f0/0 and s0/0/0 being set as passive interfaces. His diagram shows nothing connected on the s0/0/0 int of R3 (which would make the passive designation unnecessary) and a host on f0/1.
There are many other examples througout the book. My point is that the specific configuration he has for this arrangement may be different than what is depicted, and he has made adjustments for the sake of the book, which he then reverses, so he can continue playing with setups on his own time.
I'm sorry if this isn't the specific answer you wanted, but I hope it helps relieve the frustration I fully expect you to experience when reading future such printouts.

[Big Evil]

I'm new to this forum, but I can tell you that, from what I've seen in the book (I'm also using sixth ed.), the author doesn't realize that some of us are detail-oriented enough to notice things he doesn't expect us to.

Really????

[schizmark]

Really????

Not, in any way, meant as an insult; just information. There were a number of times I found myself frustrated over printouts like that, and combed through the chapters I'd read looking for something I missed. It was only yesterday, after my post, that I realized the table for the network described didn't match the diagram. In the diagram, s0/0/1 connects to 10.1.5.2, but in the table the s0/0/0 interface is used. After that, it appeared to me that the author had set the two interfaces as passive in order to avoid propagating his changes to parts of the network he didn't want affected, making reversing the change easier. Go figure.

[Big Evil]

I am sure once Todd "the author" reads this he will state why.