cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
940
Views
3
Helpful
14
Replies

MPLS TE tunnel doesnt show the traffic or rate on the tunnel

Amirmahdi.M
Level 1
Level 1

Hi everybody

I ecnountered a strange problem while testing mpls te.

Looks like the interface tunnel doesnt show the traffic going though it.

I know theres about 4gbps traffic on the tunnel but the output byte and rate is 0.

How can i solve this problem?

Example Configuration:

CSR6#show run int Tu10
Building configuration...

Current configuration : 190 bytes
!
interface Tunnel10
description TE-BALANCE
ip unnumbered Loopback0
tunnel mode mpls traffic-eng
tunnel destination 1.1.1.1
tunnel mpls traffic-eng path-option 1 explicit name ONE
end

CSR6#show run int Tu30
Building configuration...

Current configuration : 216 bytes
!
interface Tunnel30
description TE-BALANCE
ip unnumbered Loopback0
mpls traffic-eng tunnels
tunnel mode mpls traffic-eng
tunnel destination 1.1.1.1
tunnel mpls traffic-eng path-option 1 explicit name TWO
end

CSR6#show int Tu10
Tunnel10 is up, line protocol is down
Hardware is Tunnel
Description: TE-BALANCE
Interface is unnumbered. Using address of Loopback0 (6.6.6.6)
MTU 9996 bytes, BW 100 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel linestate evaluation down - transport reg down
Tunnel source 6.6.6.6, destination 1.1.1.1
Tunnel protocol/transport Label Switching
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input never, output 00:00:03, output hang never
Last clearing of "show interface" counters 00:09:13
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 40
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
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
0 packets output, 0 bytes, 0 underruns
Output 0 broadcasts (0 IP multicasts)
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
CSR6#show int Tu30
Tunnel30 is up, line protocol is up
Hardware is Tunnel
Description: TE-BALANCE
Interface is unnumbered. Using address of Loopback0 (6.6.6.6)
MTU 9996 bytes, BW 100 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel linestate evaluation up
Tunnel source 6.6.6.6, destination 1.1.1.1
Tunnel protocol/transport Label Switching
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input never, output 00:00:02, output hang never
Last clearing of "show interface" counters 00:09:14
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 16
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
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
105 packets output, 8640 bytes, 0 underruns
Output 0 broadcasts (0 IP multicasts)
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out
CSR6#

Thanks

Amir

14 Replies 14

show interface tunnel 1 accounting

Checking this command

MHM

Hi mhm
this is the output:
No traffic sent or received on this interface.

There is no output for both tunnels?

show interface tunnel-te × accounting

This correct command share output of it.

MHM

Harold Ritter
Level 12
Level 12

Hi @Amirmahdi.M ,

There's a couple of things here.

1. As per the provided output, Tu10 is down.

"Tunnel10 is up, line protocol is down"

2. No traffic is sent to the tunnel interface by default. You need to either configure "tunnel mpls traffic-eng autoroute announce" under the tunnel interface or configure a static route using the tunnel as the next hop.

Regards, 

Harold Ritter
Sr Technical Leader
CCIE 4168 (R&S, SP)
harold@cisco.com
México móvil: +52 1 55 8312 4915
Cisco México
Paseo de la Reforma 222
Piso 19
Cuauhtémoc, Juárez
Ciudad de México, 06600
México

Hi @Harold Ritter 

I have other tunnels with autoroute announce but there's still no rate on the tunnel.

There are lots of users going through this link.

 

Here is the Output:

