Exemple : Configuration de LDP multi-instance
L’instance LDP principale est configurée au niveau de la [edit protocols]
hiérarchie.
Vous pouvez configurer une instance spécifique de LDP à l’aide de l’instruction ldp
au niveau de la [edit routing-instances routing-instance-name protocols]
hiérarchie. Cela crée une instance de LDP pour l’instance de routage VRF particulière. Vous devez spécifier toutes les instructions VRF requises et appliquer des stratégies d’exportation et d’importation à votre instance LDP pour que la configuration soit validée correctement.
La plupart des niveaux hiérarchiques LDP disponibles dans une instance principale sont également disponibles pour des instances spécifiques de LDP. Toutefois, l’option no-forwarding
ne fonctionne pas dans une instance VRF de LDP.
Figure 1 montre un exemple de réseau de porte-of-carriers. Les routeurs CE3 et CE4 sont des routeurs CE du client final résidant dans la norme AS 65010. Le fournisseur VPN de l’AS 65020 dispose de trois types de routeurs : PE3 et PE4 sont des routeurs PE qui se connectent au client final, CE1 et CE2 agissent comme des routeurs CE porteurs intermédiaires, et P2 et P3 sont des routeurs de transit interne. PE1 et PE2 dans l’AS 65030 sont des routeurs PE desservant le fournisseur VPN intermédiaire, tandis que P0 et P1 sont des routeurs de transit pour l’opérateur de niveau supérieur.
Pour que cette configuration fonctionne, vous devez effectuer trois tâches principales :
-
Configurez le BGP externe entre le client VPN CE et le fournisseur VPN PE.
-
Configurez le BGP interne à l’aide de la famille VPN entre les deux paires de routeurs PE (une connexion IBGP entre PE1 et PE2 et une seconde connexion IBGP entre le routeur PE3 et le routeur PE4).
-
Établissez des connexions LDP et IGP (Interior Gateway Protocol) sur toutes les liaisons restantes. Cet exemple utilise OSPF comme IGP, mais vous pouvez utiliser l’IGP de votre choix.
Les informations à l’appui de cet exemple de LDP multi-instance de porteuse sont résumées dans Tableau 1.
Connexion |
Protocoles |
---|---|
CE3 - PE3 |
Entrée de la famille EBGP |
PE3 - P2 - CE1 |
OSPF et LDP |
CE1 - PE1 |
OSPF et LDP |
PE1 - P0 - P1 - PE2 |
OSPF et LDP |
PE1 - PE2 |
Famille IBGP inet-vpn |
PE2 - CE2 |
OSPF et LDP |
CE2 - P3 - PE4 |
OSPF et LDP |
PE4 - CE4 |
Entrée de la famille EBGP |
PE3 - PE4 |
Famille IBGP inet-vpn |
Vos tâches de configuration commencent au niveau du routeur CE3 et se déplacent routeur par routeur à travers la première partie du réseau du fournisseur VPN, dans l’AS opérateur, à travers le deuxième cluster de fournisseurs VPN de l’AS 65020, et se terminent au deuxième routeur client VPN CE4.
Étant donné que le routeur CE3 est le premier routeur client, configurez EBGP entre le routeur CE3 et le routeur PE3 du fournisseur VPN connecté. Vous devez également annoncer votre adresse de bouclage dans BGP avec une stratégie de routage pour permettre l’accessibilité IP avec le routeur CE4.
Routeur 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
Sur le routeur PE3, les tâches de configuration sont plus complexes. Vous devez terminer la connexion EBGP au routeur CE3 dans une instance VRF, activer MPLS et LDP sur l’interface pointant vers le routeur CE1 du fournisseur VPN et configurer une instance primaire d’IBGP pour atteindre le routeur PE4 à l’extrémité de l’AS 65020.
Enfin, configurez une stratégie VRF sortante qui place tout le trafic BGP et les interfaces directement connectées dans une communauté BGP, ainsi qu’une stratégie VRF entrante qui accepte un trafic communautaire BGP similaire provenant du routeur PE4.
Routeur 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
Sur le routeur P2, activez LDP et l’IGP utilisé pour le transport des étiquettes (dans ce cas, OSPF). Vous allez répéter ces tâches sur tous les routeurs centraux de transit, à la fois dans le réseau du fournisseur VPN et dans le réseau central de l’opérateur.
Routeur 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
Pour le routeur CE1, configurez LDP et OSPF de la même manière que vous avez configuré le routeur P2.
Routeur 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
Sur le routeur PE1 de la porteuse principale, configurez une instance principale pour OSPF, LDP, MPLS et IBGP (avec l’option family inet-vpn
) pour connecter le routeur au routeur PE2 voisin. Ensuite, implémentez le protocole LDP multi-instance en établissant une instance secondaire. Activez LDP et OSPF dans cette instance pour que le routeur PE1 puisse communiquer avec le routeur CE1. MPLS n’est pas requis dans l’instance secondaire.
Enfin, configurez une stratégie VRF sortante qui place tout le trafic LDP provenant du routeur CE1 dans une communauté BGP, une stratégie d’exportation qui envoie ce trafic communautaire vers le routeur PE2 et une stratégie VRF entrante qui accepte un trafic communautaire BGP similaire à partir du routeur PE2. Cette étape consiste à tunneliser le trafic LDP du fournisseur VPN vers la session BGP de l’opérateur.
Routeur 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
Sur le routeur P0, activez LDP et OSPF de la même manière que vous avez configuré ces protocoles sur le routeur P2. Vous allez répéter ces tâches sur les routeurs P1 et P3.
Routeur 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
Sur le routeur P1, activez LDP et l’IGP utilisé pour le transport des étiquettes (OSPF dans ce cas).
Routeur 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
La porteuse principale du routeur PE2 est une image miroir du routeur PE1. Tout d’abord, configurez une instance principale pour OSPF, LDP, MPLS et IBGP (avec l’option) pour connecter le family inet-vpn
routeur PE2 au routeur PE1 voisin. Ensuite, implémentez le protocole LDP multi-instance en établissant une instance secondaire. Activez LDP et OSPF dans cette instance pour que le routeur PE2 puisse communiquer avec le routeur CE2. MPLS n’est pas requis dans l’instance secondaire.
Enfin, configurez une stratégie VRF sortante qui place tout le trafic LDP provenant du routeur CE2 dans une communauté BGP, une stratégie d’exportation qui envoie ce trafic communautaire vers le routeur PE1 et une stratégie VRF entrante qui accepte un trafic communautaire BGP similaire à partir du routeur PE1. Cette étape consiste à tunneliser le trafic LDP du fournisseur VPN vers la session BGP de l’opérateur.
Routeur 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
Pour le routeur CE2, configurez LDP et OSPF comme vous l’avez fait sur le routeur CE1 et les routeurs de transit P.
Routeur 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
Étant donné que le routeur P3 est un autre routeur du fournisseur principal, activez LDP et OSPF sur toutes les interfaces de transit.
Routeur 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
Sur le routeur PE4, terminez la connexion IBGP initiée sur le routeur PE3 pour connecter les routeurs de périphérie dans l’AS 65020. Activez également LDP et MPLS sur l’interface pointant vers le routeur CE2 du fournisseur VPN et établissez une connexion EBGP au routeur CE4 à l’aide d’une instance VRF.
Enfin, configurez une stratégie VRF sortante qui place tout le trafic BGP et les interfaces directement connectées dans une communauté BGP, ainsi qu’une stratégie VRF entrante qui accepte le trafic similaire de la communauté BGP provenant du routeur PE3.
Routeur 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
Le routeur CE4 est le routeur client VPN de destination. Configurez EBGP entre le routeur CE4 et le routeur PE4 du fournisseur VPN connecté pour terminer la configuration. N’oubliez pas d’annoncer l’adresse de bouclage dans BGP en utilisant une stratégie de routage pour permettre l’accessibilité IP avec le routeur CE3.
Routeur 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
Vérification de votre travail
Pour vérifier le bon fonctionnement de votre configuration LDP multi-instance, utilisez les commandes suivantes :
-
show ldp database
-
show ldp interface
-
show ldp neighbor
-
show ldp path
-
show ldp route
-
show ldp session
-
show ldp statistics
La sortie d’affichage de ces commandes est identique à celle des versions précédentes de Junos OS, à une différence près. Un nom d’instance peut désormais être utilisé comme argument.
Si vous incluez un nom d’instance avec ces commandes, vous affichez les informations de l’instance LDP spécifiée. Par exemple, la commande show ldp neighbor instance crockett
affiche tous les voisins LDP d’une instance VRF nommée crockett
. À l’inverse, sans nom d’instance, show ldp neighbor
les voisins LDP associés à l’instance principale s’affichent.
Les sections suivantes montrent la sortie de ces commandes utilisées avec l’exemple de configuration :
- État du routeur CE3
- État du routeur PE3
- État du routeur CE1
- État du routeur PE1
- État PE2 du routeur
- État du routeur CE2
- État du routeur PE4
- État du routeur CE4
État du routeur 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
État du routeur PE3
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)
État du routeur 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
État du routeur PE1
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
État PE2 du routeur
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
État du routeur 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
État du routeur PE4
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)
État du routeur 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