Y2K and ISPs

This page is being targeted to disaster preparation for ISPs and will probably be expanded. To see the old page, go to Archived ISP/Y2K.

This discussion is oriented towards the smaller ISP, though much of this is relevant to keeping a business LAN connected to the Internet.

If you're a customer, you might get from this the questions you ought to ask your ISP to see if it's ready for year-2000. The bad news is that while some of this is simply required to do business period in 2000 even if there is no Y2K trouble, the expensive stuff required to do business if there is serious trouble will probably be out of reach of your Internet Service Provider. Remember that ISP service is now commodity that everyone pretty much pays $20 a month for. Profit margins on $20 a month and in some cases, even lower tend to be razor thin. If you are a business that must have Internet service if there's any Internet to connect to, you might consider making a deal with your provider to provide the hardware and facilities to get it to the compliance level your business requires in exchange for reduced service costs or something else your organization wants. If you think your ISP needs to be in an underground concrete bunker, yuu might be able to sell your ISP on it, but you get to pay for it.

There's a limit to what an ISP can normally do about Y2K trouble. To function, an ISP or office LAN needs connectivity to the Internet (broadband links), connectivity to your customers (usually dialup POTS and/or ISDN), power, working servers and software, working network components and software, (bridges, routers,etc.) and if you want to do business, your workstations and larger systems that process billing and other customer interaction had better be compliant. Building services required include climate control (the temperature level computers are most comfortable with is the same one you are; if the temperature hits 100 F (39 C) in the computer room, the service life of the computer is drastically reduced. Then, there's physical security. Reduced police protection is probable in the event of serious Y2K-related trouble. if there's civil disorder outside the place, a mob could do a good job on either the computers or both. However, what an ISP can do about that is pretty severely limited.

A general hint. The first place to go for compliance information is the Y2K page / site of your vendors. If you don't know what a vendor's site URK is, try http://www.vendorname.com first... e.g. http://www.cisco.com . Then try altavista using your vendorname as a keyword, if it's one or more words, enclose them as a string, e.g. "Network Associates". Please don't feel insulted by this, this page is written for sysadmins and netadmins at all levels of experience.

