cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Contributor III
Contributor III

How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

Hi,  I have a customer that has a P2P Fiber (Ethernet handoff) between two sites.  They only have 1 phone system.  The phone system use 239.255.10.0 to page the phones.  Does anyone know how I can send multi-cast page across the P2P to the remote sites?  Thanks much!

10 Replies
Anonymous
Not applicable

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

:

Thank you for asking this question in the support community.  Typically, multicast routing for applications similar to this use multicast fixed/bi-directional mode.  The Configuring Multicast Routing in AOS guide explains this application, configuration, and troubleshooting steps.

Fixed mode is designed to allow the router to become part of a multicast group permanently and route Multicast packets without running PIM or becoming part of a multicast network. This mode was originally intended to accommodate legacy Multicast products that did not support IGMP, and could not alert the nearby Multicast router that it needed to receive the Multicast stream. In this mode, the router will not run the IGMP process and will forward all received Multicast streams specified to the ‘fixed’ network. This mode also has the ability to perform bi-directional Multicast routing by making the upstream and downstream connections part of the same ‘fixed’ groups.

To place an interface in fixed/bi-directional mode, apply the following command (from interface configuration mode):

(config-int)# ip mcast-stub fixed

To specify a Multicast group an interface will permanently participate in, apply the following command (from interface configuration mode):

(config-int)# ip igmp static-group <address>

To place an interface in fixed/bi-directional mode, apply the following command (from interface configuration mode):

(config-int)# ip mcast-stub fixed

To specify a Multicast group an interface will permanently participate in, apply the following command (from interface configuration mode):

(config-int)# ip igmp static-group <address>

Here is a sample configuration:

ip multicast-routing

!

interface ppp 1

ip mcast-stub fixed

ip igmp static-group <Multicast Address>

!

interface eth 0/1

ip mcast-stub fixed

ip igmp static-group <Multicast Address>

I hope that makes sense, but please do not hesitate to reply to this post with any additional questions.  I will be happy to help in any way I can.

Levi

New Contributor II

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

We had to set this up for the exact same reason.  Our customer had PTP T1 circuits for tears and the above set up works splendidly.  It will also be needed for the fiber with Ethernet hand-off.  One discovery we made when one of the sites converted to fiber was that the service provider would not pass the multicast on the fiber.  The solution was to set up GRE tunnels on this site and then it worked great.  You may not have to do this in your case but I wanted to throw that in in case the above solution does not work right away.  There is a document on how to set up GRE if needed and it, like all Adtran docs, is concise and understandable. ~ Mike

Contributor III
Contributor III

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

Hello, Maybe someone can help me read this.  I've went through the documents and I did this at MAIN LOCATION.  I've notice all the incoming interface is at: Null, RPF nbr 0.0.0.0, does this means they are not receiving the traffic?
Show ip mroute

(*, 224.0.1.60), 168:39:44/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 168:39:44/00:00:00

(*, 239.235.10.0), 168:32:04/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 168:32:04/00:00:00

(*, 239.255.10.0), 168:39:51/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/2, Forward, 168:32:18/00:00:00
    vlan 1, Forward, 168:39:51/00:00:00

(*, 239.255.255.250), 168:39:52/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 168:39:51/00:00:00

(*, 239.255.255.253), 46:19:57/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 46:19:57/00:00:00

This is at REMOTE LOCATION
show ip m route

(*, 224.0.1.60), 168:42:20/1177:13:51, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 168:42:20/1177:13:51

(*, 239.255.10.0), 168:35:41/1177:13:51, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 168:35:41/1177:13:51
    eth 0/2, Forward, 168:34:46/1177:13:51

(*, 239.255.10.1), 70:45:02/1177:13:51, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 70:45:02/1177:13:51

(*, 239.255.255.250), 168:42:27/1177:13:51, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 168:42:27/1177:13:51

(*, 239.255.255.253), 00:38:16/1177:13:51, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 00:38:16/1177:13:51

Contributor III
Contributor III

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

Debug -


I ran these two debug on both router.

Does anyone know if I need to tell my phone system to route the multicast through the router?
I ran a debug while paging, and this is what I'm getting...

Local Router -
debug ip igmp
debug ip mroute

14:28:11: IGMP: received v2 Report from 192.168.101.123 on vlan 1 for 224.0.0.251

14:28:11: IGMP: illegal group address 224.0.0.251

