Introduction to IP Multicast

BRKIPM-1281

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

Session Goal
To provide you with an understanding of the
concepts, mechanics and protocols used to
build IP multicast networks
To enable you to ask the right questions, and
make the correct architectural decisions in
deploying and maintaining an IP Mulitcast
enabled network.

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

Agenda
Why Multicast?

Multicast History and Fundamentals

PIM Protocols
RP Choices

Multicast at Layer 2
Interdomain IP Multicast
IPv6 Multicast

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

Why Multicast?

Unicast vs. Multicast Scaling

Unicast
Server
Number of Streams

Router

Multicast
Server
Router
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

A Brief History of Multicast

Steven Deering, 1985, Stanford University
Yeah, he was way ahead of his time and too clever for all
of us.
A solution for layer2 applications in the growing layer3 campus
network
-Think overlay broadcast domain
Broadcast Domain
- all members receive
- all members can source
- members dynamically come and go
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

A Brief History of Multicast

RFC966 - 1985
Multi-destination delivery is useful to several applications, including:
- distributed, replicated databases [6,9].
- conferencing [11].
- distributed parallel computation, including distributed gaming [2].
All inherently many-to-many applications
No mention of one-to-many services such as Video/IPTV

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

A Brief History of Multicast

Overlay Broadcast Domain Requirements
- Tree building and maintenance
- Network-based source discovery
- Source route information
- Overlay mechanism tunneling
The first solution had it all
Distance Vector Multicast Routing Protocol
DVMRP, RFC1075 1988
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

A Brief History of Multicast

PIM Protocol Independent Multicast
Independent of which unicast routing protocol you run
It does require that youre running one.
Uses local routing table to determine route to sources

Router-to-router protocol to build and maintain distribution trees

Source discovery handled one of two ways:
1) Flood-and-prune PIM-DM, Dense Mode
2) Explicit Join w/ Rendezvous Point (RP) PIM-SM,
Sparse Mode - The Current Standard

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

10

A Brief History of Multicast

PIM-SM Protocol Independent Multicast Sparse Mode
- Tree building and maintenance
- Network-based source discovery
- Source route information
- Overlay mechanism tunneling
Long, Sordid IETF history
RFC4601 2006 (original draft was rewritten from
scratch)
Primary challenges to the final specification were in addressing Networkbased source discovery.

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

11

A Brief History of Multicast

Todays dominant applications are primarily one-to-many
IPTV, Contribution video over IP, etc.
Sources are well known
SSM Source Specific Multicast
RFC3569, RFC4608 2003

- Tree building and maintenance

- Network-based source discovery
- Source route information
- Overlay mechanism tunneling
Very simple and the preferred solution for one-to-many applications
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

12

Multicast Uses
Any applications with multiple receivers
One-to-many or many-to-many

Live video distribution

Collaborative groupware
Periodic data deliverypush technology
Stock quotes, sports scores, magazines, newspapers, adverts

Server/Website replication
Reducing network/resource overhead
More than multiple point-to-point flows

Resource discovery
Distributed interactive simulation (DIS)
War games
Virtual reality

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

13

Multicast Considerations
Multicast Is UDP-Based
Best effort delivery: Drops are to be expected; multicast applications should not
expect reliable delivery of data and should be designed accordingly; reliable
multicast is still an area for much research; expect to see more developments in
this area; PGM, FEC, QoS
No congestion avoidance: Lack of TCP windowing and slow-start mechanisms
can result in network congestion; if possible, multicast applications should attempt
to detect and avoid congestion conditions
Duplicates: Some multicast protocol mechanisms (e.g., asserts, registers, and
SPT transitions) result in the occasional generation of duplicate packets; multicast
applications should be designed to expect occasional duplicate packets

Out of order delivery: Some protocol mechanisms may also result in out of order
delivery of packets
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

14

Multicast Components
Cisco End-to-End Architecture
ISP A

ISP B

MSDP
RP

Multicast Source
X

Multicast Source
Y

DR

IGMP Snooping
PIM Snooping

ISP B

RP

ISP A

MBGP

DR

IGMP

PIM-SM: ASM,
SSM, BiDir
MVPN

AMT

End stations (hosts-to-routers)

IGMP, MLD, AMT

DR

Multicast routing across domains

MBGP

Campus Multicast

Interdomain Multicast

Switches (Layer 2 optimization)

Multicast source discover

IGMP snooping PIM snooping

MSDP with PIM-SM

Routers (multicast forwarding protocol)

PIM sparse mode or bidirectional PIM
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Source Specific Multicast

SSM
Cisco Public

15

Multicast Fundamentals

Unicast vs. Multicast Addressing

12.1.1.1
11.1.1.1

src addr:
10.1.1.1

src addr:
10.1.1.1
BRKIPM-1261

A unique packet
addressed to each
destination.

13.1.1.1

Same packet for

each destination.

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

17

Unicast vs. Multicast Addressing

12.1.1.1
11.1.1.1

src addr:
10.1.1.1

src addr:
10.1.1.1
BRKIPM-1261

A unique packet
addressed to each
destination.

13.1.1.1

How do we
address one
packet to
different
destinations?

..replicated at
each node along
the tree.
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

18

Multicast Addressing
Addressing
Multicast
IPv4 Header
Version

IHL

Type of Service

Identification

