> I can go either way (since this PSARC 2009/306 is not about fixing > ipmpstat, but rather about improving over ifconfig). However, having > ipmpstat print something other than statistics makes it different from > the other newer *stat commands like dlstat.
ipmpstat prints status, just like netstat prints status. > I realize that ipmpstat covers a lot of territory, but we don't have > an "aggrstat" command that prints out various views of the > link-aggregation state. Why can't the ipmpstat functionality that > displays IPMP state be moved into ipadm, leaving ipmpstat to do > statistics-ish things like "-p"? First, -p is not statistics. Second, I think of IPMP as an HA technology that uses IP but is its own beast -- for instance, is detailed information about all IP routing technologies being folded into ipadm as well? Third, the IPMP subsystem state is not just IP configuration -- it is also the running state of in.mpathd. My advice is to have ipadm show IPMP-related state that is tied to IP configuration and other observable things on those objects (e.g., indicating which IP interfaces and IPMP groups have failed). For more detailed analysis, ipmpstat should be used. -- meem
