Cisco Cisco UCS B440 M1 High-Performance Blade Server Weißbuch
© 2011 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public Information.
Page 79 of 83
among multiple departments and applications. Users can tailor the cost and acceptable risk by varying the size of
these shared resource pools.
The subsequent sections detail the migration of Service Profile created for Oracle WebLogic Server hardware, thus
utilizing the statelessness benefits of the Cisco Unified Computing System.
4.6.1 Service Profile Migration
In the present setup, there is a single Oracle WebLogic server hardware, with multiple WebLogic Managed
Servers instantiated in a WebLogic Cluster. In the event of hardware failure, migrate the Service profile of
WebLogic Server hardware to another server, which would help ensure minimal downtime for application server
environment and faster deployment of new hardware deployed with WebLogic Server Cluster.
In the event of multiple physical servers for WebLogic Cluster deployment, youwill achieve lossless end-user
services, as Service Profile of failed physical server would be migrated to the redundant physical server.
The pre-requisites to successfully migrate the failed WebLogic Cluster physical server to a available stand-by
areSANBoot of OEL5.5.
Tasks #
Task Description
1.
Verify Setup. We have Slot 3 assigned to Service Profileb230-WebLogic1.This is the
physical server wherethe Oracle WebLogic Cluster is deployed.
physical server wherethe Oracle WebLogic Cluster is deployed.
Verify the partID of Blade3 = JAF1503AMGA
2.
On event of Server Failure we would migrate this Service Profile of Server3 to Server4
(stand-by server) and verify status of WebLogic Cluster.
Disassociate Service profile b230-WebLogic1.
(stand-by server) and verify status of WebLogic Cluster.
Disassociate Service profile b230-WebLogic1.