PE2#show mpls l2 vc 739 deta
Local interface: Te0/0/6 up, line protocol up, Eth VLAN 739 up
Interworking type is Ethernet
Destination address: 10.18.106.80, VC ID: 739, VC status: up
Output interface: Tu180, imposed label stack {993 187}
Preferred path: not configured
Default path: active
Next hop: point2point
Create time: 2y17w, last status change time: 1w6d
Last label FSM state change time: 1w6d
Signaling protocol: LDP, peer 10.18.106.80:0 up
Targeted Hello: 10.18.106.110(LDP Id) -> 10.18.106.80, LDP is UP
Graceful restart: configured and not enabled
Non stop routing: configured and enabled
Status TLV support (local/remote) : enabled/supported
LDP route watch : enabled
Label/status state machine : established, LruRru
Last local dataplane status rcvd: No fault
Last BFD dataplane status rcvd: Not sent
Last BFD peer monitor status rcvd: No fault
Last local AC circuit status rcvd: No fault
Last local AC circuit status sent: No fault
Last local PW i/f circ status rcvd: No fault
Last local LDP TLV status sent: No fault
Last remote LDP TLV status rcvd: No fault
Last remote LDP ADJ status rcvd: No fault
MPLS VC labels: local 8870, remote 187
Group ID: local 12, remote 36
MTU: local 9216, remote 9216
Remote interface description: USER-A
Sequencing: receive disabled, send disabled
Control Word: On (configured: autosense)
SSO Descriptor: 10.18.106.80/739, local label: 8870
Dataplane:
SSM segment/switch IDs: 9940742/1431157 (used), PWID: 552
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


PE2#show run int Tu180
Building configuration...

Current configuration : 256 bytes
!
interface Tunnel180
description PE1.FIBER
ip unnumbered Loopback0
tunnel mode mpls traffic-eng
tunnel destination 10.18.106.80
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng path-option 1 explicit name PE1.FIBER
end

