Thanks David, I tested it and it's working correctly. In my case, it wasn't necessary to configure the loopback address in the interface lo0 maybe because I am using logical-system, but I will keep into account your recommendation.
Best regards, --- David Lockuán JNCIA-E JNCIS-E JNCIA-M JNCIS-M On Wed, Jun 8, 2011 at 4:19 PM, <[email protected]> wrote: > oups I forgot : set interface lo0 unit 0 family inet address 127.0.0.1 > > ________________________________________ > De : [email protected] [ > [email protected]] de la part de > [email protected] [[email protected]] > Date d'envoi : mercredi 8 juin 2011 23:01 > À : David Lockuan > Cc : [email protected] > Objet : [j-nsp] RE : RE : Bad time and date on firewall log. > > yep ! So I guess you don't use NTP. > > Try this : > > edit ex > set system ntp boot-server 127.0.0.1 > set system ntp server 127.0.0.1 > commit sync and-quit > > And check RE system uptime and sntp at PFE level > > I believe it works but I don't know if it's supported by Juniper ;-) > > Regards, > David > > > ________________________________________ > De : David Lockuan [[email protected]] > Date d'envoi : mercredi 8 juin 2011 22:26 > À : ROY David DTF/DERX > Cc : [email protected] > Objet : Re: RE : [j-nsp] Bad time and date on firewall log. > > Hi David, > > Here the output of the command "request pfe execute..." > > > ***************************************************************************** > {master} > test@MX960-LAB-RE0> request pfe execute command "show sntp" target fpc7 > SENT: Ukern command: show sntp > GOT: > GOT: SNTP status: > GOT: current time: Jan 1 02:54:24.583 > GOT: last SNTP update time: (null) > GOT: seconds since last update: 10464 > GOT: last update interval: 64.000 seconds > GOT: > GOT: last time offset: 0us > GOT: last frequency offset: 0.000 PPM > GOT: last RTT delay: 0us > GOT: Good SNTP updates: 0 > GOT: Bad SNTP updates: 0 > GOT: Number of overflows: 0 > LOCAL: End of file > > {master} > test@MX960-LAB-RE0> request pfe execute command "show sntp" target fpc0 > SENT: Ukern command: show sntp > GOT: > GOT: SNTP status: > GOT: current time: Jan 1 02:54:41.158 > GOT: last SNTP update time: (null) > GOT: seconds since last update: 10481 > GOT: last update interval: 64.000 seconds > GOT: > GOT: last time offset: 0us > GOT: last frequency offset: 0.000 PPM > GOT: last RTT delay: 0us > GOT: Good SNTP updates: 0 > GOT: Bad SNTP updates: 0 > GOT: Number of overflows: 0 > LOCAL: End of file > > {master} > test@MX960-LAB-RE0> > > ***************************************************************************** > > I note that the date is different from the system uptime. Do you know how > we can change the date and time of the PFE? > > thanks for all, > > BR, > > --- > David > > On Wed, Jun 8, 2011 at 2:19 PM, <[email protected]<mailto: > [email protected]>> wrote: > Hi, > > Did you try to check the time at PFE level : > > request pfe execute command "show sntp" target fpc<X> > > Regards, > David > ________________________________________ > De : [email protected]<mailto: > [email protected]> [[email protected] > <mailto:[email protected]>] de la part de David Lockuan > [[email protected]<mailto:[email protected]>] > Date d'envoi : mercredi 8 juin 2011 19:52 > À : [email protected]<mailto:[email protected]> > 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 [email protected]<mailto: > [email protected]> > 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. > > ******************************************************************************** > > > > > ******************************************************************************** > 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 [email protected] > 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 [email protected] https://puck.nether.net/mailman/listinfo/juniper-nsp
