** Maintenance Announcement – No service interruption anticipated **
We will be applying the latest stable maintenance release firmware for our Arista switch pair in our primary storage & compute POD. We do not anticipate any customer noticeable downtime.
Start: 11/28/2015 10:00:00 PM
End: 11/28/2015 11:00:00 PM
If you have questions or concerns about this maintenance, please contact the Shared Infrastructure Group at osu-sig (at) oregonstate.edu or call 737-7SIG.
** Maintenance Announcement – NO service interruption anticipated **
We are upgrading our StoreVirtual firmware from LeftHand OS 10.5 -> LeftHand OS 11.0
Production and Dev SANs are redundant and maintenance will have no noticeable effect on these SANs, meaning that the OSU systems used by students, staff, and faculty will not experience a service interruption.
Start Time: 12/21/2013 at 9:00 PM
End Time: 12/21/2013 at 4:00 AM
If you have questions or concerns about this maintenance, please contact the Shared Infrastructure Group at osu-sig (at) oregonstate.edu or call 737-7SIG.
** Maintenance Announcement – No service interruption anticipated **
We will be applying a firmware update to our iSCSI switches that support our StoreVirtual SAN. This is the storage network that back’s our VMware infrastructure.
We do not anticipate any service interruption. Our switching is redundant, we will only change the switches one at a time, and the changes should not be service interrupting.
Start: 11/09/2013 10:00 PM
End: 11/09/2013 11:00 PM
If you have questions or concerns about this maintenance, please contact the Shared Infrastructure Group at osu-sig (at) oregonstate.edu or call 737-7SIG.
Part 4 The Saga Continues.
Everything was nice and quite for a few months for us here regarding this issue. Then classes started and things got a little busy and the problem is back with a vengeance. We have been getting paged once per night. It will be a random switch in the stack not always the same one. We have logged a support case with HP and we got the standard teir1 response of update to the most current firmware. So we will be upgrading to W.15.12.0011 during our next maintenance window. If this does not address the issue we will continue to poke away at the problem!
Part 1 | Part 1 follow up | Part 2 | Part 3 | Part 4
** Emergency Maintenance Announcement – No service interruption anticipated **
We replaced a pre-failing (3:26pm) drive in the Development cluster today. The array will be rebuilding over the next few hours.
Start: 10/27/2013 7:48 PM
End: 10/27/2013 7:48 PM
If you have questions or concerns about this maintenance, please contact the Shared Infrastructure Group at osu-sig (at) oregonstate.edu or call 737-7SIG.
** Maintenance Announcement – No service interruption anticipated **
We will be performing minor maintenance.
We do not anticipate any service interruption.
Start: 10/5/2013 01:00 AM
End: 10/5/2013 01:05 AM
If you have questions or concerns about this maintenance, please contact the Shared Infrastructure Group at osu-sig (at) oregonstate.edu or call 737-7SIG.
** Emergency Maintenance Announcement – No service interruption anticipated **
We will be replacing a failed raid/rom battery in a fast disk node in our lefthand SAN. This is the storage network that back’s our VMware infrastructure.
We do not anticipate any service interruption. Our nodes are redundant for each other, we will only be working on a single node as such the change should not be service interrupting.
Start: 07/14/2013 11:00 PM
End: 07/14/2013 12:00 PM
If you have questions or concerns about this maintenance, please contact the Shared Infrastructure Group at osu-sig (at) oregonstate.edu or call 737-7SIG.
** Maintenance Announcement – No service interruption anticipated **
We will be applying a configuration change to our iSCSI switches that support our StoreVirtual SAN. This is the storage network that back’s our VMware infrastructure. (configuring timezone offset take2, kicking up syslog debug level)
We do not anticipate any service interruption. Our switching is redundant, we will only change the switches one at a time, and the changes should not be service interrupting.
Start: 06/08/2013 10:00 PM
End: 06/08/2013 10:15 PM
If you have questions or concerns about this maintenance, please contact the Shared Infrastructure Group at osu-sig (at) oregonstate.edu or call 737-7SIG.
** Maintenance Announcement – No service interruption anticipated **
We will be applying a configuration change to our iSCSI switches that support our StoreVirtual SAN. This is the storage network that back’s our VMware infrastructure. (configuring syslog)
We do not anticipate any service interruption. Our switching is redundant, we will only change the switches one at a time, and the changes should not be service interrupting.
Start: 06/04/2013 10:00 PM
End: 06/04/2013 10:15 PM
If you have questions or concerns about this maintenance, please contact the Shared Infrastructure Group at osu-sig (at) oregonstate.edu or call 737-7SIG.
We made the changes requested of us in Part 2. However we are still experiencing the occasional ping/fail on one of the switches. We have not seen an loop detected. Interesting to have loop protection turned on and doesn’t hurt anything but the blade centers and flex10s do not seem to be the problem.
So where do we go now?! Another call into hp support and they have directed us to perform the following steps:
- Re-seat all components in the switch that keeps paging us.
- Enable syslog on all switches and see if they say anything.
- Add a timezone offset to the ntp configuration.
Hopefully this will show us what is happening as we still do not have a resolution. Or is it time to start replacing hardware? Is the sfp unit in the switch bad? is the 10g module bad? is the switch bad? lots of questions and no real firm answers as to why we get woken up in the middle of the night yet all seems fine except for a quick down/up event.
Part 1 | Part 1 follow up | Part 2 | Part 3 | Part 4