[f-nsp] SLX 9640 experiences

[Jörg Kost]

Hello,

not Fredy / init7 here, but

> - no command "show interface ve <number>"

we found it under

show ip interface ve <number>

- no wildcard possible, still needs feature req,
- also under the general show interface it would be more natural and 
take up old behavior.

> - no commit/rollback at CLI

- very sure, this won't come, the 'irons had at least 'reload at/after'.

> - missing VE counters (did anybody already submit Feature Request?)

I remember during the official presentation in 2017/18, the product 
manager said,
that this is technically not possible.


Also,
+ RPKI shall come soon.

Regards
Jörg

On 8 Mar 2021, at 16:26, Robert Hass wrote:

> Hi
>
> Fredy, what are your insights after SLX implementation in Init7 
> network?
> It's probably already more than 1/2 year in production :)
>
> Let me share my experiences:
>
> We have 6 units of SLX9640 delivered and installed during May/June 
> 2020.
> All SLXes are our BGP edge routers. For "P" we still have Juniper PTX
> platform.
>
> There were problems during implementation due to bugs in code. Let's 
> me do
> the list of major problems:
> - problem with 3rd-party transceivers -> still have some issues, but
> managed with our suppiler to solve it. TAC wasn't really helpful.
> - problem with sflow and redundancy -> resolved in 4 months
> - problem with VRRP and mLAGs -> resolved in 3 months
>
> It looks some features are broken and not tested from beginning - for
> instance our VRRP and sflow
> problems tells us - mLAG (MCT) is not tested or used by many customers 
> in
> production.
>
> Positives:
> - power consumption vs MLXe
> - very good combination of amount 100G/10G ports
> - at the end issues has been resolved, and Extreme delivered fixed 
> software
>
> Negatives:
> - no commit/rollback at CLI
> - missing VE counters (did anybody already submit Feature Request?)
> - no command "show interface ve <number>"
> - missing some other CLI commands
> - needs rACL from the beginning as control plane have very strange 
> ports
> exposed to 0.0.0.0/0 :)
>
> It was often necessary to literally show GTAC what was behaving badly.
> Unfortunately GTAC is not Arista's support;)
>
> Rob
>