Time to Live

Total Length

Flags

Protocol

Fragment Offset

Header Checksum

Source
Source

Source Always
Addressthe unique unicast origin address of
1.0.0.0 - 223.255.255.255 (Class A, B, C)
the packet same as unicast

Destination
Destination

Destination Address
224.0.0.0 - 239.255.255.255 (Class D) Multicast Group Address
Options

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Range
Padding

Cisco Public

19

Multicast Addressing
Class D Group addresses 224/4

Multicast Group addresses are NOT in the unicast route table.

A separate route table is maintained for active multicast trees in the network.
Multicast state entries are initiated by receivers signaling their request to join a
group.
Sources do not need to join, they just send.
Multicast routing protocols build and maintain the trees, hop-by-hop, based on
receiver membership and source reach ability.
Source reach ability is derived from the unicast route table.
Multicast relies on a dependable unicast infrastructure.

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

20

Multicast state
Class D Group addresses 224/4
Multicast route entries are in (S,G) form.

barn#show ip mroute 232.1.1.109

(207.109.83.5, 232.1.1.109), 3w1d/00:02:40, flags: s

Incoming interface: Ethernet 0/0, RPF nbr 207.109.83.33
Outgoing interface list:
Ethernet 1/0, Forward/Sparse, 3w1d/00:02:40

Incoming interface points upstream

toward the root of the tree.

Ethernet 2/0, Forward/Sparse, 2w0d/00:02:33

barn#show ip route 232.1.1.109
% Network not in table
barn#

Outgoing interface list is where receivers

have joined downstream and where packets
will be replicated and forwarded downstream.
Multicast Group addresses
are NEVER in the unicast
route table.
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

21

Multicast Addressing224/4
Reserved link-local addresses
224.0.0.0224.0.0.255
Transmitted with TTL = 1
Examples

224.0.0.1

All systems on this subnet

224.0.0.2

All routers on this subnet

224.0.0.5

OSPF routers

224.0.0.13

PIMv2 routers

224.0.0.22

IGMPv3

Other reserved addresses

224.0.1.0224.0.1.255
Not local in scope (transmitted with TTL > 1)
Examples

224.0.1.1

NTP (Network Time Protocol)

224.0.1.32

Mtrace routers

224.0.1.78

Tibco Multicast1

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

22

Multicast Addressing224/4
Administratively scoped addresses
239.0.0.0239.255.255.255
Private address space
Similar to RFC1918 unicast addresses
Not used for global Internet trafficscoped traffic

GLOP (honest, its not an acronym)

233.0.0.0233.255.255.255
Provides /24 group prefix per ASN

SSM (Source Specific Multicast) range

232.0.0.0232.255.255.255
Primarily targeted for Internet-style broadcast
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

23

Multicast Addressing
IP Multicast MAC Address Mapping
1110

5 Bits
Lost

32 Bits
28 Bits

239.255.0.1

01-00-5e-7f-00-01
25 Bits

23 Bits

48 Bits

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

24

Multicast Addressing
IP Multicast MAC Address Mapping
Be Aware of the 32:1 Address Overlap
32IP Multicast Addresses
224.1.1.1
224.129.1.1
225.1.1.1
225.129.1.1
.
.
.
238.1.1.1
238.129.1.1
239.1.1.1
239.129.1.1
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

1Multicast MAC Address

0x0100.5E01.0101

Cisco Public

25

How Are Multicast Addresses Assigned?

Static global group address assignment (GLOP)
Temporary method to meet immediate needs
Group range: 233.0.0.0233.255.255.255
Your AS number is inserted in middle two octets
Remaining low-order octet used for group assignment

Defined in RFC 2770

GLOP Addressing in 233/8

SSM does not require group address ownership

Manual address allocation by the admin

Is still the most common practice

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

26

Host-Router Signaling:
Internet Group Management Protocol (IGMP)
How hosts tell routers about group membership
Routers solicit group membership from directly connected hosts
RFC 1112 specifies version 1 of IGMP
Supported on Windows 95

RFC 2236 specifies version 2 of IGMP

Supported on latest service pack for Windows and most
UNIX systems

RFC 3376 specifies version 3 of IGMP

Supported in Window XP and various UNIX systems

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

27

Host-Router Signaling: IGMP

Joining a Group
H2

H1

224.1.1.1

H3

Report

Host sends IGMP report to join group

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

28

Host-Router Signaling: IGMP

Maintaining a Group
224.1.1.1

224.1.1.1
H2

H1

Suppressed

Report

224.1.1.1

H3

Suppressed

Query

Router sends periodic queries to 224.0.0.1

One member per group per subnet reports
Other members suppress reports

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

29

Host-Router Signaling: IGMP

Leaving a Group (IGMPv2)
224.1.1.1
H1

H2
#1

Leave to
224.0.0.2
Group Specific
Query to 224.1.1.1
#2

Host sends leave message to 224.0.0.2

Router sends group-specific query to 224.1.1.1
No IGMP report is received within ~ 3 seconds
Group 224.1.1.1 times out
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

H3

Cisco Public

30

Host-Router Signaling: IGMPv3

RFC 3376 enables SSM
Adds include/exclude source lists
Enables hosts to listen only to a specified subset of the hosts
sending to the group

Requires new IPMulticastListen API

