Which three statements describe fails in the high availability of Cisco Unified Intelligent Contact Management central controller? (Choose three.)

Question

Options

• AIf ICM Logger side A fails, router side B cannot send historical info to ICM Logger side A and is
• BIf the private LAN fails, the Peripheral Gateways are used to help determine the active call router
• CIf ICM Logger side A fails, the impact of call processing is limited to ICM call router side A.
• DIf one ICM call router of a duplex pair of Cisco Unified ICM call routers fails, the surviving ICM call
• EThere is no impact on call processing during a Cisco Unified ICM Logger failure.
• FDuring Cisco Unified ICM call router failover processing, calls in progress in Cisco Unified

• A
  82% (49)
• B
  10% (6)
• E
  3% (2)
• F
  5% (3)

Explanation

A, C, and D correctly describe failure behaviors in Cisco Unified ICM's duplex (redundant) central controller architecture. A is correct because an ICM Logger failure breaks the historical data path between its paired router side and that logger - Router side A loses its ability to send historical data to Logger side A. C is correct because Logger side A failing is contained: it impacts only its paired side (side A), leaving side B fully operational, so call processing degradation is isolated. D is correct because this is the core HA premise - when one router in a duplex pair fails, the surviving router inherits call routing responsibilities and processing continues.

Why the distractors are wrong:

• B is wrong because Peripheral Gateways play no role in determining which call router is active - the routers themselves handle that determination via their private LAN link and internal mechanisms.
• E is wrong because a Logger failure does cause impact, specifically to historical data collection and reporting, even though real-time call routing is unaffected; "no impact" is too absolute.
• F (though truncated) is wrong because calls already in progress are generally maintained through failover by the surviving router - in-progress calls are not simply dropped.

Memory tip: Think "Logger = history, Router = routing." Logger failure hurts reporting on that side only (A, C). Router failure triggers failover to the survivor (D). PGs route calls - they never vote on who's the active controller (B is a trap).

No community discussion yet for this question.