idnits 2.17.1 draft-rfced-info-walker-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 7 longer pages, the longest (page 2) being 81 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 8 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** There are 3 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (04 July 1997) is 9791 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) No issues found here. Summary: 9 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 INTERNET-DRAFT EXPIRES JANUARY 1998 INTERNET-DRAFT 4 Network Working Group J. Walker 5 INTERNET-DRAFT Cisco Systems, Inc. 6 04 July 1997 8 The Site Installation Handbook 9 11 Status of this Memo 13 This document is an Internet-Draft. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its areas, 15 and its working groups. Note that other groups may also distribute 16 working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet- Drafts as reference 21 material or to cite them other than as ``work in progress.'' 23 To learn the current status of any Internet-Draft, please check the 24 ``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow 25 Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), 26 munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or 27 ftp.isi.edu (US West Coast). 29 This memo provides information for the Internet community. This memo 30 does not specify an Internet standard. Distribution of this memo is 31 unlimited. 33 Introduction 35 This memo is a first attempt at providing guidance on how to deal with 36 the perplexity of new LAN and WAN site installs. Experienced and 37 less experienced network engineers often do each installation blindly 38 without any form or fashion. This document is an attempt to document 39 specific install issues, practices and procedures. It is also 40 intended to be a future installation reference handbook. Please 41 email me with any comments or additional items that may have been 42 overlooked. Hopefully you will see this as a starting point to 43 collect data for the site installation that you are completing. 45 Purpose of this Work 47 This handbook should be used as a manual for necessary details 48 pertaining to site installs. This manual lists issues and factors 49 that a site must consider when setting up their own Data closets, 50 Wiring closets, or Data Centers. This handbook is only a framework 51 for setting install procedures and practices. In order to have an 52 effective set of procedures and practices, each location will have to 53 make decisions particular to their needs and requirements. 55 Audience 57 The audience for this document is network engineers, system 58 engineers, systems integration specialists, and cable installation 59 specialists. The focus of this document is on the procedures and 60 practices that need to be in place to support any technical data room 61 that a site may be implementing. 63 July 11, 1997 65 - 2 - 67 I/D Site Installation Handbook 04 July 1997 69 Scope 71 This document covers issues about what a site implementation guide 72 should contain, and what kinds of procedures are needed to ensure a 73 successful install. This memo assumes that all preliminary user input 74 into the network design has been completed before site installation. 76 Remember each site has different needs; the installation in one 77 building with one set of requirements might well be different from 78 another building or site. Be sure it fits the needs and requirements 79 of the site and the users involved. To work and be successful it must 80 be timely and functional. 82 Documentation 84 The most important process of the whole install is documentation. 85 This begins with the pre-install document and ends with a post- 86 install document. The items to start with are initial physical and 87 logical network diagrams. Next, what specific protocols and their 88 addresses per interfaces will be needed. All standard contact info 89 for SNMP should be entered into the device and on the documentation. 90 Relevant information that will be used can be very important both 91 before and after the install. It should include circuit numbers 92 along with any other pertinent information like DLCI numbers or 93 framing or encapsulation type, carrier phone numbers and your 94 company's contact names and numbers, utility company phone numbers, 95 and equipment manufacturer numbers along with serial numbers and 96 warranty contract numbers. It is helpful to have a sheet showing 97 rack placement and equipment location placement. To reduce 98 confusion, labels are helpful to document where lines go. However, 99 do not forget to place them on the lines. Also, take advantage of 100 any vendor's place to input descriptions into the network hardware 101 configs. After the install the pre-install documentation can be 102 turned into post-install documentation that can aid in 103 troubleshooting or disaster recovery later. Minimum user guides for 104 equipment installed should be left with the equipment along with the 105 completed post-install documentation. 107 Communication Lines 109 This section deals with what communication lines you will need for 110 the particular site install that is being completed. The most 111 important line that will ever be needed is an async line preferably 112 installed in wiring closets with at least "800#" access for the 113 purpose of troubleshooting with data centers or vendor tech support. 114 In the event of voice troubleshooting the network equipment with a 115 technician or dialing into that same equipment, you will really need 116 this line. In addition to your primary lines, if budget allows, an 118 July 11, 1997 120 - 3 - 122 I/D Site Installation Handbook 04 July 1997 124 ISDN line for WAN backup will save a lot of time and money for you 125 and your users in the event of dedicated line outage. If your budget 126 is tight you can still use an async line for a primary link backup as 127 well. As for the LAN lines this will depend on your environment, 128 just be sure you have enough interfaces for your particular needs, 129 i.e. ATM, Ethernet, Token Ring. The WAN lines should also be ordered 130 for the particular bandwidth requirement this particular site has, 131 i.e. DS-3, OC-3, T1 or FT1. Also, be certain that you know if you 132 need ATM, SONET, Frame Relay, or ISDN. Before you go to the site or 133 send the equipment out, make sure you have all the LAN, WAN, and 134 general cables that are needed to complete the install. 136 Premise or Structure 138 If this is a new install, take measures to ensure that you have the 139 proper location for the data or wiring closet, preferably in the 140 center of the building. Equal distances to all four corners of the 141 office space could save issues with cable run distances. Actual runs 142 of LAN cable should be certified to be of correct distance and type. 143 It is suggested that additional cables are pulled at time of 144 installation if possible, this will allow migration to future 145 technologies and general growth. Always be sure that you have a 146 large enough room for today's equipment and tomorrow's expansion of 147 technology. You can never have enough room or cable. Both existing 148 and new installs should accommodate for equipment rack placement and 149 be free of any hazards such as water pipes that could damage or 150 obstruct the equipment. There should be 36 inches clear on all four 151 sides of the rack. Equipment should be placed in racks in such a way 152 that the removal/replacement of circuit card assemblies is easy. If 153 forced to choose between placement for the viewing of LEDs verses 154 ease of repair, repair wins. Cables should be installed in such a 155 way that they are easily traced and not block access to card removal 156 or installation. Equipment itself should not be placed in such a way 157 that it becomes a tempting shelf. This could block cooling of the 158 equipment or worse, become a shelf for a liquid that could be spilled 159 on the equipment. This can be avoided by placing the equipment near 160 the top of racks or by installing an actual shelf above the 161 electronic equipment. The shelf, mentioned above can make a great 162 location to rest a PC used for configurations or a LAN Monitor device 163 for traps and troubleshooting. It is also very important to have the 164 proper air conditioner tonnage for correct cooling of the room and 165 that it will be on twenty-four hours a day seven days a week. Check 166 with your State and City laws about emergency power shutoff 167 regulations and accommodate accordingly. Two items that are often 168 overlooked are power requirements and receptacle types. Tied in with 170 July 11, 1997 172 - 4 - 174 this is UPS sizing. Check your equipment first, to see if it is AC 175 or DC, next check WATTS, AMPS, VOLTS, and possibly receptacle plug 176 types. Decide if you need online, backup, or standby UPS. Grounding 178 I/D Site Installation Handbook 04 July 1997 180 is also a very important issue for the safety and longevity of your 181 devices. You may want to look at your particular City's Code Book 182 for Data or wiring closets. You may need certain types of fire 183 extinguishers or sprinklers. Remember the old adage, "better safe 184 that sorry." All equipment, if possible, should be mounted so that 185 the power switch and cord are out of the way of traffic. This also 186 applies for LAN and WAN cables. Tie wrap all cables to the data rack 187 for a clean and manageable installation. 189 Security Considerations 191 Physical security of the data room is very important not only to 192 prevent purposeful tampering, but accidental tampering as well. A 193 log should be kept of anyone who walks into the room. This will help 194 in tracking down issues that may mysteriously arise. Alarms for fire 195 should be heard if this is a Data Center room. 197 July 11, 1997 199 - 5 - 201 I/D Site Installation Handbook 04 July 1997 203 Install Template 205 DOCUMENTATION 207 Diagrams 209 Physical 211 Logical 213 Rack Placement 215 Equipment Placement 217 Interfaces 219 Protocols 221 Addresses by Protocol 223 Snmp 225 Contact 227 Location 229 Chassis' ID 231 Numbers 233 Project Contact Phone Numbers 235 Circuit Numbers, DLCI info, PVC info, and Framing info 237 Carrier Phone Numbers and Contacts 239 Utility Companies Phone Numbers and Contacts 241 July 11, 1997 243 - 6 - 245 Equipment Manufacturer Phone Numbers and Contacts 247 I/D Site Installation Handbook 04 July 1997 249 Hardware 251 Device Serial Numbers 253 Device Warranty Numbers or Contract Numbers 255 Hardware Description Field in Device Software 257 To and From Information per Interface 259 Circuit Number on WAN Interfaces 261 Contact Phone Numbers per Interface if Needed 263 Purpose per Interface 265 Labeling 267 Device Name 269 Interface Information 271 COMMUNICATION LINES 273 Async Lines 275 Number Needed 277 LAN Lines and Type 279 July 11, 1997 281 - 7 - 283 Number Needed of Each Type 285 Ethernet 287 Fast Ethernet 289 ATM 291 I/D Site Installation Handbook 04 July 1997 293 Token Ring 295 FDDI 297 WAN Lines and Type 299 Number Needed of Each Type 301 OC-3 303 DS-3 305 T1 307 64K 309 56K 311 Type I.E. ATM, SONET, FRAME-RELAY, DEDICATED, SWITCHED 313 Speed I.E. OC-3 at 10Mbps or DS-3 at 20Mbps 315 Cables 317 Purchase all required cables for LAN and WAN 319 PREMISE 321 July 11, 1997 323 - 8 - 325 Location 327 Size 329 Placement of Equipment on Floor and in Racks 331 Tie wraps for Dressing 333 Air Conditioner Sizing 335 Emergency Power Shutoff 337 Power Requirements for Each Device 339 I/D Site Installation Handbook 04 July 1997 341 Receptacle Type for Each Device 343 UPS Sizing and Type 345 Grounding 347 Fire Equipment Needed 349 City Codes 351 SECURITY 353 Physical Security 355 Locks or Card Readers or Combo Locks Audit Trail 357 Logbook or Card Reader Logs 359 Alarms 361 Audible Alarm Siren to hear building Alarms 363 July 11, 1997 365 - 9 - 367 I/D Site Installation Handbook 04 July 1997 369 Acknowledgments 371 Thanks to my wife for putting up with the long hours and many 372 frustrations during my numerous installations. 374 Thanks goes to Kevin Hanahan (Cisco Systems, Inc.) who is right now 375 going through numerous installations of his own and suggested that we 376 document the procedures in writing not only for us, but for the 377 Internet Community and every engineer out there. His added comments 378 and editing have been immensely appreciated. 380 Thanks also go to my Professor, Chip McGinnis (NCR/Park College) for 381 direction on my Senior Computer Science project. 383 Author's Address 385 James Walker 386 Systems Engineer 387 Cisco Systems, Inc. 388 9300 W. 110th St. 389 Suite 260, Bldg. 55 390 Overland Park, KS 66210 392 Phone: (913) 344-6114 393 EMail: jawalker@CISCO.COM 395 July 11, 1997