14:28:11: IGMP: received v2 Report from 192.168.101.65 on vlan 1 for 224.0.0.252

14:28:11: IGMP: illegal group address 224.0.0.252

14:28:11: IGMP: received v2 Report from 192.168.101.33 on vlan 1 for 239.255.255.250

14:28:11: IGMP: received v2 Report from 192.168.101.91 on vlan 1 for 239.255.10.0

14:28:18: IGMP: received v2 Report from 192.168.101.7 on vlan 1 for 239.255.255.253

14:28:20: IGMP: received v2 Report from 192.168.101.6 on vlan 1 for 224.0.1.60

14:28:23: IGMP: sent General Query on tunnel 1

14:28:53: IGMP: sent General Query on eth 0/2

14:29:11: IGMP: received v2 Report from 192.168.101.123 on vlan 1 for 224.0.0.251

14:29:11: IGMP: illegal group address 224.0.0.251

14:29:11: IGMP: received v2 Report from 192.168.101.65 on vlan 1 for 239.255.255.250

14:29:11: IGMP: received v2 Report from 192.168.101.78 on vlan 1 for 224.0.0.252

14:29:11: IGMP: illegal group address 224.0.0.252

14:29:11: IGMP: received v2 Report from 192.168.101.44 on vlan 1 for 239.255.10.0

14:29:17: IGMP: received v2 Report from 192.168.101.7 on vlan 1 for 239.255.255.253

14:29:19: IGMP: received v2 Report from 192.168.101.6 on vlan 1 for 224.0.1.60

14:29:23: IGMP: sent General Query on tunnel 1

14:30:11: IGMP: received v2 Report from 192.168.101.117 on vlan 1 for 224.0.0.252

14:30:11: IGMP: illegal group address 224.0.0.252

14:30:11: IGMP: received v2 Report from 192.168.101.88 on vlan 1 for 239.255.255.250

14:30:11: IGMP: received v2 Report from 192.168.101.92 on vlan 1 for 239.255.10.0

14:30:12: IGMP: received v2 Report from 192.168.101.98 on vlan 1 for 224.0.0.251

14:30:12: IGMP: illegal group address 224.0.0.251

14:30:17: IGMP: received v2 Report from 192.168.101.6 on vlan 1 for 224.0.1.60

14:30:23: IGMP: sent General Query on tunnel 1

14:30:41: IGMP: discarded packet from 192.168.101.45 (unrecognized type->0x22)

14:30:42: IGMP: discarded packet from 192.168.101.45 (unrecognized type->0x22)

14:30:53: IGMP: sent General Query on eth 0/2

14:31:07: IGMP: discarded packet from 192.168.101.45 (unrecognized type->0x22)

14:31:11: IGMP: sent General Query on vlan 1

14:31:11: IGMP: received v2 Report from 192.168.101.123 on vlan 1 for 224.0.0.252

14:31:11: IGMP: illegal group address 224.0.0.252

14:31:11: IGMP: received v2 Report from 192.168.101.87 on vlan 1 for 239.255.255.250

14:31:11: IGMP: received v2 Report from 192.168.101.7 on vlan 1 for 224.0.0.251

14:31:11: IGMP: illegal group address 224.0.0.251

14:31:11: IGMP: received v2 Report from 192.168.101.96 on vlan 1 for 239.255.10.0

14:31:12: IGMP: received v2 Report from 192.168.101.6 on vlan 1 for 224.0.1.60

14:31:13: IGMP: received v2 Report from 192.168.101.7 on vlan 1 for 239.255.255.253

14:31:23: IGMP: sent General Query on tunnel 1

14:31:53: IGMP: sent General Query on eth 0/2

14:32:11: IGMP: sent General Query on vlan 1

14:32:11: IGMP: received v2 Report from 192.168.101.50 on vlan 1 for 239.255.10.0

14:32:11: IGMP: received v2 Report from 192.168.101.117 on vlan 1 for 224.0.0.251

14:32:11: IGMP: illegal group address 224.0.0.251

14:32:11: IGMP: received v2 Report from 192.168.101.107 on vlan 1 for 239.255.255.250

14:32:11: IGMP: received v2 Report from 192.168.101.107 on vlan 1 for 224.0.0.252

14:32:11: IGMP: illegal group address 224.0.0.252

14:32:11: IGMP: received v2 Report from 192.168.101.99 on vlan 1 for 224.0.0.251

14:32:11: IGMP: illegal group address 224.0.0.251

