- Test - lists.nanog.org

Re: FCC: 2017 Atlantic Hurricane Season Impact on Communications
by Sean Donelan 27 Aug '18

27 Aug '18

On Mon, 27 Aug 2018, Mike Hammett wrote: > There are dozens of independents on the islands. They probably didn't know > their comments were desired. The Commission is still looking for nominations for its disaster response and recovery working group. Any independent ISPs can nominate a representative.... https://docs.fcc.gov/public/attachments/DA-18-837A1.pdf The Federal Communications Commission (Commission) solicits nominations for membership on a new Disaster Response and Recovery Working Group of the Broadband Deployment Advisory Committee (BDAC). This new working group will assist the BDAC in providing advice and recommendations to the Commission on steps that can be taken to improve disaster preparation, response, and recovery for broadband infrastructure. Nominations for membership to the BDAC’s Disaster Response and Recovery Working Group should be submitted to the FCC no later than September 7, 2018.

1 0

Sprint Wireless
by Luke Guillory 27 Aug '18

27 Aug '18

Anyone from Sprint on here that can help or direct me to a contact that can help with trunk issues into a tandem? Running out of options trying to get them to sort of their issues for their customers. Thanks Luke Ns

1 0

YANG daemeon for Linux
by Karl Jørn 26 Aug '18

26 Aug '18

Hi Is there a YANG daemeon for Linux ? If yes, can any one please share their experiences ? Danke, Karl

8 8

Weekly Routing Table Report
by cscora＠apnic.net 24 Aug '18

