OLIS Announcement: AIX VIO Server reboot

Hello all

ITEC will be doing system work as indicated in the following message.  While Aleph servers housed at ITEC will be involved, ***NO*** service interruptions are expected.  This message is to inform you of these activities.   

Maureen

—–Original Message—–
From: Mike Radomski [mailto:mike.radomski@itec.suny.edu]
Sent: Thursday, January 31, 2008 1:43 PM
To: SUNYConnect Technical list
Cc: Mike Radomski
Subject: [sctech] AIX VIO Server reboot

Hello,We are beginning the initial migrations to the XP24000 storage system.  In order to begin migrating, we need to reboot our VIO servers on our pSeries systems.  The VIO servers are redundant within a managed system and can reboot without interruption to the LPARs running on the system.  The reboots will occur between 4a-7a on the designated days.  Although there should be no interruption to service, we want to communicate our intentions and thank you for your patience.

This is the current schedule for VIO reboots and the LPARs managed by the systems:

Friday 2/1 – VIO9/10

admdevbuc

admdevnew

admolddev

Monday 2/4 – VIO8, VIO3/4

admorabuc

admoranas

dutapp01

itxmail01 (Old Westbury Lotus Notes)

admoraprod2

bufapp05

bufmail02

seneca

slnoradev

slntomcat

Tuesday – VIO5/6

admoradut

admoranew

appdev02

archive01

bufapp03

bufapp04

bufhub01

delaware

itxmail02 (Old Westbury Lotus Notes)

slnoraprod

sufapp03

sufods

Wednesday – VIO1/2

admorajef

admoraold2

admorasicas

admorasuf

bufapp01

bufapp02

mohawk

saranac

slntomcat

sufhyp01

Mike Radomski

Blog:  http://mradomski.wordpress.com

 

SUNY – ITEC

Information Technology Exchange Center

Supervising Analyst of Systems and Telecommunications Services

E-mail: Mike.Radomski@itec.suny.edu

Phone: (716)878-4832

Mobile: (716)807-4040

Fax: (716)878-3485

 

We can’t solve problems by using the same kind of thinking we used when we created them. 

-Albert Einstein

Friends in the SUNY community,ITEC and OAS (System Administration) are embarking on the installation and migration phases for our HP XP storage systems.  For those that were not at Wizard, both organizations are implementing a common storage platforms, HP XP12000 and XP24000, as the building blocks of the larger dual-data center project.  Having a common platform will allow the data centers to replicate data and share a common skill set.  This all being said, ITEC will need your support in scheduling the daunting task of migrating to the XP.

Next Wednesday morning, 4a-7a, we will be upgrading our Cisco MDS switches.  HP is adding additional line cards, which are hot-add components.  I wanted to inform everyone, as the MDS’s are core components and although it is non-disruptive, stranger things have happened.

Over the next 1-3 months, we will be migrating all of the storage currently residing on our IBM Shark to the HP XP24000.  ITEC will be migrating approximately 75 systems to the new platform.  The target systems consist of development, non-production, redundant and production systems for our hosted offerings in SLN (Classic and Angel), SUNYConnect, Banner and Luminis.  We will be publishing a migration schedule next week pending some implementation tasks and migration testing.

For full production systems, we will adhere to our regular 4a-7a Wednesday maintenance window.  However, we may need to extend that window to 12a-7a for some of the larger data systems.  This will be done on a system by system basis.  We will give you at least 1 week notice, with the majority of the schedule for the next 1-3 months published next week.

For redundant, non-production and development systems, we ask for your flexibility in scheduling.  We will be asking, on a system by system basis, to schedule migration outside of the Wednesday maintenance window.

Most migrations will require two reboots.  The first reboot is to upgrade HBA drivers, followed by data synchronization, concluded with a final reboot to migrate fully to the XP24000.

Thank you for your cooperation and patience.

Comments are closed.