Hi,
Did you try to check the time at PFE level :
request pfe execute command "show sntp" target fpc<X>
Regards,
David
________________________________________
De : juniper-nsp-boun...@puck.nether.net [juniper-nsp-boun...@puck.nether.net]
de la part de David Lockuan [dlock...@gmail.com]
Date d'envoi : mercredi 8 juin 2011 19:52
À : juniper-nsp@puck.nether.net
Objet : [j-nsp] Bad time and date on firewall log.
Hi guys,
I was testing the firewall filter over a MX960 with release 10.4R1.9 and I
noted that time and date of the firewall logs was wrong. I am doing an
upgrade to release 10.4R4.5 and the issue continue.
*************************************************************************************************
{master}
test@MX960-LAB-RE0> show version
Hostname: MX960-LAB-RE0
Model: mx960
JUNOS Base OS boot [10.4R4.5]
JUNOS Base OS Software Suite [10.4R4.5]
JUNOS Kernel Software Suite [10.4R4.5]
JUNOS Crypto Software Suite [10.4R4.5]
JUNOS Packet Forwarding Engine Support (M/T Common) [10.4R4.5]
JUNOS Packet Forwarding Engine Support (MX Common) [10.4R4.5]
JUNOS Online Documentation [10.4R4.5]
JUNOS Voice Services Container package [10.4R4.5]
JUNOS Border Gateway Function package [10.4R4.5]
JUNOS Services AACL Container package [10.4R4.5]
JUNOS Services LL-PDF Container package [10.4R4.5]
JUNOS Services PTSP Container package [10.4R4.5]
JUNOS Services Stateful Firewall [10.4R4.5]
JUNOS Services NAT [10.4R4.5]
JUNOS Services Application Level Gateways [10.4R4.5]
JUNOS Services Captive Portal and Content Delivery Container package
[10.4R4.5]
JUNOS Services RPM [10.4R4.5]
JUNOS AppId Services [10.4R4.5]
JUNOS IDP Services [10.4R4.5]
JUNOS Runtime Software Suite [10.4R4.5]
JUNOS Routing Software Suite [10.4R4.5]
{master}
nsn@MX960-LAB-RE0> show firewall log detail
Time of Log: 1969-12-31 19:19:47 PET, Filter: pfe, Filter action: accept,
Name of interface: ge-7/0/4.2040
Name of protocol: RSVP, Packet Length: 140, Source address: 10.113.0.18,
Destination address: 10.113.0.17
Time of Log: 1969-12-31 19:19:46 PET, Filter: pfe, Filter action: accept,
Name of interface: ge-7/0/4.2000
Name of protocol: RSVP, Packet Length: 52, Source address: 10.113.0.2,
Destination address: 10.113.0.1
Time of Log: 1969-12-31 19:19:46 PET, Filter: pfe, Filter action: accept,
Name of interface: ge-7/0/4.2040
Name of protocol: RSVP, Packet Length: 52, Source address: 10.113.0.18,
Destination address: 10.113.0.17
Time of Log: 1969-12-31 19:19:42 PET, Filter: pfe, Filter action: accept,
Name of interface: ge-7/0/4.2000
Name of protocol: RSVP, Packet Length: 148, Source address: 10.113.0.2,
Destination address: 10.113.0.1
Time of Log: 1969-12-31 19:19:37 PET, Filter: pfe, Filter action: accept,
Name of interface: ge-7/0/4.2000
Name of protocol: RSVP, Packet Length: 52, Source address: 10.113.0.2,
Destination address: 10.113.0.1
Time of Log: 1969-12-31 19:19:37 PET, Filter: pfe, Filter action: accept,
Name of interface: ge-7/0/4.2040
Name of protocol: RSVP, Packet Length: 52, Source address: 10.113.0.18,
Destination address: 10.113.0.17
Time of Log: 1969-12-31 19:19:28 PET, Filter: pfe, Filter action: accept,
Name of interface: ge-7/0/4.2000
Name of protocol: RSVP, Packet Length: 52, Source address: 10.113.0.2,
Destination address: 10.113.0.1
Time of Log: 1969-12-31 19:19:28 PET, Filter: pfe, Filter action: accept,
Name of interface: ge-7/0/4.2040
Name of protocol: RSVP, Packet Length: 52, Source address: 10.113.0.18,
Destination address: 10.113.0.17
{master}
test@MX960-LAB-RE0> show configuration logical-systems was firewall
filter test_arfc {
term 1 {
then {
log;
accept;
}
}
}
{master}
test@MX960-LAB-RE0> show system uptime
Current time: 2011-06-08 12:50:53 PET
System booted: 2011-06-08 12:25:55 PET (00:24:58 ago)
Protocols started: 2011-06-08 12:26:56 PET (00:23:57 ago)
Last configured: 2011-06-08 12:18:26 PET (00:32:27 ago) by root
12:50PM up 25 mins, 1 user, load averages: 0.02, 0.02, 0.05
*********************************************************************************************************************************
Someone had the similar problem.
Thanks in advance,
---
David
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
********************************************************************************
IMPORTANT.Les informations contenues dans ce message electronique y compris les
fichiers attaches sont strictement confidentielles
et peuvent etre protegees par la loi.
Ce message electronique est destine exclusivement au(x) destinataire(s)
mentionne(s) ci-dessus.
Si vous avez recu ce message par erreur ou s il ne vous est pas destine,
veuillez immediatement le signaler a l expediteur et effacer ce message
et tous les fichiers eventuellement attaches.
Toute lecture, exploitation ou transmission des informations contenues dans ce
message est interdite.
Tout message electronique est susceptible d alteration.
A ce titre, le Groupe France Telecom decline toute responsabilite notamment s
il a ete altere, deforme ou falsifie.
De meme, il appartient au destinataire de s assurer de l absence de tout virus.
IMPORTANT.This e-mail message and any attachments are strictly confidential and
may be protected by law. This message is
intended only for the named recipient(s) above.
If you have received this message in error, or are not the named recipient(s),
please immediately notify the sender and delete this e-mail message.
Any unauthorized view, usage or disclosure ofthis message is prohibited.
Since e-mail messages may not be reliable, France Telecom Group shall not be
liable for any message if modified, changed or falsified.
Additionally the recipient should ensure they are actually virus free.
********************************************************************************
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
