Cisco Unified Presence, Release 7.x -- How to Troubleshoot a Multi-Node Deployment

From DocWiki

Revision as of 11:38, 5 May 2010 by Amclough (Talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

Main page: Cisco Unified Presence, Release 7.x


Contents

Previous Topic

Monitoring a Multi-Node System

Restriction

If you need to add hardware to your multi-node deployment, the hardware must comply with the multi-node hardware recommendations.


Procedure
  1. Use the Cisco Unified Presence Real-Time Monitoring Tool (RTMT) tool to monitor the CPU and memory usage of each Cisco Unified Presence node in the cluster.
  2. Use these guidelines to determine if you need additional hardware:


Deployment Model Recommendation

No High-Availability or Balanced Non-Redundant High-Availability

If the CPU reaches more than 70% capacity for a sustained period on any Cisco Unified Presence node, we recommend that you add hardware resources to your deployment.

Balanced Redundant High-Availability

If the CPU reaches more than 35% capacity for a sustained period on either Cisco Unified Presence node in the subcluster, we recommend that you add hardware resources to your deployment.

Active/Standby High-Availability

If the CPU reaches more than 70% capacity for a sustained period of time on the active Cisco Unified Presence node, we recommend that you add hardware resources to your deployment.


Related Topics



Resolving a Hardware Problem

Previous Topic

Follow this procedure if there is a problematic server, or some general hardware failure.


Restrictions

If you need to add hardware to your multi-node deployment, the hardware must comply with the multi-node hardware recommendations.


Procedure
  1. Create a new node using the system topology interface.
  2. Perform a fresh installation on this node.
  3. Unassign the users from the problematic node.
  4. Stop all services on the problematic node.
  5. Unassign the problematic node.
  6. Assign the new node to the subcluster, replacing the problematic node.
  7. Reassign the unassigned users to the new node.
  8. Delete the problematic node.
  9. Activate all services on the new node.


Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools