[j-nsp] LS to LSQ Interfaces
Jonathan Looney
jonlooney at gmail.com
Fri Jul 30 12:50:34 EDT 2010
You could probably use a commit script that checks the version and adjusts
the interface names appropriately. I'm short on cycles to create one today;
however, someone else probably could.
-Jon
On Fri, Jul 30, 2010 at 12:33 PM, Brad Fleming <bdflemin at gmail.com> wrote:
> Unfortunately we access these devices over the MLPPP bundle. So the bundle
> needs to be up for us to issue that command or the upgrade / reboot command.
>
> Is there a way to make this part of a one-time start up script though? Like
> something Junos could automatically do with the config after the update has
> been applied and the box rebooted?
>
>
>
> On Jul 30, 2010, at 10:19 AM, Jonathan Looney wrote:
>
> In configuration mode, type 'replace pattern ls- with lsq-'. That should
>> replace any occurence of ls- with lsq-. You should probably also run "show |
>> compare" afterward to ensure that this made the expected changes.
>>
>> -Jon
>>
>> On Fri, Jul 30, 2010 at 10:48 AM, Brad Fleming <bdflemin at gmail.com>
>> wrote:
>> When upgrading JunosES software from 9.6 to 10.0R3 the ls-0/0/# interface
>> needs to be changed to lsq-0/0/#. This needs to happen on the actual
>> interface on any physical interfaces in the bundle. Does anyone know of a
>> graceful way to perform this task? Does anyone know why Juniper decided to
>> change the name of the interface (certainly makes no sense to me)?
>>
>
> _______________________________________________
> juniper-nsp mailing list juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
More information about the juniper-nsp
mailing list