[alcatel-nsp] SAMO Date type

Fri Apr 16 07:41:47 EDT 2010

it is POSIX time (sometimes called Unix Epoch time) which is the grandaddy of many operating systems, including the ALU TiMOS.  Basically, it is UTC time elapsed in seconds using 86,400 seconds per day since midnight on January 1, 1970, not counting leap seconds.  so Example: 1271370712 = (2010-04-15 22:31:52Z)  Z is for Zulu time which is UTC.  The digital representation of the time allows for easier calculations

There are several converters available such as http://www.epochconverter.com/.  You should be able to see human readable time with [ date +%s -d"Jan 1, 1980 00:00:01" ]

at CLI look in [config/system/time] commands for basic zone and format settings and [admin set-time] for manual config.

________________________________
From: alcatel-nsp-bounces at puck.nether.net [mailto:alcatel-nsp-bounces at puck.nether.net] On Behalf Of David Schubert
Sent: Thursday, April 15, 2010 11:02 PM
To: alcatel-nsp at puck.nether.net
Subject: [alcatel-nsp] SAMO Date type

When I get accounting records from the samo SOAP interface, the timestamps on the acounting data look like this.

ex:
<service.CompleteServiceEgressPacketOctetsLogRecord>
...
<timeRecorded>1271379851000</timeRecorded>
<outOfProfileOctetsForwarded>1243107543</outOfProfileOctetsForwarded>
        ...
<timeCaptured>1271380452154</timeCaptured>
<children-Set></children-Set>
</service.CompleteServiceEgressPacketOctetsLogRecord>

I cant find anywhere in the docs that actually explains explicitly how to interpret these numbers.

One clue may be from From the SAM xml reference where I see:

timeRecorded: type=Date; access=read-only; default=0
How do I change the number <timeCaptured>1271380452154</timeCaptured> into a meaningful date?

Thx
Dave
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/alcatel-nsp/attachments/20100416/078b1584/attachment.html>