This occurred as of an interim upgrade from
6 8312832 Feb 23 2007 11:46:48 asa722-k8.bin to 11 8349696 May 29 2007 17:44:30 asa722-22-k8.binCisco doc indicates this might be expected behavior for 7.2(2), however the standby definitely had ospf routes prior to this incremental upgrade. I know this for a fact because I was able to get to it from other than the local inside net prior to the upgrade. Anyone else observe this? If this is expected behavior as per the doc, how is one supposed to access the standby from a remote net? I just assumed that expected behavior was for the standby to rec ospf routes from the primary, but not broadcast any.
formatting link