November 2001 - Test - lists.nanog.org

Re: Somalia
by Matthew R. Potter 23 Nov '01

23 Nov '01

A news link from Xinhua News Agency dated Nov 14... http://library.northernlight.com/FC20011114230000093.html?cb=0&dx=1006&sc=0# doc Matt

1 0

Teleglobe issues?
by Tim Devries 22 Nov '01

22 Nov '01

Has anyone seen any issues w/ regards to teleglobe? It seems they lost some power in Toronto, and caused a wack of lost connectivity. Anyone have any more information on this? Tim

1 0

Qwest multi-state outage
by Dan Hollis 22 Nov '01

22 Nov '01

Anyone have details? Looks like most of their customer IP network is down. -Dan -- [-] Omae no subete no kichi wa ore no mono da. [-]

1 0

Code Red -> Router Memory depletion?
by Mike Lewinski 22 Nov '01

22 Nov '01

We've seen two routers experiencing problems this AM that appear to be related to client swervers infected with the IIS Code Red virus. I say appear because of the timing with cpu profiles on downstream routers where infections broke out, but I don't have any direct evidence. The first one was a border router: Jul 19 08:00:47 5093: 2w5d: %SYS-2-MALLOCFAIL: Memory allocation of 65540 bytes failed from 0x603BF35C, pool Processor, alignment 0 Jul 19 08:00:47 5094: -Process= "BGP Router", ipl= 0, pid= 86 # sh ver uptime is 4 hours, 46 minutes System returned to ROM by bus error at PC 0x603BFCFC, address 0xFFFFFFF0 at 05:57:21 UTC Thu Jul 19 2001 The other one is a client aggregation router Jul 19 12:02:49 192: %SYS-2-MALLOCFAIL: Memory allocation of 1964 bytes failed from 0x314DA4A, pool Processor, alignment 0 Jul 19 12:02:49 193: -Process= "OSPF Router", ipl= 0, pid= 32 (This router is still functioning, but not allowing any incoming connections on telnet). -Mike

4 5

Re: Next generation DSLAMs
by miquels＠cistron-office.nl 22 Nov '01

22 Nov '01

In article <cistron.4.3.2.7.2.20011122213039.00b78610@localhost>, Geoff Huston <gih(a)telstra.net> wrote: >One view is http://www.potaroo.net/ispcolumn/2001-11-dsl.html Cistron Telecom in .NL built a network exactly like that by placing the BBRASes (redback) close to the DSLAM, then encapsulating the traffic for each wholesale customer into a MPLS VPN using Juniper boxes. Unfortunately due to the bad investment climate and problems with (de-)regulation and the local monopolist Cistron Telecom doesn't exist anymore, and Cistron Internet is now a client of another wholesaler that indeed delivers DSL circuits over ATM to use in one central location (for the entire country!) Looking back I am still convinced we had it right but we were probably just way ahead of our time, alas. Mike. -- "Only two things are infinite, the universe and human stupidity, and I'm not sure about the former" -- Albert Einstein.

1 0

RE: BT network outage
by Kevin Gannon 22 Nov '01

22 Nov '01

Just imagine the poor guys in the NOC ;-). Imagine the length of the queue of PHB's (pointy headed boss) "When will it be fixed", "Root cause analysis meeting in 5mins" ect ect I am interested to hear comments from people on how they manage the aftermath of P1 problems ? Also managing the manager Vs Techies during the incident. Regards, Kevin -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Neil J. McRae Sent: 21 November 2001 23:18 To: Sean Donelan Cc: nanog(a)merit.edu Subject: Re: BT network outage > The joy of single provider service. British Telecom lost most > of its national IP backbone on Tuesday affecting DSL and Dialup > service across multiple ISPs in the UK. According to news > reports, this affected almost all DSL service in the UK. > > What happened to BT? Is this a unique "feature" of the UK marketplace > or can the same thing happen in the USA? No one will ever know but I'd guess it was self inflicted, it didn't affect all providers though, my partner has DSL via one provider that was not affected, I've got DSL though another provider and that was affected [although the DSL boxes are less than 10 feet apart and go into the same exchange!] The issue in the UK around BT's ownership of the loop will never end as long as we have a government and more importantly a regulator that continues to think that "BT knows best". Regards, Neil.

1 0

