From: ISolveSystems (support@isolvesystems.com)
Date: Tue Aug 07 2007 - 14:18:52 ART
Yes, I can ping from R4/R5 to Lo0 of R1 and R3.
*R1*
Rack1R1(config-pmap-c)#do sh run int s0/0/0
Building configuration...
Current configuration : 583 bytes
!
interface Serial0/0/0
ip address 174.1.145.1 255.255.255.0
ip pim nbma-mode
ip pim sparse-dense-mode
encapsulation frame-relay
delay 10
ipv6 address 2001:CC1E:1:1515::1/64
ipv6 ospf neighbor FE80::215:FAFF:FED7:6B68
ipv6 ospf 1 area 0
no fair-queue
frame-relay class FRTS
frame-relay traffic-shaping
frame-relay map ip 174.1.145.4 104 broadcast
frame-relay map ip 174.1.145.5 105 broadcast
frame-relay map ipv6 FE80::215:FAFF:FED7:6B68 105 broadcast
frame-relay map ipv6 2001:CC1E:1:1515::5 105 broadcast
no frame-relay inverse-arp
frame-relay lmi-type cisco
end
*R3*
interface Serial0/2/0
ip address 174.1.13.3 255.255.255.0
ip pim sparse-dense-mode
service-policy output AUDIO
end
*R4*
interface Serial0/0/0
bandwidth 100000
ip address 174.1.145.4 255.255.255.0
ip pim dr-priority 0
ip pim sparse-dense-mode
encapsulation frame-relay
delay 1
no fair-queue
frame-relay class FRTS
frame-relay traffic-shaping
frame-relay map ip 174.1.145.1 401 broadcast
frame-relay map ip 174.1.145.5 401
no frame-relay inverse-arp
frame-relay lmi-type cisco
*R5*
interface Serial0/0/0
bandwidth 1000000
ip address 174.1.145.5 255.255.255.0
ip pim dr-priority 0
ip pim sparse-dense-mode
encapsulation frame-relay
ipv6 address 2001:CC1E:1:1515::5/64
ipv6 ospf priority 0
ipv6 ospf 1 area 0
no fair-queue
frame-relay class FRTS
frame-relay traffic-shaping
frame-relay map ip 174.1.145.1 501 broadcast
frame-relay map ip 174.1.145.4 501
frame-relay map ipv6 FE80::217:EFF:FEAF:8738 501 broadcast
frame-relay map ipv6 2001:CC1E:1:1515::1 501 broadcast
no frame-relay inverse-arp
frame-relay lmi-type cisco
end
On 8/7/07, Serhat Aslan <serhatworks@gmail.com> wrote:
>
> Those are the not configs that I wanted, I mean the running-config. If
> you can ping ->from serial interface of R4-R5 to loopback of routers, and if
> there is no error the separation and mapping with access-lists on both
> RP(s) and agent configuration, the system must work. It is very straight
> forward configuration.
>
> Serhat Aslan
>
>
> On 8/7/07, ISolveSystems <support@isolvesystems.com> wrote:
> >
> > Below shows R4 R5 pim enabled interfaces and neighbours. What other
> > config do you want?
> >
> > *R4*
> >
> > Rack1R4#sh ip pim int
> >
> > Address Interface Ver/ Nbr Query DR DR
> > Mode Count Intvl Prior
> > 174.1.4.4 FastEthernet0/0 v2/SD 0 30 1
> > 174.1.4.4
> > 174.1.145.4 Serial0/0/0 v2/SD 2 30 0
> > 174.1.145.1
> >
> > Rack1R4(config)#do sh ip pim nei
> > PIM Neighbor Table
> > Mode: B - Bidir Capable, DR - Designated Router, N - Default DR
> > Priority,
> > S - State Refresh Capable
> > Neighbor Interface Uptime/Expires Ver DR
> > Address
> > Prio/Mode
> > 174.1.145.1 Serial0/0/0 00:52:30/00:01:27 v2 1 /
> > DR S
> > 174.1.145.5 Serial0/0/0 00:52:31/00:01:27 v2 0 / S
> >
> > *R5*
> >
> > Rack1R5#sh ip pim int
> >
> > Address Interface Ver/ Nbr Query DR DR
> > Mode Count Intvl Prior
> > 174.1.145.5 Serial0/0/0 v2/SD 2 30 0
> > 174.1.145.1
> > 192.10.1.5 FastEthernet0/1.52 v2/SD 0 30 1
> > 192.10.1.5
> > Rack1R5#ping 150.1.1.1
> >
> >
> >
> >
> >
> > On 8/7/07, Serhat Aslan <serhatworks@gmail.com > wrote:
> > >
> > > Did you check the unicast reachability of rp/agent to clients and pim
> > > enable interfaces ? if you did can you send the config ?
> > >
> > >
> > > Serhat Aslan
> > >
> > >
> > > On 8/7/07, ISolveSystems < support@isolvesystems.com> wrote:
> > >
> > > > I have tried the nbmp mode with same result.
> > > >
> > > > I have the broadcase keyword...
> > > > frame-relay map ip 174.1.145.4 104 broadcast
> > > > frame-relay map ip 174.1.145.5 105 broadcast
> > > >
> > > >
> > > > On 8/7/07, Salau, Yemi < yemi.salau@siemens.com> wrote:
> > > > >
> > > > > 1. tried ip pim nbma-mode on R1's serial interface?
> > > > > 2. Sure the FR interfaces/dlcis are broadcast compatible? ie.
> > > > > Frame-relay map with broadcast keyword?
> > > > >
> > > > > -----Original Message-----
> > > > > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com ] On
> > > > Behalf Of
> > > > > ISolveSystems
> > > > > Sent: Tuesday, August 07, 2007 3:43 PM
> > > > > To: Group study
> > > > > Subject: RP mapping info not received
> > > > >
> > > > > Hello Expert,
> > > > > R1, R4, R5 are full meshed FR. R1 is the RP. R3 is the mapping
> > > > agent.
> > > > > All connected interfaces are configured with pim sparse dense mode
> > > > and
> > > > > are
> > > > > all neighbor up.
> > > > >
> > > > > For some reason R4 and R5 are not receiving rp mapping from
> > > > R3. Any
> > > > > idea?
> > > > >
> > > > > R4
> > > > > \
> > > > > \
> > > > > R1-----R3----R2
> > > > > /
> > > > > /
> > > > > R5
> > > > >
> > > > > Thanks.
> > > > >
> > > > >
> > > > _______________________________________________________________________
> > > > > Subscription information may be found at:
> > > > > http://www.groupstudy.com/list/CCIELab.html
> > > >
> > > > _______________________________________________________________________
> > > >
> > > > Subscription information may be found at:
> > > > http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:09 ART