Send Netdot-users mailing list submissions to
[email protected]
To subscribe or unsubscribe via the World Wide Web, visit
https://osl.uoregon.edu/mailman/listinfo/netdot-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 Netdot-users digest..."
Today's Topics:
1. Topology issues (JoeSox)
2. Re: Topology issues (JoeSox)
3. Re: Topology issues (JoeSox)
4. Re: Database issues. (Carlos Vicente)
5. Foundry VRF and VLAN Issues (Tonack, Vasco)
----------------------------------------------------------------------
Message: 1
Date: Tue, 19 Aug 2014 15:03:15 -0700
From: JoeSox <[email protected]>
Subject: [Netdot-users] Topology issues
To: netdot-users <[email protected]>
Message-ID:
<CAAXNyuA3L6mpnC1+VJg7_sdY7Eo_1+=UYmHzvQX8EW-ezJ=b...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
using v.1.0.6....
Any reason why neighbors are not showing up on generated Topology (via
Reports or from device)
manually created "10.10.2.2.defaultdomain" added 50 interfaces and added
interface #44 to "seahqfi-a.defaultdomain [Ex1] " (#2) both show as
neighbors.
the seahqfi-a doesn't have an ip address associated with it; not sure if
that matters.
Also, Nothing shows up in "whole_network_no_vlans.png" and only the other
graph with vlans.
Any help would be appreciated. maybe I need to add to a vlan or something?
--
Later, Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140819/3a00c8ff/attachment-0001.html
------------------------------
Message: 2
Date: Tue, 19 Aug 2014 15:12:37 -0700
From: JoeSox <[email protected]>
Subject: Re: [Netdot-users] Topology issues
To: netdot-users <[email protected]>
Message-ID:
<caaxnyua8ue12zritdt0_97jooy3caj6qifblwaxybtse5ph...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
correction, when I drill into device (seahqfi-a for example) it shows the
connected neighbor 10.10.2.2 but the png via Reports doesn't display.
--
Later, Joe
On Tue, Aug 19, 2014 at 3:03 PM, JoeSox <[email protected]> wrote:
> using v.1.0.6....
> Any reason why neighbors are not showing up on generated Topology (via
> Reports or from device)
> manually created "10.10.2.2.defaultdomain" added 50 interfaces and added
> interface #44 to "seahqfi-a.defaultdomain [Ex1] " (#2) both show as
> neighbors.
> the seahqfi-a doesn't have an ip address associated with it; not sure if
> that matters.
>
> Also, Nothing shows up in "whole_network_no_vlans.png" and only the other
> graph with vlans.
> Any help would be appreciated. maybe I need to add to a vlan or something?
> --
> Later, Joe
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140819/2ca35f14/attachment-0001.html
------------------------------
Message: 3
Date: Wed, 20 Aug 2014 07:11:35 -0700
From: JoeSox <[email protected]>
Subject: Re: [Netdot-users] Topology issues
To: netdot-users <[email protected]>
Message-ID:
<caaxnyua_4_t68hdujturjzpiqinbp_rumnsx3-i_s+re6zt...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
It may have been a browser cache issue. I pressed refresh key and it
displayed what I was more expecting. :blush:
Thanks for the offline help!
--
Later, Joe
On Tue, Aug 19, 2014 at 3:12 PM, JoeSox <[email protected]> wrote:
> correction, when I drill into device (seahqfi-a for example) it shows the
> connected neighbor 10.10.2.2 but the png via Reports doesn't display.
>
> --
> Later, Joe
>
>
> On Tue, Aug 19, 2014 at 3:03 PM, JoeSox <[email protected]> wrote:
>
>> using v.1.0.6....
>> Any reason why neighbors are not showing up on generated Topology (via
>> Reports or from device)
>> manually created "10.10.2.2.defaultdomain" added 50 interfaces and added
>> interface #44 to "seahqfi-a.defaultdomain [Ex1] " (#2) both show as
>> neighbors.
>> the seahqfi-a doesn't have an ip address associated with it; not sure if
>> that matters.
>>
>> Also, Nothing shows up in "whole_network_no_vlans.png" and only the other
>> graph with vlans.
>> Any help would be appreciated. maybe I need to add to a vlan or something?
>> --
>> Later, Joe
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140820/dae20892/attachment-0001.html
------------------------------
Message: 4
Date: Wed, 20 Aug 2014 10:14:28 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Database issues.
To: "Michael T. Voity" <[email protected]>
Cc: "[email protected]" <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=windows-1252
Michael,
The rotate option in prune_db is supposed to re-create the fwtable and
fwtableentry for you. If that is not happening, that?s where your problem is.
Can you try running it in debug mode, and post back the results? Also, show
your list of tables before and after, etc. Any relevant info that can help
figure this out.
Best,
cv
On Aug 18, 2014, at 3:42 PM, Michael T. Voity <[email protected]> wrote:
> Every week when 'prune_db.pl' runs it deletes the 'fwtableentry' table
> when it goes to do a rotate. When this happens I can not search for
> mac address.
>
> To recreate the table I do:
------------------------------
Message: 5
Date: Wed, 20 Aug 2014 16:33:01 +0200
From: "Tonack, Vasco" <[email protected]>
Subject: [Netdot-users] Foundry VRF and VLAN Issues
To: "[email protected]" <[email protected]>
Message-ID:
<f474652c2d01b8448fc6bfa8f8e9003c2afe5...@ex01a.campus.fu-berlin.de>
Content-Type: text/plain; charset="iso-8859-1"
Hello Guys,
I freshly installed netdot 1.0.6 on a debian server. One of my major
Problems is the Discovery of Foundry NetIron MLX Devices. When discovering a
foundry mlx device via snmp (also tried to disable the arp discovery through
cli) I ran into the issue that neither vlans nor vrf ARP Entries are
discovered. Another problem is the hardcoded vrf information in the cli
discovery script for foundry devices. If I understood the source code
correctly the idea is to hardcode the vrf names directly into the script.
We also have netdisco running which also uses snmp::info for discovering
devices. Netdisco is able to discover vrf, vlans, mac-addresses and more via
snmp without the workaround of a cli-script. So the main question is: Can
netdot discover foundry devices the same way netdisco does?
Kind regards,
Vasco Tonack
ZEDAT - Zentraleinrichtung f?r Datenverarbeitung
Unit NC - Network and Communication
Fabeckstr. 32, 14195 Berlin, Deutschland
Phone: +49-30-838-55121
Fax: +49-30-838-455121
Email: <mailto:[email protected]> [email protected]
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140820/4fcabda7/attachment.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 6349 bytes
Desc: not available
Url :
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140820/4fcabda7/attachment.gif
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6179 bytes
Desc: not available
Url :
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20140820/4fcabda7/attachment.bin
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 69, Issue 4
*******************************************
