[j-nsp] About Secure Transport for RPKI on JUNOS

2018-12-21 Thread Pyxis LX
Hi, All, Does JUNOS support any secure transports mentioned in RFC6810 for rpki-rtr protocol? (SSHv2/IPsec or TLS for rpki-rtr-tls?) I am unable to find any documents related on the JUNOS website or CLI. Given that IOS-XR supports SSHv2 tunnel, I would suspect JUNOS has same level of support? Reg

Re: [j-nsp] qfx5120-48y-8c - jtac recommeded junos version

2018-12-21 Thread Eric Krichbaum
You'll have to let us know how well they work. I heard no vc stacking until v19 code or so. Also wondering about 18 level code. Just took a set of 5100s to 17.3 with good results. -Original Message- From: juniper-nsp On Behalf Of Aaron Gould Sent: Friday, December 21, 2018 10:34 AM To: j

[j-nsp] qfx5120-48y-8c - jtac recommeded junos version

2018-12-21 Thread Aaron Gould
I got my QFX-5120's in a couple days ago. running 18.3R1.11 I don't see a JTAC Recommendation for 5120 https://kb.juniper.net/InfoCenter/index?page=content &id=KB21476 {master:0} root> show system information Model: qfx

Re: [j-nsp] SNMP_EVLIB_FAILURE - snmp not working anymore

2018-12-21 Thread Emille Blanc
Juniper has always been accommodating in my occasional request to provide disambiguation to KB's or PR's, whenever I use the feedback widget. Let them know your thoughts. -Original Message- From: juniper-nsp [mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Sebastian Wiesinger Se

Re: [j-nsp] interface-range inheritance change in 14.1X53 and 15.1

2018-12-21 Thread Thomas Bellman
On 2018-12-21 23:22 UTC, Anderson, Charles R wrote: > Can anyone shed some light on WHY this change was made? I much prefer > the old behavior. > > From PR1281947: > > "The behavior of the "interface-range" configuration statement changed > in 14.1X53 and 15.1. Prior to 14.1X53 and 15.1, more s

Re: [j-nsp] SNMP_EVLIB_FAILURE - snmp not working anymore

2018-12-21 Thread Sebastian Wiesinger
* Olivier Benghozi [2018-12-21 02:05]: > PR1270686 > > restart statistics-service This PR is one example of something I don't like in most Juniper PRs. It states the command you quoted but then there is also this text: Workaround: Disable pfed's periodic refresh using config: set accounting-op

Re: [j-nsp] interface-range inheritance change in 14.1X53 and 15.1

2018-12-21 Thread Timur Maryin via juniper-nsp
My bet is that is an example of poorly written external description. Besides "Resolved-In" has only one version. On 21-Dec-18 00:22, Anderson, Charles R wrote: Can anyone shed some light on WHY this change was made? I much prefer the old behavior. From PR1281947: "The behavior of the "int

Re: [j-nsp] SNMP_EVLIB_FAILURE - snmp not working anymore

2018-12-21 Thread Jeff Meyers
Thanks, worked! Am 21.12.2018 um 02:05 schrieb Olivier Benghozi: PR1270686 restart statistics-service Le 21 déc. 2018 à 01:23, Jeff Meyers a écrit : Dec 21 01:20:40 fra4-cr2 mib2d[67435]: SNMP_EVLIB_FAILURE: PFED ran out of transfer credits with PFE.Failed to get stats. ifl index: 373 I