Subject: too much mbone traffic when pruning is on

From: [email-masked] (Georges Aubry)
Date: Wed, 20 Nov 1996 20:49:28 +0100

We have installed mrouted 3.8 on our Solaris (SunOS 5.5.1) station which
has a mbone tunnel with our SWITCH Internet Provider. The multicast
routing is enable on the phyint 128.178.47.47 of the mrouted station.
mrouted.conf:
 pruning on
 phyint 128.178.47.47 metric 1 threshold 64
 tunnel 128.178.47.47 130.59.72.10 metric 1 threshold 64 rate_limit 500 
For the test the PIM multicast routing was not configured on the EPFL 
cisco routeur.

swidir.switch.ch     SWITCH    128.178.47   EPFL
Internet-------------router----------------router----campus network
Provider                        |
                                |
                         stimon47.epfl.ch
                         mrouted station
We have made a test of runnning mrouted during 30 minutes (on 11/19/96
at 20:00 MET time) when nobody listen the IP multicast on the subnet
128.178.47.
At the end of the test, we see, with the command "netstat -Mn", 
162000 pkts sent from swidir to stimon47 via the mbone tunnel 
and the Pkt_out counter is zero for the phyint 128.178.47.47 on stimon47.
A traffic analyzer measured 89 MBytes of mbone tunnel traffic during
these 30 minutes. The average rate is 395 Kbits/s. 

I'm surprise to see a such load of mbone traffic when there are no members
of the multicast groups on segment between SWITCH router and EPFL router.
I think hard because the bill for the Internet traffic depend on the
the amount of MBytes received.

QUESTIONS:
Is it normal to see a such load of mbone traffic when the pruning is on ?

Could someone do a similar test and tell me how many pkts are received 
from the mbone tunnel during 30 minutes when no users listen IP multicast ?

Thanks in advance,

Georges

-----------------------------------------------------------
Ecole Polytechnique Federale de Lausanne
Swiss Federal Institute of Technology
Service informatique central

Georges Aubry                   E-mail :  [email-masked]
EPFL/SIC                        WWW URL: http://www.epfl.ch
B.P. 121                        Tel.   :    +41(21)693 4513
CH-1015 Lausanne, Switzerland   Fax    :    +41(21)693 2220
-----------------------------------------------------------

---

From: Bill Fenner <[email-masked]>
Date: Fri, 22 Nov 1996 12:03:51 PST

I tried the same experiment; ran mrouted on a machine with no group members
on its local network and took packet counts after a half an hour.  It
received 1132 packets in 30 minutes, approximately 0.01 packets per second.

What kind of packet loss do you experience on that tunnel?  mrouted doesn't
currently retransmit prunes, so if you lose a prune you will continue to
get unwanted traffic.  Prune retransmission will be in the next release.

  Bill

---

From: [email-masked] (Georges Aubry)
Date: Tue, 26 Nov 1996 20:40:12 +0100

> get unwanted traffic.  Prune retransmission will be in the next release.

How can I know if there is packet loss on the tunnel?

I tried to run "mrouted -d 3" and I see that prune packets are sent.
With a protocol analyzer, I see that the prune lifetime in a
prune packet is  514 seconds (see at bottom).
But the Distance Vector Multicast Routing Protocol document (Internet Draft)
indicates that a router with no downstream dependent neighbors would use
the default prune lifetime (2 hours).

I see also a lot of messages "warning - kernel entry already exists for ..."

Are the prune lifetime and these warning messages the cause why
our mrouted station receive too much mbone traffic when no users
are members?

Georges

