cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
710
Views
0
Helpful
2
Replies

XRV CBTS policy-class seems to be not working -- need help to understand the problem

samarjit dutta
Beginner
Beginner

topo.PNG

 

 

In the above LAB topology I have 3 MPLS RSVP TE between the PEs( 1.1.1.1 and 8.8.8.8). I like to achieve -- Te 101 is for EXP 5, TE 102 for EXP4 and TE103 is for rest. But all traffic is passing through TE103. Did not able understand the actual cause of the problem, so need help. Thanks for your comments in advance.

Lab test was performed on XRV

Cisco IOS XR Software, Version 6.0.1[Default]

cisco IOS XRv Series (Pentium Celeron Stepping 3) processor with 3145215K bytes

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

Trace result from CE1 when all TEs are up:

traceroute -- All tunnel up
CE-1#traceroute 200.0.1.1

Type escape sequence to abort.
Tracing the route to 200.0.1.1

  1 100.0.0.1 44 msec 4 msec 8 msec
  2 10.1.2.2 [MPLS: Labels 24019/24023 Exp 5] 80 msec 40 msec 44 msec
  3 10.2.5.5 [MPLS: Labels 24000/24023 Exp 5] 44 msec 60 msec 40 msec
  4 10.5.6.6 [MPLS: Labels 24001/24023 Exp 5] 48 msec 36 msec 36 msec
  5 10.6.8.8 [MPLS: Label 24023 Exp 5] 64 msec 52 msec 32 msec
  6 200.0.0.2 28 msec 40 msec *
CE-1#
CE-1#
CE-1#traceroute 200.0.2.1

Type escape sequence to abort.
Tracing the route to 200.0.2.1

  1 100.0.0.1 4 msec 4 msec 8 msec
  2 10.1.2.2 [MPLS: Labels 24019/24000 Exp 4] 36 msec 36 msec 32 msec
  3 10.2.5.5 [MPLS: Labels 24000/24000 Exp 4] 20 msec 40 msec 36 msec
  4 10.5.6.6 [MPLS: Labels 24001/24000 Exp 4] 40 msec 32 msec 32 msec
  5 10.6.8.8 [MPLS: Label 24000 Exp 4] 28 msec 24 msec 28 msec
  6 200.0.0.2 20 msec 36 msec *
CE-1#traceroute 200.0.3.1

Type escape sequence to abort.
Tracing the route to 200.0.3.1

  1 100.0.0.1 16 msec 8 msec 8 msec
  2 10.1.2.2 [MPLS: Labels 24019/24001 Exp 0] 196 msec 48 msec 44 msec
  3 10.2.5.5 [MPLS: Labels 24000/24001 Exp 0] 140 msec 32 msec 44 msec
  4 10.5.6.6 [MPLS: Labels 24001/24001 Exp 0] 76 msec 40 msec 48 msec
  5 10.6.8.8 [MPLS: Label 24001 Exp 0] 136 msec 40 msec 44 msec
  6 200.0.0.2 44 msec 36 msec *
CE-1#

==========

Trace result when TE101 is only up only tunnel 101 is up

CE-1#traceroute 200.0.1.1

Type escape sequence to abort.
Tracing the route to 200.0.1.1

  1 100.0.0.1 8 msec 8 msec 8 msec
  2 10.1.2.2 [MPLS: Labels 24018/24023 Exp 5] 48 msec 68 msec 48 msec
  3 10.2.4.4 [MPLS: Labels 24000/24023 Exp 5] 40 msec 32 msec 32 msec
  4 10.4.6.6 [MPLS: Labels 24020/24023 Exp 5] 28 msec 36 msec 32 msec
  5 10.6.8.8 [MPLS: Label 24023 Exp 5] 20 msec 36 msec 28 msec
  6 200.0.0.2 36 msec 28 msec *
CE-1#
===============================================

TE configurations:

==================================================================================
RP/0/0/CPU0:PE-1#show run interface | begin interface tunne

interface tunnel-te101
 ipv4 unnumbered Loopback0
 logging events lsp-status reoptimize
 logging events lsp-status state
 logging events lsp-status reroute
 logging events lsp-status switchover
 logging events pcalc-failure
 priority 1 1
 signalled-bandwidth 100
 autoroute metric 1
 autoroute announce
  metric 1
 !
 destination 8.8.8.8
 policy-class 5
 record-route
 path-selection
  metric te
 !
 path-option 2 explicit name PATH-1-EXP5
 path-option 3 dynamic
