<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.network.nav.user">
    <title>gmane.network.nav.user</title>
    <link>http://blog.gmane.org/gmane.network.nav.user</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1143"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1141"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1139"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1138"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1134"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1128"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1124"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1113"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1110"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1109"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1106"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1105"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1100"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1098"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1095"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1092"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1085"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1084"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1082"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.network.nav.user/1081"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1143">
    <title>mod_python error and InterfaceError: connection already closed</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1143</link>
    <description>&lt;pre&gt;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 = _execut&lt;/pre&gt;</description>
    <dc:creator>Ted</dc:creator>
    <dc:date>2013-05-07T13:23:06</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1141">
    <title>Bruk av NAV og uheldige konsekvenser for Cisco-utstyr</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1141</link>
    <description>&lt;pre&gt;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 &amp;lt;164&amp;gt;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 &amp;lt;164&amp;gt;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 &amp;lt;164&amp;gt;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 &amp;lt;164&amp;gt;May 02 2013 11:27:18: %ASA-4-711004: Task ran for 152 msec, Process = snmp, PC = 8b77990, Call stack = &lt;/pre&gt;</description>
    <dc:creator>Inge Bjørnvall Arnesen</dc:creator>
    <dc:date>2013-05-02T12:42:03</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1139">
    <title>Announcement: NAV 3.14.1592 released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1139</link>
    <description>&lt;pre&gt;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
&lt;/pre&gt;</description>
    <dc:creator>Morten Brekkevold</dc:creator>
    <dc:date>2013-04-25T07:48:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1138">
    <title>Announcement: NAV 3.14.1592 released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1138</link>
    <description>&lt;pre&gt;NAV 3.14.159, another release of the endless NAV 3.14 series is now
available for download at Launchpad:
https://launchpad.net/nav/3.14/3.14.159

The release fixes the following reported issues:

  * LP#1155128 (IndexError crash in Machine Tracker)
  * LP#1158214 (mcc.py does debug logging even when configured not to)
  * LP#1160921 (Geomap won't load map data over HTTPS in Chrome)
  * LP#1161108 (Room bulk import format doesn't include geo position)
  * LP#1163256 (snmptrapd crashes with "interrupted system call" error)
  * LP#1164582 (netmap bails on fetching network graph if interface.speed
                missing)
  * LP#1165017 (Adding 0.0.0.0/0 as excepted range causes netbiostracker to
                hang)

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.


Some people have experienced that the Debian package upgrade seems to
freeze.&lt;/pre&gt;</description>
    <dc:creator>Morten Brekkevold</dc:creator>
    <dc:date>2013-04-25T07:43:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1134">
    <title>Announcement: NAV 3.14.159 released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1134</link>
    <description>&lt;pre&gt;NAV 3.14.159, another release of the endless NAV 3.14 series is now
available for download at Launchpad:
https://launchpad.net/nav/3.14/3.14.159

The release fixes the following reported issues:

  * LP#1155128 (IndexError crash in Machine Tracker)
  * LP#1158214 (mcc.py does debug logging even when configured not to)
  * LP#1160921 (Geomap won't load map data over HTTPS in Chrome)
  * LP#1161108 (Room bulk import format doesn't include geo position)
  * LP#1163256 (snmptrapd crashes with "interrupted system call" error)
  * LP#1164582 (netmap bails on fetching network graph if interface.speed
                missing)
  * LP#1165017 (Adding 0.0.0.0/0 as excepted range causes netbiostracker to
                hang)

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.


Some people have experienced that the Debian package upgrade seems to
freeze.&lt;/pre&gt;</description>
    <dc:creator>John-Magne Bredal</dc:creator>
    <dc:date>2013-04-11T07:28:20</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1128">
    <title>rsyslog, logger.conf and cisco devices</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1128</link>
    <description>&lt;pre&gt;I am running NAV ver. 3.14.15 (downloaded the virtual appliance and did an 
upgrade) but I am unable to get the syslog part to work (as well as cricket 
but that I am still researching) 

