From: Hobbs (deadheadblues@gmail.com)
Date: Wed Oct 08 2008 - 18:26:02 ART
What part of the topolgy isn't working? I don't see how topology would
affect it, as long as you has broadcast mapped for each dlci. Can you post
the running-configs for the routers that dont work?
On Wed, Oct 8, 2008 at 3:02 PM, Chuck Ryan (chryan) <chryan@cisco.com>wrote:
> This is really strange. I'm running 12.4(17.5)T and it does not work when
> I lab it up using the IE vol 1 workbook, multicast topology. However,
> running the same IOS (12.4(17.5)T), and using a simple 3 router topology
> like this:
>
> BB1 e0/0 ------ e0/0 R3 s1/1 -------- s1/1 R1
>
> where BB1 is my C-RP, and R3 is my mapping agent, it DOES WORK without the
> "ip pim autorp listener" command configured.
>
> BB1#show ip pim autorp
> AutoRP Information:
> AutoRP is enabled.
>
> PIM AutoRP Statistics: Sent/Received
> RP Announce: 28/0, RP Discovery: 0/13
> BB1#show ip pim rp mapping
> PIM Group-to-RP Mappings
> This system is an RP (Auto-RP)
>
> Group(s) 224.0.0.0/4
> RP 11.11.11.11 (?), v2v1
> Info source: 3.3.3.3 (?), elected via Auto-RP
> Uptime: 00:12:39, expires: 00:02:16
> BB1#
> *Oct 8 20:56:13.583: Auto-RP(0): Received RP-discovery, from 3.3.3.3,
> RP_cnt 1, ht 181
> *Oct 8 20:56:13.583: Auto-RP(0): Update (224.0.0.0/4, RP:11.11.11.11),
> PIMv2 v1
> BB1#
> *Oct 8 20:56:15.455: PIM(0): check pim_rp_announce 1
> *Oct 8 20:56:15.455: PIM(0): send rp announce
> *Oct 8 20:56:15.455: Auto-RP(0): Build RP-Announce for 11.11.11.11,
> PIMv2/v1, ttl 16, ht 181
> *Oct 8 20:56:15.455: Auto-RP(0): Build announce entry for (224.0.0.0/4)
> *Oct 8 20:56:15.455: Auto-RP(0): Send RP-Announce packet on Ethernet0/0
> *Oct 8 20:56:15.455: Auto-RP: Send RP-Announce packet on Loopback0
> BB1#
> R3>en
> R3#debug ip pim auto-rp
> PIM Auto-RP debugging is on
> R3#debug ip pim
> PIM debugging is on
> *Oct 8 20:57:12.767: Auto-RP(0): Build RP-Discovery packet
> *Oct 8 20:57:12.767: Auto-RP: Build mapping (224.0.0.0/4, RP:11.11.11.11),
> PIMv2 v1,
> *Oct 8 20:57:12.767: Auto-RP(0): Send RP-discovery packet on Ethernet0/0
> (1 RP entries)
> *Oct 8 20:57:12.767: Auto-RP(0): Send RP-discovery packet on Serial1/2 (1
> RP entries)
> *Oct 8 20:57:12.767: Auto-RP: Send RP-discovery packet on Loopback0 (1 RP
> entries)
> R3#debug ip mpacket
> IP multicast packets debugging is on
> R3#
> *Oct 8 20:57:14.663: IP(0): s=11.11.11.11 (Ethernet0/0) d=224.0.1.39(Serial1/2) id=253, ttl=15, prot=17, len=48(48), mforward
> *Oct 8 20:57:14.663: Auto-RP(0): Received RP-announce, from 11.11.11.11,
> RP_cnt 1, ht 181
> *Oct 8 20:57:14.663: Auto-RP(0): Update (224.0.0.0/4, RP:11.11.11.11),
> PIMv2 v1
> *Oct 8 20:57:14.663: Auto-RP(0): Received RP-announce, from 11.11.11.11,
> RP_cnt 1, ht 181
> *Oct 8 20:57:14.663: Auto-RP(0): Update (224.0.0.0/4, RP:11.11.11.11),
> PIMv2 v1
>
> R3#show ip pim autorp
> AutoRP Information:
> AutoRP is enabled.
>
> PIM AutoRP Statistics: Sent/Received
> RP Announce: 0/30, RP Discovery: 45/0
> R3#show ip pim rp mapping
> PIM Group-to-RP Mappings
> This system is an RP-mapping agent (Loopback0)
>
> Group(s) 224.0.0.0/4
> RP 11.11.11.11 (?), v2v1
> Info source: 11.11.11.11 (?), elected via Auto-RP
> Uptime: 00:14:11, expires: 00:02:48
> R3#
> If you have the IE vol 1 workbook, turn to the multicast technology
> section and try it again using that topology completely. When I use that
> topology and configure ip pim sparse-mode only, without ip pim autorp
> listener, it does not work at all. There's something about the topology that
> is the difference in whether or not this works. Could it be the use of
> frame-relay in the topology, as to why it doesn't work without ip pim autorp
> listener configured?
>
> Thanks,
>
> Chuck
>
> ------------------------------
> *From:* Hobbs [mailto:deadheadblues@gmail.com]
> *Sent:* Wednesday, October 08, 2008 3:00 PM
>
> *To:* Chuck Ryan (chryan)
> *Cc:* mark.chandra@gmail.com; Osamah Shaheen; Ali Mousawi;
> ccielab@groupstudy.com
> *Subject:* Re: Ip PIM Auto-rp Listener
>
> I am running 12.3(19). What are you running? Debugging autorp shows they
> are receiving and sending the proper messages. None of them have listener or
> sparse-dense mode.
>
> R1 (rp announcer)
>
> R1#show run | inc listener|dense
> R1#show ip pim autorp
> AutoRP Information:
> AutoRP is enabled.
>
> PIM AutoRP Statistics: Sent/Received
> RP Announce: 8/94, RP Discovery: 149/3
> R1#
>
> R2 (mapping agent):
>
> R2#show run | inc listener|dense
> R2#show ip pim autorp
> AutoRP Information:
> AutoRP is enabled.
>
> PIM AutoRP Statistics: Sent/Received
> RP Announce: 144/4, RP Discovery: 9/50
> R2#
>
> R3 (no rp commands, only sparse-mode connected to R1)
>
> R3#show ip pim autorp
> AutoRP Information:
> AutoRP is enabled.
>
> PIM AutoRP Statistics: Sent/Received
> RP Announce: 0/0, RP Discovery: 0/42
> R3#
>
> Here is debug from R1:
>
> R1#
> 00:56:54: Auto-RP(0): Received RP-announce, from 2.2.2.2, RP_cnt 1, ht 181
> 00:56:54: Auto-RP(0): Update (224.0.0.0/4, RP:2.2.2.2), PIMv2 v1
>
> Here is debug from R2:
>
> R2#debug ip pim auto-rp
> PIM Auto-RP debugging is on
> R2#
> 00:56:31: Auto-RP(0): Received RP-discovery, from 1.1.1.1, RP_cnt 1, ht
> 181
> 00:56:31: Auto-RP(0): Update (224.0.0.0/4, RP:2.2.2.2), PIMv2 v1
> R2#
>
>
>
> On Wed, Oct 8, 2008 at 1:45 PM, Chuck Ryan (chryan) <chryan@cisco.com>wrote:
>
>> What version of IOS are you running? Also, what do you get from the
>> output of "show ip pim autorp" from routers R1 and R2 ? Do you see that R1
>> is receiving RP-Announce messages from R2 ? Does R2 show that it is
>> receiving RP-Discovery messages from R1 ?
>>
>> Chuck
>>
>> ------------------------------
>> *From:* Hobbs [mailto:deadheadblues@gmail.com]
>> *Sent:* Wednesday, October 08, 2008 2:17 PM
>> *To:* Chuck Ryan (chryan)
>> *Cc:* mark.chandra@gmail.com; Osamah Shaheen; Ali Mousawi;
>> ccielab@groupstudy.com
>>
>> *Subject:* Re: Ip PIM Auto-rp Listener
>>
>> Chuck,
>>
>> I have also labbed this and it works without dense-mode or auto-rp
>> listener. I have the following
>>
>> R2---R1---R3. R1 is the mapping agent, R2 is announcing itself as RP. R3
>> accepts the discovery packet from R3. I think there is difference between
>> forwarding and accepting a multicast packet, as well as a difference between
>> generating a multicast packet (as a mapping agent does) and forwarding
>> received on another interface.
>>
>> When generating one, the router sends it out all pim enabled interfaces,
>> dense mode or note. Notice my RP is 2.2.2.2 (R2) and my MA is 1.1.1.1(R1). There is no "listener" in my config:
>>
>> R3#show run | inc listener
>> R3#show ip pim rp mapping
>> PIM Group-to-RP Mappings
>>
>> Group(s) 224.0.0.0/4
>> RP 2.2.2.2 (?), v2v1
>> Info source: 1.1.1.1 (?), elected via Auto-RP
>> Uptime: 00:04:00, expires: 00:02:24
>> R3#
>>
>>
>> On Wed, Oct 8, 2008 at 12:36 PM, Chuck Ryan (chryan) <chryan@cisco.com>wrote:
>>
>>> I just labbed this up.
>>>
>>> If you have 1 router configured as RP, and 1 other router configured as
>>> mapping agent, without "ip pim autorp listener" configured, this will
>>> not work under ip pim sparse-mode. You can confirm this with "show ip
>>> pim autorp" on both the RP router and the mapping agent router. The RP
>>> router will show "x" number of RP Announce messages sent, but 0
>>> received, whereas the mapping agent router will show 0 RP Discovery
>>> messages sent and 0 received. You can also see this with "debug ip pim
>>> autorp". You will see the RP is sending RP announce messages, and you
>>> will see the mapping agent router is building RP-Discovery packets, but
>>> they are not being sent because of the absence of PIM Dense mode (or the
>>> absence of the ip pim autorp listener command).
>>>
>>> Hope this helps to clear things up for you.
>>>
>>> Chuck
>>>
>>> -----Original Message-----
>>> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
>>> Hobbs
>>> Sent: Wednesday, October 08, 2008 1:22 PM
>>> To: mark.chandra@gmail.com
>>> Cc: Osamah Shaheen; Ali Mousawi; ccielab@groupstudy.com
>>> Subject: Re: Ip PIM Auto-rp Listener
>>>
>>> I think it's because your mapping agent is directly connected to both
>>> your RP candidates. The advertisements are allowed to be accepted, they
>>> just won't be forwarded (without autorp listener or sparse-dense-mode).
>>>
>>> If you were to make you mapping agent R5, you probably wouldn't see R1
>>> as an RP anymore. Make sure to clear rp mapping if you test this. Also
>>> you could attach another router on either end on R5 or R1 and they would
>>> not receive the rp mappings if you did not have autorp listener on R5 or
>>> R1.
>>>
>>> I don't have a lab setup to test..but I am pretty sure this is the
>>> behavior I have seen before
>>>
>>> On Wed, Oct 8, 2008 at 11:56 AM, <mark.chandra@gmail.com> wrote:
>>>
>>> > Hi Osamah,
>>> >
>>> > I've been experienced the same with you.
>>> >
>>> > So, anyone can explain this behaviour?
>>> > Sent from my BlackBerry. wireless device from XL GPRS/EDGE/3G network
>>> >
>>> > -----Original Message-----
>>> > From: Osamah Shaheen <ShaheenO@maaden.com.sa>
>>> >
>>> > Date: Wed, 08 Oct 2008 08:54:01
>>> > To: Ali Mousawi<mousawi.ali@gmail.com>; Mark Stephanus Chandra<
>>> > mark.chandra@gmail.com>
>>> > Cc: <ccielab@groupstudy.com>
>>> > Subject: RE: Ip PIM Auto-rp Listener
>>> >
>>> >
>>> > I have configured Multicast sparse-mode without ip pim autorp lisnter
>>> > and every thing was working fine, I have seen that group 224.0.0.39 is
>>>
>>> > propagated to other multicast routers. I don't know if I'm in wrong
>>> way.
>>> >
>>> >
>>> > -----Original Message-----
>>> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
>>> > Of Ali Mousawi
>>> > Sent: 2008-10-08 06:17
>>> > To: Mark Stephanus Chandra
>>> > Cc: ccielab@groupstudy.com
>>> > Subject: Re: Ip PIM Auto-rp Listener
>>> >
>>> > Hello Mark,
>>> >
>>> > ip pim auto-listener is workaround for cisco auto-rp and it is needed
>>> > in sparse mode. This will allow dense-mode for 2 groups only
>>> > 224.0.0.39 and 224.0.0.40.All other groups will use sparse.
>>> >
>>> > Regards
>>> > Ali
>>> >
>>> > On Tue, Oct 7, 2008 at 6:21 PM, Mark Stephanus Chandra <
>>> > mark.chandra@gmail.com> wrote:
>>> >
>>> > > Dear GS,
>>> > >
>>> > >
>>> > >
>>> > > I have Network Diagram :
>>> > >
>>> > >
>>> > >
>>> > > R5 ---------- SW2 ------------- R1
>>> > >
>>> > >
>>> > >
>>> > > R1 have to be multicast group for 224.0.0.0 -231.255.255.255 and R5
>>> > should
>>> > > be multicast group for 232.0.0.0 - 239.255.255.255
>>> > >
>>> > > SW2 act as the mapping agent
>>> > >
>>> > >
>>> > >
>>> > > This multicast diagram have to in ip pim sparse-mode
>>> > >
>>> > >
>>> > >
>>> > > In solution, I notice we have to use IP Pim auto-rp listener,
>>> > >
>>> > >
>>> > >
>>> > > But before I look at the solution guide, I verify with show ip pim
>>> > > rp-mapping and the mapping is works fine (I think)
>>> > >
>>> > >
>>> > >
>>> > > So can you guys verify what happen if I do not use IP PIm
>>> > autorp-listener.
>>> > >
>>> > >
>>> > >
>>> > > Here ths show ip pim mapping before ip pim rp auto listener
>>> > > configured
>>> > :
>>> > >
>>> > >
>>> > >
>>> > > R1 :
>>> > >
>>> > >
>>> > >
>>> > > R1#sh ip pim rp mapping
>>> > >
>>> > > PIM Group-to-RP Mappings
>>> > >
>>> > > This system is an RP (Auto-RP)
>>> > >
>>> > >
>>> > >
>>> > > Group(s) 224.0.0.0/5
>>> > >
>>> > > RP 150.1.1.1 (?), v2v1
>>> > >
>>> > > Info source: 150.1.8.8 (?), elected via Auto-RP
>>> > >
>>> > > Uptime: 00:23:06, expires: 00:02:34
>>> > >
>>> > > Group(s) 232.0.0.0/5
>>> > >
>>> > > RP 150.1.5.5 (?), v2v1
>>> > >
>>> > > Info source: 150.1.8.8 (?), elected via Auto-RP
>>> > >
>>> > > Uptime: 00:18:35, expires: 00:02:12
>>> > >
>>> > > R1#sh ip mroute
>>> > >
>>> > > IP Multicast Routing Table
>>> > >
>>> > > Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
>>> > > Connected,
>>> > >
>>> > > L - Local, P - Pruned, R - RP-bit set, F - Register flag,
>>> > >
>>> > > T - SPT-bit set, J - Join SPT, M - MSDP created entry,
>>> > >
>>> > > X - Proxy Join Timer Running, A - Candidate for MSDP
>>> > Advertisement,
>>> > >
>>> > > U - URD, I - Received Source Specific Host Report,
>>> > >
>>> > > Z - Multicast Tunnel, z - MDT-data group sender,
>>> > >
>>> > > Y - Joined MDT-data group, y - Sending to MDT-data group
>>> > >
>>> > > Outgoing interface flags: H - Hardware switched, A - Assert winner
>>> > >
>>> > > Timers: Uptime/Expires
>>> > >
>>> > > Interface state: Interface, Next-Hop or VCD, State/Mode
>>> > >
>>> > >
>>> > >
>>> > > (*, 224.0.1.39), 00:33:42/stopped, RP 0.0.0.0, flags: DP
>>> > >
>>> > > Incoming interface: Null, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list: Null
>>> > >
>>> > >
>>> > >
>>> > > (150.1.1.1, 224.0.1.39), 00:33:42/00:02:16, flags: PT
>>> > >
>>> > > Incoming interface: Loopback0, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list: Null
>>> > >
>>> > >
>>> > >
>>> > > (150.1.5.5, 224.0.1.39), 00:02:53/00:00:06, flags: PT
>>> > >
>>> > > Incoming interface: FastEthernet0/0, RPF nbr 156.1.18.8
>>> > >
>>> > > Outgoing interface list: Null
>>> > >
>>> > >
>>> > >
>>> > > (*, 224.0.1.40), 00:42:20/stopped, RP 0.0.0.0, flags: DCL
>>> > >
>>> > > Incoming interface: Null, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > Virtual-Access1, Forward/Sparse, 00:42:20/00:00:00
>>> > >
>>> > >
>>> > >
>>> > > (150.1.8.8, 224.0.1.40), 00:23:42/00:02:59, flags: LT
>>> > >
>>> > > Incoming interface: FastEthernet0/0, RPF nbr 156.1.18.8
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > Virtual-Access1, Forward/Sparse, 00:23:44/00:00:00
>>> > >
>>> > >
>>> > >
>>> > > SW2
>>> > >
>>> > >
>>> > >
>>> > > SW2#sh ip pim rp mapping
>>> > >
>>> > > PIM Group-to-RP Mappings
>>> > >
>>> > > This system is an RP-mapping agent (Loopback0)
>>> > >
>>> > >
>>> > >
>>> > > Group(s) 224.0.0.0/5
>>> > >
>>> > > RP 150.1.1.1 (?), v2v1
>>> > >
>>> > > Info source: 150.1.1.1 (?), elected via Auto-RP
>>> > >
>>> > > Uptime: 00:25:14, expires: 00:02:46
>>> > >
>>> > > Group(s) 232.0.0.0/5
>>> > >
>>> > > RP 150.1.5.5 (?), v2v1
>>> > >
>>> > > Info source: 150.1.5.5 (?), elected via Auto-RP
>>> > >
>>> > > Uptime: 00:20:43, expires: 00:02:15
>>> > >
>>> > > SW2#sh ip mroute
>>> > >
>>> > > IP Multicast Routing Table
>>> > >
>>> > > Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
>>> > > Connected,
>>> > >
>>> > > L - Local, P - Pruned, R - RP-bit set, F - Register flag,
>>> > >
>>> > > T - SPT-bit set, J - Join SPT, M - MSDP created entry,
>>> > >
>>> > > X - Proxy Join Timer Running, A - Candidate for MSDP
>>> > Advertisement,
>>> > >
>>> > > U - URD, I - Received Source Specific Host Report,
>>> > >
>>> > > Z - Multicast Tunnel, z - MDT-data group sender,
>>> > >
>>> > > Y - Joined MDT-data group, y - Sending to MDT-data group
>>> > >
>>> > > Outgoing interface flags: H - Hardware switched, A - Assert winner
>>> > >
>>> > > Timers: Uptime/Expires
>>> > >
>>> > > Interface state: Interface, Next-Hop or VCD, State/Mode
>>> > >
>>> > >
>>> > >
>>> > > (*, 224.0.1.39), 00:33:16/stopped, RP 0.0.0.0, flags: DCL
>>> > >
>>> > > Incoming interface: Null, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > FastEthernet0/0, Forward/Sparse, 00:22:28/00:02:05
>>> > >
>>> > > FastEthernet0/1, Forward/Sparse, 00:26:40/00:02:24
>>> > >
>>> > > Loopback0, Forward/Sparse, 00:33:16/00:02:17
>>> > >
>>> > >
>>> > >
>>> > > (150.1.1.1, 224.0.1.39), 00:25:50/00:02:13, flags: LT
>>> > >
>>> > > Incoming interface: FastEthernet0/1, RPF nbr 156.1.18.1
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > FastEthernet0/0, Forward/Sparse, 00:22:28/00:02:05
>>> > >
>>> > > Loopback0, Forward/Sparse, 00:25:50/00:02:17
>>> > >
>>> > >
>>> > >
>>> > > (150.1.5.5, 224.0.1.39), 00:21:01/00:02:58, flags: LT
>>> > >
>>> > > Incoming interface: FastEthernet0/0, RPF nbr 156.1.58.5
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > Loopback0, Forward/Sparse, 00:21:01/00:02:17
>>> > >
>>> > > FastEthernet0/1, Forward/Sparse, 00:21:01/00:02:24
>>> > >
>>> > >
>>> > >
>>> > > (*, 224.0.1.40), 00:34:15/stopped, RP 0.0.0.0, flags: DCL
>>> > >
>>> > > Incoming interface: Null, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > Loopback0, Forward/Sparse, 00:34:15/00:02:11
>>> > >
>>> > >
>>> > >
>>> > > (150.1.8.8, 224.0.1.40), 00:25:54/00:02:46, flags: PLT
>>> > >
>>> > > Incoming interface: Loopback0, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list: Null
>>> > >
>>> > >
>>> > >
>>> > > R5 :
>>> > >
>>> > >
>>> > >
>>> > > R5#sh ip pim rp mapping
>>> > >
>>> > > PIM Group-to-RP Mappings
>>> > >
>>> > > This system is an RP (Auto-RP)
>>> > >
>>> > >
>>> > >
>>> > > Group(s) 224.0.0.0/5
>>> > >
>>> > > RP 150.1.1.1 (?), v2v1
>>> > >
>>> > > Info source: 150.1.8.8 (?), elected via Auto-RP
>>> > >
>>> > > Uptime: 00:22:25, expires: 00:02:14
>>> > >
>>> > > Group(s) 232.0.0.0/5
>>> > >
>>> > > RP 150.1.5.5 (?), v2v1
>>> > >
>>> > > Info source: 150.1.8.8 (?), elected via Auto-RP
>>> > >
>>> > > Uptime: 00:21:35, expires: 00:02:13
>>> > >
>>> > > R5#sh ip mroute
>>> > >
>>> > > IP Multicast Routing Table
>>> > >
>>> > > Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C -
>>> > > Connected,
>>> > >
>>> > > L - Local, P - Pruned, R - RP-bit set, F - Register flag,
>>> > >
>>> > > T - SPT-bit set, J - Join SPT, M - MSDP created entry,
>>> > >
>>> > > X - Proxy Join Timer Running, A - Candidate for MSDP
>>> > Advertisement,
>>> > >
>>> > > U - URD, I - Received Source Specific Host Report,
>>> > >
>>> > > Z - Multicast Tunnel, z - MDT-data group sender,
>>> > >
>>> > > Y - Joined MDT-data group, y - Sending to MDT-data group
>>> > >
>>> > > Outgoing interface flags: H - Hardware switched, A - Assert winner
>>> > >
>>> > > Timers: Uptime/Expires
>>> > >
>>> > > Interface state: Interface, Next-Hop or VCD, State/Mode
>>> > >
>>> > >
>>> > >
>>> > > (*, 224.0.1.39), 00:08:29/stopped, RP 0.0.0.0, flags: DC
>>> > >
>>> > > Incoming interface: Null, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > FastEthernet3/0, Forward/Sparse, 00:08:29/00:00:00
>>> > >
>>> > > Virtual-Access1, Forward/Sparse, 00:08:29/00:00:00
>>> > >
>>> > >
>>> > >
>>> > > (150.1.1.1, 224.0.1.39), 00:08:29/00:02:39, flags: T
>>> > >
>>> > > Incoming interface: FastEthernet3/0, RPF nbr 156.1.58.8
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > Virtual-Access1, Forward/Sparse, 00:08:29/00:00:00
>>> > >
>>> > >
>>> > >
>>> > > (150.1.5.5, 224.0.1.39), 00:07:40/00:02:19, flags: T
>>> > >
>>> > > Incoming interface: Loopback0, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > FastEthernet3/0, Forward/Sparse, 00:07:40/00:00:00
>>> > >
>>> > > Virtual-Access1, Forward/Sparse, 00:07:40/00:00:00
>>> > >
>>> > >
>>> > >
>>> > > (*, 224.0.1.40), 00:08:40/stopped, RP 0.0.0.0, flags: DCL
>>> > >
>>> > > Incoming interface: Null, RPF nbr 0.0.0.0
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > FastEthernet3/0, Forward/Sparse, 00:08:44/00:00:00
>>> > >
>>> > > Virtual-Access1, Forward/Sparse, 00:08:44/00:00:00
>>> > >
>>> > >
>>> > >
>>> > > (150.1.8.8, 224.0.1.40), 00:07:50/00:02:15, flags: LT
>>> > >
>>> > > Incoming interface: FastEthernet3/0, RPF nbr 156.1.58.8
>>> > >
>>> > > Outgoing interface list:
>>> > >
>>> > > Virtual-Access1, Forward/Sparse, 00:07:50/00:00:00
>>> > >
>>> > >
>>> > >
>>> > > Thanks guys, really appreciate your help
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>> > > Regards
>>> > >
>>> > >
>>> > >
>>> > > Mark Stephanus Chandra
>>> > > IT Consultant
>>> > >
>>> > >
>>> > > 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
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > ----------------------------------------------------------------------
>>> > ----------
>>> >
>>> >
>>> > This message and any attachments are confidential and intended solely
>>> > for the use of the individual or entity to whom they are addressed. If
>>>
>>> > you are NOT the intended recipient you should not use, copy, disclose
>>> > or place any reliance on this e-mail or its contents, and immediately
>>> > notify the sender by return e-mail and delete all copies of this
>>> e-mail from your system.
>>> >
>>> > Statement and opinions expressed in this e-mail are those of the
>>> > sender, and do not necessarily reflect MA'ADEN.
>>> >
>>> > postmaster@maaden.com.sa
>>> >
>>> >
>>> > 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
This archive was generated by hypermail 2.1.4 : Sat Nov 01 2008 - 15:35:20 ARST