idnits 2.17.1 draft-ietf-mboned-mdh-01.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-23) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. ** The document is more than 15 pages and seems to lack a Table of Contents. == The page length should not exceed 58 lines per page, but there was 30 longer pages, the longest (page 1) being 63 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 263 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 497 instances of too long lines in the document, the longest one being 26 characters in excess of 72. == There are 52 instances of lines with non-RFC2606-compliant FQDNs in the document. == There are 97 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. == There are 17 instances of lines with multicast IPv4 addresses in the document. If these are generic example addresses, they should be changed to use the 233.252.0.x range defined in RFC 5771 Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 13 has weird spacing: '...), its areas...' == Line 14 has weird spacing: '... its worki...' == Line 18 has weird spacing: '... and may ...' == Line 19 has weird spacing: '...afts as refer...' == Line 22 has weird spacing: '... To learn...' == (258 more instances...) -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (14 October 1998) is 9323 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Unused Reference: '2' is defined on line 1465, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 1468, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1472, but no explicit reference was found in the text == Unused Reference: '5' is defined on line 1475, but no explicit reference was found in the text == Unused Reference: '6' is defined on line 1479, but no explicit reference was found in the text == Unused Reference: '7' is defined on line 1483, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2030 (ref. '1') (Obsoleted by RFC 4330) == Outdated reference: A later version (-14) exists of draft-ietf-idmr-igmp-mib-07 -- Unexpected draft version: The latest known version of draft-ietf-mmusic-sap is -00, but you're referring to -02. -- No information found for draft-ietf-idmr-multi-cast-routmib - is the name correct? == Outdated reference: A later version (-11) exists of draft-ietf-idmr-pim-mib-05 == Outdated reference: A later version (-11) exists of draft-ietf-idmr-dvmrp-mib-03 == Outdated reference: A later version (-07) exists of draft-ietf-idmr-traceroute-ipm-03 Summary: 13 errors (**), 0 flaws (~~), 20 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 MBONE Deployment Working Group Dave Thaler 3 INTERNET-DRAFT Microsoft 4 Category: Informational Bernard Aboba 5 Microsoft 6 14 October 1998 8 Multicast Debugging Handbook 10 1. Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working docu- 13 ments of the Internet Engineering Task Force (IETF), its areas, and 14 its working groups. Note that other groups may also distribute work- 15 ing documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference mate- 20 rial or to cite them other than as ``work in progress.'' 22 To learn the current status of any Internet-Draft, please check the 23 ``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow 24 Directories on ftp.ietf.org (US East Coast), nic.nordu.net (Europe), 25 ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). 27 The distribution of this memo is unlimited. It is filed as , and expires May 1, 1999. Please send com- 29 ments to the authors. 31 2. Abstract 33 This document serves as a handbook for the debugging of multicast con- 34 nectivity problems. In addition to reviewing commonly encountered 35 problems, the draft summarizes publicly distributable multicast diag- 36 nostic tools, and provides examples of their use, along with pointers 37 to source and binary distributions. 39 3. Introduction 41 In order to deploy multicast on a large scale, it is necessary for 42 Network Operations Centers, support personnel and customers to be able 43 to diagnose problems. Over the years a number of tools have been 44 developed that can assist in the diagnostic process. This document 45 serves as a handbook for the debugging of multicast connectivity prob- 46 lems. In addition to reviewing commonly encountered problems, the 47 draft summarizes publicly distributable multicast diagnostic tools, 48 and provides examples of their use, along with pointers to source and 49 binary distributions. 51 4. Usage scenarios 53 Multicast diagnostic tools are typically employed in one of the fol- 54 lowing settings: 56 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 57 | | | 58 | Customer service or | SDR | 59 | support | mtrace | 60 | | RTPmon | 61 | | Dr. Watson | 62 | | | 63 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 64 | | | 65 | | SDR | 66 | | mrinfo | 67 | Network or system | netstat | 68 | administrator | mconfig | 69 | | mstat | 70 | | mtrace | 71 | | RTPmon | 72 | | tcpdump | 73 | | Dr. Watson | 74 | | Duppkts | 75 | | mrouted.dump, mrouted.cache | 76 | | | 77 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 78 | | | 79 | | SDR | 80 | | mrtree | 81 | | map-mbone | 82 | Network Operations | MVIEW | 83 | Center | Multicast heartbeat | 84 | | mwatch and mcollect | 85 | | asn | 86 | | asname | 87 | | | 88 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 90 4.1. Customer service and support 92 ISPs offering multicast services are likely to encounter the following 93 classes of customer questions: 95 Session announcement problems 96 Reception problems 97 Multicast router problems 99 Below we discuss how each of these types of problems may be diagnosed. 101 4.1.1. Session announcement problems 103 Session announcement questions are those which relate to the user's 104 session announcement software. Sample complaints include: 106 No conferences were visible in the session announcement tool 107 Conference X was not visible in the session announcement tool 108 I can see conferences when dialed into POPA, but not POPB 109 I can receive conferences listed in SDR, but sometimes when I join 110 conferences via a Web site, I cannot receive them. 112 Session announcement questions are typically investigated via the fol- 113 lowing procedure: 115 1. If only a specific session announcement is missing, check the ses- 116 sion announcement from somewhere where it is being received, and find 117 the group(s) and ports that the session utilizes, as well as the 118 source IP addresses. If the problem is with all session announce- 119 ments, find the information on any current session announcement which 120 should be seen by the user. 122 2. Find out the user's IP address, if known, and the POP dialed into 123 or router connected to. One way to determine the user's router given 124 their IP address is to mtrace or traceroute to their address. 126 3. Do an mtrace between the session announcement's origin and the 127 receiver on the sap.mcast.net group. If the mtrace succeeds, note any 128 hops showing loss. 130 4. If the mtrace never gets past the receiver itself, check the NASes 131 or routers with mstat -l to see if the relevant group has been joined. 132 If not, the problem is probably with the receiver's host. Ask the 133 user to check with Dr. Watson or a sniffer to see if the router is 134 sending IGMP membership queries, and if the host is responding with 135 membership reports and if so, what versions are being used. 137 5. If the sap.mcast.net group has been joined, but the mtrace failed, 138 the problem is likely a multicast routing problem (see section 4.1.3). 140 6. If the mtrace succeeded, and one hop shows 100% loss, compare the 141 output with the TTL of the session announcement. Users may download 142 session descriptions from Web sites that they may not be in the posi- 143 tion to receive, due to site or regional scoping. The loss may also 144 be the result of a scoped boundary separating the originator and the 145 receiver, which will also be indicated as such by mtrace. 147 7. Otherwise, if the mtrace succeeded, look for hops showing non-neg- 148 ligible loss. These typically denote points of congestion (see sec- 149 tion 4.3.1). Note that if rate-limiting is installed on these con- 150 gested links, session announcements are often lost since SAP traffic 151 is given lower priority. 153 8. If all else fails, request a network sniff from the user, and 154 check whether it shows traffic to sap.mcast.net, and if so, from what 155 sources, and what is being announced. 157 4.1.2. Reception problems 159 Reception questions are those where the user has successfully received 160 the session announcement, but was unable to receive one or more media 161 streams for the session joined. Sample complaints include: 163 I joined conference X, but nothing happened 164 I joined conference X, got video but no audio 165 I joined conference X, and got intermittent audio 166 I can't see source X, but source X can see me (or vice versa) 168 Reception questions are typically investigated via the following pro- 169 cedure: 171 1. Check the session announcement, find the group(s) and ports that 172 the session utilizes, as well as the source IP addresses. 174 2. Find out the user's IP address, if known, and the POP dialed into 175 or router connected to. One way to determine the user's router given 176 their IP address is to mtrace or traceroute to their address. 178 3. Check if the user is sending RTCP reports with RTPmon, and if so, 179 what the loss rate is. 181 4. Do an mtrace between the source and the receiver on the relevant 182 group. If the mtrace succeeds, note any hops showing loss. 184 5. If the mtrace never gets past the receiver itself, check the NASes 185 or routers with mstat -l to see if the relevant group has been joined. 186 If not, the problem is probably with the receiver's host. Check with 187 Dr. Watson to see if the router is sending IGMP membership queries, 188 and if the host is responding with membership reports and if so, what 189 versions are being used. 191 6. If the relevant group has been joined, but the mtrace failed, the 192 problem is likely a multicast routing problem (see section 4.1.3). 194 7. If the mtrace succeeded, and one hop shows 100% loss, compare the 195 output with the TTL of the session announcement. The user may not be 196 in a position to receive data from the source, due to site or regional 197 scoping. The loss may also be the result of a scoped boundary sepa- 198 rating the source and the receiver, which will also be indicated as 199 such by mtrace. 201 8. Otherwise, if the mtrace succeeded, look for hops showing non-neg- 202 ligible loss. These typically denote points of congestion (see sec- 203 tion 4.3.1). 205 9. If all else fails, request a network sniff from the user, and 206 check whether it shows traffic to the relevant group, and if so, from 207 what sources. 209 Other reception complaints include: 210 When I join my first conference, it works great. But then when I 211 quit that and join another one, it doesn't work anymore. 213 Why is my modem light is still flashing even after I've quit SDR 214 and VIC? 216 Such problems are often IGMP-related problems observed by a user con- 217 necting to the network using a host which is running a TCP/IP stack 218 implementing IGMP v1. Such users will experience long leave latencies, 219 with resulting poor reception and/or performance of other applica- 220 tions. Such problems can be distinguished from ordinary reception 221 problems in that they typically do not occur for the first session 222 joined, only for subsequent sessions. The solution consists of upgrad- 223 ing the user to an IGMP v2-capable stack. 225 IGMP-related questions are typically investigated by the following 226 procedure: 228 1. Obtain the vendor and version of the user's TCP/IP stack. Deter- 229 mine whether this stack is IGMP v2-enabled. 231 2. Ask the user to run Dr. Watson or a network sniffer and to indi- 232 cate whether IGMP queries are being seen, whether responses are being 233 sent, and if so, what version. 235 4.1.3. Multicast router problems 237 Multicast router questions are those which relate to the setup of a 238 multicast router. Sample complaints include: 240 I can get video and audio when online with ISDN, but not with a 241 modem, or vice versa. 243 I can't bring up a DVMRP tunnel to my site. Why not? 245 My router works great. Why can't I get multicast? 247 Why can't I source multicast? 249 Multicast routing questions are typically investigated via the follow- 250 ing procedure: 252 1. Ask the user what the router vendor is, and what software version 253 they have running. Attempt to verify this information using mrinfo or 254 mstat. 256 2. Check whether this vendor and version supports multicast routing, 257 and whether an upgrade to a later version is recommended. 259 3. Ask for a copy of the router configuration file. 261 4. Check whether the user has NAT enabled; this is incompatible with 262 most multicast routing protocols, and so should be switched off. 264 5. Find out the user's IP address(es), or if not known, the POP dialed 265 into or router connected to. 267 6. Check the loss rate and connectivity by doing an mtrace from vari- 268 ous sources to the user's IP address. 270 7. Check the user's router with mstat -l to see if it has joined any 271 multicast groups, and check upstream routers to see if they are sub- 272 scribed to any groups. 274 8. When all else fails, request a network sniff and examine it to 275 determine what multicast routing protocols are being run, if any. 277 4.2. Network Operations Center 279 A Network Operations Center (NOC) will typically receive a complaint 280 after it has been investigated by customer support and determined to 281 be a network-related issue. Although it is desirable for customer sup- 282 port to have performed the diagnostic tests described above, if this 283 has not been done, NOC personnel will need to perform the tests them- 284 selves to isolate the cause of the problem. If the proper systems have 285 been installed, in most cases, the NOC will already have been alerted 286 to the problem prior to receiving referrals from customer support. The 287 following diagnostic procedures are recommended: 289 1. Regularly generate summaries based on RTCP receiver and sender 290 reports, using RTP monitoring tools. Sample reports may include aver- 291 age loss rates experienced during sessions, or users whose loss rates 292 exceed a particular threshold. 294 2. Determine the source of the problems by doing mtraces between the 295 sources and the receivers. 297 3. On a network monitoring station, keep track of the functioning of 298 multicast-enabled hardware, either by doing periodic mtraces, or by 299 using a heartbeat monitor to receive SNMP traps from equipment losing 300 the heartbeat. 302 4. In order to keep track of group topologies, use mapping tools such 303 as map-mbone, MVIEW, or mrtree, along with autonomous system mapping 304 tools such as asn and asname. 306 4.3. Network or system administrator 308 The NOC will escalate network engineering problems to network engi- 309 neers and system administrators if their intervention is required. In 310 order to understand the origin of the problem and repair it, it is 311 necessary to diagnose the operations of individual systems and routers 312 using router and system diagnostics such as netstat, mrinfo, mstat, 313 mconfig, RTPmon, and mtrace, as well as network analysis tools such as 314 tcpdump or Dr. Watson. 316 In smaller installations the network engineer or system administrator 317 often doubles as customer support and network operations guru, in 318 which case problems may be escalated without any triage (our condo- 319 lences). 321 Typical classes of problems encountered by network engineers and sys- 322 tem administrators include: 324 Congestion and rate-limiting problems 325 Multicast routing problems 327 4.3.1. Congestion and rate limiting problems 329 Congestion and rate limiting problems result in high packet loss with 330 subsequent loss of session announcements and decrease in quality of 331 audio and video. These problems may be investigated via the following 332 procedure: 334 1. Use RTPmon to check for receivers experiencing packet loss. 336 2. Do an mtrace from the source to the receiver on the relevant group 337 in order to locate the problematic hops. 339 3. Do an mtrace in the opposite direction to help distinguish whether 340 the problem is with the router or the link at that hop. 342 4. If the reverse mtrace shows similar loss at an hop adjacent to the 343 lossy hop in the forward mtrace, odds are that the intermediate router 344 is overloaded. Use mrinfo to check the fanout on the router. Over- 345 loaded routers are often the result of having too many tunnels. 347 5. If the reverse mtrace shows no problems near that hop, indicating 348 that loss is one-way, then check the router on the upstream end of the 349 link with mstat -nv to see if it has a rate-limit set on the link, and 350 if the link traffic is near that limit. 352 6. If the reverse mtrace shows loss over the same link, the problem is 353 likely to be link congestion. Use mstat -nv to see how much bandwidth 354 is being used by multicast traffic. (If mstat fails, running an 355 mtrace with the -T option may help to confirm link congestion, 356 although the statistics can be misleading.) 358 7. If a congested link is suspected, but mstat failed, another indica- 359 tor can be obtained by doing an mtrace from the session announcer to 360 the destination on other groups joined by the receiver, such as the 361 SAP group, and comparing loss statistics. 363 8. Check for unicast packet loss over the link using ping. Multicast 364 (but not unicast) packet loss on a link with a rate limit is an indi- 365 cation that the link's multicast rate limit should be raised or elimi- 366 nated entirely. Packet loss on a link without rate limiting is an 367 indication of congestion. On such links it may be desirable to add a 368 rate limit. Since DVMRP prunes are currently not retransmitted by most 369 routers, prunes may be lost if no rate limit exists, which may further 370 worsen the congestion problem. 372 9. Use mstat -gR to see whether a single group is using an inordinate 373 amount of the link bandwidth. If so, use mstat to see whether a sin- 374 gle source to that group is using an inordinate amount of the link 375 bandwidth. If so, attempt to contact the source (contact information 376 may be available in the session announcement). 378 4.3.2. Multicast routing problems 380 Multicast routing problems include: 382 Duplicate packets 383 Injection of bogus routes (typically into DVMRP) 384 Redistribution of unicast routes (via BGP or an IGP) into DVMRP 385 Non-pruning routers 387 Duplicate packets are a symptom of routing loops. This problem may be 388 investigated via the following procedure: 390 1. Use a program such as Duppkts to detect duplicate packets. 392 2. Use a network monitor or RTPmon to find the sources and receivers 393 on the group. 395 3. Do an mtrace from the source(s) to the receivers in order to find 396 the loop. Duplicates will also show up in mtrace output as hops with 397 negative loss. 399 Bogus route injection problems may be investigated via the following 400 procedure: 402 1. Dump the DVMRP routing table. The routing table may be examined 403 remotely via mstat using the -r options, or locally (for mrouted) by 404 sending the USR1 signal to mrouted, generating the 405 /var/tmp/mrouted.dump file. 407 2. Check the table for bogus routes (known as "martians"). Bogus 408 routes include addresses reserved for use by private internets, as 409 described in [9]. These routes include 10/8, 172.16/12, or 192.168/16, 410 or more specific routes within these regions. Injecting a default 411 route into the DVMRP backbone is also considered to be a bogus route. 413 3. Locate the origin of the bogus routes by doing an mtrace to an IP 414 address in the bogus range. 416 Symptoms of unicast route redistribution are injection of a large num- 417 ber of unicast routes (25K+) into DVMRP. The problem may be investi- 418 gated via the following procedure: 420 1. Examine the routing table. The DVMRP routing table may be examined 421 remotely via mstat -r, or locally (for mrouted) by sending the USR1 422 signal to mrouted, generating the /var/tmp/mrouted.dump file. For 423 protocol independent multicast routing protocols (such as Sparse-Mode 424 PIM), examine the unicast routing table. 426 2. Check if a single site is the predominant route injector. This 427 site is likely to be the problem. One way to check this is to mtrace 428 to addresses in a number of "suspect" prefixes. 430 3. If your router supports it, set a route limit on the DVMRP tunnel 431 interface. A limit of 7000 routes is currently recommended. You may 432 also wish to set "route-hog notification" at 5000 routes. 434 Non-pruning DVMRP routers are those which maintain groups in the mul- 435 ticast routing table although there are no downstream subscribers. The 436 problem can be solved via the following procedure: 438 1. Check the router version number using mstat or mrinfo. Non-pruning 439 routers include mrouted versions prior to 3, Cisco Systems IOS prior 440 to version 11.0(3), and Bay Networks implementations prior to 9.0. 442 2. Confirm lack of pruning as follows. First, dump the multicast for- 443 warding table. This can be done remotely with mstat -N, or locally 444 (for mrouted) by sending the USR2 signal to mrouted, generating the 445 /var/tmp/mrouted.cache file. 447 3. Check the forwarding table to see if an interface is in the outgo- 448 ing interface list for every entry in the multicast forwarding table. 449 If so, it is likely that a non-pruner lies downstream in that direc- 450 tion. 452 4. You can confirm the existence of a non-pruner by creating a tempo- 453 rary, unadvertised, session and sending (preferably with a low data 454 rate) data to that group. After a few moments, dump the forwarding 455 table again. If any interfaces appear in the outgoing interface list 456 of the entry for your test stream, then non-pruners lie in those 457 directions. 459 5. If a non-pruner exists downstream, use mrtree to follow the path of 460 the data downstream to the non-pruning router(s). 462 6. If your router supports it, enable the reject non-pruners option. 463 If not, and the unpruned interface is a tunnel, consider disabling the 464 tunnel. 466 5. Appendix - Multicast Diagnostic Tools 468 5.1. Types of tools 470 Multicast diagnostic tools typically fall into the following cate- 471 gories: 473 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 474 | | | 475 | RTP monitoring tools | RTPmon | 476 | | Msessmon | 477 | | RTPquality | 478 | | RTPdump | 479 | | RTPcast/RTPlisten | 480 | | Duppkts | 481 | | | 482 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 483 | | | 484 | | mrinfo | 485 | Multicast router | netstat | 486 | diagnostics | mconfig | 487 | | mstat | 488 | | mrouted.dump, mrouted.cache | 489 | | | 490 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 491 | | | 492 | Multicast traceroute | mtrace | 493 | | | 494 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 495 | | | 496 | | mrtree | 497 | | map-mbone | 498 | MBONE mapping tools | asn | 499 | | asname | 500 | | mcollect & mwatch | 501 | | | 502 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 503 | | | 504 | NOC tools | MVIEW | 505 | | Multicast heartbeat | 506 | | | 507 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 508 | | | 509 | Network analysis | tcpdump | 510 | tools | Dr. Watson | 511 | | | 512 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 514 RTP monitoring tools are used to monitor the transmission quality and 515 popularity of individual sessions. Multicast router diagnostics are 516 used to obtain information on the configuration and state of multicast 517 routers. MBONE mapping tools are used to map out the topology for a 518 particular group. These tools can show the topology at the level of 519 individual systems, or at the level of autonomous system connections. 520 Multicast traceroute tools are used to trace the path between a source 521 and destination. Network Operations Center tools are used to monitor 522 the state of network devices within an autonomous system. Network 523 analysis tools (such as tcpdump and Dr. Watson) are used to analyze 524 traffic on the network. 526 5.2. Facilities utilized 528 Multicast diagnostic tools typically rely on one or more of the fol- 529 lowing facilities: 531 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 532 | | | 533 | RTCP source and | RTPmon | 534 | receiver reports | Msessmon | 535 | | RTPquality | 536 | | RTPdump | 537 | | RTPcast/RTPlisten | 538 | | Duppkts | 539 | | | 540 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 541 | | | 542 | | multicast heartbeat | 543 | SNMP MIBs | mconfig | 544 | | mstat | 545 | | MVIEW | 546 | | mrtree | 547 | | | 548 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 549 | | | 550 | IGMP trace facility | mtrace | 551 | | | 552 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 553 | | | 554 | | mrinfo | 555 | | mrtree | 556 | IGMP ASK_NEIGHBORS | map-mbone | 557 | message (DVMRP) | | 558 | | | 559 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 560 | | | 561 | Routing arbiter and | asn | 562 | WHOIS Databases | asname | 563 | | | 564 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 565 | | | 566 | Internal structures | tcpdump | 567 | | netstat | 568 | | mrouted.dump, mrouted.cache | 569 | | | 570 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 572 Tools using RTCP reports analyze RTCP source and receiver reports, 573 providing information on packet loss, inter-arrival jitter, bandwidth 574 availability, or listenership. These tools therefore will only work 575 with RTP implementations which support RTCP reporting. Tools using 576 SNMP MIBs perform queries for variables in the IGMP, multicast rout- 577 ing, DVMRP, and PIM MIBs. As a result, these tools depend on implemen- 578 tation of the relevant SNMP MIBs in the network devices that are being 579 monitored. Tools based IGMP ASK_NEIGHBORS messages use these messages 580 to map portions of the MBONE, and thus will only work with routers 581 implementing DVMRP. Tools based on IGMP tracing perform a multicast 582 traceroute. These tools are typically only useful in cases where mul- 583 ticast routers along the path have a route back to the source. 585 Diagnostic tools may use more than one of these facilities. For exam- 586 ple, mstat makes use of SNMP MIBs, as well as the IGMP ASK_NEIGHBORS 587 facility. 589 5.3. RTP monitoring tools 591 This class of tools provides information required to monitor the per- 592 formance of RTP-based applications. 594 5.3.1. RTPmon 596 Authors 598 David Bacher, Andrew Swan, and Lawrence A. Rowe 599 {drbacher,aswan,rowe}@cs.berkeley.edu 600 Computer Science Division - EECS 601 University of California 602 Berkeley, CA 94720-1776 604 Description 606 RTPmon allows network administrators or support personnel to moni- 607 tor listenership as well as session quality experienced by sub- 608 scribers. The tool also facilitates tracing the cause of problems 609 resulting in quality degradation. To accomplish this task, RTPmon 610 summarizes and analyzes information provided by RTCP source and 611 receiver reports. 613 Receivers are displayed for a given sender in the form of a spread- 614 sheet, with cells being filled in with metrics such as packet loss 615 rate or jitter. Clicking on a cell displays a stripchart of statis- 616 tics on packet loss rate, smoothed packet loss rate and jitter. 617 From the stripchart it is possible to launch an mtrace between the 618 sender and the receiver, a convenient way of diagnosing network 619 problems along the multicast distribution path. Clicking on a 620 receiver or sender displays summary information. 622 For groups with large memberships, the display may be limited to 623 members surpassing a given threshold in packet loss rate or jitter. 624 Using RTPmon it is possible to sort receivers for a given sender 625 according to maximum or average loss. 627 Further information is available in the RTPmon man page. 629 Example 631 For examples and further information, see the rtpmon man page, or: 633 http://bmrc.berkeley.edu/~drbacher/projects/mm96-demo/ 635 Facilities used 637 RTCP source and receiver reports 638 IGMP multicast trace (if installed) 640 Availability 642 RTPmon is available for UNIX and may be obtained from: 643 ftp://mm-ftp.cs.berkeley.edu/pub/rtpmon/ 645 Bug reports and suggestions should be sent to: 646 rtpmon@bmrc.berkeley.edu. 648 5.3.2. RTPcast/RTPlisten, RTPquality, Duppkts, RTPdump, RTPtools, 649 Msessmon, Mpoll 651 Author 652 Mpoll: Andrew Patrick 654 Description 656 RTPcast listens to RTCP receiver reports and forwards data to 657 another multicast group; RTPlisten then listens to that group. RTP- 658 dump listens for, and dumps RTP and RTCP packets. Duppkts listens 659 on a multicast group and port, and reports the number of packets 660 received and lost, as well as the number of duplicates. RTPquality 661 listens to RTCP receiver reports and writes data on packet loss, as 662 well as late and non-sequenced packets. RTPtools allows recording 663 and playback of RTP sessions. Msessmon provides a routemap of par- 664 ticipants in RTP conferences as well as stripcharts of statistics 665 on RTP packet loss and jitter. Mpoll is a survey collection tool 666 that can be used to collect quality ratings during multicast ses- 667 sions. 669 Example 671 Information on these tools is available from: 672 http://sauce.mmlab.uninett.no/mice-nsc/tools.html 674 Facilities used 676 RTCP source and receiver reports 678 Availability 680 Binaries for RTPcast/RTPlisten are available from: 681 ftp://sauce.uio.no/mice-nsc/util/rtp 683 Source code for RTPquality is available from: 684 ftp://sauce.uio.no/mice-nsc/util/rtp/rtpqual.c 685 Source code for RTPdump is available at: 686 ftp://sauce.uio.no/mice-nsc/util/rtpdump-1.0.tar.gz 688 Source code for RTPtools is available at: 689 ftp://sauce.uio.no/mice-nsc/util/rtptools/rtptools-1.9.tar.gz 691 Source and binaries for Msessmon is available at: 692 ftp://sauce.uio.no/mice-nsc/util/msessmon/ 694 Source and binaries for Mpoll is available at: 695 ftp://sauce.uio.no/mice-nsc/util/mpoll/ 697 5.4. Multicast router diagnostics 699 This class of tools facilitates monitoring and management of multicast 700 routers. 702 5.4.1. mrouted.dump, mrouted.cache 704 Author 706 Bill Fenner, fenner@parc.xerox.com 708 Description 710 Sending the USR1 signal to mrouted dumps the internal routing table 711 to /var/tmp/mrouted.dump; sending the USR2 signal dumps the for- 712 warding cache to /var/tmp/mrouted.cache. 714 Further information on mrouted and the mrouted.dump and 715 mrouted.cache file formats is available in the mrouted man page. 717 Example 719 % cat mrouted.dump 720 vifs_with_neighbors = 2 722 Virtual Interface Table 723 Vif Name Local-Address M Thr Rate Flags 724 0 ed0 128.31.107.1 subnet: 128.31.107/24 1 1 0 querier 725 peers: 128.31.107.249 (3.8) (0xe) 726 groups: 239.109.100.200 727 224.0.0.2 728 224.0.0.4 729 pkts in : 4075 730 pkts out: 0 732 1 ed0 128.31.107.1 tunnel: 204.67.107.11 1 32 500 733 peers: 204.67.107.11 (11.2) (0x1a) 734 pkts in : 0 735 pkts out: 2359 737 Multicast Routing Table (3801 entries) 738 Origin-Subnet From-Gateway Metric Tmr In-Vif Out-Vifs 739 207.10.165.51/32 128.31.107.249 10 20 0 1 740 207.10.165.50/32 128.31.107.249 10 20 0 1 741 206.172.195.32/32 128.31.107.249 9 20 0 1 742 172/8 128.31.107.249 10 20 0 1 743 ... 745 % cat mrouted.cache 746 Multicast Routing Cache Table (198 entries) 747 Origin Mcast-group CTmr Age Ptmr IVif Forwvifs 748 131.107.2.139/32 224.0.12.0 58s 7m - -1 749 >131.107.2.139 750 143.107.103.0/27 224.0.1.1 3m 2m 3m 0P 751 >143.107.103.5 752 128.232/16 224.0.1.1 4m 7m 4m 0P 753 >128.232.2.209 754 157.161/16 224.0.1.1 67s 6m - 0 1 755 >157.161.114.2 756 206.152.163/24 224.0.1.15 74s 7m - 0 1 757 >206.152.163.21 758 4.0.0.34/32 224.0.1.32 56s 4m 25s 0P 1p 759 >4.0.0.34 760 137.39.2.254/32 224.0.1.32 3m 5m - 0 1 761 >137.39.2.254 762 137.39.43.32/30 224.0.1.32 38s 5m - 0 1 763 >137.39.43.34 764 ... 766 Facilities used 768 Internal facilities (forwarding cache and routing table) 770 Availability 772 The SNMP-capable mrouted distribution is available at: 773 ftp://ftp.merit.edu/net-research/mbone/mirrors/mrouted/ 775 5.4.2. mrinfo 777 Author 779 Van Jacobson, van@ee.lbl.gov 781 Description 783 mrinfo displays information about a multicast router; to do this, 784 it uses the IGMP ASK_NEIGHBORS message to discover the router's 785 physical and virtual interfaces. Routers are also queried for their 786 version number, and if this query is successful, for their metrics, 787 thresholds, and flags. Results are printed in an indented list for- 788 mat similar to that for map-mbone. 790 Example 792 % mrinfo 192.80.214.199 793 192.80.214.199 (collegepk-mbone1.bbnplanet.net) [version 11.2,prune,mtrace,snmp]: 794 128.167.252.196 -> 0.0.0.0 (local) [1/0/pim/querier/leaf] 795 192.80.214.199 -> 0.0.0.0 (local) [1/0/pim/querier/leaf] 796 192.41.177.196 -> 0.0.0.0 (local) [1/0/pim/querier/down/leaf] 797 128.167.252.196 -> 128.167.254.165 (devo.sura.net) [1/32/tunnel/querier/down/leaf] 798 128.167.252.196 -> 131.119.0.197 (paloalto-mbone1.bbnplanet.net) 799 [1/64/tunnel/pim/querier] 800 128.167.252.196 -> 199.94.207.2 (cambridge1-mbone1.bbnplanet.net) 801 [1/32/tunnel/pim/querier] 802 128.167.252.196 -> 137.39.43.34 (MBONE1.UU.NET) [1/32/tunnel/querier] 803 128.167.252.196 -> 192.41.177.199 (wtn-ms2.bbnplanet.net) [1/16/tunnel/querier] 804 128.167.252.196 -> 128.244.93.3 (sage.jhuapl.edu) [1/32/tunnel/querier] 805 128.167.252.196 -> 192.221.34.22 (cdrn.bbnplanet.net) [1/32/tunnel/querier] 806 128.167.252.196 -> 128.167.1.197 (cpk-ms1.ser.bbnplanet.com) [1/16/tunnel/querier] 807 128.167.252.196 -> 134.205.93.150 (dilbert.sam.pentagon.mil) [1/32/tunnel/querier] 808 128.167.252.196 -> 192.221.48.234 (atlanta3-mbone1.bbnplanet.net) 809 [1/64/tunnel/pim/querier] 810 128.167.252.196 -> 204.167.201.38 (dallas2-mbone1.bbnplanet.net) 811 [1/64/tunnel/pim/querier] 812 128.167.252.196 -> 205.130.85.3 (philipii.nap.edu) [1/32/tunnel/querier/down/leaf] 813 128.167.252.196 -> 128.175.13.36 (pfet.nss.udel.edu) [1/32/tunnel/querier/down/leaf] 814 128.167.252.196 -> 192.41.177.197 (wtn-ms1.bbnplanet.net) [1/32/tunnel/querier] 815 128.167.252.196 -> 204.148.62.28 (mbone-e.ans.net) [1/32/tunnel/querier] 816 128.167.252.196 -> 205.128.246.2 (usnrctc.bbnplanet.net) [1/32/tunnel/pim/querier] 818 Facilities used 820 IGMP ASK_NEIGHBORS message (DVMRP) 822 Availability 824 mrinfo is available for UNIX and is included in the SNMP-capable 825 mrouted distribution, available at: 826 ftp://ftp.merit.edu/net-research/mbone/mirrors/mrouted/ 828 mrinfo is also available in the MVIEW distribution, available at: 829 ftp://ftp.merit.edu/net-research/mbone/mview/ 831 5.4.3. netstat 833 Author 835 Unknown 837 Description 839 On multicast-enabled systems, netstat is typically extended so as 840 to provide information on virtual interfaces and the multicast for- 841 warding cache (-g option), as well as multicast routing statistics 842 (-gs option), and igmp behavior (-s option). 844 Example 846 %netstat -g 848 Virtual Interface Table 849 Vif Thresh Rate Local-Address Remote-Address Pkts-In Pkts-Out 850 0 1 0 128.15.2.120 16323 385 851 1 32 512 128.15.2.120 202.34.126.2 2 0 853 Multicast Forwarding Cache 854 Origin Group Packets In-Vif Out-Vifs:Ttls 855 128.15.2.120 224.2.195.166 281 0 856 128.15.1.110 239.100.101.223 1660 0 857 128.15.1.135 238.27.27.1 1660 0 858 128.15.1.110 239.111.111.235 1660 0 859 ... 861 %netstat -gs 862 multicast forwarding: 863 182880 multicast forwarding cache lookups 864 8237 multicast forwarding cache misses 865 6736 upcalls to mrouted 866 193 upcall queue overflows 867 5567 upcalls dropped due to full socket buffer 868 177 cache cleanups 869 7234 datagrams with no route for origin 870 0 datagrams arrived with bad tunneling 871 0 datagrams could not be tunneled 872 954 datagrams arrived on wrong interface 873 0 datagrams selectively dropped 874 0 datagrams dropped due to queue overflow 875 0 datagrams dropped for being too large 877 %netstat -s 878 ip: 879 3807182 total packets received 880 0 bad header checksums 881 ... 882 icmp: 883 40 calls to icmp_error 884 0 errors not generated 'cuz old message was icmp 885 ... 886 igmp: 887 18504 messages received 888 0 messages received with too few bytes 889 48 messages received with bad checksum 890 2478 membership queries received 891 0 membership queries received with invalid field(s) 892 194 membership reports received 893 0 membership reports received with invalid field(s) 894 0 membership reports received for groups to which we belong 895 8510 membership reports sent 896 tcp: 897 10705 packets sent 898 5536 data packets (1532081 bytes) 899 ... 900 udp: 901 3104045 datagrams received 902 0 with incomplete header 903 ... 905 Facilities used 907 Netstat accesses system internal data structures in order to carry 908 out its function. 910 Availability 912 netstat is included with a variety of operating systems, including 913 UNIX, OS/2, and Windows. For further information, please consult 914 the netstat man page or documentation. 916 5.4.4. mstat 918 Author 920 Dave Thaler, dthaler@microsoft.com 922 Description 924 mstat is a general purpose tool for obtaining router configuration 925 and status information. In order to perform its task, mstat uti- 926 lizes SNMP MIBs (such as the IGMP, multicast routing, PIM, and 927 DVMRP MIBs), as well as ASK_NEIGHBORS IGMP messages. mstat displays 928 the contents of various MBONE-related data structures in various 929 formats, depending on the options selected. Options include: 931 -G Show the PIM group table 932 -I Show the PIM interface table. 933 -K Show the cached IP multicast route table; works for 934 all SNMP-capable routers. 935 -N Show the IP Multicast Next Hop Table. 936 -P Show the PIM neighbor table. 937 -a Show the alternate subnet table. 938 -b Show the scoped boundary table. 939 -d Show the DVMRP neighbor table. 940 -g Show the Group Summary table. 941 -i Show the DVMRP interface table; similar to an 942 mrinfo report. 943 -l Show the IGMP local group table. 944 -r Show the DVMRP routing table; similar to a portion of 945 the mrouted.dump file. 946 -t Show the DVMRP routing next hop table; similar to 947 another portion of the mrouted.dump file. 948 -v Show statistics corresponding to the DVMRP interface table. 950 Examples 952 % mstat 953 IP Multicast Route Table for bigco.com 954 Mcast-group Origin-Subnet InIf UpTime Tmr Pkts Bytes RpF Proto 955 NTP.MCAST.NET 0.0.0.0/32 0 245341 179 0 0 0 pim 956 NTP.MCAST.NET 128.232.0.49/32 7 206403 418 3056 293376 17 dvmrp 957 NTP.MCAST.NET 128.232.2.209/32 7 206403 417 3027 290592 19 dvmrp 958 NTP.MCAST.NET 143.107.103.5/32 7 592 218 3 228 3 dvmrp 959 NTP.MCAST.NET 157.161.114.2/32 7 27703 517 411 31236 11 dvmrp 960 IETF-2-VIDEO.MC 0.0.0.0/32 0 245349 175 0 0 0 pim 961 IETF-2-VIDEO.MC 206.152.163.21/32 7 242567 244 46887 4149336 3388 dvmrp 962 MTRACE.MCAST.NE 0.0.0.0/32 0 1690 177 0 0 0 pim 963 MTRACE.MCAST.NE 194.104.0.25/32 7 405 483 2 792 0 dvmrp 964 MTRACE.MCAST.NE 206.54.224.150/32 7 456 569 4 1072 4 dvmrp 965 CISCO-RP-DISCOV 0.0.0.0/32 0 245534 0 0 0 0 pim 966 224.0.14.1 203.15.123.99/32 4 17 161 0 0 0 dvmrp 967 224.0.92.3 171.68.201.39/32 4 174 4 0 0 0 dvmrp 968 224.2.0.1 13.2.116.11/32 4 150 26 0 0 0 dvmrp 969 224.2.0.1 128.32.38.218/32 4 147 30 0 0 0 dvmrp 970 224.2.2.1 205.226.8.183/32 4 146 30 0 0 0 dvmrp 971 224.2.20.165 13.2.116.11/32 4 55 119 0 0 0 dvmrp 972 224.2.100.100 13.2.116.11/32 4 87 91 0 0 0 dvmrp 973 SAP.MCAST.NET 164.67.63.7/32 4 114 64 1 855 0 dvmrp 974 SAP.MCAST.NET 193.61.212.130/32 4 153 23 1 868 0 dvmrp 975 SAP.MCAST.NET 199.94.220.184/32 4 26 152 1 416 0 dvmrp 976 SAP.MCAST.NET 206.154.213.242/32 4 156 19 1 360 0 dvmrp 977 ... 979 Examples of the many other options are provided in the mstat man pages. 981 Facilities used 983 PIM, DVMRP, IGMP, and multicast routing MIBs 984 IGMP ASK_NEIGHBORS message (DVMRP) 986 Availability 988 mstat is included in the SNMP-capable mrouted distribution, 989 available at: 990 ftp://ftp.merit.edu/net-research/mbone/mirrors/mrouted/ 992 mstat is also available in the MVIEW distribution, available at: 993 ftp://ftp.merit.edu/net-research/mbone/mview/ 995 5.4.5. mconfig 997 Author 999 Dave Thaler, dthaler@microsoft.com 1001 Description 1002 mconfig allows the user to display and (if the community string is 1003 known) to modify the configuration of a multicast router implement- 1004 ing the DVMRP MIB. 1006 Example 1008 For more information on mconfig, please see the man page. 1010 Facilities used 1012 DVMRP MIB 1014 Availability 1016 mconfig is available for UNIX and is included in the SNMP-capable 1017 mrouted distribution, available at: ftp://ftp.merit.edu/net- 1018 research/mbone/mirrors/mrouted/ 1020 5.5. Multicast traceroute 1022 5.5.1. mtrace 1024 Author 1026 Bill Fenner, fenner@parc.xerox.com 1028 Description 1030 mtrace provides a facility by which to trace the path between a 1031 sender and a receiver of a particular group. This is particularly 1032 useful when used alongside a facility such as RTPmon, which allows 1033 you to identify problem source-receiver pairs. 1035 Note that the utility of mtrace is often limited by the multicast 1036 topology. Where multicast and unicast topologies are not aligned 1037 (as is the case in many multicast-enabled networks) mtrace may not 1038 function. 1040 For information on the details of the protocol, see reference [8]. 1042 Example 1044 % mtrace 131.243.73.36 128.15.1.250 224.2.195.166 1045 Mtrace from 131.243.73.36 to 128.15.1.250 via group 224.2.195.166 1046 Querying full reverse path... * switching to hop-by-hop: 1047 0 bigman.bigco.com (128.15.1.250) 1048 -1 * * littleman.bigco.com (128.15.1.249) DVMRP thresh^ 1 1049 -2 * * * seamr1-gw.nwnet.net (192.35.180.201) DVMRP thresh^ 32 1050 -3 * * seamr2-gw.nwnet.net (192.220.238.130) DVMRP thresh^ 0 1051 -4 * * mcast.cac.washington.edu (140.142.116.1) DVMRP thresh^ 32 1052 -5 * * * * dec3800-1-fddi-0.Sacramento.mci.net (204.70.164.29) didn't respond 1053 -6 * * * 1054 -7 * * 1055 Resuming... 1056 -5 dec3800-1-fddi-0.Sacramento.mci.net (204.70.164.29) DVMRP thresh^ 64 1057 -6 dec3800-2-fddi-0.SanFrancisco.mci.net (204.70.158.61) DVMRP thresh^ 1 1058 -7 mbone.nsi.nasa.gov (192.203.230.241) DVMRP thresh^ 64 1059 -8 * * llnl-mr2.es.net (134.55.12.229) DVMRP thresh^ 64 1060 -9 * * lbl-mr1.es.net (134.55.12.101) DVMRP thresh^ 8 1061 -10 * * mr1.lbl.gov (131.243.64.184) DVMRP thresh^ 32 1062 -11 * * ir40gw.lbl.gov (131.243.64.1) DVMRP thresh^ 0 1063 -12 * * irals.lbl.gov (131.243.128.6) PIM thresh^ 0 1064 -13 bl7-36.als.lbl.gov (131.243.73.36) 1065 Round trip time 74 ms; total ttl of 72 required. 1067 Waiting to accumulate statistics... Results after 10 seconds: 1069 Source Response Dest Overall Packet Statistics For Traffic From 1070 131.243.73.36 128.15.1.250 Packet 131.243.73.36 To 224.2.195.166 1071 v __/ rtt 77 ms Rate Lost/Sent = Pct Rate 1072 131.243.73.1 1073 131.243.128.6 irals.lbl.gov 1074 v ^ ttl 1 6 pps 0/60 = 0% 6 pps 1075 131.243.128.40 1076 131.243.64.1 ir40gw.lbl.gov 1077 v ^ ttl 2 13 pps 0/60 = 0% 6 pps 1078 131.243.64.184 mr1.lbl.gov 1079 v ^ ttl 35 9 pps 0/60 = 0% 6 pps 1080 198.128.16.13 1081 134.55.12.101 lbl-mr1.es.net 1082 v ^ ttl 35 0 pps 0/60 = 0% 0 pps 1083 134.55.12.229 llnl-mr2.es.net 1084 v ^ ttl 69 0 pps 1/60 = 2% 0 pps 1085 192.203.230.241 mbone.nsi.nasa.gov 1086 v ^ ttl 70 0 pps 0/59 = 0% 0 pps 1087 204.70.158.61 dec3800-2-fddi-0.SanFrancisco.mci.net 1088 v ^ ttl 70 0 pps 0/59 = 0% 0 pps 1089 204.70.164.29 dec3800-1-fddi-0.Sacramento.mci.net 1090 v ^ ttl 72 0 pps 0/59 = 0% 0 pps 1091 140.142.116.1 mcast.cac.washington.edu 1092 v ^ ttl 72 0 pps 0/59 = 0% 0 pps 1093 192.220.249.66 1094 192.220.238.130 seamr2-gw.nwnet.net 1095 v ^ ttl 72 0 pps 0/59 = 0% 0 pps 1096 192.220.238.129 1097 192.35.180.201 seamr1-gw.nwnet.net 1098 v ^ ttl 72 0 pps 0/59 = 0% 0 pps 1099 128.15.1.249 littleman.bigco.com 1100 v __ ttl 72 0 pps ?/59 0 pps 1101 128.15.1.250 128.15.1.250 1102 Receiver Query Source 1104 Facilities used 1106 IGMP multicast trace facility 1108 Availability 1110 mtrace is now distributed independently of mrouted. 1111 Source code is available from: 1112 ftp://ftp.parc.xerox.com/pub/net-research/ipmulti/mtrace5.1.tar.Z 1114 Binaries: 1115 ftp://ftp.parc.xerox.com/pub/net-research/ipmulti/mtrace5.1-sparc-sunos41x.tar.Z 1116 ftp://ftp.parc.xerox.com/pub/net-research/ipmulti/mtrace5.1-sparc-solaris2.tar.Z 1117 ftp://ftp.parc.xerox.com/pub/net-research/ipmulti/mtrace5.1-alpha-osf1.tar.Z 1118 ftp://ftp.parc.xerox.com/pub/net-research/ipmulti/mtrace5.1-sgi-irix.tar.Z 1120 5.6. MBONE mapping tools 1122 5.6.1. mrtree 1124 Author 1126 Dave Thaler, dthaler@microsoft.com 1127 Andy Adams, ala@merit.edu 1129 Description 1131 mrtree uses a combination of IGMP and SNMP queries to discover the 1132 actual and potential multicast (sub)trees for a given source and 1133 group, rooted at a given router. An actual tree, discovered using 1134 the multicast routing MIB, consists of routers which are currently 1135 forwarding multicast traffic to a group from a given source. A 1136 potential tree, discovered using the DVMRP MIB, is one which would 1137 exist if every host were a member of the group. 1139 Example 1141 % mrtree mbone.merit.edu 224.2.143.24 204.62.246.73 1142 Actual distribution tree rooted at mbone.merit.edu for group 224.2.143.24 1143 and source 204.62.246.73... 1144 0 mbone.merit.edu (198.108.2.20) [ver 3.8,prune,genid,mtrace], 1145 247390 pkts 1146 1 cujo.merit.edu (198.108.60.97) [ver 3.6,prune,genid,mtrace], 333448 1147 6 pkts (1347%) 1148 2 subnet: 198.108.60/24 1149 2 shockwave.merit.edu (198.108.60.69) [ver 3.8,prune,genid,mtrace,snmp], 1150 1239130 pkts (500%) 1151 1 tibia.cic.net (192.217.65.100) [ver 3.8,prune,genid,mtrace] 1152 ... (No response from tibia.cic.net) 1153 2 fibula.cic.net (192.217.65.101) [ver 3.8,prune,genid,mtrace] ? 1154 2 dcl2.gw.uiuc.edu (192.17.2.8) [ver 1.0] ? 1155 2 goober.mci.net (204.70.104.45) [ver 3.6,prune,genid,mtrace] ? 1156 ... (goober.mci.net did not respond to DVMRP 'NEIGHBORS' msg) 1157 1 a-wing.jvnc.net (130.94.40.6) [ver 3.3] 1158 ... (a-wing.jvnc.net does not support SNMP) 1160 2 liberty-eth0/0.jvnc.net (130.94.40.1) [ver 10.2] ? 1161 2 noc.hpc.org (192.187.8.2) [ver 3.8,prune,genid,mtrace] ? 1162 2 liberty.jvnc.net (130.94.40.201) [ver 10.2] ? 1163 2 dstest.ds.internic.net (198.49.45.4) [ver 3.8,prune,genid,mtrace] ? 1164 2 cybercast.cc.nus.sg (137.132.9.70) [ver 3.6,prune,genid,mtrace] ? 1165 ... (cybercast.cc.nus.sg did not respond to DVMRP 'NEIGHBORS' msg) 1167 Facilities used 1169 DVMRP and multicast routing MIBs 1170 IGMP ASK_NEIGHBORS message (DVMRP) 1172 Availability 1174 mrtree is available for UNIX and is included in the 1175 SNMP-capable mrouted distribution, available at: 1176 ftp://ftp.merit.edu/net-research/mbone/mirrors/mrouted/ 1178 mrtree is also available in the MVIEW distribution, available at: 1179 ftp://ftp.merit.edu/net-research/mbone/mview/ 1181 5.6.2. map-mbone 1183 Author 1185 Pavel Curtis, pavel@parc.xerox.com 1187 Description 1189 map-mbone is useful for discovering the topology within a DVMRP 1190 routing domain; to do this, it uses the IGMP ASK_NEIGHBORS message 1191 to discover the neighbors of the starting router. If the -f 1192 (flooding) option is enabled (this is the default if no starting 1193 router is specified), then once these neighbors are discovered, 1194 they too are queried. This continues until the leaf routers are 1195 reached. This option should be used with care since it can result 1196 in excessive load on multicast routers. 1198 If a starting router is specified but the -f option is not used, 1199 then the search terminates after the first hop routers are discov- 1200 ered, the output of map-mbone is very similar to that for mrinfo. 1201 Routers discovered by map-mbone are queried for their version num- 1202 bers, and if this query is successful, for their metrics, thresh- 1203 olds, and flags, and the results are presented in an indented list 1204 format. 1206 Example 1208 % map-mbone 192.80.214.199 1209 192.41.177.196: alias for 128.167.252.196 1211 128.167.252.196 (collegepk-mbone1.bbnplanet.net): 1212 192.41.177.196: 192.41.177.196 [1/0/querier/down] 1213 192.80.214.199: 192.80.214.199 (collegepk-mbone1.bbnplanet.net) [1/0/querier] 1214 128.167.252.196: 205.128.246.2 (usnrctc.bbnplanet.net) [1/32/tunnel/querier] 1215 204.148.62.28 (mbone-e.ans.net) [1/32/tunnel/querier] 1216 192.41.177.197 (wtn-ms1.bbnplanet.net) [1/32/tunnel/querier] 1217 128.175.13.36 (pfet.nss.udel.edu) [1/32/tunnel/querier/down] 1218 205.130.85.3 (philipii.nap.edu) [1/32/tunnel/querier/down] 1219 204.167.201.38 (dallas2-mbone1.bbnplanet.net) [1/64/tunnel/querier] 1220 192.221.48.234 (atlanta3-mbone1.bbnplanet.net) [1/64/tunnel/querier] 1221 134.205.93.150 (dilbert.sam.pentagon.mil) [1/32/tunnel/querier] 1222 128.167.1.197 (cpk-ms1.ser.bbnplanet.com) [1/16/tunnel/querier] 1223 192.221.34.22 (cdrn.bbnplanet.net) [1/32/tunnel/querier] 1224 128.244.93.3 (sage.jhuapl.edu) [1/32/tunnel/querier] 1225 192.41.177.199 (wtn-ms2.bbnplanet.net) [1/16/tunnel/querier] 1226 137.39.43.34 (MBONE1.UU.NET) [1/32/tunnel/querier] 1227 199.94.207.2 (cambridge1-mbone1.bbnplanet.net) [1/32/tunnel/querier] 1228 131.119.0.197 (paloalto-mbone1.bbnplanet.net) [1/64/tunnel/querier] 1229 128.167.254.165 (devo.sura.net) [1/32/tunnel/querier/down] 1230 128.167.252.196 (collegepk-mbone1.bbnplanet.net) [1/0/querier] 1232 192.80.214.199 (collegepk-mbone1.bbnplanet.net): alias for 128.167.252.196 1234 Facilities used 1236 IGMP ASK_NEIGHBORS message (DVMRP) 1238 Availability 1240 map-mbone is available for UNIX, and the software and manual pages are included 1241 in the SNMP-capable mrouted distribution, available at: 1242 ftp://ftp.merit.edu/net-research/mbone/mirrors/mrouted/ 1244 5.6.3. asn 1246 Author 1248 Dave Thaler, dthaler@microsoft.com 1250 Description 1252 asn gives the AS number of a given IP address by querying the rout- 1253 ing arbiter database. 1255 Example 1257 % asn 141.213.10.41 1258 AS237 1260 Facilities used 1262 Routing arbiter database 1264 Availability 1265 asn is included in the MVIEW distribution, available at: 1266 ftp://ftp.merit.edu/net-research/mbone/mview/ 1268 5.6.4. asname 1270 Author 1272 Dave Thaler, dthaler@microsoft.com 1274 Description 1276 asname gets the name of an AS, given the AS number by querying the 1277 WHOIS database. 1279 Example 1281 % asname 237 1282 NSFNETTEST14-AS 1284 Facilities used 1286 WHOIS database 1288 Availability 1290 asname is included in the MVIEW distribution, available at: 1291 ftp://ftp.merit.edu/net-research/mbone/mview/ 1293 5.7. Network Operations Center tools 1295 These tools are suitable for use in a Network Operations Center. 1297 5.7.1. MVIEW 1299 Authors 1301 Dave Thaler, dthaler@microsoft.com 1302 Andy Adams, ala@merit.edu 1304 Description 1306 MVIEW uses utilities such as mstat, mtrace, mrtree, asn and asname 1307 in order to produce a graphical depiction of the multicast network 1308 topology and the actual and potential multicast trees for a given 1309 group and source. 1311 Example 1313 Further information on MVIEW as well as examples are available from: 1314 http://www.merit.edu/net-research/mbone/mviewdoc/Welcome.html 1316 Facilities used 1318 PIM, DVMRP, IGMP, and multicast routing MIBs (mstat) 1319 IGMP ASK_NEIGHBORS message (mrinfo) 1320 Routing arbiter database (asn) 1321 WHOIS database (asname) 1323 Availability 1325 MVIEW is available for UNIX, and can be obtained from: 1326 ftp://ftp.merit.edu/net-research/mbone/mview/ 1328 Documentation is available as: 1329 ftp://ftp.merit.edu/net-research/mbone/mviewdoc/ 1331 5.7.2. Multicast heartbeat 1333 Author 1335 Many and various 1337 Description 1339 Devices implementing the multicast heartbeat listen on a designated 1340 group. If traffic is not observed on the group for a specified 1341 amount of time, an SNMP trap is generated. This allows multicast 1342 monitoring to be easily integrated into existing SNMP consoles. In 1343 situations where a shared-tree multicast routing protocol is used 1344 (such as sparse-mode PIM or CBT), it is recommended that the heart- 1345 beat generator be located close to the RP or core nodes, so as that 1346 loss of the heartbeat will correlate closely with loss of connec- 1347 tivity to the RP or core. Suitable heartbeat mechanisms include 1348 SNTP, which uses the group 224.0.1.1 (ntp.mcast.net) and UDP port 1349 123; and SAP, which uses the group 224.2.127.254 (sap.mcast.net) 1350 and UDP port 9875. 1352 Example 1354 For further information on SNTP, consult [1]. 1356 Facilities used 1358 SNTP (for time-based heartbeats) 1359 SAP (for session announcement heartbeats) 1360 SNMP traps (for alerts) 1362 Availability 1363 5.8. Network analysis tools 1365 5.8.1. Dr. Watson, the Network Detective's Assistant (DWTNDA) 1367 Author 1369 Karl Auerbach, karl@cavebear.com 1371 Description 1373 DWTNDA is a general purpose troubleshooting tool with some IP mul- 1374 ticast tools (in addition to a fair number of non-multicast tools). 1375 For example it can watch IGMP "join" activity on a LAN and put up a 1376 real-time display in tabular format. It can generate some test 1377 packets, like IGMPv2 Leaves or Group Membership Requests. It can 1378 generate and respond to multicast pings (icmp, udp, or snmp based.) 1379 It will eventually acquire more sophisticated multicast facilities. 1381 Example 1383 See http://www.cavebear.com/dwtnda/ for examples. 1385 Facilities used 1387 This is a troubleshooting tool, so it will typically respond to 1388 packets that, strictly speaking, ought to go unanswered. 1390 Availability 1392 DWTNDA runs on MS-DOS and Windows 95/98 and is free. Source is not 1393 provided. See http://www.cavebear.com/dwtnda/ for various documents 1394 and download information. 1396 5.8.2. Mtap 1398 Author 1400 Luis Fernando da Silva Barra, barra@ax.apc.org 1401 Michael Stanton, michael@omega.lncc.br 1403 Description 1405 MTap is a tool for observing IP multicast packet traffic crossing a 1406 subnet, normally an Ethernet. 1408 Each packet sent to an IP multicast group address (class D) is cap- 1409 tured, and information is extracted concerning its origin, its 1410 size, and so forth. This information is summarized, permitting the 1411 determination of the current network load resulting from multicast 1412 traffic. Apart from global summaries, traffic information is 1413 summarized by group and by source, permitting the determination of 1414 the contribution of each group and each individual sender to global 1415 traffic. The data recorded are as follows: number of multicast 1416 packets and total multicast bytes passing through the network, load 1417 level, and date and time of the last packet received. 1419 As well as processing packets sent to a multicast address, MTap 1420 also records separately multicast packets encapsulated in point-to- 1421 point packets. Thus we can also deal with traffic in DVMRP tunnels 1422 between multicast routers, and tunnel traffic data are recorded in 1423 the same way as for a group. 1425 As well as recording the data. MTap also permits that individual 1426 packet data be exhibited in dump format at capture time, both for 1427 multicast packets and for tunneled packets. 1429 In order to evaluate the impact which a group imposes on a subnet- 1430 work, MTap can enter or leave a multicast group, using the IGMP 1431 protocol. Thus traffic can be observed for a group which has no 1432 other members on the subnetwork. 1434 In addition to passively observing and recording multicast traffic, 1435 MTap has a notification mechanism, which sets off an alarm whenever 1436 user-specified load levels are exceeded, either globally, by group 1437 or by tunnel. Notifications are also logged in a dedicated window. 1439 Example 1441 Further information on Mtap will be available from: 1442 http://www.inf.puc-rio.br/~michael/GERENTE/tools 1444 Facilities used 1446 Berkeley Packet Filter (BPF) 1448 Availability 1450 MTap uses a window-based user interface, developed using Tcl/Tk, 1451 and captures packets through the Berkeley Packet Filter (BPF). It 1452 can thus be ported to different platforms. 1454 Mtap, which is still under development, has been ported to Linux 1455 and Solaris; minor problems related to packet capture have still to 1456 be resolved for the Solaris version. When it is released, it will 1457 be available from: 1458 http://www.inf.puc-rio.br/~michael/GERENTE/tools 1460 6. References 1462 [1] Mills, D., "Simple Network Time Protocol (SNTP) Version 4 for 1463 IPv4, IPv6 and OSI", RFC 2030, October 1996. 1465 [2] Fenner, W., "Internet Group Management Protocol, Version 2", RFC 1466 2236, November 1997. 1468 [3] McCloghrie, K., Farinacci, D., and D. Thaler, "Internet Group 1469 Management Protocol MIB", Internet draft (work in progress), draft- 1470 ietf-idmr-igmp-mib-07.txt, July 1998. 1472 [4] M. Handley. "SAP: Session Announcement Protocol (Version 1)." 1473 draft-ietf-mmusic-sap-02.ps, UCL, December, 1996. 1475 [5] McCloghrie, K., Farinacci, D., and D. Thaler, "IP Multicast Rout- 1476 ing MIB", Internet draft (work in progress), draft-ietf-idmr-multi- 1477 cast-routmib-07.txt, July 1998. 1479 [6] McCloghrie, K., Farinacci, D., and D. Thaler, "Protocol Indepen- 1480 dent Multicast MIB", Internet draft (work in progress), draft-ietf- 1481 idmr-pim-mib-05.txt, July 1998. 1483 [7] Thaler, D., "Distance Vector Multicasting Routing Protocol MIB", 1484 Internet draft (work in progress), draft-ietf-idmr-dvmrp-mib-03.txt, 1485 June 1996. 1487 [8] Fenner,W., and S. Casner, "A "traceroute" facility for IP Multi- 1488 cast", Internet draft (work in progress), draft-ietf-idmr-traceroute- 1489 ipm-03.txt, August 1998. 1491 [9] Rekhter, Y. et al., "Address Allocation for Private Internets", 1492 RFC 1918, February, 1996. 1494 7. Security Considerations 1496 SNMP-based monitoring tools require that the manager be provided 1497 access to the relevant MIBs. In order to limit security risks, such 1498 access will typically be provided on a selective basis. For example, 1499 the authentication and access control facilities in SNMP v3 can be 1500 used to limit access to authorized users. 1502 MBONE-mapping tools such as map-mbone should be used with care since 1503 in flooding mode they can result in excessive load on multicast 1504 routers. 1506 Through use of RTP monitoring tools, it may be possible to obtain sen- 1507 sitive information on user viewing habits. In order to protect against 1508 this, encryption technologies such as IPSEC can be used to provide 1509 confidentiality. 1511 8. Acknowledgments 1513 Thanks to Karl Auerbach for the description of the Dr. Watson tool, 1514 and to Michael Stanton for the description of the Mtap tool. 1516 9. Authors' Addresses 1518 Dave Thaler 1519 Microsoft Corporation 1520 One Microsoft Way 1521 Redmond, WA 98052 1523 Phone: 425-703-8835 1524 EMail: dthaler@microsoft.com 1526 Bernard Aboba 1527 Microsoft Corporation 1528 One Microsoft Way 1529 Redmond, WA 98052 1531 Phone: 425-936-6605 1532 EMail: bernarda@microsoft.com 1534 10. Expiration Date 1536 This memo is filed as , and expires 1537 May 1, 1999.