From: Alan Basinger (abasinge@xxxxxxxxxx)
Date: Wed Jan 17 2001 - 14:13:24 GMT-3
I have a partial mesh NBMA with multiple routers using Multipoint
interfaces,(cciebootcamp) lab number 9 layout with a twist of my own). I am
trying to add PIM to the lab and have it working in all routers except over
the NBMA cloud. It has some interesting DLCI mappings that make it difficult
to use auto RP. I can't seem to figure out were to place the MA's correctly.
I can't draw the scenario here but would like to discuss how this may work
with the types of DLCI mappings used in the scenario. I used r2 as the RP,
but now have it all messed up hahah.
r1 dlci 102 maps to r2 DLCI 201
r2 dlci 402 maps to r3 dlci 102
r3 dlci 104 maps to r4 dlci 410
r2 and r3 have 2 subinterfaces
r2 maps to r1 and r3
r3 maps to r2 and r4
Regards,
Alan Basinger
Systems Engineer
SBC DataComm
Houston Texas
abasinge@swbell.net
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Wu Jiang
Sent: Wednesday, January 17, 2001 1:48 AM
To: Claude-Vincent; Allyn Baskerville; 'Brian Hescock'; Robert DeVito
Cc: ccielab@groupstudy.com
Subject: Re: auto-rp and frame-relay
Haven't read all the mails. Is this what you are saying?
ftp://ftpeng.cisco.com/ipmulticast/autorp.html
----- Original Message -----
From: "Claude-Vincent" <claude_vincent@yahoo.com>
To: "Allyn Baskerville" <abaskerville@ibeam.com>; "'Brian Hescock'"
<bhescock@cisco.com>; "Robert DeVito" <robertdevito@hotmail.com>
Cc: <ccielab@groupstudy.com>
Sent: Wednesday, January 17, 2001 3:39 PM
Subject: Re: auto-rp and frame-relay
> Allyn,
>
> I have just tried on my routers and I can see the RP. Please refer to the
> log info pasted hereby.
>
> hub#sh ip pim rp
> Group: 229.229.229.1, RP: 192.168.1.2, v2, v1, next RP-reachable in
00:00:58
> Group: 228.228.228.1, RP: 192.168.1.2, v2, v1, next RP-reachable in
00:00:56
>
> hub#sh ip pim nei
> PIM Neighbor Table
> Neighbor Interface Uptime/Expires Ver DR
> Address Priority/Mode
> 170.10.10.1 Serial0 00:17:07/00:01:25 v2 N /
> 192.168.1.1 Serial1 00:20:55/00:01:22 v2 N /
>
> hub#sh int se1
> Serial1 is up, line protocol is up
> Hardware is HD64570
> Internet address is 192.168.1.2/24
> MTU 1500 bytes, BW 125 Kbit, DLY 20000 usec,
> reliability 255/255, txload 1/255, rxload 1/255
> Encapsulation FRAME-RELAY, loopback not set
> Keepalive set (10 sec)
> LMI enq sent 34, LMI stat recvd 0, LMI upd recvd 0
> LMI enq recvd 358, LMI stat sent 343, LMI upd sent 0, DCE LMI up
> LMI DLCI 1023 LMI type is CISCO frame relay DCE
> FR SVC disabled, LAPF state down
> Broadcast queue 0/64, broadcasts sent/dropped 390/45, interface
broadcasts
> 478
> Last input 00:00:02, output 00:00:02, output hang never
> Last clearing of "show interface" counters 01:02:41
> Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0
> Queueing strategy: weighted fair
> Output queue: 0/1000/64/0 (size/max total/threshold/drops)
> Conversations 0/2/256 (active/max active/max total)
> Reserved Conversations 0/0 (allocated/max allocated)
> Available Bandwidth 93 kilobits/sec
> 5 minute input rate 0 bits/sec, 0 packets/sec
> 5 minute output rate 0 bits/sec, 0 packets/sec
> 1078 packets input, 49573 bytes, 0 no buffer
> Received 0 broadcasts, 0 runts, 0 giants, 0 throttles
> 0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
> 1069 packets output, 44155 bytes, 0 underruns
> 0 output errors, 0 collisions, 10 interface resets
> 0 output buffer failures, 0 output buffers swapped out
> 30 carrier transitions
> DCD=up DSR=up DTR=up RTS=up CTS=up
>
> Spoke2#sh ip pim rp
> Group: 229.229.229.1, RP: 192.168.1.2, v2, v1, uptime 00:04:55, expires
> 00:04:05
> Group: 228.228.228.1, RP: 192.168.1.2, v2, v1, uptime 00:04:56, expires
> 00:04:05
> Spoke2#sh ip int brie
> Interface IP-Address OK? Method Status
> Protocol
> Ethernet0 172.10.1.1 YES manual up
down
> Loopback0 2.2.2.2 YES manual up up
> Serial0 192.168.1.1 YES NVRAM up up
> Serial1 unassigned YES unset administratively down
down
> Tunnel0 180.10.1.2 YES manual up up
>
>
> Vincent
>
> ----- Original Message -----
> From: "Allyn Baskerville" <abaskerville@ibeam.com>
> To: "'Brian Hescock'" <bhescock@cisco.com>; "Robert DeVito"
> <robertdevito@hotmail.com>
> Cc: <ccielab@groupstudy.com>
> Sent: Wednesday, January 17, 2001 1:12 AM
> Subject: RE: auto-rp and frame-relay
>
>
> > I have another question about how the RP is supposed to show up at the
> spoke
> > routers. The spoke routers receive announcements for the RP; however,
> when
> > I do a "show ip pim rp" the RP doesn't show up until after I ping a
> > multicast address. Then eventually the RP entry times out, even though
it
> > continues to be announced. Is this to be expected? Thanks - Allyn
> >
> > -----Original Message-----
> > From: Brian Hescock [mailto:bhescock@cisco.com]
> > Sent: Sunday, January 14, 2001 10:11 PM
> > To: Robert DeVito
> > Cc: ccielab@groupstudy.com
> > Subject: Re: auto-rp and frame-relay
> >
> >
> > Also, one thing a lot of people don't realize, and could be a "gotcha",
is
> > an RP learned via Auto-RP is preferred over a statically defined rp via
> > "ip pim rp-address" (assuming you aren't specifying "ip pim accept-rp to
> > filter which ones you'll accept as an RP).
> >
> > Brian
> >
> > On Mon, 15 Jan 2001, Robert DeVito wrote:
> >
> > > Does anyone have any good examples of using auto-rp in a hub and
spoke??
> > My
> > > understanding is that you need to have your MA on your hub and the
> > > rp-announce on your spokes? Am I close?
> > >
> > > Thank you,
> > > Robert
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:27:32 GMT-3