Cisco Cisco Unified Contact Center Enterprise 8.5(1) Guida Alla Risoluzione Dei Problemi
Conventions
For more information on document conventions, refer to the Cisco Technical Tips Conventions.
Problem
In an IPCC Enterprise solution, the ICM topology is configured in a duplexed mode. When one router goes
down, the other does not take over. Assume LoggerA and RouterA are active. If LoggerA stops, it fails over
to LoggerB without any problem but not for the rtr process. For example, if RouterA stops, the RouterB rtr
process dies and comes back up, but never goes into service and no calls are processedregardless of which
Router is active or running.
down, the other does not take over. Assume LoggerA and RouterA are active. If LoggerA stops, it fails over
to LoggerB without any problem but not for the rtr process. For example, if RouterA stops, the RouterB rtr
process dies and comes back up, but never goes into service and no calls are processedregardless of which
Router is active or running.
Solution
This problem is related to the number of PGs in service and the total number of PGs configured. If the ICM is
configured in a duplexed mode, RouterB or RouterA do not run simplex (isolated − enabled) unless the router
is in communication with the majority of enabled PG devices. If both PGs are active in a two PG ICM setup,
either RouterA or RouterB can run simplex and become isolated − enabled. If either one of the two PGs does
not work, RouterA can run simplex, but RouterB can not. This difference is due to the fact that if an even
number of PGs are checked in setup, RouterA runs alone if half are available. RouterB does not run simplex
because half is considered a majority to the A side and a minority to the B side. This scenario can occur if
several PGs are configured but not online, or if the Router can not see all PGs. When a CallRouter goes down,
a "test other side" takes place. When this test occurs, each side verifies if it is connected to a majority of the
PGs. If the B side can not connect to a majority of the PGs plus one additional PG, the B side never goes
active.
configured in a duplexed mode, RouterB or RouterA do not run simplex (isolated − enabled) unless the router
is in communication with the majority of enabled PG devices. If both PGs are active in a two PG ICM setup,
either RouterA or RouterB can run simplex and become isolated − enabled. If either one of the two PGs does
not work, RouterA can run simplex, but RouterB can not. This difference is due to the fact that if an even
number of PGs are checked in setup, RouterA runs alone if half are available. RouterB does not run simplex
because half is considered a majority to the A side and a minority to the B side. This scenario can occur if
several PGs are configured but not online, or if the Router can not see all PGs. When a CallRouter goes down,
a "test other side" takes place. When this test occurs, each side verifies if it is connected to a majority of the
PGs. If the B side can not connect to a majority of the PGs plus one additional PG, the B side never goes
active.
To solve this problem, verify that:
All PGs are up and running for Router failover to work correctly.
•
All IP addresses are entered correctly and on the Router ccagent process window.
•
The ccagent process window title bar says
InSvc x/y PGs
, where x represents the number of
active PGs and y represents the total number of PGs (see the A arrow in Figure1).
•
Figure 1 RouterA ccagent Process
Related Information
Technical Support − Cisco Systems
•
Contacts & Feedback | Help | Site Map
© 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
© 2014 − 2015 Cisco Systems, Inc. All rights reserved. Terms & Conditions | Privacy Statement | Cookie Policy | Trademarks of
Cisco Systems, Inc.
Updated: Feb 23, 2005
Document ID: 63173