Hansen Network Maintenance

November 17, 2011  8:00am – December 5, 2011  11:00am
Hansen

Updated 11/30/11:

Network engineers have identified the cause of the network issue in question, and have applied a workaround, which has restored the Hansen network to full functionality. The next maintenance window to address to address the root cause is scheduled for next Monday, (December 5, 2011) from 8:00am to 11:00am.

Thank you for you continued understanding. If you require any assistance or additional resources while job run times are limited to one week, please contact us at rcac-help@purdue.edu.

Updated 11/21/11: Last Thursday, ITaP network engineers performed some troubleshooting on this network issue, and have identified new steps that can be taken towards resolving of this issue.

Therefore, another maintenance window has been scheduled for next Monday, November 28, 2011, from 8:00-11:00am.

Any jobs still running will be requeued, and any new job whose requested walltime would take it past this maintenance will remain in queue until the maintenance is complete.

Thank you for your patience while engineers continue to troubleshoot this issue. If you have any questions or concerns, please contact us at rcac-help@purdue.edu.

Original Message: During these first weeks of run-time since Hansen has gone production, an intermittent issue with Hansen's network has ben discovered, for certain use cases.

While many of you have not encountered this issue, in order to ensure that Hansen continues to function in an optimal manner, ITaP network engineers have planned maintenance to troubleshoot the issue next Thursday, November 17, 2011, beginning at 8:00 AM.

This will result in a 2 hour outage to Hansen.

Any jobs still running will be requeued, and any new job whose requested walltime would take it past this maintenance will remain in queue until the maintenance is complete.

While we hope that this single maintenance will resolve the issue, we have, for the time being, changed Hansen's maximum wall time for a job from 30 to 7 days, which will allow network engineers a shorter troubleshooting cycle to perform further work, should it be necessary.

When the issue is resolved, the maximum run time will return to 30 days.

Thank you for your continued understanding. As always, if you encounter issues or have further questions, please don't hesitate to contact us at rcac-help@purdue.edu

Originally posted: January 30, 2012

Purdue University, 610 Purdue Mall, West Lafayette, IN 47907, (765) 494-4600

© 2017 Purdue University | An equal access/equal opportunity university | Copyright Complaints | Maintained by ITaP Research Computing

Trouble with this page? Disability-related accessibility issue? Please contact us at online@purdue.edu so we can help.