On Monday, June 24, 2013 12:02:50 AM Chris Adams wrote: > Why do you expect they will? The recommended releases > are not very old; it isn't like Juniper (or any other > vendor) is going to pull back all the stock in the > supply chain and reload the OS every time they change > the recommended release. Larger deployments are > probably running a specific version that they've tested > anyway (so are likely to reload all new gear out of the > box). I always needed to load the image with SSH (even > if the release was a "favorable" version).
This is typically what happens with us also. We always get the Export version of Junos with our kit and end up having to switch to Domestic anyway, and like you say, we harmonize code across the backbone. So more than likely, we'll be overwriting the existing code with what works for us. Mark.
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp
