Ajude-nos a melhorar a sua experiência.

Conte-nos a sua opinião.

Tem dois minutos para uma pesquisa?

Announcement: Try the Ask AI chatbot for answers to your technical questions about Juniper products and solutions.

close
header-navigation
keyboard_arrow_up
close
keyboard_arrow_left
list Table of Contents
keyboard_arrow_right

Esta tradução automática foi útil?

starstarstarstarstar
Go to English page
ISENÇÃO DE RESPONSABILIDADE:

Esta página será traduzida com software de tradução por máquina de terceiros. Embora esforços razoáveis tenham sido feitos para fornecer uma tradução de qualidade, a Juniper Networks não pode garantir sua exatidão. Se houver dúvidas sobre a exatidão das informações contidas nesta tradução, consulte a versão em inglês. O PDF para download está disponível apenas em inglês.

Exemplo: Configuração de comunidades em uma política de roteamento

date_range 18-Jan-25

Uma comunidade é um atributo de rota usado pelo BGP para agrupar rotas administrativamente com propriedades semelhantes.

Requisitos

Nenhuma configuração especial além da inicialização do dispositivo é necessária antes de configurar este exemplo.

  • Atualizado e revalidado usando o vMX no Junos OS Release 21.1R1.

Visão geral

Um papel principal do atributo da comunidade é ser um valor de tag administrativa usado para associar rotas em conjunto. Geralmente, essas rotas compartilham algumas propriedades comuns, mas isso não é necessário. As comunidades são uma ferramenta flexível dentro do BGP. Um valor de comunidade individual pode ser atribuído a uma única rota ou várias rotas. Uma rota pode ser atribuída a um único valor de comunidade ou vários valores. As redes usam o atributo da comunidade para ajudar na implementação de políticas de roteamento administrativo. O valor atribuído de uma rota pode permitir que ele seja aceito na rede, ou rejeitado da rede, ou permitir que ele modifique atributos.

Figura 1 mostra o dispositivo R1, o dispositivo R2 e o dispositivo R3 como pares BGP interno (IBGP) em sistema autônomo (AS) 64510. O dispositivo R4 está anunciando o espaço de endereços 172.16.0/21 a partir do AS 64511.

Topologia

Figura 1: Topologia para comunidades BGP regularesTopologia para comunidades BGP regulares

As rotas específicas recebidas pelo dispositivo R1 do dispositivo R4 são as seguintes:

content_copy zoom_out_map
user@R1> show route receive-protocol bgp 10.0.0.13