New IGMPv3 stack required in the OS
Apps must be rewritten to use IGMPv3 include/ exclude features

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

31

Host-Router Signaling: IGMPv3

New Membership Report Address
224.0.0.22 (IGMPv3 routers)
All IGMPv3 hosts send reports to this address
Instead of the target group address as in IGMPv1/v2

All IGMPv3 routers listen to this address

Hosts do not listen or respond to this address

No report suppression
All hosts on wire respond to queries
Hosts complete IGMP state sent in single response

Response interval may be tuned over broad range

Useful when large numbers of hosts reside on subnet

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

32

IGMPv3Joining a Group
1.1.1.10

1.1.1.11
H2

H1
v3 Report
(224.0.0.22)

H3

Group: 224.1.1.1
Include: (empty)

Joining member sends IGMPv3 report

to 224.0.0.22 immediately upon joining

BRKIPM-1261

1.1.1.12

2012 Cisco and/or its affiliates. All rights reserved.

1.1.1.1
rtr-a

Cisco Public

33

IGMPv3Joining Specific Source(s)

1.1.1.10

1.1.1.11
H2

H1
v3 Report
(224.0.0.22)

H3

Group: 232.1.1.1
Include: 10.0.0.1

IGMPv3 report contains desired

source(s) in the include list
Only Included source(s) are joined

BRKIPM-1261

1.1.1.12

2012 Cisco and/or its affiliates. All rights reserved.

1.1.1.1
rtr-a

Cisco Public

34

IGMPv3Maintaining State
1.1.1.10

1.1.1.11

H1

1.1.1.12

H3

H2
v3 Report
(224.0.0.22)

v3 Report
(224.0.0.22)

v3 Report
(224.0.0.22)

1.1.1.1

Query

Router sends periodic queries

All IGMPv3 members respond
Reports contain multiple group state records
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

35

Multicast L3 Forwarding
Multicast Routing is Backwards from Unicast Routing
Unicast routing is concerned about where the packet
is going
Multicast routing is concerned about where the packet came from
Initially

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

36

Unicast vs. Multicast Forwarding

Unicast Forwarding
Destination IP address directly indicates where to forward packet
Forwarding is hop-by-hop
Unicast routing table determines interface and next-hop router to forward packet

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

37

Unicast vs. Multicast Forwarding

Multicast Forwarding
Destination IP address (group) doesnt directly indicate where to forward
packet
Forwarding is Outgoing Interface List dependent (OIF)
Receivers must first be connected to the tree before traffic begins to flow
Connection messages (PIM joins) follow unicast routing
table toward multicast source
Build multicast distribution trees that determine where
to forward packets
Distribution trees rebuilt dynamically in case of network topology changes
Each router in the path maintains an OIF list per tree state

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

38

Reverse Path Forwarding (RPF)

The RPF Calculation
The multicast packets source address is checked against the unicast routing
table
This determines the interface and upstream router in the direction of the
source to which PIM joins are sent
This interface becomes the Incoming or RPF interface
A router forwards a multicast datagram only if received on the RPF interface

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

39

Reverse Path Forwarding (RPF)

RPF Calculation
SRC

Based on source address

Best path to source found in unicast
route table

10.1.1.1

A
Join

Determines where to send join

Joins continue towards source

to build multicast tree

B
D

Join

Multicast data flows down tree

E0

E1
E
E2

Unicast Route Table

Network
Interface
10.1.0.0/24
E0

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

R1

Cisco Public

40

Reverse Path Forwarding (RPF)

RPF Calculation

SRC

10.1.1.1

Based on source address

Best path to source found in unicast
route table

A
Join

Determines where to send join

Joins continue towards source
to build multicast tree
Multicast data flows down tree

C
Join

B
D
E0

R2

E1
E
E2
R1

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

41

Reverse Path Forwarding (RPF)

RPF Calculation

SRC

10.1.1.1

What if we have equal-cost paths?

We cant use both

Tie-breaker
B

Use highest next-hop IP address

D
1.1.1.1

Join
E0

Unicast Route Table

Network
Intfc Nxt-Hop
10.1.0.0/24 E0 1.1.1.1
10.1.0.0/24 E1 1.1.2.1
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

E
1.1.2.1
E1

F
E2
R1

Cisco Public

42

Multicast Distribution Trees

Shortest Path or Source Distribution Tree
Source 1

Notation: (S, G)
S = Source
G = Group

Source 2
A

BRKIPM-1261

Receiver 1

Receiver 2

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

43

Multicast Distribution Trees

Shortest Path or Source Distribution Tree
Source 1

Notation: (S2, G)
S = Source
G = Group

Source 2
A

BRKIPM-1261

Receiver 1

Receiver 2

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

44

Multicast Distribution Trees

Shared Distribution Tree
Notation: (*, G)
* = All Sources
G = Group

BRKIPM-1261

D (RP)

Receiver 1

Receiver 2

2012 Cisco and/or its affiliates. All rights reserved.

(RP)

PIM Rendezvous Point

Shared Tree

Cisco Public

45

Multicast Distribution Trees

Shared Distribution Tree
Source 1

Notation: (*, G)
* = All Sources
G = Group
Source 2

BRKIPM-1261

D (RP)

Receiver 1

Receiver 2

2012 Cisco and/or its affiliates. All rights reserved.

(RP)

PIM Rendezvous Point

Shared Tree
Source Tree

Cisco Public

46

Multicast Distribution Trees

Characteristics of Distribution Trees
Source or shortest path trees
Uses more memory O (S x G) but you get optimal paths from source to all receivers;
minimizes delay

Shared trees
Uses less memory O(G) but you may get suboptimal paths
from source to all receivers; may introduce extra delay

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

47

Multicast Tree Creation

PIM join/prune control messages
Used to create/remove distribution trees

Shortest path trees

PIM control messages are sent toward the source

Shared trees
PIM control messages are sent toward RP

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

48

PIM Protocol Variants

Major Deployed PIM Variants

PIM-SM
ASM
Any Source Multicast/RP/SPT/shared tree

SSM
Source Specific Multicast, no RP, SPT only

BiDir
Bidirectional PIM, no SPT, shared tree only

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

50

PIM-SM Shared Tree Join

RP

(*, G) State Created Only

Along the Shared Tree

(*, G) Join
Shared Tree
Receiver

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

51

PIM-SM Sender Registration

RP

Source

Traffic Flow
Shared Tree
Source Tree
(S, G) Register
(S, G) Join
BRKIPM-1261

(S, G) State Created Only

Along the Source Tree

(unicast)

Receiver

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

52

PIM-SM Sender Registration

RP

Source

Traffic Flow
Shared Tree
Source Tree
(S, G) Register
(S, G) Register-Stop
BRKIPM-1261

(S, G) Traffic Begins Arriving at

the RP via the Source Tree

(unicast)
(unicast)

Receiver

2012 Cisco and/or its affiliates. All rights reserved.

RP Sends a Register-Stop Back

to the First-Hop Router to Stop
the Register Process

Cisco Public

53

PIM-SM Sender Registration

RP

Source

Source Traffic Flows Natively

Along SPT to RP

Traffic Flow
Shared Tree
Source Tree

From RP, Traffic Flows Down

the Shared Tree to Receivers
Receiver

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

54

PIM-SM SPT Switchover

RP

Source

Traffic Flow
Shared Tree
Source Tree
(S, G) Join

BRKIPM-1261

Last-Hop Router Joins the

Source Tree

Receiver

2012 Cisco and/or its affiliates. All rights reserved.

Additional (S, G) State Is

Created Along New Part of the
Source Tree

Cisco Public

55

PIM-SM SPT Switchover

RP

Source

Traffic Flow
Shared Tree
Source Tree
(S, G)RP-bit Prune

BRKIPM-1261

Receiver

2012 Cisco and/or its affiliates. All rights reserved.

Traffic Begins Flowing

Down the New Branch of
the Source Tree
Additional (S, G) State Is Created
Along the Shared Tree to Prune Off
(S, G) Traffic

Cisco Public

56

PIM-SM SPT Switchover

RP

Source

(S, G) Traffic Flow Is Now

Pruned Off of the Shared Tree
and Is Flowing to the Receiver
via the Source Tree

Traffic Flow
Shared Tree
Source Tree
Receiver

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

57

PIM-SM SPT Switchover

RP

Source

Traffic Flow
Shared Tree
Source Tree
(S, G) Prune

BRKIPM-1261

(S, G) Traffic Flow Is No

Longer Needed by the RP so
It Prunes the Flow of (S, G)
Traffic
Receiver

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

58

PIM-SM SPT Switchover

RP

Source

(S, G) Traffic Flow Is Now Only

Flowing to the Receiver via a
Single Branch of the Source
Tree

Traffic Flow
Shared Tree
Source Tree
Receiver

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

59

The default behavior of PIM-SM (ASM) is that

routers with directly connected members will join
the shortest path tree as soon as they detect a
new multicast source.
PIM Frequently Forgotten Fact

PIM-SMEvaluation
Effective for sparse or dense distribution of multicast receivers
Advantages
Traffic only sent down joined branches
Can switch to optimal source-trees for high traffic sources dynamically
(sounds clever but it actually switches for all sources by default)

Unicast routing protocol-independent

Basis for interdomain, multicast routing
When used with MBGP, MSDP and/or SSM

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

61

Source Specific Multicast - SSM

Assume a one-to-many multicast model
Example: video/audio broadcasts, stock market data

Why does ASM need a shared tree?

So that hosts and last-hop routers can learn who the active source is for the source
discovery

What if this was already known?

Hosts could use IGMPv3 to signal exactly which (S, G) SPT to join

The shared tree and RP wouldnt be necessary

Different sources could share the same group address and not interfere with each
other

Result: Source Specific Multicast (SSM)

RFC 3569: An Overview of Source Specific Multicast (SSM)
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

62

PIM-SM SSM Tree Join

RP
Source

(S,G) State Created along

IGMPv3 (S,G) Host Report

(S,G) Join
Traffic Flow

Source Tree

Receiver

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

63

PIM-SM SSM Tree Join

RP
Source

Traffic arriving natively

along the source tree.

Shared Tree
Traffic Flow
Receiver

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

64

SSMEvaluation
Ideal for applications with one source sending to many receivers

Uses a simplified subset of the PIM-SM protocol

Simpler network operation

Solves multicast address allocation problems

Flows differentiated by both source and group
Not just by group

Content providers can use same group ranges

Since each (S,G) flow is unique

