Configuración y solución de problemas de reflejo del servicio de multidifusión en Catalyst 8000
Introducción
Este documento describe el proceso para resolver problemas de la función Multicast Service Reflection en Catalyst 8000.
Prerequisites
Requirements
Cisco recomienda que tenga conocimiento sobre estos temas:
- Conocimiento del routing multidifusión básico
- Conocimiento de la línea de comandos de Cisco IOS® XE
Componentes Utilizados
La información que contiene este documento se basa en las siguientes versiones de software y hardware.
- Router Catalyst 8500
- Cisco IOS XE 17.9.4
La información que contiene este documento se creó a partir de los dispositivos en un ambiente de laboratorio específico. Todos los dispositivos que se utilizan en este documento se pusieron en funcionamiento con una configuración verificada (predeterminada). Si tiene una red en vivo, asegúrese de entender el posible impacto de cualquier comando.
Antecedentes
El propósito de este documento es demostrar la configuración básica y la resolución de problemas de la función Multicast Service Reflection para validar un escenario de traducción de destino de multidifusión a multidifusión con un Cisco Catalyst 8000.
La función Multicast Service Reflection es una función versátil que se puede implementar en varios puntos dentro de una red para satisfacer los requisitos específicos de multidifusión. Ayuda a mejorar la eficacia y la fiabilidad de los servicios de multidifusión in entornos de red complejos, ya que permite a los usuarios traducir las direcciones de destino de multidifusión o unidifusión recibidas a direcciones de multidifusión o unidifusión que cumplen con su directiva de direccionamiento interno.
La función Reflexión del servicio de multidifusión puede traducir ambos fuente y direcciones de destino in el encabezado IPv4. Identifica los flujos de tráfico multidifusión (asociados con orígenes y grupos multidifusión específicos) que deben traducirse (según la configuración predefinida) y, cuando el tráfico alcanza el punto de reflexión, el router que realiza la traducción refleja selectivamente estos paquetes.
Uno de los componentes principales de esta función es la interfaz virtual (Vif). Esta interfaz Vif es una interfaz lógica que puede unirse estáticamente al grupo que debe reflejarse in para generar el árbol de multidifusión. En otras palabras, esta interfaz Vif actúa como receptor multicast para la secuencia original y una vez que el tráfico se reenvía a la interfaz Vif, los paquetes se reflejan y las direcciones de origen/destino se traducen a las nuevas direcciones IPv4 deseadas.
Nota: Para implementar esta función, el router debe tener instalada al menos una licencia de ventaja de red; de lo contrario, se puede observar un error al intentar configurar la interfaz Vif.
Topología
Diagrama de topología
Configuración
Para configurar la función en esta configuración, el routing multidifusión debe activarse a través de la ruta y también se requiere conectividad IPv4 básica entre el origen de multidifusión y el receptor. En esta situación, hay un switch Catalyst 9K (C9000) que actúa como router de primer salto (FHR), a continuación, el router Catalyst 8K (C8000) que es el reflector de servicio de multidifusión y también el punto de encuentro (RP) para los diferentes grupos de multidifusión y un router ASR1K (ASR1000) es el router de último salto (LHR) al que se conecta el receptor. En este ejemplo, el protocolo de gateway fronterizo externo (eBGP) se utiliza para interconectar estos dispositivos; sin embargo, no es necesario implementar un protocolo de routing concreto.
Nota: En este ejemplo se utiliza un solo RP para los diversos flujos de multidifusión. Para obtener más información sobre escenarios en los que se utilizan diferentes RP para los dominios de multidifusión, consulte la sección Ejemplos de configuración para la reflexión del servicio de multidifusión de la Guía de configuración de multidifusión IP, Cisco IOS XE 17.x
FHR (C9000)
Para iniciar la configuración en el FHR, habilite el routing multidifusión, agregue la dirección IPv4 del RP y configure el modo disperso de multidifusión independiente de protocolo (PIM-SM) en las interfaces conectadas a la fuente de multidifusión y al router del reflector de servicio multidifusión (C8000).
C9000#show run | i multicast|rp-address ip multicast-routing class-map match-any system-cpp-police-multicast-end-station class-map match-any system-cpp-police-multicast ip pim rp-address 10.100.100.1
C9000#show run interface Ten 1/0/6 Building configuration... Current configuration : 116 bytes ! interface TenGigabitEthernet1/0/6 no switchport ip address 192.168.0.1 255.255.255.252 ip pim sparse-mode end C9000#show run interface Ten 1/0/3 Building configuration... Current configuration : 116 bytes ! interface TenGigabitEthernet1/0/3 no switchport ip address 192.168.0.5 255.255.255.252 ip pim sparse-mode endEl switch C9000 está realizando una adyacencia eBGP al router C8000 para anunciar las rutas conectadas.
C9000#show run | section router bgp
router bgp 65003
bgp log-neighbor-changes
redistribute connected
neighbor 192.168.0.6 remote-as 65001Router reflector de servicio multidifusión (C8000)
En el router Catalyst 8K, para la configuración inicial, habilite el ruteo multicast, agregue la dirección IPv4 de RP apropiada y también configure PIM-SM en las interfaces conectadas a los dispositivos C9000 y ASR1000, así como en la interfaz Loopback0.
Mcast_SR#show run | i multicast|rp-address ip multicast-routing distributed ip pim rp-address 10.100.100.1
Mcast_SR#show run interface Ten 0/0/2 Building configuration... Current configuration : 156 bytes ! interface TenGigabitEthernet0/0/2 description to C9000 ip address 192.168.0.6 255.255.255.252 ip pim sparse-mode no negotiation auto cdp enable end Mcast_SR#show run interface Ten 0/0/5 Building configuration... Current configuration : 157 bytes ! interface TenGigabitEthernet0/0/5 description to ASR1000 ip address 172.16.0.1 255.255.255.252 ip pim sparse-mode no negotiation auto cdp enable endMcast_SR#show run interface loopback 0 Building configuration... Current configuration : 88 bytes ! interface Loopback0 ip address 10.100.100.1 255.255.255.255 ip pim sparse-mode end
Este router tiene dos vecinos eBGP, el vecino 192.168.0.5 es el switch C9000 que envía los prefijos para alcanzar la fuente de multidifusión y el segundo vecino es el router ASR1000 utilizado para alcanzar el receptor. Observe que este router anuncia su Loopback0 local y también anuncia la subred Vif.
Mcast_SR#show run | section router bgp router bgp 65001 bgp log-neighbor-changes network 10.100.100.1 mask 255.255.255.255 network 172.16.101.0 mask 255.255.255.252 neighbor 172.16.0.2 remote-as 65002 neighbor 192.168.0.5 remote-as 65003
Ahora, es el momento de configurar la interfaz Vif, que es la que ayuda a traducir el grupo multicast de 239.5.5.5 a 239.55.55.55. Esta interfaz lógica debe tener una dirección IP y esta subred debe ser enrutable; además, se debe configurar PIM-SM. Para habilitar la función Multicast Service Reflection, se utiliza el comando ip service mirror <interface_id> destination <destination_ip1> to <destination_ip2> mask-len <subnet_mask_length> source <source_ip>, donde interface_id es la interfaz que recibe el tráfico de multidifusión original, destination_ip1 es la dirección IPv4 original que debe traducirse (239.5.5.5), y destination_ip2 es la nueva dirección IPv4 que se espera después de la traducción (traducción) 239.55.55.55). Por último, pero no menos importante, el comando ip igmp static-group <group-address> es necesario para hacer de esta interfaz un miembro conectado estáticamente del grupo multicast original.
Mcast_SR#configure terminal
Enter configuration commands, one per line. End with CNTL/Z.
Mcast_SR(config)#interface Vif1
Mcast_SR(config-if)#ip address 172.16.101.1 255.255.255.252
Mcast_SR(config-if)#ip pim sparse-mode
Mcast_SR(config-if)#ip service reflect TenGigabitEthernet0/0/2 destination 239.5.5.5 to 239.55.55.55 mask-len 32 source 172.16.101.2
Mcast_SR(config-if)#ip igmp static-group 239.5.5.5
Mcast_SR(config-if)#endNota: La interfaz "Vif1" está estrictamente asociada con el reenvío de ruta virtual (VRF) predeterminado para la función de reflejo del servicio de multidifusión. Si se selecciona un número diferente para esta interfaz, se puede mostrar un mensaje en la consola similar a "Sólo Vif1 se puede utilizar para el reflejo del servicio en la tabla global".
El siguiente resultado muestra la interfaz Vif después de que se haya aplicado la configuración, observe que la operación de la interfaz se convierte en UP/UP y que la función de salida es SERVICE REFLECT con la ayuda del comando show ip interface <interface>:
Mcast_SR#show run interface Vif1 Building configuration... Current configuration : 229 bytes ! interface Vif1 ip address 172.16.101.1 255.255.255.252 ip pim sparse-mode ip service reflect TenGigabitEthernet0/0/2 destination 239.5.5.5 to 239.55.55.55 mask-len 32 source 172.16.101.2 ip igmp static-group 239.5.5.5 endMcast_SR#show ip interface vif1 Vif1 is up, line protocol is up Internet address is 172.16.101.1/30 Broadcast address is 255.255.255.255 Address determined by non-volatile memory MTU is 1514 bytes Helper address is not set Directed broadcast forwarding is disabled Multicast reserved groups joined: 224.0.0.1 224.0.0.2 224.0.0.22 224.0.0.13 Outgoing Common access list is not set Outgoing access list is not set Inbound Common access list is not set Inbound access list is not set Proxy ARP is enabled Local Proxy ARP is disabled Security level is default Split horizon is enabled ICMP redirects are always sent ICMP unreachables are always sent ICMP mask replies are never sent IP fast switching is enabled IP Flow switching is disabled IP CEF switching is enabled IP CEF switching turbo vector IP Null turbo vector Associated unicast routing topologies: Topology "base", operation state is UP Associated multicast routing topologies: Topology "base", operation state is UP IP multicast fast switching is enabled IP multicast distributed fast switching is disabled IP route-cache flags are Fast, CEF Router Discovery is disabled IP output packet accounting is disabled IP access violation accounting is disabled TCP/IP header compression is disabled RTP/IP header compression is disabled Probe proxy name replies are disabled Policy routing is disabled Network address translation is disabled BGP Policy Mapping is disabled Input features: MCI Check Output features: SERVICE REFLECT IPv4 WCCP Redirect outbound is disabled IPv4 WCCP Redirect inbound is disabled IPv4 WCCP Redirect exclude is disabled IP Clear Dont Fragment is disabled
LHR (ASR1000)
Para la configuración en el LHR, de la misma manera, habilite el ruteo multicast y PIM-SM en las interfaces conectadas al router Multicast Service Reflector y hacia el receptor y asegúrese también de configurar la dirección IPv4 del RP:
ASR1000#show run | i multicast|rp-address ip multicast-routing distributed ip pim rp-address 10.100.100.1
ASR1000#show run interface Ten 0/1/1 Building configuration... Current configuration : 133 bytes ! interface TenGigabitEthernet0/1/1 ip address 172.16.0.2 255.255.255.252 ip pim sparse-mode no negotiation auto cdp enable end ASR1000#show run interface GigabitEthernet0/0/0 Building configuration... Current configuration : 127 bytes ! interface GigabitEthernet0/0/0 ip address 172.16.0.5 255.255.255.252 ip pim sparse-mode negotiation auto cdp enable end
Para la conectividad IP, este router también utiliza BGP para intercambiar los prefijos conectados:
ASR1000#show run | section router bgp
router bgp 65002
bgp log-neighbor-changes
redistribute connected
neighbor 172.16.0.1 remote-as 65001Verificación inicial
Como verificación inicial, puede comenzar a verificar la conectividad IP básica, el intercambio de rutas entre los dispositivos y el estado de PIM. El siguiente resultado fue tomado del Catalyst 9K y muestra las rutas instaladas hacia el Receptor (172.16.0.6), RP Loopback0 (10.100.100.1) y Vif (172.16.101.1). También se puede ver que hay una adyacencia PIM con el router C8000 y que la asignación RP también apunta a la dirección 10.100.100.1.
C9000#show ip route 172.16.0.6 Routing entry for 172.16.0.4/30 Known via "bgp 65003", distance 20, metric 0 Tag 65001, type external Last update from 192.168.0.6 2d22h ago Routing Descriptor Blocks: * 192.168.0.6, from 192.168.0.6, 2d22h ago opaque_ptr 0x7FD797D4BA18 Route metric is 0, traffic share count is 1 AS Hops 2 Route tag 65001 MPLS label: none C9000#ping 172.16.0.6 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.0.6, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms C9000#show ip route 10.100.100.1 Routing entry for 10.100.100.1/32 Known via "bgp 65003", distance 20, metric 0 Tag 65001, type external Last update from 192.168.0.6 2d22h ago Routing Descriptor Blocks: * 192.168.0.6, from 192.168.0.6, 2d22h ago opaque_ptr 0x7FD797D4B8D8 Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 65001 MPLS label: none C9000#ping 10.100.100.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.100.100.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms C9000#show ip route 172.16.101.1 Routing entry for 172.16.101.0/30 Known via "bgp 65003", distance 20, metric 0 Tag 65001, type external Last update from 192.168.0.6 2d00h ago Routing Descriptor Blocks: * 192.168.0.6, from 192.168.0.6, 2d00h ago opaque_ptr 0x7FD797D4B8D8 Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 65001 MPLS label: none C9000#ping 172.16.101.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.101.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms C9000#show ip pim neighbor PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, P - Proxy Capable, S - State Refresh Capable, G - GenID Capable, L - DR Load-balancing Capable Neighbor Interface Uptime/Expires Ver DR Address Prio/Mode 192.168.0.6 TenGigabitEthernet1/0/3 2d22h/00:01:29 v2 1 / DR S P G C9000#show ip pim interface Address Interface Ver/ Nbr Query DR DR Mode Count Intvl Prior 192.168.0.5 TenGigabitEthernet1/0/3 v2/S 1 30 1 192.168.0.6 192.168.0.1 TenGigabitEthernet1/0/6 v2/S 0 30 1 192.168.0.1C9000#show ip pim rp mapping PIM Group-to-RP Mappings Group(s): 224.0.0.0/4, Static RP: 10.100.100.1 (?)
El Reflector de Servicio Multicast muestra las direcciones 172.16.101.1 (Vif) y 10.100.100.1 (Loopback0) como conectadas directamente, y las rutas al Origen y al Receptor que se aprenden a través de BGP:
Mcast_SR#show ip route 10.100.100.1 Routing entry for 10.100.100.1/32 Known via "connected", distance 0, metric 0 (connected, via interface) Advertised by bgp 65001 Routing Descriptor Blocks: * directly connected, via Loopback0 Route metric is 0, traffic share count is 1
Mcast_SR#show ip route 172.16.101.1 Routing entry for 172.16.101.1/32 Known via "connected", distance 0, metric 0 (connected) Routing Descriptor Blocks: * directly connected, via Vif1 Route metric is 0, traffic share count is 1Mcast_SR#show ip route 172.16.0.6 Routing entry for 172.16.0.4/30 Known via "bgp 65001", distance 20, metric 0 Tag 65002, type external Last update from 172.16.0.2 5d20h ago Routing Descriptor Blocks: * 172.16.0.2, from 172.16.0.2, 5d20h ago opaque_ptr 0x7F841CBD53D0 Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 65002 MPLS label: none
Mcast_SR#show ip route 192.168.0.2 Routing entry for 192.168.0.0/30 Known via "bgp 65001", distance 20, metric 0 Tag 65003, type external Last update from 192.168.0.5 5d20h ago Routing Descriptor Blocks: * 192.168.0.5, from 192.168.0.5, 5d20h ago opaque_ptr 0x7F841CBD5290 Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 65003 MPLS label: none
El router C8000 también muestra dos vecinos PIM con cuatro interfaces habilitadas con PIM-SM (incluidos Vif y Loopback0), también se muestra la asignación de RP correcta y con el uso del comando show ip multicast puede verificar las capacidades de Reflejo del Servicio Multicast del dispositivo:
Mcast_SR#show ip pim neighbor PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, P - Proxy Capable, S - State Refresh Capable, G - GenID Capable, L - DR Load-balancing Capable Neighbor Interface Uptime/Expires Ver DR Address Prio/Mode 192.168.0.5 TenGigabitEthernet0/0/2 5d20h/00:01:34 v2 1 / S P G 172.16.0.2 TenGigabitEthernet0/0/5 5d20h/00:01:15 v2 1 / DR S P G Mcast_SR#show ip pim interface Address Interface Ver/ Nbr Query DR DR Mode Count Intvl Prior 10.100.100.1 Loopback0 v2/S 0 30 1 10.100.100.1 192.168.0.6 TenGigabitEthernet0/0/2 v2/S 1 30 1 192.168.0.6 172.16.0.1 TenGigabitEthernet0/0/5 v2/S 1 30 1 172.16.0.2 172.16.101.1 Vif1 v2/S 0 30 1 0.0.0.0 Mcast_SR#show ip pim rp mapping PIM Group-to-RP Mappings Group(s): 224.0.0.0/4, Static RP: 10.100.100.1 (?)Mcast_SR#show ip multicast Multicast Routing: enabled Multicast Multipath: disabled Multicast Route limit: No limit Multicast Fallback group mode: Sparse Number of multicast boundaries configured with filter-autorp option: 0 MoFRR: Disabled Multicast Service-Reflect Capabilities: Multicast to Multicast Unicast to Multicast Multicast to Unicast
En el LHR se realizan verificaciones similares. La siguiente salida tomada del router ASR1000 muestra las rutas instaladas para la fuente de multidifusión traducida 172.16.101.2 (esto es importante tener en cuenta ya que en este momento el paquete de secuencia de multidifusión se recibe con un nuevo encabezado IPv4 de origen y destino) y para la dirección IPv4 RP 10.100.100.1. Observe que LHR también tiene disponibilidad para el origen de multidifusión original 192.168.0.2; sin embargo, en este punto de la topología es más importante tener disponibilidad para la subred Vif (172.16.101.0/30):
ASR1000#show ip route 10.100.100.1 Routing entry for 10.100.100.1/32 Known via "bgp 65002", distance 20, metric 0 Tag 65001, type external Last update from 172.16.0.1 2d22h ago Routing Descriptor Blocks: * 172.16.0.1, from 172.16.0.1, 2d22h ago opaque_ptr 0x7F2BFA855B80 Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 65001 MPLS label: none ASR1000#ping 10.100.100.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 10.100.100.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms ASR1000#show ip route 172.16.101.1 Routing entry for 172.16.101.0/30 Known via "bgp 65002", distance 20, metric 0 Tag 65001, type external Last update from 172.16.0.1 2d00h ago Routing Descriptor Blocks: * 172.16.0.1, from 172.16.0.1, 2d00h ago opaque_ptr 0x7F2BFA855B80 Route metric is 0, traffic share count is 1 AS Hops 1 Route tag 65001 MPLS label: none ASR1000#ping 172.16.101.1 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 172.16.101.1, timeout is 2 seconds: !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms ASR1000#show ip pim neighbor PIM Neighbor Table Mode: B - Bidir Capable, DR - Designated Router, N - Default DR Priority, P - Proxy Capable, S - State Refresh Capable, G - GenID Capable, L - DR Load-balancing Capable Neighbor Interface Uptime/Expires Ver DR Address Prio/Mode 172.16.0.1 TenGigabitEthernet0/1/1 2d22h/00:01:24 v2 1 / S P G ASR1000#show ip pim interface Address Interface Ver/ Nbr Query DR DR Mode Count Intvl Prior 172.16.0.5 GigabitEthernet0/0/0 v2/S 0 30 1 172.16.0.5 172.16.0.2 TenGigabitEthernet0/1/1 v2/S 1 30 1 172.16.0.2ASR1000#show ip route 192.168.0.2 Routing entry for 192.168.0.0/30 Known via "bgp 65002", distance 20, metric 0 Tag 65001, type external Last update from 172.16.0.1 5d21h ago Routing Descriptor Blocks: * 172.16.0.1, from 172.16.0.1, 5d21h ago opaque_ptr 0x7F2BFA855E00 Route metric is 0, traffic share count is 1 AS Hops 2 Route tag 65001 MPLS label: none ASR1000#ping 192.168.0.2 source 172.16.0.5 Type escape sequence to abort. Sending 5, 100-byte ICMP Echos to 192.168.0.2, timeout is 2 seconds: Packet sent with a source address of 172.16.0.5 !!!!! Success rate is 100 percent (5/5), round-trip min/avg/max = 1/1/1 ms
Resolución de problemas
Después de que el origen de multidifusión comience a enviar el flujo para el grupo 239.5.5.5 y mientras habilita debug ip pim en los diferentes dispositivos a través de la topología, se puede confirmar que el FHR registra el origen de multidifusión 192.168.0.2 en el RP y agrega la interfaz TenGigabitEthernet1/0/3 a la lista de interfaces salientes (OIL).
C9000#
*Oct 16 16:23:01.817: PIM(0)[default]: Re-check RP 10.100.100.1 into the (*, 239.5.5.5) entry
*Oct 16 16:23:01.817: PIM(0)[default]: Building Triggered (*,G) Join / (S,G,RP-bit) Prune message for 239.5.5.5
*Oct 16 16:23:01.817: PIM(0)[default]: Adding register encap tunnel (Tunnel0) as forwarding interface of (192.168.0.2, 239.5.5.5).
*Oct 16 16:23:01.839: PIM(0)[default]: Received v2 Join/Prune on TenGigabitEthernet1/0/3 from 192.168.0.6, to us
*Oct 16 16:23:01.839: PIM(0)[default]: Join-list: (192.168.0.2/32, 239.5.5.5), S-bit set
*Oct 16 16:23:01.839: PIM(0)[default]: MIDB Add TenGigabitEthernet1/0/3/192.168.0.6 to (192.168.0.2, 239.5.5.5), Forward state, by PIM SG Join
*Oct 16 16:23:01.839: PIM(0)[default]: Join to 0.0.0.0 on TenGigabitEthernet1/0/6 for (192.168.0.2, 239.5.5.5), Ignored.
*Oct 16 16:23:03.869: PIM(0)[default]: Received v2 Join/Prune on TenGigabitEthernet1/0/3 from 192.168.0.6, to us
*Oct 16 16:23:03.869: PIM(0)[default]: Join-list: (192.168.0.2/32, 239.5.5.5), S-bit set
*Oct 16 16:23:03.869: PIM(0)[default]: MIDB Update TenGigabitEthernet1/0/3/192.168.0.6 to (192.168.0.2, 239.5.5.5), Forward state, by PIM SG Join
*Oct 16 16:23:05.818: PIM(0)[default]: Received v2 Register-Stop on TenGigabitEthernet1/0/3 from 10.100.100.1 *Oct 16 16:23:05.818: PIM(0)[default]: for source 192.168.0.2, group 239.5.5.5
*Oct 16 16:23:05.818: PIM(0)[default]: Removing register encap tunnel (Tunnel0) as forwarding interface of (192.168.0.2, 239.5.5.5).
*Oct 16 16:23:05.818: PIM(0)[default]: Clear Registering flag to 10.100.100.1 for (192.168.0.2/32, 239.5.5.5)
*Oct 16 16:23:11.997: PIM(0)[default]: Send v2 join/prune to 192.168.0.6 (TenGigabitEthernet1/0/3)
C9000#show ip mroute 239.5.5.5 IP Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group, G - Received BGP C-Mroute, g - Sent BGP C-Mroute, N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed, Q - Received BGP S-A Route, q - Sent BGP S-A Route, V - RD & Vector, v - Vector, p - PIM Joins on route, x - VxLAN group, c - PFP-SA cache created entry, * - determined by Assert, # - iif-starg configured on rpf intf, e - encap-helper tunnel flag, l - LISP decap ref count contributor Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join t - LISP transit group Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (*, 239.5.5.5), 00:24:22/stopped, RP 10.100.100.1, flags: SPF Incoming interface: TenGigabitEthernet1/0/3, RPF nbr 192.168.0.6 Outgoing interface list: Null (192.168.0.2, 239.5.5.5), 00:24:22/00:03:11, flags: FT Incoming interface: TenGigabitEthernet1/0/6, RPF nbr 0.0.0.0 Outgoing interface list: TenGigabitEthernet1/0/3, Forward/Sparse, 00:24:22/00:02:47, flags: Al mismo tiempo, el router Multicast Service Reflector (que también es el RP para ambos grupos) recibe el registro para el S,G (192.168.0.2, 239.5.5.5) e inmediatamente detecta que este grupo cae bajo la regla de reflexión previamente definida. Luego agrega el TenGigabitEthernet0/0/2 como la interfaz entrante para el flujo 239.5.5.5, y luego registra el nuevo S,G (172.16.101.2, 239.55.55.55) a sí mismo. El router agrega Vif1 como la interfaz entrante para la secuencia 239.55.55.55 y coloca TenGigabitEthernet0/0/5 (conectándose a ASR1000) en el OIL, como se muestra en la salida del comando debug y show ip mroute:
Mcast_SR#
*Oct 16 15:46:11.758: PIM(0)[default]: Received v2 Register on TenGigabitEthernet0/0/2 from 192.168.0.5 *Oct 16 15:46:11.758: for 192.168.0.2, group 239.5.5.5
*Oct 16 15:46:11.758: PIM(0)[default]: Adding register decap tunnel (Tunnel1) as accepting interface of (192.168.0.2, 239.5.5.5). *Oct 16 15:46:11.758: MSR(0)[default]: Add 239.5.5.5 to all the SR rules *Oct 16 15:46:11.758: MSR: Found Grp idx 553648130 for rule 239.5.5.5->239.55.55.55 *Oct 16 15:46:11.758: MSR: Found Grp idx 553648130 for rule 239.5.5.5->239.55.55.55
*Oct 16 15:46:11.758: PIM(0)[default]: Insert (192.168.0.2,239.5.5.5) join in nbr 192.168.0.5's queue
*Oct 16 15:46:11.758: PIM(0)[default]: Building Join/Prune packet for nbr 192.168.0.5
*Oct 16 15:46:11.758: PIM(0)[default]: Adding v2 (192.168.0.2/32, 239.5.5.5), S-bit Join
*Oct 16 15:46:11.758: PIM(0)[default]: Send v2 join/prune to 192.168.0.5 (TenGigabitEthernet0/0/2)
*Oct 16 15:46:12.929: PIM(0)[default]: Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.55.55.55
*Oct 16 15:46:12.929: PIM(0)[default]: rp our address for group 239.55.55.55
*Oct 16 15:46:13.251: PIM(0)[default]: Received v2 Join/Prune on TenGigabitEthernet0/0/5 from 172.16.0.2, to us
*Oct 16 15:46:13.251: PIM(0)[default]: Join-list: (*, 239.55.55.55), RPT-bit set, WC-bit set, S-bit set
*Oct 16 15:46:13.252: PIM(0)[default]: MIDB Update TenGigabitEthernet0/0/5/172.16.0.2 to (*, 239.55.55.55), Forward state, by PIM *G Join
*Oct 16 15:46:13.732: PIM(0)[default]: Received v2 Register on TenGigabitEthernet0/0/2 from 192.168.0.5
*Oct 16 15:46:13.732: for 192.168.0.2, group 239.5.5.5
*Oct 16 15:46:13.732: PIM(0)[default]: Removing register decap tunnel (Tunnel1) as accepting interface of (192.168.0.2, 239.5.5.5).
*Oct 16 15:46:13.732: PIM(0)[default]: Installing TenGigabitEthernet0/0/2 as accepting interface for (192.168.0.2, 239.5.5.5).
*Oct 16 15:46:13.732: PIM(0)[default]: Prune to 0.0.0.0 on for (192.168.0.2, 239.5.5.5), Ignored.
*Oct 16 15:46:13.773: PIM(0)[default]: Adding register decap tunnel (Tunnel1) as accepting interface of (172.16.101.2, 239.55.55.55). *Oct 16 15:46:13.773: PIM(0)[default]: Adding register encap tunnel (Tunnel0) as forwarding interface of (172.16.101.2, 239.55.55.55).
*Oct 16 15:46:13.773: PIM(0)[default]: Removing register decap tunnel (Tunnel1) as accepting interface of (172.16.101.2, 239.55.55.55).
*Oct 16 15:46:13.773: PIM(0)[default]: Installing Vif1 as accepting interface for (172.16.101.2, 239.55.55.55).
*Oct 16 15:46:13.788: PIM(0)[default]: Insert (192.168.0.2,239.5.5.5) join in nbr 192.168.0.5's queue
*Oct 16 15:46:13.788: PIM(0)[default]: Building Join/Prune packet for nbr 192.168.0.5
*Oct 16 15:46:13.788: PIM(0)[default]: Adding v2 (192.168.0.2/32, 239.5.5.5), S-bit Join
*Oct 16 15:46:13.788: PIM(0)[default]: Send v2 join/prune to 192.168.0.5 (TenGigabitEthernet0/0/2)
*Oct 16 15:46:13.794: PIM(0)[default]: Received v2 Register on Vif1 from 10.100.100.1
*Oct 16 15:46:13.794: for 172.16.101.2, group 239.55.55.55
*Oct 16 15:46:13.794: PIM(0)[default]: Send v2 Register-Stop to 10.100.100.1 for 172.16.101.2, group 239.55.55.55
*Oct 16 15:46:13.794: PIM(0)[default]: Received v2 Register-Stop on Loopback0 from 10.100.100.1
*Oct 16 15:46:13.794: PIM(0)[default]: for source 172.16.101.2, group 239.55.55.55
*Oct 16 15:46:13.794: PIM(0)[default]: Removing register encap tunnel (Tunnel0) as forwarding interface of (172.16.101.2, 239.55.55.55).
*Oct 16 15:46:13.794: PIM(0)[default]: Clear Registering flag to 10.100.100.1 for (172.16.101.2/32, 239.55.55.55)
*Oct 16 15:46:13.809: PIM(0)[default]: Received v2 Join/Prune on TenGigabitEthernet0/0/5 from 172.16.0.2, to us
*Oct 16 15:46:13.809: PIM(0)[default]: Join-list: (172.16.101.2/32, 239.55.55.55), S-bit set
*Oct 16 15:46:13.809: PIM(0)[default]: MIDB Update TenGigabitEthernet0/0/5/172.16.0.2 to (172.16.101.2, 239.55.55.55), Forward state, by PIM SG Join
Mcast_SR#show ip mroute IP Multicast Routing Table Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected, L - Local, P - Pruned, R - RP-bit set, F - Register flag, T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet, X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement, U - URD, I - Received Source Specific Host Report, Z - Multicast Tunnel, z - MDT-data group sender, Y - Joined MDT-data group, y - Sending to MDT-data group, G - Received BGP C-Mroute, g - Sent BGP C-Mroute, N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed, Q - Received BGP S-A Route, q - Sent BGP S-A Route, V - RD & Vector, v - Vector, p - PIM Joins on route, x - VxLAN group, c - PFP-SA cache created entry, * - determined by Assert, # - iif-starg configured on rpf intf, e - encap-helper tunnel flag, l - LISP decap ref count contributor Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join t - LISP transit group Timers: Uptime/Expires Interface state: Interface, Next-Hop or VCD, State/Mode (*, 239.5.5.5), 00:50:36/stopped, RP 10.100.100.1, flags: SJC Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: Vif1, Forward/Sparse, 00:50:36/00:00:23, flags: (192.168.0.2, 239.5.5.5), 00:10:08/00:02:36, flags: T Incoming interface: TenGigabitEthernet0/0/2, RPF nbr 192.168.0.5 Outgoing interface list: Vif1, Forward/Sparse, 00:10:08/00:01:51, flags: (*, 239.55.55.55), 00:50:21/00:03:11, RP 10.100.100.1, flags: SF Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: TenGigabitEthernet0/0/5, Forward/Sparse, 00:50:21/00:03:11, flags: (172.16.101.2, 239.55.55.55), 00:10:06/00:03:23, flags: FT Incoming interface: Vif1, RPF nbr 0.0.0.0 Outgoing interface list: TenGigabitEthernet0/0/5, Forward/Sparse, 00:10:06/00:03:16, flags: (*, 224.0.1.40), 00:50:36/00:03:28, RP 10.100.100.1, flags: SJCL Incoming interface: Null, RPF nbr 0.0.0.0 Outgoing interface list: TenGigabitEthernet0/0/2, Forward/Sparse, 00:50:13/00:03:28, flags: TenGigabitEthernet0/0/5, Forward/Sparse, 00:50:28/00:03:10, flags: Loopback0, Forward/Sparse, 00:50:36/00:02:17, flags: Nota: Observe que para poder observar las reglas de Reflexión del Servicio Multicast que se utilizan en la salida de debug, el debug ip multicast service-mirror debe estar habilitado. Tenga en cuenta que esta depuración en particular se introdujo en la versión 17.9.1a de Cisco IOS-XE; para obtener información adicional, consulte la sección Información sobre la Función Multicast Service Reflection de la Guía de Configuración de IP Multicast, Cisco IOS XE 17.x
Desde el resultado anterior de show ip mroute se puede ver que hay entradas *,G y S,G para los grupos multicast original y nuevo. Además, el uso del comando show ip mroute <group> count puede dar una idea de los paquetes recibidos y reenviados para cada flujo de multidifusión. Esta salida también es útil ya que ayuda a identificar el reenvío de tráfico mediante la confirmación de los contadores de incremento:
Mcast_SR#show ip mroute 239.5.5.5 count
Use "show ip mfib count" to get better response time for a large number of mroutes.
IP Multicast Statistics
5 routes using 5796 bytes of memory
3 groups, 0.66 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 239.5.5.5, Source count: 1, Packets forwarded: 4053, Packets received: 4056
RP-tree: Forwarding: 11/0/100/0, Other: 12/1/0
Source: 192.168.0.2/32, Forwarding: 4042/0/113/0, Other: 4044/2/0
Mcast_SR#show ip mroute 239.5.5.5 count
Use "show ip mfib count" to get better response time for a large number of mroutes.
IP Multicast Statistics
5 routes using 5796 bytes of memory
3 groups, 0.66 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 239.5.5.5, Source count: 1, Packets forwarded: 4058, Packets received: 4061
RP-tree: Forwarding: 11/0/100/0, Other: 12/1/0
Source: 192.168.0.2/32, Forwarding: 4047/0/113/0, Other: 4049/2/0
Mcast_SR#show ip mroute 239.55.55.55 count
Use "show ip mfib count" to get better response time for a large number of mroutes.
IP Multicast Statistics
5 routes using 5796 bytes of memory
3 groups, 0.66 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 239.55.55.55, Source count: 1, Packets forwarded: 4046, Packets received: 4046
RP-tree: Forwarding: 0/0/0/0, Other: 0/0/0
Source: 172.16.101.2/32, Forwarding: 4046/0/114/0, Other: 4046/0/0
Mcast_SR#show ip mroute 239.55.55.55 count
Use "show ip mfib count" to get better response time for a large number of mroutes.
IP Multicast Statistics
5 routes using 5796 bytes of memory
3 groups, 0.66 average sources per group
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kilobits per second
Other counts: Total/RPF failed/Other drops(OIF-null, rate-limit etc)
Group: 239.55.55.55, Source count: 1, Packets forwarded: 4051, Packets received: 4051
RP-tree: Forwarding: 0/0/0/0, Other: 0/0/0
Source: 172.16.101.2/32, Forwarding: 4051/0/114/0, Other: 4051/0/0Si no se crean las entradas S,G, es importante determinar si los paquetes multicast se están recibiendo en la interfaz esperada. Algunas opciones para confirmar esta situación son el uso de una captura de paquetes incorporada (EPC) o con un seguimiento de paquetes; en el siguiente resultado, se tomó un EPC en las interfaces de entrada (Te0/0/2) y de salida (Te0/0/5) del router C8000. En este escenario de trabajo, puede observar el flujo de multidifusión original 239.5.5.5 entrante y el nuevo flujo 239.55.55.55 egresando del router:
Mcast_SR#monitor capture msr buffer size 10 match any interface tenGigabitEthernet 0/0/2 in
Mcast_SR#monitor capture msr start
Started capture point : msr
*Oct 16 17:59:06.986: %BUFCAP-6-ENABLE: Capture Point msr enabled.
Mcast_SR#monitor capture msr stop
Stopped capture point : msr
Mcast_SR#s
*Oct 16 17:59:25.699: %BUFCAP-6-DISABLE: Capture Point msr disabled
Mcast_SR#show monitor capture msr buffer brief
----------------------------------------------------------------------------
# size timestamp source destination dscp protocol
----------------------------------------------------------------------------
0 114 0.000000 192.168.0.2 -> 239.5.5.5 0 BE ICMP
1 114 2.000000 192.168.0.2 -> 239.5.5.5 0 BE ICMP
2 68 2.979961 192.168.0.5 -> 224.0.0.13 48 CS6 PIM
3 114 4.000000 192.168.0.2 -> 239.5.5.5 0 BE ICMP
4 114 6.000000 192.168.0.2 -> 239.5.5.5 0 BE ICMP
5 114 8.000000 192.168.0.2 -> 239.5.5.5 0 BE ICMP
6 114 10.000000 192.168.0.2 -> 239.5.5.5 0 BE ICMP
7 114 12.000000 192.168.0.2 -> 239.5.5.5 0 BE ICMP
8 114 14.001007 192.168.0.2 -> 239.5.5.5 0 BE ICMP
9 114 16.001999 192.168.0.2 -> 239.5.5.5 0 BE ICMP
10 114 18.001007 192.168.0.2 -> 239.5.5.5 0 BE ICMP
Mcast_SR#monitor capture msr buffer size 10 match any interface tenGigabitEthernet0/0/5 out
Mcast_SR#monitor capture msr start
Started capture point : msr
*Oct 16 18:07:26.846: %BUFCAP-6-ENABLE: Capture Point msr enabled.
Mcast_SR#monitor capture msr stop
Stopped capture point : msr
*Oct 16 18:07:50.360: %BUFCAP-6-DISABLE: Capture Point msr disabled.
Mcast_SR#show monitor capture msr buffer brief
----------------------------------------------------------------------------
# size timestamp source destination dscp protocol
----------------------------------------------------------------------------
0 73 0.000000 172.16.0.1 -> 172.16.0.2 48 CS6 TCP
1 114 0.172040 172.16.101.2 -> 239.55.55.55 0 BE ICMP 2 114 2.173047 172.16.101.2 -> 239.55.55.55 0 BE ICMP
3 114 4.172040 172.16.101.2 -> 239.55.55.55 0 BE ICMP
4 114 6.173047 172.16.101.2 -> 239.55.55.55 0 BE ICMP
5 114 8.172040 172.16.101.2 -> 239.55.55.55 0 BE ICMP
6 114 10.172040 172.16.101.2 -> 239.55.55.55 0 BE ICMP
7 114 12.173047 172.16.101.2 -> 239.55.55.55 0 BE ICMP
8 114 14.175046 172.16.101.2 -> 239.55.55.55 0 BE ICMP
9 114 16.176038 172.16.101.2 -> 239.55.55.55 0 BE ICMP
10 114 18.176038 172.16.101.2 -> 239.55.55.55 0 BE ICMP
11 46 19.318029 172.16.0.1 -> 224.0.0.1 48 CS6 IGMP
12 114 20.177045 172.16.101.2 -> 239.55.55.55 0 BE ICMP
13 72 20.629017 172.16.0.1 -> 224.0.0.13 48 CS6 PIM
14 114 22.178037 172.16.101.2 -> 239.55.55.55 0 BE ICMP
15 430 23.273033 90:77:EE:3C:80:05 -> 01:00:0C:CC:CC:CC -- LLCTambién se implementó un rastreo de paquetes con una lista de control de acceso (ACL) de filtrado ampliada en 239.5.5.5. A partir de la siguiente salida, se puede observar que los paquetes se están recibiendo en la interfaz Te0/0/2 y se consumen inicialmente y se copian internamente para utilizarse posteriormente como paquetes de entrada en la interfaz Vif1 y luego se reenvían traducidos a través de la interfaz Te0/0/5:
Mcast_SR#configure terminal Enter configuration commands, one per line. End with CNTL/Z. Mcast_SR(config)#ip access-list extended original-mcast Mcast_SR(config-ext-nacl)#permit ip any host 239.5.5.5 Mcast_SR(config-ext-nacl)#end Mcast_SR# *Oct 16 18:31:49.187: %SYS-5-CONFIG_I: Configured from console by console Mcast_SR#debug platform packet-trace packet 16 Please remember to turn on 'debug platform condition start' for packet-trace to work Mcast_SR#debug platform condition ipv4 access-list original-mcast ingress Mcast_SR#debug platform condition start Mcast_SR#show platform packet-trace packet all Packet: 0 CBUG ID: 0 Summary Input : TenGigabitEthernet0/0/2 Output :State : CONS Packet Consumed Silently Timestamp Start : 521286121898055 ns (10/16/2023 18:33:39.36879 UTC) Stop : 521286122522268 ns (10/16/2023 18:33:39.37503 UTC) Path Trace Feature: IPV4(Input) Input : TenGigabitEthernet0/0/2 Output : Source : 192.168.0.2 Destination : 239.5.5.5 Protocol : 1 (ICMP) Packet: 1 CBUG ID: 0 Summary Input : TenGigabitEthernet0/0/2 Output : State : CONS Packet Consumed Silently Timestamp Start : 521286121980895 ns (10/16/2023 18:33:39.36962 UTC) Stop : 521286122618968 ns (10/16/2023 18:33:39.37600 UTC) Path Trace Feature: PACKET_COPY Original packet number: 0 Feature: IPV4(Input) Input : TenGigabitEthernet0/0/2 Output : Source : 192.168.0.2 Destination : 239.5.5.5 Protocol : 1 (ICMP) Packet: 2 CBUG ID: 0 Summary Input : Vif1 Output : TenGigabitEthernet0/0/5 State : FWD Timestamp Start : 521286122038938 ns (10/16/2023 18:33:39.37020 UTC) Stop : 521286122694795 ns (10/16/2023 18:33:39.37676 UTC) Path Trace Feature: PACKET_COPY Original packet number: 1 Feature: IPV4(Input) Input : Vif1 Output : Source : 172.16.101.2 Destination : 239.55.55.55 Protocol : 1 (ICMP)
También es importante verificar la Base de información de ruteo de multidifusión (MRIB) y la Base de información de reenvío de multidifusión (MFIB) en el Catalyst 8K. Observe los indicadores de hardware instalado (HW), así como los contadores de reenvío de hardware que aumentan con muy pocos errores o caídas de Reverse Path Forwarding (RPF) observados. Observe también el indicador de reenvío (F) asociado a la interfaz de salida (Te0/0/5) hacia el router ASR1000:
Mcast_SR#show ip mrib route IP Multicast Routing Information Base Entry flags: L - Domain-Local Source, E - External Source to the Domain, C - Directly-Connected Check, S - Signal, IA - Inherit Accept, D - Drop ET - Data Rate Exceeds Threshold,K - Keepalive,DDE - Data Driven Event ME - MoFRR ECMP Flow based, MNE - MoFRR Non-ECMP Flow based, MP - Primary MoFRR Non-ECMP Flow based entry, e - Encap helper tunnel flag Interface flags: F - Forward, A - Accept, IC - Internal Copy, NS - Negate Signal, DP - Don't Preserve, SP - Signal Present, II - Internal Interest, ID - Internal Disinterest, LI - Local Interest, LD - Local Disinterest, MD - mCAC Denied, MI - mLDP Interest A2 - MoFRR ECMP Backup Accept (*,224.0.0.0/4) Flags: C (*,224.0.1.40) RPF nbr: 0.0.0.0 Flags: C TenGigabitEthernet0/0/2 Flags: F NS TenGigabitEthernet0/0/5 Flags: F NS Loopback0 Flags: F IC NS Tunnel1 Flags: A (*,239.5.5.5) RPF nbr: 0.0.0.0 Flags: C Vif1 Flags: F NS SR(172.16.101.2, 239.55.55.55) Index(2, 2) Tunnel1 Flags: A (*,239.55.55.55) RPF nbr: 0.0.0.0 Flags: C TenGigabitEthernet0/0/5 Flags: F NS Tunnel1 Flags: A (172.16.101.2,239.55.55.55) RPF nbr: 0.0.0.0 Flags: Vif1 Flags: A TenGigabitEthernet0/0/5 Flags: F NS (192.168.0.2,239.5.5.5) RPF nbr: 192.168.0.5 Flags: TenGigabitEthernet0/0/2 Flags: A NS Vif1 Flags: F NS SR(172.16.101.2, 239.55.55.55) Index(2, 2) Mcast_SR#show ip mfib 192.168.0.2 239.5.5.5 Entry Flags: C - Directly Connected, S - Signal, IA - Inherit A flag, ET - Data Rate Exceeds Threshold, K - Keepalive DDE - Data Driven Event, HW - Hardware Installed ME - MoFRR ECMP entry, MNE - MoFRR Non-ECMP entry, MP - MFIB MoFRR Primary, RP - MRIB MoFRR Primary, P - MoFRR Primary MS - MoFRR Entry in Sync, MC - MoFRR entry in MoFRR Client, e - Encap helper tunnel flag. I/O Item Flags: IC - Internal Copy, NP - Not platform switched, NS - Negate Signalling, SP - Signal Present, A - Accept, F - Forward, RA - MRIB Accept, RF - MRIB Forward, MA - MFIB Accept, A2 - Accept backup, RA2 - MRIB Accept backup, MA2 - MFIB Accept backup Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kbits per second Other counts: Total/RPF failed/Other drops I/O Item Counts: HW Pkt Count/FS Pkt Count/PS Pkt Count Egress Rate in pps Default (192.168.0.2,239.5.5.5) Flags: HW SW Forwarding: 1/0/100/0, Other: 0/0/0 HW Forwarding: 6530/0/114/0, Other: 2/2/0 TenGigabitEthernet0/0/2 Flags: A Vif1, SR/(172.16.101.2,239.55.55.55):553648130 Flags: F NS Pkts: 0/0/1 Rate: 0 pps Mcast_SR#show ip mfib 172.16.101.2 239.55.55.55 Entry Flags: C - Directly Connected, S - Signal, IA - Inherit A flag, ET - Data Rate Exceeds Threshold, K - Keepalive DDE - Data Driven Event, HW - Hardware Installed ME - MoFRR ECMP entry, MNE - MoFRR Non-ECMP entry, MP - MFIB MoFRR Primary, RP - MRIB MoFRR Primary, P - MoFRR Primary MS - MoFRR Entry in Sync, MC - MoFRR entry in MoFRR Client, e - Encap helper tunnel flag. I/O Item Flags: IC - Internal Copy, NP - Not platform switched, NS - Negate Signalling, SP - Signal Present, A - Accept, F - Forward, RA - MRIB Accept, RF - MRIB Forward, MA - MFIB Accept, A2 - Accept backup, RA2 - MRIB Accept backup, MA2 - MFIB Accept backup Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kbits per second Other counts: Total/RPF failed/Other drops I/O Item Counts: HW Pkt Count/FS Pkt Count/PS Pkt Count Egress Rate in pps Default (172.16.101.2,239.55.55.55) Flags: HW SW Forwarding: 0/0/0/0, Other: 0/0/0 HW Forwarding: 6550/0/114/0, Other: 0/0/0 Vif1 Flags: A TenGigabitEthernet0/0/5 Flags: F NS Pkts: 0/0/0 Rate: 0 pps Mcast_SR#show adjacency vif1 detail Protocol Interface Address IP Vif1 point2point(8) 13270 packets, 657502 bytes epoch 0 sourced in sev-epoch 0 empty encap string P2P-ADJMcast_SR#show platform software ip rp active mfib group 239.5.5.5/32 Route flags: S - Signal; C - Directly connected; IA - Inherit A Flag; L - Local; BR - Bidir route *, 239.5.5.5/32 --> OBJ_INTF_LIST (0x15) Obj id: 0x15, Flags: C OM handle: 0x3480200a50 Mcast_SR#show platform software ip rp active mfib group 239.55.55.55/32 Route flags: S - Signal; C - Directly connected; IA - Inherit A Flag; L - Local; BR - Bidir route *, 239.55.55.55/32 --> OBJ_INTF_LIST (0x36) Obj id: 0x36, Flags: C OM handle: 0x34801fa988 Mcast_SR#show platform software mlist rp active index 0x15 Multicast List entries OCE Flags: NS - Negate Signalling; IC - Internal copy; A - Accept; F - Forward; OCE Type OCE Flags Interface -------------------------------------------------------------------------------------- 0xf8000029 OBJ_ADJACENCY NS, F Vif1 0xf8000186 OBJ_ADJACENCY A Tunnel1 Mcast_SR#show platform software mlist rp active index 0x36 Multicast List entries OCE Flags: NS - Negate Signalling; IC - Internal copy; A - Accept; F - Forward; OCE Type OCE Flags Interface -------------------------------------------------------------------------------------- 0xf80000d1 OBJ_ADJACENCY NS, F TenGigabitEthernet0/0/5 0xf8000186 OBJ_ADJACENCY A Tunnel1
Para la verificación RPF, es importante verificar esto a través de los diferentes dispositivos en el trayecto multicast.
C9000#show ip rpf 192.168.0.2
RPF information for ? (192.168.0.2)
RPF interface: TenGigabitEthernet1/0/6
RPF neighbor: ? (192.168.0.2) - directly connected
RPF route/mask: 192.168.0.0/30
RPF type: multicast (connected)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base
Mcast_SR#show ip rpf 192.168.0.2
RPF information for ? (192.168.0.2)
RPF interface: TenGigabitEthernet0/0/2
RPF neighbor: ? (192.168.0.5)
RPF route/mask: 192.168.0.0/30
RPF type: unicast (bgp 65001)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast base
Mcast_SR#show ip rpf 172.16.101.2
RPF information for ? (172.16.101.2)
RPF interface: Vif1
RPF neighbor: ? (172.16.101.2) - directly connected
RPF route/mask: 172.16.101.0/30
RPF type: multicast (connected)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base
ASR1000#show ip rpf 172.16.101.2
RPF information for ? (172.16.101.2)
RPF interface: TenGigabitEthernet0/1/1
RPF neighbor: ? (172.16.0.1)
RPF route/mask: 172.16.101.0/30
RPF type: unicast (bgp 65002)
Doing distance-preferred lookups across tables
RPF topology: ipv4 multicast base, originated from ipv4 unicast baseFinalmente, puede confirmar el tráfico que se recibe y reenvía en el LHR; la primera captura muestra cómo ASR1000 recibió los paquetes del nuevo flujo (172.16.101.2, 239.55.55.55) donde las direcciones IPv4 se tradujeron según lo esperado. La segunda captura muestra el tráfico que se reenvía al receptor.
ASR1000#monitor capture LHR buffer size 10 match any interface TenGigabitEthernet 0/1/1 in
ASR1000#monitor capture LHR start
Started capture point : LHR
*Oct 17 15:16:06.192: %BUFCAP-6-ENABLE: Capture Point LHR enabled.show moni
ASR1000#show monitor capture LHR buffer brief
----------------------------------------------------------------------------
# size timestamp source destination dscp protocol
----------------------------------------------------------------------------
0 73 0.000000 172.16.0.1 -> 172.16.0.2 48 CS6 TCP
1 114 0.050992 172.16.101.2 -> 239.55.55.55 0 BE ICMP 2 114 2.051984 172.16.101.2 -> 239.55.55.55 0 BE ICMP
3 54 2.896993 172.16.0.1 -> 172.16.0.2 48 CS6 TCP
4 114 4.051984 172.16.101.2 -> 239.55.55.55 0 BE ICMP
5 72 4.967989 172.16.0.1 -> 224.0.0.13 48 CS6 PIM
6 114 6.052991 172.16.101.2 -> 239.55.55.55 0 BE ICMP
7 114 8.053983 172.16.101.2 -> 239.55.55.55 0 BE ICMP
8 114 10.053983 172.16.101.2 -> 239.55.55.55 0 BE ICMP
9 114 12.053983 172.16.101.2 -> 239.55.55.55 0 BE ICMP
10 114 14.055997 172.16.101.2 -> 239.55.55.55 0 BE ICMP
11 114 16.056989 172.16.101.2 -> 239.55.55.55 0 BE ICMP
12 114 18.055997 172.16.101.2 -> 239.55.55.55 0 BE ICMP
ASR1000#monitor capture LHR stop
Stopped capture point : LHR
ASR1000#
*Oct 17 15:16:32.029: %BUFCAP-6-DISABLE: Capture Point LHR disabled.
ASR1000#monitor capture TO_RECEIVER buffer size 10 match any interface GigabitEthernet 0/0/0 out
ASR1000#monitor capture TO_RECEIVER start
Started capture point : TO_RECEIVER
*Oct 17 15:19:00.309: %BUFCAP-6-ENABLE: Capture Point TO_RECEIVER enabled.ni
ASR1000#show monitor capture TO_RECEIVER buffer brief
----------------------------------------------------------------------------
# size timestamp source destination dscp protocol
----------------------------------------------------------------------------
0 114 0.000000 172.16.101.2 -> 239.55.55.55 0 BE ICMP
1 46 0.276994 172.16.0.5 -> 224.0.0.1 48 CS6 IGMP
2 114 1.999009 172.16.101.2 -> 239.55.55.55 0 BE ICMP 3 114 4.000000 172.16.101.2 -> 239.55.55.55 0 BE ICMP
4 46 5.550027 172.16.0.5 -> 224.0.1.40 48 CS6 IGMP
5 114 5.999009 172.16.101.2 -> 239.55.55.55 0 BE ICMP
6 114 8.000000 172.16.101.2 -> 239.55.55.55 0 BE ICMP
7 114 10.001007 172.16.101.2 -> 239.55.55.55 0 BE ICMP
8 114 12.001999 172.16.101.2 -> 239.55.55.55 0 BE ICMP
9 114 14.003006 172.16.101.2 -> 239.55.55.55 0 BE ICMP
10 114 16.003998 172.16.101.2 -> 239.55.55.55 0 BE ICMP
ASR1000#monitor capture TO_RECEIVER stop
Stopped capture point : TO_RECEIVER
*Oct 17 15:19:24.938: %BUFCAP-6-DISABLE: Capture Point TO_RECEIVER disabled. Si por alguna razón falta *,G en algún momento, puede validar el estado del Protocolo de administración de grupos de Internet (IGMP) con los comandos show ip igmp membership <group> y show ip igmp groups <group>. En este escenario, se espera que vea una entrada para el grupo multicast traducido 239.55.55.55.
ASR1000#show ip igmp membership 239.55.55.55
Flags: A - aggregate, T - tracked
L - Local, S - static, V - virtual, R - Reported through v3
I - v3lite, U - Urd, M - SSM (S,G) channel
1,2,3 - The version of IGMP, the group is in
Channel/Group-Flags:
/ - Filtering entry (Exclude mode (S,G), Include mode (G))
Reporter:
- last reporter if group is not explicitly tracked
/
-
reporter in include mode,
reporter in exclude Channel/Group Reporter Uptime Exp. Flags Interface
*,239.55.55.55 172.16.0.6 1w0d 02:40 2A Gi0/0/0
ASR1000#show ip igmp groups 239.55.55.55 IGMP Connected Group Membership Group Address Interface Uptime Expires Last Reporter Group Accounted 239.55.55.55 GigabitEthernet0/0/0 01:11:56 00:02:49 172.16.0.6
Además, en el LHR se puede utilizar una verificación de la ruta multicast para confirmar que la interfaz hacia el Receptor se agrega al OIL y el uso de un mtrace para confirmar la trayectoria inversa hacia ambas fuentes.
ASR1000#show ip mroute 239.55.55.55
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group, c - PFP-SA cache created entry,
* - determined by Assert, # - iif-starg configured on rpf intf,
e - encap-helper tunnel flag, l - LISP Decap Refcnt Contributor
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode
(*, 239.55.55.55), 23:28:12/stopped, RP 10.100.100.1, flags: SJC
Incoming interface: TenGigabitEthernet0/1/1, RPF nbr 172.16.0.1
Outgoing interface list:
GigabitEthernet0/0/0, Forward/Sparse, 00:01:52/00:02:48
(172.16.101.2, 239.55.55.55), 00:10:11/00:02:40, flags: JT
Incoming interface: TenGigabitEthernet0/1/1, RPF nbr 172.16.0.1
Outgoing interface list:
GigabitEthernet0/0/0, Forward/Sparse, 00:01:52/00:02:48
ASR1000#mtrace 172.16.101.2 Type escape sequence to abort. Mtrace from 172.16.101.2 to 172.16.0.2 via RPF From source (?) to destination (?) Querying full reverse path... 0 172.16.0.2 -1 172.16.0.2 ==> 172.16.0.2 PIM/MBGP [172.16.101.0/30] -2 172.16.0.1 ==> 172.16.101.1 PIM_MT [172.16.101.0/30] -3 172.16.101.2
ASR1000#mtrace 192.168.0.2 Type escape sequence to abort. Mtrace from 192.168.0.2 to 172.16.0.2 via RPF From source (?) to destination (?) Querying full reverse path... 0 172.16.0.2 -1 172.16.0.2 ==> 172.16.0.2 PIM/MBGP [192.168.0.0/30] -2 172.16.0.1 ==> 192.168.0.6 PIM/MBGP [192.168.0.0/30] -3 192.168.0.5 ==> 192.168.0.1 PIM_MT [192.168.0.0/30] -4 192.168.0.2Información Relacionada
Historial de revisiones
| Revisión | Fecha de publicación | Comentarios |
|---|---|---|
1.0 |
20-Oct-2023 |
Versión inicial |
Comentarios