SFTP is too slow to respond.

-
This is a common error while taking backups or upgrading the server, irrespective of CM version.
This is an SFTP error, most common in windows SFTP platforms.

In order to resolve such issue-
1. Restart SFTP service.
2.  Reboot SFTP server.
3. Download another SFTP server, preferably cygwin for linux based server, coreftp/freeftpd for windows.

In order to install cygwin server, follow the below steps.
  1. Choose a plain windows server to install cygwin setup  
  2. Once it is downloaded, run the set up and choose the below options.
    Install the source from internet. 
  3. Create a local package directory in root directory.
  4. Choose cygwin.mirrors.pair.com, as download site for LPD.
    Choose the below packages- zlib, tcp wrappers, diffutils, openssh.
    Downloading the packages would take around 30minutes.
  5. In the meantime, make the changes in system variables.
    Once it is install, run the below commands-  
ssh-host-config    (manuall answer Yes to questions except)
If the script says "This script plans to use cyg_server, Do you want to use a different name?  Answer Yes, and type sshd as the user name.
While you are still in the (black) cygwin screen, start the sshd service, type
net start sshd  
Now, the SFTP service is running on cygwin. Feel free to use it.

Click here to go through the reference link to clear your doubts.

Comments

Post a Comment

Popular posts from this blog

Status: Local Agent is not responding. This may be due to Master or Local Agent being down.

-
If you have read my previous post , you would understand why LA and MA services are important for such a scenario and no component has backed-up, rather you get the above error message. Symptoms -   All Disaster Recovery Framework (DRF) services are down, and no new devices, schedules, or statuses can be viewed from the DRF console. Also, when you access the DRF admin pages, the above error message is received. Affected CM releases 6.1.5 and later. Resolution In order to resolve it, first, verify if the Certificate Serial Number in the keystore of Publisher is present in the Truststore of all Subscribers. Complete these steps: Log on to CUCM OS Administration page of Publisher server of the cluster setup. Choose Security > Certificate Management . The Certificate List window displays. You can use the Find controls in order to filter the certificate. Click on the ipsec.pem file and check the serial number of the certificate. Log on to CUCM OS Administr
Read more

Understanding code yellow

-
Understanding sample code yellow alert- Oct 3 01:00:10, cms01, Error, Cisco CallManager, ccm: 147896: Oct 03 05:00:10.616 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowEntry: CodeYellowEntry Expected Average Delay:362 Entry Latency:20 Exit Latency:8 Sample Size:10 Total Code Yellow Entry:14 High Priority Queue Depth:2 Normal Priority Queue Depth:12 Low Priority Queue Depth:70 Cluster ID:StandAloneCluster Node ID:cms01, 3652 The above alert is about code yellow entry, it shows the time when server enters code yellow state. There are no specifications to note at this alert, CM enters code yellow when it achieves the mentioned conditions for code yellow state as mentioned in service parameters. Oct 3 01:00:12, cms01, Error, Cisco CallManager, ccm: 147897: Oct 03 05:00:12.268 UTC : %CCM_CALLMANAGER-CALLMANAGER-3-CodeYellowExit: CodeYellowExit Expected Average Delay:0 Entry Latency:20 Exit Latency:8 Sample Size:10 Time Spent in Code Yellow:2 Number of Calls Rejected Due to C
Read more