Cisco Cisco Agent Desktop 9.0 Fehlerbehebungsanleitung
CAD Base Services Problems
March 13, 2015
89
Problem
CAD client applications are slow to respond after the primary node goes
down and fails over to the secondary node.
down and fails over to the secondary node.
Solution
Slow response time is expected behavior. There are numerous
connections that must be made in order to determine that the primary
node is down and to fail over the client application to the secondary
node. Automated updating, if enabled, will also run at that time, adding
to the delay. Depending on the type of node-down situation and how
quickly connections are returned, it is possible for client applications to
take longer than normal to log in and connect to all services.
connections that must be made in order to determine that the primary
node is down and to fail over the client application to the secondary
node. Automated updating, if enabled, will also run at that time, adding
to the delay. Depending on the type of node-down situation and how
quickly connections are returned, it is possible for client applications to
take longer than normal to log in and connect to all services.
Problem
CAD base services are active on the incorrect node. For example, they
are running on the secondary node (Side B) instead of the primary node
(Side A).
are running on the secondary node (Side B) instead of the primary node
(Side A).
Solution
Restart Cisco Licensing and Resource Manager (LRM) Service on the
active node to trigger the inactive node to become active.
active node to trigger the inactive node to become active.
Problem
Enterprise service is active on both nodes after LRM fails over.
Symptom. In a high availability system, when the Licensing and
Resource Management (LRM) service fails over from Side A to Side B,
Enterprise service should follow and fail over to Side B as well. However,
it is remaining active on Side A and also becoming active on Side B.
Resource Management (LRM) service fails over from Side A to Side B,
Enterprise service should follow and fail over to Side B as well. However,
it is remaining active on Side A and also becoming active on Side B.
Cause. During a failover, Enterprise service becomes active on Side B
but does not become inactive on Side A because LRM service does not
send a demotion message to Enterprise service.
but does not become inactive on Side A because LRM service does not
send a demotion message to Enterprise service.
Solution
Restart Enterprise service on the side on which LRM service is inactive.