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. Running Under Apache Httpd 2.4? (Jeffrey Ollie)
2. Re: Running Under Apache Httpd 2.4? (Carlos Vicente)
3. Juniper EX-Series and lldp detection (Andreas Abele)
4. Re: Juniper EX-Series and lldp detection (Begley, John)
5. Re: Juniper EX-Series and lldp detection (Andreas Abele)
----------------------------------------------------------------------
Message: 1
Date: Tue, 11 Jun 2013 14:22:46 -0500
From: Jeffrey Ollie <[email protected]>
Subject: [Netdot-users] Running Under Apache Httpd 2.4?
To: netdot-users <[email protected]>
Message-ID:
<cad-dqxt4m-rehmnfocze7oxrgf1fefdkakd3tddchq+nkah...@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"
Anyone got any tips on running Netdot (master) under Httpd 2.4?
--
Jeff Ollie
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://osl.uoregon.edu/pipermail/netdot-users/attachments/20130611/5d9b5fab/attachment-0001.html
------------------------------
Message: 2
Date: Tue, 11 Jun 2013 15:47:53 -0400
From: Carlos Vicente <[email protected]>
Subject: Re: [Netdot-users] Running Under Apache Httpd 2.4?
To: Jeffrey Ollie <[email protected]>
Cc: netdot-users <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1
Hi Jeff,
Not me, but I'm curious what kind of problem you are having.
cv
On 6/11/13 3:22 PM, Jeffrey Ollie wrote:
> Anyone got any tips on running Netdot (master) under Httpd 2.4?
>
> --
> Jeff Ollie
>
>
>
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
------------------------------
Message: 3
Date: Wed, 12 Jun 2013 08:52:39 +0200
From: Andreas Abele <[email protected]>
Subject: [Netdot-users] Juniper EX-Series and lldp detection
To: netdot-users <[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-15; format=flowed
any one got an idea if it is possible to detect lldp neighborships with
Juniper Ex-Series switches/routers?
kind regards
Andreas Abele
--
--
Andreas Abele, ZIS
Nobelstr. 12
70569 Stuttgart
Email: [email protected]
Phone: +49 711 970 4703
--
--
Andreas Abele, ZIS
Nobelstr. 12
70569 Stuttgart
Email: [email protected]
Phone: +49 711 970 4703
------------------------------
Message: 4
Date: Wed, 12 Jun 2013 09:05:25 -0400
From: "Begley, John" <[email protected]>
Subject: Re: [Netdot-users] Juniper EX-Series and lldp detection
To: Andreas Abele <[email protected]>, netdot-users
<[email protected]>
Message-ID:
<6c953c96234b844aba2fd8183bdac2a2080056c...@prvpexvs06.corp.twcable.com>
Content-Type: text/plain; charset="us-ascii"
It works for me, when supported and enabled.
JB
> -----Original Message-----
> From: [email protected] [mailto:netdot-users-
> [email protected]] On Behalf Of Andreas Abele
> Sent: Wednesday, June 12, 2013 2:53 AM
> To: netdot-users
> Subject: [Netdot-users] Juniper EX-Series and lldp detection
>
> any one got an idea if it is possible to detect lldp neighborships with
> Juniper
> Ex-Series switches/routers?
>
> kind regards
> Andreas Abele
>
> --
> --
> Andreas Abele, ZIS
> Nobelstr. 12
> 70569 Stuttgart
> Email: [email protected]
> Phone: +49 711 970 4703
>
>
> --
> --
> Andreas Abele, ZIS
> Nobelstr. 12
> 70569 Stuttgart
> Email: [email protected]
> Phone: +49 711 970 4703
> _______________________________________________
> Netdot-users mailing list
> [email protected]
> https://osl.uoregon.edu/mailman/listinfo/netdot-users
This E-mail and any of its attachments may contain Time Warner Cable
proprietary information, which is privileged, confidential, or subject to
copyright belonging to Time Warner Cable. This E-mail is intended solely for
the use of the individual or entity to which it is addressed. If you are not
the intended recipient of this E-mail, you are hereby notified that any
dissemination, distribution, copying, or action taken in relation to the
contents of and attachments to this E-mail is strictly prohibited and may be
unlawful. If you have received this E-mail in error, please notify the sender
immediately and permanently delete the original and any copy of this E-mail and
any printout.
------------------------------
Message: 5
Date: Wed, 12 Jun 2013 17:14:37 +0200
From: Andreas Abele <[email protected]>
Subject: Re: [Netdot-users] Juniper EX-Series and lldp detection
To: "Begley, John" <[email protected]>, netdot-users
<[email protected]>
Message-ID: <[email protected]>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Hi John,
I did download the actual VM from the website and started it. Netdot
Version is 1.0.4.
My "Site.conf" looks as follows (for Topology discovery)
> #####################################################################
> # Topology Discovery
> #####################################################################
> # Enable or disable particular sources of topology information
> # Assign a reliability score to each source
>
> # Use Discovery Protocols (CDP, LLDP)
> TOPO_USE_DP => 1,
> TOPO_WEIGHT_DP => 8,
>
> # Use Spanning Tree Protocol
> TOPO_USE_STP => 0,
> TOPO_WEIGHT_STP => 9,
>
> # Use Forwarding Databases (forwarding tables)
> TOPO_USE_FDB => 0,
> TOPO_WEIGHT_FDB => 6,
updatedevices.pl -T -d gives me:
> root@netdot:/usr/local/netdot/bin#
> /usr/local/netdot/bin/updatedevices.pl -T -d
> INFO - /usr/local/netdot/bin/updatedevices.pl started at Wed Jun 12
> 15:06:37 2013
> INFO - Discovering Network Topology using sources: DP, P2P. Min score: 6
> DEBUG - Device::get_base_macs_from_all: Retrieving all Device MACs...
> DEBUG - Device::get_if_macs_from_all: Retrieving all Interface MACs...
> DEBUG - Device::get_base_macs_from_all: Retrieving all Device MACs...
> DEBUG - PhysAddr::map_all_to_ints: Retrieving all Interface MACs...
> DEBUG - Physaddr::map_all_to_ints: ...done
> DEBUG - Device::get_ips_from_all: Retrieving all Device IPs...
> DEBUG - Interface::dev_name_number: Retrieving all interfaces
> DEBUG - Interface::dev_name_number ...done
> Allips: HASH(0xb117fac)
> DEBUG - Zone::search: wan-bridge2.net.iao.fraunhofer.de
> DEBUG - Zone::search: net.iao.fraunhofer.de
> DEBUG - Zone::search: iao.fraunhofer.de
> DEBUG - Zone::search: fraunhofer.de
> DEBUG - Zone::search: de
> DEBUG - Topology::get_dp_links: Interface id 20782: Remote Device name
> not found: wan-bridge2.net.iao.fraunhofer.de
> DEBUG - Topology::get_dp_links: Interface id 20782: Remote Device not
> found: wan-bridge2.net.iao.fraunhofer.de
> DEBUG - Topology::get_dp_links: Interface id 20782: Remote Device IP
> not found: 0.0.0.0
> DEBUG - Topology::get_dp_links: 0 Links determined in 0 sec
> DEBUG - Topology::get_p2p_links: Checking Subnet 188.1.248.4/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 129.143.103.104/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 192.168.133.0/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 129.143.101.36/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 129.143.101.16/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 129.143.101.32/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 129.143.101.48/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 129.143.103.108/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 129.143.101.28/30
> DEBUG - Topology::get_p2p_links: Checking Subnet 129.143.103.112/30
> DEBUG - Topology::get_p2p_links: 0 Links determined in 0 sec
> DEBUG - Netdot::Topology: All links determined in 0 sec
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-3/0/0.0] <=> vc-b3.infrastruct.stuttgart [xe-5/1/1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-1/0/4.0] <=> vc-k-core.infrastruct.stuttgart [xe-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-2/0/1.0] <=> vc-c2-core.infrastruct.stuttgart [xe-4/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-b4.infrastruct.stuttgart
> [xe-1/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-3/0/1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-container-igb.defaultdomain
> [ae0.0] <=> vc-b1-core.infrastruct.stuttgart [ae0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [xe-6/1/1.0] <=> c-foyer.infrastruct.stuttgart [xe-0/1/0.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-0/0/6.0] <=> vc-e1-core.infrastruct.stuttgart [xe-6/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-0/0/0.0] <=> core-c106.izs.fraunhofer.de [xe-0/0/0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-med.infrastruct.stuttgart
> [ae0.0] <=> vc-c2-core.infrastruct.stuttgart [ae1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-3/0/4.0] <=> vc-irb-c3.infrastruct.stuttgart [xe-0/1/0.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-wb1.infrastruct.stuttgart
> [ge-0/1/2.0] <=> c-wb2.infrastruct.stuttgart [ge-0/1/2.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-b1-core.infrastruct.stuttgart
> [xe-7/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-1/0/2.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-c3-core.infrastruct.stuttgart
> [xe-7/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-2/0/2.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-f2-core.infrastruct.stuttgart
> [xe-7/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-0/0/3.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-tk2.infrastruct.stuttgart
> [ae0.0] <=> vc-a1-core.infrastruct.stuttgart [ae2.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [xe-7/1/1.0] <=> c-foyer.infrastruct.stuttgart [xe-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [ge-8/0/5.0] <=> c-kantine.infrastruct.stuttgart [ge-0/1/0.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link n5k-025.defaultdomain
> [Ethernet1/38] <=> core-c106.izs.fraunhofer.de [xe-2/0/7.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-fpl-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-2/0/6.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-r-core.infrastruct.stuttgart
> [xe-3/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-1/0/5.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link dfn-izs.izs.fraunhofer.de [Gi2/5]
> <=> c-wb1.infrastruct.stuttgart [ge-0/1/0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [ae0.0] <=> core-f014.izs.fraunhofer.de [ae0.0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-0/0/2.0] <=> vc-a2-core.infrastruct.stuttgart [xe-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-b3.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-3/0/0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [ae0.0] <=> c-pforte.infrastruct.stuttgart [ae0.0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link br-iao.defaultdomain [4] <=>
> iao-wb2.defaultdomain [1] not removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a2-core.infrastruct.stuttgart
> [ge-4/0/0.0] <=> c-a4.defaultdomain [ge-0/0/0.0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-gm.infrastruct.stuttgart
> [ge-0/1/0.0] <=> vc-a1-core.infrastruct.stuttgart [ge-9/0/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-r1.infrastruct.stuttgart
> [xe-6/1/2.0] <=> core-c106.izs.fraunhofer.de [xe-3/0/2.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-b1-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-1/0/2.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-wb2.infrastruct.stuttgart
> [ge-0/0/23.0] <=> c-lb2.infrastruct.stuttgart [ge-0/0/23.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-wb1.infrastruct.stuttgart
> [ge-0/1/1] <=> br-iao.defaultdomain [1] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-f2-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-0/0/3.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-f1-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-0/0/4.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-wb2.infrastruct.stuttgart
> [ge-0/1/1] <=> br-iao.defaultdomain [2] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-c3-core.infrastruct.stuttgart
> [xe-4/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-2/0/2.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [ge-9/0/0.0] <=> c-pforte.infrastruct.stuttgart [ge-0/1/0.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link dmz-izs.defaultdomain
> [ge-0/0/23.0] <=> vc-f0-core.infrastruct.stuttgart [ge-3/0/13.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-3/0/6.0] <=> c-lb2.infrastruct.stuttgart [xe-0/1/0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-0/0/7.0] <=> vc-f0-core.infrastruct.stuttgart [xe-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-container-ipa-02.defaultdomain
> [ge-0/1/1.0] <=> c-container-ipa-01.defaultdomain [ge-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-0/0/5.0] <=> vc-e2-core.infrastruct.stuttgart [xe-4/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-1/0/7.0] <=> vc-n-core.infrastruct.stuttgart [xe-1/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-3/0/2.0] <=> vc-r1.infrastruct.stuttgart [xe-0/1/2.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-0/0/5.0] <=> vc-e2-core.infrastruct.stuttgart [xe-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link br-iao.defaultdomain [3] <=>
> iao-wb1.defaultdomain [1] not removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-b2-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-1/0/3.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [ge-9/0/6.0] <=> c-b300.infrastruct.stuttgart [ge-0/1/0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-2/0/0.0] <=> core-f014.izs.fraunhofer.de [xe-2/0/0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-tk2.infrastruct.stuttgart
> [ge-0/1/1.0] <=> vc-a1-core.infrastruct.stuttgart [ge-9/0/4.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link iao-wb2.defaultdomain [2] <=>
> dfn-izs.izs.fraunhofer.de [Gi2/8] not removed because neighbor_fixed
> flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-1/0/4.0] <=> vc-k-core.infrastruct.stuttgart [xe-3/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-kfz-core.infrastruct.stuttgart
> [xe-0/1/0.0] <=> core-c106.izs.fraunhofer.de [xe-2/0/5.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [ae1.0] <=> c-gm.infrastruct.stuttgart [ae0.0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-lb1.infrastruct.stuttgart
> [xe-0/1/0.0] <=> core-c106.izs.fraunhofer.de [xe-3/0/5.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-t-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-1/0/6.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-c2-core.infrastruct.stuttgart
> [ae2.0] <=> vc-market.infrastruct.stuttgart [ae0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-c2-core.infrastruct.stuttgart
> [xe-5/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-2/0/1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-2/0/7.0] <=> n5k-141.defaultdomain [Ethernet1/38] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-1/0/6.0] <=> vc-t-core.infrastruct.stuttgart [xe-1/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-voip.defaultdomain
> [xe-0/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-1/0/0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-voip.defaultdomain
> [xe-1/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-1/0/0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-wb2.infrastruct.stuttgart
> [ge-0/0/2.0] <=> vpn-intern.izs.fraunhofer.de [outside] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-fpl-core.infrastruct.stuttgart
> [ge-7/1/0.0] <=> c-container-ipa-01.defaultdomain [ge-0/1/0.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-irb-c3.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-3/0/4.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-foyer.infrastruct.stuttgart
> [ae0.0] <=> vc-a1-core.infrastruct.stuttgart [ae4.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-2/0/6.0] <=> vc-fpl-core.infrastruct.stuttgart [xe-9/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-f0-core.infrastruct.stuttgart
> [xe-3/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-0/0/7.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-b2-core.infrastruct.stuttgart
> [xe-4/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-1/0/3.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [xe-9/1/1.0] <=> core-f014.izs.fraunhofer.de [xe-0/0/1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-gm.infrastruct.stuttgart
> [ge-0/1/1.0] <=> vc-a1-core.infrastruct.stuttgart [ge-8/0/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-step-ibp.defaultdomain
> [xe-1/1/0.0] <=> vc-a1-core.infrastruct.stuttgart [xe-7/1/0.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-r-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-1/0/5.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-0/0/4.0] <=> vc-f1-core.infrastruct.stuttgart [xe-5/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-3/0/3.0] <=> vc-irb-c1.infrastruct.stuttgart [xe-0/1/0.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-2/0/5.0] <=> vc-kfz-core.infrastruct.stuttgart [xe-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-wb2.infrastruct.stuttgart
> [ge-0/1/3] <=> dfn-izs.izs.fraunhofer.de [Gi2/6] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-3/0/1.0] <=> vc-b4.infrastruct.stuttgart [xe-5/1/1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [ge-8/0/0.0] <=> c-pforte.infrastruct.stuttgart [ge-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-prpool.infrastruct.stuttgart
> [ae0.0] <=> vc-c2-core.infrastruct.stuttgart [ae0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vpn-intern.izs.fraunhofer.de
> [intern] <=> dmz-izs.defaultdomain [ge-0/0/10.0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [xe-1/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-0/0/1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link c-wb1.infrastruct.stuttgart
> [ge-0/0/23.0] <=> c-lb1.infrastruct.stuttgart [ge-0/0/23.0] not seen.
> Increasing neighbor_missed counter.
> DEBUG - Topology::update_links: Link vc-a1-core.infrastruct.stuttgart
> [ge-8/0/4.0] <=> c-tk2.infrastruct.stuttgart [ge-0/1/0.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-n-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-1/0/7.0] not seen.
> Increasing neighbor_missed counter.
> DEBUG - Topology::update_links: Link
> c-gefahrstoff.infrastruct.stuttgart [ae0.0] <=>
> vc-b2-core.infrastruct.stuttgart [ae0.0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link
> vc-c106-core.infrastruct.stuttgart [xe-1/1/1.0] <=>
> core-c106.izs.fraunhofer.de [xe-2/0/3.0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link vc-e1-core.infrastruct.stuttgart
> [xe-0/1/1.0] <=> core-c106.izs.fraunhofer.de [xe-0/0/6.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-3/0/3.0] <=> vc-irb-c1.infrastruct.stuttgart [xe-0/1/1.0] not
> removed because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link iao-wb1.defaultdomain [2] <=>
> dfn-izs.izs.fraunhofer.de [Gi2/7] not removed because neighbor_fixed
> flag is on
> DEBUG - Topology::update_links: Link
> vc-c106-core.infrastruct.stuttgart [xe-0/1/1.0] <=>
> core-f014.izs.fraunhofer.de [xe-2/0/3.0] not removed because
> neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-3/0/6.0] <=> c-lb2.infrastruct.stuttgart [xe-0/1/1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-f014.izs.fraunhofer.de
> [xe-3/0/5.0] <=> c-lb1.infrastruct.stuttgart [xe-0/1/1.0] not removed
> because neighbor_fixed flag is on
> DEBUG - Topology::update_links: Link core-c106.izs.fraunhofer.de
> [xe-0/0/2.0] <=> vc-a2-core.infrastruct.stuttgart [xe-9/1/1.0] not
> removed because neighbor_fixed flag is on
> INFO - Topology discovery done in 1 sec. Links added: 0, removed: 0
> INFO - /usr/local/netdot/bin/updatedevices.pl total runtime: 1 sec
> root@netdot:/usr/local/netdot/bin#
This is because i added the topology-links manually but on my switches
the command "show lldp neighbors" gives me useful results. One example
is shown below. Any Hints or Ideas?
> root@core-f014> show lldp neighbors
> Local Interface Parent Interface Chassis Id Port
> info System Name
> xe-0/0/7.0 - 00:19:e2:56:0c:c0 xe-3/1/1.0
> vc-f0
> xe-2/0/5.0 - 00:21:59:c8:2a:40 xe-0/1/1.0
> vc-kfz
> xe-3/0/5.0 - 00:21:59:cf:2c:80 xe-0/1/1.0
> c-lb1
> xe-0/0/0.0 ae0.0 00:22:83:68:51:f0 xe-0/0/0.0
> core-c106
> xe-2/0/0.0 ae0.0 00:22:83:68:51:f0 xe-2/0/0.0
> core-c106
> xe-3/0/1.0 - 00:23:9c:01:e0:80 xe-5/1/1.0
> vc-b4
> xe-2/0/2.0 - 00:23:9c:01:eb:00 xe-4/1/1.0
> vc-c3
> xe-3/0/6.0 - 00:23:9c:01:f4:40 xe-0/1/0.0
> c-lb2
> xe-2/0/1.0 - 00:23:9c:01:f7:c0 xe-4/1/1.0
> vc-c2
> xe-1/0/6.0 - 00:23:9c:03:b9:c0 xe-0/1/1.0
> vc-t
> xe-1/0/4.0 - 00:23:9c:04:81:c0 xe-3/1/1.0
> vc-k
> xe-0/0/5.0 - 00:23:9c:04:97:c0 xe-0/1/1.0
> vc-e2
> xe-2/0/3.0 - 00:23:9c:05:1c:c0 xe-0/1/1.0
> vc-c106
> xe-1/0/7.0 - 00:23:9c:05:1f:40 xe-1/1/1.0
> vc-n
> xe-0/0/6.0 - 00:23:9c:05:a8:40 xe-6/1/1.0
> vc-e1
> xe-1/0/5.0 - 00:23:9c:05:a8:c0 xe-3/1/1.0
> vc-r
> xe-0/0/4.0 - 00:23:9c:05:ad:40 xe-0/1/1.0
> vc-f1
> xe-0/0/1.0 - 00:23:9c:05:b1:c0 xe-9/1/1.0
> vc-a1
> xe-1/0/0.0 - 00:23:9c:05:d9:40 xe-0/1/1.0
> vc-voip
> xe-1/0/2.0 - 00:23:9c:05:de:40 xe-7/1/1.0
> vc-b1
> xe-0/0/3.0 - 00:23:9c:05:e0:c0 xe-0/1/1.0
> vc-f2
> xe-0/0/2.0 - 00:23:9c:05:e5:40 xe-0/1/1.0
> vc-a2
> xe-1/0/3.0 - 00:23:9c:05:e6:c0 xe-4/1/1.0
> vc-b2
> xe-2/0/6.0 - 00:26:88:68:18:80 xe-9/1/1.0
> vc-fpl
> xe-3/0/2.0 - 28:c0:da:40:06:80 xe-0/1/2.0
> vc-r1
> xe-3/0/0.0 - 50:c5:8d:bc:29:80 xe-5/1/1.0
> vc-b3
> xe-2/0/7.0 - 54:7f:ee:24:51:ad Ethernet1/38
> N5K-141
Kind regards
Andreas Abele
Am 12.06.2013 15:05, schrieb Begley, John:
> It works for me, when supported and enabled.
>
> JB
>
>> -----Original Message-----
>> From: [email protected] [mailto:netdot-users-
>> [email protected]] On Behalf Of Andreas Abele
>> Sent: Wednesday, June 12, 2013 2:53 AM
>> To: netdot-users
>> Subject: [Netdot-users] Juniper EX-Series and lldp detection
>>
>> any one got an idea if it is possible to detect lldp neighborships with
>> Juniper
>> Ex-Series switches/routers?
>>
>> kind regards
>> Andreas Abele
>>
>> --
>> --
>> Andreas Abele, ZIS
>> Nobelstr. 12
>> 70569 Stuttgart
>> Email: [email protected]
>> Phone: +49 711 970 4703
>>
>>
>> --
>> --
>> Andreas Abele, ZIS
>> Nobelstr. 12
>> 70569 Stuttgart
>> Email: [email protected]
>> Phone: +49 711 970 4703
>> _______________________________________________
>> Netdot-users mailing list
>> [email protected]
>> https://osl.uoregon.edu/mailman/listinfo/netdot-users
> This E-mail and any of its attachments may contain Time Warner Cable
> proprietary information, which is privileged, confidential, or subject to
> copyright belonging to Time Warner Cable. This E-mail is intended solely for
> the use of the individual or entity to which it is addressed. If you are not
> the intended recipient of this E-mail, you are hereby notified that any
> dissemination, distribution, copying, or action taken in relation to the
> contents of and attachments to this E-mail is strictly prohibited and may be
> unlawful. If you have received this E-mail in error, please notify the sender
> immediately and permanently delete the original and any copy of this E-mail
> and any printout.
--
--
Andreas Abele, ZIS
Nobelstr. 12
70569 Stuttgart
Email: [email protected]
Phone: +49 711 970 4703
--
--
Andreas Abele, ZIS
Nobelstr. 12
70569 Stuttgart
Email: [email protected]
Phone: +49 711 970 4703
------------------------------
_______________________________________________
Netdot-users mailing list
[email protected]
https://osl.uoregon.edu/mailman/listinfo/netdot-users
End of Netdot-users Digest, Vol 55, Issue 1
*******************************************
