Re: [j-nsp] Hyper Mode on MX

2019-03-10 Thread Saku Ytti
Hey Michael, > After going back to review what I actually did vs what I thought I did when > enabling hyper-mode, I very much got it backwards re icmp redirects. You > have to allow redirects to be sent to use hyper-mode. That's a step > backwards and a calculated risk to take. I disallow

Re: [j-nsp] Hyper Mode on MX

2019-03-10 Thread Michael Hare via juniper-nsp
Replying to myself before someone else catches my egregious error... After going back to review what I actually did vs what I thought I did when enabling hyper-mode, I very much got it backwards re icmp redirects. You have to allow redirects to be sent to use hyper-mode. That's a step

Re: [j-nsp] Old JunOS upgrade path

2019-03-10 Thread Saku Ytti
On Sun, Mar 10, 2019 at 4:30 PM Tom Beecher wrote: > was when it was shut down. ( Hopefully. :) ) When you upgrade it, the > process only modifies certain components. Any OS upgrade process like that This is not true, the upgrade is fresh install. It is not like you do upgrade on your laptop

Re: [j-nsp] Old JunOS upgrade path

2019-03-10 Thread Tom Beecher
This was, and still is, the most accurate answer in the thread. To expand on it further Cisco IOS images are standalone binary images. Each time the device is powered on, it loads the image it is configured too, and executes it. The entire operating system is encapsulated in this image file,

Re: [j-nsp] Old JunOS upgrade path

2019-03-10 Thread Mark Tinka
On 9/Mar/19 11:18, Saku Ytti wrote: > So Gert's question 'y tho?' is very much valid, and the most obvious > reasons is because Juniper doesn't want to increase the product cost > to cover lab testing from any-to-any, as it would mean ever increase > money and time cost to release. By setting