Copyright 2007 FUJITSU LIMITED Systemwalker Resource Coordinator Virtual server Edition V13.2 December, 2007 Fujitsu Limited Functions Blade Server Management Software
Copyright 2007 FUJITSU LIMITED 2 - Integrated servers enhance operational efficiency - Separation of hardware and OS by virtualization - Systems are scatted & complex - Gaps exist between service and infrastructure lifecycles Problems Solved by Server Consolidation integration Virtualization Technology is Key to Effective Consolidation Problems B A C Virtualization software AB AB C Virtualization software D Physical integration on blade servers Logical integration by VM Disc integration on SAN storage SAN connectivity virtualization D
Copyright 2007 FUJITSU LIMITED 3 Virtualization Technology Use VM APP OS APP OS VM APP OS APP OS APP OS I/O virtualization (FC) VM APP OS APP OS Spare server I/O virtualization (FC) APP OS Storage Administration Total administration of physical & virtual servers is key Potential complexity from separate physical & virtual server management → Easier operation from unified administration Server integration can increase the problems → High availability and service continuity with virtualization Storage and network connections complex → Simplified configuration & operation with SAN connectivity virtualization technology Server consolidation can create new problems
Copyright 2007 FUJITSU LIMITED 4 RC VE Functions RC VE: Systemwalker Resource Coordinator Virtual server Edition
Copyright 2007 FUJITSU LIMITED 5 Powerful management of physical & virtual servers Visualized Administration Start up and shut down servers Display server configurations and status Functions Effect Removes system complexity, reduces operational errors, by integrating system management of physical & virtual servers c Server Manager Physical Server Visualized management Virtual Server Physical Server
Copyright 2007 FUJITSU LIMITED 6 Display chassis, server’s hardware and OS (physical OS, VM Host, VM Guest) running on servers Displays relationships between hardware and OS (physical OS, VM Host, VM Guest) in a hierarchical structure. Administrators are able to quickly identify managed server problems and their effect via the management view. Operational time and errors rare educed as cause and effect of problems can be easily detected Effects Functions Visualization of servers Manager Blade Server Chassis, Server problem Visualize where problems occur Server Chassis ID, Slot No. Host name, IP address Virtualized Administration ServerView
Copyright 2007 FUJITSU LIMITED 7 Server orchestration Functions Effects Automated configuration of a range of parameters *1 based on Excel or CSV format definitions. Auto output of current configuration details to a configuration definition file. Existent configuration files can be reused when adding servers even if configuration has changed. Initial Introduction Template 1. Configuration 4. Saving 3.Export 2.Import Appropriation ・ Edition RC VE management server Office Machine Center Data conveyance Client No need to be on the site at all times. No need to restore, as configuration errors no longer happen. Multi-server systems can be configured concurrently. Exporting the implemented system image to the configuration definition file means: Configuration is saved by backup making new implementation possible just by importing the configuration definition file. New system configurations become effective by appropriating configuration definition files from a draft. *1 ) The following parameters are covered. Chassis (chassis name, SNMP community name, IP address), LAN Switch Blade (LAN Switch name, IP address, SNMP community name, user name, password), Server Blade (physical server name, IP address, VLAN setting), Server recovery configuration (spare server name, VLAN shift, automated shift, SAN connectivity virtualization function setting) Appropriating ・ Edition 1.Design
Copyright 2007 FUJITSU LIMITED 8 Cloning in Local boot environment Blade #1 Blade #2 Blade #3 Blade #4 Management Server Cloning master 1 ~ 3 generation RC VE Managed server Functions The following network parameters can be pre-defined. Server name IP address Interface name Easy creation of system cloning image via GUI Simplified installation to new servers by automated configuration of server’s unique information based on the existent system image. Effect New server addition to existing system becomes easier – lower workloads less time. Blade #5 System is installed Note VMware environment (VM Host, VM Guest) does not apply with these functions. Server Addition Common master Slot #5 Installation only
Copyright 2007 FUJITSU LIMITED 9 Cloning in SAN boot environment SAN is pre-configured by SAN connectivity virtualization even to empty slots. New servers can be installed using automatic cloning. Effects Blade#1 SAN connectivity virtualization Servers can be installed automatically by cloning from 2 nd server onwards. Server addition becomes more effective, operational times reduce as, SAN configuration and server installation times from media pack are shortened. Since SAN can be pre-configured once, new servers can be added whenever required without SAN changes. SAN Slot#2Slot#3Slot#4 Pre-configuration Blade#2 Functions Server Addition Management Server Cloning Master 1 ~ 3 generation RC VE Common maser
Copyright 2007 FUJITSU LIMITED 10 Hardware Maintenance by SAN connectivity virtualization Functions When a server fails, RC VE can reconfigure the virtual WWN automatically for the replacement blade server. The failed server can be replaced without SAN configuration. Effects Operation1Operation2 Blade#1Slot#2 SAN Connectivity Virtualization Operation1Operation2 Blade#2 New Blade Blade#2 is replaced by a new blade Server replacement now only consists of pulling out and inserting servers. New server restart is enabled just by pressing power on. Replacement
Copyright 2007 FUJITSU LIMITED 11 System disc backup(1) Blade #1 Blade #2 Blade #3 Management Server System image 1~3 generation RC VE Blade #3 Blade #2 Blade #1 Managed server Functions Physical server system disks available to Linux and Windows. As amount of used space is compressed, backup is highly effective. As only system disc is targeted, no complicated parameter setting is required. Image is unified by management server, so generation administration is also easier. Effects Shorter times for backup and restore plus easy operation via GUI. Recovery by restoring the failed server. Recovery by restoring the new server. Disk on physical server system Back up ※ In the case of logical disc, the first disc installed in a server is the target of this function. In cases where system disc consists of multiple partitions, all partitions are the target of this backup/restore function. ※ File system check is recommended before backup is conducted.
Copyright 2007 FUJITSU LIMITED 12 System disc backup(2) SAN Blade Data Disc Data Disc SAN Configuration#1 Windows/LinuxVMware ESX Server VM Host (VMware ESX server) VM Guest (VMware ESX server) SAN Blade VM Guest SAN Blade VM Host (VMware ESX server) Blade ○○○× Back up is available Disc on left is backup target. VMware function is used to backup virtual server system disc. Versatile backup software is used to backup the data disc. Physical OS (Linux/ Windows) Back up Physical OS (Linux/ Windows) Physical OS (Linux/ Windows) ×× Physical OS (Linux/ Windows) Configuration#2Configuration#3 Back up is available Configuration#4Configuration#5Configuration#6 Back up is not available
Copyright 2007 FUJITSU LIMITED 13 Server fault recovery Internal Disc ConfigurationSAN Configuration Characteristics Slow - as Management LAN is used to recover the server. ※ Without SAN connectivity Fast – as SAN is used to recover the server. ※ Without Internal disc Use - Application servers without data - File servers with data - On failed servers where data is saved to a system disk, only OK to recover backed up data - Only Linux, Windows (VMware not applied) No limitations Image recovery Management LAN SAN System backup for recovery is saved on management server. Recovery achieved by restoring via management LAN. When server fails, recovery achieved by connecting to system image on SAN and rebooting on spare server Recovery Management server Spare server operation server Operational server Spare server Boot typeLocal bootSAN boot
Copyright 2007 FUJITSU LIMITED 14 Server recovery in local boot environment Notes ・ Image restore (around 1 hour) and operation confirmation enables recovery within a few hours. ・ VMware environment (VM Host, VM Guest) image is not included. ・ Backup restore of system and data disks not included in backup/estore. ・ The size of the spare server disk should be the same as the original application server disk. Functions Create backup images in advance from embedded system volume, deploy to a spare server and boot spare server when server is down. Operation will then restarted at the moment the backup is received by spare server. The failed server#3 is replaced by spare server and server#3 repaired. Application on spare server can be moved back to repaired server#3. When spare server not available, backup images of failed server can be restored to a replaced server. Switch blade port VLAN setting is automatic. Effects Enables quick recovery even if Windows, Linux and virtual servers are in a mixed environment. Spare server can be shared by multiple managed servers. Linux Blade #1 Win Blade #2 Win Blade #3 Spare server Back up image RC VE Management Server Blade #3 Blade #2 Blade #1 Deployment Recovery
Copyright 2007 FUJITSU LIMITED 15 Server recovery in SAN boot environment Recovery time from failed server to spare server shortened. (to just a few minutes) Server can be replaced without reconfiguring SAN environment. Switch blade port VLAN can be set automatically. Spare server can stand by in a stopped state. Saves power consumption. Spare server can be shared between multiple managed servers. Functions Effects Combining with ETERNUS SF Storage Cruiser 、 enables SAN storage configuration and visualization. Note SAN connection needs WWN zoning. I/O virtualization (FC) arrangement is also necessary. Appl “A” Appl “B” Blade#2Blade#3Blade#1 Appl “A”Appl “B” In normal situation Appl “A” Blade#3Blade#1 Appl “A” SAN Blade Appl “B” Blade#2 Appl “B” Physical server(Blade#1) When server fails Recovery Automates recovery to spare server when failure detected. No need to reconfigure SAN environment when spare server starts operation. Shortens recovery time.
Copyright 2007 FUJITSU LIMITED 16 Quick recovery in VMware environment Cold standby is possible just using VMware Standard for lower costs. Recovery from failed to spare server can be completed quickly. (in just a few minutes) With SAN connectivity virtualization functionality, recovery can be conducted without reconfiguring SAN environment. Spare server can stand by without power on. Spare server can be shared by multiple application servers. Spare server can also be shared by physical & virtual servers. Function Effects VM Host Appl “B”Appl “C” Blade#2Blade#3 Appl “B” Appl “C” ESX Server In normal operation VM ホスト VM Host Appl ”B” Appl ”C” Blade#2Blade#3 Appl “B” Appl “C” ESX Server Physical server(Blade#2) When a server fails Appl “B” Appl “C” SAN Blade VM Host APPL “A” Blade#2 Appl “A” VM Host Appl “A” Blade#2 Appl “A” ESX Server Recovery Automates recovery in VMware Standard environment by configuring ESX server on SAN SAN ESX Server RC VE
Copyright 2007 FUJITSU LIMITED 17 Quick recovery by VMotion The best way to recovery can be chosen according to different situations. Failed server recovery can be performed even in VMware VMotion environments. Functions Effects Automated recovery by RC VE when server fails. Manual shift by VMotion when server is maintained and stops working. If VM Guest is running on the spare server, shifting by SAN boot cannot be done. VM Host APPL “B”APPL “C” Blade#2Blade#3 APPL “B” APPL “C” ESX Server ESX Server In normal operation VM Host APPL “B”APPL “C” Blade#2Blade#3 APPL “B” APPL “C” ESX Server ESX Server When a virtual server is maintained APPL “B”APPL “C” VM ホスト VM Host APPL “B”APPL “C” Blade#2Blade#3 APPL “B” APPL “C” ESX Server ESX Server When a virtual server fails APPL “B”APPL “C” SAN Blade server VM Host APPL “A” Blade#1 APPL “A” ESX Server SAN Blade server VM Host APPL “A” Blade#1 APPL “A” ESX Server SAN Blade server VM Host APPL “A” Blade#1 APPL “A” ESX Server Recovery RC VE VMotion
Copyright 2007 FUJITSU LIMITED 18 Server recovery in VMware HA environment Functions Automated recovery can be done in cooperation with VMware ESX Server. If VM Guest is running on the spare server shifting by SAN boot is not possible. Effect Spare server can be used by physical servers in VMware HA environment. APPL “A” VM Host APPL “B”APPL “C” Blade#2Blade#3Blade#1 APPL “A” APPL “B” APPL “C” ESX Server ESX Server In normal operation APPL “A” VM Host APPL “B”APPL “C” Blade#2Blade#3Blade#1 APPL “A” APPL “B” APPL “C” ESX Server ESX Server When a virtual server fails APPL “A” VM Host APPL “B”APPL “C” Blade#2Blade#3Blade#1 APPL “A” APPL “B” APPL “C” ESX Server ESX Server When a physical server fails APPL “A” APPL “B”APPL “C” SAN Blade server Recovery VM HA RC VE
Copyright 2007 FUJITSU LIMITED 19 Internal disk structure management image Management client Management server Management LAN Management target RC VE Manager RC VE Client ( for free ) Windows PRIMERGY BX620S4 Management blade Switch blade RC VE Agent RC VE Agent RC VE Agent VMware ESX Server VMware ESX Server Windows Linux RC VE Agent Operation server Spare server Operation server OperationserverOperationserver
Copyright 2007 FUJITSU LIMITED 20 SAN connectivity management image Management client Management server Management LAN Management target RC VE manager RC VE Client ( for free ) Windows PRIMERGY PRIMERGY BX620S4 Management blade Switch blade RC VE Agent RC VE Agent RC VE Agent VMware ESX Server VMware ESX Server Windows Linux RC VE Agent Operation server Spare server Operation server HBA address rename configuration service RC VE Client ( for free ) Windows FC switch blade ETERNUS System disc System disc System disc Storage management by ETERNUS SF Storage Cruiser
Copyright 2007 FUJITSU LIMITED 21