14:32:17: IGMP: received v2 Report from 192.168.101.7 on vlan 1 for 239.255.255.253

14:32:21: IGMP: received v2 Report from 192.168.101.6 on vlan 1 for 224.0.1.60

14:32:22: IGMP: received v2 Report from 192.168.101.45 on vlan 1 for 224.0.0.251

14:32:22: IGMP: illegal group address 224.0.0.251

14:32:23: IGMP: sent General Query on tunnel

Here is the debug from Remote Router..
debug ip igmp
debug ip mroute

08:49:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:49:52: IGMP: sent General Query on eth 0/1
08:49:52: IGMP: received v2 Report from 192.168.101.238 on eth 0/1 for 239.255.255.250
08:49:52: IGMP: received v2 Report from 192.168.101.184 on eth 0/1 for 224.0.0.251
08:49:52: IGMP: illegal group address 224.0.0.251
08:49:52: IGMP: received v2 Report from 192.168.101.239 on eth 0/1 for 224.0.0.252
08:49:52: IGMP: illegal group address 224.0.0.252
08:49:53: IGMP: received v2 Report from 192.168.101.163 on eth 0/1 for 239.255.10.0
08:49:57: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:50:01: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:50:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:50:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:50:52: IGMP: sent General Query on eth 0/1
08:50:52: IGMP: received v2 Report from 192.168.101.181 on eth 0/1 for 239.255.10.0
08:50:52: IGMP: received v2 Report from 192.168.101.171 on eth 0/1 for 224.0.0.252
08:50:52: IGMP: illegal group address 224.0.0.252
08:50:52: IGMP: received v2 Report from 192.168.101.176 on eth 0/1 for 239.255.255.250
08:50:52: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.0.251
08:50:52: IGMP: illegal group address 224.0.0.251
08:50:57: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:50:58: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:51:02: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 239.255.255.253
08:51:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:51:52: IGMP: sent General Query on eth 0/1
08:51:52: IGMP: received v2 Report from 192.168.101.163 on eth 0/1 for 239.255.10.0
08:51:52: IGMP: received v2 Report from 192.168.101.176 on eth 0/1 for 224.0.0.251
08:51:52: IGMP: illegal group address 224.0.0.251
08:51:52: IGMP: received v2 Report from 192.168.101.238 on eth 0/1 for 239.255.255.250
08:51:53: IGMP: received v2 Report from 192.168.101.169 on eth 0/1 for 224.0.0.252
08:51:53: IGMP: illegal group address 224.0.0.252
08:51:58: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:52:01: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:52:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:52:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:52:52: IGMP: sent General Query on eth 0/1
08:52:52: IGMP: received v2 Report from 192.168.101.162 on eth 0/1 for 239.255.10.0
08:52:52: IGMP: received v2 Report from 192.168.101.174 on eth 0/1 for 239.255.255.250
08:52:52: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:52:52: IGMP: received v2 Report from 192.168.101.176 on eth 0/1 for 224.0.0.252
08:52:52: IGMP: illegal group address 224.0.0.252
08:52:52: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:52:52: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 239.255.255.253
08:52:55: IGMP: received v2 Report from 192.168.101.171 on eth 0/1 for 224.0.0.251
08:52:55: IGMP: illegal group address 224.0.0.251
08:53:00: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 224.0.0.251
08:53:00: IGMP: illegal group address 224.0.0.251
08:53:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:53:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:53:53: IGMP: received v2 Report from 192.168.101.176 on eth 0/1 for 239.255.255.250
08:53:54: IGMP: received v2 Report from 192.168.101.178 on eth 0/1 for 224.0.0.252
08:53:54: IGMP: illegal group address 224.0.0.252
08:53:54: IGMP: received v2 Report from 192.168.101.184 on eth 0/1 for 224.0.0.251
08:53:54: IGMP: illegal group address 224.0.0.251
08:53:55: IGMP: received v2 Report from 192.168.101.167 on eth 0/1 for 239.255.10.0
08:53:57: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:54:00: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:54:02: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 239.255.255.253
08:54:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:54:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:54:52: IGMP: sent General Query on eth 0/1
08:54:52: IGMP: received v2 Report from 192.168.101.167 on eth 0/1 for 239.255.10.0
08:54:52: IGMP: received v2 Report from 192.168.101.176 on eth 0/1 for 224.0.0.251
08:54:52: IGMP: illegal group address 224.0.0.251
08:54:52: IGMP: received v2 Report from 192.168.101.178 on eth 0/1 for 239.255.255.250
08:54:53: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.0.252
08:54:53: IGMP: illegal group address 224.0.0.252
08:54:55: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:55:00: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:55:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:55:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:55:52: IGMP: sent General Query on eth 0/1
08:55:52: IGMP: received v2 Report from 192.168.101.239 on eth 0/1 for 239.255.255.250
08:55:52: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 224.0.0.251
08:55:52: IGMP: illegal group address 224.0.0.251
08:55:53: IGMP: received v2 Report from 192.168.101.176 on eth 0/1 for 224.0.0.252
08:55:53: IGMP: illegal group address 224.0.0.252
08:55:55: IGMP: received v2 Report from 192.168.101.159 on eth 0/1 for 239.255.10.0
08:55:55: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 239.255.255.253
08:55:56: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:55:58: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:56:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:56:52: IGMP: sent General Query on eth 0/1
08:56:52: IGMP: received v2 Report from 192.168.101.176 on eth 0/1 for 239.255.255.250
08:56:52: IGMP: received v2 Report from 192.168.101.171 on eth 0/1 for 224.0.0.251
08:56:52: IGMP: illegal group address 224.0.0.251
08:56:53: IGMP: received v2 Report from 192.168.101.239 on eth 0/1 for 224.0.0.252
08:56:53: IGMP: illegal group address 224.0.0.252
08:56:53: IGMP: received v2 Report from 192.168.101.181 on eth 0/1 for 239.255.10.0
08:56:54: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:56:59: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:57:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:57:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:57:52: IGMP: sent General Query on eth 0/1
08:57:52: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.0
08:57:52: IGMP: received v2 Report from 192.168.101.178 on eth 0/1 for 239.255.255.250
08:57:52: IGMP: received v2 Report from 192.168.101.184 on eth 0/1 for 224.0.0.251
08:57:52: IGMP: illegal group address 224.0.0.251
08:57:53: IGMP: received v2 Report from 192.168.101.169 on eth 0/1 for 224.0.0.252
08:57:53: IGMP: illegal group address 224.0.0.252
08:58:00: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:58:01: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:58:05: MRT: Remove eth 0/1/239.255.255.253 from the olist of (*, 239.255.255.253)
08:58:05: MRT: Remove mroute (*, 239.255.255.253)
08:58:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:58:08: MRT: Inherited Output List members on (*, 239.255.255.250):
       (*, 239.255.255.250, eth 0/1)
