August 2014 - Admins - mailman3.cels.anl.gov

[JLSE-Admins] authentication failure
by Sameer Shende 25 Aug '14

25 Aug '14

Hi, I am trying to login to JLSE systems and I get: % ssh login.jlse.anl.gov The authenticity of host 'login.jlse.anl.gov (140.221.69.21)' can't be established. RSA key fingerprint is 1e:9e:d7:15:9c:7f:8d:5a:c6:4f:9e:45:bf:17:3a:7c. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'login.jlse.anl.gov,140.221.69.21' (RSA) to the list of known hosts. Saving password to keychain failed Identity added: /Users/sameer/.ssh/id_rsa (/Users/sameer/.ssh/id_rsa) --------------------------------------------------------------------------- Notice to Users This is a Federal computer system and is the property of the United States Government. It is for authorized use only. Users (authorized or unauthorized) have no explicit or implicit expectation of privacy. Any or all uses of this system and all files on this system may be intercepted, monitored, recorded, copied, audited, inspected, and disclosed to authorized site, Department of Energy, and law enforcement personnel, as well as authorized officials of other agencies, both domestic and foreign. By using this system, the user consents to such interception, monitoring, recording, copying, auditing, inspection, and disclosure at the discretion of authorized site or Department of Energy personnel. Unauthorized or improper use of this system may result in administrative disciplinary action and civil and criminal penalties. By continuing to use this system you indicate your awareness of and consent to these terms and conditions of use. LOG OFF IMMEDIATELY if you do not agree to the conditions stated in this warning. ---------------------------------------------------------------------------- Password: Received disconnect from 140.221.69.21: 2: Too many authentication failures for sameer Would you please reset this? Thanks! - Sameer

1 0

[JLSE-Admins] [Fail2Ban] SSH: banned 210.157.22.18 on
by Fail2Ban 21 Aug '14

21 Aug '14

The IP 210.157.22.18 has just been banned by Fail2Ban after 18 attempts against SSH. Latest lines containing IP:210.157.22.18 in /var/log/syslog/sshd.log Aug 22 03:56:39 ftlogin1 sshd[5935]: Invalid user admin from 210.157.22.18 Aug 22 03:56:40 ftlogin1 sshd[5938]: Postponed keyboard-interactive for invalid user admin from 210.157.22.18 port 56996 ssh2 Aug 22 03:56:41 ftlogin1 sshd[5935]: error: PAM: User not known to the underlying authentication module for illegal user admin from 210.157.22.18 Aug 22 03:56:41 ftlogin1 sshd[5935]: Failed keyboard-interactive/pam for invalid user admin from 210.157.22.18 port 56996 ssh2 Aug 22 03:56:42 ftlogin1 sshd[5938]: Received disconnect from 210.157.22.18: 11: Aug 22 03:56:42 ftlogin1 sshd[5940]: Address 210.157.22.18 maps to users134.phy.lolipop.jp, but this does not map back to the address - POSSIBLE BREAK-IN ATTEMPT! Aug 22 03:56:42 ftlogin1 sshd[5940]: Invalid user admin from 210.157.22.18 Aug 22 03:56:43 ftlogin1 sshd[5943]: Postponed keyboard-interactive for invalid user admin from 210.157.22.18 port 57039 ssh2 Aug 22 03:56:44 ftlogin1 sshd[5940]: error: PAM: User not known to the underlying authentication module for illegal user admin from 210.157.22.18 Aug 22 03:56:44 ftlogin1 sshd[5940]: Failed keyboard-interactive/pam for invalid user admin from 210.157.22.18 port 57039 ssh2 - Fail2ban on

1 0

Re: [JLSE-Admins] AMD Seattle
by Kazutomo Yoshii 21 Aug '14

21 Aug '14

Yes, we're contacting with them about Seattle. that's why we're working on some NDA / agreement stuff. In my understanding, Seattle is expected to be available in the end of this year. I'll try to get some evaluation boards. - kaz On 08/21/2014 04:01 PM, Kalyan Kumaran wrote: > Has anyone contacted AMD about getting the ARM64 Opteron? > > -Kumar > _______________________________________________ > Admins mailing list > Admins(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/admins

1 0

[JLSE-Admins] AMD Seattle
by Kalyan Kumaran 21 Aug '14

21 Aug '14

Has anyone contacted AMD about getting the ARM64 Opteron? -Kumar

1 0

Re: [JLSE-Admins] Seamicro Evaluation
by Allen, Benjamin S. 20 Aug '14

20 Aug '14

Yes. Also from talking with Scott they're also looking for help to evaluate the hardware. Hence my note that I'd be able to lend a hand in baseline benchmarking (IOR, iperf, etc), evaluating how provisioning works, etc. If we want to run application benchmarks on it, I'd want some time from Kumar's folks. Assuming someone on his team is interested. Scott, Dan and Ryan are interested is evaluating it for OpenStack use. Ben On Aug 20, 2014, at 11:27 AM, Rajeev Thakur <thakur(a)mcs.anl.gov> wrote: > Are they planning to get it and just want JLSE to host it? > > Rajeev > > > On Aug 19, 2014, at 5:30 PM, "Allen, Benjamin S." <bsallen(a)alcf.anl.gov> wrote: > >> I'm interested in hosting this, and have chatted with Scott about the eval. I can help out with installing, evaluating the systems administration side of the hardware, provisioning, baseline benchmarking, etc. >> >> Ben >> >> On Aug 19, 2014, at 5:15 PM, Kalyan Kumaran <kumaran(a)anl.gov> wrote: >> >>> >>> >>> Begin forwarded message: >>> >>>> From: "Murphy-Olson, Daniel E." <dolson(a)mcs.anl.gov> >>>> Subject: Seamicro Evaluation >>>> Date: August 19, 2014 at 5:08:28 PM CDT >>>> To: "Thakur, Rajeev" <thakur(a)mcs.anl.gov>, "Kumaran, Kalyanasundaram" <kumaran(a)alcf.anl.gov> >>>> >>>> Hi Rajeev and Kumar, >>>> >>>> The Magellan infrastructure team, Scott Devoid, Ryan Aydelott and I have been looking into several different hardware options that could be used as building blocks for Magellan's next refresh cycle. One interesting option is from Seamicro, currently part of AMD. We're interested in working with JLSE to evaluate the Seamicro hardware. >>>> >>>> Here is some more information regarding the machine we're interested in: >>>> http://www.seamicro.com/sm15000 >>>> http://www.seamicro.com/sites/default/files/SM_TO02_64_v2%205.pdf >>>> >>>> The primary areas we'd like to evaluate are: >>>> Internal torus network scalability >>>> How the system deals with changes in storage and network utilization on the fabric >>>> How well the system integrates with the Openstack control plane >>>> Serviceability of the components when operating under Openstack >>>> Compute performance under Openstack >>>> >>>> While we're primarily interested in the cloud computing capabilities, this platform may have HPC capabilities as well. >>>> >>>> Currently we have an NDA addendum we've received from AMD for this, but we don't yet have an evaluation agreement. >>>> >>>> Would you be interested in working with us on this? If so, how do we move forward? >>>> >>>> Thanks, >>>> Dan >>>> >>>> >>>> >>>> >>>> >>> >>> _______________________________________________ >>> Admins mailing list >>> Admins(a)lists.jlse.anl.gov >>> https://lists.jlse.anl.gov/mailman/listinfo/admins >> >> _______________________________________________ >> Admins mailing list >> Admins(a)lists.jlse.anl.gov >> https://lists.jlse.anl.gov/mailman/listinfo/admins >

1 0

Re: [JLSE-Admins] Seamicro Evaluation
by Rajeev Thakur 20 Aug '14

20 Aug '14

Are they planning to get it and just want JLSE to host it? Rajeev On Aug 19, 2014, at 5:30 PM, "Allen, Benjamin S." <bsallen(a)alcf.anl.gov> wrote: > I'm interested in hosting this, and have chatted with Scott about the eval. I can help out with installing, evaluating the systems administration side of the hardware, provisioning, baseline benchmarking, etc. > > Ben > > On Aug 19, 2014, at 5:15 PM, Kalyan Kumaran <kumaran(a)anl.gov> wrote: > >> >> >> Begin forwarded message: >> >>> From: "Murphy-Olson, Daniel E." <dolson(a)mcs.anl.gov> >>> Subject: Seamicro Evaluation >>> Date: August 19, 2014 at 5:08:28 PM CDT >>> To: "Thakur, Rajeev" <thakur(a)mcs.anl.gov>, "Kumaran, Kalyanasundaram" <kumaran(a)alcf.anl.gov> >>> >>> Hi Rajeev and Kumar, >>> >>> The Magellan infrastructure team, Scott Devoid, Ryan Aydelott and I have been looking into several different hardware options that could be used as building blocks for Magellan's next refresh cycle. One interesting option is from Seamicro, currently part of AMD. We're interested in working with JLSE to evaluate the Seamicro hardware. >>> >>> Here is some more information regarding the machine we're interested in: >>> http://www.seamicro.com/sm15000 >>> http://www.seamicro.com/sites/default/files/SM_TO02_64_v2%205.pdf >>> >>> The primary areas we'd like to evaluate are: >>> Internal torus network scalability >>> How the system deals with changes in storage and network utilization on the fabric >>> How well the system integrates with the Openstack control plane >>> Serviceability of the components when operating under Openstack >>> Compute performance under Openstack >>> >>> While we're primarily interested in the cloud computing capabilities, this platform may have HPC capabilities as well. >>> >>> Currently we have an NDA addendum we've received from AMD for this, but we don't yet have an evaluation agreement. >>> >>> Would you be interested in working with us on this? If so, how do we move forward? >>> >>> Thanks, >>> Dan >>> >>> >>> >>> >>> >> >> _______________________________________________ >> Admins mailing list >> Admins(a)lists.jlse.anl.gov >> https://lists.jlse.anl.gov/mailman/listinfo/admins > > _______________________________________________ > Admins mailing list > Admins(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/admins

1 0

Re: [JLSE-Admins] Access to Argonne test node
by Chase Qishi Wu (qishiwu) 20 Aug '14

20 Aug '14

Ben, Thanks for the clarification. Chase On 8/20/14, 11:17 AM, "Allen, Benjamin S." <bsallen(a)alcf.anl.gov> wrote: >Hi Chase, > >JLSE (Joint Laboratory for System Evaluation, JLSE replaces Future Tech >(FT)), doesn't allow password authentication, unless you're using an ALCF >two-factor cyrptocard. Our primary means of authentication is SSH >public/private keys. You can add a public key via your account on >https://accounts.jlse.anl.gov under "Credentials". Once you've done this >please allow about 15 minutes and attempt to use your private key to ssh >to login.jlse.anl.gov. Note the legacy hostname ft.alcf.anl.gov is just a >CNAME to login.jlse.anl.gov. > >Please let me know if you run into any issues with this. > >Ben > >On Aug 19, 2014, at 4:04 PM, Chase Qishi Wu (qishiwu) ><qishiwu(a)memphis.edu> wrote: > >> Dear sir/madam, >> >> I was not able to log onto ft.alcf.anl.gov with my username and >>password. Could you please help reset my password? >> >> Thanks, >> Chase >> >> From: Raj Kettimuthu <kettimut(a)anl.gov> >> Date: Tuesday, August 19, 2014 at 3:59 PM >> To: "Chase Qishi Wu (qishiwu)" <qishiwu(a)memphis.edu> >> Subject: Re: Access to Argonne test node >> >> Can you email admins(a)jlse.anl.gov about this? >> >> On Aug 19, 2014, at 2:47 PM, Chase Qishi Wu (qishiwu) >><qishiwu(a)memphis.edu> wrote: >> >>> Raj, >>> >>> Thank you very much for getting us the access. >>> >>> I found my login info but the password doesn¹t seem to be working. Is >>>there a way to reset my password? BTW, my account name is ³chasewu². >>> >>> Thanks, >>> Chase >> >> _______________________________________________ >> Admins mailing list >> Admins(a)lists.jlse.anl.gov >> https://lists.jlse.anl.gov/mailman/listinfo/admins >

1 0

Re: [JLSE-Admins] Access to Argonne test node
by Allen, Benjamin S. 20 Aug '14

20 Aug '14

Hi Chase, JLSE (Joint Laboratory for System Evaluation, JLSE replaces Future Tech (FT)), doesn't allow password authentication, unless you're using an ALCF two-factor cyrptocard. Our primary means of authentication is SSH public/private keys. You can add a public key via your account on https://accounts.jlse.anl.gov under "Credentials". Once you've done this please allow about 15 minutes and attempt to use your private key to ssh to login.jlse.anl.gov. Note the legacy hostname ft.alcf.anl.gov is just a CNAME to login.jlse.anl.gov. Please let me know if you run into any issues with this. Ben On Aug 19, 2014, at 4:04 PM, Chase Qishi Wu (qishiwu) <qishiwu(a)memphis.edu> wrote: > Dear sir/madam, > > I was not able to log onto ft.alcf.anl.gov with my username and password. Could you please help reset my password? > > Thanks, > Chase > > From: Raj Kettimuthu <kettimut(a)anl.gov> > Date: Tuesday, August 19, 2014 at 3:59 PM > To: "Chase Qishi Wu (qishiwu)" <qishiwu(a)memphis.edu> > Subject: Re: Access to Argonne test node > > Can you email admins(a)jlse.anl.gov about this? > > On Aug 19, 2014, at 2:47 PM, Chase Qishi Wu (qishiwu) <qishiwu(a)memphis.edu> wrote: > >> Raj, >> >> Thank you very much for getting us the access. >> >> I found my login info but the password doesn’t seem to be working. Is there a way to reset my password? BTW, my account name is “chasewu”. >> >> Thanks, >> Chase > > _______________________________________________ > Admins mailing list > Admins(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/admins

1 0

Re: [JLSE-Admins] Seamicro Evaluation
by Allen, Benjamin S. 19 Aug '14

19 Aug '14

I'm interested in hosting this, and have chatted with Scott about the eval. I can help out with installing, evaluating the systems administration side of the hardware, provisioning, baseline benchmarking, etc. Ben On Aug 19, 2014, at 5:15 PM, Kalyan Kumaran <kumaran(a)anl.gov> wrote: > > > Begin forwarded message: > >> From: "Murphy-Olson, Daniel E." <dolson(a)mcs.anl.gov> >> Subject: Seamicro Evaluation >> Date: August 19, 2014 at 5:08:28 PM CDT >> To: "Thakur, Rajeev" <thakur(a)mcs.anl.gov>, "Kumaran, Kalyanasundaram" <kumaran(a)alcf.anl.gov> >> >> Hi Rajeev and Kumar, >> >> The Magellan infrastructure team, Scott Devoid, Ryan Aydelott and I have been looking into several different hardware options that could be used as building blocks for Magellan's next refresh cycle. One interesting option is from Seamicro, currently part of AMD. We're interested in working with JLSE to evaluate the Seamicro hardware. >> >> Here is some more information regarding the machine we're interested in: >> http://www.seamicro.com/sm15000 >> http://www.seamicro.com/sites/default/files/SM_TO02_64_v2%205.pdf >> >> The primary areas we'd like to evaluate are: >> Internal torus network scalability >> How the system deals with changes in storage and network utilization on the fabric >> How well the system integrates with the Openstack control plane >> Serviceability of the components when operating under Openstack >> Compute performance under Openstack >> >> While we're primarily interested in the cloud computing capabilities, this platform may have HPC capabilities as well. >> >> Currently we have an NDA addendum we've received from AMD for this, but we don't yet have an evaluation agreement. >> >> Would you be interested in working with us on this? If so, how do we move forward? >> >> Thanks, >> Dan >> >> >> >> >> > > _______________________________________________ > Admins mailing list > Admins(a)lists.jlse.anl.gov > https://lists.jlse.anl.gov/mailman/listinfo/admins

1 0

[JLSE-Admins] Fwd: Seamicro Evaluation
by Kalyan Kumaran 19 Aug '14

19 Aug '14

Begin forwarded message: > From: "Murphy-Olson, Daniel E." <dolson(a)mcs.anl.gov> > Subject: Seamicro Evaluation > Date: August 19, 2014 at 5:08:28 PM CDT > To: "Thakur, Rajeev" <thakur(a)mcs.anl.gov>, "Kumaran, Kalyanasundaram" <kumaran(a)alcf.anl.gov> > > Hi Rajeev and Kumar, > > The Magellan infrastructure team, Scott Devoid, Ryan Aydelott and I have been looking into several different hardware options that could be used as building blocks for Magellan's next refresh cycle. One interesting option is from Seamicro, currently part of AMD. We're interested in working with JLSE to evaluate the Seamicro hardware. > > Here is some more information regarding the machine we're interested in: > http://www.seamicro.com/sm15000 > http://www.seamicro.com/sites/default/files/SM_TO02_64_v2%205.pdf > > The primary areas we'd like to evaluate are: > Internal torus network scalability > How the system deals with changes in storage and network utilization on the fabric > How well the system integrates with the Openstack control plane > Serviceability of the components when operating under Openstack > Compute performance under Openstack > > While we're primarily interested in the cloud computing capabilities, this platform may have HPC capabilities as well. > > Currently we have an NDA addendum we've received from AMD for this, but we don't yet have an evaluation agreement. > > Would you be interested in working with us on this? If so, how do we move forward? > > Thanks, > Dan > > > > >

1 0