Article Detail

Description

This article provides information about the MS-DPC syslog messages.

Symptoms

When a customer installs a MS-DPC card in one of the slots, they might see the following error messages in syslog:

May 31 07:02:40 SGCR01-re0 (FPC Slot 4, PIC Slot 0) SERVICES_UI: %PFE-3: Failed to write reply May 31 07:02:40 SGCR01-re0 (FPC Slot 4, PIC Slot 0) SERVICES_UI: %PFE-3: Failed while processing message type 23 subtype 18 [success]

For example:

{MASTER}
lab@mx480-1-re1> show services stateful-firewall flows    
Interface: sp-2/0/0, Service set: service-snat
Flow                                                State    Dir       Frm count
TCP      212.65.154.50:21    ->    139.7.35.40:40883 Forward  O              12
TCP        139.7.35.33:40701 ->  212.65.154.34:80    Forward  I              84
TCP      212.65.154.32:20    ->    139.7.35.25:41039 Forward  O               6
TCP      212.65.154.35:21    ->    139.7.35.38:41653 Forward  O              12
TCP      212.65.154.34:80    ->    139.7.35.27:41808 Forward  O              75
TCP      212.65.154.32:80    ->    139.7.35.30:42290 Forward  O              27
TCP      212.65.154.31:21    ->    139.7.35.27:41706 Forward  O              12
TCP      212.65.154.31:20    ->    139.7.35.39:41099 Forward  O               6
TCP        139.7.35.31:40204 ->  212.65.154.38:80    Forward  I              84
TCP        139.7.35.31:41603 ->  212.65.154.45:20    Forward  I               5
TCP        139.7.35.25:42029 ->  212.65.154.36:21    Forward  I              16
TCP        139.7.35.23:41943 ->  212.65.154.42:80    Forward  I              48
TCP        139.7.35.26:42473 ->  212.65.154.44:20    Forward  I               5
TCP        139.7.35.36:41119 ->  212.65.154.48:80    Forward  I              83
TCP        139.7.35.33:41123 ->  212.65.154.35:21    Forward  I              16
TCP        139.7.35.29:41861 ->  212.65.154.39:21    Forward  I              17
TCP        139.7.35.29:41311 ->  212.65.154.47:20    Forward  I               5
TCP        139.7.35.35:42064 ->  212.65.154.49:80    Forward  I              39
TCP        139.7.35.23:42205 ->  212.65.154.36:80    Forward  I              28
TCP      212.65.154.49:21    ->    139.7.35.38:41774 Forward  O              12
TCP        139.7.35.34:42261 ->  212.65.154.43:21    Forward  I              16
TCP      212.65.154.39:21    ->    139.7.35.30:41732 Forward  O              12
TCP      212.65.154.47:20    ->    139.7.35.26:41851 Forward  O               6
TCP      212.65.154.38:80    ->    139.7.35.24:41637 Forward  O              91
TCP        139.7.35.37:41158 ->  212.65.154.33:21    Forward  I              17
TCP        139.7.35.29:41040 ->  212.65.154.46:20    Forward  I               5
TCP        139.7.35.28:40823 ->  212.65.154.47:80    Forward  I              83
TCP      212.65.154.40:80    ->    139.7.35.29:40716 Forward  O              93
TCP      212.65.154.45:21    ->    139.7.35.30:41172 Forward  O              12
TCP        139.7.35.37:41857 ->  212.65.154.42:21    Forward  I              17
TCP        139.7.35.33:40878 ->  212.65.154.43:21    Forward  I              16
TCP        139.7.35.36:41293 ->  212.65.154.36:20    Forward  I               6
TCP        139.7.35.24:41286 ->  212.65.154.35:20    Forward  I               5
TCP      212.65.154.45:21    ->    139.7.35.33:41719 Forward  O              12
TCP        139.7.35.30:41641 ->  212.65.154.46:80    Forward  I              80
TCP      212.65.154.50:80    ->    139.7.35.29:41271 Forward  O              93
TCP        139.7.35.27:41387 ->  212.65.154.43:21    Forward  I              16
TCP      212.65.154.40:80    ->    139.7.35.32:41994 Forward  O              57
---(more)--- < more pages are yet to be displayed

Now if you press 'q' then check the syslog messages, you will see the 'Failed' messages

On checking the syslog messages:

{MASTER}
lab@mx480-1-re1> show log messages | match services | last 10    
Jun  1 12:29:30  mx480-1-re1 init: periodic-packet-services (PID 1417) sending signal hup: due to "proto-mastership": 0x1
Jun  1 12:29:30  mx480-1-re1 init: pic-services-logging (PID 5163) started
Jun  1 12:29:30  mx480-1-re1 init: adaptive-services (PID 5165) started
Jun  1 12:51:21  mx480-1-re1 (FPC Slot 2, PIC Slot 0) SERVICES_UI: Failed to write reply
Jun  1 12:51:21  mx480-1-re1 (FPC Slot 2, PIC Slot 0) SERVICES_UI: Failed while processing message type 23 subtype 18 [success]
Jun  1 12:54:47  mx480-1-re1 (FPC Slot 2, PIC Slot 0) SERVICES_UI: Failed to write reply
Jun  1 12:54:47  mx480-1-re1 (FPC Slot 2, PIC Slot 0) SERVICES_UI: Failed while processing message type 23 subtype 18 [success]
Jun  1 12:56:44  mx480-1-re1 (FPC Slot 2, PIC Slot 0) SERVICES_UI: Failed to write reply
Jun  1 12:56:44  mx480-1-re1 (FPC Slot 2, PIC Slot 0) SERVICES_UI: Failed while processing message type 23 subtype 18 [success]
                                        
{MASTER}
lab@mx480-1-re1>

Solution

This is expected and not a bug

This error message is expected, when a show command is killed on the RE. For example, if the show services stateful-firewall flows command is executed and you press quit after a few pages, this error message will be generated on the console. This is expected and not a bug. In other words, this error message has nothing to do with ALGs.