SW-6509-FWSM failover Troubleshooting First aid

Question

Fault Description：
（1）
active  FWSM and standby FWSM  inside interface Between，ping fails。
on side FWSM---active： ping 172.17.1.50 -------OK，ping 172.17.1.49------ping fails；
on side FWSM---standby： ping 172.17.1.49--------OK，ping 172.17.1.50-------ping fails；
but,active  FWSM and standby FWSM  outside interface between，ping OK。
on side FWSM---active：ping 172.17.1.36  、  ping 172.17.1.37、ping 172.17.1.35/33/34/、ping www.baidu.com -----------All OK；
on side FWSM---standby：ping 172.17.1.36 、  ping 172.17.1.37 、ping 172.17.1.35/33/34/、ping www.baidu.com-----------All OK；
（2）
Another problem：
active  FWSM and standby FWSM  inside interface，ping  7706-------All fails。
Summary：May be caused fwsm。
Topology ：Attachment
FWSM :
FWSM#                       show failover state
====My State===
Primary | Active |
====Other State===
Secondary | Standby |
====Configuration State===
    Interface config Syncing - STANDBY
    Sync Done
====Communication State===
    Mac set
=========Failed Reason==============
My Fail Reason:
    Ifc Failure
Other Fail Reason:
    Comm Failure
FWSM# show failover
Failover On
Failover unit Primary
Failover LAN Interface: lan Vlan 997 (up)
Unit Poll frequency 1 seconds, holdtime 15 seconds
Interface Poll frequency 15 seconds
Interface Policy 50%
Monitored Interfaces 42 of 250 maximum
Config sync: active
Version: Ours 4.0(13), Mate 4.0(13)
Last Failover at: 19:08:24 Beijing Dec 2 2013
    This host: Primary - Active
        Active time: 358944 (sec)
    Interface outside (172.17.1.36): Normal
    Interface inside (172.17.1.49): Normal (Not-Monitored)
    Other host: Secondary - Standby Ready
        Active time: 0 (sec)
    Interface outside (172.17.1.37): Normal
    Interface inside (172.17.1.50): Normal (Not-Monitored)
(Not-Monitored) -----------------??????

Answer 1

That's what I thought but the again, from the 6500 config prompt I actually get echo replys(!) from the FWCTX, with capture enabled as:
     access-list CAP permit ip any any
     capture mgmt access-list CAP interface MGMT packet-length 1500 circular-buffer
But it shows blank and no hit counts. Same happens usind RTMonitor in ASDM (6.2.(2f)) some packets that are permited and routed correctly aren't actually noticed. I don't get any logging for the missing/dropped/denied echo replies from the FWCTX to the 6500 MSFC nor for the successful replies from the 6500 to the FWCTX withh ASDM Debugging logging on.