All rights reserved. Printed in the USA. September 1997.
The information in this document is subject to change without notice. The statements, configurations, technical data,
and recommendations in this document are believed to be accurate and reliable, but are presented without express or
implied warranty . Users must tak e full responsibility for their applications of an y products specified in this document.
The information in this document is proprietary to Bay Networks, Inc.
The software described in this document is furnished under a license agreement and may only be used in accordance
with the terms of that license. A summary of the Software License is included in this document.
Trademarks
ACE, AFN, AN, BCN, BLN, BN, BNX, CN, FN, FRE, GAME, LN, PPX, and Bay Networks are registered
trademarks and Advanced Remote Node, ANH, ARN, ASN, Bay•SIS, BayStack, BayStream, BCNX, BLNX,
IP AutoLearn, SN, SPEX, Switch Node, System 5000, Bay Networks Press, and the Bay Networks logo are
trademarks of Bay Networks, Inc.
All other trademarks and registered trademarks are the property of their respective owners.
Restricted Rights Legend
Use, duplication, or disclosure by the United States Government is subject to restrictions as set forth in subparagraph
(c)(1)(ii) of the Rights in Technical Data and Computer Software clause at DFARS 252.227-7013.
Notwithstanding any other license agreement that may pertain to, or accompany the delivery of, this computer
software, the rights of the United States Government regarding its use, reproduction, and disclosure are as set forth in
the Commercial Computer Software-Restricted Rights clause at FAR 52.227-19.
Statement of Conditions
In the interest of improving internal design, operational function, and/or reliability, Bay Networks, Inc. reserves the
right to make changes to the products described in this document without notice.
Bay Networks, Inc. does not assume any liability that may occur due to the use or application of the product(s) or
circuit layout(s) described herein.
SUCH PORTIONS OF THE SOFTWARE ARE PROVIDED “AS IS” AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, WITHOUT LIMITATION, THE IMPLIED WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE.
In addition, the program and information contained herein are licensed only pursuant to a license agreement that
contains restrictions on use and disclosure (that may incorporate by reference certain limitations and notices imposed
by third parties).
Bay Networks, Inc. Software License Agreement
NOTICE:
installing the hardware unit with pre-enabled software (each of which is referred to as “Software” in this Agreement).
ii
Please carefully read this license agreement before copying or using the accompanying software or
117355-A Rev. A
BY COPYING OR USING THE SOFTWARE, YOU A CCEPT ALL OF THE TERMS AND CONDITIONS OF THIS
LICENSE AGREEMENT. THE TERMS EXPRESSED IN THIS AGREEMENT ARE THE ONLY TERMS UNDER
WHICH BAY NETWORKS WILL PERMIT YOU TO USE THE SOFTWARE. If you do not accept these terms and
conditions, return the product, unused and in the original shipping container, within 30 days of purchase to obtain a
credit for the full purchase price
1. License Grant.
nonexclusive, nontransferable license: a) to use the Software either on a single computer or, if applicable, on a single
authorized device identified by host ID, for which it was originally acquired; b) to copy the Software solely for backup
purposes in support of authorized use of the Software; and c) to use and copy the associated user manual solely in
support of authorized use of the Software by Licensee. This license applies to the Software only and does not extend
to Bay Networks Agent software or other Bay Networks software products. Bay Networks Agent software or other
Bay Networks software products are licensed for use under the terms of the applicable Bay Networks, Inc. Software
License Agreement that accompanies such software and upon payment by the end user of the applicable license fees
for such software.
2. Restrictions on use; reservation of rights.
Bay Networks and/or its licensors retain all title and ownership in both the Software and user manuals, including any
revisions made by Bay Networks or its licensors. The copyright notice must be reproduced and included with any
copy of any portion of the Software or user manuals. Licensee may not modify, translate, decompile, disassemble, use
for any competitive analysis, reverse engineer, distribute, or create derivative works from the Software or user
manuals or any copy, in whole or in part. Except as expressly provided in this Agreement, Licensee may not copy or
transfer the Software or user manuals, in whole or in part. The Software and user manuals embody Bay Networks’ and
its licensors’ confidential and proprietary intellectual property. Licensee shall not sublicense, assign, or otherwise
disclose to any third party the Software, or any information about the operation, design, performance, or
implementation of the Software and user manuals that is confidential to Bay Networks and its licensors; however,
Licensee may grant permission to its consultants, subcontractors, and agents to use the Software at Licensee’s f acility,
provided they have agreed to use the Software only in accordance with the terms of this license.
3. Limited warranty.
installed and operated on Bay Networks hardware or other equipment it is originally licensed for, to function
substantially as described in its accompanying user manual during its warranty period, which begins on the date
Software is first shipped to Licensee. If any item of Software fails to so function during its warranty period, as the sole
remedy Bay Networks will at its discretion provide a suitable fix, patch, or workaround for the problem that may be
included in a future Software release. Bay Networks further warrants to Licensee that the media on which the
Software is provided will be free from defects in materials and workmanship under normal use for a period of 90 days
from the date Software is first shipped to Licensee. Bay Networks will replace defective media at no charge if it is
returned to Bay Networks during the warranty period along with proof of the date of shipment. This warranty does not
apply if the media has been damaged as a result of accident, misuse, or abuse. The Licensee assumes all responsibility
for selection of the Software to achieve Licensee’s intended results and for the installation, use, and results obtained
from the Software. Bay Networks does not warrant a) that the functions contained in the software will meet the
Licensee’s requirements, b) that the Software will operate in the hardw are or softw are combinations that the Licensee
may select, c) that the operation of the Software will be uninterrupted or error free, or d) that all defects in the
operation of the Software will be corrected. Bay Networks is not obligated to remedy any Software defect that cannot
be reproduced with the latest Software release. These warranties do not apply to the Software if it has been (i) altered,
except by Bay Networks or in accordance with its instructions; (ii) used in conjunction with another vendor’s product,
resulting in the defect; or (iii) damaged by improper environment, abuse, misuse, accident, or negligence. THE
FOREGOING WARRANTIES AND LIMITATIONS ARE EXCLUSIVE REMEDIES AND ARE IN LIEU OF ALL
OTHER WARRANTIES EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION ANY WARRANTY OF
MERCHANT ABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Licensee is responsible for the security of
its own data and information and for maintaining adequate procedures apart from the Software to reconstruct lost or
altered files, data, or programs.
4. Limitation of liability.
COST OF SUBSTITUTE PROCUREMENT; SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES; OR ANY DAMAGES RESULTING FROM INACCURATE OR LOST DATA OR LOSS OF USE OR
Bay Networks, Inc. (“Bay Networks”) grants the end user of the Software (“Licensee”) a personal,
The Software and user manuals are protected under copyright laws.
Bay Networks warrants each item of Software, as delivered by Bay Networks and properly
IN NO EVENT WILL BAY NETWORKS OR ITS LICENSORS BE LIABLE FOR ANY
117355-A Rev. A
iii
PROFITS ARISING OUT OF OR IN CONNECTION WITH THE PERFORMANCE OF THE SOFTWARE, EVEN
IF BAY NETWORKS HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. IN NO EVENT
SHALL THE LIABILITY OF BAY NETWORKS RELATING TO THE SOFTWARE OR THIS AGREEMENT
EXCEED THE PRICE PAID TO BAY NETWORKS FOR THE SOFTWARE LICENSE.
5. Government Licensees.
by or on behalf of the United States Government. The Software and documentation are commercial products, licensed
on the open market at market prices, and were developed entirely at private expense and without the use of any U.S.
Government funds. The license to the U.S. Government is granted only with restricted rights, and use, duplication, or
disclosure by the U.S. Government is subject to the restrictions set forth in subparagraph (c)(1) of the Commercial
Computer Software––Restricted Rights clause of F AR 52.227-19 and the limitations set out in this license for civilian
agencies, and subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer Software clause of DFARS
252.227-7013, for agencies of the Department of Defense or their successors, whichever is applicable.
6. Use of Software in the European Community.
European Community. If Licensee uses the Software within a country in the European Community, the Software
Directive enacted by the Council of European Communities Directive dated 14 May, 1991, will apply to the
examination of the Software to facilitate interoperability. Licensee agrees to notify Bay Networks of any such
intended examination of the Software and may procure support and assistance from Bay Networks.
7. Term and termination.
Bay Networks’ copyright in the Software and user manuals will cease being effective at the date of expiration of the
Bay Networks copyright; those restrictions relating to use and disclosure of Bay Networks’ confidential information
shall continue in effect. Licensee may terminate this license at any time. The license will automatically terminate if
Licensee fails to comply with any of the terms and conditions of the license. Upon termination for any reason,
Licensee will immediately destroy or return to Bay Networks the Software, user manuals, and all copies. Bay
Networks is not liable to Licensee for damages in any form solely by reason of the termination of this license.
8. Export and Re-export.
or information without first obtaining any required export licenses or other governmental approvals. Without limiting
the foregoing, Licensee, on behalf of itself and its subsidiaries and affiliates, agrees that it will not, without first
obtaining all export licenses and approvals required by the U.S. Government: (i) export, re-export, transfer, or divert
any such Software or technical data, or any direct product thereof, to any country to which such exports or re-exports
are restricted or embargoed under United States export control laws and regulations, or to any national or resident of
such restricted or embargoed countries; or (ii) provide the Software or related technical data or information to any
military end user or for any military end use, including the design, development, or production of any chemical,
nuclear, or biological weapons.
9. General.
jurisdiction, the remainder of the provisions of this Agreement shall remain in full force and effect. This Agreement
will be governed by the laws of the state of California.
Should you have any questions concerning this Agreement, contact Ba y Networks, Inc., 4401 Great America P arkway,
P.O. Box 58185, Santa Clara, California 95054-8185.
LICENSEE ACKNOWLEDGES THAT LICENSEE HAS READ THIS AGREEMENT, UNDERSTANDS IT, AND
AGREES TO BE BOUND BY ITS TERMS AND CONDITIONS. LICENSEE FURTHER AGREES THAT THIS
AGREEMENT IS THE ENTIRE AND EXCLUSIVE AGREEMENT BETWEEN BAY NETWORKS AND
LICENSEE, WHICH SUPERSEDES ALL PRIOR ORAL AND WRITTEN AGREEMENTS AND
COMMUNICATIONS BETWEEN THE PARTIES PERTAINING TO THE SUBJECT MATTER OF THIS
AGREEMENT. NO DIFFERENT OR ADDITIONAL TERMS WILL BE ENFORCEABLE AGAINST BAY
NETWORKS UNLESS BAY NETWORKS GIVES ITS EXPRESS WRITTEN CONSENT, INCLUDING AN
EXPRESS WAIVER OF THE TERMS OF THIS AGREEMENT.
If any provision of this Agreement is held to be invalid or unenforceable by a court of competent
This provision applies to all Software and documentation acquired directly or indirectly
This provision applies to all Software acquired for use within the
This license is effective until terminated; however, all of the restrictions with respect to
Licensee agrees not to export, directly or indirectly, the Software or related technical data
iv
117355-A Rev. A
Contents
About This Guide
Before You Begin .............................................................................................................xvi
If you are responsible for configuring IGMP, DVMRP, MOSPF, QOSPF, RSVP , or
line services, you need to read this guide.
You can now use the Bay Command Console (BCC™) to customize IGMP on a
router. In this guide, you will find instructions for using both the BCC and Site
Manager for IGMP.
If you want toGo to
Learn about IP multicasting and multimedia servicesChapter
Start IP multicasting and multimedia services on the routerChapter 2
Customize IGMPChapter 3
Configure and customize DVMRPChapter 4
Configure and customize MOSPFChapter 5
Configure and customize QOSPFChapter 6
Configure and customize RSVPChapter 7
Reserve line resources on the routerChapter 8
Obtain information about Site Manager parameters (this is the same
information you obtain using Site Manager online Help)
Use multicasting toolsAppendix B
Appendix A
1
117355-A Rev. A
xv
Configuring IP Multicasting and Multimedia Services
.
.
Before You Begin
Before using this guide, you must complete the following procedures. For a new
router:
•Install the router (see the installation manual that came with your router).
•Connect the router to the network and create a pilot configuration file (see
Quick-Starting Routers, Configuring BayStack Remote Access
ASN Routers to a Network)
.
Make sure that you are running the latest version of Bay Networks Site Manager
and router software. For instructions, see
7–11.xx to Version 12.00
.
Conventions
angle brackets (< >)Indicate that you choose the text to enter based on the
description inside the brackets. Do not type the
brackets when entering the command.
Example: if command syntax is
you enter
Upgrading Routers from Version
ping
ping 192.32.10.12
, or
Connecting
<ip_address>
,
bold text
Indicates text that you need to enter, command names,
and buttons in menu paths.
Example: Enter
Example: Use the
Example: ATM DXI > Interfaces >
wfsm &
dinfo
command.
PVCs
identifies the
PVCs button in the window that appears when you
select the Interfaces option from the ATM DXI menu.
brackets ([ ])Indicate optional elements. You can choose none, one,
or all of the options.
.
ellipsis pointsHorizontal (. . .) and verticalellipsis points indicate
()
omitted information.
italic text
Indicates variable values in command syntax
descriptions, new terms, file and directory names, and
book titles.
quotation marks (“ ”)Indicate the title of a chapter or section within a book.
xvi
117355-A Rev. A
About This Guide
Acronyms
screen text
Indicates data that appears on the screen.
Example:
Set Bay Networks Trap Monitor Filters
separator ( > )Separates menu and option names in instructions and
internal pin-to-pin wire connections.
Example: Protocols > AppleTalk identifies the
AppleTalk option in the Protocols menu.
Example: Pin 7 > 19 > 20
vertical line (|)Indicates that you enter only one of the parts of the
command. The vertical line separates choices. Do not
type the vertical line when entering the command.
Example: If the command syntax is
show at routes
show at routes
AUIAttachment Unit Interface
BootPBootstrap Protocol
BRIBasic Rate Interface
CCITTInternational Telegraph and Telephone Consultative Committee
(now ITU-T)
CSMA/CDcarrier sense multiple access with collision detection
DLCMIData Link Control Management Interface
GUIgraphical user interface
HDLChigh-level data link control
IPInternet Protocol
ISDNIntegrated Services Digital Network
ISOInternational Organization for Standardization
ITU-TInternational Telecommunications Union-Telecommunications
(formerly CCITT)
LANlocal area network
MACmedia access control
MAUmedia access unit
MDI-Xmedia-dependent interface with crossover
NBMAnonbroadcast multi-access
nets
|
, you enter either
show at nets
or
, but not both.
117355-A Rev. A
xvii
Configuring IP Multicasting and Multimedia Services
OSIOpen Systems Interconnection
OSPFOpen Shortest Path First (Protocol)
PPPPoint-to-Point Protocol
SMDSswitched multimegabit data service
SNMPSimple Network Management Protocol
STPshielded twisted-pair
TCP/IPTransmission Control Protocol/Internet Protocol
TelnetTelecommunication Network
TFTPTrivial File Transfer Protocol
TPEtwisted-pair Ethernet
UTPunshielded twisted-pair
WANwide area network
Ordering Bay Networks Publications
To purchase additional copies of this document or other Bay Networks®
publications, order by part number from Bay Networks Press™ at the following
numbers:
xviii
•Phone--U.S./Canada: 888-422-9773
•Phone--International: 510-490-4752
•FAX--U.S./Canada and International: 510-498-2609
The Bay Networks Press catalog is available on the World Wide Web at
support.baynetworks.com/Library/GenMisc
available on the World Wide Web at
support.baynetworks.com/Library/tpubs
. Bay Networks publications are
117355-A Rev. A
.
Bay Networks Customer Service
You can purchase a support contract from your Bay Networks distributor or
authorized reseller, or directly from Bay Networks Services. For information
about, or to purchase a Bay Networks service contract, either call your local Bay
Networks field sales office or one of the following numbers:
RegionTelephone numberFax number
About This Guide
United States and
Canada
Europe33-4-92-96-69-6633-4-92-96-69-96
Asia/Pacific61-2-9927-8888 61-2-9927-8899
Latin America561-988-7661561-988-7550
Information about customer service is also available on the World Wide Web at
support.baynetworks.com
How to Get Help
If you purchased a service contract for your Bay Networks product from a
distributor or authorized reseller, contact the technical support staff for that
distributor or reseller for assistance.
If you purchased a Bay Networks service program, call one of the following Bay
Networks Technical Solutions Centers:
800-2LANWAN; then enter Express
Routing Code (ERC) 290, when prompted,
to purchase or renew a service contract
978-916-8880 (direct)
.
978-916-3514
117355-A Rev. A
Technical Solutions Center Telephone numberFax number
Billerica, MA800-2LANWAN978-916-3514
Santa Clara, CA800-2LANWAN408-495-1188
Valbonne, France33-4-92-96-69-6833-4-92-96-69-98
Sydney, Australia61-2-9927-880061-2-9927-8811
Tokyo, Japan81-3-5402-018081-3-5402-0173
xix
Chapter 1
Multicasting and Multimedia Overview
This overview covers the following topics:
TopicPage
Multicast Host Groups
Multicast Addresses1-23
Internet Group Management Protocol1-23
Distance Vector Multicast Routing Protocol1-23
Multicast Extensions to OSPF1-24
Quality of Service Extensions to OSPF1-24
Resource Reservation Protocol1-24
Bay Networks Resource Manager1-24
Multicast Table Manager1-25
1-22
117355-A Rev. A
1-21
Configuring IP Multicasting and Multimedia Services
Multicast Host Groups
IP multicasting is a method for addressing, routing, and delivering a datagram to a
collection of receivers -- called a
Host groups can be permanent or transient.
•A
permanent host group has a well-known, administratively assigned IP
multicast group address. The address, not the membership, is permanent and
defines the group. A permanent host group can consist of zero or more
members.
host group
.
•A transient host group
exists only as long as it has members that need its
services. IP addresses in the multicast range that are not reserved for
permanent groups are available for dynamic assignment to transient host
groups.
Any host system on any IP network can send a message to a multicast group using
the group’s IP multicast address. To receive a message addressed to a multicast
group, however, the host must be a member of the group and must reside on a
network where that group is registered with a local multicast router.
An IP multicasting host group can consist of zero or more members and places no
restrictions on its membership. Host members can reside anywhere; they can join
and leave the group at any time; and the y can be members of more than one group
at the same time. In order to receive a multicast message from a host group, a host
must be a member of the group. However, anyone can send a multicast datagram:
a host does not need to be a member of a group to send a multicast message to its
members.
In general, hosts that are members of the same group reside on different networks.
Howev er , a range of multicast addresses (224.0.0.x) is reserved for groups that are
locally scoped. All message traffic for these hosts remains on the local network.
Hosts that belong to a group in this address range and that reside in different
networks will not receive each other’s message traffic.
1-22
Multicast data packets are affected by traffic filters. Therefore, you must
Note:
ensure that traffic filters configured on a multicast router do not prevent a host
that is a member of a group from receiving packets intended for that group.
117355-A Rev. A
Multicast Addresses
Each host group is assigned a unique multicast address. To reach all members of
the group, a sender uses the multicast address as the destination address of the
datagram.
An IP Version 4 multicast address is a Class D address (the high-order bits are set
to 1110) from 224.0.0.0 to 239.255.255.255.
The block of addresses from 224.0.0.1 to 224.0.0.255 is reserved for routing
protocols and other low-level protocols. Multicast routers will not forward
datagrams with addresses in this range.
Internet Group Management Protocol
The Internet Group Management Protocol (IGMP) has the following
characteristics:
•Allows a host to register group memberships with the local queries router to
receive any datagrams sent to this router and targeted to a group with a
specific IP multicast address.
Multicasting and Multimedia Overview
•Allows a router to learn the existence of group members on its directly
attached networks. The router periodically sends a general group query
message to each of its local networks. Any host that is a member of a
multicasting group identifies itself by sending a response.
IGMP is described in Cha
pter 3.
Distance Vector Multicast Routing Protocol
DVMRP is a distance vector type of multicast routing protocol. It advertises
117355-A Rev. A
shortest-path routes to multicasting
containing hosts that have the capability to issue multicast datagrams. (In this
respect, DVMRP is the opposite of RIP, which advertises routes to destination
networks.)
DVMRP is described in Cha
pter 4.
source networks
-- that is, any network
1-23
Configuring IP Multicasting and Multimedia Services
Multicast Extensions to OSPF
Multicasting Extensions to OSPF (MOSPF) enhances the OSPF protocol by
providing capabilities that allow a router to forward multicast IP traffic within an
OSPF Version 2 autonomous system.
For instructions on configuring MOSPF, see Cha
Quality of Service Extensions to OSPF
QOSPF is an extension of OSPF and MOSPF that works in conjunction with the
Resource Reservation Protocol to provide quality of service (QoS) for multicast
data flows.
QOSPF is described in Cha
pter 6.
Resource Reservation Protocol
The Resource Reservation Protocol (RSVP) allo ws host systems in an IP network
to reserve resources on RSVP-capable routers for unicast or multicast dataflows.
(A dataflow is a transmission of packets from a source to one or more destinations
requiring a certain QoS.)
RSVP is described in Cha
pter 7.
Bay Networks Resource Manager
pter 5.
1-24
The Bay Networks Resource Manager lets you define a certain percentage of a
line’s bandwidth as reservable. Applications that require a guaranteed quality of
service can negotiate for the reservable bandwidth. When the router honors a
reservation request, the Resource Manager allocates bandwidth from the
reservable bandwidth, reducing the bandwidth available for other requests.
For information about the Bay Networks Resource Manager, see Cha
pter 8.
117355-A Rev. A
Multicast Table Manager
The Multicast Table Manager (MTM) makes it possible for different multicast
protocols to work together on the same router. MTM does the following:
•Manages DVMRP and MOSPF
•Provides multicast routing support for RSVP
•Supports MOSPF special features
•Supports multicast tools for tracing routes
•Maintains a multicast forwarding cache
•Forwards multicast traffic
Multicasting and Multimedia Overview
117355-A Rev. A1-25
Chapter 2
Starting Multicasting and Multimedia Services
This chapter explains how to perform a basic configuration -- that is, a
configuration using all available defaults -- for the IP multicast services described
in this manual.
Configuring IP Multicasting and Multimedia Services
Starting IGMP
When you configure any multicasting protocol described in this manual, Site
Manager automatically configures IGMP on the slot and circuit.
IGMP is required for all types of multicasting. If you want the router to receive
and forward multicast packets (that is, packets with destination addresses from
224.0.0.255 to 239.255.255.255), IGMP must be running on the slot and circuit --
even if the circuit is a point-to-point circuit that will not be involved in IGMP
group queries and join messages.
2-28117355-A Rev. A
Starting DVMRP
To start DVMRP on the router:
1.Configure a circuit on a slot and connector.
2.Configure an IP interface on the circuit.
3.Add DVMRP to the IP interface.
For information and instructions on using Site Manager to configure a circuit on a
slot and connector, see Configuring WAN Line Services or Configuring Ethernet, FDDI, and Token Ring Services. When you have successfully configured the
circuit, the Select Protocols window opens. Proceed as follows:
You do thisSystem responds
Starting Multicasting and Multimedia Services
Site Manager Procedure
1. In the Select Protocols window, choose
the following protocols:
•IP
•DVMRP
Then click on OK.
2. Set the following parameters:
•IP Address
•Subnet Mask
•Transmit Bcast Addr
•UnNumbered Assoc Address
Click on Help or see the parameter
descriptions beginning on page A-20.
3. Click on OK.Site Manager returns you to the
The IP Configuration window opens.
Configuration Manager window.
When you configure DVMRP on an IP interface, DVMRP is also configured
globally on the router.
DVMRP is now running on the router with default values for all global and
interface parameters. You customize DVMRP by modifying DVMRP parameters.
For information and instructions, see Chapter 4.
117355-A Rev. A2-29
Configuring IP Multicasting and Multimedia Services
Starting MOSPF
MOSPF is a multicasting extension of OSPF. To enable MOSPF, you must add
OSPF to an IP interface and enable MOSPF multicast extensions to support one of
the following types of multicasting:
•Intra-area multicasting
•Intra-area and inter-area multicasting
•Intra-area and inter-AS multicasting
•All multicasting
For information about MOSPF multicasting types, see Chapter 5.
Site Manager Procedure
You do thisSystem responds
1. Configure OSPF on the router as
described in
2. In the Configuration Manager window,
choose Protocols.
3. Choose IP.The IP menu opens.
4. Choose OSPF.The OSPF menu opens.
5. Choose Global.The Edit OSPF Global Parameters
6. Click on the Multicast Extensions
parameter. Click on Help or see the
parameter description on page A-29.
7. Choose the type of MOSPF you want to
configure, and then click on OK.
Configuring IP Services
.
The Protocols menu opens.
window opens.
2-30117355-A Rev. A
Starting RSVP
To start RSVP on the router:
1.Configure a circuit on a slot and connector.
2.Configure an IP interface on the circuit.
3.Add RSVP to the IP interface.
For information and instructions on using Site Manager to configure a circuit on a
slot and connector, see see Configuring WAN Line Services or Configuring Ethernet, FDDI, and Token Ring Services. When you have successfully
configured the circuit, the Select Protocols window opens. Proceed as follows:
You do thisSystem responds
Starting Multicasting and Multimedia Services
Site Manager Procedure
1. In the Select Protocols window, choose
the following protocols:
•IP
•RSVP
Then click on OK.
2. Set the following parameters:
•IP Address
•Subnet Mask
•Transmit Bcast Addr
•UnNumbered Assoc Address
Click on Help or see the parameter
descriptions beginning on page A-20.
3. Click on OK.The Initial RSVP Global Parameters
4. Click on Save.Site Manager queries you to create line
5. Click on OK.The Edit Line Resources window opens.
6. Edit the following parameters:
•Estimated Bandwidth
•Reservable Bandwidth
Click on Help or see the parameter
descriptions beginning on page A-22.
7. Click on OK.Site Manager returns you to the
The IP Configuration window opens.
widow appears.
resources.
Site Manager returns you to the
Configuration Manager window.
Configuration Manager window.
117355-A Rev. A2-31
Configuring IP Multicasting and Multimedia Services
RSVP is now running on the router with default values for all parameters. You
customize RSVP by modifying RSVP parameters. For information and
instructions, see Chapter 7.
2-32117355-A Rev. A
Chapter 3
Customizing IGMP
This chapter covers the following topics describing the Internet Group
Management Protocol (IGMP):
TopicPage
IGMP Concepts and Terminology3-2
Customizing Global IGMP3-4
Customizing IGMP on an Interface3-12
Configuring a Static Host Entry3-20
117355-A Rev. A3-1
Configuring IP Multicasting and Multimedia Services
IGMP Concepts and Terminology
The Internet Group Management Protocol (IGMP) allows hosts to communicate
their desired group memberships to their local queries router to receive any
datagrams sent to this router and targeted to a group with a specific IP multicast
address. Bay Networks routers support IGMP Version 2.
A router communicates with the hosts on a local network by sending IGMP
queries. Hosts respond by issuing IGMP reports.
A router running IGMP periodically sends host membership queries to its
attached local networks. Routers that conform to RFC 1112 generate Version 1
queries. Bay Networks routers configured with IGMP generate Version 2 queries.
If multiple IGMP routers exist on the network, Bay Networks routers designate
one router to send host member questions, using the following rules:
•Choose a router that generates Version 1 queries over a router that generates
Version 2 queries.
•Choose the router with the lowest IP address.
3-2117355-A Rev. A
IGMP Host Reports
A host that receives a membership query from a local router can respond with a
host membership report, one report for each joined multicast group. A host that
receives a query delays its reply by a random interval and listens for a reply from
any other host in the same host group. Consider a network that includes two host
members -- Host A and Host B -- of the same multicast group. The router sends
out a host membership query on the local network. Host A and Host B both
receive the query and listen on the network for a host membership report. Host B’s
delay time expires first, so it responds to the query with a membership report.
Hearing the response, Host A does not send a report of its own for the same group.
Each query from a router to a host includes a code field. IGMP inserts a
value -- n -- into this field specifying the maximum time in tenths of a second
within which the host must issue a reply. The host uses this value to calculate a
random value between 0 and n tenths of a second for the period that it waits before
sending a response.
If at least one host on the local network specifies that it is a member of a given
group, the router will forward to that network all datagrams bearing the group’s
multicast address.
Customizing IGMP
Upon initialization, the host may immediately issue a report for each of its
supported multicast groups. The router accepts and processes these asynchronous
reports the same way it accepts requested reports.
Once in a steady state, hosts and routers communicate in a way that minimizes the
exchange of queries and reports.
Host Leave Messages
When a Version 2 host leaves a group, it issues a host leave message. The
multicast router on the network issues a group-specific query to determine
whether there are other group members on the network. If no host responds to the
query , the router assumes that no members belonging to that group exist on that
interface.
117355-A Rev. A3-3
Configuring IP Multicasting and Multimedia Services
Customizing Global IGMP
When you configure a multicasting protocol on the router, IGMP is automatically
enabled with default values for all global parameters. Y ou customize global IGMP
by modifying these parameters as described under the following topics:
TopicPage
Enabling and Disabling IGMP3-5
Estimating the Number of Groups3-6
Specifying a Version Threshold Time3-8
Configuring Logging3-9
Enabling Join Acknowledgments3-10
Specifying a Forwarding Cache Limit3-11
3-4117355-A Rev. A
Enabling and Disabling IGMP
When you configure IGMP on the router, IGMP is automatically enabled.
You can use the BCC or Site Manager to disable and reenable IGMP on the router.
Using the BCC
Navigate to the global IGMP prompt and enter
state
state
state is
enabled
disabled
Using Site Manager
You do thisSystem responds
Customizing IGMP
Site Manager Procedure
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose IGMP.The IGMP menu opens.
5. Choose Global.The IGMP Global Configuration window
6. Set the Enable parameter. Click on Help
or see the parameter description on page
A-15.
7. Click on Save.You return to the Configuration Manager
117355-A Rev. A3-5
The Protocols menu opens.
opens.
window.
Configuring IP Multicasting and Multimedia Services
Estimating the Number of Groups
By default, IGMP estimates that 20 groups will be simultaneously active on this
router.
This estimate allows the router to utilize memory efficiently; exceeding this size
during router operation will not cause an error but may cause the router to
consume more memory than required.
Note: You do not need to include in the count any group from 224.0.0.0 to
224.0.0.255.
You can use the BCC or Site Manager to supply an estimate from 5 to 65,535
groups.
Using the BCC
Navigate to the global IGMP prompt and enter
estimated-groups
groups
groups is an integer from 5 to 65,535.
3-6117355-A Rev. A
Using Site Manager
You do thisSystem responds
Customizing IGMP
Site Manager Procedure
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose IGMP.The IGMP menu opens.
5. Choose Global.The IGMP Global Configuration window
6. Set the Estimated Groups parameter.
Click on Help or see the parameter
description on page A-16.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
117355-A Rev. A3-7
Configuring IP Multicasting and Multimedia Services
Specifying a Version Threshold Time
By default, 540 seconds can elapse after IGMP detects a Version 1 query before
IGMP tries to become the designated querier.
The value you specify should be greater than the Version 1 query rate of all IGMP
speakers on all networks directly connected to the router.
You can use the BCC or Site Manager to specify a version threshold time from
1 second to 65,535 seconds.
Using the BCC
Navigate to the global IGMP prompt and enter
version-threshold
threshold is the number of seconds from 1 to 65,535.
For example, the following command sets the version threshold time to 500
seconds:
igmp# version-threshold 500
igmp#
Using Site Manager
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose IGMP.The IGMP menu opens.
5. Choose Global.The IGMP Global Configuration window
6. Set the Version Threshold Time
parameter. Click on Help or see the
parameter description on page A-16.
7. Click on Save.You return to the Configuration Manager
threshold
Site Manager Procedure
The Protocols menu opens.
opens.
window.
3-8117355-A Rev. A
Configuring Logging
You can use the BCC or Site Manager to specify the messages you want IGMP to
log.
Using the BCC
Navigate to the global IGMP prompt and enter
Customizing IGMP
debug-log-flag
flag is an integer indicating the messages you want to log.
Using Site Manager
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose IGMP.The IGMP menu opens.
5. Choose Global.The IGMP Global Configuration window
6. Set the Debug parameter. Click on Help
or see the parameter description on page
A-16.
7. Click on Save.You return to the Configuration Manager
flag
Site Manager Procedure
The Protocols menu opens.
opens.
window.
117355-A Rev. A3-9
Configuring IP Multicasting and Multimedia Services
Enabling Join Acknowledgments
By default, IGMP does not respond with an acknowledgment to join requests
from host groups.
Using the following Site Manager procedure, you can configure IGMP globally to
respond to a join request by sending an IGMP query to the group.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose IGMP.The IGMP menu opens.
5. Choose Global.The IGMP Global Configuration window
6. Set the Join Ack Enable parameter. Click
on Help or see the parameter description
on page A-17.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
Note: This is a proprietary Bay Networks function. It is not part of the
standard IGMP protocol.
3-10117355-A Rev. A
Specifying a Forwarding Cache Limit
By default, IGMP allows a maximum of 512 entries in the MTM forwarding
cache. This affects all multicasting protocols.
The MTM cache must be at least as large as individual routing protocol caches
(for example, the DVMRP cache).
You can use the following Site Manager procedure to set the forwarding cache to a
different value.
Site Manager Procedure
You do thisSystem responds
Customizing IGMP
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose IGMP.The IGMP menu opens.
5. Choose Global.The IGMP Global Configuration window
6. Set the Forward Cache Limit parameter.
Click on Help or see the parameter
description on page A-17.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
117355-A Rev. A3-11
Configuring IP Multicasting and Multimedia Services
Customizing IGMP on an Interface
When you add a multicast protocol to an IP interface, IGMP is enabled with
default values for all interface parameters. You customize IGMP on the interface
by modifying these parameters as described under the following topics:
TopicPage
Enabling and Disabling IGMP on an Interface3-13
Specifying a Query Rate3-14
Specifying a Membership Timeout Interval3-16
Specifying a Designated Router Timeout Interval3-17
Specifying a Maximum Host Response Time3-18
Specifying the Lifetime of a Cache Entry for Mtrace3-19
3-12117355-A Rev. A
Enabling and Disabling IGMP on an Interface
When you add a multicasting protocol to an IP interface, IGMP is automatically
enabled on the interface.
Note: IGMP is required for multicasting to function on the interface.
You can use the BCC or Site Manager to disable and reenable IGMP on the
interface
Using the BCC
Navigate to the IGMP prompt for the interface and enter
state
state
state is
enabled
disabled
Customizing IGMP
Using Site Manager
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Enable parameter. Click on Help
or see the parameter description on page
A-18.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
117355-A Rev. A3-13
The Protocols menu opens.
window opens.
window.
Configuring IP Multicasting and Multimedia Services
Specifying a Query Rate
By default, IGMP sends a group membership query on the interface every 120
seconds.
Specifying zero disables queries only. The router still forwards multicast
datagrams on this circuit.
Note: If another IGMP r outer on this network has tak en on the query role, this
router will not send out queries unless it has not heard of any queries within
the number of seconds specified by the Designated Router Timeout parameter.
You can use the BCC or Site Manager to disable queries or specify a query rate
from 0 to 4096 seconds.
Using the BCC
Navigate the IGMP prompt for the interface and enter
query-rate
rate
rate is the number of seconds from 0 (disabling queries) to 4096.
For example, the following command specifies a query rate of 300 seconds:
igmp/2.2.2.2/3# query-rate 300
igmp/2.2.2.2/3#
3-14117355-A Rev. A
Using Site Manager
You do thisSystem responds
Customizing IGMP
Site Manager Procedure
1. In the Configuration Manager window,
choose Protocols.
6. Set the Designated Router Timeout
parameter. Click on Help or see the
parameter description on page A-19.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
seconds
Site Manager Procedure
The Protocols menu opens.
window opens.
window.
117355-A Rev. A3-17
Configuring IP Multicasting and Multimedia Services
Specifying a Maximum Host Response Time
By default, a host must wait 100 tenths of a second before responding to a query.
IGMP places this value in the code field of an IGMP query.
You can use the BCC or Site Manager to specify a value from one tenth of a
second to 100 tenths of a second.
Using the BCC
Navigate to the IGMP prompt for the interface and enter
max-host-response
time is an integer from 1 to 100 specifying the response time in tenths of a second.
For example, the following command sets the host response to 25 tenths of a
6. Set the Max Host Response Time
parameter. Click on Help or see the
parameter description on page A-20.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
time
Site Manager Procedure
The Protocols menu opens.
window opens.
window.
3-18117355-A Rev. A
Specifying the Lifetime of a Cache Entry for Mtrace
IGMP creates entries in the forwarding cache specifically for the Mtrace utility.
By default, IGMP keeps these entries in the forwarding cache for a maximum of
30 seconds.
You can use the BCC or Site Manager to specify a different lifetime value from 30
to 8192 seconds.
Using the BCC
Navigate to the IGMP prompt for the interface and enter
Customizing IGMP
mtrace-lifetime
seconds is an integer from 30 to 8192 seconds.
For example, the following command sets the Mtrace cache entry lifetime to 60
6. Set the Mtrace Entry Lifetime parameter.
Click on Help or see the parameter
description on page A-20.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
seconds
Site Manager Procedure
The Protocols menu opens.
window opens.
window.
117355-A Rev. A3-19
Configuring IP Multicasting and Multimedia Services
Configuring a Static Host Entry
A network may include a member of a multicast group that is unable to register its
group membership with the local IGMP router, for example, a host that is a
member of a multicast group but that is not running IGMP.
In this situation, you can register the group member’s network statically on the
router.
A registration entry includes
•A group address
•An address prefix length
•A circuit name
You can use Site Manager to supply this information.
Using Site Manager
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose IGMP.The IGMP menu opens.
5. Choose Static Groups.The IP IGMP Static Groups window
6. Set the following parameters:
•Group Address
•Prefix Length
•Circuit Name
Click on Help or see the parameter
descriptions beginning on page A-17.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
3-20117355-A Rev. A
Chapter 4
Customizing DVMRP
This chapter describes the Distance Vector Multicast Routing Protocol (DVMRP).
T opicPage
DVMRP Concepts and Terminology4-2
Customizing DVMRP Globally4-8
Customizing DVMRP on a Circuit4-22
Configuring a Tunnel4-33
117355-A Rev. A4-1
Configuring IP Multicasting and Multimedia Services
DVMRP Concepts and Terminology
DVMRP is a multicasting protocol that provides a mechanism for routers to
propagate multicast datagrams in a manner that minimizes the number of excess
copies sent to any particular network.
This section covers the following topics:
TopicPage
Neighbor Connections4-2
Source Route Advertisements4-4
How DVMRP Chooses a Route4-5
Routing Table4-6
Shortest-Path Trees4-7
Neighbor Connections
In a DVMRP environment, neighbors are multicasting routers that are connected
directly or through a tunnel.
•Directly connected neighbors are routers that have an interface to the same
network.
•Tunnel-connected neighbors are multicast routers that communicate through a
unicast network, exchanging DVRMP messages that are encapsulated in IP
datagrams.
In Figure 4-
1, for example, multicasting Router A has two neighbors, Router B
and Router C. Router A and Router B are connected directly -- they both have
interfaces to Net 6. Router A and Router C communicate through a tunnel that
includes a unicast router.
4-2117355-A Rev. A
Net 1
Customizing DVMRP
a3
Net 2
b3
Net 4
Net 5
b2
b1
Net 8
a2
Net 3
c1
c3
c2
C
Key
Multicast
router
Unicast
router
Multicast
host
Multicast
circuit
a1
Net 6
B
D
e1
E
e2
Net 9
A
d1
d2
d3
Tunnel
IP00031A
Figure 4-1.Multicast Routers
117355-A Rev. A4-3
Configuring IP Multicasting and Multimedia Services
At startup, a DVMRP multicasting router
1. Initializes its routing table with information on all of its local networks
2. Learns the existence of its neighbors by sending a probe for all routes on each
of its multicast interfaces (both physical circuits and tunnels)
3. Receives reports from its neighbors containing the routing information
(including route costs)
In Figure 4-
four multicasting interfaces. Router D receives reports from its multicasting
neighbors, Routers B, C, and E.
1, for example, Router D becomes active and issues routing probes on
Source Route Advertisements
A source network is an y network containing hosts that ha v e the capability to issue
multicast datagrams. DVMRP advertises shortest-path routes to multicasting
source networks. In this respect, DVMRP is the opposite of RIP, which advertises
routes to destination networks.
Periodically, each multicasting router issues full or partial routing information on
each DVMRP circuit, using DVMRP report messages. This routing information
represents the sending router’s cost to reach the specified source network. (The
cost is the sum of the hop metrics along the shortest path to the given source
network.)
Upon receiving a DVMRP report from another router, DVMRP reexamines its
routing table to determine if the shortest path information needs updating.
Specifically, DVMRP looks in the routing table for an entry describing a route to
the same source network. If one exists, DVMRP compares the cost of the two
routes and stores the route with the lower cost in its routing table.
A router will not send route reports on an interface until it knows (by means of
received probes or reports) that it has a neighboring multicast router on that
interface. It will continue to send probes periodically on an interface.
4-4117355-A Rev. A
How DVMRP Chooses a Route
Each DVMRP interface is configured with a metric that indicates the cost of the
hop. A router that receives multiple route reports for the same multicasting source
network
•Compares the cost specified in each (based on the metric field)
•Stores information from the report with the lowest cost in its routing table
A route metric is the sum of all the interface (hop) metrics from a given route
source to a given router.
igure 4-1 on page 4-3, for example, Router D receives two reports for the
In F
network connected to multicasting Router A, one from Router B and one from
Router C. Using the metrics contained in the route reports, Router D determines
that the cost of the tunneled route is greater than the cost of the route that uses
direct physical connections. Router D discards the route received from Router C
and stores the route received from Router B.
Router D then declares Router B to be the next-hop neighbor and Interface d1 to
be the next-hop interface. After a ne xt-hop neighbor has been declared for a route,
the route updates received from that neighbor for that route take precedence until
either the route times out or until another router advertises a better metric for that
route.
Customizing DVMRP
117355-A Rev. A4-5
Configuring IP Multicasting and Multimedia Services
Routing Table
Table 4-1 shows the principal items in a routing table entry.
Table 4-1.Parts of a Routing Table Entry
ItemDescription
Source subnet address
and mask
From-gatewayPrevious-hop router leading back to the source subnet
TTLNumber of seconds before this entry is removed from the
Address and mask of a subnetwork containing a host
sourcing multicast datagrams
routing table
Note that the source subnet and the previous-hop router in the DVMRP routing
table are the opposite of the destination subnet and next-hop router in a RIP
routing table.
Using this information, the router can
1. Receive a multicast datagram and determine if the datagram has arri ved on the
interface that is on the shortest path to the source network.
2. Drop the datagram if it has not arrived on the shortest-path interface.
3. Flood the multicast datagram to all active downstream DVMRP neighbors.
4-6117355-A Rev. A
Shortest-Path Trees
Route information used by DVMRP is independent of any other routing
information used by the router -- for example, routes provided by RIP. The
purpose of this routing information is to create a shortest-path tree entry in the
routing table for the propagation of multicast datagrams.
The shortest-path tree entry indicates the interface that provides the shortest path
to the network that is the source of the multicast datagram.
igure 4-1 on page 4-3, for example, the routing table on Router D includes an
In F
entry describing the shortest-path route to the network connected to Router A. The
entry indicates that Interface d1 provides the shortest path to that source network.
A shortest-path tree also indicates those interfaces that are on the shortest path to
that source network from a neighboring router.
Router E considers the network connecting it to Router D to be on the shortest
path to the source network connected to router A. Router D has an interface (d3)
that is part of the shortest path from Router E from the network connected to
Router A.
Customizing DVMRP
If neighboring routers have the same metric to a given source network, the router
with the lower IP address is responsible for propagating multicast traffic
originating from that source network onto the network or tunnel that is common to
these neighboring routers.
A network is considered a leaf network if it has no dependent downstream
neighbors for a source. In F
igure 4-1, the network connected to Router E (Net 5)
is a leaf network.
117355-A Rev. A4-7
Configuring IP Multicasting and Multimedia Services
Customizing DVMRP Globally
When you start DVMRP on the router, DVMRP runs with default values for all
global protocols. You customize DVMRP by modifying parameters as described
under the following topics:
TopicPage
Disabling and Reenabling DVMRP4-9
Setting the Update Interval4-10
Configuring Tree Pruning4-11
Configuring DVMRP Timers4-12
Specifying a Probe Interval4-16
Specifying a Route Switch Interval4-17
Estimating the Number of Routes4-18
Logging Debugging Messages4-19
Specifying the Maximum Number of Routes4-20
Enabling and Disabling Routing Policies4-21
4-8117355-A Rev. A
Disabling and Reenabling DVMRP
You can use Site Manager to disable and reenable DVMRP on the router.
You do thisSystem responds
Customizing DVMRP
Site Manager Procedure
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Enable parameter. Click on Help
or see the parameter description on page
A-2.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
117355-A Rev. A4-9
Configuring IP Multicasting and Multimedia Services
Setting the Update Interval
Periodically, each multicasting router issues full or partial routing information on
each DVMRP circuit, using DVMRP report messages. This routing information
represents the sending router’s cost to reach the specified netw ork. (The cost is the
sum of the hop metrics along the shortest path to the given source network.)
You can use Site Manager to
•Specify how often routing messages containing complete routing tables are
sent.
•Specify the minimum amount of time between triggered updates. Triggered
updates are sent when routing information changes. Issuing a full update
restarts the triggered update timer. Therefore, the triggered update interval
you specify must be shorter than the full update interval you set.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the following parameters:
•Full Update Interval
•Triggered Update Interval
Click on Help or see the parameter
descriptions beginning on page A-2.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
4-10117355-A Rev. A
Configuring Tree Pruning
If no members are detected on a branch of the shortest path tree for a given group,
DVMRP prunes the branch.
The following conditions cause DVMRP to prune the shortest-path tree for a
given group:
•The router determines that the attached network on which the host is located
(or any other locally attached network) has no active member of the group.
•The router determines that all neighbors on all attached networks other than
the next-hop network to the source have pruned off the source and group.
•The router determines that it is not located on the shortest network path to an y
remote network that includes a member of the group.
•The router sends a DVMRP prune message to its DVMRP neighbor. The
neighbor removes the router from its forwarding table.
If the host later rejoins the group, the router sends the neighbor a DVMRP
graft message. The neighbor restores the router to its forwarding table.
Tree pruning is enabled on the router by default. You can use Site Manager to
disable and reenable tree pruning on the router.
Customizing DVMRP
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Pruning Enable parameter. Click
on Help or see the parameter description
on page A-6.
7. Click on Save.You return to the Configuration Manager
117355-A Rev. A4-11
The Protocols menu opens.
window opens.
window.
Configuring IP Multicasting and Multimedia Services
Configuring DVMRP Timers
When a router adds or updates a route, it uses configurable timers to control the
useful life of the route.
Note: DVMRP timers must be the same throughout the network.
Setting the Route Expiration Timer
The route expiration timer determines how long DVMRP waits for an update
message indicating that a route is reachable. Upon expiration of this timer, this
route is advertised as unreachable until it is refreshed or until it is garbaged.
By default, DVMRP sets the route expiration time at 200 seconds.You can use
Site Manager to set the route expiration time from 20 to 4000 seconds.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Route Expiration Timeout
parameter. Click on Help or see the
parameter description on page A-3.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
4-12117355-A Rev. A
Customizing DVMRP
Setting the Garbage Timer
The garbage timer determines how long DVMRP advertises a route as
unreachable before it removes the route from the routing table. The difference
between this value and the route expiration timeout value represents the time
period that the route will be advertised as unreachable without subsequent
refreshment.
By default, DVMRP sets the garbage timer to 340 seconds. You can use Site
Manager to set the value from 40 to 8000 seconds.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Garbage Timeout parameter.
Click on Help or see the parameter
description on page A-4.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
Enter a value that is greater than the value you specified for the route expiration
timer to allow enough time for the route to be advertised as unreachable.
117355-A Rev. A4-13
Configuring IP Multicasting and Multimedia Services
Setting the Neighbor Report Timer
The neighbor report timer specifies how long the router waits to receive a report
from a neighbor before considering the connection inactive.
By default, DVMRP waits 140 seconds. You can use Site Manager to specify a
value from 40 to 8000 seconds.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Neighbor Timeout parameter.
Click on Help or see the parameter
description on page A-3.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
4-14117355-A Rev. A
Customizing DVMRP
Setting the Leaf Timer
The leaf timer determines whether or not a network or tunnel local to a given
interface is considered to be part of the shortest path to a given source network by
any DVMRP neighbor.
If during this time the local interface has not received a route report for a given
source network, this network or tunnel and its local interface are considered not to
lie in the shortest path for any neighbor. In other words, the local network is not
part of the shortest path to that specific source network.
By default, DVMRP sets the leaf timer at 200 seconds. You can use Site Manager
to specify a value from 25 to 4000 seconds.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Leaf Timeout parameter. Click on Help or see the parameter description on
page A-3.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
117355-A Rev. A4-15
Configuring IP Multicasting and Multimedia Services
Specifying a Probe Interval
The probe interval determines how often DVMRP sends a probe on interfaces
from which no neighbors have been heard.
By default, DVMRP sends a probe ev ery 10 seconds. Y ou can use Site Manager to
specify a value from 5 to 30 seconds.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Neighbor Probe Interval
parameter. Click on Help or see the
parameter description on page A-5.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
If your neighbor is running DVMRP mrouted, ensure that your probe interval
value matches the value used by the neighbor.
4-16117355-A Rev. A
Specifying a Route Switch Interval
The route switch interval specifies how long the router should wait, without
receiving a subsequent route update from the original neighbor, before switching
to a different neighbor advertising equal cost for this route.
By default, DVMRP waits 140 seconds. You can use Site Manager to specify a
value from 20 to 2000 seconds.
Site Manager Procedure
You do thisSystem responds
Customizing DVMRP
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Route Switch Timeout parameter .
Click on Help or see the parameter
description on page A-5.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
If your neighbor is running DVMRP mrouted, the recommended value is 140
seconds.
117355-A Rev. A4-17
Configuring IP Multicasting and Multimedia Services
Estimating the Number of Routes
By default, DVMRP preallocates a routing table for 25 entries. You can use Site
Manager to specify the number of entries (10 or more).
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Estimated Routes parameter.
Click on Help or see the parameter
description on page A-4.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
Enter a value that the router can use for preallocating routing tables. For an
MBone implementation, a value of 3000 or higher is recommended.
Note that routes are kept on a per-source-network basis, independent of multicast
groups. This number must include a route for every network that is local to a
circuit configured for multicasting. This allows the router to utilize memory
efficiently. Exceeding this size during router operation will not cause an error but
may cause the router to consume more memory than required.
4-18117355-A Rev. A
Logging Debugging Messages
By default, DVMRP does not log debugging messages. You can use Site Manager
to enable the logging of debugging messages and to specify the level of debug
messages.
You do thisSystem responds
Customizing DVMRP
Site Manager Procedure
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Debug Level parameter. Click on
Help or see the parameter description on
page A-5.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
117355-A Rev. A4-19
Configuring IP Multicasting and Multimedia Services
Specifying the Maximum Number of Routes
By default, DVMRP stores all learned routes in the routing table. Y ou can use Site
Manager to specify the number of routes that DVMRP can learn per slot. This
parameter limits the number of routes that can be stored in the routing table.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Max Routes parameter. Click on
Help or see the parameter description on
page A-6.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
If you specify a maximum number of routes, you must include a route for every
local network that has a circuit configured for multicasting.
4-20117355-A Rev. A
Enabling and Disabling Routing Policies
By default, routing policies are globally disabled.
This parameter allows you to configure a policy for the specified route. Bay
Networks currently supports only the policies that do not advertise the specified
route or route range. Bay Networks supports policies that advertise a default route
for the specified route or route range.
You can use the following Site Manager procedure to enable and disable routing
policies as required.
Site Manager Procedure
You do thisSystem responds
Customizing DVMRP
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose Multicast.The Multicast menu opens.
4. Choose DVMRP.The DVMRP menu opens.
5. Choose Global.The DVMRP Global Configuration
6. Set the Policy Enable parameter. Click on
Help or see the parameter description on
page A-6.
7. Click on Save.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
117355-A Rev. A4-21
Configuring IP Multicasting and Multimedia Services
Customizing DVMRP on a Circuit
You customize DVMRP on a circuit by modifying DVMRP parameters as
described under the following topics:
TopicPage
Disabling and Reenabling DVMRP on a Circuit4-22
Disabling Multicast Support on a Unicast Tunnel4-23
Calculating a Route Metric and Comparing Route Costs4-24
Specifying a Threshold4-25
Configuring a Forwarding Table4-27
Disabling Advertisement of Local Networks4-29
Advertising a Default Route4-30
Listening for a Default Route4-31
Accepting a Report from a Nonstandard DVMRP Neighbor4-32
Disabling and Reenabling DVMRP on a Circuit
By default, DVMRP is enabled on a circuit. You can use Site Manager to disable
and reenable it.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Metric parameter . Click on Help or
see the parameter description on page
A-8.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
4-24117355-A Rev. A
Specifying a Threshold
Threshold values control the scope of datagram delivery. The threshold is the
minimum IP TTL required for a multicast datagram to be forwarded out a given
interface.
For mrouted compatibility, multicast datagrams originated by the router have a
TTL of 1. These datagrams are not compared against the TTL. Unicast datagrams
originated by the router (for example, for route reports issued via a tunnel) have a
TTL of 255. A datagram that is to be forw arded through a tunnel is first compared
against the threshold and, if accepted, is then encapsulated in an IP datagram with
a TTL of 64.
able 4-2 lists
T
•Originating TTL values recommended for certain types of multicast
applications
•Threshold values recommended for routers to permit the forwarding of
packets from these applications
These values are recommended for topologies that will connect to the MBone.
6. Set the Threshold parameter. Click on Help or see the parameter description on
page A-8.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
4-26117355-A Rev. A
Configuring a Forwarding Table
To minimize the amount of time that it spends looking up routes, DVMRP creates
and maintains a cache of frequently used routes -- called a forwarding table -- for
each IP interface.
By default, DVMRP preallocates a forwarding table of 32 entries for each circuit.
You can use Site Manager to specify the maximum number of entries (32 to 512)
allowed in the forwarding table associated with this circuit.
You do thisSystem responds
Customizing DVMRP
Site Manager Procedure
1. In the Configuration Manager window,
choose Protocols.
6. Set the Forward Cache Size parameter.
Click on Help or see the parameter
description on page A-8.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
When configuring a cache size, you must also keep in mind the TTL value for
entries. If you specify a large cache size, you can specify a larger TTL value. A
smaller cache requires a smaller TTL for cache entries.
117355-A Rev. A4-27
Configuring IP Multicasting and Multimedia Services
By default, DVMRP uses a TTL of 7200 seconds (two hours) for entries in the
forwarding table. You can use Site Manager to specify a TTL from 300 to 86400
seconds.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Forward Cache TTL parameter.
Click on Help or see the parameter
description on page A-9.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
If your neighbor is running mrouted, the recommended TTL value is 300 seconds.
4-28117355-A Rev. A
Disabling Advertisement of Local Networks
By default, DVMRP advertises its own local netw orks ov er this circuit. Using Site
Manager, you can configure DVMRP so that it does not advertise local networks
over the circuit.
Site Manager Procedure
You do thisSystem responds
Customizing DVMRP
1. In the Configuration Manager window,
choose Protocols.
6. Set the Route Listen parameter. Click on
Help or see the parameter description on
page A-10.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
117355-A Rev. A4-31
Configuring IP Multicasting and Multimedia Services
Accepting a Report from a Nonstandard DVMRP Neighbor
By default, DVMRP does not accept a report from a nonstandard DVMRP
neighbor.
A standard DVMRP router does not advertise a route report before sending a
probe message to a neighbor. DVMRP uses the probe message to learn the
neighbor’s capability. Some routers, however , send only route reports; the y do not
send probes. If you want DVMRP to communicate with nonstandard DVMRP
routers, be sure to set the Route Depend Probe parameter to Enable.
You can use Site Manager to enable and disable this feature as required.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Route Depend Probe parameter.
Click on Help or see the parameter
description on page A-10.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
4-32117355-A Rev. A
Configuring a Tunnel
You configure a DVMRP tunnel by setting parameters as described under the
following topics:
TopicPage
Supplying Addresses for the Tunnel4-34
Disabling and Reenabling the Tunnel4-35
Choosing the Encapsulation Mode4-36
Specifying the Cost4-37
Specifying a TTL4-38
Configuring a Forwarding Table for the Tunnel4-39
Advertising a Default Route4-41
Listening for a Default Route4-42
Specifying an Encapsulation Mode for Control Messages4-43
Accepting a Report from a Nonstandard DVMRP Neighbor4-44
Customizing DVMRP
117355-A Rev. A4-33
Configuring IP Multicasting and Multimedia Services
Supplying Addresses for the Tunnel
To identify a unicast tunnel, you must supply the unicast IP address of both ends
of the tunnel: the local interface and the remote interface. You can use Site
Manager to supply these addresses.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Enable parameter. Click on Help
or see the parameter description on page
A-11.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
117355-A Rev. A4-35
Configuring IP Multicasting and Multimedia Services
Choosing the Encapsulation Mode
By default, DVMRP encapsulates a tunneled multicast datagram in an IP unicast
datagram. Using Site Manager, you can configure D VMRP to loosely encapsulate
multicast datagrams using the LSSR option.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Metric parameter . Click on Help or
see the parameter description on page
A-11.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
117355-A Rev. A4-37
Configuring IP Multicasting and Multimedia Services
Specifying a TTL
By default, DVMRP assigns a TTL value of 1 to a tunnel. This value is the
minimum IP TTL required for a multicast datagram to be forwarded out this
tunnel. You can use Site Manager to assign a value from 1 to 254.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Threshold parameter. Click on Help or see the parameter description on
page A-12.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
Use this value to control the scope of the datagrams. If the IP TTL is less than the
threshold value you specify, the router drops the datagram.
4-38117355-A Rev. A
Configuring a Forwarding Table for the Tunnel
By default, DVMRP preallocates a forwarding table for 32 entries. You can use
Site Manager to specify the maximum number of entries (from 32 to 512) allowed
in the forwarding table associated with this tunnel interface.
Site Manager Procedure
You do thisSystem responds
Customizing DVMRP
1. In the Configuration Manager window,
choose Protocols.
6. Set the Forward Cache Size parameter.
Click on Help or see the parameter
description on page A-12.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
117355-A Rev. A4-39
Configuring IP Multicasting and Multimedia Services
When configuring a cache size, you must also keep in mind the TTL value for
entries. If you specify a large cache size, you can specify a larger TTL value. A
smaller cache requires a smaller TTL for cache entries.
By default, DVMRP assigns a TTL value of 7200 seconds to an entry in a tunnel
forwarding table. You can use Site Manager to assign a value from 300 to 86400
seconds.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Control Message Mode
parameter. Click on Help or see the
parameter description on page A-13.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
117355-A Rev. A4-43
Configuring IP Multicasting and Multimedia Services
Accepting a Report from a Nonstandard DVMRP Neighbor
By default, DVMRP does not accept a report from a nonstandard DVMRP
neighbor.
A standard DVMRP router does not advertise a route report before it has sent a
probe message to a neighbor. DVMRP uses the probe message to learn the
neighbor’s capability. Some routers, however , send only route reports; the y do not
send probes. If you want DVMRP to communicate with nonstandard DVMRP
routers, be sure to set the Route Depend Probe parameter to Enable.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
6. Set the Report Depend Probe parameter .
Click on Help or see the parameter
description on page A-14.
7. Click on Apply, and then click on Done.You return to the Configuration Manager
The Protocols menu opens.
opens.
window.
4-44117355-A Rev. A
Chapter 5
Customizing OSPF Multicast Extensions
MOSPF is a multicasting extension of OSPF. You configure MOSPF by setting
OSPF global parameters, interface parameters, and area parameters. This chapter
covers the following topics:
TopicPage
MOSPF Overview5-2
Configuring MOSPF Globally5-4
Configuring Multicast Forwarding on an OSPF Interface5-9
117355-A Rev. A5-1
Configuring IP Multicasting and Multimedia Services
MOSPF Overview
MOSPF is a multicasting extension of the OSPF protocol that allows a router to
forward multicast IP traffic within an OSPF Version 2 AS.
An OSPF environment typically consists of an AS divided into multiple areas
connected by an OSPF backbone. You can configure an OSPF/MOSPF router as a
•Multicasting internal router (IR) that establishes neighbor relationships with
adjacent routers within an area
•Multicasting border router (BR) with interfaces to one or more areas and to
the OSPF backbone
•Multicasting boundary router (ASBR) with one or more interfaces to external
autonomous systems
igure 5-1 shows an OSPF/MOSPF AS consisting of two OSPF areas connected
F
by an OSPF backbone.
5-2117355-A Rev. A
OSPF AS
OSPF/
MOSPF
BR
OSPF/
MOSPF
IR
Customizing OSPF Multicast Extensions
Backbone
(Area 0.0.0.0)
OSPF/
MOSPF
BR
OSPF/
MOSPF
IR
OSPF/
MOSPF
IR
Area 0.0.0.1
Key
IR Internal router
BR Border router
ASBR Boundary router
OSPF/
MOSPF
OSPF/
MOSPF
IR
IR
Area 0.0.0.2
External
ASBR
External
network
IP0055A
Figure 5-1.OSPF Autonomous Systems
MOSPF supports four types of multicasting:
•Intra-area multicasting for OSPF internal routers
•Intra-area and inter-area multicasting for OSPF border routers
•Intra-area and inter-AS multicasting for OSPF boundary routers
•All multicasting types
117355-A Rev. A5-3
Configuring IP Multicasting and Multimedia Services
Configuring MOSPF Globally
You can use Site Manager to add MOSPF extensions to OSPF.
Site Manager Procedure
You do thisSystem responds
1. In the Configuration Manager window,
choose Protocols.
2. Choose IP.The IP menu opens.
3. Choose OSPF.The OSPF menu opens.
4. Choose Global.The Edit OSPF Global Parameters
5. Set the Multicast Extensions parameter.
Click on Help or see the parameter
description on page A-29.
6. Click on OK.You return to the Configuration Manager
The Protocols menu opens.
window opens.
window.
After you configure OSPF with multicast extensions, you can set multicast global
parameters as described under the following topics:
TopicPage
Enabling Deterministic Multicasting5-5
Specifying a Forwarding Timeout Value5-6
Specifying a Maximum Number of Queued Packets5-7
Enabling Dynamic TTL5-8
Note: MOSPF will not forward datagrams out an interface until multicast
forwarding is enabled on the interface. For instructions, refer to “Configuring
Multicast Forwarding on an OSPF Interface” on page 5-9.
5-4117355-A Rev. A
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.