Faulty time-response from 64bit server (Motorola -> choke)

Dears Sirs,

We're a cable/broadband/mobile-transmission/etc company who has developed a full solution for management and monitoring of Docsis broadband networks.

For ToD we're using the internal UDP-server in Linux.

Just recently we installed the application on a 64bit machine (running Ubuntu server).
There seems to be a problem with the ToD-response, the Motorola CMs doesn't accept it.

The response is (not identical timestamp):

from 64bit server:

0000 00 19 56 c9 99 3c 00 14 5e b4 6e c0 08 00 45 00 ..V..<.. ^.n...E.
0010 00 24 00 00 40 00 40 11 11 1b c1 16 5e 04 0a 0a .$..@.@. ....^...
0020 00 8a 00 25 05 05 00 10 29 d0 ca 59 60 7a 00 00 ...%.... )..Y`z..
0030 00 00 ..

from 32bit server:

0000 00 00 ca bb f0 5d 00 14 85 30 e8 7d 08 00 45 00 .....].. .0.}..E.
0010 00 20 00 ee 40 00 40 11 cb 74 ac 00 0b 03 ac 00 . ..@.@. .t......
0020 0b 67 00 25 05 c9 00 0c 2c b5 ca 59 94 6e .g.%.... ,..Y.n

There are 4 extra bytes of 0 in the response from the 64bit server. I guess this is what is making Motorola choke. The timestamp is the "ca 59 94 6e" value.

<>
DOCS-CABLE-DEVICE-MIB::docsDevDateTime.0 = STRING: 1970-1-1,0:3:13.0
DOCS-CABLE-DEVICE-MIB::docsDevEvText.2 = STRING: ToD Response received - Invalid data format

****

ARRIS DOCSIS 1.1 Touchstone Cable Modem <>
DOCS-CABLE-DEVICE-MIB::docsDevDateTime.0 = STRING: 2007-7-31,9:33:5.0

All good ;)

***

<>
DOCS-CABLE-DEVICE-MIB::docsDevDateTime.0 = STRING: 1970-1-1,0:1:8.0
DOCS-CABLE-DEVICE-MIB::docsDevEvText.3 = STRING: ToD Response received - Invalid data format

***

<>
DOCS-CABLE-DEVICE-MIB::docsDevDateTime.0 = STRING: 1970-1-1,0:0:37.0
DOCS-CABLE-DEVICE-MIB::docsDevEvText.2 = STRING: ToD Response received - Invalid data format

I haven't been able to test with other CMs yet, but will soon.

If anyone has any thoughts, tips, solutions, feel free to join in ;)

Ola