!
interface tunnel-te102
 ipv4 unnumbered Loopback0
 logging events lsp-status reoptimize
 logging events lsp-status state
 logging events lsp-status reroute
 logging events lsp-status switchover
 logging events pcalc-failure
 priority 1 1
 signalled-bandwidth 100
 autoroute metric 1
 autoroute announce
  metric 1
 !
 destination 8.8.8.8
 policy-class 4
 record-route
 path-selection
  metric te
 !
 path-option 2 explicit name PATH-2-EXP4
 path-option 3 dynamic
!
interface tunnel-te103
 ipv4 unnumbered Loopback0
 logging events lsp-status reoptimize
 logging events lsp-status state
 logging events lsp-status reroute
 logging events lsp-status switchover
 logging events pcalc-failure
 priority 1 1
 signalled-bandwidth 100
 autoroute metric 1
 autoroute announce
  metric 1
 !
 destination 8.8.8.8
 record-route
 path-selection
  metric te
 !
 path-option 2 explicit name PATH-3-Default
 path-option 3 dynamic
!
================================================

TE Status:

===============================================
RP/0/0/CPU0:PE-1#show mpls traffic-eng tunnels
Sun Jan 20 08:40:24.726 UTC


Name: tunnel-te101  Destination: 8.8.8.8  Ifhandle:0x780
  Signalled-Name: PE-1_t101
  Status:
    Admin:    up Oper:   up   Path:  valid   Signalling: connected

    path option 2,  type explicit PATH-1-EXP5 (Basis for Setup, path weight 40)
    path option 3,  type dynamic
    G-PID: 0x0800 (derived from egress interface properties)
    Bandwidth Requested: 100 kbps  CT0
    Creation Time: Sat Jan 19 10:41:59 2019 (21:58:25 ago)
  Config Parameters:
    Bandwidth:      100 kbps (CT0) Priority:  1  1 Affinity: 0x0/0xffff
    Metric Type: TE (interface)
    Path Selection:
      Tiebreaker: Min-fill (default)
    Hop-limit: disabled
    Cost-limit: disabled
    Path-invalidation timeout: 10000 msec (default), Action: Tear (default)
    AutoRoute:  enabled  LockDown: disabled   Policy class: 5
    Forward class: 0 (default)
    Forwarding-Adjacency: disabled
    Autoroute Destinations: 0
    Loadshare:          0 equal loadshares
    Auto-bw: disabled
    Fast Reroute: Disabled, Protection Desired: None
    Path Protection: Not Enabled
    BFD Fast Detection: Disabled
    Reoptimization after affinity failure: Enabled
    Soft Preemption: Disabled
  History:
    Tunnel has been up for: 05:39:37 (since Sun Jan 20 03:00:47 UTC 2019)
    Current LSP:
      Uptime: 05:38:15 (since Sun Jan 20 03:02:09 UTC 2019)
    Reopt. LSP:
      Last Failure:
        LSP not signalled, identical to the [CURRENT] LSP
        Date/Time: Sun Jan 20 08:28:17 UTC 2019 [00:12:07 ago]
    Prior LSP:
      ID: 16 Path Option: 3
      Removal Trigger: reoptimization completed

  Path info (OSPF 1 area 0):
  Node hop count: 4
  Hop0: 10.1.2.2
  Hop1: 10.2.4.2
  Hop2: 10.2.4.4
  Hop3: 10.4.6.4
  Hop4: 10.4.6.6
  Hop5: 10.6.8.6
  Hop6: 10.6.8.8
  Hop7: 8.8.8.8