18:39:29.794 Route for 131.188.3.36/32 stealing sources from default
18:39:29.805 Route for 131.188.3.32/32 stealing sources from 131.188.3/24
18:39:29.813 Route for 131.188.3.32/32 stealing sources from default
18:39:29.826 Route for 131.188.3.10/32 stealing sources from 131.188.3/24
18:39:29.833 Route for 131.188.3.10/32 stealing sources from default
18:39:29.839 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:29.846 Updating 101 routes from 130.59.72.10 to 128.178.47.47
18:39:29.862 add cache entry (24.0.8.69 224.2.206.143) gm:0, parent-vif:2
18:39:29.869 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:29.875 sent prune for (24/8 224.2.206.143)/415 on vif 2 to 130.59.72.10
18:39:29.881 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:29.886 Updating 2 routes from 130.59.72.10 to 128.178.47.47
18:39:29.901 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:29.907 Updating 101 routes from 130.59.72.10 to 128.178.47.47
18:39:29.915 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:29.921 Updating 100 routes from 130.59.72.10 to 128.178.47.47
18:39:29.929 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:29.935 Updating 100 routes from 130.59.72.10 to 128.178.47.47
18:39:29.943 RECV neighbor probe     from 130.59.72.10    to 128.178.47.47
18:39:29.949 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:29.954 Updating 4 routes from 130.59.72.10 to 128.178.47.47
18:39:29.966 warning - kernel entry already exists for (24.0.8.69 
224.2.206.143)
18:39:29.981 RECV new member report  from 128.178.47.47   to 224.0.0.2
18:39:29.988 RECV new member report  from 128.178.47.47   to 224.0.0.4
18:39:29.994 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:30.000 Updating 100 routes from 130.59.72.10 to 128.178.47.47
18:39:30.017 add cache entry (9.2.22.101 224.2.250.130) gm:0, parent-vif:2
18:39:30.026 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.032 sent prune for (9/8 224.2.250.130)/300 on vif 2 to 130.59.72.10
18:39:30.037 RECV membership query   from 128.178.47.47   to 224.0.0.1
18:39:30.050 add cache entry (171.69.163.55 224.2.206.143) gm:0, parent-vif:2
18:39:30.057 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.062 sent prune for (171.69/16 224.2.206.143)/448 on vif 2 to 
130.59.72.10
18:39:30.076 add cache entry (130.240.34.6 224.2.206.143) gm:0, parent-vif:2
18:39:30.083 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.090 sent prune for (130.240/16 224.2.206.143)/524 on vif 2 to 
130.59.72.10
18:39:30.103 add cache entry (130.240.64.47 224.2.213.97) gm:0, parent-vif:2
18:39:30.111 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.116 sent prune for (130.240/16 224.2.213.97)/514 on vif 2 to 
130.59.72.10
18:39:30.128 add cache entry (171.69.242.80 224.2.253.119) gm:0, parent-vif:2
18:39:30.136 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.141 sent prune for (171.69/16 224.2.253.119)/422 on vif 2 to 
130.59.72.10
18:39:30.155 add cache entry (171.69.58.81 224.2.231.173) gm:0, parent-vif:2
18:39:30.164 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.170 sent prune for (171.69/16 224.2.231.173)/499 on vif 2 to 
130.59.72.10
18:39:30.182 add cache entry (130.199.130.181 224.2.206.143) gm:0, parent-vif:2
18:39:30.189 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.194 sent prune for (130.199/16 224.2.206.143)/422 on vif 2 to 
130.59.72.10
18:39:30.207 add cache entry (130.240.34.7 224.2.206.143) gm:0, parent-vif:2
18:39:30.219 add cache entry (45.0.12.137 224.2.250.130) gm:0, parent-vif:2
18:39:30.227 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.232 sent prune for (45.0.12/22 224.2.250.130)/364 on vif 2 to 
130.59.72.10
18:39:30.248 add cache entry (193.167.64.154 224.42.42.2) gm:0, parent-vif:2
18:39:30.255 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.262 sent prune for (193.167.64/23 224.42.42.2)/367 on vif 2 to 
130.59.72.10
18:39:30.275 add cache entry (171.69.60.189 224.2.206.143) gm:0, parent-vif:2
18:39:30.289 add cache entry (129.240.200.195 224.2.17.6) gm:0, parent-vif:2
18:39:30.296 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.301 sent prune for (129.240.200/23 224.2.17.6)/509 on vif 2 to 
130.59.72.10
18:39:30.313 add cache entry (193.167.64.153 224.42.42.4) gm:0, parent-vif:2
18:39:30.321 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.326 sent prune for (193.167.64/23 224.42.42.4)/535 on vif 2 to 
130.59.72.10
18:39:30.338 add cache entry (130.240.64.79 224.2.156.223) gm:0, parent-vif:2
18:39:30.345 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.349 sent prune for (130.240/16 224.2.156.223)/377 on vif 2 to 
130.59.72.10
18:39:30.362 add cache entry (129.89.9.63 224.2.100.102) gm:0, parent-vif:2
18:39:30.371 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.375 sent prune for (129.89.9/24 224.2.100.102)/579 on vif 2 to 
130.59.72.10
18:39:30.387 add cache entry (129.139.8.28 224.52.0.24) gm:0, parent-vif:2
18:39:30.394 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.399 sent prune for (129.139.8/23 224.52.0.24)/331 on vif 2 to 
130.59.72.10
18:39:30.409 add cache entry (129.241.104.60 224.2.206.143) gm:0, parent-vif:2
18:39:30.417 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.422 sent prune for (129.241.104/24 224.2.206.143)/305 on vif 2 to 
130.59.72.10
18:39:30.434 add cache entry (130.240.193.242 224.2.0.1) gm:0, parent-vif:2
18:39:30.441 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.445 sent prune for (130.240/16 224.2.0.1)/569 on vif 2 to 130.59.72.10
18:39:30.457 add cache entry (130.207.8.22 224.2.129.147) gm:0, parent-vif:2
18:39:30.466 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.471 sent prune for (130.207.8/24 224.2.129.147)/420 on vif 2 to 
130.59.72.10
18:39:30.483 add cache entry (128.16.64.19 224.2.143.35) gm:0, parent-vif:2
18:39:30.490 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.495 sent prune for (128.16.64/20 224.2.143.35)/358 on vif 2 to 
130.59.72.10
18:39:30.505 add cache entry (131.136.234.172 224.2.204.125) gm:0, parent-vif:2
18:39:30.515 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.521 sent prune for (131.136.234/24 224.2.204.125)/324 on vif 2 to 
130.59.72.10
18:39:30.533 add cache entry (128.32.32.118 224.2.206.143) gm:0, parent-vif:2
18:39:30.540 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.544 sent prune for (128.32.32/24 224.2.206.143)/511 on vif 2 to 
130.59.72.10
18:39:30.556 add cache entry (128.223.5.95 224.2.130.9) gm:0, parent-vif:2
18:39:30.563 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.569 sent prune for (128.223/16 224.2.130.9)/581 on vif 2 to 
130.59.72.10
18:39:30.581 add cache entry (130.239.40.20 224.2.206.143) gm:0, parent-vif:2
18:39:30.588 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.593 sent prune for (130.239/16 224.2.206.143)/439 on vif 2 to 
130.59.72.10
18:39:30.605 add cache entry (130.246.72.110 224.2.206.143) gm:0, parent-vif:2
18:39:30.612 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.618 sent prune for (130.246.72/22 224.2.206.143)/349 on vif 2 to 
130.59.72.10
18:39:30.624 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:30.631 Updating 100 routes from 130.59.72.10 to 128.178.47.47
18:39:30.643 add cache entry (45.0.12.128 224.2.100.102) gm:0, parent-vif:2
18:39:30.650 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.655 sent prune for (45.0.12/22 224.2.100.102)/448 on vif 2 to 
130.59.72.10
18:39:30.667 add cache entry (131.136.234.172 224.2.183.208) gm:0, parent-vif:2
18:39:30.676 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.681 sent prune for (131.136.234/24 224.2.183.208)/345 on vif 2 to 
130.59.72.10
18:39:30.693 add cache entry (128.93.7.26 224.2.0.1) gm:0, parent-vif:2
18:39:30.699 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.704 sent prune for (128.93/16 224.2.0.1)/300 on vif 2 to 130.59.72.10
18:39:30.717 add cache entry (130.240.64.79 224.2.163.192) gm:0, parent-vif:2
18:39:30.725 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.729 sent prune for (130.240/16 224.2.163.192)/384 on vif 2 to 
130.59.72.10
18:39:30.741 add cache entry (138.25.8.74 224.2.143.35) gm:0, parent-vif:2
18:39:30.748 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.752 sent prune for (138.25.8/23 224.2.143.35)/572 on vif 2 to 
130.59.72.10
18:39:30.766 add cache entry (207.98.65.12 224.2.206.143) gm:0, parent-vif:2
18:39:30.773 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.778 sent prune for (207.98.64/18 224.2.206.143)/401 on vif 2 to 
130.59.72.10
18:39:30.790 add cache entry (138.25.8.74 224.2.224.2) gm:0, parent-vif:2
18:39:30.796 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.801 sent prune for (138.25.8/23 224.2.224.2)/404 on vif 2 to 
130.59.72.10
18:39:30.813 add cache entry (13.2.116.11 224.2.206.143) gm:0, parent-vif:2
18:39:30.821 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.827 sent prune for (13.2.116/22 224.2.206.143)/354 on vif 2 to 
130.59.72.10
18:39:30.836 SENT route report       from 128.178.47.47   to 130.59.72.10
18:39:30.841 update 126 starting at 2174 of 3632
18:39:30.854 ageing entries
18:39:30.865 SENT neighbor probe     from 128.178.47.47   to 224.0.0.4
18:39:30.871 SENT neighbor probe     from 128.178.47.47   to 130.59.72.10
18:39:30.884 SENT route report       from 128.178.47.47   to 130.59.72.10
18:39:30.892 SENT route report       from 128.178.47.47   to 130.59.72.10
18:39:30.899 SENT route report       from 128.178.47.47   to 130.59.72.10
18:39:30.907 SENT route report       from 128.178.47.47   to 130.59.72.10
18:39:30.926 add cache entry (13.2.116.11 224.2.0.1) gm:0, parent-vif:2
18:39:30.933 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.938 sent prune for (13.2.116/22 224.2.0.1)/541 on vif 2 to 
130.59.72.10
18:39:30.949 warning - kernel entry already exists for (24.0.8.69 
224.2.206.143)
18:39:30.969 add cache entry (130.68.20.3 224.2.243.37) gm:0, parent-vif:2
18:39:30.977 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:30.982 sent prune for (130.68/16 224.2.243.37)/468 on vif 2 to 
130.59.72.10
18:39:30.993 add cache entry (129.173.78.20 224.2.206.143) gm:0, parent-vif:2
18:39:30.999 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:31.017 sent prune for (129.173.78/24 224.2.206.143)/300 on vif 2 to 
130.59.72.10
18:39:31.026 warning - kernel entry already exists for (45.0.12.137 
224.2.250.130)
18:39:31.048 add cache entry (130.236.251.42 224.2.206.143) gm:0, parent-vif:2
18:39:31.055 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:31.060 sent prune for (130.236/16 224.2.206.143)/396 on vif 2 to 
130.59.72.10
18:39:31.075 warning - kernel entry already exists for (193.167.64.154 
224.42.42.2)
18:39:31.095 warning - kernel entry already exists for (129.240.200.195 
224.2.17.6)
18:39:31.104 RECV route report       from 130.59.72.10    to 128.178.47.47
18:39:31.110 Updating 78 routes from 130.59.72.10 to 128.178.47.47
18:39:31.126 add cache entry (128.231.200.90 224.2.183.208) gm:0, parent-vif:2
18:39:31.134 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:31.143 sent prune for (128.231.200/23 224.2.183.208)/389 on vif 2 to 
130.59.72.10
18:39:31.155 add cache entry (130.240.64.79 224.2.206.143) gm:0, parent-vif:2
18:39:31.168 warning - kernel entry already exists for (129.139.8.28 
224.52.0.24)
18:39:31.185 add cache entry (45.0.12.168 224.2.250.130) gm:0, parent-vif:2
18:39:31.199 warning - kernel entry already exists for (193.167.64.153 
224.42.42.4)
18:39:31.217 warning - kernel entry already exists for (130.207.8.22 
224.2.129.147)
18:39:31.233 add cache entry (130.140.68.43 224.2.140.0) gm:0, parent-vif:2
18:39:31.245 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:31.249 sent prune for (130.140.68/24 224.2.140.0)/300 on vif 2 to 
130.59.72.10
18:39:31.258 warning - kernel entry already exists for (131.136.234.172 
224.2.204.125)
18:39:31.277 add cache entry (131.196.20.2 224.2.206.143) gm:0, parent-vif:2
18:39:31.284 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:31.295 sent prune for (131.196.20/24 224.2.206.143)/554 on vif 2 to 
130.59.72.10
18:39:31.306 add cache entry (171.69.129.220 224.2.231.173) gm:0, parent-vif:2
18:39:31.323 add cache entry (130.68.20.3 224.2.206.143) gm:0, parent-vif:2
18:39:31.329 SENT prune message      from 128.178.47.47   to 130.59.72.10
18:39:31.334 sent prune for (130.68/16 224.2.206.143)/475 on vif 2 to 
130.59.72.10
18:39:31.348 warning - kernel entry already exists for (131.136.234.172 
224.2.183.208)
18:39:31.366 add cache entry (128.138.213.1 224.2.0.1) gm:0, parent-vif:2
18:39:31.374 SENT prune message      from 128.178.47.47   to 130.59.72.10

                        NetMetrix Packet Report
                        ----------------------------
      105)   60       0.027873  Sun0AB890    DEC0001DC    DLC    Proto=IP    
