Sto riscontrando un problema durante il recupero di un VPLS utilizzando un ME3600x con 15.3 (2) e segnalazione BGP. @yelfathi e @packettalk mi hanno indicato il percorso corretto ma non sono sicuro di come risolverlo.
Ho 2 switch ME3600 che usano RSVP come PE e 2 router MX80 come P.
I router P mostrano gli LSP come LSP di transito correttamente e i miei tunnel TE sono attivi. Su entrambi gli interruttori ottengo quanto segue: -
SW1.THN-LON#show mpls L2transport vc 501 detail
Local interface: VFI FLVPLS001 vfi up
Interworking type is Ethernet
Destination address: 46.226.0.10, VC ID: 501, VC status: down
Last error: MPLS dataplane reported a fault to the nexthop
Output interface: none, imposed label stack {}
Preferred path: not configured
Default path: no route
No adjacency
Create time: 00:19:42, last status change time: 00:19:42
Last label FSM state change time: 00:19:42
Signaling protocol: BGP
Status TLV support (local/remote) : Not Applicable
LDP route watch : Not Applicable
Label/status state machine : activating, LruRruD
Last local dataplane status rcvd: DOWN(pw-tx-fault)
Last BFD dataplane status rcvd: Not Applicable
Last BFD peer monitor status rcvd: Not Applicable
Last local AC circuit status rcvd: No fault
Last local AC circuit status sent: DOWN(pw-rx-fault)
Last local PW i/f circ status rcvd: No fault
Last local LDP TLV status sent: Not Applicable
Last remote LDP TLV status rcvd: Not Applicable
Last remote LDP ADJ status rcvd: Not Applicable
MPLS VC labels: local 27, remote 16
Group ID: local 0, remote 0
MTU: local 1500, remote 1500
Control Word: Off
Dataplane:
SSM segment/switch IDs: 0/10075 (used), PWID: 12
VC statistics:
transit packet totals: receive 0, send 0
transit byte totals: receive 0, send 0
transit packet drops: receive 0, seq error 0, send 0
SW1.THN-LON#show mpls for 46.226.0.10 detail
Local Outgoing Prefix Bytes Label Outgoing Next Hop
Label Label or Tunnel Id Switched interface
None 304720 46.226.0.10/32 0 Tu0 point2point
MAC/Encaps=14/18, MRU=9000, Label Stack{304720}, via Te0/2
A8D0E55DEB3D88F077938CDB8847 4A650000
Gli pseudo-cavi sono attivi ma il VC è ancora inattivo.
Quando si esegue il comando seguente, viene restituito il messaggio senza mappatura FEC.
SW1.THN-LON#ping mpls ipv4 46.226.0.10/32
Sending 5, 100-byte MPLS Echos to Target FEC Stack TLV descriptor,
timeout is 2 seconds, send interval is 0 msec:
Codes: '!' - success, 'Q' - request not sent, '.' - timeout,
'L' - labeled output interface, 'B' - unlabeled output interface,
'D' - DS Map mismatch, 'F' - no FEC mapping, 'f' - FEC mismatch,
'M' - malformed request, 'm' - unsupported tlvs, 'N' - no label entry,
'P' - no rx intf label prot, 'p' - premature termination of LSP,
'R' - transit router, 'I' - unknown upstream index,
'l' - Label switched with FEC change, 'd' - see DDMAP for return code,
'X' - unknown return code, 'x' - return code 0
Type escape sequence to abort.
FFFFF
Success rate is 0 percent (0/5)
Total Time Elapsed 48 ms
La configurazione per l'interruttore riguarda le parti rilevanti come segue: -
interface Tunnel0
description sw1.thn-lon-to-sw1.sco-edi
ip unnumbered Loopback0
tunnel mode mpls traffic-eng
tunnel destination 46.226.0.10
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng priority 1 1
tunnel mpls traffic-eng path-option 1 dynamic
mpls traffic-eng tunnels
l2vpn vfi context FLVPLS001
vpn id 501
autodiscovery bgp signaling bgp
ve id 1
rd 56595:501
route-target export 56595:501
route-target import 56595:501
bridge-domain 501
member GigabitEthernet0/1 service-instance 2
interface GigabitEthernet0/1
description customer xxx
switchport trunk allowed vlan none
switchport mode trunk
mtu 1600
speed 100
duplex full
service instance 1 ethernet
description Cust: xxx
encapsulation dot1q 400
rewrite ingress tag pop 1 symmetric
!
service instance 2 ethernet
description Oil and Gas VPLS
encapsulation dot1q 501
rewrite ingress tag pop 1 symmetric
interface Vlan501
no ip address
member vfi FLVPLS001
Qualsiasi aiuto / comando ecc. È molto apprezzato
router bgp 56595
bgp log-neighbor-changes
bgp graceful-restart restart-time 120
bgp graceful-restart stalepath-time 360
bgp graceful-restart
neighbor 46.226.0.10 remote-as 56595
neighbor 46.226.0.10 update-source Loopback0
!
address-family l2vpn vpls
neighbor 46.226.0.10 activate
neighbor 46.226.0.10 send-community extended
neighbor 46.226.0.10 suppress-signaling-protocol ldp
exit-address-family
Ho aggiunto la configurazione ospf per completezza.
router ospf 1
redistribute connected subnets
redistribute static subnets
network 46.226.6.80 0.0.0.3 area 0.0.0.0
mpls traffic-eng router-id Loopback0
mpls traffic-eng area 0.0.0.0
alcuni eventi da eventi atom di debug
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: Evt dataplane reactivateS, in activating
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: . Activate dataplane
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: . Need to setup the dataplane
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: . Setup dataplane, PWID 21
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: .. Provision SSM with PWID 21, VC ID 501, Block ID 3
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: .. Set imp flags: ra
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: .. : nsf
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: .. No signal context found, defaulting to single segment PW
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: .. Provision SSM with 7540/20332 (sw/seg)
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: Receive SSM dataplane unavailable notification
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: Evt dataplane downS, in activating
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: . Dataplane unavailable
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: . Set last error: MPLS dataplane reported a fault to the nexthop
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: . Notify dataplane down
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: Deactivating data plane
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: Notify dataplane down
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: Unprovision and deallocate SSM segment
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: Added vc to 60 sec retry queue
*Jun 8 05:31:57.748: AToM[46.226.0.12, 501]: Event provision retry already in retry queue
Uscita di bgp
SW1.THN-LON#show bgp l2vpn vpls all
BGP table version is 17, local router ID is 46.226.0.12
Status codes: s suppressed, d damped, h history, * valid, > best, i - internal,
r RIB-failure, S Stale, m multipath, b backup-path, f RT-Filter,
x best-external, a additional-path, c RIB-compressed,
Origin codes: i - IGP, e - EGP, ? - incomplete
RPKI validation codes: V valid, I invalid, N Not found
Network Next Hop Metric LocPrf Weight Path
Route Distinguisher: 56595:501
*> 56595:501:VEID-1:Blk-1/136
0.0.0.0 32768 ?
*>i 56595:501:VEID-2:Blk-1/136
46.226.0.10 0 100 0 ?
dopo un po 'di aiuto da parte di @ytti, l'abbiamo ridotto a un bug all'interno del me3600 per quanto riguarda la segnalazione BGP.
Abbiamo cambiato la segnalazione in LDP e ha funzionato bene. Pubblicherà un aggiornamento una volta risolto con Cisco.
nvm, ho perso il fatto che gli LSP sono
spiacente. non sono sicuro di come ordinare la formattazione
—
NetDonkey
bgp config ora aggiunto a OP
—
NetDonkey il
stackexchange non sembra perfetto per questo tipo di problema. Ma sembra che ME3600 pensi che ci siano problemi nell'etichetta IGP (ovvero tunnel RSVP). Forse 'sh ip cef 46.226.0.10 detail' sarebbe di aiuto (seguire l'etichetta hop-by-hop e post output per entrambe le direzioni). Magari prova anche a ridurre il dominio problematico, provando prima le etichette IGP su "LDP" (mantieni VPLS in BGP). Un'altra cosa che potresti provare è configurare L3 MPLS VPN su loopback di ME3600, per vedere se c'è anche un problema. Mi piacerebbe anche guardare il NLRI BGP, anche se probabilmente stanno bene dato che hai le etichette VPN.
—
ytti,
Ciao Ytti. Ci sono 2 MX80 intermedi. Daremo un'occhiata anche a quelli.
—
NetDonkey,