PRIMERGY Installation

PRIMERGY Installation
Release July, 2007 PRIMERGY Installation ServerView Architecture and Management Fujitsu Siemens Computers training documentation [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView Architecture & Management
PRIMERGY Installation Release July, 2007 ServerView Architecture & Management ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView S2 - Architecture for Flexibility
PRIMERGY Installation Release July, 2007 ServerView S2 - Architecture for Flexibility Web Browser based Management Console Central Management Station Central Monitoring/Management of PRIMERPOWER via ServerView Central Management Station. Detailed Management of PRIMEPOWER Servers via call of PW ServerView out of ServerView Serverlist. Levels: Console Web browser Central Management Station ServerView Suite & Web server Administration Health monitoring Event Management Performance Management Asset Management Update Management Database Deployment services ServerStart Remote Installation Service RemoteView RSB Concentrator, Soft RSB Managed nodes Agents Managed Servers & Devices Integrating & integrated ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Server Management – Scenario
PRIMERGY Installation Release July, 2007 PRIMERGY Server Management – Scenario This scenario allows access to information via SNMP and the ServerView Console “Win32” AND via HTTP and “ServerView S2”. ServerView “Win32” is the old/classic ServerView and is still available as part of ServerView S2. Add wireless access and voilá: management anytime, anywhere! Make your customer aware of the fact that ServerView ist not limited to FujitsuSiemens Computers products, but is able to process events, faults and display at minimum basic status / health information on third-party systems. This does need some customizing, but nothing closely as much as would be necessary to customize a Tivoli TME environment. Vice-Versa is also true: PRIMERGY servers can be easily integrated in to existing management infrastructures such as: OpenView, CA Unicenter, Tivoli TME 10 or even HP insight manager / systems insight manager! Should a customer use the common excuse: “I am already using Proliants and running Insight Manager…” you should answer: “That is excellent! That saves us much time and money, because the initial implementation is already complete!” ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Structured View: ServerView S2 Console
PRIMERGY Installation Release July, 2007 Structured View: ServerView S2 Console Tool Navigation Serverlist Filter View Area Easy to Navigate Customized server list, function navigation bar, filter bar, information Work efficiently thru group policies Focus on important events Increase stability thru homogenous settings & instant event handling Increase uptime thru tight control Deliver improved service level ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView S2 – Web Server
PRIMERGY Installation Release July, 2007 ServerView S2 – Web Server WebServer =IIS =>Windows user and IIS security Apache or IIS HTTP(S) + ServerView S2 ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView S2 – Apache User
PRIMERGY Installation Release July, 2007 ServerView S2 – Apache User User “admin” (in passwd) add users in passwd with Webserver\bin\htpasswd.exe. Apache HTTP(S) \Webserver\bin\ passwd logon with Apache user “admin” + ServerView S2 ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView S2 – Apache + SSPI
PRIMERGY Installation Release July, 2007 ServerView S2 – Apache + SSPI serverxx\administrator or fsctraining\administrator Apache HTTP(S) local Windows user logon with Windows user e.g. “administrator” + ServerView S2 or Domain user Domain controller ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 One (logical) Central Management Station Example: Virtualization managed with ServerView Virtual machines Console OS VMware MIB SNMP ServerView Agent-MIB Server Management is an essential success factor for a modern IT. To get the necessary information about a malfunction of a server, sometimes even before the a real problem occurs is a foundation for a reliable server platform. The low-level system status information is created by a cooperation of specific hardware control mechanism and dedicated management agents delivered by the hardware vendor. These agents normally reside deep in the kernel of the Operating System. Fujitsu Siemens Computer has developed a dedicated agent for VMware ESX Server, based on the proven ServerView concept. It delivers all specific information concerning the server hardware and components to assure a smooth operation. Traditional agents for the guest OS of each VM could be used without changes. But please do not check the temperatures of a virtual CPU, the result might be unpredictable :=)) VMware ESX Server Management Station ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView Agents / PDA & LED’s
PRIMERGY Installation Release July, 2007 ServerView Agents / PDA & LED’s ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY ServerView Management Agents
PRIMERGY Installation Release July, 2007 PRIMERGY ServerView Management Agents Collect data Respond to SNMP requests Generate HW-specific traps PRIMERGY agents are responsible for hardware information Other agents: UPS, Mylex / LSI, etc. Mgmt. Agents SNMP UDP/ IP These agents provide specific information on PRIMERGY server health and status. The agents is responsible for collecting data about the system, and to forward the traps from the system to a management console. The agent are also responsible to set information received from SNMP. When a request for system information is recived, the agent will gather the requested information and pass it on to the SNMP service. In a typical server you will find several agents, UPS, Raid controllers and other manageable devices. You will also find SNMP Agents in peripheral devices such as routers, switches and so on. Console ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView Agent Security
PRIMERGY Installation Release July, 2007 ServerView Agent Security No Security Everyone has full read + write control Fujitsu Siemens Computers server management agents support a wide range of security mechanisms. Due to the inherent weaknesses of SNMP V1, Fujitsu Siemens Computers provides three different levels of security. All security levels are set during agent installation. “No Security” is simple enough: Full access for everyone, sets are permitted and remote reboot / shutdown is enabled. Mgmt. Agents SNMP UDP/ IP Console SetRequest GetRequest, Trap ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 ServerView Agent Security High Security Everyone has read control, no one has write control Fujitsu Siemens Computers server management agents support a wide range of security mechanisms. Due to the inherent weaknesses of SNMP V1, Fujitsu Siemens Computers provides three different levels of security. All security levels are set during agent installation. “High Security” is also simple enough: Read access for everyone, sets are not permitted and remote reboot / shutdown is disabled. Mgmt. Agents SNMP UDP/ IP Console SetRequest GetRequest, Trap ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 ServerView Agent Security User Group based security with NT Authentication Authentication based on Windows security For full functionality coupled with acceptable security, user group based security can be used to authenticate users against the Windows user database. This is a feature unique to PRIMERGY and provides the best compromise between security without sacrificing too much security. This feature is only available when using ServerView as the console/front end. Do not use this security model with other consoles as set operations will fail. This is also configured during agent installation (this will be the method of choice during the lab). Normally, the specified user group would be “administrators”. This keeps things simple and gives those people access who are authorized anyway. Keep in mind though, that the encryption mechanism is not very strong. Transmitting an administrator password only slightly hashed is often not an option. For tighter security, you may also specify any other existing local user group or domain local user group (attention: domain groups are not supported for this feature!) and add special users for this purpose only. if no suitable groups exist, you have two choices: Create a dedicated group and add those users who are to have write (set) access to the agents. Create a dedicated group and create one or more dedicated users who are member of this group only. For maximum security, the only privilege they need is “log on locally”. A “set” authentication therefore takes place in three steps: #1 check the existence of the user in the DB #2 check if the password stored there is identical to the one supplied. #3 check if the SNMP community supplied fits Only if all three criteria are fulfilled does the set take place. Windows Console Authorized User Group Challenge for SetRequest Mgmt. Agents SetRequest SNMP UDP/ IP GetRequest, Trap ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Simply have a look inside …
PRIMERGY Installation Release July, 2007 Simply have a look inside … Graphical state of the art presentation of component states PSU via WMI scripts SEL System Event Log = chip on MoBo PDA (Prefailure Detection & Analysis) is watching for degradation of “good” values At “low” value a warning is sent to System Event Log OS-Event-Log ServerView Event Management ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Resolving issues before your service is impaired
PRIMERGY Installation Release July, 2007 Resolving issues before your service is impaired ServerView runs PDA = Prefailure Detection and Analysis PDA is watching for degradation of “good” values At “low” value, a warning is sent PSU via WMI scripts SEL System Event Log = chip on MoBo PDA (Prefailure Detection & Analysis) is watching for degradation of “good” values At “low” value a warning is sent to System Event Log OS-Event-Log ServerView Event Management Exchange component timely before failure Increase reliability proactively ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Quick localization of broken parts reduce downtime & save service costs Locator Light, System State, LocalView Display & onboard LEDs Helping to find the broken parts easily, switch on/off from ServerView - GUI ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Alarm Management ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Always knowing what’s up: Best-in-class Alarm Management for proactive management Alarm Monitor Receives all alarms (SNMP traps) Alarm Manager Management of stored Alarms Alarm – Tracking Alarm Settings General Settings Alarm forwarding … Online Help Comprehensive e.g. description of all SNMP traps ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Always knowing what`s up: Best-in-class Alarm Management for proactive management Alarm Monitor (Console) Alarm Manager ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView Alarm Service
PRIMERGY Installation Release July, 2007 ServerView Alarm Service Scenario #1: Central / Remote Event Handling Mgmt. Agent SNMP UDP/ IP Filtering Logging Forwarding Automation Web Interface HTTPS Mgmt. Agent SNMP UDP/ IP This scenario would be typically used: In large environments where a centralized management console is desired. In environments where ServerView is in use. Alarm Service integrates with ServerView (launch button, server/device list extracted from ServerView, display of events within ServerView). For best results, install Alarm Service on the same machine as ServerView. NOTE: The central ServerView / AlarmSerice console must be running at all times to receive and handle traps. Fujitsu Siemens Computers recommends a dedicated computer for this task. SNMP TAP / SMS Mgmt. Agent SNMP UDP/ IP SMTP / MAPI ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView Alarm Service
PRIMERGY Installation Release July, 2007 ServerView Alarm Service Scenario #2: Local Event Handling Mgmt. Agent SNMP SNMP This scenario would be typically used: In small environments with few servers, where ServerView itself would be too complex. By service partners wishing to provide decentralized event management services to their customers. This course will be simulating scenario #2. You will install Alarm Service on the PRIMERGY itself and configure it to forward s based on some generally useful rules. Location A Location B Mgmt. Agent SNMP SMTP / MAPI Mgmt. Agent SNMP TAP / SMS ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView Alarm Service Configuration and Use
PRIMERGY Installation Release July, 2007 ServerView Alarm Service Configuration and Use Traps are sent to AlarmService for processing AlarmService must be trap destination Devices to be handled must be known: use ServerView or WebExtension to edit server list Mgmt. Agent SNMP UDP/ IP HTTPS Mgmt. Agent SNMP UDP/ IP SNMP traps TAP / SMS SMTP / MAPI The following slides give a schematic overview over the configuration and function of AlarmService. AlarmService must be entered as a trap destination in the SNMP properties. This can happen either during ServerStart or manually from within Windows. Note that in our lab (as in scenario #2 on the previous slide), servers will be sending traps to „themselves“ or SeverStart SNMP / trap configuration Trap enters AlarmService here Overall settings: Global parameters Filter Server: Ignore these Servers! Edit / New Alarmgroup: Conditions met? Set / Edit destinations: Do it! Notifications sent+ Scripts executed ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 ServerView Alarm Service Configuration and Use Overall settings Default / global parameters Defines how to handle traps before processing them This screen configures important global settings. DEFINITION: This guide will use „to filter“ in the following sense: Filtered events do not pass the stage and are discarded/ignored/held back. Filter settings Set time for repetition in sec: Events occurring in intervals shorter than the interval specified here will be filtered. This is useful for preventing „chatter storms“ such as often caused by NICs with a poor network connection. Filter... Checkboxes: Allows to filter events by severity. Be careful with this setting! It would not be smart to filter critical events at this stage, even though it is technically possible! Delete Alarm Specifies when an alarm is to be deleted. The alarm can be deleted when it has reached a specified age, or when a specified number of entries have been made in the Log list. Alarm Actions This Pop Up refers to restoring the alarm monitor window to its original size. Log stores the event in the alarm manager log. Alarm Manager Specifies how to many entries the log may have and what to do if the maximum number of entries is exceeded. Default Alarm handling Pop up a message will generate a local pop up box in the screen. Beware of this setting, as activating it will pop up a message for each and every trap received! This can be very irritating when rebooting a server, since every reboot generates 2-3 traps. Or coming back to a server after a longer period of absence you will most certainly find the explorer window full of pop ups from the past. Store in Event Log This will store a message in the Windows event log. Trap enters AlarmService here Overall settings: Global parameters Filter Server: Ignore these Servers! Edit / New Alarmgroup: Conditions met? Set / Edit destinations: Do it! Notifications sent+ Scripts executed ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 ServerView Alarm Service Configuration and Use Filter Server Default / global parameters Defines which servers to ingore The Filter server settings defines wich servers to ignore, and wich servers to handle traps from. Trap enters AlarmService here Overall settings: Global parameters Filter Server: Ignore these Servers! Edit / New Alarmgroup: Conditions met? Set / Edit destinations: Do it! Notifications sent+ Scripts executed ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 ServerView Alarm Service Configuration and Use Edit / New Alarmgroup Settings for special processing Definition of servers and alarms to be handled Set of conditions to be met before trap is handled AlarmService needs criteria on which to act. These criteria can be: server name, event name, event severity, event source, etc. This window allows you to define these criteria: If you want traps from a specific server or from multiple servers to be handled, include them in the group by moving them to the right hand side of the select server window. Then you might want to specify which events are supposed to trigger something. This could be done by severity, type, etc. Add these events/traps in the left half of the window. IMPORTANT: Due to a bug, you may not use any special characters or spaces in the alarm group name. Doing so will cause strange effects in the configuration wizard and/or unreliable event handling. „&“ being used in the lab seems to be one of the only characters acceptable. “_” has also been verified and should work. Trap enters AlarmService here Overall settings: Global parameters Filter Server: Ignore these Servers! Edit / New Alarmgroup: Conditions met? Set / Edit destinations: Do it! Notifications sent+ Scripts executed ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 ServerView Alarm Service Configuration and Use Set / Edit destinations Notification and script execution settings Associated with alarm groups If criteria in alarm group are met, associated destinations are triggered When an event has met all the criteria in the previous slide, AlarmService must act on it. This action is configured here. The AlarmService can be configured to send , Popups, Logg to Event logs, Send Pager, send Broadcasts or to execute scripts. Trap enters AlarmService here Overall settings: Global parameters Filter Server: Ignore these Servers! Edit / New Alarmgroup: Conditions met? Set / Edit destinations: Do it! Notifications sent+ Scripts executed ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 ServerView Alarm Service Configuration and Use Output Notifications Scripts Logs The output leaves AlarmService here. Note the same event in the alarm monitor and as an . Trap enters AlarmService here Overall settings: Global parameters Filter Server: Ignore these Servers! Edit / New Alarmgroup: Conditions met? Set / Edit destinations: Do it! Notifications sent + Scripts executed ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Monitoring ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView S2 Asset Management: Export
PRIMERGY Installation Release July, 2007 ServerView S2 Asset Management: Export Flexible, efficient, centralized Forwarding Scheduled Export Export-Manager Web-based released for Windows Platform, prepared for Linux multiple Server Support integrated API (SMTP) Update-Info can also be exported (multiple server) Queries (SQL-DB) examples of queries described in manual creation of own queries Service Provider SQL-DB csv file ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

ServerView S2 Update Management
PRIMERGY Installation Release July, 2007 ServerView S2 Update Management Inventory view / Update view Shows Inventory data of Windows and Linux Servers Integrated UpdateView for each single Server Helpful Filter options Inventory Agents available for Windows and Linux platform ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Optimization opportunities? Performance Management
PRIMERGY Installation Release July, 2007 Optimization opportunities? Performance Management Information for administrators, decision makers, service staff Input for trend & problem analysis thru Rule based monitoring of CPU Memory File system NICs Performance analysis Comprehensive Reports Search for Peak-Values Correlate peak values with running processes Export of Reports into .CSV file From „boxes“ to resources For automation in the Dynamic Data Center ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Optimization opportunities? Performance Management
PRIMERGY Installation Release July, 2007 Optimization opportunities? Performance Management Comprehensive & powerful reporting Line Chart Select reports in Serverlist Graphical presentation of Performance Reports Definition of thresholds (Threshold management) Creation of rules / groups of rules Supported components: CPU, Memory, File system, NIC execution of rules on every managed server possible (copy/paste) administration of rules on the central management server Results: Delivers input for Trend Analysis & Problem analysis Provides information for administrators, decision makers, service staff Local recording of performance values of CPU Memory File system NIC Analysis of performance reports Creation of rules and groups of rules for generation of reports Bar Chart Line chart with peak values ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Archiving: know what you have (had)
PRIMERGY Installation Release July, 2007 Archiving: know what you have (had) Reduce costs for error analysis & localization compare archives of the same server compare data of different servers Archive Manager Archiving of all server data incl. busses and adapters, Cyclic new inquiry and storage, Central storage on the management station, Import, comparison, analysis of archive data (also between servers). Useable for all PRIMERGY servers in the network Advantages: All information available, also when server breaks down, Information useable for error diagnosis, Central data backup, Comparison of two servers for quick detection of changes Functions: Configuration overview: Central archiving, Dispatch per , Fast diagnosis in service centers, Access on offline data, Lifecycle management: Storing the server history, Documentation of changes, Graphical display of the changes Error analysis through: comparison of configuration of one or two servers at same/different time What can be seen: Trend information, like disks/systems getting more loaded, temperatures rising, fans degrading Configuration changes Select Servers Select Archives See Changes ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Management of PRIMERGY Blade Servers
PRIMERGY Installation Release July, 2007 Management of PRIMERGY Blade Servers ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 Management of PRIMERGY Blade Servers Full integration & uniform management Detailed information on Server Blades, Switch Blades, Mgmt Blades Special icons for quick identification Full integration & uniform management: Blade Server is fully integrated in PY ServerView Suite. This maps with our approach of uniform management : Server List, Alarm Management and further SVS Components can be used transparently throughout the all PY platforms. Of course platform specific management, e.g. for detailed failure analysis , is integrated as easy as possible. ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation Release July, 2007 Management of PRIMERGY Blade Servers ServerBlade – Systemboard View ServerBlade – Controller View Detail – Analysis through different component views. ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Remote Management ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Remote Management anywhere, anytime
PRIMERGY Installation Release July, 2007 Remote Management anywhere, anytime No Operating System Access ? use iRMc “backdoor” Scan for manageable nodes & Configure your settings: SNMP, passwords, server addresses, users, network Handling of Restart, Power ON/OFF, watchdogs Failure handling: ASR&R automatic server reconfiguration & restart Immediate insight to status thru color coding green, yellow, red Grouping in server list for better overview Easy overview even for large networks thru comfortable filtering LDSM LAN Desk Server Manager Status View for managed nodes PRIMERGY servers other TCP/IP devices (online/offline state only) More settings: Administration of call integrated products (RD, APC powerchute BE) Configuration of Remote Service Board Operation: Low system load thru configurable polling special icon ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

No Operating System up or system hangs? You still got control
PRIMERGY Installation Release July, 2007 No Operating System up or system hangs? You still got control Remote repair with iRMC Remote power on/off Forced main operating system reboot Change Set-up via remote console Text console redirection Remote repair with fully independent powerful Management Controller Integrated Remote Management Controller (iRMC) iRMC Note: iRMC in new PRIMERGY TX and RX Servers consolidates BMC and RSB functionality and covers all management levels (1 to 3). iRMC with basic features complies to BMC functionality. With activated Advanced features it complies to the RSB. Management Products: Level 1 Server Management (ServerView) In-band Management: Operating system (OS) and ServerView agents are working Agents communicate via OS with the front-end (management station) Management Information and server control via IPMI 1.5 compatible Baseboard Management Controller (BMC) Redundant access possible (per Server and/or RSB) Level 2 Remote Management (RemoteView) Out-of-band Management: Basis functions of the system boards are working Operating system is not booted, diagnosis operating system can be booted Basic remote management like power management or text consol redirection with Baseboard Management Controller (BMC/IPMI) and RemoteView front-end Level 3 Remote Management (RemoteView and RemoteView Service Board): Out-of-band Management SSL-secured access only possible via RSB independent of basis system board functions, with full graphical console redirection and remote boot images (ACR for keyboard, video, mouse and ADR for remote boot with disk images) Hardware: Remote Service Board (Option): Own Processor, Own OS, Own Web server, Own Access over LAN or Modem, External power “Automatic Server Reconfiguration and Restart” (ASR&R) prevents a system failure even if a processor or a whole memory module fails: The server automatically restarts and the defective components are removed from the configuration. The server then continues to work without the defective component (s). ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Integrated Remote Management Controller Basic features
PRIMERGY Installation Release July, 2007 Integrated Remote Management Controller Basic features For free Comprehensive System Monitoring and Control Text – Console redirection via LAN and Serial line Online firmware update Power Management (power on/off/cycle) Integrated Alarm Management Independent (Service) LAN access* Authentication: iRMC database/user management Support of Standards IPMI 2.0 standard HTTPS/SSL (128bit) iRMC Alarm management: - Platform Event Traps via SNMP: common acronym is PET - ServerView traps: ServerView SNMP traps from ServerView agent Use of enhanced features (Advanced Pack) only with „Activation Key“! *)System dependent ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Integrated Remote Management Controller Advanced Video Redirection (Advanced Pack) Charged High performance Advanced Video Redirection (AVR) Embedded KVM-Switch over IP True Headless support Hardware-video compression low net load Ethernet 10/100 Enables for: “Local” consol functionality for any system state Monitoring of Remote Boot BIOS Administration & Operating System handling ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Integrated Remote Management Controller Remote Storage (Advanced Pack)
PRIMERGY Installation Release July, 2007 Integrated Remote Management Controller Remote Storage (Advanced Pack) Charged On Management Station Access local drives or ISO image Remote storage appears as local drives in managed Server Simple usage analog to local devices USB interface for local storage Driver free solution Management Station Romote Storage ISO Images, FD, CD, DVD USB stick At boot time, a floppy at USB would run as A: Do not use C: to avoid issues at installation time install OS or applications: Performance improvements demanded, possible but not recommended yet !  LAN Enables for: “F:” Boot from local or Remote Storage device Read and write data Remote BIOS update install Operating System or applications Managed Server ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Remote Management - Scenario
PRIMERGY Installation Release July, 2007 PRIMERGY Remote Management - Scenario Customer Partner Console Server Fault! ServerView This scenario assumes that the customer is not willing to invest in a ServerView Console. The RemoteView board takes care of emergency remote control. ServerView SNMP Agents and AlarmService take care of Fault Management and Status Checking. It is worthy to note that many SME customers such as doctors, travel agencies, lawyers etc. often already use a remote control system to support their special software. That makes the concept well known to them and lowers the threshold of reluctance. General Requirements for the environment shown above: Network must be transparent for SNMP + HTTPS + SMTP Agents must be installed and configured on each server to be managed AlarmService must be installed and configured on each server to be managed Secure Remote Access must be established between partner and customer If notification is used: An SMTP or MAPI compatible mail-account must be available for use by AlarmService If RSB is used: Must be installed and configured on each server to be managed NIC Browser Gateway/ VPN SMTP HTTPS SNMP Client AlarmService ServerView SNMP Agents Management Blade* Baseboard Management Controller WAN Gateway/ VPN RemoteView ServiceBoard Integrated Remote Management Ctrl *) in BladeServers ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Exercise 09 Firmware Update Manager ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Release July, 2007 Exercise 10 Install and Configure basic PRIMERGY Server Management ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

Thank you for your attention.
PRIMERGY Installation Release July, 2007 Thank you very much for your attention. Thank you for your attention. ServerView Architecture & Management PRIMERGY Installation Release November © Fujitsu Siemens Computers All rights reserved [Name of the chapter as on the agenda] © Fujitsu Siemens Computers [Year]

PRIMERGY Installation

Similar presentations

Presentation on theme: "PRIMERGY Installation"— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

PRIMERGY Installation

Similar presentations

Presentation on theme: "PRIMERGY Installation"— Presentation transcript:

Similar presentations

About project

Feedback