Troubleshooting Cisco Emergency Responder System Problems

From DocWiki

(Difference between revisions)
Jump to: navigation, search
(Related Topics)
 
(4 intermediate revisions not shown)
Line 23: Line 23:
:'''Possible Cause'''  You have configured Cisco ER to use a TCP port that is already in use.
:'''Possible Cause'''  You have configured Cisco ER to use a TCP port that is already in use.
-
:'''Recommended Action'''  Check the Windows Event Viewer for the message “Cisco ER could not open socket at port ''peer-tcp-port'', Exiting.” If you see this message, change the Cisco ER group configuration to use a different TCP port. See the [[ # Configuring a Cisco Emergency Responder Server Group | "Configuring a Cisco Emergency Responder Server Group"]] for instructions.
+
:'''Recommended Action'''  Check the Windows Event Viewer for the message “Cisco ER could not open socket at port ''peer-tcp-port'', Exiting.” If you see this message, change the Cisco ER group configuration to use a different TCP port. See the [http://www.cisco.com/en/US/docs/voice_ip_comm/cer/8_0/English/administration/guide/e911conf.html#wpxref26300 Configuring a Cisco Emergency Responder Server Group] for instructions.
== Cisco ER Groups in Cluster Screen Does Not Load ==
== Cisco ER Groups in Cluster Screen Does Not Load ==
Line 33: Line 33:
Ensure that the specified cluster db host password is the same across all Cisco  ER server groups in the cluster.
Ensure that the specified cluster db host password is the same across all Cisco  ER server groups in the cluster.
-
For more information, see the [[# Configuring the Cisco Emergency Responder Cluster and Cluster DB Host | "Configuring the Cisco Emergency Responder Cluster and Cluster DB Host
+
For more information, see the [http://www.cisco.com/en/US/docs/voice_ip_comm/cer/8_0/English/administration/guide/e911conf.html#wpxref23848 Configuring the Cisco Emergency Responder Cluster and Cluster DB Host].
-
"]].
+
=== Related Topics ===
=== Related Topics ===
-
*  [[# Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster | "Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster"]]
+
*  [[Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster | Identifying the Cisco Emergency Responder Groups and Servers in a Cisco Emergency Responder Cluster]]
-
*  [[# Phones Moving Between Clusters | "Phones Moving Between Clusters"]]
+
*  [[Phones Moving Between Clusters | Phones Moving Between Clusters]]
-
*  [[# Collecting Trace and Debug Information | "Collecting Trace and Debug Information"]]
+
*  [[Collecting Trace and Debug Information | Collecting Trace and Debug Information]]
-
*  [[# Viewing Event Messages | "Viewing Event Messages"]]
+
*  [[Viewing Event Messages | Viewing Event Messages]]
-
*  [[# Integrating with Network Management Systems | "Integrating with Network Management Systems"]]
+
*  [[Integrating with Network Management Systems | Integrating with Network Management Systems]]
[[Category:Emergency Responder]]
[[Category:Emergency Responder]]

Latest revision as of 09:38, 11 October 2010

Contents

Troubleshooting Cisco Emergency Responder System Problems

This chapter covers topics that help you troubleshoot issues you might encounter with general operation of the Cisco ER system and the configuration screens that involve the Cisco ER server, group, and cluster.

Cisco ER Intra-Cluster Call Routing Fails

Symptom Cisco ER intra-cluster call routing fails or Cisco ER does not discover phones correctly.

Recommended Action Ensure that all the Cisco ER servers in a Cisco ER cluster can be found by their host name, and ensure that all are reachable on the network by all the other Cisco ER servers.
Recommended Action Ensure that all the Cisco ER servers can reach the Cisco ER cluster DB host and that the cluster DB password is the same across all servers in the cluster.

Cisco ER Does Not Discover Phones Correctly

Symptom Cisco ER intra-cluster call routing fails or Cisco ER does not discover phones correctly.

Recommended Action Ensure that all the Cisco ER servers in a Cisco ER cluster can be found by their host name, and ensure that all are reachable on the network by all the other Cisco ER servers.
Recommended Action Ensure that all the Cisco ER servers can reach the Cisco ER cluster DB host and that the cluster DB password is the same across all servers in the cluster.

Cisco ER Exits After Starting

Symptom Cisco ER exits after starting.

Possible Cause You have configured Cisco ER to use a TCP port that is already in use.
Recommended Action Check the Windows Event Viewer for the message “Cisco ER could not open socket at port peer-tcp-port, Exiting.” If you see this message, change the Cisco ER group configuration to use a different TCP port. See the Configuring a Cisco Emergency Responder Server Group for instructions.

Cisco ER Groups in Cluster Screen Does Not Load

Symptom The Cisco ER Groups in Cluster screen does not load, and exhibits the error “Cannot connect to cluster DB host.”

Recommended Action Ensure that the cluster DB host can be found by host name.

Ensure that the specified cluster db host password is the same across all Cisco ER server groups in the cluster.

For more information, see the Configuring the Cisco Emergency Responder Cluster and Cluster DB Host.

Related Topics

Rating: 0.0/5 (0 votes cast)

Personal tools