cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
754
Views
0
Helpful
1
Replies

MPLS traffic engineering loadshare problem

a.samuelsson
Level 1
Level 1

I have traffic engineering between 2 routers. There are 3 direct links and I need to offload some traffic over a different path due to that the traffic volume is exceeding 30G at some time of the day.

I have allocated 9,9G to each of the direct paths and 1G to each of the 8 indirect paths.

According to cef it should "serve" tunnel1013-1015 8 times more often than tunnel1027-1034

I expect to have 78% over the direct path and 22% over the indirect path but  when monitoring the tunnels I see that 60% goes over direct path and 40% over indirect path.

Can anyone see a reason for this?

sh rsvp res dest 1.1.1.1     
Tue May  3 15:11:52.708 CET
Destination Add DPort      Source Add SPort Pro   Input IF Sty Serv   Rate Burst
--------------- ----- --------------- ----- --- ---------- --- ---- ------ -----
  1.1.1.1  1013   2.2.2.2   31   0  Te0/1/0/6  SE LOAD  9900M    1K
  1.1.1.1  1014   2.2.2.2   37   0  Te0/1/0/7  SE LOAD  9900M    1K
  1.1.1.1  1015   2.2.2.2   45   0 Te0/0/0/30  SE LOAD  9900M    1K
  1.1.1.1  1027   2.2.2.2 1626   0 Te0/0/0/35  SE LOAD  1000M    1K
  1.1.1.1  1028   2.2.2.2 2662   0 Te0/0/0/35  SE LOAD  1000M    1K
  1.1.1.1  1029   2.2.2.2 2312   0 Te0/0/0/35  SE LOAD  1000M    1K
  1.1.1.1  1030   2.2.2.2  889   0 Te0/0/0/35  SE LOAD  1000M    1K
  1.1.1.1  1031   2.2.2.2   31   0      BE309  SE LOAD  1000M    1K
  1.1.1.1  1032   2.2.2.2   28   0      BE313  SE LOAD  1000M    1K
  1.1.1.1  1033   2.2.2.2   25   0      BE311  SE LOAD  1000M    1K
  1.1.1.1  1034   2.2.2.2   44   0      BE310  SE LOAD  1000M    1K


interface tunnel-te1013
 description stockholm_to_gothenburg_01
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_01
 signalled-bandwidth 9900000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name direct_gothenburg_01
 logging events link-status
!
interface tunnel-te1014
 description stockholm_to_gothenburg_02
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_02
 signalled-bandwidth 9900000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name direct_gothenburg_01
 logging events link-status
!
interface tunnel-te1015
 description stockholm_to_gothenburg_03
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_03
 signalled-bandwidth 9900000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name direct_gothenburg_01
 logging events link-status
!

!
interface tunnel-te1027
 description stockholm_to_gothenburg_07
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_07
 signalled-bandwidth 1000000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name via_malmo
 logging events link-status
!
interface tunnel-te1028
 description stockholm_to_gothenburg_28
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_28
 signalled-bandwidth 1000000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name via_malmo
 logging events link-status
!
interface tunnel-te1029
 description stockholm_to_gothenburg_08
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_08
 signalled-bandwidth 1000000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name via_malmo
 logging events link-status
!
interface tunnel-te1030
 description stockholm_to_gothenburg_09
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_09
 signalled-bandwidth 1000000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name via_malmo
 logging events link-status
!
interface tunnel-te1031
 description stockholm_to_gothenburg_09
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_09
 signalled-bandwidth 1000000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name via_karlstad
 logging events link-status
!
interface tunnel-te1032
 description stockholm_to_gothenburg_10
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_10
 signalled-bandwidth 1000000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name via_karlstad
 logging events link-status
!
interface tunnel-te1033
 description stockholm_to_gothenburg_11
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_11
 signalled-bandwidth 1000000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name via_karlstad
 logging events link-status
