NZNOG January 1999

nznog@list.waikato.ac.nz

10 participants
14 discussions

RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic

by Warwick GLENDENNING

> > On Mon, Jan 25, 1999 at 01:05:11PM +1300, Warwick GLENDENNING wrote: > > We(Waikato) currently still use OSPF on NZIX to collect NZ > routes. And this > > is vital to our traffic metering. A new metering system is > being built to > > use BGP4 to download NZ routes from our traffic provider. > Once this has been > > done, we will be very keen to download NZ routes from major > ISPs on NZIX and > > OSPF can be decommissioned. > > Supposing that a general agreement to move to BGP was made > earlier than > your planned roll-out - presumably as long as Telecom were > able to make > the NZ table available on OSPF to you, your requirements > would be satisifed? > This is true. > There is no particular necessity for us all to speak OSPF, > right? I would > assume that your particular requirements were an issue > between you and your > service provider, and not a general exchange issue. > > Just exploring ideas :) > This is true too. We only provide layer 2 connectivity. ISPs on NZIX don't have to follow some certain routing protocol. It should depend on their interest. But it should be said that Kawaihiko had multiple service providers and NZIX was the place where most of domestic traffic got exchanged. It's why Waikato has used OSPF to collect NZ routes from NZIX. Since Kawaihiko network broke up, we have been trying to build a new way to meter traffic. It will be appreciated very much if Clear can keep OSPF running until we have rolled out the new metering system. Regards Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 8 months

IOS configuration lint script

by Joe Abley

[This message has also been posted.] Hi, At various times I have been involved in maintaining routers with lots of (sub)interfaces, and lots of static routes pointing down those subinterfaces. Unfortunately, a simple "show run" on a router produces a listing with all the static routes listed together, and all the subinterfaces listed separately. On a router with a lot of static routes and a lot of connected networks, this becomes a bit of a headache - you end up with static routes hanging around long after the subinterface has been removed, and spring cleaning usually results at least a couple of confused and unhappy users for whom inbound traffic is now spiralling off somewhere else. Even when this kind of configuration is made automatically (from a database which enforces referential integrity), the odd quick-fix static route added at some time might well hang around for years after it has stopped being useful. I have often wished that I could do a "show run" which would group IOS configuration by customer. Now I can! Hooray! Take an IOS configuration file (as tftp'd or rsh'd somewhere, or perhaps retrieved using ciscoconfd) and pass it through this awk script. The configuration will be re-sorted, so that: + most configuration comes first + (sub)interface configuration comes next, with corresponding static routes + all other static routes come next + "end" The static routes corresponding to a connected (sub)interface are hence shown grouped with that subinterface. All static routes that don't point at a connected network are listed separately right at the end, where they can be scruitinised and (if appropriate) removed. Example: The following stripped-down configuration: version 11.1 service timestamps log datetime localtime service password-encryption no service udp-small-servers no service tcp-small-servers ! hostname eg ! clock timezone NZST 12 clock summer-time NZDT recurring 1 Sun Oct 2:00 3 Sun Mar 2:00 enable secret 5 hohoho ! interface ATM5/0 mtu 1500 no ip address no ip route-cache optimum atm ilmi-keepalive 30 atm pvc 999 0 16 ilmi ! interface ATM5/0.2 point-to-point description customer1's network ip address 192.168.24.1 255.255.255.252 atm pvc 502 2 120 aal5snap inarp ! interface ATM5/0.3 point-to-point description customer2's network ip address 192.168.24.5 255.255.255.252 atm pvc 503 2 51 aal5snap inarp ! interface ATM5/0.4 point-to-point description customer3's network ip address 192.168.24.9 255.255.255.252 atm pvc 504 2 52 aal5snap inarp ! interface ATM5/0.5 point-to-point description customer4's network ip address 192.168.24.13 255.255.255.252 atm pvc 505 2 53 aal5snap inarp ! ip name-server 203.97.33.1 ip name-server 203.97.37.1 ip classless ip route 10.1.4.0 255.255.252.0 192.168.24.14 ip route 172.16.0.0 255.255.0.0 192.168.24.6 ip route 172.18.0.0 255.255.0.0 192.168.24.2 ip route 192.168.25.0 255.255.255.0 192.168.24.14 ip route 192.168.27.0 255.255.255.0 192.168.24.42 ! line con 0 exec-timeout 0 0 length 20 line aux 0 line vty 0 4 exec-timeout 0 0 password 7 humhumhum length 25 ! end When run through ios-lint.awk, we get: ! generated by cisco_lint.awk ! version 11.1 service timestamps log datetime localtime service password-encryption no service udp-small-servers no service tcp-small-servers ! hostname eg ! clock timezone NZST 12 clock summer-time NZDT recurring 1 Sun Oct 2:00 3 Sun Mar 2:00 enable secret 5 hohoho ! ip name-server 203.97.33.1 ip name-server 203.97.37.1 ip classless ! line con 0 exec-timeout 0 0 length 20 line aux 0 line vty 0 4 exec-timeout 0 0 password 7 humhumhum length 25 ! interface ATM5/0 mtu 1500 no ip address no ip route-cache optimum atm ilmi-keepalive 30 atm pvc 999 0 16 ilmi ! interface ATM5/0.2 point-to-point description customer1's network ip address 192.168.24.1 255.255.255.252 atm pvc 502 2 120 aal5snap inarp ! ip route 172.18.0.0 255.255.0.0 192.168.24.2 ! interface ATM5/0.3 point-to-point description customer2's network ip address 192.168.24.5 255.255.255.252 atm pvc 503 2 51 aal5snap inarp ! ip route 172.16.0.0 255.255.0.0 192.168.24.6 ! interface ATM5/0.4 point-to-point description customer3's network ip address 192.168.24.9 255.255.255.252 atm pvc 504 2 52 aal5snap inarp ! interface ATM5/0.5 point-to-point description customer4's network ip address 192.168.24.13 255.255.255.252 atm pvc 505 2 53 aal5snap inarp ! ip route 10.1.4.0 255.255.252.0 192.168.24.14 ip route 192.168.25.0 255.255.255.0 192.168.24.14 ! ! ! The following static routes do not point to a connected interface. ! Some of these might be worth looking at more closely :) ! ip route 192.168.27.0 255.255.255.0 192.168.24.42 ! end Much nicer :) Anyway, sorry about all the bandwidth - script is at: http://www.patho.gen.nz/pub/users/jabley/ios-lint.awk Feedback welcome. Share and enjoy. Joe -- Joe Abley <jabley(a)clear.co.nz> I am not speaking for CLEAR. In fact, Network Architect, CLEAR Net I'm not speaking at all. I'm typing. --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 8 months

RE: BGP over NZIX

by Warwick GLENDENNING

Hi Felix Your email implies that you are waiting only for Waikato to implement BGP at NZIX. This does not appear to be a fair call, as no one else on the mailing list that Joe Abley posted to has made any comment on whether they would BGP peer or not at NZIX and especially the largest ISP in NZ Telecom. Regards Warwick -----Original Message----- From: tossan(a)us.ibm.com [mailto:tossan@us.ibm.com] Sent: Tuesday, 26 January 1999 08:19 To: WarwickG(a)waikato.ac.nz Cc: abley(a)clear.co.nz; nznog(a)list.waikato.ac.nz; lindsayp(a)agresearch.cri.nz; p.wilson(a)comnet.co.nz; steve(a)webmasters.co.nz; bpearson(a)telstra.co.nz; colinb(a)nz1.ibm.com; skatta(a)nz1.ibm.com; bowden(a)nz1.ibm.com; cholmes(a)telstra.co.nz Subject: BGP over NZIX IBM Global Network position re peering protocol, as explained earlier in teleconf, is we peer exclusively using BGP-4. We see no nationale in using OSPF to collect and distribute interprovider routes. In fact we have started to use BGP Communities within our global Internet BB to direct routes which previously was done by OSPF, thus further reducing OSPF role. Under the NZIX switching network we wish to pursue BGP peerings with all ISPs there who are capable, including Waikato. We await for Waikato to fully implement its BGP capability. Felix Tossan ---------------------- Forwarded by Felix Tossan/White Plains/IBM on 01/25/99 01:59 PM --------------------------- Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> on 01/24/99 07:05:11 PM To: "'Joe Abley'" <jabley(a)clear.co.nz>, Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> cc: nznog(a)list.waikato.ac.nz, "'lindsayp(a)agresearch.cri.nz'" <lindsayp(a)agresearch.cri.nz>, "'p.wilson(a)comnet.co.nz'" <p.wilson(a)comnet.co.nz>, "'steve(a)webmasters.co.nz'" <steve(a)webmasters.co.nz>, Felix Tossan/White Plains/IBM, bpearson(a)telstra.co.nz, colinb(a)nz1.ibm.com, skatta(a)nz1.ibm.com, bowden(a)nz1.ibm.com, cholmes(a)telstra.co.nz Subject: RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic We(Waikato) currently still use OSPF on NZIX to collect NZ routes. And this is vital to our traffic metering. A new metering system is being built to use BGP4 to download NZ routes from our traffic provider. Once this has been done, we will be very keen to download NZ routes from major ISPs on NZIX and OSPF can be decommissioned. Regards Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 8 months

BGP over NZIX

by tossan＠us.ibm.com

