On Thu, Dec 18, 2014 at 9:34 PM, Andrea Florio <[email protected]> wrote: > > Hello Lori, > > so looks like something is working now :) > > LISP to LISP is working : > > Gateway#ping 153.16.54.163 source GigabitEthernet0/1 > Type escape sequence to abort. > Sending 5, 100-byte ICMP Echos to 153.16.54.163, timeout is 2 seconds: > Packet sent with a source address of 153.16.53.161 > !!!!! > Success rate is 100 percent (5/5), round-trip min/avg/max = 156/160/164 ms > > > but LISP to NON-LISP is not working ... as PETR / PITR i'm using the same > ones as i use for regular lisp on my cisco router... > > Ideas? >
Are you using the same EID on your Cisco router? It may be that the PITR has cached the RLOC of your Cisco router for that EID and you have to SMR it to force it to refresh the mapping (or let the mapping expire before using the EID on LISPmob). Alberto > > Thanks, > Andrea > > > > 2014-12-17 14:45 GMT+01:00 Andrea Florio <[email protected]>: >> >> Hello Lori, >> >> thanks again for your help >> >> 2014-12-17 13:34 GMT+01:00 Lori Jakab <[email protected]>: >>> >>> How do you test? >>> >>> >> I am doing reach-ability tests. From both, a lisp enabled router, and a >> non lisp router. i cannot reach the EID 153.16.53.163/32 in both cases. >> But i have no problems with the was address (90.177.68.57) >> >> >>> Please remove the IPv6 PITRs from the list, since you don't seem to have >>> IPv6 connectivity and there are some error messages because of that >>> cluttering the logs, which will make it more difficult for you to spot >>> real problems. >>> >> >> done thanks >> >> >>> There is nothing wrong here, the above behavior is expected. The IP >>> address that you see as your RLOC is the RLOC of the RTR that is being >>> used for NAT traversal. See more details in the draft that Alberto >>> referenced. >>> >>> >> my apologies if i didn't go trough the whole document, but i don't have >> reach-ability, and this is why i believe something is not behaving as >> supposed to (doesn't have to be lispmob itself though, of course). >> The other strange thing i observe is that a traceroute, is becoming >> un-responsive at every attempt few hops shorter. >> >> >> now, if i was on a router, i would configure lisp without nat aware >> feature. I would then create a locator set by using my public ip address (a >> loopback with my public ip /32 my be required) . >> but this is not an option with lispmob as it seems that i can only >> specify and interface in my database mapping. >> >> Andrea >> >> -- >> ------------------------------------------ >> Andrea Florio >> AT&T Brno - Senior Network Architect >> CISCO CCNA Wireless and Security, CCNP Certified >> openSUSE Official Member (anubisg1) >> Email: [email protected] >> Email: [email protected] >> Cell: +39-328-7365667 >> Cell: +420-778-033288 >> Website: http://journey4ccie.com/ >> ------------------------------------------ >> > > > -- > ------------------------------------------ > Andrea Florio > AT&T Brno - Senior Network Architect > CISCO CCNA Wireless and Security, CCNP Certified > openSUSE Official Member (anubisg1) > Email: [email protected] > Email: [email protected] > Cell: +39-328-7365667 > Cell: +420-778-033288 > Website: http://journey4ccie.com/ > ------------------------------------------ >
