We are receiving the following in the event logs on all of the
CallManagers except for the Pub.  Should we be concerned?

Error: Device TransientConnection - Transient connection attempted.
Connecting Port: 0
Device name (Optional):
Device IP address: 192.168.88.52
Device type: (Optional): 255
Reason Code (Optional): 6
App ID: cisco CallManager

Explanation: A connection was established and immediately dropped before
completing registration.  Incomplete registration may indicate a device
is rehoming in the middle of registration.  The alarm could also
indicate a device misconfiguration, database error, or an
illegal/unknown device trying to attempt a connection. 
Recommended Action: No action is required if this event was issued as a
result of a normal device rehome.

[ Post a follow-up to this message ]

These errors are caused when a device starts registering with CCM then 
closes the TCP connection during the registration process.  The 
transient connection is not a problem, in and of itself.  But it is 
normally a result of a device unregistering from it's primary CCM and 
starting the registration process to the secondary.  During this time 
it will attempt to reconnect to the primary CCM.  If it does it will 
stop the registration process on the secondary and start registering 
with the primary.  Investigation as to why the device unregistered 
might be needed if it wasn't purposely done via CCMAdmin or other 
means.

There could also be other reasons for this message which are indicated 
in the text below.

Unless you are certain that the device with IP 192.18.88.52 was 
purposely unregistered at the time of this event then you might want to 
investigate why it is trying to register with this server.

Kevin
On Sep 23, 2005, at 10:58 AM, Leetun, Rob wrote:

> We are receiving the following in the event logs on all of the 
> CallManagers except for the Pub._ Should we be concerned?
>
> Error: Device TransientConnection – Transient connection attempted.
> Connecting Port: 0
> Device name (Optional):
> Device IP address: 192.168.88.52
> Device type: (Optional): 255
> Reason Code (Optional): 6
> App ID: cisco CallManager
>
> Explanation: A connection was established and immediately dropped 
> before completing registration._ Incomplete registration may indicate 
> a device is rehoming in the middle of registration._ The alarm could 
> also indicate a device misconfiguration, database error, or an 
> illegal/unknown device trying to attempt a connection.
>
> Recommended Action: No action is required if this event was issued as 
> a result of a normal device rehome.
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]

Additionally, you can look up the Reason Code at http://www.cisco.com/ =

univercd/cc/td/doc/product/voice/c_callmg/4_1/alarms41.htm.

In this case 6 means "ConnectivityError" which is pretty generic.   =

Most often these are seen in the failover/failback situation Kevin  =

described.

-Ryan

On Sep 23, 2005, at 11:24 AM, Kevin Thorngren wrote:

These errors are caused when a device starts registering with CCM  =

then closes the TCP connection during the registration process.  The  =

transient connection is not a problem, in and of itself.  But it is  =

normally a result of a device unregistering from it's primary CCM and  =

starting the registration process to the secondary.  During this time  =

it will attempt to reconnect to the primary CCM.  If it does it will  =

stop the registration process on the secondary and start registering  =

with the primary.  Investigation as to why the device unregistered  =

might be needed if it wasn't purposely done via CCMAdmin or other means.

There could also be other reasons for this message which are  =

indicated in the text below.

Unless you are certain that the device with IP 192.18.88.52 was  =

purposely unregistered at the time of this event then you might want  =

to investigate why it is trying to register with this server.

Kevin
On Sep 23, 2005, at 10:58 AM, Leetun, Rob wrote:


> We are receiving the following in the event logs on all of the  =

> CallManagers except for the Pub.  Should we be concerned?
>
> Error: Device TransientConnection =96 Transient connection attempted.
> Connecting Port: 0
> Device name (Optional):
> Device IP address: 192.168.88.52
> Device type: (Optional): 255
> Reason Code (Optional): 6
> App ID: cisco CallManager
>
> Explanation: A connection was established and immediately dropped  =

> before completing registration.  Incomplete registration may  =

> indicate a device is rehoming in the middle of registration.  The  =

> alarm could also indicate a device misconfiguration, database  =

> error, or an illegal/unknown device trying to attempt a connection.
>
> Recommended Action: No action is required if this event was issued  =

> as a result of a normal device rehome.
>
>  ________________________________________
_______
> cisco-voip mailing list
> cisco-voip@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
 ________________________________________
_______
cisco-voip mailing list
cisco-voip@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-voip

[ Post a follow-up to this message ]