This article explains the reason for the above log emssage.
Customer would receive the below logs messages.
kernel: %KERN-4: peer_input_pending_internal: 6077: peer class: 2, type: 22, index: 0, vksid: 0, state: 1 reported a sb_state 32 = SBS_CANTRCVMORE
kernel: %KERN-4: peer_inputs: 6335: VKS0 closing connection peer class: 2, type: 22, index: 0, vksid: 0, state: 1, err 5
kernel: %KERN-3: peer_proxy: 5376: Peer proxy(class: 2, type: 22, index: 0, vksid: 0, state: 1) is marked for the closing
This log messages is generated when customer disables the inline jflow and performs the commit.
MSP is connection with mspmand (ifstate: kernel <-> peer proxy <-> mspmand) In case of ptx1k it is /usr/sbin/spbfpc-multi-svcs.elf process on vhmost.
W/o jflow sampling there’s no msp ifstate client:
# ifsmon -c | grep msp
#
If we enable jflow:
# show | compare
[edit]
+ chassis {
+ fpc 0 {
+ sampling-instance s1;
+ }
...
We can see msp ifstate client appear
msp0 0 0 2142 2142 100.000 100.000
Now if we disable jflow, msp client dissapear, and in the logs we see:
- chassis {
- fpc 0 {
- sampling-instance s1;
- }
# cli sh sys comm
0 2024-03-14 08:36:30 PDT by labroot via cli
# less /var/log/messages | grep -E "peer_"
Mar 14 08:36:40 jtac-PTX1000-r037 kernel: peer_input_pending_internal: 6193: peer class: 2, type: 22, index: 0, vksid: 0, state: 1 reported a sb_state 32 = SBS_CANTRCVMORE
Mar 14 08:36:40 jtac-PTX1000-r037 kernel: peer_inputs: 6451: VKS0 closing connection peer class: 2, type: 22, index: 0, vksid: 0, state: 1, err 5
Mar 14 08:36:55 jtac-PTX1000-r037 kernel: peer_proxy: 5480: Peer proxy(class: 2, type: 22, index: 0, vksid: 0, state: 1) is marked for the closing
As you can see able the logs are just informational and have no impact.