John Magne Bredal | 15 Dec 11:21 2014
Picon
Picon

Re: Cisco IOS 3.6.x / VTP

Hi again!

On 08. des. 2014 21:25, Ken Tobias wrote:
> Thanks. Appreciated.
>
>
>     We are very interested in the OIDs you found. One problem we have
at the
>     moment is that we have no way of testing this in an exact matter as we
>     have no 3850.
>
>     I have asked around some and am expecting some feedback shortly. I
will
>     let you know what we discover.
>

Just to give you some feedback here - we didn't get any information from
any sources that explained the behaviour you were experiencing. It
seemed like a software update was the initiator of the problem and
without access to the specific device type (Cisco 3850) and software we
are running blind.

Another troubling trend is that later versions of Cisco software has
stopped supporting SNMP for configuring devices and now requires NETCONF
for such tasks. Thus we have as a task next year to implement NETCONF
support in NAV so that we are still able to use the tools that configure
devices.

PortAdmin is a popular tool, and we definitely plan to support it. It
seems that there are a lot of changes going on now in especially Cisco
(Continue reading)

John Magne Bredal | 8 Dec 12:05 2014
Picon
Picon

Re: Cisco IOS 3.6.x / VTP

On 05. des. 2014 17:24, Ken Tobias wrote:
> It is true that the startup config is the non-volatile version of
> the config that will be loaded after a reboot or power fail. However
> all changes are first stored in volatile storage in the running
> config. A write mem copies the running config to the startup config.
> If the change isn't in the running config before a write mem, it's
> not going to be in the startup config after a write mem. This is why
> I brought it up.

Agree.

> If the setting of the values was successful but the write mem was 
> not, it should show up in the running config but not the startup 
> config. This implies that the values were never effectively set in 
> the running config. I've read about dynamic VLANs that are set at run
> time based on policy. They don't show up in the running config or
> startup config to the best of my knowledge. That is the only scenario
> I can think of that would result in a port being added to the vlan
> tables but not the config file.

That is interesting.

> If we are using the "old Cisco MIB", maybe Cisco changed the default
> function of that OID to map to dynamic VLAN changes instead of
> static. Are there more current OIDs that let you choose which type of
> setting is preferred? Just a guess as this is not my specialty. I did
> a little looking around in the MIB and there are indeed other/newer
> OIDs for this, but I couldn't get them to work properly with snmpget
> and snmpset.
> 
(Continue reading)

Corey Thompson | 1 May 17:44 2014
Picon

Integration with GIS

Before I start doing such, I'm wondering if anyone has done any 
integration between NAV and a PostGIS based GIS system (mostly using 
QGIS for "frontend"), as I would rather add to existing work rather than 
repeating it...I thinking of just creating views in postgres referencing 
NAV data for the GIS to use to retrieve device inventory, status, and 
statistics in spatial queries. If it becomes successful and useful, I 
will do a writeup.

  --
Corey Thompson
Technology Manager
East Grand Forks Water and Light
1010 5th Avenue Northeast
East Grand Forks, Minnesota 56721
218-399-3310 direct
cthompson@...

Joachim Tingvold | 27 Apr 05:50 2014

Setting up NAV from scratch/non-OVA (Graphite-issues)

Hi,

Decided to install NAV from 'scratch' (i.e. not use the OVA-package). Got NAV running fine, but had some
hiccups getting Graphite working as it should. Found no documentation on this what-so-ever (neither on
the NAV-pages, or the Graphite-pages), so had to try-and-fail some. Thought I'd share.

 - Debian Wheezy (not OVA)
 - NAV via apt (from https://nav.uninett.no/debian)
      root <at> tardis:~# dpkg -s nav|grep Vers
      Version: 4.0.1-3

1) Fixed /etc/nav/graphite.conf;
	base=http://localhost:8888/

2) Copied content of '/usr/share/graphite-web/apache2-graphite.conf' into own VHost;
	<VirtualHost localhost:8888>
	( + add NameVirtualHost + Listen in /etc/apache2/ports.conf)

3) Set 'CARBON_CACHE_ENABLED=true' in '/etc/default/graphite-carbon'
   Set 'ENABLE_UDP_LISTENER = True' in '/etc/carbon/carbon.conf'
   Set 'SECRET_KEY = <longsecretstring>' in '/etc/graphite/local_settings.py'
   Set 'TIME_ZONE = '<Gallifrey>' in '/etc/graphite/local_settings.py'

4) cd /usr/share/pyshared/graphite
   python manage.py syncdb

5) Started carbon-cache (/etc/init.d/carbon-cache start)

6) Started NAV + apache

(Continue reading)

Joachim Tingvold | 27 Apr 16:56 2014

Setting up NAV from scratch/non-OVA (Graphite-issues)

Hi,

Decided to install NAV from 'scratch' (i.e. not use the OVA-package). 
Got NAV running fine, but had some hiccups getting Graphite working as 
it should. Found no documentation on this what-so-ever (neither on the 
NAV-pages, or the Graphite-pages), so had to try-and-fail some. Thought 
I'd share.

  - Debian Wheezy (not OVA)
  - NAV via apt (from https://nav.uninett.no/debian)
       root <at> tardis:~# dpkg -s nav|grep Vers
       Version: 4.0.1-3

1) Fixed /etc/nav/graphite.conf;
	base=http://localhost:8888/

2) Copied content of '/usr/share/graphite-web/apache2-graphite.conf' 
into own VHost;
	<VirtualHost localhost:8888>
	( + add NameVirtualHost + Listen in /etc/apache2/ports.conf)

