Document Foreword
This document is presented as a general
framework. It outlines the sections that should be included in all documents of
this type presented to the customer as well as those that may be specific to different
types of engagement or customer environments. In some instances the author will
have content for all sections, in other instances some may not be valid and may
be removed. Likewise, it is anticipated that in some instances the author will
need to insert additional sections so that is maybe made specific to the
customer environment and/or technology that this document applies to.
This document is section based and section
breaks are clearly marked. When deleting sections, pay close attention to
headers and footers. When changing headers and footers, please note that “First
Page Headers” and “First Page Footers” are different from the rest of the
headers and footers in a particular section.
Therefore, each will have to be edited separately.
After completing the sections of the
document, please do the following:
1.
Right-click on the existing
TOC.
2.
Select “Update field”
3.
Select “Update entire table”
4.
Click “OK”
<……> – denotes text that gives the
author information. Such sections should be removed before customer
distribution
[…….] – denotes that the text that follows
is intended as an example. Such text should be removed or amended before
customer distribution
Printing
Due to the dimensions
of the some graphics, warnings may be seen when printing is attempted. These
will relate to the print area margins supported by the printer to be used. In
practice the document generally prints regardless of such warnings.
AS templates, and the
style guide, have an A4 page orientation. Users of US Letter format may work
with the same templates, but must configure Word to scale documents accordingly
when printing. This may be done as
follows:
·
Open the
document to be printed in Word
·
From the
Tools menu choose Options
·
Select the
Print tab and ensure "Allow A4/Letter paper sizing" has a tick next
to it (in the Printing Options part of this tab)
·
Click OK
·
From the
File menu, choose Print
·
Select the
appropriate printer then click Properties
·
Ensure the
Paper/Output is set to Letter then click OK (different printers will have this
in different part of the Properties windows, but usually it is available by
clicking the Advanced button of the Layout tab)
·
Select
Letter from the Scale to paper size drop down menu of the Print window
·
Click OK
to print, choosing any other options as necessary.
<SECTION BREAK>
<To avoid header/footer and page setup problems do not remove the
carriage return following this line.>
Cisco Systems Advanced Services
<Customer
Name (please do not include a logo) and Project/Deliverable Name>
Network
Implementation Plan
Version
<x.y>
Corporate
Headquarters
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
USA
http://www.cisco.com
Tel: 408
526-4000
800 553-NETS (6387)
Fax: 408
526-4100
|
|
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE
SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND
RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED
WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL
RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND
LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE SET FORTH IN THE INFORMATION
PACKET THAT SHIPPED WITH THE PRODUCT AND ARE INCORPORATED HEREIN BY THIS
REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED
WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The following information is
for FCC compliance of Class A devices: This equipment has been tested and found
to comply with the limits for a Class A digital device, pursuant to part 15 of
the FCC rules. These limits are designed to provide reasonable protection
against harmful interference when the equipment is operated in a commercial
environment. This equipment generates, uses, and can radiate radio-frequency
energy and, if not installed and used in accordance with the instruction
manual, may cause harmful interference to radio communications. Operation of
this equipment in a residential area is likely to cause harmful interference,
in which case users will be required to correct the interference at their own
expense.
The following information is
for FCC compliance of Class B devices: The equipment described in this manual
generates and may radiate radio-frequency energy. If it is not installed in
accordance with Cisco’s installation instructions, it may cause interference
with radio and television reception. This equipment has been tested and found
to comply with the limits for a Class B digital device in accordance with the
specifications in part 15 of the FCC rules. These specifications are designed
to provide reasonable protection against such interference in a residential
installation. However, there is no guarantee that interference will not occur
in a particular installation.
You can determine whether
your equipment is causing interference by turning it off. If the interference
stops, it was probably caused by the Cisco equipment or one of its peripheral
devices. If the equipment causes interference to radio or television reception,
try to correct the interference by using one or more of the following measures:
Turn the television or radio
antenna until the interference stops.
Move the equipment to one
side or the other of the television or radio.
Move the equipment farther
away from the television or radio.
Plug the equipment into an
outlet that is on a different circuit from the television or radio. (That is,
make certain the equipment and the television or radio are on circuits
controlled by different circuit breakers or fuses.)
Modifications to this
product not authorized by Cisco Systems, Inc. could void the FCC approval and
negate your authority to operate the product.
The following third-party
software may be included with your product and will be subject to the software
license agreement:
CiscoWorks software and
documentation are based in part on HP OpenView under license from the
Hewlett-Packard Company. HP OpenView is a trademark of the Hewlett-Packard
Company. Copyright Ó 1992, 1993 Hewlett-Packard Company.
The Cisco implementation of
TCP header compression is an adaptation of a program developed by the
University of California, Berkeley (UCB) as part of UCB’s public domain version
of the UNIX operating system. All rights reserved. Copyright Ó 1981, Regents of the University of California.
Network Time Protocol (NTP).
Copyright Ó 1992, David L. Mills. The University of Delaware makes no
representations about the suitability of this software for any purpose.
Point-to-Point Protocol.
Copyright Ó 1989, Carnegie-Mellon University. All rights reserved. The name of the
University may not be used to endorse or promote products derived from this
software without specific prior written permission.
The Cisco implementation of
TN3270 is an adaptation of the TN3270, curses, and termcap programs developed
by the University of California, Berkeley (UCB) as part of the UCB’s public
domain version of the UNIX operating system. All rights reserved. Copyright Ó 1981-1988, Regents of the University of
California.
Cisco incorporates Fastmac
and TrueView software and the RingRunner chip in some Token Ring products.
Fastmac software is licensed to Cisco by Madge Networks Limited, and the
RingRunner chip is licensed to Cisco by Madge NV. Fastmac, RingRunner, and
TrueView are trademarks and in some jurisdictions registered trademarks of
Madge Networks Limited. Copyright Ó 1995, Madge Networks Limited. All rights
reserved.
Xremote is a trademark of
Network Computing Devices, Inc. Copyright Ó 1989, Network Computing Devices, Inc.,
Mountain View, California. NCD makes no representations about the suitability
of this software for any purpose.
The X Window System is a
trademark of the X Consortium, Cambridge, Massachusetts. All rights reserved.
NOTWITHSTANDING ANY OTHER
WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE
PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM
ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF
MERCHANTABILITY, FITNESS FOR A PRACTICAL PURPOSE AND NONINFRINGEMENT OR ARISING
FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR
ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL
DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA
ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS
SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
AccessPath, AtmDirector,
Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink,
the Cisco Powered Network logo, Cisco
Systems Networking Academy, the Cisco Systems Networking Academy logo, Cisco
Unity, Fast Step, Follow Me Browsing, FormShare, FrameShare, IGX, Internet
Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ logo, iQ
Net Readiness Scorecard, MGX, the Networkers logo, ScriptBuilder, ScriptShare,
SMARTnet, TransPath, Voice LAN, Wavelength Router, and WebViewer, Aironet,
ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified
Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco
Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet
Generation, Enterprise/Solver, EtherChannel, EtherSwitch, FastHub, FastSwitch,
GigaStack, IOS, IP/TV, LightStream, MICA, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing,
RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe,
TeleRouter, and VCO are trademarks or registered trademarks of Cisco Systems,
Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks
mentioned in this document or Web site are the property of their respective
owners. The use of the word partner does not imply a partnership relationship
between Cisco and any other company. (0110R).
Please refer to http://www.cisco.com/logo/ for the latest
information on Cisco logos, branding and trademarks.
INTELLECTUAL PROPERTY
RIGHTS:
THIS DOCUMENT CONTAINS
VALUABLE TRADE SECRETS AND CONFIDENTIAL INFORMATION OF CISCO SYSTEMS, INC. AND
IT’S SUPPLIERS, AND SHALL NOT BE DISCLOSED TO ANY PERSON, ORGANIZATION, OR
ENTITY UNLESS SUCH DISCLOSURE IS SUBJECT TO THE PROVISIONS OF A WRITTEN
NON-DISCLOSURE AND PROPRIETARY RIGHTS AGREEMENT OR INTELLECTUAL PROPERTY
LICENSE AGREEMENT APPROVED BY CISCO SYSTEMS, INC. THE DISTRIBUTION OF THIS
DOCUMENT DOES NOT GRANT ANY LICENSE IN OR RIGHTS, IN WHOLE OR IN PART, TO THE
CONTENT, THE PRODUCT(S), TECHNOLOGY OF INTELLECTUAL PROPERTY DESCRIBED HEREIN.
Network
Implementation Plan
Copyright Ó 2003, Cisco Systems, Inc.
All rights reserved.
COMMERCIAL IN CONFIDENCE.
A
printed copy of this document is considered uncontrolled.
Contents 5
Tables 8
Figures 10
About This Network
Implementation Plan 12
History 12
Review 12
Introduction 14
Preface 14
Related Documents 15
Safety 15
Project Overview 15
High Level Project
Overview 15
Network Overview 15
Network Topology
Diagrams 15
Physical Network Topology 15
Logical Network Topology 15
Project Contact List 15
Site Information 15
Address and Contact
Details 15
Considerations 15
Equipment Floor Plan 15
Network Topology 15
Equipment Order 15
Equipment Ordered From
Cisco by <Customer> 15
Equipment Supplied by
Cisco 15
Equipment Supplied by
<Customer> 15
Low Level
Implementation Plan 15
Assumptions 15
Tools Required 15
Implementation Tasks 15
Step 1.Confirm ESD Procedures 15
Step 2.Prepare Installation Area 15
Step 3.Build Cabinets 15
Step 4.Install Cabinet Power Feeds, Rails and
Protective Earthing 15
Step 5.Unpack Equipment 15
Step 6. Physically
Install Equipment in Cabinet Including Cables Between New Network Devices 15
Step 7.Record Equipment Serial Numbers and
Check Against Delivery Documentation 15
Step 8.Verify Card Modules are Inserted into
the Correct Slot Allocations 15
Step 9.Install Intra Cabinet Power Cabling and
Protective Earth Cabling 15
Step 10.Install Intra and
Inter-Cabinet Communications Cables 15
Step 11.Verify Circuit
Termination in <Customer> Patch Panel 15
Step 12.Power-up Cisco
Equipment 15
Step 13.Verify/Load System
Software/Firmware 15
Step 14.Configure Equipment 15
Step 15.Complete
Installation Tests 15
Step 16.Add Equipment to
<Customer> Network 15
Step 17.Complete
Commissioning Tests 15
Schematic Rack
Diagrams 15
Cabinet Layout Diagram 15
DC Power Distribution
Diagram 15
Equipment Chassis Card
Layout and Serial Numbers 15
<Device> -
<Nodename> 15
Equipment Port
Allocation and Cable Schedule 15
<Rack
Designator> 15
Circuit Information 15
Signaling Link Details 15
Circuit Details 15
Labeling Formats 15
Equipment Software
Requirements 15
Equipment Basic Setup
Procedures 15
Configuration Clearing 15
Software Upgrade 15
MGX8850 RPM IOS Upgrade 15
Equipment
Configurations 15
<Device> -
<Nodename> 15
Network Addressing
Schemes 15
Naming Conventions 15
IP Addressing Scheme 15
Point Code Addressing Scheme 15
<NMS System> -
<Hostname> 15
Installation Tests 15
To verify node errors. 15
Commissioning Tests 15
BGP Neighborship. 15
Photographs 15
Additional Sections 15
Implementation Record 15
Network Implementation
Plan Completion 15
Physical Installation
Completion 15
Implementation
Hand-over 15
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
Author: <Author Name>
<Organization>
Change Authority: <Change
Authority>
Reference Number: < EDCS or other document reference
number, this NIP template is EDCS-99002>
Table 1 Revision History
|
Version No.
|
Issue Date
|
Status
|
Reason for Change
|
|
<1.0>
|
<dd-mmm-yyyy>
|
<Draft,
Released>
|
<First
release, update, etc.>
|
|
|
|
|
|
Table 2 Revision Review
|
Reviewer’s
Details
|
Version No.
|
Date
|
|
<Name>
<Organization>
|
<Version
number>
|
<dd-mmm-yyyy>
|
|
|
|
|
Change Forecast: <High/Medium/Low>
This document will be kept under revision
control.
A printed copy of this document is considered
uncontrolled.
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
<This outline document
template has the reference EDCS-99002 and is available for download from http://wwwin-emea/ca/as/global/templates.htm.>
<To preserve the formatting and
styling of this document and maintain the look and feel of a formal Cisco
manual, the user is recommended to read
and refer to the AS Documentation Style Guide, EDCS-132810, before and
while it is being produced.>
<Provide a brief explanation of the purpose
of this document.>
[example]
The purpose of this document is to provide the
information necessary to carry out the Implementation of equipment at the
location of <Site/PoP name> and to verify basic operation. The
documentation is written as a guide for the Implementation Engineer to follow.
It contains node and site specific information and records the tests and
actions carried out. For this particular project, separate NIP documents will
be issued for other sites in this network.
Although <Customer> may wish to use it as
such, this document is not specifically intended to form a site reference
document.
It is assumed that the Implementation Engineer
has experience of Installation and Commissioning of the
<router/dial-access/WAN-switch, etc.> products covered by this document,
as well as the procedures necessary to upgrade and troubleshoot to a basic
level.
Where side symbols are included, in this
document they have the following meaning:
This
symbol means warning. The user may be
in a situation that could cause bodily injury. Before the user works on the
equipment, they should be aware of hazards involved with electrical circuitry
and be familiar with standard practices for preventing accidents.
This
symbol means caution. In this
situation, the user might do something that could result in equipment damage or
loss of data.
This
symbol means timesaver. The user
might save time by performing or being aware of the action/information
described in the paragraph.
This
symbol means note. The user must add
information, written or typed, to the document during the implementation work
or that the user must take note of the information presented.
This
symbol means tip. This symbol means tip. The text which accompanies this
symbol provides the user with a useful tip.
Due to the dimensions of the cover sheet
graphic, warnings may be seen when printing is attempted. These will relate to
the print area margins supported by the printer to be used. In practice the
cover sheet generally prints regardless of such warnings.
AS templates, and the style guide, have an A4
page orientation (as used in most parts of the world). Users of US Letter format may work with the
same templates, but must configure Word to scale documents accordingly when
printing. This may be done as follows:
· Open the document to be printed in Word
· From the Tools menu choose Options
· Select the Print tab and ensure "Allow
A4/Letter paper sizing" has a tick next to it (in the Printing Options
part of this tab)
· Click OK
· From the File menu, choose Print
· Select the appropriate printer then click
Properties
· Ensure the Paper/Output is set to Letter then
click OK (different printers will have this in different part of the Properties
windows, but usually it is available by clicking the Advanced button of the
Layout tab)
· Select Letter from the Scale to paper size drop
down menu of the Print window
· Click OK to print, choosing any other options
as necessary.
<Provide a list of any relevant documents
which have been produced to date that precede, relate or to which the NIP has
some other dependency, either Cisco or Customer owned.>
[example]
[1] Statement
of Work version
5.0
[2] Project
Plan Document version
1.0
[3] Low
Level Design Document version
3.2
[4] Site
Requirements Specification version
1.1
[5] Network
Staging Plan version
2.0
[6] Cisco
Documentation CD http://cco/univercd/cc/td/doc/product/index.htm
[7] Cisco
Connection Online CCO http://www.cisco.com
<Refer to the product documentation that is
provided with every delivery as the primary source of safety related
information. Provide URL of Cisco Product Documentation - http://www.cisco.com/univercd/home/home.htm. Do not provide a link to specific pages as
this may change in later editions. If this is unavoidable state that such
references may change and that they will not be updated in the scope of the
Cisco work. Highlight any specific points, but take care not to contradict the
published safety instructions or to imply that this document contains a full
source of safety related information. Please include the following paragraph:
Each Engineer shall perform their
duties and obligations using a reasonable degree of care, diligence, skill and
judgement. Equipment shall be handled in strict accordance with sound industry
practice and its deployment and assembly shall at all times conform to the
published documentation.>
[example]
Before installing any equipment refer to all
the product documentation included with each piece of equipment. Cisco also provides an on-line product
documentation reachable at the following URL:
http://www.cisco.com/univercd/home/home.htm
Each Engineer shall perform their duties and
obligations using a reasonable degree of care, diligence, skill and judgement.
Equipment shall be handled in strict accordance with sound industry practice
and it’s deployment and assembly shall at all times conform to the published
documentation. Nevertheless, attention is drawn to the following:
·
Two
people are required to lift equipment chassis. Equipment must be lifted keeping
a straight back, using the legs not the back. Never attempt to lift any of the
chassis by the plastic panels on the front of the chassis, or by the handles on
power supplies or processor modules. These panels and handles were not designed
to support the weight of the chassis.
·
Before
beginning any procedures requiring access to the interior of any equipment,
locate the emergency power-off switch for the room in which you are working - do not assume that it is off, check it
personally.
·
Single
mode fiber line cards are equipped with lasers that emit invisible radiation.
Because invisible laser radiation may be emitted from the aperture of the port
when no cable is connected, avoid exposure to laser radiation and do not stare
into open apertures.
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
<Provide a summary of the project such that
the Implementation Team understand what Cisco and the Customer are trying to
achieve and where this particular activity fits in to the project delivery.>
[example]
The <Customer> network is primarily
designed to handle voice and internet/frame relay traffic with all the
appropriate billing, statistic collection and quality of service provided.
Therefore the network consists of a Frame Relay backbone, Voice Access Gateways
and Gatekeepers for admission control and data access servers.
<Provide a technical summary of the network
- key technologies deployed, etc.>
[example]
The equipment covered in this document
includes:
·
Core
routers: GSR 12008 interconnected by STM-1 POS interfaces.
·
Edge
routers: 7507 that will be connected to the core by means of STM-1 POS
interfaces and by STM-1 ATM interfaces downstream 6400.
·
DSL
Universal Access Concentrators: the 6400 form aggregation point for the
downstream DSLAM over an STM-1 ATM interface.
·
DSLAM: a
6260 will aggregate the DSL connections that run over existing copper wires to
the CPE.
·
CPE: 677
ADSL modems will be used on customer premises to give a full service network to
<Customer> customers.
<Provide diagrams clearly showing the
topology of the network undergoing Implementation and detailing all components
included in this NIP document. These could be physical, logical, site by site,
or otherwise. Diagrams inserted in the Windows Metafile format, .wmf, offer
significant file size savings over full the Visio equivalent and should be used
where the original Visio files are being maintained as separate files. Other
reduced file size formats may also be used where appropriate.>
<Provide a diagram of the physical network
topology.>
[example]
Figure 1 Physical
Network Topology
<Provide a diagram of the logical network
connectivity, where applicable.>
[example]
Figure 2 Logical
Network Topology
<Provide details of the Cisco and Customer
Project Team.>
Cisco Advanced Services Partners may be used as
part of the Cisco Project Team, as listed below.
[example]
Table 3 Project
Contact List
|
Cisco Project Team
|
<Customer> Project Team
|
|
Project Manager:
Telephone:
Email:
|
Project Manager:
Telephone:
Email:
|
|
Project Engineer:
Telephone:
Email:
|
|
|
Design Engineer:
Telephone:
Email:
|
|
|
Account Manager:
Telephone:
Email:
|
|
|
Systems Engineer:
Telephone:
Email:
|
|
|
|
|
|
Partner Project Manager:
Telephone:
Email:
|
|
|
Partner Project Engineer:
Telephone:
Email:
|
|
|
Partner Design Engineer:
Telephone:
Email:
|
|
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
Address and Contact
Details
<Provide the site address, on site contacts
and remote access information.>
[example]
Table 4 Site
Contact Details
|
Site Name
|
|
|
Site Address
|
|
|
Site Contact
|
Telephone:
Facsimile:
Email:
|
|
Hours of Operation
|
|
|
Remote Access
|
|
<Provide
details of any additional activities or restrictions that apply to this
specific Implementation. Such information may be taken from the Site Survey or
other sources.>
[example]
This site is shared by multiple ISPs so
deliveries must be clearly marked and identified for the attention of the
<Customer> contact.
<Provide
a and/or diagram showing the floor plan of where the equipment is located.
Include locations of access equipment the network must connect to, circuit termination
points, etc. Use WMF, or other reduced file size, format files where possible
for diagrams.>
[example]
Table 5 Equipment Floor Plan
|
Floor
|
|
|
Room
|
|
|
Suite
|
|
|
Position
|
|
|
Rack
No.
|
|
Figure 3 Equipment Floor Plan
<Provide
a diagram of the site network connectivity, where applicable. This should
include the Customer network and any local infrastructure that could be of use
to Cisco Engineers that need to access the internet.>
[example]
Figure 4 Site Network Topology
<SECTION BREAK
to avoid header/footer and page setup problems do not remove the carriage
return following this line>
<Provide details of part numbers and
quantities. This information may be taken directly from the Customer order
details on CCO. Include the order number. Any other equipment that is necessary
to complete the Implementation should be identified, e.g. Customer supplied
power distribution strips, additional cables, crimp connectors, etc.>
Equipment Ordered From Cisco by <Customer>
<Provide details of the equipment the
Customer has ordered from Cisco that is necessary to complete the
Implementation, e.g. Cisco routers, Cisco switches, etc. Include a Cisco Sales
Order reference where possible.>
[example]
Table 6 Cisco
Ordered Equipment
|
Cisco PO No.
|
Part No.
|
Description
|
Qty
|
|
A123456
|
BPX8650
|
BPX IP+ATM switch: BPX w/BCC-4, ASM, backcards, Cisco7204TSC
|
1
|
|
A123456
|
BPX-BCC-4V-R
|
Redundant BCC, 20 Gbps,
128MB DRAM, 4MB BRAM, BCC-3-BC
|
1
|
|
A123456
|
BPX-DC
|
48VDC Power Input
Module
|
1
|
|
A123456
|
BPX-BXM-155-8
|
8-p OC3/STM-1
Module:16k cons, 230k/230k cell buff
|
2
|
|
A123456
|
BPX-SMF-155-8-BC
|
8-p, OC3/STM-1
Multi-Mode Fiber Back Card (up to 2km span)
|
2
|
|
A123456
|
CAB-SMF-SC-10
|
10ft Single Mode Fiber
Cable (SC term.)
|
12
|
|
A123456
|
PWR-7200-DC
|
Cisco 7200 DC Power
Supply Option
|
1
|
|
A123456
|
PWR-7200/2-DC
|
Cisco 7200 Dual DC
Power Supply Option
|
1
|
|
A123456
|
C7200-I/O-FE
|
Cisco 7200 Input/Output
Controller with Fast Ethernet Port
|
1
|
|
A123456
|
MEM-I/O-FLC20M
|
Cisco 7200 I/O PCMCIA
Flash Memory, 20 MB Option
|
1
|
|
A123456
|
MEM-I/O-FLD110M
|
Cisco 7200 I/O PCMCIA
Flash Disk, 110 MB Option
|
1
|
|
A123456
|
NPE-200
|
Cisco 7200 Network
Processing Engine, 4 MB SRAM
|
1
|
|
A123456
|
MEM-NPE-128MB
|
128MB Memory for
NPE-200/NPE-150/NPE-100 in 7200 Series
|
1
|
|
A123456
|
PA-A3-OC3SMI
|
1-Port ATM Enhanced
OC3c/STM1 Single mode(IR)Port Adapter
|
1
|
|
A123456
|
MGX8850
|
MGX 8850, 24 I/O+4 SRM
slots, PXM1, PXM-UI, Cooling, 19" Mnt
|
1
|
|
A123456
|
MGX-DC
|
MGX 8850 DC PEM and
MGX-CAB-AC/DC
|
1
|
|
A123456
|
PXM1-4-155-R
|
PXM1, 4 155 Mbps
broadband ports (upgrade of PXM1)
|
1
|
|
A123456
|
MGX-SMFIR-4-155/B
|
PXM1 4 port 155 Mbps
Back Card, SMF-IR, SC connectors
|
1
|
|
A123456
|
MGX-RPM-128/B
|
Route Processor Module
- 128 Meg of DRAM
|
1
|
|
A123456
|
MGX-RJ45-FE
|
Fast Ethernet Back Card
for the RPM, RJ45 connector
|
1
|
|
A123456
|
AX-CESM-8E1
|
Circuit Emulation
Service Module, Eight E1 Ports
|
1
|
|
A123456
|
AX-FRSM-8E1-C
|
Frame Service Module,
Eight Channelized E1 Ports
|
1
|
|
A123456
|
AX-RJ48-8E1
|
Redundancy Back Card
for AX-RJ48-8E1
|
2
|
|
A123456
|
CISCO7507/4X2
|
Cisco 7507 7-Slot, 2
CyBus, 2 RSP4, Dual Power Supply
|
1
|
|
A123456
|
PWR-7507/4X2-DC
|
Cisco 7507/4x2 Dual AC
Power Supply Option
|
1
|
|
A123456
|
MEM-RSP4-256M
|
RSP4 256MB DRAM Option
|
2
|
|
A123456
|
MEM-RSP4-FLC20M
|
RSP4 Flash Card: 20 MB
Option
|
2
|
|
A123456
|
VIP2-50
|
Versatile Interface
Processor 2, Model 50
|
3
|
|
A123456
|
MEM-VIP250-128M-D
|
128 Mbytes DRAM Option
for VIP2-50/xIP-50
|
3
|
|
A123456
|
MEM-VIP250-8M-S
|
8 Mbytes SRAM Option
for VIP2-50/xIP-50
|
3
|
|
A123456
|
PA-A3-OC3SMI
|
1-Port ATM Enhanced
OC3c/STM1 Single mode(IR)Port Adapter
|
1
|
|
A123456
|
PA-8T-V35
|
8-Port Serial, V.35
Port Adapter
|
2
|
|
A123456
|
PA-2FEISL-TX
|
2 port Fast
Ethernet/ISL 100BaseTx Port Adapter
|