multinicb failure case understanding required
Hello,
What has happened that MULtinicB resource faulted on both nodes.
that lead to the failure of proxies and other dependent resources configured in service group
can you please let us know what could be the recovery procedure if the network gets corrected.
will all the resources come online automaticaly or sdmin has to take any action ?
... and this is where it comes back to: it depends on your configuration/environment.
The reason for marking resources as faulted so they will not come online on the same system without manual intervention/being cleared is to protect you (ie: the rationale being that if the resource has faulted, it might be an idea for someone to take a look at it before trying to online it there again).
If the only fault is with the network, the non-persistent resources may not fault themselves (this depends on the type/nature of the resource, obviously), though obviously they may not be usable while the network is down. So if that was the case (no other resources faulted apart from network) then AutoRestart=1 would be fine.
possible considerations before setting AutoRestart=2
• the default is 1 for a reason, eg: what if you had resources faulted from a previous/earlier issue that was still being fixed? if the fault was auto cleared then it could bring the resource up on the problem system prematurely/before it was ready
• if you do want to go ahead with this setting, you really need to test it in your environment (or at least understand the behaviour/implications) to make sure it's behaving the way you expect it to / need it to in the event of fault/failure