3) Set 'CARBON_CACHE_ENABLED=true' in '/etc/default/graphite-carbon'
    Set 'ENABLE_UDP_LISTENER = True' in '/etc/carbon/carbon.conf'
    Set 'SECRET_KEY = <longsecretstring>' in 
'/etc/graphite/local_settings.py'
    Set 'TIME_ZONE = '<Gallifrey>' in '/etc/graphite/local_settings.py'

4) cd /usr/share/pyshared/graphite
    python manage.py syncdb

(Continue reading)

davide | 22 Apr 18:36 2014

Is there a way to change the default 10 rows in the lists?

It should be useful if I can change the default 10 rows in the

"Show xx entries"

in the lists.

I searched through the configuration file and in the .js but I can't change
this.

I wish to put 50 rows or at least "all".

Thank you

Morten Brekkevold | 22 Apr 15:22 2014
Picon
Picon

Re: Manually adjust topology - [interface] table changes

On Sat, 19 Apr 2014 14:57:32 +0200 (CEST) <davide@...> wrote:

> I read https://nav.uninett.no/doc/3.15/howto/debugging-topology.html but I
> can't resolve the error in topology discovering on my network.
>
> I have some Catalyst 3550 with stackable modules that automaticaly are not
> correclty connected.
>
> I changed the [interface] table to adjust my topology and all is okay but my
> changes are lost from automatic discover.
>
> How can I permanently change the [interface] table?

You can't. All information in the interface table consists of
collected/detected information. Any changes made outside of NAV will
only be temporary.

If you would post details of your actual topology, where NAV is
mistaken, and add the details collected as described in [1], we may be
able to make a more qualified comment as to what may be happening. Feel
free to replace device names and text you would rather not divulge, as
long as you do it consistently.

[1] https://nav.uninett.no/doc/4.0/howto/debugging-topology.html#looking-for-the-missing-link

--

-- 
Morten Brekkevold
UNINETT

(Continue reading)

Morten Brekkevold | 22 Apr 12:36 2014
Picon
Picon

Re: Nav 4.0.1 trouble with nav pping service

On Mon, 14 Apr 2014 09:48:02 +0200 (CEST) Jostein Berge
<jostein.berge@...> wrote:

> Having some trouble starting pping after upgradring from 3.15 
> Running on 
> pping.log produces the following error : 
[snip]
> File "/usr/lib/python2.7/dist-packages/nav/metrics/carbon.py", line 57, in send_metrics_to 
> carbon.send(packet) 
> socket.error: [Errno 111] Connection refused 
>
>
> Anyone have solution for this ? 

Yes, this likely means the Carbon backend is not running, so NAV cannot
send its metrics to it. Please start the carbon-cache backend.

--

-- 
Morten Brekkevold
UNINETT

John-Magne Bredal | 22 Apr 09:38 2014
Picon
Picon

Re: Shutdown a port

Hi!

On 04/16/2014 01:39 PM, davide@... wrote:
> NAV 4
> 
> I can change port description or vlan in "Configure port".
> 
> How can I change the port administrative status?
> 

It is not possible to change the administrative status of the interface from
PortAdmin. The reason for this is that it simply has not been requested from the
NAV users.

The tool used for setting the interface administrative status is Arnold. The use
case for Arnold is that you have a mac- or ip-address that you want to shut out
from your network, so you search for that in Arnold and set the administrative
status of the resulting interface.

However, if you wish to manually set administrative statuses from PortAdmin,
that is something we can implement. Please register a bug for this on
https://bugs.launchpad.net/nav/+filebug and we will handle it.

regards

--

-- 
John-Magne Bredal
UNINETT AS

(Continue reading)

Morten Brekkevold | 22 Apr 13:04 2014
Picon
Picon

Re: Problem with uplink detecion

On Thu, 10 Apr 2014 12:00:24 +0000 "martin.jaburek@..."
<martin.jaburek@...> wrote:

> I can understand, that it is trying to determine the topology based on
> vlans. 
>
> How do you handle the situation when we have many vlans with different STP
> roots? Or some uplinks are limited to a subset of available vlans. 

NAV will traverse the path of each VLAN individually, starting at the
determined root router port for that VLAN. NAV does not get root
information from STP, but has detected which subnet prefix(es) are
routed on that VLAN, and uses this to detect the root router port. 

On the device connected to that router port (or on the same device, in
the case of an L3 switch), NAV will descend further on all trunks with
the current VLAN allowed, and non-trunks having this as their native
VLAN.

STP information is only used to find STP blocked ports. STP blocked
ports will not be traversed by the detector, only registered as blocked
on the VLAN that is being detected.

> Or if we have different allowed vlans from one side and the other
> side?

You mean a mismatch in the list of allowed vlans on each side of a
trunk? That would be logged as an error.

> I attached navtopology.log. I reduced it to include only three devices
(Continue reading)

Mischa Diehm | 31 Mar 12:28 2014
Picon
Picon

NAV mac-search with Nexus and FabricPath

Hi,

we have FP activated in our datacenter and use Cisco Nexus (5,6,7)k. I'm not sure what caused the problem but NAV can't find MAC-addresses on these devices and even on catalysts behind them anymore. I don't know what algorithm is used to figure out where a MAC-address is attached but maybe someone who knows can clarify what is needed for that to work?

Thanks in advance,
Mischa


-- 
Mischa Diehm | Network Operations Center (NOC)
UniBasel | UniRechenZentrum (URZ)
Klingebergstr. 70 | CH-4056 Basel
Tel. +41 61 267 1574 | http://urz.unibas.ch
Attachment (smime.p7s): application/pkcs7-signature, 2977 bytes

Gmane