08:58:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:58:52: IGMP: sent General Query on eth 0/1
08:58:52: IGMP: received v2 Report from 192.168.101.170 on eth 0/1 for 239.255.255.250
08:58:52: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.0.251
08:58:52: IGMP: illegal group address 224.0.0.251
08:58:53: IGMP: received v2 Report from 192.168.101.164 on eth 0/1 for 239.255.10.0
08:58:53: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
08:58:53: IGMP: received v2 Report from 192.168.101.239 on eth 0/1 for 224.0.0.252
08:58:53: IGMP: illegal group address 224.0.0.252
08:58:54: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
08:59:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
08:59:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
08:59:52: IGMP: received v2 Report from 192.168.101.239 on eth 0/1 for 224.0.0.252
08:59:52: IGMP: illegal group address 224.0.0.252
08:59:52: IGMP: received v2 Report from 192.168.101.184 on eth 0/1 for 239.255.255.250
08:59:52: IGMP: received v2 Report from 192.168.101.176 on eth 0/1 for 224.0.0.251
08:59:52: IGMP: illegal group address 224.0.0.251
08:59:53: IGMP: received v2 Report from 192.168.101.159 on eth 0/1 for 239.255.10.0
09:00:00: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
09:00:01: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
09:00:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
09:00:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
09:00:52: IGMP: sent General Query on eth 0/1
09:00:52: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.0
09:00:52: IGMP: received v2 Report from 192.168.101.170 on eth 0/1 for 239.255.255.250
09:00:52: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 224.0.0.251
09:00:52: IGMP: illegal group address 224.0.0.251
09:00:53: IGMP: received v2 Report from 192.168.101.184 on eth 0/1 for 224.0.0.252
09:00:53: IGMP: illegal group address 224.0.0.252
09:00:58: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 239.255.255.253
09:00:58: MRT: Add mroute (*, 239.255.255.253)
09:00:58: MRT: Add eth 0/1/239.255.255.253 to the olist of (*, 239.255.255.253)
09:00:59: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
09:01:01: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
09:01:01: MRT: Inherited Output List members on (*, 239.255.255.250):
       (*, 239.255.255.250, eth 0/1)
09:01:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1
09:01:36: IGMP: received v2 Query from 172.17.17.1 on eth 0/2
09:01:52: IGMP: sent General Query on eth 0/1
09:01:52: IGMP: received v2 Report from 192.168.101.238 on eth 0/1 for 239.255.255.250
09:01:54: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.0
09:01:55: IGMP: received v2 Report from 192.168.101.177 on eth 0/1 for 224.0.1.60
09:01:55: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 239.255.255.253
09:01:56: IGMP: received v2 Report from 192.168.101.142 on eth 0/1 for 224.0.0.251
09:01:56: IGMP: illegal group address 224.0.0.251
09:01:57: IGMP: received v2 Report from 192.168.101.184 on eth 0/1 for 224.0.0.252
09:01:57: IGMP: illegal group address 224.0.0.252
09:02:01: IGMP: received v2 Report from 192.168.101.165 on eth 0/1 for 239.255.10.1
09:02:06: IGMP: received v2 Query from 172.16.16.1 on tunnel 1

I'm really hoping someone has a clue, cause I'm completely lost.

Anonymous
Not applicable

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

:

Do you still have questions on this application?  What isn't working properly?  Are you attempting to use multicast over a GRE tunnel, because the debug output does not show multicast traffic traversing a GRE tunnel.  When you get a chance, will you please reply with the current configurations of both ADTRAN units, how the application is intended to function, and what isn't working properly?

Levi

Contributor III
Contributor III

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

Hi Levi,  I'm trying to get multicast over a GRE tunnel.  We have an allworx 24x on the main site (MAIN).  Remote phones at (REMOTE).  When people page all call page, it use multi cast of 239.255.10.0, port 53586.  However people in Remote office is not hearing the page.  I'm hoping that by me adding the GRE tunnel on that POINT-to-POINT fiber that it will resolve the issue, but still no luck.  Attached are config file of both site.  It's been modify a bit to remove sensitive info.

New Contributor II

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

Touristis,

Our customer has a 3COM and multicasts are used for paging, conferencing, time updates to the remote phones, and lamp updates. We have had this customer for 13 years and they had PTP T1s to branches from the main site. We had to first enable Multicast routing to get this to work on the PTP T1. The most recent branch had fiber PTP and we built it out the same way only to discover the Service Provider would not pass the Multicast traffic. We implemented GRE and it worked great.

Remember from earlier posts that the GRE tunnel is a routable interface so you will need a routing statement on to send your multicast traffic through the tunnel. I have to confess that since this branch was so small and the pipe so large we just routed ALL traffic via the GRE with an ip route 0.0.0.0 0.0.0.0 statement on the remote branch and a static route on the main branch. I have been advised this can possibly be a bad practice since GRE has some processing involved but nothing negative was noted here. It was a 5M pipe with 5 PC, an ATM, and 1 IP phone.

Carefully follow the Adtran implementation guide to set this up.

I copied and pasted the relevant programming from our working setup. Main is 131.53.1.0/24 and 131.53.6.0/24 is the remote. The PTP is 10.10.6.0/30 and the tunnel is 10.100.6.0/30. We also are using the firewall here since the main router touches the public internet. This is why there is an access-policy. It is not necessary to have this if you are not using the firewall feature. Equipment being used is Netvanta 3448 on both sides.

Hopefully this points you in the right direction. Based on previous posts it looks like you were close. I remember this being a bit frustrating on my go at it but these configs work and have been in place for over a year with no issues. ~ Mike

Anonymous
Not applicable

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

:

Thank you for replying with the configurations.  When you get a chance, will you please reply with the output from the show ip mroute command on both units?  Also, will you please verify that the TTL of the page/multicast is greater than one?  Sometimes in this application, the paging system is not meant to traverse a router and remain on the same broadcast domain, so the TTL is set to one on the phones, and thus would fail in this application.

Levi

Contributor III
Contributor III

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

Hi Levi,

These are the only option I have on the phone system.

Paging Base IP Addr239.255.10.0
Paging Port56586
Paging Max Hop Count3
Paging Maximum Duration (minutes)1

This is for the MAIN location.

