Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue trying to deploy a new SR path. #9

Open
Tinbo1383 opened this issue Dec 31, 2017 · 15 comments
Open

Issue trying to deploy a new SR path. #9

Tinbo1383 opened this issue Dec 31, 2017 · 15 comments

Comments

@Tinbo1383
Copy link

Hey there,

For a project @work I had to set up a simple topology to demonstrate the advantages of using SR over LDP/RSVP. So reading around I found this Pathman SR app that lets you configure dynamically SR paths over your MPLS network. So I set up a small topology, 4 XRv in EVE-NG, set up a new ubuntu VM with ODL and on top Pathman SR.

I think it went ok, but there a few things that I'm still struggling at and wanted to know if you guys can be of any help.

So, first of all, like I said, I have 4 XRv routers, but, only 3 of them are recognized as SR ready/PCEP ready and one of them is not. This is the log for that:

3586 2017-12-31 18:02:50.116 UTC root:node_sr_update INFO: SR sid updated for: 67372036 from bgp
3586 2017-12-31 18:02:50.116 UTC root:node_sr_update INFO: SR sid updated for: 16843009 from bgp
3586 2017-12-31 18:02:50.116 UTC root:node_sr_update ERROR: No BGP SID for: 33686018
3586 2017-12-31 18:02:50.116 UTC root:node_sr_update INFO: SR sid updated for: 50529027 from bgp

it seems the issue has to do with something called "termination-point" but it's weird cause thats actually the node that is directly connected to the VM with ODL/Pathman SR