inet.0: 24 destinations, 28 routes (24 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 172.16.0.0/24           10.0.0.13                               64511 I
* 172.16.1.0/24           10.0.0.13                               64511 I
* 172.16.2.0/24           10.0.0.13                               64511 I
* 172.16.3.0/24           10.0.0.13                               64511 I
  172.16.4.0/24           10.0.0.13                               64511 I
  172.16.5.0/24           10.0.0.13                               64511 I
  172.16.6.0/24           10.0.0.13                               64511 I
  172.16.7.0/24           10.0.0.13                               64511 I

Os administradores do AS 64511 querem receber determinado tráfego de usuário do dispositivo R1 e outro tráfego de usuários do dispositivo R3. Para atingir essa meta administrativa, o dispositivo R4 anexa o valor da comunidade de 64511:1 a algumas rotas que envia e anexa o valor da comunidade 64511:3 a outras rotas que envia. As políticas de roteamento dentro do AS 64510 são configuradas usando um critério de correspondência da comunidade para alterar a preferência local das rotas recebidas para novos valores que alteram o algoritmo de seleção de rotas BGP. A rota com o mais alto valor de preferência local é preferida.

No dispositivo R1, as rotas com o valor da comunidade 64511:1 recebem uma preferência local de 200, e as rotas com o valor da comunidade 64511:3 recebem uma preferência local de 50. No dispositivo R3, o inverso é feito para que rotas com o valor da comunidade 64511:3 sejam atribuídas a uma preferência local de 200, e rotas com o valor da comunidade 64511:1 recebem uma preferência local de 50. Essas informações são então comunicadas através do IBGP pelo dispositivo R1 e pelo dispositivo R3 para o dispositivo R2.

Configuração rápida da CLI mostra a configuração de todos os dispositivos em Figura 1.

A configuração passo a passo da seção descreve as etapas de configuração nos dispositivos R1 e R4.

Configuração

Configuração rápida da CLI

Para configurar este exemplo rapidamente, 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 [edit] hierarquia.

Dispositivo R1

content_copy zoom_out_map
set interfaces ge-0/0/0 unit 0 family inet address 10.0.0.1/30
set interfaces ge-0/0/1 unit 0 family inet address 10.1.0.5/30
set interfaces ge-0/0/2 unit 0 family inet address 10.0.0.14/30
set interfaces lo0 unit 0 family inet address 192.168.0.1/32
set policy-options policy-statement change-local-preference term find-R1-routes from community R1_PREFERRED
set policy-options policy-statement change-local-preference term find-R1-routes then local-preference 200
set policy-options policy-statement change-local-preference term find-R3-routes from community R3_PREFERRED
set policy-options policy-statement change-local-preference term find-R3-routes then local-preference 50
set policy-options policy-statement send-direct term 1 from protocol direct
set policy-options policy-statement send-direct term 1 from route-filter 10.0.0.12/30 exact
set policy-options policy-statement send-direct term 1 then accept
set policy-options community R3_PREFERRED members 64511:3
set policy-options community R1_PREFERRED members 64511:1
set protocols bgp group int type internal
set protocols bgp group int local-address 192.168.0.1
set protocols bgp group int export send-direct
set protocols bgp group int neighbor 192.168.0.2
set protocols bgp group int neighbor 192.168.0.3
set protocols bgp group ext type external
set protocols bgp group ext import change-local-preference
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 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 passive
set routing-options router-id 192.168.0.1
set routing-options autonomous-system 64510

Dispositivo R2

content_copy zoom_out_map
set interfaces ge-0/0/0 unit 0 family inet address 10.0.0.2/30
set interfaces ge-0/0/1 unit 0 family inet address 10.1.0.1/30
set interfaces lo0 unit 0 family inet address 192.168.0.2/32
set protocols bgp group int type internal
set protocols bgp group int local-address 192.168.0.2
set protocols bgp group int neighbor 192.168.0.1
set protocols bgp group int neighbor 192.168.0.3
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 passive
set routing-options router-id 192.168.0.2
set routing-options autonomous-system 64510

Dispositivo R3

content_copy zoom_out_map
set interfaces ge-0/0/0 unit 0 family inet address 10.1.0.6/30
set interfaces ge-0/0/1 unit 0 family inet address 10.1.0.2/30
set interfaces ge-0/0/2 unit 0 family inet address 10.0.0.10/30
set interfaces lo0 unit 0 family inet address 192.168.0.3/32
set policy-options policy-statement change-local-preference term find-R3-routes from community R3_PREFERRED
set policy-options policy-statement change-local-preference term find-R3-routes then local-preference 200
set policy-options policy-statement change-local-preference term find-R1-routes from community R1_PREFERRED
set policy-options policy-statement change-local-preference term find-R1-routes then local-preference 50
set policy-options policy-statement send-direct term 1 from protocol direct
set policy-options policy-statement send-direct term 1 from route-filter 10.0.0.8/30 exact
set policy-options policy-statement send-direct term 1 then accept
set policy-options community R1_PREFERRED members 64511:1
set policy-options community R3_PREFERRED members 64511:3
set protocols bgp group int type internal
set protocols bgp group int local-address 192.168.0.3
set protocols bgp group int export send-direct
set protocols bgp group int neighbor 192.168.0.1
set protocols bgp group int neighbor 192.168.0.2
set protocols bgp group ext type external
set protocols bgp group ext import change-local-preference
set protocols bgp group ext peer-as 64511
set protocols bgp group ext neighbor 10.0.0.9
set protocols ospf area 0.0.0.0 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 lo0.0 passive
set routing-options router-id 192.168.0.3
set routing-options autonomous-system 64510

Dispositivo R4

content_copy zoom_out_map
set interfaces ge-0/0/0 unit 0 family inet address 10.0.0.13/30
set interfaces ge-0/0/1 unit 0 family inet address 10.0.0.9/30
set interfaces lo0 unit 0 family inet address 192.168.0.4/32
set policy-options policy-statement send-static term 1 from protocol static
set policy-options policy-statement send-static term 1 from route-filter 172.16.0.0/24 exact
set policy-options policy-statement send-static term 1 from route-filter 172.16.1.0/24 exact
set policy-options policy-statement send-static term 1 from route-filter 172.16.2.0/24 exact
set policy-options policy-statement send-static term 1 from route-filter 172.16.3.0/24 exact
set policy-options policy-statement send-static term 1 then community add R1_PREFERRED
set policy-options policy-statement send-static term 1 then accept
set policy-options policy-statement send-static term 2 from protocol static
set policy-options policy-statement send-static term 2 from route-filter 172.16.4.0/24 exact
set policy-options policy-statement send-static term 2 from route-filter 172.16.5.0/24 exact
set policy-options policy-statement send-static term 2 from route-filter 172.16.6.0/24 exact
set policy-options policy-statement send-static term 2 from route-filter 172.16.7.0/24 exact
set policy-options policy-statement send-static term 2 then community add R3_PREFERRED
set policy-options policy-statement send-static term 2 then accept
set policy-options policy-statement send-static term 3 then reject
set policy-options community R3_PREFERRED members 64511:3
set policy-options community R1_PREFERRED members 64511:1
set protocols bgp group to-R1 type external
set protocols bgp group to-R1 export send-static
set protocols bgp group to-R1 peer-as 64510
set protocols bgp group to-R1 neighbor 10.0.0.14
set protocols bgp group to-R3 type external
set protocols bgp group to-R3 export send-static
set protocols bgp group to-R3 peer-as 64510
set protocols bgp group to-R3 neighbor 10.0.0.10
set routing-options router-id 192.168.0.4
set routing-options autonomous-system 64511
set routing-options static route 172.16.0.0/24 reject
set routing-options static route 172.16.1.0/24 reject
set routing-options static route 172.16.2.0/24 reject
set routing-options static route 172.16.3.0/24 reject
set routing-options static route 172.16.4.0/24 reject
set routing-options static route 172.16.5.0/24 reject
set routing-options static route 172.16.6.0/24 reject
set routing-options static route 172.16.7.0/24 reject

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 R1:

  1. Configure as interfaces.

    content_copy zoom_out_map
    [edit interfaces]
    user@R1# set ge-0/0/0 unit 0 family inet address 10.0.0.1/30
    user@R1# set ge-0/0/1 unit 0 family inet address 10.1.0.5/30
    user@R1# set ge-0/0/2 unit 0 family inet address 10.0.0.14/30
    user@R1# set lo0 unit 0 family inet address 192.168.0.1/32
    
  2. Configure conexões internas de protocolo de gateway (IGP) para dispositivos R2 e R3.

    content_copy zoom_out_map
    [edit protocols ospf area 0.0.0.0]
    user@R1# set interface ge-0/0/0.0
    user@R1# set interface ge-0/0/1.0
    user@R1# set interface lo0.0 passive
    
  3. Configure as conexões IBGP aos dispositivos R2 e R3.

    content_copy zoom_out_map
    [edit protocols bgp group int]
    user@R1# set type internal
    user@R1# set local-address 192.168.0.1
    user@R1# set export send-direct
    user@R1# set neighbor 192.168.0.2
    user@R1# set neighbor 192.168.0.3
    
  4. Configure a conexão EBGP com o dispositivo R4.

    content_copy zoom_out_map
    [edit protocols bgp group ext]
    user@R1# set type external
    user@R1# set import change-local-preference
    user@R1# set peer-as 64511
    user@R1# set neighbor 10.0.0.13
    
  5. Configure a política send-direct.

    Essa política é mencionada na configuração do IBGP e permite que o dispositivo R2 tenha acessibilidade externa. Uma alternativa é configurar uma next-hop self política no dispositivo R1 e no dispositivo R3.

    content_copy zoom_out_map
    [edit policy-options policy-statement send-direct term 1]
    user@R1# set from protocol direct
    user@R1# set from route-filter 10.0.0.12/30 exact
    user@R1# set then accept
    
  6. Configure a política que altera a preferência local por rotas com tags de comunidade especificadas.

    content_copy zoom_out_map
    [edit policy-options ]
    user@R1# set policy-statement change-local-preference term find-R1-routes from community R1_PREFERRED
    user@R1# set policy-statement change-local-preference term find-R1-routes then local-preference 200
    user@R1# set policy-statement change-local-preference term find-R3-routes from community R3_PREFERRED
    user@R1# set policy-statement change-local-preference term find-R3-routes then local-preference 50
    user@R1# set community R3_PREFERRED members 64511:3
    user@R1# set community R1_PREFERRED members 64511:1
    
  7. Configure o número do sistema autônomo (AS) e o ID do roteador.

    content_copy zoom_out_map
    [edit routing-options]
    user@R1# set router-id 192.168.0.1
    user@R1# set autonomous-system 64510
    

Para configurar o dispositivo R4:

  1. Configure as interfaces.

    content_copy zoom_out_map
    [edit interfaces]
    user@R4# set ge-0/0/0 unit 0 family inet address 10.0.0.13/30
    user@R4# set ge-0/0/1 unit 0 family inet address 10.0.0.9/30
    user@R4# set lo0 unit 0 family inet address 192.168.0.4/32
    
  2. Configure a conexão EBGP com o dispositivo R1 e o dispositivo R3.

    content_copy zoom_out_map
    [edit protocols bgp]
    user@R4# set group to-R1 type external
    user@R4# set group to-R1 export send-static
    user@R4# set group to-R1 peer-as 64510
    user@R4# set group to-R1 neighbor 10.0.0.14
    user@R4# set group to-R3 type external
    user@R4# set group to-R3 export send-static
    user@R4# set group to-R3 peer-as 64510
    user@R4# set group to-R3 neighbor 10.0.0.10
    
  3. Configure as tags da comunidade.

    content_copy zoom_out_map
    [edit policy-options ]
    user@R4# set community R3_PREFERRED members 64511:3
    user@R4# set community R1_PREFERRED members 64511:1
    
  4. Configure a política send-static.

    Esta política é mencionada nas conexões EBGP ao dispositivo R1 e ao dispositivo R3. A política anexa a comunidade 64511:1 (PREFERRED) a algumas rotas e à comunidade 64511:3 (NOT_PREFERRED) a outras rotas.

    content_copy zoom_out_map
    [edit policy-options]
    user@R4# set policy-statement send-static term 1 from protocol static
    user@R4# set policy-statement send-static term 1 from route-filter 172.16.0.0/24 exact
    user@R4# set policy-statement send-static term 1 from route-filter 172.16.1.0/24 exact
    user@R4# set policy-statement send-static term 1 from route-filter 172.16.2.0/24 exact
    user@R4# set policy-statement send-static term 1 from route-filter 172.16.3.0/24 exact
    user@R4# set policy-statement send-static term 1 then community add R1_PREFERRED
    user@R4# set policy-statement send-static term 1 then accept
    user@R4# set policy-statement send-static term 2 from protocol static
    user@R4# set policy-statement send-static term 2 from route-filter 172.16.4.0/24 exact
    user@R4# set policy-statement send-static term 2 from route-filter 172.16.5.0/24 exact
    user@R4# set policy-statement send-static term 2 from route-filter 172.16.6.0/24 exact
    user@R4# set policy-statement send-static term 2 from route-filter 172.16.7.0/24 exact
    user@R4# set policy-statement send-static term 2 then community add R3_PREFERRED
    user@R4# set policy-statement send-static term 2 then accept
    user@R4# set policy-statement send-static term 3 then reject
    
  5. Configure as rotas estáticas.

    content_copy zoom_out_map
    [edit routing-options static]
    user@R4# set route 172.16.0.0/24 reject
    user@R4# set route 172.16.1.0/24 reject
    user@R4# set route 172.16.2.0/24 reject
    user@R4# set route 172.16.3.0/24 reject
    user@R4# set route 172.16.4.0/24 reject
    user@R4# set route 172.16.5.0/24 reject
    user@R4# set route 172.16.6.0/24 reject
    user@R4# set route 172.16.7.0/24 reject
    
  6. Configure o número do sistema autônomo (AS) e o ID do roteador.

    content_copy zoom_out_map
    [edit routing-options]
    user@R4# set router-id 192.168.0.4
    user@R4# set autonomous-system 64511
    

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.

Dispositivo R1

content_copy zoom_out_map
user@R1# show interfaces
ge-0/0/0 {
    unit 0 {
        family inet {
            address 10.0.0.1/30;
        }
    }
}
ge-0/0/1 {
    unit 0 {
        family inet {
            address 10.1.0.5/30;
        }
    }
}
ge-0/0/2 {
    unit 0 {
        family inet {
            address 10.0.0.14/30;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 192.168.0.1/32;
        }
    }
}
content_copy zoom_out_map
user@R1# show protocols
bgp {
    group int {
        type internal;
        local-address 192.168.0.1;
        export send-direct;
        neighbor 192.168.0.2;
        neighbor 192.168.0.3;
    }
    group ext {
        type external;
        import change-local-preference;
        peer-as 64511;
        neighbor 10.0.0.13;
    }
}
ospf {
    area 0.0.0.0 {
        interface ge-0/0/0.0;
        interface ge-0/0/1.0;
        interface lo0.0 {
            passive;
        }
    }
}
content_copy zoom_out_map
user@R1# show policy-options
policy-statement change-local-preference {
    term find-R1-routes {
        from community R1_PREFERRED;
        then {
            local-preference 200;
        }
    }
    term find-R3-routes {
        from community R3_PREFERRED;
        then {
            local-preference 50;
        }
    }
}
policy-statement send-direct {
    term 1 {
        from {
            protocol direct;
            route-filter 10.0.0.12/30 exact;
        }
        then accept;
    }
}
community R3_PREFERRED members 64511:3;
community R1_PREFERRED members 64511:1;
content_copy zoom_out_map
user@R1# show routing-options
router-id 192.168.0.1;
autonomous-system 64510;

Dispositivo R4

content_copy zoom_out_map
user@R4# show interfaces
ge-0/0/0 {
    unit 0 {
        family inet {
            address 10.0.0.13/30;
        }
    }
}
ge-0/0/1 {
    unit 0 {
        family inet {
            address 10.0.0.9/30;
        }
    }
}
lo0 {
    unit 0 {
        family inet {
            address 192.168.0.4/32;
        }
    }
}
content_copy zoom_out_map
user@R4# show protocols
bgp {
    group to-R1 {
        type external;
        export send-static;
        peer-as 64510;
        neighbor 10.0.0.14;
    }
    group to-R3 {
        type external;
        export send-static;
        peer-as 64510;
        neighbor 10.0.0.10;
    }
}
content_copy zoom_out_map
user@R4# show policy-options
policy-statement send-static {
    term 1 {
        from {
            protocol static;
            route-filter 172.16.0.0/24 exact;
            route-filter 172.16.1.0/24 exact;
            route-filter 172.16.2.0/24 exact;
            route-filter 172.16.3.0/24 exact;
        }
        then {
            community add R1_PREFERRED;
            accept;
        }
    }
    term 2 {
        from {
            protocol static;
            route-filter 172.16.4.0/24 exact;
            route-filter 172.16.5.0/24 exact;
            route-filter 172.16.6.0/24 exact;
            route-filter 172.16.7.0/24 exact;
        }
        then {
            community add R3_PREFERRED;
            accept;
        }
    }
    term 3 {
        then reject;
    }
}
community R3_PREFERRED members 64511:3;
community R1_PREFERRED members 64511:1;
content_copy zoom_out_map
user@R4# show routing-options
router-id 192.168.0.4;
autonomous-system 64511;
static {
    route 172.16.0.0/24 reject;
    route 172.16.1.0/24 reject;
    route 172.16.2.0/24 reject;
    route 172.16.3.0/24 reject;
    route 172.16.4.0/24 reject;
    route 172.16.5.0/24 reject;
    route 172.16.6.0/24 reject;
    route 172.16.7.0/24 reject;
}

Se você terminar de configurar os dispositivos, entre no commit modo de configuração.

Verificação

Confirme se a configuração está funcionando corretamente.

Verificação das rotas enviadas no dispositivo R4

Propósito

No dispositivo R4, verifique as rotas enviadas para o dispositivo R1 e o dispositivo R3.

Ação

content_copy zoom_out_map
user@R4> show route advertising-protocol bgp 10.0.0.14 extensive

inet.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
* 172.16.0.0/24 (1 entry, 1 announced)
 BGP group to-R1 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:1

* 172.16.1.0/24 (1 entry, 1 announced)
 BGP group to-R1 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:1

* 172.16.2.0/24 (1 entry, 1 announced)
 BGP group to-R1 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:1

* 172.16.3.0/24 (1 entry, 1 announced)
 BGP group to-R1 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:1

* 172.16.4.0/24 (1 entry, 1 announced)
 BGP group to-R1 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:3

* 172.16.5.0/24 (1 entry, 1 announced)
 BGP group to-R1 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:3

* 172.16.6.0/24 (1 entry, 1 announced)
 BGP group to-R1 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:3

* 172.16.7.0/24 (1 entry, 1 announced)
 BGP group to-R1 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:3

content_copy zoom_out_map
user@R4> show route advertising-protocol bgp 10.0.0.10 extensive

inet.0: 13 destinations, 13 routes (13 active, 0 holddown, 0 hidden)
* 172.16.0.0/24 (1 entry, 1 announced)
 BGP group to-R3 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:1

* 172.16.1.0/24 (1 entry, 1 announced)
 BGP group to-R3 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:1

* 172.16.2.0/24 (1 entry, 1 announced)
 BGP group to-R3 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:1

* 172.16.3.0/24 (1 entry, 1 announced)
 BGP group to-R3 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:1

* 172.16.4.0/24 (1 entry, 1 announced)
 BGP group to-R3 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:3

* 172.16.5.0/24 (1 entry, 1 announced)
 BGP group to-R3 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:3

* 172.16.6.0/24 (1 entry, 1 announced)
 BGP group to-R3 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:3

* 172.16.7.0/24 (1 entry, 1 announced)
 BGP group to-R3 type External
     Nexthop: Self
     AS path: [64511] I
     Communities: 64511:3

Significado

O dispositivo R4 marcou as rotas com as comunidades 64511:1 e 64511:3 e as enviou para o dispositivo R1 e R3.

Verificação das rotas recebidas no dispositivo R2

Propósito

No dispositivo R2, verifique as rotas recebidas do dispositivo R1 e do dispositivo R3.

Ação

content_copy zoom_out_map
user@R2> show route receive-protocol bgp 192.168.0.1

inet.0: 25 destinations, 25 routes (25 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.0.0.12/30            192.168.0.1                  100        I
* 172.16.0.0/24           10.0.0.13                    200        64511 I
* 172.16.1.0/24           10.0.0.13                    200        64511 I
* 172.16.2.0/24           10.0.0.13                    200        64511 I
* 172.16.3.0/24           10.0.0.13                    200        64511 I
content_copy zoom_out_map
user@R2> show route receive-protocol bgp 192.168.0.3

inet.0: 25 destinations, 25 routes (25 active, 0 holddown, 0 hidden)
  Prefix                  Nexthop              MED     Lclpref    AS path
* 10.0.0.8/30             192.168.0.3                  100        I
* 172.16.4.0/24           10.0.0.9                     200        64511 I
* 172.16.5.0/24           10.0.0.9                     200        64511 I
* 172.16.6.0/24           10.0.0.9                     200        64511 I
* 172.16.7.0/24           10.0.0.9                     200        64511 I
content_copy zoom_out_map
user@R2> show route match-prefix 172.16.*

inet.0: 25 destinations, 25 routes (25 active, 0 holddown, 0 hidden)
+ = Active Route, - = Last Active, * = Both

172.16.0.0/24      *[BGP/170] 1w3d 00:02:11, localpref 200, from 192.168.0.1
                      AS path: 64511 I, validation-state: unverified
                    >  to 10.0.0.1 via ge-0/0/0.0
172.16.1.0/24      *[BGP/170] 1w3d 00:02:11, localpref 200, from 192.168.0.1
                      AS path: 64511 I, validation-state: unverified
                    >  to 10.0.0.1 via ge-0/0/0.0
172.16.2.0/24      *[BGP/170] 1w3d 00:02:11, localpref 200, from 192.168.0.1
                      AS path: 64511 I, validation-state: unverified
                    >  to 10.0.0.1 via ge-0/0/0.0
172.16.3.0/24      *[BGP/170] 1w3d 00:02:11, localpref 200, from 192.168.0.1
                      AS path: 64511 I, validation-state: unverified
                    >  to 10.0.0.1 via ge-0/0/0.0
172.16.4.0/24      *[BGP/170] 1w3d 00:01:50, localpref 200, from 192.168.0.3
                      AS path: 64511 I, validation-state: unverified
                    >  to 10.1.0.2 via ge-0/0/1.0
172.16.5.0/24      *[BGP/170] 1w3d 00:01:50, localpref 200, from 192.168.0.3
                      AS path: 64511 I, validation-state: unverified
                    >  to 10.1.0.2 via ge-0/0/1.0
172.16.6.0/24      *[BGP/170] 1w3d 00:01:50, localpref 200, from 192.168.0.3
                      AS path: 64511 I, validation-state: unverified
                    >  to 10.1.0.2 via ge-0/0/1.0
172.16.7.0/24      *[BGP/170] 1w3d 00:01:50, localpref 200, from 192.168.0.3
                      AS path: 64511 I, validation-state: unverified
                    >  to 10.1.0.2 via ge-0/0/1.0

Significado

O dispositivo R2 tem as rotas com as preferências locais esperadas e as rotas ativas esperadas, conforme designado pelos asterisco (*).

Exemplo: Configuração de uma política de roteamento com base no número de comunidades BGP
footer-navigation