From: Steve McNutt (lpd@xxxxxxxxxxxxxxxx)
Date: Sun Nov 05 2000 - 22:26:07 GMT-3
That's used by auto-RP. here's a snippet from the IOS config guide:
If all interfaces are in sparse mode, a default configured RP to support the
two well-known groups 224.0.1.39 and 224.0.1.40. Auto RP relies on these two
well-known groups to collect and distribute RP-mapping information. When
this is the case and the ip pim accept-rp auto-rp command is configured,
another ip pim accept-rp command accepting the default RP must be
configured, as follows:
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Hazel Gachoka
Sent: Sunday, November 05, 2000 7:45 PM
To: ccielab@groupstudy.com
Subject: Multicast question
I am configuring mulitcast and specifying that r1 should only join group
224.1.2.3, however, despite using an igmp access-goup permiting only one
gorup, 224.0.1.40 is still permitted. Can anyone see why?
Here is a copy of the show tech ipmulticast:
Hazel
Building configuration...
Current configuration:
!
version 12.0
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
!
hostname r1
!
!
ip subnet-zero
no ip domain-lookup
ip multicast-routing
ip dvmrp route-limit 20000
!
!
!
interface Serial1
ip address 137.2.128.1 255.255.255.0
no ip directed-broadcast
ip pim sparse-mode
ip igmp join-group 224.1.2.3
ip igmp access-group 1
clockrate 2000000
!
no ip classless
ip pim rp-address 137.2.5.5
!
access-list 1 permit 224.1.2.3
!
line con 0
transport input none
line aux 0
line vty 0 4
login
!
end
------------------ show ip pim interface ------------------
Address Interface Version/Mode Nbr Query DR
Count Intvl
137.2.128.1 Serial1 v2/Sparse 1 30 0.0.0.0
------------------ show ip pim interface count ------------------
Address Interface FS Mpackets In/Out
137.2.128.1 Serial1 * 174/0
------------------ show ip pim neighbor ------------------
PIM Neighbor Table
Neighbor Address Interface Uptime Expires Ver Mode
137.2.128.5 Serial1 00:49:21 00:01:16 v1 Sparse
------------------ show ip pim rp ------------------
Group: 224.0.1.40, RP: 137.2.5.5, v1, uptime 00:00:12, expires never
Group: 224.1.2.3, RP: 137.2.5.5, uptime 00:00:12, expires never
------------------ show ip igmp groups ------------------
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter
224.0.1.40 Serial1 00:49:33 never 0.0.0.0
224.1.2.3 Serial1 01:18:53 never 0.0.0.0
------------------ show ip igmp interface ------------------
Serial1 is up, line protocol is up
Internet address is 137.2.128.1/24
IGMP is enabled on interface
Current IGMP version is 2
CGMP is disabled on interface
IGMP query interval is 60 seconds
IGMP querier timeout is 120 seconds
IGMP max query response time is 10 seconds
Last member query response interval is 1000 ms
Inbound IGMP access group is 1
IGMP activity: 4 joins, 2 leaves
Multicast routing is enabled on interface
Multicast TTL threshold is 0
Multicast groups joined: 224.1.2.3 224.0.1.40
------------------ show ip mroute count ------------------
IP Multicast Statistics
2 routes using 692 bytes of memory
2 groups, 0.00 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per
second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 224.0.1.40, Source count: 0, Group pkt count: 0
Group: 224.1.2.3, Source count: 0, Group pkt count: 0
------------------ show ip mroute ------------------
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, C - Connected, L - Local, P - Pruned
R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT
X - Proxy Join Timer Running
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 224.0.1.40), 01:18:49/00:00:00, RP 137.2.5.5, flags: SJPCL
Incoming interface: Serial1, RPF nbr 137.2.128.5
Outgoing interface list: Null
(*, 224.1.2.3), 00:51:55/00:00:00, RP 137.2.5.5, flags: SJPCL
Incoming interface: Serial1, RPF nbr 137.2.128.5
Outgoing interface list: Null
r1#ping 224.1.2.3
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.1.2.3, timeout is 2 seconds:
Reply to request 0 from 137.2.128.5, 8 ms
Reply to request 0 from 137.2.80.6, 16 ms
r1#ping 224.0.1.40
Type escape sequence to abort.
Sending 1, 100-byte ICMP Echos to 224.0.1.40, timeout is 2 seconds:
.
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:25:42 GMT-3