...
Code Block |
---|
language | text |
---|
title | show pim vrf testvrf topology: |
---|
|
R2# show pim vrf testvrf topology
Mon Nov 28 02:54:45 2022
IP PIM Multicast Topology Table
Entry state: (*/S,G)[RPT/SPT] Mode, Protocol, Uptime, Info
Interface state: Name, Uptime, Fwd, Info
(10.168.20.2, 239.1.1.10) SPT, asm, Up: 00h02m02s
JP: joined (never), RPF: pmsi/2:100/1.1.1.1/21, (1.1.1.1)
(10.168.20.2, 239.1.1.10) RPT not-prune, Up: 00h00m00s
(*, 239.1.1.10) asm, Up: 00h02m01s, RP: 2.2.2.2 is local (config)
JP: joined (never), RPF: unknown, (0.0.0.0)
te0/0/6 asm, Up: 00h02m01s is local
R1# show pim vrf testvrf topology
Mon Nov 28 02:53:28 2022
IP PIM Multicast Topology Table
Entry state: (*/S,G)[RPT/SPT] Mode, Protocol, Uptime, Info
Interface state: Name, Uptime, Fwd, Info
(10.168.20.2, 239.1.1.10) SPT, asm, Up: 00h02m53s
JP: joined (never), RPF: Tengigabitethernet0/0/6, (10.168.20.2)
pmsi/1:100/1.1.1.1/21 asm, Up: 00h02m19s is local |
Начиная с версии 3.9.1.140R был добавлен функционал построения RSVP- P2MP туннелей для MVPN сервиса. Для его работы требуется перевести транспорт на MPLS RSVP, включить поддержку RSVP P2MP туннелей в конфигурации VRF. Приведем пример конфигурации R1(На остальных маршрутизаторах конфигурация идентична):
Code Block |
---|
language | text |
---|
title | Конфигурация RSVP P2MP: |
---|
|
interface loopback 1
ipv4 address 1.1.1.1/32
interface loopback 10
ipv4 address 1.1.1.1/32
vrf testvrf
interface tengigabitethernet 0/0/1
description "To R2"
ipv4 address 10.0.0.1/30
load-interval 20
interface tengigabitethernet 0/0/6
description "Server Multicast"
ipv4 address 10.168.20.1/24
vrf testvrf
interface tengigabitethernet 0/0/11
description "To R3"
ipv4 address 10.0.0.13/30
load-interval 20
vrf testvrf
export route-target 100:100
import route-target 100:100
mvpn <<<<< Создание обработчика MVPN
provider-tunnel-type rsvp-p2mp <<<<< Выбираем тип туннелей для MVPN
exit
rd 1:100
mpls
forwarding
interface loopback 1
interface tengigabitethernet 0/0/1
interface tengigabitethernet 0/0/11
exit
router-id 1.1.1.1
transport-address 1.1.1.1
exit
rsvp
interface tengigabitethernet 0/0/1
exit
interface tengigabitethernet 0/0/11
exit
tunnel to_R2
destination 2.2.2.2
forwarding-adjacency <<<<< Данная команда позволяет осуществить форвардинг сервисного трафика через ТЕ-туннель
source 1.1.1.1
tunnel-lsp R1_to_R2
exit
tunnel to_R3
destination 3.3.3.3
forwarding-adjacency <<<<< Данная команда позволяет осуществить форвардинг сервисного трафика через ТЕ-туннель
source 1.1.1.1
tunnel-lsp R1_to_R3
exit
exit
exit
exit
router bgp 100
address-family ipv4 mvpn <<<<< Добавляем SAFI5 mvpn
exit
address-family vpnv4 unicast
exit
bgp router-id 1.1.1.1
neighbor 2.2.2.2
address-family ipv4 mvpn
advertisement-interval 0
exit
address-family vpnv4 unicast
exit
bfd fast-detect
remote-as 100
send-community
send-community-ext
update-source 1.1.1.1
exit
neighbor 3.3.3.3
address-family ipv4 mvpn
advertisement-interval 0
exit
address-family vpnv4 unicast
exit
bfd fast-detect
remote-as 100
send-community
send-community-ext
update-source 1.1.1.1
router isis 1
interface loopback 1
address-family ipv4 unicast
exit
passive
exit
interface tengigabitethernet 0/0/1
address-family ipv4 unicast
bfd fast-detect
exit
point-to-point
exit
interface tengigabitethernet 0/0/11
address-family ipv4 unicast
bfd fast-detect
exit
level level-2
exit
point-to-point
exit
ipv4-te-level level-2
microloop-avoidance rib-update-delay 140
net 49.0000.0000.1000.0000.00
spf interval maximum-wait 80
te-router-id 1.1.1.1 |
Проверим построение P2MP туннелей:
Code Block |
---|
language | text |
---|
title | show mpls rsvp lsps p2mp |
---|
|
show mpls rsvp lsps p2mp
Wed Oct 23 04:14:24 2024
Role: I - Ingress, T - Transit, E - Egress, * - Detour, # - Facility backup
Flags: E - Entropy Label Capability
Name Id Source P2MP-ID S2L Sub LSP Destination In/Out Label Role Flags State
---------------------------------------- ------ ----------------- ----------------- ------------------------- ----------------- ----- ------ ------
2.2.2.2:65534:mvpn:mvpn 65534 2.2.2.2 33686018 1.1.1.1 30/- E up
1.1.1.1:65535:mvpn:mvpn 65535 1.1.1.1 16843009 2.2.2.2 -/26 I up
2.2.2.2:65535:mvpn:mvpn 65535 2.2.2.2 33686018 1.1.1.1 29/- E up |
Более расширенную информация можно посмотреть с помощью команды show mpls rsvp lsps p2mp detailed:
Code Block |
---|
language | text |
---|
title | show mpls rsvp lsps p2mp detailed |
---|
|
show mpls rsvp lsps p2mp detailed
Wed Oct 23 04:16:16 2024
Tunnel: none, id: 65534
LSP name: none, signaled-name: 2.2.2.2:65534:mvpn:mvpn, id: 65534, P2MP-ID: 33686018, Source: 2.2.2.2
S2L Sub LSP: Destination 1.1.1.1, Sub Group ID: 1, Sub Group Originator ID: 2.2.2.2
State: up, Protection role: working
Direction: egress, Node protect: disabled, Bandwidth protection requirement: disabled
Carrying the normal traffic after protection switching: no
Protected by a fast reroute: none
Downstream repaired: yes
Path recording is not desired
SE Style is desired
LSP rerouting is none
OAM MEP entities are not desired
OAM MIP entities are not desired
TSpec: ave rate=0 bytes/s, burst=0 bytes, peak rate=inf bytes/s
FSpec: ave rate=0 bytes/s, burst=0 bytes, peak rate=inf bytes/s
Upstream information:
Signaling interface: Tengigabitethernet0/0/1
Neighbor: 10.0.0.2
Label: 30, type: mpls-label
Incoming ERO Outgoing ERO
---------------------------- ----------------------------
hop0 10.0.0.1/32
Tunnel: none, id: 65535
LSP name: none, signaled-name: 1.1.1.1:65535:mvpn:mvpn, id: 65535, P2MP-ID: 16843009, Source: 1.1.1.1
S2L Sub LSP: Destination 2.2.2.2, Sub Group ID: 1, Sub Group Originator ID: 1.1.1.1
State: up, Protection role: working
Direction: ingress, Node protect: disabled, Bandwidth protection requirement: disabled
Carrying the normal traffic after protection switching: no
Protected by a fast reroute: none
Downstream repaired: yes
Path recording is not desired
SE Style is desired
LSP rerouting is none
OAM MEP entities are not desired
OAM MIP entities are not desired
TSpec: ave rate=0 bytes/s, burst=0 bytes, peak rate=inf bytes/s
FSpec: ave rate=0 bytes/s, burst=0 bytes, peak rate=inf bytes/s
Downstream information:
Next hop: 10.0.0.2
Signaling interface: Tengigabitethernet0/0/1
Neighbor: 10.0.0.2
Label: 26, type: mpls-label
Incoming ERO Outgoing ERO
---------------------------- ----------------------------
hop0 10.0.0.1/32 10.0.0.2/32
hop1 10.0.0.2/32 |
Code Block |
---|
language | text |
---|
title | show bgp ipv4 mvpn |
---|
|
show bgp ipv4 mvpn
Wed Oct 23 05:06:09 2024
BGP router identifier 1.1.1.1, local AS number 100
Graceful Restart is disabled
BGP table state: active
Status codes: d damped, h history, > best, b backup, S stale, * active, u untracked, i internal
Origin codes: i igp, e egp, ? incomplete
Network Next hop Metric LocPrf Weight Path
------------------------ ---------------- ------- ------- ------- -----
> 1:100 [1][1.1.1.1]
1.1.1.1 0 100 0 i
>i 2:100 [1][2.2.2.2]
2.2.2.2 0 100 0 i
>i 2:100 [3][46.61.193.86][225.54.205.136][2.2.2.2]
2.2.2.2 0 100 0 i
> 2:100 [4][46.61.193.86][225.54.205.136][2.2.2.2][2.2.2.2]
1.1.1.1 0 100 0 i
>i 2:100 [5][46.61.193.86][225.54.205.136]
2.2.2.2 0 100 0 i
> 1:100 [6][100][2.2.2.2][225.54.205.136]
1.1.1.1 0 100 0 i
> 1:100 [7][100][46.61.193.86][225.54.205.136]
1.1.1.1 0 100 0 i |