Ejemplo: Configuración de RPF basada en remitentes en una MVPN de BGP con túneles de proveedor punto a multipunto MLDP
En este ejemplo, se muestra cómo configurar el reenvío de ruta inversa basado en remitentes (RPF) en una VPN de multidifusión BGP (MVPN). El RPF basado en el remitente ayuda a evitar que varios enrutadores de borde de proveedor (PE) envíen tráfico al núcleo, evitando así que se envíe tráfico duplicado a un cliente.
Requisitos
No se necesita ninguna configuración especial más allá de la inicialización del dispositivo antes de configurar este ejemplo.
El RPF basado en remitentes solo se admite para MVPN de BGP de MPLS con túneles de proveedor punto a multipunto RSVP-TE. Se admiten los modos MVPN de solo SPT y SPT-RPT.
El RPF basado en el remitente no funciona cuando se utilizan túneles de proveedor punto a multipunto con interfaces conmutadas por etiquetas (LSI). Junos OS solo asigna una única etiqueta LSI para cada VRF y utiliza esta etiqueta para todos los túneles punto a multipunto. Por lo tanto, la etiqueta que recibe la salida no indica el enrutador de PE de envío. Actualmente, las etiquetas LSI no se pueden escalar para crear una etiqueta única para cada túnel punto a multipunto. Como tal, se deben usar interfaces de túnel virtual (vt) para la funcionalidad de RPF basada en el remitente con túneles de proveedor punto a multipunto.
Este ejemplo requiere la versión 21.1R1 o posterior de Junos OS en el enrutador de PE que tenga habilitado el RPF basado en remitentes.
Descripción general
En este ejemplo se muestra un único sistema autónomo (escenario intra-AS) en el que un origen envía tráfico de multidifusión (grupo 224.1.1.1) a la VPN (instancia de VRF vpn-1). Dos receptores se suscriben al grupo. Están conectados al dispositivo CE2 y al dispositivo CE3, respectivamente. Los LSP de punto a multipunto MLDP con túneles de proveedor inclusivos se configuran entre los enrutadores de PE. PIM (C-PIM) está configurado en los vínculos PE-CE.
Para MPLS, el protocolo de control de señalización que se usa aquí es LDP. De manera opcional, puede usar RSVP para señalar túneles punto a punto y punto a punto.
OSPF se usa para la conectividad del protocolo de puerta de enlace interior (IGP), aunque SI-SI también es una opción compatible. Si utiliza OSPF, debe habilitar la ingeniería de tráfico de OSPF.
Para fines de prueba, los enrutadores se utilizan para simular el origen y los receptores. Los dispositivos PE2 y PE3 se configuran para unirse estáticamente al grupo 224.1.1.1 mediante el set protocols igmp interface interface-name static group 224.1.1.1 comando. En el caso de que no se disponga de un host receptor de multidifusión real, como en este ejemplo, esta configuración IGMP estática es útil. En los dispositivos CE conectados a los receptores, para hacer que escuchen la dirección del grupo de multidifusión, el ejemplo utiliza set protocols sap listen 224.1.1.1. Se utiliza un comando ping para enviar tráfico de multidifusión al MBPN del BGP.
La RPF basada en el remitente está habilitada en el dispositivo PE2, de la siguiente manera:
[routing-instances vpn-1 protocols mvpn] user@PE2# set sender-based-rpf
Si lo desea, puede configurar hot-root-standby con sender-based-rpf.
Topología
La Figura 1 muestra la red de ejemplo.
Figura 1: RPF basado en remitentes en una MVPN
de BGP
de BGP
Establecer comandos para todos los dispositivos en la topología muestra la configuración de todos los dispositivos de la Figura 1.
En la sección Configuración del dispositivo PE2 se describen los pasos para el dispositivo PE2.
Establecer comandos para todos los dispositivos de la topología
Configuración rápida de CLI
Para configurar rápidamente este ejemplo, copie los siguientes comandos, péguelos en un archivo de texto, elimine los saltos de línea, cambie los detalles necesarios para que coincidan con su configuración de red y, luego, copie y pegue los comandos en la CLI en el nivel jerárquico [edit] .
Dispositivo CE1
set interfaces ge-1/2/10 unit 0 family inet address 10.1.1.1/30 set interfaces ge-1/2/10 unit 0 family mpls set interfaces lo0 unit 0 family inet address 10.1.1.1/32 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-1/2/10.0 set protocols pim rp static address 10.100.1.2 set protocols pim interface all set routing-options router-id 10.1.1.1
Dispositivo CE2
set interfaces ge-1/2/14 unit 0 family inet address 10.1.1.18/30 set interfaces ge-1/2/14 unit 0 family mpls set interfaces lo0 unit 0 family inet address 10.1.1.6/32 set protocols sap listen 224.1.1.1 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-1/2/14.0 set protocols pim rp static address 10.100.1.2 set protocols pim interface all set routing-options router-id 10.1.1.6
Dispositivo CE3
set interfaces ge-1/2/15 unit 0 family inet address 10.1.1.22/30 set interfaces ge-1/2/15 unit 0 family mpls set interfaces lo0 unit 0 family inet address 10.1.1.7/32 set protocols sap listen 224.1.1.1 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-1/2/15.0 set protocols pim rp static address 10.100.1.2 set protocols pim interface all set routing-options router-id 10.1.1.7
Dispositivo P
set interfaces ge-1/2/11 unit 0 family inet address 10.1.1.6/30 set interfaces ge-1/2/11 unit 0 family mpls set interfaces ge-1/2/12 unit 0 family inet address 10.1.1.9/30 set interfaces ge-1/2/12 unit 0 family mpls set interfaces ge-1/2/13 unit 0 family inet address 10.1.1.13/30 set interfaces ge-1/2/13 unit 0 family mpls set interfaces lo0 unit 0 family inet address 10.1.1.3/32 set protocols rsvp interface all set protocols mpls traffic-engineering bgp-igp-both-ribs set protocols mpls interface ge-1/2/11.0 set protocols mpls interface ge-1/2/12.0 set protocols mpls interface ge-1/2/13.0 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-1/2/11.0 set protocols ospf area 0.0.0.0 interface ge-1/2/12.0 set protocols ospf area 0.0.0.0 interface ge-1/2/13.0 set protocols ldp interface ge-1/2/11.0 set protocols ldp interface ge-1/2/12.0 set protocols ldp interface ge-1/2/13.0 set protocols ldp p2mp set routing-options router-id 10.1.1.3
Dispositivo PE1
set interfaces ge-1/2/10 unit 0 family inet address 10.1.1.2/30 set interfaces ge-1/2/10 unit 0 family mpls set interfaces ge-1/2/11 unit 0 family inet address 10.1.1.5/30 set interfaces ge-1/2/11 unit 0 family mpls set interfaces vt-1/2/10 unit 2 family inet set interfaces lo0 unit 0 family inet address 10.1.1.2/32 set interfaces lo0 unit 102 family inet address 10.100.1.2/32 set protocols rsvp interface ge-1/2/11.0 set protocols mpls traffic-engineering bgp-igp-both-ribs set protocols mpls label-switched-path p2mp-template template set protocols mpls label-switched-path p2mp-template p2mp set protocols mpls interface ge-1/2/11.0 set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 10.1.1.2 set protocols bgp group ibgp family inet unicast set protocols bgp group ibgp family inet-vpn any set protocols bgp group ibgp family inet-mvpn signaling set protocols bgp group ibgp neighbor 10.1.1.4 set protocols bgp group ibgp neighbor 10.1.1.5 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-1/2/11.0 set protocols ldp interface ge-1/2/11.0 set protocols ldp p2mp set policy-options policy-statement parent_vpn_routes from protocol bgp set policy-options policy-statement parent_vpn_routes then accept set routing-instances vpn-1 instance-type vrf set routing-instances vpn-1 interface ge-1/2/10.0 set routing-instances vpn-1 interface vt-1/2/10.2 set routing-instances vpn-1 interface lo0.102 set routing-instances vpn-1 provider-tunnel ldp-p2mp set routing-instances vpn-1 provider-tunnel selective group 225.0.1.0/24 source 0.0.0.0/0 ldp-p2mp set routing-instances vpn-1 provider-tunnel selective group 225.0.1.0/24 source 0.0.0.0/0 threshold-rate 0 set routing-instances vpn-1 vrf-target target:100:10 set routing-instances vpn-1 protocols ospf export parent_vpn_routes set routing-instances vpn-1 protocols ospf area 0.0.0.0 interface lo0.102 passive set routing-instances vpn-1 protocols ospf area 0.0.0.0 interface ge-1/2/10.0 set routing-instances vpn-1 protocols pim rp local address 10.100.1.2 set routing-instances vpn-1 protocols pim interface ge-1/2/10.0 mode sparse set routing-instances vpn-1 protocols mvpn mvpn-mode rpt-spt set routing-options router-id 10.1.1.2 set routing-options route-distinguisher-id 10.1.1.2 set routing-options autonomous-system 65001
Dispositivo PE2
set interfaces ge-1/2/12 unit 0 family inet address 10.1.1.10/30 set interfaces ge-1/2/12 unit 0 family mpls set interfaces ge-1/2/14 unit 0 family inet address 10.1.1.17/30 set interfaces ge-1/2/14 unit 0 family mpls set interfaces vt-1/2/10 unit 4 family inet set interfaces lo0 unit 0 family inet address 10.1.1.4/32 set interfaces lo0 unit 104 family inet address 10.100.1.4/32 set protocols igmp interface ge-1/2/14.0 static group 224.1.1.1 set protocols rsvp interface ge-1/2/12.0 set protocols mpls traffic-engineering bgp-igp-both-ribs set protocols mpls label-switched-path p2mp-template template set protocols mpls label-switched-path p2mp-template p2mp set protocols mpls interface ge-1/2/12.0 set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 10.1.1.4 set protocols bgp group ibgp family inet unicast set protocols bgp group ibgp family inet-vpn any set protocols bgp group ibgp family inet-mvpn signaling set protocols bgp group ibgp neighbor 10.1.1.2 set protocols bgp group ibgp neighbor 10.1.1.5 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-1/2/12.0 set protocols ldp interface ge-1/2/12.0 set protocols ldp p2mp set policy-options policy-statement parent_vpn_routes from protocol bgp set policy-options policy-statement parent_vpn_routes then accept set routing-instances vpn-1 instance-type vrf set routing-instances vpn-1 interface vt-1/2/10.4 set routing-instances vpn-1 interface ge-1/2/14.0 set routing-instances vpn-1 interface lo0.104 set routing-instances vpn-1 provider-tunnel ldp-p2mp set routing-instances vpn-1 provider-tunnel selective group 225.0.1.0/24 source 0.0.0.0/0 ldp-p2mp set routing-instances vpn-1 provider-tunnel selective group 225.0.1.0/24 source 0.0.0.0/0 threshold-rate 0 set routing-instances vpn-1 vrf-target target:100:10 set routing-instances vpn-1 protocols ospf export parent_vpn_routes set routing-instances vpn-1 protocols ospf area 0.0.0.0 interface lo0.104 passive set routing-instances vpn-1 protocols ospf area 0.0.0.0 interface ge-1/2/14.0 set routing-instances vpn-1 protocols pim rp static address 10.100.1.2 set routing-instances vpn-1 protocols pim interface ge-1/2/14.0 mode sparse set routing-instances vpn-1 protocols mvpn mvpn-mode rpt-spt set routing-instances vpn-1 protocols mvpn sender-based-rpf set routing-instances vpn-1 protocols mvpn hot-root-standby source-tree set routing-options router-id 10.1.1.4 set routing-options route-distinguisher-id 10.1.1.4 set routing-options autonomous-system 65001
Dispositivo PE3
set interfaces ge-1/2/13 unit 0 family inet address 10.1.1.14/30 set interfaces ge-1/2/13 unit 0 family mpls set interfaces ge-1/2/15 unit 0 family inet address 10.1.1.21/30 set interfaces ge-1/2/15 unit 0 family mpls set interfaces vt-1/2/10 unit 5 family inet set interfaces lo0 unit 0 family inet address 10.1.1.5/32 set interfaces lo0 unit 105 family inet address 10.100.1.5/32 set protocols igmp interface ge-1/2/15.0 static group 224.1.1.1 set protocols rsvp interface ge-1/2/13.0 set protocols mpls traffic-engineering bgp-igp-both-ribs set protocols mpls label-switched-path p2mp-template template set protocols mpls label-switched-path p2mp-template p2mp set protocols mpls interface ge-1/2/13.0 set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 10.1.1.5 set protocols bgp group ibgp family inet unicast set protocols bgp group ibgp family inet-vpn any set protocols bgp group ibgp family inet-mvpn signaling set protocols bgp group ibgp neighbor 10.1.1.2 set protocols bgp group ibgp neighbor 10.1.1.4 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-1/2/13.0 set protocols ldp interface ge-1/2/13.0 set protocols ldp p2mp set policy-options policy-statement parent_vpn_routes from protocol bgp set policy-options policy-statement parent_vpn_routes then accept set routing-instances vpn-1 instance-type vrf set routing-instances vpn-1 interface vt-1/2/10.5 set routing-instances vpn-1 interface ge-1/2/15.0 set routing-instances vpn-1 interface lo0.105 set routing-instances vpn-1 provider-tunnel ldp-p2mp set routing-instances vpn-1 provider-tunnel selective group 225.0.1.0/24 source 0.0.0.0/0 set routing-instances vpn-1 provider-tunnel selective group 225.0.1.0/24 source 0.0.0.0/0 threshold-rate 0 set routing-instances vpn-1 vrf-target target:100:10 set routing-instances vpn-1 protocols ospf export parent_vpn_routes set routing-instances vpn-1 protocols ospf area 0.0.0.0 interface lo0.105 passive set routing-instances vpn-1 protocols ospf area 0.0.0.0 interface ge-1/2/15.0 set routing-instances vpn-1 protocols pim rp static address 10.100.1.2 set routing-instances vpn-1 protocols pim interface ge-1/2/15.0 mode sparse set routing-instances vpn-1 protocols mvpn mvpn-mode rpt-spt set routing-options router-id 10.1.1.5 set routing-options route-distinguisher-id 10.1.1.5 set routing-options autonomous-system 65001
Procedimiento
Procedimiento paso a paso
Configuración del dispositivo PE2
Procedimiento
Procedimiento paso a paso
En el ejemplo siguiente, debe explorar por varios niveles en la jerarquía de configuración. Para obtener más información acerca de cómo navegar por la CLI, consulte Uso del editor de CLI en el modo de configuración de la Guía del usuario de la CLI de Junos OS.
Para configurar el dispositivo PE2:
-
Habilite el modo IP mejorado.
[edit chassis] user@PE2# set network-services enhanced-ip
-
Configure las interfaces de los dispositivos.
[edit interfaces] user@PE2# set ge-1/2/12 unit 0 family inet address 10.1.1.10/30 user@PE2# set ge-1/2/12 unit 0 family mpls user@PE2# set ge-1/2/14 unit 0 family inet address 10.1.1.17/30 user@PE2# set ge-1/2/14 unit 0 family mpls user@PE2# set vt-1/2/10 unit 4 family inet user@PE2# set lo0 unit 0 family inet address 10.1.1.4/32 user@PE2# set lo0 unit 104 family inet address 10.100.1.4/32
-
Configure IGMP en la interfaz orientada hacia el borde del cliente.
[edit protocols igmp] user@PE2# set interface ge-1/2/14.0
-
(Opcional) Forzar al dispositivo PE para que se una al grupo de multidifusión con una configuración estática.
Normalmente, esto sucedería dinámicamente en una configuración con fuentes y receptores reales.
[edit protocols igmp] user@PE2# set interface ge-1/2/14.0 static group 224.1.1.1
-
Configure RSVP en las interfaces que se dirigen al núcleo del proveedor.
[edit protocols rsvp] user@PE2# set interface ge-1/2/0.10
-
Configure MPLS.
[edit protocols mpls] user@PE2# set traffic-engineering bgp-igp-both-ribs user@PE2# set label-switched-path p2mp-template template user@PE2# set label-switched-path p2mp-template p2mp user@PE2# set interface ge-1/2/12.0
-
Configure el BGP interno (IBGP) entre los enrutadores de PE.
[edit protocols bgp group ibgp] user@PE2# set type internal user@PE2# set local-address 10.1.1.4 user@PE2# set family inet unicast user@PE2# set family inet-vpn any user@PE2# set family inet-mvpn signaling user@PE2# set neighbor 10.1.1.2 user@PE2# set neighbor 10.1.1.5
-
Configure un OSPF o SI-SI.
[edit protocols ospf] user@PE2# set traffic-engineering user@PE2# set area 0.0.0.0 interface lo0.0 passive user@PE2# set area 0.0.0.0 interface ge-1/2/12.0
-
(Opcional) Configure LDP.
En su lugar, se puede usar RSVP para la señalización MPLS.
[edit protocols bgp group ibgp] user@PE2# set interface ge-1/2/12.0 user@PE2# set p2mp
-
Configure una política de enrutamiento que se utilizará en la VPN.
La política se utiliza para exportar el BGP a la sesión de IGP PE-CE.
[edit policy-options policy-statement parent_vpn_routes] user@PE2# set from protocol bgp user@PE2# set then accept
-
Configure la instancia de enrutamiento.
[edit routing-instances vpn-1] user@PE2# set instance-type vrf user@PE2# set interface vt-1/2/10.4 user@PE2# set interface ge-1/2/14.0 user@PE2# set interface lo0.104
-
Configure el túnel del proveedor.
[edit routing-instances vpn-1 provider-tunnel] user@PE2# set ldp-p2mp user@PE2# set selective group 225.0.1.0/24 source 0.0.0.0/0 ldp-p2mp user@PE2# set selective group 225.0.1.0/24 source 0.0.0.0/0 threshold-rate 0
-
Configure el destino VRF.
En el contexto de rutas IPv4 de unidifusión, la elección
vrf-targettiene dos implicaciones. En primer lugar, todas las rutas aprendidas localmente (en este caso, directas y estáticas) en el VRF se exportan al BGP con el destino de ruta (RT) especificado. Además, cada ruta BGP inet-vpn recibida con ese valor RT se importa a VRF vpn-1. Esto tiene la ventaja de una configuración más simple y el inconveniente de una menor flexibilidad en la selección y modificación de las rutas exportadas e importadas. También implica que la VPN es de malla completa y que todos los enrutadores de PE obtienen rutas entre sí, por lo que no son factibles configuraciones complejas como hub-and-spoke o extranet. Si se requiere alguna de estas características, es necesario usarlasvrf-importyvrf-exporten su lugar.[edit ] user@PE2# set routing-instances vpn-1 vrf-target target:100:10
-
Configure la sesión OSPF de PE-CE.
[edit routing-instances vpn-1 protocols ospf] user@PE2# set export parent_vpn_routes user@PE2# set area 0.0.0.0 interface lo0.104 passive user@PE2# set area 0.0.0.0 interface ge-1/2/14.0
-
Configure la sesión PE-CE PIM.
[edit routing-instances vpn-1 protocols pim] user@PE2# set rp static address 10.100.1.2 user@PE2# set interface ge-1/2/14.0 mode sparse
-
Habilite el modo MVPN.
Ambos
rpt-sptyspt-onlyson compatibles con RPF basado en remitentes.[edit routing-instances vpn-1 protocols mvpn] user@PE2# set mvpn-mode rpt-spt
-
Habilite RPF basado en senderos.
[edit routing-instances vpn-1 protocols mvpn] user@PE2# set sender-based-rpf
-
Configure el ID del enrutador, el distinguidor de enrutador y el número de AS.
[edit routing-options] user@PE2# set router-id 10.1.1.4 user@PE2# set route-distinguisher-id 10.1.1.4 user@PE2# set autonomous-system 65001
Resultados
Desde el modo de configuración, escriba los comandos , show interfaces, show protocols, show routing-instancesshow policy-optionsy show routing-options para confirmar la show chassisconfiguración. Si el resultado no muestra la configuración deseada, repita las instrucciones de este ejemplo para corregirla.
user@PE2# show chassis network-services enhanced-ip;
user@PE2# show interfaces
ge-1/2/12 {
unit 0 {
family inet {
address 10.1.1.10/30;
}
family mpls;
}
}
ge-1/2/14 {
unit 0 {
family inet {
address 10.1.1.17/30;
}
family mpls;
}
}
vt-1/2/10 {
unit 5 {
family inet;
}
}
lo0 {
unit 0 {
family inet {
address 10.1.1.5/32;
}
}
unit 105 {
family inet {
address 10.100.1.5/32;
}
}
}
user@PE2# show protocols
igmp {
interface ge-1/2/15.0 {
static {
group 224.1.1.1;
}
}
}
rsvp {
interface all;
}
mpls {
traffic-engineering bgp-igp-both-ribs;
label-switched-path p2mp-template {
template;
p2mp;
}
interface ge-1/2/13.0;
}
bgp {
group ibgp {
type internal;
local-address 10.1.1.5;
family inet {
unicast;
}
family inet-vpn {
any;
}
family inet-mvpn {
signaling;
}
neighbor 10.1.1.2;
neighbor 10.1.1.4;
}
}
ospf {
traffic-engineering;
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface ge-1/2/13.0;
}
}
ldp {
interface ge-1/2/13.0;
p2mp;
}
user@PE2# show policy-options
policy-statement parent_vpn_routes {
from protocol bgp;
then accept;
}
user@PE2# show routing-instances
vpn-1 {
instance-type vrf;
interface vt-1/2/10.5;
interface ge-1/2/15.0;
interface lo0.105;
provider-tunnel {
ldp-p2mp;
selective {
group 225.0.1.0/24 {
source 0.0.0.0/0 {
ldp-p2mp;
threshold-rate 0;
}
}
}
vrf-target target:100:10;
protocols {
ospf {
export parent_vpn_routes;
area 0.0.0.0 {
interface lo0.105 {
passive;
}
interface ge-1/2/15.0;
}
}
pim {
rp {
static {
address 10.100.1.2;
}
}
interface ge-1/2/15.0 {
mode sparse;
}
}
mvpn {
mvpn-mode {
rpt-spt;
}
sender-based-rpf;
}
}
}
user@PE2# show routing-options router-id 10.1.1.5; route-distinguisher-id 10.1.1.5; autonomous-system 65001;
Cuando termine de configurar el dispositivo, ingrese commit desde el modo de configuración.
Verificación
Confirme que la configuración funcione correctamente.
- Verificación de RPF basado en remitentes
- Comprobación de las rutas del BGP
- Comprobación de las uniones PIM en los dispositivos receptores de CE descendentes
- Comprobación de las uniones PIM en los dispositivos PE
- Comprobación de las rutas de multidifusión
- Comprobación de las rutas de multidifusión C de MVPN
- Comprobación del PE de origen
- Comportamiento RPF basado en remitentes específicos de la plataforma
Verificación de RPF basado en remitentes
Propósito
Asegúrese de que el RPF basado en el remitente esté habilitado en el dispositivo PE2.
Acción
user@PE2> show mvpn instance vpn-1
MVPN instance:
Legend for provider tunnel
S- Selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g) RM -- remote VPN route
Family : INET
Instance : vpn-1
MVPN Mode : RPT-SPT
Sender-Based RPF: Enabled.
Hot Root Standby: Disabled. Reason: Not enabled by configuration.
Provider tunnel: I-P-tnl:LDP-P2MP:10.1.1.4, lsp-id 16777217
Neighbor Inclusive Provider Tunnel
10.1.1.2 LDP-P2MP:10.1.1.2, lsp-id 16777219
10.1.1.5 LDP-P2MP:10.1.1.5, lsp-id 16777210
C-mcast IPv4 (S:G) Provider Tunnel St
0.0.0.0/0:224.1.1.1/32 LDP-P2MP:10.1.1.2, lsp-id 16777219
0.0.0.0/0:224.2.127.254/32 LDP-P2MP:10.1.1.3, lsp-id 16777210
MVPN instance:
Legend for provider tunnel
S- Selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g) RM -- remote VPN route
Family : INET6
Instance : vpn-1
MVPN Mode : RPT-SPT
Sender-Based RPF: Enabled.
Hot Root Standby: Disabled. Reason: Not enabled by configuration.
Provider tunnel: I-P-tnl:LDP-P2MP:10.1.1.4, lsp-id 16777217
Comprobación de las rutas del BGP
Propósito
Asegúrese de que las rutas esperadas del BGP se agregan a las tablas de enrutamiento en los dispositivos PE.
Acción
user@PE1> show route protocol bgp
inet.0: 10 destinations, 14 routes (10 active, 0 holddown, 0 hidden)
inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
vpn-1.inet.0: 14 destinations, 15 routes (14 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.1.6/32 *[BGP/170] 1d 04:23:24, MED 1, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299792(top)
10.1.1.7/32 *[BGP/170] 1d 04:23:23, MED 1, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299776(top)
10.1.1.16/30 *[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299792(top)
10.1.1.20/30 *[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299776(top)
10.100.1.4/32 *[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299792(top)
10.100.1.5/32 *[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299776(top)
vpn-1.inet.1: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
mpls.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
bgp.l3vpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.1.4:32767:10.1.1.6/32
*[BGP/170] 1d 04:23:24, MED 1, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299792(top)
10.1.1.4:32767:10.1.1.16/30
*[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299792(top)
10.1.1.4:32767:10.100.1.4/32
*[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299792(top)
10.1.1.5:32767:10.1.1.7/32
*[BGP/170] 1d 04:23:23, MED 1, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299776(top)
10.1.1.5:32767:10.1.1.20/30
*[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299776(top)
10.1.1.5:32767:10.100.1.5/32
*[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776, Push 299776(top)
bgp.mvpn.0: 5 destinations, 8 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:10.1.1.4:32767:10.1.1.4/240
*[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299792
1:10.1.1.5:32767:10.1.1.5/240
*[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776
6:10.1.1.2:32767:1001:32:10.100.1.2:32:224.1.1.1/240
*[BGP/170] 1d 04:17:25, MED 0, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776
[BGP/170] 1d 04:17:24, MED 0, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299792
6:10.1.1.2:32767:1001:32:10.100.1.2:32:224.2.127.254/240
*[BGP/170] 1d 04:17:25, MED 0, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776
[BGP/170] 1d 04:17:23, MED 0, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299792
7:10.1.1.2:32767:1001:32:10.1.1.1:32:224.1.1.1/240
*[BGP/170] 20:34:47, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776
[BGP/170] 20:34:47, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299792
vpn-1.mvpn.0: 7 destinations, 13 routes (7 active, 2 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:10.1.1.4:32767:10.1.1.4/240
*[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299792
1:10.1.1.5:32767:10.1.1.5/240
*[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776
6:10.1.1.2:32767:1001:32:10.100.1.2:32:224.1.1.1/240
[BGP/170] 1d 04:17:25, MED 0, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776
[BGP/170] 1d 04:17:24, MED 0, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299792
6:10.1.1.2:32767:1001:32:10.100.1.2:32:224.2.127.254/240
[BGP/170] 1d 04:17:25, MED 0, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776
[BGP/170] 1d 04:17:23, MED 0, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299792
7:10.1.1.2:32767:1001:32:10.10.1.1:32:224.1.1.1/240
[BGP/170] 20:34:47, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299792
[BGP/170] 20:34:47, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/11.0, Push 299776
user@PE2> show route protocol bgp
inet.0: 10 destinations, 14 routes (10 active, 0 holddown, 0 hidden)
inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
vpn-1.inet.0: 14 destinations, 15 routes (14 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.1.1/32 *[BGP/170] 1d 04:23:24, MED 1, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299808(top)
10.1.1.7/32 *[BGP/170] 1d 04:23:20, MED 1, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299776(top)
10.1.1.0/30 *[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299808(top)
10.1.1.20/30 *[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299776(top)
10.100.1.2/32 *[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299808(top)
10.100.1.5/32 *[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299776(top)
vpn-1.inet.1: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
mpls.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
bgp.l3vpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.1.2:32767:10.1.1.1/32
*[BGP/170] 1d 04:23:24, MED 1, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299808(top)
10.1.1.2:32767:10.1.1.0/30
*[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299808(top)
10.1.1.2:32767:10.100.1.2/32
*[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299808(top)
10.1.1.5:32767:10.1.1.7/32
*[BGP/170] 1d 04:23:20, MED 1, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299776(top)
10.1.1.5:32767:10.1.1.20/30
*[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299776(top)
10.1.1.5:32767:10.100.1.5/32
*[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776, Push 299776(top)
bgp.mvpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:10.1.1.2:32767:10.1.1.2/240
*[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299808
1:10.1.1.5:32767:10.1.1.5/240
*[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776
5:10.1.1.2:32767:32:10.1.1.1:32:224.1.1.1/240
*[BGP/170] 20:34:47, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299808
vpn-1.mvpn.0: 7 destinations, 9 routes (7 active, 1 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:10.1.1.2:32767:10.1.1.2/240
*[BGP/170] 1d 04:23:24, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299808
1:10.1.1.5:32767:10.1.1.5/240
*[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.5
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299776
5:10.1.1.2:32767:32:10.1.1.1:32:224.1.1.1/240
*[BGP/170] 20:34:47, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/12.0, Push 299808
user@PE3> show route protocol bgp
inet.0: 10 destinations, 14 routes (10 active, 0 holddown, 0 hidden)
inet.3: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
vpn-1.inet.0: 14 destinations, 15 routes (14 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.1.1/32 *[BGP/170] 1d 04:23:23, MED 1, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299808(top)
10.1.1.6/32 *[BGP/170] 1d 04:23:20, MED 1, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299792(top)
10.1.1.0/30 *[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299808(top)
10.1.1.16/30 *[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299792(top)
10.100.1.2/32 *[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299808(top)
10.100.1.4/32 *[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299792(top)
vpn-1.inet.1: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
mpls.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
bgp.l3vpn.0: 6 destinations, 6 routes (6 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.1.2:32767:10.1.1.1/32
*[BGP/170] 1d 04:23:23, MED 1, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299808(top)
10.1.1.2:32767:10.1.1.0/30
*[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299808(top)
10.1.1.2:32767:10.100.1.2/32
*[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299808(top)
10.1.1.4:32767:10.1.1.6/32
*[BGP/170] 1d 04:23:20, MED 1, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299792(top)
10.1.1.4:32767:10.1.1.16/30
*[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299792(top)
10.1.1.4:32767:10.100.1.4/32
*[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299776, Push 299792(top)
bgp.mvpn.0: 3 destinations, 3 routes (3 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:10.1.1.2:32767:10.1.1.2/240
*[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299808
1:10.1.1.4:32767:10.1.1.4/240
*[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299792
5:10.1.1.2:32767:32:10.1.1.1:32:224.1.1.1/240
*[BGP/170] 20:34:47, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299808
vpn-1.mvpn.0: 7 destinations, 8 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:10.1.1.2:32767:10.1.1.2/240
*[BGP/170] 1d 04:23:23, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299808
1:10.1.1.4:32767:10.1.1.4/240
*[BGP/170] 1d 04:23:20, localpref 100, from 10.1.1.4
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299792
5:10.1.1.2:32767:32:10.1.1.1:32:224.1.1.1/240
*[BGP/170] 20:34:47, localpref 100, from 10.1.1.2
AS path: I, validation-state: unverified
> via ge-1/2/13.0, Push 299808
Comprobación de las uniones PIM en los dispositivos receptores de CE descendentes
Propósito
Asegúrese de que se están enviando los mensajes de unión esperados.
Acción
user@CE2> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.1
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream interface: ge-1/2/14.0
Group: 224.2.127.254
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream interface: ge-1/2/14.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
-----
user@CE3> show pim join
Instance: PIM.master Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.1
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream interface: ge-1/2/15.0
Group: 224.2.127.254
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream interface: ge-1/2/15.0
Instance: PIM.master Family: INET6
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
-----
Significado
Tanto el dispositivo CE2 como el dispositivo CE3 envían paquetes de unión C ascendentes a sus enrutadores PE vecinos, su siguiente salto de unidifusión para llegar a la fuente C.
Comprobación de las uniones PIM en los dispositivos PE
Propósito
Asegúrese de que se están enviando los mensajes de unión esperados.
Acción
user@PE1> show pim join instance vpn-1
Instance: PIM.vpn-1 Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.1
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream interface: Local
Group: 224.1.1.1
Source: 10.1.1.1
Flags: sparse,spt
Upstream interface: ge-1/2/10.0
Group: 224.2.127.254
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream interface: Local
user@PE2> show pim join instance vpn-1
Instance: PIM.vpn-1 Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.1
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream protocol: BGP
Upstream interface: Through BGP
Group: 224.1.1.1
Source: 10.1.1.1
Flags: sparse,spt
Upstream protocol: BGP
Upstream interface: Through BGP
Group: 224.2.127.254
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream protocol: BGP
Upstream interface: Through BGP
user@PE3> show pim join instance vpn-1
Instance: PIM.vpn-1 Family: INET
R = Rendezvous Point Tree, S = Sparse, W = Wildcard
Group: 224.1.1.1
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream protocol: BGP
Upstream interface: Through BGP
Group: 224.1.1.1
Source: 10.1.1.1
Flags: sparse,spt
Upstream protocol: BGP
Upstream interface: Through BGP
Group: 224.2.127.254
Source: *
RP: 10.100.1.2
Flags: sparse,rptree,wildcard
Upstream protocol: BGP
Upstream interface: Through BGP
Significado
Tanto el dispositivo CE2 como el dispositivo CE3 envían paquetes de unión C ascendentes a sus enrutadores PE vecinos, su siguiente salto de unidifusión para llegar a la fuente C.
El estado C-Join apunta a BGP como la interfaz ascendente. En realidad, no existe una relación de vecino PIM entre los PE. El PE descendente convierte el estado C-PIM (C-S, C-G) en una ruta de BGP de unión de árbol de origen tipo 7 y lo envía al enrutador de PE ascendente hacia el origen C.
Comprobación de las rutas de multidifusión
Propósito
Verifique que el flujo de multidifusión C esté integrado en MVPN vpn-1 y que el dispositivo PE1 lo envíe al túnel del proveedor.
Acción
user@PE1> show multicast route instance vpn-1
Instance: vpn-1 Family: INET
Group: 224.1.1.1/32
Source: *
Upstream interface: local
Downstream interface list:
ge-1/2/11.0
Group: 224.1.1.1
Source: 10.1.1.1/32
Upstream interface: ge-1/2/10.0
Downstream interface list:
ge-1/2/11.0
Group: 224.2.127.254/32
Source: *
Upstream interface: local
Downstream interface list:
ge-1/2/11.0
user@PE2> show multicast route instance vpn-1
Instance: vpn-1 Family: INET
Group: 224.1.1.1/32
Source: *
Upstream rpf interface list:
vt-1/2/10.4 (P)
Sender Id: Label 299840
Downstream interface list:
ge-1/2/14.0
Group: 224.1.1.1
Source: 10.1.1.1/32
Upstream rpf interface list:
vt-1/2/10.4 (P)
Sender Id: Label 299840
Group: 224.2.127.254/32
Source: *
Upstream rpf interface list:
vt-1/2/10.4 (P)
Sender Id: Label 299840
Downstream interface list:
ge-1/2/14.0
user@PE3> show multicast route instance vpn-1
Instance: vpn-1 Family: INET
Group: 224.1.1.1/32
Source: *
Upstream interface: vt-1/2/10.5
Downstream interface list:
ge-1/2/15.0
Group: 224.1.1.1
Source: 10.1.1.1/32
Upstream interface: vt-1/2/10.5
Group: 224.2.127.254/32
Source: *
Upstream interface: vt-1/2/10.5
Downstream interface list:
ge-1/2/15.0
Significado
El resultado muestra que, a diferencia de los otros dispositivos PE, el dispositivo PE2 usa RPF basado en el remitente. La salida del dispositivo PE2 incluye el emisor RPF ascendente. El campo ID de remitente solo se muestra cuando el RPF basado en el remitente está habilitado.
Comprobación de las rutas de multidifusión C de MVPN
Propósito
Compruebe la información de la ruta de multidifusión C de MVPN,
Acción
user@PE1> show mvpn c-multicast instance-name vpn-1
MVPN instance:
Legend for provider tunnel
S- Selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g) RM -- remote VPN route
Family : INET
Instance : vpn-1
MVPN Mode : RPT-SPT
C-mcast IPv4 (S:G) Provider Tunnel St
0.0.0.0/0:224.1.1.1/32 I-P-tnl:LDP-P2MP:1.1.1.3, lsp-id 16777217 RM
10.1.1.1/32:224.1.1.1/32 I-P-tnl:LDP-P2MP:1.1.1.3, lsp-id 16777217 RM
0.0.0.0/0:224.2.127.254/32 I-P-tnl:LDP-P2MP:1.1.1.3, lsp-id 16777217 RM
...
user@PE2> show mvpn c-multicast instance-name vpn-1
MVPN instance:
Legend for provider tunnel
S- Selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g) RM -- remote VPN route
Family : INET
Instance : vpn-1
MVPN Mode : RPT-SPT
C-mcast IPv4 (S:G) Provider Tunnel St
0.0.0.0/0:224.1.1.1/32 I-P-tnl:LDP-P2MP:1.1.1.2, lsp-id 16777217
10.1.1.1/32:224.1.1.1/32 I-P-tnl:LDP-P2MP:1.1.1.2, lsp-id 16777217
0.0.0.0/0:224.2.127.254/32 I-P-tnl:LDP-P2MP:1.1.1.2, lsp-id 16777217
...
user@PE3> show mvpn c-multicast instance-name vpn-1
MVPN instance:
Legend for provider tunnel
S- Selective provider tunnel
Legend for c-multicast routes properties (Pr)
DS -- derived from (*, c-g) RM -- remote VPN route
Family : INET
Instance : vpn-1
MVPN Mode : RPT-SPT
C-mcast IPv4 (S:G) Provider Tunnel St
0.0.0.0/0:224.1.1.1/32 I-P-tnl:LDP-P2MP:1.1.1.2, lsp-id 16777217
10.1.1.1/32:224.1.1.1/32 I-P-tnl:LDP-P2MP:1.1.1.2, lsp-id 16777217
0.0.0.0/0:224.2.127.254/32 I-P-tnl:LDP-P2MP:1.1.1.2, lsp-id 16777217
...
Significado
El resultado muestra el túnel del proveedor y la información de la etiqueta.
Comprobación del PE de origen
Propósito
Compruebe los detalles del PE de origen,
Acción
user@PE1> show mvpn c-multicast source-pe
Instance : vpn-1
MVPN Mode : RPT-SPT
Family : INET
C-Multicast route address :0.0.0.0/0:224.1.1.1/32
MVPN Source-PE1:
extended-community: no-advertise target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: lo0.102 Index: -1610691384
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: lo0.102 Index: -1610691384
C-Multicast route address :10.1.1.1/32:224.1.1.1/32
MVPN Source-PE1:
extended-community: no-advertise target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: ge-1/2/10.0 Index: -1610691384
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: ge-1/2/10.0 Index: -1610691384
C-Multicast route address :0.0.0.0/0:224.2.127.254/32
MVPN Source-PE1:
extended-community: no-advertise target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: lo0.102 Index: -1610691384
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: lo0.102 Index: -1610691384
user@PE2> show mvpn c-multicast source-pe
Instance : vpn-1
MVPN Mode : RPT-SPT
Family : INET
C-Multicast route address :0.0.0.0/0:224.1.1.1/32
MVPN Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
C-Multicast route address :10.1.1.1/32:224.1.1.1/32
MVPN Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
C-Multicast route address :0.0.0.0/0:224.2.127.254/32
MVPN Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
user@PE3> show mvpn c-multicast source-pe
Instance : vpn-1
MVPN Mode : RPT-SPT
Family : INET
C-Multicast route address :0.0.0.0/0:224.1.1.1/32
MVPN Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
C-Multicast route address :10.1.1.1/32:224.1.1.1/32
MVPN Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
C-Multicast route address :0.0.0.0/0:224.2.127.254/32
MVPN Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
PIM Source-PE1:
extended-community: target:10.1.1.2:72
Route Distinguisher: 10.1.1.2:32767
Autonomous system number: 65001
Interface: (Null)
...
Significado
El resultado muestra el túnel del proveedor y la información de la etiqueta.
Comportamiento RPF basado en remitentes específicos de la plataforma
Use el Explorador de características para confirmar la compatibilidad de plataforma y versión para características específicas.
Utilice la siguiente tabla para revisar el comportamiento específico de la plataforma para su plataforma.
| Plataforma |
Diferencia |
|---|---|
| serie MX |
|