May 2016 - Test - lists.nanog.org

Preferring RSVP for only one l2circuit.
by Mohamed Kamal 27 May '16

27 May '16

I have a full-mesh LDP LSPs between my MX-104 routers, however, between two specific routers and on the same loopbacks I configured RSVP LSP to be used as the transport for only one l2circuit and no more. The problem is, when the RSVP gets signaled, it gets installed in the inet.3 and gets preferred over any other LDP LSP. So all the traffic destined to RSVP tail-end will prefer the RSVP over the LDP. I have increased the preference of the RSVP, and it has been taken out of the inet.3, so the l2circuit didn't prefer the RSVP path anymore! Do anyone has a working configuration for this? or should I configured another loopback address on every pair of routers for the RSVP signalling? -- mk

4 5

Weekly Routing Table Report
by Routing Analysis Role Account 27 May '16

27 May '16

This is an automated weekly mailing describing the state of the Internet Routing Table as seen from APNIC's router in Japan. The posting is sent to APOPS, NANOG, AfNOG, AusNOG, SANOG, PacNOG, SAFNOG, PaNOG, SdNOG, BJNOG, CaribNOG and the RIPE Routing WG. Daily listings are sent to bgp-stats(a)lists.apnic.net For historical data, please see http://thyme.rand.apnic.net. If you have any comments please contact Philip Smith <pfsinoz(a)gmail.com>. Routing Table Report 04:00 +10GMT Sat 28 May, 2016 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 594503 Prefixes after maximum aggregation (per Origin AS): 217631 Deaggregation factor: 2.73 Unique aggregates announced (without unneeded subnets): 291513 Total ASes present in the Internet Routing Table: 53890 Prefixes per ASN: 11.03 Origin-only ASes present in the Internet Routing Table: 36576 Origin ASes announcing only one prefix: 15650 Transit ASes present in the Internet Routing Table: 6452 Transit-only ASes present in the Internet Routing Table: 170 Average AS path length visible in the Internet Routing Table: 4.3 Max AS path length visible: 54 Max AS path prepend of ASN ( 55644) 51 Prefixes from unregistered ASNs in the Routing Table: 1029 Unregistered ASNs in the Routing Table: 368 Number of 32-bit ASNs allocated by the RIRs: 14035 Number of 32-bit ASNs visible in the Routing Table: 10862 Prefixes from 32-bit ASNs in the Routing Table: 42481 Number of bogon 32-bit ASNs visible in the Routing Table: 7 Special use prefixes present in the Routing Table: 0 Prefixes being announced from unallocated address space: 362 Number of addresses announced to Internet: 2808989828 Equivalent to 167 /8s, 109 /16s and 200 /24s Percentage of available address space announced: 75.9 Percentage of allocated address space announced: 75.9 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 98.2 Total number of prefixes smaller than registry allocations: 193849 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 152413 Total APNIC prefixes after maximum aggregation: 42506 APNIC Deaggregation factor: 3.59 Prefixes being announced from the APNIC address blocks: 163652 Unique aggregates announced from the APNIC address blocks: 67122 APNIC Region origin ASes present in the Internet Routing Table: 5193 APNIC Prefixes per ASN: 31.51 APNIC Region origin ASes announcing only one prefix: 1187 APNIC Region transit ASes present in the Internet Routing Table: 919 Average APNIC Region AS path length visible: 4.4 Max APNIC Region AS path length visible: 54 Number of APNIC region 32-bit ASNs visible in the Routing Table: 2096 Number of APNIC addresses announced to Internet: 754412868 Equivalent to 44 /8s, 247 /16s and 109 /24s Percentage of available APNIC address space announced: 88.2 APNIC AS Blocks 4608-4864, 7467-7722, 9216-10239, 17408-18431 (pre-ERX allocations) 23552-24575, 37888-38911, 45056-46079, 55296-56319, 58368-59391, 63488-64098, 131072-135580 APNIC Address Blocks 1/8, 14/8, 27/8, 36/8, 39/8, 42/8, 43/8, 49/8, 58/8, 59/8, 60/8, 61/8, 101/8, 103/8, 106/8, 110/8, 111/8, 112/8, 113/8, 114/8, 115/8, 116/8, 117/8, 118/8, 119/8, 120/8, 121/8, 122/8, 123/8, 124/8, 125/8, 126/8, 133/8, 150/8, 153/8, 163/8, 171/8, 175/8, 180/8, 182/8, 183/8, 202/8, 203/8, 210/8, 211/8, 218/8, 219/8, 220/8, 221/8, 222/8, 223/8, ARIN Region Analysis Summary ---------------------------- Prefixes being announced by ARIN Region ASes: 181275 Total ARIN prefixes after maximum aggregation: 89149 ARIN Deaggregation factor: 2.03 Prefixes being announced from the ARIN address blocks: 186737 Unique aggregates announced from the ARIN address blocks: 88167 ARIN Region origin ASes present in the Internet Routing Table: 16356 ARIN Prefixes per ASN: 11.42 ARIN Region origin ASes announcing only one prefix: 5828 ARIN Region transit ASes present in the Internet Routing Table: 1715 Average ARIN Region AS path length visible: 3.8 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 1237 Number of ARIN addresses announced to Internet: 1099642048 Equivalent to 65 /8s, 139 /16s and 52 /24s Percentage of available ARIN address space announced: 58.2 ARIN AS Blocks 1-1876, 1902-2042, 2044-2046, 2048-2106 (pre-ERX allocations) 2138-2584, 2615-2772, 2823-2829, 2880-3153 3354-4607, 4865-5119, 5632-6655, 6912-7466 7723-8191, 10240-12287, 13312-15359, 16384-17407 18432-20479, 21504-23551, 25600-26591, 26624-27647, 29696-30719, 31744-33791 35840-36863, 39936-40959, 46080-47103 53248-55295, 62464-63487, 64198-64296, 393216-397212 ARIN Address Blocks 3/8, 4/8, 6/8, 7/8, 8/8, 9/8, 11/8, 12/8, 13/8, 15/8, 16/8, 17/8, 18/8, 19/8, 20/8, 21/8, 22/8, 23/8, 24/8, 26/8, 28/8, 29/8, 30/8, 32/8, 33/8, 34/8, 35/8, 38/8, 40/8, 44/8, 45/8, 47/8, 48/8, 50/8, 52/8, 53/8, 54/8, 55/8, 56/8, 57/8, 63/8, 64/8, 65/8, 66/8, 67/8, 68/8, 69/8, 70/8, 71/8, 72/8, 73/8, 74/8, 75/8, 76/8, 96/8, 97/8, 98/8, 99/8, 100/8, 104/8, 107/8, 108/8, 128/8, 129/8, 130/8, 131/8, 132/8, 134/8, 135/8, 136/8, 137/8, 138/8, 139/8, 140/8, 142/8, 143/8, 144/8, 146/8, 147/8, 148/8, 149/8, 152/8, 155/8, 156/8, 157/8, 158/8, 159/8, 160/8, 161/8, 162/8, 164/8, 165/8, 166/8, 167/8, 168/8, 169/8, 170/8, 172/8, 173/8, 174/8, 184/8, 192/8, 198/8, 199/8, 204/8, 205/8, 206/8, 207/8, 208/8, 209/8, 214/8, 215/8, 216/8, RIPE Region Analysis Summary ---------------------------- Prefixes being announced by RIPE Region ASes: 142652 Total RIPE prefixes after maximum aggregation: 70520 RIPE Deaggregation factor: 2.02 Prefixes being announced from the RIPE address blocks: 151964 Unique aggregates announced from the RIPE address blocks: 94043 RIPE Region origin ASes present in the Internet Routing Table: 18075 RIPE Prefixes per ASN: 8.41 RIPE Region origin ASes announcing only one prefix: 7878 RIPE Region transit ASes present in the Internet Routing Table: 3012 Average RIPE Region AS path length visible: 4.3 Max RIPE Region AS path length visible: 36 Number of RIPE region 32-bit ASNs visible in the Routing Table: 4806 Number of RIPE addresses announced to Internet: 704609664 Equivalent to 41 /8s, 255 /16s and 125 /24s Percentage of available RIPE address space announced: 102.4 RIPE AS Blocks 1877-1901, 2043, 2047, 2107-2136, 2585-2614 (pre-ERX allocations) 2773-2822, 2830-2879, 3154-3353, 5377-5631 6656-6911, 8192-9215, 12288-13311, 15360-16383 20480-21503, 24576-25599, 28672-29695 30720-31743, 33792-35839, 38912-39935 40960-45055, 47104-52223, 56320-58367 59392-61439, 61952-62463, 196608-204287 RIPE Address Blocks 2/8, 5/8, 25/8, 31/8, 37/8, 46/8, 51/8, 62/8, 77/8, 78/8, 79/8, 80/8, 81/8, 82/8, 83/8, 84/8, 85/8, 86/8, 87/8, 88/8, 89/8, 90/8, 91/8, 92/8, 93/8, 94/8, 95/8, 109/8, 141/8, 145/8, 151/8, 176/8, 178/8, 185/8, 188/8, 193/8, 194/8, 195/8, 212/8, 213/8, 217/8, LACNIC Region Analysis Summary ------------------------------ Prefixes being announced by LACNIC Region ASes: 61535 Total LACNIC prefixes after maximum aggregation: 12202 LACNIC Deaggregation factor: 5.04 Prefixes being announced from the LACNIC address blocks: 75875 Unique aggregates announced from the LACNIC address blocks: 36025 LACNIC Region origin ASes present in the Internet Routing Table: 2473 LACNIC Prefixes per ASN: 30.68 LACNIC Region origin ASes announcing only one prefix: 576 LACNIC Region transit ASes present in the Internet Routing Table: 567 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 23 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 2506 Number of LACNIC addresses announced to Internet: 171169024 Equivalent to 10 /8s, 51 /16s and 213 /24s Percentage of available LACNIC address space announced: 102.0 LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-265628 + ERX transfers LACNIC Address Blocks 177/8, 179/8, 181/8, 186/8, 187/8, 189/8, 190/8, 191/8, 200/8, 201/8, AfriNIC Region Analysis Summary ------------------------------- Prefixes being announced by AfriNIC Region ASes: 14037 Total AfriNIC prefixes after maximum aggregation: 3217 AfriNIC Deaggregation factor: 4.36 Prefixes being announced from the AfriNIC address blocks: 15913 Unique aggregates announced from the AfriNIC address blocks: 5825 AfriNIC Region origin ASes present in the Internet Routing Table: 736 AfriNIC Prefixes per ASN: 21.62 AfriNIC Region origin ASes announcing only one prefix: 181 AfriNIC Region transit ASes present in the Internet Routing Table: 167 Average AfriNIC Region AS path length visible: 4.7 Max AfriNIC Region AS path length visible: 26 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 217 Number of AfriNIC addresses announced to Internet: 78714880 Equivalent to 4 /8s, 177 /16s and 24 /24s Percentage of available AfriNIC address space announced: 78.2 AfriNIC AS Blocks 36864-37887, 327680-328703 & ERX transfers AfriNIC Address Blocks 41/8, 102/8, 105/8, 154/8, 196/8, 197/8, APNIC Region per AS prefix count summary ---------------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5559 4192 76 China Education and Research 7545 3342 356 223 TPG Telecom Limited 4766 3177 11144 1123 Korea Telecom 17974 2946 914 96 PT Telekomunikasi Indonesia 9829 2522 1479 497 National Internet Backbone 9808 2096 8781 40 Guangdong Mobile Communicatio 4755 2092 431 241 TATA Communications formerly 4808 1701 2301 552 CNCGROUP IP network China169 9583 1510 122 556 Sify Limited 38197 1509 94 218 Sun Network (Hong Kong) Limit Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-APNIC ARIN Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 22773 3331 2947 139 Cox Communications Inc. 6389 2298 3671 41 BellSouth.net Inc. 18566 2195 394 275 MegaPath Corporation 20115 1923 1938 403 Charter Communications 209 1695 4971 773 Qwest Communications Company, 30036 1692 336 415 Mediacom Communications Corp 6983 1690 849 232 EarthLink, Inc. 4323 1512 984 372 tw telecom holdings, inc. 701 1297 10718 705 MCI Communications Services, 11492 1283 234 584 CABLE ONE, INC. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-ARIN RIPE Region per AS prefix count summary --------------------------------------- ASN No of nets /20 equiv MaxAgg Description 39891 2901 151 11 SaudiNet, Saudi Telecom Compa 20940 2595 1002 1863 Akamai International B.V. 34984 1965 326 358 TELLCOM ILETISIM HIZMETLERI A 12479 1229 998 88 France Telecom Espana SA 8551 1220 376 55 Bezeq International-Ltd 6849 1148 355 21 JSC "Ukrtelecom" 8402 1124 544 15 OJSC "Vimpelcom" 13188 1078 98 68 TOV "Bank-Inform" 31148 1024 47 44 Freenet Ltd. 9198 936 352 26 JSC Kazakhtelecom Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-RIPE LACNIC Region per AS prefix count summary ----------------------------------------- ASN No of nets /20 equiv MaxAgg Description 10620 3472 541 155 Telmex Colombia S.A. 8151 2258 3425 576 Uninet S.A. de C.V. 7303 1511 940 234 Telecom Argentina S.A. 11830 1476 368 51 Instituto Costarricense de El 6503 1473 437 56 Axtel, S.A.B. de C.V. 6147 1112 377 27 Telefonica del Peru S.A.A. 26615 1007 2325 34 Tim Celular S.A. 3816 1002 479 175 COLOMBIA TELECOMUNICACIONES S 7738 994 1882 40 Telemar Norte Leste S.A. 11172 907 125 77 Alestra, S. de R.L. de C.V. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-LACNIC AfriNIC Region per AS prefix count summary ------------------------------------------ ASN No of nets /20 equiv MaxAgg Description 24863 1087 402 44 Link Egypt (Link.NET) 37611 639 48 2 Afrihost-Brevis Computer Serv 36903 626 315 103 Office National des Postes et 36992 509 1359 27 ETISALAT MISR 8452 489 1472 15 TE-AS 37492 395 234 68 Orange Tunisie 29571 301 37 13 Cote d'Ivoire Telecom 24835 294 466 14 Vodafone Data 15399 285 35 10 Wananchi Group (Kenya) Limite 2018 257 327 74 TENET (The UNINET Project) Complete listing at http://thyme.rand.apnic.net/current/data-ASnet-AFRINIC Global Per AS prefix count summary ---------------------------------- ASN No of nets /20 equiv MaxAgg Description 4538 5559 4192 76 China Education and Research 10620 3472 541 155 Telmex Colombia S.A. 7545 3342 356 223 TPG Telecom Limited 22773 3331 2947 139 Cox Communications Inc. 4766 3177 11144 1123 Korea Telecom 17974 2946 914 96 PT Telekomunikasi Indonesia 39891 2901 151 11 SaudiNet, Saudi Telecom Compa 20940 2595 1002 1863 Akamai International B.V. 9829 2522 1479 497 National Internet Backbone 6389 2298 3671 41 BellSouth.net Inc. Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 10620 3472 3317 Telmex Colombia S.A. 22773 3331 3192 Cox Communications Inc. 7545 3342 3119 TPG Telecom Limited 39891 2901 2890 SaudiNet, Saudi Telecom Compa 17974 2946 2850 PT Telekomunikasi Indonesia 6389 2298 2257 BellSouth.net Inc. 9808 2096 2056 Guangdong Mobile Communicatio 4766 3177 2054 Korea Telecom 9829 2522 2025 National Internet Backbone 18566 2195 1920 MegaPath Corporation Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 65001 PRIVATE 5.143.176.0/20 15468 OJSC Rostelecom 30662 UNALLOCATED 8.2.129.0/24 3356 Level 3 Communicatio 53506 UNALLOCATED 8.17.102.0/23 3356 Level 3 Communicatio 46467 UNALLOCATED 8.19.192.0/24 46887 Lightower Fiber Netw 16589 UNALLOCATED 8.20.247.0/24 35838 CCANET Limited 16589 UNALLOCATED 8.26.56.0/24 35838 CCANET Limited 46473 UNALLOCATED 8.27.122.0/24 12180 Internap Network Ser 46473 UNALLOCATED 8.27.124.0/24 12180 Internap Network Ser 27205 UNALLOCATED 8.38.16.0/21 3356 Level 3 Communicatio 27205 UNALLOCATED 8.38.16.0/22 32787 Prolexic Technologie Complete listing at http://thyme.rand.apnic.net/current/data-badAS Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 23.226.112.0/20 62788 >>UNKNOWN<< 23.249.144.0/20 40430 colo4jax, LLC 27.100.7.0/24 56096 >>UNKNOWN<< 41.73.1.0/24 37004 >>UNKNOWN<< 41.73.2.0/24 37004 >>UNKNOWN<< 41.73.3.0/24 37004 >>UNKNOWN<< 41.73.4.0/24 37004 >>UNKNOWN<< 41.73.5.0/24 37004 >>UNKNOWN<< 41.73.6.0/24 37004 >>UNKNOWN<< 41.73.7.0/24 37004 >>UNKNOWN<< Complete listing at http://thyme.rand.apnic.net/current/data-add-IANA Number of prefixes announced per prefix length (Global) ------------------------------------------------------- /1:0 /2:0 /3:0 /4:0 /5:0 /6:0 /7:0 /8:16 /9:13 /10:36 /11:101 /12:266 /13:514 /14:1036 /15:1763 /16:13043 /17:7609 /18:12712 /19:25937 /20:38001 /21:39713 /22:65681 /23:57477 /24:328881 /25:560 /26:598 /27:419 /28:48 /29:32 /30:14 /31:1 /32:32 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 39891 2664 2901 SaudiNet, Saudi Telecom Compa 22773 2557 3331 Cox Communications Inc. 18566 2097 2195 MegaPath Corporation 30036 1507 1692 Mediacom Communications Corp 6389 1476 2298 BellSouth.net Inc. 10620 1376 3472 Telmex Colombia S.A. 6983 1340 1690 EarthLink, Inc. 34984 1249 1965 TELLCOM ILETISIM HIZMETLERI A 11492 1186 1283 CABLE ONE, INC. 6849 968 1148 JSC "Ukrtelecom" Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1575 2:748 4:20 5:2065 6:31 8:962 12:1779 13:39 14:1699 15:45 16:2 17:84 18:90 20:48 22:1 23:1514 24:1763 27:2275 31:1767 32:59 33:2 34:2 35:5 36:292 37:2231 38:1221 39:25 40:91 41:2826 42:397 43:1724 44:43 45:1938 46:2493 47:78 49:1168 50:875 51:33 52:195 54:331 55:7 56:7 57:42 58:1529 59:886 60:344 61:1823 62:1499 63:1936 64:4445 65:2164 66:4255 67:2193 68:1093 69:3293 70:1156 71:474 72:2006 74:2536 75:346 76:349 77:1375 78:1298 79:845 80:1274 81:1352 82:948 83:698 84:831 85:1578 86:480 87:1057 88:563 89:2000 90:172 91:6036 92:914 93:2323 94:2385 95:2314 96:499 97:359 98:937 99:46 100:75 101:1044 103:10902 104:2448 105:125 106:405 107:1181 108:669 109:2195 110:1241 111:1639 112:1012 113:1169 114:1060 115:1613 116:1580 117:1439 118:2065 119:1626 120:930 121:1178 122:2178 123:2023 124:1576 125:1730 128:735 129:400 130:418 131:1321 132:620 133:176 134:455 135:127 136:373 137:348 138:1729 139:274 140:543 141:459 142:639 143:896 144:696 145:159 146:872 147:631 148:1481 149:507 150:645 151:883 152:618 153:285 154:632 155:934 156:503 157:444 158:337 159:1119 160:488 161:715 162:2321 163:548 164:884 165:1033 166:320 167:1147 168:1873 169:662 170:1612 171:263 172:571 173:1643 174:746 175:723 176:1744 177:3927 178:2209 179:1129 180:2042 181:1772 182:1862 183:980 184:807 185:6515 186:2964 187:2120 188:2116 189:1689 190:7681 191:1209 192:8933 193:5743 194:4384 195:3763 196:1673 197:1073 198:5556 199:5700 200:6937 201:3744 202:10177 203:9643 204:4519 205:2728 206:2986 207:3135 208:4053 209:3873 210:3882 211:2049 212:2676 213:2228 214:852 215:71 216:5793 217:1967 218:797 219:607 220:1689 221:865 222:668 223:1237 End of report

