Disk Enclosures
1748153 Members
3446 Online
108758 Solutions
New Discussion юеВ

Re: EVA 8000 Managing Controller

 
SOLVED
Go to solution
Mark Poeschl_2
Honored Contributor

Re: EVA 8000 Managing Controller

Yes. I've made that mistake in the past and as I recall things just didn't work at all if you had that wrong. (That may have changed with later versions of VCS/XCS.) In any case, the hosts are indeed set to OS type = Tru64
IBaltay
Honored Contributor

Re: EVA 8000 Managing Controller

Hi,
cam_ccfg_aa_enable=1 gives us reads only via the managing controller
cam_ccfg_aa_enable=0 reads go also via the proxy controller

the problem could be that Tru64 even if there is SET PREFERRED PATH TO CONTROLLER A or B, FAILOVER/FAILBACK, is not able to correctly detect the failback of the controller e.g. after the repair and it continues to read via the proxy controller. If more then 60% of the READ IO (minimum 5000 IO per hour) within the next hour, the EVA controllers swap the managing contorller role back to the proxy controller. Thus after the time you can have e.g. 80% utilisation of the controller A and 20% utilisation of the controller B.
the pain is one part of the reality
sgparker
Occasional Advisor

Re: EVA 8000 Managing Controller

Mark, was there any one resolution to your issue in July?
I am seeing the same issues in a mixed OS enviroment EVA8000, over 95% of vdisks are managed by one controller.
Thanks for any info.