Recovery Procedure for MCP or MCPHC

In this scenario, the message typically occurs if the Measurements application loses the connection with the measurements FTP server. The error could be caused by a network connectivity problem or a misconfiguration of the FTP server parameters.

1. Enter the rtrv-ftp-serv command. If a measurement server is listed, verify the parameters.
   Example of command and possible output:

   rtrv-ftp-serv
       Command entered at terminal #6.
   ;
   
       e1061001 11-09-30 02:31:38 MST  EAGLE5 44.0.0-64.10.0
   
       APP       IPADDR           LOGIN            PRIO  PATH
       --------  ---------------  ---------------  ----  ----
       meas      10.241.14.62     eagleuser        1     /meas/reports
   
       FTP SERV table is (1  of 10)  10% full

2. If the output does not show an entry for the meas application, configure a measurements FTP server in accordance with the “Adding an FTP Server” procedure in Database Administration Manual - System Management to clear the alarm.
3. Verify connectivity with the FTP server with the ping command. Enter the pass:loc=<mcp>:cmd=”ping <server ipaddr>” command.
   Example of command and possible output:

   > pass:loc=1105:cmd="ping 10.241.14.62"
   
   Command Accepted - Processing
   
       e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0
       pass:loc=1105:cmd="ping 10.241.14.62"
       Command entered at terminal #6.
   ;
   
       e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0
       PASS: Command sent to card
   ;
   
       e1061001 11-09-30 02:53:17 MST  EAGLE5 44.0.0-64.10.0
   
       PING command in progress
   
   ;
   
       e1061001 11-09-30 02:53:18 MST  EAGLE5 44.0.0-64.10.0
   
   ;
   
       e1061001 11-09-30 02:53:20 MST  EAGLE5 44.0.0-64.10.0
       PING 10.241.14.62: 56 data bytes
       64 bytes from 10.241.14.62: icmp_seq=0. time=5. ms
       64 bytes from 10.241.14.62: icmp_seq=1. time=5. ms
       64 bytes from 10.241.14.62: icmp_seq=2. time=5. ms
       ----10.241.14.62 PING Statistics----
       3 packets transmitted, 3 packets received, 0% packet loss
       round-trip (ms)  min/avg/max = 5/5/5
   
       PING command complete.

   If the ping test fails, verify the physical network connectivity between the Eagle and the FTP server.
4. If the ping command is successful, attempt to transfer a file to the FTP server. Enter the pass:loc=<mcp>:cmd=”ftptest –a meas” command.
   Example of command and possible output:

   > pass:loc=1105:cmd="ftptest -a meas"
   Command Accepted - Processing
       e1061001 11-09-30 02:56:02 MST  EAGLE5 44.0.0-64.10.0
       pass:loc=1105:cmd="ftptest -a meas"
       Command entered at terminal #6.
   ;
       e1061001 11-09-30 02:56:02 MST  EAGLE5 44.0.0-64.10.0
       PASS: Command sent to card
   ;
       e1061001 11-09-30 02:56:02 MST  EAGLE5 44.0.0-64.10.0
       FTPTEST: Command In Progress
   ;
       e1061001 11-09-30 02:56:02 MST  EAGLE5 44.0.0-64.10.0
       FTP Interface Test
          Test Results: PASS
          Server IP:    10.241.14.62
          FTP Error:    0
          Segment:      190004fa
          Diag Msg:
   
       FTPTEST: Command Complete.

5. If the alarm is not cleared, try the FTP from another system and verify the login and directory. If this is unsuccessful, contact My Oracle Support (MOS).