Open parulagrawal14 opened 7 years ago
nikmon2
commented
7 years ago Hi,
What's your ODL version? Can you share the beginning of the pathman.log file, showing the topology build up?
Cheers, Niklas
parulagrawal14
commented
7 years ago Hi,
Thanks for your reply.
I am using ODL version 0.4.4-Beryllium-SR4
Kindly find the complete logs below:
19279 2017-11-29 18:02:11.483 UTC root:
Regards, Parul
On Wed, Nov 29, 2017 at 10:23 PM, nikmon2 notifications@github.com wrote:
Hi,
What's your ODL version? Can you share the beginning of the pathman.log file, showing the topology build up?
Cheers, Niklas
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CiscoDevNet/Opendaylight-BGP-Pathman-apps/issues/3#issuecomment-347923743, or mute the thread https://github.com/notifications/unsubscribe-auth/AL780w3KoSwNF5b5WxySYLu9aFjtJAGLks5s7YvugaJpZM4Qs8R4 .
nikmon2
commented
7 years ago Hi Parul,
I don't see any PCEP details. What is the output of: http://{controller_ip}:8181/restconf/operational/network-topology:network-topology/topology/pcep-topology
The router loopback IP used for bgp_ls must match the pcep IP. That's how the two topologies are tied together.
Cheers, Niklas
parulagrawal14
commented
7 years ago Hi,
Output of the pcep topology { "topology": [ { "topology-id": "pcep-topology", "topology-types": { "network-topology-pcep:topology-pcep": {} }, "node": [ { "node-id": "pcc://192.168.121.237", "network-topology-pcep:path-computation-client": { "ip-address": "192.168.121.237", "state-sync": "synchronized", "stateful-tlv": { "odl-pcep-ietf-stateful07:stateful": { "lsp-update-capability": true, "odl-pcep-ietf-initiated00:initiation": true } } } } ] } ] }
Regards, Parul
On Wed, Nov 29, 2017 at 1:07 PM, nikmon2 notifications@github.com wrote:
Hi Parul,
I don't see any PCEP details. What is the output of: http://{controller_ip}:8181/restconf/operational/network- topology:network-topology/topology/pcep-topology
Cheers, Niklas
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/CiscoDevNet/Opendaylight-BGP-Pathman-apps/issues/3#issuecomment-347963554, or mute the thread https://github.com/notifications/unsubscribe-auth/AL7809yEvt1jK0DrGXKcy64NnsjNuwW6ks5s7auPgaJpZM4Qs8R4 .
nikmon2
commented
7 years ago Hi Parul,
The loopback on your "router-id" should then be: "192.168.121.237" for this node, in the output from: http://{controller_ip}:8181/restconf/operational/network-topology:network-topology/topology/example-linkstate-topology
{
"node-id": "bgpls://IsisLevel2:0/type=node&as=65504&domain=3323134238&router=0000.0000.0029",
"termination-point": [
{
"tp-id": "bgpls://IsisLevel2:0/type=tp&ipv4=59.0.0.29",
"l3-unicast-igp-topology:igp-termination-point-attributes": {}
},
{
"tp-id": "bgpls://IsisLevel2:0/type=tp&ipv4=56.0.0.29",
"l3-unicast-igp-topology:igp-termination-point-attributes": {}
},
{
"tp-id": "bgpls://IsisLevel2:0/type=tp&ipv4=54.0.0.29",
"l3-unicast-igp-topology:igp-termination-point-attributes": {}
},
{
"tp-id": "bgpls://IsisLevel2:0/type=tp"
}
],
"l3-unicast-igp-topology:igp-node-attributes": {
"router-id": [
"198.19.1.29"
],
"name": "sfc",
"isis-topology:isis-node-attributes": {
"net": [
"72.0000.0000.0000.0000.0000.0029"
],
"ted": {
"te-router-id-ipv4": "198.19.1.29"
},
"iso": {
"iso-system-id": "0000.0000.0029"
}
}
}
}Cheers, Niklas
mjyasini
commented
6 years ago I have the same problem, following what Niklas explained, first of all my PCC ip address should be in the range of ODL IP address and for having the PCEP link to be UP, I have to define IP of the source on router as bellow:
mpls traffic-eng interface GigabitEthernet0/0/0/0 ! interface GigabitEthernet0/0/0/1 ! interface GigabitEthernet0/0/0/2 ! interface GigabitEthernet0/0/0/3 ! pce peer source ipv4 172.16.1.84 >>>> management interface of router peer ipv4 172.16.1.128 >>>>>ODL IP Address ! stateful-client instantiation ! speaker-entity-id 10.10.4.100 !
!
my first question is that, why i have to specify peer source ip address, while in other sample configurations , there is not such configuration?
my second question is that the "router ID" is the ip address of loopback interface defines under ISIS. how it is possible to be equal to PCEP IP (which in my case is 172.16.1.84) considering that this address should be the address of physical interface connected to ODL, if i want to have PCEP link UP and working.
thank you in advanced
nikmon2
commented
6 years ago my first question is that, why i have to specify peer source ip address, while in other sample configurations , there is not such configuration?Both the routers and your ODL controller need to be able to reach each other, test that the contro
Adding that explicit configuration, changes your PCC address, and Pathman can't consolidate what link-state entires match what PCC. Today that needs to be one and the same IP.
my second question is that the "router ID" is the ip address of loopback interface defines under ISIS. how it is possible to be equal to PCEP IP (which in my case is 172.16.1.84) considering that this address should be the address of physical interface connected to ODL, if i want to have PCEP link UP and working.It should not need to be a directly connected interface. If that was the case, it would get complicated as soon as yo go outside a lab. Just verify that you can ping your loopbacks from the controller.
Hope this helps.
Cheers, Niklas
Hi All,
I am getting below error while executing the steps mentioned:
Click "Create new LSP" on pathman app Select source and destination Click "Go" Choose path Enter name "mypath" Click "Deploy"
"7967 2017-11-28 09:31:08.878 UTC root:rest_interface_parser INFO: Commands Recieved: {u'path': [u'R1', u'R2'], u'name': u'mypath', u'option': u'create'} 7967 2017-11-28 09:31:08.878 UTC root:getHoplist INFO: Path: [u'0001.0001.0001', u'0001.0001.0002'] 7967 2017-11-28 09:31:08.878 UTC root:getHoplist INFO: Hoplist: [u'20.0.0.3'] 7967 2017-11-28 09:31:08.895 UTC root:create_02_Lsp INFO: Create 02LSP response: {u'errors': {u'error': [{u'error-type': u'protocol', u'error-tag': u'invalid-value', u'error-message': u'URI has bad format. If operations behind mount point should be showed, URI has to end with yang-ext:mount'}]}} 7967 2017-11-28 09:31:08.895 UTC root:post INFO: {"response": [{"cause": "KeyError: output", "option": "unknown", "success": false}]}" 9900 2017-01-03 14:45:31.791 UTC root:rest_interface_parser INFO: Commands Recieved: {u'path': [u'router1', u'router2'], u'name': u'mypat\x00', u'option': u'create'}
Can you please guide me on this ?