Добавил:
Опубликованный материал нарушает ваши авторские права? Сообщите нам.
Вуз: Предмет: Файл:

CCNP 642-811 BCMSN Exam Certification Guide - Cisco press

.pdf
Скачиваний:
161
Добавлен:
24.05.2014
Размер:
10.85 Mб
Скачать

366 Chapter 15: Multicast

You can limit the range of multicast groups supported by the RP by using an access list. The override keyword causes this RP to be preferred over any that is automatically determined. The RP must be defined on every router in the PIM domain, including the RP itself.

Cisco also provides a proprietary means to automatically inform PIM-SM routers of the appropriate RP for a group. This is known as Auto-RP. This is done by identifying a centrally located and wellconnected router to function as the mapping agent. The mapping agent learns of all candidate RPs that are announced over the Cisco-RP-Announce multicast address 224.0.1.39. To define a router as a mapping agent, use the following global configuration command:

Switch(config)# ip pim send-rp-disovery scope ttl

The mapping agent sends RP-to-group mapping information to all PIM routers over the Cisco-RP- Discovery multicast address 224.0.1.40. The Time-To-Live (TTL) value is set in these messages to limit the scope of the mapping. This limits how many router hops away the information will still be valid.

You must then explicitly define each candidate RP router. Once a router knows it can be an RP, it begins sending announcements to the mapping agent. Configure a router as an RP with the following global configuration command:

Switch(config)# ip pim send-rp-announce type mod/num scope ttl group-list access-list- number

The interface given corresponds to the advertised RP address. The announcement’s scope is limited by the number of router hops (TTL). The router will also advertise itself as a candidate RP for the multicast groups permitted in the access list.

PIM Version 2

The second version of PIM also includes a dynamic RP-to-group mapping advertisement mechanism. This is known as the boostrap router method, and is standards-based.

PIMv2 is similar to the Cisco auto-RP method. First, a bootstrap router (BSR) is identified; this router learns about RP candidates for a group and advertises them to PIM routers. You need to configure only the BSR and candidate RPs; all other PIM routers learn of the appropriate RP from the BSR. Define a BSR using the following global configuration command:

Switch(config)# ip pim bsr-candidate type mod/num hash-mask-length [priority]

The interface used determines the BSR address. RP selection for a group is based on a hashing function. The length of the hash mask controls the number of consecutive multicast groups that hash to the same RP.

Switching Multicast Traffic 367

Next, you must identify each of the candidate RP routers. Configure each RP with the following global configuration command:

Switch(config)# ip pim rp-candidate type mod/num ttl group-list access-list-number

Finally, by default, the bootstrap messages permeate the entire PIM domain. You can limit the scope of the advertisements by defining PIMv2 border routers, which will not forward the bootstrap messages. Use the following global configuration command:

Switch(config)# ip pim border

Switching Multicast Traffic

Routers or multilayer switches can build multicast trees and set up forwarding in an efficient, intelligent manner. At Layer 2, however, a switch can examine only the Ethernet frame header to find the source and destination MAC addresses. These switches cannot enjoy the luxury of ondemand multicast forwarding at all; the best information they have is the destination multicast address, and that signifies only that the frame needs to be flooded out all ports on the VLAN.

Two methods have been developed to help switches make intelligent forwarding decisions for multicast traffic: IGMP snooping and CGMP. One method requires more sophisticated switching hardware, whereas the other method leans on a nearby router for assistance.

IGMP Snooping

In normal operation, a host desiring multicast group membership must contact a local router so that it gets added into the multicast tree. IGMP snooping allows a switch to eavesdrop on these IGMP membership reports, so that it can find out who is requesting which group.

Recall that to join a group, a host must send its IGMP membership report to the multicast address of the group itself. A Layer 2-only switch must listen to every multicast frame to find the IGMP information. Clearly, this becomes a burden to the switch CPU.

A multilayer or Layer 3 switch has a clear advantage—it can inherently pick out Layer 3 information within frames. This type of switch must listen only to every IGMP packet. When a membership report is overheard, the switch adds the multicast group’s MAC address to its Content Addressable Memory (CAM) table (if it doesn’t already exist), along with the source switch port where the IGMP packet was received. This links the group address with the host who requested membership.

As other hosts request membership to the group, the respective switch ports are added to the CAM table list for the group address. Now, when a frame destined for the multicast group arrives, it can be replicated out exactly the right ports to reach the recipients.

368 Chapter 15: Multicast

With IGMP snooping, there are two special cases of group membership in the CAM table:

All multicast routers known by the switch (dynamically learned) are also recorded for a group in the CAM table. Multicast frames must also be replicated toward any routers so that they can be routed elsewhere if needed.

The switch CPU itself is also a member of every multicast group so that it can watch IGMP messages come and go. Only IGMP traffic is processed; the CPU does not inspect other multicast frames.

IGMP snooping is enabled on all switch ports and VLAN interfaces, by default, on switch platforms that support it. This includes the Catalyst 2950, 3550, 4500, and 6500 families, as each has additional hardware to support Layer 3 functionality. To enable or disable IGMP snooping, use the following global configuration command:

