NESTA PÁGINA
Exemplo: configurar a interoperação VPLS baseada em H-VPLS e baseada em LDP
Este exemplo mostra como configurar o serviço hierárquico de LAN privada virtual (H-VPLS) em um cenário que usa VPLS baseado em LDP e VPLS baseado em BGP interoperando em uma implantação multihoming. Esse cenário é útil quando uma implantação do cliente tem os dois tipos diferentes de VPLS em uso, e você precisa integrá-los. Outro exemplo é quando o ISP-A está executando VPLS e ISP-B baseados em BGP está executando o VPLS baseado em LDP, e os dois ISPs estão fundindo suas redes.
Requisitos
Nenhuma configuração especial além da inicialização do dispositivo é necessária antes de configurar este exemplo.
Visão geral
Neste exemplo, o Device PE2 e o Device PE3 estão atuando como roteadores de borda de provedores de internet (PE) com base em BGP, bem como terminação de VPLS baseada em LDP.
Os dispositivos neste exemplo têm as seguintes funções:
BGP VPLS apenas PE — Dispositivo PE1
LDP VPLS apenas PE — Dispositivo PE4
BGP-LDP VPLS PE — Dispositivo PE2 e Dispositivo PE3
A Figura 1 mostra a topologia usada neste exemplo.
Figura 1: H-VPLS com interoperação VPLS baseada em LDP e BGP
Do dispositivo PE4, o pseudowire ao dispositivo PE3 é o caminho principal ou de trabalho. O pseudowire Device PE2 é o caminho de backup.
A configuração rápida da CLI mostra a configuração para todos os dispositivos da Figura 1. O procedimento passo a passo da seção descreve as etapas do Dispositivo PE1, Dispositivo PE2 e Dispositivo PE4.
Configuração
Procedimento
- Configuração rápida da CLI
- Procedimento passo a passo
- Procedimento passo a passo
- Procedimento passo a passo
- Resultados
Configuração rápida da CLI
Para configurar rapidamente este exemplo, copie os seguintes comandos, cole-os em um arquivo de texto, remova quaisquer quebras de linha, altere os detalhes necessários para combinar com a configuração de sua rede e, em seguida, copie e cole os comandos na CLI no nível de [edit] hierarquia.
Dispositivo PE1
set interfaces ge-2/0/5 encapsulation ethernet-vpls set interfaces ge-2/0/5 unit 0 description to_CE1 set interfaces ge-2/0/5 unit 0 family vpls set interfaces fe-2/0/9 unit 0 description to_PE2 set interfaces fe-2/0/9 unit 0 family inet address 10.10.3.1/30 set interfaces fe-2/0/9 unit 0 family mpls set interfaces fe-2/0/10 unit 0 description to_PE3 set interfaces fe-2/0/10 unit 0 family inet address 10.10.1.1/30 set interfaces fe-2/0/10 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.0.2.1/24 set protocols mpls interface fe-2/0/10.0 set protocols mpls interface fe-2/0/9.0 set protocols ldp interface fe-2/0/10.0 set protocols ldp interface fe-2/0/9.0 set protocols ldp interface lo0.0 set protocols bgp group internal-peers type internal set protocols bgp group internal-peers local-address 192.0.2.1 set protocols bgp group internal-peers family l2vpn signaling set protocols bgp group internal-peers neighbor 192.0.2.2 set protocols bgp group internal-peers neighbor 192.0.2.3 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface fe-2/0/10.0 set protocols ospf area 0.0.0.0 interface fe-2/0/9.0 set routing-instances h-vpls-PE1 instance-type vpls set routing-instances h-vpls-PE1 interface ge-2/0/5.0 set routing-instances h-vpls-PE1 route-distinguisher 1:1 set routing-instances h-vpls-PE1 vrf-target target:1:1 set routing-instances h-vpls-PE1 protocols vpls interface ge-2/0/5.0 set routing-instances h-vpls-PE1 protocols vpls site PE1-vpls site-identifier 2 set routing-options autonomous-system 64510
Pe2 do dispositivo
set interfaces ge-2/0/6 encapsulation ethernet-vpls set interfaces ge-2/0/6 unit 0 description to_CE2 set interfaces ge-2/0/6 unit 0 family vpls set interfaces fe-2/0/8 unit 0 description to_PE3 set interfaces fe-2/0/8 unit 0 family inet address 10.10.4.2/30 set interfaces fe-2/0/8 unit 0 family mpls set interfaces fe-2/0/9 unit 0 description to_PE4 set interfaces fe-2/0/9 unit 0 family inet address 10.10.5.1/30 set interfaces fe-2/0/9 unit 0 family mpls set interfaces fe-2/0/10 unit 0 description to_PE1 set interfaces fe-2/0/10 unit 0 family inet address 10.10.3.2/30 set interfaces fe-2/0/10 unit 0 family mpls set interfaces lo0 unit 0 family inet address 192.0.2.2/24 set protocols mpls interface fe-2/0/10.0 set protocols mpls interface fe-2/0/9.0 set protocols mpls interface fe-2/0/8.0 set protocols ldp interface fe-2/0/10.0 set protocols ldp interface fe-2/0/9.0 set protocols ldp interface fe-2/0/8.0 set protocols ldp interface lo0.0 set protocols bgp group ibgp type internal set protocols bgp group ibgp local-address 192.0.2.2 set protocols bgp group ibgp family l2vpn signaling set protocols bgp group ibgp neighbor 192.0.2.3 set protocols bgp group ibgp neighbor 192.0.2.1 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface fe-2/0/10.0 set protocols ospf area 0.0.0.0 interface fe-2/0/9.0 set protocols ospf area 0.0.0.0 interface fe-2/0/8.0 set routing-instances h-vpls-PE2 instance-type vpls set routing-instances h-vpls-PE2 interface ge-2/0/6.0 set routing-instances h-vpls-PE2 route-distinguisher 1:2 set routing-instances h-vpls-PE2 vrf-target target:1:1 set routing-instances h-vpls-PE2 protocols vpls interface ge-2/0/6.0 set routing-instances h-vpls-PE2 protocols vpls site PE2-vpls site-identifier 1 set routing-instances h-vpls-PE2 protocols vpls site PE2-vpls multi-homing set routing-instances h-vpls-PE2 protocols vpls site PE2-vpls mesh-group h-vpls-PE2 set routing-instances h-vpls-PE2 protocols vpls vpls-id 100 set routing-instances h-vpls-PE2 protocols vpls mesh-group h-vpls-PE2 vpls-id 100 set routing-instances h-vpls-PE2 protocols vpls mesh-group h-vpls-PE2 local-switching set routing-instances h-vpls-PE2 protocols vpls mesh-group h-vpls-PE2 neighbor 192.0.2.4 set routing-options autonomous-system 64510
Dispositivo PE3
set interfaces fe-2/0/8 unit 0 description to_PE2 set interfaces fe-2/0/8 unit 0 family inet address 10.10.4.1/30 set interfaces fe-2/0/8 unit 0 family mpls set interfaces fe-2/0/9 unit 0 description to_PE4 set interfaces fe-2/0/9 unit 0 family inet address 10.10.6.1/30 set interfaces fe-2/0/9 unit 0 family mpls set interfaces fe-2/0/10 unit 0 description to_PE1 set interfaces fe-2/0/10 unit 0 family inet address 10.10.1.2/30 set interfaces fe-2/0/10 unit 0 family mpls set interfaces ge-2/1/3 encapsulation ethernet-vpls set interfaces ge-2/1/3 unit 0 description to_CE3 set interfaces ge-2/1/3 unit 0 family vpls set interfaces lo0 unit 0 family inet address 192.0.2.3/24 set protocols mpls interface fe-2/0/10.0 set protocols mpls interface fe-2/0/8.0 set protocols mpls interface fe-2/0/9.0 set protocols ldp interface fe-2/0/10.0 set protocols ldp interface fe-2/0/9.0 set protocols ldp interface fe-2/0/8.0 set protocols ldp interface lo0.0 set protocols bgp group internal-peers type internal set protocols bgp group internal-peers local-address 192.0.2.3 set protocols bgp group internal-peers family l2vpn signaling set protocols bgp group internal-peers neighbor 192.0.2.2 set protocols bgp group internal-peers neighbor 192.0.2.1 set protocols ospf traffic-engineering set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface fe-2/0/10.0 set protocols ospf area 0.0.0.0 interface fe-2/0/8.0 set protocols ospf area 0.0.0.0 interface fe-2/0/9.0 set routing-instances h-vpls-PE3 instance-type vpls set routing-instances h-vpls-PE3 interface ge-2/1/3.0 set routing-instances h-vpls-PE3 route-distinguisher 1:3 set routing-instances h-vpls-PE3 vrf-target target:1:1 set routing-instances h-vpls-PE3 protocols vpls interface ge-2/1/3.0 set routing-instances h-vpls-PE3 protocols vpls site PE3-vpls site-identifier 1 set routing-instances h-vpls-PE3 protocols vpls site PE3-vpls multi-homing set routing-instances h-vpls-PE3 protocols vpls site PE3-vpls mesh-group h-vpls-PE3 set routing-instances h-vpls-PE3 protocols vpls vpls-id 100 set routing-instances h-vpls-PE3 protocols vpls mesh-group h-vpls-PE3 vpls-id 100 set routing-instances h-vpls-PE3 protocols vpls mesh-group h-vpls-PE3 local-switching set routing-instances h-vpls-PE3 protocols vpls mesh-group h-vpls-PE3 neighbor 192.0.2.4 set routing-options autonomous-system 64510
Dispositivo PE4
set interfaces fe-2/0/9 unit 0 description to_PE3 set interfaces fe-2/0/9 unit 0 family inet address 10.10.6.2/30 set interfaces fe-2/0/9 unit 0 family mpls set interfaces fe-2/0/10 unit 0 description to_PE2 set interfaces fe-2/0/10 unit 0 family inet address 10.10.5.2/30 set interfaces fe-2/0/10 unit 0 family mpls set interfaces ge-2/1/7 encapsulation ethernet-vpls set interfaces ge-2/1/7 unit 0 description to_CE4 set interfaces ge-2/1/7 unit 0 family vpls set interfaces lo0 unit 0 family inet address 192.0.2.4/24 set protocols mpls interface fe-2/0/10.0 set protocols mpls interface fe-2/0/9.0 set protocols ldp interface fe-2/0/10.0 set protocols ldp interface fe-2/0/9.0 set protocols ldp interface lo0.0 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface fe-2/0/10.0 set protocols ospf area 0.0.0.0 interface fe-2/0/9.0 set routing-instances ldp-vpls instance-type vpls set routing-instances ldp-vpls interface ge-2/1/7.0 set routing-instances ldp-vpls protocols vpls vpls-id 100 set routing-instances ldp-vpls protocols vpls neighbor 192.0.2.3 set routing-instances ldp-vpls protocols vpls neighbor 192.0.2.2
Dispositivo CE1
set interfaces ge-2/0/8 unit 0 description to_PE1 set interfaces ge-2/0/8 unit 0 family inet address 172.16.0.1/24 set interfaces lo0 unit 0 family inet address 10.255.14.214/32 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-2/0/8.0
Dispositivo CE2
set interfaces ge-2/1/5 unit 0 description to_PE2 set interfaces ge-2/1/5 unit 0 family inet address 172.16.0.2/24 set interfaces lo0 unit 0 family inet address 10.255.14.215/32 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-2/1/5.0
Dispositivo CE3
set interfaces ge-2/0/9 unit 0 description to_PE3 set interfaces ge-2/0/9 unit 0 family inet address 172.16.0.3/24 set interfaces lo0 unit 0 family inet address 10.255.14.218/32 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-2/0/9.0
Dispositivo CE4
set interfaces ge-2/1/6 unit 0 description to_PE4 set interfaces ge-2/1/6 unit 0 family inet address 172.16.0.4/24 set interfaces lo0 unit 0 family inet address 10.255.14.219/32 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface ge-2/1/6.0
Procedimento passo a passo
O exemplo a seguir exige que você navegue por vários níveis na hierarquia de configuração. Para obter informações sobre como navegar pela CLI, consulte o uso do Editor de CLI no modo de configuração no guia de usuário da CLI.
Para configurar o dispositivo VPLS PE baseado em BGP:
-
Configure as interfaces.
Na interface do dispositivo que se conecta à borda do cliente, habilite o encapsulamento VPLS e a família de endereços VPLS.
Nas interfaces voltadas para o núcleo, habilite rótulos MPLS.
[edit interfaces] user@PE1# set ge-2/0/5 encapsulation ethernet-vpls user@PE1# set ge-2/0/5 unit 0 description to_CE1 user@PE1# set ge-2/0/5 unit 0 family vpls user@PE1# set fe-2/0/10 unit 0 description to_PE3 user@PE1# set fe-2/0/10 unit 0 family inet address 10.10.1.1/30 user@PE1# set fe-2/0/10 unit 0 family mpls user@PE1# set fe-2/0/9 unit 0 description to_PE2 user@PE1# set fe-2/0/9 unit 0 family inet address 10.10.3.1/30 user@PE1# set fe-2/0/9 unit 0 family mpls user@PE1# set lo0 unit 0 family inet address 192.0.2.1/24
-
Habilite MPLS e LDP nas interfaces.
Nas interfaces de dispositivo MTU que se conectam a outros dispositivos PE, configure MPLS e LDP.
[edit protocols mpls] user@PE1# set interface fe-2/0/10.0 user@PE1# set interface fe-2/0/9.0 [edit protocols ldp ] user@PE1# set interface fe-2/0/10.0 user@PE1# set interface fe-2/0/9.0 user@PE1# set interface lo0.0
-
Habilite o roteamento nas interfaces.
Nas interfaces de dispositivo MTU que se conectam a outros dispositivos PE, configure um protocolo de gateway interior (IGP), como OSPF ou IS-IS.
[edit protocols ospf area 0.0.0.0] user@PE1# set interface lo0.0 passive user@PE1# set interface fe-2/0/10.0 user@PE1# set interface fe-2/0/9.0
-
Configure o BGP com a sinalização de VPN de Camada 2.
A
l2vpn signalingdeclaração permite o suporte para anúncios de VPN de VPLS e Camada 2 sob as mesmas informações de alcance da camada de rede (NLRI).A malha completa interna do IBGP (IBGP) inclui Dispositivo PE1, Dispositivo PE2 e Dispositivo PE3. O dispositivo PE4 não está incluído.
[edit protocols bgp group internal-peers] user@PE1# set type internal user@PE1# set local-address 192.0.2.1 user@PE1# set family l2vpn signaling user@PE1# set neighbor 192.0.2.2 user@PE1# set neighbor 192.0.2.3
-
Configure a instância de roteamento VPLS.
Como se trata de VPLS baseado em BGP, inclua um diferencial de rota, um alvo VRF e um nome do site e ID.
[edit routing-instances h-vpls-PE1] user@PE1# set instance-type vpls user@PE1# set interface ge-2/0/5.0 user@PE1# set route-distinguisher 1:1 user@PE1# set vrf-target target:1:1 [edit routing-instances h-vpls-PE1 protocols vpls] user@PE1# set interface ge-2/0/5.0 user@PE1# set site PE1-vpls site-identifier 2
-
Configure o número do sistema autônomo (AS).
[edit routing-options] user@PE1# set autonomous-system 64510
Procedimento passo a passo
O exemplo a seguir exige que você navegue por vários níveis na hierarquia de configuração. Para obter informações sobre como navegar pela CLI, consulte o uso do Editor de CLI no modo de configuração no guia de usuário da CLI.
Para configurar o dispositivo VPLS PE baseado em BGP-LDP:
Configure as interfaces.
Na interface de dispositivo PE-r que se conecta à borda do cliente, configure um dos tipos de encapsulamento VPLS e a família de endereços VPLS. Isso permite o VPLS.
Nas interfaces voltadas para o núcleo, habilite rótulos MPLS.
[edit interfaces] user@PE2# set ge-2/0/6 encapsulation ethernet-vpls user@PE2# set ge-2/0/6 unit 0 description to_CE2 user@PE2# set ge-2/0/6 unit 0 family vpls user@PE2# set fe-2/0/10 unit 0 description to_PE1 user@PE2# set fe-2/0/10 unit 0 family inet address 10.10.3.2/30 user@PE2# set fe-2/0/10 unit 0 family mpls user@PE2# set fe-2/0/9 unit 0 description to_PE4 user@PE2# set fe-2/0/9 unit 0 family inet address 10.10.5.1/30 user@PE2# set fe-2/0/9 unit 0 family mpls user@PE2# set fe-2/0/8 unit 0 description to_PE3 user@PE2# set fe-2/0/8 unit 0 family inet address 10.10.4.2/30 user@PE2# set fe-2/0/8 unit 0 family mpls user@PE2# set lo0 unit 0 family inet address 192.0.2.2/24
Habilite MPLS e LDP nas interfaces.
Nas interfaces de dispositivo MTU que se conectam a outros dispositivos PE, configure MPLS e LDP.
[edit protocols mpls] user@PE2# set interface fe-2/0/10.0 user@PE2# set interface fe-2/0/9.0 user@PE2# set interface fe-2/0/8.0 [edit protocols ldp] user@PE2# set interface fe-2/0/10.0 user@PE2# set interface fe-2/0/9.0 user@PE2# set interface fe-2/0/8.0 user@PE2# set interface lo0.0
Habilite o roteamento nas interfaces.
Nas interfaces de dispositivo MTU que se conectam a outros dispositivos PE, configure um protocolo de gateway interior (IGP), como OSPF ou IS-IS.
[edit protocols ospf area 0.0.0.0] user@PE2# set interface lo0.0 passive user@PE2# set interface fe-2/0/10.0 user@PE2# set interface fe-2/0/9.0 user@PE2# set interface fe-2/0/8.0
[edit protocols bgp group ibgp] user@PE2# set type internal user@PE2# set local-address 192.0.2.2 user@PE2# set family l2vpn signaling user@PE2# set neighbor 192.0.2.3 user@PE2# set neighbor 192.0.2.1
Configure VPLS.
A
vpls-iddeclaração permite a sinalização de LDP para a instância VPLS.[edit routing-instances h-vpls-PE2] user@PE2# set instance-type vpls user@PE2# set interface ge-2/0/6.0 user@PE2# set route-distinguisher 1:2 user@PE2# set vrf-target target:1:1 [edit routing-instances h-vpls-PE2 protocols vpls] user@PE2# set interface ge-2/0/6.0 user@PE2# set site PE2-vpls site-identifier 1 user@PE2# set site PE2-vpls multi-homing user@PE2# set site PE2-vpls mesh-group h-vpls-PE2 user@PE2# set vpls-id 100 user@PE2# set mesh-group h-vpls-PE2 vpls-id 100 user@PE2# set mesh-group h-vpls-PE2 local-switching user@PE2# set mesh-group h-vpls-PE2 neighbor 192.0.2.4
[edit routing-options] user@PE2# set autonomous-system 64510
Procedimento passo a passo
O exemplo a seguir exige que você navegue por vários níveis na hierarquia de configuração. Para obter informações sobre como navegar pela CLI, consulte o uso do Editor de CLI no modo de configuração no guia de usuário da CLI.
Para configurar o dispositivo VPLS PE baseado em LDP:
Configure as interfaces.
Na interface de dispositivo PE-r que se conecta à borda do cliente, configure um dos tipos de encapsulamento VPLS e a família de endereços VPLS. Isso permite o VPLS.
Nas interfaces voltadas para o núcleo, habilite rótulos MPLS.
[edit interfaces] user@PE4# set fe-2/0/10 unit 0 description to_PE2 user@PE4# set fe-2/0/10 unit 0 family inet address 10.10.5.2/30 user@PE4# set fe-2/0/10 unit 0 family mpls user@PE4# set fe-2/0/9 unit 0 description to_PE3 user@PE4# set fe-2/0/9 unit 0 family inet address 10.10.6.2/30 user@PE4# set fe-2/0/9 unit 0 family mpls user@PE4# set ge-2/1/7 encapsulation ethernet-vpls user@PE4# set ge-2/1/7 unit 0 description to_CE4 user@PE4# set ge-2/1/7 unit 0 family vpls user@PE4# set lo0 unit 0 family inet address 192.0.2.4/24
Habilite MPLS e LDP nas interfaces.
Nas interfaces de dispositivo MTU que se conectam a outros dispositivos PE, configure MPLS e LDP.
[edit protocols mpls] user@PE4# set interface fe-2/0/10.0 user@PE4# set interface fe-2/0/9.0 [edit protocols ldp] user@PE4# set interface fe-2/0/10.0 user@PE4# set interface fe-2/0/9.0 user@PE4# set interface lo0.0
Habilite o roteamento nas interfaces.
Nas interfaces de dispositivo MTU que se conectam a outros dispositivos PE, configure um protocolo de gateway interior (IGP), como OSPF ou IS-IS.
[edit protocols ospf area 0.0.0.0] user@PE4# set interface lo0.0 passive user@PE4# set interface fe-2/0/10.0 user@PE4# set interface fe-2/0/9.0
Configure VPLS.
A
vpls-iddeclaração permite a sinalização de LDP para a instância VPLS.[edit routing-instances ldp-vpls] user@PE4# set instance-type vpls user@PE4# set interface ge-2/1/7.0 user@PE4# set protocols vpls vpls-id 100 [edit routing-instances ldp-vpls protocols vpls] user@PE4# set neighbor 192.0.2.3 user@PE4# set neighbor 192.0.2.2
Resultados
A partir do modo de configuração, confirme sua configuração entrando nosshow interfaces, show protocolsshow routing-instancese show routing-options comandos. Se a saída não exibir a configuração pretendida, repita as instruções neste exemplo para corrigir a configuração.
Dispositivo PE1
user@PE1# show interfaces
ge-2/0/5 {
encapsulation ethernet-vpls;
unit 0 {
description to_CE1;
family vpls;
}
}
fe-2/0/9 {
}
unit 0 {
description to_PE2;
family inet {
address 10.10.3.1/30;
}
family mpls;
}
}
fe-2/0/10 {
unit 0 {
description to_PE3;
family inet {
address 10.10.1.1/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 192.0.2.1/24;
}
}
}
user@PE1# show protocols
mpls {
interface fe-2/0/10.0;
interface fe-2/0/9.0;
}
bgp {
group internal-peers {
type internal;
local-address 192.0.2.1;
family l2vpn {
signaling;
}
neighbor 192.0.2.2;
neighbor 192.0.2.3;
}
}
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface fe-2/0/10.0;
interface fe-2/0/9.0;
}
}
ldp {
interface fe-2/0/10.0;
interface fe-2/0/9.0;
interface lo0.0;
}
user@PE1# show routing-instances
h-vpls-PE1 {
instance-type vpls;
interface ge-2/0/5.0;
route-distinguisher 1:1;
vrf-target target:1:1;
protocols {
vpls {
interface ge-2/0/5.0;
site PE1-vpls {
site-identifier 2;
}
}
}
}
user@PE1# show routing-options
autonomous-system 64510;
Pe2 do dispositivo
user@PE2# show interfaces
ge-2/0/6 {
encapsulation ethernet-vpls;
unit 0 {
description to_CE2;
family vpls;
}
}
fe-2/0/8 {
unit 0 {
description to_PE3;
family inet {
address 10.10.4.2/30;
}
family mpls;
}
}
fe-2/0/9 {
unit 0{
description to_PE4;
family inet {
address 10.10.5.1/30;
}
family mpls;
}
}
fe-2/0/10 {
unit 0 {
description to_PE1;
family inet {
address 10.10.3.2/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 192.0.2.2/24;
}
}
}
user@PE2# show protocols
mpls {
interface fe-2/0/10.0;
interface fe-2/0/9.0;
interface fe-2/0/8.0;
}
bgp {
group ibgp {
type internal;
local-address 192.0.2.2;
family l2vpn {
signaling;
}
neighbor 192.0.2.3;
neighbor 192.0.2.1;
}
}
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface fe-2/0/10.0;
interface fe-2/0/9.0;
interface fe-2/0/8.0;
}
}
ldp {
interface fe-2/0/10.0;
interface fe-2/0/9.0;
interface fe-2/0/8.0;
interface lo0.0;
}
user@PE2# show routing-instances
h-vpls-PE2 {
instance-type vpls;
interface ge-2/0/6.0;
route-distinguisher 1:2;
vrf-target target:1:1;
protocols {
vpls {
interface ge-2/0/6.0;
site PE2-vpls {
site-identifier 1;
multi-homing;
mesh-group h-vpls-PE2;
}
vpls-id 100;
mesh-group h-vpls-PE2 {
vpls-id 100;
local-switching;
neighbor 192.0.2.4;
}
}
}
}
user@PE2# show routing-options
autonomous-system 64510;
Dispositivo PE4
user@PE4# show interfaces
ge-2/1/7 {
encapsulation ethernet-vpls;
unit 0 {
description to_CE4;
family vpls;
}
}
fe-2/0/9 {
unit 0 {
description to_PE3;
family inet {
address 10.10.6.2/30;
}
family mpls;
}
}
fe-2/0/10 {
unit 0 {
description to_PE2;
family inet {
address 10.10.5.2/30;
}
family mpls;
}
}
lo0 {
unit 0 {
family inet {
address 192.0.2.4/24;
}
}
}
user@PE4# show protocols
mpls {
interface fe-2/0/9.0;
interface fe-2/0/10.0;
}
ospf {
area 0.0.0.0 {
interface lo0.0 {
passive;
}
interface fe-2/0/9.0;
interface fe-2/0/10.0;
}
}
ldp {
interface fe-2/0/10.0;
interface fe-2/0/9.0;
interface lo0.0;
}
user@PE4# show routing-instances
ldp-vpls {
instance-type vpls;
interface ge-2/1/7.0;
protocols {
vpls {
vpls-id 100;
neighbor 192.0.2.3;
neighbor 192.0.2.2;
}
}
}
Se você terminar de configurar os dispositivos, entre no commit modo de configuração.
Verificação
Confirme que a configuração está funcionando corretamente. Em um cenário multihoming com BGP-LDP VPLS, os pseudowires LDP estão no estado inferior para o PE de backup (Dispositivo PE2). Enquanto no VPLS PE (Device PE4) somente para LDP, os pseudowires para os dispositivos BGP-LDP PE primários e de backup estão em alta.
- Verificando as conexões VPLS
- Acionando manualmente um switch do Pseudowire ativo para o Pseudowire de backup
- Verificando a conectividade
- Verificando as tabelas de roteamento VPN bgp camada 2
- Verificando as tabelas de roteamento de circuitos de Camada 2
Verificando as conexões VPLS
Propósito
Verifique se as conexões VPLS estão funcionando como esperado.
Ação
Do modo operacional, entre no show vpls connections comando.
user@PE1> show vpls connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down NP -- interface hardware not present
CM -- control-word mismatch -> -- only outbound connection is up
CN -- circuit not provisioned <- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status IL -- no incoming label
MM -- MTU mismatch MI -- Mesh-Group ID not available
BK -- Backup connection ST -- Standby connection
PF -- Profile parse failure PB -- Profile busy
RS -- remote site standby SN -- Static Neighbor
LB -- Local site not best-site RB -- Remote site not best-site
VM -- VLAN ID mismatch
Legend for interface status
Up -- operational
Dn -- down
Instance: h-vpls-PE1
Local site: PE1-vpls (2)
connection-site Type St Time last up # Up trans
1 rmt Up Oct 16 16:52:27 2012 1
Remote PE: 192.0.2.2, Negotiated control-word: No
Incoming label: 800016, Outgoing label: 800009
Local interface: vt-2/0/10.51380738, Status: Up, Encapsulation: VPLS
Description: Intf - vpls h-vpls-PE1 local site 2 remote site 1
user@PE2> show vpls connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down NP -- interface hardware not present
CM -- control-word mismatch -> -- only outbound connection is up
CN -- circuit not provisioned <- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status IL -- no incoming label
MM -- MTU mismatch MI -- Mesh-Group ID not available
BK -- Backup connection ST -- Standby connection
PF -- Profile parse failure PB -- Profile busy
RS -- remote site standby SN -- Static Neighbor
LB -- Local site not best-site RB -- Remote site not best-site
VM -- VLAN ID mismatch
Legend for interface status
Up -- operational
Dn -- down
Instance: h-vpls-PE2
BGP-VPLS State
Local site: PE2-vpls (1)
connection-site Type St Time last up # Up trans
1 rmt RN
2 rmt Up Oct 16 17:12:31 2012 1
Remote PE: 192.0.2.1, Negotiated control-word: No
Incoming label: 800257, Outgoing label: 800000
Local interface: vt-2/0/10.118489089, Status: Up, Encapsulation: VPLS
Description: Intf - vpls h-vpls-PE2 local site 1 remote site 2
LDP-VPLS State
VPLS-id: 100
Mesh-group connections: h-vpls-PE2
Neighbor Type St Time last up # Up trans
192.0.2.4(vpls-id 100) rmt Up Oct 16 17:12:30 2012 1
Remote PE: 192.0.2.4, Negotiated control-word: No
Incoming label: 800000, Outgoing label: 800001
Negotiated PW status TLV: No
Local interface: vt-2/0/10.118489088, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls h-vpls-PE2 neighbor 192.0.2.4 vpls-id 100
user@PE3> show vpls connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down NP -- interface hardware not present
CM -- control-word mismatch -> -- only outbound connection is up
CN -- circuit not provisioned <- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status IL -- no incoming label
MM -- MTU mismatch MI -- Mesh-Group ID not available
BK -- Backup connection ST -- Standby connection
PF -- Profile parse failure PB -- Profile busy
RS -- remote site standby SN -- Static Neighbor
LB -- Local site not best-site RB -- Remote site not best-site
VM -- VLAN ID mismatch
Legend for interface status
Up -- operational
Dn -- down
Instance: h-vpls-PE3
BGP-VPLS State
Local site: PE3-vpls (1)
connection-site Type St Time last up # Up trans
1 rmt LN
2 rmt LN
LDP-VPLS State
VPLS-id: 100
Mesh-group connections: h-vpls-PE3
Neighbor Type St Time last up # Up trans
192.0.2.4(vpls-id 100) rmt LN
user@PE4> show vpls connections
Layer-2 VPN connections:
Legend for connection status (St)
EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS
EM -- encapsulation mismatch WE -- interface and instance encaps not same
VC-Dn -- Virtual circuit down NP -- interface hardware not present
CM -- control-word mismatch -> -- only outbound connection is up
CN -- circuit not provisioned <- -- only inbound connection is up
OR -- out of range Up -- operational
OL -- no outgoing label Dn -- down
LD -- local site signaled down CF -- call admission control failure
RD -- remote site signaled down SC -- local and remote site ID collision
LN -- local site not designated LM -- local site ID not minimum designated
RN -- remote site not designated RM -- remote site ID not minimum designated
XX -- unknown connection status IL -- no incoming label
MM -- MTU mismatch MI -- Mesh-Group ID not available
BK -- Backup connection ST -- Standby connection
PF -- Profile parse failure PB -- Profile busy
RS -- remote site standby SN -- Static Neighbor
LB -- Local site not best-site RB -- Remote site not best-site
VM -- VLAN ID mismatch
Legend for interface status
Up -- operational
Dn -- down
Instance: ldp-vpls
VPLS-id: 100
Neighbor Type St Time last up # Up trans
192.0.2.2(vpls-id 100) rmt Up Oct 16 17:12:23 2012 1
Remote PE: 192.0.2.2, Negotiated control-word: No
Incoming label: 800001, Outgoing label: 800000
Negotiated PW status TLV: No
Local interface: vt-2/0/10.17825793, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls ldp-vpls neighbor 192.0.2.2 vpls-id 100
192.0.2.3(vpls-id 100) rmt Up Oct 16 17:12:20 2012 1
Remote PE: 192.0.2.3, Negotiated control-word: No
Incoming label: 800000, Outgoing label: 800000
Negotiated PW status TLV: No
Local interface: vt-2/0/10.17825792, Status: Up, Encapsulation: ETHERNET
Description: Intf - vpls ldp-vpls neighbor 192.0.2.3 vpls-id 100
Significado
No dispositivo PE1, a conexão BGP-VPLS com o dispositivo PE2 está ativa. Em uma condição de estado estável, o Dispositivo PE2 é o roteador principal e tem todos os pseudowires terminando nele. O tráfego flui de CE1 a PE1 para PE2 a PE4 a CE4.
No dispositivo PE2, a conexão BGP-VPLS com o dispositivo PE1 está ativa. A conexão com o dispositivo PE3 está no estado do RN. A conexão LDP-VPLS com o dispositivo PE4 está ativa.
No dispositivo PE3, todas as conexões VPLS estão no estado LN. Isso é esperado porque o dispositivo PE3 é o backup.
No dispositivo PE4, o roteador VPLS somente para LDP, o pseudowire principal para o Dispositivo PE2 e o pseudowire de backup para o Dispositivo PE3 estão em alta.
Acionando manualmente um switch do Pseudowire ativo para o Pseudowire de backup
Propósito
Verifique se quando o dispositivo PE2 fica indisponível, o fluxo de tráfego muda para o dispositivo PE3.
Ação
No dispositivo PE2, desativar as interfaces.
user@PE2# deactivate interfaces user@PE2# commit
Reexame o
show vpls connectionscomando em todos os dispositivos PE.user@PE1> show vpls connections Layer-2 VPN connections: Legend for connection status (St) EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS EM -- encapsulation mismatch WE -- interface and instance encaps not same VC-Dn -- Virtual circuit down NP -- interface hardware not present CM -- control-word mismatch -> -- only outbound connection is up CN -- circuit not provisioned <- -- only inbound connection is up OR -- out of range Up -- operational OL -- no outgoing label Dn -- down LD -- local site signaled down CF -- call admission control failure RD -- remote site signaled down SC -- local and remote site ID collision LN -- local site not designated LM -- local site ID not minimum designated RN -- remote site not designated RM -- remote site ID not minimum designated XX -- unknown connection status IL -- no incoming label MM -- MTU mismatch MI -- Mesh-Group ID not available BK -- Backup connection ST -- Standby connection PF -- Profile parse failure PB -- Profile busy RS -- remote site standby SN -- Static Neighbor LB -- Local site not best-site RB -- Remote site not best-site VM -- VLAN ID mismatch Legend for interface status Up -- operational Dn -- down Instance: h-vpls-PE1 Local site: PE1-vpls (2) connection-site Type St Time last up # Up trans 1 rmt Up Oct 17 12:24:01 2012 2 Remote PE: 192.0.2.3, Negotiated control-word: No Incoming label: 800000, Outgoing label: 800257 Local interface: vt-2/0/10.84934656, Status: Up, Encapsulation: VPLS Description: Intf - vpls h-vpls-PE1 local site 2 remote site 1user@PE2> show vpls connections Layer-2 VPN connections: Legend for connection status (St) EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS EM -- encapsulation mismatch WE -- interface and instance encaps not same VC-Dn -- Virtual circuit down NP -- interface hardware not present CM -- control-word mismatch -> -- only outbound connection is up CN -- circuit not provisioned <- -- only inbound connection is up OR -- out of range Up -- operational OL -- no outgoing label Dn -- down LD -- local site signaled down CF -- call admission control failure RD -- remote site signaled down SC -- local and remote site ID collision LN -- local site not designated LM -- local site ID not minimum designated RN -- remote site not designated RM -- remote site ID not minimum designated XX -- unknown connection status IL -- no incoming label MM -- MTU mismatch MI -- Mesh-Group ID not available BK -- Backup connection ST -- Standby connection PF -- Profile parse failure PB -- Profile busy RS -- remote site standby SN -- Static Neighbor LB -- Local site not best-site RB -- Remote site not best-site VM -- VLAN ID mismatch Legend for interface status Up -- operational Dn -- down Instance: h-vpls-PE2 BGP-VPLS State Local site: PE2-vpls (1) LDP-VPLS State VPLS-id: 100 Mesh-group connections: h-vpls-PE2 Neighbor Type St Time last up # Up trans 192.0.2.4(vpls-id 100) rmt OLuser@PE3> show vpls connections Layer-2 VPN connections: Legend for connection status (St) EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS EM -- encapsulation mismatch WE -- interface and instance encaps not same VC-Dn -- Virtual circuit down NP -- interface hardware not present CM -- control-word mismatch -> -- only outbound connection is up CN -- circuit not provisioned <- -- only inbound connection is up OR -- out of range Up -- operational OL -- no outgoing label Dn -- down LD -- local site signaled down CF -- call admission control failure RD -- remote site signaled down SC -- local and remote site ID collision LN -- local site not designated LM -- local site ID not minimum designated RN -- remote site not designated RM -- remote site ID not minimum designated XX -- unknown connection status IL -- no incoming label MM -- MTU mismatch MI -- Mesh-Group ID not available BK -- Backup connection ST -- Standby connection PF -- Profile parse failure PB -- Profile busy RS -- remote site standby SN -- Static Neighbor LB -- Local site not best-site RB -- Remote site not best-site VM -- VLAN ID mismatch Legend for interface status Up -- operational Dn -- down Instance: h-vpls-PE3 BGP-VPLS State Local site: PE3-vpls (1) connection-site Type St Time last up # Up trans 2 rmt Up Oct 17 12:24:01 2012 1 Remote PE: 192.0.2.1, Negotiated control-word: No Incoming label: 800257, Outgoing label: 800000 Local interface: vt-2/0/10.135266304, Status: Up, Encapsulation: VPLS Description: Intf - vpls h-vpls-PE3 local site 1 remote site 2 LDP-VPLS State VPLS-id: 100 Mesh-group connections: h-vpls-PE3 Neighbor Type St Time last up # Up trans 192.0.2.4(vpls-id 100) rmt Up Oct 17 12:24:02 2012 1 Remote PE: 192.0.2.4, Negotiated control-word: No Incoming label: 800000, Outgoing label: 800000 Negotiated PW status TLV: No Local interface: vt-2/0/10.135266305, Status: Up, Encapsulation: ETHERNET Description: Intf - vpls h-vpls-PE3 neighbor 192.0.2.4 vpls-id 100user@PE4> show vpls connections Layer-2 VPN connections: Legend for connection status (St) EI -- encapsulation invalid NC -- interface encapsulation not CCC/TCC/VPLS EM -- encapsulation mismatch WE -- interface and instance encaps not same VC-Dn -- Virtual circuit down NP -- interface hardware not present CM -- control-word mismatch -> -- only outbound connection is up CN -- circuit not provisioned <- -- only inbound connection is up OR -- out of range Up -- operational OL -- no outgoing label Dn -- down LD -- local site signaled down CF -- call admission control failure RD -- remote site signaled down SC -- local and remote site ID collision LN -- local site not designated LM -- local site ID not minimum designated RN -- remote site not designated RM -- remote site ID not minimum designated XX -- unknown connection status IL -- no incoming label MM -- MTU mismatch MI -- Mesh-Group ID not available BK -- Backup connection ST -- Standby connection PF -- Profile parse failure PB -- Profile busy RS -- remote site standby SN -- Static Neighbor LB -- Local site not best-site RB -- Remote site not best-site VM -- VLAN ID mismatch Legend for interface status Up -- operational Dn -- down Instance: ldp-vpls VPLS-id: 100 Neighbor Type St Time last up # Up trans 192.0.2.2(vpls-id 100) rmt OL 192.0.2.3(vpls-id 100) rmt Up Oct 16 17:12:20 2012 1 Remote PE: 192.0.2.3, Negotiated control-word: No Incoming label: 800000, Outgoing label: 800000 Negotiated PW status TLV: No Local interface: vt-2/0/10.17825792, Status: Up, Encapsulation: ETHERNET Description: Intf - vpls ldp-vpls neighbor 192.0.2.3 vpls-id 100
Significado
No dispositivo PE1, a conexão BGP-VPLS com o dispositivo PE3 está ativa. O tráfego flui de CE1 a PE1 para PE3 a PE4 a CE4.
No dispositivo PE2, a conexão BGP-VPLS com o dispositivo PE1 está no estado de OL.
No dispositivo PE3, todas as conexões VPLS estão ativas.
No dispositivo PE4, a conexão VPLS com o dispositivo PE2 está no estado de OL. A conexão VPLS com o dispositivo PE3 está ativa.
Se você reativar as interfaces no dispositivo PE2, as conexões voltarão ao estado anterior e ao fluxo de tráfego.
Verificando a conectividade
Propósito
Verifique se o dispositivo CE1 pode ping do dispositivo CE4.
Ação
user@CE1> ping 10.255.14.219 PING 10.255.14.219 (10.255.14.219): 56 data bytes 64 bytes from 10.255.14.219: icmp_seq=0 ttl=64 time=1.149 ms 64 bytes from 10.255.14.219: icmp_seq=1 ttl=64 time=0.779 ms ^C --- 10.255.14.219 ping statistics --- 2 packets transmitted, 2 packets received, 0% packet loss round-trip min/avg/max/stddev = 0.779/0.964/1.149/0.185 ms
Significado
A saída mostra que o VPLS está operacional.
Verificando as tabelas de roteamento VPN bgp camada 2
Propósito
Verifique se as rotas VPLS são aprendidas com o BGP.
Ação
user@PE1> show route table bgp.l2vpn.0
bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:3:1:1/96
*[BGP/170] 20:00:11, localpref 100, from 192.0.2.3
AS path: I, validation-state: unverified
> to 10.10.1.2 via fe-2/0/10.0
user@PE3> show route table bgp.l2vpn.0
bgp.l2vpn.0: 1 destinations, 1 routes (1 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
1:1:2:1/96
*[BGP/170] 20:00:11, localpref 100, from 192.0.2.1
AS path: I, validation-state: unverified
> to 10.10.1.1 via fe-2/0/10.0
Verificando as tabelas de roteamento de circuitos de Camada 2
Propósito
Verifique se as rotas VPLS são aprendidas com o LDP.
Ação
user@PE3> show route table l2circuit.0
l2circuit.0: 2 destinations, 2 routes (2 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both
192.0.2.4:NoCtrlWord:5:100:Local/96
*[VPLS/7] 01:30:11, metric2 1
> to 10.10.6.2 via fe-2/0/9.0
192.0.2.4:NoCtrlWord:5:100:Remote/96
*[LDP/9] 20:41:57
Discard
user@PE4> show route table bgp.l2vpn.0
l2circuit.0: 3 destinations, 3 routes (2 active, 0 holddown, 1 hidden)
+ = Active Route, - = Last Active, * = Both
192.0.2.3:NoCtrlWord:5:100:Local/96
*[VPLS/7] 20:42:51, metric2 1
> to 10.10.6.1 via fe-2/0/9.0
192.0.2.3:NoCtrlWord:5:100:Remote/96
*[LDP/9] 20:41:57
Discard