Netstat rrd error updating

Searched the archives and found other mentions of this error but no
solution. I have a Solaris 8 server with the Hobbit client 
reporting to the
Hobbit server, and everything works except the netstat 
trend graph. I made
sure Hobbit generates the netstat.rrd file itself, and 
verified that it has
the correct fields:

$ rrdtool dump netstat.rrd |grep "<name>"

                <name> udpInDatagrams </name>
                <name> udpOutDatagrams </name>
                <name> udpInErrors </name>
                <name> tcpActiveOpens </name>
                <name> tcpPassiveOpens </name>
                <name> tcpAttemptFails </name>
                <name> tcpEstabResets </name>
                <name> tcpCurrEstab </name>
                <name> tcpOutDataBytes </name>
                <name> tcpInInorderBytes </name>
                <name> tcpInUnorderBytes </name>
                <name> tcpRetransBytes </name>
                <name> tcpOutDataPackets </name>
                <name> tcpInInorderPackets </name>
                <name> tcpInUnorderPackets </name>
                <name> tcpRetransPackets </name>

But viewing a debug output of rrd-data.log shows that 
something is making it
think there should only be 11 fields:

2006-10-13 19:18:22 RRD update param 03:

'udpInDatagrams:udpOutDatagrams:udpInErrors:tcpActiveOpens:tcp
PassiveOpens:t

cpAttemptFails:tcpEstabResets:tcpCurrEstab:tcpOutDataBytes:tcp
InInorderBytes

:tcpInUnorderBytes'

11 items here, yes.

2006-10-13 19:18:22 RRD update param 04:

'1160767102:1580411:5594723:0:113952:19256340:17330:36082:7:65
3169856:440119

035:9398449:159635980:26380336:13186666:30559:612744'

And 16 values there. Most odd.

I had a chance to revisit this problem I was having with the netstat rrd
data. I noticed that our Solaris 8 servers are not reporting any of the
following fields "tcpOutDataPackets tcpInInorderPackets tcpInUnorderPackets
tcpRetransPackets". They just don't exist on a "netstat -s" output. Do those
come from some GNU version of netstat?

I only really needed the established TCP connections data anyway, so I ended
up writing a small perl script to report whatever fields I needed and
disabled the built-in netstat tool on the client.