Switch(config)# [no] ip igmp snooping

CGMP

When a Layer 2 switch cannot perform IGMP snooping itself, a nearby multicast router can assist. Cisco developed the proprietary Cisco Group Membership Protocol (CGMP) for this purpose.

A router or multilayer switch configured for multicast routing can also be configured for CGMP. As hosts send IGMP membership reports to join or leave multicast groups, the CGMP router relays this message to all interested switches. The CGMP messages are multicast over the well-known address 0100.0cdd.dddd; by definition, this multicast group is flooded everywhere as a special case so that CGMP messages can be transported across non-CGMP switches.

The CGMP messages include the requesting host’s MAC address, along with the MAC address of the multicast group it wants to join or leave. When a Layer 2 switch receives this CGMP information, it becomes a simple task to add the multicast group and associated hosts to its CAM table. In effect, the router has become a “hearing aid” for a switch that is IGMP snooping “hearing impaired.”

By default, CGMP is disabled on all interfaces on multicast routers. To enable it, use the following interface configuration command:

Switch(config-if)# ip cgmp

Only the multicast router must be configured for CGMP. All IOS-based Layer 2 switches have CGMP enabled by default, so they will automatically process CGMP messages from routers.

Verifying Multicast Routing and Switching 369

NOTE As a rule, IGMP snooping and CGMP are mutually exclusive—they cannot both be used simultaneously on a switch. For switches that have IGMP snooping capability, IGMP snooping is enabled by default. For switches that cannot do IGMP snooping, CGMP is enabled by default.

If you are configuring IP multicast support in your network, be sure to identify any legacy Layer 2 switches that are capable only of flooding multicast traffic. Enable CGMP on these switches, and then enable CGMP on an upstream multicast router or multilayer switch. This way, your entire network will be able to intelligently constrain the flooding of multicast traffic.

Verifying Multicast Routing and Switching

To verify the operation of the features discussed in this chapter, you can use the commands listed in the sections that follow. In particular, look for the active router, standby or backup routers, and loadbalancing methods in use.

Multicast Routing with PIM

Remember that PIM is based on the unicast routing table; no separate multicast routing table is kept. Table 15-2 lists those commands that you need to verify that the multicast routing with PIM operations is working as intended.

Table 15-2 Commands for Verifying Multicast Routing with PIM

Task

Command Syntax

 

 

Show valid routes.

show ip route

 

 

Show neighboring PIM routers.

show ip pim neighbor

 

 

Verify RPF information for a host address.

show ip rpf ip-address

 

 

Show PIM RPs.

show ip pim rp

 

 

Show PIMv1 Auto-RP.

show ip pim autorp

 

 

Show PIM v2 BSRs.

show ip pim bsr-router

 

 

Multicast Switching

Table 15-3 lists those commands that you need to verify that IGMP snooping is configured and working as intended.

370 Chapter 15: Multicast

Table 15-3 Commands for Verifying IGMP Operation

Task

Command Syntax

 

 

List active IGMP groups and members.

show ip igmp groups

 

 

Show IGMP activity on an interface.

show ip igmp interface type mod/num

 

 

Show IGMP snooping activity.

show ip igmp snooping

 

 

You can also perform some multicast testing with multilayer switches. Choose a multicast group address that several switches can join. Configure a specific interface to join the group with the following interface configuration command:

Switch(config-if)# ip igmp join-group multicast-address

Then, you can use show commands to see information about the group and the IGMP membership. After several switches have joined the group, you can also issue a ping to the multicast group IP address. Every switch that has joined the group should answer with a reply.

What Would Happen Without a Multicast Router?

Suppose that a network is so small that a multicast router is not available. Instead, only one or more Layer 2 or Layer 3 switches are used. Can a multicast group be supported for users that want to view a streaming video from a server?

Multicast can always be supported, with or without a router. When a host sends an IGMP membership report to join a group, it does so blindly. After all, a host does not know about multicast routers at all—it just sends out a request to join and hopes that it will start receiving traffic destined for the multicast group address. Even if a multicast router is present, it doesn’t send a reply to a host that has joined a group. A router only periodically sends out membership queries asking if hosts are still wanting to remain a member of the group.

In this small network, Layer 2 switches will simply flood the server’s multicast traffic out all ports on the VLAN. No CGMP router is available to lend its intelligence. Layer 3 switches can use IGMP snooping, however, to constrain the multicast flooding. Although a router isn’t present, the switch can still listen to the membership reports being sent to the nonexistent router.

Foundation Summary 371

Foundation Summary

The Foundation Summary is a collection of information that provides a convenient review of many key concepts in this chapter. If you are already comfortable with the topics in this chapter, this summary can help you recall a few details. If you just read this chapter, this review should help solidify some key facts. If you are doing your final preparation before the exam, this information is a convenient way to review the day before the exam.

IP multicast addresses range from 224.0.0.0 to 239.255.255.255 (highest 4 bits are always 1110).

