Comware Based
cancel
Showing results for 
Search instead for 
Did you mean: 

Playing with VPLS - only tracert gives "Request time out"

MichaelM55
Trusted Contributor

Playing with VPLS - only tracert gives "Request time out"

I started a small VPLS lab: 4 switches so far, LDP with dynamic LSPs and OSPF

 

routing works:

 

display ospf routing

         OSPF Process 1 with Router ID10.0.1.3
                  Routing Tables

 Routing for Network
 Destination        Cost     Type    NextHop         AdvRouter       Area
10.0.1.1/32    2        Stub   10.0.1.105 10.0.1.1    0.0.0.0
10.0.1.2/32    1        Stub   10.0.1.105 10.0.1.2    0.0.0.0
10.0.1.3/32    0        Stub   10.0.1.3   10.0.1.3    0.0.0.0
10.0.1.4/32    1        Stub   10.0.1.110 10.0.1.4    0.0.0.0
10.0.1.100/30  2        Transit10.0.1.105 10.0.1.2    0.0.0.0
10.0.1.104/30  1        Transit10.0.1.106 10.0.1.2    0.0.0.0
10.0.1.108/30  1        Transit10.0.1.109 10.0.1.3    0.0.0.0
10.0.1.112/30  2        Stub   10.0.1.110 10.0.1.4    0.0.0.0

 Total Nets: 8
 Intra Area: 8  Inter Area: 0  ASE: 0  NSSA: 0

 

ping works:

 

ping lsp ipv410.0.1.1 32
 LSP Ping FEC: IPV4 PREFIX10.0.1.1/32 : 100  data bytes, press CTRL_C to break
 Reply from10.0.1.101: bytes=100 Sequence=1 time = 3 ms
 Reply from10.0.1.101: bytes=100 Sequence=2 time = 3 ms
 Reply from10.0.1.101: bytes=100 Sequence=3 time = 8 ms
 Reply from10.0.1.101: bytes=100 Sequence=4 time = 3 ms
 Reply from10.0.1.101: bytes=100 Sequence=5 time = 3 ms

 But with tracert I´m getting "Request time out"

 

tracert lsp ipv410.0.1.1 32
 LSP Trace Route FEC: IPV4 PREFIX10.0.1.1/32 , press CTRL_C to break
  TTL   Replier            Time    Type      Downstream
  0                                Ingress  10.0.1.109/[1025]
  1    10.0.1.109     3 ms    Transit  10.0.1.105/[1025]
  2    10.0.1.105     2 ms    Transit  10.0.1.101/[3]
  3 Request time out
  4    10.0.1.101     4 ms    Egress

 

The question is why?