DYNES-Deployments

[Jorge Batista <>]

Brian,

Speaking of, Azher mentioned Caltech is ready. Is all between Caltech and some other site clear for testing?

Let me know as soon as any other sites are ready and I'll add them to the tests.

Thanks,
Jorge

On Aug 21, 2013 3:10 PM, "Brian Cashman" <> wrote:

Yes, your site has been upgraded. As I mentioned to Charles we're in the process of ramping up testing.

Thanks,
     Brian

On 8/21/13 2:12 PM, Brian Bockelman wrote:

Hi Brian,

Oddly enough, I was about to separately email you about the OESS / Bridge-PSS upgrade --

UNL has the S4810 in place, and would be interested in getting our site upgraded ASAP.

Thanks!

Brian

On Aug 21, 2013, at 12:18 PM, Brian Cashman <> wrote:

Charles,

At this time, we're still testing connectivity between sites. The only test we're running right now is between Tufts and the University of Florida (both directions). So, dynesfdt ping uf should work. The others are still being tested as I mentioned and we'll be adding more sites to the automated tests hopefully soon.

The thread below was specific to Rice and Houston, two sites that happened to have S4810 switches. A while back the DYNES-PIs decided to replace DRAGON in as many places as we could along with upgrading the OSCARS version from 0.5 to 0.6.

Sites with S4810 switches will have OESS software installed
Sites with 8024F switches (e.g., Tufts) will have the Bridge-PSS software installed

OESS and Bridge-PSS replace DRAGON. At Tufts, we've upgraded OSCARS to 0.6 and installed the Bridge-PSS. So, no DRAGON. I did happen to see that the VM running OSCARS and the Bridge-PSS is still named "tufts_vlsr_idcv6," which I think was the name it had originally when it was running DRAGON.

Glad to see you back into the fray.

     Brian

On 8/21/13 12:49 PM, Gray, Charles wrote:

I’ve been out of the DYNES fray this summer and focused on a physical reorg of our datacenter.  Having just started looking at DYNES again, I reread the deployment list emails and noticed this thread wondering if these circumstances were applicable to Tufts.  If so, I’d appreciate advice on how to articulate what I need to the list.

 

I’ve tried to DYNESFDT ping various sites with no success.  Could still be pilot error needing more education, but I noticed that DRAGON was also installed on Tufts’ IDC.

 

Regards,

Charles Gray

Senior Systems Administrator

Tufts Technology Services (TTS)

169 Holland Street

Somerville, MA 02144

(617) 627-5327 (w)

(617) 627-3307 (f)

it.tufts.edu

 

 

 

From: [] On Behalf Of Brian Cashman
Sent: Wednesday, July 03, 2013 11:50 AM
To:
Cc: William Deigaard; Jason Bothe; Deniz Gurkan; Charles E Chambers; ; Ty Bell
Subject: Re: [dynes-deployments] Need some OSCARS/DYNES/<something> help...

 

William and Deniz:

I didn't realize until today that both of your sites, Rice and Houston, have an S4810 switch. Rather than spend too much time on this particular issue let me suggest a hopefully better alternative. We've been having problems with DRAGON setting up circuits and DRAGON, at least the DRAGON we installed on your IDCs, supports that switch. What I'd like to do is instead install OESS software and if it's not on there already, a version of the switch firmware that supports OpenFlow. The OESS software will include an updated version of OSCARS and replaces DRAGON with configuring the switch using OpenFlow. If that's acceptable to you please let me know. Ty Bell, cc'd here, would be the one doing the installation.

The IDC I have for Rice is 168.7.170.198. Does Houston have a separate IDC?

Thanks,
     Brian

On 7/2/13 12:43 PM, William Deigaard wrote:

Hello,

 

At Rice (and UofH), it appears, we cannot seem to create a circuit reservation on DYNES

 

Perhaps we broke something.  Perhaps we're doing something wrong.  Perhaps something never worked.  We can't quite tell.

 

When we try to create a circuit using the OSCARS interface, we get errors like the following:

 

 

Errors on Oscars console for circuit from Rice to LEARN:

 

 

 

 

Errors in Oscars ConnectivityPCE.log

 

level=INFO ts=2013-07-02T04:02:16.598000Z event=net.es.oscars.pce.Connectivity.pceCreate.start guid=dynes.rice.edu-WBUI-a92dba30-6c55-41b3-9744-5c4be17f7da6 gri=dynes.rice.edu-307 
level=INFO ts=2013-07-02T04:02:16.598000Z event=net.es.oscars.pce.Connectivity.pceCreate.end guid=dynes.rice.edu-WBUI-a92dba30-6c55-41b3-9744-5c4be17f7da6 gri=dynes.rice.edu-307 status=0 
level=INFO ts=2013-07-02T04:02:16.869000Z event=net.es.oscars.pce.Connectivity.invoke-client.start guid=dynes.rice.edu-WBUI-a92dba30-6c55-41b3-9744-5c4be17f7da6 gri=dynes.rice.edu-307 msg=getTopology url="https://localhost:9019/topoBridge 
level=WARN ts=2013-07-02T04:02:18.437000Z event=net.es.oscars.pce.Connectivity.invoke-client.end guid=dynes.rice.edu-WBUI-a92dba30-6c55-41b3-9744-5c4be17f7da6 gri=dynes.rice.edu-307 errSeverity=MINOR status=-1 msg="OSCARSSoapService.invoke:Exception connecting to getTopology on https://localhost:9019/topoBridge Message is: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint." 
level=ERROR ts=2013-07-02T04:02:18.438000Z event=net.es.oscars.pce.Connectivity.calculatePath.end guid=dynes.rice.edu-WBUI-a92dba30-6c55-41b3-9744-5c4be17f7da6 gri=dynes.rice.edu-307 errSeverity=MAJOR status=-1 msg="Error from topoBridge: OSCARSSoapService.invoke:Exception connecting to getTopology on https://localhost:9019/topoBridge Message is: A SOAP 1.2 message is not valid when sent to a SOAP 1.1 only endpoint." 
level=INFO ts=2013-07-02T04:02:18.438000Z event=net.es.oscars.pce.Connectivity.invoke-client.start guid=dynes.rice.edu-WBUI-a92dba30-6c55-41b3-9744-5c4be17f7da6 gri=dynes.rice.edu-307 msg=PCEReply url="https://localhost:10000/OSCARS/PCERuntimeService 

In particular, we've noticed that we can't seem to make a basic connection to the topoBridge:

[root@vm1-idc-rice oscars]# wget https://localhost:9019/topoBridge

--2013-07-02 16:34:47--  https://localhost:9019/topoBridge
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:9019... connected.
OpenSSL: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate
Unable to establish SSL connection.

 

 

Any suggestions from folks out there?

 

Thanks.

 

 

-- 
William Deigaard  ^-^
() (O O)
Go Owls!         ( v )
------------------m-m--Director,
713-348-5262 (o) Networking, Telecommunications & Data Centers
713-487-7423 (m) Rice University