Use fence_manual ... but it is not supported officially by TUV in production environments ...
Do not use that... How does that actually fence the offending node when it needs to?
The concept of fencing is for the preservation of data integrity, circumventing it with a manual fence is useful only for testing, if you need to fence an errant node in production and don't, it might just corrupt your shared storage. Sigh...
Make a firewall provision, it's imperative you get fencing right.