PE2#show int Tunnel180
Tunnel180 is up, line protocol is up
Hardware is Tunnel
Description: PE1.FIBER
Interface is unnumbered. Using address of Loopback0 (10.18.106.110)
MTU 17936 bytes, BW 100 Kbit/sec, DLY 50000 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation TUNNEL, loopback not set
Keepalive not set
Tunnel linestate evaluation up
Tunnel source 10.18.106.110, destination 10.18.106.80
Tunnel protocol/transport Label Switching
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input never, output 00:00:05, output hang never
Last clearing of "show interface" counters 15w4d
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
0 packets input, 0 bytes, 0 no buffer
Received 0 broadcasts (0 IP multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored, 0 abort
1437860 packets output, 84620249 bytes, 0 underruns
0 output errors, 0 collisions, 0 interface resets
0 unknown protocol drops
0 output buffer failures, 0 output buffers swapped out

 

 

By the way the output bytes real counter is definitely not 84MB.

Thanks

Amir

 

Amirmahdi.M
Level 1
Level 1

 

Also im using ASR-903 (RSP3_400) with below image:

asr900rsp3-universalk9.03.18.03.SP.156-2.SP3-ext.bin

 

I Also Checked an SR1006 (RP2) with below image and it shows the Interface Tunnel rate correctly:

asr1000rp2-adventerprisek9.03.13.06a.S.154-3.S6a-ext

 

 

Friend mpls te is unidirectional i.e. it only forward traffic 

I see output count some number that ok.

You need to add  tunnel in other end for retrun back traffic.

MHM

Hi @MHM Cisco World 

I know it uni directional but my problem is with the output rate:

5 minute output rate 0 bits/sec, 0 packets/sec

i know theres about 4gbps traffic on the tunnel but it only shows the total output bytes which i dont need.

the other end has a tunnel for return traffic but theres still no output rate.

Thanks

Amir

 

Show mpls traffic engineer tunnels

Share this please 

MHM

CSR6#Show mpls traffic-eng tunnels

P2P TUNNELS/LSPs:

Name: TE-BALANCE (Tunnel10) Destination: 1.1.1.1
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit ONE (Basis for Setup, path weight 30)

Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
Path-selection Tiebreaker:
Global: not set Tunnel Specific: not set Effective: min-fill (default)
Hop Limit: disabled [ignore: Explicit Path Option with all Strict Hops]
Cost Limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear
AutoRoute: disabled LockDown: disabled Loadshare: 0 [0] bw-based
auto-bw: disabled
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
Node Hop Count: 3

InLabel : -
OutLabel : GigabitEthernet1, 16
Next Hop : 172.16.46.4
RSVP Signalling Info:
Src 6.6.6.6, Dst 1.1.1.1, Tun_Id 10, Tun_Instance 25
RSVP Path Info:
My Address: 172.16.46.6
Explicit Route: 172.16.46.4 172.16.24.4 172.16.24.2 172.16.12.2
172.16.12.1 1.1.1.1
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

History:
Tunnel:
Time since created: 21 minutes, 57 seconds
Time since path change: 18 minutes, 6 seconds
Number of LSP IDs (Tun_Instances) used: 25
Current LSP: [ID: 25]
Uptime: 18 minutes, 6 seconds

Name: TE-BALANCE (Tunnel20) Destination: 1.1.1.1
Status:
Admin: admin-down Oper: down Path: not valid Signalling: Down
path option 1, type explicit TWO

Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
Path-selection Tiebreaker:
Global: not set Tunnel Specific: not set Effective: min-fill (default)
Hop Limit: disabled
Cost Limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear
AutoRoute: disabled LockDown: disabled Loadshare: 0 [0] bw-based
AutoRoute destination: enabled
auto-bw: disabled
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Reason for the tunnel being down: Tunnel interface is shutdown

History:
Tunnel:
Time since created: 21 minutes, 56 seconds
Number of LSP IDs (Tun_Instances) used: 0

Name: TE-BALANCE (Tunnel30) Destination: 1.1.1.1
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit TWO (Basis for Setup, path weight 30)

Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: TE (default)
Path-selection Tiebreaker:
Global: not set Tunnel Specific: not set Effective: min-fill (default)
Hop Limit: disabled [ignore: Explicit Path Option with all Strict Hops]
Cost Limit: disabled
Path-invalidation timeout: 10000 msec (default), Action: Tear
AutoRoute: disabled LockDown: disabled Loadshare: 0 [0] bw-based
auto-bw: disabled
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
Node Hop Count: 3

InLabel : -
OutLabel : GigabitEthernet2, 28
Next Hop : 172.16.56.5
RSVP Signalling Info:
Src 6.6.6.6, Dst 1.1.1.1, Tun_Id 30, Tun_Instance 20
RSVP Path Info:
My Address: 172.16.56.6
Explicit Route: 172.16.56.5 172.16.35.5 172.16.35.3 172.16.13.3
172.16.13.1 1.1.1.1
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

History:
Tunnel:
Time since created: 21 minutes, 56 seconds
Time since path change: 18 minutes, 11 seconds
Number of LSP IDs (Tun_Instances) used: 20
Current LSP: [ID: 20]
Uptime: 18 minutes, 11 seconds

LSP Tunnel TE-BALANCE is signalled, connection is up
InLabel : GigabitEthernet2, implicit-null
Prev Hop : 172.16.56.5
OutLabel : -
RSVP Signalling Info:
Src 1.1.1.1, Dst 6.6.6.6, Tun_Id 10, Tun_Instance 11
RSVP Path Info:
My Address: 6.6.6.6
Explicit Route: NONE
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

LSP Tunnel TE-BALANCE is signalled, connection is up
InLabel : GigabitEthernet1, implicit-null
Prev Hop : 172.16.46.4
OutLabel : -
RSVP Signalling Info:
Src 1.1.1.1, Dst 6.6.6.6, Tun_Id 30, Tun_Instance 16
RSVP Path Info:
My Address: 6.6.6.6
Explicit Route: NONE
Record Route: NONE
Tspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits
RSVP Resv Info:
Record Route: NONE
Fspec: ave rate=0 kbits, burst=1000 bytes, peak rate=0 kbits

P2MP TUNNELS:

P2MP SUB-LSPS:
CSR6#

Dead tunnel' 

Can you share show ip route'

Do you see 1.1.1.1 as C or L in rib ?

You use autoroute announce only?

The interface Tunnel 20 is admin down because i didnt want to use it.

in some cases i did use autoroute announce (in asr903-csr1000v ios15) but it still didnt show the output rate.

To summerize the info, the problem seems to be gone on csr1000v(ios17) and asr1006(03.13.06a.S.154-3.S6a)

but on csr1000v(ios15.4) and asr903(3.18.03.SP.156-2.SP3) it doesnt show the rate.

 

The tunnel is UP

You need to push traffic via tunnel 

Here if you use announce only traffic to 1.1.1.1 will pass through tunnel 

You need static route for any prefix in tail end of tunnel 

Or use forward adjunacy (it hard to config).

MHM

I have pushed traffic via tunnel.

i static routed one of tail end's loopback addresses to Tu10 and Tu30 and configured interface pseduwire to go through the tunnels.

there is traffic on the tunnel but the interface tunnel doesnt show the rate.