Fred, or those after some details...
fpapps[3347]: <399816> <ERRS> |fpapps| hapiPortLinkStatus: Failed to read phy status on port 0/0/0"
this is a generic error, despite what the docs say. Nothing specific to do with the master/master-R or master/local, mostly this error seems to exist for 72xx alarms and a few other minor (non related to this discussion) cases.
In this case, hapi refers to the hardware API, and we can infer from the name that some bad juju has happened trying to interogate the port 0/0/0 for its PHY status. As it turns out, this error lives within the port polling section and if this error is seen the port is actually marked as down (I suspect the full logs would show the port going down just after this) - which would cause VRRP to flap
The question from Seth is quite relevant - is this happening frequently ?
Plus I would wonder does this error appear for other ports ? are there other ports in use that do not have the error (and if not, can a dummy port be added) ? did the port come back up immediately ? What did the device on the far end report ?
may turn out to be hardware, might be that the 72xx just incorrectly complained just as the port was transitioning state for an external reason etc.
regards
-jeff