X rj45 3m × 4 Tks mark On Fri, May 27, 2016 at 5:00 AM -0700, <nanog-request@nanog.org> wrote: Send NANOG mailing list submissions to nanog@nanog.org To subscribe or unsubscribe via the World Wide Web, visit http://mailman.nanog.org/mailman/listinfo/nanog or, via email, send a message with subject or body 'help' to nanog-request@nanog.org You can reach the person managing the list at nanog-owner@nanog.org When replying, please edit your Subject line so it is more specific than "Re: Contents of NANOG digest..." Today's Topics: 1. Frontier routing issue? (Matt Hoppes) 2. AS 714/6185 IX Peering (Graham Johnston) 3. LLDP via SNMP (Avi Freedman) 4. Re: LLDP via SNMP (Spencer Ryan) 5. RE: LLDP via SNMP (Michael Hare) 6. Re: LLDP via SNMP (Jeff Gehlbach) 7. Re: LLDP via SNMP (Saku Ytti) 8. Re: Network traffic simulator (David) 9. Re: Network traffic simulator (Jim Greene) 10. Re: Network traffic simulator (Tom Smyth) 11. VOIP Monitoring Solution (segs) 12. Re: Frontier routing issue? (Gambill, Nate) 13. Re: LLDP via SNMP (Fedor Sumkin) 14. GRE on ASR9001 (Rukka Pal) 15. Re: GRE on ASR9001 (Saku Ytti) 16. Re: GRE on ASR9001 (Rukka Pal) 17. Re: GRE on ASR9001 (Saku Ytti) ---------------------------------------------------------------------- Message: 1 Date: Thu, 26 May 2016 08:22:18 -0400 From: Matt Hoppes To: nanog@nanog.org Subject: Frontier routing issue? Message-ID: <40AD53F9-BEB3-4930-9603-381DE1901B14@rivervalleyinternet.net> Content-Type: text/plain; charset=us-ascii Is anyone else in the north east seeing routing issues on frontier right now? Unable to get to many websites. Trace route seems to complete fine but you can't bring up any content. ------------------------------ Message: 2 Date: Thu, 26 May 2016 13:11:35 +0000 From: Graham Johnston To: NANOG Subject: AS 714/6185 IX Peering Message-ID: <82C0CE81789FE64D8F4D152631918297B149B4@MSG6.westman.int> Content-Type: text/plain; charset="us-ascii" Is there anyone from AS 714/6185 that can reach out to me, AS 19016, to try and get traffic from your network to come to me via your Equinix IX connection instead of a transit connections. Graham Johnston Network Planner Westman Communications Group 204.717.2829 johnstong@westmancom.com P think green; don't print this email. ------------------------------ Message: 3 Date: Thu, 26 May 2016 10:47:15 -0400 (EDT) From: freedman@freedman.net (Avi Freedman) To: nanog@nanog.org Subject: LLDP via SNMP Message-ID: <20160526144715.AA0D655006E16@freedman.net> Content-Type: text/plain; charset="US-ASCII" Have had the question come up a few times, so I wanted to poll the community to see... For those who are monitoring LLDP, how have you found the SNMP MIB support support for it on Juniper, Cisco, Brocade, Arista, and others? Wondering if you've needed to resort to CLI scraping or APIs to get the data? Thanks, Avi Freedman CEO, Kentik ------------------------------ Message: 4 Date: Thu, 26 May 2016 10:51:03 -0400 From: Spencer Ryan To: avi@kentik.com Cc: "North American Network Operators' Group" Subject: Re: LLDP via SNMP Message-ID: Content-Type: text/plain; charset=UTF-8 We use Observium for most of our SNMP monitoring, and it correctly pulls LLDP and CDP data from all of our Cisco and Arista gear. *Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com On Thu, May 26, 2016 at 10:47 AM, Avi Freedman wrote:
Have had the question come up a few times, so I wanted to poll the community to see...
For those who are monitoring LLDP, how have you found the SNMP MIB support support for it on Juniper, Cisco, Brocade, Arista, and others?
Wondering if you've needed to resort to CLI scraping or APIs to get the data?
Thanks,
Avi Freedman CEO, Kentik
------------------------------ Message: 5 Date: Thu, 26 May 2016 15:53:53 +0000 From: Michael Hare To: Spencer Ryan , "avi@kentik.com" Cc: North American Network Operators' Group Subject: RE: LLDP via SNMP Message-ID: Content-Type: text/plain; CHARSET=US-ASCII My experience with Juniper has been mixed, experience with 12.X and 13.X made me wonder if I had a poor understanding of how to do a proper decode or if Juniper's implementation itself had issues as I would often get incomplete results. We've now grab over XML and have been pleased with that choice to the point I no longer see it as a "resort" but the most efficient way for us to move forward. I used to open JTAC cases on each SNMP problem I'd come across [ CoS, mac-accounting ] and it generally wasn't a good use of our time. -Michael -----Original Message----- From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of Spencer Ryan Sent: Thursday, May 26, 2016 9:51 AM To: avi@kentik.com Cc: North American Network Operators' Group Subject: Re: LLDP via SNMP We use Observium for most of our SNMP monitoring, and it correctly pulls LLDP and CDP data from all of our Cisco and Arista gear. *Spencer Ryan* | Senior Systems Administrator | sryan@arbor.net *Arbor Networks* +1.734.794.5033 (d) | +1.734.846.2053 (m) www.arbornetworks.com On Thu, May 26, 2016 at 10:47 AM, Avi Freedman wrote:
Have had the question come up a few times, so I wanted to poll the community to see...
For those who are monitoring LLDP, how have you found the SNMP MIB support support for it on Juniper, Cisco, Brocade, Arista, and others?
Wondering if you've needed to resort to CLI scraping or APIs to get the data?
Thanks,
Avi Freedman CEO, Kentik
------------------------------ Message: 6 Date: Thu, 26 May 2016 14:53:19 -0400 From: Jeff Gehlbach To: "nanog@nanog.org" Subject: Re: LLDP via SNMP Message-ID: <34b0b707-79be-b1c7-d89c-d18690aea6d1@opennms.org> Content-Type: text/plain; charset="windows-1252" On 05/26/2016 10:47 AM, Avi Freedman wrote:
For those who are monitoring LLDP, how have you found the SNMP MIB support support for it on Juniper, Cisco, Brocade, Arista, and others?
I can't speak to Brocade (just haven't been to a customer recently who has their kit and wants topology), but I've found support from Juniper, Cisco, and Arista to be very good. As long as the device software load is reasonably modern and LLDP is lit up everywhere, topology usually just works. We added LLDP support a couple years ago to OpenNMS' L2/L3 link-discovery service daemon (on top of CDP, IS-IS, and OSPF). Everything is done via SNMP, for now anyway. If you read Java, you can profit from our experience by sifting through the various LLDP-related classes in our code here: https://github.com/OpenNMS/opennms/ Tangentially, we've also been working on integration with OpenDaylight, which pretty much demands going ReSTful to gather underlay and overlay topology data. -jeff