- Test - lists.nanog.org

Re: Great job AT&T (re: Microsoft problems)
by Mike Lewinski 24 Jan '01

24 Jan '01

> > Most Microsoft sites (Microsoft.com, MSN.com, Hotmail.com, etc.) > > are affected. The Microsoft technical team is troubleshooting this > > issue. > > Hotmail has had no impact regarding this issue. That's *not* what our clients have reported or what I observe. Some clients have hotmail set as their start page and are calling to report "The internet is DOWN!" To make matters worse, IE's default 'auto.search.msn.com' which is used when a site is unreachable is itself unreachable. So client's aren't even getting the marginally useful error page normally displayed if a site can't be contacted. I observed the same behaviors from a dialup outside our network ~9am MST, and no connections to www.hotmail.com were possible. It doesn't appear to be a DNS resolution issue for 'hotmail.com', as I can telnet www.hotmail.com 80 and GET / HTTP1.1 to retrieve the page. But Internet Explorer does *not* load the page, appearing to hang while attempting to access 'passport.com' which does not have resolution currently. Mike

2 1

Re: [OT]: Involuntary outages may start at 7am PST
by Kevin Oberman 24 Jan '01

24 Jan '01

> From: "Kavi, Prabhu" <prabhu_kavi(a)tenornetworks.com> > Date: Wed, 24 Jan 2001 13:25:43 -0500 > Sender: owner-nanog(a)merit.edu > > > Quoting from the 1/22/01 online issue of US News & World Report: > > "Ironically, California's nightmare stems in part from the state's efforts > to lower rates. In 1996, both houses of the state legislature voted > unanimously to deregulate the market for wholesale electricity, enabling > power producers to sell electricity to utilities on the spot market. But the > new law failed to create a free retail market-in most cases, rates for > consumers and businesses were fixed until at least April 2002. ... > No major power plant has been built in California for more than a > decade, partly because of environmental restrictions." > > And in the 1/29/01 online issue: > > "... In California, however, utilities were forbidden to enter into > long-term supply contracts and were forced immediately to buy energy > in the volatile wholesale spot market." > > So tell me, how could PG&E have accurately forecasted the booming > demand for power back in 1996 and protected themselves, given no > new plants were being built? They could/did not. They made a corporate bet and they lost. That does not make it someone else's fault. PG&E and SO. Cal. Edison were major forces in lobbying for the regulatory changes that have driven them to the edge of insolvency. R. Kevin Oberman, Network Engineer Energy Sciences Network (ESnet) Ernest O. Lawrence Berkeley National Laboratory (Berkeley Lab) E-mail: oberman(a)es.net Phone: +1 510 486-8634

1 0

Re: Great job AT&T (re: Microsoft problems)
by Jeff Frost 24 Jan '01

24 Jan '01

On Wed, 24 Jan 2001, Dave McKay wrote: > > Sean Donelan (sean(a)donelan.com) wrote: > > > > Well, AT&T couldn't fix the problem, but at least their customer > > service people knew there was a problem and were willing to attempt > > contact with someone at Microsoft. > > > > Most Microsoft sites (Microsoft.com, MSN.com, Hotmail.com, etc.) > > are affected. The Microsoft technical team is troubleshooting this > > issue. > > Hotmail has had no impact regarding this issue. > > Dave, are you certain of that? Because I can't get to the hotmail.com login page right this second and have received complaints from several associates that they can't get into their hotmail accounts. -- Jeff Frost VP Technology <jeff(a)digitalpipe.net> Digital Pipe Communications, Inc.

1 0

What is going on in the PAC NW (Microsoft Outage)
by SMcGrath＠dhhs.state.nh.us 24 Jan '01

24 Jan '01

Is there any information available about Microsoft and MS related companies being unavailable the customers are restless

1 0

[Possibly OT] Need to Rent/Lease a Core Switch
by Karyn Ulriksen 24 Jan '01

24 Jan '01

We are in the process of migrating our DataCenter to a new location. To accomodate a smooth transition, we are in need of either renting or leasing a "core level" switch to use while we bring up both datacenters in tandem. The equipment requirements are as follows: Minimum 8 GigE GBIX (Fiber) Ports Minimum 24 10/100 ethernet Ports Layer 3 Routing (prefer BGP, OSPF mimimally) 802.1q VLAN capable up to 254 VLANs. Prefer dual power and dual MSM/RPC modules for redundancy. Minimum 32Gbps thruput Required Install Date: February 1, 2001 Currently considering Extreme Networks Black Diamond 6808, Extreme Networks Alpine, and Cisco 6000/6500 series. Willing to consider others that meet above criteria. Please contact me off list at kulriksen(a)publichost.com or 949-743-2014. --------------------------------------------------------------------- Best regards, Karyn Ulriksen Director of Network Operations PublicHost, A SiteStream Company 1 Jenner, Suite 100 Irvine, California 92618 USA Phone: (949) 743-2000 email: kulriksen(a)publichost.com URL: http://www.publichost.com ===========================================

1 0

RE: Labeling and naming
by Jason Lixfeld 24 Jan '01

24 Jan '01

I'll use your reply as a template: Device naming convention: <2 letters of the state/province abbreviation> <3 letters of city code> <3 letters of POP location> <unless there is only one POP in the city, then this field is blank> <1 letter describing device type> a = RAS Server/Access device (including remote console devices) s = Switch r = Router <2 letter device abbreviation> 12 = Cisco 12000 Series 75 = Cisco 7500 Series 50 = Cisco Catalyst 5000 Series 65 = Cisco Catalyst 6500 Series p3 = Lucent PM3 58 = Cisco AS5800 etc.. <2 digit device sequence identifier> <x letter/digit interface ID/number> Examples: ON-TOR-FRN-R12-01-POS11-2 Ontario, Toronto, Front St. Cisco 12000, #1, POS, slot 11, port 2 BC-VAN-HBR-R75-04-A9-0-1 British Columbia, Vancouver, Harbour Center, Cisco 7500 Series, #4, ATM, linecard 9, slot 0, interface 1 AB-CAL-A53-01-32 Alberta, Calgary, Cisco AS5300, #1, dialup port 32 NOTE: DNS for the devices themselves (for telnet, ssh, snmp, etc) are identicle to the above, except the interface information is not included. ie: ON-TOR-FRN-R12-09.LOOK.CA > -----Original Message----- > From: Przemyslaw Karwasiecki [mailto:karwas@ifxcorp.com] > Sent: Wednesday, January 24, 2001 10:36 AM > To: Kurt Erik Lindqvist; nanog(a)merit.edu > Subject: RE: Labeling and naming > > > > Hello, > > We are currently trying to resolve the very same issue. > So far we plan to use following scheme: > > 1) Device name should be concatenation of following parts: > > <2 letters of ISO country code> > http://www.bcpl.net/~jspath/isocodes.html > <3 letters of airport city code> > http://www.ufreight.com/faq/airport_code/airport_code_by_ac.html > <3 letters of location> > to be created > <4 letters of device name abbreviations> > to be created -- in case of cisco: model number > <1 letter separator> > arbitrary decided to be capital letter X (no DNS nor > arithmetic exp problems) > <1 letter device ordinal> > can be hex if needed > > Examples: > USMIANOC3662X1 - Miami Lakes NOC cisco 3662 > USMIATPL7206X1 - Miami Teleplace cisco 7206 > USMIANAPJM20X1 - Miami NAP Juniper M20 > VEBRMPOP2501X1 - Venezuela, Barquisimento POP, VE cisco 2501 > VACCSCTV1010X1 - Venezuela, Caracas CANTV collocation, > cisco Lightstream 1010 > > 2) We will also create DNS zone ???core.net which will be > used in two main ways: > > a) reverse DNS lookup, to map IP addresses into > hierarchical names, like: > > serial1-0-0-128-<customer_name>.USMIATPL3662X1.TelePlace.mia.u > s.ifxcore.net > This will be mainly used for tools like traceroute, etc. > > b) straight DNS lookups of devices itself, like: > USMIATPL3662X1.ifxcore.net > This will be used to get easy access to a device itself > (through Loopback), > and due to mnemonic nature of device name should be > easy to memorize. > > So far the only problem we run into with this scheme is 12 > character limit > on hostnames on some boxes. > > Przemek > > -----Original Message----- > From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of > Kurt Erik Lindqvist > Sent: Wednesday, January 24, 2001 9:21 AM > To: nanog(a)merit.edu > Subject: Labeling and naming > > > > > > For a project I am currently working on I stumbled upon the following. > What is the best way to lable and name equipment? Although > this applies to > all equipment such as SDH ADMs, IP, ATM etc I realised that > it seems to be > hardest to find a sensible convention for IP equipment. > Preferably I would > like to find a convention that fits all, but I guess that is utopia. > > So, since list contains, PTTs, Telcos, ISPs and wannabees is there any > good common scheme or pointers to something useful? > > - kurtis - > > > > > -------------------------------------------------------------- > ----------- > This email server is running an evaluation copy of the > MailShield anti- > spam software. Please contact your email administrator if you have any > questions about this message. MailShield product info: www.mailshield.com .