Multicast MAC addresses always start with 0100.5e (next bit is always 0). The lower 28 bits of the IP address are mapped over into the lower 23 bits of the MAC address.

RPF decides whether a multicast packet can be forwarded—if it arrived on an interface where the source can be found, it is forwarded; if not, it is dropped.

IGMP is the protocol used to join and leave (as well as to maintain) multicast groups.

PIM is a multicast routing protocol used to build multicast tree topologies.

Table 15-4 A Comparison of PIM Modes

 

Multicast Flows

Tree Construction

Tree Refinements

 

 

 

 

Dense Mode

(S,G)

Top-down; source is the

First flood, then prune

 

 

root, recipients are leaf

 

 

 

nodes

 

 

 

 

 

Sparse Mode

(*,G)

Bottom-up; RP is the root,

Group extended from

 

 

source can be anywhere,

recipients toward RP;

 

 

recipients are leaf nodes

pruning only when mem-

 

 

 

ber leaves group

 

 

 

 

Sparse-Dense Mode

(S,G) or (*,G)

Hybrid on a per-group basis

n/a

 

 

 

 

372 Chapter 15: Multicast

Table 15-5 IP PIM Multicast Configuration Commands

Task

Command Syntax

 

 

Enable multicast routing.

ip multicast-routing

 

 

Use PIM Dense Mode on an

ip pim dense-mode

interface.

 

 

 

Use PIM Sparse Mode on an

ip pim sparse-mode

interface.

 

 

 

Use PIM Sparse-Dense Mode.

ip pim sparse-dense-mode

 

 

Define a PIMv1 RP.

ip pim rp-address ip-address [access-list-number] [override]

 

 

Define a PIMv1 Auto-RP

ip pim send-rp-discovery scope ttl

mapping agent.

 

 

 

Identify the PIMv1 Auto-RP RP

ip pim send-rp-announce type mod/num scope ttl group-list access-

routers.

list-number

 

 

Define a PIMv2 BSR.

ip pim bsr-candidate type mod/num hash-mask-length [priority]

 

 

Identify the PIMv2 candidate

ip pim rp-candidate type mod/num ttl group-list access-list-number

RP routers.

 

 

 

Define a PIMv2 border router.

ip pim border

 

 

IGMP snooping allows a switch to intercept IGMP messages to learn of group members and their port locations.

CGMP allows a router to relay IGMP join and leave requests to Layer 2 switches. The switches then learn of group members and their port locations.

Q&A 373

Q&A

The questions and scenarios in this book are more difficult than what you should experience on the actual exam. The questions do not attempt to cover more breadth or depth than the exam; however, they are designed to make sure that you know the answers. Rather than allowing you to derive the answers from clues hidden inside the questions themselves, the questions challenge your understanding and recall of the subject. Hopefully, these questions will help limit the number of exam questions on which you narrow your choices to two options and then guess.

The answers to these questions can be found in Appendix A.

1.By default, what does a router or Layer 3 switch do with multicast packets?

2.By default, what does a Layer 2 switch do with a multicast packet?

3.What high-order bit combination signals that an IP address is used for multicast?

4.If the IP-to-MAC multicast address mapping is somewhat ambiguous, how can a frame be forwarded to the correct destination group?

5.What IP multicast address range is set aside for use only on the local network segment?

6.For the RPF check, the source IP address is looked up in the unicast routing table. To forward the packet, what should the result of the test be?

7.What important difference exists between IGMPv1 and IGMPv2?

8.To join a multicast group, what type of message is sent? Where is this message sent?

9.What is the purpose of the IGMP Querier?

10.For PIM Dense Mode, how is the multicast tree built?

11.Where is the root of the PIM Sparse Mode tree located?

12.With PIM Sparse-Dense Mode, is the PIM mode determined per interface or per group?

13.What routing table is used for PIM?

14.What command is used to configure an interface for the hybrid PIM mode?

15.When a switch performs IGMP snooping, what is it snooping for?

16.What else does a Layer 2 switch need when it is configured for CGMP?

17.When should IGMP snooping and CGMP be used together on a switch?

18.At a trade show, several PCs and servers are connected to a single Layer 2 switch. The switch has CGMP enabled. When a server begins to send video data to a multicast address, what happens to that traffic?

PART IV: Campus Network

Services

Chapter 16 Quality of Service Overview

Chapter 17 Diffserv QoS Configuration

Chapter 18 IP Telephony

Chapter 19 Securing Switch Access

Chapter 20 Securing with VLANs

This part of the book covers the following BCMSN exam topics:

Describe the quality issues with voice traffic on a switched data network, including jitter and delay.

Describe the QoS solutions that address voice-quality issues.

Describe the features and operation of network analysis modules on Catalyst switches to improve network traffic management.

Implement IP technology on a switched network with auxiliary VLANs.

Configure QoS features on multilayer switched networks to provide optimal quality and bandwidth utilization for applications and data.

Describe the general design models when implementing IP telephony in a switched network environment.

Plan QoS implementation within a multilayer switched network.

Соседние файлы в предмете Сети и Телекоммуникации