Calling K2S, Kakatiya, Riddle

[ding]

[quote name='k2s' timestamp='1326376088' post='1301288745']
for an IP address to be assigned.....it should be a valid ...... here

172.30.0.0 = [color=#40e0d0]0000 0000[/color] | [color=#b22222]0000 0000 --------> ikkada all host bits are 0's.... for an IP address to be valid, neither subnet nor host bits [/color]
[color=#b22222] shud be 0's[/color]
255.255.255.0 = 1111 1111 | 0000 0000
-------------------------------------------------------------
[/quote]
loopback ki subnet number ivalemaa

[ding]

one last ques to all


R1(config)#router eigrp 90
R1(config-router)#network 172.30.0.0 0.0.255.255
R1(config-router)#network 10.1.0.0 0.0.255.255
R1(config-router)#exit
R1(config)#do sh ip pro
Routing Protocol is "eigrp 90"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 90
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is in effect
Automatic address summarization:
172.30.0.0/16 for Serial0/0, Serial0/1
Summarizing with metric 128256
10.0.0.0/8 for Loopback0, Loopback1, Loopback3
Loopback4, Loopback5, Loopback6
Loopback7, Loopback8
Summarizing with metric 2169856
Maximum path: 4
Routing for Networks:
[b][color=#ff0000] 10.1.0.0/16[/color][/b]
[b][color=#ff0000] 172.30.0.0[/color][/b]
Routing Information Sources:
Gateway Distance Last Update
(this router) 90 00:00:40

oka network ki mask chupinchindi inko daaniki chupinchaledu, y???????

[k2s]

[quote name='shakkku' timestamp='1326376590' post='1301288783']
loopback ki subnet number ivalemaa
[/quote]
no unless u exclusively configure ip subnet-zero
else
No interface can be assigned a subnet / network address

[k2s]

[quote name='shakkku' timestamp='1326377002' post='1301288816']
one last ques to all


R1(config)#router eigrp 90
R1(config-router)#network 172.30.0.0 0.0.255.255
R1(config-router)#network 10.1.0.0 0.0.255.255
R1(config-router)#exit
R1(config)#do sh ip pro
Routing Protocol is "eigrp 90"
Outgoing update filter list for all interfaces is not set
Incoming update filter list for all interfaces is not set
Default networks flagged in outgoing updates
Default networks accepted from incoming updates
EIGRP metric weight K1=1, K2=0, K3=1, K4=0, K5=0
EIGRP maximum hopcount 100
EIGRP maximum metric variance 1
Redistributing: eigrp 90
EIGRP NSF-aware route hold timer is 240s
Automatic network summarization is in effect
Automatic address summarization:
172.30.0.0/16 for Serial0/0, Serial0/1
Summarizing with metric 128256
10.0.0.0/8 for Loopback0, Loopback1, Loopback3
Loopback4, Loopback5, Loopback6
Loopback7, Loopback8
Summarizing with metric 2169856
Maximum path: 4
Routing for Networks:
[b][color=#ff0000] 10.1.0.0/16[/color][/b]
[b][color=#ff0000] 172.30.0.0[/color][/b]
Routing Information Sources:
Gateway Distance Last Update
(this router) 90 00:00:40

oka network ki mask chupinchindi inko daaniki chupinchaledu, y???????
[/quote]
2 reasons...
[list=1]
[*]By default EIGRP acts as IGRP ( classfull) protocol. ie, unless u exclusively mention "no auto-summary" under router eigrp config mode, it summarizes the network subnet to classfull
[*]If the nexthop interface or link address is not the boundary of subnets what u want to advertise, subnets will not be summerized ... i.e,
[/list]
R1<----------------->R2<----------------->R3
10.1.0.0/16 12.1.1.0/24

on R1:
Fa0/1 : 10.1.1.1/16
Lo1 : 172.23.16.1/32

on R2:
Fa0/2: 10.1.1.2/16
Fa0/3: 12.1.1.1/24
Lo2: 192.168.1.1/24

on R3:
Fa0/3 : 12.1.1.2/24
Lo3: 10.10.10.3/32


RouteTable on R1:

C 10.1.1.1/16 is directly connected
C 172.23.16.1/32 is directly connected
D 12.0.0.0/8 [90/xxx] via 10.1.1.2
D 192.168.1.0/24 [90/xxx] via 10.1.1.2

R3 Lo3 will be advertised to R2 thru 12 network so there ends boundary of 10 network... so 10 network ( R3's Lo3) is classfull summerized & adv to R2, & R2 see its routing table finds more specific route of directly connected 10.1.1.2 ( its Fa0/2) & never installs in its routing table & never forwards to R1.

R1 never knows about R3's loopback... so there is no fully connectivity in the network

Ur answer: akkada may 10.1.0.0/16 network is continuous till it reaches that router... & 172.30.0.0 is class B... if no mask is shown, it means its classfull default class B mask viz /16

[k2s]

[k2s]