Спасибо хабру за большое количество статей по мультикасту.
Я же хочу поделиться опытом в настройке Мультикаст-роутинга на достаточно новом маршрутизаторе ASR9010 c IOS XR ver. 4.3.1. Примеров в ru’нете я не нашел. Настройка получения multicast’а от провайдера будет выполнена на связке PIM-SM/MBGP/MSDP.
Этапы настройки. 1. Собираем стык с провайдером контента. 2. Конфигурируем уровень 3 a. MBGP b. PIM c. MSDP 3. Настраиваем мультикаст vlan для пользователей
1. Стык
В данном примере стык организован через qinq канал id 211. Для стыка используется vlan id 213.
2. Конфигурируем уровень 3
Включаем мультикаст роутинг на интерфейсе, используемом для стыка с провайдером:
• Настраиваем MBGP/BGP
Предварительно настроим prefix-set с сетками мультикаст-источников и unicast маршрутом до точки RP, на их основе сделаем route-policy, т.к. по умолчанию ASR все маршруты будет «дропать».
Проверяем, приходят ли маршруты:
sh bgp ipv4 multicast
• Настраиваем PIM:
PIM – протокол мультикаст маршрутизации. Точка рондеву(RP) – как правило, это отдельный мультикаст-маршрутизатор на котором сходятся все мультикаст источники, как внешние так и внутренние. Задаем точку RP (rondevu point) и указываем, какие мультикаст группы мы будем с нее забирать
Проверяем наличие PIM-интерфейсов
sh pim interface bundle-ether 1.211213
• Настраиваем MSDP:
Multicast Source Discovery Protocol – с помощью этого протокола маршрутизатор клиента получает информацию о принадлежности мультикаст группы к тому или иному источнику в виде SA-сообщений, которые хранятся в SA-cache
Как правило, для настройки msdp используют адреса p2p соединения.
Делаем ACL для получения только нужных групп:
3. Мультикаст vlan для пользователей
Создаем bvi интерфейс будущего мультикаст вилана:
Создаем ACL в котором перечисляем мультикаст группы доступные в этом вилане:
Включаем на igmp-интерфейсе мультикаст-роутинг и устанавливаем поддержку igmp v2:
• Применяем igmp-profile и направляем мультикаст вилан на абонентский сегмент:
Создаем bridge group IPTV и bridge-domain 176:
Создаем l2transport интерфейс по направлению к абонентскому сегменту:
Добавляем в bridge-domain наш igmp-интерфейс и интерфейс по направлению на абонентский сегмент:
Примечание: Если выполнять изменения в igmp-профиле, то для их применения на бридж-домене потребуется убрать профиль из домена, применить изменения и опять его навесить.
Проверено на совместимость со следующими моделями устройств уровня доступа:
Cisco ASR 9000 Series Aggregation Services Router L2VPN and Ethernet Services Configuration Guide, Release 4.3.x
Results
Chapter: Configuring Link Bundles
Configuring Link Bundles
On the Cisco ASR 9000 Series Aggregation Services Routers, a bundle is a group of one or more ports that are aggregated together and treated as a single link. The different links within a single bundle can have varying speeds, where the fastest link can be a maximum of four times greater than the slowest link. Each bundle has a single MAC, a single IP address, and a single configuration set (such as ACLs or QoS).
The Cisco ASR 9000 Series Routers supports bundling for these types of interfaces:
NoteBundles do not have a one-to-one modular services card association.
Feature History for Configuring Link Bundling on Cisco IOS XR Software
Release
Modification
This feature was introduced on the Cisco ASR 9000 Series Routers.
Contents
This chapter includes these sections:
Prerequisites for Configuring Link Bundles
Before configuring Link Bundling, be sure that these tasks and conditions are met:
If you suspect user group assignment is preventing you from using a command, contact your AAA administrator for assistance.
– 2-port 10-Gigabit Ethernet line card
– 4-port 10-Gigabit Ethernet line card
– 8-port 10-Gigabit Ethernet line card
– 16-port 10-Gigabit Ethernet line card
– 20-port Gigabit Ethernet line card
– 40-port Gigabit Ethernet line card
NoteFor more information about physical interfaces, PLIMs, and modular services cards, refer to the Cisco ASR 9000 Series Routers Hardware Installation Guide.
Information About Configuring Link Bundles
To implement the Link Bundling feature, you must understand these concepts:
Link Bundling Overview
A link bundle is simply a group of ports that are bundled together and act as a single link. The advantages of link bundles are these:
Although the individual links within a single bundle can have varying speeds, all links within a bundle must be of the same type.
Cisco IOS XR software supports these methods of forming bundles of Ethernet interfaces:
Characteristics of Cisco ASR 9000 Series Routers Link Bundles
This list describes the properties and limitations of link bundles on Cisco ASR 9000 Series Routerss:
Link Aggregation Through LACP
Aggregating interfaces on different modular services cards provides redundancy, allowing traffic to be quickly redirected to other member links when an interface or modular services card failure occurs.
The optional Link Aggregation Control Protocol (LACP) is defined in the IEEE 802 standard. LACP communicates between two directly connected systems (or peers) to verify the compatibility of bundle members. For the Cisco ASR 9000 Series Routers, the peer can be either another router or a switch. LACP monitors the operational state of link bundles to ensure these:
LACP transmits frames containing the local port state and the local view of the partner system’s state. These frames are analyzed to ensure both systems are in agreement.
IEEE 802.3ad Standard
The IEEE 802.3ad standard typically defines a method of forming Ethernet link bundles.
For each link configured as bundle member, this information is exchanged between the systems that host each end of the link bundle:
This information is used to form the link aggregation group identifier (LAG ID). Links that share a common LAG ID can be aggregated. Individual links have unique LAG IDs.
The system identifier distinguishes one router from another, and its uniqueness is guaranteed through the use of a MAC address from the system. The bundle and link identifiers have significance only to the router assigning them, which must guarantee that no two links have the same identifier, and that no two bundles have the same identifier.
The information from the peer system is combined with the information from the local system to determine the compatibility of the links configured to be members of a bundle.
Bundle MAC addresses in the Cisco ASR 9000 Series Routers come from a set of reserved MAC addresses in the backplane.This MAC address stays with the bundle as long as the bundle interface exists. The bundle uses this MAC address until the user configures a different MAC address. The bundle MAC address is used by all member links when passing bundle traffic. Any unicast or multicast addresses set on the bundle are also set on all the member links.
NoteWe recommend that you avoid modifying the MAC address, because changes in the MAC address can affect packet forwarding.
QoS and Link Bundling
On the ingress direction, QoS is applied to the local instance of a bundle. Each bundle is associated with a set of queues. QoS is applied to the various network layer protocols that are configured on the bundle.
On the egress direction, QoS is applied on the bundle with a reference to the member links. QoS is applied based on the sum of the member bandwidths.
When QoS is applied on the bundle for either the ingress or egress direction, QoS is applied at each member interface.
The Link Bundling feature supports all the QoS features described in the Cisco ASR 9000 Series Aggregation Services Router Modular Quality of Service Configuration Guide.
The Link Bundling feature supports these QoS features:
VLANs on an Ethernet Link Bundle
802.1Q VLAN subinterfaces can be configured on 802.3ad Ethernet link bundles. Keep this information in mind when adding VLANs on an Ethernet link bundle:
NoteThe memory requirement for bundle VLANs is slightly higher than standard physical interfaces.
To create a VLAN subinterface on a bundle, include the VLAN subinterface instance with the interface Bundle-Ether command:
interface Bundle-Ether instance.subinterface
After you create a VLAN on an Ethernet link bundle, all physical VLAN subinterface configuration is supported on that link bundle.
Link Bundle Configuration Overview
These steps provide a general overview of the link bundle configuration process. Keep in mind that a link must be cleared of all previous network layer configuration before it can be added to a bundle:
1.In global configuration mode, create a link bundle. To create an Ethernet link bundle, enter the interface Bundle-Ether command.
2.Assign an IP address and subnet mask to the virtual interface using the ipv4 address command.
3.Add interfaces to the bundle you created in Step 1 with the bundle id command in the interface configuration submode. You can add up to 32 links to a single bundle.
NoteA link is configured to be a member of a bundle from the interface configuration submode for that link.
Nonstop Forwarding During Card Failover
Cisco IOS XR software supports nonstop forwarding during failover between active and standby paired RSP cards. Nonstop forwarding ensures that there is no change in the state of the link bundles when a failover occurs.
For example, if an active RSP fails, the standby RSP becomes operational. The configuration, node state, and checkpoint data of the failed RSP are replicated to the standby RSP. The bundled interfaces will all be present when the standby RSP becomes the active RSP.
NoteFailover is always onto the standby RSP.
NoteYou do not need to configure anything to guarantee that the standby interface configurations are maintained.
Link Failover
When one member link in a bundle fails, traffic is redirected to the remaining operational member links and traffic flow remains uninterrupted.
On the Cisco ASR 9000 Series Aggregation Services Routers, a bundle is a group of one or more ports that are aggregated together and treated as a single link. The different links within a single bundle can have varying speeds, where the fastest link can be a maximum of four times greater than the slowest link. Each bundle has a single MAC, a single IP address, and a single configuration set (such as ACLs or QoS).
The Cisco ASR 9000 Series Routers supports bundling for these types of interfaces:
How to Configure Link Bundling
This section contains these procedures:
Configuring Ethernet Link Bundles
This section describes how to configure a Ethernet link bundle.
NoteMAC accounting is not supported on Ethernet link bundles.
NoteIn order for an Ethernet bundle to be active, you must perform the same configuration on both connection endpoints of the bundle.
SUMMARY STEPS
The creation of an Ethernet link bundle involves creating a bundle and adding member interfaces to that bundle, as shown in the steps that follow.
— the ability to aggregate multiple interfaces together in an L2 manner, based on the standards defined in 802.1ax/802.1ad
— A group of physical interfaces with the same: speed,media, peer
— Treated as a single interface by higher layer protocol (one MAC, one IP, one set of configuration)
Alternative names used are: EtherChannel, Port-Channel, Link Bundle or LAG.
Advantages
— Increase link availability
— A single peering between two devices instead of having multiple individual links requiring ECMP (in L3) or STP (L2)
Functionality
— All the features are applied on the bundle interface, but replicated to the NPU’s that have members in this bundle.
— Members can be on multiple LCs
— L3 hashing is based on Source IP, Destination IP and Router ID, Src/Dest Ports are included too on TCP/UDP packet
— L2 hashing is based on Source MAC, Destination MAC, and Router ID
for more details on the Loadbalancing architecture see the https://supportforums.cisco.com/docs/DOC-26687
— Global MAC addresses stored in the backplane EEPROM are used as Bundle mac addresses
— Min/Max active member links can be configured on Bundle interface
— Bundle interface and its members can be shut/no shut independently
— There are 3 different modes: LACP (active/passive), or no LACP (ON)
— LACP in active mode will send and receive control packets as opposed to passive mode that will only response to received control packets
— LACP can be configured in short mode (1 sec) or long mode (30 sec) which determines the rate at which control packets are exchanged.
— For each port 28 bytes of information (LAG ID) and is exchanged between peers:
— If Bundle interface is outgoing multicast interface, then one bundle line card (BLC) is chosen to forward the multicast traffic and that decision is made by MRIB (In control plane).
— In egress BLC, packet is delivered to all Trident Chips. The member interface selected for a hash (from Trident Packet Header) will be local only to one Trident Chip. The other Trident Chip drops packet as member is not local.
Bundle Configuration
Bundle Config:
lacp system priority 40000
lacp system mac 000c.15c0.bd15
bundle maximum-active links hot-standby
Members Config
LACP Configuration
— An optional tool for checking that the bundle membership configuration makes sense and that the partner machine is also willing and able to aggregate the same set of links.
— Timeout: The default (long) period of a packet every 30 seconds (timeout after 90 seconds), and the «short» period of a packet every second (timeout after 3 seconds).
— Each LACP system has a system identifier which consists of a MAC address and a system priority. The MAC should be unique to the system (if it matches a partner system, LACP negotiations may fail), and the combination of the priority and MAC address are used to determine which is the higher priority system (default 32768)
— Starting from 4.1; the global system priority and MAC address can each be overridden for a specific bundle and configured under the bundle interface config
BFD over Bundle members (BoB or BFDoBM)
— BFD over Bundle members is an enhancement to the Layer 3 fast protection protocol for determining whether a Bundle member can be used to forward traffic
— BFD has three external states: Up, Down, Neighbor Unconfigured (Nbr_Unconfig)
— BFD sessions can be shut down in one of two ways:
— BFD sessions are only started on member links once they have reached LACP DISTRIBUTING state. Consequently the status of the BFD protocol does not affect the LACP state of a link in any way
Multichassis Link Aggregation (MC-LAG)
— A new feature for IOS XR release 4.0. MC-LAG involves two devices collaborating to act as a single LAG from the perspective of a (third) connected device
— Only one of the XR devices forwards traffic at any one time, eliminating the risk of forwarding loops. When a failure occurs, the XR devices coordinate to perform a switchover, changing the device on which traffic is being forwarded by manipulating the link LACP states
— The use case for this is at the edge of a provider’s network, to allow a «simple» customer edge (CE) device which only supports standard LACP to be connected to two provider edge (PE) devices. Thus the CE device is «dual-homed», providing better L2 redundancy from the provider’s side. In the mLACP documentation, the CE device is referred to as a Dual-Homed Device (DHD) and each PE device is known as a Point of Attachment (POA). The POA forwarding traffic for the bundle is the Active device for that bundle with the other POA being Standby
— The two POAs communicate with each other over an LDP link using the Inter-Chassis Communication Protocol (ICCP)
MLACP Configuration
mlacp system mac 000d.000e.000f
mlacp system priority 1
lacp switchover suppress-flaps 300
bundle wait-while 100
ipv4 address 5.4.3.1 255.255.255.255
description Connected to DHD Gi0/0/0/0
bundle id 1 mode active
description Connected to POA2 Gi0/0/0/3
ipv4 address 1.2.3.1 255.255.255.0
address-family ipv4 unicast
discovery targeted-hello accept
mlacp system mac 000d.000e.000f
mlacp system priority 1
lacp switchover suppress-flaps 300
bundle wait-while 100
ipv4 address 5.4.3.2 255.255.255.255
description Connected to DHD Gi0/0/0/3
bundle id 1 mode active
description Connected to POA1 Gi0/0/0/3
ipv4 address 1.2.3.2 255.255.255.0
address-family ipv4 unicast
discovery targeted-hello accept
lacp switchover suppress-flaps 300
bundle wait-while 100
description Connected to POA1 Gi0/0/0/0
bundle id 1 mode active
description Connected to POA2 Gi0/0/0/0
bundle id 1 mode active
Troubleshooting
— show bundle status
— show lacp system-id
— show bundle reasons
— admin show diag chassis eeprom-info
— bundle-hash bundle-ether 10
— show cef hardware egress detail location
— show controller bundle bundle-ether location
— show bundle trace all/process
— show tech-support bundle file
— admin show tech-support bundle file
— show iccp counters
— show iccp counters
— show mlacp inconsistencies
— When adding a member interface to a bundle ensure NO other configs present under the member interface.
RP/0/RSP0/CPU0:RTP-VIKING-L2-3(config)#interface gigabitEthernet 0/6/0/5RP/0/RSP0/CPU0:RTP-VIKING-L2-3(config-if)#bundle id 1 mode active RP/0/RSP0/CPU0:RTP-VIKING-L2-3(config-if)#commit% Failed to commit one or more configuration items during an atomic operation, no changes have been made. Please use ‘show configuration failed’ to view the errors
Show config failed would show the following reason.
!!% Bundle membership configuration conflicts with underlying physical link configuration (either already existing or also present in the same commit). Please refer to configuration documentation for further assistance.
Remove conflicting configuration to proceed
— Bundle interface doesn’t come up
— Bundle members are not distributing
— L3 traffic is not flowing
hardware detail egress location »
Make sure the rx_adj field matches the correct lag id. Make sure the «leaf» shows «forwarding» and nrLDI shows RX and TX adjacency as «COMPLETE»
Limitations/Restrictions
— All member links should be of the same speed
— Maximum number of Link Bundling interfaces per chassis is 255 (however a few are reserved for Bundle-POS interfaces)
— Maximum number of Link Bundle interface per line card is 64
— Maximum number of members per bundle is 64. User will be allowed to configure more than 8 members and the additional links will be in de-attached state
Bundles do not have a one-to-one modular services card association.