Hello,   There's no way to 'clear' the counter per se.  If the controller is bad, once you replace it, the errors will stop.   First check that the controller is indeed bad.  If you prefer the CLI:  GrpName>member select MEMBERNAME show controllers   That should show both controllers status.   The 'b2b' link is the interconnect between both controllers.  If that error shows up, the passive CM will reboot itself, and most times comes right back online and resync with the primary.   There were issues in older firmware that also would result in this kind of error.   If the passive CM doesn't show up when you list the controller status, then attach the serial cable that came with the array to the passive CM.  9600, n, 8, 1,  no flowcontrol.  That will provide more information about the CM's status.  I.e. is it rebooting, or not responsive at all and need to be replaced.  Regards, Don 
Hi All,  Getting an error i've never seen before on our secondary (standby) controller in a PS6100.  I'm guessing the controller has died, but there are no amber lights on it or anything, and no indication that anything is wrong from the CLI except this message:    b2b_shutdown_link:  Secondary exceeded b2b link reboot count Primary controller knows the secondary is down, normal errors associated with that condition do appear. I wonder if there's a way to clear the reboot loop counter.  I know how to do it on an IBM DS system...Any thoughts? Thanks! 
PS6100 - b2b_shutdown_link: Secondary exceeded b2b link reboot count