Are you rebooting the VM with the "reboot" command in the VM? If so, try the rebootRouter API or the UI instead. There's no agent in the virtual router so CloudStack may not be aware of a reboot performed outside of CloudStack. This is even the case for a reboot of a virtual router by vSphere native HA, although I think this particular case is being fixed.
Best regards, Kirk On 09/12/2013 04:40 PM, Noel Kendall wrote: > FW rules are not persistent in VR? I am trying to figure out why a V4.1 VR > does not properly NAT, and of course,reboot several times to reset state. I > see that after each reboot, the NAT rules are gone. If I go to the mgr, and > touchthe rules for the network in some way, the rules are re-instated. > Makes me think that the mgr is not aware of the VR change of state on reboot, > and is failing to command it with properset of rules. > Rather discouraging. I had a working environment in 4.0.1, now, toast. > Thoughts?? > N >