3586 2017-12-31 18:03:18.712 UTC root:add_node INFO: New node: Node(name=u'67372036', id=u'67372036', loopback=u'4.4.4.4', portlist=[u'10.10.24.4', u'10.10.34.4'], pcc=u'pcc://4.4.4.4', pcep_type='07'
, prefix=[u'10.10.24.0/24', u'10.10.34.0/24', u'4.4.4.4/32'], sid='')
3586 2017-12-31 18:03:18.930 UTC root:add_node INFO: New node: Node(name=u'16843009', id=u'16843009', loopback=u'1.1.1.1', portlist=[u'10.10.12.1', u'10.10.13.1'], pcc=u'pcc://1.1.1.1', pcep_type='07'
, prefix=[u'1.1.1.1/32', u'10.10.12.0/24', u'10.10.13.0/24'], sid='')
3586 2017-12-31 18:03:18.931 UTC root:node_structure ERROR: Node 33686018 is missing 'termination-point'
3586 2017-12-31 18:03:18.931 UTC root:add_node INFO: New node: Node(name=u'33686018', id=u'33686018', loopback='', portlist=[], pcc='', pcep_type='', prefix=[u'10.10.12.0/24', u'10.10.23.0/24', u'10.1
0.24.0/24', u'192.168.1.0/30'], sid='')
3586 2017-12-31 18:03:19.137 UTC root:add_node INFO: Updated node: Node(name=u'33686018', id=u'33686018', loopback='', portlist=[u'10.10.12.2', u'10.10.23.2', u'10.10.24.2'], pcc='', pcep_type='', pre
fix=[u'10.10.12.0/24', u'10.10.23.0/24', u'10.10.24.0/24', u'192.168.1.0/30', u'2.2.2.2/32'], sid='')
3586 2017-12-31 18:03:19.335 UTC root:add_node INFO: New node: Node(name=u'50529027', id=u'50529027', loopback=u'3.3.3.3', portlist=[u'10.10.13.3', u'10.10.23.3', u'10.10.34.3'], pcc=u'pcc://3.3.3.3',
pcep_type='07', prefix=[u'10.10.13.0/24', u'10.10.23.0/24', u'10.10.34.0/24', u'3.3.3.3/32'], sid='')

All XRv routers has the same config, something like this:

router ospf 1
distribute bgp-ls
router-id 2.2.2.2
segment-routing mpls
redistribute connected
area 0
mpls traffic-eng
segment-routing mpls
interface Loopback0
passive enable
prefix-sid index 2001
!
interface GigabitEthernet0/0/0/0
network point-to-point
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa enable
!
interface GigabitEthernet0/0/0/1
network point-to-point
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa enable
!
interface GigabitEthernet0/0/0/2
network point-to-point
fast-reroute per-prefix
fast-reroute per-prefix ti-lfa enable
!
!
mpls traffic-eng router-id 2.2.2.2
!
router bgp 1
bgp router-id 2.2.2.2
address-family ipv4 unicast
!
address-family link-state link-state
!
neighbor 1.1.1.1
remote-as 1
update-source Loopback0
address-family ipv4 unicast
route-reflector-client
!
!
neighbor 3.3.3.3
remote-as 1
update-source Loopback0
address-family ipv4 unicast
!
!
neighbor 4.4.4.4
remote-as 1
update-source Loopback0
address-family ipv4 unicast
route-reflector-client
!
!
neighbor 192.168.1.2
remote-as 1
update-source GigabitEthernet0/0/0/3
address-family ipv4 unicast
route-reflector-client
!
address-family link-state link-state
route-reflector-client
!
!
!
mpls traffic-eng
pce
peer source ipv4 2.2.2.2
peer ipv4 192.168.1.2
!
segment-routing
logging events peer-status
stateful-client
instantiation
cisco-extension
!
!
auto-tunnel pcc
tunnel-id min 15 max 99
!
reoptimize timers delay installation 0
!
end

Issue#2: This is not a big deal but I think it has something to do with the other issues. Pathman SR can't get the XRv hostnames I assigned to them. It is assigning some weirds numbers. Its not actually an issue cause the topology is small but I'm guessing there is something wrong with my setup.

Issue#3:
I have configured a TE Tunnel with SR manually but it doesn't appear on Pathman SR

RP/0/0/CPU0:P1#sh mpls traffic-eng tunnels 14
Sun Dec 31 18:51:27.659 UTC

Name: tunnel-te14 Destination: 4.4.4.4 Ifhandle:0x90
Signalled-Name: P1_t14
Status:
Admin: up Oper: up Path: valid Signalling: connected

path option 10, (Segment-Routing) type explicit SR14 (Basis for Setup)
G-PID: 0x0800 (derived from egress interface properties)
Bandwidth Requested: 0 kbps  CT0
Creation Time: Sun Dec 31 17:10:08 2017 (01:41:19 ago)

Config Parameters:
Bandwidth: 0 kbps (CT0) Priority: 7 7 Affinity: 0x0/0x0
Metric Type: TE (global)
Path Selection:
Tiebreaker: Min-fill (default)
Protection: any (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
Path Protection: Not Enabled
BFD Fast Detection: Disabled
Reoptimization after affinity failure: Enabled
SRLG discovery: Disabled
History:
Tunnel has been up for: 01:31:31 (since Sun Dec 31 17:19:56 UTC 2017)
Current LSP:
Uptime: 01:31:26 (since Sun Dec 31 17:20:01 UTC 2017)
Prior LSP:
ID: 3 Path Option: 10
Removal Trigger: reoptimization completed

Segment-Routing Path Info (OSPF 1 area 0)
Segment0[Node]: 2.2.2.2, Label: 18001
Segment1[Node]: 3.3.3.3, Label: 19001
Segment2[Node]: 4.4.4.4, Label: 20001
Displayed 1 (of 1) heads, 0 (of 0) midpoints, 0 (of 0) tails
Displayed 1 up, 0 down, 0 recovering, 0 recovered heads

My question is, do all SR paths in the network appear on Pathman SR app or just the ones you configure using the app?

Issue#4: When I tried to set up the new path and deploy it using Pathman SR I got the following error:

3586 2017-12-31 18:20:24.461 UTC root:initialize INFO: Init 2 done - debug saved
3586 2017-12-31 18:20:24.461 UTC root:rest_interface_parser INFO: Commands Relieved: {u'option': u'list_all'}
3586 2017-12-31 18:20:24.468 UTC root:get_url INFO: Url get Status: 200
3586 2017-12-31 18:20:24.468 UTC root:listAllLsp INFO: list: [], formatted: []
3586 2017-12-31 18:20:24.469 UTC root:post INFO: {"response": [{"list": [], "option": "list_all", "success": true}]}
3586 2017-12-31 18:21:38.063 UTC root:initialize INFO: Init 2 done - debug saved
3586 2017-12-31 18:21:38.064 UTC root:rest_interface_parser INFO: Commands Relieved: {u'src': u'16843009', u'dst': u'67372036', u'option': u'path', u'metric': u'igp'}
3586 2017-12-31 18:21:38.064 UTC root:post INFO: {"response": [{"path": [["16843009", "50529027", "67372036"]], "metric": [2], "option": "path", "success": true}]}
3586 2017-12-31 18:21:50.909 UTC root:initialize INFO: Init 2 done - debug saved
3586 2017-12-31 18:21:50.911 UTC root:rest_interface_parser INFO: Commands Relieved: {u'path': [u'16843009', u'50529027', u'67372036'], u'option': u'create', u'name': u'TEST-PATHMAN'}
3586 2017-12-31 18:21:50.913 UTC root:get_loop_list INFO: Path: [u'16843009', u'50529027', u'67372036']
3586 2017-12-31 18:21:50.913 UTC root:get_loop_list INFO: Loop list: [u'3.3.3.3', u'4.4.4.4']
3586 2017-12-31 18:21:50.913 UTC root:get_sid_list INFO: Path: [u'16843009', u'50529027', u'67372036']
3586 2017-12-31 18:21:50.913 UTC root:get_sid_list INFO: SID list: [19001, 20001]
3586 2017-12-31 18:21:51.522 UTC root:createSRtunnel INFO: Create SR Tunnel response: {u'output': {u'failure': u'failed', u'error': [{u'error-object': {u'ignore': False, u'processing-rule': False, u'type'
: 4, u'value': 2}}]}}
3586 2017-12-31 18:21:53.526 UTC root:post INFO: {"response": [{"cause": {"failure": "failed", "error": [{"error-object": {"ignore": false, "processing-rule": false, "type": 4, "value": 2}}]}, "op
tion": "create", "success": false}]}
3586 2017-12-31 18:21:53.536 UTC root:initialize INFO: Init 2 done - debug saved
3586 2017-12-31 18:21:53.536 UTC root:rest_interface_parser INFO: Commands Relieved: {u'option': u'list_all'}
3586 2017-12-31 18:21:53.545 UTC root:get_url INFO: Url get Status: 200
3586 2017-12-31 18:21:53.545 UTC root:listAllLsp INFO: list: [], formatted: []
3586 2017-12-31 18:21:53.546 UTC root:post INFO: {"response": [{"list": [], "option": "list_all", "success": true}]}

Type 4 Value 2, what does it mean?

Well, I think all issues are connected somehow but I wanted to separate them so we can tackle them one by one.

Thanks a lot guys and by the way this is an amazing project!

Jose Jimbo
@nikmon2
Copy link
Contributor

nikmon2 commented Dec 31, 2017

Issue#2: This is not a big deal but I think it has something to do with the other issues. Pathman SR can't get the XRv hostnames I assigned to them. It is assigning some weirds numbers. Its not actually an issue cause the topology is small but I'm guessing there is something wrong with my setup

A:
OSPF does not carry hostnames with bgp-ls, therefore you will see the OSPF node-ID's on your map. (isis does)

  • You can get names displayed by putting your loopbacks in your /etc/hosts file - or registering them with your dns. (/etc/hosts for where pathman runs)

Cheers,
Niklas

@nikmon2
Copy link
Contributor

nikmon2 commented Dec 31, 2017

Issue#4: When I tried to set up the new path and deploy it using Pathman SR I got the following error:

3586 2017-12-31 18:21:51.522 UTC root:createSRtunnel INFO: Create SR Tunnel response: {u'output': {u'failure': u'failed', u'error': [{u'error-object': {u'ignore': False, u'processing-rule': False, u'type' : 4, u'value': 2}}]}}
3586 2017-12-31 18:21:53.526 UTC root:post INFO: {"response": [{"cause": {"failure": "failed", "error": [{"error-object": {"ignore": false, "processing-rule": false, "type": 4, "value": 2}}]}, "option": "create", "success": false}]}

A:
4/2 means that your device cannot do SR. from https://tools.ietf.org/html/rfc5440

   Error-Type=3 or Error-Type=4:  if a PCEP message is received that
      carries a PCEP object (with the P flag set) not recognized by the
      PCE or recognized but not supported, then the PCE MUST send a
      PCErr message with a PCEP-ERROR object (Error-Type=3 and 4,
      respectively).  In addition, the PCE MAY include in the PCErr
      message the unknown or not supported object.  The corresponding
      path computation request MUST be cancelled by the PCE without
      further notification.

You can get more information from your router with:

show mpls traffic-eng pce trace last 20

This is likely related to issue 1.

Cheers,
Niklas

@nikmon2
Copy link
Contributor

nikmon2 commented Dec 31, 2017

issue1:

3586 2017-12-31 18:02:50.116 UTC root:node_sr_update ERROR: No BGP SID for: 33686018
3586 2017-12-31 18:02:50.116 UTC root:node_sr_update INFO: SR sid updated for: 50529027 from bgp

it seems the issue has to do with something called "termination-point" but it's weird cause thats actually the node that is directly connected to the VM with ODL/Pathman SR

3586 2017-12-31 18:03:18.712 UTC root:add_node INFO: New node: Node(name=u'67372036', id=u'67372036', loopback=u'4.4.4.4', portlist=[u'10.10.24.4', u'10.10.34.4'], pcc=u'pcc://4.4.4.4', pcep_type='07', prefix=[u'10.10.24.0/24', u'10.10.34.0/24', u'4.4.4.4/32'], sid='')
3586 2017-12-31 18:03:18.930 UTC root:add_node INFO: New node: Node(name=u'16843009', id=u'16843009', loopback=u'1.1.1.1', portlist=[u'10.10.12.1', u'10.10.13.1'], pcc=u'pcc://1.1.1.1', pcep_type='07', prefix=[u'1.1.1.1/32', u'10.10.12.0/24', u'10.10.13.0/24'], sid='')
3586 2017-12-31 18:03:18.931 UTC root:node_structure ERROR: Node 33686018 is missing 'termination-point'

A:
Something is up with your node 33686018.

  • No termination point means that this node either doesn't have any interfaces, or pathman could not match bgp-ls to pcep topo.
    My guess is that it is using another loopback as router-id than pcep address.

Cheers,
Niklas

@nikmon2
Copy link
Contributor

nikmon2 commented Dec 31, 2017

Issue#3:
I have configured a TE Tunnel with SR manually but it doesn't appear on Pathman SR

A:
All active paths should show up. The basis for pathman information is from ODL's pcep topo: http://{odl_ip}:8181/restconf/operational/network-topology:network-topology/topology/pcep-topology

If your LSP is listed here, then Pathman should show it.

  • If it still doesn't display, then there may be an error logged in the /tmp/pathman.log file.

Cheers,
Niklas

@Tinbo1383
Copy link
Author

Tinbo1383 commented Jan 1, 2018 via email

@Tinbo1383
Copy link
Author

Tinbo1383 commented Jan 1, 2018 via email

@Tinbo1383
Copy link
Author

Tinbo1383 commented Jan 1, 2018 via email

@Tinbo1383
Copy link
Author

Tinbo1383 commented Jan 1, 2018 via email

@nikmon2
Copy link
Contributor

nikmon2 commented Jan 1, 2018

Hi Jose,

There is still something wrong with your router 2.2.2.2. The below means that is not SR capable.

Jan  1 00:32:37.913 mpls/te/pceerror 0/0/CPU0 t10 :8946: SR-ERO received without SR capability
Jan  1 00:32:37.913 mpls/te/pcectrl 0/0/CPU0 t10 TCP:9676: (PCE  T) Enqueued Error to 192.168.1.2: Type: 4 Value: 2

Here is a checklist:

  1. Verify that the all have their PCEP sessions up. (only required for headend)
 show mpls traffic-eng peer

  1. Make sure ODL can ping all loopbacks (pce addresses used)

  2. Verify that al nodes are SR enabled by issuing the following command:


RP/0/0/CPU0:sjc#show segment-routing traffic-eng ipv4 top
Mon Jan  1 19:46:58.959 UTC

SR-TE topology database:
------------------------

Node 1
  TE router ID: 198.19.1.21
  Host name: kcy
  ISIS system ID: 0000.0000.0021 level-2
  Prefix SID:
    Prefix 198.19.1.21, label 16021 (regular)

  Link[0]: local address 44.0.0.21, remote address 44.0.0.24
    Local node:
      ISIS system ID: 0000.0000.0021 level-2
    Remote node:
      TE router ID: 198.19.1.24
      Host name: min
      ISIS system ID: 0000.0000.0024 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24001 (unprotected)

  Link[1]: local address 45.0.0.21, remote address 45.0.0.27
    Local node:
      ISIS system ID: 0000.0000.0021 level-2
    Remote node:
      TE router ID: 198.19.1.27
      Host name: san
      ISIS system ID: 0000.0000.0027 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24005 (unprotected)

  Link[2]: local address 46.0.0.21, remote address 46.0.0.30
    Local node:
      ISIS system ID: 0000.0000.0021 level-2
    Remote node:
      TE router ID: 198.19.1.30
      Host name: sjc
      ISIS system ID: 0000.0000.0030 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24007 (unprotected)

  Link[3]: local address 58.0.0.21, remote address 58.0.0.22
    Local node:
      ISIS system ID: 0000.0000.0021 level-2
    Remote node:
      TE router ID: 198.19.1.22
      Host name: lax
      ISIS system ID: 0000.0000.0022 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 125000000, Reservable 12500
    Adj SID: 24003 (unprotected)

Node 2
  TE router ID: 198.19.1.22
  Host name: lax
  ISIS system ID: 0000.0000.0022 level-2
  Prefix SID:
    Prefix 198.19.1.22, label 16022 (regular)

  Link[0]: local address 48.0.0.22, remote address 48.0.0.27
    Local node:
      ISIS system ID: 0000.0000.0022 level-2
    Remote node:
      TE router ID: 198.19.1.27
      Host name: san
      ISIS system ID: 0000.0000.0027 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24003 (unprotected)

  Link[1]: local address 49.0.0.22, remote address 49.0.0.30
    Local node:
      ISIS system ID: 0000.0000.0022 level-2
    Remote node:
      TE router ID: 198.19.1.30
      Host name: sjc
      ISIS system ID: 0000.0000.0030 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24005 (unprotected)

  Link[2]: local address 58.0.0.22, remote address 58.0.0.21
    Local node:
      ISIS system ID: 0000.0000.0022 level-2
    Remote node:
      TE router ID: 198.19.1.21
      Host name: kcy
      ISIS system ID: 0000.0000.0021 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 125000000, Reservable 12500
    Adj SID: 24001 (unprotected)

Node 3
  TE router ID: 198.19.1.24
  Host name: min
  ISIS system ID: 0000.0000.0024 level-2
  Prefix SID:
    Prefix 198.19.1.24, label 16024 (regular)

  Link[0]: local address 44.0.0.24, remote address 44.0.0.21
    Local node:
      ISIS system ID: 0000.0000.0024 level-2
    Remote node:
      TE router ID: 198.19.1.21
      Host name: kcy
      ISIS system ID: 0000.0000.0021 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24001 (unprotected)

  Link[1]: local address 51.0.0.24, remote address 51.0.0.28
    Local node:
      ISIS system ID: 0000.0000.0024 level-2
    Remote node:
      TE router ID: 198.19.1.28
      Host name: sea
      ISIS system ID: 0000.0000.0028 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24003 (unprotected)

  Link[2]: local address 57.0.0.24, remote address 57.0.0.30
    Local node:
      ISIS system ID: 0000.0000.0024 level-2
    Remote node:
      TE router ID: 198.19.1.30
      Host name: sjc
      ISIS system ID: 0000.0000.0030 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 125000000, Reservable 12500
    Adj SID: 24005 (unprotected)

Node 4
  TE router ID: 198.19.1.27
  Host name: san
  ISIS system ID: 0000.0000.0027 level-2
  Prefix SID:
    Prefix 198.19.1.27, label 16027 (regular)

  Link[0]: local address 45.0.0.27, remote address 45.0.0.21
    Local node:
      ISIS system ID: 0000.0000.0027 level-2
    Remote node:
      TE router ID: 198.19.1.21
      Host name: kcy
      ISIS system ID: 0000.0000.0021 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24003 (unprotected)

  Link[1]: local address 48.0.0.27, remote address 48.0.0.22
    Local node:
      ISIS system ID: 0000.0000.0027 level-2
    Remote node:
      TE router ID: 198.19.1.22
      Host name: lax
      ISIS system ID: 0000.0000.0022 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24001 (unprotected)

Node 5
  TE router ID: 198.19.1.30
  Host name: sjc
  ISIS system ID: 0000.0000.0030 level-2
  Prefix SID:
    Prefix 198.19.1.30, label 16030 (regular)

  Link[0]: local address 46.0.0.30, remote address 46.0.0.21
    Local node:
      ISIS system ID: 0000.0000.0030 level-2
    Remote node:
      TE router ID: 198.19.1.21
      Host name: kcy
      ISIS system ID: 0000.0000.0021 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24009 (unprotected)

  Link[1]: local address 49.0.0.30, remote address 49.0.0.22
    Local node:
      ISIS system ID: 0000.0000.0030 level-2
    Remote node:
      TE router ID: 198.19.1.22
      Host name: lax
      ISIS system ID: 0000.0000.0022 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24007 (unprotected)

  Link[2]: local address 55.0.0.30, remote address 55.0.0.28
    Local node:
      ISIS system ID: 0000.0000.0030 level-2
    Remote node:
      TE router ID: 198.19.1.28
      Host name: sea
      ISIS system ID: 0000.0000.0028 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24001 (unprotected)

  Link[3]: local address 56.0.0.30, remote address 56.0.0.29
    Local node:
      ISIS system ID: 0000.0000.0030 level-2
    Remote node:
      TE router ID: 198.19.1.29
      Host name: sfc
      ISIS system ID: 0000.0000.0029 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24005 (unprotected)

  Link[4]: local address 57.0.0.30, remote address 57.0.0.24
    Local node:
      ISIS system ID: 0000.0000.0030 level-2
    Remote node:
      TE router ID: 198.19.1.24
      Host name: min
      ISIS system ID: 0000.0000.0024 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 125000000, Reservable 12500
    Adj SID: 24003 (unprotected)

Node 6
  TE router ID: 198.19.1.28
  Host name: sea
  ISIS system ID: 0000.0000.0028 level-2
  Prefix SID:
    Prefix 198.19.1.28, label 16028 (regular)

  Link[0]: local address 51.0.0.28, remote address 51.0.0.24
    Local node:
      ISIS system ID: 0000.0000.0028 level-2
    Remote node:
      TE router ID: 198.19.1.24
      Host name: min
      ISIS system ID: 0000.0000.0024 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24003 (unprotected)

  Link[1]: local address 53.0.0.28, remote address 53.0.0.26
    Local node:
      ISIS system ID: 0000.0000.0028 level-2
    Remote node:
      TE router ID: 198.19.1.26
      Host name: por
      ISIS system ID: 0000.0000.0026 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24001 (unprotected)

  Link[2]: local address 55.0.0.28, remote address 55.0.0.30
    Local node:
      ISIS system ID: 0000.0000.0028 level-2
    Remote node:
      TE router ID: 198.19.1.30
      Host name: sjc
      ISIS system ID: 0000.0000.0030 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24005 (unprotected)

Node 7
  TE router ID: 198.19.1.26
  Host name: por
  ISIS system ID: 0000.0000.0026 level-2
  Prefix SID:
    Prefix 198.19.1.26, label 16026 (regular)

  Link[0]: local address 53.0.0.26, remote address 53.0.0.28
    Local node:
      ISIS system ID: 0000.0000.0026 level-2
    Remote node:
      TE router ID: 198.19.1.28
      Host name: sea
      ISIS system ID: 0000.0000.0028 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24001 (unprotected)

  Link[1]: local address 54.0.0.26, remote address 54.0.0.29
    Local node:
      ISIS system ID: 0000.0000.0026 level-2
    Remote node:
      TE router ID: 198.19.1.29
      Host name: sfc
      ISIS system ID: 0000.0000.0029 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24003 (unprotected)

Node 8
  TE router ID: 198.19.1.29
  Host name: sfc
  ISIS system ID: 0000.0000.0029 level-2
  Prefix SID:
    Prefix 198.19.1.29, label 16029 (regular)

  Link[0]: local address 54.0.0.29, remote address 54.0.0.26
    Local node:
      ISIS system ID: 0000.0000.0029 level-2
    Remote node:
      TE router ID: 198.19.1.26
      Host name: por
      ISIS system ID: 0000.0000.0026 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24001 (unprotected)

  Link[1]: local address 56.0.0.29, remote address 56.0.0.30
    Local node:
      ISIS system ID: 0000.0000.0029 level-2
    Remote node:
      TE router ID: 198.19.1.30
      Host name: sjc
      ISIS system ID: 0000.0000.0030 level-2
    Metric: IGP 10, TE 10
    Bandwidth: Total link 1250000, Reservable 12500
    Adj SID: 24003 (unprotected)

RP/0/0/CPU0:sjc#

Here is an example OSPF config I used.
I notice that you are missing the forwarding command.

!
ospf name-lookup
router ospf pce
 router-id 198.19.1.21
 area 0
  segment-routing forwarding mpls
  mpls traffic-eng
  segment-routing mpls
  interface Loopback0
   prefix-sid absolute 16021
   cost 1
   passive enable
  !
  interface GigabitEthernet0/0/0/0
   cost 10
   network point-to-point
  !
  interface GigabitEthernet0/0/0/1
   cost 10
   network point-to-point
  !
  interface GigabitEthernet0/0/0/2
   cost 10
   network point-to-point
  !
!

@Tinbo1383
Copy link
Author

Tinbo1383 commented Jan 1, 2018 via email

@nikmon2
Copy link
Contributor

nikmon2 commented Jan 1, 2018

I'm using 6.2.1, and it's available in 6.4.1.
Don't know when it was added.
Try: show mpls forwarding, it should that you have bound labels/SIDs

Cheers,
Niklas

RP/0/0/CPU0:sjc#show mpls forwarding
Mon Jan  1 21:57:25.169 UTC
Local  Outgoing    Prefix             Outgoing     Next Hop        Bytes
Label  Label       or ID              Interface                    Switched
------ ----------- ------------------ ------------ --------------- ------------
16021  Pop         SR Pfx (idx 21)    Gi0/0/0/1    46.0.0.21       700310
16022  Pop         SR Pfx (idx 22)    Gi0/0/0/2    49.0.0.22       70041900
16024  Pop         SR Pfx (idx 24)    Gi0/0/0/0    57.0.0.24       700459
16026  16026       SR Pfx (idx 26)    Gi0/0/0/3    55.0.0.28       756570
       16026       SR Pfx (idx 26)    Gi0/0/0/4    56.0.0.29       0
16027  16027       SR Pfx (idx 27)    Gi0/0/0/1    46.0.0.21       756589
       16027       SR Pfx (idx 27)    Gi0/0/0/2    49.0.0.22       0
16028  Pop         SR Pfx (idx 28)    Gi0/0/0/3    55.0.0.28       35015100
16029  Pop         SR Pfx (idx 29)    Gi0/0/0/4    56.0.0.29       34314602
24000  Pop         SR Adj (idx 1)     Gi0/0/0/3    55.0.0.28       0
24001  Pop         SR Adj (idx 3)     Gi0/0/0/3    55.0.0.28       0
24002  Pop         SR Adj (idx 1)     Gi0/0/0/0    57.0.0.24       0
24003  Pop         SR Adj (idx 3)     Gi0/0/0/0    57.0.0.24       0
24004  Pop         SR Adj (idx 1)     Gi0/0/0/4    56.0.0.29       0
24005  Pop         SR Adj (idx 3)     Gi0/0/0/4    56.0.0.29       0
24006  Pop         SR Adj (idx 1)     Gi0/0/0/2    49.0.0.22       0
24007  Pop         SR Adj (idx 3)     Gi0/0/0/2    49.0.0.22       0
24008  Pop         SR Adj (idx 1)     Gi0/0/0/1    46.0.0.21       0
24009  Pop         SR Adj (idx 3)     Gi0/0/0/1    46.0.0.21       0
RP/0/0/CPU0:sjc#

@Tinbo1383
Copy link
Author

Tinbo1383 commented Jan 1, 2018 via email

@nikmon2
Copy link
Contributor

nikmon2 commented Jan 2, 2018

Hi Jose,

I have not used 6.1.3, but I have seen pcep issues w 6.1.1, so you may be better served with a 6.2 image.

If you are using VIRL w XRv, then you may want to add this command to your configuration:

mpls traffic-eng platform-check disable

As you have SR enabled and the router complains that is not, this looks like an XR issue to me.

Below is a full config example for OSPF.
There are some slight differences to yours:

  • OSPF SR commands inside area0 vs before
  • ntp configured
  • the platform check command

Cheers,
Niklas

hostname sjc
service timestamps log datetime msec
service timestamps debug datetime msec
telnet vrf default ipv4 server max-servers 10
domain ipv4 host kcy 198.19.1.21
domain ipv4 host lax 198.19.1.22
domain ipv4 host min 198.19.1.24
domain ipv4 host por 198.19.1.26
domain ipv4 host san 198.19.1.27
domain ipv4 host sea 198.19.1.28
domain ipv4 host sfc 198.19.1.29
domain ipv4 host sjc 198.19.1.30
vrf lool
!
line template vty
 timestamp
 exec-timeout 720 0
!
line console
 exec-timeout 0 0
 length 50
 interactive syntax check
!
line default
 exec-timeout 720 0
!
vty-pool default 0 50
! (snmp removed)
!
ntp
 server 198.18.1.1
!
alias pps show int | i packets/sec
alias sbs show bgp sum
ipv4 unnumbered mpls traffic-eng Loopback0
control-plane
 management-plane
  inband
   interface all
    allow all
   !
  !
 !
!
interface Loopback0
 description Loopback
 ipv4 address 198.19.1.30 255.255.255.255
!
interface MgmtEth0/0/CPU0/0
 description OOB Management
 ! Configured on launch
 ipv4 address 198.18.1.37 255.255.255.0
!
interface GigabitEthernet0/0/0/0
 ipv4 address 57.0.0.30 255.255.255.0
!
interface GigabitEthernet0/0/0/1
 ipv4 address 46.0.0.30 255.255.255.0
 speed 10
!
interface GigabitEthernet0/0/0/2
 ipv4 address 49.0.0.30 255.255.255.0
 speed 10
!
interface GigabitEthernet0/0/0/3
 ipv4 address 55.0.0.30 255.255.255.0
 speed 10
!
interface GigabitEthernet0/0/0/4
 ipv4 address 56.0.0.30 255.255.255.0
 speed 10
!
route-policy pass-all
  pass
end-policy
!
router static
 address-family ipv4 unicast
  10.16.0.0/16 198.18.1.1
  11.11.8.0/24 Null0
  198.18.128.0/18 198.18.1.1
 !
!
ospf name-lookup
router ospf pce
 distribute bgp-ls
 router-id 198.19.1.30
 address-family ipv4 unicast
 area 0
  segment-routing forwarding mpls
  mpls traffic-eng
  segment-routing mpls
  interface Loopback0
   prefix-sid absolute 16030
   cost 1
   passive enable
  !
  interface GigabitEthernet0/0/0/0
   cost 10
   network point-to-point
  !
  interface GigabitEthernet0/0/0/1
   cost 10
   network point-to-point
  !
  interface GigabitEthernet0/0/0/2
   cost 10
   network point-to-point
  !
  interface GigabitEthernet0/0/0/3
   cost 10
   network point-to-point
  !
  interface GigabitEthernet0/0/0/4
   cost 10
   network point-to-point
  !
  interface GigabitEthernet0/0/0/5
   cost 10
   network broadcast
  !
 !
!
router bgp 65504
 bgp router-id 198.19.1.30
 bgp cluster-id 198.19.1.30
 address-family ipv4 unicast
  network 46.0.0.30/32
  network 49.0.0.30/32
  network 55.0.0.30/32
  network 56.0.0.30/32
 !
 address-family link-state link-state
 !
 neighbor 198.18.1.80
  remote-as 65504
  update-source MgmtEth0/0/CPU0/0
  address-family ipv4 unicast
   route-reflector-client
  !
  address-family link-state link-state
   route-reflector-client
  !
 !
 neighbor 198.19.1.21
  remote-as 65504
  update-source Loopback0
  address-family ipv4 unicast
   route-reflector-client
  !
 !
 neighbor 198.19.1.22
  remote-as 65504
  update-source Loopback0
  address-family ipv4 unicast
   route-reflector-client
  !
 !
 neighbor 198.19.1.24
  remote-as 65504
  update-source Loopback0
  address-family ipv4 unicast
   route-reflector-client
  !
 !
 neighbor 198.19.1.26
  remote-as 65504
  update-source Loopback0
  address-family ipv4 unicast
   route-reflector-client
  !
 !
 neighbor 198.19.1.27
  remote-as 65504
  update-source Loopback0
  address-family ipv4 unicast
   route-reflector-client
  !
 !
 neighbor 198.19.1.28
  remote-as 65504
  update-source Loopback0
  address-family ipv4 unicast
   route-reflector-client
  !
 !
 neighbor 198.19.1.29
  remote-as 65504
  update-source Loopback0
  address-family ipv4 unicast
   route-reflector-client
  !
 !
!
mpls oam
!
rsvp
 interface GigabitEthernet0/0/0/0
  bandwidth 100 100
 !
 interface GigabitEthernet0/0/0/1
  bandwidth 100 100
 !
 interface GigabitEthernet0/0/0/2
  bandwidth 100 100
 !
 interface GigabitEthernet0/0/0/3
  bandwidth 100 100
 !
 interface GigabitEthernet0/0/0/4
  bandwidth 100 100
 !
!
mpls traffic-eng platform-check disable
mpls traffic-eng
 interface GigabitEthernet0/0/0/0
 !
 interface GigabitEthernet0/0/0/1
 !
 interface GigabitEthernet0/0/0/2
 !
 interface GigabitEthernet0/0/0/3
 !
 interface GigabitEthernet0/0/0/4
 !
 pce
  peer ipv4 198.18.1.80
  !
  segment-routing
  stateful-client
   instantiation
   cisco-extension
  !
 !
 auto-tunnel pcc
  tunnel-id min 1 max 99
 !
 reoptimize timers delay installation 0
!
netconf-yang agent
 ssh
!
ssh server v2
ssh server netconf vrf default
ssh server netconf port 830
ssh timeout 120
end

@Tinbo1383
Copy link
Author

Hey there,

So I tried 6.5.1 version, a bit buggy but now I get a different error:

Jan 14 21:17:51.320 mpls/te/pceerror 0/0/CPU0 t11 :1778: Unknown ERO type 5!
Jan 14 21:17:51.320 mpls/te/pcectrl 0/0/CPU0 t11 TCP:9615: (PCE T) Enqueued Error to 192.168.1.2: Type: 3 Value: 2

I think I read somewhere it has to do with the address of the tunnel, I added this config:

RP/0/0/CPU0:P1#sh run
Sun Jan 14 21:24:12.393 UTC
Building configuration...
!! IOS XR Configuration 6.5.1.02I
!! Last configuration change at Sun Jan 14 19:18:38 2018 by cisco
!
hostname P1
logging console debugging
domain name claro.com
ipv4 unnumbered mpls traffic-eng Loopback0

but no luck so far

I'm gonna try a 6.2.x version this week but I don't think it has something to do with the IOS version.

@Tahir93
Copy link

Tahir93 commented May 5, 2018 •
edited

Hi everyone,

I am facing the same issue. When I am deploying a path via pathman sr the following error pops up "Response indicated the error in frontend-backend communication. "
My PCEP and SR both are up and enabled.

Following are the logs that appear when i try to deploy the path via pathman.

432 2018-05-05 03:07:49.460 UTC root:initialize INFO: Init 2 done - debug saved
432 2018-05-05 03:07:49.461 UTC root:rest_interface_parser INFO: Commands Relieved: {u'path': [u'R1-P1', u'R3-P3'], u'option': u'create', u'name': u'R1-P1 -> R3-P3'}
432 2018-05-05 03:07:49.462 UTC root:get_loop_list INFO: Path: [u'R1-P1', u'R3-P3']
432 2018-05-05 03:07:49.462 UTC root:get_loop_list INFO: Loop list: [u'49.1.1.3']
432 2018-05-05 03:07:49.462 UTC root:get_sid_list INFO: Path: [u'R1-P1', u'R3-P3']
432 2018-05-05 03:07:49.463 UTC root:get_sid_list INFO: SID list: [33]
432 2018-05-05 03:07:49.559 UTC root:createSRtunnel INFO: Create SR Tunnel response: {u'output': {u'failure': u'failed', u'error': [{u'error-object': {u'ignore': False, u'processing-rule': False, u'type': 4, u'value': 2}}]}}
432 2018-05-05 03:07:51.562 UTC root:post INFO: {"response": [{"cause": {"failure": "failed", "error": [{"error-object": {"ignore": false, "processing-rule": false, "type": 4, "value": 2}}]}, "option": "create", "success": false}]}
432 2018-05-05 03:07:51.596 UTC root:initialize INFO: Init 2 done - debug saved
432 2018-05-05 03:07:51.597 UTC root:rest_interface_parser INFO: Commands Relieved: {u'option': u'list_all'}
432 2018-05-05 03:07:51.630 UTC root:get_url INFO: Url get Status: 200
432 2018-05-05 03:07:51.632 UTC root:listAllLsp INFO: list: [], formatted: []
432 2018-05-05 03:07:51.632 UTC root:post INFO: {"response": [{"list": [], "option": "list_all", "success": true}]}

Any help in this regard is highly appreciated.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nikmon2 @Tahir93 @Tinbo1383