Viprion Blade failed because of heartbeat

Hi Guys,

 

Our Client have a viprion 6400 with 2 blades. One of the blades went down unexpectedly due to a heartbeat failure. After 5 minutes it went back up again. What might be the cause of this heartbeat failure? Please refer to the portion of logs below:

 

May 18 06:27:18 slot1/ns1-unit2 notice clusterd[419]: 013a0006:5: Slot 2 failed (heartbeat). May 18 06:27:18 slot1/ns1-unit2 err clusterd[419]: 013a0014:3: Blade 1: blade 2 FAILED May 18 06:27:18 slot1/ns1-unit2 notice clusterd[419]: 013a0024:5: Blade 1: Changing primary from 2 to 1 (self)

 

some logs are ommitted

 

May 18 06:27:26 slot1/ns1-unit2 err clusterd[419]: 013a0009:3: Blade 1: blade 2 powered DOWN. May 18 06:27:39 slot1/ns1-unit2 notice mcpd[661]: 01071451:5: Received CMI hello from /Common/ns1.unit1.globe.com.ph May 18 06:27:56 slot1/ns1-unit2 warning csyncd[429]: 013b0005:4: Command failed: cmd=rsync -qaI --timeout=15 /var/run/manifest.1 rsync://127.3.0.2/csync/var/run/manifest.1, rc=10 May 18 06:28:10 slot1/ns1-unit2 warning csyncd[429]: 013b0005:4: Command failed: cmd=rsync -qaI --timeout=15 rsync://127.3.0.2/csync/var/tmstat2/cluster/blade2.tm2 /var/tmstat2/cluster/blade2.tm2, rc=10 May 18 06:30:01 slot1/ns1-unit2 notice iprepd[559]: 015a0009:5: IP Reputation has no license currently May 18 06:31:22 slot1/ns1-unit2 notice clusterd[419]: 013a0010:5: Blade 1: blade 2 powered up.