Murthy E-G19462 wrote:
> Hans,
> 
> Sorry I missed out responding to this mail. At any time, only the active
> controller
> Reads the pssv_spcn_list file and Standby controller gets populated with
> configuration info
> by Active controller using MBCSv.
> 
> If switchover/Failover happens Because Standby already has information,
> it will proceed to provide 
> service.
> 
> In a scenario where we are second time rebooting (power on), and we have
> a scenario where previous standby 
> Needs to be active, then it reads from the it's pssv_spcn_list
> (currently XML) and builds the system.

Thanks but,

pssv_spcn_list is not stored on the replicated partition. If we store 
pssv_spcn_list on the replicated partition too, then the new active 
controller will also boot from PSS => consistent behaviour.

Isn't that good or what is the reason that you have not choosen not to 
share pssv_spcn_list between the controllers?

Regards,
Hans


> 
> This is how we envisioned. Are you facing any problem with this
> behaviour?
> 
> Regards
> Murthy
>   
> 
> 
>>-----Original Message-----
>>From: [EMAIL PROTECTED] 
>>[mailto:[EMAIL PROTECTED] On Behalf Of Hans Feldt
>>Sent: Tuesday, October 16, 2007 5:21 PM
>>To: [email protected]
>>Subject: [Users] pssv_spcn_list attributes
>>
>>According to the controller rpm spec file, pssv_spcn_list is 
>>persistent but not shared. Is that correct?
> 
> 
> According the expected behavious, this is correct. 
> 
>>What happens e.g. when two controller are started (cold/power 
>>on) with enough time between them to allow the first 
>>controller to write 'PSS' to this file. From what source will 
>>the second controller then boot XML or PSS?
> 
> 
> See response above.
> 
>>Regards,
>>Hans
>>_______________________________________________
>>Users mailing list
>>[email protected]
>>http://list.opensaf.org/maillist/listinfo/users
>>
> 
> 

_______________________________________________
Users mailing list
[email protected]
http://list.opensaf.org/maillist/listinfo/users

Reply via email to