RmCm and Outbound Subsystem Verification

From DocWiki

Jump to: navigation, search

RmCm and Outbound Subsystem Verification

Problem Summary The Outbound subsystem is not changing state to IN SERVICE from INITIALIZING.
Error Message N/A
Possible Cause During a fail over, it might take a couple of minutes before the Outbound subsystem displays the correct state IN SERVICE as the verification cycle needs to complete.
Recommended Action

For the Outbound subsystem to be IN SERVICE, the following conditions apply:

  • The RmCm subsystem on the same box must also be in service. The RmCm subsystem is considered to be active when you have provisioned the RmCm Provider and its associated agent extensions.
  • The Unified CCX Database service (on the publisher node) should be up and running. For example, if you have a dual node (Node A and B) setup with Node A as the publisher node, you need to have the Unified CCX Database service up and running on Node A for the Outbound subsystem to be IN SERVICE.

Note - The publisher node will always be the first node installed in the cluster. On the standby service, if all four nodes are up and running and RmCM is in service, then the Outbound subsystem is IN SERVICE.

Release Release 10.5(1)
Associated CDETS # N/A

Rating: 0.0/5 (0 votes cast)

Personal tools