!
interface tunnel-te1034
 description stockholm_to_gothenburg_12
 ipv4 unnumbered Loopback0
 load-interval 30
 signalled-name stockholm_to_gothenburg_12
 signalled-bandwidth 1000000
 autoroute announce
 !
 destination 1.1.1.1
 record-route
 path-option 10 explicit name via_karlstad
 logging events link-status



sh cef 1.1.1.1 det        
Tue May  3 15:13:31.079 CET
1.1.1.1/32, version 1758697, internal 0x1000001 0x0 (ptr 0x736b2c74) [1], 0x0 (0x73673330), 0xa20 (0x7b9ec6f0)
 Updated May  3 13:41:49.350
 Prefix Len 32, traffic index 0, precedence n/a, priority 3
  gateway array (0x71f182b8) reference count 3, flags 0x68, source lsd (5), 1 backups
                [3 type 4 flags 0x401 (0x7271a390) ext 0x0 (0x0)]
  LW-LDI[type=1, refc=1, ptr=0x73673330, sh-ldi=0x7271a390]
  gateway array update type-time 4 May  3 15:11:17.840
 LDI Update time May  3 15:11:17.840
 LW-LDI-TS May  3 15:11:17.840
   via 1.1.1.1/32, tunnel-te1013, 9 dependencies, weight 9900000, class 0 [flags 0x0]
    path-idx 0 NHID 0x0 [0x71adbad0 0x71ad9760]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1014, 9 dependencies, weight 9900000, class 0 [flags 0x0]
    path-idx 1 NHID 0x0 [0x71ad8ae8 0x71ad8a40]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1015, 9 dependencies, weight 9900000, class 0 [flags 0x0]
    path-idx 2 NHID 0x0 [0x71ad89ec 0x71ada5d0]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1027, 9 dependencies, weight 1000000, class 0 [flags 0x0]
    path-idx 3 NHID 0x0 [0x71adbcc8 0x71adb68c]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1028, 9 dependencies, weight 1000000, class 0 [flags 0x0]
    path-idx 4 NHID 0x0 [0x71adb9d4 0x71ada4d4]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1029, 9 dependencies, weight 1000000, class 0 [flags 0x0]
    path-idx 5 NHID 0x0 [0x71ada8c4 0x71ad9e44]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1030, 9 dependencies, weight 1000000, class 0 [flags 0x0]
    path-idx 6 NHID 0x0 [0x71ad4de0 0x71ad9df0]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1031, 9 dependencies, weight 1000000, class 0 [flags 0x0]
    path-idx 7 NHID 0x0 [0x71ad691c 0x71adb29c]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1032, 9 dependencies, weight 1000000, class 0 [flags 0x0]
    path-idx 8 NHID 0x0 [0x71adae04 0x71adb3ec]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1033, 9 dependencies, weight 1000000, class 0 [flags 0x0]
    path-idx 9 NHID 0x0 [0x71adb788 0x71ad8458]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}
   via 1.1.1.1/32, tunnel-te1034, 9 dependencies, weight 1000000, class 0 [flags 0x0]
    path-idx 10 NHID 0x0 [0x71adbd1c 0x71adbb24]
    next hop 1.1.1.1/32
    local adjacency
     local label 27050      labels imposed {ImplNull}

    Weight distribution:
    slot 0, weight 9900000, normalized_weight 9, class 0
    slot 1, weight 9900000, normalized_weight 9, class 0
    slot 2, weight 9900000, normalized_weight 9, class 0
    slot 3, weight 1000000, normalized_weight 1, class 0
    slot 4, weight 1000000, normalized_weight 1, class 0
    slot 5, weight 1000000, normalized_weight 1, class 0
    slot 6, weight 1000000, normalized_weight 1, class 0
    slot 7, weight 1000000, normalized_weight 1, class 0
    slot 8, weight 1000000, normalized_weight 1, class 0
    slot 9, weight 1000000, normalized_weight 1, class 0
    slot 10, weight 1000000, normalized_weight 1, class 0

    Load distribution: 0 1 2 3 4 5 6 7 8 9 10 0 1 2 0 1 2 0 1 2 0 1 2 0 1 2 0 1 2 0 1 2 0 1 2 (refcount 3)

    Hash  OK  Interface                 Address
    0     Y   tunnel-te1013             point2point    
    1     Y   tunnel-te1014             point2point    
    2     Y   tunnel-te1015             point2point    
    3     Y   tunnel-te1027             point2point    
    4     Y   tunnel-te1028             point2point    
    5     Y   tunnel-te1029             point2point    
    6     Y   tunnel-te1030             point2point    
    7     Y   tunnel-te1031             point2point    
    8     Y   tunnel-te1032             point2point    
    9     Y   tunnel-te1033             point2point    
    10    Y   tunnel-te1034             point2point    
    11    Y   tunnel-te1013             point2point    
    12    Y   tunnel-te1014             point2point    
    13    Y   tunnel-te1015             point2point    
    14    Y   tunnel-te1013             point2point    
    15    Y   tunnel-te1014             point2point    
    16    Y   tunnel-te1015             point2point    
    17    Y   tunnel-te1013             point2point    
    18    Y   tunnel-te1014             point2point    
    19    Y   tunnel-te1015             point2point    
    20    Y   tunnel-te1013             point2point    
    21    Y   tunnel-te1014             point2point    
    22    Y   tunnel-te1015             point2point    
    23    Y   tunnel-te1013             point2point    
    24    Y   tunnel-te1014             point2point    
    25    Y   tunnel-te1015             point2point    
    26    Y   tunnel-te1013             point2point    
    27    Y   tunnel-te1014             point2point    
    28    Y   tunnel-te1015             point2point    
    29    Y   tunnel-te1013             point2point    
    30    Y   tunnel-te1014             point2point    
    31    Y   tunnel-te1015             point2point    
    32    Y   tunnel-te1013             point2point    
    33    Y   tunnel-te1014             point2point    
    34    Y   tunnel-te1015             point2point


                    Monitor Time: 00:38:46          SysUptime: 1809:41:51

