Mailing List Archive: JUNOS 5.4R2.4 cflow timestamps not changing

Anybody else seen this? We upgraded to 5.4R2.4 a couple of days ago
and since then the timestamps on cflow export haven't changed at all.

using flow-tools (the Cisco's are reporting proper times, so I'm
pretty sure the flow-tools work fine).

1002.18:28:47.470 1002.18:28:47.470 50 128.125.233.83 1214 53 80.25.207.176 3271 6 0 1 40
1002.18:28:47.475 1002.18:28:47.475 50 128.125.233.83 4462 53 65.164.233.213 1214 6 0 1 40
1002.18:28:47.443 1002.18:28:47.443 50 128.125.233.83 1214 53 65.196.22.253 62850 6 0 1 40
1002.18:28:47.468 1002.18:28:47.468 50 128.125.245.83 50506 49 128.125.182.157 443 6 0 1 52

and the system time seems to be ok:

# run show system uptime
Current time: 2002-10-04 13:02:04 PDT
System booted: 2002-10-02 18:26:16 PDT (1d 18:35 ago)
Protocols started: 2002-10-02 18:27:18 PDT (1d 18:34 ago)
Last configured: 2002-10-04 12:34:04 PDT (00:28:00 ago) by whacl
1:02PM up 1 day, 18:36, 2 users, load averages: 0.08, 0.11, 0.08

but all of the cflow data claims it's 2002-10-02 18:28:47. it seems the
fractional part of the time changes, but the day/h/m/s part is always
the same....

----
Carl Hayter
ISD - Data Network Operations
University of Southern California

Hi Carl,

If not done yet, please open a support case with JTAC ( support@juniper.net ),
and provide these few details :

- JUNOS SW version prior to upgrade to 5.4R2.4
- [cli] show log sampled | no-more
- [configuration] # show forwarding-options
- [cli] if you have a local output file : show log /var/tmp/<filename> |
match "#" | no-more
- also mention changes ( if any, on JUNOS configuration or flow-tools )

And of course,

- [cli] show chassis hardware

Regards,

- Kisito

At 22:06 10/4/2002, hayter wrote:
>Anybody else seen this? We upgraded to 5.4R2.4 a couple of days ago
>and since then the timestamps on cflow export haven't changed at all.
>
>using flow-tools (the Cisco's are reporting proper times, so I'm
>pretty sure the flow-tools work fine).
>
>1002.18:28:47.470 1002.18:28:47.470
>50 128.125.233.83 1214 53 80.25.207.176 3271 6 0 1
>40
>1002.18:28:47.475 1002.18:28:47.475
>50 128.125.233.83 4462 53 65.164.233.213 1214 6 0 1
>40
>1002.18:28:47.443 1002.18:28:47.443
>50 128.125.233.83 1214 53 65.196.22.253 62850
>6 0 1 40
>1002.18:28:47.468 1002.18:28:47.468 50 128.125.245.83 50506
>49 128.125.182.157 443 6 0 1 52
>
>and the system time seems to be ok:
>
># run show system uptime
>Current time: 2002-10-04 13:02:04 PDT
>System booted: 2002-10-02 18:26:16 PDT (1d 18:35 ago)
>Protocols started: 2002-10-02 18:27:18 PDT (1d 18:34 ago)
>Last configured: 2002-10-04 12:34:04 PDT (00:28:00 ago) by whacl
> 1:02PM up 1 day, 18:36, 2 users, load averages: 0.08, 0.11, 0.08
>
>but all of the cflow data claims it's 2002-10-02 18:28:47. it seems the
>fractional part of the time changes, but the day/h/m/s part is always
>the same....
>
>----
>Carl Hayter
>ISD - Data Network Operations
>University of Southern California
>_______________________________________________
>juniper-nsp mailing list juniper-nsp@puck.nether.net
>http://puck.nether.net/mailman/listinfo/juniper-nsp