Unified ICM and Unified CCE Database Troubleshooting: Router Process Rejects Logger Configuration Data Load

From DocWiki

(Difference between revisions)
Jump to: navigation, search
m (Bot: Adding {{Template:Required Metadata}})
Line 1: Line 1:
-
{{Template:Required Metadata}}
 
== Router Process Rejects Logger Configuration Data Load ==
== Router Process Rejects Logger Configuration Data Load ==
Line 10: Line 9:
</td></tr><tr><td> '''Recommended Action''' </td><td>Increase the following registry key value: Router\CurrentVersion\Configuration\Config\LargeTableTimeout  
</td></tr><tr><td> '''Recommended Action''' </td><td>Increase the following registry key value: Router\CurrentVersion\Configuration\Config\LargeTableTimeout  
-
</td></tr><tr><td> '''Release''' </td><td>Release 7.5(1)</td></tr><tr><td> '''Associated CDETS&nbsp;#''' </td><td> None. </td></tr></table>
+
</td></tr><tr><td> '''Release''' </td><td>Release 7.5(1) and 8.0</td></tr><tr><td> '''Associated CDETS&nbsp;#''' </td><td> None. </td></tr></table>
[[Category:Unified ICM/CCE & Hosted, Release 7.5]]
[[Category:Unified ICM/CCE & Hosted, Release 7.5]]
 +
[[Category:Unified CCE, Release 8.0]]

Revision as of 20:20, 8 March 2010

Router Process Rejects Logger Configuration Data Load

Problem Summary During initialization, the Router process rejects the configuration data load from logger.
Error Message None.
Possible Cause This occurs because the Logger is busy and does not send a heartbeat to the Router. The Router waits for the heartbeat for 2 minutes (the default interval), doesn't receive a heartbeat, and finally rejects the data.
Recommended Action Increase the following registry key value: Router\CurrentVersion\Configuration\Config\LargeTableTimeout
Release Release 7.5(1) and 8.0
Associated CDETS # None.

Rating: 0.0/5 (0 votes cast)

Personal tools