4A0-108 Nokia Multicast Protocols Questions and Answers

It is the delay before the source PE switches traffic from the I-PMSI to the S-PMSI.

It is the delay before the source PE sends MDT Join TLVs.

It is the delay before the source PE switches traffic from the S-PMSI to the I-PMSI when traffic rate drops below the threshold.

It is the delay before the receiver PE prunes the S-PMSI.

Group Specific Query

Group Membership Query

Host Query

Source Specific Query

Group-and-Source Specific Query

MP_REACH_NLRI

MP_UNREACH_NLRI

MCAST-VPN NLRI

PMSINLRI

Alcatel-Lucent 7750 SR configuration does not permit using the system address for an anycast RP address.

The system address of a router must be a unique address within the domain, while the anycast address is configured on multiple routers within the domain.

PIM will not be able to establish its signaling sessions if the anycast address uses the system address.

Best practice is to use the system address as the anycast address for PIM.

The I-PMSI enables a PE to transmit packets to a subset of PEs in the MVPN.

An I-PMSI cannot be instantiated by MPLS P2MP P-tunnels.

The I-PMSI is created and signaled by PIM or BGP Auto Discovery.

An I-PMSI can be reused in multiple MVPNs.

MP-BGP, PIM

MP-BGP, MP-BGP

mLDP, PIM

MP-BGP, mLDP

Leave group message

Report suppression is eliminated

IGMP snooping

TTL of 1 for IGMP messages

Formalized IGMP Querier election

One to one

Many to all

One to many

Many to many

One to all

01-00-5e-66-3a-6b

01-00-5e-75-2a-0b

01-00-5e-67-2a-0b

00-01-5e-a1-2a-6b

00-01-5e-67-2a-0b

00-01-5e-76-2b-cc

It is how PIM neighbors become aware of each other

It is how receivers signal the source

It is the path to the RP

It is the multicast data forwarding path

It is the path to the DR

show router pim interface

show router pim status detail

show router pim status

show router interface detail

Allocate each AS a unique range of Inter-domain multicast addresses

Define an addressing structure for inside a domain

Provide a solution for the depletion of addresses

Eliminate the problem of IP multicast addresses overlapping when converted to multicast MAC addresses

It is a mechanism to distribute RP-set information dynamically

The bootstrap router gets and propagates RP information via multicast messages

The bootstrap router gets and propagates RP information via unicast and multicast messages

BSR relies on timers to discover that an RP-Candidate router is no longer available

For BSR to work, every router in the multicast network should be configured as BSR candidate

The router will propagate a (*, 239.1.1.1) join towards RP if it exists

The router will randomly pick a source from 192.168.1.1 and 192.168.1.2 and send an (S, G)join towards the source

The IGMPv3 report will be dropped and a log about misconfiguration will be generated

The router will send a PIM (192.168.1.1,232.1.1.1) Join

Channel 239.1.1.4 will be established while 239.1.1.8 will not

Channel 239.1.1.8 will be established while 239.1 1.4 will not

Both of these two channels will be established

Neither of these two channels will be established

This is the initial join message and exclusions of sources will follow

It is willing to receive traffic from any source

This is the initial join message and a selection of source will follow

This is the way it indicates it is leaving the group

The RP is the root of the tree

The multicast source is the root of the tree

It is represented by (*, G) entries

It is represented by (S, G) entries

The path between receiver and source is always the shortest path

It is always created as a result of switchover

It is the initial forwarding path created

Authentication

Guaranteed Delivery

Device Security

Preventing packet forwarding loops

Preventing Denial of Service attacks

The same way as it identifies receivers

From the IGMP Host Membership Reports received

From the default gateway address of unicast frames

From the IGMP Queries received

The switch issues a message on all ports to which only routers respond

The router will tear down channel 239.1.1.3 as it's non-mandatory and establish a new channel for 239.1.1.6

The router will tear down either channel 239.1.1.1 or 239.1.1.2 as they are low class and establish a new channel for 239.1.1.6

No existing channel will be torn down and the new channel for 239.1.1.6 will be established as there is enough resource

The new channel 239.1.1.6 won't be established and a log will be generated

Never

30 seconds

60 seconds

120 seconds

260 seconds

Whenever it receives a Query

Mrouter port is indicated by (**) entry in the MFIB

Mrouter port can be configured manually

A port on which any type of IGMP message is received will be set as an mrouter port

IGMP reports will only be forwarded out of mrouter ports once igmp-snooping is enabled in the vpls service

Allowing the source to select the multicast group address

Creating standards for Directory Services

Allowing the receiver to specify the source address

Modifying the IGMP messaging format to include the multicast source address

Modifying the PIM messaging format to include the multicast source address

When a router receives an IGMP Query from another device

When a router receives a PIM Hello from another device

When a router receives a BSM from a router with a better priority

When a router receives a multicast data packet on an outgoing interface

This is another term for asymmetric routing

This refers to having different routing policies or routing topologies for unicast and multicast networks

This refers to the case when the base routing table imports routes from two different protocols

This refers to the case when unicast and multicast routing tables contain the same route entries

Yes

No

IGMP

PIM

PIM or IGMP

PIM and IGMP are both used by a multicast receiver

BSM

PIM in the VRF.

PIM in the service provider's core network.

GRE encapsulation for multicast data traffic.

MPLS encapsulation for multicast data traffic.

vpn-ipv6

vpn-ipv4

mvpn-ipv6

mvpn-ipv4

FF7x:730:2001:DBS:FEED::/96 (x is scope)

FF7x:730:2001:DBS:FEED::/80 (x is scope)

FF7x: 740:2001:DB8:FEED::/96 (x is scope)

FF7x:740:2001:DB8:FEED::/80(x is scope)

23

25

27

28

MLD snooping enables switches to forward multicast data to specific hosts interested in the group.

MLD snooping can co-exist with IGMP snooping in the same VPLS service.

Once MLD snooping is enabled, the switch can snoop both MLDv1 and MLDv2 messages.

MLD snooping snoops MLD report and done messages, but not query messages.

FF02::1

FF02::2

FF02::16

The multicast group address of the multicast data that the router is receiving

Receivers are generally unknown by the source.

Receivers are generally known by each other.

It is well suited for applications in which the receivers provide feedback to each other and the source.

There is a single data flow for each group on the source segment.

All devices are potentially capable of generating multicast data.

It is well suited for applications such as video on demand, where each source sends a separate data stream to each of the many different receivers.