Cathy Zhou wrote: > I don't agree. The VRRP router is created with the specified VRID and > address family. Ideally, if the VNIC is renamed, vrrpd should simply > find the new VNIC name and start to listen to the PF_ROUTE messages for > the new interface name and tracks the IP addresses configured on that > new interface as well. > > But we don't have the mechanism available to be informed with the > renaming operation, so vrrpd will behave incorrectly.
That's not different from dozens of other parts of the system. Arguably, VRRP is far less important than IP filters and routing. Why does it need to be protected specially? > Also, if the VRRP VNIC does not exist, the router enabling operation > would simply fail. Therefore, once the router is enabled, the VNIC > should not be deleted for consistency purpose. I'm still puzzled. This sounds like a job for sysevents or something similar (though there are probably Zones concerns with that), but I don't see why nailing it to the wall is the right answer. -- James Carlson 42.703N 71.076W <carlsonj at workingcode.com>