Protocol:General
Interface             In(bps)      Out(bps)     InBytes/Delta  OutBytes/Delta
tt1013                    0/ --%     7.9G/ --%        0/0        891.8T/0     
tt1030                    0/ --%     2.0G/ --%        0/0         15.1T/0     
tt1034                    0/ --%     2.3G/ --%        0/0        150.5T/0     

Quit='q',     Clear='c',    Freeze='f', Thaw='t',
Next set='n', Prev set='p', Bytes='y',  Packets='k'
(General='g', IPv4 Uni='4u', IPv4 Multi='4m', IPv6 Uni='6u', IPv6 Multi='6m')

1 Accepted Solution

Accepted Solutions

Vinit Jain
Cisco Employee
Cisco Employee

Hello,

Could you please share the topology of the network and the below outputs:

- show version (output from both the routers)

one thing i would like to point out is, the traffic on the tunnels will be load-balanced based on the flows. so it may be possible that a higher load traffic flow might have taken the path of the low bandwidth tunnel (based on teh CEF) and thus, you might see more traffic on the low bandwidth link.

i think the best way would be to check few of the flows using the below command:

- show ip cef exact-route <source> <dest>

This command will help understand which exact tunnel interface a particular traffic flow is taking.

Hope this helps.

Regards

Vinit

Thanks
--Vinit

View solution in original post

1 Reply 1

Vinit Jain
Cisco Employee
Cisco Employee

Hello,

Could you please share the topology of the network and the below outputs:

- show version (output from both the routers)

one thing i would like to point out is, the traffic on the tunnels will be load-balanced based on the flows. so it may be possible that a higher load traffic flow might have taken the path of the low bandwidth tunnel (based on teh CEF) and thus, you might see more traffic on the low bandwidth link.

i think the best way would be to check few of the flows using the below command:

- show ip cef exact-route <source> <dest>

This command will help understand which exact tunnel interface a particular traffic flow is taking.

Hope this helps.

Regards

Vinit

Thanks
--Vinit