onos-service-announce

[Andrew Ragusa <>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Jeronimo

I updated the perfSONAR configs for this.  I also need to get the
Indiana GigaPOP to accept that prefix before it will work.  I'm
putting in a ticket with neteng to fix that on the router.

Thanks
A.J.


On 8/13/15 4:08 PM, Jeronimo Bezerra wrote:
> Hi A.J.,
> 
> Please use perfsonar.ampath.net <http://perfsonar.ampath.net>
> (190.103.184.146) on your Maddash configuration to connect to our
> PS. But, inside ONOS’s IP domain, we had to change our server’s IP
> to keep inside the same IP domain (10.10.0.0/16) we use for
> AmLight.
> 
> External IP: 190.103.184.146 Internal (ONOS VRF): 10.10.11.2
> (reachable only for ONOS users).
> 
> Is that ok for you?
> 
> Could you please try again?
> 
> Thanks, Jeronimo
> 
> 
>> On Aug 13, 2015, at 3:33 PM, Andrew Ragusa 
>> <
>>  
>> <mailto:>>
>>  wrote:
>> 
> Hi Jeronimo
> 
> Our MadDash UI is unable to talk to your perfSONAR host.  Here is
> the results of traceroute.
> 
> [root@onos-ps
>  onos-regular-testing]# traceroute 190.103.184.162 
> traceroute to 190.103.184.162 (190.103.184.162), 30 hops max, 60
> byte packets 1  irb.3800.dcr3.bldc.net.uits.iu.edu
> <http://bldc.net.uits.iu.edu> (140.182.45.2)  0.221 ms  0.228 ms
> 0.250 ms 2  ae-23.900.br2.bldc.net.uits.iu.edu
> <http://bldc.net.uits.iu.edu> (134.68.3.80)  7.680 ms  7.729 ms
> 7.663 ms 3  ae-0.0.br2.ictc.net.uits.iu.edu
> <http://ictc.net.uits.iu.edu> (134.68.3.34)  1.424 ms  1.437 ms 
> 1.485 ms 4  ae-10.902.dcr.ictc.net.uits.iu.edu (134.68.3.147)
> 1.352 ms  1.315 ms  1.406 ms 5  ae-21.902.br2.ictc.net.uits.iu.edu
> <http://ictc.net.uits.iu.edu> (134.68.3.146)  1.199 ms  1.168 ms
> 1.145 ms 6  ae-4.9.rtr.ictc.indiana.gigapop.net 
> <http://rtr.ictc.indiana.gigapop.net> (149.165.254.229)  2.810 ms 
> 2.797 ms  2.802 ms 7  et-10-0-0.101.rtr.chic.net.internet2.edu 
> <http://rtr.chic.net.internet2.edu> (149.165.254.186)  7.725 ms
> 7.625 ms  7.713 ms 8  et-5-0-0.108.rtr.atla.net.internet2.edu 
> <http://rtr.atla.net.internet2.edu> (198.71.45.10)  26.152 ms 
> 26.149 ms  26.148 ms 9  from-flr-atl-i2.ampath.net
> <http://from-flr-atl-i2.ampath.net> (198.32.252.237)  38.809 ms
> 38.971 ms 39.094 ms
> 
> Also I am unable to ping from our perfSONAR box to your perfSONAR
> box 190.103.186.114, I can however ping 190.103.186.113
> 
> Do I need to update our configuration?
> 
> Thanks A.J.
> 
> 
> 
> On 8/13/15 3:02 PM, Jeronimo Bezerra wrote:
>>>> Hi A.J.,
>>>> 
>>>> From AmLight ONOS deployment, from a server in Brazil, we can
>>>> ping a few IP addresses connected to Internet2 ONOS (10.1.101
>>>> and 10.1.102). I haven’t tested all IPs yet.
>>>> 
>>>> Our Maddash: onos.ampath.net <http://onos.ampath.net> 
>>>> <http://onos.ampath.net>
>>>> 
>>>> Thanks, Jeronimo
>>>> 
>>>>> On Aug 13, 2015, at 2:49 PM, Andrew Ragusa
>>>>> <
>>>>>  
>>>>> <mailto:>
>>>>>  
>>>>> <mailto:>>
>>>>>  wrote:
>>>>> 
>>>> Hi Everyone
>>>> 
>>>> It took a little longer than expected but ONOS is now up and 
>>>> running.
>>>> 
>>>> We also made a small change to the multi agent config file. 
>>>> Please refresh it (instructions here 
>>>> http://docs.perfsonar.net/multi_agent_config.html)
>>>> 
>>>> I currently have peerings from MAX, FIU, and Europe.  If you
>>>> need assistance with getting anything setup please let me
>>>> know.
>>>> 
>>>> Thanks A.J.
>>>> 
>>>> 
>>>> On 8/13/15 10:02 AM, Andrew Ragusa wrote:
>>>>>>> Hi Everyone
>>>>>>> 
>>>>>>> We are going to be restarting the ONOS/IP.SDN slice,
>>>>>>> and getting people connected.  This is going to be
>>>>>>> temporary for a demo next week.
>>>>>>> 
>>>>>>> Once we think we have the ONOS slice working we will
>>>>>>> send another email with the current peerings and see
>>>>>>> what we need to do to get everything working again.
>>>>>>> 
>>>>>>> If you have any concerns please let us know.
>>>>>>> 
>>>>>>> The goal is to have everything working by end of the
>>>>>>> day tomorrow.
>>>>>>> 
>>>>>>> Thanks A.J. Ragusa Software Engineering - GlobalNOC @ 
>>>>>>> Indiana University
>>>>>>> 
>>>> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG/MacGPG2 v2.0.19 (Darwin)
Comment: GPGTools - http://gpgtools.org

iEYEARECAAYFAlXM/voACgkQb9t+xjErh3RcRwCfSvins5cSi0NwWsUCSOFoCL2o
WEEAoLA3/kCJFa/NC1p31m1+CrVhgtI3
=nAcJ
-----END PGP SIGNATURE-----