NNCLI or native CLI for 8xxx chassis

[stauftm]

Just wondering how many of you out there are using cli primarily for managing your 8xxx chassis devices. And if command line is your choice, if you have a preference between the native CLI or the NNCLI?

Just curious.

Thanks,
Todd

[Michael McNamara]

The NNCLI is buggy depending on the software release. I've kept with the legacy (Passport) CLI on all my ERS 8600 switches (running 5.1.x software).

Cheers!

[brazenhead]

I use CLI for 99% of my configuration changes. I use Device Manager if I want to quickly check a port config or other setting or graph port traffic, or maybe update a port vlan membership. I've never used or investigated NNCLI - pretty much all I know about it is that it takes up space in all the documentation.

[Dominik]

I also use the old native ERS8600 CLI in fact I am used to it. Sometimes it is a littlebit confusing when you work a lot with the NNCLI (ACLI) on the stackable Avaya switches.

In long term I think a step to the ACLI on all devices make sense, so you have only one set of commands that you can use on all Avaya devices.

Cheers

[Dojs]

I used the Old CLI. Its better i think

[shezzski]

Passport CLI will be phased out and ACLI will be the only option, just like VSP9000.

This makes sense as it can save the developers time to work on other enhancements.

[Michael McNamara]

This makes sense as it can save the developers time to work on other enhancements.

When it works... it's makes great sense... when it doesn't it should be avoided like the plague.

[Paul L]

old school CLI for me. 

[telecom116]

Old CLI for me on the 8600/8800.

If you'd ever needed to program or troubleshoot OSPF routing on a ERS 5520 using the NNCLI/ACLI, you'll stay with the old CLI on your 8800s.