[cisco-voip] SDLLinkOutOfService

Wes Sisk wsisk at cisco.com
Tue Apr 21 17:06:08 EDT 2009


SCCP signaling is much more lenient than SDL signaling.

/wes

On Tuesday, April 21, 2009 4:24:13 PM, Melvin Fong <mfong at pacific.edu> 
wrote:
> With this error sometimes we get "server is down" and also a loss of
> phones, so this loss of communications is not just between call
> managers? But with the phones also? One time the phones stayed
> registered with the remote call manager until the ones on site were
> rebooted.
>
> -----Original Message-----
> From: Ryan Ratliff [mailto:rratliff at cisco.com] 
> Sent: Tuesday, April 21, 2009 11:43 AM
> To: Melvin Fong
> Cc: Chris Ward; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] SDLLinkOutOfService
>
> Loss of connectivity, dropped tcp acks leading to the session being  
> reset by one party, etc.  The only conclusive way to see what is  
> happening is to get it in a packet capture and that can be difficult  
> with a random failure.
>
> -Ryan
>
> On Apr 21, 2009, at 2:17 PM, Melvin Fong wrote:
>
> Is there a typical network issue that may be causing this?
> All the services show running and running since last reboot of call
> managers.
>
> -----Original Message-----
> From: Ryan Ratliff [mailto:rratliff at cisco.com]
> Sent: Tuesday, April 21, 2009 11:11 AM
> To: Melvin Fong
> Cc: Chris Ward; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] SDLLinkOutOfService
>
> In the alarm it will call out the remote node and application id.
> Basically when this error is logged the tcp connection on port 8002
> between servers running the ccm service has been lost.  The server
> will automatically try and reconnect.
>
> You've either got a transient network issue or a ccm service stopping/
> crashing somewhere.
>
> -Ryan
>
> On Apr 21, 2009, at 1:52 PM, Melvin Fong wrote:
>
> Chris,
>
>     Yes all servers were moved, 2 to the new data center and one to an
> offsite center.
>
> IP's remained the same.
>
> Mel
>
>
>
> From: Chris Ward [mailto:chrward at cisco.com]
> Sent: Tuesday, April 21, 2009 10:20 AM
> To: Melvin Fong; cisco-voip at puck.nether.net
> Subject: Re: [cisco-voip] SDLLinkOutOfService
>
>
>
> Melvin,
>
> This means that either CCM or CTI is not able to communicate with CCM
> or CTI on another node. How many nodes in the cluster? When you moved
> the datacenter, were all servers moved? Were any removed from the
> cluster? Did the IP addressing scheme remain the same?
>
> Chris Ward
>
> From: Melvin Fong <mfong at pacific.edu>
> Date: Tue, 21 Apr 2009 10:13:59 -0700
> To: <cisco-voip at puck.nether.net>
> Subject: [cisco-voip] SDLLinkOutOfService
>
> Since we moved our data center we have been getting the alert
> "SDLLinkOutOfService"
> When I look at the call manager is up (or back up), sometimes we also
> get an alert that the server is down (call manager).  We are running
> UCM 6.1.2 1000-13 and are set to auto/auto.  Any ideas as to what may
> be causing this?  Thanks for any help from anyone!
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>
>
> _______________________________________________
> cisco-voip mailing list
> cisco-voip at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-voip
>   



More information about the cisco-voip mailing list