I have left 5.8f for good now and I am throwing myself under the 6.1
train. At least my SSH connection issue is fixed in this release and I
can focus purely on the LACP-issues. During my dry ssh period, I
committed https://github.com/ipcjk/brocadecli - this tool can paste
changes into the mlx/cer-series with interval, timeouts, etc - maybe
somebody find it also useful for daily or automated tasks.
The sbsupgrd.py / the SCP based manifest upgrade does not work for me,
because there is no variable for the enable-password. I will stick to
tftp and/or the „old“ scp way for now.
Jörg
On 1 Feb 2017, at 7:05, Youssef Bengelloun-Zahr wrote:
> SCP based upgrade is possible, my SE confirmed that some time ago.
>
> It has been introduced officially as a feature in release 6.1, look at
> the release notes.
>
> HTH..
>
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp
train. At least my SSH connection issue is fixed in this release and I
can focus purely on the LACP-issues. During my dry ssh period, I
committed https://github.com/ipcjk/brocadecli - this tool can paste
changes into the mlx/cer-series with interval, timeouts, etc - maybe
somebody find it also useful for daily or automated tasks.
The sbsupgrd.py / the SCP based manifest upgrade does not work for me,
because there is no variable for the enable-password. I will stick to
tftp and/or the „old“ scp way for now.
Jörg
On 1 Feb 2017, at 7:05, Youssef Bengelloun-Zahr wrote:
> SCP based upgrade is possible, my SE confirmed that some time ago.
>
> It has been introduced officially as a feature in release 6.1, look at
> the release notes.
>
> HTH..
>
>
_______________________________________________
foundry-nsp mailing list
foundry-nsp@puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp