HP-UX TCP/IP Performance White Paper, March 2008

49
The only real "fix" to this is to migrate to IPv6 where the ID field is much larger.
0 packets forwarded
This is the number of IP datagrams the system has forwarded. If the system is not intended to be an IP
router, and this value is non-zero, it means that one or more other systems are using this system as a router,
and that someone forgot to set ip_forwarding to zero with ndd on this system. Two configuration
problems need to be fixed.
56 packets not forwardable
This is the number of datagrams this system could not forward – either because it was configured to not
forward IP datagrams, or because it tried to forward but could not find a route. In the former case, the
remote systems trying to use the system as a gateway need to be reconfigured. In the latter, the routing
tables need to be updated. The netstat –r command displays the current routing tables and the
route(1M) command is used to update these tables. Refer to the route(1M) man page for help on
updating the routing tables.
IPv6:
6240733 total packets received
The total number of IPv6 datagrams received by this node.
5 bad IPv6 headers
The total number of bad IPv6 headers or IPv6 packets containing bad IPv6 extension headers received by
this node.
3206 fragments received
The total number of IPv6 datagram fragments received.
0 fragments dropped
As with IPv4, an increment in this statistic could mean a possible Frankengram situation when the fragments
are reported duped, or simply that the fragments are indeed being duplicated by the network. Fragments
may also be dropped as a result of packet loss in the network (preventing reassembly of the original
datagram), and as a result of settings on the limits of memory consumed by IPv6 fragment reassembly.
(ip6_reass_mem_limit – see Appendix B for guidelines on setting the ip6_reass_mem_limit in
some conditions.)