cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Announcements
Join Customer Connection to register!
812
Views
0
Helpful
5
Replies
zhiyun.zhang
Beginner

Anyone can help me see the following log.(6509-E)

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.

1 ACCEPTED SOLUTION

Accepted Solutions
Leo Laohoo
VIP Community Legend

%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?

View solution in original post

5 REPLIES 5
Leo Laohoo
VIP Community Legend

%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?

View solution in original post

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.

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.

we are facing same problem in cisco C6807-XL, please suggest us for same issue.
Leo Laohoo
VIP Community Legend

%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.

Cisco Bug: CSCui19403