DYNES-Deployments

[William Deigaard <>]

Ty,

Yes, this is the correct list.  Couple of clarifications:

   1) the DYNES interface is fixed now using the "reboot without optic 
inserted workaround," so it should show up now).
   2) the UTHSC link is down and not connected at this point.  We may 
re-introduce that soon.
   3) The "Local Use 10G" link is not connected currently, but will be once 
circuit creating works for us.

So, please proceed at your leisure with upgrading.  Thanks.




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

On Jul 5, 2013, at 12:58 PM, Ty Bell 
<>
 wrote:

> William,
> 
> Looking at the list of interfaces connected to the Rice S4810, it looks 
> like the only ones that are up and connected are to the FDT and IDC. I 
> wanted to check on this before upgrading the the switch since I'll need to 
> reload it a couple times. Am I clear to upgrade?
> 
> sw-rice>show interfaces description
> Interface                OK  Status     Protocol    Description
> TenGigabitEthernet 0/0   NO  up         down        'DYNES ION/WAN'
> TenGigabitEthernet 0/18  NO  up         down        '10GE interface (local 
> use)'
> TenGigabitEthernet 0/19  YES up         up          'fdt-rice 10GE eth0 
> interface'
> TenGigabitEthernet 0/20  YES up         up          'fdt-rice 1GE eth2 
> interface'
> TenGigabitEthernet 0/22  YES up         up          'fdt-rice 1GE eth3 
> interface'
> TenGigabitEthernet 0/24  YES up         up          'idc-rice 1GE 
> connection (eth1) for control-plane'
> TenGigabitEthernet 0/36  NO  up         down        'UTHSC 10GE link via 
> Travis St. Fiber'
> ManagementEthernet 0/0   YES up         up          Switch Management
> 
> --Ty
> 
> On Jul 3, 2013, at 3:56 PM, William Deigaard 
> <>
>  wrote:
> 
>> Brian,
>> 
>> Sounds good.  The console line is in place, and the switch password is 
>> still the default.
>> 
>> Thanks for the help.
>> 
>> 
>> -- 
>> William Deigaard  ^-^
>> ()
>>  (O O)
>> Go Owls!         ( v )
>> ------------------m-m--Director,
>> 713-348-5262 (o.)       Networking, Telecommunications & Data Centers
>> 713-487-7423 (gv)       Rice University
>> 
>> On Jul 3, 2013, at 1: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.
>>>> 
>>>> 
>>> 
>>> 
>>> 
> 
>