Transcript System Management on OpenVMS HP System Management Forum

OpenVMS Blade
Management
Barry Kierstein
Software Engineer-AM Project Manager
[email protected]
Parts written by Curt Spacht
System Mangement Architect/Project Leader, OpenVMS
Business Critical Systems
[email protected]
© 2008 Hewlett-Packard Development Company, L.P.
The information contained herein is subject to change without notice
Agenda
•
Overview of HP System Management
•
Overview of a Blade enclosure
•
Overview of iLO (MP)
•
Overview of OA
•
Overview of VCM/VCEM
•
Overview of HP SIM/VSE
•
Overview of System Management Homepage
July 20, 2015
2
Overview of HP System
Management
•
Simplify system management and configuration
by use of software and virtualization
− Simplify steps to do various management tasks
− Ease hardware replacement – user-removable parts
− Ease system migration between Blades
• Faster recovery from hardware failure
• Hardware or firmware upgrades
− Provide a “single pane of glass” for all platforms and
operating systems to monitor all Blade systems
− Facilitate and automate configuration, monitoring,
workload management and capacity planning as much
as possible
July 20, 2015
3
Overview of HP System
Management
•
To implement these goals, provide hardware and
software capabilities to make this possible
− Remote management of Blade via IP
− Enclosure monitors temperature and health of various
components - Blades, fans, power supplies, network
adapters, etc.
− Add capabilities to Blades, network adapters, SAN
connects, so one Blade can be configured to look like
another Blade and assume any work that it was doing
− System management software running under HP SIM
takes advantage of the flexibility of the hardware to
monitor and migrate systems as needed
July 20, 2015
4
Overview of a Blade - Front
July 20, 2015
5
Overview of a Blade - Front
July 20, 2015
6
Overview of a Blade - Front
July 20, 2015
7
Overview of a Blade - Front
July 20, 2015
8
Overview of a Blade - Front
July 20, 2015
9
Overview of a Blade - Front
July 20, 2015
10
Overview of a Blade - Front
July 20, 2015
11
Overview of a Blade - Front
July 20, 2015
12
Overview of a Blade - Front
July 20, 2015
13
Overview of a Blade - Front
July 20, 2015
14
Overview of iLO (MP)
•
Each Integrity system has an integrated Lights
Out (Management Processor) to control the Blade
through a browser via the IP protocol
− Can turn the Blade on/off, configure the console inputs
and outputs, set boot options, etc.
− Gives access to the Blade console that is used by the
operating system for booting and general system
access (text or graphics based)
− Can install or upgrade an operating system onto the
Blade (provisioning) or a remote DVD on a PC
• In the case of OpenVMS, an Infoserver can also be used
July 20, 2015
15
Overview of iLO (MP)
July 20, 2015
16
Overview of iLO (MP)
July 20, 2015
17
Overview of OA
•
The Online Administrator allows for management
of the enclosure itself through a browser using
the IP protocol
− Implemented as a hardware module that plugs into the
back of the enclosure. Two can be installed to provide
for failover.
− View configuration and health of each component of
the enclosure – Blades, management components like
the OA and VC-enet, VC FC module, network switches,
power supplies, fans, etc.
− Quick access to the iLO of each Blade
July 20, 2015
18
Overview of OA
July 20, 2015
19
Overview of OA
July 20, 2015
20
Overview of OA
July 20, 2015
21
Overview of OA
July 20, 2015
22
Overview of OA – VC-enet
July 20, 2015
23
Overview of OA
July 20, 2015
24
Overview of OA
July 20, 2015
25
Overview of VCM
(Virtual Connect Manager)
•
Virtual Connect enables Blades to assume the
role of another Blade
− “Workload” – the operating system and applications
that do work or provide services
− “Logical server” – a virtualized hardware platform that
runs a workload, and consists of the following:
• MAC address for network adapters
• SAN WWIDs for SAN storage
• CPU IDs required for software licensing of software
− The logical server attributes are stored in a profile by
the Virtual Connect software, and can apply the profile
to any Blade in the enclosure
− Assumes that the operating system is on a SAN disk
July 20, 2015
26
Overview of VCM
•
Virtual Connect pools resources into a Virtual
Connect Domain
− MAC addresses, SAN WWIDs and virtual CPU IDs are
allocated to a Virtual Connect Domain, and can be
allocated to any Blade in the domain
• Allows easy replacement of Blades
• Network administrators and SAN administrators are only
engaged when the Virtual Connect Domain is initially
configured with a pool of MAC addresses, SAN WWIDs and
CPU IDs
− Virtual Connect Domains were initially one enclosure,
but will soon span 4 enclosures
July 20, 2015
27
Overview of VCM
•
VCM manages a Virtual Connect Domain through
a browser using the IP protocol
− Implemented as a hardware module (VC-enet) that
plugs into the back of the enclosure. Two can be
installed to provide for failover.
− Allows the migration of a logical server from one Blade
to another
• Shut down the operating system
• Migrate the profile to another Blade using VCM
• Boot the operating system on the other Blade
− Manages Blades in a Virtual Connect Domain
July 20, 2015
28
Overview of VCM
July 20, 2015
29
Overview of VCM – Edit profile 1
July 20, 2015
30
Overview of VCM – Edit profile 2
July 20, 2015
31
Overview of VCEM
•
Virtual Connect Enterprise Manager Extends the
VCM style of management over multiple Virtual
Connect Domains
− Software spans Virtual Connect Domains to provide
logical server migration over a large computer facility
− Uses Virtual Connect to do its work
July 20, 2015
32
Overview of HP SIM/VSE
•
HP SIM/Virtual Server Environment is HP’s
“single pane of glass” for managing computer
installations
− Goal to scale to the largest computer installations
− Support both the Proliant and Integrity platforms
July 20, 2015
33
Overview of HP SIM/VSE
•
HP SIM/VSE supports various management tasks
− Creation, configuration, management and migration of
logical servers and virtual machines
− Performance and power usage data gathering/Capacity
planning
• Optimize workload placement
• Optimize power usage
• Tool for planning server consolidation
− Power monitoring and regulation
• Maximum performance, maximum power savings, and
somewhere in between
− Manage capacity (iCAP) and workloads (gWLM)
July 20, 2015
34
Overview of HP SIM/VSE
•
HP SIM/VSE supports various management tasks
− Goal of optimizing server and energy use
• Lower power and cooling costs
− Compute “what-if” placements of workloads on various
servers – existing or proposed acquisitions
− Migrate workloads on off-peak times to fewer physical
servers and shut down the servers needed at peak times
− Goal of reducing downtime to perform repairs,
preventative maintenance and software/firmware
upgrades
• Migrate a logical server to another Blade, fix/upgrade the Blade,
migrate the logical server back to the original Blade
• Can do this in VCM/VCEM, but number of steps reduced
July 20, 2015
35
Overview of HP SIM/VSE
July 20, 2015
36
Overview of HP SIM/VSE
July 20, 2015
37
Overview of HP SIM/VSE
July 20, 2015
38
Overview of HP SIM/VSE
July 20, 2015
39
Overview of HP SIM/VSE
July 20, 2015
40
Overview of HP SIM/VSE
July 20, 2015
41
Overview of HP SMH
•
HP System Management Homepage shows
various system metrics and can throw events
based on user-defined thresholds
•
Uses a browser interface
•
Free, downloadable from the OpenVMS System
Management homepage
July 20, 2015
42
Overview of HP SMH
July 20, 2015
43
Overview of HP SMH
July 20, 2015
44
Overview of HP SMH
July 20, 2015
45
Overview of HP SMH
July 20, 2015
46
Overview of HP SMH
July 20, 2015
47
Overview of HP SMH
July 20, 2015
48
Overview of HP SMH
July 20, 2015
49
OpenVMS Contacts
•
[email protected]
•
[email protected]
•
[email protected] (Our manager)
July 20, 2015
50