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: Cisco UCS Fabric Interconnect macsuck failure (inetjunkmail)
   2. Question about multiple nodes per port report (Sebastian R?sch)
   3. Re: Question about multiple nodes per port report (Steven Xu)
   4. Re: Question about multiple nodes per port report
      (Sebastian R?sch)
--- Begin Message ---
We confirmed that our "last seen" matches the date the UCS infrastructure
was upgraded from 2.1 to 2.2 which I guess includes upgrading the NX-OS on
the Fabric Interconnects.  I suppose the new code responds differently.

On Mon, Nov 30, 2015 at 2:56 PM, inetjunkmail <[email protected]>
wrote:

> We're trying to macsuck a pair of Cisco UCS 6200 Fabric Interconnects and
> getting some errors.   For each MAC the debug output contains the following
> error:
>
> [14565] 2015-11-30 18:57:38 debug  [172.26.126.6] macsuck
> 00:20:26:a1:36:f7 - port 0 has no bp_index mapping - skipping
>
>
> We never paid much attention to these in the past but we do have some MAC
> to port mappings from a few months ago so it may have broken as a result of
> a code upgrade on our devices.
>
>
> SNMP::Info::device_type() layers:01000110 id:9 sysDescr:"Cisco NX-OS(tm)
> ucs, Software (ucs-6100-k9-system), Version 5.2(3)N2(2.26c), RELEASE
> SOFTWARE Copyright (c) 2002-2013 by Cisco Systems, Inc.   Compiled
> 10/6/2015 14:00:00"
>
>
> We upgraded Netdisco today to see it tha would help but it had no efect.
>
> SoftwareVersion*App::Netdisco <http://netdisco.org/>*2.033004DB Schema
> <https://metacpan.org/module/netdisco-db-deploy>v40Dancer
> <http://http//perldancer.org/>1.3202Bootstrap <http://getbootstrap.com/>
> 2.3.1PostgreSQL <http://www.postgresql.org/>PostgreSQL 9.2.14 on
> x86_64-redhat-linux-gnu, compiled by gcc (GCC) 4.8.3 20140911 (Red Hat
> 4.8.3-9), 64-bit.
>  DBI 1.631, DBD::Pg 2.19.3SNMP::Info <http://snmp-info.sourceforge.net/>
> 3.30Perl <http://www.perl.org/>5.016003
>
>
>
> Can you provide any guidance on diagnosing the issue?
>
>
>
>
>

--- End Message ---
--- Begin Message ---
Hi all,

can somebody tell me how the "multiple nodes per port report" works? For me it 
seems, that it shows current connected nodes and also nodes that has been seen 
some time ago (Where is this timerange defined, can I control it?) But for this 
report, wouldn´t it be better, if it only shows the nodes, that were fetched 
with the last macsuck? This is a very good function for finding 
pocketswitches/non managed switches, but it would be good, if it would show the 
exact count of nodes on a port.



Regards,

Sebastian

--- End Message ---
--- Begin Message --- Hi Sebastian,

This report counts all "active" nodes. Depending on how you configured netdisco (particularly, the node_freshness option), nodes are active for a certain period according to node_freshness. If it's set to 0, nodes are active forever until they change switch port; then the results you get in this report won't be very reliable.

If you set node_freshness to 60 minutes, then the nodes that appear in this report are the ones that the nodes that were seen in the last 60 minutes. However, if you're changing it, you'll need to note that it may affect how your users see results elsewhere in Netdisco.

Currently, this report is not set up to take time ranges. You'd need to hack one up.

Steven

-----Sebastian Rösch <[email protected]> wrote: -----
To: "[email protected]" <[email protected]>
From: Sebastian Rösch <[email protected]>
Date: 12/01/2015 11:06AM
Subject: [Netdisco] Question about multiple nodes per port report

Hi all,

 

can somebody tell me how the “multiple nodes per port report” works? For me it seems, that it shows current connected nodes and also nodes that has been seen some time ago (Where is this timerange defined, can I control it?) But for this report, wouldn´t it be better, if it only shows the nodes, that were fetched with the last macsuck? This is a very good function for finding pocketswitches/non managed switches, but it would be good, if it would show the exact count of nodes on a port.

 

 

 

Regards,

 

Sebastian

------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Netdisco mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

--- End Message ---
--- Begin Message ---
Thanks for your quick feedback Steven,

I will try now to use another node_freshness value. But as you said, I will 
tell my colleagues to keep in mind the archive option when searching....


Best Regards

Sebastian

Von: Steven Xu [mailto:[email protected]]
Gesendet: Dienstag, 1. Dezember 2015 17:33
An: Sebastian Rösch <[email protected]>
Cc: [email protected]
Betreff: Re: [Netdisco] Question about multiple nodes per port report

Hi Sebastian,

This report counts all "active" nodes. Depending on how you configured netdisco 
(particularly, the node_freshness option), nodes are active for a certain 
period according to node_freshness. If it's set to 0, nodes are active forever 
until they change switch port; then the results you get in this report won't be 
very reliable.

If you set node_freshness to 60 minutes, then the nodes that appear in this 
report are the ones that the nodes that were seen in the last 60 minutes. 
However, if you're changing it, you'll need to note that it may affect how your 
users see results elsewhere in Netdisco.

Currently, this report is not set up to take time ranges. You'd need to hack 
one up.

Steven

-----Sebastian Rösch <[email protected]<mailto:[email protected]>> wrote: -----
To: 
"[email protected]<mailto:[email protected]>"
 
<[email protected]<mailto:[email protected]>>
From: Sebastian Rösch <[email protected]<mailto:[email protected]>>
Date: 12/01/2015 11:06AM
Subject: [Netdisco] Question about multiple nodes per port report
Hi all,

can somebody tell me how the "multiple nodes per port report" works? For me it 
seems, that it shows current connected nodes and also nodes that has been seen 
some time ago (Where is this timerange defined, can I control it?) But for this 
report, wouldn´t it be better, if it only shows the nodes, that were fetched 
with the last macsuck? This is a very good function for finding 
pocketswitches/non managed switches, but it would be good, if it would show the 
exact count of nodes on a port.



Regards,

Sebastian
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Netdisco mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/netdisco-users

--- End Message ---
------------------------------------------------------------------------------
Go from Idea to Many App Stores Faster with Intel(R) XDK
Give your users amazing mobile app experiences with Intel(R) XDK.
Use one codebase in this all-in-one HTML5 development environment.
Design, debug & build mobile apps & 2D/3D high-impact games for multiple OSs.
http://pubads.g.doubleclick.net/gampad/clk?id=254741911&iu=/4140
_______________________________________________
Netdisco mailing list - Digest Mode
[email protected]
https://lists.sourceforge.net/lists/listinfo/netdisco-users

Reply via email to