May 2013 - Nav-users - lister.unit.no

Device Uplink
by Bruno Galindro da Costa 01 Aug '13

01 Aug '13

What is the process that discover device's uplink? Is /usr/local/nav/bin/navtopology? Is it possible to put it's execution in debug mode? I've some devices that not have uplink information after added. Whitout this information, netmap can't draw it. -- Att. Bruno Galindro da Costa

3 20

NAV dashboard teaser
by John-Magne Bredal 01 Jul '13

01 Jul '13

Hi NAV'ers! In an effort to break the silence on this mailing-list I decided to post a teaser of what we're working with regarding new layout and user friendlyness. The attached image shows the last iteration of the front page. The plan is to make it customizable for the individual user by provinding a set of "Navlets" or widgets that show updated information and provide shortcuts to NAV's tools. A user can add, remove and reorder Navlets to create the dashboard he wants. Some of the Navlets are individually configured, for instance to display the graph or the status the user finds most interesting. A Navlet can be set to auto-update periodically so that the dashboard can be used on always on screens in network monitoring environments. This is a work in progress. Any input from you is appreciated! NB: The logo is a placeholder. Regards -- John-Magne Bredal UNINETT AS

3 4

Announcement: NAV 3.14.1592 released
by Morten Brekkevold 30 May '13

30 May '13

NAV 3.14.1592, another maintenance release of the endless NAV 3.14 series is now available for download at Launchpad: https://launchpad.net/nav/3.14/3.14.1592 This release changes some aspects of how Cricket is configured to collect traffic statistics, so we have added a couple of important upgrade notes: * The Cricket trees `switch-ports` and `router-interfaces` have been consolidated into a single `ports` tree, where all physical ports' traffic stats now also are collected. After running the usual `syncdb.py` command, you should run `mcc.py` once manually (as the navcron user) to ensure the Cricket config tree is updated right away. When everything is up and running again, you can optionally delete the `switch-ports` and `router-interfaces` directories from your `cricket-config` directory, as they are no longer used by NAV. * NAV now supplies its own `subtree-sets` configuration to Cricket. If you have made manual changes to your Cricket collection setup and/or this file, you may need to update your setup accordingly. This release fixes the following reported issues: * LP#1165193 (Prefix Matrix Doesn't Handle HSRP) * LP#1165206 (ARP Entries on HSRP Subnets are Double Counted) * LP#1169553 (Consolidate switch-ports, router-interfaces and physical port traffic statistics in Cricket) * LP#1169837 (servicemon debug logs no matter what the log level is set to) * LP#1169872 (VRRP/HSRP plugin is not enabled by default) * LP#1169986 (ipdevpoll spins in its tracks and doesn't reconnect on database connection loss) * LP#1170221 (Subnet matrix crashes with AttributeError when only one scope prefix is registered) * LP#1170291 (Mac search + DNS crashes with AttributeError in NAV 3.14.159) * LP#1170329 (eventengine dies on loss of database connection) * LP#1170374 (Alertengine dies on loss of database connection) * LP#1170634 (The SMS daemon dies when database connection is lost) * LP#1172204 (Device history crashes with NameError on invalid date input) Please report bugs at https://launchpad.net/nav/+filebug Binary packages for Debian will be made available as soon as possible. The Debian package is maintained by Morten Werner Forsbring, on commission from UNINETT. Happy NAVing everyone! -- Morten Brekkevold UNINETT AS

2 2

mod_python error and InterfaceError: connection already closed
by Ted 08 May '13

08 May '13

I've been running NAV (3.14.15 on Debian appliance) for a few weeks without any issues but recently I started getting errors when running the Layer 2 trace tool. I tried upgrading but I guess the package for Debian hasn't been released yet... Any suggestions would be appreciated. Thank you. The error message is below: MOD_PYTHON ERROR ProcessId: 1023 Interpreter: 'nav-appliance.uninett.no' ServerName: 'nav-appliance.uninett.no' DocumentRoot: '/usr/share/nav/htdocs' URI: '/l2trace/' Location: '/' Directory: None Filename: '/usr/share/nav/htdocs/l2trace' PathInfo: '/' Phase: 'PythonHandler' Handler: 'django.core.handlers.modpython' Traceback (most recent call last): File "/usr/lib/python2.6/dist-packages/mod_python/importer.py", line 1537, in HandlerDispatch default=default_handler, arg=req, silent=hlist.silent) File "/usr/lib/python2.6/dist-packages/mod_python/importer.py", line 1229, in _process_target result = _execute_target(config, req, object, arg) File "/usr/lib/python2.6/dist-packages/mod_python/importer.py", line 1128, in _execute_target result = object(arg) File "/usr/lib/pymodules/python2.6/django/core/handlers/modpython.py", line 228, in handler return ModPythonHandler()(req) File "/usr/lib/pymodules/python2.6/django/core/handlers/modpython.py", line 208, in __call__ signals.request_finished.send(sender=self.__class__) File "/usr/lib/pymodules/python2.6/django/dispatch/dispatcher.py", line 162, in send response = receiver(signal=self, sender=sender, **named) File "/usr/lib/pymodules/python2.6/django/db/__init__.py", line 84, in close_connection conn.close() File "/usr/lib/pymodules/python2.6/django/db/backends/__init__.py", line 70, in close self.connection.close() InterfaceError: connection already closed

