Beispiel: Konfigurieren von LDP für mehrere Instanzen
Die primäre LDP-Instanz wird auf Hierarchieebene [edit protocols]
konfiguriert.
Sie können eine bestimmte Instanz von LDP konfigurieren, indem Sie die ldp
Anweisung auf Hierarchieebene [edit routing-instances routing-instance-name protocols]
verwenden. Dadurch wird eine LDP-Instanz für die jeweilige VRF-Routinginstanz erstellt. Sie müssen alle erforderlichen VRF-Anweisungen angeben und Export- und Importrichtlinien auf Ihre LDP-Instanz anwenden, damit die Konfiguration ordnungsgemäß festgeschrieben wird.
Die meisten LDP-Hierarchieebenen, die in einer primären Instanz verfügbar sind, sind auch für bestimmte Instanzen von LDP verfügbar. Die no-forwarding
Option funktioniert jedoch nicht in einer VRF-basierten Instanz von LDP.

Abbildung 1 zeigt ein Beispiel für ein Carrier-of-Carriers-Netzwerk. CE3 und CE4 sind CE-Router für Endkunden, die sich in AS 65010 befinden. Der VPN-Anbieter in AS 65020 verfügt über drei Arten von Routern: PE3 und PE4 sind PE-Router, die eine Verbindung zum Endkunden herstellen, CE1 und CE2 fungieren als zwischengeschaltete Carrier-CE-Router und P2 und P3 sind interne Transit-Router. PE1 und PE2 in AS 65030 sind PE-Router, die den zwischengeschalteten VPN-Anbieter bedienen, und P0 und P1 sind Transitrouter für den Top-Tier-Netzbetreiber.
Damit diese Konfiguration funktioniert, müssen Sie drei Hauptaufgaben ausführen:
-
Konfigurieren Sie externes BGP zwischen der CE des VPN-Kunden und dem PE des VPN-Anbieters.
-
Konfigurieren Sie internes BGP mithilfe der VPN-Familie zwischen beiden PE-Routerpaaren (eine IBGP-Verbindung zwischen PE1 und PE2 und eine zweite IBGP-Verbindung zwischen Router PE3 und Router PE4).
-
Stellen Sie LDP- und Interior Gateway Protocol (IGP)-Verbindungen auf allen verbleibenden Verbindungen her. In diesem Beispiel wird OSPF als IGP verwendet, Sie können jedoch auch die IGP Ihrer Wahl verwenden.
Informationen, die dieses LDP-Beispiel für mehrere Carrier-of-Carrier-Instanzen unterstützen, sind in Tabelle 1zusammengefasst.
Verbindung |
Protokolle |
---|---|
CE3 - PE3 |
EBGP-Familie inet |
PE3 - P2 - CE1 |
OSPF und LDP |
CE1 - PE1 |
OSPF und LDP |
PE1 - P0 - P1 - PE2 |
OSPF und LDP |
PE1 - PE2 |
IBGP-Familie inet-vpn |
PE2 - CE2 |
OSPF und LDP |
CE2 - P3 - PE4 |
OSPF und LDP |
PE4 - CE4 |
EBGP-Familie inet |
PE3 - PE4 |
IBGP-Familie inet-vpn |
Ihre Konfigurationsaufgaben beginnen bei Router CE3 und bewegen sich Router für Router durch den ersten Teil des VPN-Provider-Netzwerks, in den Carrier-AS, durch den zweiten VPN-Provider-Cluster von AS 65020 und enden beim zweiten VPN-Kunden-Router CE4.
Da Router CE3 der erste Kundenrouter ist, konfigurieren Sie EBGP zwischen Router CE3 und dem verbundenen VPN-Anbieter Router PE3. Außerdem müssen Sie Ihre Loopback-Adresse im BGP mit einer Routing-Richtlinie ankündigen, um die IP-Erreichbarkeit mit Router CE4 zu ermöglichen.
Router 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
Auf Router PE3 sind die Konfigurationsaufgaben aufwändiger. Sie müssen die EBGP-Verbindung zu Router CE3 in einer VRF-Instanz herstellen, MPLS und LDP auf der Schnittstelle aktivieren, die auf den VPN-Anbieter-Router CE1 zeigt, und eine primäre Instanz von IBGP so konfigurieren, dass sie Router PE4 am äußersten Rand von AS 65020 erreicht.
Richten Sie abschließend eine ausgehende VRF-Richtlinie ein, die den gesamten BGP-Datenverkehr und direkt verbundene Schnittstellen in einer BGP-Community platziert, sowie eine eingehende VRF-Richtlinie, die ähnlichen BGP-Community-Datenverkehr vom Router PE4 akzeptiert.
Router 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
Aktivieren Sie auf Router P2 LDP und die IGP, die für den Transport von Etiketten verwendet wird (in diesem Fall OSPF). Sie wiederholen diese Aufgaben auf allen Transit-Core-Routern, sowohl im Netzwerk des VPN-Anbieters als auch im Netzwerk des Core-Netzbetreibers.
Router 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
Konfigurieren Sie LDP und OSPF für Router CE1 auf die gleiche Weise, wie Sie Router P2 konfiguriert haben.
Router 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
Konfigurieren Sie auf dem Core-Carrier-Router PE1 eine primäre Instanz für OSPF, LDP, MPLS und IBGP (mit der family inet-vpn
Option), um den Router mit dem benachbarten Router PE2 zu verbinden. Implementieren Sie als Nächstes LDP mit mehreren Instanzen, indem Sie eine sekundäre Instanz einrichten. Aktivieren Sie in diesem Fall LDP und OSPF, damit Router PE1 mit Router CE1 kommunizieren kann. MPLS ist in der sekundären Instanz nicht erforderlich.
Richten Sie abschließend eine ausgehende VRF-Richtlinie ein, die den gesamten LDP-Datenverkehr von Router CE1 in eine BGP-Community leitet, eine Exportrichtlinie, die diesen Community-Datenverkehr an Router PE2 sendet, und eine eingehende VRF-Richtlinie, die ähnlichen BGP-Community-Datenverkehr von Router PE2 akzeptiert. Bei diesem Schritt wird der LDP-Datenverkehr des VPN-Anbieters in die BGP-Sitzung des Netzbetreibers getunnelt.
Router 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
Aktivieren Sie LDP und OSPF auf Router P0 auf die gleiche Weise, wie Sie diese Protokolle auf Router P2 konfiguriert haben. Wiederholen Sie diese Aufgaben auf Router P1 und Router P3.
Router 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
Aktivieren Sie auf Router P1 LDP und die IGP, die für den Transport von Etiketten verwendet wird (in diesem Fall OSPF).
Router 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
Der Core-Carrier Router PE2 ist ein Spiegelbild des Router PE1. Konfigurieren Sie zunächst eine primäre Instance für OSPF, LDP, MPLS und IBGP (mit der Option), um Router PE2 mit dem family inet-vpn
benachbarten Router PE1 zu verbinden. Implementieren Sie als Nächstes LDP mit mehreren Instanzen, indem Sie eine sekundäre Instanz einrichten. Aktivieren Sie in diesem Fall LDP und OSPF, damit Router PE2 mit Router CE2 kommunizieren kann. MPLS ist in der sekundären Instanz nicht erforderlich.
Richten Sie abschließend eine ausgehende VRF-Richtlinie ein, die den gesamten LDP-Datenverkehr von Router CE2 in eine BGP-Community leitet, eine Exportrichtlinie, die diesen Community-Datenverkehr an Router PE1 sendet, und eine eingehende VRF-Richtlinie, die ähnlichen BGP-Community-Datenverkehr von Router PE1 akzeptiert. Bei diesem Schritt wird der LDP-Datenverkehr des VPN-Anbieters in die BGP-Sitzung des Netzbetreibers getunnelt.
Router 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
Konfigurieren Sie für Router CE2 LDP und OSPF wie auf Router CE1 und den Transit-P-Routern.
Router 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
Da es sich bei Router P3 um einen weiteren Core-Provider-Router handelt, sollten Sie LDP und OSPF auf allen Transitschnittstellen aktivieren.
Router 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
Schließen Sie auf Router PE4 die auf Router PE3 initiierte IBGP-Verbindung ab, um die Edge-Router in AS 65020 zu verbinden. Aktivieren Sie außerdem LDP und MPLS auf der Schnittstelle, die auf den Router CE2 des VPN-Anbieters verweist, und stellen Sie mithilfe einer VRF-Instanz eine EBGP-Verbindung zu Router CE4 her.
Richten Sie abschließend eine ausgehende VRF-Richtlinie ein, die den gesamten BGP-Datenverkehr und direkt verbundene Schnittstellen in einer BGP-Community platziert, und eine eingehende VRF-Richtlinie, die ähnlichen BGP-Community-Datenverkehr vom Router PE3 akzeptiert.
Router 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
Router CE4 ist der Ziel-VPN-Kundenrouter. Konfigurieren Sie EBGP zwischen Router CE4 und dem verbundenen VPN-Anbieter Router PE4, um die Konfiguration abzuschließen. Denken Sie daran, die Loopback-Adresse im BGP anzukündigen, indem Sie eine Routing-Richtlinie verwenden, um die IP-Erreichbarkeit mit Router CE3 zu ermöglichen.
Router 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
Verifizieren Ihrer Arbeit
Verwenden Sie die folgenden Befehle, um den ordnungsgemäßen Betrieb Ihrer LDP-Konfiguration mit mehreren Instanzen zu überprüfen:
-
show ldp database
-
show ldp interface
-
show ldp neighbor
-
show ldp path
-
show ldp route
-
show ldp session
-
show ldp statistics
Die Anzeigeausgabe für diese Befehle ist bis auf einen Unterschied die gleiche wie in früheren Junos OS-Versionen. Ein Instanzname kann nun als Argument verwendet werden.
Wenn Sie diesen Befehlen einen Instanznamen beifügen, werden Informationen für die angegebene LDP-Instanz angezeigt. Beispielsweise zeigt der Befehl show ldp neighbor instance crockett
alle LDP-Nachbarn für eine VRF-Instanz mit dem Namen crockett
. Umgekehrt werden ohne Instanznamen die LDP-Nachbarn angezeigt, show ldp neighbor
die der primären Instanz zugeordnet sind.
Die folgenden Abschnitte zeigen die Ausgabe dieser Befehle, die mit dem Konfigurationsbeispiel verwendet werden:
- Router CE3-Status
- Router PE3-Status
- Router CE1-Status
- Router PE1-Status
- Router PE2-Status
- Router CE2-Status
- Router PE4-Status
- Router CE4-Status
Router CE3-Status
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
Router PE3-Status
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)
Router CE1-Status
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
Router PE1-Status
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
Router PE2-Status
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
Router CE2-Status
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
Router PE4-Status
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)
Router CE4-Status
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