The original logger.conf points to /var/lib/nav/log/cisco.log - shouldn't that 
point to /var/log/nav? Anyway I changed that to point to /var/log/messages

I also had to enable in rsyslog.conf to receive UDP messages by uncommenting 
the lines $ModLoad imudp and $UDPServerRun 514.

When I do tail -f /var/log/messages I can see that the Cisco switches are 
sending messages. If I try to pull up the syslog messages through NAV however 
it tells me that there are no messages. 

Any pointers would be greatly appreciated. 


&lt;/pre&gt;</description>
    <dc:creator>Ted</dc:creator>
    <dc:date>2013-04-09T15:26:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1124">
    <title>Single device configurations</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1124</link>
    <description>&lt;pre&gt;Guys, is it possible to configure NAV to:

1 - ignore a single or a range of devices to be ignored from the polling
process? I think this will be possible when we put it in maintenance mode.
I'm right?

2 - apply per device ipdevpool's plugins intervals? According to docs, its
is possible to set intervals for all devices but I hope that exists some
other "hide" config to do that :)

&lt;/pre&gt;</description>
    <dc:creator>Bruno Galindro da Costa</dc:creator>
    <dc:date>2013-04-03T20:59:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1113">
    <title>Device Uplink</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1113</link>
    <description>&lt;pre&gt;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.

&lt;/pre&gt;</description>
    <dc:creator>Bruno Galindro da Costa</dc:creator>
    <dc:date>2013-03-27T14:00:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1110">
    <title>Unmanaged devices</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1110</link>
    <description>&lt;pre&gt;Hi!

    Question 1: Is it possible to change the device type? I know this
information is gathered from device, but when the device has no snmp
support, but only an ip address (like a printer), I need to specify it's
type in the system to built more detailed and consistent reports.

    Question 2: How can I insert an unmanaged switch or hub in NAV? I need
this because I want to know where this kind of devices are inserted in our
network to planning a future replacement of it.

    Question 3: Where I can change the netmap device icons? The device icon
is related to type or category? Would be great if it where possible to
change the device's icon to reflect it's model.
Hi!

&lt;/pre&gt;</description>
    <dc:creator>Bruno Galindro da Costa</dc:creator>
    <dc:date>2013-03-21T17:54:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1109">
    <title>Netmap - link colors</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1109</link>
    <description>&lt;pre&gt;Hi!

    Which is the premisse for netmap colorize the link between two devices?
What is the meaning of grey's link color?
    I'm wondering this because from yesterday to today, the links between
my devices changed from green to grey...

&lt;/pre&gt;</description>
    <dc:creator>Bruno Galindro da Costa</dc:creator>
    <dc:date>2013-03-21T17:37:41</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1106">
    <title>Announcement: NAV 3.14.15 released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1106</link>
    <description>&lt;pre&gt;NAV 3.14.15, the first maintenance release of the NAV 3.14 series is now
available for download at Launchpad:
https://launchpad.net/nav/3.14/3.14.15

The 3.14.15 fixes the following reported issues:

  * LP#1152173 (Deleting rrdviewer.conf causes crash when attempting to view
                graphs from ipdevinfo)
  * LP#1152599 (VLANs periodically lose one or more prefixes)
  * LP#1154626 (Threshold bulk config UI unresponsive, with javascript console
                error)
  * LP#1155096 (Filtering by category in syslog analyzer doesn't work)
  * LP#1156647 (Topology is not cleared when ports are shut down)
  * LP#1157154 (Netmap stopped working in NAV 3.14.1)
  * LP#1157594 (netbiostracker crashes when a netbios host reports an empty mac
                address)
  * LP#1157658 (Failing ipdevpoll plugin should be identified in log messages at
                the ERROR level)

Please report bugs at https://launchpad.net/nav/+filebug :-)


Binary packages for Debian will be made available as soon as possible&lt;/pre&gt;</description>
    <dc:creator>Morten Brekkevold</dc:creator>
    <dc:date>2013-03-21T09:19:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1105">
    <title>Netmap broken in 3.14.1</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1105</link>
    <description>&lt;pre&gt;Just updated the Debian package to from 3.13.1 to 3.14.1 and netmap 
