Interesting- I was thinking timers and forgot about the DR and non-DR types
mismatch
Here is the results from labbing it up
The answer is it will not work by just making one change on R3 based on the
restrictions
NON-Broadcast and Point-to-Multipoint timers match and neighbors come up
but.......see the output below
R1
__
do sh ip sop inter serial 1/0
Serial1/0 is up, line protocol is up
Internet Address 192.168.1.1/24, Area 0
Process ID 1, Router ID 1.1.1.1, Network Type POINT_TO_MULTIPOINT, Cost:
64
Transmit Delay is 1 sec, State POINT_TO_MULTIPOINT
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5 -
Timers Match
oob-resync timeout 120
Hello due in 00:00:09
Supports Link-local Signaling (LLS)
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 1, maximum is 1
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 2, Adjacent neighbor count is 2
Adjacent with neighbor 3.3.3.3
Adjacent with neighbor 2.2.2.2
Suppress hello for 0 neighbor(s)
do sh ip ospf ne (beware as it may appear all is good)
Neighbor ID Pri State Dead Time Address Interface
3.3.3.3 0 FULL/ - 00:01:45 192.168.1.3 Serial1/0
2.2.2.2 0 FULL/ - 00:01:55 192.168.1.2 Serial1/0
do sh ip route (missing routes from R3)
1.0.0.0/32 is subnetted, 1 subnets
C 1.1.1.1 is directly connected, Loopback0
2.0.0.0/32 is subnetted, 1 subnets
O 2.2.2.2 [110/65] via 192.168.1.2, 00:02:15, Serial1/0
192.168.1.0/24 is variably subnetted, 2 subnets, 2 masks
C 192.168.1.0/24 is directly connected, Serial1/0
O 192.168.1.2/32 [110/64] via 192.168.1.2, 00:02:15, Serial1/0
R3
__
do sh ip ospf inte serial 1/0
Serial1/0 is up, line protocol is up
Internet Address 192.168.1.3/24, Area 0
Process ID 1, Router ID 3.3.3.3, Network Type NON_BROADCAST, Cost: 64
Transmit Delay is 1 sec, State DR, Priority 1
Designated Router (ID) 3.3.3.3, Interface address 192.168.1.3
Backup Designated router (ID) 1.1.1.1, Interface address 192.168.1.1
Timer intervals configured, Hello 30, Dead 120, Wait 120, Retransmit 5 -
Timers Match
oob-resync timeout 120
Hello due in 00:00:14
Supports Link-local Signaling (LLS)
Index 1/1, flood queue length 0
Next 0x0(0)/0x0(0)
Last flood scan length is 2, maximum is 2
Last flood scan time is 0 msec, maximum is 0 msec
Neighbor Count is 1, Adjacent neighbor count is 1
Adjacent with neighbor 1.1.1.1 (Backup Designated Router) - Believes
that 1.1.1.1 BDR
Suppress hello for 0 neighbor(s)
do sh ip ospf ne (beware as it may appear all is good)
Neighbor ID Pri State Dead Time Address Interface
1.1.1.1 1 FULL/BDR 00:01:54 192.168.1.1 Serial1/0
do sh ip route (no routes)
3.0.0.0/32 is subnetted, 1 subnets
C 3.3.3.3 is directly connected, Loopback0
C 192.168.1.0/24 is directly connected, Serial1/0
From: Di Bias, Steve [mailto:[email protected]]
Sent: October-13-10 8:35 PM
To: [email protected]; [email protected]
Subject: Re: [OSL | CCIE_RS] Troubleshooting
Sorry im on the road so if my words are mispelled you know why.
Maybe im confused but if im not allowed to chane anything on r3 what can we
do? You have another issue as well since nbma wants dr and
point-to-multipoint does not. Timers could be chaned but you cant mix dr
and non-dr types and still become adjacent so that wont work.
Since im driving i cant lab this up but i dont see how to make this work
correctly
Sent from my T-Mobile myTouch 3G Slide
----- Reply message -----
From: "Jason Maynard" <[email protected]>
Date: Wed, Oct 13, 2010 5:02 pm
Subject: [OSL | CCIE_RS] Troubleshooting
To: "Di Bias, Steve" <[email protected]>,
"[email protected]" <[email protected]>
Ok that works
I hope I am thinking correctly but here it goes, what if you have the
restriction as stated below and you were only allowed one command to
resolve the issue. Remember you have already resolved the issue in regards
to the IP address on R2
From: Di Bias, Steve [mailto:[email protected]]
Sent: October-13-10 7:45 PM
To: [email protected]; [email protected]; Di Bias, Steve
Subject: Re: [OSL | CCIE_RS] Troubleshooting
Sorry i meant neighbor statements :)
Sent from my T-Mobile myTouch 3G Slide
----- Reply message -----
From: "Di Bias, Steve" <[email protected]>
Date: Wed, Oct 13, 2010 4:40 pm
Subject: [OSL | CCIE_RS] Troubleshooting
To: "[email protected]" <[email protected]>,
"[email protected]" <[email protected]>
If the only restriction is on r3 you could change the first two to nbma, add
network statements and make r1 the dr
Sent from my T-Mobile myTouch 3G Slide
----- Reply message -----
From: "Jason Maynard" <[email protected]>
Date: Wed, Oct 13, 2010 4:27 pm
Subject: [OSL | CCIE_RS] Troubleshooting
To: "Di Bias, Steve" <[email protected]>,
"[email protected]" <[email protected]>
Correct! - I have added your comment to the blog -
What else could be done if there was a restriction to not change the network
type on R3?
From: Di Bias, Steve [mailto:[email protected]]
Sent: October-13-10 6:59 PM
To: Jason Maynard; [email protected]
Subject: RE: [OSL | CCIE_RS] Troubleshooting
We are quiet because we are studying, but I like challenges!!
The first issue I see is that R3 is configured for NBMA while R1 and R2 are
configured to use point-to-multipoint ospf network types. I'm not sure what
the restrictions are but changing the network type should bring up the
neighbor.
I also do notice a second thing with R2 which has a /30 netmask while R1 and
R3 have /24's. You may run into strange things with this config so if you
change it to match with a /24 you should now have full reachability.
So IP mismatch and network type mismatch is what I see here.
Steve
_____
From: [email protected]
[mailto:[email protected]] On Behalf Of Jason Maynard
Sent: Wednesday, October 13, 2010 2:43 PM
To: [email protected]
Subject: [OSL | CCIE_RS] Troubleshooting
I have noticed that the study list becomes very quiet at times so I want to
start some discussion to hopefully help all of us stay engaged
I have started to create a questions around troubleshooting on my blog. You
can lab it up to see all the issues or just look at the configuration to try
to identify all the issues.
Here is the link
http://packetsanalyzed.blogspot.com/2010/10/troubleshooting-1.html
Marko/Tyson: if you consider this spam please send me an email and I will no
longer include links to my blog when using OSL. - this is really to help
keep folks engaged and stir up additional discussions and further enhance
the learning experience.
UHS Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution of this information is prohibited, and may be
punishable by law. If this was sent to you in error, please notify the
sender by reply e-mail and destroy all copies of the original message.
UHS Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution of this information is prohibited, and may be
punishable by law. If this was sent to you in error, please notify the
sender by reply e-mail and destroy all copies of the original message.
UHS Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution of this information is prohibited, and may be
punishable by law. If this was sent to you in error, please notify the
sender by reply e-mail and destroy all copies of the original message.
UHS Confidentiality Notice: This e-mail message, including any attachments,
is for the sole use of the intended recipient(s) and may contain
confidential and privileged information. Any unauthorized review, use,
disclosure or distribution of this information is prohibited, and may be
punishable by law. If this was sent to you in error, please notify the
sender by reply e-mail and destroy all copies of the original message.
_______________________________________________
For more information regarding industry leading CCIE Lab training, please visit
www.ipexpert.com
