DYNES-Deployments

[Ty Bell <>]

You should now be able to ssh as the admin user using your private key. For 
example

ssh -i your.private.key -l admin some.ip.address

--Ty

On Aug 15, 2013, at 12:03 PM, Bahaa Araji 
<>
 wrote:

> Hi,
> I am sending the public key,if you can update the authorized key file.
> 
> Thanks.
> 
> 
> On Thu, Aug 15, 2013 at 10:39 AM, Ty Bell 
> <>
>  wrote:
> If you're not familiar with ssh public and private keys, please reference 
> this: http://en.wikipedia.org/wiki/Ssh-keygen. You need to provide the 
> contents of your .ssh/foo.pub file
> 
> --Ty
> 
> On Aug 15, 2013, at 11:28 AM, Ty Bell 
> <>
>  wrote:
> 
> > Please reply with the public keys of those requiring access and I'll 
> > update the authorized_keys files.
> >
> > --Ty
> >
> > On Aug 15, 2013, at 11:02 AM, "Gurkan, Deniz" 
> > <>
> >  wrote:
> >
> >> Ty,
> >>
> >> Harsha is a student of mine graduated long time ago.
> >> Is there any other way you can recommend us? Sorry for the inconvenience.
> >>
> >> Deniz
> >>
> >>
> >>
> >>
> >> On 8/14/13 1:08 PM, "Ty Bell" 
> >> <>
> >>  wrote:
> >>
> >>> There is one public key in the authorized_keys file for the admin user:
> >>> 
> >>>  . Are you familiar with this user? Is it possible
> >>> for you to contact them and request your public key be added?
> >>>
> >>> --Ty
> >>>
> >>> On Aug 14, 2013, at 1:27 PM, Bahaa Araji 
> >>> <>
> >>>  wrote:
> >>>
> >>>> Hi Ty,
> >>>>
> >>>> I could not ssh to the IDC server (129.7.46.17), i am getting the
> >>>> message below, please advise.
> >>>>
> >>>> Thanks,
> >>>> Bahaa Araji
> >>>> Research Assistant
> >>>> University of Houston
> >>>> <image.png>
> >>>>
> >>>>
> >>>>
> >>>> On Tue, Aug 13, 2013 at 4:41 PM, Ty Bell 
> >>>> <>
> >>>>  wrote:
> >>>> The admin user on the IDC host machine (168.7.170.198) and VM
> >>>> (168.7.170.200) contains public keys for the following:
> >>>> soren@soren
> >>>> 
> >>>> 
> >>>>
> >>>> If one of those users could ssh 
> >>>> ,
> >>>>  they'll find a
> >>>> file called pw with the passwords needed for your equipment.
> >>>>
> >>>> --Ty
> >>>>
> >>>> On Aug 13, 2013, at 11:57 AM, "Gurkan, Deniz" 
> >>>> <>
> >>>> wrote:
> >>>>
> >>>>> Ty,
> >>>>>
> >>>>> Is there any update on this request please?
> >>>>>
> >>>>> Thanks,
> >>>>> Deniz
> >>>>>
> >>>>>
> >>>>>
> >>>>> -----Original Message-----
> >>>>> From: William Deigaard 
> >>>>> [mailto:]
> >>>>> Sent: Thursday, August 08, 2013 6:59 PM
> >>>>> To: Jason Bothe
> >>>>> Cc: Ty Bell; Brian Cashman; Gurkan, Deniz; Chambers, Charles E;
> >>>> ;
> >>>>  Kumbi, Tesfaye; 
> >>>> ;
> >>>> David A. J. Ripley
> >>>>> Subject: Re: [dynes-deployments] Need some OSCARS/DYNES/<something>
> >>>> help...
> >>>>>
> >>>>> Ty,
> >>>>>
> >>>>> It looks like the vm has been replaced on the IDC, so I suspect we
> >>>> need to re-establish OSCARS login accounts.
> >>>>>
> >>>>> Do you have a username/password that we could use?  Or could you set
> >>>> it to the default so we can change it?
> >>>>>
> >>>>> If you aren't ready to have us poke, then just tell me to wait. :-)
> >>>>>
> >>>>> 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
> >>>>>
> >>>>> On Aug 7, 2013, at 9:54 AM, Jason Bothe 
> >>>>> <>
> >>>>>  wrote:
> >>>>>
> >>>>>> Excellent, thanks!
> >>>>>>
> >>>>>> Jason
> >>>>>>
> >>>>>>
> >>>>>> On 7, Aug 2013, at 9:51 AM, Ty Bell 
> >>>>>> <>
> >>>>>>  wrote:
> >>>>>>
> >>>>>>> Hi Jason,
> >>>>>>>
> >>>>>>> Yes, we've upgraded the firmware and the IDC. We're testing and
> >>>> verifying reliable circuit creation.
> >>>>>>>
> >>>>>>> --Ty
> >>>>>>>
> >>>>>>> On Aug 7, 2013, at 10:44 AM, Jason Bothe 
> >>>>>>> <>
> >>>>>>>  wrote:
> >>>>>>>
> >>>>>>>> Ty,
> >>>>>>>>
> >>>>>>>> Can you confirm whether or not you guys were successfully able to
> >>>> upgrade the firmware?
> >>>>>>>>
> >>>>>>>> Thanks,
> >>>>>>>>
> >>>>>>>> Jason
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> On 15, Jul 2013, at 3:31 PM, Jason Bothe 
> >>>>>>>> <>
> >>>>>>>>  wrote:
> >>>>>>>>
> >>>>>>>>> Ty
> >>>>>>>>>
> >>>>>>>>> Can you try now?  I reset the switch and the optic seems to be up.
> >>>>>>>>>
> >>>>>>>>> Thanks
> >>>>>>>>>
> >>>>>>>>> Jason
> >>>>>>>>>
> >>>>>>>>> Sent from my iPhone
> >>>>>>>>>
> >>>>>>>>> On Jul 15, 2013, at 14:19, Ty Bell 
> >>>>>>>>> <>
> >>>>>>>>>  wrote:
> >>>>>>>>>
> >>>>>>>>>> Hi William,
> >>>>>>>>>>
> >>>>>>>>>> Would it be possible to get Te0/0 on the Rice switch connected
> >>>> so we can try some circuits to LEARN?
> >>>>>>>>>>
> >>>>>>>>>> --Ty
> >>>>>>>>>>
> >>>>>>>>>> On Jul 8, 2013, at 1:19 PM, William Deigaard 
> >>>>>>>>>> <>
> >>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>>> 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.e
> >>>>>>>>>>>>>>> nd
> >>>>>>>>>>>>>>> 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/OSCAR
> >>>>>>>>>>>>>>> SNotify
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>>
> >>>>>>>>>>>>>>> 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.
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>
> >>>>
> >>>
> >
> 
> 
> <dynestest>

Attachment: signature.asc
Description: Message signed with OpenPGP using GPGMail