2 1

Bruk av NAV og uheldige konsekvenser for Cisco-utstyr
by Inge Bjørnvall Arnesen 07 May '13

07 May '13

Hei, Takk for et glitrende program! Jeg har testkjørt dette hos oss i et halvårs tid, men sliter med et alvorlig og et mindre alvorlig problem: 1: Cisco ASA. Vi bruker denne serien ganske mye og i de fleste tilfeller fungerer NAV bra. Mot bokser som har 10-30 VLAN ser det ut til å gå som det skal. På bokser med mange VLAN (128+) får vi derimot en feil på SNMP-tasken hvert kvarter: 2013-05-02T11:27:18.100301+02:00 XXX <164>May 02 2013 11:27:18: %ASA-4-711004: Task ran for 150 msec, Process = snmp, PC = 8c4b7c8, Call stack = 2013-05-02T11:27:18.100301+02:00 XXX <164>May 02 2013 11:27:18: %ASA-4-711004: Task ran for 150 msec, Process = snmp, PC = 8c4b7c8, Call stack = 0x08B70783 0x08B50B1D 0x08B4F87C 0x08063B63 2013-05-02T11:27:18.100311+02:00 XXX <164>May 02 2013 11:27:18: %ASA-4-711004: Task ran for 152 msec, Process = snmp, PC = 8b77990, Call stack = 2013-05-02T11:27:18.100311+02:00 XXX <164>May 02 2013 11:27:18: %ASA-4-711004: Task ran for 152 msec, Process = snmp, PC = 8b77990, Call stack = 0x08B77990 0x08B76699 0x08B734A9 0x08B75F48 0x08B50E0E 0x08B4F87C 0x08063B63 2013-05-02T11:27:23.113341+02:00 XXX <164>May 02 2013 11:27:23: %ASA-4-711004: Task ran for 150 msec, Process = snmp, PC = 8b7772e, Call stack = 2013-05-02T11:27:23.113417+02:00 XXX <164>May 02 2013 11:27:23: %ASA-4-711004: Task ran for 150 msec, Process = snmp, PC = 8b7772e, Call stack = 0x08B7772E 0x08B7645B 0x08B734A9 0x08B75F48 0x08B50E0E 0x08B4F87C 0x08063B63 Melding ASA-4-711004 gir beskjed om at en task er et "CPU Hog", noe som kan få alvorlige konsekvenser tradisjonelle ASA-bokser (pre-SMP). Når dette skjer, vil nodene i ASA-klyngen oppleve pakketap og vil nodene vil kunne miste kontakten med hverandre både på inn og utsiden. Det siste ser ut til å være avhengig av den øvrige CPU-belastningen i øyeblikket. 2013-05-02T11:27:28.147580+02:00 XXX <161>May 02 2013 11:27:28: %ASA-1-105005: (Secondary) Lost Failover communications with mate on interface YYY 2013-05-02T11:27:28.147628+02:00 XXX <161>May 02 2013 11:27:28: %ASA-1-105008: (Secondary) Testing Interface YYY 2013-05-02T11:27:28.349692+02:00 XXX <161>May 02 2013 11:27:28: %ASA-1-105009: (Secondary) Testing on interface YYY Passed 2013-05-02T11:27:33.263707+02:00 XXX <161>May 02 2013 11:27:33: %ASA-1-105005: (Secondary) Lost Failover communications with mate on interface outside 2013-05-02T11:27:33.416249+02:00 XXX <161>May 02 2013 11:27:33: %ASA-1-105008: (Secondary) Testing Interface outside 2013-05-02T11:27:33.726430+02:00 XXX <161>May 02 2013 11:27:33: %ASA-1-105009: (Secondary) Testing on interface outside Passed Er dette et kjent problem? Mulig det er tilfeldig, men jeg fikk samme problem når jeg forsøkte noen SNMP bulk-transfers. 2: Cisco switcher. Her får vi en feilmelding fra samtlige switcher hvert kvarter. Meldingen er noe obskur: "2013-05-01T00:04:36.711253+02:00 ZZZ <132>266532: 147851: May 1 00:04:36.638 MEST: %BIT-4-OUTOFRANGE: bit 0 is not in the expected range of 1 to 4094" med hilsen, -- Inge Arnesen

2 1