Re: [j-nsp] prsearch missing in inaction

Agreed it was offline for far too long, in fact even when it was still operational it clearly wasn't indexing for months since I could search for a release and model number and miss heaps of PR's that were in release notes or mentioned by JTAC in cases I'd logged when things were on fire. On Tue,

Re: [j-nsp] prsearch missing in inaction

Yeah, thanks Juniper for taking a year to fix a critical tool for network engineers. I'll be right back, I just upgraded one of my Juniper devices and now my network is on fire. On 05.08.19 09:12, Chris Lee wrote: > And it's 5th August and as promised in the last KB update PR Search >

Re: [j-nsp] prsearch missing in inaction

And it's 5th August and as promised in the last KB update PR Search functionality is now back online! Thank you all at Juniper who worked on restoring this to service! On Fri, Aug 2, 2019 at 11:58 PM Richard McGovern wrote: > I am doing some new checking. I am like 99.9% sure the floppy disk

Re: [j-nsp] prsearch missing in inaction

I am doing some new checking. I am like 99.9% sure the floppy disk idea will not fly -__ Hopefully I will have an update sometime next week. Enjoy your visit to San Jose. Regards, Rich Richard McGovern Sr Sales Engineer, Juniper Networks 978-618-3342 I’d rather be lucky than good, as I

Re: [j-nsp] prsearch missing in inaction

Hi, Was reminded of this today. I see that basic search will be fixed by 2019-08-05 - but still no comparison between releases which really is the key thing that people want. I’d like a dump of all the PRs and “fixed in release x” details, so I can build my own PR search tool and make it

Re: [j-nsp] prsearch missing in inaction

Nathan, not sure what history you are seeking, but if tell me what PR listing you seek, I'll see what I can gather. Richard McGovern Sr Sales Engineer, Juniper Networks 978-618-3342 On 5/13/19, 9:25 AM, "Nathan Ward" wrote: > On 14/05/2019, at 1:17 AM, Nathan Ward wrote: >

Re: [j-nsp] prsearch missing in inaction

> On 14/05/2019, at 1:17 AM, Nathan Ward wrote: > > >> On 9/05/2019, at 11:52 PM, Richard McGovern > > wrote: >> >> Nathan, I am not sure what you want to hear, or what would make you >> satisfied, but YES Juniper [IT?] did screw-up, and a restore from back-up

Re: [j-nsp] prsearch missing in inaction

> On 9/05/2019, at 11:55 PM, Richard McGovern wrote: > > Tom, sorry but that is way far-fetched. Nathan, if TAC will not provide you > this info, then I am sure your local SE can assist. I know I can/would for > any of my accounts. Oh sure, my local SE is great, as noted earlier in the

Re: [j-nsp] prsearch missing in inaction

> On 9/05/2019, at 11:52 PM, Richard McGovern wrote: > > Nathan, I am not sure what you want to hear, or what would make you > satisfied, but YES Juniper [IT?] did screw-up, and a restore from back-up > was/is not possible. So this situation is now being worked on, unfortunately > at a not

Re: [j-nsp] prsearch missing in inaction

* Richard McGovern via juniper-nsp [2019-05-09 13:58]: > Tom, sorry but that is way far-fetched. Nathan, if TAC will not > provide you this info, then I am sure your local SE can assist. I > know I can/would for any of my accounts. I don't know, Juniper seems to go strange ways in terms of

Re: [j-nsp] prsearch missing in inaction

Hi, On Thu, May 9, 2019 at 1:54 PM Richard McGovern via juniper-nsp wrote: > Nathan, I am not sure what you want to hear, or what would make you > satisfied, but YES Juniper [IT?] did screw-up, and a restore from back-up > was/is not possible. So this situation is now being worked on,

Re: [j-nsp] prsearch missing in inaction

I cannot agree more, but unfortunately not my area to affect. BTW, in 40 years in networking working for multiple vendors, every company has room (and sometime great room) for improvement, . . . Richard McGovern Sr Sales Engineer, Juniper Networks 978-618-3342 On 5/9/19, 8:11 AM, "James C

Re: [j-nsp] prsearch missing in inaction

As someone who has a P1 case open on the QFX10008 (8.4R1.8) [WMU has retreated to 8.1R3.3] now sitting at day 15 that produced three different types of core dumps with issues on the ULC-30Q28, ULC-60S-6Q, and MSNOOPD, it would be really nice to go fishing on the bugs myself. I have found

Re: [j-nsp] prsearch missing in inaction

Tom, sorry but that is way far-fetched. Nathan, if TAC will not provide you this info, then I am sure your local SE can assist. I know I can/would for any of my accounts. Rich Richard McGovern Sr Sales Engineer, Juniper Networks 978-618-3342 On 5/9/19, 5:02 AM, "Tom Hodgson" wrote:

Re: [j-nsp] prsearch missing in inaction

Nathan, I am not sure what you want to hear, or what would make you satisfied, but YES Juniper [IT?] did screw-up, and a restore from back-up was/is not possible. So this situation is now being worked on, unfortunately at a not so fast pace. I hope you decide to stay with Juniper, as I feel

Re: [j-nsp] prsearch missing in inaction

https://kb.juniper.net/KB33515 If i recall correctly what i heard about it. There is some third party(or smth) search engine which is(was) used and it had issues. And there is no way to upgrade/fix that engine as it out of support/development. So i has to be replaced or re-written from

Re: [j-nsp] prsearch missing in inaction

>> And regarding PRs delta between your present release and 17.4R2-S2 release >> , JTAC is not authorised to provide that info. I suggest you to reach out >> to juniper accounts team who can help you on this > > Why? I have no idea, maybe this engineer was just lazy but I’ve had the same >

Re: [j-nsp] prsearch missing in inaction

> On 9/05/2019, at 10:44 AM, Richard McGovern wrote: > > Contacted someone internally and yes this is being worked on. The time > period is "end of Q2, hopefully sooner". Can you shed any light on what on earth is going on, and why? It seems crazy that a company would disable this sort of

Re: [j-nsp] prsearch missing in inaction

Contacted someone internally and yes this is being worked on. The time period is "end of Q2, hopefully sooner". In the meantime, if you need comparison between 2 releases of same major release, then TAC should be able to generate this for you via internal PR DIFF tool. This only works

Re: [j-nsp] prsearch missing in inaction

> On 8/05/2019, at 7:05 PM, Rob Foehl wrote: > > On Tue, 7 May 2019, Nathan Ward wrote: > >> Is it actually coming back? Hard to believe the “technical issue” given how >> long it’s been, seems like a pretty big systemic issue rather than a >> technical one. “Actively worked on” seems pretty

Re: [j-nsp] prsearch missing in inaction

On Tue, 7 May 2019, Nathan Ward wrote: Is it actually coming back? Hard to believe the “technical issue” given how long it’s been, seems like a pretty big systemic issue rather than a technical one. “Actively worked on” seems pretty inactive, to me. Maybe it runs on Space, and they're just

[j-nsp] prsearch missing in inaction

Hi, Anyone know what the story with this is? I just got a “you should upgrade to one of these releases” from JTAC, but apparently they’re not authorised to do a bug search for me to compare releases, which is what the currently offline prsearch tool used to do for anyone who wanted it. Been