ZMS High Availability Management: ZMS-NMS-TRX-HA, ZMS-NMS-TRX-HA-DST

Overview

ZMS HA is a high availability solution for the ZMS server. This two-node redundancy configuration offers protection against a single point of failure in the ZMS. A disaster recovery option may be added to the ZMS HA solution, providing a remote hot standby server for recovery in the event of a catastrophic failure of the ZMS HA system. The ZMS HA solution offers automatic cut-over to the redundant hardware/software component when an error is detected. The ZMS High Availability (HA) solution requires two local ZMS servers with a shared disk array and redundant hardware including: disk controllers, network interfaces, and power supplies. Disaster recovery can be added to the ZMS HA configuration by including a 3rd-server that is remotely located from the primary ZMS HA cluster.

The ZMS HA solution utilizes Oracle Realtime Application Cluster architecture to provide a single system image allowing multiple servers to access a single ZMS database. The ZMS HA cluster consists of two nodes, one in active mode and the other in standby. All devices and ZMS clients access the ZMS HA system using a Virtual IP (VIP) address. The Oracle cluster software maps this Virtual IP address to the active server. When a failure occurs in the active ZMS server, there is a rapid automatic switch-over to the standby ZMS HA server. The Oracle cluster software automatically handles the re-mapping of the VIP to the new active server making this change transparent to the devices and clients.

When a remote disaster recovery server is added to an ZMS HA configuration, the remote hot standby server receives database updates from the HA system providing database synchronization. In the event of a catastrophic failure at the ZMS HA site, a manual failover to the remote hot standby server can be performed within a short time frame.

View printable version

Specifications

Features
  • Built on industry-leading high availability architecture
  • Protection against single-point of failure
  • Faster error detection and recovery with automatic cut-over on failure
  • Scalability across database instances
  • Flexibility to provide future processing capacity without additional hardware
  • Presents single system image to ZMS clients and devicesDisaster recovery option offers remote ZMS backup server in hot standby mode, for fast switch-over in the event of catastrophic failure of ZMS HA system
Management Interfaces
  • OSS Gateway
  • Northbound Corba IDL
  • XML
  • Configuration, provisioning, status, inventory and capacity information
Computing Platform Requirements

Software Environment

  • Solaris 10

Hardware

  • Tier 2: Oracle SPARC T4-1
  • Tier 3: Oracle SPARC T4-2

Ordering Information

Model
Description
ZMS-NMS-TR2-HA
High availability feature license for ZMS Tier 2 system (up to 1000 MSANs with 100,000 CPEs/400,000 connections), requires ZMS-NMS-TR2 and ZMS-NMS-TR2_STNDBY licenses
ZMS-NMS-TR3-HA
High availability feature license for ZMS Tier 3 system (up to 2000 MSANs with 1,000,000,000 CPEs/4,000,000 connections), requires ZMS-NMS-TR3 and ZMS-NMS-TR3_STNDBY licenses
ZMS-NMS-TR2-HA-DST
Disaster Recovery feature license for ZMS HA Tier 2 system (up to 1000 MSANs with 100,000 CPEs/400,000 connections), requires ZMS-NMS-TR2 and ZMS-NMS-TR2_STNBY and ZMS-NMS-TR2-HA licenses
ZMS-NMS-TR3-HA-DST
Disaster Recovery feature license for ZMS HA Tier 2 system (up to 2,000 MSANs with 1,000,000 CPEs/4,000,000 connections), requires ZMS-NMS-TR3 and ZMS-NMS-TR3_STNBY and ZMS-NMS-TR3-HA licenses