More secure
No Bogus source traffic
Cant consume network bandwidth
Not received by host application

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

65

Many-to-Many State Problem

Creates huge amounts of (S,G) state
State maintenance workloads skyrocket
High OIL fan-out makes the problem worse

Router performance begins to suffer

Using shared trees only

Provides some (S, G) state reduction
Results in (S, G) state only along SPT to RP
Frequently still too much (S, G) state
Need a solution that only uses (*, G) state

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

66

Bidirectional PIMOverview

Sender/
Receiver

RP
Receiver

Shared Tree
Receiver
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

67

Bidirectional PIMOverview

Sender/
Receiver

RP
Receiver

Source Traffic Forwarded

Bidirectionally Using (*,G) State
Shared Tree
Source Traffic
Receiver
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

68

Bidir PIMEvaluation
Ideal for many to many applications
Drastically reduces network mroute state
Eliminates all (S,G) state in the network
SPTs between sources to RP eliminated
Source traffic flows both up and down shared tree

Allows many-to-many applications to scale

Permits virtually an unlimited number of sources

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

69

RP Choices

PIM-SM ASM RP Requirements

Group to RP mapping
Consistent in all routers within the PIM domain

RP redundancy requirements
Eliminate any single point of failure

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

71

How Does the Network Learn RP Address?

Static configuration
Manually on every router in the PIM domain

AutoRP
Originally a Cisco solution
Facilitated PIM-SM early transition

BSR
draft-ietf-pim-sm-bsr

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

72

Static RPs
Hard-configured RP address
When used, must be configured on every router

All routers must have the same RP address

RP failover not possible
Exception: if anycast RPs are used

Command
ip pim rp-address <address> [group-list <acl>] [override]
Optional group list specifies group range
Default: range = 224.0.0.0/4 (includes auto-RP groups!)

Override keyword overrides auto-RP information

Default: auto-RP learned info takes precedence

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

73

C-RP
1.1.1.1

Announce

MA
B
Announce

Announce

Announce

Announce

MA

D
Announce

Announce

Auto-RPFrom 10,000 Feet

Announce

C-RP
2.2.2.2

RP-Announcements Multicast to the

Cisco Announce (224.0.1.39) Group
Announce
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

74

Auto-RPFrom 10,000 Feet

MA
A

C-RP
1.1.1.1

MA
B
D

C-RP
2.2.2.2

RP-Discoveries Multicast to the

Cisco Discovery (224.0.1.40) Group
Discovery
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

75

BSRFrom 10,000 Feet

BSR Election Process

C-BSR
D

C-BSR
C-BSR

C
E

BSR Msgs

BSR Messages Flooded Hop-by-Hop

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

76

BSRFrom 10,000 Feet

Highest Priority C-BSR
Is Elected as BSR
G

BSR
D

C
E

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

77

BSRFrom 10,000 Feet

BSR
D

C-RP

C-RP

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

78

BSRFrom 10,000 Feet

BSR
D

C-RP
BSR Msgs

C-RP

BSR Messages Containing RP-Set

Flooded Hop-by-Hop
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

79

Multicast at Layer 2

L2 Multicast Frame Switching

Problem: Layer 2 Flooding of Multicast Frames

Typical L2 switches treat multicast traffic as

unknown or broadcast and must flood the
frame to every port

PIM

Static entries can sometimes be set to specify

which ports should receive which group(s) of
multicast traffic
Dynamic configuration of these entries would
cut down on user administration

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Multicast M

Cisco Public

81

L2 Multicast Frame Switching

IGMPv1v2 Snooping
Switches become IGMP-aware
IGMP packets intercepted by the NMP
or by special hardware ASICs

PIM

Requires special hardware to maintain throughput

Switch must examine contents of IGMP messages to determine
which ports want what traffic
IGMP membership reports
IGMP leave messages

IGMP

Impact on low-end, Layer 2 switches

Must process all Layer 2 multicast packets

IGMP

Admin load increases with multicast traffic load

Generally results in switch meltdown
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

82

L2 Multicast Frame Switching

Impact of IGMPv3 on IGMP Snooping

IGMPv3 reports sent to separate group (224.0.0.22)

Switches listen to just this group

Only IGMP trafficno data traffic

Substantially reduces load on switch CPU
Permits low-end switches to implement IGMPv3 snooping

No report suppression in IGMPv3

Enables individual member tracking

IGMPv3 supports source-specific includes/excludes

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

83

SummaryFrame Switches
IGMP Snooping

Switches with Layer 3-aware hardware/ASICs

High-throughput performance maintained

Increases cost of switches
Switches without Layer 3-aware hardware/ASICs

Suffer serious performance degradation or

even meltdown!
Shouldnt be a problem when IGMPv3 is implemented

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

84

Interdomain IP Multicast

MBGP Overview
MBGP: Multiprotocol BGP

Defined in RFC 2858 (extensions to BGP)

Can carry different types of routes

Unicast
Multicast

Both routes carried in same BGP session

Does not propagate multicast state info
Thats PIMs job

Same path selection and validation rules

AS-Path, LocalPref, MED
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

86

MBGP Overview
Separate BGP tables maintained
Unicast prefixes for unicast forwarding

Unicast prefixes for multicast RPF checking

AFI = 1, Sub-AFI = 1
Contains unicast prefixes for unicast forwarding

Populated with BGP unicast NLRI

AFI = 1, Sub-AFI = 2
Contains unicast prefixes for RPF checking

Populated with BGP multicast NLRI

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

87

MBGP Overview
MBGP Allows Divergent Paths and Policies

Same IP address holds dual significance

Unicast routing information
Multicast RPF information

For same IPv4 address two different NLRI with different nexthops
Can therefore support both congruent and incongruent
topologies

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

88

Interdomain ASM? Really?? ;)

MSDP Multicast Source Discovery Protocol

RFC 3618
ASM only
RPs knows about all sources in their domain
Sources cause a PIM Register to the RP
Tell RPs in other domains of its sources
Via MSDP SA (Source Active) messages

RPs know about receivers in a domain

Receivers cause a (*, G) Join to the RP
RP can join the source tree in the peer domain
Via normal PIM (S, G) joins

MSDP required for interdomain ASM source discovery

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

90

MSDP Overview
MSDP Example
Domain E
RP

MSDP Peers

Domain C

Join (*, 224.2.2.2)

Receiver

RP

Domain B
RP
RP

Domain D
RP

Domain A
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

91

MSDP Overview
MSDP Example
Domain E
RP

MSDP Peers
Source Active
Messages

SA

SA

Domain C

Receiver

RP

Domain B

SA

SA

SA

RP
SA
SA

RP

SA Message
192.1.1.1, 224.2.2.2
Source

RP
SA Message
192.1.1.1, 224.2.2.2

Domain D

Domain A

Register
192.1.1.1, 224.2.2.2

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

92

MSDP Overview
MSDP Example
Domain E
RP

MSDP Peers

Domain C

Receiver

RP

Domain B
RP
RP

Domain D
RP
Source

BRKIPM-1261

Domain A
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

93

MSDP Overview
MSDP Example
Domain E
RP

MSDP Peers
Multicast Traffic

Domain C

Receiver

RP

Domain B
RP
RP

Domain D
RP
Source

BRKIPM-1261

Domain A
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

94

MSDP Overview
MSDP Example
Domain E
RP

MSDP Peers
Multicast Traffic

Domain C

Receiver

RP

Domain B
RP
RP

Domain D
RP
Source

BRKIPM-1261

Domain A
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

95

MSDP Overview
MSDP Example
Domain E
RP

MSDP Peers
Multicast Traffic

Domain C

Receiver

RP

Domain B
RP
RP

Domain D
RP
Source

BRKIPM-1261

Domain A
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

96

MSDP wrt SSMUnnecessary

Domain E
ASM MSDP Peers
(Irrelevant to SSM)

RP

Multicast Traffic

Domain C

Receiver

Receiver Learns
S and G Out of
Band, i.e.,
Webpage

RP

Domain B
RP
RP

Domain D
Source in 232/8
Source

BRKIPM-1261

RP

Domain A
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

97

MSDP wrt SSMUnnecessary

Domain E
ASM MSDP Peers
(Irrelevant to SSM)

RP

Multicast Traffic

Domain C

Receiver

Data flows natively

along the interdomain
source tree

RP

Domain B
RP
RP

Domain D
Source in 232/8
Source

BRKIPM-1261

RP

Domain A
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

98

Anycast RPOverview
Redundant RP technique for ASM which uses MSDP
for RP synchronization
Uses single defined RP address
Two or more routers have same RP address
RP address defined as a loopback interface
Loopback address advertised as a host route
Senders and receivers join/register with closest RP
Closest RP determined from the unicast routing table
Because RP is statically defined

MSDP session(s) run between all RPs

Informs RPs of sources in other parts of network
RPs join SPT to active sources as necessary

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

99

Anycast RPOverview

Src

RP1

BRKIPM-1261

RP2

MSDP

A
10.1.1.1

Rec

Src

SA

Rec

2012 Cisco and/or its affiliates. All rights reserved.

B
10.1.1.1

SA

Rec

Cisco Public

Rec

100

Anycast RPOverview

Src

Src
RP2

A
10.1.1.1

B
10.1.1.1

RP1

Rec

BRKIPM-1261

Rec

2012 Cisco and/or its affiliates. All rights reserved.

Rec

Cisco Public

Rec

101

Internet IP Multicast
We can build multicast distribution trees.
PIM

We can RPF on interdomain sources

MBGP

We no longer need (or want) network-based source discovery

SSM

So interdomain IP Multicast is in every home, right?

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

102

Whats Missing?
Without an overlay mechanism, Multicast in the Internet is an all or
nothing solution
Each receiver must be on an IP multicast-enabled path
Many core networks have IP multicast-enabled, but few
edge networks accept multicast transit traffic
Deering had tunneling in the original solution

Even Mcast-aware content owners are forced to provide unicast

streams to gain audience size
Unicast cannot scale dynamically for live content
Splitters/caches just distribute the problem
Still has a cost per user
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

103

AMTAutomatic Multicast Tunneling

Automatic IP multicast without explicit tunnels
http://www.ietf.org/internet-drafts/draft-ietf-mboned-auto-multicast-X.txt

Allow multicast content distribution to extend to

unicast-only connected receivers
Bring the flat scaling properties of multicast to the Internet

Provide the benefits of multicast wherever multicast

