System Management Core Instance
Core instances display in alphabetical order in the System Management user interface. During normal conditions in a high availability environment, one core instance is in Backup mode while the other is in Primary mode (highlighted green). Queue Manager is running on the core instance that is in Primary mode. In a standalone environment, only one core instance is displayed, which is always in Primary mode (highlighted blue).
Each core instance displays its name, mode, and any components associated with it. Non-controllable components are shaded gray and listed first (in alphabetical order). Controllable components are unshaded and listed second in alphabetical order).
The Make Primary button appears on the instance that is in Backup mode. The Maintenance button appears on all core instances.
Data displayed in an instance appears in the System Management user interface and updates automatically every five seconds. If an instance or component is removed, it may remain in the System Management user interface until the configuration is updated or page is refreshed.
Name
Displays the name of the core instance and the server on which it is installed.
Mode
Description of the core instance modes:
| Mode | Description | Notes |
|---|---|---|
| Primary | Running and has a backup instance associated with it. | Green background. |
| Backup | Ready to run if a failover occurs. | Gray background. |
| Standalone | Running with no backup instance associated with it. | Blue background. |
| Shutdown | All services and components except Report Writer are stopped. This includes the service that starts and stops components. In this mode, the instance cannot respond to commands from the user interface. | Start the instance from the host server to change the mode. |
| Connection Lost | There is no longer a network connection, the instance is down, or the Notification Server cannot communicate with the instance. | Check the error logs for details or restore the network connection. |
| Maintenance | Services are stopped except for the service that stops and starts services. No components are active. | None. |
Components
Components are displayed for both core and peripheral instances. The icon displayed for each component identifies whether it is active, starting, stopped, or unknown.
| Status | Description |
| Active | Component is active. |
| Starting | Component is initializing. |
| Stopped | Component is not active or not connected. |
| Unknown | Component status is unknown because its "heartbeat" was not detected. The component may actually be active (or not), but cannot be recognized due to a network issue or other problem. Refer to the System Management Troubleshooting topic in the System Management Maintenance Guide for more information. If a component has a stopped status and then its heartbeat is lost, the stopped icon will remain on the component. |
Non-controllable components are shaded gray and listed first (in alphabetical order). Controllable components are unshaded and listed second (in alphabetical order). Examples of components for a core instance are:
- CTI Connector
- Queue Manager
- Enterprise Pulse
- License Server
- Opmode Server
- Provider
- Readerboard Adapter
- Real-Time Adapter
- Report Writer
CTI Connector Details
The progress bar is not displayed for solutions which use TIAL Aspect or do not use TIAL (such as Cisco Unified Contact Center Express (UCCX), Interactive Intelligence Customer Interaction Center (CIC), and Interactive Voice Gateway (IVG)).
When the CTI Connector component is Starting, a progress bar indicates how many CTI devices are successfully registered and how many have failed. The percentage of completed devices also displays. The percentage includes both successful and failed components.
After the CTI Connector component has started, its status changes to Active and the progress bar and percentage are removed.
If the component is Stopped, the progress bar is removed.
If any CTI devices fails, the progress bar remains on the screen so the integrator or sysadmin can take appropriate action. The number of failed devices displays in red.
If a new holding queue, callback queue, or incoming extension is created via Configuration, the progress bar immediately updates with the new number of devices registered and failed.
