CS IT Support Wiki - User contributions [en]

Networking at CS - Overview

2026-05-01T19:22:04Z

Pip:

:There are three main networks in CS at Malone Hall. They are:

::'''Public CS Grad/Research Net''' (128.220.35.x) - Uses IP addresses that are ''accessible from the Internet''.

::'''Private CS Grad/Research Net''' (10.161.159.x) - Uses IP addresses that are ''only accessible from within the Hopkins network (and Hopkins VPN)''.

::'''CS Undergrad Net''' (128.220.224.x) - Uses IP addresses that are ''accessible from the Internet''

:The Public and Private Grad/Research Nets are only ''physically'' accessible via network jacks in Malone Hall in CS work areas, except for the CS Undergrad Labs (Malone Hall 122 and the Ugrad Lab side of MH G61). The CS Undergrad Net is only ''physically'' accessible via network jacks in the CS Undergrad Lab. (Of course, you can access the Grad/Research Nets and the Ugrad Net systems remotely from other systems.)

:Not all network jacks are active. If you need to use a network jack but are not getting any network connection at all from it, please {{mailto|support|email us}} to ask for it to be activated.

 

==Network Jacks (Wallports) In Malone Hall==

:Network jacks may be located be under floor panels via access doors on the floor or they might be located on the wall, depending upon where you're located. Each network jack is identified with a floor number and jack number. (It is very important that any correspondence with CS IT Support or JHU Networking about a network jack include the full jack number.)

:(For those grad students working on the third floor of Malone, you might see that your floor panel access door is located under a slightly raised cabinet where the floor access door might be difficult to reach. For your convenience, there are network cables already coming out of those specific floor panels, and each of those cables is labeled with the port number.)

:Each active network jack in your Malone ''office'' will go to exactly one of those two Grad/Research networks (Public ''or'' Private Grad Net), so care will be needed to connect your computers into appropriate jacks. Again, if a jack is not currently active, you can {{mailto|support|email us}} to have it activated.

:Any given network jack can be changed from one network to the other (i.e., ''public to private'' or ''private to public'') with relatively little difficulty with an emailed request to [mailto:support@cs.jhu.edu CS Support]. We will pass on your request to JHU Networking. JHU Networking will be administering the network configurations; here is their current plan:

:* '''Even-numbered jacks''', by default, are connected to the '''''Public''''' CS Grad network, 128.220.35.x
:* '''Odd-numbered jacks''', by default, are be connected to the '''''Private''''' CS Grad network, 10.161.159.x

:'''Note 1:''' All network jacks in the CS Undergrad Lab are part of the CS Undergrad Net (128.220.224.x)

:'''Note 2:''' If you have a system that will reside in the G29 Malone ''server room'' instead, please contact CS Support, and we will help arrange your system's connections to the appropriate network, as there are no wallports in G-29.

 

== ''Public'' CS Grad/Research Network Details ==

:The '''"Public" CS Grad/Research Net''' uses IP addresses that are directly accessible from the Internet. It is useful for servers that need to be widely accessible or for systems that people need to connect to without going through the Hopkins VPN. (For example, if you need to ssh into your work machine from out on the Internet, your work machine needs a public IP address.)

:Systems on the Public Grad Net can freely communicate with systems elsewhere on the Hopkins network, including systems on the Private CS Grad Net.

:In order to set up a system on the Public Grad Net, you will need to follow the instructions at [[Requesting a Static IP Address on the CS Network]] and indicate in your request that the IP address will be public. There is '''no''' ''dynamic IP address service'' available on the Public network.

===Public IP Security Considerations===

:Please keep in mind that a system with a Public IP is exposed to the Internet. That means that '''''your system is open and vulnerable to access attempts from the outside.''''' If you're the only one who will access your system from the outside, please consider a Private IP instead, and use the VPN to put you into the JHU network so that you can access your system. If you have several outside people needing access to your system, then, yes, a Public IP is probably needed.