(*, 224.0.1.60), 993:51:39/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 993:51:39/00:00:00

(*, 239.235.10.0), 993:43:59/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 993:43:59/00:00:00
    tunnel 1, Forward, 824:46:07/00:00:00

(*, 239.235.10.1), 05:03:06/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:03:06/00:00:00
    tunnel 1, Forward, 05:02:04/00:00:00

(*, 239.235.10.2), 05:03:03/stopped , RP 0.0.0.0, Flags:

(*, 239.235.10.3), 05:03:02/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:03:02/00:00:00
    tunnel 1, Forward, 05:02:00/00:00:00

(*, 239.235.10.4), 05:02:59/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:59/00:00:00
    tunnel 1, Forward, 05:01:58/00:00:00

(*, 239.235.10.5), 05:02:58/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:58/00:00:00
    tunnel 1, Forward, 05:01:57/00:00:00

(*, 239.235.10.6), 05:02:56/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:57/00:00:00
    tunnel 1, Forward, 05:01:57/00:00:00

(*, 239.235.10.7), 05:02:55/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:55/00:00:00
    tunnel 1, Forward, 05:01:55/00:00:00

(*, 239.235.10.8), 05:02:54/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:54/00:00:00
    tunnel 1, Forward, 05:01:54/00:00:00

(*, 239.235.10.9), 05:02:52/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:52/00:00:00
    tunnel 1, Forward, 05:01:52/00:00:00

(*, 239.235.10.10), 05:02:51/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:51/00:00:00
    tunnel 1, Forward, 05:01:50/00:00:00

(*, 239.235.10.8), 05:02:54/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:54/00:00:00
    tunnel 1, Forward, 05:01:54/00:00:00

(*, 239.235.10.9), 05:02:52/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:52/00:00:00
    tunnel 1, Forward, 05:01:52/00:00:00

(*, 239.235.10.10), 05:02:51/stopped , RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    vlan 1, Forward, 05:02:51/00:00:00
    tunnel 1, Forward, 05:01:50/00:00:00


This is for the Remote location:

(*, 224.0.1.60), 487:45:49/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 487:45:49/352:03:15

(*, 239.235.10.0), 824:45:34/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    tunnel 1, Forward, 824:45:34/352:03:15

(*, 239.235.10.1), 05:01:54/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:54/352:03:15
    tunnel 1, Forward, 04:59:52/352:03:15

(*, 239.235.10.2), 05:01:51/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:51/352:03:15
    tunnel 1, Forward, 04:59:50/352:03:15

(*, 239.235.10.3), 05:01:49/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:49/352:03:15
    tunnel 1, Forward, 04:59:48/352:03:15

(*, 239.235.10.4), 05:01:47/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:47/352:03:15
    tunnel 1, Forward, 04:59:47/352:03:15

(*, 239.235.10.5), 05:01:45/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:45/352:03:15
    tunnel 1, Forward, 04:59:45/352:03:15

(*, 239.235.10.6), 05:01:44/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:44/352:03:15
    tunnel 1, Forward, 04:59:44/352:03:15

(*, 239.235.10.7), 05:01:42/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:42/352:03:15
    tunnel 1, Forward, 04:59:43/352:03:15

(*, 239.235.10.8), 05:01:41/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:41/352:03:15
    tunnel 1, Forward, 04:59:41/352:03:15

(*, 239.235.10.9), 05:01:39/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:39/352:03:15
    tunnel 1, Forward, 04:59:39/352:03:15

(*, 239.235.10.10), 05:01:37/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:37/352:03:15
    tunnel 1, Forward, 04:59:37/352:03:15

(*, 239.235.10.11), 05:01:36/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:36/352:03:15
    tunnel 1, Forward, 04:59:34/352:03:15

(*, 239.235.10.12), 05:01:34/352:03:15, RP 0.0.0.0, Flags:
  Incoming interface: Null, RPF nbr 0.0.0.0
  Outgoing interface list:
    eth 0/1, Forward, 05:01:34/352:03:15
--MORE--

Anonymous
Not applicable

Re: How to route multicast to remote sites via P2P Fiber with Ethernet handoff?

:

I went ahead and flagged this post as "Assumed Answered." If any of the responses on this thread assisted you, please mark them as Correct or Helpful as the case may be with the applicable buttons. This will make them visible and help other members of the community find solutions more easily. If you still need assistance, we would be more than happy to continue working with you on this - just let us know in a reply.

Thanks,

Levi