ISP Y2K Readiness Outline
  1. Physical connectivity to the Internet
    • telco (copper) wired T1-OC5 local loop: your basic connection. While a second loop pointing at an independent feed is a good thing, if your telco broadband connections die, you'll be trying to get to the Net on two dead connects for the price of one.
    • telco, etc. fiber optic: I'm not sure if the fiber optic will stay up if the copper wired part of the network goes down, I don't know how many of the connections are in common. Fiber optic is independent of telco if you go with another provider of fiber optic dial tone with its own network. Make sure they aren't using telco local loops to get to the Net if you're using this for improving redundancy.
    • cable modems, e.g. @Work While I know of one ISP that uses or used a standard home account to support a few hundred users on a regular basis, I think this can only be justified in the event of emergency. Running several hundred users through a single user account costing $30/month is difficult to justify doing even to your local cable company, as much as you may hate them. More to the point, that kind of scam is likely to be unplugged without any notice or warning, and might be considered illegal theft of cable service. If available, check into @Work. If you do, check into what @Work uses as a backbone provider. The worst news here is that your cable provider or home.com may not be Y2K ready.
    • wireless point-to-point - for 10-20 miles, figure $1500 or so for each end. This price may drop if the Tuscon Amateur Radio Society ever manages to get their spread-spectrum transceiver kit complete and ready to sell. While the bandwidth is only 500Kbps, it should be fairly inexpensive. I really like the wireless solution best in a lot of ways.
    • satellite: Haven't had a chance to check into the costs yet. If you've got numbers from 128Kbps - OC3 service and bi-directional terminals, please let me know.
  2. Backbone redundancy - If you've got alternate path(s) to the Internet, they don't do you much good if they connect to the same backbone and it fails, or your separate feed sites connect to a common upstream link between your ISP and a backbone and that link breaks. Check to make sure that this is not true. Specify this in your service agreement if need be.
  3. Peering Points - In the US, MAE East, MAE West, and the smaller regional providers. Europe, Asia, and other continents and countries have peering points of their own. You probably want to know whether the one you're ultimately connected to has generator backup, and how many days of fuel that generator has.
  4. Connectivity to your customers
    • dialup POTS: your dialup modem pool is probably compliant. Check with your vendor anyway, you might have the only one in the universe that isn't. Not much you can do about telco / local dial tone availability.
    • ISDN: It is conceivable though unlikely that ISDN might be working even with the regular dial network down.
    • cellular / PCS: It is conceivable though unlikely that cell phones might be up with regular dial network down, while this actually has happened during earthquakes, unless somebody hits a phone pole due to losing street or traffic lights, chances are, if dialup goes, so does cell / PCS. However, this simply means you probably should have one around the office in case you need to call for help, you won't want to plug cell phones into your modem pool.
    • wireless point-to-point: see above, you may be working with reduced bandwidths and less expensive transceivers. You might want to look into providing this and setup to your customers for an appropriate fee if you can find some good turnkey packages. This might be a good thing even in the absence of Y2K trouble, no T1 local loop from telco because your link to your feed is via microwave, telco won't be taking your network down.
    • voice phones: If you have a PBX or the usual business key stations, check with the vendors for Y2K compliance. Battery backup is a good idea. And keep a POTS phone, preferably the old fashioned Western Electric type desk/wall phones, lying around just in case your PBX / business phones lose power or take a dive for other reasons. If it has a transformer brick attached, it is not suitable as an emergency phobe.
  5. Power: It is quite possible that your power will be down and some telco will be up. If so, you might as well stay in operation. Communications in a power outage are extremely valuable for things like organizing relief efforts, getting medical advice in emergencies, and even calling for help if 911 is down, as well as keeping critical business operations going. For extended discussion of generators, alternative power, low power/no power lighting, emergency heating etc., go to the Personal Preparation section of my site and to the complete chapters of my unpublished Y2K preparation book
    • backups: Are you keeping at least weekly off-site tape (or whatever) backups of your server and business files? If your place burns down and you can get an insurance company setup, you'll be very happy to have these.
    • UPS - batteries: These are valuable mainly for dealing with power fluctuations and very short term black/brownouts. If you plan to stay in business during blackouts, see above.
    • generators: see above.
    • alternative power - For solar, figure about $10/watt. For windmill / hydro / steam (i.e. run your ISP on firewood. No, I'm not kidding.) Economizing on power is the best way to save money on the size of your generating system, but compromising reliability in the process is fairly easy and needs to be watched for. For information on power generation, see above.. If you do decide to try a laptop server server, you're best advised to turn all power management features off, and due to the probability that laptop hard drives are less reliable than regular hard drives, consider running a SCSI/100 Base T PCMCIA card to connect to your network and a SCSI chain running enough standard hard drives in a separate box with a small power supply to support whatever RAID level you can afford and run RAID SCSI compatible software. (I suggest RAID 5.) Put your tape backup in the same box. You should get substantial power savings. Another option might be LCD flat panel monitors and your regular system, but this is rather expensive. However, your most important power savings will be in the area of lighting (recommended: compact fluorescents or LED based fixtures, though oil lamps/ Coleman type lanterns will work in emergencies. The efficiency range of lighting is from 5% (incandescent light bulbs) to 95%+ (LED).
  6. Servers and software. You really ought to read through the entire computer section of my Y2K page after you finish this part of the outline. Make sure that you replace the CMOS or equivalent on your computer (clock/low level configuration) batteries no earlier than 11/1999. And keep spare batteries. And put the configuration info on a floppy.
  7. Business
    • workstations: If you're running a Windows machine that hasn't been Y2K-fixed, it's Y2K broken, you can't depend on the computer or the operating system or the applications or your data files to handle Y2K correctly. Go here for help. If you're running Mac, check your applications and data files. Your applications should be checked at your vendor Y2K pages, I don't know which scan tools for data files run on Mac.
    • billing systems (might be midrange / mainframe in larger ISPs) If you're a smaller ISP, this is probably running on your workstations. See above, and pay attention to spreadsheets and database data files. If you're running midrange or mainframe systems and custom applications, there isn't much I can do for you, other than advise checking with your vendors, find a good automated scan tool that'll check your custom code, and start RIGHT NOW if you haven't already. You probably should have started in 1998 or 1997. In general, you'll want to eyeball every single use of date commands in your software. There appear to be ways of writing non-compliant software in all popular computer languages from COBOL, C (all variants), Java, Javascript. Good luck, if you're starting now (this was written in 4/1999) you're really going to need it.
  8. Building considerations
    • Climate control: If you're running alternative power, you probably can't afford to run either air conditioning or electric heating. See above for preparation with respect to heating.
    • Water / Sewage: If power goes down for any length of time, your water and sewage go with them. If you're still trying to do business, i.e. if telco is still up, you'll need stored water and some method of disposing of sewage. Check the Personal Preparation section of my Y2K page.
    • Physical security
      • burglar alarm: Make sure it's got a hefty battery backup. If you're using a system that reports to a central monitoring station, make sure that vendor is Y2K compliant. If you can't get the right straight answers out of them, find another vendor. Of course, if telco goes down, chances are, so does your access to your alarm company.
      • physical measures: Steel doors, with high-quality locks, are a good idea. Being able to board up windows or glass doors is a good thing. Concrete buildings are also a good thing.
      • Of course, the ultimate backup to your physical security is your insurance company. Check their Y2K compliance, and have fun reading their Y2K compliance statements.
  9. Personnel considerations
    • On duty for the rollover? Having some senior level people available at your ISP for the rollover is a good idea. I hate to say this, but you probably should limit the alcohol consumption at this New Year's company party. If you're in an urban area, having an armed person or two might be a good idea, and that person should avoid the booze. I agree that this sucks.
    • After the rollover depends on what happens. If rioting mobs burn down the city your ISP is in, it isn't likely you'll have many customers left or that the ones that can connect to you have a reasonable expectation of continued service. If you're a regional provider, though, your out of town customers will not care if your city was burned to ashes, they are still going to expect you to be up short of a nuclear detonation. Also remember that you may have emergency traffic running through your system, from disaster management agencies to people trying to find out about the safety of their loved ones. If there are transportation problems, the Internet may be more important than ever for business communication.
    • One possible thing you might consider is to do a company sponsored Y2K preparation program, group purchases of Y2K supplies, etc. See above for more information about that.
  10. Note that SBA loans are available for Y2K remediation and upgrading. Click for information. There is also some special tax treatment for Y2K preparation, click here for information on both and other information available for small business Y2K in general.
  11. Finally, in a disaster, what can you do to help? Check this article out about lessons learned at the Los Alamos fire where the local ISP community came together and put together online clearing houses for disaster-related information almost instantaneously.