Primary Contact: Joel Burks, joel.burks@oregonstate.edu
I will be reseating SUP 6 on DCS1 tonight after 5 pm. This will cause SUP 5 to become the active SUP. This is in order to troubleshoot a hardware issue.
Yesterday at 2:00 pm, Information Services made a change to the university’s spam filter that made the filter overly sensitive. As a result, some email sent from outside OSU was inappropriately tagged as spam. This issue was corrected at 11:00 am today, April 18.
We advise that all members of the OSU community check their “junk” or ”spam” email folders as well as any other folder that might apply rules to email sent to your OSU email address. The issue did not affect any email you may have sent during this time.
As a good practice, we always recommend that people check their junk email folder on a regular basis, as even the best spam filter is not 100% perfect. In the meantime, we apologize for this incident that may have caused email to be misfiled in your email client.
Primary Contact: Joel Burks, joel.burks@oregonstate.edu
Per TAC instructions, the order doesn’t matter. But it was recommended to set the MTU on the primary VPC devices, then on the secondary. Also, recommended doing during a maintenance window. Since we’re running versions newer than 5.0(2)N2(1) there should be a graceful failover to the secondary devices for the port channels involved. Also the commands should be the same on 5010s and 5548s.
Primary Contact: Joel Burks, joel.burks@oregonstate.edu
We will be swapping SUPs on dcs1 after 5 pm. There are two SUPs in the chassis. We will be removing one and adding it back with a newer SUP.
We have done this before with no effect on traffic.
I will be patching CN-Home, CN-Share, TSS1, and TSS4 this Saturday after 10PM during our normal maintenance window.
Bruce Beicke Systems Administrator 541-713-3551 bruce.beicke@oregonstate.edu
Phone service at the Hatfield Marine Science Center was interrupted on Monday, April 15, between 11:00 am and 1:00 pm. Inbound callers were unable to communicate with responders and outbound service at HMSC was largely unavailable. Voicemail was not affected by the incident.
The problem has been resolved, and we apologize for the service interruption. The incident was trigged by a router reboot that was initiated to resolve a network connectivity issue.
Updated: Corrected dates in text.
The EmpCenter time and attendance system will be unavailable from 11:59PM on Saturday, April 20 through 2:00AM on Sunday, April 21 due to scheduled maintenance by the vendor.
Jill Swenson
Associate Director, Enterprise Computing Services Oregon State University 541-737-0682
The EmpCenter time and attendance system will be unavailable from 11:59PM on Saturday, April 21 through 2:00AM on Sunday, April 20 due to scheduled maintenance by the vendor.
Jill Swenson
Associate Director, Enterprise Computing Services Oregon State University 541-737-0682
** Maintenance Announcement – No service interruption anticipated **
Services Maintained & Purpose of Maintenance: Technical Plan: Background:
The connection for CSACS1 to Active Directory is currently degraded. This is generally not an issue as authentication can still pass for both CSACS1 & 2, but changes to AD authentication cannot currently be made. This may have been caused be the last patch I installed on this device approximately four weeks ago.
To correct the issue: my plan, working with Cisco TAC, is to un-join the CSACS servers. This will allow me to make changes to CSACS1 without affecting CSACS2. To further mitigate issues, I will point VPN auth at CSACS2. After the majority of users, and sources using AD auth have been moved to CSACS2. I will then perform the un-joining, and remove CSACS1′s association with Active Directory. I will have to remove all authentication rules that have to do with AD first. After the AD association is removed, I will re-join CSACS1 to the domain. Next I will then join CSACS1 to CSACS2, making CSACS2 the primary, which will sync it’s config with CSACS1. This will insure the authentication rules I deleted will be properly re-added.
Roll back will be a config restore from backup. Testing will include auth against wireless, VPN, SMTP and Cisco devices.
Maintenance Window: Start: 04/13/2013 10:00 PM End: 04/13/2013 10:30 PM
If you have questions or concerns about this maintenance, please contact Network Engineering at net (at) oregonstate.edu or call 737-HELP.
Per our newly-announced schedule for regular monthly maintenance, Blackboard will be unavailable on the morning of Saturday, April 20, from 6:00 to 9:00 am. We will be installing patches to correct some known issues with student access to grades, quiz creation, and to the patch software itself. We will also fix a few bugs in locally-developed Blackboard building blocks.
Through August, general maintenance is scheduled on the following Saturday mornings. Messages will be posted prior to each event confirming the 3 hour maintenance window.
The complete 2013 calendar for Blackboard maintenance can be found at http://blogs.oregonstate.edu/bbsc/2013/03/22/scheduled-maintenance-2013.
If you have any questions about these planned service interruptions, please contact Lynn Greenough, Blackboard Steering Committee chair, at Lynn.Greenough@oregonstate.edu.
New comment on your post “SUP switchover on DataCenter1″ Author : burksj (IP: 10.214.126.21 , mechagodzilla.nws.oregonstate.edu) E-mail : joel.burks@oregonstate.edu URL : http:// Whois : http://whois.arin.net/rest/ip/10.214.126.21 Comment: This was done around 5:30 pm that evening.
You can see all comments on this post here: http://intranet.nws.oregonstate.edu/blog/archives/4424#comments
Permalink: http://intranet.nws.oregonstate.edu/blog/archives/4424#comment-173 Trash it: http://intranet.nws.oregonstate.edu/blog/wp-admin/comment.php?action=trash&c=173 Spam it: http://intranet.nws.oregonstate.edu/blog/wp-admin/comment.php?action=spam&c=173
Since the maintenance on 3/30/2013, we have been experiencing intermittent monitor failures on the load balancers for the Exchange and Lync servers. A minor NIC configuration change is necessary to resolve the issue. We will remove the servers one at a time from the load balancers to update the affected servers starting after 9:30 PM this evening. We do not expect this maintenance to cause the Exchange databases to failover or to impact service for Exchange or Lync in any way. In addition to this change, we will bring the Lync servers up to current patch level while they are offline.
We have already resolved this issue with a minor NIC configuration change on two of 8 interfaces on two of the 6 Lync servers. These interfaces were being intermittently shutdown by the failed monitor and may have caused intermittent client issues. We also suspect that this issue is responsible for Outlook users receiving the message “The Microsoft Exchange Administrator has made a change that requires you to quit and restart Outlook”.
Kirsten Petersen
Network Services
Oregon State University
ServerSupport@oregonstate.edu
