Re: RIPv2 Over framerelay

ty all.!
Thanking You

Yours Sincerely

Divin Mathew John
divinjohn_at_gmail.com
divin_at_dide3d.com
http://www.dide3d.com
+91 9945430983
+91 9846697191
+974 5008916
PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
Sent from Bangalore, KA, India

On Sat, Apr 18, 2009 at 8:19 AM, Divin Mathew John <divinjohn_at_gmail.com> wrote:
> "Split horizon for Frame Relay and SMDS encapsulation is disabled by
> default. Split horizon is not disabled by default for interfaces using
> any of the X.25 encapsulations. For all other encapsulations, split
> horizon is enabled by default. "
>
> http://www.cisco.com/en/US/docs/ios/12_0/np1/configuration/guide/1crip.html#wp4813
> Thanking You
>
> Yours Sincerely
>
> Divin Mathew John
> divinjohn_at_gmail.com
> divin_at_dide3d.com
> http://www.dide3d.com
> +91 9945430983
> +91 9846697191
> +974 5008916
> PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
> Sent from Bangalore, KA, India
>
>
> On Sat, Apr 18, 2009 at 8:13 AM, Bryan Bartik <bbartik_at_ipexpert.com> wrote:
>> Divin,
>>
>> Also, remember EIGRP uses a different command that RIP for split-horizon.
>> And it is not disabled by default on Frame interfaces, unlike RIP.
>>
>> Bryan Bartik
>> CCIE #23707, CCNP
>> Sr. Support Engineer - IPexpert, Inc.
>> URL: http://www.IPexpert.com
>>
>> On Fri, Apr 17, 2009 at 8:39 PM, Divin Mathew John <divinjohn_at_gmail.com>
>> wrote:
>>>
>>> Are you talking about the split horizon being turned off by default on
>>> NBMA frame relay type connection?
>>> Thanking You
>>>
>>> Yours Sincerely
>>>
>>> Divin Mathew John
>>> divinjohn_at_gmail.com
>>> divin_at_dide3d.com
>>> http://www.dide3d.com
>>> +91 9945430983
>>> +91 9846697191
>>> +974 5008916
>>> PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
>>> Sent from Bangalore, KA, India
>>>
>>>
>>> On Sat, Apr 18, 2009 at 8:07 AM, Ryan West <rwest_at_zyedge.com> wrote:
>>> > Divin,
>>> >
>>> > RIP on NBMA main interfaces is disabled by default, but enabled on
>>> > subinterfaces and other encapsulation types.
>>> >
>>> > -ryan
>>> >
>>> > -----Original Message-----
>>> > From: nobody_at_groupstudy.com [mailto:nobody_at_groupstudy.com] On Behalf Of
>>> > Divin Mathew John
>>> > Sent: Friday, April 17, 2009 10:28 PM
>>> > To: Cisco certification
>>> > Subject: RIPv2 Over framerelay
>>> >
>>> > I kinda have a Hub and spoke topology.
>>> >
>>> > R2 is the Hub and R1 and R2 are the spokes. Now i ran RIPv2 on all the
>>> > routers. I did establish the layer-2 reach ability. Now to my suprise
>>> > without turning off splithorizon on the interface at R2 i seem to get
>>> > all the routes. Routes from both R1 and R2. there seems to be no
>>> > problems in the routing table . and i can reach all the loopbacks of
>>> > all the routers from anywhere on my topology. BUT. according to the
>>> > books we gotta disable split horizon on the interfaces for all routes
>>> > to appear on the routing table on all routers.! my config is as
>>> > follows
>>> >
>>> > R1
>>> >
>>> > interface Loopback0
>>> > ip address 1.1.1.1 255.255.255.0
>>> > !
>>> > interface Serial0/0
>>> > ip address 192.168.1.1 255.255.255.0
>>> > encapsulation frame-relay
>>> > serial restart-delay 0
>>> > clock rate 64000
>>> > frame-relay map ip 192.168.1.2 102 broadcast
>>> > frame-relay map ip 192.168.1.3 102 broadcast
>>> > no frame-relay inverse-arp
>>> > !
>>> > interface Serial0/1
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > interface Serial0/2
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > interface Serial0/3
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > router rip
>>> > version 2
>>> > network 1.0.0.0
>>> > network 192.168.1.0
>>> > no auto-summary
>>> > !
>>> > ip http server
>>> > no ip http secure-server
>>> > *******************************************************
>>> >
>>> > R2
>>> >
>>> > interface Loopback0
>>> > ip address 2.2.2.2 255.255.255.0
>>> > !
>>> > interface Serial0/0
>>> > ip address 192.168.1.2 255.255.255.0
>>> > encapsulation frame-relay
>>> > serial restart-delay 0
>>> > clock rate 64000
>>> > frame-relay map ip 192.168.1.1 201 broadcast
>>> > frame-relay map ip 192.168.1.3 203 broadcast
>>> > no frame-relay inverse-arp
>>> > !
>>> > interface Serial0/1
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > interface Serial0/2
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > interface Serial0/3
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > router rip
>>> > version 2
>>> > network 2.0.0.0
>>> > network 192.168.1.0
>>> > no auto-summary
>>> > !
>>> > ip http server
>>> > no ip http secure-server
>>> > !
>>> > !
>>> >
>>> > *******************************
>>> > R3
>>> >
>>> > interface Loopback0
>>> > ip address 3.3.3.3 255.255.255.0
>>> > !
>>> > interface Serial0/0
>>> > ip address 192.168.1.3 255.255.255.0
>>> > encapsulation frame-relay
>>> > serial restart-delay 0
>>> > clock rate 64000
>>> > frame-relay map ip 192.168.1.1 302 broadcast
>>> > frame-relay map ip 192.168.1.2 302 broadcast
>>> > no frame-relay inverse-arp
>>> > !
>>> > interface Serial0/1
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > interface Serial0/2
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > interface Serial0/3
>>> > no ip address
>>> > shutdown
>>> > serial restart-delay 0
>>> > !
>>> > router rip
>>> > version 2
>>> > network 3.0.0.0
>>> > network 192.168.1.0
>>> > no auto-summary
>>> > !
>>> > ip http server
>>> > no ip http secure-server
>>> > !
>>> >
>>> > ***********************************
>>> > R3#sh ip route
>>> > Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
>>> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
>>> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
>>> > E1 - OSPF external type 1, E2 - OSPF external type 2
>>> > i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS
>>> > level-2
>>> > ia - IS-IS inter area, * - candidate default, U - per-user static
>>> > route
>>> > o - ODR, P - periodic downloaded static route
>>> >
>>> > Gateway of last resort is not set
>>> >
>>> > 1.0.0.0/24 is subnetted, 1 subnets
>>> > R 1.1.1.0 [120/2] via 192.168.1.1, 00:00:24, Serial0/0
>>> > 2.0.0.0/24 is subnetted, 1 subnets
>>> > R 2.2.2.0 [120/1] via 192.168.1.2, 00:00:24, Serial0/0
>>> > 3.0.0.0/24 is subnetted, 1 subnets
>>> > C 3.3.3.0 is directly connected, Loopback0
>>> > C 192.168.1.0/24 is directly connected, Serial0/0
>>> >
>>> >
>>> > R1#sh ip route
>>> > Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
>>> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
>>> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
>>> > E1 - OSPF external type 1, E2 - OSPF external type 2
>>> > i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS
>>> > level-2
>>> > ia - IS-IS inter area, * - candidate default, U - per-user static
>>> > route
>>> > o - ODR, P - periodic downloaded static route
>>> >
>>> > Gateway of last resort is not set
>>> >
>>> > 1.0.0.0/24 is subnetted, 1 subnets
>>> > C 1.1.1.0 is directly connected, Loopback0
>>> > 2.0.0.0/24 is subnetted, 1 subnets
>>> > R 2.2.2.0 [120/1] via 192.168.1.2, 00:00:16, Serial0/0
>>> > 3.0.0.0/24 is subnetted, 1 subnets
>>> > R 3.3.3.0 [120/2] via 192.168.1.3, 00:00:16, Serial0/0
>>> > C 192.168.1.0/24 is directly connected, Serial0/0
>>> >
>>> > R2#sh ip route
>>> > Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
>>> > D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
>>> > N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
>>> > E1 - OSPF external type 1, E2 - OSPF external type 2
>>> > i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS
>>> > level-2
>>> > ia - IS-IS inter area, * - candidate default, U - per-user static
>>> > route
>>> > o - ODR, P - periodic downloaded static route
>>> >
>>> > Gateway of last resort is not set
>>> >
>>> > 1.0.0.0/24 is subnetted, 1 subnets
>>> > R 1.1.1.0 [120/1] via 192.168.1.1, 00:00:29, Serial0/0
>>> > 2.0.0.0/24 is subnetted, 1 subnets
>>> > C 2.2.2.0 is directly connected, Loopback0
>>> > 3.0.0.0/24 is subnetted, 1 subnets
>>> > R 3.3.3.0 [120/1] via 192.168.1.3, 00:00:10, Serial0/0
>>> > C 192.168.1.0/24 is directly connected, Serial0/0
>>> >
>>> > What am i missing here? . I tried with EIGRP too.. Split horizon seems
>>> > to be the problem there. R3 doesnt get R1's loopback and viceversa.!
>>> > Thanking You
>>> >
>>> > Yours Sincerely
>>> >
>>> > Divin Mathew John
>>> > divinjohn_at_gmail.com
>>> > divin_at_dide3d.com
>>> > http://www.dide3d.com
>>> > +91 9945430983
>>> > +91 9846697191
>>> > +974 5008916
>>> > PGP PUBLIC KEY BLOCK @ http://www.dide3d.com/divin_Public_PGP_key.txt
>>> >
>>> >
>>> > Blogs and organic groups at http://www.ccie.net
>>> >
>>> > _______________________________________________________________________
>>> > Subscription information may be found at:
>>> > http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>> Blogs and organic groups at http://www.ccie.net
>>>
>>> _______________________________________________________________________
>>> Subscription information may be found at:
>>> http://www.groupstudy.com/list/CCIELab.html
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>> --

Blogs and organic groups at http://www.ccie.net
Received on Sat Apr 18 2009 - 08:25:10 ART