1 0

LLDP via SNMP
by freedman＠freedman.net 27 May '16

27 May '16

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

7 6

Re: NANOG Digest, Vol 100, Issue 26
by mark＠rapid-communications.com 27 May '16

27 May '16

X rj45 3m × 4 Tks mark On Fri, May 27, 2016 at 5:00 AM -0700, <nanog-request(a)nanog.org> wrote: Send NANOG mailing list submissions to nanog(a)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(a)nanog.org You can reach the person managing the list at nanog-owner(a)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(a)nanog.org Subject: Frontier routing issue? Message-ID: <40AD53F9-BEB3-4930-9603-381DE1901B14(a)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(a)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(a)westmancom.com P think green; don't print this email. ------------------------------ Message: 3 Date: Thu, 26 May 2016 10:47:15 -0400 (EDT) From: freedman(a)freedman.net (Avi Freedman) To: nanog(a)nanog.org Subject: LLDP via SNMP Message-ID: <20160526144715.AA0D655006E16(a)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(a)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(a)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(a)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(a)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(a)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(a)nanog.org" Subject: Re: LLDP via SNMP Message-ID: <34b0b707-79be-b1c7-d89c-d18690aea6d1(a)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

1 0

GRE on ASR9001
by Rukka Pal 27 May '16

27 May '16