:And, because systems on the Public Grad Net are exposed to the Internet, they are expected to be managed in a way that preserves their security and the security of the Hopkins network. The JHU Network Security Team (part of the [http://www.it.jhu.edu/ IT@JH] group, ''not'' CS) may periodically perform security scans of systems on the Public Grad Net. If they determine that there are security problems with a system, they may disable all Internet access for that system until the problems are resolved.

===Opening Ports on the JHU Firewall===

:Some systems with a CS '''public''' IP might might want to be accessible through JHU's perimeter firewall. (CS does not maintain a departmental firewall) To have a port opened on the JHU firewall, please see: [https://support.cs.jhu.edu/wiki/Requesting_Open_Ports_on_the_JHU_Firewall Requesting Open Ports on the JHU Firewall]

 

== ''Private'' CS Grad/Research Network Details==

:The '''"Private" CS Grad/Research Net''' uses IP addresses that can only be directly accessed from either the Hopkins network or the Hopkins VPN. It is useful for systems that do not need to be accessed from the Internet, like desktop computers or printers. The private addressing used on this network helps keep the systems a little more secure, since no one on the Internet can contact them directly.

:You can connect your system to the Private Grad Net by following the instructions at [[Connecting to the CS Grad Nets]]. By default, you will receive a ''dynamic IP address''. If you need a ''static IP address'', follow the instructions at [[Requesting a Static IP Address on the CS Network]], making sure to specify that you want a ''private static IP address''.

 

==''CS Undergrad Network'' Details==

:The '''CS Undergrad Network''' is only available via wall and tabletop network jacks in Malone Hall Room 122 (the CS Collaboration Room). (Note that our other Ugrad Lab room, the Ugrad Lab side of Malone Hall G61, houses additional Ugrad Lab systems, but we are not currently supporting users plugging into the network in that room). To connect to the CS Undergrad Net, follow the instructions at [[Connecting to the CS Ugrad Net]]. Your computer will receive a dynamic IP address. There are no static IP addresses granted for the CS Ugrad Net.

 

== Requesting a Static IP Address ==

:If you need to request a ''static IP address'', please follow the instructions at [[Requesting a Static IP Address on the CS Network]].

 

== DNS Servers to use when on the CS Network ==

:Primary DNS: '''10.200.1.1'''

:Secondary DNS: '''10.200.2.2'''

:DHCP-provided CS IPs will automatically receive the above DNS servers.

 

== General Configuration Notes ==

===Public Network (128.220.35.x, even-numbered ports)===

:Subnet Mask: '''255.255.255.0'''

:Gateway: '''128.220.35.1'''

===Private Network (10.161.159.x, odd-numbered ports)===

:Subnet Mask: '''255.255.255.0'''

:Gateway: '''10.161.159.1'''

 

== Security Note ==

:All computers that connect to the CS Grad/Research or Undergrad net should be at their latest security levels and should be configured to prevent viruses, etc. For antivirus software, please see the [http://it.jhu.edu/antivirus JHU Antivirus webpage].

[[Category:Networking]]

Notices

2026-04-16T23:11:52Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===



{{outage
|services=masters10
|time=Thursday, April 16
|summary=masters10 is having hardware problems and is not usable at this time. We expect it to be unavailable through at least part of next week. Please use the other masters systems in the meantime.
}}
 

=== PLANNED CS IT SERVICE OUTAGES ===


:'''WHAT:''' Major (but overnight) Network and WiFi outages planned for the 3rd floor of Malone Hall starting the evening of April 21... 3rd Floor access to CS IT Services will be affected...

:'''WHEN:''' Tues, April 21, 11pm through Wed. April 22, 3am

:'''DETAILS:''' JHU Networking is planning to complete their upgrade of their network equipment in Malone Hall and will be performing the '''third floor''' upgrade starting April 21 at 11pm. That means that the 3rd floor CS, ISI, and Malone Center offices and labs will not have any network connectivity (including ethernet and wifi.) This also means that ''if you're on the '''3rd''' floor'' and try to connect to the CS server room or to CS IT services during that time, you will be unable to do so.






 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access,


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2026-02-18T16:42:38Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===





{{outage
|services=mail
|time=Wednesday, February 18, starting around 11:15 am
|summary=There is an issue with the mail server that we're investigating. You might be unable to check or store mail messages until the problem is fixed.
|update=As of about 11:45 am, we believe we've fixed the problem.
}}

=== PLANNED CS IT SERVICE OUTAGES ===


 
'''WHAT:''' Major CS Grad/Research Net & Ugrad Net IT services outage to perform maintenance on a server...

'''WHEN:''' Tuesday, February 24, from 6am to 8am.

'''DETAILS:''' We need to perform some maintenance on one of our servers. This will take approximately 2 hours to complete. During this time, several our of Grad/Research Net and Ugrad Net IT services will be unavailable. Below is a list of the services affected...

'''CS IT Services That Will Not Be Available During The Service Outage:'''
* CS Mail service, both incoming and outgoing, will be suspended for CS Grad/Research Net users. And some CS email services will not be available for CS Ugrad Net users. Incoming mail should be queued by the sender until our mail service is back up again. Outgoing CS mail will not be available to Grad/Research Net users, but since CS Ugrads can send through the JHU mail server, CS Ugrads might still be able to send email during the services outage (just not from our lab computers or compute servers.)

* IMAP, POP, and webmail (for both Grad/Research and Ugrad accounts) will be unavailable.

* No locally-stored CS webpages will be available. The main CS website (run by WSE) may or may not remain accessible. If you have a personal or lab CS page that we maintain locally in the dept, those will be unavailable. The CS IT Support Wiki and its Notices page will remain available.

* All CS Linux user accounts and home directories on both the Grad/Research and Ugrad Nets will be inaccessible during the service outage.

* ssh service to our Grad and Ugrad Linux clients (masters1 through masters16, ugrad1 through ugrad24, gradx, ugradx, gradz, and ugradz) will be unavailable.

* Console (desktop) access at any of our Linux client systems will be unavailable.

* SMB (SAMBA) File Shares (the CS Office Staff and some others use these) will be unavailable.

* MySQL service via the mysql.cs.jhu.edu server will be unavailable.

If there are any unexpected complications during the configuration changes that will delay the restoration of services, we will update the CS IT Support Wiki's Notices page at: https://support.cs.jhu.edu/wiki/Notices





 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access,


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2026-02-18T16:30:10Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===





{{outage
|services=mail
|time=Wednesday, February 18, starting around 11:15 am
|summary=There is an issue with the mail server that we're investigating. You might be unable to check or store mail messages until the problem is fixed.
}}

=== PLANNED CS IT SERVICE OUTAGES ===


 
'''WHAT:''' Major CS Grad/Research Net & Ugrad Net IT services outage to perform maintenance on a server...

'''WHEN:''' Tuesday, February 24, from 6am to 8am.

'''DETAILS:''' We need to perform some maintenance on one of our servers. This will take approximately 2 hours to complete. During this time, several our of Grad/Research Net and Ugrad Net IT services will be unavailable. Below is a list of the services affected...

'''CS IT Services That Will Not Be Available During The Service Outage:'''
* CS Mail service, both incoming and outgoing, will be suspended for CS Grad/Research Net users. And some CS email services will not be available for CS Ugrad Net users. Incoming mail should be queued by the sender until our mail service is back up again. Outgoing CS mail will not be available to Grad/Research Net users, but since CS Ugrads can send through the JHU mail server, CS Ugrads might still be able to send email during the services outage (just not from our lab computers or compute servers.)

* IMAP, POP, and webmail (for both Grad/Research and Ugrad accounts) will be unavailable.

* No locally-stored CS webpages will be available. The main CS website (run by WSE) may or may not remain accessible. If you have a personal or lab CS page that we maintain locally in the dept, those will be unavailable. The CS IT Support Wiki and its Notices page will remain available.

* All CS Linux user accounts and home directories on both the Grad/Research and Ugrad Nets will be inaccessible during the service outage.

* ssh service to our Grad and Ugrad Linux clients (masters1 through masters16, ugrad1 through ugrad24, gradx, ugradx, gradz, and ugradz) will be unavailable.

* Console (desktop) access at any of our Linux client systems will be unavailable.

* SMB (SAMBA) File Shares (the CS Office Staff and some others use these) will be unavailable.

* MySQL service via the mysql.cs.jhu.edu server will be unavailable.

If there are any unexpected complications during the configuration changes that will delay the restoration of services, we will update the CS IT Support Wiki's Notices page at: https://support.cs.jhu.edu/wiki/Notices





 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access,


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2026-01-08T20:32:15Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===


{{red|'''UPDATE: Nov 30, 2025, 2:45pm:''' Webserver is working again! CS websites can now be access. }} ORIGINAL:'''Nov 30, 2025, 2pm:''' CS Webservice is down. The CS webserver is experiencing issues, and we are looking into the problem. In the meantime, you will be unable to access the main CS website or personal websites.




=== PLANNED CS IT SERVICE OUTAGES ===



{{outage
|type=Planned outage
|time=Wednesday, January 14 and Thursday, January 15
|services=gradz and ugradz
|summary=We will need to shut down two of our [[:Category:Linux Clients|Linux clients]] for maintenance. The two clients are gradz and ugradz. They might be unavailable for as much as two days, depending on how long the maintenance takes. Please use our other Linux clients during the maintenance window.}}



 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access,


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2025-10-31T13:20:02Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2025-10-30T13:45:50Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-10-30T11:48:37Z

Pip: /* Outage #1: CS Webserver Will Be Unavailable */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff operates out of Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We are available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 



== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.



=== PLANNED CS IT SERVICE OUTAGES ===


===Outage #1: CS Webserver Will Be Unavailable===

:'''WHAT:''' CS Webserver will be unavailable due server maintenance.

:'''WHEN:''' Thursday, October 30, from 7am to 7:30am.

:'''UPDATE:''' As of 7:45 am, all web services have been restored.

:'''DETAILS:'''

:On Thursday, October 30, at 7:00 am, we will be taking the department web server offline for some necessary maintenance. It should be offline for no more than half an hour.

:During the maintenance window, the CS department website will be unreachable, as will any lab group or individual websites hosted by the CS IT group. The CS grad net webmail will be unavailable.

:Web sites hosted elsewhere (e.g. a GitHub Pages site with a cs.jhu.edu hostname) will be unaffected. Other CS services will be unaffected.

====Outage #2: CS Labs/Systems Will Be Unavailable====
:'''WHAT:''' Malone Hall MH 122 '''and''' Malone Hall G61, both the Masters and Ugrad sides of the lab, and ''all'' the lab Linux computers, will be closed to CS students due to an ACM Programming Contest.

:'''WHEN:''' Starting Friday evening, November 7, 5pm '''through''' Saturday, November 8, 9pm.

:'''DETAILS:'''

: Both the MH 122 '''and''' G61 Masters and Ugrad Labs will be used for an ACM Programming Contest and will therefore be '''''closed''''' to those not participating in the contest.

: Additionally, all of the labs' Linux computers (masters1 through masters16 and ugrad1 through ugrad24) will be unavailable during the time period referenced above.

* During the lab closure times, compute servers, gradx.cs.jhu.edu, gradz.cs.jhu.edu, ugradx.cs.jhu.ed, and ugradz.cs.jhu.edu '''''will continue to be available remotely''''', via SSH.

* We have to take down the lab systems late that Friday afternoon. At the end of the ACM contest that Saturday night, the coordinators of that contest will be turning our lab computer systems back on. Most should boot normally. But, if some do not, just trying using an alternate one in the lab. We'll be back in the Monday afterwards and can check on any systems that didn't boot normally. (And don't forget, as mentioned above our compute servers -- gradx, gradz, ugradx, ugradz -- will continue to be remotely available, even if the lab systems are not.)

* The printers in MH 122 and MH G61 will remain online, but, please pick up your printouts outside of the contest hours.


 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access, {{red|except for what's listed above.}}


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access, {{red|except for what's listed above.}}

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Available Printers

2025-10-14T19:08:16Z

Pip:

We have various printers available for general use throughout the CS Dept.

{{red|'''Because of the great diversity in functionality amongst printers and people's personal systems, we can only offer support/assistance in configuring printing for only those computer systems and printers that CS IT Support maintains.''' '''''We do not configure users' own systems to print to our printers.'''''}}

Please see our [[:Category:Printing|Printing category]] for an '''overview and notes''' regarding printing at CS.

Also, please see the [[#Printer Problems|Printer Problems]] section at the bottom of this page.

NOTE: In the chart below, QUEUE NAME is the print queue name of the printer on our Ugrad and Masters'/Grad Lab Linux computers.



{| class="wikitable"

|-
! LOCATION !! MODEL !! HOSTNAME !! CS GRAD/UGRAD LABS LINUX QUEUE NAME !! AVAILABLE TO !! NOTES
|-
|Malone 122 (CS Undergraduate Lab)  ||HP LaserJet M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone G61 (Masters'/Ugrad Lab) ||HP LaserJet M610||mhg61prt.cs.jhu.edu||mhg61prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) '''''{{red|NEW!}}'''''||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers) '''''However, for CS students''', we ask that they only print to the color copier if color is absolutely necessary, and only during the CS Office's office hours.''|| {{red|('''''NEW'' ''HP'' copier, replaced the old ''Canon'' Copier''')}}
COLOR, Duplexing copier '''and''' printer. {{red|1='''NOTE:''' Please default your print configuration to ''Black and White or Grayscale''. Only choose ''Color'' if you need to print out specifically in color.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|Malone 257A (North-end section of MH 2nd floor) ||HP LaserJet p4515x||mh2ndprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Versions of the driver for up through MacOS 10.12 are available there as well. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone 352 (''{{red|'''NEW'''}} printer in the 3rd floor Kitchen Area, as of 5/28/25'') ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==Note to Mac Users==

:Macs can be somewhat tricky when configuring printers. One thing you should keep in mind when configuring one of our networked printers on your Mac is to choose to install an '''IP''' printer, put in the IP address or full hostname (with .cs.jhu.edu part) for the '''Address''' field. (Sometimes, only the full hostname will work if the IP address doesn't.) For the '''Protocol''' field, choose ''Line Printer Daemon -LPD''. (That '''Protocol''' field is usually the part that most Mac users do not set, and that needs to be set to print properly to our printers, in our experience.) You can keep the '''Queue''' field blank. That should be all you need. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==Printer Problems==

* If one of the printers that CS IT Support manages (other than the dept copier) is low on toner or experiencing print-quality issues, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] 

* If you run out of paper at the printer, ''please visit Malone Hall 160 (the CS main office),'' and request more.

* If a CS-managed printer jams, and you are able to remove the jammed sheet, but the printer seems to hang on printing:
** Turn off the printer
** Unplug the power from the printer
** Wait at least 30 seconds.
** Plug the printer back in.
** Turn printer back on.
That usually clears out a printer's internal print queue.

* If a CS-managed printer jams, and you are unable to remove/find the paper jamming in the printer, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

[[Category:Printing]]

[[Category:Labs]]

Available Printers

2025-10-10T14:35:25Z

Pip:

We have various printers available for general use throughout the CS Dept.

{{red|'''Because of the great diversity in functionality amongst printers and people's personal systems, we can only offer support/assistance in configuring printing for only those computer systems and printers that CS IT Support maintains.''' '''''We do not configure users' own systems to print to our printers.'''''}}

Please see our [[:Category:Printing|Printing category]] for an '''overview and notes''' regarding printing at CS.

Also, please see the [[#Printer Problems|Printer Problems]] section at the bottom of this page.

NOTE: In the chart below, QUEUE NAME is the print queue name of the printer on our Ugrad and Masters'/Grad Lab Linux computers.



{| class="wikitable"

|-
! LOCATION !! MODEL !! HOSTNAME !! CS GRAD/UGRAD LABS LINUX QUEUE NAME !! AVAILABLE TO !! NOTES
|-
|Malone 122 (CS Undergraduate Lab)  ||HP LaserJet M610 ||mh122prt.cs.jhu.edu||mh122prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605
|-
|Malone G61 (Masters'/Ugrad Lab) {{red|'''Temporarily unavailable'''; use mh122prt instead.}} ||HP LaserJet M610||mhg61prt.cs.jhu.edu||mhg61prt||All CS Students and faculty/staff/researchers/postdocs (and accessible from all Grad and Ugrad Linux computers)||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-m610-series/31570605

|-
|Malone 154 (CS Office Mailroom) '''''{{red|NEW!}}'''''||HP Color LaserJet - MFP E877 Copier/Printer||cscopier.cs.jhu.edu||cscopier|| All CS Students and faculty/staff/researchers/postdocs (and access from all Grad and Ugrad Linux computers) '''''However, for CS students''', we ask that they only print to the color copier if color is absolutely necessary, and only during the CS Office's office hours.''|| {{red|('''''NEW'' ''HP'' copier, replaced the old ''Canon'' Copier''')}}
COLOR, Duplexing copier '''and''' printer. {{red|1='''NOTE:''' Please default your print configuration to ''Black and White or Grayscale''. Only choose ''Color'' if you need to print out specifically in color.}} Copier/Printer is also a scanner allowing for ''Scan-to-Email''. (There is no Scan-to-USB or Load-from-USB option available.)

'''NOTE: CS IT ''does not'' maintain or configure the HP copier. If you have issues with the copier, please report those issues to staff in the CS office, MH-160.'''

'''DRIVERS:''' Drivers for '''Windows''' can be found here: [https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449 https://support.hp.com/us-en/drivers/hp-color-laserjet-managed-mfp-e877-printer-series/38348449] We suggest using the ''Smart Universal Print Driver'' It works well and is easy to install.

There is another page for "what if my driver is not listed" that includes '''Mac''' and '''Linux''': [https://support.hp.com/us-en/document/ish_6966654-6966703-16 https://support.hp.com/us-en/document/ish_6966654-6966703-16] In any case, you might be presented with multiple types of HP drivers for a specific platform. You'll need to try various ones until you find one that works for your specific system.

However, for '''MacOS''', here are some basics steps that have been suggested to us that might help you configure access to the copier: 1) Download [https://ftp.hp.com/pub/softlib/software12/HP_Quick_Start/osx/Applications/HP_Easy_Admin.app.zip ''HP Easy Admin'' app]. 2) Unzip, and you will need to find the actual file to run that starts the app. 3) Starting and following the prompts of the HP Easy Admin app ''should'' be all you need to install the proper driver. 4) In MacOS, go to System Preferences - Printers &Scanners, and click the + sign to add a printer. 5) Do not let it scan for the copier. Instead, you should see three graphics at the top of the Add Printer window. Choose the center image of a globe called IP. 6) Enter the HP Copier's full hostname, ''cscopier.cs.jhu.edu''. (Do not use the HP Copier's numerical IP address) 7) For Protocol, choose HP Jetdirect Socket from the drop-down. 8) Under ''Use'', choose the driver that hopefully, your Easy Admin app downloaded for you (should have "877" somewhere in the driver name.) 9) Click Add, and at this point, the copier should be added. '''NOTE:''' We have found that for some unknown reason, once the copier is added, you might or might not be able to use the Finishing options (stapler) right away. In two different macbook instances, even after a reboot, the stapler option didn't appear as an active Finishing option during a print attempt until sometime after the copier was added (in these cases, we didn't see the stapler option available to use until at least another day. We're assuming it's either a MacOS issue or an HP driver issue.

And for '''Linux''', your CUPS driver might be enough to allow access to the copier's features. If not, youll need to search for an appropriate driver for your flavor of Linux.

|-
|Malone 257A (North-end section of MH 2nd floor) ||HP LaserJet p4515x||mh2ndprt1.cs.jhu.edu||N/A||All CS Non-UGrad People|| Duplexing printer. If you plan to print ''from your own computer'', make sure you go to HP's site and download the appropriate drivers for your computer and this printer. [https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895 https://support.hp.com/us-en/drivers/selfservice/hp-laserjet-p4510-printer-series/3558888/model/3558895] Once at that site, choose your OS and driver. Windows users should be able to easily find a driver there. Versions of the driver for up through MacOS 10.12 are available there as well. If you can't find the driver you need, you might find that any standard PS or PCL driver should work.
|-
|Malone 352 (''{{red|'''NEW'''}} printer in the 3rd floor Kitchen Area, as of 5/28/25'') ||HP LaserJet M602 ||you can use either mh3rdprt.cs.jhu.edu or mh3rdprt2.cs.jhu.edu||N/A||All CS non-Ugrad people||Duplexing printer. For most up to date OSes, you should just be able to add the printer as an IPP printer using the printer's hostname, with no additional driver installation needed. If you find you do need a printer driver, please see HP's driver download page: https://support.hp.com/us-en/drivers/hp-laserjet-enterprise-600-printer-m602-series/5145285

|}

==Note to Mac Users==

:Macs can be somewhat tricky when configuring printers. One thing you should keep in mind when configuring one of our networked printers on your Mac is to choose to install an '''IP''' printer, put in the IP address or full hostname (with .cs.jhu.edu part) for the '''Address''' field. (Sometimes, only the full hostname will work if the IP address doesn't.) For the '''Protocol''' field, choose ''Line Printer Daemon -LPD''. (That '''Protocol''' field is usually the part that most Mac users do not set, and that needs to be set to print properly to our printers, in our experience.) You can keep the '''Queue''' field blank. That should be all you need. Note, though, for the cscopier printer (see its section above), you need to set a different protocol.

==Printer Problems==

* If one of the printers that CS IT Support manages (other than the dept copier) is low on toner or experiencing print-quality issues, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] 

* If you run out of paper at the printer, ''please visit Malone Hall 160 (the CS main office),'' and request more.

* If a CS-managed printer jams, and you are able to remove the jammed sheet, but the printer seems to hang on printing:
** Turn off the printer
** Unplug the power from the printer
** Wait at least 30 seconds.
** Plug the printer back in.
** Turn printer back on.
That usually clears out a printer's internal print queue.

* If a CS-managed printer jams, and you are unable to remove/find the paper jamming in the printer, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu]

[[Category:Printing]]

[[Category:Labs]]

Notices

2025-10-10T14:33:45Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Python on the CS Webservers

2025-10-01T19:33:51Z

Pip: /* Python Packages */

Python is supported as a CGI program on the [[:Category:Webpages and Webservices|CS Department webservers]], but there are a few things you should know about it.

You may also want to read about [[Python on the CS Linux Clients]].

== Python Versions ==

The web servers have both Python 3 and Python 2 available. As of February 2021, the web servers are using '''''Python 3.6''''' by default. This is ''different'' from the [[:Category:Linux Clients|Linux clients]], which use a ''newer'' version. (As of fall 2025, the Linux clients use Python 3.13 by default.) If you're writing programs to run on one of the department web servers, '''we recommend you restrict those programs to use only features available in the web servers' version of Python 3.'''

The web servers have several other versions of Python ''available''. The Python versions available on both the web servers and the Linux clients are:

* Python 3.6 (default on the web servers)
* Python 3.9
* Python 3.11
* Python 3.12
* Python 3.13 (default on the Linux clients)

The version of Python used for your programs will depend on what interpreter you call at the top of your program. If you use {{code|#!/usr/bin/env python}} or {{code|#!/usr/bin/env python3}}, you will get the default Python for the system (which, again, will be different between the web server and the Linux client you can log in to). If you use {{code|#!/usr/bin/env python2}}, you will get Python 2.7 on the web server and the program will not work on our Linux clients. You can also give the precise version of Python you want; for example, {{code|#!/usr/bin/env python3.11}} will use Python 3.11 on both the web server and the Linux clients.

(It's good practice to explicitly use {{code|python3}} when you intend to use Python 3. Using {{code|python}} by itself is only recommended [https://www.python.org/dev/peps/pep-0394/ in a handful of situations] that mostly don't apply to our web servers.)

== Python Packages ==

The set of Python packages installed on the webservers is fairly minimal. If you need a package that's not installed, you should first try installing it yourself into your home directory, using our [[Python on the CS Linux Clients#Installing_Python_Packages|self-installation instructions]]. If that does not work, you can contact us at {{mailto|support}} for assistance, but be aware that we are not be able to install every requested package.

If you need a package that is not supported on our web servers' default Python version, you can use the versioned Python executable to set up the virtual environment. For example, if you had a package that needed Python 3.11 or later, you could run <kbd>python3.11 -m venv <var>/path/to/venv/directory</var></kbd>. If you run a Python program in such a venv, it will use the version of Python you used to set up the venv, even if the program starts with {{code|#!/usr/bin/env python3}} or {{code|#!/usr/bin/env python}}.

See the previous section for which versions of Python are available on both our web servers and our Linux clients.

== Deployment Options ==

For technical reasons, we do not support WSGI. You will have to run your Python programs as either CGI or FastCGI programs. (Most major Python web frameworks support FastCGI deployment; see their documentation for details.)

[[Category:Webpages and Webservices]]

Python on the CS Webservers

2025-10-01T18:46:57Z

Pip: /* Python Packages */

Python is supported as a CGI program on the [[:Category:Webpages and Webservices|CS Department webservers]], but there are a few things you should know about it.

You may also want to read about [[Python on the CS Linux Clients]].

== Python Versions ==

The web servers have both Python 3 and Python 2 available. As of February 2021, the web servers are using '''''Python 3.6''''' by default. This is ''different'' from the [[:Category:Linux Clients|Linux clients]], which use a ''newer'' version. (As of fall 2025, the Linux clients use Python 3.13 by default.) If you're writing programs to run on one of the department web servers, '''we recommend you restrict those programs to use only features available in the web servers' version of Python 3.'''

The web servers have several other versions of Python ''available''. The Python versions available on both the web servers and the Linux clients are:

* Python 3.6 (default on the web servers)
* Python 3.9
* Python 3.11
* Python 3.12
* Python 3.13 (default on the Linux clients)

The version of Python used for your programs will depend on what interpreter you call at the top of your program. If you use {{code|#!/usr/bin/env python}} or {{code|#!/usr/bin/env python3}}, you will get the default Python for the system (which, again, will be different between the web server and the Linux client you can log in to). If you use {{code|#!/usr/bin/env python2}}, you will get Python 2.7 on the web server and the program will not work on our Linux clients. You can also give the precise version of Python you want; for example, {{code|#!/usr/bin/env python3.11}} will use Python 3.11 on both the web server and the Linux clients.

(It's good practice to explicitly use {{code|python3}} when you intend to use Python 3. Using {{code|python}} by itself is only recommended [https://www.python.org/dev/peps/pep-0394/ in a handful of situations] that mostly don't apply to our web servers.)

== Python Packages ==

The set of Python packages installed on the webservers is fairly minimal. If you need a package that's not installed, you should first try installing it yourself into your home directory, using our [[Python on the CS Linux Clients#Installing_Python_Packages|self-installation instructions]]. If that does not work, you can contact us at {{mailto|support}} for assistance, but be aware that we are not be able to install every requested package.

If you need a package that is not supported on our web servers' default Python version, you can use the versioned Python executable to set up the virtual environment. For example, if you had a package that needed Python 3.11 or later, you could run <kbd>python3.11 -m venv <var>/path/to/venv/directory</var></kbd>. See the previous section for which versions of Python are available on both our web servers and our Linux clients.

== Deployment Options ==

For technical reasons, we do not support WSGI. You will have to run your Python programs as either CGI or FastCGI programs. (Most major Python web frameworks support FastCGI deployment; see their documentation for details.)

[[Category:Webpages and Webservices]]

Python on the CS Webservers

2025-10-01T18:43:20Z

Pip: /* Python Versions */

Python is supported as a CGI program on the [[:Category:Webpages and Webservices|CS Department webservers]], but there are a few things you should know about it.

You may also want to read about [[Python on the CS Linux Clients]].

== Python Versions ==

The web servers have both Python 3 and Python 2 available. As of February 2021, the web servers are using '''''Python 3.6''''' by default. This is ''different'' from the [[:Category:Linux Clients|Linux clients]], which use a ''newer'' version. (As of fall 2025, the Linux clients use Python 3.13 by default.) If you're writing programs to run on one of the department web servers, '''we recommend you restrict those programs to use only features available in the web servers' version of Python 3.'''

The web servers have several other versions of Python ''available''. The Python versions available on both the web servers and the Linux clients are:

* Python 3.6 (default on the web servers)
* Python 3.9
* Python 3.11
* Python 3.12
* Python 3.13 (default on the Linux clients)

The version of Python used for your programs will depend on what interpreter you call at the top of your program. If you use {{code|#!/usr/bin/env python}} or {{code|#!/usr/bin/env python3}}, you will get the default Python for the system (which, again, will be different between the web server and the Linux client you can log in to). If you use {{code|#!/usr/bin/env python2}}, you will get Python 2.7 on the web server and the program will not work on our Linux clients. You can also give the precise version of Python you want; for example, {{code|#!/usr/bin/env python3.11}} will use Python 3.11 on both the web server and the Linux clients.

(It's good practice to explicitly use {{code|python3}} when you intend to use Python 3. Using {{code|python}} by itself is only recommended [https://www.python.org/dev/peps/pep-0394/ in a handful of situations] that mostly don't apply to our web servers.)

== Python Packages ==

The set of Python packages installed on the webservers is fairly minimal. If you need a package that's not installed, you should first try installing it yourself into your home directory, using our [[Python on the CS Linux Clients#Installing_Python_Packages|self-installation instructions]]. If that does not work, you can contact us at {{mailto|support}} for assistance, but be aware that we are not be able to install every requested package.

== Deployment Options ==

For technical reasons, we do not support WSGI. You will have to run your Python programs as either CGI or FastCGI programs. (Most major Python web frameworks support FastCGI deployment; see their documentation for details.)

[[Category:Webpages and Webservices]]

Template:Code

2025-09-29T19:49:50Z

Pip: Created page with "<code {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} {{#if:{{{style|}}}|style="{{{style}}}"}}>{{{1}}}</code><noinclude> See https://www.mediawiki.org..."

<code {{#if:{{{class|}}}|class="{{{class}}}"}} {{#if:{{{id|}}}|id="{{{id}}}"}} {{#if:{{{style|}}}|style="{{{style}}}"}}>{{{1}}}</code><noinclude>
See https://www.mediawiki.org/wiki/Template:Code .
</noinclude>

Notices

2025-09-19T13:02:05Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-18T20:18:09Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-18T20:18:02Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-18T20:13:15Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-18T16:54:01Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-18T16:53:53Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-18T16:53:33Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-18T16:53:13Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-10T18:01:08Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-10T17:07:46Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-09-10T17:01:54Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Notices

2025-09-10T16:57:35Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */

Disk Quotas

2025-08-29T12:41:56Z

Pip: Quota increase

'''CS ''UGRAD'' Net Users:''' Due to the number of students using the Ugrad Linux systems, on the '''''CS Ugrad Net''''', the Ugrad accounts ''are subject to '''disk quotas''''', which are limits on the total amount of data you are permitted to store in your home directory (or, in some cases, other directories). If you exceed a quota, you will be unable to create new files or add to existing files until you reduce the total amount of disk space you're using to go below your quota.

'''CS ''GRAD'' Net Users:''' The '''''CS Grad/Research Net''''' does not currently have disk quotas enabled. But, we ask that users on the CS Grad/Research Net be mindful that you are ''sharing disk space with much of CS''. If you need to store large amounts of data on the CS Grad Net, please see: [[Storing Large Amounts Of Data On Our Systems]]

== How Quotas Work on the ''CS Ugrad Net'' ==

Every account that is subject to a quota has limit on the total amount of disk space used by that account's files. For most of our CS Ugrad accounts, that limit is '''15 GiB'''. Once you hit that limit, all attempts to allocate more space (creating new files, making existing files larger, etc.) will fail.

''If you cannot allocate more space (because you've hit your quota limit), '''you might not be able to log in via the GUI on our Ugrad computer lab Linux systems'''. If that happens, you will have to SSH in remotely and reduce your disk usage below your quota.''

==='''''{{red|IMPORTANT NOTE:}} If You Are Using A ''Cloud Drive'' ('''Dropbox''', '''Google Drive''', etc.)===

:If you have your CS Ugrad Linux account linked to a cloud drive such as '''Dropbox''' or '''Google Drive''', please note that those services may download local copies of your cloud files into your Ugrad account. This is an extremely quick way to go over your CS Ugrad disk quota. We recommend you not link cloud drives with your CS Linux account (unless your cloud drive is very small and well within your CS Ugrad disk quota.) We cannot accomodate users' cloud data within our provided home directory disk resources.

== How to Check Your Quota on the ''CS Ugrad Net'' ==

Log in to one of the [[Linux Clients on the CS Undergrad Net]] and run the following command from the command line:

quota

If it doesn't print anything, you are not subject to any quotas. If it does print something, the output will look like this:

''account'': 1.6GiB used out of 15.0GiB quota

This should be fairly self-explanatory. The person (with account name "''account''") has files totaling 1.6 gigabytes of data. The account's usage limit is 15 gigabytes.

== How to Get Yourself Under Quota on the ''CS Ugrad Net''==

If you're over quota, the only way to get back under is to delete or shrink files until your total disk usage is reduced below your limit.

You can use the <code>du</code> command line program (short for "d"isk "u"sage) to see how much space individual files or directories are using. One of the simplest ways to invoke it is to run the following command from your home directory:

du -h | sort -h

The above command will show you every directory in your home directory (and every subdirectory of them and every subdirectory of those and so on) and how much space it and all of its contents occupies, with the largest directories shown last. The directories containing the most data are probably the best candidates to start cleaning out.

Another useful command is the following:

du -sh * .??* | sort -h

This version of running the du command lists all directories ''and all files'' in the current directory and their sizes. (The ''previous'' version of running the du command shows all directories, not just the ones directly in the current directory, ''and'' it doesn't list files directly; they simply get added to the size tally for the directory they're in.)

:'''NOTE:''' With either of the two above commands, it might be helpful to pipe them to ''less'' or ''more'', or something similar, should your output be long enough to scroll by. For example...

:<pre>du -h | sort -h | less</pre>

Another use of du can provide some additional detail of what files are taking up the most space:

du -ha |sort -h |tail

=== If You Have .nfs Files ===

If, from the above list of commands, you run:

du -sh * .??* | sort -h

and you notice a file with a name starting with "<code>.nfs</code>" followed by a long string of numbers, you will want to remove it, as it can be a very large (and unwanted) file. And it's not a file you can use the <code>rm</code> command with (unlike other with other files.)

The .nfs file is created when some other file ''is deleted'' while a running program ''is still using'' that file. Our systems simply renames that other file (that you deleted) to <code>.nfs</code> (followed by a long string of numbers) while the program is still running. As soon as the program exits, the <code>.nfs</code> file will be removed. But, if the .nfs file remains in your directory, as mentioned, you cannot simply remove it with a <code>rm</code> command, as you would do with regular files. The .nfs file remains because there is some process/program open that is keeping the .nfs file in place. If you tried to directly remove the .nfs file that some process has open, there would be a replacement .nfs file created. So, you need to stop the program that is running that is keeping the .nfs file open.

If you need to figure out what program is using the file, you can use the <code>lsof</code> program, like this:

lsof .nfs''000000003114807500000002''

(Obviously, use the actual name of the file in your directory.) Its output will look something like this:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
pv 9671 example 1w REG 0,45 167772160 823427189 .nfs000000003114807500000002

The most useful information is at the beginning, giving the name and process ID of the running program.

''This will only work on the system running the program.'' If, for example, you started a program on our <code>ugradx</code> system, you would only see useful information from <code>lsof</code> if you also ran it on <code>ugradx</code>. If you ran it on, say, <code>ugradz</code>, it would still see the <code>.nfs</code> file (because all the ugrad systems see the same home directory folders), but it wouldn't be able to find what program was using it.

=== If You Can't Find any Large Files ===

Sometimes the <code>quota</code> program will say that you're using a lot of disk space, but the <code>du</code> command doesn't show anything large.

One common cause for this is because of a quirk in Unix filesystem behavior. If a you delete a file while it's in use by a running program, the file will disappear from the directory, ''but it will still exist, invisibly using disk space'' until the running program exits. Even worse, if the program writes data to this deleted file, the extra data gets counted against your quota, even though you can't see the file. (Usually when you delete a file that's in use you'll get a .nfs file, [[#If You Have .nfs Files|as described above]], but sometimes the file will just disappear entirely.)

You can use the <code>lsof</code> program to find files that have deen deleted but are still in use, like this:

lsof +aL1 /home

If you have any files in this state, it'll print something like this:

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NLINK NODE NAME
pv 16081 example 1w REG 0,45 159907840 0 823427190 /home/example/inuse (barley.cs.jhu.edu:/home)

That will show the name of the program and the location where the file used to be before it was deleted. If you don't have any other way to stop the program, you can usually terminate it with the <code>kill</code> command, like this:

kill ''16081''

For the number, use the process ID (PID) from <code>lsof</code>'s output.

''This will only work if you run <code>lsof</code> on the same system where the other program is running.'' You might need to log into several systems to check things if you've used more than one for your recent work.

=== If You Still Can't Reduce Your Disk Usage ===

If the system insists that you're over quota but you can't figure out why, you can always email us at [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.

== A Note on File Size and Disk Usage ==

On our systems, files are compressed before they're stored on disk. Consequently, the disk space used by a file (what you see if you run <kbd>du -sh <var>file</var></kbd>) is likely to be smaller than the amount of data stored in the file (which is what you see if you run <kbd>ls -lh <var>file</var></kbd>). Since our quotas are based on the actual amount of disk space used, the sizes shown by <code>du</code> are most relevant here. If you rely on just the sizes shown by <code>ls</code>, you might be misled about how much your quota is being affected by particular files.

== If You Need a Larger Quota on the ''CS Ugrad Net''==

If your class projects or research require more disk space than your quota will allow, please contact [mailto:support@cs.jhu.edu support@cs.jhu.edu] and detail the reasons your current quota is insufficient. (Note: Please ''do not'' request a larger disk quota to accommodate ''cloud drives'' such as '''Dropbox''' and '''Google Drive'''.) Please include the following information when requesting more disk space:

* Your CS username
* CS student status (ugrad? grad? concurrent?)
* Your JHED ID
* How much additional space you require.
* Name ''and'' section of class you're taking that's requiring the extra space.
* Name of the professor teaching the class.
* How long you need the increased quota. After that, your quota will be reduced to its normal level, and you will need to be below that level to write files to your directory.

''Quota increases are not guaranteed. Allow '''at least''' one full business day for your quota increase request to be processed.''

[[Category:Accounts]]
[[Category:Linux Clients]]

Notices

2025-08-22T16:09:41Z

Pip: /* OUTAGE 1: Linux Lab Systems Not Accessible During Upgrades */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 





== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 12:15 on Friday, all of our Linux clients have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage will start at 8:00 pm and is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access.


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2025-08-21T18:24:09Z

Pip: /* OUTAGE 1: Linux Lab Systems Not Accessible During Upgrades */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 





== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 2:30 pm on Thursday, ugradx, gradx, and all the lab computers (ugrad1 through ugrad24 and masters1 through masters16) have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage will start at 8:00 pm and is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access.


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2025-08-20T16:24:19Z

Pip: /* OUTAGE 1: Linux Lab Systems Not Accessible During Upgrades */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 





== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 12:30 on Wednesday, all lab computers (ugrad1 through ugrad24 and masters1 through masters16) have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage will start at 8:00 pm and is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access.


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2025-08-19T20:46:05Z

Pip: /* Outage 2: Networking Outage on the Malone Ground Floor */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 





== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 12:30 on Tuesday, all ugrad systems from ugrad1 through ugrad12 have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage will start at 8:00 pm and is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access.


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2025-08-19T20:28:16Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 





== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.
 

=== PLANNED CS IT SERVICE OUTAGES ===



==== '''OUTAGE 1:''' Linux Lab Systems Not Accessible During Upgrades====
:'''WHEN:''' Tuesday, August 19 through Friday, August 22

:'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

:'''UPDATE:''' As of about 12:30 on Tuesday, all ugrad systems from ugrad1 through ugrad12 have been upgraded.

:'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

:The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

:Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

==== '''Outage 2:''' Networking Outage on the Malone Ground Floor ====

:'''WHAT:''' WiFi and Ethernet connections will not be available on the ground floor of Malone Hall during an upcoming JHU-planned networking outage.

:'''WHEN:''' JHU's Planned Network Outage – Wednesday, August 27, 2025, from 8pm through midnight.

:'''DESCRIPTION:''' JHU is planning a network outage at Malone Hall to install new networking equipment. The outage is expected to last between two and four hours. During the outage, the wireless access points on the ground floor will be offline, as will most of the Ethernet jacks. Please be prepared to not have any network connectivity on the Malone ground floor during this time.

:Ethernet connections in the Malone server room, G29, will not be affected by this outage. Any servers in G29 should remain accessible. The Linux clients and Ethernet jacks in room G61, which contains the ground floor masters and undergrad labs, will not be affected either. (But any laptops brought into G61 during the outage probably won't be able to access the wireless network.)

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access.


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Notices

2025-08-19T16:25:23Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

== {{red|CS IT STAFF AVAILABILITY}} ==

* The CS IT Support staff is back in Malone Hall. Our group is working a hybrid schedule with some of us working remotely on certain days, while others of our team are on campus.
* We continue being available M-F, 8:30 to 5pm, but there may be certain times we might be online only.
* Therefore, please remember to email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for assistance.
* Also, please have [https://support.cs.jhu.edu/wiki/Zoom Zoom] available on your device(s), so that we can arrange to contact you using that method, as an alternative to in-person communication.
* For the time being, Steve DeBlasio, our accounts liaison, is providing a virtual version of his daily office hours for accounts, etc. Email [mailto:support@cs.jhu.edu support@cs.jhu.edu] for details.

 





== {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} ==

=== UNPLANNED CS IT SERVICE OUTAGES ===

:None at this time.

=== PLANNED CS IT SERVICE OUTAGES ===


'''WHEN:''' Tuesday, August 19 through Friday, August 22

'''WHAT: '''Subsets of the CS Linux clients will be down for upgrades over the course of the week.

'''UPDATE:''' As of about 12:30 on Tuesday, all ugrad systems from ugrad1 through ugrad12 have been upgraded.

'''DETAILS:''' We will be upgrading our Linux clients from Fedora 40 to Fedora 42. This will require having the clients offline during the upgrades. We'll do this in stages, so there will always be some clients available at all times.

The lab machines whose numbers are integer multiples of five (ugrad5, ugrad10, ugrad15, ugrad20, masters5, masters10, and masters15) have already been upgraded (those are the staging systems we mentioned in a recent email to the CS faculty and students), so those will remain available throughout the week. The upgrade schedule for the remainder of the systems will be as follows:

* On Tuesday, August 19, ugrad1 through ugrad12 (located in MH-122) will be upgraded (...except for ugrad5 and ugrad10, which are already done.)
* On Wednesday, August 20, ugrad13 through ugrad24 and masters1 through masters16 (located in MH-G61) will be upgraded (...except for ugrad15, ugrad20, masters5, masters10, and masters15, which are already done.)
* On Thursday, August 21, ugradx and gradx (remotely-accessible only) will be upgraded.
* On Friday, August 22, ugradz and gradz (remotely-accessible only) will be upgraded, along with any systems we were unable to upgrade earlier in the week.

Expect each system being upgraded to be unavailable between 9:00 am and 4:00 pm on the days for which it's scheduled. If a system remains unavailable after 4:00 pm on its scheduled day, this CS IT Support Wiki's Notices page will be updated with the appropriate information.

 

== {{red|CS COMPUTING LAB AVAILABILITY}} ==



:'''MH 122''' (CS Undergrad Lab/Collaboration room) is available for in-person access.


:'''MH G61''' (CS Masters/Ugrad Labs) is available for in-person access.

 

== {{red|AUDIO/VISUAL (A/V) OUTAGES}} ==
:None at this time.

[[Category:All]]

Third-Party Website Hosting with a CS Domain Name

2025-08-15T16:23:46Z

Pip: /* Process */

There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page hosting, like GitHub Pages or Google Sites, to more full-featured cloud platforms like Netlify, Heroku, Amazon Web Services, and Google Cloud Platform.

It is generally possible to use such third-party services in conjunction with a cs.jhu.edu hostname. For example, you could use <var>mycoursename</var>.cs.jhu.edu for course info served from a GitHub Pages site under your personal GitHub account. Any service that allows a DNS CNAME to point to their web server should let you use a cs.jhu.edu hostname in this way.

At this time, we only offer this service for CS Department faculty members.

== Process ==

# You must to set up the site yourself; CS IT Support staff are unable to provide assistance with this step
# Follow the service's custom domain instructions to see what DNS CNAME record you need to have added
#* CS IT Support staff may be able to assist you by pointing you to the right page in the service's documentation, but we can't promise we can help in every instance
# Fill out our [https://support.cs.jhu.edu/forms/ip-address-application IP address application]
#* Put the cs.jhu.edu hostname you want in the “Requested Machine Name” field
#* Put information about the CNAME record you need in the comment field
#* Add other information as appropriate (e.g. put in your contact information)
#* If a field is required but not applicable to this (e.g. the “Will you use DHCP” field), just put anything in that field

We'll let you know when things are set up on our end.

[[Category:Webpages and Webservices]]

Third-Party Website Hosting with a CS Domain Name

2025-08-15T13:45:15Z

Pip:

There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page hosting, like GitHub Pages or Google Sites, to more full-featured cloud platforms like Netlify, Heroku, Amazon Web Services, and Google Cloud Platform.

It is generally possible to use such third-party services in conjunction with a cs.jhu.edu hostname. For example, you could use <var>mycoursename</var>.cs.jhu.edu for course info served from a GitHub Pages site under your personal GitHub account. Any service that allows a DNS CNAME to point to their web server should let you use a cs.jhu.edu hostname in this way.

At this time, we only offer this service for CS Department faculty members.

== Process ==

# You must to set up the site yourself; CS IT Support staff are unable to provide assistance with this step
# Follow the service's custom domain instructions to see what DNS CNAME record you need to have added
# Fill out our [https://support.cs.jhu.edu/forms/ip-address-application IP address application]
#* Put the cs.jhu.edu hostname you want in the “Requested Machine Name” field
#* Put information about the CNAME record you need in the comment field
#* Add other information as appropriate (e.g. put in your contact information)
#* If a field is required but not applicable to this (e.g. the “Will you use DHCP” field), just put anything in that field

We'll let you know when things are set up on our end.

[[Category:Webpages and Webservices]]

Third-Party Website Hosting with a CS Domain Name

2025-08-15T13:39:52Z

Pip:

There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page hosting, like GitHub Pages or Google Sites, to more full-featured cloud platforms like Netlify or Heroku.

It is generally possible to use such third-party services in conjunction with a cs.jhu.edu hostname. For example, you could use <var>mycoursename</var>.cs.jhu.edu for course info served from a GitHub Pages site under your personal GitHub account. Any service that allows a DNS CNAME to point to their web server should let you use a cs.jhu.edu hostname in this way.

At this time, we only offer this service for CS Department faculty members.

== Process ==

# You must to set up the site yourself; CS IT Support staff are unable to provide assistance with this step
# Follow the service's custom domain instructions to see what DNS CNAME record you need to have added
# Fill out our [https://support.cs.jhu.edu/forms/ip-address-application IP address application]
#* Put the cs.jhu.edu hostname you want in the “Requested Machine Name” field
#* Put information about the CNAME record you need in the comment field
#* Add other information as appropriate (e.g. put in your contact information)
#* If a field is required but not applicable to this (e.g. the “Will you use DHCP” field), just put anything in that field

We'll let you know when things are set up on our end.

[[Category:Webpages and Webservices]]

Redirecting A CS URL To A Github Site

2025-08-15T13:38:25Z

Pip:

If you're a [https://www.cs.jhu.edu/faculty/ CS faculty member] with a [https://docs.github.com/en/pages/getting-started-with-github-pages/creating-a-github-pages-site GitHub Pages] site for CS Department–related work (research or teaching), but would rather have a CS URL instead that points to the GitHub Pages site, we can help with that.

Please follow our instructions for [[Third-Party Website Hosting with a CS Domain Name]]. The GitHub documentation for your site should be the “[https://docs.github.com/en/pages/configuring-a-custom-domain-for-your-github-pages-site/managing-a-custom-domain-for-your-github-pages-site#configuring-a-subdomain Configuring a Subdomain]” section of their custom domain documentation.

[[Category:Webpages and Webservices]]

Third-Party Website Hosting with a CS Domain Name

2025-08-15T13:33:57Z

Pip: Created page with "There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page h..."

There are a number of website hosting services outside of Hopkins that people sometimes want to use for their CS Department–related websites. These range from static page hosting, like GitHub Pages or Google Sites, to more full-featured cloud platforms like Heroku.

It is generally possible to use such third-party services in conjunction with a cs.jhu.edu hostname. For example, you could use <var>mycoursename</var>.cs.jhu.edu for course info served from a GitHub Pages site under your personal GitHub account. Any service that allows a DNS CNAME to point to their web server should let you use a cs.jhu.edu hostname in this way.

At this time, we only offer this service for CS Department faculty members.

== Process ==

# You must to set up the site yourself; CS IT Support staff are unable to provide assistance with this step
# Follow the service's custom domain instructions to see what DNS CNAME record you need to have added
# Fill out our [https://support.cs.jhu.edu/forms/ip-address-application IP address application]
#* Put the cs.jhu.edu hostname you want in the “Requested Machine Name” field
#* Put information about the CNAME record you need in the comment field
#* Add other information as appropriate (e.g. put in your contact information)
#* If a field is required but not applicable to this (e.g. the “Will you use DHCP” field), just put anything in that field

We'll let you know when things are set up on our end.

[[Category:Webpages and Webservices]]

Notices

2025-08-12T15:27:01Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2025-08-06T20:10:21Z

Pip: /* PLANNED CS IT SERVICE OUTAGES */

Notices

2025-08-06T14:38:12Z

Pip: /* {{red|CS IT SERVICE OUTAGES (Unplanned & Planned)}} */

Notices

2025-08-01T13:06:47Z

Pip: /* UNPLANNED CS IT SERVICE OUTAGES */ ugrad7 and 10 are down

Malone G29 Server Room

2025-07-16T15:27:32Z

Pip: /* Power */

The Computer Science Department has a server room in Malone Hall Room G29. This page is for CS faculty/researchers who have already been allocated space in that room or want to request space in the room. It also describes how to make the best use of your space allocation.

Please read the below sections first. Then, if you would like your server hosted in our server room or have questions that are not answered here or need to make arrangements with us if you've been allocated space in the server room, please email us at {{mailto|support}}.

== Services Provided (and Not Provided) by CS IT Staff ==

=== Things We Will Do for You ===

CS IT will:

* Provide space on a rack for your equipment, possibly on a rack shared with other CS faculty
* Provide network access for your equipment (see [[#Networking|Networking]] below)
* Provide power access for your equipment (see [[#Power|Power]] below)
* Provide you and your designees J-Card access to the room
* Add you to a ''Malone server room mailing list'' for server room-related announcements, etc.
** (However, you should continue to check the CS IT Support Wiki [[Notices]] page if you experience issues such as network, etc. that could be affecting your systems in the server room.)

=== Things You Will Need to Do Yourself ===

CS IT will ''not'':

* Install your systems on the rack
* Make network or power connections between your systems and our equipment on the rack
* Administer your systems

{{messagebox|'''NOTE:''' CS IT Support does not administer research systems. Please see our [[Services Provided By CS IT|Scope Of Services]] and [[:Category:Research Computing|Research Computing]] pages for more details.|type=warning}}

== Physical Space ==

Each rack is labeled with a letter and number. Within each rack, space is divided vertically into numbered "rack units". We will provide you the rack letter/number combo and the range of RUs available to you.

== Airflow/Cooling ==

The server room is set up in a ''"hot aisle/cold aisle"'' configuration. The front of each rack, which is the end with the single, wider door, faces a "cold aisle". The cold aisles are also marked by perforations in the floor tiles. Cold air from the air conditioning units enters the aisles through these perforations. The back of each rack faces a "hot aisle", which does not have perforated floor tiles.

When installing equipment in your rack, ''you should orient the equipment so that the fans pull air in from the cold aisle and exhaust air out to the hot aisle.'' This ensures good cooling efficiency for the entire room. Equipment installed backwards may overheat and may cause adjacent equipment to also overheat.

== Networking ==

Each rack has a switch with ports labeled for the CS public grad net and the CS private grad net. (See [[Networking at CS - Overview|our networking overview]] for more information on those networks.) If you need another network, please ask; we may be able to accommodate the request.

You will need to follow [[Requesting a Static IP Address on the CS Network|our procedure for requesting static IP addresses]] for your equipment, in addition to connecting the equipment to the correct ports on the switch.

Our network connections are '''1 Gigabit''' Ethernet using RJ-45 connectors. If you need other accommodations, please contact us and we'll see what arrangements we can make.

Please do not use any of the switch ports labeled "Reserved", nor any of the unlabeled ports.

== Power ==

Each rack has several power distribution units (PDUs). Most racks have:

* Two 120V PDUs with NEMA 15/20 amp outlets. (The 15A outlets are the standard household receptacle.)
* One 208V PDU with a few C19 outlets and several more C13 outlets.

Some racks have fewer PDUs because of space limitations. You can check the labels on the rack's PDUs to see what voltages they are.

Each PDU has a display showing the amount of current it is supplying at the moment, in amps. The limits for the PDUs are:

* The 120V PDUs may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
* The 120V PDUs may ''never'' exceed 20 amps, for any period of time
* The 208V PDUs have two banks of outlets:
** Each bank may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
** Each bank may ''never'' exceed 20 amps, for any period of time
** The entire PDU may only exceed 24 amps for short periods of time (no more than an hour per day, in total)
** The entire PDU may ''never'' exceed 30 amps, for any period of time

The 208V PDU on rack B4 only has one outlet bank, and has limits corresponding to a single 208V PDU bank: no more than 16 amps in continuous usage, and no more than 20 amps at all.

The two-bank PDUs have LEDs showing which bank's current is being displayed at the moment. If both LEDs are lit, it's showing the PDU's total power usage. Press the "Select" button to cycle the display among the banks and the PDU.

We do not assign PDUs to individual faculty members, nor do we assign equipment to specific PDUs. This means:

# You can choose which PDU your equipment plugs into, subject to your equipment's voltage requirements, of course.
# Other faculty members might be using the same PDU as you. You might need to coordinate overall power usage with those other faculty members.

== Access to the Server Room ==

Server room access is controlled by J-Card. In order to grant someone access, the faculty owner of the rack space should {{mailto|support|email us}} and request it. The request needs to contain the name and JHED ID of the person who should be granted access, as well as an estimate of how long you expect the person to be using the room.

== Other Notes ==

* '''Do ''not'' prop the door to the server room open.''' We are notified any time the door stays open for too long. If you expect to need to door to remain open for some period of time, please {{mailto|support|email us}} ahead of time to let us know.

* The server room is fairly loud. If you want to use ear protection while you're working there, you can use one of the headsets that are hanging on the wall all the way to the right after you enter the room. Please return the headsets to their hangers when you're done with them.

* There is a "crash cart" at the back of the room with a monitor, keyboard, and mouse on it. You can use it to connect a display to your servers on a temporary basis. Please return it to its storage area when you're done.

* '''''Please turn the server room lights off when you're done in the room.'''''

[[Category:Malone Hall]]
[[Category:Misc]]
[[Category:Research Computing]]

Malone G29 Server Room

2025-07-16T15:21:11Z

Pip: /* Power */

The Computer Science Department has a server room in Malone Hall Room G29. This page is for CS faculty/researchers who have already been allocated space in that room or want to request space in the room. It also describes how to make the best use of your space allocation.

Please read the below sections first. Then, if you would like your server hosted in our server room or have questions that are not answered here or need to make arrangements with us if you've been allocated space in the server room, please email us at {{mailto|support}}.

== Services Provided (and Not Provided) by CS IT Staff ==

=== Things We Will Do for You ===

CS IT will:

* Provide space on a rack for your equipment, possibly on a rack shared with other CS faculty
* Provide network access for your equipment (see [[#Networking|Networking]] below)
* Provide power access for your equipment (see [[#Power|Power]] below)
* Provide you and your designees J-Card access to the room
* Add you to a ''Malone server room mailing list'' for server room-related announcements, etc.
** (However, you should continue to check the CS IT Support Wiki [[Notices]] page if you experience issues such as network, etc. that could be affecting your systems in the server room.)

=== Things You Will Need to Do Yourself ===

CS IT will ''not'':

* Install your systems on the rack
* Make network or power connections between your systems and our equipment on the rack
* Administer your systems

{{messagebox|'''NOTE:''' CS IT Support does not administer research systems. Please see our [[Services Provided By CS IT|Scope Of Services]] and [[:Category:Research Computing|Research Computing]] pages for more details.|type=warning}}

== Physical Space ==

Each rack is labeled with a letter and number. Within each rack, space is divided vertically into numbered "rack units". We will provide you the rack letter/number combo and the range of RUs available to you.

== Airflow/Cooling ==

The server room is set up in a ''"hot aisle/cold aisle"'' configuration. The front of each rack, which is the end with the single, wider door, faces a "cold aisle". The cold aisles are also marked by perforations in the floor tiles. Cold air from the air conditioning units enters the aisles through these perforations. The back of each rack faces a "hot aisle", which does not have perforated floor tiles.

When installing equipment in your rack, ''you should orient the equipment so that the fans pull air in from the cold aisle and exhaust air out to the hot aisle.'' This ensures good cooling efficiency for the entire room. Equipment installed backwards may overheat and may cause adjacent equipment to also overheat.

== Networking ==

Each rack has a switch with ports labeled for the CS public grad net and the CS private grad net. (See [[Networking at CS - Overview|our networking overview]] for more information on those networks.) If you need another network, please ask; we may be able to accommodate the request.

You will need to follow [[Requesting a Static IP Address on the CS Network|our procedure for requesting static IP addresses]] for your equipment, in addition to connecting the equipment to the correct ports on the switch.

Our network connections are '''1 Gigabit''' Ethernet using RJ-45 connectors. If you need other accommodations, please contact us and we'll see what arrangements we can make.

Please do not use any of the switch ports labeled "Reserved", nor any of the unlabeled ports.

== Power ==

Each rack has several power distribution units (PDUs). Most racks have:

* Two 120V PDUs with NEMA 15/20 amp outlets. (The 15A outlets are the standard household receptacle.)
* One 208V PDU with a few C19 outlets and several more C13 outlets.

Some racks have fewer PDUs because of space limitations. You can check the labels on the rack's PDUs to see what voltages they are.

Each PDU has a display showing the amount of current it is supplying at the moment, in amps. The limits for the PDUs are:

* The 120V PDUs may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
* The 120V PDUs may ''never'' exceed 20 amps, for any period of time
* The 208V PDUs have two banks of outlets:
** Each bank may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
** Each bank may ''never'' exceed 20 amps, for any period of time
** The entire PDU may only exceed 24 amps for short periods of time (no more than an hour per day, in total)
** The entire PDU may ''never'' exceed 30 amps, for any period of time

The 208V PDU on rack B4 only has one outlet bank, and has limits corresponding to a single 208V PDU bank: no more than 16 amps in continuous usage, and no more than 20 amps at all.

The two-bank PDUs have LEDs showing which bank's current is being displayed at the moment. If both LEDs are lit, it's showing the PDU's total power usage. Press the "Select" button to cycle the display among the banks and the PDU.

Note that we do not plan to designate which PDU your racked equipment will use. You can choose that. However, you do not have exclusive use to the PDU you choose. You might need to coordinate power usage with other faculty members using the same PDU.

== Access to the Server Room ==

Server room access is controlled by J-Card. In order to grant someone access, the faculty owner of the rack space should {{mailto|support|email us}} and request it. The request needs to contain the name and JHED ID of the person who should be granted access, as well as an estimate of how long you expect the person to be using the room.

== Other Notes ==

* '''Do ''not'' prop the door to the server room open.''' We are notified any time the door stays open for too long. If you expect to need to door to remain open for some period of time, please {{mailto|support|email us}} ahead of time to let us know.

* The server room is fairly loud. If you want to use ear protection while you're working there, you can use one of the headsets that are hanging on the wall all the way to the right after you enter the room. Please return the headsets to their hangers when you're done with them.

* There is a "crash cart" at the back of the room with a monitor, keyboard, and mouse on it. You can use it to connect a display to your servers on a temporary basis. Please return it to its storage area when you're done.

* '''''Please turn the server room lights off when you're done in the room.'''''

[[Category:Malone Hall]]
[[Category:Misc]]
[[Category:Research Computing]]

Malone G29 Server Room

2025-07-16T15:19:02Z

Pip: /* Power */

The Computer Science Department has a server room in Malone Hall Room G29. This page is for CS faculty/researchers who have already been allocated space in that room or want to request space in the room. It also describes how to make the best use of your space allocation.

Please read the below sections first. Then, if you would like your server hosted in our server room or have questions that are not answered here or need to make arrangements with us if you've been allocated space in the server room, please email us at {{mailto|support}}.

== Services Provided (and Not Provided) by CS IT Staff ==

=== Things We Will Do for You ===

CS IT will:

* Provide space on a rack for your equipment, possibly on a rack shared with other CS faculty
* Provide network access for your equipment (see [[#Networking|Networking]] below)
* Provide power access for your equipment (see [[#Power|Power]] below)
* Provide you and your designees J-Card access to the room
* Add you to a ''Malone server room mailing list'' for server room-related announcements, etc.
** (However, you should continue to check the CS IT Support Wiki [[Notices]] page if you experience issues such as network, etc. that could be affecting your systems in the server room.)

=== Things You Will Need to Do Yourself ===

CS IT will ''not'':

* Install your systems on the rack
* Make network or power connections between your systems and our equipment on the rack
* Administer your systems

{{messagebox|'''NOTE:''' CS IT Support does not administer research systems. Please see our [[Services Provided By CS IT|Scope Of Services]] and [[:Category:Research Computing|Research Computing]] pages for more details.|type=warning}}

== Physical Space ==

Each rack is labeled with a letter and number. Within each rack, space is divided vertically into numbered "rack units". We will provide you the rack letter/number combo and the range of RUs available to you.

== Airflow/Cooling ==

The server room is set up in a ''"hot aisle/cold aisle"'' configuration. The front of each rack, which is the end with the single, wider door, faces a "cold aisle". The cold aisles are also marked by perforations in the floor tiles. Cold air from the air conditioning units enters the aisles through these perforations. The back of each rack faces a "hot aisle", which does not have perforated floor tiles.

When installing equipment in your rack, ''you should orient the equipment so that the fans pull air in from the cold aisle and exhaust air out to the hot aisle.'' This ensures good cooling efficiency for the entire room. Equipment installed backwards may overheat and may cause adjacent equipment to also overheat.

== Networking ==

Each rack has a switch with ports labeled for the CS public grad net and the CS private grad net. (See [[Networking at CS - Overview|our networking overview]] for more information on those networks.) If you need another network, please ask; we may be able to accommodate the request.

You will need to follow [[Requesting a Static IP Address on the CS Network|our procedure for requesting static IP addresses]] for your equipment, in addition to connecting the equipment to the correct ports on the switch.

Our network connections are '''1 Gigabit''' Ethernet using RJ-45 connectors. If you need other accommodations, please contact us and we'll see what arrangements we can make.

Please do not use any of the switch ports labeled "Reserved", nor any of the unlabeled ports.

== Power ==

Each rack has several power distribution units (PDUs). Most racks have:

* Two 120V PDUs with NEMA 15/20 amp outlets. (The 15A outlets are the standard household receptacle.)
* One 208V PDU with a few C19 outlets and several more C13 outlets.

Some racks have fewer PDUs because of space limitations. You can check the labels on the rack's PDUs to see what voltages they are.

Each PDU has a display showing the amount of current it is supplying at the moment, in amps. The limits for the PDUs are:

* The 120V PDUs may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
* The 120V PDUs may ''never'' exceed 20 amps, for any period of time
* The 208V PDUs have two banks of outlets:
** Each bank may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
** Each bank may ''never'' exceed 20 amps, for any period of time
** The entire PDU may only exceed 24 amps for short periods of time (no more than an hour per day, in total)
** The entire PDU may ''never'' exceed 30 amps, for any period of time

The 208V PDU on rack B4 only has one outlet bank, and has limits corresponding to a single 208V PDU bank: no more than 16 amps in continuous usage, and no more than 20 amps at all.

The two-bank PDUs have LEDs showing which bank's current is being displayed at the moment. If both LEDs are lit, it's showing the PDU's total power usage. Press the "Select" button to cycle the display between the banks and the PDU.

Note that we do not plan to designate which PDU your racked equipment will use. You can choose that. However, you do not have exclusive use to the PDU you choose. You might need to coordinate power usage with other faculty members using the same PDU.

== Access to the Server Room ==

Server room access is controlled by J-Card. In order to grant someone access, the faculty owner of the rack space should {{mailto|support|email us}} and request it. The request needs to contain the name and JHED ID of the person who should be granted access, as well as an estimate of how long you expect the person to be using the room.

== Other Notes ==

* '''Do ''not'' prop the door to the server room open.''' We are notified any time the door stays open for too long. If you expect to need to door to remain open for some period of time, please {{mailto|support|email us}} ahead of time to let us know.

* The server room is fairly loud. If you want to use ear protection while you're working there, you can use one of the headsets that are hanging on the wall all the way to the right after you enter the room. Please return the headsets to their hangers when you're done with them.

* There is a "crash cart" at the back of the room with a monitor, keyboard, and mouse on it. You can use it to connect a display to your servers on a temporary basis. Please return it to its storage area when you're done.

* '''''Please turn the server room lights off when you're done in the room.'''''

[[Category:Malone Hall]]
[[Category:Misc]]
[[Category:Research Computing]]

Malone G29 Server Room

2025-07-16T15:18:27Z

Pip: /* Power */ Rack C4 only has 120V PDUs

The Computer Science Department has a server room in Malone Hall Room G29. This page is for CS faculty/researchers who have already been allocated space in that room or want to request space in the room. It also describes how to make the best use of your space allocation.

Please read the below sections first. Then, if you would like your server hosted in our server room or have questions that are not answered here or need to make arrangements with us if you've been allocated space in the server room, please email us at {{mailto|support}}.

== Services Provided (and Not Provided) by CS IT Staff ==

=== Things We Will Do for You ===

CS IT will:

* Provide space on a rack for your equipment, possibly on a rack shared with other CS faculty
* Provide network access for your equipment (see [[#Networking|Networking]] below)
* Provide power access for your equipment (see [[#Power|Power]] below)
* Provide you and your designees J-Card access to the room
* Add you to a ''Malone server room mailing list'' for server room-related announcements, etc.
** (However, you should continue to check the CS IT Support Wiki [[Notices]] page if you experience issues such as network, etc. that could be affecting your systems in the server room.)

=== Things You Will Need to Do Yourself ===

CS IT will ''not'':

* Install your systems on the rack
* Make network or power connections between your systems and our equipment on the rack
* Administer your systems

{{messagebox|'''NOTE:''' CS IT Support does not administer research systems. Please see our [[Services Provided By CS IT|Scope Of Services]] and [[:Category:Research Computing|Research Computing]] pages for more details.|type=warning}}

== Physical Space ==

Each rack is labeled with a letter and number. Within each rack, space is divided vertically into numbered "rack units". We will provide you the rack letter/number combo and the range of RUs available to you.

== Airflow/Cooling ==

The server room is set up in a ''"hot aisle/cold aisle"'' configuration. The front of each rack, which is the end with the single, wider door, faces a "cold aisle". The cold aisles are also marked by perforations in the floor tiles. Cold air from the air conditioning units enters the aisles through these perforations. The back of each rack faces a "hot aisle", which does not have perforated floor tiles.

When installing equipment in your rack, ''you should orient the equipment so that the fans pull air in from the cold aisle and exhaust air out to the hot aisle.'' This ensures good cooling efficiency for the entire room. Equipment installed backwards may overheat and may cause adjacent equipment to also overheat.

== Networking ==

Each rack has a switch with ports labeled for the CS public grad net and the CS private grad net. (See [[Networking at CS - Overview|our networking overview]] for more information on those networks.) If you need another network, please ask; we may be able to accommodate the request.

You will need to follow [[Requesting a Static IP Address on the CS Network|our procedure for requesting static IP addresses]] for your equipment, in addition to connecting the equipment to the correct ports on the switch.

Our network connections are '''1 Gigabit''' Ethernet using RJ-45 connectors. If you need other accommodations, please contact us and we'll see what arrangements we can make.

Please do not use any of the switch ports labeled "Reserved", nor any of the unlabeled ports.

== Power ==

Each rack has several power distribution units (PDUs). Most racks have:

* Two 120V PDUs with NEMA 15/20 amp outlets. (The 15A outlets are the standard household receptacle.)
* One 208V PDU with a few C19 outlets and several more C13 outlets.

Some racks have fewer PDUs because of space limitations. You can check the labels on the rack's PDUs to see what voltages they are.

Each PDU has a display showing the amount of current it is currently supplying, in amps. The limits for the PDUs are:

* The 120V PDUs may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
* The 120V PDUs may ''never'' exceed 20 amps, for any period of time
* The 208V PDUs have two banks of outlets:
** Each bank may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
** Each bank may ''never'' exceed 20 amps, for any period of time
** The entire PDU may only exceed 24 amps for short periods of time (no more than an hour per day, in total)
** The entire PDU may ''never'' exceed 30 amps, for any period of time

The 208V PDU on rack B4 only has one outlet bank, and has limits corresponding to a single 208V PDU bank: no more than 16 amps in continuous usage, and no more than 20 amps at all.

The two-bank PDUs have LEDs showing which bank's current is being displayed at the moment. If both LEDs are lit, it's showing the PDU's total power usage. Press the "Select" button to cycle the display between the banks and the PDU.

Note that we do not plan to designate which PDU your racked equipment will use. You can choose that. However, you do not have exclusive use to the PDU you choose. You might need to coordinate power usage with other faculty members using the same PDU.

== Access to the Server Room ==

Server room access is controlled by J-Card. In order to grant someone access, the faculty owner of the rack space should {{mailto|support|email us}} and request it. The request needs to contain the name and JHED ID of the person who should be granted access, as well as an estimate of how long you expect the person to be using the room.

== Other Notes ==

* '''Do ''not'' prop the door to the server room open.''' We are notified any time the door stays open for too long. If you expect to need to door to remain open for some period of time, please {{mailto|support|email us}} ahead of time to let us know.

* The server room is fairly loud. If you want to use ear protection while you're working there, you can use one of the headsets that are hanging on the wall all the way to the right after you enter the room. Please return the headsets to their hangers when you're done with them.

* There is a "crash cart" at the back of the room with a monitor, keyboard, and mouse on it. You can use it to connect a display to your servers on a temporary basis. Please return it to its storage area when you're done.

* '''''Please turn the server room lights off when you're done in the room.'''''

[[Category:Malone Hall]]
[[Category:Misc]]
[[Category:Research Computing]]

Malone G29 Server Room

2025-07-15T17:11:40Z

Pip: /* Power */

The Computer Science Department has a server room in Malone Hall Room G29. This page is for CS faculty/researchers who have already been allocated space in that room or want to request space in the room. It also describes how to make the best use of your space allocation.

Please read the below sections first. Then, if you would like your server hosted in our server room or have questions that are not answered here or need to make arrangements with us if you've been allocated space in the server room, please email us at {{mailto|support}}.

== Services Provided (and Not Provided) by CS IT Staff ==

=== Things We Will Do for You ===

CS IT will:

* Provide space on a rack for your equipment, possibly on a rack shared with other CS faculty
* Provide network access for your equipment (see [[#Networking|Networking]] below)
* Provide power access for your equipment (see [[#Power|Power]] below)
* Provide you and your designees J-Card access to the room
* Add you to a ''Malone server room mailing list'' for server room-related announcements, etc.
** (However, you should continue to check the CS IT Support Wiki [[Notices]] page if you experience issues such as network, etc. that could be affecting your systems in the server room.)

=== Things You Will Need to Do Yourself ===

CS IT will ''not'':

* Install your systems on the rack
* Make network or power connections between your systems and our equipment on the rack
* Administer your systems

{{messagebox|'''NOTE:''' CS IT Support does not administer research systems. Please see our [[Services Provided By CS IT|Scope Of Services]] and [[:Category:Research Computing|Research Computing]] pages for more details.|type=warning}}

== Physical Space ==

Each rack is labeled with a letter and number. Within each rack, space is divided vertically into numbered "rack units". We will provide you the rack letter/number combo and the range of RUs available to you.

== Airflow/Cooling ==

The server room is set up in a ''"hot aisle/cold aisle"'' configuration. The front of each rack, which is the end with the single, wider door, faces a "cold aisle". The cold aisles are also marked by perforations in the floor tiles. Cold air from the air conditioning units enters the aisles through these perforations. The back of each rack faces a "hot aisle", which does not have perforated floor tiles.

When installing equipment in your rack, ''you should orient the equipment so that the fans pull air in from the cold aisle and exhaust air out to the hot aisle.'' This ensures good cooling efficiency for the entire room. Equipment installed backwards may overheat and may cause adjacent equipment to also overheat.

== Networking ==

Each rack has a switch with ports labeled for the CS public grad net and the CS private grad net. (See [[Networking at CS - Overview|our networking overview]] for more information on those networks.) If you need another network, please ask; we may be able to accommodate the request.

You will need to follow [[Requesting a Static IP Address on the CS Network|our procedure for requesting static IP addresses]] for your equipment, in addition to connecting the equipment to the correct ports on the switch.

Our network connections are '''1 Gigabit''' Ethernet using RJ-45 connectors. If you need other accommodations, please contact us and we'll see what arrangements we can make.

Please do not use any of the switch ports labeled "Reserved", nor any of the unlabeled ports.

== Power ==

Each rack has several power distribution units (PDUs). Most racks have:

* Two 120V PDUs with NEMA 15/20 amp outlets. (The 15A outlets are the standard household receptacle.)
* One 208V PDU with a few C19 outlets and several more C13 outlets.

Some racks have fewer PDUs because of space limitations, but every rack should have at least one 120V and one 208V PDU.

Each PDU has a display showing the amount of current it is currently supplying, in amps. The limits for the PDUs are:

* The 120V PDUs may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
* The 120V PDUs may ''never'' exceed 20 amps, for any period of time
* The 208V PDUs have two banks of outlets:
** Each bank may only exceed 16 amps for short periods of time (no more than an hour per day, in total)
** Each bank may ''never'' exceed 20 amps, for any period of time
** The entire PDU may only exceed 24 amps for short periods of time (no more than an hour per day, in total)
** The entire PDU may ''never'' exceed 30 amps, for any period of time

The 208V PDU on rack B4 only has one outlet bank, and has limits corresponding to a single 208V PDU bank: no more than 16 amps in continuous usage, and no more than 20 amps at all.

The two-bank PDUs have LEDs showing which bank's current is being displayed at the moment. If both LEDs are lit, it's showing the PDU's total power usage. Press the "Select" button to cycle the display between the banks and the PDU.

Note that we cannot guarantee each faculty member a designated PDU. You might need to coordinate power usage with other faculty members using the same PDU.

== Access to the Server Room ==

Server room access is controlled by J-Card. In order to grant someone access, the faculty owner of the rack space should {{mailto|support|email us}} and request it. The request needs to contain the name and JHED ID of the person who should be granted access, as well as an estimate of how long you expect the person to be using the room.

== Other Notes ==

Do not prop the door to the server room open. We are notified any time the door stays open for too long. If you expect to need to door to remain open for some period of time, please {{mailto|support|email us}} ahead of time to let us know.

The server room is fairly loud. If you want to use ear protection while you're working there, you can use one of the headsets that are hanging on the wall all the way to the right after you enter the room. Please return the headsets to their hangers when you're done with them.

There is a "crash cart" at the back of the room with a monitor, keyboard, and mouse on it. You can use it to connect a display to your servers on a temporary basis. Please return it to its storage area when you're done.

'''''Please turn the server room lights off when you're done in the room.'''''

[[Category:Malone Hall]]
[[Category:Misc]]
[[Category:Research Computing]]

Malone G29 Server Room

2025-07-15T17:04:25Z

Pip: /* Networking */

The Computer Science Department has a server room in Malone Hall Room G29. This page is for CS faculty/researchers who have already been allocated space in that room or want to request space in the room. It also describes how to make the best use of your space allocation.

Please read the below sections first. Then, if you would like your server hosted in our server room or have questions that are not answered here or need to make arrangements with us if you've been allocated space in the server room, please email us at {{mailto|support}}.

== Services Provided (and Not Provided) by CS IT Staff ==

=== Things We Will Do for You ===

CS IT will:

* Provide space on a rack for your equipment, possibly on a rack shared with other CS faculty
* Provide network access for your equipment (see [[#Networking|Networking]] below)
* Provide power access for your equipment (see [[#Power|Power]] below)
* Provide you and your designees J-Card access to the room
* Add you to a ''Malone server room mailing list'' for server room-related announcements, etc.
** (However, you should continue to check the CS IT Support Wiki [[Notices]] page if you experience issues such as network, etc. that could be affecting your systems in the server room.)

=== Things You Will Need to Do Yourself ===

CS IT will ''not'':

* Install your systems on the rack
* Make network or power connections between your systems and our equipment on the rack
* Administer your systems

{{messagebox|'''NOTE:''' CS IT Support does not administer research systems. Please see our [[Services Provided By CS IT|Scope Of Services]] and [[:Category:Research Computing|Research Computing]] pages for more details.|type=warning}}

== Physical Space ==

Each rack is labeled with a letter and number. Within each rack, space is divided vertically into numbered "rack units". We will provide you the rack letter/number combo and the range of RUs available to you.

== Airflow/Cooling ==

The server room is set up in a ''"hot aisle/cold aisle"'' configuration. The front of each rack, which is the end with the single, wider door, faces a "cold aisle". The cold aisles are also marked by perforations in the floor tiles. Cold air from the air conditioning units enters the aisles through these perforations. The back of each rack faces a "hot aisle", which does not have perforated floor tiles.

When installing equipment in your rack, ''you should orient the equipment so that the fans pull air in from the cold aisle and exhaust air out to the hot aisle.'' This ensures good cooling efficiency for the entire room. Equipment installed backwards may overheat and may cause adjacent equipment to also overheat.

== Networking ==

Each rack has a switch with ports labeled for the CS public grad net and the CS private grad net. (See [[Networking at CS - Overview|our networking overview]] for more information on those networks.) If you need another network, please ask; we may be able to accommodate the request.

You will need to follow [[Requesting a Static IP Address on the CS Network|our procedure for requesting static IP addresses]] for your equipment, in addition to connecting the equipment to the correct ports on the switch.

Our network connections are '''1 Gigabit''' Ethernet using RJ-45 connectors. If you need other accommodations, please contact us and we'll see what arrangements we can make.

Please do not use any of the switch ports labeled "Reserved", nor any of the unlabeled ports.

== Power ==

Each rack has several power distribution units (PDUs). Most racks have:

* Two 120V PDUs with NEMA 15/20 amp outlets. (The 15A outlets are the standard household receptacle.)
* One 208V PDU with a few C19 outlets and several more C13 outlets.

Some racks have fewer PDUs because of space limitations, but every rack should have at least one 120V and one 208V PDU.

Each PDU has a display showing the amount of current it is currently supplying, in amps. The limits for the PDUs are:

* The 120V PDUs may only exceed 16 amps for short periods of time (no more than an hour per day)
* The 120V PDUs may ''never'' exceed 20 amps, for any period of time
* The 208V PDUs have two banks of outlets:
** Each bank may only exceed 16 amps for short periods of time (no more than an hour per day)
** Each bank may ''never'' exceed 20 amps, for any period of time
** The entire PDU may only exceed 24 amps for short periods of time (no more than an hour per day)
** The entire PDU may ''never'' exceed 30 amps, for any period of time

The 208V PDU on rack B4 only has one outlet bank, and has limits corresponding to a single 208V PDU bank: no more than 16 amps in continuous usage, and no more than 20 amps at all.

The two-bank PDUs have LEDs showing which bank's current is being displayed at the moment. If both LEDs are lit, it's showing the PDU's total power usage. Press the "Select" button to cycle the display between the banks and the PDU.

Note that we cannot guarantee each faculty member a designated PDU. You might need to coordinate power usage with other faculty members using the same PDU.

== Access to the Server Room ==

Server room access is controlled by J-Card. In order to grant someone access, the faculty owner of the rack space should {{mailto|support|email us}} and request it. The request needs to contain the name and JHED ID of the person who should be granted access, as well as an estimate of how long you expect the person to be using the room.

== Other Notes ==

Do not prop the door to the server room open. We are notified any time the door stays open for too long. If you expect to need to door to remain open for some period of time, please {{mailto|support|email us}} ahead of time to let us know.

The server room is fairly loud. If you want to use ear protection while you're working there, you can use one of the headsets that are hanging on the wall all the way to the right after you enter the room. Please return the headsets to their hangers when you're done with them.

There is a "crash cart" at the back of the room with a monitor, keyboard, and mouse on it. You can use it to connect a display to your servers on a temporary basis. Please return it to its storage area when you're done.

'''''Please turn the server room lights off when you're done in the room.'''''

[[Category:Malone Hall]]
[[Category:Misc]]
[[Category:Research Computing]]

Malone G29 Server Room

2025-07-15T17:02:15Z

Pip: /* Physical Space */

The Computer Science Department has a server room in Malone Hall Room G29. This page is for CS faculty/researchers who have already been allocated space in that room or want to request space in the room. It also describes how to make the best use of your space allocation.

Please read the below sections first. Then, if you would like your server hosted in our server room or have questions that are not answered here or need to make arrangements with us if you've been allocated space in the server room, please email us at {{mailto|support}}.

== Services Provided (and Not Provided) by CS IT Staff ==

=== Things We Will Do for You ===

CS IT will:

* Provide space on a rack for your equipment, possibly on a rack shared with other CS faculty
* Provide network access for your equipment (see [[#Networking|Networking]] below)
* Provide power access for your equipment (see [[#Power|Power]] below)
* Provide you and your designees J-Card access to the room
* Add you to a ''Malone server room mailing list'' for server room-related announcements, etc.
** (However, you should continue to check the CS IT Support Wiki [[Notices]] page if you experience issues such as network, etc. that could be affecting your systems in the server room.)

=== Things You Will Need to Do Yourself ===

CS IT will ''not'':

* Install your systems on the rack
* Make network or power connections between your systems and our equipment on the rack
* Administer your systems

{{messagebox|'''NOTE:''' CS IT Support does not administer research systems. Please see our [[Services Provided By CS IT|Scope Of Services]] and [[:Category:Research Computing|Research Computing]] pages for more details.|type=warning}}

== Physical Space ==

Each rack is labeled with a letter and number. Within each rack, space is divided vertically into numbered "rack units". We will provide you the rack letter/number combo and the range of RUs available to you.

== Airflow/Cooling ==

The server room is set up in a ''"hot aisle/cold aisle"'' configuration. The front of each rack, which is the end with the single, wider door, faces a "cold aisle". The cold aisles are also marked by perforations in the floor tiles. Cold air from the air conditioning units enters the aisles through these perforations. The back of each rack faces a "hot aisle", which does not have perforated floor tiles.

When installing equipment in your rack, ''you should orient the equipment so that the fans pull air in from the cold aisle and exhaust air out to the hot aisle.'' This ensures good cooling efficiency for the entire room. Equipment installed backwards may overheat and may cause adjacent equipment to also overheat.

== Networking ==

Each rack has a switch with ports labeled for the CS public grad net and the CS private grad net. (See [[Networking at CS - Overview|our networking overview]] for more information on those networks.) If you need another network, please ask; we may be able to accommodate the request.

You will need to follow [[Requesting a Static IP Address on the CS Network|our procedure for requesting static IP addresses]] for your equipment, in addition to connecting the equipment to the correct ports on the switch.

Our network connections are '''1 Gigabit''' Ethernet using RJ-45 connectors. If you need other accommodations, please contact us and we'll see what arrangements we can make.

Please do not use any of the ports on the switches labeled "Reserved", nor any of the unlabeled ports.

== Power ==

Each rack has several power distribution units (PDUs). Most racks have:

* Two 120V PDUs with NEMA 15/20 amp outlets. (The 15A outlets are the standard household receptacle.)
* One 208V PDU with a few C19 outlets and several more C13 outlets.

Some racks have fewer PDUs because of space limitations, but every rack should have at least one 120V and one 208V PDU.

Each PDU has a display showing the amount of current it is currently supplying, in amps. The limits for the PDUs are:

* The 120V PDUs may only exceed 16 amps for short periods of time (no more than an hour per day)
* The 120V PDUs may ''never'' exceed 20 amps, for any period of time
* The 208V PDUs have two banks of outlets:
** Each bank may only exceed 16 amps for short periods of time (no more than an hour per day)
** Each bank may ''never'' exceed 20 amps, for any period of time
** The entire PDU may only exceed 24 amps for short periods of time (no more than an hour per day)
** The entire PDU may ''never'' exceed 30 amps, for any period of time

The 208V PDU on rack B4 only has one outlet bank, and has limits corresponding to a single 208V PDU bank: no more than 16 amps in continuous usage, and no more than 20 amps at all.

The two-bank PDUs have LEDs showing which bank's current is being displayed at the moment. If both LEDs are lit, it's showing the PDU's total power usage. Press the "Select" button to cycle the display between the banks and the PDU.

Note that we cannot guarantee each faculty member a designated PDU. You might need to coordinate power usage with other faculty members using the same PDU.

== Access to the Server Room ==

Server room access is controlled by J-Card. In order to grant someone access, the faculty owner of the rack space should {{mailto|support|email us}} and request it. The request needs to contain the name and JHED ID of the person who should be granted access, as well as an estimate of how long you expect the person to be using the room.

== Other Notes ==

Do not prop the door to the server room open. We are notified any time the door stays open for too long. If you expect to need to door to remain open for some period of time, please {{mailto|support|email us}} ahead of time to let us know.

The server room is fairly loud. If you want to use ear protection while you're working there, you can use one of the headsets that are hanging on the wall all the way to the right after you enter the room. Please return the headsets to their hangers when you're done with them.

There is a "crash cart" at the back of the room with a monitor, keyboard, and mouse on it. You can use it to connect a display to your servers on a temporary basis. Please return it to its storage area when you're done.

'''''Please turn the server room lights off when you're done in the room.'''''

[[Category:Malone Hall]]
[[Category:Misc]]
[[Category:Research Computing]]