Welcome, Guest. Please login or register.

Author Topic: Cron and discovery.  (Read 4251 times)

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Cron and discovery.
« on: February 13, 2012, 09:18:57 PM »
We have been using 1o6 with an hourly cron job with options -p -o
Since the upgrade to 1o7 I've noticed that this process is now taking 61 mintues where it used to be ~20mins.

Is there a faster/better way for me to do this as it was nice having it run every hour.

I'm not that keen to split it up into separate jobs as most of the gear is located in one site with similar names.

The amount of time it takes to run for each switch/router seems to increase each time a switch/router is completed.

Any ideas?
Cheers
Code: [Select]
10.16.2.1    PETRO6CORE1  v16St i72  Jv p3/0 b3    Fp1002Fx1002Fp1Fp1004Fx1004Fp1005Fx1005Fp95Fp1003Fx1003Fp980Fx980Fp224Fx224f78  105/4-9s
10.90.6.10   DNSW1        v7IxIx i29 Jv p0/0 b1    Fp1002Fx1002Fp1Fp1005Fx1005Fp1004Fx1004Fp1003Fx1003Fp980Fx980f6  104/5-3s
10.21.1.10   HMSW1        v8IxIx i29  p0/0 b1   Fp1002Fx1002Fp1Fp1005Fx1005Fp1004Fx1004Fp1003Fx1003Fp980Fx980f12  103/6-1s
10.16.7.10   PGSW1        v9 i13      p1/0    Fp1002Fx1002Fp1005Fx1005Fp1003Fx1003Fp1Fx1Fp1004Fx1004Fp980Fx980f20  103/7-2s
10.18.1.10  AKDXTS1   v12 i52     p2/1   Fp1002Fx1002Fp1005Fx1005Fp999Fp1003Fx1003Fp1Fx1Fp1004Fx1004Fp980Fx980f36  104/8-4s
...
...
10.19.1.19   AV1COGL1   v12 i12     p0/1    Fp1002Fx1002Fp1005Fx1005Fp1003Fx1003Fp208Fx208Fp1Fx1Fp1004Fx1004Fp980Fx980f28   22/163-3s
10.59.1.38   AV1POST2     v8St i55   Jv p0/2    Fp1002Fx1002Fp1Fp1005Fx1005Fp1004Fx1004Fp1003Fx1003Fp980Fx980f33   21/164-2s
10.19.1.46   AV1RBS1      v8St i55   Jv p0/2    Fp1002Fx1002Fp1005Fx1005Fp1003Fx1003Fp1Fp1004Fx1004Fp980Fx980f24   20/165-2s
10.26.8.5    AV1ASYNC1    SuIb i3 Jv p0/1       19/166-4s
10.19.1.49   AV1ARC5      v9IxIx i29 Jv p0/2    Fp1002Fx1002Fp1005Fx1005Fp1003Fx1003Fp1Fp1004Fx1004Fp980Fx980f45   18/167-2s
10.59.1.43   AV1CINE2     v8St i55   Jv p0/2    Fp1002Fx1002Fp1Fp1005Fx1005Fp1004Fx1004Fp1003Fx1003Fp980Fx980f31   17/168-2s
10.19.1.34   AV1PABX2     v9St i55   Jv p0/2    Fp1002Fx1002Fp1005Fx1005Fp1003Fx1003Fp1Fp1004Fx1004Fp980Fx980f18   16/169-2s

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2785
    • View Profile
    • NeDi