Anyone here running GRE tunnels between ASR9001series? I am planning to connect some special-purpose remote sites to my core infra using unencrypted GRE tunnels and OSPF routing. The estimated bandwidth requirements are between 500Mbps and several Gbps. I am not planning to use MPAs, instead the fixed 10G ports I believe this should present no significant problems to the ASR9001, just wanted to get a confirmation. Thanks!

2 3

Re: AS 714/6185 IX Peering
by Ren Provo 27 May '16

27 May '16

Third time should be the charm? (Thanks Job!) Cheers! -Ren Sent from my iPhone 6S Plus > On May 27, 2016, at 11:36 AM, Ren Provo <ren.provo(a)gmail.com> wrote: > > Several folks have written to ensure I spotted this during RIPE. Indeed, the reminder to engage contacts posted at http://as714.peeringdb.com - namely peering-NOC(a)apple.com - was sent. Y'all didn't see it because it was sent from an email that is not registered on this list. Spotted the rejection later. Hence take two today and a confirmation Graham's concern has been noted within Apple. > > Cheers! -Ren > Sent from my iPhone 6S Plus > >> On May 26, 2016, at 3:11 PM, Graham Johnston <johnstong(a)westmancom.com> wrote: >> >> 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(a)westmancom.com<mailto:johnstong@westmancom.com> >> P think green; don't print this email. >>

1 0

Frontier routing issue?
by Matt Hoppes 26 May '16

26 May '16

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.

2 1

AS 714/6185 IX Peering
by Graham Johnston 26 May '16

26 May '16

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(a)westmancom.com<mailto:johnstong@westmancom.com> P think green; don't print this email.

1 0

NYNOG Inaugural meet livestream
by Joly MacFie 25 May '16

25 May '16

http://isoc-ny.org/p2/8521 -- --------------------------------------------------------------- Joly MacFie 218 565 9365 Skype:punkcast -------------------------------------------------------------- -

1 0

Re: Network traffic simulator
by Spencer Ryan 25 May '16

25 May '16

Yeah. We run all of our IXIA gear 24/7 in automated feature/regression testing. We are looking into high density layer 1 packet switches so we can automate physical topology changes as well. On May 25, 2016 3:14 AM, "Saku Ytti" <saku(a)ytti.fi> wrote: Ugh. In all cases below, where it says Agilent it should say IXIA. > Many times in QoS testing you'd have EF, AF, BE > traffic, and you have expectation how many percentage in given > situation should given class drop, doing this in Agilent is a chore. > > Agilent probably has best in the breed network with emulation > capabilities. And focus generally seems to be in protocol > testing/development where network emulation is tremendously useful. > > As the platforms are very expensive, not many SPs are using them, so > they're not getting input from SPs what the boxes should be doing. > This market is very poorly tapped, there is large demand in the market > for proper testing equipment but it's just priced out of reach. I > believe Spirent and Agilent should sell the hardware at-cost, then > sell timed licenses, where maybe 1000h license would be today's full > cost. Large segment of this market might not use box at all in some > year and would generally only require modest hours from it. > Bit harder to justify the cost with low use, compared to vendors who > run them automated 24/7. -- ++ytti

1 0