is deployed
Let the networks which have deployed multicast benefit from their deployment

Work seamlessly with existing applications

No OS kernel changes

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

104

Native Interdomain Multicast (SSM)

As Long as IP Multicast Is
Enabled on Every Router from
the Source to the Receivers,
the Benefits of IP Multicast Are
Realized

Content Owner

Mcast-Enabled ISP

Unicast-Only Network

Mcast Traffic
Mcast Join

Mcast-Enabled Local Provider

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

105

Native Interdomain Multicast (SSM)

The Benefits Being an Unlimited
Number of Receivers Can Be
Served with a Single Stream of
Content at No Additional Costs

Content Owner

Mcast-Enabled ISP

Unicast-Only Network

Mcast Traffic
Mcast Join

Mcast-Enabled Local Provider

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

106

AMTAutomatic Multicast Tunneling

The AMT Anycast Address
Allows for All AMT Gateway to
Find the Closest AMT Relay
the Nearest Edge
of the Multicast Topology of the
Source
Unicast-Only Network

Content Owner

Mcast-Enabled ISP

Mcast Traffic
Once the Multicast Join
Times Out,
an AMT Join Is
Sent from the
Host Gateway Toward
the Global AMT Anycast
Address
BRKIPM-1261

Mcast Join
AMT Request
Mcast-Enabled Local Provider
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

107

AMTAutomatic Multicast Tunneling

AMT Request Captured
by the AMT Relay
Router

Content Owner

Mcast-Enabled ISP

Unicast-Only Network

Mcast Traffic
Mcast Join
AMT Request
Mcast-Enabled Local Provider
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

108

AMTAutomatic Multicast Tunneling

Content Owner

Mcast-Enabled ISP
(S,G) Is Learned from the AMT Join
Message, Then (S,G) PIM Join Is Sent
Toward the Source
Unicast-Only Network

Mcast Traffic
Mcast Join
AMT Request
Mcast-Enabled Local Provider
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

109

AMTAutomatic Multicast Tunneling

AMT Relay Replicates Stream
on Behalf of Downstream
AMT Receiver, Adding a
Unicast Header Destined
to the Receiver

Content Owner

Mcast-Enabled ISP

Unicast-Only Network

Mcast Traffic
Mcast Join
AMT Request
Ucast Stream
Mcast-Enabled Local Provider
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

110

AMTAutomatic Multicast Tunneling

Additional Receivers Are Served by the
AMT Relays; the Benefits of IP Multicast
Are Retained by the Content Owner and
All Enabled Networks in the Path

Content Owner

Mcast-Enabled ISP

Unicast-Only Network

Mcast Traffic
Mcast Join
AMT Request
Ucast Stream
Mcast-Enabled Local Provider
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

111

AMTAutomatic Multicast Tunneling

Creates an Expanding Radius
of Incentive to Deploy Multicast

Content Owner

Mcast-Enabled ISP

Unicast-Only Network

Enables Multicast
Content to a Large
(Global) Audience
Mcast Traffic
Mcast Join
AMT Request
Ucast Stream
Mcast-Enabled Local Provider
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

112

AMTAutomatic Multicast Tunneling

Creates an Expanding Radius
of Incentive to Deploy Multicast

Content Owner

Mcast-Enabled ISP

Unicast-Only Network

Enables Multicast
Content to a Large
(Global) Audience
Mcast Traffic
Mcast Join
AMT Request
Ucast Stream
Mcast-Enabled Local Provider
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

113

AMTAutomatic Multicast Tunneling

Creates an Expanding Radius
of Incentive to Deploy Multicast

Content Owner

Mcast-Enabled ISP

Enables Multicast
Content to a Large
(Global) Audience
Mcast Traffic
Mcast Join
AMT Request
Ucast Stream
Mcast-Enabled Local Provider
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

114

IPv6 Multicast

IPv4 vs. IPv6 Multicast

IP Service

IPv4 Solution

IPv6 Solution

Address Range

32-Bit, Class D

128-Bit (112-Bit Group)

Protocol-Independent

Routing

Protocol-Independent

All IGPs and GBP4+

All IGPs and BGP4+

with v6 Mcast SAFI

Forwarding

PIM-DM, PIM-SM:
ASM, SSM, BiDir

PIM-SM: ASM, SSM, BiDir

Group Management

IBMPv1, v2, v3

MLDv1, v2

Domain Control

Boundary/Border

Scope Identifier

Interdomain Source Discovery

MSDP Across Independent PIM

Domains

Single RP Within Globally Shared

Domains

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

116

IPv6 Multicast Addresses (RFC 3513)

128 Bits
8
FF

4
4
Flags Scope

1111 1111

F
8 Bits

Flags
P T Scope

Flags =

8 Bits
Scope =

BRKIPM-1261

Interface-ID

T or Lifetime, 0 if Permanent, 1 if Temporary

P Proposed for Unicast-Based Assignments
Others Are Undefined and Must Be Zero
1 = interface-local
link
admin-local
5 = site
8 = organization
E = global

2012 Cisco and/or its affiliates. All rights reserved.

2=
4=

Cisco Public

117

IPv6 Layer 2 Multicast

Addressing Mapping

IPv6 Multicast Address

112 Bits
8
FF

4
4
Flags Scope

80
High-Order

32
Low-Order

80 Bits Lost