1 0

[OT]: Involuntary outages may start at 7am PST
by Kavi, Prabhu 24 Jan '01

24 Jan '01

Uh, PG&E does buy power at the market. They are simply not allowed to sell power at the market price, which is the root cause of the problem. Deregulation tends to work when both sides are fully deregulated (buying and selling). Crimping the creation of new power plants and being forced to sell essentially unlimited amounts of power at a nearly fixed price caused this mess. Blame the environmentalists and politicians, not PG&E. Prabhu > -----Original Message----- > From: Nathan Stratton [mailto:nathan@robotics.net] > Sent: Monday, January 22, 2001 10:27 PM > To: Sean Donelan > Cc: nanog(a)merit.edu > Subject: Re: Involuntary outages may start at 7am PST > > > > On 22 Jan 2001, Sean Donelan wrote: > > > Have any Internet providers or private data centers announced any > > voluntary "good neighbor" measures such as wider > temperature and humdity > > limits, lights-out operation, off-peak use of heavy > electrical demands > > for laser printers, etc. > > Don't take this the wrong way, but frankly I would not be > happy if my colo > providers started implementing wider temperature and humdity > limits. I pay > large amounts of money for colo and I want what I am paying > for. This mess > was caused by California regulators and very very greedy PG&E > who gambled > on lower rates and lost. PG&E should be forces to liquidate > other out of > state assets and buy power at the market. > > -Nathan > > >

2 1

RE: Labeling and naming
by owen＠dixon.delong.sj.ca.us 24 Jan '01

24 Jan '01