Name: tunnel-te102  Destination: 8.8.8.8  Ifhandle:0x880
  Signalled-Name: PE-1_t102
  Status:
    Admin:    up Oper:   up   Path:  valid   Signalling: connected

    path option 2,  type explicit PATH-2-EXP4 (Basis for Setup, path weight 31)
    path option 3,  type dynamic
    G-PID: 0x0800 (derived from egress interface properties)
    Bandwidth Requested: 100 kbps  CT0
    Creation Time: Sat Jan 19 23:46:15 2019 (08:54:09 ago)
  Config Parameters:
    Bandwidth:      100 kbps (CT0) Priority:  1  1 Affinity: 0x0/0xffff
    Metric Type: TE (interface)
    Path Selection:
      Tiebreaker: Min-fill (default)
    Hop-limit: disabled
    Cost-limit: disabled
    Path-invalidation timeout: 10000 msec (default), Action: Tear (default)
    AutoRoute:  enabled  LockDown: disabled   Policy class: 4
    Forward class: 0 (default)
    Forwarding-Adjacency: disabled
    Autoroute Destinations: 0
    Loadshare:          0 equal loadshares
    Auto-bw: disabled
    Fast Reroute: Disabled, Protection Desired: None
    Path Protection: Not Enabled
    BFD Fast Detection: Disabled
    Reoptimization after affinity failure: Enabled
    Soft Preemption: Disabled
  History:
    Tunnel has been up for: 05:18:56 (since Sun Jan 20 03:21:28 UTC 2019)
    Current LSP:
      Uptime: 05:18:56 (since Sun Jan 20 03:21:28 UTC 2019)
    Reopt. LSP:
      Last Failure:
        LSP not signalled, identical to the [CURRENT] LSP
        Date/Time: Sun Jan 20 08:28:17 UTC 2019 [00:12:07 ago]
    Prior LSP:
      ID: 5 Path Option: 2
      Removal Trigger: tunnel shutdown

  Path info (OSPF 1 area 0):
  Node hop count: 4
  Hop0: 10.1.3.3
  Hop1: 10.3.5.3
  Hop2: 10.3.5.5
  Hop3: 10.5.7.5
  Hop4: 10.5.7.7
  Hop5: 10.7.8.7
  Hop6: 10.7.8.8
  Hop7: 8.8.8.8

Name: tunnel-te103  Destination: 8.8.8.8  Ifhandle:0x980
  Signalled-Name: PE-1_t103
  Status:
    Admin:    up Oper:   up   Path:  valid   Signalling: connected

    path option 2,  type explicit PATH-3-Default (Basis for Setup, path weight 40)
    path option 3,  type dynamic
    G-PID: 0x0800 (derived from egress interface properties)
    Bandwidth Requested: 100 kbps  CT0
    Creation Time: Sun Jan 20 00:00:16 2019 (08:40:08 ago)
  Config Parameters:
    Bandwidth:      100 kbps (CT0) Priority:  1  1 Affinity: 0x0/0xffff
    Metric Type: TE (interface)
    Path Selection:
      Tiebreaker: Min-fill (default)
    Hop-limit: disabled
    Cost-limit: disabled
    Path-invalidation timeout: 10000 msec (default), Action: Tear (default)
    AutoRoute:  enabled  LockDown: disabled   Policy class: not set
    Forward class: 0 (default)
    Forwarding-Adjacency: disabled
    Autoroute Destinations: 0
    Loadshare:          0 equal loadshares
    Auto-bw: disabled
    Fast Reroute: Disabled, Protection Desired: None
    Path Protection: Not Enabled
    BFD Fast Detection: Disabled
    Reoptimization after affinity failure: Enabled
    Soft Preemption: Disabled
  History:
    Tunnel has been up for: 05:18:56 (since Sun Jan 20 03:21:28 UTC 2019)
    Current LSP:
      Uptime: 05:18:56 (since Sun Jan 20 03:21:28 UTC 2019)
    Reopt. LSP:
      Last Failure:
        LSP not signalled, identical to the [CURRENT] LSP
        Date/Time: Sun Jan 20 08:28:17 UTC 2019 [00:12:07 ago]
    Prior LSP:
      ID: 4 Path Option: 2
      Removal Trigger: tunnel shutdown

  Path info (OSPF 1 area 0):
  Node hop count: 4
  Hop0: 10.1.2.2
  Hop1: 10.2.5.2
  Hop2: 10.2.5.5
  Hop3: 10.5.6.5
  Hop4: 10.5.6.6
  Hop5: 10.6.8.6
  Hop6: 10.6.8.8
  Hop7: 8.8.8.8
Displayed 3 (of 3) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 3 up, 0 down, 0 recovering, 0 recovered heads
RP/0/0/CPU0:PE-1#

2 Replies 2

samarjit dutta
Beginner
Beginner

76 views but ... no reply. still waiting .... :)

 

Hi samarjit dutta,
I would do the following in order to check the operations:
1- Connect CE1 not as vrf device, connect CE1 to PE1 in global scope. Do not enable mpls in this connection, ipv4 only
2- At CE1 create static route to destination, 8.8.8.8, use PE1 as next-hop.
3- Perform the tests again in order to check if PBTS is working

I know that this is not your environment but it will check your PBTS setup more closely.
Regards
Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: