October 2010 - Core-students - mailman3.cels.anl.gov

Where's Max?
by Max trefonides 11 Oct '10

11 Oct '10

Reminder: Working from home today. Happy European Invasion Day!! -- Max - mobile

1 1

Output from "cron" command
by Super-User 10 Oct '10

10 Oct '10

Your "cron" job on mercury /usr/lib/fs/nfs/nfsfind produced the following output: find: stat() error /exports/proj-fischer00/fischer/pc/00000001.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc/00000002.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc/My Music/00000002.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc/My Music/00000001.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc/My Pictures/RR/DMIR_6/DMIR222a.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc/My Pictures/RR/DMIR_6/DMIR222b.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc2/00000001.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc2/nek5n/doc/movies: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc2/My Music/00000002.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc2/My Music/00000001.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc2/My Pictures/RR/DMIR_6/DMIR222b.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc2/My Pictures/RR/DMIR_6/DMIR222a.JPG: Value too large for defined data type find: stat() error /exports/proj-fischer00/fischer/pc2/00000002.JPG: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc6/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc1/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc5/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc10/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc2/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc8/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc0/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc7/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc9/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc3/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc11/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/contribtest/datatypes/bc4/bcr0c1.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/perftest/long.err: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/examples/perftest/lrtestf.c: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/mpid/ch_nexus/nexus-rm/quickthreads/md/null.README: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/mpid/ch_nexus/nexus-rm/data_conversion/stamp-h.in: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/mpid/ch_nexus/nexus-rm/ports0/stamp-h.in: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/mpid/ch_nexus/nexus-rm/ports0/p0_th_null_i.h: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/mpid/ch_nexus/nexus-rm/ports0/p0_th_null.h: Value too large for defined data type find: stat() error /exports/shared/nt-homes001/lusk/mpich/mpid/ch_nexus/nexus-4.0b4/config/CONFIG: Value too large for defined data type

1 0

Re: [CELS Sysadmins] [aig] Beer
by stace＠mcs.anl.gov 08 Oct '10

08 Oct '10

Avoid 55 N! Daniel Buettner <buettner(a)alcf.anl.gov> wrote: m3 t00! ----- "Craig Stacey" <stace(a)mcs.anl.gov> wrote: > Tonight, around 6:30ish, heading to Brixies. And, for those who want > to > stick around, the Henhouse Prowlers will be playing some kick-ass > bluegrass around 10. > _______________________________________________ > This is the CELS Sysadmins mailing list. It is sent to memebers of: > core-admins(a)mcs.anl.gov, hpc-admins(a)mcs.anl.gov, systems(a)alcf.anl.gov, > aig(a)alcf.anl.gov. > Do not subscribe directly to this list. Thanks. > _______________________________________________ > aig mailing list > aig(a)lists.alcf.anl.gov > https://lists.alcf.anl.gov/cgi-bin/mailman/listinfo/aig _______________________________________________ This is the CELS Sysadmins mailing list. It is sent to memebers of: core-admins(a)mcs.anl.gov, hpc-admins(a)mcs.anl.gov, systems(a)alcf.anl.gov, aig(a)alcf.anl.gov. Do not subscribe directly to this list. Thanks.

1 0

[CELS Sysadmins] Beer
by Craig Stacey 08 Oct '10

08 Oct '10

Tonight, around 6:30ish, heading to Brixies. And, for those who want to stick around, the Henhouse Prowlers will be playing some kick-ass bluegrass around 10. _______________________________________________ This is the CELS Sysadmins mailing list. It is sent to memebers of: core-admins(a)mcs.anl.gov, hpc-admins(a)mcs.anl.gov, systems(a)alcf.anl.gov, aig(a)alcf.anl.gov. Do not subscribe directly to this list. Thanks.

6 6

[CELS Sysadmins] Let's get this party started
by Tisha Stacey 08 Oct '10

08 Oct '10

We're gathering up in room 4302. It has two entrances; if you go to the westernmost one, the door will either be ajar or just plain unlatched, so you should be able to get in. - Tisha _______________________________________________ This is the CELS Sysadmins mailing list. It is sent to memebers of: core-admins(a)mcs.anl.gov, hpc-admins(a)mcs.anl.gov, systems(a)alcf.anl.gov, aig(a)alcf.anl.gov. Do not subscribe directly to this list. Thanks.

2 1

DRAFT:::: Outage Notification: Tuesday, October 12 @ 0430hrs CST for 30 minutes
by Schmitz Corby 08 Oct '10

08 Oct '10

Not to be sent to the division, comments welcome now: All: In preparation for the power outage coming up in a couple weeks, we are trying to get networking things in order. This will simplify power- up and transition times for the outage, as well and put some new equipment into production to simplify our architecture. This work will involve a complete outage of all MCS services for a short window of time on Tuesday morning. The expected interruption in service should be a few minutes, with some portions lasting only a few seconds. This will affect all MCS infrastructure devices including, but not limited to, web, mail, file, authentication, login, database, compute and other various services provided by MCS. This will NOT affect HPC resources unless they rely on specific services listed above. During this time, desktops will be unaffected, except that many of them rely on services (file, authentication, etc) which will be unavailable. We are taking steps to ensure a successful transition, but will back out the changes if things are not going as expected. All work, including the option of backing out changes, will be completed during this 30 minute window. I will send out a note ahead of the initiation of changes, and then follow with an all-clear message when complete. There is a chance that desktop systems may not deal well with the changes being made. If you discover problems when you arrive on Tuesday, please reboot your system prior to contacting systems. If the problem continues, please visit the helpdesk. If you have any questions or concerns, please contact me at your earliest convenience. -- Corby Schmitz Network Engineer CIS/MCS/MREN/Starlight Argonne National Laboratory 9700 S. Cass Ave. Argonne, IL 60439 Desk: 630-252-7664 Cell: 630-512-1502 E-mail: schmitz(a)anl.gov

2 1

[CELS Sysadmins] Party! 10/23, 7PM
by Craig Stacey 07 Oct '10

07 Oct '10

Sorry if you already saw this on the facepage, but not everyone's on that. http://stace.com/party Birthday, house(re)warming, beer! 7317 W 58th Pl. Summit 60501 Be there or be somewhere else and lame. You wouldn't want to be lame. -- Craig _______________________________________________ This is the CELS Sysadmins mailing list. It is sent to memebers of: core-admins(a)mcs.anl.gov, hpc-admins(a)mcs.anl.gov, systems(a)alcf.anl.gov, aig(a)alcf.anl.gov. Do not subscribe directly to this list. Thanks.

1 1

Status Update and Outage Musings
by Schmitz Corby 07 Oct '10

07 Oct '10

Since I am going to miss the sync today, I wanted to give an update on where I am at with projects: -Load balance setup - network complete, Dan has access to the room, still supporting Dan as we go -Bio switches (bd49 and bc49) - online and being monitored by nagios, supporting Hunter as we go -New fiber-channel switch is racked and configured, all we have to do is move fiber, verified 32 ports active -5020 replacement for 5010, racked and configured (with only one caveat, see below) ready to go after the power outage -Switch for globus at SC10 is configured and ready to go 5020 configuration I renumbered things when configuring the 5020 as I wanted to protect the first 16 ports as they have the ability to be either GigE or 10GigE. Eth1/2 MCS-IDS:Core down 1 full 1000 1/10g Eth1/3 lin240-tape-rob:Co down trunk full 1000 1/10g Eth1/4 mcs-240mgt-C1:Core down trunk full 1000 1/10g Eth1/5 mcs-240mgt-C2:Core down trunk full 1000 1/10g Eth1/17 Systems-1-C1:Core down 1 full 10G 10g Eth1/18 Systems-3-C1:Core down 1 full 10G 10g Eth1/19 MCS-SW-RTR-C1:Core down trunk full 10G 10g Eth1/20 MCS-SW-RTR-C2:Core down trunk full 10G 10g Eth1/21 Mercury:Core down 6 full 10G 10g Eth1/22 Quicksilver:Core down 6 full 10G 10g Eth1/25 CI-Backup:Core down 808 full 10G 10g Eth1/26 PerfSonar.MREN:Wat down 110 full 10G 10g Po101 Systems-1-PC:Core down 1 auto auto -- Po102 mcs-240mgt-PC:Core down 1 auto 1000 -- Po103 Systems-3-PC:Core down 1 auto auto -- Po220 MCS-SW-RTR-PC:Core down 1 auto auto -- mgmt0 MGMT:Core up routed full 1000 -- Port 1/2 is the IDS capture port. To make this work, and not burn fiber on it, I am going to coordinate to move the sensor after the power outage. We will drop it in one of the racks and cable it up from there. It is a deep box, so there is no need for it to be in the network rack anyway. We will need to burn two fibers back to mcs-240rtr, one to the tape robot switch. Everything else is in the adjacent racks. The big caveat is that I cannot configure the FEX shelves until they are connected. This is going to be a problem. I will not be onsite when we power down and I may or may not be onsite when we power up. The tasks that need to be completed are as follows: 1. connect uplinks from mcs-240rtr to new mcs-240sw (5020) - 2x 10GigE 2. connect FEX shelves to new mcs-240sw (5020) - 1x 10GigE each (vi twinax cable) 3. configure FEX interfaces with config that follows I can pre-run everything, label it and have Linda do this. There is not much to shuffle here, but it can go badly. The alternative is to cut over to the new infrastructure before the power outage. This would involve a 4-7 minute blip while the FEX shelves cut over to the new 5020. This can be a very early morning project for me, since it doesn't really require any additional resources. I can cut over one of the 10GigE circuits currently feeding the 5010, and this would allow the interruption for mercury/quicksilver to be a few seconds. I think this is the best plan, but that's just my opinion. interface Ethernet101/1/1 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/2 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/3 description VSERVER6:Core switchport access vlan 186 spanning-tree port type edge interface Ethernet101/1/4 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/5 description v808 switchport access vlan 808 interface Ethernet101/1/6 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/7 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/8 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/9 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/10 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/11 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/12 description v808 switchport access vlan 6 spanning-tree port type edge interface Ethernet101/1/13 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/14 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/15 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/16 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/17 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/18 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/19 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/20 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/21 description CI-Webserver:Infra switchport access vlan 720 spanning-tree port type edge interface Ethernet101/1/22 description QUICKSILVER:Watch switchport access vlan 6 spanning-tree port type edge interface Ethernet101/1/23 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/24 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/25 description STO02 switchport access vlan 14 spanning-tree port type edge interface Ethernet101/1/26 description STO02 switchport access vlan 6 spanning-tree port type edge interface Ethernet101/1/27 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/28 description AUTH:Core switchport access vlan 7 spanning-tree port type edge interface Ethernet101/1/29 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/30 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/31 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/32 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/33 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/34 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/35 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/36 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/37 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/38 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/39 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/40 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/41 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/42 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/43 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/44 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/45 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/46 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/47 description v808 switchport access vlan 808 spanning-tree port type edge interface Ethernet101/1/48 description v815 switchport access vlan 815 interface Ethernet103/1/1 description THRASH:fex switchport access vlan 808 interface Ethernet103/1/2 description TROUNCE:fex switchport access vlan 808 interface Ethernet103/1/3 description VANQUISH:fex switchport access vlan 808 interface Ethernet103/1/4 description CHURN:fex switchport access vlan 808 interface Ethernet103/1/5 description GRIND:fex switchport access vlan 808 interface Ethernet103/1/6 description STEAMROLLER:fex switchport access vlan 808 interface Ethernet103/1/7 description CRANK:fex switchport access vlan 808 interface Ethernet103/1/8 description CRUSH:fex switchport access vlan 808 interface Ethernet103/1/9 description OCTAPUS:fex switchport access vlan 808 interface Ethernet103/1/10 description OCTAGON:fex switchport access vlan 808 interface Ethernet103/1/11 description ELEPHANT:fex switchport access vlan 808 interface Ethernet103/1/12 description TRIUMPH:fex switchport access vlan 808 interface Ethernet103/1/13 description LAL-MGMT:fex switchport access vlan 808 interface Ethernet103/1/14 description STOMP:Infra switchport access vlan 808 interface Ethernet103/1/15 description THWOMP:Infra switchport access vlan 808 interface Ethernet103/1/16 description v808 switchport access vlan 808 interface Ethernet103/1/17 description v808 switchport access vlan 808 interface Ethernet103/1/18 description v808 switchport access vlan 808 interface Ethernet103/1/19 description v808 switchport access vlan 808 interface Ethernet103/1/20 description v808 switchport access vlan 808 interface Ethernet103/1/21 description v808 switchport access vlan 808 interface Ethernet103/1/22 description v808 switchport access vlan 808 interface Ethernet103/1/23 description v808 switchport access vlan 808 interface Ethernet103/1/24 description v808 switchport access vlan 808 interface Ethernet103/1/25 description v808 switchport access vlan 808 interface Ethernet103/1/26 description v808 switchport access vlan 808 interface Ethernet103/1/27 description v808 switchport access vlan 808 interface Ethernet103/1/28 description v808 switchport access vlan 808 interface Ethernet103/1/29 description v808 switchport access vlan 808 interface Ethernet103/1/30 description v808 switchport access vlan 808 interface Ethernet103/1/31 description v808 switchport access vlan 808 interface Ethernet103/1/32 description v808 switchport access vlan 808 interface Ethernet103/1/33 description v808 switchport access vlan 808 interface Ethernet103/1/34 description VIETA:fex switchport access vlan 808 interface Ethernet103/1/35 description BG-ANL-EXTERNAL:fex switchport access vlan 186 interface Ethernet103/1/36 description MGT3.LCF:fex switchport access vlan 808 interface Ethernet103/1/37 description MGT2.LCF:fex switchport access vlan 808 interface Ethernet103/1/38 description GLOBUSCVS:fex switchport access vlan 86 interface Ethernet103/1/39 description USAGEDB:fex switchport access vlan 808 interface Ethernet103/1/40 description PETSC:fex switchport access vlan 808 interface Ethernet103/1/41 description CONSOLO:fex switchport access vlan 14 interface Ethernet103/1/42 description NEWTON:fex switchport access vlan 808 interface Ethernet103/1/43 description GIRARD:fex switchport access vlan 808 interface Ethernet103/1/44 description NOMER:fex switchport access vlan 736 interface Ethernet103/1/45 description SIPID:fex switchport access vlan 736 interface Ethernet103/1/46 description GNEP:fex switchport access vlan 808 interface Ethernet103/1/47 description V8:fex switchport access vlan 808 interface Ethernet103/1/48 description COOKIE:fex switchport access vlan 808 -corby

2 2

Forgot to mention at the sync...
by Tina J. Stanton-Piersanti 07 Oct '10

07 Oct '10

I will be taking a vacation day tomorrow! Today is my FRIDAY!! T.

1 1

Going mobile
by Schmitz Corby 07 Oct '10

07 Oct '10

I have to pick up some grounding stuff for SC at the electrical supply house, grab the last bit of supplies that I think I need at HD and then hop on my 3pm conference call. I am going mobile for the afternoon to get all of this done. I will be on my phone from 3-4 during the conference call, but feel free to interrupt me if need be. I will be looking at, and dealing with email as I go. -corby

1 0