[j-nsp] prsearch missing in inaction

[Richard McGovern]

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 there are far worse things one could be concerned about than this.

Just my 2 cents worth.  The devil you know, is often better than the devil you do not know, . . .

Rich

Richard McGovern
Sr Sales Engineer, Juniper Networks 
978-618-3342
 

On 5/9/19, 7:35 AM, "Timur Maryin" <timamaryin at mail.ru> wrote:

    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 scratch.
    
    
    
    
    On 09-May-19 02:37, Nathan Ward wrote:
    > 
    > 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 thing intentionally for such a long time and with such poor comms and timing info. “Technical issue” sounds like an accident - but surely a restore from backup would work, right?
    > I cannot think of a scenario here which looks anywhere remotely positive for Juniper - every scenario I can consider has a root cause of “complete and utter incompetence” somewhere along the chain.
    > I really like Juniper, so I’ve searched, but, this is a hard one, help me out here..
    >