07-05-2016 08:01 PM - edited 03-08-2019 06:30 AM
Jul 5 19:56:12 172.31.10.237 68712: *Jul 5 20:07:19.449 BeiJing: %SSH-SW1-4-SSH2_UNEXPECTED_MSG: Unexpected message type has arrived. Terminating the connection from 141.212.122.33
Jul 5 19:56:39 172.31.10.237 68713: *Jul 5 20:07:47.321 BeiJing: %SYS-SW1-2-MALLOCFAIL: Memory allocation of 65536 bytes failed from 0x748684C, alignment 0
Jul 5 19:56:39 172.31.10.237 68714: Pool: Processor Free: 43140832 Cause: Memory fragmentation
Jul 5 19:56:39 172.31.10.237 68715: Alternate Pool: None Free: 0 Cause: No Alternate pool
Jul 5 19:56:39 172.31.10.237 68716: -Process= "LDP", ipl= 0, pid= 1187
Jul 5 19:56:39 172.31.10.237 68717: -Traceback= 7455E48z 7467BC0z 7486850z 7AB1104z 7AB1230z 7AB55ECz 7AA210Cz 7ABC974z 7AA633Cz 7AAB20Cz 528D260z 5286AF4z
Jul 5 19:56:40 172.31.10.237 68718: *Jul 5 20:07:47.965 BeiJing: %SSH-SW1-3-NOMEMORY: Memory allocation failed.
Jul 5 19:56:48 172.31.10.237 68719: 20:07:57.065 FW[MOD 23]: scp_fpoe_req: memory allocation error, subopcode=13, count=1
Jul 5 19:56:48 172.31.10.237 68720: 20:07:57.105 FW[MOD 23]: scp_fpoe_req: memory allocation error, subopcode=13, count=1
Jul 5 19:56:48 172.31.10.237 68721: *Jul 5 20:07:57.169 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68722: *Jul 5 20:07:57.169 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68723: *Jul 5 20:07:57.169 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switchvs_rp_environmental:env_raise_alarm_rp failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68724: *Jul 5 20:07:57.177 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68725: *Jul 5 20:07:57.177 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68726: *Jul 5 20:07:57.177 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switchvs_rp_environmental:env_clear_alarm_rp failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68727: *Jul 5 20:07:57.185 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68728: *Jul 5 20:07:57.185 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68729: *Jul 5 20:07:57.185 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switchvs_rp_environmental:env_clear_alarm_rp failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68730: *Jul 5 20:07:57.185 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68731: *Jul 5 20:07:57.185 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Jul 5 19:56:48 172.31.10.237 68732: *Jul 5 20:07:57.189 BeiJing: %RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switchvs_rp_environmental:env_raise_alarm_rp failed (non-fatal). Expected when VSL goes down.
Solved! Go to Solution.
07-05-2016 10:25 PM
%PFREDUN-SW1-4-BOOTSTRING_INVALID: The bootfile s2t54-adventerprisek9-mz.SPA.151-2.SY2.bin is present on the active supervisor but not on the standby
Firstly, this is dangerous because this is telling me the IOS file is found in the active supervisor but is absent in the secondary supervisor.
%SSH-SW1-4-SSH2_UNEXPECTED_MSG: Unexpected message type has arrived. Terminating the connection from <IP address>
Next, please explain what the different IP addresses are. Are the IP addresses KNOWN to be friendly or not? If they are, then are they scripts that remote into the chassis to run some commands?
07-05-2016 10:25 PM
%PFREDUN-SW1-4-BOOTSTRING_INVALID: The bootfile s2t54-adventerprisek9-mz.SPA.151-2.SY2.bin is present on the active supervisor but not on the standby
Firstly, this is dangerous because this is telling me the IOS file is found in the active supervisor but is absent in the secondary supervisor.
%SSH-SW1-4-SSH2_UNEXPECTED_MSG: Unexpected message type has arrived. Terminating the connection from <IP address>
Next, please explain what the different IP addresses are. Are the IP addresses KNOWN to be friendly or not? If they are, then are they scripts that remote into the chassis to run some commands?
07-05-2016 11:50 PM
Hi.Leo Laohoo
thanks of your help, in the configure of 6509, It's not any host(from internet) to be 6509, it's not anything scripts to be run.
07-06-2016 12:08 AM
If the IP addresses are NOT friendly/known, then it looks like a limited DoS attack by using SSH to attempting to blow the CPU out.
11-10-2017 09:59 PM
07-05-2016 10:31 PM
%RPC-SW1-4-CORE_SAT_RPC_FAIL: RPC between Core and Remote Switch failed to send ICC msg to remote switch - have failed (non-fatal). Expected when VSL goes down.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide