Send netdisco-users mailing list submissions to
        [email protected]

To subscribe or unsubscribe via the World Wide Web, visit
        https://lists.sourceforge.net/lists/listinfo/netdisco-users
or, via email, send a message with subject or body 'help' to
        [email protected]

You can reach the person managing the list at
        [email protected]

When replying, please edit your Subject line so it is more specific
than "Re: Contents of netdisco-users digest..."
Today's Topics:

   1. Re: Problem after upgrade (Sassan Dibadj)
   2. patch against SNMP::Info::Layer3::AlcateLucent.pm os_ver()
      (Chris Stromsoe)
   3. Re: patch against SNMP::Info::Layer3::AlcateLucent.pm
      os_ver() (Chris Stromsoe)
   4. Re: patch against SNMP::Info::Layer3::AlcateLucent.pm
      os_ver() (Chris Stromsoe)
   5. Re: Netdisco2 Cron (Deshong, Kenneth)
   6. Netdisco2 Web Application (Deshong, Kenneth)
--- Begin Message ---
My web front end continued to work while the error was going on, I had to 
revert back to a backup before the upgrade as I was under a time crunch.

I feel safer running the upgrade again now though.

Thanks for the catch.

-----Original Message-----
From: Oliver Gorwits [mailto:[email protected]]
Sent: Tuesday, July 15, 2014 11:13 AM
To: [email protected]
Subject: Re: [Netdisco] Problem after upgrade

On 2014-07-15 13:32, Harry wrote:
> Harry <spam@...> writes:
>
> Looks like I accidentially solved it :)
>
> After adding "interactives" to the workers config the error
> disappeared.
> Now I have in deployment.yml
> workers:
>   interactives: 2
>   pollers: 10

Nice catch, many thanks!

I've just uploaded version 2.028003 to CPAN with a default for interactives if 
one is not set.

regards,
oliver.



________________________________

UT Southwestern Medical Center
The future of medicine, today.

--- End Message ---
--- Begin Message --- It looks like sysDescr format for AOS changed some time after 6.4.2.954.R01 to lead with the string Alcatel-Lucent, the hardware model, then the OS release. This patch fixes devices with newer AOS releases being discovered with an OS version of "Alcatel-Lucent".

-Chris

--- AlcatelLucent.pm.orig       2014-06-30 16:28:51.486408429 -0700
+++ AlcatelLucent.pm    2014-06-30 16:24:35.870596229 -0700
@@ -115,6 +115,11 @@
     my $alu = shift;

     my $descr = $alu->description();
+
+    if ( $descr =~ m/^Alcatel-Lucent \S+ (\S+) Service Release, / ) {
+        return $1;
+    }
+
     if ( $descr =~ m/^(\S+)/ ) {
         return $1;
     }




--- End Message ---
--- Begin Message --- A slightly better replacement for SNMP::Info::Layer3::AlcateLucent.pm os_ver() than the earlier patch.

sub os_ver {
    my $alu = shift;

    my $descr = $alu->description();

    if ( $descr =~ m/^Alcatel-Lucent \S+ ([\.\dR]+) Service Release, / ) {
        return $1;
    }

    if ( $descr =~ m/^Alcatel-Lucent ([\.\dR]+) GA, / ) {
        return $1;
    }

    if ( $descr =~ m/^(\S+)/ ) {
        return $1;
    }

    # No clue what this will try but hey
    return $alu->SUPER::os_ver();
}


-Chris

On Tue, 15 Jul 2014, Chris Stromsoe wrote:

It looks like sysDescr format for AOS changed some time after
6.4.2.954.R01 to lead with the string Alcatel-Lucent, the hardware model,
then the OS release.  This patch fixes devices with newer AOS releases
being discovered with an OS version of "Alcatel-Lucent".

-Chris

--- AlcatelLucent.pm.orig       2014-06-30 16:28:51.486408429 -0700
+++ AlcatelLucent.pm    2014-06-30 16:24:35.870596229 -0700
@@ -115,6 +115,11 @@
     my $alu = shift;

     my $descr = $alu->description();
+
+    if ( $descr =~ m/^Alcatel-Lucent \S+ (\S+) Service Release, / ) {
+        return $1;
+    }
+
     if ( $descr =~ m/^(\S+)/ ) {
         return $1;
     }


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users




--- End Message ---
--- Begin Message --- Last update. Collapsed all the regexps into a single line. This correctly parses os version on all of the A-L devices I have access to.

sub os_ver {
    my $alu = shift;

    my $descr = $alu->description();
    return $1 if $descr =~ m/\b(\d[\.\d]+R\d+) (?:GA|Service Release), /;

    # No clue what this will try but hey
    return $alu->SUPER::os_ver();
}



-Chris

On Tue, 15 Jul 2014, Chris Stromsoe wrote:

A slightly better replacement for SNMP::Info::Layer3::AlcateLucent.pm
os_ver() than the earlier patch.

sub os_ver {
    my $alu = shift;

    my $descr = $alu->description();

    if ( $descr =~ m/^Alcatel-Lucent \S+ ([\.\dR]+) Service Release, / ) {
        return $1;
    }

    if ( $descr =~ m/^Alcatel-Lucent ([\.\dR]+) GA, / ) {
        return $1;
    }

    if ( $descr =~ m/^(\S+)/ ) {
        return $1;
    }

    # No clue what this will try but hey
    return $alu->SUPER::os_ver();
}


-Chris

On Tue, 15 Jul 2014, Chris Stromsoe wrote:

It looks like sysDescr format for AOS changed some time after
6.4.2.954.R01 to lead with the string Alcatel-Lucent, the hardware model,
then the OS release.  This patch fixes devices with newer AOS releases
being discovered with an OS version of "Alcatel-Lucent".

-Chris

--- AlcatelLucent.pm.orig       2014-06-30 16:28:51.486408429 -0700
+++ AlcatelLucent.pm    2014-06-30 16:24:35.870596229 -0700
@@ -115,6 +115,11 @@
     my $alu = shift;

     my $descr = $alu->description();
+
+    if ( $descr =~ m/^Alcatel-Lucent \S+ (\S+) Service Release, / ) {
+        return $1;
+    }
+
     if ( $descr =~ m/^(\S+)/ ) {
         return $1;
     }


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users


------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users




--- End Message ---
--- Begin Message ---
Looking at the new setup guide (I'm installing the newest version of Netdisco) 
and I have a question regarding multiple nodes.  In Netdisco v1.3 I would list 
individual starting nodes under the CRON job. Netdisco2 looks different.  If I 
have two separate locations I want to use as starting points how does that 
work. Lets say IP: 1.1.1.1 and 2.2.2.2  

schedule:
  discoverall:
    when: '0 9 * * *'
  arpwalk:
    when:
      min: 30
  macwalk:
    when:
      min: 15
      hour: '*/2'
      wday: 'mon-fri'
  nbtwalk:
    when: '0 8,13,21 * * *'
  expire:
    when: '20 23 * * *'

Ken DeShong
Network Engineer
USF Health Information Systems
Desk: 813-396-9472
Fax: 813-974-5198 

   
Amazing Things Happen When You Connect the Unconnected

 
 
 



--- End Message ---
--- Begin Message ---
I finished my setup using the guide published by Oliver.  Everything went as 
planned (I think) and I can even discover my test switch but I can't launch the 
website on the server. I'm not really a linux admin so I'm just a sheep 
following the guides. Not much experience troubleshooting.

I've tried NetDisco and Netdisco2
http://localhost/netdisco2
http://127.0.0.1/netdisco2
http://10.119.xx.xx/netdisco2    (real IP of server)


on Netdisco 1.3 I can use all the above it works perfectly.


Ken DeShong
Network Engineer
USF Health Information Systems
Desk: 813-396-9472
Fax: 813-974-5198

[Health IS Email Logo (2)]



Amazing Things Happen When You Connect the Unconnected






--- End Message ---
------------------------------------------------------------------------------
Want fast and easy access to all the code in your enterprise? Index and
search up to 200,000 lines of code with a free copy of Black Duck
Code Sight - the same software that powers the world's largest code
search on Ohloh, the Black Duck Open Hub! Try it now.
http://p.sf.net/sfu/bds
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to