Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
Silver

CallManager Transient Connection Attempt

I restarted the Call Manager, and it came up with these errors in the CCM Event Viewer. No problem was noticed with devices, but when tried to start Unity (was shutdown previously), the Unity ports won't get registered, and I got TapiLine Initialization failed errors in the Unity Event Viewer. After trying for about 15mins, Unity started.

Does these errors below has anything to do with this behaviour? I see no other errors in CCM EventViewer.

4/25/2002 9:07:38 PM Cisco Tftp Error None 3 N/A CM001 The description for Event ID ( 3 ) in Source ( Cisco Tftp ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: kCTFTPConnectSendFileNonTimeoutError - NonTimeout error during call to recvfrom().

ErrorNumber: 10054

Block: 1

App ID: Cisco Tftp

Cluster ID: CM001-Cluster

Node ID: 192.168.4.241

Explanation: NonTimeout error occurred during call to recvfrom().

Recommended Action: Ensure your system is connected to the network. Check windows Taskmanager to make sure TFTP is getting sufficient processor

time to serve files. Make sure you are following configuration guide recommendations for your system configuration..

4/25/2002 9:07:37 PM Cisco CallManager Error None 3 N/A CM001 The description for Event ID ( 3 ) in Source ( Cisco CallManager ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: DChannelOOS - D channel out of service.

Device Name.: S0/DS1-0@SDA00908F0034DB

Device IP address: 192.168.4.240

Channel Id.: 24

Unique channel Id: S0/DS1-0@SDA00908F0034DB:24

Reason [Optional].: 0

App ID: Cisco CallManager

Cluster ID: CM001-Cluster

Node ID: 192.168.4.241

Explanation: Indicated D channel has gone out of service.

Recommended Action: Contact TAC for help if this alarm continue to generate..

4/25/2002 9:07:24 PM Cisco CallManager Error None 3 N/A CM001 The description for Event ID ( 3 ) in Source ( Cisco CallManager ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event: DeviceTransientConnection - Transient connection attempt.

Connecting Port: 2000

Device name [Optional].:

Device IP address.: 192.168.2.32

Device type. [Optional]: 255

Reason Code [Optional].: 6

App ID: Cisco CallManager

Cluster ID: CM001-Cluster

Node ID: 192.168.4.241

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..

Thanks,

Partha

3 REPLIES
New Member

Re: CallManager Transient Connection Attempt

Hi!

I'm getting the exact same error message (Transient connection attempt) Do you resently upgrade your tftp service? 6.0.1?

don

New Member

Re: CallManager Transient Connection Attempt

We've been getting the Transient Connection Attempt errors on our CM for about a month and have yet to be able to pin them down - they don't seem to be causing us any errors - but there are quite a few daily.

How did you upgrade the TFTP service independent of CM?

New Member

Re: CallManager Transient Connection Attempt

perhaps you mean TSP 6.0(1) ?

645
Views
0
Helpful
3
Replies
CreatePlease to create content