> Hello, > > We are currently trying to resolve the very same issue. > So far we plan to use following scheme: > > 1) Device name should be concatenation of following parts: > > <2 letters of ISO country code> > http://www.bcpl.net/~jspath/isocodes.html Not a bad start, but somewhat unnecessary given next field. > <3 letters of airport city code> > http://www.ufreight.com/faq/airport_code/airport_code_by_ac.html Doesn't scale. Not all cities where POPs end up have airports. Additionally, do you use the closest airport, closest major airport (by what definition), etc. Further, if you go to 4 letter airport code, then you can use the full ICAO abbreviations and you eliminate the need for your previous field. examples: KSJC = San Jose, California, US ELHR = Heathrow, London, UK CYVR = Vancouver, British Columbia, Canada KACV = Arcata, California, US (actually in McKinleyville, CA) > <3 letters of location> > to be created Probably helps solve previous problem somewhat, but creates a certain amount of arbitrariness that makes the naming convention harder to deal with and tends to introduce naming errors. > <4 letters of device name abbreviations> > to be created -- in case of cisco: model number So a Cisco 12008 is abbreviated how, vs. say a 12016, or a 1201? Additionally, someone person needs to have central control of a database of these designators, and there comes a tradeoff between specificity and viability at some point. In most cases, functional purpose turns out to be more desirable than equipment type information in the host name. (Such as IBR == Internet Border Router, etc.) > <1 letter separator> > arbitrary decided to be capital letter X (no DNS nor arithmetic exp problems) Hmmm... I probably would have used either U or I for that, but X is as good as any, I suppose. Does improve readability. > <1 letter device ordinal> > can be hex if needed > And when you end up with more than 16 7513's in the same location, what do you do? Do you start with 0 or 1? Do you end with 0 or F? > Examples: > USMIANOC3662X1 - Miami Lakes NOC cisco 3662 > USMIATPL7206X1 - Miami Teleplace cisco 7206 > USMIANAPJM20X1 - Miami NAP Juniper M20 > VEBRMPOP2501X1 - Venezuela, Barquisimento POP, VE cisco 2501 > VACCSCTV1010X1 - Venezuela, Caracas CANTV collocation, cisco Lightstream 1010 > > 2) We will also create DNS zone ???core.net which will be used in two main ways: > > a) reverse DNS lookup, to map IP addresses into hierarchical names, like: > serial1-0-0-128-<customer_name>.USMIATPL3662X1.TelePlace.mia.us.ifxcore.net > This will be mainly used for tools like traceroute, etc. > > b) straight DNS lookups of devices itself, like: > USMIATPL3662X1.ifxcore.net > This will be used to get easy access to a device itself (through Loopback), > and due to mnemonic nature of device name should be easy to memorize. > > So far the only problem we run into with this scheme is 12 character limit > on hostnames on some boxes. > File a bug report with the vendor. The RFCs are clear that this is not valid. > Przemek > I would propose a better alternative if I had one. Unfortunately, I have yet to see a naming scheme that didn't have problems. I will say that the following components of naming schemes I have run across tend to work fairly well: CLLI codes for geographic locations (SNTC = Santa Clara California, JYCY = Jersey City, New Jersey, etc.) These are the codes used to describe where you called on your phone bill. They do scale to most international scenarios (LNDN=London, UK, etc.) If your network is architected in such a way that devices have consistent functional groupings, then using that functional grouping as a portion of the name tends to work fairly well. Usually, for example, I'm much more concerned with getting to the router that does the particular task than with what model of hardware it is when I'm trying to reach it. It's much more useful to connect to ibr01.sntc01... than to C12016X01.sntc01, because I may or may not know which 12016 in that location is the IBR vs. some other function, and I may not be able to remember whether that particular IBR is a 7513, 12016, or something else. Numbering starting at 1 vs numbering starting at 0 both have their share of tradeoffs. I prefer starting at 0, because I find most humans can adapt to that fairly quickly. By starting at 0, you end up with the ability to use mod 2 computations for pairs of routers. Starting at 1, the math becomes more complex (1 pairs with 2 instead of 0 pairs with 1). That's my $.02. Owen > -----Original Message----- > From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of > Kurt Erik Lindqvist > Sent: Wednesday, January 24, 2001 9:21 AM > To: nanog(a)merit.edu > Subject: Labeling and naming > > > > > > For a project I am currently working on I stumbled upon the following. > What is the best way to lable and name equipment? Although this applies to > all equipment such as SDH ADMs, IP, ATM etc I realised that it seems to be > hardest to find a sensible convention for IP equipment. Preferably I would > like to find a convention that fits all, but I guess that is utopia. > > So, since list contains, PTTs, Telcos, ISPs and wannabees is there any > good common scheme or pointers to something useful? > > - kurtis - > > > >

1 0

RE: Labeling and naming
by Frank Coluccio 24 Jan '01

24 Jan '01

Correction: in my previous message I incorrectly cited Syncordia, when I meant to say "Telcordia," which is the new name for Bellcore. ------Original Message------ From: "Frank Coluccio" <fcoluccio(a)dticonsulting.com> To: Przemyslaw Karwasiecki <karwas(a)ifxcorp.com>, Kurt Erik Lindqvist <kurtis(a)kurtis.pp.se>, nanog(a)merit.edu Sent: January 24, 2001 4:33:53 PM GMT Subject: RE: Labeling and naming A similar Bellcore/Syncordia convention that is used by the telcos and their affiliates closely resembles what you have described. It's called CLLI, for Common Language Location Identification, pronounced (some would argue, appropriately,) "Silly." I'm not necessarily recommending this convention, but it does provide some food for thought, and a basis for comparison to other methods that may be discussed here. See: http://www.ntca.org/bus_tech/tech_eng/clli.html An excerpt: ----begin: Code Format A CLLI code is an 11 character alphanumeric code that assigns a unique identification code to each location and to each coded telephone plant item. The code structure is: AAAABBCCDDD AAAA is the geographical or place code BB is the geopolitical or state/country code CC is the network site code DDD is the network entity code The combination of these codes comprises a unique place, a unique building and a specific entity. For example: CITYSTBDDS0 represents the first digital switch (DS0), in the town of CITY, in the state of ST, in the building BD. CLLI codes are used to: - identify buildings - identify specific equipment sites or interface points - identify entities such as switches <continued at above url > -----end One common pitfall in labeling physical assets occurs when logical IDs become confused with physical attributes that describe geography and order. As in floor, rack, shelf, slot, jack and I/O numbers, etc. A relational database is usually used to solve this, by maintaining the logical attributes in the background, or vice versa. Frank Coluccio DTI Consulting Inc. New York, NY fcoluccio(a)dticonsulting.com ------Original Message------ From: "Przemyslaw Karwasiecki" <karwas(a)ifxcorp.com> To: Kurt Erik Lindqvist <kurtis(a)kurtis.pp.se>, nanog(a)merit.edu Sent: January 24, 2001 3:36:29 PM GMT Subject: RE: Labeling and naming Hello, We are currently trying to resolve the very same issue. So far we plan to use following scheme: 1) Device name should be concatenation of following parts: <2 letters of ISO country code> http://www.bcpl.net/~jspath/isocodes.html <3 letters of airport city code> http://www.ufreight.com/faq/airport_code/airport_code_by_ac.html <3 letters of location> to be created <4 letters of device name abbreviations> to be created -- in case of cisco: model number <1 letter separator> arbitrary decided to be capital letter X (no DNS nor arithmetic exp problems) <1 letter device ordinal> can be hex if needed Examples: USMIANOC3662X1 - Miami Lakes NOC cisco 3662 USMIATPL7206X1 - Miami Teleplace cisco 7206 USMIANAPJM20X1 - Miami NAP Juniper M20 VEBRMPOP2501X1 - Venezuela, Barquisimento POP, VE cisco 2501 VACCSCTV1010X1 - Venezuela, Caracas CANTV collocation, cisco Lightstream 1010 2) We will also create DNS zone ???core.net which will be used in two main ways: a) reverse DNS lookup, to map IP addresses into hierarchical names, like: serial1-0-0-128-<customer_name>.USMIATPL3662X1.TelePlace.mia.us.ifxcore.net This will be mainly used for tools like traceroute, etc. b) straight DNS lookups of devices itself, like: USMIATPL3662X1.ifxcore.net This will be used to get easy access to a device itself (through Loopback), and due to mnemonic nature of device name should be easy to memorize. So far the only problem we run into with this scheme is 12 character limit on hostnames on some boxes. Przemek -----Original Message----- From: owner-nanog(a)merit.edu [mailto:owner-nanog@merit.edu]On Behalf Of Kurt Erik Lindqvist Sent: Wednesday, January 24, 2001 9:21 AM To: nanog(a)merit.edu Subject: Labeling and naming For a project I am currently working on I stumbled upon the following. What is the best way to lable and name equipment? Although this applies to all equipment such as SDH ADMs, IP, ATM etc I realised that it seems to be hardest to find a sensible convention for IP equipment. Preferably I would like to find a convention that fits all, but I guess that is utopia. So, since list contains, PTTs, Telcos, ISPs and wannabees is there any good common scheme or pointers to something useful? - kurtis -

1 0

ATT Broadband / RoadRunner Routing Failures
by Daniel Senie 24 Jan '01

24 Jan '01

The ATT Broadband / MediaOne RoadRunner network in New England appears to have major routing problems. Their recorded announcement indicates they're having connectivity problems resulting in people not being able to reach web pages. Of course the problem covers more than the web... Traces to IP addresses of places I need to reach fail within the ATT Broadband network, or within the ATT.NET space (i.e. either in net 24 or net 12). This has been going on since at least 6:30AM EST. I first noticed an inability to reach quite a few DNS servers. I can get to my colo, though. My servers in the colo appear able to see everywhere (so hopefully the reverse is also true). Looks like some very broken routing going on in ATT land. -- ----------------------------------------------------------------- Daniel Senie dts(a)senie.com Amaranth Networks Inc. http://www.amaranth.com

1 0