Services
This feature allows for flexible network deployment by allowing you to map an application service to a specific network. Additionally, this feature allows for the differentiation of intra- and inter-networks on a per service basis. This means that traffic from different services can be segmented, which allows for service specific-networks and routes. This is predicated on the creation of network elements, networks, and routes to support the segmentation of service traffic.
Geo-redundant (spare) nodes and dual-path monitoring are special code on the node at the spare site that continually monitors the availability of the database instances at the primary site to determine if an automatic failover should occur due to loss of the active site servers. In the event of a network outage, it is possible that if the system is monitoring a single network path only and intra- and inter-networks are differentiated, an erroneous condition might occur where both sites try to assume activity. Inherent dual-path monitoring protects against this scenario.
- OAM
- Replication
- Signaling
- HA_Secondary
- HA_MP_Secondary
- Replication_MP
Table 3-7 Core Services
Name | Intra-NE Network | Inter-NE Network |
---|---|---|
OAM | Unspecified | Unspecified |
Replication | LAN1 | WAN1 |
Signaling | Unspecified | Unspecified |
HA_Secondary | Unspecified | Unspecified |
HA_MP_Secondary | Unspecified | Unspecified |
Replication_MP | LAN1 | WAN2 |
Note:
Services might vary depending on the application. For example, DSR adds a service known as ComAgent to the existing core services. Additionally, workflow and provisioning instruction might differ from the direction provided here. Always follow the provisioning guidelines for your specific application and release.