Re: Multicast doubt

sateeshk10 · ‎03-05-2009

Hi,

I have some 10 servers which is runing multicast applications. Now I would like know those Multicast IP address of those servers.

Is there any command to check the same in router.

Regards

sateesh

andrew.prince · ‎03-05-2009

try "show ip mroute"

HTH>

sateeshk10 · ‎03-06-2009

Hi,

Thanks for your prompt reply.I have one more query..

My application team complaining that multicast is not working. So, How prove that network is fine.

Is there any special commands which i can show to them and confim that network is allowing multicast traffic

Regards

sateesh

andrew.prince · ‎03-06-2009

Define "not working" ?

Are clients not registering and not receving content?

Are servers not seeing client requests to join?

sateeshk10 · ‎03-06-2009

Hi,

Simple like everybody complaning that applications is not working due to network is not allowing the multicast traffic thats all.

Now i need prove that there is no problem with multicast netowrk. So i need some commands so that i can show to them.

Are clients not registering and not receving content?

Are servers not seeing client requests to join?

It can be any thing. just want to show to them its working fine.

Regards

sateesh

andrew.prince · ‎03-06-2009

check your config - make sure if you are using switches they are enabled for multicasting etc.

sateeshk10 · ‎03-06-2009

Hi,

I am looking for some show commands and explantion which i want to prove that multicast is working fine in the network..

Regards

sateesh

andrew.prince · ‎03-06-2009

mrinfo [hostname | address] [source-address | interface]

Query a multicast router about which neighboring multicast routers are peering with it.

mstat source [destination] [group]

Display IP multicast packet rate and loss information.

mtrace source [destination] [group]

Trace the path from a source to a destination branch for a multicast distribution tree for a given group.

ping [group-name | group-address]

Send an ICMP Echo Request to a multicast group address.

show frame-relay ip rtp header-compression [interface type number]

Display Frame Relay RTP header compression statistics.

show ip dvmrp route [ip-address]

Display the entries in the DVMRP routing table.

show ip igmp groups [group-name | group-address | type number]

Display the multicast groups that are directly connected to the router and that were learned via IGMP.

show ip igmp interface [type number]

Display multicast-related information about an interface.

show ip mcache [group [source]]

Display the contents of the IP fast-switching cache.

show ip mpacket [source-address | source-name] [group-address | group-name] [detail]

Display the contents of the circular cache-header buffer.

show ip mroute [group-name | group-address] [source] [summary] [count] [active kbps]

Display the contents of the IP multicast routing table.

show ip pim interface [type number] [count]

Display information about interfaces configured for PIM.

show ip pim neighbor [type number]

List the PIM neighbors discovered by the router.

show ip pim rp [group-name | group-address]

Display the RP routers associated with a sparse-mode multicast group.

show ip pim vc [group-or-name] [type number]

Display ATM VC status information for multipoint VCs opened by PIM.

show ip rpf {source-address | source-name}

Display how the router is doing Reverse-Path Forwarding (that is, from the unicast routing table, DVMRP routing table, or static mroutes).

show ip rtp header-compression [type number] [detail]

Display RTP header compression statistics.

show ip sdr [group | "session-name" | detail]

Display the Session Directory Protocol Version 2 cache.

sateeshk10 · ‎03-09-2009

Hi,

Thanks for info.

I am newbee to multicast. But in my network muticast is already configured by somebody.. Now i want to know the following details

which server is runing multicast application

who is trying(client) to access the multicast server

If you want me provide some more details by runing commands i can provide same to you.let me know whci show commands output are required for you to provide the details..

sorry to bother you again

Regards

sateesh

gesadmin1 · ‎03-09-2009

sateesh,

andrew already gave you a plethora of show commands to get this output. You should attempt to run some of the commands and research the output on your own at least at first so that you learn something. two of the commands that you should investigate further are:

- sh ip mroute

- sh ip igmp groups

If you are using catalyst switches elsewhwere in your network and igmp snooping is still enabled you can execute this command:

- sh ip igmp snooping group

sateeshk10 · ‎03-13-2009

Hi,

pl. find below O/p i have some queries on the same.

When i geven the sh ip mroute i have observed some IP which is starts with 224.*.*.* actually i am runing multicast aplication on one server only but i am seeing so many IP which starts with 224.*.*.*. I hope clients are communication 224.*.*.* ryt?

when i gave sh ip igmp its showing 224.0.1.40..menas is that servers is runing multicast application.. nothing but my multicast server IP?..

pl. explain the O/Pof below commands

#sh ip mroute

(*, 233.6.6.6), 4d21h/stopped, RP 0.0.0.0, flags: D

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Port-channel5, Forward/Sparse-Dense, 4d21h/00:00:00

