BOGUS PACKET TYPE: Protocol version mismatch – major->30 minor->30 错误分析

客户在上个月做灾备演练完,重启CICS WLM后,发现其中一个region不断报如下错误:产生大量日志文 件,最终撑爆文件系统,需要客户手工不断刷除日志文 件:

018-09-09-21:26:45.224+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2654 0x00001a1b msgID=0x16C9A14F
(receive_packet) assoc->3013e128 BOGUS PACKET TYPE: Protocol version mismatch – major->30 minor->30
2018-09-09-21:26:45.224+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2675 0x00001a1b msgID=0x16C9A150
(receive_packet) assoc->3013e128 frag_length 13364 in header > fragbuf data size 4352
2018-09-09-21:26:45.232+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2654 0x00001d1e msgID=0x16C9A14F
(receive_packet) assoc->30139668 BOGUS PACKET TYPE: Protocol version mismatch – major->30 minor->30
2018-09-09-21:26:45.232+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2675 0x00001d1e msgID=0x16C9A150
(receive_packet) assoc->30139668 frag_length 13364 in header > fragbuf data size 4352
2018-09-09-21:26:45.240+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2654 0x00000809 msgID=0x16C9A14F
(receive_packet) assoc->30142928 BOGUS PACKET TYPE: Protocol version mismatch – major->30 minor->30
2018-09-09-21:26:45.240+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2675 0x00000809 msgID=0x16C9A150
(receive_packet) assoc->30142928 frag_length 13364 in header > fragbuf data size 4352
2018-09-09-21:26:45.249+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2654 0x00001415 msgID=0x16C9A14F
(receive_packet) assoc->30143fe8 BOGUS PACKET TYPE: Protocol version mismatch – major->30 minor->30
2018-09-09-21:26:45.250+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2675 0x00001415 msgID=0x16C9A150
(receive_packet) assoc->30143fe8 frag_length 13364 in header > fragbuf data size 4352
2018-09-09-21:26:45.259+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2654 0x00001b1c msgID=0x16C9A14F
(receive_packet) assoc->3013de68 BOGUS PACKET TYPE: Protocol version mismatch – major->30 minor->30
2018-09-09-21:26:45.259+08:00I—– PID#21758128 WARNING rpc cn_pkt cnrcvr.c 2675 0x00001b1c msgID=0x16C9A150
(receive_packet) assoc->3013de68 frag_length 13364 in header > fragbuf data size 4352

最后,终于经过分析,通过手工杀掉进程 ID PID#21758128后,报错日志没有再发生。最终经IBM实验室,确认为网络错误,如下为IBM实验室回复: 
Analyse:

1.Firstly,those error messages were result result of TXSeries receiving
an rpc
packet that was not properly formatted.usually,this is network
configuration issue.
If this is intermittent occurring issue, physical network check up will
be necessary.
This particular warning message does not have any impact on
the functionality of the product and customer can safely ignore the
message.

Advise:
1.Advise cu to check if they have multi net card or multi IP address.
so you also can collect “sarpccp show mapping” and send me for check.
2.If cu have multi IP address, I strongly advise to set RPC_UNSUPPORTED_NETADDRS or
RPC_UNSUPPORTED_NETIFS to restrict RPC to use only one IP address.

3.You also can consider using RPC_RESTRICTED_PORTS to restrict the port
range used by RPC.

4.You also have need to confirm if customer had some network/security
scans that time.


以下文章点击率最高

Loading…

     

如果这文章对你有帮助,请扫左上角微信支付-支付宝,给于打赏,以助博客运营