IP 
    stimon47 -> 130.59.72.10 Id=8a03  --------------

Packet number = 105  Arrival time = 42.978274  Length = 60

------------  DLC Header  ------------
DLC: Destination: DEC_00:01:DC (aa:0:4:0:1:dc)
DLC: Source: Sun_0A:B8:90 (8:0:20:a:b8:90)
DLC: Protocol: IP

------------  IP Header  ------------
IP: Version = 4
IP: Header length = 20
IP: Type of service = Routine(0)
IP: Delay = Normal (0)
IP: Throughput = Normal (0)
IP: Reliability = Normal (0)
IP: Packet length = 40
IP: Id = 8a03
IP: Fragment offset = 0
IP: Flags = [Don't Fragment = 1][More = 0]
IP: Time to live = 255
IP: Protocol = IGMP (2)
IP: Header checksum = 77A9
IP: Source address = stimon47 (128.178.47.47)
IP: Destination address = 130.59.72.10
IP: 20 bytes of data

0000:  AA 00 04 00 01 DC 08 00 - 20 0A B8 90 08 00 45 00   ........ .....E.
0010:  00 28 8A 03 40 00 FF 02 - 77 A9 80 B2 2F 2F 82 3B   .(..@...w...//.;
0020:  48 0A 13 07 A9 90 01 0E - 08 03 82 F0 00 00 E0 02   H...............
0030:  D5 61 00 00 02 02 38 36 - 2E 35 31 2E               .a....86.51.

===============================================================================
=