MPLS Traffic Engineering Tunnels: No Traffic Flow Through the Tunnel

sajjadalamery · ‎11-11-2023

Hello,

we have issue in tunnel TE, we have config the auto-bw in MPLS traffic engineer in our network and config the tunnel TE and we have issued the tunnel TE does not calculate the traffic through it and not registered because no traffic passed with Tunnel TE it when we applied the command " show interface Tunnel 130, kindly your support to solve this issue.

note the Traffic its Through the Tunnel when we applied the command "show ip route 10.239.130.1 "

output of command "show ip route 10.239.130.1 "

DMUSEMA5-NtCor01#show ip route 10.239.130.1
Routing entry for 10.239.130.0/24
Known via "ospf 239", distance 110, metric 42, type intra area
Last update from 10.239.248.193 on Tunnel130, 00:00:10 ago
Routing Descriptor Blocks:
* 10.239.248.193, from 10.239.248.193, 00:00:10 ago, via Tunnel130
Route metric is 42, traffic share count is 1

below the config of Tunnel TE in our device:

interface Tunnel130
description TE-RMUSEMA5-RpGwy01
ip unnumbered Loopback100
mpls ip
tunnel mode mpls traffic-eng
tunnel destination 10.239.248.193
tunnel mpls traffic-eng autoroute announce
tunnel mpls traffic-eng path-option 1 dynamic
tunnel mpls traffic-eng path-selection metric igp
tunnel mpls traffic-eng auto-bw frequency 300
end

,

=========================

state tunnel before calculating the BW.

DMUSEMA5-NtCor02#show mpls traffic-eng tunnels tunnel 130

Name: TE-RMUSEMA5-RpGwy01 (Tunnel130) Destination: 10.239.248.193
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type dynamic (Basis for Setup, path weight 40)

Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: IGP (interface)
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: enabled LockDown: disabled Loadshare: 0 [0] bw-based
auto-bw: (300/44) 0 Bandwidth Requested: 0
Minimum: 0, Maximum: 4294967295
Samples Missed 1: Samples Collected 25
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Active Path Option Parameters:
State: dynamic path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
Node Hop Count: 1

InLabel : -
OutLabel : Vlan105, implicit-null
Next Hop : 10.239.28.114
RSVP Signalling Info:
Src 10.239.248.2, Dst 10.239.248.193, Tun_Id 130, Tun_Instance 2282
RSVP Path Info:
My Address: 10.239.28.113
Explicit Route: 10.239.28.114 10.239.248.193
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
Shortest Unconstrained Path Info:
Path Weight: 40 (IGP)
Explicit Route: 10.239.28.114 10.239.248.193

History:
Tunnel:
Time since created: 6 days, 20 hours, 51 minutes
Time since path change: 1 minutes, 27 seconds
Number of LSP IDs (Tun_Instances) used: 2282
Current LSP: [ID: 2282]
Uptime: 1 minutes, 27 seconds
Prior LSP: [ID: 3]
ID: path option unknown
Removal Trigger: tunnel shutdown

==================================

state tunnel after calculating the BW.

DMUSEMA5-NtCor02#show mpls traffic-eng tunnels tunnel 130

Name: TE-RMUSEMA5-RpGwy01 (Tunnel130) Destination: 10.239.248.193
Status:
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type dynamic (Basis for Setup, path weight 40)

Config Parameters:
Bandwidth: 0 kbps (Global) Priority: 7 7 Affinity: 0x0/0xFFFF
Metric Type: IGP (interface)
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: enabled LockDown: disabled Loadshare: 0 [0] bw-based
auto-bw: (300/278) 0 Bandwidth Requested: 0
Minimum: 0, Maximum: 4294967295
Samples Missed 0: Samples Collected 2
Fault-OAM: disabled, Wrap-Protection: disabled, Wrap-Capable: No
Active Path Option Parameters:
State: dynamic path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
Node Hop Count: 1

InLabel : -
OutLabel : Vlan105, implicit-null
Next Hop : 10.239.28.114
RSVP Signalling Info:
Src 10.239.248.2, Dst 10.239.248.193, Tun_Id 130, Tun_Instance 2282
RSVP Path Info:
My Address: 10.239.28.113
Explicit Route: 10.239.28.114 10.239.248.193
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
Shortest Unconstrained Path Info:
Path Weight: 40 (IGP)
Explicit Route: 10.239.28.114 10.239.248.193

History:
Tunnel:
Time since created: 6 days, 20 hours, 52 minutes
Time since path change: 2 minutes, 32 seconds
Number of LSP IDs (Tun_Instances) used: 2282
Current LSP: [ID: 2282]
Uptime: 2 minutes, 32 seconds
Prior LSP: [ID: 3]
ID: path option unknown
Removal Trigger: tunnel shutdown
DMUSEMA5-NtCor02#

MHM Cisco World · ‎11-11-2023

....

Thanks A Lot
MHM

sajjadalamery · ‎11-11-2023

Thank you for your response. The problem is not about manually setting the bandwidth. We want to enable Auto-bw in the TE tunnel because we are unaware of the traffic size through the tunnel from the source. We need to automatically calculate the traffic through the tunnel to set the bandwidth

MHM Cisco World · ‎11-11-2023

let me check again.

Thanks A Lot
MHM

sajjadalamery · ‎11-11-2023

I think the issue about the auto-bw has not work because rate of the traffic has not through it in the tunnel According applied the command " show interface tunnel 130" i saw the "

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

"

this is the output of the command:

DMUSEMA5-NtCor01#show interfaces tunnel130
Tunnel130 is up, line protocol is up
Hardware is Tunnel
Description: TE-RMUSEMA5-RpGwy01
Interface is unnumbered. Using address of Loopback100 (10.239.248.1)
MTU 17888 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.239.248.1, destination 10.239.248.193
Tunnel protocol/transport Label Switching
Tunnel transmit bandwidth 8000 (kbps)
Tunnel receive bandwidth 8000 (kbps)
Last input never, output 00:00:00, output hang never
Last clearing of "show interface" counters 6d23h
Input queue: 0/75/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
2108 packets output, 124102 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

MHM Cisco World · ‎11-11-2023

0 packets input, 0 bytes, 0 no buffer

2108 packets output, 124102 bytes, 0 underruns
there is traffic count OUT from tunnel interface.
the MPLS TE is unidirectional so do you config tunnel in tail end of MPLS TE?

Thanks A Lot
MHM

sajjadalamery · ‎11-11-2023

No, we don't config tunnel in tail end. We want to manage the download traffic to destination only.

and about the "2108 packets output, 124102 bytes, 0 underruns" the tunnel tell me the packet has through it the tunnel and number of packets, but it does not calculate the size of packet or the traffic in the tunnel.

haydersinan · ‎11-11-2023

..