33-33-xx-xx-xx-xx
48 Bits

Ethernet MAC Address

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

118

Unicast-Based Multicast Addresses

8
FF

4
4
Flags Scope

8
Rsvd

8
Plen

64
Network-Prefix

32
Group-ID

RFC 3306unicast-based multicast addresses

Similar to IPv4 GLOP addressing

Solves IPv6 global address allocation problem

Flags = 00PT
P = 1, T = 1 Unicast-based multicast address

Example
Content providers unicast prefix
1234:5678:9::/48
Multicast address
FF3x:0030:1234:5678:0009::0001

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

119

IPv6 Routing for Multicast

RPF-based on reachability to v6 source same as
with v4 multicast
RPF still protocol-independent
Static routes, mroutes
Unicast RIB: BGP, ISIS, OSPF, EIGRP, RIP, etc.
Multiprotocol BGP (mBGP)
Support for v6 mcast subaddress family

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

120

IPv6 Multicast Forwarding

PIM-Sparse Mode (PIM-SM)
RFC4601

PIM Source Specific Mode (SSM)

RFC3569 SSM overview (v6 SSM needs MLDv2)
Unicast, prefix-based multicast addresses ff30::/12
SSM range is ff3X::/96

PIM Bi-Directional Mode (BiDir)

draft-ietf-pim-bidir-09.txt

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

121

RP Mapping Mechanisms for IPv6

Static RP assignment
BSR
Auto-RPno current plans
Embedded RP

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

122

Embedded RP AddressingRFC3956
8
FF

4
4
4
4
Flags Scope Rsvd RPadr

8
Plen

64
Network-Prefix

32
Group-ID

Proposed new multicast address type

Uses unicast-based multicast addresses (RFC 3306)

RP address is embedded in multicast address

Flag bits = 0RPT
R = 1, P = 1, T = 1 Embedded RP address

Network-Prefix::RPadr = RP address
For each unicast prefix you own, you now also own:
16 RPs for each of the 16 multicast scopes (256 total) with 2^32 multicast groups assigned to
each RP (2^40 total)

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

123

Embedded RP AddressingExample
Multicast Address with Embedded RP Address
8
FF

4
4
4
4
Flags Scope Rsvd RPadr

8
Plen

64
Network-Prefix

32
Group-ID

FF76:0130:1234:5678:9abc::4321

1234:5678:9abc::1
Resulting RP Address
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

124

Multicast Listener DiscoverMLD

MLD is equivalent to IGMP in IPv4
MLD messages are transported over ICMPv6
Version number confusion
MLDv1 corresponds to IGMPv2
RFC 2710

MLDv2 corresponds to IGMPv3, needed for SSM

RFC 3810

MLD snooping
draft-ietf-magma-snoop-12.txt

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

125

Now You Know

Why multicast?
Multicast fundamentals

PIM protocols
RP choices
Multicast at Layer 2

Interdomain IP multicast
IPv6 Multicast bits

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

126

Q&A

Announcing the New

IOS XR Specialist Certification!
Is there a training course I can take?
Yes! There is a New course: Implementing and Maintaining
Cisco Technologies Using IOS XR (IMTXR)
https://learningnetwork.cisco.com/community/certifications/ser
vice_provider/ios_xr_specialist

When can I get certified?

Launch date is June 12, 2012.
The IOS XR Specialist Certification exam number is 644-906.

How can I get access to IOS XR to prepare?

Customer & Partners: Cisco Learning Labs (July 2012)

Please spread the word about this

new Cisco Specialist Certification!

Partners: SE Gold Labs (July 2012)

Is there a Cisco Press book?

Yes! IOS XR Fundamentals (ISBN-10: 1-58705-271-7)

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

128

More Information
White papers
Web and mailers
Cisco Press

RTFB
CCO multicast
http://www.cisco.com/go/ipmulticast

Customer support mailing list

tac@cisco.com
RTFB = Read the Fine Book
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

129

Recommended Reading
Continue your Cisco Live learning
experience with further reading
from Cisco Press
Check the Recommended
Reading flyer for suggested
books

Available Onsite at the Cisco Company Store

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

SM
Cisco Public

130

Complete Your Online

Session Evaluation
Give us your feedback and you
could win fabulous prizes.
Winners announced daily.
Receive 20 Passport points for each
session evaluation you complete.

Complete your session evaluation

online now (open a browser through
our wireless network to access our Dont forget to activate your
Cisco Live Virtual account for access to
portal) or visit one of the Internet
stations throughout the Convention all session material, communities, and
on-demand and live activities throughout
Center.
the year. Activate your account at the
Cisco booth in the World of Solutions or visit
www.ciscolive.com.
BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

131

Final Thoughts
Get hands-on experience with the Walk-in Labs located in World of
Solutions, booth 1042
Come see demos of many key solutions and products in the main Cisco
booth 2924
Visit www.ciscoLive365.com after the event for updated PDFs, ondemand session videos, networking, and more!
Follow Cisco Live! using social media:
Facebook: https://www.facebook.com/ciscoliveus

Twitter: https://twitter.com/#!/CiscoLive
LinkedIn Group: http://linkd.in/CiscoLI

BRKIPM-1261

2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public

132

BRKIPM-1261
2012 Cisco and/or its affiliates. All rights reserved.

Cisco Public