[email protected] wrote: > On (02/17/10 08:13), James Carlson wrote: >> The "netstat -pn" command shows some of this information. It should >> probably show more than it does. >> >> To get the actual timers, I think you'll need to use the ::nce or ::ncec >> command in "mdb -k" and look at the actual data structures. > > The expiration timers are managed in in.ndpd, so grovelling in the > kernel won't help in this case.
As pointed out in another reply, I don't think that's true for actual Neighbor Discovery entries. It's only true for Router Discovery stuff. >> (Not sure >> why there are two of these commands or why they seem to duplicate what >> the existing ::netstat command was supposed to do ...) > > See Section 6.1 of http://cr.opensolaris.org/~sowmini/arpip.pdf > the ncec_t keeps the interface agnostic Neighbor cache information - > everything needed to manage the ND state machine itself. The nce_t > keeps the interface specific information (fastpath header, dl_unitdata_req_t > info and other things that are ill_t specific). Usually there will > be a single nce_t for an ncec_t, but in the ipmp case, multiple nce_t's > may point to a common ncec_t. It sounds to me like the ::ncec information should be (or have been) displayed in ::netstat -p. -- James Carlson 42.703N 71.076W <[email protected]> _______________________________________________ networking-discuss mailing list [email protected]
