Deploying Non-HA components in MSCS：骨髓间充质干细胞非HA组件部署.pptVIP

Deploying non-HA Components in a Microsoft Cluster Environment Unicenter NSM Release 11.1 Last Revision March 15, 2007 Glossary The following terms and abbreviations are used in this presentation: “HA” = Highly Available “NSM” = Unicenter Network Systems Management “USD” = Unicenter Service Desk “MSCS” = Microsoft Cluster Server “Cluster Name” = Network name associated with the cluster group “AMS” = Unicenter Alert Management System “UNS” = Unicenter Notification System Disclaimer This presentation pertains to Unicenter NSM r11.1; it is not designed to apply to r11.0 This document represents field best practice. As such, it is supported on a “best effort” basis - as are any field developed tools. CA reserves to right to update this document as needed in response to any issue. Therefore, you should check for an updated version before opening any issue related to this best practice. Disclaimer This presentation is not a substitute for MSCS skills. In order to implement HA for NSM via MSCS or to apply this best practice you should have these skills. Objectives The procedures provided in the presentation are designed for architectures where: as part of a migration from Unicenter NSM 3.1 to NSM r11.1, non-HA and HA components must intermix Certain components, such as the Alert Management System (AMS), which is not HA, must be installed with other components which are. Scope Installation of the non-HA components is summarized Information on how to make these non HA components Highly Available is beyond the scope of this presentation. However, wherever possible, testing has been carried out with the view to make them HA Non-HA Components Alert Management System (AMS) Unicenter Notification Service (UNS) EM Provider Unicenter Repository Bridge Unicenter Dynamic Containment Service (DCS) The following Agent Technology (AT) components: OS Agent Gateway AS/400 Agent Active Directory Services Agent For additional information….. Appendix C “Making Components Clust