Transcript CSM Project startup

Critical Systems Management
Project
Steve Lloyd
SAN Manager
(31st October 2005)
Agenda
 Project Overview
 Roles and Responsibilities
 Project Organisation and Timeline
 Major Deliverables
 Questions
Project Overview
 Purpose of the Project
 Project Objectives
 Overall Scope
 Risk Assessment
 Budget
 Communication
Purpose of the Project
The purpose of this Project is to increase the
overall effectiveness of our current
Systems/Network Management Tools and
Practices, therefore improving IT Service
Delivery to our customers.
Objectives and Scope
The Project will cover the following areas:
1. System Management
2. System Monitoring
3. RMS Change Management
Objectives - System Management
 Configure current System Management
Tools within INSRV
 Document INSRV System Management
processes and procedures
 Evaluate future needs for onsite and
remote access management of INSRV
Critical Systems.
 Assign responsibility for administering
System Management.
Scope - System Management
Onsite Access:





Keyboard Video Mouse over IP
Power cycling of remote servers
Web and client based management tools
Secure physical console access
Dell OpenManage ?
Scope - System Management
Remote Access:
 Citrix Metaframe
 CISCO 3640 router
 Secure Shell
 Windows XP Remote Desktop Protocol
 Virtual Private Network
 Modem dial-up service
System Management
Examples:
 Dell Remote Console (KVM over IP)
 SAN Monitoring Web Page
 Dell Remote Assistant Card
 Citrix Metaframe
 Document using Concept Maps

Network Applications>Departmental Software>INSRV>Concept Mapping
Objectives - System Monitoring
 Implement a monitoring system that will
detect problems with any INSRV Critical
Systems before they turn into costly
downtime.
 Improve availability and performance of
our IT Infrastructure and gain in-depth
visibility into systems/network problems.
Objectives - System Monitoring
•
•
Evaluate future needs for Monitoring of
our Critical Systems.
Assign responsibility for administering
System Monitoring.
Scope - System Monitoring
 Install and configure a Simple Network
Management Protocol management
station.
 Evaluate current monitoring tools, such
as What’s Up, Sflow, etc…..
 Statistical Analysis (MRTG, RRD)
SNMP Network Management
 An SNMP based network management
system incorporates the following:
Management Station (OpenNMS)
Management Information Base (MIB)
An Agent on each client (servers, switches, etc)
SysName, SysDescr, SysLocation, SysContact
Network management protocol
• SNMP - the protocol used between the management
station and the clients
System Monitoring
System Monitoring
Examples:
 NetWare MRTG graphs
 Blackboard and Voyager RRD graphs
 OpenNMS - SNMP Management Station
 What’s UP monitoring

Network Applications>Departmental Software>INFOS>Whats Up
Change Management
Change Management is a process that ensures
standardised methods and procedures are
used for efficient and prompt handling of all
changes, in order to minimise the impact of
any related incidents upon service quality.
Not every change is an improvement,
but every improvement is a change!
© www.itilsurvival.com
(reproduced with permission)
ITIL Service Management
© www.itilsurvival.com
(reproduced with permission)
Availability Management
Continuity
Management
Capacity Management
Financial
Management
Release
Management
for IT services
Service Level
Management
IT
Infrastructure
Change
Management
Configuration
Management
Incident
Management
security
IT Service
Problem Management
The Service Support Set
= Interconnection between the processes =
I
I
I
Incident
Management
I
D
Problem
C
Work
Around
Known
Error
M
S
L
Change
Management
D
Configuration
Management
D
Customer,
Supplier, etc.
RFC
B
H
S
Change
SOLUTION
© www.itilsurvival.com
(reproduced with permission)
Problem
Management
Release
Management
Change Management
The Functionally Oriented Organisation
GOAL
GOAL
GOAL
GOAL
GOAL
GOAL
ACTIVITIES
FEEDBACK
ACTIVITIES
FEEDBACK
ACTIVITIES
FEEDBACK
ACTIVITIES
FEEDBACK
ACTIVITIES
FEEDBACK
ACTIVITIES
FEEDBACK
RESULT
RESULT
RESULT
RESULT
RESULT
RESULT
the lines decide
© www.itilsurvival.com
(reproduced with permission)
UIS
NetWare/Unix
Apps
Web
GOAL
Change Management
The Process Driven Organisation
Apps
Web
ACTIVITIES
FEEDBACK
RESULT
NetWare/Unix
UIS
the processes decide
© www.itilsurvival.com
(reproduced with permission)
Objectives - RMS Change
Management
 Implementation of a Change
Management system using the RMS
Change Management software.
 Delegation of system wide Change
