DYNES-Deployments

[Ty Bell <>]

Yea, I was able to reach the Rice s4810 from the IDC VM host on /dev/ttyS0, 
so console is all set.

--Ty

On Jul 3, 2013, at 2:22 PM, Brian Cashman 
<>
 wrote:

> William,
> 
> I think we can upgrade the firmware if we have console access. It
> appears that you have the switch console connected the IDC. I think that
> as long as we have the enable password for the switch, we're good. Ty
> can say for sure.
> 
> Brian
> 
> On 7/3/13 12:50 PM, William Deigaard wrote:
>> Brian,
>> 
>> The IP you listed is correct for the Rice IDC.  The vm running on it is at 
>> 168.7.170.200.
>> 
>> 
>> I continued to work on the issue after we sent the email below.  I believe 
>> most of that was caused by poor formulation of the src and dst sites in 
>> the OSCARS web interface.
>> 
>> When using the FDTAgent, I found that the most telling error was found in 
>> the /var/log/oscars/api.out file on the IDC VM:
>> 
>> ERROR ts=2013-07-02T10:43:38.794000Z 
>> event=OSCARSInternal-API.SubscribeManager05.getSubscription.end 
>> guid=dynes.rice.edu-V05-a15b14d6-4bae-42f2-9734-1456633934c1 
>> gri=dynes.rice.edu-319 errSeverity=MAJOR status=-1 msg="Problem writing 
>> SAAJ model to stream" 
>> url=https://learn-idc2.tx-learn.net:8443/axis2/services/OSCARSNotify 
>> 
>> 
>> I was planning on talking with the LEARN folks about the health and 
>> happiness of their IDC, but if we're planning on going to OESS sooner 
>> rather than later, I'll hold off on that.
>> 
>> 
>> And lastly, the Dell representative is willing to come to Rice to do the 
>> same firmware upgrade (to get to Openflow) that was already done at UofH.  
>> Should we arrange for that for you, or do you want to do it?
>> 
>> Thanks.
>> 
>> 
>