Ejemplo: Configuración de LDP de varias instancias
La instancia principal de LDP se configura en el nivel jerárquico [edit protocols] .
Puede configurar una instancia específica de LDP mediante la ldp instrucción en el [edit routing-instances routing-instance-name protocols] nivel de jerarquía. Esto crea una instancia de LDP para la instancia de enrutamiento VRF concreta. Debe especificar todas las instrucciones VRF necesarias y aplicar políticas de exportación e importación a la instancia de LDP para que la configuración se confirme correctamente.
La mayoría de los niveles de jerarquía de LDP disponibles en una instancia primaria también están disponibles para instancias específicas de LDP. Sin embargo, la no-forwarding opción no funciona en una instancia de LDP basada en VRF.
Figura 1: Diagrama de topología LDP de varias instancias
Figura 1 muestra un ejemplo de una red de operadora de operadoras. CE3 y CE4 son enrutadores CE de cliente final que residen en el AS 65010. El proveedor de VPN del AS 65020 tiene tres tipos de enrutadores: PE3 y PE4 son enrutadores PE que se conectan al cliente final, CE1 y CE2 actúan como enrutadores CE de portadora intermedia, y P2 y P3 son enrutadores de tránsito interno. PE1 y PE2 del AS 65030 son enrutadores PE que prestan servicios al proveedor de VPN intermedio, y P0 y P1 son enrutadores de tránsito para la operadora de nivel superior.
Para que esta configuración funcione, debe completar tres tareas principales:
-
Configure el BGP externo entre el CE del cliente VPN y el PE del proveedor VPN.
-
Configure el BGP interno mediante la familia VPN entre ambos pares de enrutadores PE (una conexión IBGP entre PE1 y PE2 y una segunda conexión IBGP entre el enrutador PE3 y el enrutador PE4).
-
Establezca conexiones LDP y Protocolo de puerta de enlace interior (IGP) en todos los vínculos restantes. En este ejemplo se utiliza OSPF como IGP, pero puede utilizar el IGP de su elección.
La información que respalda este ejemplo de LDP de múltiples instancias de portadora se resume en Tabla 1.
|
Conexión |
Protocolos |
|---|---|
|
CE3 - PE3 |
Inet de la familia EBGP |
|
PE3 - P2 - CE1 |
OSPF y LDP |
|
CE1 - PE1 |
OSPF y LDP |
|
PE1 - P0 - P1 - PE2 |
OSPF y LDP |
|
PE1 - PE2 |
Familia IBGP inet-vpn |
|
PE2 - CE2 |
OSPF y LDP |
|
CE2 - P3 - PE4 |
OSPF y LDP |
|
PE4 - CE4 |
Inet de la familia EBGP |
|
PE3 - PE4 |
Familia IBGP inet-vpn |
Las tareas de configuración comienzan en el enrutador CE3 y se mueven entre enrutadores a través de la primera parte de la red del proveedor de VPN, al AS del operador, al segundo clúster de proveedores de VPN del AS 65020 y terminan en el segundo enrutador CE4 del cliente VPN.
Dado que el enrutador CE3 es el primer enrutador del cliente, configure el EBGP entre el enrutador CE3 y el enrutador PE3 del proveedor de VPN conectado. También debe anunciar su dirección de circuito cerrado en BGP con una política de enrutamiento para permitir la accesibilidad IP con el enrutador CE4.
Enrutador CE3
user@CE3# set interfaces ge-0/0/0 description to-PE3 set interfaces ge-0/0/0 unit 0 family inet address 172.16.33.1/30 set interfaces lo0 unit 0 family inet address 192.168.10.3/32 set policy-options policy-statement loopback term 1 from route-filter 192.168.10.3/32 exact set policy-options policy-statement loopback term 1 then accept set policy-options policy-statement loopback term 3 then reject set protocols bgp group to-PE3 export loopback set protocols bgp group to-PE3 peer-as 65020 set protocols bgp group to-PE3 neighbor 172.16.33.2 set routing-options router-id 192.168.10.3 set routing-options autonomous-system 65010
En el enrutador PE3, las tareas de configuración son más complicadas. Debe completar la conexión EBGP con el enrutador CE3 en una instancia de VRF, habilitar MPLS y LDP en la interfaz que apunte hacia el enrutador CE1 del proveedor de VPN y configurar una instancia principal de IBGP para llegar al enrutador PE4 en el extremo más alejado del AS 65020.
Por último, configure una política de VRF saliente que coloque todo el tráfico de BGP y las interfaces conectadas directamente en una comunidad de BGP y una política de VRF entrante que acepte tráfico de comunidad de BGP similar del enrutador PE4.
Enrutador PE3
user@PE3# set interfaces ge-0/0/0 description to-CE3 set interfaces ge-0/0/0 unit 0 family inet address 172.16.33.2/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-P2 set interfaces ge-0/0/1 unit 0 family inet address 10.1.32.1/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.20.3/32 set policy-options policy-statement vpn-customer-export term 1 from protocol bgp set policy-options policy-statement vpn-customer-export term 1 from protocol direct set policy-options policy-statement vpn-customer-export term 1 then community add vpn-customer-comm set policy-options policy-statement vpn-customer-export term 1 then accept set policy-options policy-statement vpn-customer-export term 2 then reject set policy-options policy-statement vpn-customer-import term 1 from protocol bgp set policy-options policy-statement vpn-customer-import term 1 from community vpn-customer-comm set policy-options policy-statement vpn-customer-import term 1 then accept set policy-options policy-statement vpn-customer-import term 2 then reject set policy-options community vpn-customer-comm members target:65020:1 set routing-instances vpn-customer instance-type vrf set routing-instances vpn-customer protocols bgp group customer peer-as 65010 set routing-instances vpn-customer protocols bgp group customer as-override set routing-instances vpn-customer protocols bgp group customer neighbor 172.16.33.1 set routing-instances vpn-customer interface ge-0/0/0.0 set routing-instances vpn-customer route-distinguisher 192.168.20.3:1 set routing-instances vpn-customer vrf-import vpn-customer-import set routing-instances vpn-customer vrf-export vpn-customer-export set protocols bgp group to-PE4 type internal set protocols bgp group to-PE4 local-address 192.168.20.3 set protocols bgp group to-PE4 neighbor 192.168.20.14 family inet-vpn unicast set protocols ldp interface ge-0/0/1.0 set protocols mpls interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 set routing-options router-id 192.168.20.3 set routing-options autonomous-system 65020
En el enrutador P2, habilite LDP y el IGP utilizados para transportar etiquetas (en este caso, OSPF). Repetirá estas tareas en todos los enrutadores de núcleo de tránsito, tanto en la red del proveedor de VPN como en la red del operador central.
Enrutador P2
user@P2# set interfaces ge-0/0/0 description to-PE3 set interfaces ge-0/0/0 unit 0 family inet address 10.1.32.2/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-CE1 set interfaces ge-0/0/1 unit 0 family inet address 10.1.21.1/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.20.2/32 set protocols ldp interface ge-0/0/0.0 set protocols ldp interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 set routing-options router-id 192.168.20.2 set routing-options autonomous-system 65020
Para el enrutador CE1, configure LDP y OSPF de la misma manera que configuró el enrutador P2.
Enrutador CE1
user@CE1# set interfaces ge-0/0/0 description to-P2 set interfaces ge-0/0/0 unit 0 family inet address 10.1.21.2/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-PE1 set interfaces ge-0/0/1 unit 0 family inet address 172.16.11.1/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.20.1/32 set protocols ldp interface ge-0/0/0.0 set protocols ldp interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 set routing-options router-id 192.168.20.1 set routing-options autonomous-system 65020
En el enrutador de operador principal PE1, configure una instancia principal para OSPF, LDP, MPLS e IBGP (con la family inet-vpn opción) para conectar el enrutador al enrutador vecino PE2. A continuación, implemente LDP de varias instancias estableciendo una instancia secundaria. Habilite LDP y OSPF en esta instancia para que el enrutador PE1 se comunique con el enrutador CE1. MPLS no es necesario en la instancia secundaria.
Por último, configure una política de VRF saliente que coloque todo el tráfico de LDP procedente del enrutador CE1 en una comunidad BGP, una política de exportación que envíe este tráfico de comunidad al enrutador PE2 y una política de VRF entrante que acepte tráfico de comunidad BGP similar del enrutador PE2. Este paso tuneliza el tráfico LDP del proveedor de VPN a la sesión BGP del operador.
Enrutador PE1
user@PE1# set interfaces ge-0/0/0 description to-CE1 set interfaces ge-0/0/0 unit 0 family inet address 172.16.11.2/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-P0 set interfaces ge-0/0/1 unit 0 family inet address 10.1.10.1/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.30.1/32 set policy-options policy-statement bgp-routes-export term 1 from protocol bgp set policy-options policy-statement bgp-routes-export term 1 from community vpn-provider-comm set policy-options policy-statement bgp-routes-export term 1 then accept set policy-options policy-statement bgp-routes-export term 2 then reject set policy-options policy-statement vpn-provider-export term 1 from protocol ldp set policy-options policy-statement vpn-provider-export term 1 from protocol ospf set policy-options policy-statement vpn-provider-export term 1 then community add vpn-provider-comm set policy-options policy-statement vpn-provider-export term 1 then accept set policy-options policy-statement vpn-provider-export term 2 then reject set policy-options policy-statement vpn-provider-import term 1 from protocol bgp set policy-options policy-statement vpn-provider-import term 1 from community vpn-provider-comm set policy-options policy-statement vpn-provider-import term 1 then accept set policy-options policy-statement vpn-provider-import term 2 then reject set policy-options community vpn-provider-comm members target:65030:1 set routing-instances vpn-provider instance-type vrf set routing-instances vpn-provider protocols ldp egress-policy bgp-routes-export set routing-instances vpn-provider protocols ldp interface ge-0/0/0.0 set routing-instances vpn-provider protocols mpls traffic-engineering bgp-igp set routing-instances vpn-provider protocols mpls interface ge-0/0/0.0 set routing-instances vpn-provider protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set routing-instances vpn-provider protocols ospf export bgp-routes-export set routing-instances vpn-provider interface ge-0/0/0.0 set routing-instances vpn-provider route-distinguisher 192.168.30.1:1 set routing-instances vpn-provider vrf-import vpn-provider-import set routing-instances vpn-provider vrf-export vpn-provider-export set protocols bgp group pe type internal set protocols bgp group pe local-address 192.168.30.1 set protocols bgp group pe family inet-vpn unicast set protocols bgp group pe neighbor 192.168.30.2 set protocols ldp interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set routing-options router-id 192.168.30.1 set routing-options autonomous-system 65030
En el enrutador P0, habilite LDP y OSPF de la misma manera que configuró estos protocolos en el enrutador P2. Repetirá estas tareas en el enrutador P1 y el enrutador P3.
Enrutador P0
user@P0# set interfaces ge-0/0/0 description to-PE1 set interfaces ge-0/0/0 unit 0 family inet address 10.1.10.2/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-P1 set interfaces ge-0/0/1 unit 0 family inet address 10.1.1.1/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.30.10/32 set protocols ldp interface ge-0/0/0.0 set protocols ldp interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 set routing-options router-id 192.168.30.10 set routing-options autonomous-system 65030
En el enrutador P1, habilite LDP y el IGP utilizado para transportar etiquetas (OSPF en este caso).
Enrutador P1
user@P1# set interfaces ge-0/0/0 description to-P0 set interfaces ge-0/0/0 unit 0 family inet address 10.1.1.2/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-PE2 set interfaces ge-0/0/1 unit 0 family inet address 10.1.12.1/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.30.11/32 set protocols ldp interface ge-0/0/0.0 set protocols ldp interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 set routing-options router-id 192.168.30.11 set routing-options autonomous-system 65030
El enrutador de portadora principal PE2 es una imagen especular del enrutador PE1. En primer lugar, configure una instancia principal para OSPF, LDP, MPLS e IBGP (con la opción) para conectar el family inet-vpn enrutador PE2 al enrutador vecino PE1. A continuación, implemente LDP de varias instancias estableciendo una instancia secundaria. Habilite LDP y OSPF en esta instancia para que el enrutador PE2 se comunique con el enrutador CE2. MPLS no es necesario en la instancia secundaria.
Por último, configure una política de VRF saliente que coloque todo el tráfico LDP procedente del enrutador CE2 en una comunidad BGP, una política de exportación que envíe este tráfico de comunidad al enrutador PE1 y una política de VRF entrante que acepte tráfico de comunidad BGP similar del enrutador PE1. Este paso tuneliza el tráfico LDP del proveedor de VPN a la sesión BGP del operador.
Enrutador PE2
user@PE2# set interfaces ge-0/0/0 description to-P1 set interfaces ge-0/0/0 unit 0 family inet address 10.1.12.2/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-CE2 set interfaces ge-0/0/1 unit 0 family inet address 172.16.22.2/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.30.2/32 set policy-options policy-statement bgp-routes-export term 1 from protocol bgp set policy-options policy-statement bgp-routes-export term 1 from community vpn-provider-comm set policy-options policy-statement bgp-routes-export term 1 then accept set policy-options policy-statement bgp-routes-export term 2 then reject set policy-options policy-statement vpn-provider-export term 1 from protocol ldp set policy-options policy-statement vpn-provider-export term 1 from protocol ospf set policy-options policy-statement vpn-provider-export term 1 then community add vpn-provider-comm set policy-options policy-statement vpn-provider-export term 1 then accept set policy-options policy-statement vpn-provider-export term 2 then reject set policy-options policy-statement vpn-provider-import term 1 from protocol bgp set policy-options policy-statement vpn-provider-import term 1 from community vpn-provider-comm set policy-options policy-statement vpn-provider-import term 1 then accept set policy-options policy-statement vpn-provider-import term 2 then reject set policy-options community vpn-provider-comm members target:65030:1 set routing-instances vpn-provider instance-type vrf set routing-instances vpn-provider protocols ldp egress-policy bgp-routes-export set routing-instances vpn-provider protocols ldp interface ge-0/0/1.0 set routing-instances vpn-provider protocols mpls traffic-engineering bgp-igp set routing-instances vpn-provider protocols mpls interface ge-0/0/1.0 set routing-instances vpn-provider protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set routing-instances vpn-provider protocols ospf export bgp-routes-export set routing-instances vpn-provider interface ge-0/0/1.0 set routing-instances vpn-provider route-distinguisher 192.168.30.2:1 set routing-instances vpn-provider vrf-import vpn-provider-import set routing-instances vpn-provider vrf-export vpn-provider-export set protocols bgp group pe type internal set protocols bgp group pe local-address 192.168.30.2 set protocols bgp group pe family inet-vpn unicast set protocols bgp group pe neighbor 192.168.30.1 set protocols ldp interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface lo0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set routing-options router-id 192.168.30.2 set routing-options autonomous-system 65030
Para el enrutador CE2, configure LDP y OSPF como lo hizo en el enrutador CE1 y los enrutadores P de tránsito.
Enrutador CE2
user@CE2# set interfaces ge-0/0/0 description to-PE2 set interfaces ge-0/0/0 unit 0 family inet address 172.16.22.1/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-P3 set interfaces ge-0/0/1 unit 0 family inet address 10.1.23.2/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.20.12/32 set protocols ldp interface ge-0/0/0.0 set protocols ldp interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 set routing-options router-id 192.168.20.12 set routing-options autonomous-system 65020
Dado que el enrutador P3 es otro enrutador de proveedor principal, habilite LDP y OSPF en todas las interfaces de tránsito.
Enrutador P3
user@P3# set interfaces ge-0/0/0 description to-CE2 set interfaces ge-0/0/0 unit 0 family inet address 10.1.23.1/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-PE4 set interfaces ge-0/0/1 unit 0 family inet address 10.1.43.2/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.20.13/32 set protocols ldp interface ge-0/0/0.0 set protocols ldp interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/1.0 set protocols ospf area 0.0.0.0 interface lo0.0 set routing-options router-id 192.168.20.13 set routing-options autonomous-system 65020
En el enrutador PE4, complete la conexión IBGP iniciada en el enrutador PE3 para conectar los enrutadores de borde en el AS 65020. Además, habilite LDP y MPLS en la interfaz que apunte hacia el enrutador CE2 del proveedor de VPN y establezca una conexión EBGP con el enrutador CE4 mediante el uso de una instancia VRF.
Por último, configure una política de VRF saliente que coloque todo el tráfico BGP y las interfaces conectadas directamente en una comunidad BGP y una política de VRF entrante que acepte tráfico de comunidad BGP similar del enrutador PE3.
Enrutador PE4
user@PE4# set interfaces ge-0/0/0 description to-P3 set interfaces ge-0/0/0 unit 0 family inet address 10.1.43.1/30 set interfaces ge-0/0/0 unit 0 family mpls set interfaces ge-0/0/1 description to-CE4 set interfaces ge-0/0/1 unit 0 family inet address 172.16.44.2/30 set interfaces ge-0/0/1 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.168.20.14/32 set policy-options policy-statement vpn-customer-export term 1 from protocol bgp set policy-options policy-statement vpn-customer-export term 1 from protocol direct set policy-options policy-statement vpn-customer-export term 1 then community add vpn-customer-comm set policy-options policy-statement vpn-customer-export term 1 then accept set policy-options policy-statement vpn-customer-export term 2 then reject set policy-options policy-statement vpn-customer-import term 1 from protocol bgp set policy-options policy-statement vpn-customer-import term 1 from community vpn-customer-comm set policy-options policy-statement vpn-customer-import term 1 then accept set policy-options policy-statement vpn-customer-import term 2 then reject set policy-options community vpn-customer-comm members target:65020:1 set routing-instances vpn-customer instance-type vrf set routing-instances vpn-customer protocols bgp group customer peer-as 65010 set routing-instances vpn-customer protocols bgp group customer as-override set routing-instances vpn-customer protocols bgp group customer neighbor 172.16.44.1 set routing-instances vpn-customer interface ge-0/0/1.0 set routing-instances vpn-customer route-distinguisher 192.168.20.14:1 set routing-instances vpn-customer vrf-import vpn-customer-import set routing-instances vpn-customer vrf-export vpn-customer-export set protocols bgp group int type internal set protocols bgp group int local-address 192.168.20.14 set protocols bgp group int neighbor 192.168.20.3 family inet-vpn unicast set protocols ldp interface ge-0/0/0.0 set protocols mpls interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface ge-0/0/0.0 set protocols ospf area 0.0.0.0 interface lo0.0 set routing-options router-id 192.168.20.14 set routing-options autonomous-system 65020
El enrutador CE4 es el enrutador del cliente de VPN de destino. Configure el EBGP entre el enrutador CE4 y el proveedor de VPN conectado Router PE4 para completar la configuración. Recuerde anunciar la dirección de circuito cerrado en BGP mediante una política de enrutamiento que permita la accesibilidad IP con el enrutador CE3.
Enrutador CE4
user@CE4# set interfaces ge-0/0/0 description to-PE4 set interfaces ge-0/0/0 unit 0 family inet address 172.16.44.1/30 set interfaces lo0 unit 0 family inet address 192.168.10.4/32 set policy-options policy-statement loopback term 1 from route-filter 192.168.10.4/32 exact set policy-options policy-statement loopback term 1 then accept set policy-options policy-statement loopback term 3 then reject set protocols bgp group provider export loopback set protocols bgp group provider peer-as 65020 set protocols bgp group provider neighbor 172.16.44.2 set routing-options router-id 192.168.10.4 set routing-options autonomous-system 65010
Verificación de su trabajo
Para comprobar el correcto funcionamiento de la configuración de LDP de varias instancias, utilice los siguientes comandos:
-
show ldp database -
show ldp interface -
show ldp neighbor -
show ldp path -
show ldp route -
show ldp session -
show ldp statistics
La salida de pantalla para estos comandos es la misma que en versiones anteriores de Junos OS, excepto por una diferencia. Ahora se puede utilizar un nombre de instancia como argumento.
Si incluye un nombre de instancia con estos comandos, mostrará información para la instancia de LDP especificada. Por ejemplo, el comando show ldp neighbor instance crockett muestra todos los vecinos de LDP para una instancia de VRF denominada crockett. Por el contrario, show ldp neighbor sin un nombre de instancia muestra los vecinos de LDP asociados con la instancia principal.
En las secciones siguientes se muestra el resultado de estos comandos utilizados con el ejemplo de configuración:
- Estado del enrutador CE3
- Estado PE3 del enrutador
- Estado del enrutador CE1
- Estado PE1 del enrutador
- Estado PE2 del enrutador
- Estado del enrutador CE2
- Estado PE4 del enrutador
- Estado del enrutador CE4
Estado del enrutador CE3
user@CE3> show bgp summary
Threading mode: BGP I/O
Default eBGP mode: advertise - accept, receive - accept
Groups: 1 Peers: 1 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet.0
2 2 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
172.16.33.2 65020 19653 19724 0 0 6d 3:53:37 Establ
inet.0: 2/2/2/0
user@CE3> show route protocol bgp
inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
172.16.44.0/30 *[BGP/170] 6d 00:53:43, localpref 100
AS path: 65020 I, validation-state: unverified
> to 172.16.33.2 via ge-0/0/0.0
192.168.10.4/32 *[BGP/170] 6d 00:53:42, localpref 100
AS path: 65020 65020 I, validation-state: unverified
> to 172.16.33.2 via ge-0/0/0.0
inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
user@CE3> ping 192.168.10.4 source 192.168.10.3 count 2
PING 192.168.10.4 (192.168.10.4): 56 data bytes
64 bytes from 192.168.10.4: icmp_seq=0 ttl=54 time=24.744 ms
64 bytes from 192.168.10.4: icmp_seq=1 ttl=54 time=16.336 ms
--- 192.168.10.4 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 16.336/20.540/24.744/4.204 ms
Estado PE3 del enrutador
user@PE3> show bgp summary
Threading mode: BGP I/O
Default eBGP mode: advertise - accept, receive - accept
Groups: 2 Peers: 2 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
bgp.l3vpn.0
2 2 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
172.16.33.1 65010 19783 19708 0 0 6d 4:19:07 Establ
vpn-customer.inet.0: 1/1/1/0
192.168.20.14 65020 19299 19297 0 1 6d 1:17:05 Establ
bgp.l3vpn.0: 2/2/2/0
vpn-customer.inet.0: 2/2/2/0
user@PE3> show route protocol ldp
inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
224.0.0.2/32 *[LDP/9] 6d 04:55:21, metric 1
MultiRecv
inet.3: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.23.0/30 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Push 299968
10.1.43.0/30 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Push 300000
192.168.20.1/32 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Push 299952
192.168.20.2/32 *[LDP/9] 6d 04:22:00, metric 1
> to 10.1.32.2 via ge-0/0/1.0
192.168.20.12/32 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Push 299984
192.168.20.13/32 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Push 300016
192.168.20.14/32 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Push 300032
vpn-customer.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
mpls.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
299856 *[LDP/9] 6d 04:22:00, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Pop
299856(S=0) *[LDP/9] 6d 04:22:00, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Pop
299984 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Swap 299952
300000 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Swap 299968
300016 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Swap 299984
300032 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Swap 300000
300048 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Swap 300016
300064 *[LDP/9] 6d 01:18:46, metric 1
> to 10.1.32.2 via ge-0/0/1.0, Swap 300032
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
vpn-customer.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
user@PE3> show route protocol bgp
inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
inet.3: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
vpn-customer.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
172.16.44.0/30 *[BGP/170] 6d 01:19:31, localpref 100, from 192.168.20.14
AS path: I, validation-state: unverified
> to 10.1.32.2 via ge-0/0/1.0, Push 299968, Push 300032(top)
192.168.10.3/32 *[BGP/170] 6d 04:21:33, localpref 100
AS path: 65010 I, validation-state: unverified
> to 172.16.33.1 via ge-0/0/0.0
192.168.10.4/32 *[BGP/170] 6d 01:19:30, localpref 100, from 192.168.20.14
AS path: 65010 I, validation-state: unverified
> to 10.1.32.2 via ge-0/0/1.0, Push 299968, Push 300032(top)
mpls.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.20.14:1:172.16.44.0/30
*[BGP/170] 6d 01:19:31, localpref 100, from 192.168.20.14
AS path: I, validation-state: unverified
> to 10.1.32.2 via ge-0/0/1.0, Push 299968, Push 300032(top)
192.168.20.14:1:192.168.10.4/32
*[BGP/170] 6d 01:19:30, localpref 100, from 192.168.20.14
AS path: 65010 I, validation-state: unverified
> to 10.1.32.2 via ge-0/0/1.0, Push 299968, Push 300032(top)
inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
vpn-customer.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Estado del enrutador CE1
user@CE1> show ldp neighbor
Address Interface Label space ID Hold time
172.16.11.2 ge-0/0/1.0 172.16.11.2:0 12
10.1.21.1 ge-0/0/0.0 192.168.20.2:0 12
user@CE1> show route
inet.0: 15 destinations, 15 routes (15 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.21.0/30 *[Direct/0] 6d 01:32:24
> via ge-0/0/0.0
10.1.21.2/32 *[Local/0] 6d 01:32:24
Local via ge-0/0/0.0
10.1.23.0/30 *[OSPF/10] 6d 03:34:28, metric 3
> to 172.16.11.2 via ge-0/0/1.0
10.1.32.0/30 *[OSPF/10] 6d 01:31:41, metric 2
> to 10.1.21.1 via ge-0/0/0.0
10.1.43.0/30 *[OSPF/10] 6d 03:28:49, metric 4
> to 172.16.11.2 via ge-0/0/1.0
172.16.11.0/30 *[Direct/0] 6d 04:57:56
> via ge-0/0/1.0
172.16.11.1/32 *[Local/0] 6d 04:57:56
Local via ge-0/0/1.0
192.168.20.1/32 *[Direct/0] 6d 04:40:45
> via lo0.0
192.168.20.2/32 *[OSPF/10] 6d 01:31:41, metric 1
> to 10.1.21.1 via ge-0/0/0.0
192.168.20.3/32 *[OSPF/10] 6d 01:31:41, metric 2
> to 10.1.21.1 via ge-0/0/0.0
192.168.20.12/32 *[OSPF/150] 6d 03:34:27, metric 1, tag 3489725958
> to 172.16.11.2 via ge-0/0/1.0
192.168.20.13/32 *[OSPF/150] 6d 03:28:46, metric 1, tag 3489725958
> to 172.16.11.2 via ge-0/0/1.0
192.168.20.14/32 *[OSPF/150] 6d 02:51:40, metric 1, tag 3489725958
> to 172.16.11.2 via ge-0/0/1.0
224.0.0.2/32 *[LDP/9] 6d 04:57:56, metric 1
MultiRecv
224.0.0.5/32 *[OSPF/10] 6d 04:57:56, metric 1
MultiRecv
inet.3: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.23.0/30 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Push 300032
10.1.43.0/30 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Push 300064
192.168.20.2/32 *[LDP/9] 6d 01:31:39, metric 1
> to 10.1.21.1 via ge-0/0/0.0
192.168.20.3/32 *[LDP/9] 6d 01:31:39, metric 1
> to 10.1.21.1 via ge-0/0/0.0, Push 299856
192.168.20.12/32 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Push 300048
192.168.20.13/32 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Push 300080
192.168.20.14/32 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Push 300096
mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
299888 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Swap 300032
299904 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Swap 300048
299920 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Swap 300064
299936 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Swap 300080
299952 *[LDP/9] 6d 01:32:49, metric 1
> to 172.16.11.2 via ge-0/0/1.0, Swap 300096
299968 *[LDP/9] 6d 01:31:39, metric 1
> to 10.1.21.1 via ge-0/0/0.0, Pop
299968(S=0) *[LDP/9] 6d 01:31:39, metric 1
> to 10.1.21.1 via ge-0/0/0.0, Pop
299984 *[LDP/9] 6d 01:31:39, metric 1
> to 10.1.21.1 via ge-0/0/0.0, Swap 299856
inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
ff02::2/128 *[INET6/0] 1w0d 02:45:00
MultiRecv
Estado PE1 del enrutador
user@PE1> show ldp neighbor instance vpn-provider
Address Interface Label space ID Hold time
172.16.11.1 ge-0/0/0.0 192.168.20.1:0 14
user@PE1> show ldp database instance vpn-provider
Input label database, 172.16.11.2:0--192.168.20.1:0
Labels received: 8
Label Prefix
299888 10.1.23.0/30
299920 10.1.43.0/30
3 192.168.20.1/32
299968 192.168.20.2/32
299984 192.168.20.3/32
299904 192.168.20.12/32
299936 192.168.20.13/32
299952 192.168.20.14/32
Output label database, 172.16.11.2:0--192.168.20.1:0
Labels advertised: 8
Label Prefix
300032 10.1.23.0/30
300064 10.1.43.0/30
299824 192.168.20.1/32
300112 192.168.20.2/32
300128 192.168.20.3/32
300048 192.168.20.12/32
300080 192.168.20.13/32
300096 192.168.20.14/32
user@PE1> show ldp interface instance vpn-provider
Interface Address Label space ID Nbr Next
count hello
ge-0/0/0.0 172.16.11.2 172.16.11.2:0 1 2
user@PE1> show ldp path instance vpn-provider
Output Session (label) Input Session (label)
192.168.20.1:0(299824)( ) 192.168.20.1:0(3)( )
Attached route: 192.168.20.1/32, Ingress route
192.168.20.1:0(300032) ( )
Attached route: 10.1.23.0/30
192.168.20.1:0(300048) ( )
Attached route: 192.168.20.12/32
192.168.20.1:0(300064) ( )
Attached route: 10.1.43.0/30
192.168.20.1:0(300080) ( )
Attached route: 192.168.20.13/32
192.168.20.1:0(300096) ( )
Attached route: 192.168.20.14/32
192.168.20.1:0(300112) 192.168.20.1:0(299968)
Attached route: 192.168.20.2/32, Ingress route
192.168.20.1:0(300128) 192.168.20.1:0(299984)
Attached route: 192.168.20.3/32, Ingress route
user@PE1> show ldp route instance vpn-provider
Destination Next-hop intf/lsp/table Next-hop address
10.1.21.0/30 ge-0/0/0.0 172.16.11.1
10.1.23.0/30 192.168.30.2
10.1.32.0/30 ge-0/0/0.0 172.16.11.1
10.1.43.0/30 192.168.30.2
172.16.11.0/30 ge-0/0/0.0
172.16.11.2/32
192.168.20.1/32 ge-0/0/0.0 172.16.11.1
192.168.20.2/32 ge-0/0/0.0 172.16.11.1
192.168.20.3/32 ge-0/0/0.0 172.16.11.1
192.168.20.12/32 192.168.30.2
192.168.20.13/32 192.168.30.2
192.168.20.14/32 192.168.30.2
224.0.0.5/32
user@PE1> show ldp session instance vpn-provider
Address State Connection Hold time Adv. Mode
192.168.20.1 Operational Open 21 DU
user@PE1> show bgp summary
Threading mode: BGP I/O
Default eBGP mode: advertise - accept, receive - accept
Groups: 1 Peers: 1 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
bgp.l3vpn.0
5 5 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
192.168.30.2 65030 19795 19797 0 0 6d 4:21:31 Establ
bgp.l3vpn.0: 5/5/5/0
vpn-provider.inet.0: 5/5/5/0
Estado PE2 del enrutador
user@PE2> show ldp neighbor instance vpn-provider
Address Interface Label space ID Hold time
172.16.22.1 ge-0/0/1.0 192.168.20.12:0 12
user@PE2> show ldp database instance vpn-provider
Input label database, 172.16.22.2:0--192.168.20.12:0
Labels received: 8
Label Prefix
299888 10.1.21.0/30
299904 10.1.32.0/30
299808 192.168.20.1/32
299920 192.168.20.2/32
299936 192.168.20.3/32
3 192.168.20.12/32
299856 192.168.20.13/32
299872 192.168.20.14/32
Output label database, 172.16.22.2:0--192.168.20.12:0
Labels advertised: 8
Label Prefix
300000 10.1.21.0/30
300032 10.1.32.0/30
299888 192.168.20.1/32
300016 192.168.20.2/32
300048 192.168.20.3/32
299920 192.168.20.12/32
299952 192.168.20.13/32
299984 192.168.20.14/32
user@PE2> show ldp interface instance vpn-provider
Interface Address Label space ID Nbr Next
count hello
ge-0/0/1.0 172.16.22.2 172.16.22.2:0 1 4
user@PE2> show ldp path instance vpn-provider
Output Session (label) Input Session (label)
192.168.20.12:0(299888)( )( )
( )
Attached route: 192.168.20.1/32
192.168.20.12:0(299920) 192.168.20.12:0(3)
Attached route: 192.168.20.12/32, Ingress route
192.168.20.12:0(299952) 192.168.20.12:0(299856)
Attached route: 192.168.20.13/32, Ingress route
192.168.20.12:0(299984) 192.168.20.12:0(299872)
Attached route: 192.168.20.14/32, Ingress route
192.168.20.12:0(300000) ( )
Attached route: 10.1.21.0/30
192.168.20.12:0(300016) ( )
Attached route: 192.168.20.2/32
192.168.20.12:0(300032) ( )
Attached route: 10.1.32.0/30
192.168.20.12:0(300048) ( )
Attached route: 192.168.20.3/32
user@PE2> show ldp route instance vpn-provider
Destination Next-hop intf/lsp/table Next-hop address
10.1.21.0/30 192.168.30.1
10.1.23.0/30 ge-0/0/1.0 172.16.22.1
10.1.32.0/30 192.168.30.1
10.1.43.0/30 ge-0/0/1.0 172.16.22.1
172.16.22.0/30 ge-0/0/1.0
172.16.22.2/32
192.168.20.1/32 192.168.30.1
192.168.20.2/32 192.168.30.1
192.168.20.3/32 192.168.30.1
192.168.20.12/32 ge-0/0/1.0 172.16.22.1
192.168.20.13/32 ge-0/0/1.0 172.16.22.1
192.168.20.14/32 ge-0/0/1.0 172.16.22.1
224.0.0.5/32
user@PE2> show ldp session instance vpn-provider
Address State Connection Hold time Adv. Mode
192.168.20.12 Operational Open 21 DU
user@PE2> show bgp summary
Threading mode: BGP I/O
Default eBGP mode: advertise - accept, receive - accept
Groups: 1 Peers: 1 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
bgp.l3vpn.0
5 5 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
192.168.30.1 65030 35560 35557 0 0 1w4d 2:35:55 Establ
bgp.l3vpn.0: 5/5/5/0
vpn-provider.inet.0: 5/5/5/0
Estado del enrutador CE2
user@CE2> show ldp neighbor
Address Interface Label space ID Hold time
172.16.22.2 ge-0/0/0.0 172.16.22.2:0 12
10.1.23.1 ge-0/0/1.0 192.168.20.13:0 11
user@CE2> show route
inet.0: 16 destinations, 16 routes (16 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.21.0/30 *[OSPF/10] 1w4d 00:42:23, metric 3
> to 172.16.22.2 via ge-0/0/0.0
10.1.23.0/30 *[Direct/0] 1w4d 02:44:36
> via ge-0/0/1.0
10.1.23.2/32 *[Local/0] 1w4d 02:44:36
Local via ge-0/0/1.0
10.1.32.0/30 *[OSPF/10] 1w4d 00:41:40, metric 4
> to 172.16.22.2 via ge-0/0/0.0
10.1.43.0/30 *[OSPF/10] 1w4d 02:38:50, metric 2
> to 10.1.23.1 via ge-0/0/1.0
172.16.22.0/30 *[Direct/0] 1w4d 02:44:36
> via ge-0/0/0.0
172.16.22.1/32 *[Local/0] 1w4d 02:44:36
Local via ge-0/0/0.0
192.168.0.0/16 *[Static/5] 1w5d 01:55:12
> to 10.93.31.254 via fxp0.0
192.168.20.1/32 *[OSPF/150] 1w4d 02:44:26, metric 1, tag 3489725958
> to 172.16.22.2 via ge-0/0/0.0
192.168.20.2/32 *[OSPF/150] 1w4d 00:41:37, metric 1, tag 3489725958
> to 172.16.22.2 via ge-0/0/0.0
192.168.20.3/32 *[OSPF/150] 1w4d 00:41:37, metric 1, tag 3489725958
> to 172.16.22.2 via ge-0/0/0.0
192.168.20.12/32 *[Direct/0] 1w4d 02:44:36
> via lo0.0
192.168.20.13/32 *[OSPF/10] 1w4d 02:38:50, metric 1
> to 10.1.23.1 via ge-0/0/1.0
192.168.20.14/32 *[OSPF/10] 1w4d 02:01:44, metric 2
> to 10.1.23.1 via ge-0/0/1.0
224.0.0.2/32 *[LDP/9] 1w4d 02:44:36, metric 1
MultiRecv
224.0.0.5/32 *[OSPF/10] 1w4d 02:44:36, metric 1
MultiRecv
inet.3: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.21.0/30 *[LDP/9] 1w4d 00:42:23, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Push 300000
10.1.32.0/30 *[LDP/9] 1w4d 00:41:40, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Push 300032
192.168.20.1/32 *[LDP/9] 1w4d 02:44:26, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Push 299888
192.168.20.2/32 *[LDP/9] 1w4d 00:41:40, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Push 300016
192.168.20.3/32 *[LDP/9] 1w4d 00:41:40, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Push 300048
192.168.20.13/32 *[LDP/9] 1w4d 02:38:47, metric 1
> to 10.1.23.1 via ge-0/0/1.0
192.168.20.14/32 *[LDP/9] 1w4d 02:01:41, metric 1
> to 10.1.23.1 via ge-0/0/1.0, Push 299872
mpls.0: 8 destinations, 8 routes (8 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
299808 *[LDP/9] 1w4d 02:44:26, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Swap 299888
299856 *[LDP/9] 1w4d 02:38:47, metric 1
> to 10.1.23.1 via ge-0/0/1.0, Pop
299856(S=0) *[LDP/9] 1w4d 02:38:47, metric 1
> to 10.1.23.1 via ge-0/0/1.0, Pop
299872 *[LDP/9] 1w4d 02:01:41, metric 1
> to 10.1.23.1 via ge-0/0/1.0, Swap 299872
299888 *[LDP/9] 1w4d 00:42:23, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Swap 300000
299904 *[LDP/9] 1w4d 00:41:40, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Swap 300032
299920 *[LDP/9] 1w4d 00:41:40, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Swap 300016
299936 *[LDP/9] 1w4d 00:41:40, metric 1
> to 172.16.22.2 via ge-0/0/0.0, Swap 300048
inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
ff02::2/128 *[INET6/0] 1w5d 01:55:12
MultiRecv
Estado PE4 del enrutador
user@PE4> show bgp summary
Threading mode: BGP I/O
Default eBGP mode: advertise - accept, receive - accept
Groups: 2 Peers: 2 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
bgp.l3vpn.0
2 2 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
172.16.44.1 65010 35462 35336 0 0 1w4d 1:56:16 Establ
vpn-customer.inet.0: 1/1/1/0
192.168.20.3 65020 35168 35168 0 1 1w4d 0:42:52 Establ
bgp.l3vpn.0: 2/2/2/0
vpn-customer.inet.0: 2/2/2/0
user@PE4> show route protocol bgp
inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
inet.3: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
vpn-customer.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
172.16.33.0/30 *[BGP/170] 1w4d 00:43:33, localpref 100, from 192.168.20.3
AS path: I, validation-state: unverified
> to 10.1.43.2 via ge-0/0/0.0, Push 300080, Push 299936(top)
192.168.10.3/32 *[BGP/170] 1w4d 00:43:32, localpref 100, from 192.168.20.3
AS path: 65010 I, validation-state: unverified
> to 10.1.43.2 via ge-0/0/0.0, Push 300080, Push 299936(top)
192.168.10.4/32 *[BGP/170] 1w4d 01:56:57, localpref 100
AS path: 65010 I, validation-state: unverified
> to 172.16.44.1 via ge-0/0/1.0
mpls.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.168.20.3:1:172.16.33.0/30
*[BGP/170] 1w4d 00:43:33, localpref 100, from 192.168.20.3
AS path: I, validation-state: unverified
> to 10.1.43.2 via ge-0/0/0.0, Push 300080, Push 299936(top)
192.168.20.3:1:192.168.10.3/32
*[BGP/170] 1w4d 00:43:32, localpref 100, from 192.168.20.3
AS path: 65010 I, validation-state: unverified
> to 10.1.43.2 via ge-0/0/0.0, Push 300080, Push 299936(top)
inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
vpn-customer.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
user@PE4> show route protocol ldp
inet.0: 20 destinations, 20 routes (20 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
224.0.0.2/32 *[LDP/9] 1w4d 02:05:35, metric 1
MultiRecv
inet.3: 7 destinations, 7 routes (7 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
10.1.21.0/30 *[LDP/9] 1w4d 00:46:06, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Push 299888
10.1.32.0/30 *[LDP/9] 1w4d 00:45:23, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Push 299904
192.168.20.1/32 *[LDP/9] 1w4d 02:05:25, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Push 299824
192.168.20.2/32 *[LDP/9] 1w4d 00:45:23, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Push 299920
192.168.20.3/32 *[LDP/9] 1w4d 00:45:23, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Push 299936
192.168.20.12/32 *[LDP/9] 1w4d 02:05:25, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Push 299776
192.168.20.13/32 *[LDP/9] 1w4d 02:05:25, metric 1
> to 10.1.43.2 via ge-0/0/0.0
vpn-customer.inet.0: 5 destinations, 5 routes (5 active, 0 holddown, 0 hidden)
mpls.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
299776 *[LDP/9] 1w4d 02:05:25, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Pop
299776(S=0) *[LDP/9] 1w4d 02:05:25, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Pop
299792 *[LDP/9] 1w4d 02:05:25, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Swap 299776
299840 *[LDP/9] 1w4d 02:05:25, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Swap 299824
299904 *[LDP/9] 1w4d 00:46:06, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Swap 299888
299920 *[LDP/9] 1w4d 00:45:23, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Swap 299904
299936 *[LDP/9] 1w4d 00:45:23, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Swap 299920
299952 *[LDP/9] 1w4d 00:45:23, metric 1
> to 10.1.43.2 via ge-0/0/0.0, Swap 299936
bgp.l3vpn.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
vpn-customer.inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
Estado del enrutador CE4
user@CE4> show route protocol bgp
inet.0: 11 destinations, 11 routes (11 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
172.16.33.0/30 *[BGP/170] 1w4d 00:46:22, localpref 100
AS path: 65020 I, validation-state: unverified
> to 172.16.44.2 via ge-0/0/0.0
192.168.10.3/32 *[BGP/170] 1w4d 00:46:21, localpref 100
AS path: 65020 65020 I, validation-state: unverified
> to 172.16.44.2 via ge-0/0/0.0
inet6.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
user@CE4> show bgp summary
Threading mode: BGP I/O
Default eBGP mode: advertise - accept, receive - accept
Groups: 1 Peers: 1 Down peers: 0
Table Tot Paths Act Paths Suppressed History Damp State Pending
inet.0
2 2 0 0 0 0
Peer AS InPkt OutPkt OutQ Flaps Last Up/Dwn State|#Active/Received/Accepted/Damped...
172.16.44.2 65020 35346 35470 0 0 1w4d 2:00:25 Establ
inet.0: 2/2/2/0
user@CE4> ping 192.168.10.3 source 192.168.10.4 count 2
PING 192.168.10.3 (192.168.10.3): 56 data bytes
64 bytes from 192.168.10.3: icmp_seq=0 ttl=54 time=63.857 ms
64 bytes from 192.168.10.3: icmp_seq=1 ttl=54 time=19.586 ms
--- 192.168.10.3 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max/stddev = 19.586/41.721/63.857/22.135 ms