No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade
Knowledge Base

MPLS LSP is down between JXX and NE05

Publication Date:  2019-07-11  |   Views:  1021  |   Downloads:  0  |   Author:  c84079748  |   Document ID:  EKB1001826567

Contents

Issue Description

Topology:




Configuration NE05:

 

#

ip vpn-instance Test1

 description xxxx

 ipv4-family

  route-distinguisher 100:20

  vpn-target 100:20 export-extcommunity

  vpn-target 100:20 import-extcommunity

#

ip vpn-instance Test2

 description xxxx

 ipv4-family

  route-distinguisher 100:10

  vpn-target 100:10 export-extcommunity

  vpn-target 100:10 import-extcommunity

#

mpls lsr-id 172.27.0.62

mpls

 mpls te

 mpls rsvp-te

 mpls te cspf

 mpls te cspf preferred-igp ospf 1 area 0.0.0.0

#

mpls ldp

#

#

acl number 2001

 rule 5 permit source 192.168.0.0 0.0.0.255

 rule 6 permit source 10.0.0.0 0.0.0.255

 rule 7 permit source 172.0.0.0 0.0.0.255

#

#

interface GigabitEthernet0/2/10

 description xxxx

 undo shutdown

 mtu 1548

 ip address 172.27.7.130 255.255.255.252

 ospf cost 100

 ospf network-type p2p

 ospf enable 1 area 0.0.0.0

 mpls

 mpls te

 mpls te bandwidth max-reservable-bandwidth 1000000

 mpls te bandwidth bc0 1000000

 mpls rsvp-te

 mpls ldp

 undo dcn

#

interface NULL0

#

interface LoopBack0

 ip address 172.27.0.62 255.255.255.255

 ospf enable 1 area 0.0.0.0

#

interface Tunnel0/2/10

 description xxxx

 ip address unnumbered interface LoopBack0

 tunnel-protocol mpls te

 destination 172.27.0.26

 mpls te tunnel-id 1

 mpls te resv-style ff

 mpls te igp shortcut ospf

 mpls te commit

 mpls

 mpls mtu 1548

#

 

 ipv4-family unicast

  undo synchronization

  peer xxx enable

  peer 172.27.0.26 enable

  peer 172.27.0.26 group xxx

 #

 ipv4-family vpnv4

  undo policy vpn-target

  peer xxx enable

  peer xxx reflect-client

  peer 172.27.0.26 enable

  peer 172.27.0.26 group xxx

 #

 ipv4-family vpn-instance Test1

  compare-different-as-med

  import-route direct

 #

 ipv4-family vpn-instance Test2

  compare-different-as-med

  import-route direct

 #

ospf 1 router-id 172.27.0.62

 opaque-capability enable

 enable traffic-adjustment

 advertise mpls-lsr-id

 area 0.0.0.0

  authentication-mode md5 1 cipher XXXXXX

  network 0.0.0.0 255.255.255.255

  mpls-te enable

#


Alarm Information


[HUAWEI]display interface brief

PHY: Physical

*down: administratively down

(l): loopback

(s): spoofing

(b): BFD down

(B): Bit-error-detection down

(e): ETHOAM down

(d): Dampening Suppressed

InUti/OutUti: input utility/output utility

Interface                   PHY   Protocol  InUti OutUti   inErrors  outErrors

Ethernet0/0/0               down  down         0%     0%          0          0

GigabitEthernet0/2/10       up    up           0%     0%          0          0

GigabitEthernet0/2/11       up    up        0.01%     0%          0          0

LoopBack0                   up    up(s)        0%     0%          0          0

NULL0                       up    up(s)        0%     0%          0          0

Tunnel0/2/10                up    down         0%     0%          0          0

Tunnel0/2/11                *down down         0%     0%          0          0



Handling Process


Checked configuration and all looks good on both sides; Took a packet and noticed that, since the DD packet in OSPF is more than 1500, the peer device cannot handle it.



Root Cause


Jxxx cannot handle the ospf dd packet which is over 1500.



Solution


Changed the MTU to 1500 on tunnel interface and physical so that OSPF relation can go to full.