12.07.2015 Views

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

Brocade MLX Series and Brocade NetIron XMR Diagnostic Guide ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

8PIM DM <strong>and</strong> PIM SMclear ip msdp sa-cacheSyntax: clear ip msdp sa-cache This comm<strong>and</strong> clears all of the cache entries. Use the variable to clear only the entriesmatching either a source or a group.To clear MSDP statistics, enter the clear ip msdp statistics comm<strong>and</strong> at the Privileged EXEC level ofthe CLI.clear ip msdp statisticsSyntax: clear ip msdp statistics This comm<strong>and</strong> clears statistics for all the peers. To clear statistics for a specific peer, enter thepeer’s IP address using the variable.Configuration notes• MSDP depends on BGP <strong>and</strong> Multiprotocol BGP (MBGP) for inter-domain operations.• Routers that run MSDP usually also run BGP. The source address used by the MSDP router isnormally configured to be the same source address used by BGP.• For MSDP mesh groups, on each device that will be part of the mesh group, there must be amesh group definition for all the peers in the mesh group.• It is recommended that you use the connect-source loopback parameter when issuingthe msdp-peer comm<strong>and</strong>. If you do not use this parameter, the <strong>Brocade</strong> device uses theoutgoing interface’s IP address. You must also make sure the IP address of the connect-sourceloopback parameter is the source IP address used by the PIM-RP, <strong>and</strong> the BGP router.Common diagnostic scenarios• High CPU usage with MSDP traffic between two peers.This issue can be resolved by resetting both peers.• PIM SM Multicast packets are not being successfully transmitted.A device downstream has multicast passive <strong>and</strong> PIM snooping enabled. Once PIM snooping isdisabled on the downstream device, <strong>and</strong> added on MBGP links, the problem is resolved.• Unable to remove an MSDP peer.This issue is resolved by upgrading the software version to reflect the latest patches <strong>and</strong>versions.PIM DM <strong>and</strong> PIM SMProtocol-Independent Multicast (PIM) helps to simplify the complexity of the routing protocol. PIM issimilar to DVMRP in that PIM builds source-routed multicast delivery trees <strong>and</strong> employs reversepath check when forwarding multicast packets.There are two PIM modes: Dense <strong>and</strong> Sparse. The Dense Mode (DM) is suitable for denselypopulated multicast groups, primarily in the LAN environment. The Sparse Mode (SM) is suitable forsparsely populated multicast groups with the focus on WAN.288 <strong>Brocade</strong> <strong>MLX</strong> <strong>Series</strong> <strong>and</strong> <strong>Brocade</strong> <strong>NetIron</strong> <strong>XMR</strong> <strong>Diagnostic</strong> <strong>Guide</strong>53-1002426-02

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!