oess-users - Re: [oess-users] Circuit Fail: OSCARS Unable to find IDC ?

Subject: oess-users

List archive

Re: [oess-users] Circuit Fail: OSCARS Unable to find IDC ?

From: AJ Ragusa <>
To:
Subject: Re: [oess-users] Circuit Fail: OSCARS Unable to find IDC ?
Date: Fri, 29 May 2015 10:04:49 -0400

Hi Azher

Can you check the version of OESS DB you have.

in the OESS database

select * from oess_version

I'm guessing that in a previous upgrade you missed the upgrade script, it shouldn't be a big deal we just need to find the version of the schema you are running and then run that upgrade script.

A.J.

On 5/29/15 9:58 AM, Azher Mughal wrote:
> For sure, it was 1.1.5. Below is the capture from console:
>
>
>
> [root@idc-v6 oess-1.1.6]# yum install *.rpm
> Loaded plugins: security
> Setting up Install Process
> Examining nddi-tiles-0.0.1-1.el6.noarch.rpm: nddi-tiles-0.0.1-1.el6.noarch
> nddi-tiles-0.0.1-1.el6.noarch.rpm: does not update installed package.
> Examining nox-0.10.6-1.el6.x86_64.rpm: nox-0.10.6-1.el6.x86_64
> Marking nox-0.10.6-1.el6.x86_64.rpm as an update to nox-0.10.5-2.el6.x86_64
> Examining oess-core-1.1.6-1.el6.noarch.rpm: oess-core-1.1.6-1.el6.noarch
> Marking oess-core-1.1.6-1.el6.noarch.rpm as an update to
> oess-core-1.1.5-1.el6.noarch
> Examining oess-frontend-1.1.6-1.el6.noarch.rpm:
> oess-frontend-1.1.6-1.el6.noarch
> Marking oess-frontend-1.1.6-1.el6.noarch.rpm as an update to
> oess-frontend-1.1.5-1.el6.noarch
> Examining perl-AnyEvent-7.07-1.noarch.rpm: perl-AnyEvent-7.07-1.noarch
> perl-AnyEvent-7.07-1.noarch.rpm: does not update installed package.
> Examining perl-AnyEvent-DBus-0.31-1.noarch.rpm:
> perl-AnyEvent-DBus-0.31-1.noarch
> perl-AnyEvent-DBus-0.31-1.noarch.rpm: does not update installed package.
> Examining perl-AnyEvent-Fork-1.2-1.noarch.rpm:
> perl-AnyEvent-Fork-1.2-1.noarch
> perl-AnyEvent-Fork-1.2-1.noarch.rpm: does not update installed package.
> Examining perl-AnyEvent-Fork-RPC-1.21-1.noarch.rpm:
> perl-AnyEvent-Fork-RPC-1.21-1.noarch
> perl-AnyEvent-Fork-RPC-1.21-1.noarch.rpm: does not update installed package.
> Examining perl-HTML-FormatText-WithLinks-0.14-1.noarch.rpm:
> perl-HTML-FormatText-WithLinks-0.14-1.noarch
> perl-HTML-FormatText-WithLinks-0.14-1.noarch.rpm: does not update
> installed package.
> Examining perl-IO-AIO-4.18-1.x86_64.rpm: perl-IO-AIO-4.18-1.x86_64
> perl-IO-AIO-4.18-1.x86_64.rpm: does not update installed package.
> Examining perl-IO-FDPass-1.0-1.x86_64.rpm: perl-IO-FDPass-1.0-1.x86_64
> perl-IO-FDPass-1.0-1.x86_64.rpm: does not update installed package.
> Examining perl-MIME-Lite-TT-HTML-0.04-1.noarch.rpm:
> perl-MIME-Lite-TT-HTML-0.04-1.noarch
> perl-MIME-Lite-TT-HTML-0.04-1.noarch.rpm: does not update installed package.
> Examining perl-OESS-1.1.6-1.noarch.rpm: perl-OESS-1.1.6-1.noarch
> Marking perl-OESS-1.1.6-1.noarch.rpm as an update to
> perl-OESS-1.1.5-8.noarch
> Examining perl-OSCARS-Client-1.1.6-1.noarch.rpm:
> perl-OSCARS-Client-1.1.6-1.noarch
> Marking perl-OSCARS-Client-1.1.6-1.noarch.rpm as an update to
> perl-OSCARS-Client-1.1.5-1.noarch
> Examining perl-Proc-FastSpawn-1.2-1.x86_64.rpm:
> perl-Proc-FastSpawn-1.2-1.x86_64
> perl-Proc-FastSpawn-1.2-1.x86_64.rpm: does not update installed package.
> Examining perl-SOAP-Data-Builder-0.9-1.noarch.rpm:
> perl-SOAP-Data-Builder-0.9-1.noarch
> perl-SOAP-Data-Builder-0.9-1.noarch.rpm: does not update installed package.
> Examining yui2-2.9.0-1.rh6_1.x86_64.rpm: yui2-2.9.0-1.rh6_1.x86_64
> yui2-2.9.0-1.rh6_1.x86_64.rpm: does not update installed package.
> Resolving Dependencies
> --> Running transaction check
> ---> Package nox.x86_64 0:0.10.5-2.el6 will be updated
> ---> Package nox.x86_64 0:0.10.6-1.el6 will be an update
> ---> Package oess-core.noarch 0:1.1.5-1.el6 will be updated
> ---> Package oess-core.noarch 0:1.1.6-1.el6 will be an update
> ---> Package oess-frontend.noarch 0:1.1.5-1.el6 will be updated
> ---> Package oess-frontend.noarch 0:1.1.6-1.el6 will be an update
> ---> Package perl-OESS.noarch 0:1.1.5-8 will be updated
> ---> Package perl-OESS.noarch 0:1.1.6-1 will be an update
> ---> Package perl-OSCARS-Client.noarch 0:1.1.5-1 will be updated
> ---> Package perl-OSCARS-Client.noarch 0:1.1.6-1 will be an update
> --> Finished Dependency Resolution
>
> Dependencies Resolved
>
> ==========================================================================================================================
> Package                      Arch             Version
> Repository                                    Size
> ==========================================================================================================================
> Updating:
> nox                          x86_64           0.10.6-1.el6
> /nox-0.10.6-1.el6.x86_64                     107 M
> oess-core                    noarch           1.1.6-1.el6
> /oess-core-1.1.6-1.el6.noarch                185 k
> oess-frontend                noarch           1.1.6-1.el6
> /oess-frontend-1.1.6-1.el6.noarch             13 M
> perl-OESS                    noarch           1.1.6-1
> /perl-OESS-1.1.6-1.noarch                    681 k
> perl-OSCARS-Client           noarch           1.1.6-1
> /perl-OSCARS-Client-1.1.6-1.noarch            51 k
>
> Transaction Summary
> ==========================================================================================================================
> Upgrade       5 Package(s)
>
> Total size: 121 M
> Is this ok [y/N]: y
> Downloading Packages:
> Running rpm_check_debug
> Running Transaction Test
> Transaction Test Succeeded
> Running Transaction
> Warning: RPMDB altered outside of yum.
>   Updating   :
> perl-OESS-1.1.6-1.noarch
> 1/10
>   Updating   :
> nox-0.10.6-1.el6.x86_64
> 2/10
> mkdir: cannot create directory `/var/run/nox': File exists
>   Updating   :
> oess-core-1.1.6-1.el6.noarch
> 3/10
>   Updating   :
> perl-OSCARS-Client-1.1.6-1.noarch
> 4/10
>   Updating   :
> oess-frontend-1.1.6-1.el6.noarch
> 5/10
>   Cleanup    :
> oess-frontend-1.1.5-1.el6.noarch
> 6/10
>   Cleanup    :
> oess-core-1.1.5-1.el6.noarch
> 7/10
>   Cleanup    :
> perl-OSCARS-Client-1.1.5-1.noarch
> 8/10
>   Cleanup    :
> perl-OESS-1.1.5-8.noarch
> 9/10
>   Cleanup    :
> nox-0.10.5-2.el6.x86_64
> 10/10
>   Verifying :
> perl-OESS-1.1.6-1.noarch
> 1/10
>   Verifying :
> nox-0.10.6-1.el6.x86_64
> 2/10
>   Verifying :
> oess-frontend-1.1.6-1.el6.noarch
> 3/10
>   Verifying :
> oess-core-1.1.6-1.el6.noarch
> 4/10
>   Verifying :
> perl-OSCARS-Client-1.1.6-1.noarch
> 5/10
>   Verifying :
> oess-core-1.1.5-1.el6.noarch
> 6/10
>   Verifying :
> perl-OSCARS-Client-1.1.5-1.noarch
> 7/10
>   Verifying :
> oess-frontend-1.1.5-1.el6.noarch
> 8/10
>   Verifying :
> nox-0.10.5-2.el6.x86_64
> 9/10
>   Verifying :
> perl-OESS-1.1.5-8.noarch
> 10/10
>
> Updated:
>   nox.x86_64 0:0.10.6-1.el6         oess-core.noarch
> 0:1.1.6-1.el6             oess-frontend.noarch 0:1.1.6-1.el6
>   perl-OESS.noarch 0:1.1.6-1        perl-OSCARS-Client.noarch
> 0:1.1.6-1
>
> Complete!
> [root@idc-v6 oess-1.1.6]#
>
> On 5/29/2015 6:55 AM, Andrew Ragusa wrote:

Hi Azher

What version of OESS were you running previously? I am guessing that
you either missed an upgrade script in a previous upgrade, or your
previous version was not 1.1.5.

Thanks
A.J.

On 5/29/15 9:49 AM, Azher Mughal wrote:
>>> Hi AJ,
>>>
>>> I tried the following steps after updating rpms. But the script is
>>> complaining about the version. Currently I was on 1.1.5. Any
>>> suggestions ?
>>>
>>> Thanks -Azher
>>>
>>> #cd perl-OESS-1.1.6/share/upgrade/
>>>
>>> [root@idc-v6 upgrade]# ls oess-1.0.10-1.0.11 oess-1.0.2-1.0.3
>>> oess-1.0.5-1.0.6 oess-1.0.8-1.0.9   oess-1.1.1-1.1.2
>>> oess-1.1.4-1.1.5 oess-1.0.11-1.0.12 oess-1.0.3-1.0.4
>>> oess-1.0.6-1.0.7 oess-1.0.9-1.0.10 oess-1.1.2-1.1.3
>>> oess-1.1.5-1.1.6 oess-1.0.12-1.1.0   oess-1.0.4-1.0.5
>>> oess-1.0.7-1.0.8 oess-1.1.0-1.1.1   oess-1.1.3-1.1.4
>>>
>>> [root@idc-v6 upgrade]# perl oess-1.1.5-1.1.6 "my" variable $rows
>>> masks earlier declaration in same scope at oess-1.1.5-1.1.6 line
>>> 100.
>>> *******************************************************************
>>>
>>>
*********             OESS DB UPGRADE           ************
>>> *******************************************************************
>>>
>>>
********* This will upgrade from 1.1.5 to 1.1.6 **********
>>> ********* of the OESS DB any other version will not work
>>> ************ Do you wish to continue [y/n]: y Wrong version of OESS
>>> DB This script only upgrades from version 1.1.5 to 1.1.6
>>>
>>>
>>> On 5/27/2015 7:54 AM, Andrew Ragusa wrote:
>>>> Hi Azher
>>>>
>>>> I hope to send out the OESS 1.1.6 documentation, and change log
>>>> to the list later on today.
>>>>
>>>> This ticket is not included in 1.1.6, it came in too late in the
>>>> development cycle to make it into the release.
>>>>
>>>> Is there a date you need this by?
>>>>
>>>> Thanks A.J.
>>>>
>>>>
>>>> On 5/27/15 9:39 AM, Azher Mughal wrote:
>>>>> Hi AJ,
>>>>> Can you please update if OESS release 1.1.6 will include this
>>>>> ticket ?
>>>>> Thanks -Azher
>>>>> On 5/1/2015 7:25 AM, Andrew Ragusa wrote:
>>>>>> Ok ticket 11044 is tracking that feature, it is currently
>>>>>> queued for a future OESS release.
>>>>>>
>>>>>> Thanks A.J.
>>>>>>
>>>>>>
>>>>>> On 5/1/15 10:19 AM, Azher Mughal wrote:
>>>>>>> Hi AJ,
>>>>>>> On 5/1/2015 7:13 AM, Andrew Ragusa wrote: Hi Azher
>>>>>>> I'm not sure about what you are asking. Are you asking
>>>>>>> for the AL2S topology to be changed.
>>>>>>>> No.
>>>>>>> Or are you asking for the ability to tune the
>>>>>>> trafficEngineeringMetric value for each remoteLink in an
>>>>>>> OESS instance?
>>>>>>>> Yes, Tune the traffic engineering in the site OESS
>>>>>>>> instance so that OSCARS will take that path
>>>>>>>> specifically.
>>>>>>> I can put a ticket in for the OESS feature if you want.
>>>>>>>> That will be great.
>>>>>>>> Thanks -Azher
>>>>>>
>>>>>>> Thanks A.J.
>>>>>>
>>>>>>> On 4/30/15 5:57 PM, Azher Mughal wrote:
>>>>>>>>>> Hello,
>>>>>>>>>>
>>>>>>>>>> Caltech and UMich have multiple peerings (AL2S and
>>>>>>>>>> ESnet). Both domains are getting error "Unable to
>>>>>>>>>> find IDC", details below. When any other domain
>>>>>>>>>> creates a path to them, path works. ESnet is only
>>>>>>>>>> used for NSI aggregator.
>>>>>>>>>>
>>>>>>>>>> Is there a way in OESS to change the traffic
>>>>>>>>>> engineering value so that AL2S is always prefferred
>>>>>>>>>> ?
>>>>>>>>>>
>>>>>>>>>> E.g. Caltech:
>>>>>>>>>> https://ndb7.net.internet2.edu/TopologyViewer/?domain=caltech.e
du
&t
>>>> s_i
>>>>>> nstance=http%3A%2F%2Fdcn-ts.internet2.edu%3A8012%2FperfSONAR_PS%2Fs
er
vic
>>>>>>
>>>>> es%2Ftopology
>>>>>>>>>> -Azher
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> -------- Forwarded Message -------- Subject:     Re:
>>>>>>>>>> [oscars-support] Circuit Fail: Unable to find IDC ?
>>>>>>>>>> Date: Tue, 28 Apr 2015 12:08:53 -0400 From:
>>>>>>>>>> Andrew Lake Reply-To:
>>>>>>>>>> To:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Hi Azher,
>>>>>>>>>>
>>>>>>>>>> I see that UMich has a peering with al2s and es.net
>>>>>>>>>> <http://es.net>. I wonder if it’s preferring the
>>>>>>>>>> es.net <http://es.net> path, and there is no entry in
>>>>>>>>>> the lookup module for that domain so it complains it
>>>>>>>>>> can’t find the IDC. You could try running
>>>>>>>>>> oscars-idcadd to point at es.net <http://es.net> or
>>>>>>>>>> specifying al2s in the middle of the path so it uses
>>>>>>>>>> that instead.
>>>>>>>>>>
>>>>>>>>>> Andy
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>>> On Apr 28, 2015, at 10:20 AM, Azher Mughal
>>>>>>>>>>> <
>>>>>>>>>>> > wrote:
>>>>>>>>>>>
>>>>>>>>>>> Andy, Any suggestions ?
>>>>>>>>>>>
>>>>>>>>>>> Thanks -Azher
>>>>>>>>>>>
>>>>>>>>>>> On 4/27/2015 9:08 AM, Azher Mughal wrote:
>>>>>>>>>>>> Hi Andy,
>>>>>>>>>>>>
>>>>>>>>>>>> I have the following in the IDC domains list.
>>>>>>>>>>>> Both of these domains talk with ESnet aggregator
>>>>>>>>>>>> using the NSI aggregator.
>>>>>>>>>>>>
>>>>>>>>>>>> Caltech:
>>>>>>>>>>>>
>>>>>>>>>>>> [root@idc-v6 oscars]#
>>>>>>>>>>>> /opt/oscars/lookup/bin/oscars-idclist Loading
>>>>>>>>>>>> manifest from
>>>>>>>>>>>> /etc/oscars/LookupService/conf/manifest.yaml
>>>>>>>>>>>>
>>>>>>>>>>>> ID: 2 Type: IDC Expiration: NEVER Protocols:
>>>>>>>>>>>> Type: http://oscars.es.net/OSCARS/06 Location:
>>>>>>>>>>>> https://al2s.net.internet2.edu:9001/OSCARS
>>>>>>>>>>>> Relationships: [controls]
>>>>>>>>>>>> urn:ogf:network:domain=al2s.net.internet2.edu
>>>>>>>>>>>> <http://al2s.net.internet2.edu>
>>>>>>>>>>>>
>>>>>>>>>>>> UMich: [root@oess ~]#
>>>>>>>>>>>> /opt/oscars/lookup/bin/oscars-idclist Loading
>>>>>>>>>>>> manifest from
>>>>>>>>>>>> /etc/oscars/LookupService/conf/manifest.yaml
>>>>>>>>>>>>
>>>>>>>>>>>> ID: 3 Type: IDC Expiration: NEVER Protocols:
>>>>>>>>>>>> Type: http://oscars.es.net/OSCARS/06 Location:
>>>>>>>>>>>> https://al2s.net.internet2.edu:9001/OSCARS
>>>>>>>>>>>> Relationships: [controls]
>>>>>>>>>>>> urn:ogf:network:domain=al2s.net.internet2.edu
>>>>>>>>>>>> <http://al2s.net.internet2.edu>
>>>>>>>>>>>>
>>>>>>>>>>>> Thanks -Azher
>>>>>>>>>>>>
>>>>>>>>>>>> On 4/27/2015 8:04 AM, Andrew Lake wrote:
>>>>>>>>>>>>> Hi Azher,
>>>>>>>>>>>>>
>>>>>>>>>>>>> I’ve been out the past couple weeks, so sorry
>>>>>>>>>>>>> for the delay. Did you find your answer to
>>>>>>>>>>>>> this? It is usually caused because a domain’s
>>>>>>>>>>>>> IDC has not been added to the OSCARS lookup
>>>>>>>>>>>>> module. I can help with commands if this is
>>>>>>>>>>>>> still an issue.
>>>>>>>>>>>>>
>>>>>>>>>>>>> Thanks, Andy
>>>>>>>>>>>>>
>>>>>>>>>>>>>
>>>>>>>>>>>>>> On Apr 14, 2015, at 12:24 PM, Azher Mughal
>>>>>>>>>>>>>> <
>>>>>>>>>>>>>> > wrote:
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Hi,
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> What caused this error ? I restarted OSCARS
>>>>>>>>>>>>>> and then kicked a new reservation, but same
>>>>>>>>>>>>>> error.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> OSCARSService.log: WARN
>>>>>>>>>>>>>> ts=2015-04-14T03:07:06.165000Z
>>>>>>>>>>>>>> event=OSCARSInternal-API.invoke-client.end
>>>>>>>>>>>>>> guid=oess.dcn.umnet.umich.edu
>>>>>>>>>>>>>> <http://oess.dcn.umnet.umich.edu>-V05-f1b776c9-a3f5-4134-b1
2c
-f
>>>> 0a6
>>>>>> 946c00a3
>>>>>>> gri=oess.dcn.umnet.umich.edu
>>>>>>> <http://oess.dcn.umnet.umich.edu>-2745
>>>>>>>>>>>>>> errSeverity=MINOR status=-1
>>>>>>>>>>>>>> msg="OSCARSSoapService.invoke:Exception
>>>>>>>>>>>>>> connecting to lookup on
>>>>>>>>>>>>>> https://localhost:9014/lookup Message is:
>>>>>>>>>>>>>> Unable to find IDC"
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Since this is localhost, so iptables should
>>>>>>>>>>>>>> not be an issue. I have the following in the
>>>>>>>>>>>>>> iptables config.
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> -A INPUT -i lo -j ACCEPT
>>>>>>>>>>>>>>
>>>>>>>>>>>>>> Thanks -Azher
>>>>>>>>>>>>>>
>>>>>>>>>> -- This message has been scanned for viruses and
>>>>>>>>>> dangerous content by *MailScanner*
>>>>>>>>>> <http://www.mailscanner.info/>, and is believed to
>>>>>>>>>> be clean.
>>>>>>>>>>
>>>>
>>>>
>>>

Re: [oess-users] Circuit Fail: OSCARS Unable to find IDC ?, (continued)

List archive

Re: [oess-users] Circuit Fail: OSCARS Unable to find IDC ?