From: Mike Kraus \(mikraus\) (mikraus@cisco.com)
Date: Thu Jul 05 2007 - 14:07:25 ART
IP pim nbma-mode still uses 224.0.0.13, the interface still doesn't know
what to do with a local-link multicasts (224.0.0.13) as Scott indicates.
See here:
*************
No PIM neighbor without broadcast statements
*************
R2#sho run int se0/0
Building configuration...
Current configuration : 322 bytes
!
interface Serial0/0
ip address 10.2.45.2 255.255.255.0
ip pim dr-priority 5000
ip pim nbma-mode
ip pim sparse-mode
encapsulation frame-relay
ip ospf network point-to-multipoint non-broadcast
ip ospf priority 100
frame-relay map ip 10.2.45.4 204
frame-relay map ip 10.2.45.5 205
no frame-relay inverse-arp
End
R2#sho ip pim neigh
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
10.12.12.1 FastEthernet0/0 02:47:27/00:01:16 v2 1 / S
*************
Debugging shows PIM messages unable to be sent
*************
R2#debug ip packet 101
*Jul 4 20:57:56.033: IP: s=10.2.45.2 (local), d=224.0.0.13 (Serial0/0),
len 56, sending broad/multicast
*Jul 4 20:57:56.033: IP: s=10.2.45.2 (local), d=224.0.0.13 (Serial0/0),
len 56, encapsulation failed
*************
Once, I put all my broadcast statements back on, my PIM neighbors come
back
*************
R4(config)#int se0/0
R4(config-if)#frame-relay map ip 10.2.45.2 402 broad
R5(config)#int se0/0
R5(config-if)#frame-relay map ip 10.2.45.2 502 broad
R2(config)#int se0/0
R2(config-if)#frame-relay map ip 10.2.45.4 204 broad
R2(config-if)#frame-relay map ip 10.2.45.5 205 broad
R2(config-if)#
*Jul 4 21:04:04.801: %PIM-5-NBRCHG: neighbor 10.2.45.4 UP on interface
Serial0/0
R2(config-if)#
*Jul 4 21:04:33.764: %PIM-5-NBRCHG: neighbor 10.2.45.5 UP on interface
Serial0/0
R2(config-if)#
R2(config-if)#do sho ip pim neigh
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
10.12.12.1 FastEthernet0/0 02:50:10/00:01:32 v2 1 / S
10.2.45.5 Serial0/0 00:01:25/00:01:19 v2 1 / S
10.2.45.4 Serial0/0 00:01:54/00:01:19 v2 1 / S
-----Original Message-----
From: Scott Morris [mailto:smorris@ipexpert.com]
Sent: Thursday, July 05, 2007 11:32 AM
To: 'Marko Milivojevic'; Mike Kraus (mikraus); 'Ben'; 'John Jones'
Cc: 'Cisco certification'
Subject: RE: FR static P2P mapping on physical interfaces
IP PIM modes have to do with Multicast routing. Routing protocols using
multicast have nothing to do with multicast routing. Anything using a
224.0.0.x address is link-local only.
The problem most likely (if you do "debug ip packet") is that you'll see
"encapsulation failed" messages, which means your router doesn't know
what to do with them. The "broadcast" keyword needs to be seen on the
DLCI when you do a "show frame map" command.
HTH,
Scott Morris, CCIE4 (R&S/ISP-Dial/Security/Service Provider) #4713,
JNCIE #153, CISSP, et al.
CCSI/JNCI-M/JNCI-J
VP - Technical Training - IPexpert, Inc.
IPexpert Sr. Technical Instructor
A Cisco Learning Partner - We Accept Learning Credits!
smorris@ipexpert.com
Telephone: +1.810.326.1444
Fax: +1.810.454.0130
http://www.ipexpert.com
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Marko Milivojevic
Sent: Thursday, July 05, 2007 11:59 AM
To: Mike Kraus (mikraus); Ben; John Jones
Cc: Cisco certification
Subject: RE: FR static P2P mapping on physical interfaces
> Even though OSPF would be running fine, you would find that multicast
packets
> would fail to be encapsulated and would not be transmitted.
Wouldn't this be addressed with "ip pim nbma"?
This archive was generated by hypermail 2.1.4 : Sat Aug 18 2007 - 08:17:39 ART