IBM Global Network position re peering protocol, as explained earlier in teleconf, is we peer exclusively using BGP-4. We see no nationale in using OSPF to collect and distribute interprovider routes. In fact we have started to use BGP Communities within our global Internet BB to direct routes which previously was done by OSPF, thus further reducing OSPF role. Under the NZIX switching network we wish to pursue BGP peerings with all ISPs there who are capable, including Waikato. We await for Waikato to fully implement its BGP capability. Felix Tossan ---------------------- Forwarded by Felix Tossan/White Plains/IBM on 01/25/99 01:59 PM --------------------------- Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> on 01/24/99 07:05:11 PM To: "'Joe Abley'" <jabley(a)clear.co.nz>, Warwick GLENDENNING <WarwickG(a)waikato.ac.nz> cc: nznog(a)list.waikato.ac.nz, "'lindsayp(a)agresearch.cri.nz'" <lindsayp(a)agresearch.cri.nz>, "'p.wilson(a)comnet.co.nz'" <p.wilson(a)comnet.co.nz>, "'steve(a)webmasters.co.nz'" <steve(a)webmasters.co.nz>, Felix Tossan/White Plains/IBM, bpearson(a)telstra.co.nz, colinb(a)nz1.ibm.com, skatta(a)nz1.ibm.com, bowden(a)nz1.ibm.com, cholmes(a)telstra.co.nz Subject: RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic We(Waikato) currently still use OSPF on NZIX to collect NZ routes. And this is vital to our traffic metering. A new metering system is being built to use BGP4 to download NZ routes from our traffic provider. Once this has been done, we will be very keen to download NZ routes from major ISPs on NZIX and OSPF can be decommissioned. Regards Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 8 months

RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic

by Warwick GLENDENNING

We(Waikato) currently still use OSPF on NZIX to collect NZ routes. And this is vital to our traffic metering. A new metering system is being built to use BGP4 to download NZ routes from our traffic provider. Once this has been done, we will be very keen to download NZ routes from major ISPs on NZIX and OSPF can be decommissioned. Regards Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 9 months

RE: BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic

by Warwick GLENDENNING

For our customers we apply community tags to routes so that customers can differentiate between routes learnt from off-shore BGP peers, and those learnt from within NZ - I would imagine that Telecom can do something similar for you. I would keen to hear Telecom NZ view as they seem to have been very quiet on this topic? Warwick --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 9 months

BGP over NZIX -comments from Waikato about Joe Ableys posting on this topic

by Warwick GLENDENNING

Waikato has no objection to carriers or ISP's running BGP meshes at the NZIX if it provides a more robust service. However from Waikato's perspective (and possibly for other smaller NZIX users) we would prefer that routers connected to the NZIX also ran OSPF as we use this process to collect NZ routes and differentiate between domestic and international traffic for our campus IP traffic metering.It is possible that other NZIX users do the same. OSPF is also less complex to manage for smaller users with fewer highly skilled network staff. Thanks and best regards Warwick *********************************************************************** Warwick Glendenning NZCE REA Dip.Mgt.St. Network Services Manager Information and Technology Services University of Waikato Private Bag 3105 Hamilton, NZ Tel:07-8384363 Fax:07-8384066 mobile: 025-356121 email:warwickg@waikato.ac.nz --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 9 months

Re: BGP over NZIX

by Pieren, Jay

Hi AgResearch is connected to NZIX as well. We provide services for DRC and MIRINZ. Jay Pieren IT Service Manager Phone: ++64-3-489-9080 AgResearch New Zealand Ltd. Fax: ++64-3-489-3739 Invermay Research Centre Mobile: ++64-25-223-4330 Puddle Alley Private Bag 50034 Mosgiel, Otago New Zealand --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 9 months

RE: BGP over NZIX

by Dennis Su

Joe, KC still has a Cisco 3600 connected to NZIX. It could just be used for route collecting but I am not 100% sure. Cheers, Dennis ----------------------------------------------------------------- Dennis Su Msc CNE CCNA Network Engineer, Network Services, ITS, University of Waikato, Hamilton, New Zealand Tel 64 7 838 4183 Fax 64 7 838 4066 Email d.su(a)waikato.ac.nz > -----Original Message----- > From: Tony Wicks [mailto:tonyw@iconz.co.nz] > Sent: Wednesday, January 20, 1999 12:11 PM > To: nznog(a)list.waikato.ac.nz > Cc: jabley(a)clear.co.nz > Subject: Re: BGP over NZIX > > > >Did I miss KC? Many apologies if so; do KC have a router at NZIX? > > > No, KC connects to NZIX via us ( ICONZ ). > > Tony Wicks > Network Engineer, ICONZ > > --------- > To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz > where the body of your message reads: > unsubscribe nznog > --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 9 months

Re: BGP over NZIX

by Tony Wicks

>Did I miss KC? Many apologies if so; do KC have a router at NZIX? No, KC connects to NZIX via us ( ICONZ ). Tony Wicks Network Engineer, ICONZ --------- To unsubscribe from nznog, send email to majordomo(a)list.waikato.ac.nz where the body of your message reads: unsubscribe nznog

22 years, 9 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

NZNOG January 1999