implementing tivoli at princeton universityesm/ware/planet-tivoli-2001.pdf · planet tivoli, may...
TRANSCRIPT
Planet Tivoli, May 2001 Princeton University
Implementing Tivoli at Princeton University
Charles A. AugustineManager, Enterprise Systems
Management
Planet Tivoli, May 2001 Princeton University
Issues for Higher EducationIssues for Higher EducationEconomic justification is difficultDifferent time constraints than businessFew colleges or universities use ESM systemsMany locally developed tools
Planet Tivoli, May 2001 Princeton University
Bringing Tivoli to PrincetonBringing Tivoli to PrincetonPrinceton Partnership 2000 project
Convert applications to distributed platformsProvide infrastructure comparable to mainframe
Tivoli/Princeton partnershipBroad range of productsEvaluate applicability in higher education
Planet Tivoli, May 2001 Princeton University
Implementation TimelineImplementation TimelineJune 1998 – Purchased Tivoli suiteDecember 1998 – TWS (Maestro) in productionSept-Dec. 1998 – Framework/DM/TEC architecture planning and initial implementationApril 1999 – Permanent ESM group formedSept. 2000 – All production systems monitored
Planet Tivoli, May 2001 Princeton University
Tivoli Products Initially InstalledTivoli Products Initially InstalledEnterprise ConsoleDistributed MonitoringWorkload Scheduler (Maestro)NetViewService Desk
Planet Tivoli, May 2001 Princeton University
Current Tivoli ConfigurationCurrent Tivoli ConfigurationDistributed Monitoring
150 Solaris and Windows NT hostsMonitor system health (CPU, Memory, Disk, etc.)E-mail and pager notification from TEC & DMWeb page monitor
Workload Scheduler (Maestro)25 hosts, 300 schedules, 2000 jobsMonitored via DM and TEC
Planet Tivoli, May 2001 Princeton University
Current Tivoli ConfigurationCurrent Tivoli ConfigurationNetView
Used in addition to existing toolsProcessing SNMP trapsNotifications via e-mail and pagerNot sending Tivoli events
Service DeskReplaced by locally developed Web application
Planet Tivoli, May 2001 Princeton University
Staffing/OrganizationStaffing/OrganizationBegan with temporary project teamHired consultants for initial design and installationCreated permanent ESM group after initial installationService Desk implemented by Help Desk staffNetview implemented by Networking staff
Planet Tivoli, May 2001 Princeton University
Princeton IT OrganizationPrinceton IT Organization
EnterpriseServices
FinancialServices
AdministrativeServices
InformationSystems
AcademicServices
SupportServices
VP Computing and Information Technology
Planet Tivoli, May 2001 Princeton University
Departments using TivoliDepartments using Tivoli
EnterpriseSystems
Management
EnterpriseServices
FinancialServices
AdministrativeServices
AdministrativeApplication
Support
UnixSystems
PCSystems
Networking
PlatformServices
ProjectDevelopment
AdministrativeServices
InformationSystems
AcademicServices
Help Desk
SupportServices
VP Computing and Information Technology
Planet Tivoli, May 2001 Princeton University
Enterprise Systems ManagementEnterprise Systems ManagementManagerTwo system administratorsResponsibilities
Tivoli MonitoringTivoli Workload SchedulerDazel Output Management
Planet Tivoli, May 2001 Princeton University
Completed ProjectsCompleted ProjectsHeartbeat systemCustomized event display
Group events by host and application areaModify event contents via TEC rulesWeb event display
Web page monitorTools to instrument non-Tivoli monitors
Planet Tivoli, May 2001 Princeton University
Web Event DisplayWeb Event Display
Planet Tivoli, May 2001 Princeton University
Planet Tivoli, May 2001 Princeton University
Planned ProjectsPlanned ProjectsLogfile adapters for application logsNotification engine for TECManager for OracleApplication Performance Monitor
Planet Tivoli, May 2001 Princeton University
Lessons LearnedLessons LearnedUnderestimated time and staffing needsDifficulty of replacing existing toolsTop-down vs. bottom-up strategy
Planet Tivoli, May 2001 Princeton University
Why did we underestimate time and staffing?
Why did we underestimate time and staffing?
Turnkey application vs. toolkitDifficulty of changing current practicesTime required to master productsOperational tasks preempt developmentOpen positionsMultiple projects
Planet Tivoli, May 2001 Princeton University
Why not replace existing tools?Why not replace existing tools?Existing tools are
Not integratedNot uniform
But, these tools are alsoWell understoodTested and reliableIntegrated into operational processes
Planet Tivoli, May 2001 Princeton University
Development StrategiesDevelopment StrategiesBottom-up Top-downBottom-up Top-down
Start with infrastructureSynthesize application status from lower level eventsUsers are system administratorsReplace existing monitors
Start with applicationsAnalyze application problems based on lower level information.Users are application owners and operationsIntegrate existing monitors
Planet Tivoli, May 2001 Princeton University
Development StrategiesDevelopment Strategies+ Bottom-up -+ Bottom-up -
Models application dependenciesDrives high reliability
Needs buy-in from system administratorsReplaces existing tools
+ Top-down -+ Top-down -Models end-user experienceAdds value immediately
More complex monitorsLess sophisticated users
Planet Tivoli, May 2001 Princeton University
Summary – Tivoli@PrincetonSummary – Tivoli@PrincetonTWS schedules all new application systemsNetView provides critical operation alertsTEC/DM monitors all production hostsProgress has been slower than expectedFuture TEC/DM development will focus on applications rather than infrastructure
Planet Tivoli, May 2001 Princeton University
For more informationFor more informationPrinceton ESM Web site: http://www.princeton.edu/~esmE-mail [email protected]