Nesta página
Exemplo: Configuração de grandes comunidades BGP
Este exemplo mostra que você configura o atributo de caminho transitivo opcional - uma comunidade BGP de 12 byte que fornece o valor mais significativo de 4 byte para codificar o número do sistema autônomo como administrador global e os dois números atribuídos de 4 byte restantes para codificar os valores locais conforme definido no RFC 8092. Você pode configurar uma grande comunidade BGP em [edit policy-options community community-name members] níveis de hierarquia.[edit routing-options static route ip-address community] O formato de atributos de comunidade de grande porte BGP tem quatro campos: large:global administrator:assigned number:assigned number.
Requisitos
Este exemplo usa os seguintes componentes de hardware e software:
Três roteadores da Série MX
Junos OS Release 17.3 ou posterior em todos os dispositivos
Nenhuma configuração especial além da inicialização do dispositivo é necessária antes de configurar este exemplo.
Visão geral
Neste exemplo, o Dispositivo R1 e o Dispositivo R2 são vizinhos OSPF em sistema autônomo (AS) 64510. O dispositivo R3 tem uma conexão BGP (EBGP) externa ao dispositivo R1. O dispositivo R2 tem redes de clientes no espaço de endereços 172.16/16, simulado com endereços em sua interface de loopback (lo0). O dispositivo R1 tem rotas estáticas para várias redes 172.16.x/24, e anexa valores regulares da comunidade a essas rotas. O dispositivo R1 então usa uma política de exportação para anunciar as rotas para o Dispositivo R3. O Dispositivo R3 recebe essas rotas e usa uma política de importação para agregar grandes valores de comunidade às rotas.
Topologia
A Figura 1 mostra a rede de amostra.
Configuração
Configuração rápida da CLI
Para configurar rapidamente este exemplo, copie os seguintes comandos, cole-os em um arquivo de texto, remova qualquer quebra de linha, altere os detalhes necessários para combinar com a configuração da sua rede e, em seguida, copie e cole os comandos no CLI no nível de hierarquia [editar].
Dispositivo R1
set interfaces fe-1/2/0 unit 0 family inet address 10.0.0.1/30 set interfaces fe-1/2/3 unit 0 family inet address 10.0.0.14/30 set interfaces lo0 unit 0 family inet address 192.168.0.1/32 primary set routing-options static route 172.16.1.0/24 next-hop 10.0.0.2 set routing-options static route 172.16.1.0/24 community 64510:1 set routing-options static route 172.16.1.0/24 community large:64510:100:1 set routing-options static route 172.16.2.0/24 next-hop 10.0.0.2 set routing-options static route 172.16.2.0/24 community 64510:2 set routing-options static route 172.16.2.0/24 community large:64510:200:2 set routing-options static route 172.16.3.0/24 next-hop 10.0.0.2 set routing-options static route 172.16.3.0/24 community 64510:3 set routing-options static route 172.16.4.0/24 next-hop 10.0.0.2 set routing-options static route 172.16.4.0/24 community 64510:4 set routing-options router-id 192.168.0.1 set routing-options autonomous-system 64510 set protocols bgp group ext type external set protocols bgp group ext export send-static set protocols bgp group ext peer-as 64511 set protocols bgp group ext neighbor 10.0.0.13 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface fe-1/2/0.0 set policy-options policy-statement send-static term 1 from protocol static set policy-options policy-statement send-static term 1 then accept
Dispositivo R2
set interfaces fe-1/2/0 unit 0 family inet address 10.0.0.2/30 set interfaces lo0 unit 0 family inet address 192.168.0.2/32 set interfaces lo0 unit 0 family inet address 172.16.1.1/32 set interfaces lo0 unit 0 family inet address 172.16.2.2/32 set interfaces lo0 unit 0 family inet address 172.16.3.3/32 set interfaces lo0 unit 0 family inet address 172.16.4.4/32 set routing-options router-id 192.168.0.2 set protocols ospf area 0.0.0.0 interface lo0.0 passive set protocols ospf area 0.0.0.0 interface fe-1/2/0.0
Dispositivo R3
set interfaces fe-1/2/3 unit 0 family inet address 10.0.0.13/30 set interfaces lo0 unit 0 family inet address 192.168.0.3/32 set routing-options router-id 192.168.0.3 set routing-options autonomous-system 64511 set protocols bgp group to-R1 type external set protocols bgp group to-R1 import set-large-comms set protocols bgp group to-R1 peer-as 64510 set protocols bgp group to-R1 neighbor 10.0.0.14 set policy-options policy-statement set-large-comms term route-1 from route-filter 172.16.1.0/24 exact set policy-options policy-statement set-large-comms term route-1 then community add large2-as set policy-options policy-statement set-large-comms term route-1 then accept set policy-options policy-statement set-large-comms term route-2 from route-filter 172.16.2.0/24 exact set policy-options policy-statement set-large-comms term route-2 then community add large2-ip set policy-options policy-statement set-large-comms term route-2 then accept set policy-options policy-statement set-large-comms term route-3 from route-filter 172.16.3.0/24 exact set policy-options policy-statement set-large-comms term route-3 then community add large1-as set policy-options policy-statement set-large-comms term route-3 then accept set policy-options policy-statement set-large-comms term route-4 from route-filter 172.16.4.0/24 exact set policy-options policy-statement set-large-comms term route-4 then community add large1-ip set policy-options policy-statement set-large-comms term route-4 then accept set policy-options community large1-as members large:64511:3:1 set policy-options community large1-ip members large:7777:4:1 set policy-options community large2-as members large:64511:1:1 set policy-options community large2-ip members large:7777:2:1
Procedimento
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 na CLI, veja Use o editor de CLI no modo de configuração no Guia de usuário do Junos OS CLI.
Para configurar o dispositivo R3:
Configure as interfaces.
[edit interfaces] set fe-1/2/3 unit 0 family inet address 10.0.0.13/30 set lo0 unit 0 family inet address 192.168.0.3/32
Configure o número do sistema autônomo (AS) e o ID do roteador.
[edit routing-options] set router-id 192.168.0.3 set autonomous-system 64511
Configure a conexão EBGP com o dispositivo R1.
[edit protocols bgp group to-R1] set type external set import set-large-comms set peer-as 64510 set neighbor 10.0.0.14
Configure a política que agrega grandes valores de comunidade às rotas recebidas do Dispositivo R1.
Uma grande comunidade usa uma notação de
large:global administrator:assigned number:assigned number. Os valores específicos da comunidade podem ser qualquer coisa que cumpra suas metas administrativas, dentro de determinados parâmetros.[edit policy-options policy-statement set-large-comms] set term route-1 from route-filter 172.16.1.0/24 exact set term route-1 then community add large2-as set term route-1 then accept set term route-2 from route-filter 172.16.2.0/24 exact set term route-2 then community add large2-ip set term route-2 then accept set term route-3 from route-filter 172.16.3.0/24 exact set term route-3 then community add large1-as set term route-3 then accept set term route-4 from route-filter 172.16.4.0/24 exact set term route-4 then community add large1-ip set term route-4 then accept
[edit policy-options ] set community large1-as members large:64511:3:1 set community large1-ip members large:7777:4:1 set community large2-as members large:64511:1:1 set community large2-ip members large:7777:2:1
Resultados
A partir do modo de configuração, confirme sua configuração entrando noshow interfaces, show protocolsshow policy-optionse 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.
user@R3# show interfaces
fe-1/2/3 {
unit 0 {
family inet {
address 10.0.0.13/30;
}
}
}
lo0 {
unit 0 {
family inet {
address 192.168.0.3/32;
}
}
}
user@R3# show protocols
bgp {
group to-R1 {
type external;
import set-large-comms;
peer-as 64510;
neighbor 10.0.0.14;
}
}
user@R3# show policy-options
policy-statement set-large-comms {
term route-1 {
from {
route-filter 172.16.1.0/24 exact;
}
then {
community add large2-as;
accept;
}
}
term route-2 {
from {
route-filter 172.16.2.0/24 exact;
}
then {
community add large2-ip;
accept;
}
}
term route-3 {
from {
route-filter 172.16.3.0/24 exact;
}
then {
community add large1-as;
accept;
}
}
term route-4 {
from {
route-filter 172.16.4.0/24 exact;
}
then {
community add large1-ip;
accept;
}
}
}
community large1-as members large:64511:3:1;
community large1-ip members large:7777:4:1;
community large2-as members large:64511:1:1;
community large2-ip members large:7777:2:1;
user@R3# show routing-options router-id 192.168.0.3; autonomous-system 64511;
Se você terminar de configurar o dispositivo, entre no commit modo de configuração.
Verificação
Confirme se a configuração está funcionando corretamente.
Verificando o R1
Propósito
No dispositivo R1, verifique o 172.16. rotas na tabela de roteamento.
Ação
user@R1> show route protocol static match-prefix 172.16.* detail
inet.0: 17 destinations, 17 routes (17 active, 0 holddown, 0 hidden)
172.16.1.0/24 (1 entry, 1 announced)
*Static Preference: 5
Next hop type: Router, Next hop index: 580
Address: 0xb7a1270
Next-hop reference count: 9
Next hop: 10.0.0.2 via fe-1/2/0.0, selected
Session Id: 0x140
State: < Active Int Ext >
Local AS: 64510
Age: 4d 19:02:23
Validation State: unverified
Task: RT
Announcement bits (2): 0-KRT 4-BGP_RT_Background
AS path: I
Communities: 64510:1 large:64510:100:1
172.16.2.0/24 (1 entry, 1 announced)
*Static Preference: 5
Next hop type: Router, Next hop index: 580
Address: 0xb7a1270
Next-hop reference count: 9
Next hop: 10.0.0.2 via fe-1/2/0.0.0, selected
Session Id: 0x140
State: < Active Int Ext >
Local AS: 64510
Age: 4d 19:02:23
Validation State: unverified
Task: RT
Announcement bits (2): 0-KRT 4-BGP_RT_Background
AS path: I
Communities: 64510:2 large:64510:200:2
172.16.3.0/24 (1 entry, 1 announced)
*Static Preference: 5
Next hop type: Router, Next hop index: 580
Address: 0xb7a1270
Next-hop reference count: 9
Next hop: 10.0.0.2 via fe-1/2/0.0.0, selected
Session Id: 0x140
State: < Active Int Ext >
Local AS: 64510
Age: 4d 22:17:12
Validation State: unverified
Task: RT
Announcement bits (2): 0-KRT 4-BGP_RT_Background
AS path: I
Communities: 64510:3
172.16.4.0/24 (1 entry, 1 announced)
*Static Preference: 5
Next hop type: Router, Next hop index: 580
Address: 0xb7a1270
Next-hop reference count: 9
Next hop: 10.0.0.2 via fe-1/2/0.0.0, selected
Session Id: 0x140
State: < Active Int Ext >
Local AS: 64510
Age: 4d 22:17:12
Validation State: unverified
Task: RT
Announcement bits (2): 0-KRT 4-BGP_RT_Background
AS path: I
Communities: 64510:4
. . .
Significado
A saída mostra que a comunidade regular e os grandes valores da comunidade estão vinculados às rotas.
As comunidades estão conectadas a rotas estáticas, demonstrando assim que comunidades regulares e de grande porte podem ser anexadas a rotas estáticas.
Verificando o R3
Propósito
No dispositivo R3, verifique o 172.16. rotas na tabela de roteamento.
Ação
user@R3> show route protocol bgp match-prefix 172.16.* detail
inet.0: 14 destinations, 14 routes (14 active, 0 holddown, 0 hidden)
172.16.1.0/24 (1 entry, 1 announced)
*BGP Preference: 170/-101
Next hop type: Router, Next hop index: 581
Address: 0xb7a10f0
Next-hop reference count: 8
Source: 10.0.0.14
Next hop: 10.0.0.14 via fe-1/2/3.0, selected
Session Id: 0x140
State: < Active Ext >
Local AS: 64511 Peer AS: 64510
Age: 3d 16:36:18
Validation State: unverified
Task: BGP_64510.10.0.0.14
Announcement bits (1): 0-KRT
AS path: 64510 I
Communities: 64510:1 large:64510:100:1 large:64511:1:1
Accepted
Localpref: 100
Router ID: 192.168.0.1
172.16.2.0/24 (1 entry, 1 announced)
*BGP Preference: 170/-101
Next hop type: Router, Next hop index: 581
Address: 0xb7a10f0
Next-hop reference count: 8
Source: 10.0.0.14
Next hop: 10.0.0.14 via fe-1/2/3.0, selected
Session Id: 0x140
State: < Active Ext >
Local AS: 64511 Peer AS: 64510
Age: 3d 16:36:18
Validation State: unverified
Task: BGP_64510.10.0.0.14
Announcement bits (1): 0-KRT
AS path: 64510 I
Communities: 64510:2 large:7777:2:1 large:64510:200:2
Accepted
Localpref: 100
Router ID: 192.168.0.1
172.16.3.0/24 (1 entry, 1 announced)
*BGP Preference: 170/-101
Next hop type: Router, Next hop index: 581
Address: 0xb7a10f0
Next-hop reference count: 8
Source: 10.0.0.14
Next hop: 10.0.0.14 via fe-1/2/3.0, selected
Session Id: 0x140
State: < Active Ext >
Local AS: 64511 Peer AS: 64510
Age: 3d 16:36:18
Validation State: unverified
Task: BGP_64510.10.0.0.14
Announcement bits (1): 0-KRT
AS path: 64510 I
Communities: 64510:3 large:64511:3:1
Accepted
Localpref: 100
Router ID: 192.168.0.1
172.16.4.0/24 (1 entry, 1 announced)
*BGP Preference: 170/-101
Next hop type: Router, Next hop index: 581
Address: 0xb7a10f0
Next-hop reference count: 8
Source: 10.0.0.14
Next hop: 10.0.0.14 via fe-1/2/3.0, selected
Session Id: 0x140
State: < Active Ext >
Local AS: 64511 Peer AS: 64510
Age: 3d 16:36:18
Validation State: unverified
Task: BGP_64510.10.0.0.14
Announcement bits (1): 0-KRT
AS path: 64510 I
Communities: 64510:4 large:7777:4:1
Accepted
Localpref: 100
Router ID: 192.168.0.1
. . .
Significado
A saída mostra que os valores anunciados regulares e de grande porte da comunidade permanecem vinculados às rotas, e que os novos grandes valores da comunidade são adicionados quando recebidos pela R3.