Re: Cron and discovery.
« Reply #1 on: February 13, 2012, 11:03:13 PM »
 :( I actually hoped it was faster than oh6. Do you have full logs to compare? Do all devices take longer or is it limited to a few? Was it the first discovery with oh7 taking 61 minutes or is it the same for subsequent runs? Eventually a run with -v would reveal other possibilities, where nedi loses time..
« Last Edit: February 13, 2012, 11:14:11 PM by rickli »
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Cron and discovery.
« Reply #2 on: February 13, 2012, 11:18:16 PM »
arh, I do not have the old logs, but I know it was only taking about 20mins - they got overwritten. :(

Was just watching current discovery of this one chassis cisco 6504E
Looks like after each of the Fp1004 or Fx1004 it just stops for ages and the rest of the vlans.
We use these vlans on a few of our switches but not all, most use the default ascending for internal vlans but some use descending allocation 4096 downwards.

this has been commented out in nedi.conf
;ignoredvlans   ^10[01][0-9]$


Code: [Select]
11:06:13  -  start poll
11:09:12  -  end poll
cisco 6504E
10.19.0.1    AV1CORE1     v63St i204  p15/3 b1    Fp1002Fx1002Fp443Fp445Fp1Fp1004Fx1004Fp1005Fx1005Fp447Fp980Fp446Fp245Fp441Fp444Fp442Fp1003Fx1003f272  103/3-178s


Am trying it with the ignored vlans back in nedi.conf. This may be my problem.
Will update soon on outcome.
Mark.

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Cron and discovery.
« Reply #3 on: February 13, 2012, 11:48:50 PM »
Scan took 23 minutes, which is about right.
Have double checked old nedi.conf and it has these vlans being ignored.

Guess I'll figure out a way to do the switches with VlanIDs 1001-1005.

Cheers
Mark.

pc_sg

  • Guest
Re: Cron and discovery.
« Reply #4 on: February 14, 2012, 09:02:36 AM »
Look at this article:

http://www.ciscopress.com/articles/article.asp?p=29803

"Numbers 1001 to 1024 are reserved by Cisco and cannot be configured."

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Cron and discovery.
« Reply #5 on: February 14, 2012, 09:24:42 PM »
Yeah it says that, but the internal allocation of vlans can be changed so that you can use them.
It starts to count down from 4096 instead of counting upwards from 1001.
IOS command:vlan internal allocation policy descending

Can be handy, but also a pain as I've just found out :(

rickli

  • Administrator
  • Hero Member
  • *****
  • Posts: 2785
    • View Profile
    • NeDi
Re: Cron and discovery.
« Reply #6 on: February 14, 2012, 10:29:33 PM »
Have you tried using the CLI for getting forwarding tables? It's much faster than SNMP with vlanindexing anyways...
Please consider Other-Invoices on your NeDi installation for an annual contribution, tx!
-Remo

pc_sg

  • Guest
Re: Cron and discovery.
« Reply #7 on: February 15, 2012, 08:29:04 AM »
Yeah it says that, but the internal allocation of vlans can be changed so that you can use them.
It starts to count down from 4096 instead of counting upwards from 1001.
IOS command:vlan internal allocation policy descending

Can be handy, but also a pain as I've just found out :(
Looking around for an explanation of advantages of this command, I've found nothing.
I absolutely don't want to criticize, but looking to the Cisco documentation I've found, internal VLANs are never usable. But I may be wrong!
I'll question our LAN Advisor...
Anyway, Extended VLAN are not propagated by VTP domain, so are useless for us.
Currently the default "vlan internal allocation policy ascending" is fine for us. The best way we are using VLAN it is to identify unambiguously VLAN <-> subnet association. So 1000 VLAN are enough. Of course network segmentation is good practice. But this is to indulge in rhetoric :)

Paolo (don't blame me!)

ntmark

  • Full Member
  • ***
  • Posts: 136
    • View Profile
    • tvnz.co.nz
Re: Cron and discovery.
« Reply #8 on: February 15, 2012, 08:38:52 PM »
I totally agree Paolo.
If I had any say in this gear that went into our network we would of left the vlan ascending policy as is and not used those vlanIDs.

Yes internal vlans aren't usable but they can be changed from default, as I believe you've already looked up that command. :)

haha, network segmentation is why we are using those vlans lol.
Maybe in the next incarnation we can fix it, but until then /sadface

Mark.