Send Netdot-devel mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
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 Netdot-devel digest..."
Today's Topics:
1. [Netdot - Bug #1895] (New) Exported RANCID results in all
devices "down". ([email protected])
2. [Netdot - Bug #1896] (New) trailing whitespace in BIND zone
generation ([email protected])
3. [Netdot - Bug #1897] (New) Cannot get FWT from Cisco devices
properly when using SNMPv3 ([email protected])
----------------------------------------------------------------------
Message: 1
Date: Mon, 13 Jun 2016 15:23:45 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1895] (New) Exported RANCID
results in all devices "down".
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1895 has been reported by dbuechler-cablemo-com -.
----------------------------------------
Bug #1895: Exported RANCID results in all devices "down".
https://osl.uoregon.edu/redmine/issues/1895
Author: dbuechler-cablemo-com -
Status: New
Priority: Normal
Assignee:
Category:
Target version:
Resolution:
When exporting RANCID configs from netdot, RANCID believes all devices are
down. A Google search informed me that RANCID changed its database delimiter
from colon to semicolon in or around version 3.0.
Modifying Rancid.pm solved my problem, but perhaps a Site.conf variable would
be useful?
As requested, I'm including a diff.
Thank you for your time.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 2
Date: Tue, 14 Jun 2016 08:51:42 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1896] (New) trailing whitespace
in BIND zone generation
To: [email protected], [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1896 has been reported by Matt Zagrabelny.
----------------------------------------
Bug #1896: trailing whitespace in BIND zone generation
https://osl.uoregon.edu/redmine/issues/1896
Author: Matt Zagrabelny
Status: New
Priority: Normal
Assignee:
Category: DNS
Target version:
Resolution:
The first line of the generated BIND zone file contains a trailing space
character.
This patch removes that space.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
Message: 3
Date: Tue, 14 Jun 2016 09:08:48 -0700
From: [email protected]
Subject: [Netdot-devel] [Netdot - Bug #1897] (New) Cannot get FWT from
Cisco devices properly when using SNMPv3
To: [email protected]
Message-ID: <[email protected]>
Content-Type: text/plain; charset=utf-8
Issue #1897 has been reported by Carlos Vicente.
----------------------------------------
Bug #1897: Cannot get FWT from Cisco devices properly when using SNMPv3
https://osl.uoregon.edu/redmine/issues/1897
Author: Carlos Vicente
Status: New
Priority: High
Assignee:
Category:
Target version: 1.0.8
Resolution:
The "cisco community indexing" trick is not handled properly when using SNMPv3.
It appears that the solution is to use the "context" parameter in the SNMPv3
session to specify the VLAN.
--
You have received this notification because you have either subscribed to it,
or are involved in it.
To change your notification preferences, please click here:
http://osl.uoregon.edu/redmine/my/account
------------------------------
_______________________________________________
Netdot-devel mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-devel
End of Netdot-devel Digest, Vol 111, Issue 1
********************************************