24 Aug '18

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, SANOG, PacNOG, SAFNOG TZNOG, MENOG, BJNOG, SDNOG, CMNOG, LACNOG, IRNOG 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 25 Aug, 2018 Report Website: http://thyme.rand.apnic.net Detailed Analysis: http://thyme.rand.apnic.net/current/ Analysis Summary ---------------- BGP routing table entries examined: 711713 Prefixes after maximum aggregation (per Origin AS): 273276 Deaggregation factor: 2.60 Unique aggregates announced (without unneeded subnets): 341846 Total ASes present in the Internet Routing Table: 61612 Prefixes per ASN: 11.55 Origin-only ASes present in the Internet Routing Table: 53212 Origin ASes announcing only one prefix: 23205 Transit ASes present in the Internet Routing Table: 8400 Transit-only ASes present in the Internet Routing Table: 260 Average AS path length visible in the Internet Routing Table: 4.0 Max AS path length visible: 34 Max AS path prepend of ASN ( 30873) 32 Prefixes from unregistered ASNs in the Routing Table: 55 Number of instances of unregistered ASNs: 55 Number of 32-bit ASNs allocated by the RIRs: 23808 Number of 32-bit ASNs visible in the Routing Table: 19184 Prefixes from 32-bit ASNs in the Routing Table: 80326 Number of bogon 32-bit ASNs visible in the Routing Table: 20 Special use prefixes present in the Routing Table: 2 Prefixes being announced from unallocated address space: 272 Number of addresses announced to Internet: 2857455684 Equivalent to 170 /8s, 81 /16s and 80 /24s Percentage of available address space announced: 77.2 Percentage of allocated address space announced: 77.2 Percentage of available address space allocated: 100.0 Percentage of address space in use by end-sites: 99.0 Total number of prefixes smaller than registry allocations: 237793 APNIC Region Analysis Summary ----------------------------- Prefixes being announced by APNIC Region ASes: 193767 Total APNIC prefixes after maximum aggregation: 55359 APNIC Deaggregation factor: 3.50 Prefixes being announced from the APNIC address blocks: 191973 Unique aggregates announced from the APNIC address blocks: 79241 APNIC Region origin ASes present in the Internet Routing Table: 9019 APNIC Prefixes per ASN: 21.29 APNIC Region origin ASes announcing only one prefix: 2534 APNIC Region transit ASes present in the Internet Routing Table: 1342 Average APNIC Region AS path length visible: 4.0 Max APNIC Region AS path length visible: 26 Number of APNIC region 32-bit ASNs visible in the Routing Table: 3981 Number of APNIC addresses announced to Internet: 767386627 Equivalent to 45 /8s, 189 /16s and 100 /24s 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, 64297-64395, 131072-139577 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: 211629 Total ARIN prefixes after maximum aggregation: 100126 ARIN Deaggregation factor: 2.11 Prefixes being announced from the ARIN address blocks: 211412 Unique aggregates announced from the ARIN address blocks: 100195 ARIN Region origin ASes present in the Internet Routing Table: 18229 ARIN Prefixes per ASN: 11.60 ARIN Region origin ASes announcing only one prefix: 6758 ARIN Region transit ASes present in the Internet Routing Table: 1805 Average ARIN Region AS path length visible: 3.6 Max ARIN Region AS path length visible: 23 Number of ARIN region 32-bit ASNs visible in the Routing Table: 2415 Number of ARIN addresses announced to Internet: 1103319200 Equivalent to 65 /8s, 195 /16s and 80 /24s 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-399260 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: 195094 Total RIPE prefixes after maximum aggregation: 93057 RIPE Deaggregation factor: 2.10 Prefixes being announced from the RIPE address blocks: 191399 Unique aggregates announced from the RIPE address blocks: 113352 RIPE Region origin ASes present in the Internet Routing Table: 25436 RIPE Prefixes per ASN: 7.52 RIPE Region origin ASes announcing only one prefix: 11467 RIPE Region transit ASes present in the Internet Routing Table: 3523 Average RIPE Region AS path length visible: 4.1 Max RIPE Region AS path length visible: 34 Number of RIPE region 32-bit ASNs visible in the Routing Table: 7324 Number of RIPE addresses announced to Internet: 714069376 Equivalent to 42 /8s, 143 /16s and 213 /24s 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, 64396-64495 196608-210331 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: 91736 Total LACNIC prefixes after maximum aggregation: 20544 LACNIC Deaggregation factor: 4.47 Prefixes being announced from the LACNIC address blocks: 93193 Unique aggregates announced from the LACNIC address blocks: 40829 LACNIC Region origin ASes present in the Internet Routing Table: 7458 LACNIC Prefixes per ASN: 12.50 LACNIC Region origin ASes announcing only one prefix: 2060 LACNIC Region transit ASes present in the Internet Routing Table: 1398 Average LACNIC Region AS path length visible: 4.7 Max LACNIC Region AS path length visible: 26 Number of LACNIC region 32-bit ASNs visible in the Routing Table: 5006 Number of LACNIC addresses announced to Internet: 172006176 Equivalent to 10 /8s, 64 /16s and 155 /24s LACNIC AS Blocks 26592-26623, 27648-28671, 52224-53247, 61440-61951, 64099-64197, 262144-268700 + 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: 19431 Total AfriNIC prefixes after maximum aggregation: 4143 AfriNIC Deaggregation factor: 4.69 Prefixes being announced from the AfriNIC address blocks: 23464 Unique aggregates announced from the AfriNIC address blocks: 7986 AfriNIC Region origin ASes present in the Internet Routing Table: 1183 AfriNIC Prefixes per ASN: 19.83 AfriNIC Region origin ASes announcing only one prefix: 386 AfriNIC Region transit ASes present in the Internet Routing Table: 235 Average AfriNIC Region AS path length visible: 4.4 Max AfriNIC Region AS path length visible: 29 Number of AfriNIC region 32-bit ASNs visible in the Routing Table: 458 Number of AfriNIC addresses announced to Internet: 100231168 Equivalent to 5 /8s, 249 /16s and 104 /24s 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 4681 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4421 478 471 TPG-INTERNET-AP TPG Telecom Limited, AU 7552 2989 1154 86 VIETEL-AS-AP Viettel Group, VN 4766 2825 11135 768 KIXS-AS-KR Korea Telecom, KR 9829 2813 1495 541 BSNL-NIB National Internet Backbone, IN 45899 2569 1638 157 VNPT-AS-VN VNPT Corp, VN 9394 2541 4907 32 CTTNET China TieTong Telecommunications 17974 2262 962 71 TELKOMNET-AS2-AP PT Telekomunikasi Indo 9808 2252 8699 26 CMNET-GD Guangdong Mobile Communication 4755 2118 417 204 TATACOMM-AS TATA Communications formerl 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 6327 3448 1324 82 SHAW - Shaw Communications Inc., CA 11492 3268 253 411 CABLEONE - CABLE ONE, INC., US 22773 3228 2968 149 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 16509 2271 4808 773 AMAZON-02 - Amazon.com, Inc., US 18566 2166 405 109 MEGAPATH5-US - MegaPath Corporation, US 20115 2141 2652 505 CHARTER-NET-HKY-NC - Charter Communicat 209 2038 5085 604 CENTURYLINK-US-LEGACY-QWEST - Qwest Com 30036 2028 345 142 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom 16625 1995 1043 1463 AKAMAI-AS - Akamai Technologies, Inc., 7018 1774 20210 1283 ATT-INTERNET4 - AT&T Services, Inc., US 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 12479 4704 1613 125 UNI2-AS, ES 39891 3778 203 20 ALJAWWALSTC-AS, SA 8551 3099 378 44 BEZEQ-INTERNATIONAL-AS Bezeqint Interne 20940 2546 615 1892 AKAMAI-ASN1, US 12389 2042 1893 732 ROSTELECOM-AS, RU 34984 2015 335 507 TELLCOM-AS, TR 9121 1821 1692 19 TTNET, TR 13188 1604 100 43 TRIOLAN, UA 6849 1241 355 21 UKRTELNET, UA 8402 1205 544 14 CORBINA-AS OJSC "Vimpelcom", RU 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 8151 4884 3349 608 Uninet S.A. de C.V., MX 10620 3487 531 459 Telmex Colombia S.A., CO 11830 2657 369 78 Instituto Costarricense de Electricidad 6503 1665 444 63 Axtel, S.A.B. de C.V., MX 7303 1429 952 205 Telecom Argentina S.A., AR 28573 1084 2229 181 CLARO S.A., BR 3816 1022 510 117 COLOMBIA TELECOMUNICACIONES S.A. ESP, C 11172 929 126 85 Alestra, S. de R.L. de C.V., MX 18881 915 1080 32 TELEFÔNICA BRASIL S.A, BR 6147 907 377 31 Telefonica del Peru S.A.A., PE 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 1184 396 48 LINKdotNET-AS, EG 37611 895 107 9 Afrihost, ZA 36903 778 391 137 MT-MPLS, MA 36992 745 1411 40 ETISALAT-MISR, EG 24835 641 818 18 RAYA-AS, EG 8452 591 1728 14 TE-AS TE-AS, EG 37492 474 470 57 ORANGE-, TN 29571 463 70 13 ORANGE-COTE-IVOIRE, CI 37342 386 32 1 MOVITEL, MZ 23889 375 231 15 MauritiusTelecom, MU 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 8151 4884 3349 608 Uninet S.A. de C.V., MX 12479 4704 1613 125 UNI2-AS, ES 4538 4681 4192 74 ERX-CERNET-BKB China Education and Rese 7545 4421 478 471 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 203 20 ALJAWWALSTC-AS, SA 10620 3487 531 459 Telmex Colombia S.A., CO 6327 3448 1324 82 SHAW - Shaw Communications Inc., CA 11492 3268 253 411 CABLEONE - CABLE ONE, INC., US 22773 3228 2968 149 ASN-CXA-ALL-CCI-22773-RDC - Cox Communi 8551 3099 378 44 BEZEQ-INTERNATIONAL-AS Bezeqint Interne Complete listing at http://thyme.rand.apnic.net/current/data-ASnet Global Per AS Maximum Aggr summary ---------------------------------- ASN No of nets Net Savings Description 4538 4681 4607 ERX-CERNET-BKB China Education and Research Net 12479 4704 4579 UNI2-AS, ES 7545 4421 3950 TPG-INTERNET-AP TPG Telecom Limited, AU 39891 3778 3758 ALJAWWALSTC-AS, SA 6327 3448 3366 SHAW - Shaw Communications Inc., CA 22773 3228 3079 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 8551 3099 3055 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 10620 3487 3028 Telmex Colombia S.A., CO 7552 2989 2903 VIETEL-AS-AP Viettel Group, VN 11492 3268 2857 CABLEONE - CABLE ONE, INC., US Complete listing at http://thyme.rand.apnic.net/current/data-CIDRnet List of Unregistered Origin ASNs (Global) ----------------------------------------- Bad AS Designation Network Transit AS Description 230105 UNALLOCATED 38.110.79.0/24 23015 CMC180-TOR-AS - Cambridge Merc 64500 DOCUMENT 45.43.56.0/24 135391 AOFEI-HK AOFEI DATA INTERNATIO 266842 UNALLOCATED 45.238.156.0/22 265680 HNTELCO S.A, HN 65001 PRIVATE 46.237.40.0/21 13118 ASN-YARTELECOM PJSC Rostelecom 64513 PRIVATE 62.150.101.0/24 9155 QNET Kuwait, KW 65537 DOCUMENT 62.162.120.0/24 6821 MT-AS-OWN bul. Orce Nikolov bb 64121 UNALLOCATED 98.159.9.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64121 UNALLOCATED 98.159.12.0/24 19555 KMI-NETWORK - Kinder Morgan, I 64140 UNALLOCATED 98.159.14.0/24 64121 UNKNOWN 4259905537 PRIVATE 103.250.48.0/24 132917 YELLOWPAGESGROUP-AS-AP Yellow Complete listing at http://thyme.rand.apnic.net/current/data-badAS Prefixes from private and non-routed address space (Global) ----------------------------------------------------------- Prefix Origin AS Description 100.66.224.0/19 209 CENTURYLINK-US-LEGACY-QWEST - Qwest Communicati 198.18.1.19/32 7497 CSTNET-AS-AP Computer Network Information Cente Complete listing at http://thyme.rand.apnic.net/current/data-dsua Advertised Unallocated Addresses -------------------------------- Network Origin AS Description 27.100.7.0/24 56096 UNKNOWN 41.76.136.0/22 37500 -Reserved AS-, ZZ 41.76.136.0/24 37500 -Reserved AS-, ZZ 41.76.138.0/24 37500 -Reserved AS-, ZZ 41.76.139.0/24 37500 -Reserved AS-, ZZ 41.76.140.0/22 37500 -Reserved AS-, ZZ 41.78.92.0/22 14988 BTC-GATE1, BW 41.78.180.0/23 37265 -Reserved AS-, ZZ 43.251.20.0/22 9381 WTT-AS-AP WTT HK Limited, HK 45.121.32.0/22 134356 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:14 /9:11 /10:36 /11:99 /12:291 /13:570 /14:1096 /15:1900 /16:13370 /17:7932 /18:13806 /19:25374 /20:39278 /21:45530 /22:88363 /23:71758 /24:400129 /25:799 /26:603 /27:624 /28:35 /29:20 /30:19 /31:4 /32:52 Advertised prefixes smaller than registry allocations ----------------------------------------------------- ASN No of nets Total ann. Description 12479 3455 4704 UNI2-AS, ES 6327 3238 3448 SHAW - Shaw Communications Inc., CA 39891 2946 3778 ALJAWWALSTC-AS, SA 11492 2623 3268 CABLEONE - CABLE ONE, INC., US 8551 2561 3099 BEZEQ-INTERNATIONAL-AS Bezeqint Internet Backbo 22773 2497 3228 ASN-CXA-ALL-CCI-22773-RDC - Cox Communications 18566 2060 2166 MEGAPATH5-US - MegaPath Corporation, US 11830 2005 2657 Instituto Costarricense de Electricidad y Telec 30036 1780 2028 MEDIACOM-ENTERPRISE-BUSINESS - Mediacom Communi 10620 1580 3487 Telmex Colombia S.A., CO Complete listing at http://thyme.rand.apnic.net/current/data-sXXas-nos Number of /24s announced per /8 block (Global) ---------------------------------------------- 1:1616 2:827 4:18 5:2861 6:43 7:1 8:1125 12:1871 13:210 14:1796 15:32 16:3 17:191 18:54 20:51 23:2489 24:2341 25:2 27:2478 31:2012 32:88 35:29 36:522 37:2896 38:1495 39:257 40:118 41:3191 42:702 43:1975 44:120 45:5363 46:3116 47:199 49:1339 50:1054 51:318 52:1088 54:368 55:1 56:12 57:39 58:1629 59:992 60:406 61:2113 62:1870 63:1790 64:5078 65:2201 66:4716 67:2673 68:1147 69:3306 70:1157 71:582 72:2191 74:2724 75:416 76:464 77:1650 78:1690 79:2253 80:1569 81:1393 82:1065 83:782 84:1034 85:1998 86:561 87:1364 88:908 89:2355 90:214 91:6434 92:1260 93:2377 94:2406 95:2961 96:901 97:355 98:935 99:133 100:84 101:989 102:184 103:18502 104:3533 105:215 106:769 107:1769 108:710 109:3324 110:1645 111:1800 112:1337 113:1306 114:1130 115:1646 116:1655 117:1775 118:2214 119:1659 120:1015 121:1043 122:2423 123:1725 124:1447 125:1920 128:1129 129:671 130:494 131:1620 132:732 133:190 134:1003 135:232 136:507 137:651 138:1942 139:677 140:475 141:737 142:851 143:1000 144:810 145:476 146:1230 147:735 148:1643 149:757 150:756 151:1097 152:825 153:323 154:1489 155:800 156:1464 157:799 158:657 159:1840 160:1312 161:810 162:2633 163:605 164:1077 165:1552 166:462 167:1257 168:3150 169:831 170:3859 171:492 172:1007 173:2087 174:971 175:796 176:2029 177:4013 178:2501 179:1269 180:2180 181:2412 182:2350 183:1254 184:1062 185:13979 186:3538 187:2425 188:2899 189:2000 190:8157 191:1354 192:9803 193:6103 194:5017 195:3992 196:2743 197:1612 198:5573 199:5914 200:7435 201:4876 202:10293 203:10269 204:4571 205:2903 206:3197 207:3209 208:3933 209:4027 210:3884 211:1998 212:3044 213:2818 214:1037 215:56 216:5999 217:2130 218:860 219:567 220:1807 221:998 222:971 223:1372 End of report

