185Task Command RemarksDisplay the content of the PIMrouting table.display pim [ all-instance |vpn-instance vpn-instance-name ]routing-table [ group-address[ mask { mask-length | mask } ] |source-address [ mask{ mask-length | mask } ] |incoming-interface [ interface-typeinterface-number | register ] |outgoing-interface { include |exclude | match } { interface-typeinterface-number | register } |mode mode-type | flags flag-value| fsm ] * [ | { begin | exclude |include } regular-expression ]Available in any viewDisplay the RP information.display pim [ all-instance |vpn-instance vpn-instance-name ]rp-info [ group-address ] [ | { begin| exclude | include }regular-expression ]Available in any viewReset PIM control messagecounters.reset pim [ all-instance |vpn-instance vpn-instance-name ]control-message counters[ interface interface-typeinterface-number ]Available in user viewPIM configuration examplesPIM-DM configuration exampleNetwork requirementsAs shown in Figure 53, receivers receive VOD information through multicast. The receiver groups ofdifferent organizations form stub networks, and one or more receiver hosts exist in each stub network. Theentire PIM domain is operating in the dense mode.Host A and Host C are multicast receivers in two stub networks.IGMPv2 runs between Switch A and N1 and between Switch B/Switch C and N2.
