La documentazione per questo prodotto è stata redatta cercando di utilizzare un linguaggio senza pregiudizi. Ai fini di questa documentazione, per linguaggio senza di pregiudizi si intende un linguaggio che non implica discriminazioni basate su età, disabilità, genere, identità razziale, identità etnica, orientamento sessuale, status socioeconomico e intersezionalità. Le eventuali eccezioni possono dipendere dal linguaggio codificato nelle interfacce utente del software del prodotto, dal linguaggio utilizzato nella documentazione RFP o dal linguaggio utilizzato in prodotti di terze parti a cui si fa riferimento. Scopri di più sul modo in cui Cisco utilizza il linguaggio inclusivo.
Cisco ha tradotto questo documento utilizzando una combinazione di tecnologie automatiche e umane per offrire ai nostri utenti in tutto il mondo contenuti di supporto nella propria lingua. Si noti che anche la migliore traduzione automatica non sarà mai accurata come quella fornita da un traduttore professionista. Cisco Systems, Inc. non si assume alcuna responsabilità per l’accuratezza di queste traduzioni e consiglia di consultare sempre il documento originale in inglese (disponibile al link fornito).
In questo documento viene descritto il motivo per cui il router della succursale secondaria non è in grado di apprendere il mapping di Auto-RP (Rendezvous Point) e vengono fornite le procedure per risolvere il problema.
In una configurazione con router a doppio confine presso una filiale SD-WAN, il router SD-WAN principale può apprendere i messaggi di mappatura Auto-RP, a differenza del router SD-WAN secondario. Se il router SD-WAN scelto come Protocol Independent Multicast (PIM) Assert Forwarder non ha appreso i mapping Auto-RP, anche gli switch a valle della filiale non riceveranno questi mapping.
ip pim rp-address 169.1.224.1 override
ip pim autorp listener
ip pim send-rp-announce Loopback1 scope 30 group-list RP-Groups
ip pim send-rp-discovery Loopback0 scope 30
ip pim ssm range PIM-SSM-Range
dc1-9k-01#sh ip access-lists RP-Groups
Standard IP access list RP-Groups
30 permit 239.1.0.0, wildcard bits 0.0.255.255
Branch-9k#sh ip pim rp mapping
PIM Group-to-RP Mappings
Branch-9k#
Configurazioni PIM sullo switch:
Branch-9k#sh run | in pim
ip pim sparse-mode
ip pim sparse-mode
ip pim sparse-mode
ip pim autorp listener
ip pim ssm range PIM-SSM-Range
Branch-9k#
Branch-C8300-01#sh ip mfib vrf 10 224.0.1.40
Entry Flags: C - Directly Connected, S - Signal, IA - Inherit A flag,
ET - Data Rate Exceeds Threshold, K - Keepalive
DDE - Data Driven Event, HW - Hardware Installed
ME - MoFRR ECMP entry, MNE - MoFRR Non-ECMP entry, MP - MFIB
MoFRR Primary, RP - MRIB MoFRR Primary, P - MoFRR Primary
MS - MoFRR Entry in Sync, MC - MoFRR entry in MoFRR Client,
e - Encap helper tunnel flag.
I/O Item Flags: IC - Internal Copy, NP - Not platform switched,
NS - Negate Signalling, SP - Signal Present,
A - Accept, F - Forward, RA - MRIB Accept, RF - MRIB Forward,
MA - MFIB Accept, A2 - Accept backup,
RA2 - MRIB Accept backup, MA2 - MFIB Accept backup
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kbits per second
Other counts: Total/RPF failed/Other drops
I/O Item Counts: HW Pkt Count/FS Pkt Count/PS Pkt Count Egress Rate in pps
VRF 10
(*,224.0.1.40) Flags: C HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 1741/1741/0
Lspvif0, LSM/0, RPF-ID: *, Flags: F NS
Pkts: 0/0/0 Rate: 0 pps
GigabitEthernet0/0/0.100 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
(169.1.10.3,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 29642/29642/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: IC
(169.1.10.4,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 29939/29939/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A NS
GigabitEthernet0/0/0.100 Flags: IC
(169.1.20.2,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 47783/47783/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: IC
(169.1.20.6,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 47720/47720/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: IC
(169.1.20.10,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 47784/47784/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: IC
(169.1.20.14,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 47724/47724/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: IC
(169.1.100.7,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 60088/60088/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: IC
(169.2.20.2,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 47680/47680/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: IC
(169.2.20.6,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 47640/47640/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: IC
Branch-C8300-01#
Branch-C8300-02#sh ip mfib vrf 10 224.0.1.40
Entry Flags: C - Directly Connected, S - Signal, IA - Inherit A flag,
ET - Data Rate Exceeds Threshold, K - Keepalive
DDE - Data Driven Event, HW - Hardware Installed
ME - MoFRR ECMP entry, MNE - MoFRR Non-ECMP entry, MP - MFIB
MoFRR Primary, RP - MRIB MoFRR Primary, P - MoFRR Primary
MS - MoFRR Entry in Sync, MC - MoFRR entry in MoFRR Client,
e - Encap helper tunnel flag.
I/O Item Flags: IC - Internal Copy, NP - Not platform switched,
NS - Negate Signalling, SP - Signal Present,
A - Accept, F - Forward, RA - MRIB Accept, RF - MRIB Forward,
MA - MFIB Accept, A2 - Accept backup,
RA2 - MRIB Accept backup, MA2 - MFIB Accept backup
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kbits per second
Other counts: Total/RPF failed/Other drops
I/O Item Counts: HW Pkt Count/FS Pkt Count/PS Pkt Count Egress Rate in pps
VRF 10
(*,224.0.1.40) Flags: C HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 10549/10549/0
Lspvif0, LSM/0, RPF-ID: *, Flags: F NS
Pkts: 0/0/0 Rate: 0 pps
GigabitEthernet0/0/0.100 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
(169.1.10.3,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A NS
GigabitEthernet0/0/0.100 Flags: F IC NS <==
Pkts: 0/0/0 Rate: 0 pps
(169.1.10.4,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A NS
GigabitEthernet0/0/0.100 Flags: F IC NS <==
Pkts: 0/0/0 Rate: 0 pps
(169.1.20.2,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
(169.1.20.6,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
(169.1.20.10,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A NS
GigabitEthernet0/0/0.100 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
(169.1.20.14,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A NS
GigabitEthernet0/0/0.100 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
(169.2.20.2,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
(169.2.20.6,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
Lspvif0, LSM/0, RPF-ID: *, Flags: A
GigabitEthernet0/0/0.100 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
Branch-C8300-02#
Il flag F impostato indica che il router Branch-C8300-02 è il server d'inoltro designato per AutoRP e per il traffico multicast. Quando i router adiacenti PIM si trovano nello stesso dominio di trasmissione, viene selezionato il server d'inoltro di asserzione PIM/server d'inoltro designato. Il router con l'indirizzo IP più alto viene scelto come server d'inoltro di asserzione PIM/server d'inoltro designato. (La distanza amministrativa (AD) e la metrica sono uguali). In questo scenario, il router di succursale 2 ha un indirizzo IP più alto rispetto al router di succursale 1:
Branch-C8300-01#sh run interface Gi0/0/0.100
Building configuration...
Current configuration : 336 bytes
!
interface GigabitEthernet0/0/0.100
description OSPF peering interface1
encapsulation dot1Q 100
vrf forwarding 10
ip address 169.101.10.1 255.255.255.240
no ip redirects
ip pim sparse-mode
ip nbar protocol-discovery
ip ospf network broadcast
ip ospf dead-interval 40
ip ospf 10 area 0
ip ospf cost 10
arp timeout 1200
end
Branch-C8300-02#sh run interface Gi0/0/0.100
Building configuration...
Current configuration : 336 bytes
!
interface GigabitEthernet0/0/0.100
description OSPF peering interface1
encapsulation dot1Q 100
vrf forwarding 10
ip address 169.101.10.2 255.255.255.240
no ip redirects
ip pim sparse-mode
ip nbar protocol-discovery
ip ospf network broadcast
ip ospf dead-interval 40
ip ospf 10 area 0
ip ospf cost 15
arp timeout 1200
end
Branch-C8300-01#sh ip pim vrf 10 rp mapping
PIM Group-to-RP Mappings
Group(s) 239.195.0.0/16
RP 10.125.125.1 (?), v2v1
Info source: 169.254.100.9 (?), elected via Auto-RP
Uptime: 1w0d, expires: 00:02:31
Branch-C8300-01#
Branch-C8300-02#sh ip pim vrf 10 rp mapping
PIM Group-to-RP Mappings
Branch-C8300-02#
DC-8500-01#sh ip mfib vrf 10 224.0.1.40
Entry Flags: C - Directly Connected, S - Signal, IA - Inherit A flag,
ET - Data Rate Exceeds Threshold, K - Keepalive
DDE - Data Driven Event, HW - Hardware Installed
ME - MoFRR ECMP entry, MNE - MoFRR Non-ECMP entry, MP - MFIB
MoFRR Primary, RP - MRIB MoFRR Primary, P - MoFRR Primary
MS - MoFRR Entry in Sync, MC - MoFRR entry in MoFRR Client,
e - Encap helper tunnel flag.
I/O Item Flags: IC - Internal Copy, NP - Not platform switched,
NS - Negate Signalling, SP - Signal Present,
A - Accept, F - Forward, RA - MRIB Accept, RF - MRIB Forward,
MA - MFIB Accept, A2 - Accept backup,
RA2 - MRIB Accept backup, MA2 - MFIB Accept backup
Forwarding Counts: Pkt Count/Pkts per second/Avg Pkt Size/Kbits per second
Other counts: Total/RPF failed/Other drops
I/O Item Counts: HW Pkt Count/FS Pkt Count/PS Pkt Count Egress Rate in pps
VRF 10
(*,224.0.1.40) Flags: C HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 294/294/0
TenGigabitEthernet0/0/0.10 Flags: F IC NS
Pkts: 0/0/0 Rate: 0 pps
Lspvif0, LSM/1, RPF-ID: *, Flags: F NS
Pkts: 0/0/0 Rate: 0 pps
(169.1.10.4,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
TenGigabitEthernet0/0/0.10 Flags: A IC
Lspvif0, LSM/1, RPF-ID: *, Flags: F
Pkts: 0/0/0 Rate: 0 pps
(169.1.20.2,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
TenGigabitEthernet0/0/0.10 Flags: A IC
Lspvif0, LSM/1, RPF-ID: *, Flags: F
Pkts: 0/0/0 Rate: 0 pps
(169.1.20.6,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
TenGigabitEthernet0/0/0.10 Flags: A IC
Lspvif0, LSM/1, RPF-ID: *, Flags: F
Pkts: 0/0/0 Rate: 0 pps
(169.1.20.10,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
TenGigabitEthernet0/0/0.10 Flags: A IC
Lspvif0, LSM/1, RPF-ID: *, Flags: F
Pkts: 0/0/0 Rate: 0 pps
(169.1.20.14,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
TenGigabitEthernet0/0/0.10 Flags: A IC
Lspvif0, LSM/1, RPF-ID: *, Flags: F
Pkts: 0/0/0 Rate: 0 pps
(169.1.100.7,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
TenGigabitEthernet0/0/0.10 Flags: A IC
Lspvif0, LSM/1, RPF-ID: *, Flags: F <==
Pkts: 0/0/0 Rate: 0 pps
(169.2.20.2,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
TenGigabitEthernet0/0/0.10 Flags: A IC
Lspvif0, LSM/1, RPF-ID: *, Flags: F
Pkts: 0/0/0 Rate: 0 pps
(169.2.20.6,224.0.1.40) Flags: HW
SW Forwarding: 0/0/0/0, Other: 0/0/0
HW Forwarding: 0/0/0/0, Other: 0/0/0
TenGigabitEthernet0/0/0.10 Flags: A IC
Lspvif0, LSM/1, RPF-ID: *, Flags: F
Pkts: 0/0/0 Rate: 0 pps
Lspvif0 è l'interfaccia del tunnel virtuale come il tunnel Point-to-Multipoint (P2MP), ovvero un endpoint a più endpoint remoti. Il tunnel Lspvif0 viene utilizzato nel multicast SD-WAN. Lspvif0 è il tunnel virtuale che indica che i pacchetti vengono trasmessi tramite l'overlay SD-WAN.
DC-8500-01#sh interfaces Lspvif0
Lspvif0 is up, line protocol is up
Hardware is
Interface is unnumbered. Using address of SD-WAN-system-intf (169.1.100.3)
MTU 17892 bytes, BW 10000000 Kbit/sec, DLY 5000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation LOOPBACK, loopback not set
Keepalive set (10 sec)
Last input never, output 00:00:10, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/0 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
3 packets input, 210 bytes, 0 no buffer
Received 0 broadcasts (3 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1628856 packets output, 71967520 bytes, 0 underruns
Output 0 broadcasts (1289488 IP multicasts)
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
LSM/1 nell'output MFIB indica l'elenco di replica collegato al tunnel Lspvif0.
Come per la progettazione di Cisco SD-WAN Multicast, il router DC apprende i router di filiale abilitati per PIM tramite il protocollo OMP (Overlay Management Protocol) e l'IP di sistema di questi router di filiale vengono aggiunti all'elenco di replica.
DC-8500-01#sh SD-WAN omp multicast-auto-discover
Code:
C -> chosen
I -> installed
Red -> redistributed
Rej -> rejected
L -> looped
R -> resolved
S -> stale
Ext -> extranet
Stg -> staged
IA -> On-demand inactive
Inv -> invalid
BR-R -> border-router reoriginated
TGW-R -> transport-gateway reoriginated
ADDRESS SOURCE FROM
FAMILY TENANT VPN ORIGINATOR PEER STATUS
---------------------------------------------------------
ipv4 0 10 169.1.100.3 0.0.0.0 C,Red,R
0 10 169.1.100.4 2.2.2.1 Inv,U
2.2.2.2 Inv,U
0 10 169.101.100.1 2.2.2.1 C,R
2.2.2.2 C,I,R
0 10 169.101.100.2 2.2.2.1 C,R
2.2.2.2 C,I,R
Nota: I pacchetti AutoRP provenienti dal router DC verranno inviati ai router delle filiali tramite il tunnel BFD SD-WAN (Dataplane). Il router DC incapsula i pacchetti AutoRP al tunnel IPsec e li inoltra ai router della succursale.
DC-8500-01#sh mvpn replication lsm-id 1
Repl ID : 1FFFFF LSM ID : 1 Uptime : 1w3d
Path Set ID : 25
Replication branches: 2
IR (169.101.100.1)
Uptime : 1w3d Refcount : 2
Remote Label : 1006
IR (169.101.100.2)
Uptime : 1w3d Refcount : 2
Remote Label : 1004
DC-8500-01#sh platform software SD-WAN f0 next-hop indirect all
Show SD-WAN next-hop oce all :
OCE ID: 0xf8000d9f, OCE Type: SD-WAN_NH_INDIRECT
Indirect: client_handle 0x5649f38aaa80, ppe addr 418b02c0
nhobj_type: SD-WAN_NH_LOCAL_SLA_CLASS, nhobj_handle: 0xf80805cf
label: 1006, dst_vpn: 10, nexthop sys_ip: 169.101.100.1, sla_class: 1
La catena OCE indiretta è la catena di inoltro interna creata quando il router DC apprende i percorsi unicast dal rispettivo router di succursale. Questa procedura è conforme alla progettazione del multicast SD-WAN, in cui il multicast sfrutta il routing unicast per inoltrare le informazioni RP multicast.
Il motivo per cui il router DC non inoltra il mapping AutoRP al router 02 della diramazione è che l'OCE indiretto è creato solo per il router 01 della diramazione, ma non per il router 02 della diramazione. Solo quando la catena di inoltro interna viene stabilita al router della rispettiva diramazione, il router DC inoltra il mapping AutoRP a tale router della diramazione.
DC-8500-01#sh ip route vrf 10 omp
Routing Table: 10
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, m - OMP
n - NAT, Ni - NAT inside, No - NAT outside, Nd - NAT DIA
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
H - NHRP, G - NHRP registered, g - NHRP registration summary
o - ODR, P - periodic downloaded static route, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR
& - replicated local route overrides by connected
Gateway of last resort is 169.1.10.1 to network 0.0.0.0
m 169.101.0.0/16 [251/0] via 169.101.100.1, 2w0d, SD-WAN-system-intf
DC-8500-01#
DC-8500-01#sh SD-WAN omp routes 169.101.0.0/16
Code:
C -> chosen
I -> installed
Red -> redistributed
Rej -> rejected
L -> looped
R -> resolved
S -> stale
Ext -> extranet
Inv -> invalid
Stg -> staged
IA -> On-demand inactive
U -> TLOC unresolved
BR-R -> border-router reoriginated
TGW-R -> transport-gateway reoriginated
AFFINITY
PATH ATTRIBUTE GROUP
TENANT VPN PREFIX FROM PEER ID LABEL STATUS TYPE TLOC IP COLOR ENCAP PREFERENCE NUMBER REGION ID REGION PATH
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
0 10 169.101.0.0/16 2.2.2.1 15 1004 R installed 169.101.100.2 public-internet ipsec - None None -
2.2.2.1 19 1006 C,I,R installed 169.101.100.1 biz-internet ipsec - None None -
2.2.2.2 16 1004 R installed 169.101.100.2 public-internet ipsec - None None -
2.2.2.2 21 1006 C,R installed 169.101.100.1 biz-internet ipsec - None None -
DC-8500-01#
Il motivo per cui le route apprese dal router secondario non vengono installate in RIB è che le route apprese dal router secondario hanno un costo OSPF più alto rispetto al router primario:
DC-8500-01#sh SD-WAN omp routes 169.101.0.0/16 detail
--------------------------------------------------------------------------
omp route entries for tenant-id 0 vpn 10 route 169.101.0.0/16
--------------------------------------------------------------------------
RECEIVED FROM:
peer 2.2.2.1
path-id 15
label 1004
status R
loss-reason origin-metric
lost-to-peer 2.2.2.1
lost-to-path-id 19
Attributes:
originator 169.101.100.2
type installed
tloc 169.101.100.2, public-internet, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 10
preference not set
affinity-group None
region-id None
region-path not set
route-reoriginator not set
tag not set
origin-proto OSPF-external-1
origin-metric 35
as-path not set
community not set
unknown-attr-len not set
RECEIVED FROM:
peer 2.2.2.1
path-id 19
label 1006
status C,I,R
loss-reason not set
lost-to-peer not set
lost-to-path-id not set
Attributes:
originator 169.101.100.1
type installed
tloc 169.101.100.1, biz-internet, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 10
preference not set
affinity-group None
region-id None
region-path not set
route-reoriginator not set
tag not set
origin-proto OSPF-external-1
origin-metric 30
as-path not set
community not set
unknown-attr-len not set
RECEIVED FROM:
peer 2.2.2.2
path-id 16
label 1004
status R
loss-reason origin-metric
lost-to-peer 2.2.2.2
lost-to-path-id 21
Attributes:
originator 169.101.100.2
type installed
tloc 169.101.100.2, public-internet, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 10
preference not set
affinity-group None
region-id None
region-path not set
route-reoriginator not set
tag not set
origin-proto OSPF-external-1
origin-metric 35
as-path not set
community not set
unknown-attr-len not set
RECEIVED FROM:
peer 2.2.2.2
path-id 21
label 1006
status C,R
loss-reason not set
lost-to-peer not set
lost-to-path-id not set
Attributes:
originator 169.101.100.1
type installed
tloc 169.101.100.1, biz-internet, ipsec
ultimate-tloc not set
domain-id not set
overlay-id 1
site-id 10
preference not set
affinity-group None
region-id None
region-path not set
route-reoriginator not set
tag not set
origin-proto OSPF-external-1
origin-metric 30
as-path not set
community not set
unknown-attr-len not set
DC-8500-01#
omp
no shutdown
send-path-limit 16
ecmp-limit 16
graceful-restart
no as-dot-notation
timers
holdtime 300
advertisement-interval 1
graceful-restart-timer 43200
eor-timer 300
exit
address-family ipv4 vrf 10
advertise ospf external <==
!
address-family ipv6
advertise connected
advertise static
Branch-C8300-02#sh run interface Lo0
Building configuration...
Current configuration : 151 bytes
!
interface Loopback0
description Management loopback
vrf forwarding 10
ip address 169.101.100.2 255.255.255.255
no ip redirects
ip mtu 1500
end
Configurazioni OMP sul router di succursale 02 per annunciare le route connesse:
omp
no shutdown
overlay-as 65376
send-path-limit 16
ecmp-limit 16
graceful-restart
no as-dot-notation
timers
holdtime 60
advertisement-interval 1
graceful-restart-timer 43200
eor-timer 300
exit
address-family ipv4 vrf 10
advertise ospf external
advertise connected <==
!
address-family ipv6
advertise connected
advertise static
!
!
Viene ora visualizzato il mapping AutoRP appreso sul router di succursale 02:
Branch-C8300-02# sh ip pim vrf 10 rp mapping
PIM Group-to-RP Mappings
Group(s) 239.195.0.0/16
RP 10.125.125.1 (?), v2v1
Info source: 169.1.10.4 (terin.net.afrihost.co.za), elected via Auto-RP
Uptime: 00:02:18, expires: 00:02:47
Branch-C8300-02#
Analogamente, è possibile visualizzare il mapping AutoRP appreso anche sullo switch di diramazione:
Branch-9k#sh ip pim rp mapping
PIM Group-to-RP Mappings
Group(s) 239.195.0.0/16
RP 10.125.125.1 (?), v2v1
Info source: 169.254.100.9 (?), elected via Auto-RP
Uptime: 00:03:36, expires: 00:02:46
Acl: RP-Region-Ent-Sites, Static-Override
RP: 10.125.125.1 (?)
Quando si controlla l'output della catena di inoltro/OCE indiretto sul router DC, sono presenti voci per l'indirizzo ip del sistema dei router delle sedi principali e secondarie:
DC-8500-01#sh platform software SD-WAN f0 next-hop indirect all
Show SD-WAN next-hop oce all :
OCE ID: 0xf80009bf, OCE Type: SD-WAN_NH_INDIRECT
Indirect: client_handle 0x5649f389fbc0, ppe addr 418b05c0
nhobj_type: SD-WAN_NH_LOCAL_SLA_CLASS, nhobj_handle: 0xf808044f
label: 1006, dst_vpn: 10, nexthop sys_ip: 169.101.100.1, sla_class: 1
OCE ID: 0xf80009df, OCE Type: SD-WAN_NH_INDIRECT
Indirect: client_handle 0x5649f38a11f0, ppe addr 418b06d0
nhobj_type: SD-WAN_NH_LOCAL_SLA_CLASS, nhobj_handle: 0xf808045f
label: 1004, dst_vpn: 10, nexthop sys_ip: 169.101.100.2, sla_class: 1
Ora si vede che il router DC RIB ha anche prefissi appresi dal router 02 della diramazione installato.
DC-8500-01#sh ip route vrf 10 omp
Routing Table: 10
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, m - OMP
n - NAT, Ni - NAT inside, No - NAT outside, Nd - NAT DIA
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
H - NHRP, G - NHRP registered, g - NHRP registration summary
o - ODR, P - periodic downloaded static route, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR
& - replicated local route overrides by connected
Gateway of last resort is 169.1.10.1 to network 0.0.0.0
169.101.0.0/16 is variably subnetted, 3 subnets, 3 masks
m 169.101.0.0/16 [251/0] via 169.101.100.1, 13:59:47, SD-WAN-system-intf
m 169.101.10.0/28
[251/0] via 169.101.100.2, 00:07:50, SD-WAN-system-intf
m 169.101.100.2/32
[251/0] via 169.101.100.2, 00:07:50, SD-WAN-system-intf
Durante l'implementazione del multicast su Cisco SD-WAN, è necessario accertarsi che tutti i router remoti (compresi i router principali e secondari) pubblicizzino il prefisso unicast al router SD-WAN più vicino a RP tramite OMP. Il multicast SD-WAN sfrutta il routing unicast per creare la catena di inoltro necessaria per la trasmissione delle informazioni sul control plane multicast.
Revisione | Data di pubblicazione | Commenti |
---|---|---|
1.0 |
15-May-2025
|
Versione iniziale |