1 0

Microsoft - list of Azure DNS servers
by Ryan Finnesey 24 Aug '18

24 Aug '18

I am looking for someone from Microsoft to contact me off list. I am looking for a complete list of Azure DNS servers. Cheers Ryan

1 0

IPv6 Management
by Justin Wilson 23 Aug '18

23 Aug '18

We were having an interesting debate on IPV6 management on layer2 devices. Does anyone have a best practice document they have seen for utilizing v6 Management addresses? I know Cisco has some extensive documentation on using v6 on their wireless products. I know everyone has thoughts so am interested in any best practices which have been presented to the community. I haven’t worried about management access on layer2 devices, as long as the layer2 devices can pass any cast, multicast, and other things v6 needs. However, I could see why you would want v6 management addresses. And go…. Justin Wilson j2sw(a)mtin.net www.mtin.net www.midwest-ix.com

4 3

Re: Hurricane Lane: Catagory 5 storm forecast to sideswipe Hawaii
by Scott Weeks 22 Aug '18

22 Aug '18

--- sean(a)donelan.com wrote: From: Sean Donelan <sean(a)donelan.com> Hurricane warnings have been issued for Hurricane Lane, which strengthened to a catagory 5 storm on Tuesday. The forecast cone of uncertainity shows the path sideswiping Hawaii on Thursday. ------------------------------------------- Yep, this one's closer than the other 2-3 weeks ago. I thought about sending another 'dust off your DR plan' for those networks doing business in the AP region that have stuff here, but if they didn't on the last one they wouldn't on this one, either. :-) It's an M (>110 MPH) until the Big Island on Thur and then goes down to a regular hurricane Friday when it hits Maui and Oahu Friday. http://www.prh.noaa.gov/cphc/tcpages/?product=5day_cone_with_line_and_wind&… http://weather.hawaii.edu/satellite/jsanim.cgi?res=4km&chnl=ir&domain=nep&p… scott

