Welcome, Guest. Please login or register.

Author Topic: Discovery failing for new device type  (Read 2882 times)

ptm2300

  • Guest
Discovery failing for new device type
« on: April 28, 2010, 04:34:08 PM »
Hi.  Nedi autodiscovery has worked great on all new routers/switches we've added to our network up until this point.  We've added a new Cisco ASR1002 running IOS-XE and the script now fails with:

II i9 j3           a2     ignoring bad Prompt argument "": missing opening delimiter of match operat
or at /usr/local/nedi/inc/libcli-netssh.pl line 397

Line 397 of hte script is
my ($stdout, $stderr, $exit) = $ssh->cmd("","${sshen}${sshpg}$cmd{$main::dev{$_[0]}{os}}{conf}\nexit\n");

Can anyone help with what I need to do to fix?  Thanks.

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Discovery failing for new device type
« Reply #1 on: April 25, 2011, 11:23:09 PM »
I've just created a def file for our ASR1002-F, running IOS-XR 12.2-23.XNF2, and seems to be working fine.
not sure if if this helps or not but below is the def file.
I did have to make nedi use the -a -I flags as it was on mgmt interface.

I'm still running 1oh5 eagerly awaiting the release of 1oh6 final :D

Code: [Select]
# Definition for 1.3.6.1.4.1.9.1.476 created by Defgen 1.5 on 1.Sep 10 8:54 (admin)

# General
SNMPv   2HC
Type    Cisco ASR1002F
OS      IOS
Icon    csbn
Bridge
Dispro  CDP
Serial  1.3.6.1.2.1.47.1.1.1.1.11.1
Bimage  1.3.6.1.2.1.16.19.6.0

# Vlan Specific
VLnams
VTPdom
VTPmod

# Interfaces
IFalia  1.3.6.1.2.1.31.1.1.1.18
IFalix  1.3.6.1.2.1.31.1.1.1.1
IFvlan
IFvlix
IFdupl  1.3.6.1.2.1.10.7.2.1.19
IFduix  1.3.6.1.2.1.10.7.2.1.1
Halfdp  2
Fulldp  3

# Modules
Modesc  1.3.6.1.2.1.47.1.1.1.1.2
Moclas  1.3.6.1.2.1.47.1.1.1.1.5
Movalu  9
Moslot  1.3.6.1.2.1.47.1.1.1.1.7
Modhw   1.3.6.1.2.1.47.1.1.1.1.8
Modsw   1.3.6.1.2.1.47.1.1.1.1.10
Modfw   1.3.6.1.2.1.47.1.1.1.1.9
Modser  1.3.6.1.2.1.47.1.1.1.1.11
Momodl  1.3.6.1.2.1.47.1.1.1.1.13

# RRD Graphing
CPUutl  1.3.6.1.4.1.9.9.109.1.1.1.1.8.2
Temp    1.3.6.1.4.1.9.9.13.1.3.1.3.1
MemCPU  1.3.6.1.4.1.9.9.48.1.1.1.6.2
Custom

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Discovery failing for new device type
« Reply #2 on: April 25, 2011, 11:43:39 PM »
lol should of read the OPs date....
oh well.
Still can't wait to get my greedy hand on 1oh6.
Thank you community, and Remo!!!

tristanbob

  • Full Member
  • ***
  • Posts: 159
    • View Profile
Re: Discovery failing for new device type
« Reply #3 on: April 26, 2011, 01:47:09 AM »
ntmark,

Thanks for the contribution!  Why don't you fire up Nedi RC on a dev box and connect to a few dev devices to help us test Nedi further?  ;)

Cheers,

Tristan
Please visit "Other"->"Invoices" on your NeDi installation to make an annual contribution and support Nedi!

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Discovery failing for new device type
« Reply #4 on: April 26, 2011, 02:18:53 AM »
already there. just did it for production. fixing the bugs from the forum notes as i find them.
;)