appears to no longer work, just the spinning wheel.
Anyone else experiencing this? Haven't looked much further into it yet, 
but save myself some time if others have noticed the problem and have a 
solution.

Also, (again, I haven't had time to look closely at it yet) is there a 
way to configure the geomap to plot only physical layer-2 connections? 
It is plotting vl1 connections to root hub along with the physical 
connections.

Thanks for any assistance in advance, and I'll report if I find anything.

&lt;/pre&gt;</description>
    <dc:creator>Corey Thompson</dc:creator>
    <dc:date>2013-03-20T16:06:24</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1100">
    <title>Dlink DGS-3100 / DGS-3120 support</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1100</link>
    <description>&lt;pre&gt;Hi!

   Is Dlink DGS-3100 / DGS-3120 supported by NAV? If yes, why these errors
are ocurring with ipdevpoll module?

2013-03-19 19:52:09,257 [WARNING plugins.typeoid.typeoid] [inventory
10.10.25.110] Netbox has changed type from unknown to unknown (sysObjectID
1.3.6.1.4.1.171.10.94.3)
2013-03-19 19:52:30,376 [ERROR jobs.jobhandler] [inventory 10.10.25.110
Job 'inventory' for 10.10.25.110 aborted: ('Job aborted due to plugin
failure', TimeoutError('',))
2013-03-19 19:54:49,507 [ERROR jobs.jobhandler] [linkcheck 10.10.25.110]
Job 'linkcheck' for 10.10.25.110 aborted: ('Job aborted due to plugin
failure', TimeoutError('',))

   Is there a way to put ipdevpoll module in debug mode to see what is
happening with more details?

   The device is correctly configured with snmpv2c. See it:

# snmpwalk -v2c -c public 10.10.25.110 .1.3.6.1.2.1.2.2.1.2.40
iso.3.6.1.2.1.2.2.1.2.40 = STRING: "Ethernet Interface"

   That command was executed from the same VM that NAV is installed.


I have another two monitored devices: Dl&lt;/pre&gt;</description>
    <dc:creator>Bruno Galindro da Costa</dc:creator>
    <dc:date>2013-03-19T19:24:56</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1098">
    <title>Announcement: NAV 3.14.1 released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1098</link>
    <description>&lt;pre&gt;Just a week shy of Pi Day, we bring you a new NAV feature release: NAV
3.14.1 is now available for download at Launchpad:
https://launchpad.net/nav/3.14/3.14.1

The 3.14.1 release adds the following user-visible features and
improvements:

  * NAV now fully supports SNMP communication over IPv6. Please see the
    release notes for more information.

  * Most of the service monitor plugins now support IPv6.

  * NAV documentation is slowly moving out of the wiki and into Sphinx. Now,
    every NAV installation includes a link from the front page to the
    browseable, locally installed documentation.

  * The Toolbox can now be collapsed into an icon/title-based list if the tool
    descriptions aren't needed or wanted.

  * The ordering of tools in the Toolbox can now be customized individually by
    each user.

  * The status page and portadmin have been adapted to work well on small
    screens/mobile devices.

  * Portadmin now supports editing trunks. 

  * Portadmin includes a new feature to enable tr&lt;/pre&gt;</description>
    <dc:creator>Morten Brekkevold</dc:creator>
    <dc:date>2013-03-07T09:16:46</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1095">
    <title>maintengine.py has trouble with TypeError</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1095</link>
    <description>&lt;pre&gt;Sometime this last week our maintengine has stopped working:


/#/usr/local/nav/bin/maintengine.py
Traceback (most recent call last):
  File "/usr/local/nav/bin/maintengine.py", line 45, in &amp;lt;module&amp;gt;
    main()
  File "/usr/local/nav/bin/maintengine.py", line 39, in main
    check_devices_on_maintenance()
  File "/usr/local/nav/lib/python/nav/maintengine.py", line 479, in check_devices_on_maintenance
    send_event(events, maxdate_boxes, boxes_off_maintenance)
  File "/usr/local/nav/lib/python/nav/maintengine.py", line 343, in send_event
    str(curr_event['maint_end'])))
TypeError: not all arguments converted during string formatting


NAV 3.13.0

I guess something has gone wrong in the database. Where to look?


--Ingeborg
&lt;/pre&gt;</description>
    <dc:creator>Ingeborg Hellemo</dc:creator>
    <dc:date>2013-03-04T12:42:45</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1092">
    <title>Announcement: NAV 3.13.1 final released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1092</link>
    <description>&lt;pre&gt;The first maintenance release of NAV 3.13 is now available for download
at Launchpad: https://launchpad.net/nav/3.13/3.13.1

The 3.13.1 updates the release notes with some information about the
netbiostracker feature and the new alert message template system, and
fixes the following reported issues:

  * LP#1126340 (arnold t1000 crashes on pursuit)
  * LP#1126341 (arnold autoenable crashes on missing interface)
  * LP#1128868 (Arnold does not display a candidate for manual block)
  * LP#1130093 (NetworkX 1.6 throws exception in eventengine)
  * LP#1130103 (Typo in ReportListTemplate.tmpl)

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. Although he did not post a notice to this list,
the 3.13.0 packages have been available at pkg-nav.alioth.debian.org
since last week.

Happy NAVing, everyone!

&lt;/pre&gt;</description>
    <dc:creator>Morten Brekkevold</dc:creator>
    <dc:date>2013-02-21T11:40:42</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1085">
    <title>Warning from eventengine - topology problem</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1085</link>
    <description>&lt;pre&gt;NAV 3.13.0

Eventengine logs a lot of topology problems of two kinds. 

One regarding the NAV-server itself:

2013-02-18 11:23:37,173 [WARNING nav.eventengine.topology] 
NAVServer('129.242.5.182') topology problem: router ma-gsw3.infra is up, but 
not in VLAN graph for &amp;lt;Prefix: 129.242.5.0/24 (vlan 103 (nett,srv,5-nettet))&amp;gt;. 
Defaulting to 'reachable' status.

The other kind regarding some (but not all) random devices: 

2013-02-18 11:23:37,740 [WARNING nav.eventengine.topology] nfh-b100-nc.prn 
topology problem: router nfh-gsw.infra is up, but not in VLAN graph for 
&amp;lt;Prefix: 10.253.19.0/24 (vlan 600 (uit,prn))&amp;gt;. Defaulting to 'reachable' 
status.


Is there anything we can do to in our setup to eliminate the warnings (except 
changing the debug level...)?


--Ingeborg
&lt;/pre&gt;</description>
    <dc:creator>Ingeborg Hellemo</dc:creator>
    <dc:date>2013-02-18T10:31:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1084">
    <title>NetworkXNoPath: No path between server and router</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1084</link>
    <description>&lt;pre&gt;We are running NAV 3.13.0 since 08.02.13

Some days ago something happened in our environment that caused eventengine to 
throw an error:

2013-02-13 17:08:57,887 [ERROR nav.eventengine.engine] Unhandled exception in 
plugin &amp;lt;nav.eventengine.plugins.boxstate.BoxStateHandler object at 0x804e170d0&amp;gt;
; ignoring it
Traceback (most recent call last):
  File "/usr/local/nav/lib/python/nav/eventengine/engine.py", line 190, in 
handle_event
    handler.handle()
  File "/usr/local/nav/lib/python/nav/eventengine/plugins/delayedstate.py", 
line 52, in handle
    return self._handle_start()
  File "/usr/local/nav/lib/python/nav/eventengine/plugins/delayedstate.py", 
line 68, in _handle_start
    self._set_internal_state_down()
  File "/usr/local/nav/lib/python/nav/eventengine/plugins/boxstate.py", line 
29, in _set_internal_state_down
    shadow = self._verify_shadow()
  File "/usr/local/nav/lib/python/nav/eventengine/plugins/delayedstate.py", 
line 189, in _verify_shadow
    netbox.up = (Netbox.UP_DOWN if netbox_appears&lt;/pre&gt;</description>
    <dc:creator>Ingeborg Hellemo</dc:creator>
    <dc:date>2013-02-18T10:24:48</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1082">
    <title>Announcement: NAV 3.13.0 final released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1082</link>
    <description>&lt;pre&gt;The final stable release of NAV 3.13.0 is now available for download at
Launchpad: https://launchpad.net/nav/3.13/3.13.0

In addition to the features and bugfixes in the two beta releases, the
3.13.0 release fixes the following reported issues:

  * LP#1092848 (logengine regression: crash on various non-Cisco syslog entries)
  * LP#1102831 (machine tracker ip sort does not work)
  * LP#1104025 (vlan view needs a search page)
  * LP#1104027 (vlan view does not draw a vlan graph if there are no ipv4
                prefixes)
  * LP#1107723 (collect_active_ip crashes when prefix ids has been changed)
  * LP#1108647 (navbar search should search for vlan net types)
  * LP#1108702 (Unused prefixes are never deleted)
  * LP#1108880 (Physical port view annotates all non-switching ports as layer 3
                ports)
  * LP#1110368 (Messages UI crashes when entering non-ASCII characters in forms)
  * LP#1115013 (Modules with status down don't show up in 'Delete modules' page)
  * LP#1115109 (Machine tracker switch&lt;/pre&gt;</description>
    <dc:creator>Morten Brekkevold</dc:creator>
    <dc:date>2013-02-07T13:05:37</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1081">
    <title>Announcement: NAV 3.13.0 final released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1081</link>
    <description>&lt;pre&gt;A beta version of the next NAV feature release, version 3.13.0b1, is now
available for download at Launchpad: https://launchpad.net/nav/3.13/3.13.0b1

The 3.13.0b1 release adds the following user-visible features and
improvements:

  * The eventEngine has been rewritten to Python. This was the last remaining
    Java component of NAV, meaning Java is no longer needed for installing and
    running NAV.

  * VLANs are now searchable from the Navbar.

  * IPv4, IPv6 and MAC host counts for each VLAN is now graphed over time.

  * NAV is now able to detect and graph data from sensors on Cisco Nexus
    devices.

  * Maintenance tasks can now be configured to end automatically when all
    components involved in the task are up.

  * IP Devices that are down can be placed on immediate maintenance until up
    again directly from the status page.

  * Subscriptions to MAC address prefixes are now possible in Macwatch. Use
    with caution!

And contains fixes for these reported issues:

  * LP#305435  (Sort by "S&lt;/pre&gt;</description>
    <dc:creator>Morten Brekkevold</dc:creator>
    <dc:date>2012-12-14T12:31:10</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.network.nav.user/1080">
    <title>Announcement: NAV 3.13.0b2 released</title>
    <link>http://comments.gmane.org/gmane.network.nav.user/1080</link>
    <description>&lt;pre&gt;A second beta version of the next NAV feature release, version 3.13.0b2,
is now available for download at Launchpad:
https://launchpad.net/nav/3.13/3.13.0b2

The 3.13.0b2 fixes the following reported issues since b1:

  * LP#309705  (Add RSS feed for messages)
  * LP#735521  (Tracking machines behind a port where the name has changed
                fails)
  * LP#1014513 (Ajax calls need to handle session timeout)
  * LP#1062136 (linkState events should be sent only for redundant links)
  * LP#1062197 (ipdevinfo DNS table should be on a separate tab)
  * LP#1062200 (ipdevinfo needs a port view tab for physical ports)
  * LP#1083511 (MachineTracker form data is reset on result page)
  * LP#1092154 (Portadmin crash when unicode characters in ifalias)
  * LP#1092156 (Portadmin crash when it cannot find a netbox by name or ip,- and
                interface by id)
  * LP#1092848 (logengine regression: crash on various non-Cisco syslog entries)
  * LP#1099321 (cricket frontpage displays !short-desc!)
  * LP#10993&lt;/pre&gt;</description>
    <dc:creator>Morten Brekkevold</dc:creator>
    <dc:date>2013-01-25T13:01:54</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.network.nav.user">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.network.nav.user</link>
  </textinput>
</rdf:RDF>