1 0

Hurricane Lane: Catagory 5 storm forecast to sideswipe Hawaii
by Sean Donelan 22 Aug '18

22 Aug '18

Hurricane warnings have been issued for Hurricane Lane, which strengthened to a catagory 5 storm on Tuesday. The forecast cone of uncertainity shows the path sideswiping Hawaii on Thursday.

1 0

Re: NANOG Digest, Vol 127, Issue 16
by Saymon Araújo 22 Aug '18

22 Aug '18

- PRTG, it's realy easy to configure. Most of the senssors are SNMP of: traffic/ping/cpu/memory and some senssors for servers like DNS and Radius, etc. - Zabbix, there's 2 things that made us use Zabbix, the first one it's Zabbix Proxy, since the network it's geographical distribuited we need a tool that provides us monitoring from another places with a low price. And LLD that i use for monitoring BGP/OSPF sessions and prefix. - Elastiflow - For Syslog we use Graylog, that i recomend, it's a excelente tool for monitoring syslog messages and there's a lot of features such as extractors, streams and alerts. I think that PRTG it's kind expensive solution ( if you buy the license ), but provides a easy way to monitor a lot of things. Just one thing, if your license expires your are no able to update your software and if you want to buy the license for upgrade, the days without the license counts as negative days, i never seen that before, like, if you don't update the license for 1 year and bought the 3 years lisence, you will got 2 years of support and upgrade. Atenciosamente, Em sex, 17 de ago de 2018 às 09:00, <nanog-request(a)nanog.org> escreveu: > Send NANOG mailing list submissions to > nanog(a)nanog.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://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. Re: What NMS do you use and why? (Nick Peelman) > 2. Re: What NMS do you use and why? (Joe Loiacono) > 3. RE: What NMS do you use and why? (Stan Ouchakov) > 4. Re: What NMS do you use and why? (Nick Peelman) > 5. Re: What NMS do you use and why? (Kushal) > 6. RE: What NMS do you use and why? (Michael Braun (michbrau)) > 7. Re: What NMS do you use and why? (Nick W) > 8. Akamia Contact (Romeo Czumbil) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 15 Aug 2018 23:14:32 +0000 > From: Nick Peelman <npeelman(a)ETC1.net> > To: Colton Conor <colton.conor(a)gmail.com> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: What NMS do you use and why? > Message-ID: <D0CDB355-16C7-49E1-9FD6-EDFFB618CC70(a)ETC1.net> > Content-Type: text/plain; charset="Windows-1252" > > I think anybody looking for a be-all-end-all solution will find nothing > but heartburn. > > different suites have different strong suits, and deciding you are going > to pursue one and ignore all others may mean living without a feature or > set of features you may find really useful or eventually necessary. but > maintaining multiple complete NMSes isn’t really tenable either. > > all of that said, we use a combination of a couple. Nagios/Icinga because > it’s been around forever (both in the world and in our network), and the > power of script based checks, being able to write your own handlers and > pretty much just leverage it as a framework you can shove questions into > and get regular answers from is invaluable. > > LibreNMS gives us the best pretty pictures, letting us monitor much much > more than just interface traffic, out of the box. much more than cacti is > capable of without a ton of work (i.e. down to the tx/rx power and > temperature readings of individual SFPs). it scales relatively well; at > least in theory. i will be able to tell you for sure later this year as we > are near the limits of what we can monitor with a single polling device. > alerting out of Libre into Slack has proven quite fantastic. we can spawn > threads attached to anything from a BGP peer dropping or a CPU alert as we > move to triage and solve, even if we are in the field or meetings or > whatever. > > we also still have cacti around for random one-offs. as great as Libre is, > its poller can be a bit intense for some devices; so in those cases it’s > safer for us to just have cacti graph the one or two OIDs we need > specifically, without trolling all the other available sensors. > > we ran OpenNMS for a bit, but it proved way to dumb to maintain a large > (and growing) complex network, without dedicating at least one or two > people to the care and feeding of it. > > -nick > > — > Nick Peelman > Network Engineer | Enhanced Telecommunications Corp. > 812-222-0169<tel:812-222-0169> | npeelman(a)etc1.net<mailto: > npeelman(a)etc1.net> | www.etczone.com<http://www.etczone.com/> > > Sent from my iPhone > > On Aug 15, 2018, at 09:49, Colton Conor <colton.conor(a)gmail.com<mailto: > colton.conor(a)gmail.com>> wrote: > > We are looking for a new network monitoring system. Since there are so > many operators on this list, I would like to know which NMS do you use and > why? Is there one that you really like, and others that you hate? > > For free options (opensouce), LibreNMS and NetXMS come highly recommended > by many wireless ISPs on low budgets. However, I am not sure the commercial > options available nor their price points. > > > > > ------------------------------ > > Message: 2 > Date: Wed, 15 Aug 2018 20:31:13 -0400 (EDT) > From: Joe Loiacono <jloiacon(a)gmail.com> > To: William Herrin <bill(a)herrin.us> > Cc: NANOG <nanog(a)nanog.org>, Colton Conor <colton.conor(a)gmail.com> > Subject: Re: What NMS do you use and why? > Message-ID: > <593335944.184.1534379472982.JavaMail.jloia@DESKTOP-FDMC6S8> > Content-Type: text/plain; charset=utf-8 > > Consider also open-source FlowViewer for netflow capture and analysis. A > lot of very useful netflow based analytical tools in an easy UI. Sits on > top of a robust set of Carnegie-Mellon's high-capacity SiLK netflow tools. > > https://sourceforge.net/projects/flowviewer/ > > Joe > > > > ----- Original Message ----- > From: "William Herrin" <bill(a)herrin.us> > To: "Colton Conor" <colton.conor(a)gmail.com> > Cc: "NANOG" <nanog(a)nanog.org> > Sent: Wednesday, August 15, 2018 3:25:48 PM > Subject: Re: What NMS do you use and why? > > On Wed, Aug 15, 2018 at 9:49 AM, Colton Conor <colton.conor(a)gmail.com> > wrote: > > We are looking for a new network monitoring system. Since there are so > many > > operators on this list, I would like to know which NMS do you use and > why? > > Is there one that you really like, and others that you hate? > > I still use a tool I wrote in perl nearly 20 years ago called > "MrPing." MrPing handles multi-dependency graphs. > > Consider: > > A is reachable via either B or C. > > If A and B are down but C is up, A being down is a separate failure > from B being down. I need to know about both. > > If B and C are both down, A is unreachable. I don't want to receive > alerts about A because they'll distract me from the root cause of the > problem: that both B and C are down. The NMS should record that A is > unreachable but it should also tell me that A being unreachable is a > dependent failure that I can ignore until I fix the failures it > depends on. > > > The NMSes I've paid attention to either don't support dependencies > well at all or support only simple hierarchical dependencies. > Resilient, professional networks simply aren't built that way. > > Regards, > Bill Herrin > > > -- > William Herrin ................ herrin(a)dirtside.com bill(a)herrin.us > Dirtside Systems ......... Web: <http://www.dirtside.com/> > > > ------------------------------ > > Message: 3 > Date: Thu, 16 Aug 2018 15:39:52 +0000 > From: Stan Ouchakov <stano(a)imaginesoftware.com> > To: Joe Loiacono <jloiacon(a)gmail.com>, William Herrin <bill(a)herrin.us> > Cc: NANOG <nanog(a)nanog.org> > Subject: RE: What NMS do you use and why? > Message-ID: <e12e489f5c6c4837bd2cee6efe9cb3e0(a)imaginesoftware.com> > Content-Type: text/plain; charset="utf-8" > > Regarding netflow/sflow/ipfix monitoring, we had recently started using > elastiflow by Robert Cowart. Scales very well with pretty visualizations. > Cannot imagine what paid / supported version has to offer :) > > https://github.com/robcowart/elastiflow > > > > -----Original Message----- > From: NANOG <nanog-bounces(a)nanog.org> On Behalf Of Joe Loiacono > Sent: Wednesday, August 15, 2018 8:31 PM > To: William Herrin <bill(a)herrin.us> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: What NMS do you use and why? > > Consider also open-source FlowViewer for netflow capture and analysis. A > lot of very useful netflow based analytical tools in an easy UI. Sits on > top of a robust set of Carnegie-Mellon's high-capacity SiLK netflow tools. > > https://sourceforge.net/projects/flowviewer/ > > Joe > > > > ----- Original Message ----- > From: "William Herrin" <bill(a)herrin.us> > To: "Colton Conor" <colton.conor(a)gmail.com> > Cc: "NANOG" <nanog(a)nanog.org> > Sent: Wednesday, August 15, 2018 3:25:48 PM > Subject: Re: What NMS do you use and why? > > On Wed, Aug 15, 2018 at 9:49 AM, Colton Conor <colton.conor(a)gmail.com> > wrote: > > We are looking for a new network monitoring system. Since there are so > > many operators on this list, I would like to know which NMS do you use > and why? > > Is there one that you really like, and others that you hate? > > I still use a tool I wrote in perl nearly 20 years ago called "MrPing." > MrPing handles multi-dependency graphs. > > Consider: > > A is reachable via either B or C. > > If A and B are down but C is up, A being down is a separate failure from B > being down. I need to know about both. > > If B and C are both down, A is unreachable. I don't want to receive alerts > about A because they'll distract me from the root cause of the > problem: that both B and C are down. The NMS should record that A is > unreachable but it should also tell me that A being unreachable is a > dependent failure that I can ignore until I fix the failures it depends on. > > > The NMSes I've paid attention to either don't support dependencies well at > all or support only simple hierarchical dependencies. > Resilient, professional networks simply aren't built that way. > > Regards, > Bill Herrin > > > -- > William Herrin ................ herrin(a)dirtside.com bill(a)herrin.us > Dirtside Systems ......... Web: <http://www.dirtside.com/> > > ------------------------------ > > Message: 4 > Date: Thu, 16 Aug 2018 15:42:44 +0000 > From: Nick Peelman <npeelman(a)ETC1.net> > To: Stan Ouchakov <stano(a)imaginesoftware.com> > Cc: Joe Loiacono <jloiacon(a)gmail.com>, William Herrin > <bill(a)herrin.us>, NANOG <nanog(a)nanog.org> > Subject: Re: What NMS do you use and why? > Message-ID: <61BD4D17-F5EB-46AC-BEE2-5D289FECDDBD(a)ETC1.net> > Content-Type: text/plain; charset="Windows-1252" > > seconded. the pains of maintaining ELK are made worthwhile by this alone. > > -nick > > — > Nick Peelman > Network Engineer | Enhanced Telecommunications Corp. > 812-222-0169<tel:812-222-0169> | npeelman(a)etc1.net<mailto: > npeelman(a)etc1.net> | www.etczone.com<http://www.etczone.com/> > > Sent from my iPhone > > On Aug 16, 2018, at 11:41, Stan Ouchakov <stano(a)imaginesoftware.com > <mailto:stano@imaginesoftware.com>> wrote: > > Regarding netflow/sflow/ipfix monitoring, we had recently started using > elastiflow by Robert Cowart. Scales very well with pretty visualizations. > Cannot imagine what paid / supported version has to offer :) > > https://github.com/robcowart/elastiflow > > > > -----Original Message----- > From: NANOG <nanog-bounces(a)nanog.org<mailto:nanog-bounces@nanog.org>> On > Behalf Of Joe Loiacono > Sent: Wednesday, August 15, 2018 8:31 PM > To: William Herrin <bill(a)herrin.us<mailto:bill@herrin.us>> > Cc: NANOG <nanog(a)nanog.org<mailto:nanog@nanog.org>> > Subject: Re: What NMS do you use and why? > > Consider also open-source FlowViewer for netflow capture and analysis. A > lot of very useful netflow based analytical tools in an easy UI. Sits on > top of a robust set of Carnegie-Mellon's high-capacity SiLK netflow tools. > > https://sourceforge.net/projects/flowviewer/ > > Joe > > > > ----- Original Message ----- > From: "William Herrin" <bill(a)herrin.us<mailto:bill@herrin.us>> > To: "Colton Conor" <colton.conor(a)gmail.com<mailto:colton.conor@gmail.com>> > Cc: "NANOG" <nanog(a)nanog.org<mailto:nanog@nanog.org>> > Sent: Wednesday, August 15, 2018 3:25:48 PM > Subject: Re: What NMS do you use and why? > > On Wed, Aug 15, 2018 at 9:49 AM, Colton Conor <colton.conor(a)gmail.com > <mailto:colton.conor@gmail.com>> wrote: > We are looking for a new network monitoring system. Since there are so > many operators on this list, I would like to know which NMS do you use and > why? > Is there one that you really like, and others that you hate? > > I still use a tool I wrote in perl nearly 20 years ago called "MrPing." > MrPing handles multi-dependency graphs. > > Consider: > > A is reachable via either B or C. > > If A and B are down but C is up, A being down is a separate failure from B > being down. I need to know about both. > > If B and C are both down, A is unreachable. I don't want to receive alerts > about A because they'll distract me from the root cause of the > problem: that both B and C are down. The NMS should record that A is > unreachable but it should also tell me that A being unreachable is a > dependent failure that I can ignore until I fix the failures it depends on. > > > The NMSes I've paid attention to either don't support dependencies well at > all or support only simple hierarchical dependencies. > Resilient, professional networks simply aren't built that way. > > Regards, > Bill Herrin > > > -- > William Herrin ................ herrin(a)dirtside.com<mailto: > herrin(a)dirtside.com> bill(a)herrin.us<mailto:bill@herrin.us> Dirtside > Systems ......... Web: <http://www.dirtside.com/> > > > ------------------------------ > > Message: 5 > Date: Thu, 16 Aug 2018 22:19:35 +0530 > From: Kushal <kushal.r(a)h4g.co> > To: Stan Ouchakov <stano(a)imaginesoftware.com>, Nick Peelman > <npeelman(a)etc1.net> > Cc: NANOG <nanog(a)nanog.org> > Subject: Re: What NMS do you use and why? > Message-ID: <etPan.5b75ab1f.dbb654b.3ad(a)h4g.co> > Content-Type: text/plain; charset="utf-8" > > Being a small business we like to use a mostly free and open source tools. > Our networking monitoring stack presently looks like: > > Simple Reachability Monitoring (Ping) - uptimerobot.com > > Just $4.5 per month for 50 monitors with 1 minute intervals (free if you > are find with 5 minutes monitoring intervals). This is connected to our > slack channel and also sends SMS when something goes offline. > > Traffic & Device Monitoring - LibreNMS > > A fork of Observium but adds the much needed alerting feature that > observing only offers with it's paid plans. We use it to monitor switch > port traffic, BGP sessions, device health, etc. > > Packet Inspection or Flow Monitoring we use FastNetMon ( > https://fastnetmon.com/features/) the free edition is good for our needs. > > > On August 16, 2018 at 9:16:42 PM, Nick Peelman (npeelman(a)etc1.net) wrote: > > seconded. the pains of maintaining ELK are made worthwhile by this alone. > > -nick > > — > Nick Peelman > Network Engineer | Enhanced Telecommunications Corp. > 812-222-0169<tel:812-222-0169> | npeelman(a)etc1.net<mailto: > npeelman(a)etc1.net> | www.etczone.com<http://www.etczone.com/> > > Sent from my iPhone > > On Aug 16, 2018, at 11:41, Stan Ouchakov <stano(a)imaginesoftware.com > <mailto:stano@imaginesoftware.com>> wrote: > > Regarding netflow/sflow/ipfix monitoring, we had recently started using > elastiflow by Robert Cowart. Scales very well with pretty visualizations. > Cannot imagine what paid / supported version has to offer :) > > https://github.com/robcowart/elastiflow > > > > -----Original Message----- > From: NANOG <nanog-bounces(a)nanog.org<mailto:nanog-bounces@nanog.org>> On > Behalf Of Joe Loiacono > Sent: Wednesday, August 15, 2018 8:31 PM > To: William Herrin <bill(a)herrin.us<mailto:bill@herrin.us>> > Cc: NANOG <nanog(a)nanog.org<mailto:nanog@nanog.org>> > Subject: Re: What NMS do you use and why? > > Consider also open-source FlowViewer for netflow capture and analysis. A > lot of very useful netflow based analytical tools in an easy UI. Sits on > top of a robust set of Carnegie-Mellon's high-capacity SiLK netflow tools. > > https://sourceforge.net/projects/flowviewer/ > > Joe > > > > ----- Original Message ----- > From: "William Herrin" <bill(a)herrin.us<mailto:bill@herrin.us>> > To: "Colton Conor" <colton.conor(a)gmail.com<mailto:colton.conor@gmail.com>> > > Cc: "NANOG" <nanog(a)nanog.org<mailto:nanog@nanog.org>> > Sent: Wednesday, August 15, 2018 3:25:48 PM > Subject: Re: What NMS do you use and why? > > On Wed, Aug 15, 2018 at 9:49 AM, Colton Conor <colton.conor(a)gmail.com > <mailto:colton.conor@gmail.com>> wrote: > We are looking for a new network monitoring system. Since there are so > many operators on this list, I would like to know which NMS do you use and > why? > Is there one that you really like, and others that you hate? > > I still use a tool I wrote in perl nearly 20 years ago called "MrPing." > MrPing handles multi-dependency graphs. > > Consider: > > A is reachable via either B or C. > > If A and B are down but C is up, A being down is a separate failure from B > being down. I need to know about both. > > If B and C are both down, A is unreachable. I don't want to receive alerts > about A because they'll distract me from the root cause of the > problem: that both B and C are down. The NMS should record that A is > unreachable but it should also tell me that A being unreachable is a > dependent failure that I can ignore until I fix the failures it depends > on. > > > The NMSes I've paid attention to either don't support dependencies well at > all or support only simple hierarchical dependencies. > Resilient, professional networks simply aren't built that way. > > Regards, > Bill Herrin > > > -- > William Herrin ................ herrin(a)dirtside.com<mailto: > herrin(a)dirtside.com> bill(a)herrin.us<mailto:bill@herrin.us> Dirtside > Systems ......... Web: <http://www.dirtside.com/> >

1 0

optical circulator as a bidirectional one fiber solution
by Baldur Norddahl 22 Aug '18

22 Aug '18

Hello There is a lack of bidirectional one fiber (BIDI) options for 40G and 100G optics. Usually BIDI is implemented using two CWDM wavelengths, one for tx and one for rx. However there is also a lack of CWDM and DWDM options for 40G and 100G. Would it be possible to use an optical circulator like this one (customized to 1310 nm)? https://www.fs.com/de/en/products/33364.html Combined with a traditional two fiber 1310 nm 10 km 40G QSFP module like this: https://www.fs.com/de/en/products/24422.html The link distance would be 5 km. The optical circulator separates tx and rx by the direction the light travels in. It would work even though both directions use the same wavelength. There will likely be some reflection but hopefully attenuated enough that it is regarded as background noise. Has anyone done this? Any reason it would not work? Regards, Baldur

8 10