Management
This project does not attempt to implement a full
Change Management System for all INSRV
infrastructure equipment.
Scope - RMS Change Management
 Full Change Management System for all
SAN attached equipment.
Cardiff University’s SAN
Cathays Campus LAN
FileSrv1
Heath Campus LAN
FileSrv7
FileSrv8
FileSrv14
Client PC
Client PC
Sites 3 miles apart
FC Switch1
FC Switch3
FC Switch2
FC Switch4
SAN Fibre Channel
Network
Tape Library 1
Storage Processor 1
Tape Library 2
Storage Processor 2
Enterprise RAID
Storage Array 1
Enterprise RAID
Storage Array 2
Storage Processor 1
Storage Processor 2
Mirrored Storage
Primary
Primary
Primary
Secondary
Secondary
Secondary
NetWare in the SAN
Secondary Secondary
Secondary
Primary
Primary
Primary
Cardiff University’s SAN
Cathays Campus LAN
AppSrv1
AppSrv2
Heath Campus LAN
AppSrv3
AppSrv4
AppSrv5
AppSrv6
Client PC
Client PC
Sites 3 miles apart
FC Switch1
FC Switch3
FC Switch2
FC Switch4
SAN Fibre Channel
Network
Tape Library 1
Storage Processor 1
Tape Library 2
Storage Processor 2
Enterprise RAID
Storage Array 1
Enterprise RAID
Storage Array 2
Storage Processor 1
Storage Processor 2
Mirrored Storage
Primary
Primary
Primary
Secondary
Secondary
Secondary
Solaris In the SAN
Secondary Secondary
Secondary
Primary
Primary
Primary
Scope - RMS Change Management
 To produce a comprehensive Inventory
of all INSRV Infrastructure equipment
such as servers, LAN switches, etc..
 Manage the installation of all new INSRV
infrastructure equipment
 Manage the change of location of any
INSRV infrastructure equipment
Risk Identification and Assessment
Risk
Probability
Impact
Management
Staff availability
2
2
Ensure adequate notice
and full support of Team
Leaders.
Project scope
may expand
1
2
Project scope to be
actively managed
Section 4 of the University Project Framework on Risk Identification and Assessment.
Budget
Project capital requirements:
 Small consumables budget for
hospitality and technical books.
 RMS Change Management training and
consultancy already paid for.
Recurrent cost:
 Project will identify possible future
spends.
Communication
 Weekly Project Team Meetings
 Monthly Project Reviews
 INSRV Staff web site:
http://www.cardiff.ac.uk/insrvstaff/projectandworking/csm/
 Minutes of project meetings
 Project reports
 Issue log
 Project plan
 Risk assessment log
Roles and Responsibilities
A Virtual project team has been put together
for this Project.
Each virtual team member will be asked to
commit two hours per week for the first
three months, then one hour per week for
the remaining three months. The Project
Manager will be required to work two days
per week for the duration of the project.
Roles and Responsibilities
Tasks will be allocated to individuals for their
INSRV Team. Following liaison with his/her
Team Leader, these tasks should be
delegated to the appropriate member of
staff within their INSRV Team.
Roles and Responsibilities
Steve Lloyd - Project Leader
Hugh Beadie - Architecture, Research & Development
Ceri Davies - Platforms
Maurice Drane - Platforms
Jonathon Edwards – Operations
Chris Jones - Help Desk
Mike Jorgenson - Network
Dave Ball – Applications
Noel Evans - Platforms (Windows )
Toby Freeman – Directory Services & NetWare
Lucy Warburton - Administrator
Hugh Gulliver - Security (Team Member to be confirmed)
Dave Westcott - Workstation (Team Member to be confirmed
Project Organisation and Timeline
Phase one
Stage
Duration
Start
Planning
4 weeks
03/10/05
System Management
4 weeks
31/10/05
System Monitoring
4 weeks
28/11/05
Change Management
4 weeks
09/01/06
Project Organisation and Timeline
Phase two
Stage
Duration
Start
Monitoring & Review of Phase
One
6 weeks
06/02/06
Project Report
4 weeks
20/03/06
Project Review
2 weeks
17/04/06
Project End – 1st May 2006
Major Deliverables
 Documentation of current System
Management processes and procedures.
 Implementation of a centrally managed
Monitoring system for all INSRV Critical
Systems.
 Implementation of a Change Management
system using the RMS Change
Management software.
Major Deliverables
 Assign responsibility for administering
System Management, Monitoring and
Change Management
 Report on future requirements and
possible future projects.
The outcome of this project will be
presented to the INSRV Board Members
and Senior Team Leaders.
Questions ?