Re: [j-nsp] RE : RE : RE : Bad time and date on firewall log.
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, wrote:
> oups I forgot : set interface lo0 unit 0 family inet address 127.0.0.1
>
>
> De : juniper-nsp-boun...@puck.nether.net [
> juniper-nsp-boun...@puck.nether.net] de la part de
> david@orange-ftgroup.com [david@orange-ftgroup.com]
> Date d'envoi : mercredi 8 juin 2011 23:01
> À : David Lockuan
> Cc : juniper-nsp@puck.nether.net
> 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 [dlock...@gmail.com]
> Date d'envoi : mercredi 8 juin 2011 22:26
> À : ROY David DTF/DERX
> Cc : juniper-nsp@puck.nether.net
> 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, david@orange-ftgroup.com>> wrote:
> Hi,
>
> Did you try to check the time at PFE level :
>
> request pfe execute command "show sntp" target fpc
>
> Regards,
> David
>
> De : juniper-nsp-boun...@puck.nether.net 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]
> JUN
[j-nsp] RE : RE : RE : Bad time and date on firewall log.
oups I forgot : set interface lo0 unit 0 family inet address 127.0.0.1
De : juniper-nsp-boun...@puck.nether.net [juniper-nsp-boun...@puck.nether.net]
de la part de david@orange-ftgroup.com [david@orange-ftgroup.com]
Date d'envoi : mercredi 8 juin 2011 23:01
À : David Lockuan
Cc : juniper-nsp@puck.nether.net
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 [dlock...@gmail.com]
Date d'envoi : mercredi 8 juin 2011 22:26
À : ROY David DTF/DERX
Cc : juniper-nsp@puck.nether.net
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,
mailto:david@orange-ftgroup.com>> wrote:
Hi,
Did you try to check the time at PFE level :
request pfe execute command "show sntp" target fpc
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: accep
Re: [j-nsp] RE : RE : Bad time and date on firewall log.
On Wed, Jun 08, 2011 at 11:01:36PM +0200, david@orange-ftgroup.com wrote: > 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 ;-) http://juniper.cluepon.net/ER_Local_time_source Sigh... trying to get that into JUNOS for almost 10 years now. :-Z Too easy to fix. won't happen I guess. Best regards, Daniel -- CLUE-RIPE -- Jabber: d...@cluenet.de -- dr@IRCnet -- PGP: 0xA85C8AA0 ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[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 [dlock...@gmail.com]
Date d'envoi : mercredi 8 juin 2011 22:26
À : ROY David DTF/DERX
Cc : juniper-nsp@puck.nether.net
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,
mailto:david@orange-ftgroup.com>> wrote:
Hi,
Did you try to check the time at PFE level :
request pfe execute command "show sntp" target fpc
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: acce
Re: [j-nsp] RE : 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, wrote:
> Hi,
>
> Did you try to check the time at PFE level :
>
> request pfe execute command "show sntp" target fpc
>
> 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
>
[j-nsp] RE : Bad time and date on firewall log.
Hi,
Did you try to check the time at PFE level :
request pfe execute command "show sntp" target fpc
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 ele
[j-nsp] mlppp testing gear
Hi everyone - does anyone know of a MLPPP testing gear. I need to test the scalability of MLPPPoE/oA but have not find anything useful (Spirent does not support it for sure nor does the original Ixia. I'm checking if at least N2X arm of Ixia has something). Thanks, Marlon ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[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
Re: [j-nsp] Ipv6 over Aggregated Sonet
Hi Dusan Thanks for your response Also we configured the same prefix over GigabitEthernet interface connecting both devices and everything looks ok (even is-is V6), but with the Agregatted sonnet does not, regards Mario -Mensaje original- De: Dusan Avbreht Para: Mario Andres Rueda Jaimes Cc: juniper-nsp@puck.nether.net Asunto: Re: [j-nsp] Ipv6 over Aggregated Sonet Fecha: Wed, 8 Jun 2011 17:34:09 +0200 Hi Mario, Version 10.4 till revision R4 have problem with IPv6 next-hope reachability. Tray with 10.4R4.5 and it works! Regards, Dusan On Wed, Jun 8, 2011 at 3:42 PM, Mario Andres Rueda Jaimes wrote: Hi All We are trying to configure IPv6 addressing, between a M20 and M160 running junos 10.4 and 9.6 respectively over aggregated sonet interface, the main issue is that is-is (V6) adjacency don't comes up, the two Ip addresses are reachable each other via ICMP, but the neighbor doesn't. Instead, ipv4 is-is runs ok. I think that the problem is that Agreggate Sonnet interfaces doesn't have any mac-address associated by default. The official documentation I've been read says that no problem is espected activating ipv6 over aggregated sonnet interfaces Anybody has any kind of suggestions about this case ? Thanks Mario Rueda ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp -- Dušan Avbreht Professional Service Consultant AVDUS d.o.o. Mobile: +386 41 340546 E: d.avbr...@gmail.com E: du...@avdus.net ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
Re: [j-nsp] Ipv6 over Aggregated Sonet
Hi Mario, Version 10.4 till revision R4 have problem with IPv6 next-hope reachability. Tray with 10.4R4.5 and it works! Regards, Dusan On Wed, Jun 8, 2011 at 3:42 PM, Mario Andres Rueda Jaimes < maeve2...@gmail.com> wrote: > Hi All > > We are trying to configure IPv6 addressing, between a M20 and M160 > running junos 10.4 and 9.6 respectively over aggregated sonet interface, > the main issue is that is-is (V6) adjacency don't comes up, the two Ip > addresses are reachable each other via ICMP, but the neighbor doesn't. > Instead, ipv4 is-is runs ok. > > I think that the problem is that Agreggate Sonnet interfaces doesn't > have any mac-address associated by default. The official documentation > I've been read says that no problem is espected activating ipv6 over > aggregated sonnet interfaces > > Anybody has any kind of suggestions about this case ? > > > Thanks > > Mario Rueda > > ___ > juniper-nsp mailing list juniper-nsp@puck.nether.net > https://puck.nether.net/mailman/listinfo/juniper-nsp > -- Dušan Avbreht Professional Service Consultant AVDUS d.o.o. Mobile: +386 41 340546 E: d.avbr...@gmail.com E: du...@avdus.net ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
[j-nsp] Ipv6 over Aggregated Sonet
Hi All We are trying to configure IPv6 addressing, between a M20 and M160 running junos 10.4 and 9.6 respectively over aggregated sonet interface, the main issue is that is-is (V6) adjacency don't comes up, the two Ip addresses are reachable each other via ICMP, but the neighbor doesn't. Instead, ipv4 is-is runs ok. I think that the problem is that Agreggate Sonnet interfaces doesn't have any mac-address associated by default. The official documentation I've been read says that no problem is espected activating ipv6 over aggregated sonnet interfaces Anybody has any kind of suggestions about this case ? Thanks Mario Rueda ___ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
