• May 22, 2012, 08:29:52 PM
Welcome, Guest. Please login or register. Registration is free.
Did you miss your activation email?

Author Topic: NNCLI or native CLI for 8xxx chassis  (Read 554 times)

0 Members and 1 Guest are viewing this topic.

Offline stauftm

  • Full Member
  • ***
  • Posts: 69
NNCLI or native CLI for 8xxx chassis
« on: November 23, 2011, 03:21:20 PM »
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


Online Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 2517
    • Michael McNamara
Re: NNCLI or native CLI for 8xxx chassis
« Reply #1 on: November 23, 2011, 04:39:01 PM »
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!
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline brazenhead

  • Sr. Member
  • ****
  • Posts: 120
Re: NNCLI or native CLI for 8xxx chassis
« Reply #2 on: November 23, 2011, 07:55:14 PM »
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.

Offline Dominik

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 662
Re: NNCLI or native CLI for 8xxx chassis
« Reply #3 on: November 24, 2011, 06:20:05 AM »
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
Itīs always the network...

Offline Dojs

  • Jr. Member
  • **
  • Posts: 42
Re: NNCLI or native CLI for 8xxx chassis
« Reply #4 on: November 24, 2011, 02:23:45 PM »
I used the Old CLI. Its better i think

Offline shezzski

  • Jr. Member
  • **
  • Posts: 29
Re: NNCLI or native CLI for 8xxx chassis
« Reply #5 on: November 29, 2011, 01:09:48 AM »
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.

Online Michael McNamara

  • Administrator
  • Hero Member
  • *****
  • Posts: 2517
    • Michael McNamara
Re: NNCLI or native CLI for 8xxx chassis
« Reply #6 on: November 29, 2011, 11:06:15 AM »
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.
We've been helping network engineers, system administrators and technology professionals since June 2009.
If you've found this site useful or helpful, please help me spread the word. Link to us in your blog or homepage - Thanks!

Offline Paul L

  • Global Moderator
  • Sr. Member
  • *****
  • Posts: 278
    • Paul's Networking blog
Re: NNCLI or native CLI for 8xxx chassis
« Reply #7 on: November 30, 2011, 09:44:16 PM »
old school CLI for me. 
ACSS- Avaya Enterprise Routing Switch  #8

Offline telecom116

  • Jr. Member
  • **
  • Posts: 47
Re: NNCLI or native CLI for 8xxx chassis
« Reply #8 on: December 16, 2011, 07:49:35 PM »
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.