Hello,
These are taken from MX104 Routing Engine logs, correct?
If yes then "2016-05-11 16:19:58" is added by syslogd on RE.
And "2016-05-11 21:19:57" is WELF timestamp in syslog message from MS-MIC.
MS-MIC always keeps UTC timezone and this cannot be changed.
HTH
Thx
Alex
On 11/05/2016 23:08, Aa
Aaron,
Have you tested any of the OAM features on the ACX5048 like Y.1564,
802.3ah, 802.1ag, Y.1731, Two-Way Active Measurement Protocol (TWAMP) and
RFC2544? Do you have smaller ACX's like the 2200 connected to the ACX5048?
Are you using Juniper MX routers in your network as well?
On Tue, May 10,
Continuing this thread...
Any idea why my cgnat syslog shows 2 different times (Central Time and
Universal Time) ?
16:19:58 is actually the system time on the mx104, but further into the
syslog trap you see UTC 21:19:57
2016-05-11 16:19:58 User.Info 10.101.12.243 May 11 16:19:58
eng-lab-mx104-cg
On 11/May/16 20:47, Michael Loftis wrote:
> In our case except in testing with flow prior to 14.2 (unsure which
> revision), and with a cold start we've not really observed issues with
> RIB->FIB convergence in our use cases after upgrading to MPC3E's and
> later. With the prior generation setu
On Tue, May 10, 2016 at 1:12 PM, Adam Vitkovsky
wrote:
> > Michael Loftis
> > Sent: Wednesday, April 27, 2016 6:48 PM
> > To: Matthew Crocker
> > Cc: juniper-nsp@puck.nether.net
> > Subject: Re: [j-nsp] Full routes on MX5
> >
> > You'll definitely be a lot happier with the bigger RE's...usually m
You cant do it
They didnt want to create a switch with 16 x 10G for 5K$ list price
Nitzan
On Wed, May 11, 2016 at 5:30 PM, Paul S. wrote:
> Hi folks,
>
> Do the QSFP+ ports on the EX4300 support channelization (
> https://www.juniper.net/documentation/en_US/junos15.1/topics/task/configuration/
Adam-
I opened a JTAC case a few weeks back and was told to use the bgp export policy
method. I haven't tried it in our lab yet, as I'm not keen on the method. To
be fair I was looking at instance granularity, not mac address. If I end up
testing something, I'll report back.
-Michael
> ---
On 11/May/16 18:04, Adam Vitkovsky wrote:
> Brocade is using Broadcom chips as well right? Or are they using their own
> chips in some of the boxes?
The last time I tested the NetIron's, it was their own silicon.
Mark.
___
juniper-nsp mailing list j
> Mark Tinka
> Sent: Saturday, April 30, 2016 10:50 AM
> > Besides Cisco and Juniper solutions discussed, what else is out there
> > that has more than 4 10G ports with these feature sets?
>
> Look at Brocade.
>
> I'm not sure what they are doing now, but back then, they had a solid 1U
> Metro-E bo
Hi folks,
Do the QSFP+ ports on the EX4300 support channelization
(https://www.juniper.net/documentation/en_US/junos15.1/topics/task/configuration/qfx3500-3600-standalone-channel-configuring.html)?
i.e: Can I break them out to 4x10g interfaces if ever needed? I've
actually been unable to find
> Michael Hare
> Sent: Saturday, April 23, 2016 12:12 AM
>
> Does anyone know if it is possible and how to add communities to routes to
> an EVPN routing-instance in the instance configuration itself? For example,
> in bgp.evpn.0, I have
>
> 2:a.b.c.d:200::1900::00:1f:45:a0:1b:bb/304 (2 entries, 0
> Alexander Arseniev
> Sent: Wednesday, April 20, 2016 7:36 AM
>
> Hello,
> MS-MIC (and MS-MPC NPUs as well) automatically cuts out network (in your
> case .128) and broadcast (in your case .255) IPs.
> The rest cannot be expressed as single prefix, hence a bunch of smaller
> prefixes is annonced i
On 11/May/16 09:48, Phil Mayers wrote:
>
> The Cat6k including 6840 can certainly do a fair number of MPLS
> features, we use their older brother (6880, sup2T) and for a little
> while longer predecessor (sup720) as MPLS PE in L3VPN (inc. 6vPE),
> MVPN and some small amount of L2VPN (mainly EoM
On 10/05/16 21:47, Aaron wrote:
I have been curious about the cisco catalyst 6800 line… seems that the 6840
might fit this realm of smaller mpls pe… not sure of price…
The Cat6k including 6840 can certainly do a fair number of MPLS
features, we use their older brother (6880, sup2T) and for a
14 matches
Mail list logo