Re: how many roots must DNS have before it's considered broken (Re: ISP network design of non-authoritative caches)
by Simon Higgs 22 Nov '01

22 Nov '01

At 05:21 AM 11/19/01 +0000, you wrote: >Once we start down the slippery slope of "I'm a root too", how >many different ad hoc DNS "universes" (for lack of better >term) must we have before we decide that things are "broken"? Two. That happened back in 1996 when the IANA TLD applicants began getting their glue added to AlterNIC. Today lack of entry in the root has created a dozen or so more alt.roots. Now people are beginning to notice the consequences (i.e. the .US zone is now causing cache pollution outside the legacy root since it's using the ICANN .BIZ name servers - and that .BIZ isn't recognized by all the alt.roots). But it's OK. Really. There's only one root. Honest. Except for this one, which is being run with all the usual I* blessings: http://www.isi.edu/otdr/ >Maintaining a single, authoritative root seems, IMHO, to be a >Good Thing. Given multiple registries, namespace collisions >would get ugly -- and, even in the absence of collisions, let us >consider "reachability" issues. That's the point. Getting the alt.root "universes" to cooperate is an exercise similar to "cat herding", but it has to start somewhere. Best Regards, Simon -- DNS is not a sacred cow that cannot be replaced by something better.

6 5

Routing to .US TLD servers
by Sean Donelan 22 Nov '01

22 Nov '01

If you (or your customers) have difficulties resolving domains in the US zone, it was moved recently moved to a new set of servers. Nothing special, except they are all in 209 net space, and are being announced as /24 network routes. There is no covering CIDR aggregate being announced, so providers which still filter 209 CIDR blocks (i.e. an obsolete copy of access-list 112) you may have difficulty reaching the new servers. a.gtld.biz. 209.173.53.162 b.gtld.biz. 209.173.57.162 c.gtld.biz. 209.173.60.65 route-server>show ip bgp 209.173.48.0/20 longer BGP table version is 502125, local router ID is 134.24.38.246 Status codes: s suppressed, d damped, h history, * valid, > best, i - internal Origin codes: i - IGP, e - EGP, ? - incomplete Network Next Hop Metric LocPrf Weight Path *> 209.173.53.0 134.24.127.30 35 0 1740 7018 701 7786 i *> 209.173.57.0 134.24.127.30 35 0 1740 7018 7786 i *> 209.173.58.0 134.24.127.30 35 0 1740 7018 1 7473 9911 7786 ? *> 209.173.60.0 134.24.127.30 35 0 1740 7018 209 7786 i This is strictly a network routing issue, and has nothing to do the merits of Neustar, ICANN or any other DNS issue. If you, and all your upstreams, accept /24's you shouldn't see any problems.

1 0

Re: BT monopoly causes widespread network failure
by Rodney Thayer 22 Nov '01

22 Nov '01

At 06:19 PM 11/21/2001 -0500, Sean Donelan wrote: >Yes. But I'm more interested in how a provider manages to wipe >out their entire national network. That takes talent. > >I'm sure BT has some clever network engineers, and they could have >done it to themselves. On the other hand, BT uses the exact same >equipment as US providers and other providers around the world. >Is there some latent defect in the vendor gear we all use? Or arrogance. There seem to be a lot of allegedly clueful service providers out there that have single points of failure, lack of genetic diversity, insufficient resources assigned to allegedly mission-critical facilities, etc.etc. Notice for example there doesn't seem to be anyone from BT speaking here... I assume, given the usual suspects that graciously ignore the NA in NANOG, that nothing relevant has been posted on UK/European lists...

2 1

Next generation DSLAMs
by srihari varada 22 Nov '01

22 Nov '01

Hello: I would like to know what services are planned to be converged on the next generation DSLAM boxes from the service provider point of view. A servicve that was talked of was the VPNs provisioned through either ATM or IP/MPLS backbone networks. What would be the OSS support in them? I would be interested in the subscriber management models especially. Any known literature available in the public domain? I do understand that the majority of the current DSLAMs implement common denominator function (that is to restrict their funcitonality at switching or teminating ATM PVCs.) PPP and PPPoE, designed to preserve dialup experience and capital investment of ISPs on dial up infrastructure, will be processed at the competitive or non-competitve ISP domains. Regards, Srihari Varada

2 1