Port-channel3, Forward/Sparse-Dense, 4d21h/00:00:00

Port-channel2, Forward/Sparse-Dense, 4d21h/00:00:00

(192.168.22.117, 233.6.6.6), 4d21h/00:02:03, flags: T

Incoming interface: Port-channel2, RPF nbr 192.168.101.2

Outgoing interface list:

Port-channel3, Forward/Sparse-Dense, 00:03:48/00:00:00

Port-channel5, Forward/Sparse-Dense, 4d21h/00:00:00

(*, 235.6.6.6), 2d11h/stopped, RP 0.0.0.0, flags: D

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Port-channel5, Forward/Sparse-Dense, 2d11h/00:00:00

Port-channel3, Forward/Sparse-Dense, 2d11h/00:00:00

Port-channel2, Forward/Sparse-Dense, 2d11h/00:00:00

(192.168.22.113, 235.6.6.6), 1d22h/00:02:24, flags: T

Incoming interface: Port-channel2, RPF nbr 192.168.101.2

Outgoing interface list:

Port-channel3, Forward/Sparse-Dense, 1d22h/00:00:00

Port-channel5, Forward/Sparse-Dense, 00:06:28/00:00:00

(*, 230.0.0.4), 1w5d/stopped, RP 0.0.0.0, flags: D

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Port-channel5, Forward/Sparse-Dense, 1w5d/00:00:00

Port-channel3, Forward/Sparse-Dense, 1w5d/00:00:00

Port-channel2, Forward/Sparse-Dense, 1w5d/00:00:00

(192.168.22.137, 230.0.0.4), 00:01:06/00:02:59, flags: T

Incoming interface: Port-channel2, RPF nbr 192.168.101.2

Outgoing interface list:

Port-channel3, Forward/Sparse-Dense, 00:01:06/00:00:00

Port-channel5, Prune/Sparse-Dense, 00:01:06/00:01:53

(192.168.22.175, 230.0.0.4), 00:01:23/00:02:59, flags: T

Incoming interface: Port-channel2, RPF nbr 192.168.101.2

Outgoing interface list:

Port-channel3, Forward/Sparse-Dense, 00:01:23/00:00:00

Port-channel5, Forward/Sparse-Dense, 00:01:23/00:00:00

(192.168.22.174, 230.0.0.4), 00:03:07/00:01:41, flags: T

Incoming interface: Port-channel2, RPF nbr 192.168.101.2

Outgoing interface list:

Port-channel3, Forward/Sparse-Dense, 00:03:07/00:00:00

Port-channel5, Forward/Sparse-Dense, 00:00:06/00:00:00

(192.168.22.173, 230.0.0.4), 00:03:16/00:01:41, flags: T

Incoming interface: Port-channel2, RPF nbr 192.168.101.2

Outgoing interface list:

Port-channel3, Forward/Sparse-Dense, 00:03:16/00:00:00

Port-channel5, Forward/Sparse-Dense, 00:00:15/00:00:00

(*, 224.3.4.5), 5d02h/00:02:42, RP 0.0.0.0, flags: D

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Port-channel5, Forward/Sparse-Dense, 5d02h/00:00:00

Port-channel3, Forward/Sparse-Dense, 5d02h/00:00:00

Port-channel2, Forward/Sparse-Dense, 5d02h/00:00:00

(*, 224.0.1.40), 41w2d/00:02:49, RP 0.0.0.0, flags: DCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Port-channel5, Forward/Sparse-Dense, 41w2d/00:00:00

Port-channel3, Forward/Sparse-Dense, 41w2d/00:00:00

Port-channel2, Forward/Sparse-Dense, 41w2d/00:00:00

-===========================================================

# sh ip igmp groups

IGMP Connected Group Membership

Group Address Interface Uptime Expires Last Reporter Group Accounted

224.0.1.40 Port-channel5 41w2d 00:02:14 192.168.107.2

224.0.1.40 Port-channel3 41w2d 00:02:16

Regards

sateesh

gesadmin1 · ‎03-13-2009

192.168.22.117, .113, .137, .175, .174, and .173 are all sourcing multicast traffic. It looks like the upstream device with the address of 192.168.101.2 is where the streams are coming from (at least into this device). The 224.x.x.x addresses that you see are part of the normal multicast operation. Note that 233.6.6.6 and 235.6.6.6 addresses have an overlapping multicast MAC address (0100:5e06:0606) which may or may not be what you want. Also, you should change the multicast address of your 230.0.0.4 to be something else such as 230.1.1.4 or something since this translates into a multicast MAC of 0100:5E00:0004 which is the same multicast MAC of the DVMRP.